NOTE    The fault (or failure) analysis process links effects to anomalies. The effect may have different probabilities of occurrence in different mission phases/plant states

[1] PLCS terminology dictionary, 2000.

[1] ISO 9000, Quality Management System - Fundamentals and vocabulary

[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004.

NOTE    May define the "production break in" point or the applicability of modifications to realized product already built.

[1] PLCS Activity Model, 2000.

[1] ISO 9000, Quality Management System - Fundamentals and vocabulary

[1] PLCS terminology dictionary, 2000.

NOTE    Synonym to component.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    Elicited support needs are derived from analyses of customer and stakeholder needs and priorities with associated rationale, including source documents or agreements.

Elicited support needs may include:

• intended life time of product and support
• intended duration of deployments
• quantities of products to be supported
• needs for standardization in order to interface effectively with other organizations, users or partners, to reduce needs for new or additional investments, or to comply with life cycle needs of the product and its support; information from development, production, use, support and disposal of similar products
• experience from similar organizations, environments and scenarios
• experience from use and support of the product since its introduction into service.

May use AP233.

[1] PLCS Activity Model, 2000.

[1] PLCS terminology dictionary, 2000.

NOTE    End items have children, but no parents.

Synonym to top item.

[1] PLCS terminology dictionary, 2000.

NOTE    An organization may be involved in several enterprises and an enterprise may involve on or more organizations.

[1] ISO 15288, Systems engineering -- System life cycle processes , 2002.

NOTE    Non-preferred word.

Synonym to product.

[1] PLCS terminology dictionary, 2000.

NOTE    Examples are: National/NATO Stock Number, Manufacturer's Part Number, Manufacturer Code (eg CAGE), Logistic Control Numbers [eg LCN, Alternative LCN (ALCN), End Item Acronym Code (EIAC)], Colloquial names and aliases. This activity will allow links to product information related to the element, which will be enabled when the product structure is populated.

NOTE    The approval authority for a change can be delegated to different levels in the organisation, dependant upon the classification of the change. As the life cycle progresses, the change authority often transitions to individuals with greater management and fiscal responsibility because the effect of a change can be more widespread and, as a result, the cost impact of change decisions are normally greater. The most complex multi-level configuration change management is practised on projects in which authority for making change decisions is structured around tiered " Change boards". The change approval authorities span many contractor and customer organisations each with defined limited authority to approve changes to the portion of the "system" under their organisation. Those changes, which exceed the authority of lower level change approval authorities, are elevated to a higher level.

NOTE    This establishes constraints and relationships on and between tasks. These may be due temporal, spatial, or sequential dependencies, or imposed by safety or other policies.

[1] PLCS terminology dictionary, 2000.

NOTE    This includes documentation of the change opportunity or problem and the creation of a suitable description (AAM CM A1122) an analysis of the problem/opportunity and the reason for for a possible change along with a statement of its impact sufficient for evaluation (AAM CM A1123), determination of the appropriate level of priority (AAM CM A1121) and the raising and the approval of a Valid need for change as an input to (AAM CM A113) - Evaluate and co-ordinate solution or variance.

NOTE    The activities involved in developing, implementing and verifying the change solution(s) are planned (AAM CM A1132), the business case is developed and the soluion authorised, deferred or rejected in sub-process (AAM CM A1133). Evaluate and co-ordinate is the process of reviewing the impact assessments, determining in detail impact of the change in respect to operation, support, schedule, effectivity and cost in order to approve or reject the proposal. Includes the process of grouping changes to make economical and/or convenience/opportunistic packages. Variances will be subject to this activity to establish effects on other CIs.

Considers the technical, support, schedule and cost impacts of a requested change before making a judgement as to whether the change should be approved for implementation and incorporation in the PIF and its documentation.

NOTE    Evaluated support improvement opportunity may be expressed as specified tasks or as work requests.

[1] PLCS Activity Model, 2000.

[1] ISO/IEC 12207, Information technology -- Software life cycle processes , 2004.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

!!Needs discussions within SSE!!

NOTE    Eg split pins, nuts, bolts, washers, circlips, cable ties that are generally used only once then discarded after removal.

[1] PLCS terminology dictionary, 2000.

[1] PLCS terminology dictionary, 2000.

See: (http://en.wikipedia.org/wiki/ISO_10303-11)

[1] DEXlib definitions, .

[1] DEXlib definitions, .

NOTE    Extensions are applied to usage factor limits (eg Bay servicing), and do not affect accrued usage factor. An extension has to be authorised and can have limitations associated with it (these will usually be stress related). Additionally, an authorising authority may only be empowered to extend certain characteristics and only by a given percentage. Extensions apply to actual product instances, not to product designs.

Extensions do not transfer with subassemblies. If a task that is due on a subassembly is extended, and the assembly is removed from the parent prior to the task being performed, then the extension is cancelled and if the subassembly is fitted to a new parent, the task must be performed at the original time, or re-extended. Records of extensions and who authorised them must be kept.

See: anticipation

[1] PLCS terminology dictionary, 2000.

[1] PLCS Activity Model, 2000.