13.WORK MANAGEMENT

13.1Overview

The Work Management schema provides data structures for representation of the data required to manage work and actions during life-cycle process (e.g. Engineering change proposal, configuration change control etc.). The structure is based on three fundamental concepts: work request, work order and activity. A work_request documents the need for a potential action, which may or may not ever be performed. If the request is approved, it is done thorough some actions being taken on the request. This action identifying the work to be done to address the request is formally directed by the work_order.

13.2 Description

13.2.1 Configuration Change Control

Configuration Change Control is the process to manage preparation, justification, coordination, disposition and implementation of proposed engineering changes and deviations to effected Configuration Items.

Figure 13.1 Activity and Related Entites

This process is supported by the Entities work_request, work_order and activity. The simplified Express G indicates the relationship between the three entities.

13.2.2 Product Instance Maintenance History

The maintenance history is essential not only to plan the support activities of a product instance but also to plan its operational use. The logistic_activity is a subtype of the Entity activity. From activity, the Entity logistic_activity inherits the attributes describing the who, when and what of the activity.

activity

Figure 13.2 Product Instance Maintenance History

13.3 EXPRESS G Diagrams

WORK_MANAGEMENT_SCHEMA EXPRESS-G diagram 4 of 5

WORK_MANAGEMENT_SCHEMA EXPRESS-G diagram 5 of 5

13.4 EXPRESS Syntax

SCHEMA WORK_MANAGEMENT_SCHEMA;

REFERENCE FROM ANOMALY_SCHEMA (detection_method,

product_anomaly, compensating_provision);

REFERENCE FROM CHARACTERISTICS_SCHEMA (characteristic,

characteristic_assignment); REFERENCE FROM CONFIGURATION_SCHEMA

(configuration_item); REFERENCE FROM CORE_MODEL_SCHEMA

(product, product_definition_relationship, element,

product_version, product_definition);

REFERENCE FROM DATE_AND_TIME_SCHEMA (date_and_time);

REFERENCE FROM INFORMATION_OBJECT_SCHEMA (information_object,

publication);

REFERENCE FROM PERSON_AND_ORGANIZATION_SCHEMA (person_organization_select);

REFERENCE FROM PRODUCT_CONCEPT_SCHEMA (product_concept,

specification, specification_category, specification_expression);

REFERENCE FROM PRODUCT_INSTANCE_SCHEMA (product_instance_definition);

REFERENCE FROM SCENARIO_AND_MAINTENANCE_SCHEMA (scenario);

REFERENCE FROM SUPPORT_RESOURCES_SCHEMA (identifier,

label, text_select);

REFERENCE FROM TASK_SCHEMA (task_method,

task, task_resource_requirement);

13.4.1 activity_element_select

TYPE activity_element_select = SELECT (product,

product_definition, specification_expression, characteristic, compensating_provision, specification_category, detection_method,

ENTITY work_order;

13.4.13 work_request

A work_request is the solicitation for some work to be done.

ENTITY work_request;

END_SCHEMA/-- WORK_MANAGEMENT_SCHEMA