• Create a taxonomy (schema) for the entitlement data tag
• Define conformance details and scoping requirements
• Build an implementation guide
• Define examples (use cases) to accompany implementation guidance
• Specify the standard’s alignment with other standards
• Generate an XML schema definition for entitlement tag creation

• Use-cases - Define and describe use-cases to drive generation of Taxonomy.
• Alignment - Describe alignment with and relationships to existing SAM, service management and other standards.
• Elements definition - Elements, interfaces, etc., that will be part of the standard.
• Entitlements definition - Define the minimum requirements to identify and prove compliance for common licensing models.
• Implementation - Describe what must be implemented, and how to implement, at a minimum to claim 19770-3 compatibility.
• Evangelism - Describe market demand, benefits, relationships to existing standards, and other public relations tasks.
• XML Editors - XML editors.
• Review & Edit - Document editors.

Participation is open to qualified individuals

Participation in the 19770-3 OWG is open to any qualified individuals with relevant expertise in software asset management, software licensing, software manufacturing, and related disciplines. We also welcome editorial help from individuals who have technical documentation experience. All OWG members are required to sign a statement acknowledging that the results of the work being done shall be copyright of ISO/IEC. Copyright in all drafts shall be held by ISO/IEC. All 19770-3 OWG members shall be expected to contribute meaningful content to the standard and remain active in order to maintain their membership status. To volunteer for the ISO/IEC 19770-3 OWG, click this link to send an email request to John Tomeny: johnt@ sassafras.com

ISO/IEC Software Asset Management (SAM) Standards White Paper
- 19770-2 Software Identification Tag
- 19770-3 Software Entitlement Tag

Click here to download the (pdf) white paper.

International Standards for Software Asset Management (SAM) provide a model to follow in setting up and operating an asset management system specifically oriented to the management of software assets. The model incorporates the features on which experts in the field have reached a consensus as being the international state of the art. Through the use of the SAM family of standards, organizations can develop and implement a framework for managing their software assets and prepare for an internal or external assessment of their SAM processes.

The focus of this presentation is on two ISO/IEC SAM Standards, one published and one under development: ISO/IEC 19770-2 Software Identification Tag and 19770-3 Software Entitlement Tag, and how they fit into the SAM ecosystem. ISO/IEC 19770-2 provides a standard for authoritative identification of software installations to assist in complete and positive identification of installed software. ISO/IEC 19770-3 is under development and will provide a framework and criterion of measurement for creating unambiguous definitions of entitlements to assist in effective software reconciliation, effective cost reduction in software license management, and proof of compliance.

Meetings and Time Commitment

The full OWG hosts conference call meetings on Tuesdays as needed - not weekly unless necessary. The initial purpose of full OWG meetings is to assist with collaboration between the OWG working committees and to provide overall direction to all members. As work develops on the standard, some of the technical work that spans the individual committees will be addressed in the Tuesday conference calls.

The primary technical work of the ISO/IEC 19770-3 OWG takes place in the working committees. Each committee schedules their own meetings as needed to accomplish their work. Members will confer with each other during the committee calls and do most of their work between calls. Time commitment is difficult to assess since it tends to be driven on an individual basis depending on the level of interest that each participant demonstrates in the work. But it would not be unusual to anticipate one conference call per week (for up to one hour) either with the OWG or with your working committee, and then whatever amount of time you are personally willing to commit to research and development tasks between calls.