7. USAGE SCENARIO
7.1 Overview
In the NPDM allowance is made for the likelihood that a system may be supplied to different customers who may not only use it in different ways and environments but may also have different resources (such as personnel skills) and different policies on maintenance. However it is inevitable that the same failures will probably occur and that many tasks will be common. (e.g. the NH90 helicopter is intended for 11 different services across 4 nations).
7.2 Description
7.2.1 Scenario and Role
Rather than force a separate copy of the database to be developed for each customer, the NPDM provides for these differences through the scenario entity. This is then used in many places as the context for assignments (such as a task to a product) to indicate that the assignment is applicable in the scenario.
As a further refinement to this, the system may have multiple roles (for the NH90 these could be submarine warfare, search and rescue, etc.) which lead to different maintenance requirements. A scenario may include several roles.
7.2.2 Maintenance Concept
This part of the NPDM provides a narrative description of the levels and depths to which a product will be maintained in order to achieve the required availability in a given product_usage, operating_location, role and scenario. The maintenance_concept provides the basis for the maintenance plan and will normally evolve throughout the product's life cycle e.g. an interim maintenance-concept may be developed for a product's introduction to service, and a long term maintenance concept be adopted once all the necessary long term logistic support is in place. It provides, moreover, indication of the maintenance level(s) authorized to perform the required maintenance task/function.
7.2.3 Procurement Concept
A narrative description of the likely procurement activity and methodology to be employed during the product's in-service phase is of outmost importance. This description should take account of the type of equipment and services to be procured to meet the achieved_availability assigned as required. Account should be taken of the limitations that will be imposed dependent on maintenance_level, product_usage, operating_location, role and scenario.
The procurement_concept provides the basis for the manner of procuring items for maintenance, repair or overhaul of products (sourcing_method) and the disposition action to be taken on unserviceable items (recovery_method).
7.3 EXPRESS G Diagrams
|
|
|
|
|
|
4,4 |
|
|
4,3 |
|
4,2 |
|
|
|||
|
|
|
|
|
|
organization |
identifier |
text_select |
|
|
||||||
|
|
4,5 |
|
|
|
|
|
|
id |
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
time_measure_with_unit |
|
|
|
|
|
|
|
|
|
|||||
|
|
|
user S[1:?] |
|
description |
|
|
|
||||||||
|
|
|
|
duration |
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
name |
|
|
|
|
applies_to |
|
|
|
|
operating_location_count |
|
|
|||
4,1 |
|
provisioning_ |
|
|
|
|
|
|
|
|||||||
|
|
|
scenario |
INTEGER |
|
|||||||||||
|
|
|
number_of_systems |
|
||||||||||||
label |
|
|
period |
|
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for_period
repair_count
INTEGER
*provisioning_
maintenance_count quantity
INTEGER
recommended_by applies_to
4,4 |
4,6 |
organization |
unit_of_issue |
usage S[0:?]
1,1(2)
|
where_used S[0:?] |
operating_ |
|
|
|
role |
location |
|
|
|
|
|
|
|
name |
description |
|
|
|
4,1 |
4,2 |
location |
name |
4,1 |
|
label |
|||
label |
text_select |
|
|
|
|
|
|
description
4,2 text_select
SCENARIO_AND_MAINTENANCE_SCHEMA EXPRESS-G diagram 1 of 4
4,3 identifier
4,2 text_select
1,1 scenario
1,1 scenario
2,1 maintenance_level
4,3 identifier
4,2 text_select
id
description 
assigned_for
for_scenario
level
|
|
4,4 |
|
|
|
4,3 |
|
|
|
4,2 |
|
|
|
||||||||||||
|
|
|
|
organization |
|
|
identifier |
|
|
|
|
|
|
text_select |
|||||||||||
|
|
|
|
|
defined_by |
|
|
|
id |
|
description |
|
|
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||
|
|
|
levels L[1:?] |
|
|
|
|
|
|
|
|
|
4,9 |
||||||||||||
maintenance_ |
|
maintenance_ |
|
||||||||||||||||||||||
concept |
|
|
|
|
|
|
|
|
|
level |
|
|
|
|
|
|
|
|
|
|
|
product_definition_element_relationship |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4,11 |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||
|
|
2,1(2) |
|
|
|
|
|
|
|
level |
|
|
|
|
|
|
|
|
|
|
|
product_definition_relationship |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
concept |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4,13 |
||
|
|
|
|
|
|
|
|
|
|
product_ |
|
|
|
|
|
|
|||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
product_instance_definition |
||||
maintenance_ |
|
|
|
|
|
|
maintenance_ |
|
|
|
|
|
|
|
|
|
|
||||||||
|
target |
|
|
|
level_ |
|
|
|
|
|
|
|
|
|
|
4,10 |
|||||||||
concept_ |
|
|
|
|
|
|
|
|
|
|
|||||||||||||||
|
|
|
|
|
|
|
association |
|
|
|
|
|
|
|
|
|
|
|
product_design_definition |
||||||
assignment |
|
|
|
|
|
|
|
|
|
|
product |
|
|
|
|
2,2(3) |
|
4,8 |
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
product_ |
|
|
|
|
|
|
|
|
|
|
|
element_relationship |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
aspects |
|
|
|
|
|
|
|
|
|
|
4,7 |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
element |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
sourcing_ |
|
assigned_to |
|
|
|
|
|
|
|
|
|
assigned_to |
|||||||||||||
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
method_ |
|
|
|
|
|
|
|
|
|
|
level |
|
|
|
|
|
|
|
|
|
|
|
|
||
|
2,1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
assignment |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
maintenance_level |
|
|
|
|
|
|
recovery_ |
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
method_ |
|
|
|
||
|
|
1,1 |
|
|
for_scenario |
|
|
|
|
|
|
assignment |
|
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||
|
|
|
|
|
scenario |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
assigned_method |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
assigned_method |
|||
id |
|
description |
4,2 |
sourcing_ |
sourcing S[1:?] procurement_ recovery S[1:?] |
recovery_ |
text_select |
|
|||
method |
concept |
method |
4,3 |
description |
|
id |
|
|
|
identifier |
|
|
|
|
SCENARIO_AND_MAINTENANCE_SCHEMA EXPRESS-G diagram 2 of 4
|
|
|
|
|
|
4,3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
identifier |
|
|
|
|
|
||
|
|
|
|
|
|
|
id |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4,4 |
responsible_organization |
procurement_ |
project |
procurement_ |
|
name |
procurement |
|
|
||||
|
|
|
|||||||||||
project_ |
|
_project_ |
|
|
|||||||||
organization |
|
|
|
project |
|
|
|
|
|
||||
|
assignment |
|
|
|
|
|
name |
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
assigned_to |
|
description |
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2,2 |
|
|
4,2 |
|
|
|
|
|
|
||
|
|
product_aspects |
|
|
text_select |
|
|
|
|
|
|||
4,1 label
4,12 element_definition
SCENARIO_AND_MAINTENANCE_SCHEMA EXPRESS-G diagram 3 of 4
PERSON_AND_ORGANIZATION_SCHEMA.organization |
4,4(1,2,3) |
4,7(2) |
CORE_MODEL_SCHEMA.element |
4,8(2) |
CORE_MODEL_SCHEMA.element_relationship |
CHARACTERISTICS_SCHEMA.unit_of_issue |
4,6(1) |
4,9(2) |
CORE_MODEL_SCHEMA.product_definition_element_relationship |
SUPPORT_RESOURCES_SCHEMA.label |
4,1(1,3) |
4,10(2) |
CORE_MODEL_SCHEMA.product_design_definition |
MEASURE_SCHEMA.time_measure_with_unit |
4,5(1) |
4,11(2) |
CORE_MODEL_SCHEMA.product_definition_relationship |
SUPPORT_RESOURCES_SCHEMA.identifier |
4,3(1,2,3) |
4,13(2) |
PRODUCT_INSTANCE_SCHEMA.product_instance_definition |
SUPPORT_RESOURCES_SCHEMA.text_select |
4,2(1,2,3) |
4,12(3) |
CORE_MODEL_SCHEMA.element_definition |
SCENARIO_AND_MAINTENANCE_SCHEMA EXPRESS-G diagram 4 of 4
7.4 EXPRESS Syntax
SCHEMA SCENARIO_AND_MAINTENANCE_SCHEMA;
REFERENCE FROM CHARACTERISTICS_SCHEMA (unit_of_issue);
REFERENCE FROM CORE_MODEL_SCHEMA (element,
element_relationship, product_definition_element_relationship, product_design_definition, product_definition_relationship, element_definition);
REFERENCE FROM MEASURE_SCHEMA (time_measure_with_unit);
REFERENCE FROM PERSON_AND_ORGANIZATION_SCHEMA (organization);
REFERENCE FROM PRODUCT_INSTANCE_SCHEMA (product_instance_definition);
REFERENCE FROM SUPPORT_RESOURCES_SCHEMA (label,
text_select, identifier);
7.4.1 procurement_project_name
TYPE procurement_project_name = SELECT (element_definition,
label); END_TYPE;
7.4.2 product_aspects
TYPE product_aspects = SELECT (element,
element_relationship, product_definition_element_relationship, product_design_definition, product_definition_relationship product_instance_definition);
END_TYPE;
7.4.3 location
The geographical location or area in which the product will be operated.
ENTITY location
SUPERTYPE OF (operating_location);
name |
: label; |
description : text_select; END_ENTITY;
name: |
The identification of the geographical location or area in which |
|
the product will be operated. |
description: |
A narrative description of the operating location. |
7.4.4 maintenance_concept
A narrative description of the levels and depths to which a product will be maintained in order to achieve the required availability in a given product_usage, operating_location, role and scenario. The maintenance_concept provides the basis for the maintenance plan and will normally evolve throughout the product's life cycle e.g. an interim maintenance-concept may be developed for a product's introduction to service, and a long term maintenance concept be adopted once all the necessary long term logistic support is in place.
ENTITY maintenance_concept;
id |
: identifier; |
description |
: text_select; |
levels |
: LIST [1:?] OF maintenance_level; |
END_ENTITY; |
|
id: |
The identification of the type of maintenance concept. |
description: |
The narrative description of the maintenance concept. |
levels: |
Identification of the maintenance level(s) authorized to perform |
|
the required maintenance task/function. |
7.4.5 maintenance_concept_assignment
The assignment of a maintenance concept to an element or product_design_definition or product_definition_relationship.
ENTITY maintenance_concept_assignment;
concept |
: maintenance_concept; |
assigned_for |
: scenario; |
target |
: product_aspects; |
END_ENTITY; |
|
concept: |
The association of a maintenance concept with a specific |
|
product. |
assigned_for: |
The identification of the scenario in which the assignment of a |
|
maintenance_concept to a product applies. |
target: |
The product to which a maintenance_concept is assigned. |
7.4.6 maintenance_level
Indication of the maintenance level(s) authorized to perform the required maintenance task/function.
ENTITY maintenance_level;
id |
: identifier; |
defined_by |
: organization; |
description : text_select; |
|
END_ENTITY; |
|
id: |
Identification of the maintenance level(s) authorized to perform |
|
the required maintenance task/function. |
defined_by: |
The organization responsible for defining the maintenance level. |
description: |
The narrative description of the maintenance level. |
7.4.7 operating_location
The name of the geographical location or area in which the product will be operated.
ENTITY operating_location
SUBTYPE OF (location);
END_ENTITY;
7.4.8 procurement_concept
A narrative description of the likely procurement activity and methodology to be employed during the product's in-service phase. This description should take account of the type of equipment and services to be procured to meet the achieved_availability assigned as required. Account should be taken of the limitations that will be imposed dependent on maintenance_level, product_usage, operating_location, role and scenario. The procurement_concept provides the basis for sourcing_method and recovery_method.
ENTITY procurement_concept;
sourcing : SET [1:?] OF sourcing_method; recovery : SET [1:?] OF recovery_method;
END_ENTITY; |
|
sourcing: |
Indicates the manner of procuring items for maintenance, repair |
|
or overhaul of products. |
recovery: |
Indicates the disposition action to be taken on the unserviceable |
|
product. |
7.4.9 procurement_project
A grouping that is applied to products (and/or their uses in other products) for the purpose of managing procurement of those products.
ENTITY procurement_project;
id |
: identifier; |
name |
: procurement_project_name; |
description : text_select; |
|
END_ENTITY; |
|
id: |
The identification of the procurement project. |
name: |
The word or group of words by which the procurement_project is |
|
referred to. |
description: |
A description of the procurement project. |
7.4.10 procurement_project_assignment
The assignment of a procurement project to a product.
ENTITY procurement_project_assignment;
project |
: procurement_project; |
responsible_organization |
: organization; |
assigned_to |
: product_aspects; |
END_ENTITY; |
|
project: |
The procurement project being assigned. |
responsible_organization: |
The organization responsible for the assignment of the |
|
procurement project. |
assigned_to: |
The product data to which the procurement project is assigned. |
7.4.11 product_maintenance_level_association
The maintenance_level which has been assigned for a particular product aspect.
ENTITY product_maintenance_level_association;
product |
: product_aspects; |
level |
: maintenance_level; |
END_ENTITY; |
|
product: |
The particular product aspect to which a maintenance_level is |
|
assigned. |
level: |
The maintenance_level which has been assigned. |
7.4.12 provisioning_period
The calendar period in which the provisioning_quantity will be applicable to the product when operating in a specific scenario. Assigned as a time_unit_with_measure.
ENTITY provisioning_period;
name |
: label; |
duration |
: time_measure_with_unit; |
applies_to |
: scenario; |
END_ENTITY; |
|
name: |
The word or group of words which identify the |
|
provisioning_period. |
duration: |
The calendar period in which the provisioning_quantity will be |
|
applicable to the product when operating in a specific scenario. |
|
Assigned as a time_measure_with_unit. |
applies_to: |
The identification of the scenario in which the assignment of a |
|
provisioning_period for the product applies. |
7.4.13 provisioning_quantity
The numeric quantity of the product which is the subject of provisioning activity, assigned as a specific unit_of_issue to a specific organization.
ENTITY provisioning_quantity;
repair_count |
: OPTIONAL INTEGER; |
maintenance_count : OPTIONAL INTEGER; |
|
recommended_by |
: organization; |
applies_to |
: unit_of_issue; |
for_period |
: provisioning_period; |
WHERE |
|
WR1: EXISTS(repair_count)OR EXISTS(maintenance_count); |
|
END_ENTITY; |
|
repair_count: |
The quantity of provisioned items required for the performance of |
|
repair and overhaul maintenance tasks to the specific product. |
maintenance_count: |
The quantity of provisioned items required for the performance of |
|
maintenance tasks to the specific product, other than corrective |
|
or unscheduled tasks. |
recommended_by: |
The organization responsible for recommending the |
|
provisioning_quantity. |
applies_to: |
Indicates the physical measurement, the count, or when neither is |
|
appropriate the container or shape of a product for the purposes |
|
of provisioning and issue to an organization. |
for_period: |
The calender period in which the provisioning_quantity will be |
|
applicable to the product when operating in a specific scenario. |
|
Assigned as a time_measure_with_unit. |
7.4.14 recovery_method
Indicates the disposition action to be taken on unserviceable items.
ENTITY recovery_method;
id |
: |
identifier; |
description : |
text_select; |
|
END_ENTITY;
id: |
The identification of the recovery_method for the unserviceable |
|
product. |
description: |
A narrative description of the disposition action to be taken on |
|
the unserviceable product. |
7.4.15 recovery_method_assignment
The assignment of a recovery method to an element or product_design_definition or product_definition_relationship in a specific scenario.
ENTITY recovery_method_assignment;
assigned_method |
: recovery_method; |
assigned_to |
: product_aspects; |
level |
: OPTIONAL maintenance_level; for_scenario |
: scenario; |
|
END_ENTITY; |
|
assigned_method: |
The assigned recovery_method to be taken on the unserviceable |
|
product. |
assigned_to: |
The particular product_aspects to which a recovery_method |
|
requires to be assigned. |
level: |
The maintenance_level which has been assigned to a particular |
|
product and its recovery_method. |
for_scenario: |
The identification of the scenario in which the assignment of a |
|
recovery_method to a product applies. |
7.4.16 role
The specific operational role that a product is required to perform. This will affect the logistic support requirements to be determined for the product under this specific role.
ENTITY role; |
|
name |
: label; |
where_used |
: SET [0:?] OF operating_location; |
description : text_select; |
|
END_ENTITY; |
|
name: |
The word or group of words which identify the specific role of the |
|
product. |
where_used: |
The name of the geographical location or area in which the |
|
product will be operated for the performance of a specific role. |
description: |
A narrative description of the specific operational role that a |
|
product is required to perform. This will affect the logistic |
|
support requirements to be determined for the product under this |
|
specific role. |
7.4.17 scenario
Scenario is used to allow for the different factors affecting different users of a product. For example, users from different countries may be subject to different legislation or conditions which determine how a task may be performed.
ENTITY scenario; |
|
|
id |
: identifier; |
|
usage |
: SET [0:?] OF |
role; |
user |
: SET [1:?] OF |
organization; |
operating_location_count |
: OPTIONAL INTEGER; |
|
number_of_systems |
: OPTIONAL INTEGER; |
|
description |
: text_select; |
|
END_ENTITY; |
|
|
id: |
The identification of the scenario. |
usage: |
The role or roles that are envisaged in the scenario. |
user: |
The primary organization to which the scenario applies. |
operating_location_count: |
The number of operating locations for the product within the |
|
scenario. |
number_of_systems: |
The number of primary defence systems to operated in the |
|
scenario. |
description: |
A description of the scenario. |
7.4.18 sourcing_method
Indicates the manner of procuring items for maintenance, repair or overhaul of products.
ENTITY sourcing_method;
id |
: identifier; |
description : text_select; |
|
END_ENTITY; |
|
id: |
The identification of a specific sourcing_method for a product. |
description: |
A narrative description indicating the manner of procuring items |
|
for maintenance, repair or overhaul of products. |
7.4.19 sourcing_method_assignment
The assignment of a sourcing method to a product_aspect in a specific scenario.
ENTITY sourcing_method_assignment;
assigned_method |
: sourcing_method; |
assigned_to |
: product_aspects; |
level |
: OPTIONAL maintenance_level; |
for_scenario |
: scenario; |
END_ENTITY; |
|
assigned_method: |
The assigned sourcing_method to be applied for provisioning of |
|
a specific product. |
assigned_to: |
The particular product_aspect to which a sourcing_method |
|
requires to be assigned. |
level: |
The maintenance_level which has been assigned to a particular |
|
product with respect to a specific sourcing_method. |
for_scenario: |
The identification of the scenario in which the assignment of a |
|
sourcing_method to a product applies. |
END_SCHEMA/-- SCENARIO_AND_MAINTENANCE_SCHEMA