BACK to
Implemenation
Guidelines

Overview

Configuration change control

Product Instance maintenance history

The Work Management Schema

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.

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.

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.

Figure 13.2 Product Instance Maintenance History