SMI Scoping Document - Launch In Context subprofile - Target SMI-S Release 1.5

Sep 11, 2026

SMI Scoping Document defines requirements for adding Launch-in-Context (LIC) support to SMI-S 1.5 by introducing a new LIC subprofile leveraging the Access Points subprofile. The work aims to enable storage customers to integrate tools, SRMs, and element managers with seamless access to required storage management applications. It specifies objectives for representing LIC points with launch metadata, linking LIC points to the management domain, and providing concrete LIC capability representations, including instance behavior and RemoteServiceAccessPoint requirements.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages7

Reading Time3 min

AccessFree to download

1 Description

1.1 Short Description

1.2 Feature Mapping Requirements

1.3 Specific Objectives within Scope

2 Dependencies

2.1 TWG Dependencies

2.2 DMTF WG Dependencies

2.3 Other Standards Dependencies

2.4 Author Dependencies

3 Modeling Requirements/Detailed Description

3.1 Overview

3.2 Instance Diagram

3.3 RemoteServiceAccessPoint

SMI Scoping Document Scoping Document for Launch In Context subprofile Duane Baldwin, John Crandall, Martine Wedlake June 25, 2008 Target SMI-S Release: 1.5 NOTE: All sections of the scoping document are optional. However, the champion should attempt to fill out all sections for which there is information available. NOTE: A scoping document is complete (you may exit scoping) as soon as the scoping document (with whatever level of detail) passes a TWG ballot. NOTE: The official Release Statement of Work will be derived from balloted scoping documents. Presentations may be used at TSG face to face meetings to explain what the item is all about and answer concerns, but the Statement of Work will be derived from the balloted Scoping Document. 1 Description This section provides a short description of the work item and how it will address the related Markets Requirements. Add Launch-in-Context (LIC) support in SMI-S via the addition of a new LIC subprofile that leverages the Access Points subprofile. This new subprofile will be developed in the Core TWG and will be part of the SMI-S 1.5 Common Profiles book. Providing solutions to storage customers that enable the integration of various tools, SRMs, and element managers they use to run their business will promote the adoption of SMI-S and provide real value to the customer. Launch-in-Context is one way to provide a basic level of integration and seamless access to storage management tools & applications essential to the customer. 1.1 Short Description Provide a short description (one or two sentences) of the subject of the Scoping Document. This section is to be used in the creation of the Statement of Work for the SMI-S Release. If nothing is provided, “Not Available” will be placed in the Statement of Work. Add Launch-in-Context (LIC) support in SMI-S via the addition of a new LIC subprofile that leverages the Access Points subprofile. 1.2 Feature Mapping Requirements Identify if you believe this scoping document addresses any requirements from the Feature Mapping document. An example table is shown below: | Req \# | Requirement | Capability | | --- | --- | --- | SMI Scoping Document | | | | | --- | --- | --- | | | | | | | | | 1.3 Specific Objectives within Scope List (bulleted list) the specific objectives that are intended to be supported by the work outlined in this scoping document. • Represent LIC points with meta-data to explain how to establish launch (e.g., SSO, context, parameters, etc.) • Link LIC point to the management domain • Provide concrete representation of LIC capabilities 2 Dependencies NOTE: All the dependencies do not have to be identified upfront. However, any dependencies that are discovered during development of the spec material represents a risk to the scoped item. If a new dependency “discovered” during development, that dependency can cause the item in question to be deferred to a future release. 2.1 TWG Dependencies Describe known dependencies between functions in this scoping document and functions or profiles owned by other TWGs. -No direct dependencies outside of Core. But being a common subprofile, various device types may choose to implement. 2.2 DMTF WG Dependencies Describe known dependencies between functions in this scoping document and mofs or profiles owned by DMTF WGs. -Currently none. New classes are being proposed as SNIA classes. SMI Scoping Document 2.3 Other Standards Dependencies If the change to SMI-S requires work on the part of any other standards organization (e.g., T11, T10 or IETF) then list those dependencies. For example, if CIM over SCSI depends on a T10 change, then the T10 dependency should be identified. -None. 2.4 Author Dependencies Identify the known existing Spec Clauses (e.g., Profiles) and Authors that are impacted by this scoping document. If agreement from the author has been achieved, indicate that the author has agreed. The follow

FAQs

What is the purpose of this scoping document for SMI-S 1.5?

It defines how to add Launch-in-Context (LIC) support to SMI-S 1.5 via a new LIC subprofile that leverages the Access Points subprofile.

What objectives are intended to be supported within scope?

The scope includes representing LIC points with launch metadata, linking LIC points to the management domain, and providing concrete representations of LIC capabilities.

What kind of LIC entry points are supported initially?

The document states support for URL-based LIC entry points now, while other entry points such as direct invocation will be added later.

Sep 11, 2026

Uploaded by eBook King