ISO/TS 8000-120:2009(E)

Annex D
(informative)

Use cases

D.1 General

This annex contains a number of use cases illustrating the business requirements for, and use of, provenance information for property values. In accordance with ISO 8000-110, master data messages are coded using concepts from a data dictionary. Table D.1 lists the concept identifiers that are used in this annex and their meanings.

Table D.1 — Concepts used

Identifier Type Name

0161-1#02-015007#1

property

enclosure material

0161-1#07-000435#1

value of property

ceramic

0161-1#07-185586#1

value of property

resin

NOTE 1 This annex uses concept identifiers from the ECCMA Open Technical Dictionary (eOTD). Any dictionary that met the requirements of ISO 8000-110 could have been used.

Table D.2 lists the organizations that are referenced in this annex with their identifiers.

Table D.2 — Organizations referenced

Identifier Name Role

0161-XYZQW

IM1

Manager of catalogue of items of supply

0161-ABCDE

ABC Company

Manufacturer of microcircuits

0161-BCDEF

XYZ Company

Data aggregator

NOTE 2 This annex uses organization identifiers from the eOTD. Any ISO/IEC 6523 compliant organization identification scheme could have been used.

NOTE 3 See ISO/IEC 6523-1 for the specification of the elements of an organization identifier.

IM1 maintains is master data for items of supply in IOS-MS (Item of Supply Management System).

Table D.3 lists the persons who are referenced in this annex with thier identifiers.

Table D.3 — Persons referenced

Identifier Name Company Role

JPS3642

John P. Smith

IM1

Cataloguer

ROLLINS1

William F. Rollins

ABC Company

Engineer

BAKER2

Catherine A. Baker

ABC Company

Engineer

DOE1

Jane E. Doe

ABC Company

Customer service representative

NOTE 4 The codes "0161-ABCDE", "0161-BCDEF" and "0161-XYZQW" are dummy codes used for illustration purposes.

In this annex, times are given to the day, e.g., 1998-12-01, for simplicity. This part of ISO 8000 allows times to be given to any finer level of precision, e.g., 1998-12-01T08:41:36.118.

Data is given in coded and decoded form, using the notation in the Introduction. An actual master data message conforming to this part of ISO 8000 would have data in coded form.

D.2 Abbreviated terms

For the purposes of this annex, the following abbreviated terms apply:

ECCMA Electronic Commerce Code Management Association
eOTD ECCMA Open Technical Dictionary
id identifier
PDM product data management

D.3 UC1: Initial cataloguing of item of production

This use case covers initial cataloguing of an item of production by a manufacturer. The microcurcuit described in C.1 is used as sample data for this use case.

Actors:

William F. Rollins

engineer at ABC Company assigned to design the microcircuit

Steps:

1

Mr. Rollins designs the microcircuit with the properties listed in C.1.

2

On 1998-02-07, Mr. Rollins enters the property values into the record for the item in the manufacturer's product data management (PDM) system, including the property value to indicate that the chosen enclosure material is ceramic.

3

The PDM system records the property values with provenance information. The property value that the enclosure material is ceramic is recorded as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-ABCDE", "ROLLINS1", 1998-02-07)))

Decoded:

pv("enclosure material", "ceramic",
   (create("ABC Company", "William F. Rollins", 1998-02-07)))

D.4 UC2: Initial cataloguing of item of supply from drawings

This use case covers initial assignment of a value for the item of supply described in C.1 during initial cataloguing. The cataloguer transcribes technical property values from information on drawings.

Actors:

John P. Smith

cataloguer at IM1 responsible for initial cataloguing of the microcircuit

Steps:

1

A request for codification is forwarded to IM1 with supporting documentation, including the part drawings.

2

Mr. Smith determines properties of the microcircuit from the drawings and other documentation supplied with the codification request.

3

On 1998-06-13, Mr. Smith enters the property values into the record for the item in IOS-MS, including the property value to indicate that the chosen enclosure material is ceramic.

4

IOS-MS records the property values with provenance information. The property value that the enclosure material is ceramic is recorded as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-XYZQW", "JPS3642", 1998-10-11)))

Decoded:

pv("enclosure material", "ceramic",
   (create("IM1", "John P. Smith", 1998-10-11)))

5

Once all property values are entered, the NSN (5962-00-057-7131) is assigned to the item.

D.5 UC3: Initial cataloguing of item of supply using cataloguing at source

This use case covers initial assignment of a value for the item of supply described in C.1 during initial cataloguing by IM1. The cataloguer obtains technical property values by querying the manufacturer.

Actors:

John P. Smith

cataloguer at IM1 responsible for initial cataloguing of the microcircuit

Jane E. Doe

customer service representative at ABC Company responsible for responding to requests for data

Preconditions:

1

Use case UC1 has been executed.

Steps:

1

A request for codification is forwarded to IM1 with supporting documentation, including the part number

2

On 1998-10-11 Mr. Smith sends a query to ABC Company asking for values for all properties of the microcircuit required by IM1's data requirements statement (DRS).

3

On 1998-10-12 Ms. Doe extracts the properties of the microcircuit from its PDM system and sends them in a master data message to Mr. Smith

4

On 1998-10-15, after validating the property values received from the manufacturer against IM1's DRS, Mr. Smith copies the property values into the record for the item in IOS-MS, including the property value to indicate that the chosen enclosure material is ceramic.

5

The IOS-MS records the property values with provenance information. The property value that the enclosure material is ceramic is recorded as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-ABCDE", "ROLLINS1", 1998-02-07),
    extract("0161-ABCDE", "DOE1", 1998-10-12)))

Decoded:

pv("enclosure material", "0161-1#07-000435#1",
   (create("ABC Company", "William F. Rollins", 1998-02-07),
    extract("ABC Company", "Jane E. Doe", 1998-10-12)))

Since the property value for the enclosure material is copied from data provided by the manufacturer, the create event refers back to the original entry of the property value at the manufacturer.

6

Once all property values are entered, the NSN (5962-00-057-7131) is assigned to the item.

D.6 UC4: Update catalogue entry for item of production

This use case covers the update of the catalogue record of an item of production by a manufacturer. The microcurcuit described in C.1 is used as sample data for this use case.

Actors:

Catherine A. Baker

engineer at ABC Company assigned to update the design of the microcircuit

Preconditions:

1

Use case UC1 has been executed.

Steps:

1

Ms. Baker creates a new version of the design of the microcircuit, changing the enclosure material to resin.

2

On 1998-11-01, Ms. Baker enters the new property value for enclosure material into the manufacturer's PDM system, indicating that the enclosure material is resin.

3

The PDM system records the new property value with provenance information as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-185586#1",
   (create("0161-ABCDE", "BAKER2", 1998-11-01)))

Decoded:

pv("enclosure material", "resin",
   (create("ABC Company", "Catherine A. Baker", 1998-11-01)))

D.7 UC5: Publication of initial catalogue record for item of supply

This use case covers the publication of the catalogue record of an item of supply by the master data manager. The microcurcuit described in C.1 is used as sample data for this use case.

Preconditions:

1

Use case UC3 has been executed.

Steps:

1

On 1999-12-04 a batch process that extracts characteristic data from IOS-MS runs automatically.

2

The data is written to CD-ROMs and delivered to subscribers.

3

The property value with provenance information for the enclosure material of the microcircuit is written to the CD-ROM as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-ABCDE", "ROLLINS1", 1998-02-07),
    extract("0161-ABCDE", "DOE1", 1998-10-11),
    extract("0161-XYZQW", null, 1999-12-04)))

Decoded:

pv("enclosure material", "ceramic",
   (create("ABC Company", "William F. Rollins", 1998-02-07),
    extract("ABC Company", "Jane E. Doe", 1998-10-11),
    extract("IM1", null, 1999-12-04)))

D.8 UC6: Update to catalogue entry for item of supply using cataloguing at source

This use case covers the update of a property value for the item of supply described in C.1 during a data quality assurance program. The cataloguer obtains the technical property values by querying the manufacturer.

Actors:

John P. Smith

cataloguer at IM1 responsible for maintaining the catalogue record of the microcircuit

Jane E. Doe

customer service representative at ABC Company responsible for responding to requests for data

Preconditions:

1

Use case UC4 has been executed.

Steps:

1

As part of a data quality assurance program, on 1998-12-05 Mr. Smith sends ABC Company a query to verify the property values for the microcircuit.

2

On 1998-12-07 Ms. Doe extracts the properties of the microcircuit from its PDM system and sends them in a master data message to Mr. Smith

3

Mr. Smith compares the property values in the master data message to those in IOS-MS, and determines that the enclosure material property has changed.

4

On 1998-12-10, after validating the property value against IM1's DRS, Mr. Smith copies the property value into the record for the item in IOS-MS, to indicate that the chosen enclosure material is resin

5

IOS-MS records the updated property value with provenance information as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-185586#1",
   (create("0161-ABCDE", "BAKER2", 1998-11-01),
    extract("0161-ABCDE", "DOE1", 1998-12-07)))

Decoded:

pv("0161-1#02-015007#1", "0161-1#07-185586#1",
   (create("ABC Company", "Catherine A. Baker", 1998-11-01),
    extract("ABC Company", "Jane E. Doe", 1998-12-07)))

Since the property value for the enclosure material is copied from data provided by the manufacturer, the create event refers back to the original entry of the property value at the manufacturer.

D.9 UC7: Aggregation of information on item of supply

This use case covers the extraction of data on an item of supply from IOS-MS and integration with other data.

Preconditions:

1

Use case UC5 has been executed.

Steps:

1

XYZ Company receives a copy of the CD-ROM and integrates it with its database of master data.

2

The property value with provenance information for the enclosure material of the microcircuit is written to the aggregator's database of master data as:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-ABCDE", "ROLLINS1", 1998-02-07),
    extract("0161-ABCDE", "DOE1", 1998-10-11),
    extract("0161-XYZQW", null, 1999-12-04)))

Decoded:

pv("enclosure material", "ceramic",
   (create("ABC Company", "William F. Rollins", 1998-02-07),
    extract("ABC Company", "Jane E. Doe", 1998-10-11),
    extract("IM1", null, 1999-12-04)))

D.10 UC8: Review of catalogue entry for item of supply using cataloguing at source

This use case covers the review of a property value for the item of supply described in C.1 during a data quality assurance program. The cataloguer obtains the technical property values by querying the manufacturer.

Actors:

John P. Smith

cataloguer at IM1 responsible for maintaining the catalogue record of the microcircuit

Preconditions:

1

Use cases UC6 and UC7 have been executed.

Steps:

1

As part of a data quality assurance program, on 1998-12-05 Mr. Smith sends ABC Company a query to verify the property values for the microcircuit.

2

ABC Company does not respond.

3

Mr. Smith sends a query for data about the microcircuit to XYZ Company's data service.

4

On 1999-02-21 the data service responds with a record containing the following:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-000435#1",
   (create("0161-ABCDE", "ROLLINS1", 1998-02-07),
    extract("0161-ABCDE", "DOE1", 1998-10-11),
    extract("0161-XYZQW", null, 1999-12-04),
    extract("0161-BCDEF", null, 1999-02-21)))

Decoded:

pv("enclosure material", "ceramic",
   (create("ABC Company", "William F. Rollins", 1998-02-07),
    extract("ABC Company", "Jane E. Doe", 1998-10-11),
    extract("IM1", null, 1999-12-04),
    extract("XYZ Company", null, 1999-02-21)))

5

Mr. Smith compares the property value returned by the data service with that in IOS-MS:

Coded:

pv("0161-1#02-015007#1", "0161-1#07-185586#1",
   (create("0161-ABCDE", "BAKER2", 1998-11-01),
    extract("0161-ABCDE", "DOE1", 1998-12-07)))

Decoded:

pv("enclosure material", "resin",
   (create("ABC Company", "Catherine A. Baker", 1998-11-01),
    extract("ABC Company", "Jane E. Doe", 1998-12-07)))

6

By comparing the dates of the create events, Mr. Smith easily determines that the property value in IOS-MS is more up-to-date than the property value sent by the data service; furthermore, the orgID in the extract("0161-XYZQW", null, 1999-12-04) event indicates that the property value from the data service is an echo of an older value from IOS-MS. Therefore, he does not make any update to IOS-MS based on this data.


© ISO 2009 — All rights reserved