|
Before Issue 4.1, the Common Information Repository (CIR) was known as the Technical Information Repository (TIR).
The term CIR is used throughout this document to refer to both CIR and TIR.
|
Functional Items
|
Used to uniquely identify an item performing a function in a given system at a given position.
|
||
Circuit Breakers
|
Used to uniquely identify a device used to break properly an electrical circuit or to inactivate an electrical function.
|
||
Parts
|
Used to uniquely identify an item of the product, forming part of an assembly or subassembly, which is not normally broken down further.
|
||
Zones
|
Used to uniquely identify a structural area of the product.
|
||
Access points
|
Used to uniquely identify an access point to be opened to gain access to the equipment.
|
||
Enterprise information
|
Used to uniquely identify an organization involved in the manufacturing or in the supply of the product or part of it.
|
||
Supplies
|
Used to uniquely identify both the consumable products and their use conditions (consumable requirement and use conditions). It covers any consumables, materials, and expendables required to correctly accomplish a given action, task, or procedure.
• Consumables — For example, oils, greases, paints
• Materials — For example, gasket sheet, sheet metal
• Expendables — For example, O-rings, gaskets, tab washers
|
||
Supplies, requirements
|
Used to capture and represent supplies requirements and use conditions. The supplies requirements identification can be used to uniquely identify the supplies use-conditions. For example, in which case a supply or a group of supplies can be used.
|
||
Support equipment
|
Used to uniquely identify any support equipment required to correctly accomplish a given action, task, or procedure.
|
||
Tools
|
Used to uniquely identify any tool required to correctly accomplish a given action, task, or procedure.
|
||
Functional and/or physical areas
|
The functional and/or physical breakdown is the collection of functional and/or physical areas with their properties and the relationships between them.
|
||
Controls and indicators
|
This information assists personnel in determining the location and function of the controls and indicators.
|
Applicability annotations
|
Used to store externalized applicability annotations for projects which need to externalize the applicability annotations from other data modules. The advantage of externalizing the applicability from other data modules is to simplify data module revisions.
|
Warnings
|
Used to collect and centralize in one place, warnings that are used in several data modules. It is an alternative to the warning collection at data module level.
|
Cautions
|
Used to collect and centralize in one place, cautions that are used in several data modules. It is an alternative to the caution collection at data module level.
|