Nato Product Data Model (Npdm)

8/3/2019 Nato Product Data Model (Npdm)

1/154

NATO CALS Office (NCO) - November 2000

NORTH ATLANTIC TREATY ORGANIZATION

ORGANISATION DU TRAITE DE L'ATLANTIQUE NORD

TheNATO Product Data Model (NPDM) is a conceptual data model. It defines a common set of

data definitions and data structures to support Defence System technical information management,

throughout its life cycle, in the context of NATO nations and NATO industries.

The NPDM addresses the NATO requirement for data interoperability between different

Information Systems by delivering a common data semantic and thus enabling consistency of interfaces

at the information level without requiring standardization of hardware or software.

The NPDM uses EXPRESS, ISO 10303-11, as the modelling language to enable both humanunderstanding and computer processing of these semantics.

NPDM version 4.00 has been developed by the NATO CALS Office (NCO) under the guidance of

the NATO CALS Management Board (NCMB) with contributions from Association GOSET, France,

Daimler Chrysler Aerospace (former DASA), Germany, Eurostep Limited, United Kingdom and

Metasistemi S.p.A,Italy.

Intellectual Property Rights (IPR) for this document are owned by NATO. The NATO CALS Office

grants permission to photocopy or otherwise reproduce this material for internal use only and under the

conditions that it will remain unchanged and that ownership by the NCO is recognized. This document

may not be copied for sale or profit.

Comments or observations on layout, content and future distribution of this document are welcomedby the NATO CALS Office.

Contacts

NPDM Custodian

Lt.Col. Boye Tranum

tel. +32.2.707.35935

fax +32.2.707.3598

e-mail [email protected]


2/154

NATO CALS Office (NCO) - November 2000

TABLE OF CONTENT

1. Introduction.............................................................................................................. 11.1 General..........................................................................................................................................1

1.2 Technical view..............................................................................................................................1

1.3 A Brief History..............................................................................................................................2

1.4 What is new in Version 4.00.........................................................................................................4

1.5 Motivation.....................................................................................................................................5

1.6 Information Modeling...................................................................................................................6

2. How to Use the NPDM............................................................................................. 82.1 Specifying Information Requirements...........................................................................................8

2.2 Defining a Common Vocabulary...................................................................................................9

2.3 Implementing an Integrated Product Database............................................................................10

2.3.1 In the Industry .....................................................................................................................11

2.3.2 In a Project..........................................................................................................................12

2.3.3 In the NATO Armed Forces................................................................................................13

2.4 How to Implement the NPDM ....................................................................................................132.5 To Create a Physical Model........................................................................................................14

2.5.1 The Requirement.................................................................................................................14

2.5.2 The Method.........................................................................................................................15

3. Model Overview ..................................................................................................... 173.1 The High Level Model................................................................................................................17

3.2 Model Organization ....................................................................................................................18

4. The Core Model (CoreModel)............................................................................... 204.1 Overview.....................................................................................................................................20

4.2 Description..................................................................................................................................21

4.2.1 Product Design....................................................................................................................21

4.2.2 Product Instance..................................................................................................................26

4.2.3 Crossing between Breakdowns and Product Design Structure............................................304.3 EXPRESS G Diagrams...............................................................................................................31

4.4 EXPRESS Definition..................................................................................................................32

4.4.1 alias_select ..........................................................................................................................32

4.4.2 breakdown_type..................................................................................................................32

4.4.3 contracted_items .................................................................................................................33

4.4.4 element_type .......................................................................................................................33

4.4.5 factor ...................................................................................................................................33

4.4.6 indenture_level....................................................................................................................33

4.4.7 procurement_project_name.................................................................................................33

4.4.8 realisation_select.................................................................................................................33

4.4.9 standard_breakdown_type...................................................................................................33

4.4.10 standard_element_type........................................................................................................33

4.4.11 value_select.........................................................................................................................344.4.12 adaptive_maintenance .........................................................................................................34

4.4.13 alias_identification..............................................................................................................34

4.4.14 alternate_element_relationship............................................................................................34

4.4.15 alternate_product_instance_relationship .............................................................................34

4.4.16 alternate_product_relationship............................................................................................34

4.4.17 applied_contract_assignment ..............................................................................................35

4.4.18 assembly_component_usage ...............................................................................................35

4.4.19 breakdown...........................................................................................................................35

4.4.20 classification_system...........................................................................................................35

4.4.21 container_usage...................................................................................................................35

4.4.22 contract_assignment............................................................................................................36

4.4.23 corrective_maintenance.......................................................................................................364.4.24 element................................................................................................................................36


3/154


4/154

NATO Product Data Model (NPDM) Version 4.00

iv

5. Configuration.......................................................................................................... 515.1 Overview.....................................................................................................................................51

5.2 Description..................................................................................................................................51

5.2.1 Configuration Items.............................................................................................................51

5.2.2 Configuration Change .........................................................................................................53

5.2.3 Product Concept..................................................................................................................545.3 EXPRESS G Diagrams...............................................................................................................57

5.4 EXPRESS Definition..................................................................................................................58

5.4.1 activity_element_select .......................................................................................................58

5.4.2 configured_specification_select..........................................................................................59

5.4.3 operator ...............................................................................................................................59

5.4.4 solution_select.....................................................................................................................59

5.4.5 specification_operand_select ..............................................................................................59

5.4.6 types_of_role.......................................................................................................................59

5.4.7 activity.................................................................................................................................59

5.4.8 activity_element ..................................................................................................................60

5.4.9 activity_relationship............................................................................................................60

5.4.10 configuration_effectivity.....................................................................................................61

5.4.11 configuration_item..............................................................................................................615.4.12 configuration_item_characterization...................................................................................61

5.4.13 configuration_item_relationship .........................................................................................62

5.4.14 configuration_item_solution ...............................................................................................62

5.4.15 dated_effectivity..................................................................................................................62

5.4.16 lot_effectivity......................................................................................................................62

5.4.17 product_concept..................................................................................................................63

5.4.18 product_concept_category_association...............................................................................63

5.4.19 product_concept_condition_association .............................................................................64

5.4.20 product_concept_inclusion_association..............................................................................64

5.4.21 product_concept_relationship .............................................................................................64

5.4.22 product_concept_specification_association ........................................................................65

5.4.23 serial_numbered_effectivity................................................................................................655.4.24 specification ........................................................................................................................65

5.4.25 specification_category.........................................................................................................66

5.4.26 specification_expression .....................................................................................................66

5.4.27 specification_inclusion........................................................................................................66

5.4.28 work_order..........................................................................................................................67

5.4.29 work_request.......................................................................................................................67

6. Failure Analysis (Anomaly)................................................................................... 686.1 Overview.....................................................................................................................................68

6.2 Description..................................................................................................................................68

6.2.1 Effects .................................................................................................................................68

6.2.2 Causal relationships ............................................................................................................69

6.3 EXPRESS G Diagrams...............................................................................................................71

6.4 Definitions...................................................................................................................................726.4.1 detection_method_category ................................................................................................72

6.4.2 probability...........................................................................................................................72

6.4.3 product_anomaly_or_anomaly_in_mission_phase..............................................................72

6.4.4 safety_hazard_severity........................................................................................................72

6.4.5 task_assignment_logic ........................................................................................................72

6.4.6 and_consequential_failure_relationship..............................................................................73

6.4.7 anomaly_in_mission_phase.................................................................................................73

6.4.8 cause_description................................................................................................................73

6.4.9 compensating_provision......................................................................................................73

6.4.10 consequence_probability.....................................................................................................73

6.4.11 consequential_failure_mode................................................................................................73

6.4.12 consequential_failure_relationship......................................................................................74

6.4.13 damage................................................................................................................................74


5/154


v

6.4.14 design_provision.................................................................................................................74

6.4.15 detection_method................................................................................................................74

6.4.16 effect ...................................................................................................................................74

6.4.17 failure_mode .......................................................................................................................75

6.4.18 failure_mode_from_specified_source.................................................................................75

6.4.19 mission................................................................................................................................756.4.20 mission_phase.....................................................................................................................75

6.4.21 mode_effect_assignment .....................................................................................................76

6.4.22 operator_action ...................................................................................................................76

6.4.23 or_consequential_failure_relationship ................................................................................76

6.4.24 other_item_effect ................................................................................................................77

6.4.25 preventive_task_assignment................................................................................................77

6.4.26 primary_failure....................................................................................................................77

6.4.27 product_anomaly.................................................................................................................77

6.4.28 product_anomaly_relationship ............................................................................................77

6.4.29 roll_up_relationship ............................................................................................................78

6.4.30 task_anomaly_assignment...................................................................................................78

6.4.31 xor_consequential_failure_relationship ..............................................................................78

7. Task Descriptions (Task)....................................................................................... 797.1 Overview.....................................................................................................................................79

7.2 Description..................................................................................................................................79

7.2.1 What to do...........................................................................................................................79

7.2.2 What is used to do the job...................................................................................................82

7.3 EXPRESS G Diagrams...............................................................................................................84

7.4 Definitions...................................................................................................................................85

7.4.1 defined_task_type ...............................................................................................................85

7.4.2 encoded_item ......................................................................................................................85

7.4.3 facility_select ......................................................................................................................86

7.4.4 hazard_values......................................................................................................................86

7.4.5 information_realisation_select ............................................................................................86

7.4.6 interval_code.......................................................................................................................867.4.7 maintenance_or_scrap_rate_select......................................................................................86

7.4.8 method_or_task...................................................................................................................86

7.4.9 percentage ...........................................................................................................................86

7.4.10 resource_item......................................................................................................................86

7.4.11 task_target ...........................................................................................................................87

7.4.12 task_type_select ..................................................................................................................87

7.4.13 additional_skill_requirement...............................................................................................87

7.4.14 advisory_task_stage ............................................................................................................87

7.4.15 base_task_method ...............................................................................................................87

7.4.16 concurrent_methods ............................................................................................................87

7.4.17 criticality .............................................................................................................................87

7.4.18 decision_point.....................................................................................................................88

7.4.19 encoding..............................................................................................................................887.4.20 external_task_type...............................................................................................................88

7.4.21 facility_or_infrastructure.....................................................................................................88

7.4.22 facility_type ........................................................................................................................88

7.4.23 information_requirement.....................................................................................................89

7.4.24 logistic_task_method...........................................................................................................89

7.4.25 logistic_task_target_assignment..........................................................................................89

7.4.26 logistics_task.......................................................................................................................90

7.4.27 looping_method ..................................................................................................................90

7.4.28 maintenance_percent...........................................................................................................90

7.4.29 occurence_rate ....................................................................................................................90

7.4.30 operability ...........................................................................................................................91

7.4.31 period_measure...................................................................................................................91

7.4.32 personnel_hazard ................................................................................................................91


6/154


vi

7.4.33 personnel_skill ....................................................................................................................92

7.4.34 quantified_task_resource_requirement................................................................................92

7.4.35 repeat_count........................................................................................................................92

7.4.36 repeat_until .........................................................................................................................92

7.4.37 repeat_while........................................................................................................................92

7.4.38 scrap_on_removal ...............................................................................................................937.4.39 skill_grade...........................................................................................................................93

7.4.40 skill_subject ........................................................................................................................93

7.4.41 specific_facility...................................................................................................................93

7.4.42 stop_task_method................................................................................................................93

7.4.43 structured_task_method ......................................................................................................94

7.4.44 supplementary_task.............................................................................................................94

7.4.45 task......................................................................................................................................94

7.4.46 task_consideration...............................................................................................................94

7.4.47 task_function_class .............................................................................................................94

7.4.48 task_method ........................................................................................................................94

7.4.49 task_method_assignment.....................................................................................................95

7.4.50 task_method_relationship_with_context .............................................................................95

7.4.51 task_method_sequence........................................................................................................957.4.52 task_resource_requirement..................................................................................................95

7.4.53 task_resource_role ..............................................................................................................96

7.4.54 task_target_assignment .......................................................................................................96

7.4.55 task_training........................................................................................................................96

7.4.56 test_condition......................................................................................................................97

7.4.57 training_location .................................................................................................................97

8. Technical Documentation (InfoObj) .................................................................... 988.1 Overview.....................................................................................................................................98

8.2 Description..................................................................................................................................98

8.3 EXPRESS G Diagrams.............................................................................................................102

8.4 Definitions.................................................................................................................................103

8.4.1 dtd_selection .....................................................................................................................1038.4.2 information_link_select.....................................................................................................103

8.4.3 information_object_content_selection ..............................................................................103

8.4.4 language_assignment_select..............................................................................................103

8.4.5 reference_or_object...........................................................................................................104

8.4.6 target_information_select..................................................................................................104

8.4.7 version_logic.....................................................................................................................104

8.4.8 base_information_object...................................................................................................104

8.4.9 base_language_assignment ...............................................................................................104

8.4.10 binary_encoded_information ............................................................................................104

8.4.11 derivation_description.......................................................................................................104

8.4.12 derived_information_object..............................................................................................105

8.4.13 encoded_information_content...........................................................................................105

8.4.14 external_document ............................................................................................................1058.4.15 external_document_element..............................................................................................105

8.4.16 information_definition_relationship..................................................................................105

8.4.17 information_encoding_form..............................................................................................105

8.4.18 information_link................................................................................................................106

8.4.19 information_object ............................................................................................................106

8.4.20 information_object_category ............................................................................................106

8.4.21 information_object_category_relationship........................................................................107

8.4.22 information_object_derivation..........................................................................................107

8.4.23 information_object_relationship .......................................................................................107

8.4.24 information_representation_relationship...........................................................................107

8.4.25 language ............................................................................................................................107

8.4.26 sgml_string........................................................................................................................108

8.4.27 structured_information_object ..........................................................................................108


7/154


vii

8.4.28 text_encoded_information.................................................................................................108

8.4.29 versioned_information_object...........................................................................................108

9. Logistic Support Analysis (Lsa).......................................................................... 1099.1 Overview...................................................................................................................................109

9.2 Description................................................................................................................................109

9.2.1 Scenario and Role .............................................................................................................1099.2.2 Characteristics...................................................................................................................109


9.4 Definitions.................................................................................................................................113

9.4.1 applicability_switch ..........................................................................................................113

9.4.2 characteristic_assignment_type.........................................................................................113

9.4.3 characteristic_target_select ...............................................................................................113

9.4.4 price_type..........................................................................................................................114

9.4.5 product_aspects.................................................................................................................114

9.4.6 qualifier_select..................................................................................................................114

9.4.7 scenario_or_role................................................................................................................114

9.4.8 standard_qualifier..............................................................................................................114

9.4.9 achieved_availability.........................................................................................................114

9.4.10 administrative_and_logistic_delay_time...........................................................................1149.4.11 administrative_lead_time ..................................................................................................115

9.4.12 annual_number_of_missions.............................................................................................115

9.4.13 annual_operation_time......................................................................................................115

9.4.14 annual_usage_characteristic..............................................................................................115

9.4.15 authorized_life ..................................................................................................................115

9.4.16 availability_characteristic..................................................................................................115

9.4.17 built_in_test_cannot_duplicates........................................................................................115

9.4.18 built_in_test_retest_ok ......................................................................................................116

9.4.19 characteristic .....................................................................................................................116

9.4.20 characteristic_assignment..................................................................................................116

9.4.21 currency_unit ....................................................................................................................116

9.4.22 detection_level ..................................................................................................................1179.4.23 distribution_based_period.................................................................................................117

9.4.24 failure_characteristic.........................................................................................................117

9.4.25 failure_mode_ratio ............................................................................................................117

9.4.26 failure_rate ........................................................................................................................117

9.4.27 fault_isolation....................................................................................................................118

9.4.28 inherent_availablity...........................................................................................................118

9.4.29 inherent_maintenance_factor ............................................................................................118

9.4.30 location..............................................................................................................................118

9.4.31 maintainability_characteristic ...........................................................................................118

9.4.32 maintenance_concept ........................................................................................................119

9.4.33 maintenance_concept_assignment.....................................................................................119

9.4.34 maintenance_level.............................................................................................................119

9.4.35 mean_maintenance_downtime ..........................................................................................1199.4.36 monetary_characteristic ....................................................................................................120

9.4.37 money_measure.................................................................................................................120

9.4.38 narrative_characteristic .....................................................................................................120

9.4.39 narrative_characteristic_with_switch ................................................................................120

9.4.40 non_standard_qualifier......................................................................................................120

9.4.41 operating_location.............................................................................................................121

9.4.42 operation_life ....................................................................................................................121

9.4.43 operational_availability.....................................................................................................121

9.4.44 package_quantity...............................................................................................................121

9.4.45 period_characteristic.........................................................................................................121

9.4.46 point_in_time ....................................................................................................................121

9.4.47 price_break........................................................................................................................121

9.4.48 price_characteristic_assignment........................................................................................122


8/154


viii

9.4.49 price_with_minimum_quantity..........................................................................................122

9.4.50 procurement_concept........................................................................................................122

9.4.51 product_life .......................................................................................................................122

9.4.52 product_maintenance_level_association ...........................................................................122

9.4.53 product_price ....................................................................................................................122

9.4.54 property.............................................................................................................................1239.4.55 provisioning_period ..........................................................................................................123

9.4.56 provisioning_quantity........................................................................................................123

9.4.57 qualified_characteristic_assignment..................................................................................124

9.4.58 recovery_method...............................................................................................................124

9.4.59 recovery_method_assignment ...........................................................................................124

9.4.60 reliability_characteristic....................................................................................................124

9.4.61 role ....................................................................................................................................125

9.4.62 scenario .............................................................................................................................125

9.4.63 shelf_life ...........................................................................................................................126

9.4.64 ship_time...........................................................................................................................126

9.4.65 sourcing_method...............................................................................................................126

9.4.66 sourcing_method_assignment ...........................................................................................126

9.4.67 spare_factor.......................................................................................................................1269.4.68 standby_time.....................................................................................................................126

9.4.69 supportability_characteristic .............................................................................................127

9.4.70 testability_characteristic....................................................................................................127

9.4.71 time_between_adaptive_maintenance_tasks.....................................................................127

9.4.72 time_between_corrective_maintenance_tasks...................................................................127

9.4.73 time_between_failure........................................................................................................127

9.4.74 time_between_induced_maintenance_tasks ......................................................................128

9.4.75 time_between_inherent_maintenance_tasks......................................................................128

9.4.76 time_between_maintenance_tasks.....................................................................................128

9.4.77 time_between_no_fault_found_maintenance_tasks ..........................................................128

9.4.78 time_between_overhauls...................................................................................................128

9.4.79 time_between_perfective_maintenance_tasks...................................................................129

9.4.80 time_between_preventive_maintenance_tasks..................................................................129

9.4.81 time_between_scheduled_shop_visit ................................................................................129

9.4.82 time_characteristic ............................................................................................................129

9.4.83 time_to_perform_task.......................................................................................................129

9.4.84 time_to_repair...................................................................................................................130

9.4.85 total_life............................................................................................................................130

9.4.86 unit_of_issue.....................................................................................................................130

9.4.87 wear_out_life ....................................................................................................................130

10. Supporting Schemas ......................................................................................... 13110.1 Approval ...................................................................................................................................131

10.2 Person and Organization ...........................................................................................................131

10.3 Date and Time...........................................................................................................................131

10.4 Support Resources ....................................................................................................................13110.5 Referenced STEP Integrated Resources (IR)............................................................................131


10.7 npdm_approval .........................................................................................................................133

10.7.1 approval_assigned_item....................................................................................................133

10.7.2 applied_approval_assignment ...........................................................................................134

10.7.3 approval ............................................................................................................................134

10.7.4 approval_person_organization..........................................................................................134

10.7.5 approval_relationship........................................................................................................134

10.7.6 approval_role ....................................................................................................................135

10.7.7 approval_status .................................................................................................................135

10.7.8 product_baseline_approval_assignement..........................................................................135

10.7.9 product_design_baseline_approval ...................................................................................135

10.7.10 product_instance_baseline_approval ............................................................................135


9/154


ix

10.7.11 product_requirement_baseline_approval ......................................................................136

10.8 npdm_person_organization.......................................................................................................136

10.8.1 person_oganization_select ................................................................................................136

10.8.2 person_organization_assigned_items................................................................................136

10.8.3 person_organization_select_with_role..............................................................................137

10.8.4 address ..............................................................................................................................13710.8.5 organization.......................................................................................................................137

10.8.6 organization_relationship..................................................................................................138

10.8.7 organization_role ..............................................................................................................138

10.8.8 organization_with_role .....................................................................................................138

10.8.9 organizational_address......................................................................................................138

10.8.10 person............................................................................................................................139

10.8.11 person_and_or_organization_assignment .....................................................................139

10.8.12 person_in_organization.................................................................................................139

10.8.13 person_in_organization_role.........................................................................................139

10.8.14 person_in_organization_with_role................................................................................140

10.8.15 person_role....................................................................................................................140

10.8.16 person_with_role...........................................................................................................140

10.8.17 personal_address...........................................................................................................14010.9 npdm_date_time........................................................................................................................140

10.9.1 date_time_assigned_items.................................................................................................141

10.9.2 date_time_select................................................................................................................141

10.9.3 date_time_select_with_role...............................................................................................142

10.9.4 date_and_or_time_assignment ..........................................................................................142

10.9.5 date_and_time...................................................................................................................142

10.9.6 date_and_time_assignment ...............................................................................................142

10.9.7 date_assignment ................................................................................................................142

10.9.8 date_role............................................................................................................................143

10.9.9 date_time_role...................................................................................................................143

10.9.10 time_assignment............................................................................................................143

10.9.11 time_role .......................................................................................................................143

10.10 npdm_support_resources ......................................................................................................143


10/154

Page 0 of 154


11/154

Page 1 of 154

1. INTRODUCTION

1.1 General

The NATO Product Data Model (NPDM) is a formal description of the data

required to support the logistics process for the acquisition and support of major systems.

Such systems include aircraft, tanks and ships, and other complex products. The objective

is to support the information required, used or provided by:

the owner of a complex product;

the people responsible for maintaining and repairing the product;

the organization(s) who design and manufacture the product.

These three groups have had equal priority. This is necessary as the contractual

boundaries between them are becoming increasingly variable.

This information has been covered by several existing standards, such as MIL-STD

1388, AECMA Spec 1000D and AECMA Spec 2000M. The NPDM takes an integrated

approach to the data covered by these specifications but also recognizes the possibilities

for other kinds of data such as design information and multi-media. It does so in a way thatshould enable current approaches to be followed while enabling richer and more effective

new methods to be applied.

1.2 Technical view

The NPDM is meant to be used as the basic component of an Information

Technology System Architecture that supports the concept of data accessible from

multiple applications and business perspectives and that may be stored in and moved

between multiple Information Systems.

The NPDM may be seen as the basic element of the three-layer architecture defined

by the ANSI/X3/SPARC Study Group on Database Management Systems. In particular

such architecture may be described as follows:

The conceptual layer contains a single model, within a given context, acting as

the basis for integration of data used by different applications or stored in

different formats. Models in this layer must not include details that are specific

to a particular application or business perspective and they must not include

physical (e.g. storage) format.


12/154

Page 2 of 154

The internal layer contains the physical model. It represents the way in which

data is physically stored. There may be many valid physical models for the same

conceptual model. Any physical model must be able to import data that

conforms to the associated conceptual model.

The external layer is a view of the conceptual model from a particular

perspective and for a particular application. There may be many valid external

models for the same conceptual model. An external model maps to a subset of

the conceptual model in such a way that the data described in the external model

can be exported in the format of the conceptual model.

As part of this architecture, the NPDM has the role ofconceptual layer. It defines

a common set of data definitions and data structures to support Defense System technical

information management, throughout the life cycle, in the context of NATO nations and

NATO industries.

It is meant to be used as the platform for the development ofphysical and external

models which are able to support data sharing and data exchange.

The NPDM addresses the NATO requirement for data interoperability between

different Information Systems by delivering a common data semantic and thus enabling

consistency of interfaces at the information level without requiring standardization of

hardware or software.

1.3 A Brief History

The NATO Acquisition Logistic Workshop (ALW) final report, in 1993,

established the requirement for the development of the NPDM. From the ALW

conclusions and recommendations:

" It is recommended that NATO assumes responsibility for the development of a

consistent and stable set of data definitions ( a single data dictionary) which is applicable

to land, sea and air services and manufacturing industry"

The first effort concentrated on the harmonization of the data elements contained in

three input Standards (MIL-STD-1388-2B, AECMA S2000M, and AECMA S1000D).

This task was completed in 1996 and the NATO CALS Data Dictionary Version 1 was

consequently published. The NATO CALS Pilot Project #1 Management Group decided at

that point in time to proceed with the development of a database design model (e.g. IDEF

1X or similar model).


13/154

Page 3 of 154

The modeling working group used EXPRESS as the modeling language. In doing

this they had the opportunity to use the state of the art in Information Technology and

Data Modeling (object-oriented languages and databases, multimedia, SGML).

An important element of the approach was that some basic Integrated Resources(IR) specified within STEP were incorporated directly in the NPDM, when appropriate.

This is a very important feature of the NPDM which means that data created in accordance

with STEP can easily be integrated in the NPDM data set. In addition, adoption of STEP

IRs will facilitate later migration to an ISO standard as recommended by the ALW.

The initial NATO Product Data Model was created over a relatively short period of

time and resulted in the publication of NCDM Version 2.02 in November 1997. This

version was the base for the Industrial Rig Test which performed a cross check of the

model by implementing it in relational tables in a Database Application. The result of the

Rig Test was a list of issues and proposals for improvement.

The NCDM Version 3.00, published in May 1998, was the result of the revision of

the model on the basis of the Rig Test Report.

The NCDM Version 3.00 has proved to be an outstanding NATO CALS product. It

has been world wide appreciated for its innovative concepts of integration of design data,

derived from the engineering design process, and the support data produced by the

Logistic Support Analysis and Failure Mode Analysis. It has influenced the work done in

the product data area around the world. In particular:

It has provided the initial vision for the launch of the Product Life Cycle

Support (PLCS) initiative.

It has been translated and published in Japanese by JCALS.

It has been the basis for the Finish Defense Information Architecture

implementation.

It has been used as a 'reference' by the Turkish Aerospace Industries (TAI) when

they developed the Turkish General Staff (TGS) Logistics System Data Model.

It has provided the basic concepts for the launch of the Italian MoD project

(CALS Italia) which will develop a new Logistics Information System using the

NPDM as its conceptual model.

And, finally, it has been implemented in a software prototype, founded by the

French DGA, to test the model constructs and to prove that an Information

System, based on a relational database, could be developed from the conceptual

model.


14/154

Page 4 of 154

The NATO CALS Office has been collecting comments, issues and change

proposals for the last year. Consequently, an initiative was started in September 1999 to

analyze all requirements for changes and to produce an update version of the Model. The

result is the NPDM Version 4.00, which is presented in this publication.

1.4 What is new in Version 4.00

The NPDM Version 4.00 takes a wider life cycle perspective and provides a better

support for the Configuration Management process. While Version 3.00 was focused on

the acquisition logistics data, Version 4.00 expands the scope of the NPDM to also include

the management of Defense System Data during the operational life. Also important is that

Version 4.00 is now able to capture and manage the user requirements defined in the very

early stages of a program.

The following are the main new features of NPDM:

Product instance and product instance management. The product instance,

in the NPDM terminology, is the actual physical system, normally identified by

a serial number, a tail number or a lot number. A product instance is the result

of the manufacturing process where one single product design is realized in

one or many product instances.

In order to support the product instance during its operational life, some new

data structures have been defined. The NPDM Version 4.00 gives the possibility

to maintain a record of the product instance current configuration with the

history of component replacements. Maintenance history and operational usage

history may be captured in order to optimize the support activities and to plan

operational deployment. Logistic activities have been defined as a subtype of the

Entity activity which in turn is closely linked to work_request and work_order.

In this way, the maintenance activity itself can be captured by the NPDM.

Associations of the product instance with different person and/or organizations

in different roles (e.g. owner, user, driver, etc) may be defined. To define wherethe product instance is located at a certain point in time, an associations with

location can be established.

Product concept and product concept specification. The user requirements

are defined in the very early phase of a program before the design activity starts.

At that point in time, the idea or concept of the system is formalized by

describing the expected features and functionality. For this process, the NPDM,

has defined a dedicated set of data structures based on the Entities

product_conceptand specification.


15/154

Page 5 of 154

The NPDM Version 4.00 exploits these entities for the identification of the

requirement baseline, which is an important element of Configuration

Management. The NPDM defines the requirement baseline as identified by the

set of specifications which are linked to configuration_item through the Entity

configuration_item_characterization and that are associated with the Entity

requirement_baseline_approval.

Configuration Management. Most of the feedback on Version 3.00 was

related to CM. A consolidation of proposals and feedback and an analysis of the

NATO STANAG 4159 and CM best practices was conducted for the extension

of the NPDM. The result was the requirement paper NCMB(NCO)-(99)A-54

published in August 99. Based on these requirements, the model was revisited

to identify the data structures needed to support CM. The features of Version

4.00 in the area of CM are the followings:

Configuration Status Accounting is a CM major function that is directly

supported by the NPDM. From a database implementation of the NPDM it is

possible to derive, at any time, the current configuration status of: (1) the

user requirements, (2) the physical and functional design, and of (3) each

individual product instance.

Configuration Identification is based on the Entity configuration_item,

which collects the unambiguous identification of user specifications (as-

required), of physical designs (as-designed) and of each product instance

(as-built and as-used).

Configuration Change is managed through the Entities work_request,

work_orderand activity.

Configuration Baselines are identified by those configuration_items(s) that

are associated with a baseline_approval. According to the NATO STANAG

three different types of baselines are identified: (1) requirement baseline, (2)

physical design baseline, and (3) product instance baseline.

1.5 Motivation

Modern defense systems cannot operate without access to large quantities of

technical information. This information is an asset as valuable and necessary as the

defense system itself.

Today, technical information is created in digital form. This behaves differently

compared to information on paper. The opportunities are enormous, but new problems

and risks are at the same time introduced. A major problem arises when multiple


16/154

Page 6 of 154

organizations need to use the same information. Differences in data definition and data

format block communications between partners and require development of expensive

interfaces. Too often, data is locked into the application in which it is created forcing the

use of proprietary solutions. As a result, many IT systems which ought to be offering

business improvement act, in practice, as barriers.

To address the above issues, the NATO Product Data Model (NPDM) defines a

common set of data definitions that can be used to achieve consistency of interfaces at the

information level without requiring standardization of hardware or software. The role of

the NPDM is to standardize content of a life-cycle repository for defense system technical

information with the objective that Armed Forces with different Information Technology

infrastructure, e.g. different hardware and software platforms, can make use of the same

technical information.

1.6 Information Modeling

Raw data is not information. Two parties can only exchange data in conjunction

with an agreement on the meaning of the data. Consider the number 1964. This number

is data without information. The data becomes useful if we add the information that it is a

year (1964), or the number of people attending the 98 CALS Europe Conference.

Although the data is the same in both cases, the information is different.

An information model addresses the underlying meaning of data regardless oftechnology. A model describes meaning through structure and correctness constraints. It

does not specify encoding techniques for data values.

The NATO Product Data Model uses EXPRESS as a formal language for

specifying information requirements. EXPRESS is an ISO standard (ISO 10303-11) and

has been used by STEP, POSC and other projects to describe the information requirements

of many engineering activities.

The function of EXPRESS is to describe information requirements and correctness

conditions necessary for meaningful data exchange. An EXPRESS information model isorganized into schemas. The NPDM, for instance, is organized in ten schemas. These

schemas contain the model definitions and serve as a mechanism for subdividing large

information models. Within each schema there are three categories of definitions:

Entity Definitions: describe classes of real-world objects with associated

properties. product, for instance, is an entity of the NPDM. The properties are

called attributes and can be simple values, such as name or id or

relationships between occurrences of entities, such as owner or part of.

Entities can also be organized into classification hierarchies, and inherit


17/154

Page 7 of 154

attributes from super-types. The inheritance model supports single and multiple

inheritance, as well as a new type, called AND/OR inheritance.

Type Definitions: describe ranges of possible values. The language provides

several built-in types. A modeler can construct new types using the built-intypes, generalizations of several types, and aggregates of values.

Correctness Rules: are crucial components of entity and type definitions. These

local rules constrain relationships between entity instances or define the range of

values allowed for a defined type. Global rules can also make statements about

an entire information base.


18/154

Page 8 of 154

2. HOW TO USE THE NPDM

2.1 Specifying Information Requirements.

An information model is an agreement on the meaning of data. This agreement is

represented in a formal manner using an appropriate descriptive language (e.g.

EXPRESS). An agreement is a mutual understanding or arrangement between parties.

The parties, in our case, are the Defense Industry and the NATO Armed Forces. The

agreement defines WHAT data will be exchanged and what is the MEANING. In a data

model the meaning of data is conveyed by the data structure and relationship. How data is

created by the industry and how it is used by the single Armed Force is not part of the

agreement. The processes and software applications that make use of the data are not part

of the agreement either.

The NPDM can be used to specify the technical information needed by the NATO

Armed Forces to support a defense system in service, through-life. From the project

manager perspective, the NPDM can be used to identify data requirements for a specific

project. The utilization of the NPDM in this sense is very similar to what is done today

when data elements are contracted according to legacy standards (e.g. MIL STD 1388).

The advantage of using the NPDM resides in the quality of the contracted data. The model

gives an integrated view of data where design data like system physical and functionalbreakdowns are integrated with support data and with the data needed to make technical

documentation available.

Text appearing as [times roman italics] in the following paragraph is provided as a

sample language that can be used in developing the data requirements for a Request For Proposal

(RFP) or Request for Quotation (RFQ) SOW.

! The contractor shall provide configuration and design data that could support the production of Bill of Material (BOM) Reports and of Labelled Occurrence,

Multilevel, Indented Product Structure Reports. This data shall be in the form of

instances of the following NPDM entities:

- product

- product_version

- product_design_definition and its subtypes as needed


19/154

Page 9 of 154

2.2 Defining a Common Vocabulary

There is a flow of information (e.g. Defense System Technical Information)

between the industry, originator of the data, and the Armed Forces, users of the same data.

There could also be a need for data exchanged between Armed Forces of different NATO

nations. When parties with different software and hardware platforms need to share the

same information, the need for interfaces arises. These are sophisticated and expensive

software that acts as translators between different systems.

Figure 1. Number of interfaces without a common vocabulary

As illustrated in figure 1, the number of director translators between systems growsas N(N-1) where N is the number of systems. The NPDM can be used as a common

vocabulary, agreed by the Defense Industry and by the NATO Armed Forces, to

dramatically decrease the number of interfaces. In this case the number of interfaces only

grows as 2N.

Figure 2. Number of interfaces using the NPDM as a common vocabulary

A

B

C

F

E

D

A

B

C

F

E

D

NATO Product

Data Model


20/154

Page 10 of 154

2.3 Implementing an Integrated Product Database

A Data Model can be implemented in a database. An EXPRESS data model is

technology independent and can be implemented in a variety of databases (e.g. Relational,

Object Oriented, and hybrid). For this discussion we assume that the model is

implemented in a relational database (e.g. SQL SERVER, ORACLE, INFORMIX etc ).

The strength of relational systems is in their ability to store large amounts of data

in a highly normalized, tabular form, and to perform efficient queries across large data

sets. Relational systems use SQL for both data definition and data manipulation.

Unfortunately, EXPRESS does not include a construct to create relational tables

automatically. A method of mapping the NPDM to a relational database was experimented

during the Rig Test.

In this method, each entity is mapped to a table with columns for attributes. Each

table has a column with a unique identifier for each instance. Attributes with primitive

value are stored in place and composite values like selects, and aggregates are stored as

foreign keys containing the corresponding unique instance identifier. Inheritance is

normalized out of the tables. The table for each entity type contains the local attributes

defined by the entity and uses the instance identifier as the primary key. A complete entity

instance, with all inherited attributes, can be reconstructed by a join on the identifier across

all tables in the type hierarchy.

Other conflicts that ought to be addressed to implement the NPDM in a relational

database are the following:

The relational model does not directly support the union construct. EXPRESS

Selects are simulated by a table with a column for each possible member type.

Only one column in each row contains a value. The remaining columns are

empty;

Relational systems primitive data types are not as extensive as those of

EXPRESS. A mapping is therefore needed to link the NPDM data types withthose supported by the selected relational system;

Relational systems need to know the length of the each field in the database.

This requires further data analysis since no attribute length is defined in the

NPDM;

Finally, EXPRESS imposes no limit on the length of type or attribute names,

while the NPDM define entities and attributes with long names. Some relational

systems restrict the length of table and column names to 30 characters. Name

length conflicts in this case need to be resolved.


21/154

Page 11 of 154

Potential users of an Integrated Product Database build around the NPDM are the

Industry, Defense System project teams and the NATO Armed Forces.

2.3.1 In the Industry

The need for the industry to integrate their engineering processes around

integrated product database is becoming more and more evident.

Engineering applications have unusually complex information models. These

information models are complex because engineering applications manipulate simulations

of the real world. Models for areas such as CAD geometry, tolerances, materials, and

manufacturing plans are structurally and semantically rich. Applications are similarly

complex, and are tightly bound to the models. Often, the information exists only as

program language structures taken from a primary application, usually a PDM or CAD

system. Subsequent applications must be modified whenever the primary applicationchanges. The resulting situation is that only special-purpose databases, controlled by PDM

and CAD vendors, are used to describe complex products. Designers and Manufacturers

do not have any control over their product databases, which is clearly undesirable for

strategic reasons. Also, the customers request for complex design data together with the

logistic support information in an open format accessible by off-the-shelf DBMS, is not

easily addressed.

To overcome the above problems, design and manufacturing companies need to

integrate their engineering processes around product databases.

Figure 3. Integrated Product Database data sources.

The term integrated refers here to the process of reconciling data from many

different sources so that the resulting collection can be managed consistently with

minimum redundancy.

CAD/CAM PDM LSA tools

Integrated Product

Data Base

users


22/154

Page 12 of 154

Some of the technical opportunities are:

Integration around product databases enables concurrent engineering - a process

where multiple engineers work on different facets of a product concurrently;

An Integrated Product Database gives the opportunity to store, in a single

source, information needed to deliver Technical Documentation (e.g. Technical

Manuals) together with Defense System Configuration data;

An Integrated Product Database enables a more efficient and flexible way of

delivering data to NATO Armed Forces:

The NATO Armed Forces can be allowed to access the contractor

maintained database through extensive use of web technologies;

The database itself or part of it can be delivered to the Armed Forces as part

of an Information System;

Data can be delivered to the Armed Forces using exchange files (STEP Part

21, XML, ASCII files)

2.3.2 In a Project

A major value of an Integrated Product Database is that it can support remote

access by any authorized user. The project team can make use of this feature to obtain

ready access to the data while it is created. The advantages of this are obvious, for

instance:

verification that system requirements are met can be assessed in real time;

a continuous and concurrent decision schema is enabled, thus avoiding the

long delays in traditional milestone management;

use of cross boundary integrated teams is facilitate;

verification of database accuracy and completeness can be more easily and

accurately assessed.

Text appearing as [times roman italics] in the following paragraph is provided as a

sample language that can be used in developing the data requirements for a Request For

Proposal (RFP) or Request for Quotation (RFQ) SOW:

! The contractor shall provide a cost effective method of implementing anintegrated product technical database based on the NATO Product Data Model

such that it can be accessed by any authorised person or organisation.


23/154

Page 13 of 154

2.3.3 In the NATO Armed Forces

Several NATO nations are investing heavily in major IT infrastructure programs to

improve logistic support for their armed forces. The NATO CALS Organization does not

intend to recommend a specific hardware or software solution that all the various parties

would be required to adopt and integrate with their existing infrastructure systems. Clearly,

the definition and development of Information Systems is a national responsibility.

However, the NATO CALS Organization does recommend the use of the NPDM

as the conceptual model for individual nation Information Systems.. The benefit of such an

approach is that, through the use of the common conceptual model, data can be accessed

and moved between different information systems (see paragraph 1.2), hence between

different NATO nations and NATO industries. The definition of common data semantics

is the NATO CALS Organization addresses the requirement of NATO information

interoperability in the area of defense system technical information.

Furthermore, the NPDM, by standardizing at the information level, offers the

opportunity to define an Information Infrastructure built around a Defense System

Technical Information Database. The benefits of such repository of technical information

for all the available weapon systems are self evident. Even more dramatic benefits could

be achieved if the Defense System Technical Information Database is implemented in a

consistent way across NATO by all Nations. In this case the realization of a NATO

Distributed Database for Defense System Technical Information will be achieved.

NATO Nations working together (e.g. Combined Joint Task Force) could then be allowed

to access each-other weapon system technical database on a need to know basis.

2.4 How to Implement the NPDM

As said in paragraph 1.2, the NPDM could be used as an interoperability platform

to develop physical models, external models, databases and Information Systems. The

following diagram loosely follows IDEF0 notation and illustrates the activities required to

build an IT system on top of the NPDM.


24/154

Page 14 of 154

Figure 4. Building an IT System on Top of the NPDM

The boxes in the diagram represent activities to be performed; the arrows are

components of the system that should be available to perform the activities.

By delivering the NPDM, the basic component of the system, the first activity is

completed. A common 'vocabulary' is in place. All the other components are grounded on

the NPDM but are equally essential and need to be developed by the organizations willing

to implement the Information System. It should be stressed that, to achieve interoperability

between programs and between NATO Armed Forces, it is mandatory that the NPDM is

used as the conceptual model in the development of national IT solutions.

2.5 To Create a Physical Model

In order to implement the NPDM, a set of implementation guidelines must be

developed. The NATO CALS Office is developing this for NATO programs and NATO

nations based on the following approach, which could be followed by any organization

trying to implement the NPDM:

2.5.1 The Requirement

The first step in building interoperable IT systems is to agree the extent, structure andmeaning of the data to be shared or exchanged within a particular context. This is

achieved by defining a conceptual data model.

The NPDM is the NATO conceptual data model for product data and support data.It provides semantic coherence for all partners in the NATO context.

Being a conceptual model, the NPDM addresses semantic definitions but does notdefine physical data format, functional viewpoints, business rules and conventions

applicable to the NATO context.

Create

Conceptual

Model

Business Model

Data RequirementsNPDM

Entities/Subtypes

Attributes

Relationships

Integrity Rules

Create

Physical

Model

Technical Environment

Performance Consideration

Business Rules

Attribute Formats

Tables

Columns

Keys/Indicies

Triggers

Create &

Update Data

Empty Database

Populated DatabaseInput Data

Software Applications

Import/Export Interfaces ( STEP/PDM)

Business Processes & Funct.


25/154

Page 15 of 154

Without the definition of the above elements, a single conceptual data model couldgive rise to many different real world solutions. The level of interoperability between

these systems depends on the degree of divergence in format, business rules and

conventions that are used by different implementers.

The development of Implementation Guidelines with the definition of physical format,functional viewpoints, business rules and conventions is in the interest of NATO

information interoperability.

2.5.2 The Method

The NATO approach for the NPDM Implementation Guidelines is based on theintegration with the Product Life Cycle Support initiative (PLCS) and on a progressive

and iterative approach as illustrated in the figure below.

The first step is to identify NPDM modules that are likely to be stable over time andthat are expected not to be changed by PLCS.

For each module, task 1 will analyse data definitions of the selected module with the

objective of defining entity unique keys and to resolve the few existing many to

many relationships between entities. Task 1 will deliver the logical model.

Figure 5. Developing Implemetation Guidelines

Task 2 will define the physical model and will map it to the logical model. A physicalmodel is used as reference for database implementation.

Task 3 will start with the identification of functional viewpoints. A primary sourcewill be the functional analysis performed under Pilot Project #1 task 2.4. Additional

functionality, capable of exploiting the benefits of a shared data environment, should

also be identified.

Each functional viewpoint will be mapped to the supporting metadata in the physicalmodel. NATO business rules, conventions, coding and possible derivation algorithms

will be identified and documented for each functional viewpoint.

PHYSICAL MODEL

Functional

Viewpoints

NATO Product

Data ModelMODULE 1 MODULE 2 MODULE 3

LOGICAL MODELTASK 1

TASK 2

TASK 3


26/154

Page 16 of 154

A more detailed description of this method, including examples of results is

available. The Implementation Guidelines for the entire NPDM are currently under

development and will be completed by autumn 2001.


27/154

Page 17 of 154

3. MODEL OVERVIEW

3.1 The High Level Model

A very basic simplified view of the NATO Product Data Model is shown below:

Figure 6. Abstract View of the NPDM

This can be interpreted as follows:

The product concept is, normally, the first object to be created. It is identified in

the very early stage of the life cycle of the system and is described

Documents

Nato Product Data Model (Npdm)