Loading...
S3000L Schema
The information on this page is considered "draft" for discussion purposes only, and is not an official source of the schemas or related information represented here.
For official information on S3000L, see the S3000L website.
Classes
Class (Element)
AdditionalTrainingRequirement
Chapter
19
Paragraph
4.15.3.21
Units of Functionality Diagrams
X
X
X
Additional Training Requirement
Description
The AdditionalTrainingRequirement attributeGroup identifies additional training required for the given competence (Trade, SkillLevel or Skill), in order for the defined competence to be qualified to play the role of the personnel resource.
Comment
Note: An instance of class AdditionalTrainingRequirement has no meaning by itself, but only in the context of an association between a specific required personnel resource, and a defined competence (ie, in the context of a specific instance of TaskPersonnelResourceCompetence).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AggregatedElement
Chapter
19
Paragraph
4.7.3.1
Short Name
beAggr
Units of Functionality Diagrams
X
Aggregated Element
Description
The AggregatedElement class is a specialization of the BreakdownElement class, and identifies a collection of BreakdownElements that are grouped for an identified purpose, eg, a system, function or a slot.
Comment
Note: Wherever the BreakdownElement class is used in the data model, AggregatedElement can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AggregatedElementRevision
Chapter
19
Paragraph
4.7.3.2
Short Name
beRev
Units of Functionality Diagrams
X
Aggregated Element Revision
Description
The AggregatedElementRevision class is a specialization of the BreakdownElementRevision class, and represents a design iteration that is applied to an AggregatedElement.
Comment
Note: Wherever BreakdownElementRevision is used in the data model, AggregatedElementRevision can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AllocatedMaintenanceLevel
Chapter
19
Paragraph
4.16.3.5
Short Name
maintLevel
Units of Functionality Diagrams
X
X
X
Allocated Maintenance Level
Description
The AllocatedMaintenanceLevel relationship class defines an association between an instance of PlannedTaskTarget and an identified support organization where the associated PlannedTaskItem will be carried out.
Comment
Note: There is one instance of AllocatedMaintenanceLevel per relevant combination of PlannedTaskUsage and support organization. AllocatedMaintenanceLevel special recommendations: - Where the AllocatedMaintenanceLevel is dependent upon eg, operational scenario, it must be distinguished by the assignment of an ApplicabilityStatement to the AllocatedMaintenanceLevel instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
AllocatedMaintenanceLevelItem
Chapter
19
Paragraph
4.16.3.6
Units of Functionality Diagrams
X
Allocated Maintenance Level Item
Description
The AllocatedMaintenanceLevelItem interface is implemented by classes that can represent support organizations where a rectifying or operational task can be performed.
Units of Functionality
Class (Element)
AllowedProductConfiguration
Chapter
19
Paragraph
4.8.3.4
Units of Functionality Diagrams
X
X
X
X
Allowed Product Configuration
Description
The AllowedProductConfiguration interface is implemented by classes that define allowed configurations for a defined ProductVariant. AllowedProductConfiguration defines permitted combinations of hardware and software parts which can or must be installed in specific locations (positions) of an end item, and demonstrates that the product complies with applicable regulations.
Units of Functionality
Class (Element)
AllowedProductConfigurationByConfigurationIdentifier
Chapter
19
Paragraph
4.8.3.8
Short Name
prodConf
Units of Functionality Diagrams
X
X
Allowed Product Configuration By Configuration Identifier
Description
The AllowedProductConfigurationByConfigurationIdentifier class represents an AllowedProductConfiguration that is identified and managed by other means than a part identifier.
Attribute Properties
Units of Functionality
Class (Element)
AllowedProductConfigurationHardwarePartAsDesigned
Chapter
19
Paragraph
4.8.3.7
Short Name
hwConfPart
Units of Functionality Diagrams
X
Allowed Product Configuration Hardware Part As Designed
Description
The AllowedProductConfigurationHardwarePartAsDesigned class is a specialization of class HardwarePartAsDesigned, and represents hardware parts that are issued as authorized allowed product configurations.
Attribute Properties
partIdentifier
partName
partSpecialHandlingRequirement
hardwarePartOperationalAuthorizedLife
hardwarePartHazardousClass
hardwarePartFitmentRequirement
hardwarePartElectromagneticIncompatible
hardwarePartElectrostaticSensitive
hardwarePartElectromagneticSensitive
hardwarePartMagneticSensitive
hardwarePartRadiationSensitive
partMaturityClass
partObsolescenceRiskAssessment
hardwarePartLogisticsCategory
hardwarePartRepairability
hardwarePartRepairabilityStrategy
hardwarePartMaintenanceStart
hardwarePartWasteProductsInUseDisposalDescription
hardwarePartWasteProductsPlannedDisposalDescription
hardwarePartEnvironmentalAspectInUseClass
hardwarePartEnvironmentalAspectPlannedDisposalClass
hardwarePartScrapRate
hardwarePartConsumptionRate
partDemilitarizationClass
Element Properties
Units of Functionality
Class (Element)
AllowedProductConfigurationItem
Chapter
19
Paragraph
4.8.3.11
Units of Functionality Diagrams
X
Allowed Product Configuration Item
Description
The AllowedProductConfigurationItem interface is implemented by classes which applicability can be the restricted to specific AllowedProductConfigurations.
Comment
An instance of a class that implements the AllowedProductConfigurationItem interface can be associated with more than one AllowedProductConfiguration, ie, an instance representing the includedItem can be applicable to more than one AllowedProductConfiguration.
Units of Functionality
Class (Element)
AlternatePartAsDesignedRelationship
Chapter
19
Paragraph
4.4.3.2
Short Name
altPart
Units of Functionality Diagrams
X
X
X
X
Alternate Part As Designed Relationship
Description
The AlternatePartAsDesignedRelationship relationship class is used to define alternate parts. An alternate part is interchangeable with the base part in all its usages. The alternate part is a context independent alternate that is form, fit, and function equivalent in any use (Source: ISO 10303:239 Product Life Cycle Support).
Comment
Note: AlternatePartAsDesignedRelationship defines one alternate PartAsDesigned at the time, and applies both to HardwarePartAsDesigned and SoftwarePartAsDesigned.
Element Properties
Units of Functionality
Class (Element)
AND
Chapter
19
Paragraph
4.22.3.14
Short Name
and
Units of Functionality Diagrams
X
AND
Description
The AND class is a specialization of class LogicalOperator, and defines a list of ApplicabilityEvaluations that all need to be TRUE in order for the overall ApplicabilityStatement to be TRUE.
Comment
Note: S1000D uses AND statements in the definition of an applic element.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityAssertItem
Chapter
19
Paragraph
4.22.3.22
Units of Functionality Diagrams
X
Applicability Assert Item
Description
The ApplicabilityAssertItem interface is implemented by classes that have instances (values) that can be used for defining applicability statements.
Units of Functionality
Class (Element)
ApplicabilityAssignment
Chapter
19
Paragraph
4.22.3.9
Units of Functionality Diagrams
X
X
Applicability Assignment
Description
The ApplicabilityAssignment relationship class defines a relationship between a specific ApplicabilityStatement and an instance of any class that implements the ApplicabilityAssignmentItem interface, ie, instance to which the ApplicabilityStatement applies.
Comment
Note: There is one instance of ApplicabilityAssignment per relevant combination of ApplicabilityStatement and instance to which the ApplicabilityStatement is being applied (ie, instance of any class that implements the ApplicabilityAssignmentItem interface).
Element Properties
Units of Functionality
Class (Element)
ApplicabilityAssignmentItem
Chapter
19
Paragraph
4.22.3.10
Units of Functionality Diagrams
X
Applicability Assignment Item
Description
The ApplicabilityAssignmentIteminterface is implemented by classes that can be associated with applicability statements.
Comment
Note: ApplicabilityStatements can also be assigned to any class that is a subclass of the enumerated classes, eg, RectifyingTask which is a subclass of Task (rule of substitutability).
Units of Functionality
Class (Element)
ApplicabilityEvaluation
Chapter
19
Paragraph
4.22.3.11
Units of Functionality Diagrams
X
X
Applicability Evaluation
Description
The ApplicabilityEvaluation class identifies an expression against which the applicability statement can be asserted.
Comment
ApplicabilityEvaluation is an abstract class, ie, an instantiation of ApplicabilityEvaluation must always be done using any of its specializations:
- ApplicabilityEvaluationByLogicalOperator
- ApplicabilityEvaluationByAssertionOfCondition
- ApplicabilityEvaluationByAssertionOfClassInstance
- ApplicabilityEvaluationByAssertionOfSerializedItems
- ApplicabilityEvaluationByApplicabilityStatementReference
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByApplicabilityStatementReference
Chapter
19
Paragraph
4.22.3.17
Short Name
nestedApplic
Units of Functionality Diagrams
X
Applicability Evaluation By Applicability Statement Reference
Description
The ApplicabilityEvaluationByApplicabilityStatementReference class is a specialization of class ApplicabilityEvaluation, and makes a reference another ApplicabilityStatement that must be asserted as part of a parent ApplicabilityEvaluation expression. This class enables the definition of nested applicability statements.
Comment
Note: An instance of ApplicabilityEvaluationByApplicabilityStatementReference does not have any meaning outside the context of the ApplicabilityStatement or LogicalOperator, in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByAssertion
Chapter
19
Paragraph
4.22.3.18
Units of Functionality Diagrams
X
Applicability Evaluation By Assertion
Description
The ApplicabilityEvaluationByAssertion class is a specialization of class ApplicabilityEvaluation, and identifies a value against which an applicability statement must be asserted.
Comment
Note: ApplicabilityEvaluationByAssertion is an abstract class, ie, an instantiation of ApplicabilityEvaluationByAssertion must always be done using any of its specializations.
Note: ApplicabilityEvaluationByAssertion subclasses:
- ApplicabilityEvaluationByAssertionOfCondition
- ApplicabilityEvaluationByAssertionOfClassInstance
- ApplicabilityEvaluationByAssertionOfSerializedItems
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByAssertionOfClassInstance
Chapter
19
Paragraph
4.22.3.21
Short Name
assertInst
Units of Functionality Diagrams
X
Applicability Evaluation By Assertion Of Class Instance
Description
The ApplicabilityEvaluationByAssertionOfClassInstance class is a specialization of class ApplicabilityEvaluationByAssertion and identifies a class instance against which an applicability statement must be asserted.
Comment
Note: An instance of ApplicabilityEvaluationByAssertionOfClassInstance does not have any meaning outside the context of the ApplicabilityStatement or LogicalOperator in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByAssertionOfCondition
Chapter
19
Paragraph
4.22.3.19
Short Name
assertCond
Units of Functionality Diagrams
X
Applicability Evaluation By Assertion Of Condition
Description
The ApplicabilityEvaluationByAssertionOfCondition class is a specialization of class ApplicabilityEvaluationByAssertion, and identifies a condition statement against which the applicability statement must be asserted.
Comment
Note: An instance of ApplicabilityEvaluationByAssertionOfCondition does not have any meaning outside the context of the ApplicabilityStatement or LogicalOperator in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByAssertionOfSerializedItems
Chapter
19
Paragraph
4.22.3.23
Short Name
assertSi
Units of Functionality Diagrams
X
Applicability Evaluation By Assertion Of Serialized Items
Description
The ApplicabilityEvaluationByAssertionOfSerializedItems class is a specialization of class ApplicabilityEvaluationByAssertion, and identifies a range of serialized items against which the applicability statement must be asserted.
Comment
Note: An instance of ApplicabilityEvaluationByAssertionOfSerializedItems does not have any meaning outside the context of the ApplicabilityStatement or LogicalOperator in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityEvaluationByLogicalOperator
Chapter
19
Paragraph
4.22.3.12
Units of Functionality Diagrams
X
Applicability Evaluation By Logical Operator
Description
The ApplicabilityEvaluationByLogicalOperator class is a specialization of class ApplicabilityEvaluation, and defines a logical expression against which an applicability statement can be evaluated.
Comment
Note: An instance of LogicalOperator is always defined for a specific instance of ApplicabilityEvaluationByLogicalOperator. An instance of LogicalOperator does always refer to one or many other instances of ApplicabilityEvaluation, which in turn can be either a logical expression or a value to be asserted.
Note: An instance of ApplicabilityEvaluationByLogicalOperator does not have any meaning outside the context of the ApplicabilityStatement or LogicalOperator instance, in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ApplicabilityStatement
Chapter
19
Paragraph
4.22.3.7
Short Name
applicDef
Units of Functionality Diagrams
X
X
X
Applicability Statement
Description
The ApplicabilityStatement class defines explicit applicability statements to be applied against instances in a LSA database.
Comment
Note: Applicability statements can be evaluated in a maintenance execution environment, eg, using an Interactive Electronic Technical Publishing (IETP).
Note: ApplicabilityStatement can be specialized into a DatedApplicabilityStatement.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ApplicableBlockOfSerializedEndItems
Chapter
19
Paragraph
4.8.3.13
Units of Functionality Diagrams
X
Applicable Block Of Serialized End Items
Description
The ApplicableBlockOfSerializedEndItems attributeGroup defines a possibly open-ended serial number range.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AuthorityDrivenTaskRequirement
Chapter
19
Paragraph
4.13.3.2
Short Name
authTaskReq
Units of Functionality Diagrams
X
Authority Driven Task Requirement
Description
The AuthorityDrivenTaskRequirement class is a specialization of class TaskRequirement, and will be used to record task requirements which are derived from regulations and/or other authoritative sources.
Comment
Note: AuthorityDrivenTaskRequirement special recommendations: Each instance of AuthorityDrivenTaskRequirement must have at least one document reference from which the task requirement is derived, using the DocumentAssignment capability defined in UoF Document (via the DocumentAssignmentItem interface). Refer to Para 4.20.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AuthorityToOperate
Chapter
19
Paragraph
4.20.4.26
Short Name
authToOp
Units of Functionality Diagrams
X
X
X
Authority To Operate
Description
AuthorityToOperate signifies the safety aspects of a product to be manufactured, and is issued by a regulating body, and once issued, the design cannot be changed without re-authorization.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
AuthorizedLife
Chapter
19
Paragraph
4.20.4.67
Units of Functionality Diagrams
X
X
X
Authorized Life
Description
AuthorizedLife compoundAttribute is used to represent authorized life limits together with its authorizing organization.
Comment
Note: Multiple values for authorizedLife mean ‘whichever is reached first’. AuthorizedLife special recommendations: - If an item has different authorized lives depending on eg, operational environments, these can be represented as a set of values for the authorizedLife attribute and be distinguished by the assignment of an ApplicabilityStatement to the respective instance of PropertyType that represents the individual value. Refer to Para 4.22.
Attribute Properties
Units of Functionality
Class (Element)
BlockOfSerializedItems
Units of Functionality Diagrams
X
Block Of Serialized Items
Description
The BlockOfSerializedItems attributeGroup defines a possibly open-ended serial number range of end items or specific hardware parts.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Breakdown
Chapter
19
Paragraph
4.3.3.1
Short Name
bkdn
Units of Functionality Diagrams
X
X
X
X
Breakdown
Description
The Breakdown class identifies a specific partitioning of a Product into a set of related elements so as to form parent-child views that comprise the product elements.
Comment
Note: An example of a breakdown type is the GEIA-STD-0007 functional breakdown.
Examples of breakdowns are:
-Functional
-Physical
-System
-Zonal
-Hybrid, i.e., a mixture of the functional, physical, system and zonal
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElement
Chapter
19
Paragraph
4.3.3.7
Units of Functionality Diagrams
X
X
X
X
X
X
Breakdown Element
Description
The BreakdownElement class is used to represent items that are part of one or many Breakdowns and revisions thereof.
Comment
Note: BreakdownElement is defined as an abstract class, ie, this class will never be instantiated, but any of its subclasses will. Subclasses of BreakdownElement are: HardwareElement (defined in UoF Breakdown Element Realization). Refer to Para 4.5. SoftwareElement (defined in UoF Breakdown Element Realization). Refer to Para 4.5. ZoneElement (defined in UoF Breakdown Element Realization). Refer to Para 4.5. AggregatedElement (defined in UoF Breakdown Aggregated Element). Refer to Para 4.7.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElementInZoneRelationship
Chapter
19
Paragraph
4.6.3.3
Short Name
inZone
Units of Functionality Diagrams
X
X
X
Breakdown Element In Zone Relationship
Description
The BreakdownElementInZoneRelationship relationship class defines an association between two instances of BreakdownElementUsageInBreakdown where the relatedZone instance must represent the usage of a zonal location (ZoneElementRevision).
Comment
Note: There is one instance of BreakdownElementInZoneRelationship per combination of BreakdownElementUsageInBreakdown and zonal location (ZoneElementRevision via the relatedZone association).
Element Properties
Units of Functionality
Class (Element)
BreakdownElementRevision
Chapter
19
Paragraph
4.3.3.8
Units of Functionality Diagrams
X
X
X
X
X
Breakdown Element Revision
Description
The BreakdownElementRevision class defines a revision (design iteration) that is applied to a BreakdownElement.
Comment
Note: New revisions of BreakdownElements are often defined during product design.
Note: BreakdownElementRevision is defined as an abstract class, ie, this class will never be instantiated but any of its subclasses will. Subclasses of BreakdownElementRevision are:
- HardwareElementRevision (defined in UoF Breakdown Element Realization). Refer to Para 4.5.
- SoftwareElementRevision (defined in UoF Breakdown Element Realization). Refer to Para 4.5.
- ZoneElementRevision (defined in UoF Breakdown Element Realization). Refer to Para 4.5.
- AggregatedElementRevision (defined in UoF Breakdown Aggregated Element). Refer to Para 4.7.
Note: A revision of a breakdown element can be used in one or many breakdowns via the BreakdownRevision and BreakdownElementUsageInBreakdown. This means that the same BreakdownElementRevision can be re-used in between different types of breakdowns for a single Product/ProductVariant, as well as be re-used in between Products/ProductVariants.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElementRevisionRelationship
Chapter
19
Paragraph
4.3.3.9
Short Name
beRel
Units of Functionality Diagrams
X
X
Breakdown Element Revision Relationship
Description
The BreakdownElementRevisionRelationship relationship class defines relationships in between two instances of BreakdownElementRevision.
Comment
Note: BreakdownElementRevisionRelationship can be used to represent the functional/physical breakdown element relationship as defined in GEIA-STD-0007.
Note: BreakdownElementRevisionRelationship can be used to represent, eg, use of software in hardware.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElementStructure
Chapter
19
Paragraph
4.3.3.5
Short Name
beChild
Units of Functionality Diagrams
X
Breakdown Element Structure
Description
The BreakdownElementStructure relationship class is an association that establishes a hierarchical structure between BreakdownElementRevisions (parent/child) that belong to the same BreakdownRevision.
Comment
Note: An explicit breakdown structure is accomplished by organizing the usages of the BreakdownElementRevisions, ie, by organizing the instances of BreakdownElementUsageInBreakdown instead of the organizing the BreakdownElementRevisions themselves.
Note: A breakdown structure can also be derived from the values given as breakdownElementIdentifiers. The breakdown structure is then implicit, rather than explicit and do not require the usage of the BreakdownElementStructure class. This approach can be used if the breakdownElementIdentifier follows the logic of eg, GEIA-STD-0007 Logistics Control Number (LCN) or S1000D Standard Numbering System (SNS). A discussion on the advantages/disadvantages of the respective approach is given in Chap 4 Configuration Management.
Note: Both parent and child instances of BreakdownElementUsageInBreakdown must be defined for the same instance of BreakdownRevision.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElementStructureRelationship
Chapter
19
Paragraph
4.3.3.6
Short Name
relatedElem
Units of Functionality Diagrams
X
X
Breakdown Element Structure Relationship
Description
The BreakdownElementStructureRelationship relationship class is an association where the usage of a BreakdownElementRevision (relating) is restricted or associated with the usage of another BreakdownElementRevision (related).
Comment
Note: Examples on information that can be represented using BreakdownElementStructureRelationship are:
- Substitute elements such as “real” vs “dummy”
- Element A cannot be installed at the same time as element B (“negative statement”)
- Element A must only be installed with element C (“positive statement”)
Note: Both instances of BreakdownElementStructure must relate to instances of BreakdownElementUsageInBreakdown that exist within the same BreakdownRevision.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
BreakdownElementUsageInBreakdown
Chapter
19
Paragraph
4.3.3.4
Short Name
beUsage
Units of Functionality Diagrams
X
X
X
X
Breakdown Element Usage In Breakdown
Description
The BreakdownElementUsageInBreakdown relationshipclass is an association establishing the BreakdownElementRevisions (related) that belong to a BreakdownRevision (relating).
Comment
Note: Each instance of BreakdownElementUsageInBreakdown is uniquely defined for one combination of BreakdownElementRevision and BreakdownRevision. An instance of the BreakdownElementUsageInBreakdown class doesn’t have any meaning by itself but only in the context of a BreakdownRevision.
Note: An instance of BreakdownElementUsageInBreakdown can be the parent of many instances of BreakdownElementUsageInBreakdown (ie, BreakdownElementRevisions) defined for the same BreakdownRevision.
Note: There is one instance of BreakdownElementStructure per parent-child relationship, and there is no explicit ordering in between the parent-child relationships defined for a specific BreakdownElementUsageInBreakdown (ie, ordering of child elements for a specific parent element).
Element Properties
Units of Functionality
Class (Element)
BreakdownItem
Chapter
19
Paragraph
4.3.3.2
Units of Functionality Diagrams
X
Breakdown Item
Description
The BreakdownItem interface represents the common behavior of those items that can have one or many associated breakdown structures.
Comment
Note: Breakdowns must be defined either on a Product level or on a ProductVariant level, but must never occur on both levels for one and the same Product.
Units of Functionality
Class (Element)
BreakdownRevision
Chapter
19
Paragraph
4.3.3.3
Short Name
bkdnRev
Units of Functionality Diagrams
X
X
X
Breakdown Revision
Description
The BreakdownRevision class defines an explicit revision (design iteration) that is applied to a Breakdown.
Comment
Note: BreakdownElementRevisions used in a breakdown are related to a BreakdownRevision and not directly to the Breakdown.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
CandidateItemAnalysisActivity
Chapter
19
Paragraph
4.10.3.1
Units of Functionality Diagrams
X
X
X
X
X
Candidate Item Analysis Activity
Description
The CandidateItemAnalysisActivity class identifies the LSA activities that can be performed for the respective LSA Candidate, the rationale behind it, and the recorded status for the respective analysis activity.
Comment
Note: LSA activities are often selected during the LSA guidance conference.
Note: LSA activities can be defined for LSA Candidates at any level of indenture.
Note: The CandidateItemAnalysisActivity class is an abstract class, ie, the class itself will never be instantiated but any of its subclasses can. Subclasses of CandidateItemAnalysisActivity are:
- LSACandidateComparativeAnalysisActivity
- LSACandidateHumanFactorAnalysisActivity
- LSACandidateReliabilityAnalysisActivity
- LSACandidateMaintainabilityAnalysisActivity
- LSACandidateTestabilityAnalysisActivity
- LSACandidateFailureModeAndEffectAnalysisActivity
- LSACandidateDamageAnalysisActivity
- LSACandidateSpecialEventAnalysisActivity
- LSACandidateLevelOfRepairAnalysisActivity
- LSACandidateMaintenanceTaskAnalysisActivity
- LSACandidateSoftwareDataLoadingAnalysisActivity
- LSACandidateSoftwareSupportAnalysisActivity
- LSACandidateOperationalAnalysisActivity
- LSACandidateSimulationOperationalScenariosAnalysisActivity
- LSACandidateTrainingNeedsAnalysisActivity
- LSACandidateOtherAnalysisActivity
Attribute Properties
Units of Functionality
Class (Element)
ChangeRequest
Chapter
19
Paragraph
4.13.3.7
Short Name
cr
Units of Functionality Diagrams
X
X
X
X
Change Request
Description
The ChangeRequest class supports the recording of needed changes to the product design.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ChangeRequestSource
Chapter
19
Paragraph
4.13.3.8
Short Name
changeReq
Units of Functionality Diagrams
X
Change Request Source
Description
The ChangeRequestSource relationship class define an association between a ChangeRequest and the TaskRequirementRevision for which the change request has been identified.
Comment
Note: There is one instance of ChangeRequestSource per combination of ChangeRequest and TaskRequirement.
Element Properties
Units of Functionality
Class (Element)
ChangeRequestTarget
Chapter
19
Paragraph
4.13.3.9
Short Name
crObject
Units of Functionality Diagrams
X
Change Request Target
Description
The ChangeRequestTarget relationship class defines an association between a ChangeRequest and the LSACandidate which is affected by the defined change.
Comment
Note: There is one instance of ChangeRequestTarget per combination of ChangeRequest and LSACandidate.
Element Properties
Units of Functionality
Class (Element)
CircuitBreaker
Chapter
19
Paragraph
4.14.3.24
Short Name
cb
Units of Functionality Diagrams
X
X
X
Circuit Breaker
Description
The CircuitBreaker class identifies individual circuit breakers that are installed on the Product.
Comment
Note: CircuitBreaker special recommendations: Circuit breaker location can be defined using the assignment of a Document, where the documentAssignmentRole is set to “Source”, and the documentPortion attribute describes the location.
Attribute Properties
Element Properties
Class (Element)
ClassificationType
Chapter
19
Paragraph
4.20.4.68
Units of Functionality Diagrams
X
X
X
Classification Type
Description
The ClassificationType primitive is used for representing references to terms, which can be used for classification. The data model assumes that each term used has a definition in an external dictionary such as the ASD/AIA Dictionary, SX001D. This is also known as a Reference Data Library (RDL) in OASIS PLCS. For more information on the use of RDL refer to www.plcs-resources.org.
Comment
Note: Classifications often appears as value lists (enumerations) in legacy applications.
Note: There is also a compound attribute type defined within S3000L for representing dated classifications (DatedClassification). This compound attribute type adds the possibility to define a date for when the classification was done.
Note: Assignment of ApplicabilityStatements to instances of ClassificationType enables multiple classifications to be given for a single attribute in the data model, where multiple classifications are allowed, and still distinguish when a single classification is applicable.
Attribute Properties
Units of Functionality
Class (Element)
CompetenceDefinitionItem
Chapter
19
Paragraph
4.15.3.16
Units of Functionality Diagrams
X
Competence Definition Item
Description
The CompetenceDefinitionItem interface enables Skills, SkillLevels and Trades to be associated with the definition of a personnel resource that is needed to perform a Task or a SubtaskByDefinition.
Element Properties
Units of Functionality
Class (Element)
ConditionDefinitionItem
Chapter
19
Paragraph
4.22.3.5
Units of Functionality Diagrams
X
Condition Definition Item
Description
The ConditionDefinitionItem interface is implemented by classes that can be asserted in order to determine the applicability of the data being defined during LSA.
Element Properties
Units of Functionality
Class (Element)
ConditionInstance
Chapter
19
Paragraph
4.20.4.64
Short Name
condInst
Units of Functionality Diagrams
X
X
X
Condition Instance
Description
The ConditionInstance class identifies instances that belongs to a specific ConditionType, and can be used in the definition of one or more applicability statements.
Comment
Note: An example of a ConditionInstance is: • ‘Service bulletin S001 -Chain guard’ (an identified instance that belongs to the ‘Service bulletin’ ConditionType)
Note: The following rules can be applied to populate an S1000D CCT: conditionInstanceIdentifier can populate the S1000D CCT condition id attribute conditionInstanceDescription can populate the S1000D CCT conditiondescription element conditionInstanceName can populate the S1000D CCT conditionnameand conditiondisplayname elements, respectively
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ConditionStatement
Chapter
19
Paragraph
4.20.4.66
Units of Functionality Diagrams
X
X
X
Condition Statement
Description
The ConditionStatement relationship class firstly defines a reference to the related condition definition which must be asserted, and secondly a reference to the value which needs to be true in order for the ApplicabilityEvaluationByAssertionOfCondition expression to be true.
Comment
Note: An instance of ConditionStatement does not have any meaning outside the context of the ApplicabilityEvaluationByAssertionOfCondition instance in which it is being defined.
Element Properties
Units of Functionality
Class (Element)
ConditionType
Chapter
19
Paragraph
4.20.4.65
Short Name
cond
Units of Functionality Diagrams
X
X
X
Condition Type
Description
The ConditionType class defines types of conditions which cannot be derived from any of the other classes that are defined within the S3000L data model.
Comment
Note: Examples of condition types that cannot be derived from any other class in the S3000L data model, and therefore needs to be defined as a ConditionType are: Service bulletin Operational environment Wind speed Ashore/Afloat Operational scenario Operational state
Note: An example of a class in the data model which can be used to assert an applicability expression is Customer. Individual customers (ie, instances of class Organization) can be used in the ApplicabilityEvaluationByAssertionOfClassInstance. These values will therefore already exist in the LSA data and must not be defined as a ConditionType.
Note: An example on ConditionType and ConditionInstance is ‘Service Bulletin’ (which is an instance of class ConditionType) and ‘Service bulletin S001 -Chain guard’ (which is an instance of ConditionInstance).
Note: The following rules can be applied to populate an S1000D Condition cross-reference table (CCT): conditionTypeName can populate the S1000D CCT conditiontype id attribute and conditiontypename element, respectively conditionTypeDescription can populate the S1000D CCT conditiontypedescription element
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ConditionTypeClassValue
Chapter
19
Paragraph
4.22.3.3
Units of Functionality Diagrams
X
Condition Type Class Value
Description
The ConditionTypeClassValue class is a specialization of class ConditionTypeValue and represents condition values which can be enumerated (instances of ClassificationType).
Comment
Note: Examples on valid values (instances of ClassificationType) that can be used are: Pre/Post defined as valid values for eg, the Service bulletin ConditionType Deser’/Arctic defined as valid values for an Operational environment ConditionType
Note: Instances of the ConditionTypeClassValue have no meaning by itself, but only in the context of a specific ConditionType.
Note: The following rules can be applied to populate an S1000D CCT: • conditionTypeClassValue can populate the S1000D CCT conditiontypeenum element for the associated ConditionType
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ConditionTypePropertyValue
Chapter
19
Paragraph
4.22.3.4
Short Name
propValue
Units of Functionality Diagrams
X
Condition Type Property Value
Description
The ConditionTypePropertyValue class is a specialization of class ConditionTypeValue and represents, eg, valid values and value ranges, which can be used for a specific ConditionType.
Comment
Note: Valid values can be of any kind of PropertyType, ie, it can be a SingleValuePropertyType, ValueWithTolerancesPropertyType, or a ValueRangePropertyType.
Note: Examples on valid property values are ‘0-15’, ‘15-30’ and ‘30-45’ defined for ConditionType ‘Wind speed’.
Note: Instances of the ConditionTypePropertyValue have no meaning by itself, but only in the context of a specific ConditionType.
Note: The following rules can be applied to populate an S1000D CCT: • conditionTypePropertyValue can populate the S1000D CCT conditiontypeenum element for the associated ConditionType
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ConditionTypeValue
Chapter
19
Paragraph
4.22.3.2
Units of Functionality Diagrams
X
Condition Type Value
Description
The ConditionTypeValue class defines valid values for a specific ConditionType.
Comment
Note: The ConditionTypeValue class is an abstract class, ie, any of its subclasses must be used for the actual representation of the expression to be evaluated or asserted. • ConditionTypeValue subclasses: - ConditionTypeClassValue - ConditionTypePropertyValue
Note: Instances of the ConditionTypeValue have no meaning by itself, but only in the context of a specific ConditionType.
Element Properties
Units of Functionality
Class (Element)
ContainedSubstance
Chapter
19
Paragraph
4.4.3.8
Short Name
contSubs
Units of Functionality Diagrams
X
X
X
Contained Substance
Description
The ContainedSubstance relationship class defines a relationship in between a SubstanceDefinition and a HardwarePartAsDesigned in which the substance is contained. It can eg, record the quantity of the contained substance, and a justification.
Comment
Note: There is one instance of ContainedSubstance per relevant combination of SubstanceDefinition and HardwarePartAsDesigned.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Contract
Chapter
19
Paragraph
4.1.3.3
Short Name
contr
Units of Functionality Diagrams
X
X
X
X
X
Contract
Description
The Contract class identifies contracts that are relevant for the LSA program under consideration.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ContractContext
Chapter
19
Paragraph
4.1.3.2
Short Name
context
Units of Functionality Diagrams
X
Contract Context
Description
The ContractContext class is a relationship class which defines the Project context for a Contract.
Comment
Note: There is one instance of ContractContext per relevant combination of Contract and Project.
Units of Functionality
Class (Element)
ContractContractor
Chapter
19
Paragraph
4.1.3.7
Short Name
contractor
Units of Functionality Diagrams
X
Contract Contractor
Description
The ContractContractor relationship class defines relationships in between a Contract and the Contractor organization.
Comment
Note: There is one instance of ContractContractor per combination of Contract and Contractor.
Element Properties
Units of Functionality
Class (Element)
ContractCustomer
Chapter
19
Paragraph
4.1.3.9
Short Name
customer
Units of Functionality Diagrams
X
Contract Customer
Description
The ContractCustomer relationship class defines relationships in between a Contract and the Customer organization.
Comment
Note: There is one instance of ContractCustomer per combination of Contract and Customer.
Units of Functionality
Class (Element)
ContractedProductVariant
Chapter
19
Paragraph
4.1.3.13
Short Name
contrPv
Units of Functionality Diagrams
X
X
X
X
Contracted Product Variant
Description
The ContractedProductVariant relationship class defines relationships in between a Contract and the ProductVariants that has been contracted. A contracted product variant can be restricted to one or many specific blocks of serialized items (using the contractedBlockOfSerializedItems attribute), and/or to one or many specific user organizations (via the UserOfContractedProductVariant relationship class).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ContractedProductVariantAtOperatingLocation
Chapter
19
Paragraph
4.2.3.10
Short Name
atOpLoc
Units of Functionality Diagrams
X
X
Contracted Product Variant At Operating Location
Description
The ContractedProductVariantAtOperatingLocation relationship class adds information to the association in between a contracted product variant and its operating location.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ContractedProductVariantAtOperatingLocationType
Chapter
19
Paragraph
4.2.3.9
Short Name
atOpLocType
Units of Functionality Diagrams
X
X
Contracted Product Variant At Operating Location Type
Description
The ContractedProductVariantAtOperatingLocationType relationship class adds information to the association in between a contracted product variant and its operating location type.
Comment
Note: There is one instance of ContractedProductVariantAtOperatingLocationType per relevant combination of ContractedProductVariant and OperatingLocationType.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Contractor
Chapter
19
Paragraph
4.1.3.6
Units of Functionality Diagrams
X
Contractor
Description
The Contractor interface is implemented by classes that can play the role of a Contractor.
Units of Functionality
Class (Element)
ContractRelationship
Chapter
19
Paragraph
4.1.3.4
Short Name
relContr
Units of Functionality Diagrams
X
X
Contract Relationship
Description
The ContractRelationship class is a relationship class, which defines relationships in between two related Contracts.
Comment
Note: An example of a contract relationship is subcontract.
Note: There is one instance of ContractRelationship per relevant combination of relating Contract and related Contract.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
CorrectionFactor
Chapter
19
Paragraph
4.9.3.17
Short Name
factor
Units of Functionality Diagrams
X
X
X
X
Correction Factor
Description
The CorrectionFactor attributeGroup defines a correction factor for an associated failure rate or mean time between failure value. Correction factors can be defined for eg, the following situations:
Comment
Note: CorrectionFactor special recommendations: A CorrectionFactor is always dependent upon eg, operational environment or location within a Product. This condition must be made explicit by the assignment of an ApplicabilityStatement. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Customer
Chapter
19
Paragraph
4.1.3.8
Units of Functionality Diagrams
X
Customer
Description
The Customer interface is implemented by classes that can play the role of a Customer.
Units of Functionality
Class (Element)
Damage
Chapter
19
Paragraph
4.13.4.5
Short Name
dmg
Units of Functionality Diagrams
X
X
X
X
Damage
Description
Damage defines the loss or reduction of functionality caused by a special event (induced failure).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
DamageAnalysisItem
Chapter
19
Paragraph
4.12.3.1
Units of Functionality Diagrams
X
Damage Analysis Item
Description
The DamageAnalysisItem interface is implemented by classes that represent hardware items.
Units of Functionality
Class (Element)
DataModuleScope
Chapter
19
Paragraph
4.14.3.7
Short Name
dm
Units of Functionality Diagrams
X
X
Data Module Scope
Description
The DataModuleScope relationship class defines associations between instances of S1000DDataModuleIssue and the TaskRevisions which are documented in the data module (completely or partially).
Comment
Note: There is one instance of DataModuleScope per combination of S1000DDataModuleIssue and TaskRevision.
Element Properties
Class (Element)
DatedApplicabilityStatement
Chapter
19
Paragraph
4.22.3.8
Short Name
datedApplicDef
Units of Functionality Diagrams
X
Dated Applicability Statement
Description
The DatedApplicabilityStatement class is a specialization of class ApplicabilityStatement, and defines applicability statements where the applicability is not just defined by the expression to be evaluated, but is also limited in time.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
DatedClassification
Chapter
19
Paragraph
4.21.4.91
Units of Functionality Diagrams
X
Dated Classification
Description
The DatedClassification compoundAttribute is used to represent classifications where the date when the classification was done is as important as the classification itself.
Attribute Properties
Units of Functionality
Class (Element)
DateTimeType
Class (Element)
DateType
Date Type
Description
The DateType primitive is used to represent calendar dates.
Comment
Note: All DateType attributes are defined as integers. The rules for how to populate the respective value are defined in the data elements list.
Note: The DateType primitive does not include any predefined format, eg, 23/10/08 or 2008-10 23. Date format is avoided in order to simplify data exchange.
Attribute Properties
Class (Element)
DescriptorType
Chapter
19
Paragraph
4.22.4.46
Units of Functionality Diagrams
X
Descriptor Type
Description
The DescriptorType primitive is used to represent any form of textual information (free form).
Comment
Note: The descriptor attribute must allow for text in an indentured manner. The descriptorProvidedBy attribute identifies the organization that provided the textual information. The descriptorProvidedDate identifies the date when the information was provided.
Note: The DescriptorType attributes descriptorLanguage, descriptorProvidedBy and descriptorProvidedDate enables eg, multiple descriptions to be provided for different purposes for the same object, and still be distinguished by organization and date.
Note: Assignment of ApplicabilityStatements to instances of DescriptorType enables multiple descriptive texts to be given for a single attribute in the data model, where multiple descriptions are allowed, and still distinguish when a single descriptive text is applicable.
Attribute Properties
Units of Functionality
Class (Element)
DetectionMeanAlarm
Chapter
19
Paragraph
4.11.3.12
Short Name
alarm
Units of Functionality Diagrams
X
X
X
Detection Mean Alarm
Description
The DetectionMeanAlarm class supports the definition and description of alarms being implemented by a specific detection mean.
Comment
Note: An instance of class DetectionMeanAlarm has no meaning by itself, but only in the context of a specific DetectionMeanCapability.
Attribute Properties
Element Properties
Class (Element)
DetectionMeanCapability
Chapter
19
Paragraph
4.11.3.11
Short Name
detectMnCap
Units of Functionality Diagrams
X
X
Detection Mean Capability
Description
The DetectionMeanCapability class supports the definition and description of the detection mean capabilities realized by a specific hardware item.
Comment
Note: An instance of class DetectionMeanCapability has no meaning by itself, but only in the context of a specific hardware item (HardwarePartAsDesigned or HardwareElementRevision).
Attribute Properties
Element Properties
Class (Element)
DetectionMeanItem
Chapter
19
Paragraph
4.11.3.10
Units of Functionality Diagrams
X
Detection Mean Item
Description
The DetectionMeanItem interface is implemented by those classes whose instances can be used for the detection and/or localization of one or many failure modes.
Element Properties
Units of Functionality
Class (Element)
DirectMaintenanceCost
Chapter
19
Paragraph
4.9.3.10
Short Name
cost
Units of Functionality Diagrams
X
Direct Maintenance Cost
Description
The DirectMaintenanceCost attributeGroup is a specialization of KeyPerformanceIndicator, and represents costs which include the shop maintenance man-hours, shop test man-hours, repair cost (incl. required material). Statistical values which represent the occurrence rate like Mean Time Between Failure (MTBF) and Mean Time Between Unscheduled Removal (MTBUR) must be considered for that cost element.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of DirectMaintenanceCost has multiple directMaintenanceCost values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first
Note: DirectMaintenanceCost special recommendations:
- An LSACandidate can have multiple direct maintenance cost values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of the directMaintenanceCost (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple direct maintenance cost values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ direct maintenance cost value, and one ‘actual’ direct maintenance cost value. These values must be distinguished using the valueDetermination attribute for the respective instance of directMaintenanceCost.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
DiscreteTimeLimit
Chapter
19
Paragraph
4.16.3.13
Short Name
condTl
Units of Functionality Diagrams
X
Discrete Time Limit
Description
The DiscreteTimeLimit class is a specialization of the TimeLimit class, and is used to identify limits that are distinct from each other, ie, there is no scheduled next occurrence for the associated task.
Comment
Note: An instance of class DiscreteTimeLimit has no meaning by itself, but only in the context of a specific instance of PlannedTaskTarget or TaskRequirementTarget.
Note: DiscreteTimeLimit need not contain a computable expression, ie, it can just contain a timeLimitDescription without any computable triggers or thresholds.
Note: The threshold association defines a specified interval, from a defined event, to the next required performance of the PlannedTaskTarget. The defined event is identified by the trigger association.
Note: The trigger association describes the event to which the threshold is related, eg, bird strike or engine replacement. If the DiscreteTimeLimit does not define any trigger association, it must be assumed that the trigger event equals the hardwarePartMaintenanceStart defined for HardwarePart in UoF Part Definition. The trigger activates the threshold.
Note: Multiple instances of ThresholdDefinitions for both the trigger and the threshold association mean ‘whichever is reached first’. DiscreteTimeLimit special recommendations: - Where an instance of DiscreteTimeLimit is dependent upon eg, external conditions or customer, it must be distinguished by the assignment of an ApplicabilityStatement to the DiscreteTimeLimit instance. Refer to Para 4.22.
Note: The DiscreteTimeLimit can be used to define ::Q::Perform once::Q:: and ::Q::On condition::Q:: time limits as defined in S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Document
Chapter
19
Paragraph
4.15.4.3
Units of Functionality Diagrams
X
X
X
X
Document
Description
The Document class represents documents which are of relevance for the LSA program.
Comment
Note: Document is an abstract class, ie, an instantiation of Document must be either an S1000DDataModule, an S1000DPublicationModule, or an ExternalDocument.
Element Properties
Units of Functionality
Class (Element)
DocumentAssignment
Chapter
19
Paragraph
4.20.3.11
Short Name
doc
Units of Functionality Diagrams
X
X
X
Document Assignment
Description
The DocumentAssignment relationship class defines a relationship between a specific Document or DocumentIssue and an instance of any class that implements the DocumentAssignmentItem interface.
Comment
Note: The role of the document being assigned is determined by the documentAssignmentRole attribute.
Note: The documentPortion attribute identifies a defined portion of a document which is of interest in a specific usage.
Note: There is one instance of DocumentAssignment per relevant combination of Document or DocumentIssue and instance to which the Document or DocumentIssue is assigned.
Note: DocumentAssignment special recommendations: - Where an instance of DocumentAssignment is dependent upon eg, customer, it must be distinguished by the assignment of an ApplicabilityStatement to the DocumentAssignment instance. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
DocumentAssignmentItem
Chapter
19
Paragraph
4.20.3.9
Units of Functionality Diagrams
X
Document Assignment Item
Description
The DocumentAssignmentItem interface is implemented by classes that can be associated with additional document information.
Comment
Note: Documents can also be assigned to any class that is a subclass of the enumerated classes, eg, to a RectifyingTask which is a subclass of Task.
Units of Functionality
Class (Element)
DocumentIssue
Chapter
19
Paragraph
4.20.3.2
Units of Functionality Diagrams
X
X
Document Issue
Description
The DocumentIssue class represents a specific document issue which is of relevance for the LSA program.
Comment
Note: DocumentIssue is an abstract class, ie, an instantiation of DocumentIssue must be either an S1000DDataModuleIssue, an S1000DPublicationModuleIssue, or an ExternalDocumentIssue.
Element Properties
Class (Element)
DocumentItem
Paragraph
4.20.3.10
Units of Functionality Diagrams
X
Document Item
Description
The DocumentItem interface is implemented by classes that represent documents.
Units of Functionality
Class (Element)
DownTime
Chapter
19
Paragraph
4.9.3.6
Short Name
time
Units of Functionality Diagrams
X
Down Time
Description
The DownTime attributeGroup is a specialization of KeyPerformanceIndicator, and represents the acceptable mean down time, where mean down time is the time where an item is non-operational.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of DownTime has multiple downTime values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: DownTime special recommendations:
- An LSACandidate can have multiple down time values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of downTime (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple down time values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ down time value, and one ‘actual’ down time value. These values must be distinguished using the valueDetermination attribute for the respective instance of downtime.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
EventThresholdDefinition
Units of Functionality Diagrams
X
Event Threshold Definition
Description
The EventThresholdDefinition class is a specialization of class ThresholdDefinition and is used to represent the number of occurrences of an explicit event that constitutes a threshold or trigger.
Comment
Note: An instance of class EventThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger
Note: EventThresholdDefinition is an abstract class, ie, an instantiation of EventThresholdDefinition must be either a TaskThresholdDefinition, a SpecialEventThresholdDefinition or a FailureModeThresholdDefinition.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ExternalDocument
Chapter
19
Paragraph
4.20.3.7
Short Name
extDoc
Units of Functionality Diagrams
X
External Document
Description
The ExternalDocument class is a specialization of class Document, and represents all documents that are not identified and produced in accordance with S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ExternalDocumentIssue
Chapter
19
Paragraph
4.20.3.8
Short Name
docIss
Units of Functionality Diagrams
X
External Document Issue
Description
The ExternalDocumentIssue class is a specialization of the DocumentIssue class, and represents specific issues of documents that are not identified and produced in accordance with S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FacilityResourceSpecification
Chapter
19
Paragraph
4.15.3.13
Short Name
facResSpec
Units of Functionality Diagrams
X
Facility Resource Specification
Description
The FacilityResourceSpecification class is a specialization of ResourceSpecification, and identifies specifications of facility resources (eg, power, internet, hangar, dock) which can be realized by one or many HardwarePartAsDesigned.
Comment
Note: Use of FacilityResourceSpecifications allows for more generic task/subtask definitions, ie, the task/subtask does not need to be changed based on customer specific realizations of facilities.
Note: FacilityResourceSpecification special recommendations: See special recommendations for ResourceSpecification, Para 4.15.3.8
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailureAnalysisItem
Chapter
19
Paragraph
4.11.3.1
Units of Functionality Diagrams
X
Failure Analysis Item
Description
The FailureAnalysisItem interface is implemented by classes that represent hardware items.
Element Properties
Units of Functionality
Class (Element)
FailureMode
Chapter
19
Paragraph
4.11.3.2
Units of Functionality Diagrams
X
X
X
X
X
X
Failure Mode
Description
The FailureMode class supports the definition of possible failure modes for a specific hardware item.
Comment
Note: An instance of class FailureMode has no meaning by itself, but only in the context of a hardware item (FailureAnalysisItem).
Note: The FailureMode class is an abstract class, ie, the class itself will never be instantiated but any of its subclasses can. Subclasses of FailureMode are: TechnicalFailureMode LSAFailureMode.
Note: The failureModeDetectionAbilityRating and failureModeLocalizationAbilityRating attributes are both of data type DatedClassification, ie, both ratings must have an associated date representing the date when the rating was performed.
Note: FailureMode special recommendations: The failureModeFailureRate attribute can have multiple failure rate values, eg, depending on operational environment. These must be distinguished by the assignment of ApplicabilityStatement to the instances of failureModeFailureRate value (ie, the instances of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailureModeDetection
Chapter
19
Paragraph
4.11.3.13
Short Name
fmDetect
Units of Functionality Diagrams
X
Failure Mode Detection
Description
The FailureModeDetection relationship class defines an association between an instance of DetectionMeanAlarm and an instance of FailureMode which can be observed, detected and/or localized by the detection mean alarm.
Comment
Note: There is one instance of FailureModeDetection per combination of DetectionMeanAlarm and FailureMode.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailureModeEffect
Chapter
19
Paragraph
4.11.3.7
Units of Functionality Diagrams
X
X
X
X
Failure Mode Effect
Description
The FailureModeEffect class defines the consequences of an identified failure mode and its effect on the local/next higher/end item operation, function, or status.
Comment
Note: An instance of class FailureModeEffect has no meaning by itself, but only in the context of an identified FailureMode.
Note: The FailureModeEffect class is an abstract class, ie, an instantiation of FailureModeEffect must be done using any of its specializations: LocalFailureModeEffect HigherFailureModeEffect
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailureModeThresholdDefinition
Short Name
fmThld
Units of Functionality Diagrams
X
Failure Mode Threshold Definition
Description
The FailureModeThresholdDefinition class is a specialization of class EventThresholdDefinition. FailureModeThresholdDefinition is used to represent the number of occurrences of a specific FailureMode (UoF LSA FMEA) that constitutes the threshold or trigger. Refer to Para 4.11.
Comment
Note: An instance of class FailureModeThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailureRate
Chapter
19
Paragraph
4.9.3.16
Short Name
rate
Units of Functionality Diagrams
X
Failure Rate
Description
The FailureRate attributeGroup is a specialization of KeyPerformanceIndicator, where the failure rate is the total number of failures within a population of an LSA Candidate item divided by the total functional life of the population during the measurement interval. The definition holds for time, rounds, miles, cycles or other measures of life units.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of FailureRate has multiple failureRate values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: FailureRate special recommendations:
- An LSACandidate can have multiple failure rate values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instances of failureRate (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple failure rate values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ failure rate value, and one ‘actual’ failure rate value. These values must be distinguished using the valueDetermination attribute for the respective instance of failureRate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FailuresPerOperatingHour
Chapter
19
Paragraph
4.9.3.12
Short Name
nr
Units of Functionality Diagrams
X
Failures Per Operating Hour
Description
The FailuresPerOperatingHour attributeGroup is a specialization of KeyPerformanceIndicator, and represents the failure rate, expressed in failures per operating hour. The FailuresPerOperatingHour defines a specified value which will be the maximum acceptable failure behavior of a component.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of FailuresPerOperatingHour has multiple failuresPerOperatingHour values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: FailuresPerOperatingHour special recommendations:
- An LSACandidate can have multiple failures per operating hour values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instances of failuresPerOperatingHour (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple failures per operating hour values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ failures per operating hour value, and one ‘actual’ failures per operating hour value. These values must be distinguished using the valueDetermination attribute for the respective instance of failuresPerOperatingHour.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
FunctionalFailure
Chapter
19
Paragraph
4.13.3.10
Short Name
funcFail
Units of Functionality Diagrams
X
Functional Failure
Description
The FunctionalFailure class documents functional failures identified during Preventive Maintenance Analysis (PMA).
Comment
Note: Functional failures can also be identified based on the outcome of Scheduled Maintenance Analysis (SMA) or Reliability Centered Maintenance (RCM).
Note: There is one instance of TaskRequirementTarget per combination of TaskRequirement and LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
HardwareElement
Chapter
19
Paragraph
4.5.3.1
Short Name
beHw
Units of Functionality Diagrams
X
X
Hardware Element
Description
The HardwareElement class is a specialization of the BreakdownElement class, and represents a specification that is realized as hardware parts (often referred to as equipment).
Comment
Note: Wherever the BreakdownElement class is used in the data model, HardwareElement can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
HardwareElementPartRealization
Chapter
19
Paragraph
4.5.3.3
Short Name
hwPart
Units of Functionality Diagrams
X
X
X
X
X
Hardware Element Part Realization
Description
The HardwareElementPartRealization relationship class defines an association between an instance of HardwareElementRevision and the HardwarePartAsDesigned which fulfills the hardware element specification.
Comment
Note: There is one instance of HardwareElementPartRealization per combination of HardwareElementRevision and HardwarePartAsDesigned. HardwareElementPartRealization special recommendations: - Where an instance of HardwareElementPartRealization is dependent upon product variant or allowed product design configuration, it must be defined by the assignment of ItemInProductVariant or ItemInAllowedProductConfiguration to the instance of HardwareElementPartRealization under consideration. Refer to Para 4.8.
Element Properties
Units of Functionality
Class (Element)
HardwareElementRevision
Chapter
19
Paragraph
4.5.3.2
Short Name
beRev
Units of Functionality Diagrams
X
X
X
Hardware Element Revision
Description
The HardwareElementRevision class is a specialization of the BreakdownElementRevision class, and represents a design iteration that is applied to a HardwareElement.
Comment
Note: Wherever the BreakdownElementRevision class is used in the data model, HardwareElementRevision can be used instead (the rule of substitutability).
Note: HardwareElementRevision special recommendations:
- A HardwareElementRevision can have multiple replaceability strategies (ie, values of the attribute hardwareElementFunctionalReplaceabilityStrategy). Each replaceability strategy value (ie, instance of ClassificationType) must then have an associated ApplicabilityStatement as defined in the UoF Applicability Statement, in order to define when the respective replaceability strategy is applicable.
- A HardwareElementRevision can have multiple reparability strategies (ie, values of the hardwareElementRepairabilityStrategy attribute). Each hardwareElementRepairabilityStrategy value (ie, instance of ClassificationType) must then have an associated ApplicabilityStatement as defined in UoF Applicability Statement, in order to define when respective hardwareElementRepairabilityStrategy is applicable.
Attribute Properties
breakdownElementRevisionIdentifier
breakdownElementRevisionCreationDate
breakdownElementRevisionStatus
maintenanceSignificantOrRelevant
hardwareElementStructuralIndicator
hardwareElementFunctionalReplaceability
hardwareElementFunctionalReplaceabilityStrategy
hardwareElementRepairability
hardwareElementRepairabilityStrategy
Element Properties
Units of Functionality
Class (Element)
HardwarePartAsDesigned
Chapter
19
Paragraph
4.4.3.6
Short Name
hwPart
Units of Functionality Diagrams
X
X
X
X
X
Hardware Part As Designed
Description
The HardwarePartAsDesigned class is a specialization of class PartAsDesigned, and represents parts that will be realized as physical items (hardware), including non-countable material.
Comment
Note: HardwarePartAsDesignedDesignData (attributeGroup) is the definitional information which defines characteristics for the HardwarePartAsDesigned identified during the design activities.
Note: HardwarePartAsDesignedSupportData (attributeGroup) is the definitional information which defines characteristics for the HardwarePartAsDesigned identified during the supportability analysis activities.
Note: HardwarePartAsDesignedControlledItemData (attributeGroup) is the definitional information which defines characteristics for the HardwarePartAsDesigned identified during different control analysis activities.
Note: A HardwarePartAsDesigned can have more than one hardwarePartWasteProductsInUseDisposalDescription and/or hardwarePartWasteProductsPlannedDisposalDescription. This will most likely reflect changes in part waste products disposal descriptions over time.
Note: A HardwarePartAsDesigned can have more than one hardwarePartEnvironmentalAspectInUseClass and/or hardwarePartEnvironmentalAspectPlannedDisposalClass classification. This will most likely reflect changes in hardware part environmental aspects over time.
Note: HardwarePartAsDesigned special recommendations:
- A HardwarePartAsDesigned can have multiple reparability strategies (ie, values for hardwarePartRepairabilityStrategy). Each hardwarePartRepairabilityStrategy value (ie, instance of the ClassificationType data type) must then have an associated ApplicabilityStatement, as defined in the UoF Applicability Statement, in order to define when respective reparability strategy is applicable. The applicability statement will in most cases include Operator as one of the parameters to be evaluated.
- A HardwarePartAsDesigned can have multiple consumption rates (ie, values for hardwarePartConsumptionRate). Each hardwarePartConsumptionRate value (ie, instance of the PropertyType data type) must then have an associated ApplicabilityStatement, as defined in the UoF Applicability Statement, in order to define when respective consumption rate is applicable. The applicability statement will in most cases include HardwareElementPartRealization, ie, usage, as one of the parameters to be evaluated.
Attribute Properties
HardwarePartAsDesigned
partIdentifier
partName
HardwarePartAsDesignedDesignData
partSpecialHandlingRequirement
PartAsDesignedDesignData
hardwarePartOperationalAuthorizedLife
hardwarePartHazardousClass
hardwarePartFitmentRequirement
hardwarePartElectromagneticIncompatible
hardwarePartElectrostaticSensitive
hardwarePartElectromagneticSensitive
hardwarePartMagneticSensitive
hardwarePartRadiationSensitive
HardwarePartAsDesignedSupportData
partMaturityClass
partObsolescenceRiskAssessment
hardwarePartLogisticsCategory
hardwarePartRepairability
hardwarePartRepairabilityStrategy
hardwarePartMaintenanceStart
hardwarePartWasteProductsInUseDisposalDescription
hardwarePartWasteProductsPlannedDisposalDescription
hardwarePartEnvironmentalAspectInUseClass
hardwarePartEnvironmentalAspectPlannedDisposalClass
hardwarePartScrapRate
hardwarePartConsumptionRate
HardwarePartAsDesignedControlledItemData
partDemilitarizationClass
Element Properties
Units of Functionality
Class (Element)
HardwarePartAsDesignedDesignData
Hardware Part As Designed Design Data
Description
No Description
Class (Element)
HardwarePartAsDesignedSupportData
Hardware Part As Designed Support Data
Description
No Description
Attribute Properties
hardwarePartLogisticsCategory
hardwarePartRepairability
hardwarePartRepairabilityStrategy
hardwarePartMaintenanceStart
hardwarePartWasteProductsInUseDisposalDescription
hardwarePartWasteProductsPlannedDisposalDescription
hardwarePartEnvironmentalAspectInUseClass
hardwarePartEnvironmentalAspectPlannedDisposalClass
hardwarePartScrapRate
hardwarePartConsumptionRate
Class (Element)
HigherFailureModeEffect
Chapter
19
Paragraph
4.11.3.9
Short Name
hghrEfct
Units of Functionality Diagrams
X
Higher Failure Mode Effect
Description
The HigherFailureModeEffect class is a specialization of FailureModeEffect, and identifies the consequences of each failure/damage mode affecting the next higher indenture level, or the essential functions affecting system/equipment operating capability and mission completion capability.
Comment
Note: An instance of class HigherFailureModeEffect has no meaning by itself, but only in the context of an identified FailureMode.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
IdentifierType
Identifier Type
Description
The IdentifierType primitive is used to represent any form of identification.
Comment
Note: The identifierSetBy relates to an Organization as the data type. The Organization class is defined in UoF Project, and contains an organizationIdentifier (mandatory) and an organizationName (optional).
Attribute Properties
Class (Element)
InitialTimeLimit
Short Name
initial
Units of Functionality Diagrams
X
Initial Time Limit
Description
The InitialTimeLimit class defines a specific interval for the first scheduled performance of a periodic task.
Comment
Note: An instance of class InitialTimeLimit has no meaning by itself, but only in the context of a specific PeriodicTimeLimit.
Note: The threshold association defines a specified interval for the first performance of the associated RectifyingTask or OperationalTask.
Note: Multiple instances of ThresholdDefinition for the threshold association mean “whichever is reached first”.
Element Properties
Units of Functionality
Class (Element)
ItemInAllowedProductConfiguration
Chapter
19
Paragraph
4.8.3.9
Short Name
apcEfy
Units of Functionality Diagrams
X
X
X
Item In Allowed Product Configuration
Description
The ItemInAllowedProductConfiguration relationship class defines an association between a resolved configuration and a definition of the parts that is allowed to be installed on serialized Products that confirms with the resolved AllowedProductConfiguration.
Comment
Note: There is one instance of ItemInAllowedProductConfiguration per relevant combination of resolvedConfiguration and includedItem.
Element Properties
Units of Functionality
Class (Element)
ItemInProductVariant
Chapter
19
Paragraph
4.8.3.1
Short Name
usableOn
Units of Functionality Diagrams
X
X
Item In Product Variant
Description
The ItemInProductVariant relationship class defines that the applicability of a breakdown element or specific realization thereof is limited to a specific product variant.
Comment
Note: ItemInProductVariant can be used for representing GEIA-STD-0007 System/End Item Usable On Codes.
Note: Instances of BreakdownElementUsageInBreakdown without any associated ItemInProductVariant means that the usage of the associated BreakdownElementRevision is valid for all ProductVariants.
Note: There must be one instance of ItemInProductVariant per permitted combination of ProductVariant and BreakdownElementUsageInBreakdown, HardwareElementPartRealization and SoftwareElementPartRealization, respectively.
Element Properties
Units of Functionality
Class (Element)
KeyPerformanceIndicator
Chapter
19
Paragraph
4.9.3.2
Units of Functionality Diagrams
X
X
X
X
X
Key Performance Indicator
Description
The KeyPerformanceIndicator attributeGroup defines eg, customer or user specific values per LSACandidate. The value for a given key performance indicator can be defined as being eg, specified, contracted, allocated, distributed or actual, using the valueDetermination attribute for the respective key performance value (valueDetermination is an attribute of the PropertyType primitive).
Comment
Note: Requirements are often stated as product design and performance data in the contract.
Note: Key performance indicators can be defined for LSA Candidates at any level of indenture.
Note: An instance of class KeyPerformanceIndicator has no meaning by itself, but only in the context of a specific LSACandidate.
Note: KeyPerformanceIndicator attributeGroup is an abstract class, ie, an instantiation of KeyPerformanceIndicator must be done using any of its specializations: ProductServiceLife ScheduledMaintenanceInterval MaintenanceFreeOperatingPeriod DownTime MaintenanceManHoursPerOperatingHour MeanTimeBetweenUnscheduledRemoval MeanTimeToRepair DirectMaintenanceCost ShopProcessingTime FailuresPerOperatingHour ReplacementTime LifeCycleCost MeanTimeBetweenFailure FailureRate
Note: The KeyPerformanceIndicator class does not contain any key performance indicator values. These are contained within the respective subclass of KeyPerformanceIndicator, eg, ProductServiceLife.
Note: KeyPerformanceIndicator special recommendations: Where an instance of KeyPerformanceIndicator is dependent upon eg, operator or operational environment, it must be distinguished by the assignment of an ApplicabilityStatement to the KeyPerformanceIndicator. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LifeCycleCost
Chapter
19
Paragraph
4.9.3.14
Short Name
cost
Units of Functionality Diagrams
X
Life Cycle Cost
Description
The LifeCycleCost attributeGroup is a specialization of KeyPerformanceIndicator, and represents the total calculated cost for an LSA Candidate throughout its planned life.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of LifeCycleCost has multiple lifeCycleCost values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: LifeCycleCost special recommendations:
- An LSACandidate can have multiple life cycle cost values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of lifeCycleCost (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple life cycle cost values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ life cycle cost value, and one ‘actual’ life cycle cost value. These values must be distinguished using the valueDetermination attribute for the respective instance of lifeCycleCost.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LocalFailureModeEffect
Chapter
19
Paragraph
4.11.3.8
Short Name
lclEfct
Units of Functionality Diagrams
X
Local Failure Mode Effect
Description
The LocalFailureModeEffect class is a specialization of FailureModeEffect, and identifies the consequences of each postulated failure/damage mode affecting the hardware item (HardwarePart or HardwareElementRevision) under analysis. It is possible for the local effect to be the failure mode itself.
Comment
Note: An instance of class LocalFailureModeEffect has no meaning by itself, but only in the context of an identified FailureMode.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LogicalOperator
Units of Functionality Diagrams
X
Logical Operator
Description
The LogicalOperator class defines the logical expression to be evaluated.
Comment
Note: LogicalOperator is an abstract class, ie, an instantiation of LogicalOperator must always be done using any of its specializations AND, OR or NOT.
Element Properties
Units of Functionality
Class (Element)
LSACandidate
Chapter
19
Paragraph
4.9.3.1
Units of Functionality Diagrams
X
X
X
X
X
LSA Candidate
Description
The LSACandidate interface is implemented by classes that can be selected as LSA Candidates.
Comment
Note: An associated KeyPerformanceIndicator must be of any its specializations (eg, MeanTimeBetweenFailure, DownTime).
Note: An LSACandidate can have more than one LSACandidateMaintenanceConcept and LSACandidateMaintenanceSolution description, respectively. The validity of the respective description can be determined by the assignment of ApplicabilityStatements. Refer to Para 4.22.
Note: Only those instances of BreakdownElementRevision and PartAsDesigned (ie, instances of those classes that implement the LSACandidate interface) that are selected as LSA Candidates must identify analysis activities to be performed.
Note: Since the LSACandidate interface must be implemented by BreakdownElementRevision and PartAsDesigned respectively, it means that instances of the following classes can be selected as LSA Candidates:
- HardwareElementRevision
- SoftwareElementRevision
- AggregatedElementRevision
- ZoneElementRevision
- HardwarePartAsDesigned
- SoftwarePartAsDesigned
Attribute Properties
Units of Functionality
Class (Element)
LSACandidateComparativeAnalysisActivity
Chapter
19
Paragraph
4.10.3.2
Short Name
comp
Units of Functionality Diagrams
X
LSA Candidate Comparative Analysis Activity
Description
The LSACandidateComparativeAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding comparative analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateComparativeAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateDamageAnalysisActivity
Chapter
19
Paragraph
4.10.3.8
Short Name
dmg
Units of Functionality Diagrams
X
LSA Candidate Damage Analysis Activity
Description
The LSACandidateDamageAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding damage analysis for the LSA Candidate under consideration.
Comment
Note: An instance of LSACandidateDamageAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateFailureModeAndEffectAnalysisActivity
Chapter
19
Paragraph
4.10.3.7
Short Name
fmea
Units of Functionality Diagrams
X
LSA Candidate Failure Mode And Effect Analysis Activity
Description
The LSACandidateFailureModeAndEffectAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding failure mode and effect analysis (LSA FMEA) for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateFailureModeAndEffectAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateHumanFactorAnalysisActivity
Chapter
19
Paragraph
4.10.3.3
Short Name
hf
Units of Functionality Diagrams
X
LSA Candidate Human Factor Analysis Activity
Description
The LSACandidateHumanFactorAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding human factor analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateHumanFactorAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateLevelOfRepairAnalysisActivity
Chapter
19
Paragraph
4.10.3.10
Short Name
lora
Units of Functionality Diagrams
X
LSA Candidate Level Of Repair Analysis Activity
Description
The LSACandidateLevelOfRepairAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding level of repair analysis (LORA) for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateLevelOfRepairAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateMaintainabilityAnalysisActivity
Chapter
19
Paragraph
4.10.3.5
Short Name
mntnblty
Units of Functionality Diagrams
X
LSA Candidate Maintainability Analysis Activity
Description
The LSACandidateMaintainabilityAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding maintainability analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateMaintainabilityAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateMaintenanceTaskAnalysisActivity
Chapter
19
Paragraph
4.10.3.11
Short Name
mta
Units of Functionality Diagrams
X
LSA Candidate Maintenance Task Analysis Activity
Description
The LSACandidateMaintenanceTaskAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding maintenance task analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateMaintenanceTaskAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateOperationalAnalysisActivity
Chapter
19
Paragraph
4.10.3.14
Short Name
opa
Units of Functionality Diagrams
X
LSA Candidate Operational Analysis Activity
Description
The LSACandidateOperationalAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding operational analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateOperationalAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateOtherAnalysisActivity
Chapter
19
Paragraph
4.10.3.17
Short Name
other
Units of Functionality Diagrams
X
LSA Candidate Other Analysis Activity
Description
The LSACandidateOtherAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding additional types of analysis activities that needs to be performed for the LSA Candidate under consideration, apart from those defined in Para 4.10.3.1 to Para 4.10.3.16.
Comment
Note: An instance of class LSACandidateOtherAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateReliabilityAnalysisActivity
Chapter
19
Paragraph
4.10.3.4
Short Name
rlbty
Units of Functionality Diagrams
X
LSA Candidate Reliability Analysis Activity
Description
The LSACandidateReliabilityAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding reliability analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateReliabilityAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateSimulationOperationalScenariosAnalysisActivity
Chapter
19
Paragraph
4.10.3.15
Short Name
simOp
Units of Functionality Diagrams
X
LSA Candidate Simulation Operational Scenarios Analysis Activity
Description
The LSACandidateSimulationOperationalScenariosAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding simulation of operational scenarios for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateSimulationOperationalScenariosAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateSoftwareDataLoadingAnalysisActivity
Chapter
19
Paragraph
4.10.3.12
Short Name
sdl
Units of Functionality Diagrams
X
LSA Candidate Software Data Loading Analysis Activity
Description
The LSACandidateSoftwareDataLoadingAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding software data loading analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateSoftwareDataLoadingAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateSoftwareSupportAnalysisActivity
Chapter
19
Paragraph
4.10.3.13
Short Name
ssa
Units of Functionality Diagrams
X
LSA Candidate Software Support Analysis Activity
Description
The LSACandidateSoftwareSupportAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding software support analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateSoftwareSupportAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateSpecialEventAnalysisActivity
Chapter
19
Paragraph
4.10.3.9
Short Name
sEvnt
Units of Functionality Diagrams
X
LSA Candidate Special Event Analysis Activity
Description
The LSACandidateSpecialEventAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding special events analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateSpecialEventAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateTechnologyBehaviourRating
Chapter
19
Paragraph
4.12.3.2
Units of Functionality Diagrams
X
X
X
LSA Candidate Technology Behaviour Rating
Description
The LSACandidateTechnologyBehaviourRating attributeGroup describes technologies used and its characteristics regarding knowledge of its behavior.
Comment
Note: An instance of class LSACandidateTechnologyBehaviourRating has no meaning by itself, but only in the context of a hardware item.
Note: Both the technologyBehaviourKnowledgeRating and the technologySensitivityRating attributes are of data type DatedClassification, ie, both ratings must have an associated date defining the date when the rating was performed. A hardware item can also have multiple ratings over time.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateTestabilityAnalysisActivity
Chapter
19
Paragraph
4.10.3.6
Short Name
tstblty
Units of Functionality Diagrams
X
LSA Candidate Testability Analysis Activity
Description
The LSACandidateTestabilityAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding testability analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateTestabilityAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSACandidateTrainingNeedsAnalysisActivity
Chapter
19
Paragraph
4.10.3.16
Short Name
tna
Units of Functionality Diagrams
X
LSA Candidate Training Needs Analysis Activity
Description
The LSACandidateTrainingNeedsAnalysisActivity class is a specialization of CandidateItemAnalysisActivity, and records the decision made regarding training needs analysis for the LSA Candidate under consideration.
Comment
Note: An instance of class LSACandidateTrainingNeedsAnalysisActivity has no meaning by itself, but only in the context of a specific LSACandidate.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSAFailureMode
Chapter
19
Paragraph
4.11.3.4
Short Name
lsaFm
Units of Functionality Diagrams
X
X
LSA Failure Mode
Description
The LSAFailureMode class is a specialization of FailureMode, and supports the grouping of identified technical failure modes which leads to the same combination of failure mode signature (troubleshooting) and maintenance procedure.
Comment
Note: An instance of class LSAFailureMode has no meaning by itself, but only in the context of a hardware item. The LSAFailureMode has two specializations which can be used to record the probability for an individual LSA failure mode to occur in relation to the entire population of LSA failure modes identified for the related hardware item (HardwarePartAsDesigned or HardwareElementRevision). These specializations are LSAFailureModeWithDistributionRatio and LSAFailureModeWithDistributionRating, respectively.
Note: The failureModeDetectionAbilityRating and failureModeLocalizationAbilityRating attributes are both of data type DatedClassification, ie, both ratings must have an associated date representing the date when the rating was performed.
Note: LSAFailureMode special recommendations: The failureModeFailureRate attribute can have multiple failure rate values, eg, depending on operational environment. These must be distinguished by the assignment of ApplicabilityStatement to the instances of failureModeFailureRate value (ie, the instances of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSAFailureModeWithDistributionRating
Chapter
19
Paragraph
4.11.3.6
Short Name
lsaFmRtg
Units of Functionality Diagrams
X
LSA Failure Mode With Distribution Rating
Description
The LSAFailureModeWithDistributionRating class is a specialization of LSAFailureMode, and records the rating for the occurrence of an individual LSA failure mode in relation to the entire population of LSA failure modes identified for the related hardware item (HardwarePartAsDesigned or HardwareElementRevision).
Comment
Note: An instance of class LSAFailureModeWithDistributionRating has no meaning by itself, but only in the context of a specific hardware item.
Note: The failureModeDetectionAbilityRating and failureModeLocalizationAbilityRating attributes are both of data type DatedClassification, ie, both ratings must have an associated date representing the date when the rating was performed.
Note: LSAFailureModeWithDistributionRating special recommendations:
- The failureModeFailureRate attribute must not be populated for an instance of LSAFailureModeWithDistributionRating
- The LSAFailureModeDistributionRating attribute can have multiple distribution rating values, eg, depending on operational environment. These must be distinguished by the assignment of ApplicabilityStatement to the instances of LSAFailureModeDistributionRating value (ie, the instances of ClassificationType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
LSAFailureModeWithDistributionRatio
Chapter
19
Paragraph
4.11.3.5
Short Name
lsaFmRo
Units of Functionality Diagrams
X
LSA Failure Mode With Distribution Ratio
Description
The LSAFailureModeWithDistributionRatio class is a specialization of LSAFailureMode, and records the ratio for an individual LSA failure mode to occur in relation to the entire population of LSA failure modes identified for the related hardware item (HardwarePartAsDesigned or HardwareElementRevision).
Comment
Note: An instance of class LSAFailureModeWithDistributionRatio has no meaning by itself, but only in the context of a specific hardware item.
Note: The failureModeDetectionAbilityRating and failureModeLocalizationAbilityRating attributes are both of data type DatedClassification, ie, both ratings must have an associated date representing the date when the rating was performed.
Note: The sum of distribution ratios applicable under the same conditions must always equal one for each item under analysis.
Note: LSAFailureModeWithDistributionRatio special recommendations:
- The failureModeFailureRate attribute must not be populated for an instance of LSAFailureModeWithDistributionRatio
- The LSAFailureModeDistributionRatio attribute can have multiple distribution ratio values, eg, depending on operational environment. These must be distinguished by the assignment of ApplicabilityStatement to the instances of LSAFailureModeDistributionRatio value (ie, the instances of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MaintenanceCapabilityAtOperatingLocationType
Chapter
19
Paragraph
4.2.3.8
Short Name
maintCap
Units of Functionality Diagrams
X
Maintenance Capability At Operating Location Type
Description
The MaintenanceCapabilityAtOperatingLocationType relationship class defines relationships in between an OperatingLocationType and maintenance capabilities in terms of MaintenanceLevels that will be available at the operating location type.
Comment
Note: There is one instance of MaintenanceCapabilityAtOperatingLocationType per relevant combination of OperatingLocationType and MaintenanceLevel.
Element Properties
Units of Functionality
Class (Element)
MaintenanceFreeOperatingPeriod
Chapter
19
Paragraph
4.9.3.5
Short Name
per
Units of Functionality Diagrams
X
Maintenance Free Operating Period
Description
The MaintenanceFreeOperatingPeriod attributeGroup is a specialization of KeyPerformanceIndicator, and represents the acceptable maintenance free operating period, where maintenance free operating period is the interval in which no maintenance actions occur.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of MaintenanceFreeOperatingPeriod has multiple maintenanceFreeOperatingPeriod values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: MaintenanceFreeOperatingPeriod special recommendations:
- An LSACandidate can have multiple maintenance free operating period values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of maintenanceFreeOperatingPeriod (ie, to the respective instance of PropertyType. Refer to Para 4.22.
- An LSACandidate can have multiple maintenance free operating periods being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ maintenance free operating period value, and one ‘actual’ maintenance free operating period value. These values must be distinguished using the valueDetermination attribute for the respective instance of maintenanceFreeOperatingPeriod.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MaintenanceLevel
Chapter
19
Paragraph
4.2.3.2
Short Name
mlv
Units of Functionality Diagrams
X
X
X
X
X
Maintenance Level
Description
Maintenance activities can be structured into maintenance levels according to operator maintenance policy, and organization of maintenance means.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MaintenanceLocation
Chapter
19
Paragraph
4.2.3.3
Short Name
mLoc
Units of Functionality Diagrams
X
X
X
X
X
Maintenance Location
Description
The MaintenanceLocation class identifies actual locations where maintenance activities will be carried out.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MaintenanceManHoursPerOperatingHour
Chapter
19
Paragraph
4.9.3.7
Short Name
mh
Units of Functionality Diagrams
X
Maintenance Man Hours Per Operating Hour
Description
The MaintenanceManHoursPerOperatingHour attributeGroup is a specialization of KeyPerformanceIndicator, and represents the acceptable maintenance man hours per operating hour, where maintenance man hours per operating hour is the ratio of maintenance man-hours expended to the operating interval (as defined by the measurement base) of the system/equipment.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of MaintenanceManHoursPerOperatingHour has multiple maintenanceManHoursPerOperatingHour values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: MaintenanceManHoursPerOperatingHour special recommendations:
- An LSACandidate can have multiple maintenance man hours per operating hour values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of maintenanceManHoursPerOperatingHour (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple maintenance man hours per operating hour values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ maintenance man hours per operating hour value, and one ‘actual’ maintenance man hours per operating hour value. These values must be distinguished using the valueDetermination attribute for the respective instance of maintenanceManHoursPerOperatingHour.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MaterialResourceSpecification
Chapter
19
Paragraph
4.15.3.9
Short Name
mtrlResSpec
Units of Functionality Diagrams
X
Material Resource Specification
Description
The MaterialResourceSpecification class is a specialization of ResourceSpecification, and identifies specifications of material resources (eg, spares, consumables, tools) which can be realized by one or many HardwarePartAsDesigned.
Comment
Note: Use of MaterialResourceSpecifications allows for more generic task/subtask definitions, ie, the task/subtask does not need to be changed based on customer specific tool sets.
Note: MaterialResourceSpecification special recommendations: See special recommendations for ResourceSpecification, Para 4.15.3.8
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MeanTimeBetweenFailure
Chapter
19
Paragraph
4.9.3.15
Short Name
mt
Units of Functionality Diagrams
X
Mean Time Between Failure
Description
The MTBF attributeGroup is a specialization of KeyPerformanceIndicator, where the MTBF is the total operational life of a population of an LSA Candidate divided by the total number of failures within the population during a particular measurement interval. The definition holds for time, rounds, miles, events, or other measure of life units.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of MeanTimeBetweenFailure has multiple meanTimeBetweenFailure values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: MeanTimeBetweenFailure special recommendations:
- An LSACandidate can have multiple mean time between failure values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of meanTimeBetweenFailure (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple mean time between failure values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ mean time between failure value, and one ‘actual’ mean time between failure value. These values must be distinguished using the valueDetermination attribute for the respective instance of meanTimeBetweenFailure.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MeanTimeBetweenUnscheduledRemoval
Chapter
19
Paragraph
4.9.3.8
Short Name
mt
Units of Functionality Diagrams
X
Mean Time Between Unscheduled Removal
Description
The MeanTimeBetweenUnscheduledRemoval attributeGroup is a specialization of KeyPerformanceIndicator, and represents the total number of operational units (eg, miles, rounds, hours) divided by the total number of items removed from that system during a stated period of time. This term is defined to exclude removals as either being scheduled or performed in order to facilitate other maintenance and removals for product improvement.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of MeanTimeBetweenUnscheduledRemoval has multiple meanTimeBetweenUnscheduledRemoval values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: MeanTimeBetweenUnscheduledRemoval special recommendations:
- An LSACandidate can have multiple mean time between unscheduled removal values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of meanTimeBetweenUnscheduledRemoval value (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple mean time between unscheduled removal values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ mean time between unscheduled removal value and one ‘actual’ mean time between unscheduled removal value. These values must be distinguished using the valueDetermination attribute for the respective instance of meanTimeBetweenUnscheduledRemoval.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
MeanTimeToRepair
Chapter
19
Paragraph
4.9.3.9
Short Name
mt
Units of Functionality Diagrams
X
Mean Time To Repair
Description
The MeanTimeToRepair attributeGroup is a specialization of KeyPerformanceIndicator, and represents the total elapsed time for corrective maintenance divided by the total number of corrective maintenance actions during a given period of time.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of MeanTimeToRepair has multiple meanTimeToRepair values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: MeanTimeToRepair special recommendations:
- An LSACandidate can have multiple mean time to repair values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of meanTimeToRepair (ie, to the respective instance of PropertyType). Refer to Para 4.22.An LSACandidate can have multiple mean time to repair values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ mean time to repair value, and one ‘actual’ mean time to repair value. These values must be distinguished using the valueDetermination attribute for the respective instance of meanTimeToRepair.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
NestedAllowedProductConfigurationRelationship
Chapter
19
Paragraph
4.8.3.5
Short Name
nestedPC
Units of Functionality Diagrams
X
X
Nested Allowed Product Configuration Relationship
Description
The NestedAllowedProductConfigurationRelationship relationship class defines an association between a parent AllowedProductConfiguration and an AllowedProductConfiguration that is allowed to be included as part of the parent AllowedProductConfiguration.
Comment
Note: There is one instance of NestedAllowedProductConfigurationRelationship per parent-child relationship.
Element Properties
Units of Functionality
Class (Element)
NestedProductVariantRelationship
Chapter
19
Paragraph
4.8.3.3
Short Name
nestedPV
Units of Functionality Diagrams
X
X
Nested Product Variant Relationship
Description
The NestedProductVariantRelationship relationship class defines an association between a parent ProductVariant and a ProductVariant that is defined to be included as part of the parent ProductVariant.
Comment
Note: There is one instance of NestedProductVariantRelationship per parent-child relationship.
Element Properties
Units of Functionality
Class (Element)
NonConformanceData
Chapter
19
Paragraph
4.8.3.10
Units of Functionality Diagrams
X
Non Conformance Data
Description
The NonConformanceData attributeGroup defines attributes that must be provided if a specific part does not fully comply with the requirements of its usage in the resolved AllowedProductConfiguration.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
NOT
Short Name
not
Units of Functionality Diagrams
X
N O T
Description
The NOT class is a specialization of class LogicalOperator, and defines that the related ApplicabilityEvaluation needs to be FALSE in order for the overall ApplicabilityStatement to be TRUE.
Comment
Note: S1000D does not make explicit use of NOT statements in the definition of an applic element.
Element Properties
Units of Functionality
Class (Element)
NumericalPropertyType
Numerical Property Type
Description
The NumericalPropertyType primitive is used for representing numerical property values together with its associated unit of measure.
Comment
Note: The NumericalPropertyType class is an abstract class, ie, any of its subclasses must be used for the actual representation of a numerical property value. PropertyType subclasses: - SingleValuePropertyType (a property with a value and its UoM) - ValueWithTolerancesPropertyType (a property with a value, its unit of measure, along with acceptable upper and lower offset values) - ValueRangePropertyType (a property with no fixed value, but defined by upper and lower limits along with a unit of measure)
Attribute Properties
Class (Element)
OperatingLocation
Chapter
19
Paragraph
4.2.3.7
Short Name
opLoc
Units of Functionality Diagrams
X
X
X
X
X
Operating Location
Description
The OperatingLocation class defines the exact location where the contracted product variant will be operated.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
OperatingLocationType
Chapter
19
Paragraph
4.2.3.6
Short Name
opLocType
Units of Functionality Diagrams
X
X
X
X
X
Operating Location Type
Description
The OperatingLocationType class defines types of locations where the contracted product variant will be operated.
Comment
Note: The OperatingLocationType can be generic, ie, it does not need to define any specific characteristics, but just enables the recording of the number of contracted product variants and its operating requirements as defined within the ContractedProductVariantAtOperatingLocationType relationship class.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
OperationalTask
Chapter
19
Paragraph
4.14.3.4
Short Name
opTask
Units of Functionality Diagrams
X
Operational Task
Description
The OperationalTask class is a specialization of class Task.
Comment
Note: Operational tasks are tasks that are required for operational purposes, eg, fueling. An operational task may also be used as a subtask within one or many rectifying tasks.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Operator
Chapter
19
Paragraph
4.2.3.1
Units of Functionality Diagrams
X
Operator
Description
The Operator interface must be implemented by classes that can be responsible for operating and maintaining the contracted product variant.
Comment
Note: Each OperatingLocationType and OperatingLocation is uniquely defined for a specific Operator.
Units of Functionality
Class (Element)
OperatorMaintenanceLevel
Chapter
19
Paragraph
4.2.3.4
Short Name
opers
Units of Functionality Diagrams
X
Operator Maintenance Level
Description
The OperatorMaintenanceLevel relationship class defines relationships in between an Operator and the MaintenanceLevels which is part of the support solution for the contracted product variant.
Comment
Note: There is one instance of OperatorMaintenanceLevel per relevant combination of Operator and MaintenanceLevel.
Element Properties
Units of Functionality
Class (Element)
OperatorMaintenanceLocation
Chapter
19
Paragraph
4.2.3.5
Short Name
opers
Units of Functionality Diagrams
X
Operator Maintenance Location
Description
The OperatorMaintenanceLocation relationship class defines relationships in between an Operator and actual MaintenanceLocations which is part of the support solution for the contracted product variant.
Comment
Note: There is one instance of OperatorMaintenanceLocation per relevant combination of Operator and MaintenanceLocation.
Element Properties
Units of Functionality
Class (Element)
OR
Short Name
or
Units of Functionality Diagrams
X
O R
Description
The OR class is a specialization of class LogicalOperator, and defines a list of ApplicabilityEvaluations where at least one needs to be TRUE in order for the overall ApplicabilityStatement to be TRUE.
Comment
Note: S1000D does not use OR statements in the definition of an applic element.
Element Properties
Units of Functionality
Class (Element)
OrderedSubtaskCircuitBreakerSettings
Chapter
19
Paragraph
4.14.3.21
Short Name
ordCbSet
Units of Functionality Diagrams
X
Ordered Subtask Circuit Breaker Settings
Description
The OrderedSubtaskCircuitBreakerSettings class is a specialization of the SubtaskCircuitBreakerSettings class. OrderedSubtaskCircuitBreakerSettings must be used when the order in which individual circuit breakers are set are of importance.
Comment
Note: The ordered association with one or many instances of SubtaskCircuitBreakerSetting defines the order and state in which individual circuit breakers must be set.
Element Properties
Units of Functionality
Class (Element)
Organization
Chapter
19
Paragraph
4.1.3.5
Short Name
org
Units of Functionality Diagrams
X
X
X
X
X
X
Organization
Description
The Organization class identifies organizations that can be referred to from the LSA program.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
OrganizationAssignment
Chapter
19
Paragraph
4.20.4.61
Short Name
orgInfo
Units of Functionality Diagrams
X
X
X
X
Organization Assignment
Description
The OrganizationAssignment relationship class defines a relationship between a specific Organization and an instance of any class that implements the OrganizationAssignmentItem interface.
Comment
Note: The role of the Organization being assigned is determined by organizationAssignmentRole attribute.
Note: There is one instance of OrganizationAssignment per relevant combination of Organization and instance to which the Organization is being assigned (ie, instance of any class that implements the OrganizationAssignmentItem interface). OrganizationAssignment special recommendations: - Where an instance of OrganizationAssignment is dependent upon eg, customer, it must be distinguished by the assignment of an ApplicabilityStatement to the OrganizationAssignment instance. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
OrganizationAssignmentItem
Chapter
19
Paragraph
4.19.3.1
Units of Functionality Diagrams
X
Organization Assignment Item
Description
The OrganizationAssignmentItem interface is implemented by classes that can be associated with optional organizational information.
Comment
Note: Organizations can also be assigned to any class that is a subclass of the enumerated classes, eg, to a RectifyingTask which is a subclass of Task.
Units of Functionality
Class (Element)
ParameterThresholdDefinition
Short Name
paramThld
Units of Functionality Diagrams
X
Parameter Threshold Definition
Description
The ParameterThresholdDefinition class is a specialization of class ThresholdDefinition and is used to represent a value with unit that constitutes a threshold or trigger.
Comment
Note: An instance of class ParameterThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger
Note: An example of ParameterThresholdDefinition is 1000 flight hours.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PartAsDesigned
Chapter
19
Paragraph
4.9.4.1
Units of Functionality Diagrams
X
X
X
X
X
X
X
Part As Designed
Description
PartAsDesigned is a discrete object that can come into existence as a consequence of a manufacturing process (Source: ISO 10303:239 Product Life Cycle Support).
Comment
Note: PartAsDesigned is an abstract class, ie, an instantiation of PartAsDesigned must always be either a HardwarePartAsDesigned or a SoftwarePartAsDesigned.
Note: Examples of different partIdentifiers are Original Equipment Manufacturer (OEM) part numbers and Supplier part numbers.
Note: PartAsDesignedDesignData (attributeGroup) is the definitional information which defines characteristics for the PartAsDesigned identified during the design activities.
Note: PartAsDesignedSupportData (attributeGroup) is the definitional information which defines characteristics for the PartAsDesigned identified during the supportability analysis activities.
Note: PartAsDesignedControlledItemData (attributeGroup) is the definitional information which defines characteristics for the PartAsDesigned identified during different control analysis activities.
Note: A PartAsDesigned can have more than one part maturity classification (partMaturityClass). This will most likely reflect changes in part maturity over time. If the classificationDate attribute included in the DatedClassification compound attribute is not enough to determine the validity of the respective partMaturityClass value, ApplicabilityStatement can be used to further determine the applicability of the respective value. Refer to Para 4.22,
Note: A PartAsDesigned can have more than one partObsolescenceRiskAssessment description. This will most likely reflect changes in part obsolescence risk assessment over time. If the descriptorProvidedDate attribute included in the DescriptorType is not enough to determine the validity of the respective partObsolescenceRiskAssessment description, ApplicabilityStatement can be used to further determine the applicability of the respective description. Refer to Para 4.22,
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PartAsDesignedControlledItemData
Part As Designed Controlled Item Data
Description
No Description
Attribute Properties
Class (Element)
PartAsDesignedDesignData
Part As Designed Design Data
Description
No Description
Attribute Properties
Class (Element)
PartAsDesignedPartsList
Chapter
19
Paragraph
4.4.3.3
Short Name
partsList
Units of Functionality Diagrams
X
X
X
X
Part As Designed Parts List
Description
The PartAsDesignedPartsList class represents a Bill-Of-Material for a given PartAsDesigned.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PartAsDesignedPartsListEntry
Chapter
19
Paragraph
4.4.3.4
Short Name
pListEntry
Units of Functionality Diagrams
X
X
X
X
Part As Designed Parts List Entry
Description
The PartAsDesignedPartsListEntry relationship class is being used to define the content in a PartAsDesignedPartsList.
Comment
Note: PartAsDesignedPartsListEntry defines one “row” at the time in a PartAsDesignedPartsList (Bill-of-Material), ie, there is one instance of PartAsDesignedPartsListEntry per contained part.
Note: The PartAsDesignedPartsListEntry applies both to HardwarePartAsDesigned and SoftwarePartAsDesigned, and a BOM can consist of both HardwarePartAsDesigned and SoftwarePartAsDesigned.
Note: Physical replaceability and replaceability strategy in the context of a PartAsDesignedPartsListEntry are used to define if the child part can be replaced in its parent part and if so at what maintenance level.
Note: PartAsDesignedPartsListEntry special recommendations: A PartAsDesigned included in another PartAsDesigned can have multiple replaceability strategies (ie, values of the attribute physicalReplaceabilityStrategy). Each physicalReplaceabilityStrategy value (ie instance of data type ClassificationType) must then have an associated ApplicabilityStatement, as defined in the UoF Applicability Statement, in order to define when the respective physicalReplaceabilityStrategy is applicable. The Applicability Statement will in most cases include Operator as one of the parameters to be evaluated.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PartAsDesignedSupportData
Part As Designed Support Data
Description
No Description
Attribute Properties
Class (Element)
PeriodicTimeLimit
Short Name
perTl
Units of Functionality Diagrams
X
Periodic Time Limit
Description
The PeriodicTimeLimit class is a specialization of the TimeLimit class, and is used to identify limits that are repeated with a specific interval, ie, there is a next scheduled occurrence for the associated task.
Comment
Note: An instance of class PeriodicTimeLimit has no meaning by itself, but only in the context of a specific instance of PlannedTaskTarget or TaskRequirementTarget.
Note: The InitialTimeLimit association defines a specified interval for the first required performance of the PlannedTaskItem (ie, RectifyingTask or OperationalTask). The interval must be assumed to be triggered by the condition that is defined as the hardwarePartMaintenanceStart for HardwarePart in UoF Part Definition. Refer to Para 4.4.
Note: Multiple instances of RepeatTimeLimit for the repeat association require that each instance of RepeatTimeLimit is ordered using the SubsequentRepeatRelationship class. PeriodicTimeLimit special recommendations: - Where an instance of PeriodicTimeLimit is dependent upon eg, external conditions or customer, it must be distinguished by the assignment of an ApplicabilityStatement to the PeriodicTimeLimit instance. Refer to Para 4.22.
Note: The PeriodicTimeLimit class can be used to define explicit combinations of initial ::Q::Perform once::Q:: and ::Q::Perform periodically::Q:: time limits as defined in S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PlannedTaskItem
Chapter
19
Paragraph
4.16.3.3
Units of Functionality Diagrams
X
Planned Task Item
Description
The PlannedTaskItem interface is implemented by classes that can be associated with a PlannedTaskTarget, ie, be associated with task limits and preferred locations for task execution.
Element Properties
Units of Functionality
Class (Element)
PlannedTaskTarget
Chapter
19
Paragraph
4.16.3.4
Short Name
plndTask
Units of Functionality Diagrams
X
Planned Task Target
Description
The PlannedTaskTarget relationship class is a specialization of the TaskTarget class which adds information in terms of task limits and preferred support organization for task execution.
Comment
Note: There is one instance of PlannedTaskTarget per relevant combination of PlannedTaskItem and LSACandidate.
Note: The PlannedTaskTarget class must be used to associate RectifyingTasks and OperationalTasks with the items on which the they will be performed. PlannedTaskTarget interfaces: - PlannedTaskTarget implements the TimeLimitItem interface
Note: Associating a PlannedTaskTarget with a specific maintenance level, by default means that any maintenance level above can carry out the same Task.
Note: PlannedTaskTarget special recommendations: Where an instance of PlannedTaskTarget is dependent upon eg, external conditions, customer, it must be distinguished by the assignment of an ApplicabilityStatement to the PlannedTaskTarget instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
PossibleSpecialEventEffect
Chapter
19
Paragraph
4.12.3.4
Short Name
cause
Units of Functionality Diagrams
X
X
Possible Special Event Effect
Description
The PossibleSpecialEventEffect relationship class defines an association between an instance of SpecialEvent and the Damage which can be caused by the special event.
Comment
Note: There is one instance of PossibleSpecialEventEffect per combination of SpecialEvent and Damage.
Element Properties
Units of Functionality
Class (Element)
Product
Chapter
19
Paragraph
4.1.3.14
Short Name
prod
Units of Functionality Diagrams
X
X
X
X
X
X
Product
Description
The Product class identifies a family of items sharing the same underlying design purpose. A Product must have at least one defined product variant.
Comment
Note: An example of generic product is F-15. Product attributes: - productIdentifier (one or many) - productName (zero, one or many)
Note: An example of a type of productIdentifier is the GEIA-STD-0007 End Item Acronym Code. Product associations: - A Product must have at least one defined ProductVariant
Attribute Properties
Units of Functionality
Class (Element)
ProductServiceLife
Chapter
19
Paragraph
4.9.3.3
Short Name
life
Units of Functionality Diagrams
X
Product Service Life
Description
The ProductServiceLife attributeGroup is a specialization of KeyPerformanceIndicator, and represents eg, the number of years the LSA Candidate is expected to be in service.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of ProductServiceLife has multiple productServiceLife values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: ProductServiceLife special recommendations:
- An LSACandidate can have multiple product service life values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of productServiceLife (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple product service life values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ product service life value, and one ‘actual’ product service life value. These values must be distinguished using the valueDetermination attribute for the respective instance of productServiceLife.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ProductUsagePhase
Chapter
19
Paragraph
4.12.3.9
Short Name
usagePhase
Units of Functionality Diagrams
X
X
X
X
Product Usage Phase
Description
The ProductUsagePhase class defines usage phases of interest for the Product in scope of the LSA program.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ProductVariant
Chapter
19
Paragraph
4.1.3.15
Short Name
prodVar
Units of Functionality Diagrams
X
X
X
X
X
X
X
Product Variant
Description
The ProductVariant class identifies a member of a Product family that is configured for a specific purpose and is offered to customers.
Comment
Note: A ProductVariant is also known as a Model in S1000D and S2000M.
Note: Examples of product variants are F-15A and F-15B ProductVariant attributes: - productVariantIdentifier (one or many) - productVariantName (zero, one or many)
Note: An example of a type of productVariantIdentifier is the GEIA-STD-0007 System/End Item Usable On Code.
Attribute Properties
Element Properties
Class (Element)
ProductVariantItem
Chapter
19
Paragraph
4.8.3.2
Units of Functionality Diagrams
X
Product Variant Item
Description
The ProductVariantItem interface is implemented by classes which applicability can be the restricted to specific ProductVariants.
Comment
Note: An instance of a class that implements the ProductVariantItem interface can be associated with more than one ProductVariant, ie, an instance representing the ItemInProductVariant can be applicable to more than one ProductVariant.
Element Properties
Units of Functionality
Class (Element)
Project
Chapter
19
Paragraph
4.1.3.1
Short Name
proj
Units of Functionality Diagrams
X
X
X
X
Project
Description
The Project class identifies the overall LSA project (often also known as the LSA program).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
PropertyType
Chapter
19
Paragraph
4.19.4.26
Units of Functionality Diagrams
X
X
X
Property Type
Description
The PropertyType primitive is used for representing property values and can also include additional information on when a property value was recorded and the method by which the value has been determined (eg, estimated, calculated).
Comment
Note: The PropertyType class is an abstract class, ie, any of its subclasses must be used for the actual representation of a property value. PropertyType subclasses: - NumericalPropertyType (values with unit) - TextPropertyType (a property value described as a string, eg, ::Q::As-required::Q::).
Note: Where no explicit recommendations have been made for attributes that are of data type PropertyType in the S3000L data model, the default is that they use the SingleValuePropertyType representation, ie, the property value is provided as a value together with its associated unit of measure.
Note: The assignment of an Organization to an instance of PropertyType enables the recording of organizational information against any property value, eg, to identify the Organization that recorded a specific property value.
Note: Assignment of ApplicabilityStatements to instances of PropertyType enables multiple values to be given for a single attribute in the data model, where multiple values are allowed, and still distinguish when a single value is applicable.
Attribute Properties
Units of Functionality
Class (Element)
QuantifiedSpecialEventOccurrence
Chapter
19
Paragraph
4.12.3.8
Short Name
quantEvntOcc
Units of Functionality Diagrams
X
Quantified Special Event Occurrence
Description
The QuantifiedSpecialEventOccurrence relationship class is a specialization of the SpecialEventOccurrence class.
Comment
Note: QuantifiedSpecialEventOccurrence special recommendations:
- The specialEventOccurrenceRate attribute can have multiple occurrence rate values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of specialEventOccurrenceRate (ie, to the respective instance of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
RandomSubtaskCircuitBreakerSettings
Chapter
19
Paragraph
4.14.3.22
Short Name
rndmCbSet
Units of Functionality Diagrams
X
Random Subtask Circuit Breaker Settings
Description
The RandomSubtaskCircuitBreakerSettings class is a specialization of the SubtaskCircuitBreakerSettings class. RandomSubtaskCircuitBreakerSettings must be used when the order in which individual circuit breakers are set are of no importance.
Element Properties
Units of Functionality
Class (Element)
RatedSpecialEventOccurrence
Chapter
19
Paragraph
4.12.3.7
Short Name
ratedEvntOcc
Units of Functionality Diagrams
X
Rated Special Event Occurrence
Description
The RatedSpecialEventOccurrence relationship class is a specialization of the SpecialEventOccurrence class.
Comment
Note: RatedSpecialEventOccurrence special recommendations: The specialEventOccurrenceRating attribute can have multiple occurrence ratings depending on, for example operational environment. These ratings must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of specialEventOccurrenceRating ie, to the respective instance of ClassificationType. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
RectifyingTask
Chapter
19
Paragraph
4.14.3.2
Short Name
task
Units of Functionality Diagrams
X
X
Rectifying Task
Description
The RectifyingTask class is a specialization of class Task.
Comment
Note: Each maintenance activity is driven by an event. This event can be a failure, damage, special event or a time limit (interval). All these events require a maintenance action that resolves the event. Each task that is able to resolve an event must be defined as a rectifying task.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
Remark
Chapter
19
Paragraph
4.19.4.25
Short Name
rmk
Units of Functionality Diagrams
X
X
X
Remark
Description
The Remark class represents remarks of any kind, which anyone working within the LSA rogram would like to put against an object of interest.
Comment
Note: Since the remarkText is of data type DescriptorType, all remarks can also identify the organization that provided the remark, and the date when it was recorded.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
RemarkAssignment
Chapter
19
Paragraph
4.22.4.43
Units of Functionality Diagrams
X
X
Remark Assignment
Description
The RemarkAssignment relationship class defines a relationship between a Remark and an instance of a class that implements the RemarkAssignmentItem interface.
Comment
Note: There is one instance of RemarkAssignment per relevant combination of Remark and instance for which the Remark is written (ie, instance of a class that implements the RemarkAssignmentItem interface). RemarkAssignment special recommendations: - Where an instance of RemarkAssignment is dependent upon eg, external conditions or customer, it must be distinguished by the assignment of an ApplicabilityStatement to the RemarkAssignment instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
RemarkAssignmentItem
Chapter
19
Paragraph
4.21.3.2
Units of Functionality Diagrams
X
Remark Assignment Item
Description
The RemarkAssignmentItem interface is implemented by all classes that can be associated with one or many remarks.
Comment
Note: Remarks can also be assigned to any class that is a subclass of the enumerated classes, eg, to a RectifyingTask which is a subclass of Task (the rule of substitutability).
Units of Functionality
Class (Element)
RepeatTimeLimit
Short Name
repeat
Units of Functionality Diagrams
X
Repeat Time Limit
Description
The RepeatTimeLimit class defines task limits that are repeated with a specific interval.
Comment
Note: An instance of class RepeatTimeLimit has no meaning by itself, but only in the context of a specific PeriodicTimeLimit. Note: RepeatTimeLimit must contain a computable expression. Note: The threshold association defines a specified interval for the repeated performance of the associated RectifyingTask or OperationalTask. Note: Multiple instances of ThresholdDefinition for the threshold association mean ‘whichever is reached first’. Note: The RepeatTimeLimit class can be used to define ::Q::Perform periodically::Q:: time limits as defined in S1000D.
Element Properties
Units of Functionality
Class (Element)
ReplacementTime
Chapter
19
Paragraph
4.9.3.13
Short Name
time
Units of Functionality Diagrams
X
Replacement Time
Description
The ReplacementTime attributeGroup is a specialization of KeyPerformanceIndicator, and represents the duration of the replacement of a (eg, faulty) component within any technical system by another (eg, new) component.
Comment
Note: The contracted/allocated/specified ReplacementTime defines a specified value which will be the maximum acceptable duration for component replacement. In practice, this value can be used to document for example, a customer's requirement to be able to perform 98% of all replacement tasks below a specified value of two hours (= maximum replacement time). Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of ReplacementTime has multiple replacementTime values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
Note: ReplacementTime special recommendations: An LSACandidate can have multiple replacement time values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of replacementTime (ie, to the respective instance of PropertyType). Refer to Para 4.22.An LSACandidate can have multiple replacement time values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ replacement time value, and one ‘actual’ replacement time value. These values must be distinguished using the valueDetermination attribute for the respective instance of replacementTime.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ResourceRealization
Chapter
19
Paragraph
4.15.3.8
Short Name
partReal
Units of Functionality Diagrams
X
X
X
X
Resource Realization
Description
The ResourceRealization relationship class defines relationships between ResourceSpecifications and the HardwarePartAsDesigned that fulfills the respective specification.
Comment
Note: There is one instance of ResourceRealization per relevant combination of ResourceSpecification and HardwarePartAsDesigned. ResourceRealization special recommendations: - Where a ResourceRealization is dependent upon eg, customer, maintenance level or external conditions, it must be distinguished by the assignment of an ApplicabilityStatement to the ResourceRealization instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
ResourceSpecification
Chapter
19
Paragraph
4.15.3.7
Units of Functionality Diagrams
X
X
X
X
Resource Specification
Description
The ResourceSpecification class specifies a resource which can be realized by one or many HardwarePartAsDesigned.
Comment
Note: Use of ResourceSpecifications allows for more generic task/subtask definitions, ie, the task/subtask does not need to be changed based on customer specific tool sets. Note: ResourceSpecification is an abstract class, ie, an instantiation of ResourceSpecification must be either a FacilityResourceSpecification or a MaterialResourceSpecification.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
S1000DDataModule
Chapter
19
Paragraph
4.20.3.3
Short Name
s1000dDM
Units of Functionality Diagrams
X
S1000 D Data Module
Description
The S1000DDataModule class is a specialization of class Document and is used to represent documents written in accordance with an S1000D schema.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
S1000DDataModuleIssue
Chapter
19
Paragraph
4.14.4.2
Short Name
dmIss
Units of Functionality Diagrams
X
X
S1000 D Data Module Issue
Description
The S1000DDataModuleIssue class is a specialization of the DocumentIssue class, and is used to represent a specific issue of a data module written in accordance with an S1000D schema.
Attribute Properties
Element Properties
Class (Element)
S1000DPublicationModule
Chapter
19
Paragraph
4.20.3.5
Short Name
s1000dPM
Units of Functionality Diagrams
X
S1000 D Publication Module
Description
The S1000DPublicationModule class is a specialization of class Document, and is used to represent a publications published in accordance with S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
S1000DPublicationModuleIssue
Chapter
19
Paragraph
4.20.3.6
Short Name
pmIss
Units of Functionality Diagrams
X
S1000 D Publication Module Issue
Description
The S1000DPublicationModuleIssue class is a specialization of the DocumentIssue class, and is used to represent a specific issue of a publication module published in accordance with S1000D.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SamplingDefinition
Chapter
19
Paragraph
4.16.3.9
Short Name
samplByDef
Units of Functionality Diagrams
X
X
Sampling Definition
Description
The SamplingDefinition class identifies the method to be used for selecting a limited set of manufactured products, on which a task will be performed when a specific time limit has been reached.
Comment
Note: An instance of class SamplingDefinition has no meaning by itself, but only in the context of a specific DiscreteTimeLimit, InitialTimeLimit or RepeatTimeLimit (via the SamplingItem interface). Note: An instance of SamplingDefinition can be (but need not be) specialized into either SamplingDefinitionByRatio or SamplingDefinitionByValue.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SamplingDefinitionByRatio
Chapter
19
Paragraph
4.16.3.10
Short Name
samplByRo
Units of Functionality Diagrams
X
Sampling Definition By Ratio
Description
The SamplingDefinitionByRatio class is a specialization of the SamplingDefinition class, and identifies that the method used for selecting manufactured products is done by ratio.
Comment
Note: An instance of class SamplingDefinitionByRatio has no meaning by itself, but only in the context of a specific DiscreteTimeLimit, InitialTimeLimit or RepeatTimeLimit.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SamplingDefinitionByValue
Chapter
19
Paragraph
4.16.3.11
Short Name
samplByValue
Units of Functionality Diagrams
X
Sampling Definition By Value
Description
The SamplingDefinitionByValue class is a specialization of the SamplingDefinition class, and identifies that the method used for selecting manufactured products is done by value, ie, a definitive number of manufactured products.
Comment
Note: An instance of class SamplingDefinitionByValue has no meaning by itself, but only in the context of a specific DiscreteTimeLimit, InitialTimeLimit or RepeatTimeLimit.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SamplingItem
Chapter
19
Paragraph
4.16.3.12
Units of Functionality Diagrams
X
Sampling Item
Description
The SamplingItem interface is implemented by classes that can be associated with a defined sampling method.
Element Properties
Units of Functionality
Class (Element)
ScheduledMaintenanceInterval
Chapter
19
Paragraph
4.9.3.4
Short Name
int
Units of Functionality Diagrams
X
Scheduled Maintenance Interval
Description
The ScheduledMaintenanceInterval attributeGroup is a specialization of KeyPerformanceIndicator, and represents the number of operational units (eg, rounds, miles, hours) between scheduled maintenance.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of ScheduledMaintenanceInterval has multiple scheduledMaintenanceInterval values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first
Note: ScheduledMaintenanceInterval special recommendations:
- An LSACandidate can have multiple scheduled maintenance interval values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of scheduledMaintenanceInterval (ie, to the respective instance of PropertyType. Refer to Para 4.22.
- An LSACandidate can have multiple scheduled maintenance interval values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ scheduled maintenance interval value, and one ‘actual’ scheduled maintenance interval value. These values must be distinguished using the valueDetermination attribute for the respective instance of scheduledMaintenanceInterval.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SecurityClass
Chapter
19
Paragraph
4.18.3.1
Short Name
scc
Units of Functionality Diagrams
X
X
X
X
Security Class
Description
The SecurityClass class identifies security classes that can be assigned to objects within an LSA program.
Comment
Note: Security classification system to be used must be determined by the project.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SecurityClassification
Chapter
19
Paragraph
4.18.3.3
Short Name
sec
Units of Functionality Diagrams
X
X
X
X
X
Security Classification
Description
The SecurityClassification relationship class defines a relationship between an instance of SecurityClass and the object that is classified (ie, an instance of a class that implements the SecurityClassificationItem interface).
Comment
Note: There is one instance of SecurityClassification per relevant combination of SecurityClass and instance to which the SecurityClass is applied (ie, relevant instances of BreakdownElement, PartAsDesigned, Task, Subtask or TaskRequirement). SecurityClassification special recommendations - Where an instance of SecurityClassification is dependent upon eg, customer, it must be distinguished by the assignment of an ApplicabilityStatement to the SecurityClassification instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
SecurityClassificationItem
Chapter
19
Paragraph
4.18.3.2
Units of Functionality Diagrams
X
Security Classification Item
Description
The SecurityClassificationItem interface is implemented by classes that can be candidates for security classification.
Element Properties
Units of Functionality
Class (Element)
SerializationItem
Chapter
19
Paragraph
4.22.3.25
Units of Functionality Diagrams
X
Serialization Item
Description
The SerializationItem interface is implemented by classes that that can be serialized.
Units of Functionality
Class (Element)
SerialNumberApplicabilityItem
Chapter
19
Paragraph
4.8.3.12
Units of Functionality Diagrams
X
Serial Number Applicability Item
Description
The SerialNumberApplicabilityItem interface is implemented by classes that that can have a limited applicability to ranges of serialized end items.
Units of Functionality
Class (Element)
SerialNumberRange
Serial Number Range
Description
The SerialNumberRange compoundAttribute is used to identify a possibly open-ended interval of serialized items.
Attribute Properties
Class (Element)
ShopProcessingTime
Chapter
19
Paragraph
4.9.3.11
Short Name
time
Units of Functionality Diagrams
X
Shop Processing Time
Description
The ShopProcessingTime attributeGroup is a specialization of KeyPerformanceIndicator, and represents the duration from the start of the repair activities in the repair shop until the closing of the repair procedure without considering any shipping and delay times.
Comment
Note: valueDetermination is an attribute of the PropertyType primitive. - If an instance of ShopProcessingTime has multiple shopProcessingTime values without any additional applicability statement, or multiple values with the same applicability statement, these values are then to be interpreted as whichever is reached first.
ShopProcessingTime special recommendations:
- An LSACandidate can have multiple shop processing time values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of shopProcessingTime (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- An LSACandidate can have multiple shop processing time values being defined during different stages of the LSA candidate life cycle. For example, one and the same LSA candidate can have one ‘specified’ shop processing time value, and one ‘actual’ shop processing time value. These values must be distinguished using the valueDetermination attribute for the respective instance of shopProcessingTime.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SingleValuePropertyType
Single Value Property Type
Description
The SingleValuePropertyType primitive is used to represent a value with its unit of measure.
Comment
Note: SingleValuePropertyType is the default representation for all attributes that are of data type PropertyType.
Attribute Properties
Class (Element)
Skill
Chapter
19
Paragraph
4.15.3.18
Short Name
skill
Units of Functionality Diagrams
X
X
X
X
Skill
Description
The Skill class identifies specific skills as defined by codes according to agreed encoding systems.
Attribute Properties
Units of Functionality
Class (Element)
SkillLevel
Chapter
19
Paragraph
4.15.3.19
Short Name
skillLevel
Units of Functionality Diagrams
X
X
X
Skill Level
Description
The SkillLevel class defines specific skill levels for a defined Trade, eg, advanced, intermediate or master.
Comment
Note: An instance of class SkillLevel has no meaning by itself, but only in the context of a specific Trade.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SoftwareElement
Chapter
19
Paragraph
4.5.3.4
Short Name
beSw
Units of Functionality Diagrams
X
Software Element
Description
The SoftwareElement class is a specialization of the BreakdownElement class, and represents a specification that is realized in terms of software.
Comment
Note: Wherever the BreakdownElement class is used in the data model, SoftwareElement can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SoftwareElementPartRealization
Chapter
19
Paragraph
4.5.3.6
Short Name
swPart
Units of Functionality Diagrams
X
X
X
X
X
Software Element Part Realization
Description
The SoftwareElementPartRealization relationship class defines an association between an instance of SoftwareElementRevision and the SoftwarePartAsDesigned which fulfills the software element specification.
Comment
Note: There is one instance of SoftwareElementPartRealization per combination of SoftwareElementRevision and SoftwarePartAsDesigned. SoftwareElementPartRealization special recommendations: - Where an instance of SoftwareElementPartRealization is dependent upon product variant or allowed product design configuration, it must be defined by the assignment of ItemInProductVariant or ItemInAllowedProductConfiguration to the instance of SoftwareElementPartRealization under consideration. Refer to Para 4.8.
Element Properties
Units of Functionality
Class (Element)
SoftwareElementRevision
Chapter
19
Paragraph
4.5.3.5
Short Name
beRev
Units of Functionality Diagrams
X
Software Element Revision
Description
The SoftwareElementRevision class is a specialization of the BreakdownElementRevision class, and represents a design iteration that is applied to a SoftwareElement.
Comment
Note: Wherever the BreakdownElementRevision class is used in the data model, SoftwareElementRevision can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SoftwarePartAsDesigned
Chapter
19
Paragraph
4.5.4.2
Short Name
swPart
Units of Functionality Diagrams
X
X
Software Part As Designed
Description
SoftwarePartAsDesigned is a specialization of class PartAsDesigned, and represents parts that will be realized as executable software or as data files (eg, maps).
Comment
Note: SoftwarePartAsDesignedDesignData (attributeGroup) is the definitional information which defines characteristics for the SoftwarePartAsDesigned identified during the design activities. Note: SoftwarePartAsDesignedSupportData (attributeGroup) is the definitional information which defines characteristics for the SoftwarePartAsDesigned identified during the supportability analysis activities. Note: SoftwarePartAsDesignedControlledItemData (attributeGroup) is the definitional information which defines characteristics for the SoftwarePartAsDesigned identified during different control analysis activities.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SoftwarePartAsDesignedDesignData
Software Part As Designed Design Data
Description
No Description
Attribute Properties
Class (Element)
SpecialEvent
Chapter
19
Paragraph
4.12.3.5
Short Name
sEvnt
Units of Functionality Diagrams
X
X
X
X
X
Special Event
Description
The SpecialEvent class identifies special events that can occur during different usage phases of the product, which can lead to damages on one or many hardware items (HardwarePartAsDesigned or HardwareElementRevision).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SpecialEventOccurrence
Chapter
19
Paragraph
4.12.3.6
Units of Functionality Diagrams
X
X
X
X
Special Event Occurrence
Description
The SpecialEventOccurrence relationship class defines an association between an instance of SpecialEvent and an instance of ProductUsagePhase during which the special event can occur.
Comment
Note: The SpecialEventOccurrence class is an abstract class, ie, an instantiation of SpecialEventOccurrence must be either: RatedSpecialEventOccurrence QuantifiedSpecialEventOccurrence Note: RatedSpecialEventOccurrence and QuantifiedSpecialEventOccurrence respectively, mandate the recording of the frequency for which the associated special event is expected to occur during a specific product usage phase, either by rating or by ratio. Note: There is one instance of SpecialEventOccurrence per combination of SpecialEvent and ProductUsagePhase.
Element Properties
Units of Functionality
Class (Element)
SpecialEventThresholdDefinition
Short Name
sEvntThld
Units of Functionality Diagrams
X
Special Event Threshold Definition
Description
The SpecialEventThresholdDefinition class is a specialization of class EventThresholdDefinition. SpecialEventThresholdDefinition is used to represent the number of occurrences of a specific SpecialEvent (UoF Special Event And Damage) that constitutes the threshold or trigger.
Comment
Note: An instance of class SpecialEventThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubsequentRepeatRelationship
Short Name
subseqRep
Units of Functionality Diagrams
X
Subsequent Repeat Relationship
Description
The SubsequentRepeatRelationship class defines an ordered relationship between two instances of RepeatTimeLimit, where the succeeding RepeatTimeLimit replaces the preceding RepeatTimeLimit at a specific point defined by the SubsequentRepeatRelationship trigger.
Comment
Note: The definition of when an instance of RepeatTimeLimit will be succeeded by another instance of RepeatTimeLimit (ie, replaced by another instance) is determined by the instance of ThresholdDefinition defined via the SubsequentRepeatRelationship trigger association. Note: The trigger association describes the event when the instance of RepeatTimeLimit identified by the succeeding association will replace the instance of RepeatTimeLimit identified by the preceding association. Note: Multiple instances of ThresholdDefinition for the trigger association mean ::Q::whichever is reached first::Q::.
Element Properties
Units of Functionality
Class (Element)
SubstanceDefinition
Chapter
19
Paragraph
4.19.4.9
Short Name
subs
Units of Functionality Diagrams
X
X
X
X
Substance Definition
Description
The SubstanceDefinition class deals with the identification of high concern physical matter that is contained in one or many HardwarePartAsDesigned.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubstitutePartAsDesignedRelationship
Chapter
19
Paragraph
4.4.3.5
Short Name
substPart
Units of Functionality Diagrams
X
X
Substitute Part As Designed Relationship
Description
The SubstitutePartAsDesignedRelationship relationship class is used to define substitute parts. As opposed to the alternate part, which is context free, substitute part is context dependent, ie, the SubstitutePartAsDesignedRelationship is a relationship that indicates that one PartAsDesignedPartsListEntry instance can be substituted by another instance of PartAsDesignedPartsListEntry, where both instances of PartAsDesignedPartsListEntry refers to the same parent PartAsDesignedPartsList (Source: ISO 10303:239 Product Life Cycle Support).
Comment
Note: SubstitutePartAsDesignedRelationship defines one substitute part at the time, and applies both to HardwarePartAsDesigned and SoftwarePartAsDesigned.
Element Properties
Units of Functionality
Class (Element)
Subtask
Chapter
19
Paragraph
4.14.3.8
Units of Functionality Diagrams
X
X
X
X
X
Subtask
Description
The Subtask class defines steps to be performed within a TaskRevision. Subtasks are used to provide detailed information about the Task.
Comment
Note: Subtask is an abstract class, ie, an instantiation of Subtask needs to be either, a SubtaskByDefinition, a SubtaskByTaskReference, or a SubtaskByExternalReference (subclass of class SubtaskByDefinition). Note: Subtasks within a TaskRevision can be time lined (scheduled) using the SubtaskTimeline relationship class. Note: Alternative Subtasks within a Task must be distinguished by the assignment of ApplicabilityStatements.
Note: Subtask special recommendations: Where a Subtask is dependent upon eg, maintenance level, it must be distinguished by the assignment of an ApplicabilityStatement to the Subtask instance. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubtaskAcceptanceParameter
Chapter
19
Paragraph
4.14.3.17
Units of Functionality Diagrams
X
X
X
X
Subtask Acceptance Parameter
Description
The SubtaskAcceptanceParameter attributeGroup defines criteria that needs to be fulfilled before the subtask can be closed.
Comment
Note: An instance of class SubtaskAcceptanceParameter has no meaning by itself, but only in the context of a specific instance of SubtaskByDefinition.
Note: SubtaskAcceptanceParameter special recommendations:
- The value for the subtaskAcceptanceParameterValue attribute can use either of the following PropertyType representations:
-- SingleValuePropertyType
-- ValueWithTolerancesPropertyType
-- ValueRangePropertyType
- The subtaskAcceptanceParameterValue can have multiple values depending on, for example operational environment. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of subtaskAcceptanceParameterValue (ie, to the respective instance of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubtaskByDefinition
Chapter
19
Paragraph
4.14.3.15
Short Name
subtByDef
Units of Functionality Diagrams
X
X
Subtask By Definition
Description
The SubtaskByDefinition class is a specialization of Subtask. A SubtaskByDefinition provides a detailed characterization of the subtask to be included in the overall TaskRevision. A SubtaskByDefinition cannot be referenced from any other Task.
Comment
Note: SubtaskByDefinition can be specialized into a SubtaskByExternalReference.
Note: SubtaskByDefinition special recommendations:
- The value for the subtaskDuration attribute can use either of the following PropertyType representations:
-- SingleValuePropertyType
-- ValueWithTolerancesPropertyType
-- ValueRangePropertyType
- The subtaskDuration attribute can have multiple values depending on, for example. maintenance level. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of subtaskDuration (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- See special recommendations for Subtask, Para 4.14.3.8
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubtaskByExternalReference
Chapter
19
Paragraph
4.14.3.25
Short Name
subtByExtRef
Units of Functionality Diagrams
X
Subtask By External Reference
Description
The SubtaskByExternalReference class is a specialization of SubtaskByDefinition. SubtaskByExternalReference must be used whenever the complete description of the Subtask is described in an external source, ie, outside the scope of the LSA program under consideration.
Comment
Note: See special recommendations for SubtaskByDefinition, refer to Para 4.14.3.15
Attribute Properties
Units of Functionality
Class (Element)
SubtaskByTaskReference
Chapter
19
Paragraph
4.14.3.13
Short Name
subtByRef
Units of Functionality Diagrams
X
Subtask By Task Reference
Description
The SubtaskByTaskReference class is a specialization of Subtask. SubtaskByTaskReference will be used when the Subtask is defined as a Task in its own right.
Comment
Note: SubtaskByTaskReference is the only mechanism in S3000L that supports reuse of task steps and/or task procedures in between Tasks.
Note: SubtaskByTaskReference special recommendations: See special recommendations for Subtask, Para 4.14.3.8
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubtaskCircuitBreakerSetting
Chapter
19
Paragraph
4.14.3.23
Units of Functionality Diagrams
X
X
Subtask Circuit Breaker Setting
Description
The SubtaskCircuitBreakerSetting attributeGroup defines the state that the individual circuit breaker must be set in.
Comment
Note: An instance of class SubtaskCircuitBreakerSetting has no meaning by itself, but only in the context of a specific instance of either OrderedSubtaskCircuitBreakerSettings or RandomSubtaskCircuitBreakerSettings.
Attribute Properties
Element Properties
Class (Element)
SubtaskCircuitBreakerSettings
Chapter
19
Paragraph
4.14.3.19
Units of Functionality Diagrams
X
X
Subtask Circuit Breaker Settings
Description
The SubtaskCircuitBreakerSettings class identifies a set of circuit breakers that must be set in specific states as part of the SubtaskByDefinition.
Comment
Note: The SubtaskCircuitBreakerSettings class is an abstract class, ie, an instantiation of SubtaskCircuitBreakerSettings must be either: OrderedSubtaskCircuitBreakerSettings RandomSubtaskCircuitBreakerSettings Note: An instance of a subclass of SubtaskCircuitBreakerSettings has no meaning by itself, but only in the context of a specific instance of SubtaskByDefinition. Note: A mixture of ordered an unordered SubtaskCircuitBreakerSettings can be defined by having multiple instances of SubtaskCircuitBreakerSettings which then are organized into a timeline using instances of the SubtaskCircuitBreakerSettingsTimeline class. Note: Multiple instances of SubtaskCircuitBreakerSettings within the same SubtaskByDefinition without explicit relationships between each other (via the SubtaskCircuitBreakerSettingsTimeline relationship class) must be regarded as being performed in parallel.
Element Properties
Units of Functionality
Class (Element)
SubtaskCircuitBreakerSettingsTimeline
Chapter
19
Paragraph
4.14.3.20
Short Name
precCb
Units of Functionality Diagrams
X
X
Subtask Circuit Breaker Settings Timeline
Description
The SubtaskCircuitBreakerSettingsTimeline relationship class defines a time dependency between two instances of SubtaskCircuitBreakerSettings within the same SubtaskByDefinition.
Element Properties
Units of Functionality
Class (Element)
SubtaskInZone
Chapter
19
Paragraph
4.14.3.16
Short Name
inZone
Units of Functionality Diagrams
X
X
X
Subtask In Zone
Description
The SubtaskInZone relationship class defines associations between instances of SubtaskByDefinition and the zonal location (ZoneElement) in which the respective subtask will be performed.
Comment
Note: There is one instance of SubtaskInZone per relevant combination of SubtaskByDefinition and zonal location (ZoneElement).
Element Properties
Units of Functionality
Class (Element)
SubtaskTarget
Chapter
19
Paragraph
4.14.3.18
Short Name
subtTgt
Units of Functionality Diagrams
X
Subtask Target
Description
The SubtaskTarget relationship class defines an association between an instance of SubtaskByDefinition and the object (instance of a class that implements the LSACandidate interface) on which a SubtaskByDefinition will be performed.
Comment
Note: There is one instance of SubtaskTarget per relevant combination of SubtaskByDefinition and LSACandidate.
Element Properties
Units of Functionality
Class (Element)
SubtaskTimeline
Chapter
19
Paragraph
4.14.3.9
Short Name
precSubt
Units of Functionality Diagrams
X
X
X
X
Subtask Timeline
Description
The SubtaskTimeline relationship class can define timeline associations between two instances of Subtask. The timeline association enables the definition of time dependencies between two Subtasks within the same TaskRevision.
Comment
Note: Subtasks that don’t relate to any other Subtask, via the SubtaskTimeline association, must be regarded as being performed in sequence according to their subtaskIdentifiers (low to high). Note: This class supports the creation of a GANTT-schema for a Task.
Note: SubtaskTimeline special recommendations: The subtaskTimelineLag attribute can have multiple values depending on, for example environmental conditions. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of subtaskTimelineLag (ie, to the respective instance of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SubtaskWarningCautionNote
Chapter
19
Paragraph
4.14.3.12
Short Name
wcn
Units of Functionality Diagrams
X
X
Subtask Warning Caution Note
Description
The SubtaskWarningCautionNote relationship class defines associations between instances of Subtask and WarningCautionNotes that applies to the respective subtask.
Comment
Note: There is one instance of SubtaskWarningCautionNote per relevant combination of Subtask and WarningCautionNote. SubtaskWarningCautionNote special recommendations: - Where a SubtaskWarningCautionNote is dependent upon eg, maintenance level or external conditions, it must be distinguished by the assignment of an ApplicabilityStatement to the SubtaskWarningCautionNote instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
SupportingTask
Chapter
19
Paragraph
4.14.3.3
Short Name
supTask
Units of Functionality Diagrams
X
X
Supporting Task
Description
The SupportingTask class is a specialization of class Task.
Comment
Note: A supporting task does not ::Q::solve::Q:: an event, but may be used as a subtask within one or many rectifying tasks. An example of a supporting task is open hatch, or jack a car.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
SupportingTaskTarget
Chapter
19
Paragraph
4.17.3.1
Short Name
supTask
Units of Functionality Diagrams
X
Supporting Task Target
Description
The SupportingTaskTarget relationship class is a specialization of the TaskTarget class. SupportingTaskTarget defines associations between instances of SupportingTask and specific task target items (ie, instances of the classes that implement the LSACandidate interface) on which the SupportingTask will be performed.
Comment
Note: There is one instance of SupportingTaskTarget per relevant combination of SupportingTask and LSACandidate.
Element Properties
Units of Functionality
Class (Element)
Task
Chapter
19
Paragraph
4.14.3.1
Units of Functionality Diagrams
X
X
X
X
X
X
X
Task
Description
The Task class supports the detailed specification of a task.
Comment
Note: Task is an abstract class, ie, an instantiation of Task must be either, a RectifyingTask, an OperationalTask or a SupportingTask. Refer to Chap 12 for definitions and usages of the respective task type.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskDocumentResource
Chapter
19
Paragraph
4.15.3.22
Short Name
doc
Units of Functionality Diagrams
X
Task Document Resource
Description
The TaskDocument class is a specialization of TaskResource, and identifies Documents needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: Each instance of TaskDocumentResource is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of document resource definitions is enabled through the use of Documents.
Note: TaskDocumentResource special recommendations: See special recommendations for Task Resource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskFacilityResource
Chapter
19
Paragraph
4.15.3.10
Units of Functionality Diagrams
X
Task Facility Resource
Description
The TaskFacilityResource class is a specialization of TaskResource and identifies facility resources needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: TaskFacilityResource is an abstract class, ie, an instantiation of TaskFacilityResource must be done using any of its specializations: TaskFacilityResourceBySpecification TaskFacilityResourceByReference Note: Each instance of TaskFacilityResource is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of facility resource definitions is enabled through the use of FacilityResourceSpecifications and HardwarePartAsDesigned.
Note: TaskFacilityResource special recommendations: See special recommendations for TaskResource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskFacilityResourceByReference
Chapter
19
Paragraph
4.15.3.11
Short Name
facPart
Units of Functionality Diagrams
X
Task Facility Resource By Reference
Description
The TaskFacilityResourceByReference class is a specialization of TaskFacilityResource, and identifies a specific hardware item (HardwarePartAsDesigned or HardwareElement) as the facility resource needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: Each instance of TaskFacilityResourceByReference is uniquely defined for a specific instance of Task or SubtaskByDefinition.
Note: TaskFacilityResourceByReference special recommendations: See special recommendations for TaskResource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskFacilityResourceBySpecification
Chapter
19
Paragraph
4.15.3.12
Short Name
facSpec
Units of Functionality Diagrams
X
Task Facility Resource By Specification
Description
The TaskFacilityResourceBySpecification class is a specialization of TaskFacilityResource, and identifies the facility resource needed to perform a specific Task or SubtaskByDefinition through a FacilityResourceSpecification.
Comment
Note: Each instance of TaskFacilityResourceBySpecification is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of facility resource specifications is enabled through the use of FacilityResourceSpecification.
Note: TaskFacilityResourceBySpecification special recommendations: See special recommendations for TaskResource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskFrequency
Chapter
19
Paragraph
4.16.3.2
Short Name
frequency
Units of Functionality Diagrams
X
X
X
X
Task Frequency
Description
The TaskFrequency attributeGroup defines the frequency of performance or occurrence for the associated Task.
Comment
Note: An instance of class TaskFrequency has no meaning by itself, but only in the context of a specific TaskTarget (task usage). Note: Task frequency (eg, annualization) must be defined whenever a task has more than one time limit.
Note: TaskFrequency special recommendations:
- Where a TaskFrequency is dependent upon eg, external conditions, customer, it must be distinguished by the assignment of an ApplicabilityStatement to the TaskFrequency instance. Refer to Para 4.22.
- The taskFrequency attribute can have multiple values depending on, for example external conditions. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of taskFrequency ie, to the respective instance of PropertyType. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskJustification
Chapter
19
Paragraph
4.14.3.6
Short Name
taskJust
Units of Functionality Diagrams
X
Task Justification
Description
The TaskJustification relationship class defines associations between instances of TaskRevision and the TaskRequirements that justifies the task.
Comment
Note: There is one instance of TaskJustification per combination of TaskRevision and TaskRequirement.
Element Properties
Units of Functionality
Class (Element)
TaskMaterialResource
Chapter
19
Paragraph
4.15.3.4
Units of Functionality Diagrams
X
Task Material Resource
Description
The TaskMaterialResource class is a specialization of TaskResource and identifies material resources needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: TaskMaterialResource is an abstract class, ie, an instantiation of TaskMaterialResource must be done using any of its specializations: TaskMaterialResourceBySpecification TaskMaterialResourceByReference Note: Each instance of TaskMaterialResource is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of material resource definitions is enabled through the use of MaterialResourceSpecifications and HardwarePartAsDesigned.
Note: TaskMaterialResource special recommendations: See special recommendations for Task Resource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskMaterialResourceByReference
Chapter
19
Paragraph
4.15.3.5
Short Name
part
Units of Functionality Diagrams
X
Task Material Resource By Reference
Description
The TaskMaterialResourceByReference class is a specialization of TaskMaterialResource, and identifies a specific hardware item (HardwarePartAsDesigned or HardwareElement) as the material resource needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: Each instance of TaskMaterialResourceByReference is uniquely defined for a specific instance of Task or SubtaskByDefinition.
Note: TaskMaterialResourceByReference special recommendations: See special recommendations for Task Resource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskMaterialResourceBySpecification
Chapter
19
Paragraph
4.15.3.6
Short Name
mtrlSpec
Units of Functionality Diagrams
X
Task Material Resource By Specification
Description
The TaskMaterialResourceBySpecification class is a specialization of TaskMaterialResource, and identifies the material resource needed to perform a specific Task or SubtaskByDefinition, through a MaterialResourceSpecification.
Comment
Note: Each instance of TaskMaterialResourceBySpecification is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of material resource specifications is enabled through the use of MaterialResourceSpecification.
Note: TaskMaterialResourceBySpecification special recommendations: See special recommendations for Task Resource, Para 4.15.3.2
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskPersonnelResource
Chapter
19
Paragraph
4.15.3.15
Short Name
pers
Units of Functionality Diagrams
X
Task Personnel Resource
Description
The TaskPersonnelResource class is a specialization of TaskResource, and identifies personnel resources needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: Each instance of TaskPersonnelResource is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of personnel resource definitions is enabled through the use of Trades, SkillLevels and Skills.
Note: TaskPersonnelResource special recommendations:
- The taskResourceDuration, taskNumberOfPersonnelResource and taskPersonnelResourceLabourTime attributes can have multiple values depending on, for example maintenance level or external conditions. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of taskResourceDuration, taskNumberOfPersonnelResource and taskPersonnelResourceLabourTime, respectively (ie, to the respective instance of PropertyType). Refer to Para 4.22.
- See special recommendations for ResourceSpecification, Para 4.15.3.8
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskPersonnelResourceCompetence
Chapter
19
Paragraph
4.15.3.20
Short Name
compt
Units of Functionality Diagrams
X
X
Task Personnel Resource Competence
Description
The TaskPersonnelResourceCompetence relationship class defines relationships between instances of TaskPersonnelResource and the specific competences that are required for the person that will play the role as the personnel resource.
Comment
Note: There is one instance of TaskPersonnelResourceCompetence per relevant combination of TaskPersonnelResource and competence (ie, Trade, Skill or SkillLevel). TaskPersonnelResourceCompetence special recommendations: - Where a TaskPersonnelResourceCompetence is dependent upon eg, customer, maintenance level, or external conditions, it must be distinguished by the assignment of an ApplicabilityStatement to the TaskPersonnelResourceCompetence instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
TaskReference
Chapter
19
Paragraph
4.14.3.14
Short Name
taskRef
Units of Functionality Diagrams
X
Task Reference
Description
The TaskReference relationship class defines associations between instances of SubtaskByTaskReference and the Task that is referenced as a subtask.
Comment
Note: There is one instance of TaskReference per combination of SubtaskByTaskReference and Task.
Element Properties
Units of Functionality
Class (Element)
TaskRequirement
Chapter
19
Paragraph
4.13.3.1
Short Name
taskReq
Units of Functionality Diagrams
X
X
X
X
X
X
X
Task Requirement
Description
The TaskRequirement class supports the specification of task requirements prior to any detailed task analysis. There is also a specialization of TaskRequirement, namely AuthorityDrivenTaskRequirement.
Attribute Properties
Element Properties
Class (Element)
TaskRequirementJustification
Chapter
19
Paragraph
4.13.3.6
Short Name
trJust
Units of Functionality Diagrams
X
X
X
Task Requirement Justification
Description
The TaskRequirementJustification relationship class defines associations between instances of TaskRequirement and items that justify the task requirement, ie, instances of classes that implement the TaskRequirementJustificationItem interface.
Comment
Note: There is one instance of TaskRequirementJustification per combination of TaskRequirementRevision and item that justifies the task requirement.
Element Properties
Units of Functionality
Class (Element)
TaskRequirementJustificationItem
Chapter
19
Paragraph
4.13.3.5
Units of Functionality Diagrams
X
Task Requirement Justification Item
Description
The TaskRequirementJustificationItem interface is implemented by classes that can justify a task requirement.
Element Properties
Units of Functionality
Class (Element)
TaskRequirementRevision
Chapter
19
Paragraph
4.13.3.3
Short Name
trRev
Units of Functionality Diagrams
X
X
X
Task Requirement Revision
Description
The TaskRequirementRevision class defines a revision (design iteration) of a TaskRequirement.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskRequirementTarget
Chapter
19
Paragraph
4.13.3.4
Short Name
taskReq
Units of Functionality Diagrams
X
Task Requirement Target
Description
The TaskRequirementTarget relationship class defines an association between an instance of TaskRequirement and an instance of LSACandidate for which the task requirement is identified.
Comment
Note: There is one instance of TaskRequirementTarget per combination of TaskRequirement and LSACandidate.
Element Properties
Units of Functionality
Class (Element)
TaskResource
Chapter
19
Paragraph
4.15.3.2
Units of Functionality Diagrams
X
X
X
X
Task Resource
Description
The TaskResource class supports the identification of resources needed for the performance of a specific Task or SubtaskByDefinition.
Comment
Note: TaskResource is an abstract class, ie, an instantiation of TaskResource must be done using any of the following specializations: TaskMaterialResourceBySpecification TaskMaterialResourceByReference TaskFacilityResourceBySpecification TaskFacilityResourceByReference TaskPersonnelResource TaskDocumentResource Note: Each instance of TaskResource is uniquely defined for a specific instance of Task or SubtaskByDefinition. Reuse of resource definitions is enabled through the use of ResourceSpecifications, HardwarePartAsDesigned, Skills, Trades and Documents. Note: An instance of class TaskResource has no meaning by itself, but only in the context of a specific Task or SubtaskByDefinition.
Note: TaskResource special recommendations:
- Where a TaskResource is dependent upon eg, maintenance level or external condition, it must be distinguished by the assignment of an ApplicabilityStatement to the TaskResource instance. Refer to Para 4.22.
- The taskResourceDuration attribute can have multiple values depending on, for example maintenance level or external condition. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of taskResourceDuration (ie, to the respective instance of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskResourceByReferenceItem
Chapter
19
Paragraph
4.15.3.14
Units of Functionality Diagrams
X
Task Resource By Reference Item
Description
The TaskResourceByReferenceItem interface is implemented by classes that represent hardware which can be used as a resource in a task.
Element Properties
Units of Functionality
Class (Element)
TaskResourceItem
Chapter
19
Paragraph
4.15.3.1
Units of Functionality Diagrams
X
Task Resource Item
Description
The TaskResourceItem interface enables resources to be assigned to classes that implement this interface.
Units of Functionality
Class (Element)
TaskResourceRelationship
Chapter
19
Paragraph
4.15.3.3
Short Name
relRes
Units of Functionality Diagrams
X
X
X
Task Resource Relationship
Description
The TaskResourceRelationship relationship class defines associations between two instances of TaskResource within the same instance of Task or SubtaskByDefinition. An example of a task resource relationship is eg, person A ::Q::uses::Q:: tool B.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TaskRevision
Chapter
19
Paragraph
4.14.3.5
Short Name
taskRev
Units of Functionality Diagrams
X
X
X
Task Revision
Description
The TaskRevision class defines an explicit revision (design iteration) of a Task.
Comment
Note: A detailed procedure for the performance of the task can be documented in zero, one or many S1000D data modules. The Task UoF supports cross references between task revisions being defined in accordance with S3000L and data module issues being produced in accordance with the S1000D procedure and schedule schemes, respectively. Note: A TaskRevision in S3000L can be split into many S1000D data modules. One S1000D data module can cover many S3000L tasks. However, projects are strongly recommended to aim for a one to one correspondence. Note: Where the concept of master data modules is used in the S1000D Common Source DataBase (CSDB), it is recommended to just keep the cross references between the S3000L tasks and the master data modules in the CSDB. TaskRevision special recommendations: - The value for the taskDuration and taskTotalLabourTime attributes can use either of the following PropertyType representations: SingleValuePropertyType ValueWithTolerancesPropertyType ValueRangePropertyType - The taskDuration and taskTotalLabourTime attributes can have multiple values depending on, for example maintenance level. These values must be distinguished by the assignment of an ApplicabilityStatement to the respective instance of taskDuration and taskTotalLabourTime, respectively (ie, to the respective instance of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Class (Element)
TaskRevisionWarningCautionNote
Chapter
19
Paragraph
4.14.3.11
Short Name
wcn
Units of Functionality Diagrams
X
X
Task Revision Warning Caution Note
Description
The TaskRevisionWarningCautionNote relationship class defines associations between instances of TaskRevision and WarningCautionNotes that applies to the respective task revision.
Comment
Note: There is one instance of TaskRevisionWarningCautionNote per relevant combination of TaskRevision and WarningCautionNote. TaskRevisionWarningCautionNote special recommendations: - Where a TaskRevisionWarningCautionNote is dependent upon eg, maintenance level or external conditions, it must be distinguished by the assignment of an ApplicabilityStatement to the TaskRevisionWarningCautionNote instance. Refer to Para 4.22.
Element Properties
Units of Functionality
Class (Element)
TaskTarget
Chapter
19
Paragraph
4.16.3.1
Units of Functionality Diagrams
X
X
X
X
X
Task Target
Description
The TaskTarget relationship class defines a relationship between a Task and the object on which the Task will be performed. The object must be an instance of a class that implements the LSACandidate interface. Refer to Para 4.9.
Comment
Note: TaskTarget is an abstract class, ie, an instantiation of TaskTarget needs to be either a PlannedTaskTarget or SupportingTaskTarget. Refer to Para 4.17.
Element Properties
Units of Functionality
Class (Element)
TaskThresholdDefinition
Chapter
19
Paragraph
4.16.3.23
Short Name
taskThld
Units of Functionality Diagrams
X
Task Threshold Definition
Description
The TaskThresholdDefinition class is a specialization of class EventThresholdDefinition. TaskThresholdDefinition is used to represent the number of occurrences of a specific Task (UoF Task) that constitutes the threshold or trigger. Refer tp Para 4.14.
Comment
Note: An instance of class TaskThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TextProperty
No Name
Description
The TextProperty primitive is used to represent a property value described as a string value, eg, ::Q::As-required::Q::.
Attribute Properties
Class (Element)
TechnicalFailureMode
Chapter
19
Paragraph
4.11.3.3
Short Name
techFm
Units of Functionality Diagrams
X
Technical Failure Mode
Description
The TechnicalFailureMode class is a specialization of FailureMode, and supports the definition of technical failure modes for a specific hardware item.
Comment
Note: An instance of class TechnicalFailureMode has no meaning by itself, but only in the context of a hardware item. Note: The failureModeDetectionAbilityRating and failureModeLocalizationAbilityRating attributes are both of data type DatedClassification, ie, both ratings must have an associated date representing the date when the rating was performed.
Note: TechnicalFailureMode special recommendations: The failureModeFailureRate attribute can have multiple failure rate values, eg, depending on operational environment. These must be distinguished by the assignment of ApplicabilityStatement to the instances of failureModeFailureRate value (ie, the instances of PropertyType). Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TextPropertyType
Class (Element)
ThresholdDefinition
Chapter
19
Paragraph
4.21.4.77
Units of Functionality Diagrams
X
X
X
Threshold Definition
Description
The ThresholdDefinition class defines the value or event that constitutes a threshold or trigger.
Comment
Note: An instance of class ThresholdDefinition has no meaning by itself, but only in the context of a specific instance of either: DiscreteTimeLimit, as a trigger DiscreteTimeLimit, as a threshold InitialTimeLimit, as an initial threshold RepeatTimeLimit, as a threshold SubsequentRepeatRelationship, as a trigger Note: ThresholdDefinition is an abstract class, ie, an instantiation of ThresholdDefinition must be either a ParameterThresholdDefinition or an EventThresholdDefinition.
Element Properties
Units of Functionality
Class (Element)
TimeLimit
Chapter
19
Paragraph
4.16.3.7
Units of Functionality Diagrams
X
X
X
X
X
Time Limit
Description
The TimeLimit class identifies thresholds (intervals) which defines when the associated task (via PlannedTaskTarget) will be performed on the identified LSACandidate.
Comment
Note: An instance of class TimeLimit has no meaning by itself, but only in the context of a specific PlannedTaskTarget or TaskRequirementTarget. Refer to Para 4.13. Note: TimeLimit is an abstract class, ie, an instantiation of TimeLimit must be an instantiation of either DiscreteTimeLimit or PeriodicTimeLimit.
Note: TimeLimit special recommendations: Where an instance of TimeLimit is dependent upon eg, external conditions or customer, it must be distinguished by the assignment of an ApplicabilityStatement to the TimeLimit instance. Refer to Para 4.22.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
TimeLimitItem
Chapter
19
Paragraph
4.16.3.8
Units of Functionality Diagrams
X
Time Limit Item
Description
The TimeLimitItem interface is implemented by classes that can have an associated interval or limit that must not be exceeded.
Units of Functionality
Class (Element)
TimeOffset
Class (Element)
Trade
Chapter
19
Paragraph
4.15.3.17
Short Name
trade
Units of Functionality Diagrams
X
X
X
X
Trade
Description
The Trade class identifies types of occupations.
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
User
Chapter
19
Paragraph
4.1.3.10
Units of Functionality Diagrams
X
User
Description
The User interface is implemented by classes that can play the role of a user.
Units of Functionality
Class (Element)
UserCustomerContext
Chapter
19
Paragraph
4.1.3.11
Short Name
customerCxt
Units of Functionality Diagrams
X
User Customer Context
Description
The UserCustomerContext relationship class defines relationships in between a User organization and the Customer organization for which the User organization has been defined.
Comment
Note: There is one instance of UserCustomerContext per combination of User and Customer organizations.
Units of Functionality
Class (Element)
UserOfContractedProductVariant
Chapter
19
Paragraph
4.1.3.12
Short Name
user
Units of Functionality Diagrams
X
User Of Contracted Product Variant
Description
The UserOfContractedProductVariant relationship class defines relationships in between a ContractedProductVariant and the Organization that is defined as being the User of the ContractedProductVariant under consideration.
Comment
Note: There is one instance of UserOfContractedProductVariant per combination of ContractedProductVariant and User organization.
Element Properties
Units of Functionality
Class (Element)
ValueRangePropertyType
Value Range Property Type
Description
The ValueRangePropertyType primitive is used to represent a property with a value range in terms of upper and lower limits along with a unit of measure.
Attribute Properties
Class (Element)
ValueWithTolerancesPropertyType
Value With Tolerances Property Type
Description
The ValueWithTolerancesPropertyType primitive is used to represent a value with its unit of measure, along with acceptable upper and lower offset values.
Attribute Properties
Class (Element)
WarningCautionNote
Chapter
19
Paragraph
4.14.3.10
Short Name
wcn
Units of Functionality Diagrams
X
X
X
Warning Caution Note
Description
The WarningCautionNote class defines advices concerning safety, legal and health aspects.
Attribute Properties
Element Properties
Class (Element)
XOR
X O R
Description
No Description
Class (Element)
ZoneElement
Chapter
19
Paragraph
4.6.3.1
Short Name
beZone
Units of Functionality Diagrams
X
X
Zone Element
Description
The ZoneElement class is a specialization of the BreakdownElement class, and is used to represent a 3 dimensional space within a Product.
Comment
Note: Wherever the BreakdownElement class is used in the data model, ZoneElement can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Class (Element)
ZoneElementRevision
Chapter
19
Paragraph
4.6.3.2
Short Name
beRev
Units of Functionality Diagrams
X
Zone Element Revision
Description
The ZoneElementRevision class is a specialization of the BreakdownElementRevision class, and represents a design iteration that is applied to a ZoneElement.
Comment
Note: Wherever the BreakdownElementRevision class is used in the data model, ZoneElementRevision can be used instead (the rule of substitutability).
Attribute Properties
Element Properties
Units of Functionality
Properties
Property (Attribute)
additionalTrainingRequirementsDescription
Units of Functionality Diagrams
X
Additional Training Requirements Description
Description
additionalTrainingRequirementsDescription is a narrative statement which describes the additional training which is necessary to achieve a specific personnel competence.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
aggregatedElementDescription
Short Name
beDescr
Units of Functionality Diagrams
X
Aggregated Element Description
Description
aggregatedElementDescription is a phrase that gives more information on the aggregated element under consideration.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
aggregatedElementType
Short Name
beType
Units of Functionality Diagrams
X
Aggregated Element Type
Description
aggregatedElementType is a classification that identifies further specialization of an aggregated element.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
allowedProductConfigurationIdentifier
Short Name
prodConfId
Units of Functionality Diagrams
X
Allowed Product Configuration Identifier
Description
allowedProductConfigurationIdentifier is a string of characters that are unique to the issuing organization which is used to designate an AllowedProductConfiguration and to differentiate it from other AllowedProductConfigurations.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
applicabilityEndDate
Short Name
endDate
Units of Functionality Diagrams
X
Applicability End Date
Description
applicabilityEndDate is a date that defines the upper bound of the interval for a dated applicability statement.
Data Type
DateType
Units of Functionality
Property (Attribute)
applicabilityStartDate
Short Name
startDate
Units of Functionality Diagrams
X
Applicability Start Date
Description
applicabilityStartDate is a date that defines the lower bound of the interval for a dated applicability statement.
Data Type
DateType
Units of Functionality
Property (Attribute)
applicabilityStatementDescription
Short Name
applicDescr
Units of Functionality Diagrams
X
Applicability Statement Description
Description
applicabilityStatementDescription is a narrative statement that provides a human readable description of the rule expressed in the applicability statement.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
applicabilityStatementIdentifier
Short Name
applicId
Units of Functionality Diagrams
X
Applicability Statement Identifier
Description
applicabilityStatementIdentifier is a string of characters used to uniquely identify an ApplicabilityStatement and to differentiate it from other ApplicabilityStatements.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
applicableSerialNumberRange
Short Name
efy
Units of Functionality Diagrams
X
X
Applicable Serial Number Range
Description
applicableSerialNumberRange is a design characteristic that identifies an interval of serialized items which may be an open-ended.
Data Type
SerialNumberRange
Units of Functionality
Property (Attribute)
authorityToOperateIdentifier
Short Name
authToOpId
Units of Functionality Diagrams
X
Authority To Operate Identifier
Description
authorityToOperateIdentifier is a string of characters that are unique to the issuing organization which is used to designate an AuthorityToOperate and to differentiate it from other AuthorityToOperate.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
authorizedLife
Units of Functionality Diagrams
X
Authorized Life
Description
authorizedLife is a characteristic which defines the maximum life limit for an item, and upon reaching this limit, any further usage of the item must be re-authorized.
Comment
Multiple values for authorizedLife mean "whichever is reached first".
If an item has different authorized lives depending on eg, operational environments, these can be represented as a set of values for the authorizedLife attribute and be distinguished by the assignment of an ApplicabilityStatement to the respective instance of PropertyType that represents the individual value. Refer to Para 4.22.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
breakdownElementEssentiality
Short Name
esc
Units of Functionality Diagrams
X
Breakdown Element Essentiality
Description
breakdownElementEssentiality is a design classification that identifies the operational impact of the breakdown element at the product level.
Comment
Based on the criticality as defined during the FMECA.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
breakdownElementIdentifier
Short Name
beId
Units of Functionality Diagrams
X
Breakdown Element Identifier
Description
breakdownElementIdentifier is a string of characters used to uniquely identify a BreakdownElement and to differentiate it from other BreakdownElements that comprise a product.
Comment
Can be used to establish a hierarchical structure of the technical system.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
breakdownElementName
Short Name
name
Units of Functionality Diagrams
X
Breakdown Element Name
Description
breakdownElementName is a word or phrase by which the breakdown element is known and can be easily referenced.
Comment
It is recommended that breakdownElementName be the same as technical name (techname) in S1000D.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
breakdownElementRelationshipType
Short Name
relType
Units of Functionality Diagrams
X
Breakdown Element Relationship Type
Description
breakdownElementRelationshipType is a classification that identifies the type of relationship established between two BreakdownElementRevisions.
Comment
The related breakdown elements do not need to be used in the same breakdown, ie it can be used to establish the relationship between a breakdown element in a functional breakdown and a breakdown element in a physical breakdown.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
breakdownElementRevisionCreationDate
Short Name
beRevDate
Units of Functionality Diagrams
X
Breakdown Element Revision Creation Date
Description
breakdownElementRevisionCreationDate defines the date when the breakdown element revision was created.
Data Type
DateType
Units of Functionality
Property (Attribute)
breakdownElementRevisionIdentifier
Short Name
beRevId
Units of Functionality Diagrams
X
Breakdown Element Revision Identifier
Description
breakdownElementRevisionIdentifier is a string of characters used to uniquely identify a BreakdownElementRevision and to differentiate it from other BreakdownElementRevisions.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
breakdownElementRevisionStatus
Short Name
status
Units of Functionality Diagrams
X
Breakdown Element Revision Status
Description
breakdownElementRevisionStatus is a classification that identifies the maturity of a BreakdownElementRevision.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
breakdownElementStructure RelationshipType
Units of Functionality Diagrams
X
Breakdown Element Structure Relationship Type
Description
breakdownElementStructureRelationshipType is a classification that identifies the type of restriction or association between two BreakdownElementRevisions.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
breakdownRevisionCreationDate
Short Name
bkdnRevDate
Units of Functionality Diagrams
X
Breakdown Revision Creation Date
Description
breakdownRevisionCreationDate defines the date when the breakdown revision was created.
Data Type
DateType
Units of Functionality
Property (Attribute)
breakdownRevisionIdentifier
Short Name
bkdnRevId
Units of Functionality Diagrams
X
Breakdown Revision Identifier
Description
breakdownRevisionIdentifier is a string of characters used to uniquely identify a BreakdownRevision and to differentiate it from other BreakdownRevisions.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
breakdownRevisionStatus
Short Name
status
Units of Functionality Diagrams
X
Breakdown Revision Status
Description
breakdownRevisionStatus is a classification that identifies the maturity of a BreakdownRevision.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
breakdownType
Short Name
bkdnType
Units of Functionality Diagrams
X
Breakdown Type
Description
breakdownType is a classification that identifies the type of breakdown for the product.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
candidateItemAnalysisActivityDate
Short Name
update
Units of Functionality Diagrams
X
Candidate Item Analysis Activity Date
Description
candidateItemAnalysisActivityDate defines the date for the latest update of the candidate item analysis activity information.
Data Type
DateType
Units of Functionality
Property (Attribute)
candidateItemAnalysisActivityIndicator
Short Name
indicator
Units of Functionality Diagrams
X
Candidate Item Analysis Activity Indicator
Description
candidateItemAnalysisActivityIndicator is a classification that identifies whether the candidate item analysis activity is selected for a specific LSA candidate.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
candidateItemAnalysisActivityRationale
Short Name
rationale
Units of Functionality Diagrams
X
Candidate Item Analysis Activity Rationale
Description
candidateItemAnalysisActivityRationale is a phrase that gives more information on the reason for the selection/non selection of the candidate item analysis activity.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
candidateItemAnalysisActivityStatus
Short Name
status
Units of Functionality Diagrams
X
Candidate Item Analysis Activity Status
Description
candidateItemAnalysisActivityStatus a classification that identifies the progression of the candidate item analysis activity.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
changeRequestDescription
Short Name
crDescr
Units of Functionality Diagrams
X
Change Request Description
Description
changeRequestDescription is a phrase that gives more information on a desired product design change.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
changeRequestIdentifier
Short Name
crId
Units of Functionality Diagrams
X
Change Request Identifier
Description
changeRequestIdentifier is a string of characters used to uniquely identify a ChangeRequest and to differentiate it from other ChangeRequests.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
circuitBreakerIdentifier
Short Name
cbId
Units of Functionality Diagrams
X
Circuit Breaker Identifier
Description
circuitBreakerIdentifier is a string of characters used to uniquely identify a CircuitBreaker and to differentiate it from other CircuitBreakers.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
circuitBreakerName
Short Name
name
Units of Functionality Diagrams
X
Circuit Breaker Name
Description
circuitBreakerName is a word or phrase by which the circuit breaker is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
circuitBreakerState
Short Name
cbState
Units of Functionality Diagrams
X
Circuit Breaker State
Description
circuitBreakerState is a classification which defines the state that the circuit breaker must be in after the accomplishment of the subtask.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
circuitBreakerType
Short Name
cbType
Units of Functionality Diagrams
X
Circuit Breaker Type
Description
circuitBreakerType is a classification that defines type of circuit breaker.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
class
Units of Functionality Diagrams
X
Class
Description
class is a characteristic that represents the term that is used for classification.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
classificationDate
Units of Functionality Diagrams
X
Classification Date
Description
classificationDate is a characteristicMetadata which defines the date when the classification was determined.
Data Type
DateType
Units of Functionality
Property (Attribute)
classifier
Units of Functionality Diagrams
X
Classifier
Description
The word or code by which the term (class) is known.
Comment
Source: ISO 10303:239 ed.2, Product Life Cycle Support.
Data Type
char
Units of Functionality
Property (Attribute)
conditionInstanceDescription
Short Name
condInstDescr
Units of Functionality Diagrams
X
Condition Instance Description
Description
conditionInstanceDescription is a narrative statement of the meaning of the condition instance.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
conditionInstanceIdentifier
Short Name
condInstId
Units of Functionality Diagrams
X
Condition Instance Identifier
Description
conditionInstanceIdentifier is a string of characters used to uniquely identify a ConditionInstance and to differentiate it from other ConditionInstances.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
conditionInstanceName
Short Name
name
Units of Functionality Diagrams
X
Condition Instance Name
Description
conditionInstanceName is a word or phrase by which the condition instance is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
conditionTypeClassValue
Units of Functionality Diagrams
X
Condition Type Class Value
Description
conditionTypeClassValue is a classification that is valid for a specific ConditionType.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
conditionTypeDescription
Short Name
condDescr
Units of Functionality Diagrams
X
Condition Type Description
Description
conditionTypeDescription is a narrative statement of the meaning of the condition type.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
conditionTypeName
Short Name
condName
Units of Functionality Diagrams
X
Condition Type Name
Description
conditionTypeName is a word by which the condition type is known and can be easily referenced.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
conditionTypePropertyValue
Short Name
propValue
Units of Functionality Diagrams
X
Condition Type Property Value
Description
conditionTypePropertyValue is a property that is valid for a specific ConditionType.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
containedSubstanceJustification Description
Units of Functionality Diagrams
X
Contained Substance Justification Description
Description
containedSubstanceJustificationDescription is a phrase that gives more information on the most important property for the function of the hardware part as designed, that the included substance has.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
contractedBlockOfSerializedItems
Short Name
block
Units of Functionality Diagrams
X
Contracted Block Of Serialized Items
Description
contractedBlockOfSerializedItems identifies an interval of serialized items as known by the customer.
Data Type
SerialNumberRange
Units of Functionality
Property (Attribute)
contractIdentifier
Short Name
contrId
Units of Functionality Diagrams
X
Contract Identifier
Description
contractIdentifier is a string of characters used to uniquely identify a Contract and to differentiate it from other Contracts.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
contractRelationshipType
Short Name
relType
Units of Functionality Diagrams
X
Contract Relationship Type
Description
contractRelationshipType is a classification that defines the type of relationship that is established between two contracts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
correctionFactor
Short Name
factor
Units of Functionality Diagrams
X
Correction Factor
Description
correctionFactor is a value by which the original key performance indicator value must be corrected to meet a specific design or usage of the system related to specific conditions, eg. environment which causes additional stress to the system (sand, extreme temperatures, salty environment).
Data Type
double
Units of Functionality
Property (Attribute)
correctionFactorDate
Short Name
defDate
Units of Functionality Diagrams
X
Correction Factor Date
Description
correctionFactorDate defines the date when the correction factor was identified.
Data Type
DateType
Units of Functionality
Property (Attribute)
correctionFactorJustification
Short Name
just
Units of Functionality Diagrams
X
Correction Factor Justification
Description
correctionFactorJustification is a phrase that gives more information on the reason for the introduction of the correction factor.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
damageDescription
Short Name
dmgDescr
Units of Functionality Diagrams
X
Damage Description
Description
damageDescription is a phrase that gives more information on the expected damage.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
damageFamily
Short Name
dmgFamily
Units of Functionality Diagrams
X
Damage Family
Description
damageFamily is a classification that defines type of damage.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
dataModuleCode
Short Name
dmc
Units of Functionality Diagrams
X
Data Module Code
Description
dataModuleCode is a string of characters used to uniquely identify an S1000DDataModule and to differentiate it from other S1000DDataModules.
Comment
A dataModuleCode must be created in accordance with the rules defined in S1000D.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
dataModuleInfoname
Short Name
infoname
Units of Functionality Diagrams
X
Data Module Infoname
Description
dataModuleInfoname is a word or phrase by which the data module is known and can be easily referenced.
Comment
Equals S1000D element "Infoname".
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
dataModuleIssueNumber
Short Name
dmIssId
Units of Functionality Diagrams
X
Data Module Issue Number
Description
dataModuleIssueNumber is a string of characters used to uniquely identify a data module issue (revision) and to differentiate it from other data module issues.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
dayComponent
Units of Functionality Diagrams
X
Day Component
Description
The day element of the DateType expressed as a value between 1 and 31.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
int
Units of Functionality
Property (Attribute)
descriptorLanguage
Units of Functionality Diagrams
X
Descriptor Language
Description
Classification that determines the language in which the descriptorText is written.
Comment
Source:OASIS PLCS DEXlib.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
descriptorProvidedBy
Units of Functionality Diagrams
X
Descriptor Provided By
Description
The organization that provided the descriptorText.
Comment
Source: OASIS PLCS DEXlib.
Data Type
Organization
Units of Functionality
Property (Attribute)
descriptorProvidedDate
Units of Functionality Diagrams
X
Descriptor Provided Date
Description
The date when the descriptorText was provided.
Comment
Source: OASIS PLCS DEXlib.
Data Type
DateType
Units of Functionality
Property (Attribute)
descriptorText
Units of Functionality Diagrams
X
Descriptor Text
Description
Text that provides further information about the subject under consideration.
Comment
The descriptorText attribute must allow for text in an indentured manner.
Source: OASIS PLCS DEXlib.
Data Type
char
Units of Functionality
Property (Attribute)
detectionMeanAlarmDescription
Short Name
alarmDescr
Units of Functionality Diagrams
X
Detection Mean Alarm Description
Description
detectionMeanAlarmDescription is a phrase that gives more information on the alarm as such.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
detectionMeanDescription
Short Name
detectMnDescr
Units of Functionality Diagrams
X
Detection Mean Description
Description
detectionMeanDescription is a phrase that gives more information on the mean that warns the user or maintainer that a failure has occurred.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
detectionMeanFalseAlarmPresentation
Units of Functionality Diagrams
X
Detection Mean False Alarm Presentation
Description
detectionMeanFalseAlarmPresentation is a phrase that gives more information on how the alarm is presented to the user/maintainer.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
detectionMeanFalseAlarmRate
Units of Functionality Diagrams
X
Detection Mean False Alarm Rate
Description
detectionMeanFalseAlarmRate identifies the percentage (expressed as a decimal value) of all alarms that indicate a malfunction that cannot be verified by maintenance personnel performing follow-on tests.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
detectionMeanType
Short Name
detectMnType
Units of Functionality Diagrams
X
Detection Mean Type
Description
detectionMeanType is a classification that defines the type of test that generates the symptom.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
directMaintenanceCost
Short Name
cost
Units of Functionality Diagrams
X
Direct Maintenance Cost
Description
directMaintenanceCost include shop maintenance man-hours, shop test man-hours, repair cost (incl. required material). Statistical values like MTBF (Mean Time Between Failure) and MTBUR (Mean Time Between Unscheduled Removal) are taken into consideration.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
documentAssignmentRole
Short Name
docRole
Units of Functionality Diagrams
X
Document Assignment Role
Description
documentAssignmentRole is a classification that identifies the role of a document being assigned to something.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
documentIdentifier
Short Name
docId
Units of Functionality Diagrams
X
Document Identifier
Description
documentIdentifier is a string of characters used to uniquely identify an ExternalDocument and to differentiate it from other ExternalDocuments.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
documentIssueDate
Short Name
issDate
Units of Functionality Diagrams
X
Document Issue Date
Description
documentIssueDate defines the date when a specific issue (revision) of a document was issued.
Data Type
DateType
Units of Functionality
Property (Attribute)
documentIssueIdentifier
Short Name
docIssId
Units of Functionality Diagrams
X
Document Issue Identifier
Description
documentIssueIdentifier is a string of characters used to uniquely identify an ExternalDocumentIssue and to differentiate it from other ExternalDocumentIssues.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
documentLocation
Short Name
docLoc
Units of Functionality Diagrams
X
Document Location
Description
documentLocation is a phrase that gives more information on where to find a specific document (issue).
Comment
May be a string that contains a hyperlink to the document (or specific issue of the document).
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
documentPortion
Short Name
docPortion
Units of Functionality Diagrams
X
Document Portion
Description
documentPortion is a phrase that gives a reference to the portion of a document which is of interest in a specific usage.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
documentTitle
Short Name
docTitle
Units of Functionality Diagrams
X
Document Title
Description
documentTitle is a word or phrase by which the document is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
documentType
Short Name
docType
Units of Functionality Diagrams
X
Document Type
Description
documentType is a classification that identifies categories of documents to which individual documents can belong.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
downTime
Short Name
time
Units of Functionality Diagrams
X
Down Time
Description
downTime is the acceptable (maximum) down time (MDT), where down time is the duration where an item is non-operational.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
eventThresholdNumberOfEvent Occurrences
Units of Functionality Diagrams
X
Event Threshold Number Of Event Occurrences
Description
eventThresholdNumberOfEventOccurrences is the number of event occurrences required to initiate the related threshold or trigger.
Data Type
int
Units of Functionality
Property (Attribute)
failureModeDescription
Short Name
fmDescr
Units of Functionality Diagrams
X
Failure Mode Description
Description
failureModeDescription is a phrase that gives more information on the manner in which a failure occurs.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
failureModeDetectionAbilityDescription
Short Name
detectDescr
Units of Functionality Diagrams
X
Failure Mode Detection Ability Description
Description
failureModeDetectionAbilityDescription is a phrase that gives more information on the ability to detect an identified failure mode. The description can include eg, a summary of the available detection means.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
failureModeDetectionAbilityRating
Short Name
detectRtg
Units of Functionality Diagrams
X
Failure Mode Detection Ability Rating
Description
failureModeDetectionAbilityRating is a support classification defining the ability to detect an identified failure mode.
Comment
Qualitative judgment made by the analyst.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
failureModeDetectionRate
Short Name
detectRte
Units of Functionality Diagrams
X
Failure Mode Detection Rate
Description
failureModeDetectionRate defines the percentage of failure modes detected by the defined detection mean.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
failureModeEffect
Units of Functionality Diagrams
X
Failure Mode Effect
Description
failureModeEffect is a phrase that gives more information on the consequences that a failure mode can have on the local/next higher/end item operation, function, or status.
Comment
Local effect -The consequences of each postulated failure/damage mode affecting the LSA candidate must be described along with any second order effects that result. Potential conditions where the failure/damage of one item results in a change of the conditional failure probability or effect of a second item must be identified. It is possible for the "local effect" to be the failure/damage mode itself. Next higher effect -The consequences of each failure/damage mode affecting the next higher indenture level must be described. End effect -The effect of each failure/damage mode upon the essential functions(s) affecting system/equipment operating capability and mission completion capability must be determined. The end effect described may be the result of a double failure. For example, failure of a safety device may result in a catastrophic end effect only in the event that both the prime function goes beyond the limit for which the safety device is set, and the safety device fails.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
failureModeEffectLevel
Short Name
efctLevel
Units of Functionality Diagrams
X
Failure Mode Effect Level
Description
failureModeEffectLevel is classification that identifies the higher indenture level that will be affected by the failure mode under consideration.
Data Type
Type ClassificationType
Units of Functionality
Property (Attribute)
failureModeFailureRate
Short Name
failRte
Units of Functionality Diagrams
X
Failure Mode Failure Rate
Description
failureModeFailureRate is the total number of failures within a population of the item under analysis divided by the total functional life of the population during the measurement interval.
Comment
The definition holds for time, rounds, miles, cycles or other measures of life units.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
failureModeIdentifier
Short Name
fmId
Units of Functionality Diagrams
X
Failure Mode Identifier
Description
failureModeIdentifier is a string of characters used to uniquely identify a FailureMode and to differentiate it from other FailureModes.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
failureModeIsolationRate
Short Name
isolRte
Units of Functionality Diagrams
X
Failure Mode Isolation Rate
Description
failureModeIsolationRate defines the percentage of detected failures that are associated without ambiguity to the failure of an identified item or component.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
failureModeLocalizationAbilityDescription
Short Name
lznDescr
Units of Functionality Diagrams
X
Failure Mode Localization Ability Description
Description
failureModeLocalizationAbilityDescription is a phrase that gives more information on the ability to localize an identified failure mode. The description can include a summary of localization means available or required.
Comment
failureModeLocalizationAbilityDescription is generally complementary to failureModeDetectionAbilityRating.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
failureModeLocalizationAbilityRating
Short Name
lznRtg
Units of Functionality Diagrams
X
Failure Mode Localization Ability Rating
Description
failureModeLocalizationAbilityRating is a support classification defining the ability to localize an identified failure mode.
Comment
Qualitative judgment made by the analyst.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
failureRate
Short Name
rate
Units of Functionality Diagrams
X
Failure Rate
Description
failureRate is the total number of failures within a population of an LSA candidate item divided by the total functional life of the population during the measurement interval.
Comment
The definition holds for time, rounds, miles, cycles or other measures of life units.
Refer to GEIA-0007, failure_rate_type
Data Type
PropertyType
Units of Functionality
Property (Attribute)
failuresPerOperatingHour
Short Name
nr
Units of Functionality Diagrams
X
Failures Per Operating Hour
Description
failuresPerOperatingHour is the failure rate expressed in failures per operating hour.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
fixedResourceMarker
Short Name
fixed
Units of Functionality Diagrams
X
Fixed Resource Marker
Description
fixedResourceMarker is a classification that identifies that no other resource than the specified is allowed to be used in the task/subtask.
Data Type
boolean
Units of Functionality
Property (Attribute)
functionalFailureDescription
Short Name
funcFailDescr
Units of Functionality Diagrams
X
Functional Failure Description
Description
functionalFailureDescription is a phrase that gives more information on a possible functional failure identified during preventive maintenance analysis (PMA).
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
functionalFailureEffectCriticality
Short Name
efctCritic
Units of Functionality Diagrams
X
Functional Failure Effect Criticality
Description
functionalFailureEffectCriticality is a classification that identifies the most serious impact that the functional failure will have on the end item.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementFunctionalReplaceability
Units of Functionality Diagrams
X
Hardware Element Functional Replaceability
Description
hardwareElementFunctionalReplaceability is a design classification that indicates whether a part is replaceable at its functional location defined from a technical standpoint, independent of customer maintenance concepts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementFunctionalReplaceabilityStrategy
Units of Functionality Diagrams
X
Data element hardware Element Functional Replaceability Strategy
Description
hardwareElementFunctionalReplaceabilityStrategy is a support classification that defines the replaceability strategy chosen for a specific customer and maintenance concept. Replaceability strategy can include information about the maintenance level, at which the replacement task is to be performed.
Data Type
Type ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementRepairability
Short Name
rep
Units of Functionality Diagrams
X
Hardware Element Repairability
Description
hardwareElementRepairability is a design classification that indicates whether a part is repairable from a technical standpoint, independent of customer maintenance concepts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementRepairabilityStrategy
Short Name
rpy
Units of Functionality Diagrams
X
Hardware Element Repairability Strategy
Description
hardwareElementRepairabilityStrategy is a support classification that defines the repairability strategy chosen for a specific customer and maintenance concept.
Comment
Repairability strategy can include information on which maintenance level the repair is to be performed.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementStructuralIndicator
Short Name
ssi
Units of Functionality Diagrams
X
Hardware Element Structural Indicator
Description
hardwareElementStructuralIndicator is a design classification that defines how important the breakdown element is to structural integrity.
Comment
Note 1: A Structure Significant Item (SSI) is an item which was identified by any selection process coming from a Scheduled Maintenance Analysis Procedure like MSG-3 or S4000P. For this item, a Scheduled Maintenance Analysis (SMA) will be performed.
Note 2: A Structural Item (SI) is part of the systems bodywork.
Note 3: A Structural Detail (SD), also named Significant Detail in the S4000P, is a limited area of an SSI or a local spot being also part of the whole SSI. In contrast to an SSI, the SD is not identified by an own identifier (eg an own part number). Therefore these SD's must be defined and documented on a respective SSI drawing. For identification within any breakdown structure, an additional artificial breakdown element identifier can be addressed.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwareElementType
Short Name
beType
Units of Functionality Diagrams
X
Hardware Element Type
Description
hardwareElementType is a design classification that identifies further specialization of a hardware element.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartConsumptionRate
Short Name
consRte
Units of Functionality Diagrams
X
Hardware Part Consumption Rate
Description
hardwarePartConsumptionRate is a support characteristic which defines the number of times that the hardware part is replaced in 100 repairs of the next higher assembly.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
hardwarePartElectromagneticIncompatible
Short Name
emi
Units of Functionality Diagrams
X
Hardware Part Electromagnetic Incompatible
Description
hardwarePartElectromagneticIncompatible is a design classification which identifies the ability of an electrical equipment to function satisfactorily in its electromagnetic environment without inadmissibly influencing this environment to which also other equipment belongs.
Data Type
boolean
Units of Functionality
Property (Attribute)
hardwarePartElectromagneticSensitive
Short Name
ems
Units of Functionality Diagrams
X
Hardware Part Electromagnetic Sensitive
Description
hardwarePartElectromagneticSensitive is a design classification which identifies electronic components subject to catastrophic failure, major characteristic change or performance degradation from influences of electromagnetic fields.
Data Type
boolean
Units of Functionality
Property (Attribute)
hardwarePartElectrostaticSensitive
Short Name
ess
Units of Functionality Diagrams
X
Hardware Part Electrostatic Sensitive
Description
hardwarePartElectrostaticSensitive is a design classification which identifies electronic components subject to catastrophic failure, major characteristic change or performance degradation from influences of electrostatic fields and/or electrical charges.
Data Type
boolean
Units of Functionality
Property (Attribute)
hardwarePartEnvironmentalAspectInUseClass
Short Name
envmtInUseClass
Units of Functionality Diagrams
X
Hardware Part Environmental Aspect In Use Class
Description
hardwarePartEnvironmentalAspectInUseClass is a support classification which identifies environment aspects that must to be considered during use of the hardware part.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartEnvironmentalAspectPlannedDisposalClass
Short Name
envmtDispClass
Units of Functionality Diagrams
X
Hardware Part Environmental Aspect Planned Disposal Class
Description
hardwarePartEnvironmentalAspectPlannedDisposalClass is a support classification which identifies environment aspects that must to be considered during planned disposal of the hardware part.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartFitmentRequirement
Short Name
ftc
Units of Functionality Diagrams
X
Hardware Part Fitment Requirement
Description
hardwarePartFitmentRequirement is a design classification which identifies that an item cannot be fitted in its ‘as supplied’ state but must undergo some operation before, or during, installation.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartHazardousClass
Short Name
haz
Units of Functionality Diagrams
X
Hardware Part Hazardous Class
Description
Definition hardwarePartHazardousClass is a design classification which identifies a design part as capable of posing a significant risk to health, safety or property during transportation, handing or storage.
Comment
The Substance Identification Numbers listed in Chapter 2 of the United Nations Recommendations on the Transport of Dangerous Goods ST/SG/AC.10/1/Rev5, must be used to enable integration with other ASD specifications.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartLogisticsCategory
Short Name
logCat
Units of Functionality Diagrams
X
Hardware Part Logistics Category
Description
hardwarePartLogisticsCategory is a support classification that defines the role of a hardware part as designed in the context of product support.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartMagneticSensitive
Short Name
mse
Units of Functionality Diagrams
X
Hardware Part Magnetic Sensitive
Description
hardwarePartMagneticSensitive is a design classification which identifies electronic components subject to catastrophic failure, major characteristic change or performance degradation from influences of magnetic fields.
Data Type
boolean
Units of Functionality
Property (Attribute)
hardwarePartMaintenanceStart
Short Name
maintStart
Units of Functionality Diagrams
X
Hardware Part Maintenance Start
Description
hardwarePartMaintenanceStart is a support classification which defines when maintenance scheduling must be initiated for a realized part.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartOperationalAuthorizedLife
Short Name
opAul
Units of Functionality Diagrams
X
Hardware Part Operational Authorized Life
Description
hardwarePartOperationalAuthorizedLife is a design characteristic which identifies the maximum usage limit for which an item may be operated, and upon reaching this limit, any further usage of the item must be re-authorized.
Data Type
AuthorizedLife
Units of Functionality
Property (Attribute)
hardwarePartRadiationSensitive
Short Name
rse
Units of Functionality Diagrams
X
Hardware Part Radiation Sensitive
Description
hardwarePartRadiationSensitive is a design classification which identifies electronic components subject to catastrophic failure, major characteristic change or performance degradation from influences of radioactive radiation.
Data Type
boolean
Units of Functionality
Property (Attribute)
hardwarePartRepairability
Short Name
rep
Units of Functionality Diagrams
X
Hardware Part Repairability
Description
hardwarePartRepairability is a support classification which defines whether the HardwarePartAsDesigned is repairable from a technical perspective (eg, a vendor/supplier standpoint) independent of customer maintenance concepts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartRepairabilityStrategy
Short Name
rpy
Units of Functionality Diagrams
X
Hardware Part Repairability Strategy
Description
hardwarePartRepairabilityStrategy is a support classification which defines the repairability strategy chosen for a specific customer and maintenance concept. Repairability strategy can include information on which maintenance level the repair is to be performed.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
hardwarePartScrapRate
Short Name
sra
Units of Functionality Diagrams
X
Hardware Part Scrap Rate
Description
hardwarePartScrapRate is a support characteristic of a hardware part which defines the percentage of repairable units which, when removed from service, will be found to be beyond economic repair and therefore have to be scrapped.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
hardwarePartWasteProductsInUseDisposalDescription
Short Name
inUseDispDescr
Units of Functionality Diagrams
X
Hardware Part Waste Products In Use Disposal Description
Description
hardwarePartWasteProductsInUseDisposalDescription is a phrase that gives more information on how waste products for an individual part need to be managed when the part is disposed of according to the procedure during use or after being used.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
hardwarePartWasteProductsPlannedDisposalDescription
Short Name
plndDispDescr
Units of Functionality Diagrams
X
Hardware Part Waste Products Planned Disposal Description
Description
hardwarePartWasteProductsPlannedDisposalDescription is a phrase that gives more information on how waste products need to be managed when the entire population of a part is disposed of according to the procedure for planned disposal.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
identifier
Units of Functionality Diagrams
X
Identifier
Description
The text that conveys the assigned identifier.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
char
Units of Functionality
Property (Attribute)
identifierClassifier
Units of Functionality Diagrams
X
Identifier Classifier
Description
Classification that determines the type of identifier being defined.
Comment
Source: OASIS PLCS DEXlib.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
identifierSetBy
Units of Functionality Diagrams
X
Identifier Set By
Description
Defines the organization that determined ("owns") the assigned identifier.
Comment
The identifierSetBy relates to an Organization as the data type. The Organization class is defined in UoF Project, and contains an organizationIdentifier (mandatory) and an organizationName (optional).
Source: OASIS PLCS DEXlib.
Data Type
Organization
Units of Functionality
Property (Attribute)
informationCode
Short Name
infoCode
Units of Functionality Diagrams
X
Information Code
Description
informationCode is a classification which identifies type of task according to S1000D.
Comment
S1000D information codes must be used to enable integration with other ASD specifications.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
keyPerformanceIndicatorMethod
Short Name
kpiMthd
Units of Functionality Diagrams
X
Key Performance Indicator Method
Description
keyPerformanceIndicatorMethod is a phrase that gives more information on the method by which the key performance indicator value has been derived.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
keyPerformanceIndicatorPercentile
Short Name
kpiPctl
Units of Functionality Diagrams
X
Key Performance Indicator Percentile
Description
keyPerformanceIndicatorPercentile is the percentage of all occurrences related to a specified key performance indicator that must be within the limit of the value defined for the key performance indicator.
Comment
A customer requirement is that 98% of all replacement tasks must be performed below a specified value of two hours (= maximum replacement time).
Data Type
PropertyType
Units of Functionality
Property (Attribute)
keyPerformanceIndicatorStatus
Short Name
kpiStatus
Units of Functionality Diagrams
X
Key Performance Indicator Status
Description
keyPerformanceIndicatorStatus is a classification defining the status of acceptance of the recorded value for the key performance indicator.
Comment
Includes purchase price, installation cost, operating costs, maintenance and upgrade costs, and remaining (residual or salvage) value at the end of ownership or its useful life.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
lifeAuthorizingOrganization
Units of Functionality Diagrams
X
Life Authorizing Organization
Description
lifeAuthorizingOrganization is a characteristicMetadata which defines the organization that authorized the maximum life limit.
Data Type
Organization
Units of Functionality
Property (Attribute)
lifeCycleCost
Short Name
cost
Units of Functionality Diagrams
X
Life Cycle Cost
Description
lifeCycleCost is the sum of all recurring and non-recurring (one-time) costs over the full life cycle of the LSA candidate.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
lowerBound
Units of Functionality Diagrams
X
Lower Bound
Description
lowerBound is a characteristic that represents the first valid serial number.
Data Type
char
Units of Functionality
Property (Attribute)
lowerLimitValue
Units of Functionality Diagrams
X
Lower Limit Value
Description
The lower limit of a value range.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
lowerOffsetValue
Units of Functionality Diagrams
X
Lower Offset Value
Description
The lower limit defined as the lower offset value from the nominal value (value + lower limit).
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
LSACandidateIndicator
Units of Functionality Diagrams
X
LSA Candidate Indicator
Description
LSACandidateIndicator is a support classification which defines the depth of analysis that will be performed on the candidate item.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
LSACandidateMaintenanceConcept
Units of Functionality Diagrams
X
LSA Candidate Maintenance Concept
Description
LSACandidateMaintenanceConcept is a statement of maintenance considerations, constraints and strategy for the operational support that governs the maintenance levels and type of maintenance activities to be carried out for the LSA candidate under analysis.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
LSACandidateMaintenanceSolution
Units of Functionality Diagrams
X
LSA Candidate Maintenance Solution
Description
LSACandidateMaintenanceSolution is a statement of maintenance activities and maintenance levels that has been decided for the LSA candidate under analysis.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
LSACandidateRationale
Units of Functionality Diagrams
X
LSA Candidate Rationale
Description
LSACandidateRationale is a phrase that gives more information on the reason for ’full’, ’partial’ or ’non’ LSA Candidate indicator selection.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
LSAFailureModeDistributionRating
Units of Functionality Diagrams
X
LSA Failure Mode Distribution Rating
Description
LSAFailureModeDistributionRating is a support classification that identifies the rating for the occurrence of an individual LSA failure mode in comparison to the entire population of LSA failure modes identified for the item under analysis.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
LSAFailureModeDistributionRatio
Units of Functionality Diagrams
X
LSA Failure Mode Distribution Ratio
Description
LSAFailureModeDistributionRatio identifies the fraction of an individual LSA failure mode in relation to the entire population of LSA failure modes identified for the item under analysis.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
maintenanceFreeOperatingPeriod
Short Name
per
Units of Functionality Diagrams
X
Maintenance Free Operating Period
Description
maintenanceFreeOperatingPeriod is the acceptable (minimum) maintenance free operating period, where maintenance free operating period is the interval in which no maintenance actions occur.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
maintenanceLevelCapabilityDescription
Short Name
mlvCapDescr
Units of Functionality Diagrams
X
Maintenance Level Capability Description
Description
maintenanceLevelCapabilityDescription is a phrase that gives more information on eg. defined capabilities in terms of personnel, availability of special facilities, time limits and environmental conditions to be assumed. These capabilities are the basis in determining the functions to be accomplished at the respective maintenance level.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
maintenanceLevelIdentifier
Short Name
mlvId
Units of Functionality Diagrams
X
Maintenance Level Identifier
Description
maintenanceLevelIdentifier is a string of characters used to uniquely identify a MaintenanceLevel and to differentiate it from other MaintenanceLevels.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
maintenanceLevelName
Short Name
name
Units of Functionality Diagrams
X
Maintenance Level Name
Description
maintenanceLevelName is a word or phrase by which the maintenance level is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
maintenanceLocationDescription
Short Name
mLocDescr
Units of Functionality Diagrams
X
Maintenance Location Description
Description
maintenanceLocationDescription is a phrase that gives more information on eg. actual capabilities in terms of personnel, availability of special facilities, time limits and environmental conditions.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
maintenanceLocationIdentifier
Short Name
mLocId
Units of Functionality Diagrams
X
Maintenance Location Identifier
Description
maintenanceLocationIdentifier is a string of characters used to uniquely identify a MaintenanceLocation and to differentiate it from other MaintenanceLocations.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
maintenanceLocationName
Short Name
name
Units of Functionality Diagrams
X
Maintenance Location Name
Description
maintenanceLocationName is a word or phrase by which the maintenance location is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
maintenanceManHoursPerOperatingHour
Short Name
mh
Units of Functionality Diagrams
X
Maintenance Man Hours Per Operating Hour
Description
maintenanceManHoursPerOperatingHour is the (maximum) acceptable maintenance man hours per operating hour, where maintenance man hours per operating hour is the ratio of maintenance man hours expended to the operating interval (as defined by the measurement base) of the system/equipment.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
maintenanceSignificantOrRelevantIndicator
Units of Functionality Diagrams
X
Maintenance Significant Or Relevant Indicator
Description
maintenanceSignificantOrRelevantIndicator is a support classification of a BreakdownElement as a candidate for maintenance as a result of scheduled maintenance analyses or failure modes and effects analyses.
Comment
A maintenance significant item is an item which was identified by any selection process coming from a scheduled maintenance analysis like MSG-3 or S4000P. For this type of item a scheduled maintenance task will be documented. A maintenance relevant item is an item which can be repaired or replaced as a result of failure or damage.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
meanTimeBetweenFailure
Short Name
mt
Units of Functionality Diagrams
X
Mean Time Between Failure
Description
meanTimeBetweenFailure is the (minimum) mean time between failure (MTBF), where the MTBF is the total operational life of a population of an LSA candidate divided by the total number of failures within the population during a particular measurement interval.
Comment
The definition holds for time, rounds, miles, events, or other measure of life units.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
meanTimeBetweenUnscheduledRemoval
Short Name
mt
Units of Functionality Diagrams
X
Mean Time Between Unscheduled Removal
Description
meanTimeBetweenUnscheduledRemoval is the minimum mean time between unscheduled removal, where mean time between unscheduled removal is the total number of operational units (eg, miles, rounds, hours) divided by the total number of items removed from that system during a stated period of time.
Comment
This term is defined to exclude removals either being scheduled or performed to facilitate other maintenance and removals for product improvement.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
meanTimeToRepair
Short Name
mt
Units of Functionality Diagrams
X
Mean Time To Repair
Description
meanTimeToRepair is the (maximum) mean time to repair (MTTR), where MTTR is the total elapsed time for corrective maintenance divided by the total number of corrective maintenance actions during a given period of time.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
monthComponent
Units of Functionality Diagrams
X
Month Component
Description
The month element of the DateType expressed as a value between 1 and 12.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
int
Units of Functionality
Property (Attribute)
nominalValue
Units of Functionality Diagrams
X
Nominal Value
Description
Specifies the single value that is the base value for specifying the range.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
nonConformanceDescription
Short Name
nonConfDescr
Units of Functionality Diagrams
X
Non Conformance Description
Description
nonConformanceDescription is a phrase that gives more information on how the related item does not comply with its requirements.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
nonConformanceRestriction
Short Name
nonConfRestr
Units of Functionality Diagrams
X
Non Conformance Restriction
Description
nonConformanceRestriction is a phrase that gives more information on how the use of the related item restricts the specified capabilities of the item in which it is contained.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
nonConformanceType
Short Name
nonConfType
Units of Functionality Diagrams
X
Non Conformance Type
Description
nonConformanceType is a classification that identifies in which way the related item does not comply with its requirements.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
numberOfOperatingLocations
Short Name
nrOfLoc
Units of Functionality Diagrams
X
Number Of Operating Locations
Description
numberOfOperatingLocations is the number of locations which will receive and operate the contracted product variant.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
operatingLocationDescription
Short Name
opLocDescr
Units of Functionality Diagrams
X
Operating Location Description
Description
operatingLocationDescription is a phrase that gives more information on eg, actual operating and environmental conditions.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
operatingLocationIdentifier
Short Name
opLocId
Units of Functionality Diagrams
X
Operating Location Identifier
Description
operatingLocationIdentifier is a string of characters used to uniquely identify an OperatingLocation and to differentiate it from other OperatingLocations.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
operatingLocationName
Short Name
name
Units of Functionality Diagrams
X
Operating Location Name
Description
operatingLocationName is a word or phrase by which the operating location is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
operatingLocationTypeDescription
Short Name
opTypeDescr
Units of Functionality Diagrams
X
Operating Location Type Description
Description
operatingLocationTypeDescription is a phrase that gives more information on eg, operating and environmental conditions to be assumed.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
operatingLocationTypeIdentifier
Short Name
opTypeId
Units of Functionality Diagrams
X
Operating Location Type Identifier
Description
operatingLocationTypeIdentifier is a string of characters used to uniquely identify an OperatingLocationType and to differentiate it from other OperatingLocationTypes.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
operatingLocationTypeName
Short Name
name
Units of Functionality Diagrams
X
Operating Location Type Name
Description
operatingLocationTypeName is a word or phrase by which the operating location type is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
operatingRequirementAtOperatingLocation
Short Name
opReq
Units of Functionality Diagrams
X
Operating Requirement At Operating Location
Description
operatingRequirementAtOperatingLocation is the (annual) operating requirement per operating location and contracted product.
Comment
Annual operating requirements may be measurement based, generally operating hours, but also other measurement bases can be possible.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
operatingRequirementAtOperatingLocationType
Short Name
opReq
Units of Functionality Diagrams
X
Operating Requirement At Operating Location Type
Description
operatingRequirementAtOperatingLocationType is the (annual) operating requirement per operating location type and contracted product.
Comment
Annual operating requirements may be measurement based, generally operating hours, but also other measurement bases can be possible.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
organizationAssignmentRole
Short Name
orgRole
Units of Functionality Diagrams
X
Organization Assignment Role
Description
organizationAssignmentRole is a classification that identifies the role of the organization being assigned to an object in the LSA dataset.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
organizationIdentifier
Short Name
orgId
Units of Functionality Diagrams
X
Organization Identifier
Description
Definition organizationIdentifier is a string of characters used to uniquely identify an organization and to differentiate it from other organizations.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
organizationName
Short Name
name
Units of Functionality Diagrams
X
Organization Name
Description
organizationName is a word or phrase by which the organization is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
packagedTask
Short Name
packTask
Units of Functionality Diagrams
X
Packaged Task
Description
packagedTask identifies if the task is created in order to group a set of previously defined tasks.
Data Type
boolean
Units of Functionality
Property (Attribute)
partDemilitarizationClass
Short Name
dec
Units of Functionality Diagrams
X
Part Demilitarization Class
Description
partDemilitarizationClass is a controlled item classification defining special measures to be taken when a part is being disposed of, eg. render them useless for military purposes or destroy any indications of military purposes or performance characteristics.
Comment
Examples are from S2000M.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
partIdentifier
Short Name
partId
Units of Functionality Diagrams
X
Part Identifier
Description
partIdentifier is a string of characters that are unique to the issuing organization which is used to designate a PartAsDesigned and to differentiate it from other designed parts.
Comment
Includes manufacturer’s part, drawing, model, type, or source controlling numbers.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
partMaturityClass
Short Name
maturity
Units of Functionality Diagrams
X
Part Maturity Class
Description
partMaturityClass is a support classification defining the maturity of the part in order to determine the certainty by which the parts characteristics can be valued.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
partName
Short Name
name
Units of Functionality Diagrams
X
Part Name
Description
partName is a word or phrase by which the designed part is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
partObsolescenceRiskAssessment
Short Name
obsRisk
Units of Functionality Diagrams
X
Part Obsolescence Risk Assessment
Description
partObsolescenceRiskAssessment is a support characteristic describing the risk associated with loss of the part in the supply chain due to factors such as termination of manufacturing, replacement with a different model, etc.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
partsListEntryIdentifier
Short Name
posId
Units of Functionality Diagrams
X
Parts List Entry Identifier
Description
partsListEntryIdentifier is a string of characters providing a relative position within the parts list.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
partsListRevisionIdentifier
Short Name
pListRevId
Units of Functionality Diagrams
X
Parts List Revision Identifier
Description
partsListRevisionIdentifier is a string of characters used to uniquely identify a revision of a PartAsDesignedPartsList partsListType and to differentiate it from other PartAsDesignedPartsList revisions of the same partsListType.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
partsListType
Short Name
pListType
Units of Functionality Diagrams
X
Parts List Type
Description
partsListType is a classification which identifies the context and intended use of the list of parts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
partSpecialHandlingRequirement
Short Name
phstReq
Units of Functionality Diagrams
X
Part Special Handling Requirement
Description
partSpecialHandlingRequirement is a phrase that gives more information on requirements for special handling of the part.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
physicalReplaceability
Short Name
repl
Units of Functionality Diagrams
X
Physical Replaceability
Description
physicalReplaceability is a classification which identifies whether a part is interchangeable in a specific assembly.
Comment
This classification is done from a technical standpoint (ie, a vendor/supplier standpoint) and is independent of customer maintenance concepts.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
physicalReplaceabilityStrategy
Short Name
rly
Units of Functionality Diagrams
X
Physical Replaceability Strategy
Description
physicalReplaceabilityStrategy is a classification which identifies the replaceability strategy chosen for a specific customer and maintenance concept. Replaceability strategy can include information about the maintenance level, at which the replacement task is to be performed.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
productIdentifier
Short Name
prodId
Units of Functionality Diagrams
X
Product Identifier
Description
productIdentifier is a string of characters used to uniquely identify a Product and to differentiate it from other Products.
Comment
An example of a type of productIdentifier is the GEIA-STD-0007 End Item Acronym Code.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
productName
Short Name
name
Units of Functionality Diagrams
X
Product Name
Description
productName is a word or phrase by which the product is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
productServiceLife
Short Name
life
Units of Functionality Diagrams
X
Product Service Life
Description
productServiceLife defines the number of years that the LSA candidate is expected to be in service.
Comment
Other measures than years can be used.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
productUsagePhase
Short Name
usagePhase
Units of Functionality Diagrams
X
Product Usage Phase
Description
productUsagePhase is a classification which identifies phases during the products in-service phase.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
productVariantIdentifier
Short Name
prodVarId
Units of Functionality Diagrams
X
Product Variant Identifier
Description
productVariantIdentifier is a string of characters used to uniquely identify a ProductVariant and to differentiate it from other ProductVariants.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
productVariantName
Short Name
name
Units of Functionality Diagrams
X
Product Variant Name
Description
productVariantName is a word or phrase by which the product variant is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
projectIdentifier
Short Name
projId
Units of Functionality Diagrams
X
Project Identifier
Description
projectIdentifier is a string of characters used to uniquely identify a Project and to differentiate it from other Projects.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
projectName
Short Name
name
Units of Functionality Diagrams
X
Project Name
Description
projectName is a word or phrase by which the project is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
publicationModuleCode
Short Name
pmc
Units of Functionality Diagrams
X
Publication Module Code
Description
publicationModuleCode is a string of characters used to uniquely identify an S1000DPublicationModule and to differentiate it from other S1000DPublicationModules.
Comment
A publicationModuleCode must be created in accordance with the rules defined in S1000D.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
publicationModuleIssueNumber
Short Name
pmIssId
Units of Functionality Diagrams
X
Publication Module Issue Number
Description
publicationModuleIssueNumber is a string of characters used to uniquely identify a publication module issue (revision) and to differentiate it from other publication module issues.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
publicationModuleTitle
Short Name
pmTitle
Units of Functionality Diagrams
X
Publication Module Title
Description
publicationModuleTitle is a word or phrase by which the publication module is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
quantityOfChildElement
Short Name
qty
Units of Functionality Diagrams
X
Quantity Of Child Element
Description
quantityOfChildElement is the amount that a child element is used in its parent element within a parent/child relationship.
Comment
If no value is given, it must be interpreted as value "1" with a unit of "each". For as required amounts, the text property is used with "As Required" or other text as appropriate.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
quantityOfContainedSubstance
Short Name
qty
Units of Functionality Diagrams
X
Quantity Of Contained Substance
Description
quantityOfContainedSubstance is the amount of the substance included in a HardwarePartAsDesigned
Data Type
PropertyType
Units of Functionality
Property (Attribute)
quantityOfContractedProductVariant
Short Name
qty
Units of Functionality Diagrams
X
Quantity Of Contracted Product Variant
Description
quantityOfContractedProductVariant is the amount of a product variant included in a contract.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
quantityOfProductVariantAtOperatingLocation
Short Name
qty
Units of Functionality Diagrams
X
Quantity Of Product Variant At Operating Location
Description
quantityOfProductVariantAtOperatingLocation is the number of serialized items, of a specific product variant, that is to be operated at a specific operating location.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
quantityOfProductVariantAtOperatingLocationType
Short Name
qty
Units of Functionality Diagrams
X
Quantity Of Product Variant At Operating Location Type
Description
quantityOfProductVariantAtOperatingLocationType is the number of serialized items, of a specific product variant, that is to be operated at a specific operating location type.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
referenceDesignator
Short Name
rfd
Units of Functionality Diagrams
X
Reference Designator
Description
referenceDesignator is a string of characters used to uniquely identify the location of a child element within a parent element.
Comment
referenceDesignator serves as a cross reference between parts contained in wiring diagrams, hydraulic systems etc. and the Illustrated Parts Catalogue (IPC). Letters, numbers or symbols are used to uniquely identify and locate discrete units, portions thereof and basic parts of a specific component.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
remarkText
Short Name
text
Units of Functionality Diagrams
X
Remark Text
Description
remarkText is a phrase that provides the user with information that is helpful but does not belong to the immediate subject.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
remarkType
Short Name
rmkType
Units of Functionality Diagrams
X
Remark Type
Description
remarkType is a classification that defines the purpose of the remark.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
replacementTime
Short Name
time
Units of Functionality Diagrams
X
Replacement Time
Description
replacementTime is the duration of the replacement of a (eg faulty) component within any technical system by another (eg new) component.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
resourceSpecificationDescription
Short Name
resDescr
Units of Functionality Diagrams
X
Resource Specification Description
Description
resourceSpecificationDescription is a phrase that gives more information on the specified resource needed to perform one or many tasks.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
resourceSpecificationIdentifier
Short Name
resSpecId
Units of Functionality Diagrams
X
Resource Specification Identifier
Description
resourceSpecificationIdentifier is a string of characters used to uniquely identify a ResourceSpecification and to differentiate it from other ResourceSpecifications.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
resourceSpecificationName
Short Name
name
Units of Functionality Diagrams
X
Resource Specification Name
Description
resourceSpecificationName is a word or phrase by which the resource specification is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
samplingMethodDescription
Short Name
samplDescr
Units of Functionality Diagrams
X
Sampling Method Description
Description
samplingMethodDescription is a phrase that gives more information on the sampling method used.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
samplingRatio
Short Name
samplRo
Units of Functionality Diagrams
X
Sampling Ratio
Description
samplingRatio is the number of samples over the total population expressed as a ratio, eg, 0,1 (equals 10%).
Comment
The value must be represent as decimal, even though it should have been a fraction.
Data Type
double
Units of Functionality
Property (Attribute)
samplingValue
Short Name
samplValue
Units of Functionality Diagrams
X
Sampling Value
Description
samplingValue the number of samples over the total population expressed as a value, eg, 10 aircraft.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
scheduledMaintenanceInterval
Short Name
int
Units of Functionality Diagrams
X
Scheduled Maintenance Interval
Description
scheduledMaintenanceInterval is the (minimum) number of operational units (eg rounds, miles, hours) between scheduled maintenance.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
securityClass
Short Name
scc
Units of Functionality Diagrams
X
Security Class
Description
securityClass is a classification that defines the level of confidentiality.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
shopProcessingTime
Short Name
time
Units of Functionality Diagrams
X
Shop Processing Time
Description
shopProcessingTime is the duration from the start of the repair activities in the repair shop until the closing of the repair procedure without considering any shipping and delay times.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
skillCode
Short Name
skillCode
Units of Functionality Diagrams
X
Skill Code
Description
skillCode is a string of characters used to uniquely identify a Skill and to differentiate it from other Skills.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
skillLevelDescription
Short Name
skillLevDescr
Units of Functionality Diagrams
X
Skill Level Description
Description
skillLevelDescription is a phrase that gives more information on the identified skill level.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
skillLevelName
Short Name
name
Units of Functionality Diagrams
X
Skill Level Name
Description
skillLevelName is a classification which identifies competency level.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
softwareElementModificationFrequency
Short Name
modFreq
Units of Functionality Diagrams
X
Software Element Modification Frequency
Description
softwareElementModificationFrequency is a support characteristic defining the expected frequency that the SoftwarePart will be modified.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
softwareElementSize
Short Name
swSize
Units of Functionality Diagrams
X
Software Element Size
Description
softwareElementSize is a design characteristic defining the expected size of the SoftwarePart for this particular SoftwareElementRevision.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
softwareElementType
Short Name
beType
Units of Functionality Diagrams
X
Software Element Type
Description
softwareElementType is a design classification that identifies further specialization of a software element.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
softwarePartSize
Short Name
swSize
Units of Functionality Diagrams
X
Software Part Size
Description
softwarePartSize is the actual size of a software part.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
softwareType
Short Name
swType
Units of Functionality Diagrams
X
Software Type
Description
softwareType is a design classification which identifies if the software and/or data can be loaded/unloaded to/from the related hardware part.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
specialEventDescription
Short Name
evntDescr
Units of Functionality Diagrams
X
Special Event Description
Description
specialEventDescription is a phrase that gives more information on the special event that can cause a related damage mode.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
specialEventGroup
Short Name
evntGrp
Units of Functionality Diagrams
X
Special Event Group
Description
specialEventGroup is a classification used for the grouping of special events.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
specialEventOccurrenceRate
Short Name
occRte
Units of Functionality Diagrams
X
Special Event Occurrence Rate
Description
specialEventOccurrenceRate is a quantification of how often a specific special event will occur.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
specialEventOccurrenceRating
Short Name
occRtg
Units of Functionality Diagrams
X
Special Event Occurrence Rating
Description
specialEventOccurrenceRating is a classification that qualifies how often a specific special event will occur.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
specialEventTitle
Short Name
evntTitle
Units of Functionality Diagrams
X
Special Event Title
Description
specialEventTitle is a classification which identifies the title (name) by which a special event is known.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
substanceCharacteristicsRecordingDate
Short Name
recDate
Units of Functionality Diagrams
X
Substance Characteristics Recording Date
Description
substanceCharacteristicsRecordingDate defines the date of the latest changes to the substance characteristics data.
Data Type
DateType
Units of Functionality
Property (Attribute)
substanceDescription
Short Name
subsDescr
Units of Functionality Diagrams
X
Substance Description
Description
substanceDescription is a phrase that gives more information on the substance used in one or many hardware parts.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
substanceIdentifier
Short Name
subsId
Units of Functionality Diagrams
X
Substance Identifier
Description
substanceIdentifier is a string of characters, unique to the issuing organization used to designate the substance and to differentiate it from other similar substances.
Comment
One source for substance identifiers can be Chemical Abstract Substance Registry Numbers (often referred to as a CAS Number). Refer to www.cas.org.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
substanceName
Short Name
name
Units of Functionality Diagrams
X
Substance Name
Description
substanceName is a word or phrase by which a substance is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
substanceRiskDescription
Short Name
riskDescr
Units of Functionality Diagrams
X
Substance Risk Description
Description
substanceRiskDescription is a phrase that describes risks associated with the substance.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
substanceRiskFactor
Short Name
riskFactor
Units of Functionality Diagrams
X
Substance Risk Factor
Description
substanceRiskFactor is a classification which identifies possible risks associated with substance usage.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
substanceUsageCategory
Short Name
usageCat
Units of Functionality Diagrams
X
Substance Usage Category
Description
substanceUsageCategory is a classification which identifies possible limitations in substance usage.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
subtaskAcceptanceParameterDescription
Short Name
paraDescr
Units of Functionality Diagrams
X
Subtask Acceptance Parameter Description
Description
subtaskAcceptanceParameterDescription is a phrase that describes the criteria that determines whether a subtask is completed.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
subtaskAcceptanceParameterValue
Short Name
paraValue
Units of Functionality Diagrams
X
Subtask Acceptance Parameter Value
Description
subtaskAcceptanceParameterValue is the value (criteria) that must be fulfilled before the subtask can be ended.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
subtaskDescription
Short Name
subtDescr
Units of Functionality Diagrams
X
Subtask Description
Description
subtaskDescription is a phrase that gives more information on the subtask procedure.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
subtaskDuration
Short Name
duration
Units of Functionality Diagrams
X
Subtask Duration
Description
subtaskDuration is the average time expended, regardless of the number of personnel working simultaneously, required for the performance of the subtask.
Comment
subtaskDuration does not include time spent awaiting spares, support equipment, facilities or personnel (logistics delay time).
Data Type
PropertyType
Units of Functionality
Property (Attribute)
subtaskEndItemObjectiveState
Short Name
eiObjState
Units of Functionality Diagrams
X
Subtask End Item Objective State
Description
subtaskEndItemObjectiveState is a classification which defines the state that will exist after the accomplishment of the subtask.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
subtaskIdentifier
Short Name
subtId
Units of Functionality Diagrams
X
Subtask Identifier
Description
subtaskIdentifier is a string of characters used to uniquely identify a Subtask and to differentiate it from other Subtasks.
Comment
A subtask is identified within the context of a task.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
subtaskMaintenanceLocation
Short Name
maintLoc
Units of Functionality Diagrams
X
Subtask Maintenance Location
Description
subtaskMaintenanceLocation is a classification which indicates where the maintenance task will be carried out in terms of a product (end item or major assembly).
Comment
Source: S1000D Item Location Code
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
subtaskName
Short Name
name
Units of Functionality Diagrams
X
Subtask Name
Description
subtaskName is a word or phrase by which a subtask is known and can be easily referenced.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
subtaskRole
Short Name
subtRole
Units of Functionality Diagrams
X
Subtask Role
Description
subtaskRole is a classification which identifies if the subtask is required for preparation, core, or close-up purposes.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
subtaskTimelineEvent
Short Name
evnt
Units of Functionality Diagrams
X
Subtask Timeline Event
Description
subtaskTimelineEvent is a classification which identifies the starting point for subtask under consideration in relation to the start or end point of the subtask playing the role of its predecessor.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
subtaskTimelineLag
Short Name
lag
Units of Functionality Diagrams
X
Subtask Timeline Lag
Description
subtaskTimelineLag is the time between the related subtask timeline event (start/end) and the start for the subtask under consideration.
Comment
Time lining just using references to the start point for the entire task, can use the lag attribute to indicate the time relative to the starting point of the first subtask and set subtaskTimelineEvent = ‘start’.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskDuration
Short Name
duration
Units of Functionality Diagrams
X
Task Duration
Description
taskDuration is the average time expended, regardless of the number of personnel working simultaneously, required for the performance of a task, scheduled or unscheduled.
Comment
taskDuration does not include time spent awaiting spares, support equipment, facilities or personnel (logistics delay time).
May be calculated from the durations of the subtasks.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskFacilityResourceQuantity
Short Name
qty
Units of Functionality Diagrams
X
Task Facility Resource Quantity
Description
taskFacilityResourceQuantity is the quantity of the facility resource needed by a subtask, or aggregated per task.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskFrequency
Short Name
frequency
Units of Functionality Diagrams
X
Task Frequency
Description
taskFrequency is the frequency of performance or occurrence of the task, expressed as the number of annual occurrences.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskFrequencyCalculationMethod
Short Name
calcMthd
Units of Functionality Diagrams
X
Task Frequency Calculation Method
Description
taskFrequencyCalculationMethod is a phrase that gives more information on the method used for calculating the task frequency.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskIdentifier
Short Name
taskId
Units of Functionality Diagrams
X
Task Identifier
Description
taskIdentifier is a string of characters used to uniquely identify a Task and to differentiate it from other Tasks.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
taskMaterialResourceCategory
Short Name
cat
Units of Functionality Diagrams
X
Task Material Resource Category
Description
taskMaterialResourceCategory is a classification that defines the logistics role of the needed material resource in the context of the task/subtask.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskMaterialResourceQuantity
Short Name
qty
Units of Functionality Diagrams
X
Task Material Resource Quantity
Description
taskMaterialResourceQuantity is the quantity of the material resource needed by a subtask, or aggregated per task.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskName
Short Name
name
Units of Functionality Diagrams
X
Task Name
Description
taskName is a word or phrase by which a task is known and can be easily referenced.
Comment
The following rules must be followed to enable integration with other ASD specifications: taskName must use the information code name for the informationCode that is associated with the task. Additional qualifiers can be added to establish a unique taskName, if multiple tasks with the same informationCode is associated with one and the same breakdown element or part.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskNumberOfPersonnelResource
Short Name
number
Units of Functionality Diagrams
X
Task Number Of Personnel Resource
Description
taskNumberOfPersonnelResource is the number of persons with the same role and skill code needed within one task/subtask.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskOperabilityImpact
Short Name
opImpact
Units of Functionality Diagrams
X
Task Operability Impact
Description
taskOperabilityImpact is a classification that indicates the operational status and mission readiness of the end item during the task.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskPersonnelResourceLabourTime
Short Name
laborTime
Units of Functionality Diagrams
X
Task Personnel Resource Labour Time
Description
taskPersonnelResourceLabourTime is the time expended within a task/subtask per personnel resource.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskPersonnelResourceRole
Short Name
persRole
Units of Functionality Diagrams
X
Task Personnel Resource Role
Description
taskPersonnelResourceRole is a classification that defines the role of the personnel resource needed within a task/subtask.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskPersonnelSafetyCriticality
Short Name
persSafety
Units of Functionality Diagrams
X
Task Personnel Safety Criticality
Description
taskPersonnelSafetyCriticality is a classification that identifies the most serious health aspects that the performance of the task can pose on personnel performing the task.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskProductIntegrityCriticality
Short Name
prodIntegr
Units of Functionality Diagrams
X
Task Product Integrity Criticality
Description
taskProductIntegrityCriticality is a classification that identifies whether the task is critical if failure to accomplish it would result in adverse effects on system reliability, efficiency, effectiveness, safety, or cost. A task will also be designated as critical whenever system design characteristics approach human limitations, and thereby, significantly increase the likelihood of degraded, delayed, or otherwise impaired mission performance.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskRequirementAuthority
Short Name
auth
Units of Functionality Diagrams
X
Task Requirement Authority
Description
taskRequirementAuthority identifies the organization that is the authoritative source for the identified task requirement.
Data Type
Organization
Units of Functionality
Property (Attribute)
taskRequirementAuthoritySourceType
Short Name
authType
Units of Functionality Diagrams
X
Task Requirement Authority Source Type
Description
taskRequirementAuthoritySourceType is a classification which indicates the source of an authority driven task requirement.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskRequirementDate
Short Name
revDate
Units of Functionality Diagrams
X
Task Requirement Date
Description
taskRequirementDate defines the date when the task requirement was recorded.
Data Type
DateType
Units of Functionality
Property (Attribute)
taskRequirementDecision
Short Name
trDecision
Units of Functionality Diagrams
X
Task Requirement Decision
Description
taskRequirementDecision is a classification which identifies the status for the task requirement.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskRequirementDescription
Short Name
trDescr
Units of Functionality Diagrams
X
Task Requirement Description
Description
taskRequirementDescription is a phrase that gives more information on the maintenance requirements that have been determined as the outcome of eg. Reliability Centered Maintenance (RCM) analysis, LSA-FMEA or In-service feedback.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskRequirementIdentifier
Short Name
trId
Units of Functionality Diagrams
X
Task Requirement Identifier
Description
taskRequirementIdentifier is a string of characters used to uniquely identify a TaskRequirement and to differentiate it from other TaskRequirements.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
taskRequirementRevisionChange Description
Units of Functionality Diagrams
X
Task Requirement Revision Change Description
Description
taskRequirementRevisionChangeDescription is a phrase that gives more information on changes introduced between two revisions of a task requirement.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskRequirementRevisionIdentifier
Short Name
trRevId
Units of Functionality Diagrams
X
Task Requirement Revision Identifier
Description
taskRequirementRevisionIdentifier is a string of characters used to uniquely identify a TaskRequirementRevision and to differentiate it from other TaskRequirementRevisions.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
taskRequirementSpecialResource Requirement
Units of Functionality Diagrams
X
Task Requirement Special Resource Requirement
Description
taskRequirementSpecialResourceRequirement is a phrase that gives more information on special (peculiar) resources needed for the performance of the required task.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskResourceDuration
Short Name
duration
Units of Functionality Diagrams
X
Task Resource Duration
Description
taskResourceDuration is the average time that a resource is needed for the performance of a task, scheduled or unscheduled.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
taskResourceRelationshipCategory
Short Name
relType
Units of Functionality Diagrams
X
Task Resource Relationship Category
Description
taskResourceRelationshipCategory is a classification that identifies the type of relationship established between two resources needed within the same subtask.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskRevisionChangeDescription
Short Name
revChangeDescr
Units of Functionality Diagrams
X
Task Revision Change Description
Description
taskRevisionChangeDescription is a phrase that gives more information on changes introduced between two revisions of a task.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
taskRevisionIdentifier
Short Name
taskRevId
Units of Functionality Diagrams
X
Task Revision Identifier
Description
taskRevisionIdentifier is a string of characters used to uniquely identify a TaskRevision and to differentiate it from other TaskRevisions.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
taskRevisionStatus
Short Name
status
Units of Functionality Diagrams
X
Task Revision Status
Description
taskRevisionStatus is a classification which identifies the progress on the definition of a task revision.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
taskTotalLabourTime
Units of Functionality Diagrams
X
Task Total Labour Time
Description
taskTotalLabourTime is the total time expended within a task. Includes the labor time for all required personnel resources.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
technologyBehaviourKnowledgeRating
Short Name
bhvrRtg
Units of Functionality Diagrams
X
Technology Behaviour Knowledge Rating
Description
technologyBehaviourKnowledgeRating is a support classification that identifies the knowledge of behavior of the technology used, during normal use or caused by special event.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
technologySensitivityRating
Short Name
sensRtg
Units of Functionality Diagrams
X
Technology Sensitivity Rating
Description
technologySensitivityRating is a support classification that identifies possible damage sources during normal use or caused by special event.
Data Type
DatedClassification
Units of Functionality
Property (Attribute)
textValue
Units of Functionality Diagrams
X
Text Value
Description
The string that is the element of representation.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
char
Units of Functionality
Property (Attribute)
thresholdValue
Short Name
thldValue
Units of Functionality Diagrams
X
Threshold Value
Description
thresholdValue is the value that defines the limit (interval) for when a task is to be performed.
Data Type
PropertyType
Units of Functionality
Property (Attribute)
timeLimitDescription
Short Name
limitDescr
Units of Functionality Diagrams
X
Time Limit Description
Description
timeLimitDescription is a phrase that gives more information on the limit (threshold and/or trigger) that initiates the performance of the associated task.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
timeLimitHarmonizationIndicator
Short Name
harmoniz
Units of Functionality Diagrams
X
Time Limit Harmonization Indicator
Description
timeLimitHarmonizationIndicator identifies if the time limit is the result from a task limit harmonization and/or packaging procedure.
Comment
Such tasks are in general inspection or/and overhaul packages, documented against non-physical breakdown elements.
Data Type
boolean
Units of Functionality
Property (Attribute)
tradeName
Short Name
tradeName
Units of Functionality Diagrams
X
Trade Name
Description
tradeName is a classification which identifies the type of occupation.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
trainingMethod
Short Name
trainMeth
Units of Functionality Diagrams
X
Training Method
Description
trainingMethod is a classification which identifies the method how an additional required training for a specific competence can be performed..
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
unit
Units of Functionality Diagrams
X
Unit
Description
The unit with which the quantity is expressed.
Comment
Source: ISO 10303:239 ed.2 Product Life Cycle Support.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
upperBound
Units of Functionality Diagrams
X
Upper Bound
Description
upperBound is a characteristic that represents the last valid serial number.
Comment
If the value for upperBound is not specified, the range has no upper bound.
Data Type
char
Units of Functionality
Property (Attribute)
upperLimitValue
Units of Functionality Diagrams
X
Upper Limit Value
Description
The upper limit of a value range.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
upperOffsetValue
Units of Functionality Diagrams
X
Upper Offset Value
Description
The upper limit defined as the upper offset value from the nominal value (value + upper offset value).
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
value
Units of Functionality Diagrams
X
Value
Description
The value of the quantity.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
double
Units of Functionality
Property (Attribute)
valueDetermination
Units of Functionality Diagrams
X
Value Determination
Description
The method by which the value of the property has been determined.
Comment
Source: ISO 10303:239 ed.2 Product Life Cycle Support.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
valueRecordingDate
Units of Functionality Diagrams
X
Value Recording Date
Description
The date when the property value was recorded.
Comment
Source: OASIS PLCS DEXlib.
Data Type
DateType
Units of Functionality
Property (Attribute)
warningCautionNoteDescription
Short Name
wcnDescr
Units of Functionality Diagrams
X
Warning Caution Note Description
Description
warningCautionNoteDescription is a phrase that gives more information on advices concerning safety, legal and health aspects.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
warningCautionNoteIdentifier
Short Name
wcnId
Units of Functionality Diagrams
X
Warning Caution Note Identifier
Description
warningCautionNoteIdentifier is a string of characters used to uniquely identify a WarningCautionNote and to differentiate it from other WarningCautionNotes.
Data Type
IdentifierType
Units of Functionality
Property (Attribute)
warningCautionNoteType
Short Name
wcnType
Units of Functionality Diagrams
X
Warning Caution Note Type
Description
warningCautionNoteType is a classification of the provided safety, legal and health aspects as a warning, caution or note.
Data Type
ClassificationType
Units of Functionality
Property (Attribute)
yearComponent
Units of Functionality Diagrams
X
Year Component
Description
The year element of the DateType expressed as a value between 1 and 9999.
Comment
Source: ISO 10303:239 Product Life Cycle Support.
Data Type
int
Units of Functionality
Property (Attribute)
zoneElementDescription
Short Name
beDescr
Units of Functionality Diagrams
X
Zone Element Description
Description
zoneElementDescription is a phrase that gives more information on the zone element under consideration.
Data Type
DescriptorType
Units of Functionality
Property (Attribute)
zoneElementType
Short Name
beType
Units of Functionality Diagrams
X
Zone Element Type
Description
zoneElementType is a classification that identifies further specialization of a zone element.
Data Type
ClassificationType
Units of Functionality
Concept Schemes
Concept Scheme (Values List)
General Acronyms
Chapter
21.3
Paragraph
2
Acronyms
Description
No Description
Comment
When there is doubt that an abbreviation or acronym will be understood or whenever there is ample space to write in full, the term must be written out rather than abbreviated.
Abbreviations for word combinations, acronyms, must be used as such and not separated for use singly, unless authorized singly.
Single abbreviations can be combined when necessary if there is no abbreviation listed for the combination.
Abbreviations are used in a consistent manner throughout this specification to represent all tenses, singular and plural of their definition.
Concepts for this Scheme:
AIA
Description
Aerospace Industries Association of America
AD
Description
Accidental Damage
AOR
Description
Annual Operating Rate
ASD
Description
AeroSpace and Defense Industries Association of Europe
BE
Description
Breakdown Element
BEI
Description
Breakdown Element Identifier
BER
Description
Breakdown Element Revision
BIT
Description
Built in Test
BITE
Description
Built in Test Equipment
CBS
Description
Cost Breakdown Structure
CE
Description
Communauté Européenne
CEE
Description
Communauté Economique Européenne
Chap
Description
Chapter
CI
Description
Candidate Item
CIL
Description
Candidate Item List
CM
Description
Configuration Management
CMR
Description
Certification Maintenance Requirements
COTS
Description
Commercial Off The Shelf
CP
Description
Change Proposal
CRD
Description
Customer Requirements Document
DA
Description
Design Authority
DADD
Description
Data and Definition Document
DEL
Description
Data Element List
DEX
Description
Data Exchange Specification
DLM
Description
Depot Level Maintenance
DMC
Description
Data Module Code
DoD
Description
Department of Defense
DRACAS
Description
Data Reporting and Corrective Action System
DSE
Description
Damage and Special Event
ED
Description
Environmental Deterioration
ELORA
Description
Economical Level of Repair Analysis
FC
Description
Failure Cause
FFE
Description
Functional Failure Effect
FFEC
Description
Functional Failure Effect Code
Fig
Description
Figure
FLS
Description
Field Loadable Software
FMA
Description
Failure Mode Analysis
FMEA
Description
Failure Mode and Effects Analysis
FMECA
Description
Failure Mode and Effects Criticality Analysis
FMR
Description
Failure Mode Ratio
FTA
Description
Fault Tree Analysis
GC
Description
Guidance Conference
GCD
Description
Guidance Conference Document
GEIA
Description
Government Electronic and Information Technology Association
GVI
Description
General Visual Inspection
ICN
Description
Information Control Number
ID
Description
Identifier
ILC
Description
Item Location Code
ILS
Description
Integrated Logistic Support
ISMO
Description
In Service Maintenance Optimization
ISO
Description
International Standards Organization
IT
Description
Information Technology
IUA
Description
Item Under Analysis
kg
Description
kilogram
LAN
Description
Local Area Network
lb
Description
pound
LCC
Description
Life Cycle Costs
LCMP
Description
LSA Configuration Management Plan
LCN
Description
Logistic Control Number
LORA
Description
Level of Repair Analysis
LRU
Description
Line Replaceable Unit
LSA
Description
Logistic Support Analysis
LSA
Description
RC Logistic Support Analysis Review Conference
M
Description
Mean active maintenance action time
MC
Description
Maintenance Concept
MDT
Description
Maintenance Down Time
MET
Description
Mean Elapsed Time
MIL-STD
Description
Military Standard (US DoD)
ML
Description
Maintenance Level
MoD
Description
Ministry of Defence
MRI
Description
Maintenance Relevant Item
MRO
Description
Maintenance, Repair & Overhaul
MSDS
Description
Material Safety Data Sheet
MSI
Description
Maintenance Significant Item
MSN
Description
Manufacturer Serial Number
MTA
Description
Maintenance Task Analysis
MTBF
Description
Mean Time Between Failures
MTBM
Description
Mean Time Between Maintenance
MTTR
Description
Mean Time to Repair
NATO
Description
North Atlantic Treaty Organization
O&S
Description
Operating and Support
OASIS
Description
Organisation for the Advancement of Structural Information Standards
OEM
Description
Original Equipment Manufacturer
OM
Description
Obsolescence Management
OMP
Description
Operator Maintenance Plan
ORD
Description
Operational Requirements Document
para
Description
Paragraph
PBS
Description
Product Breakdown Structure
PDF
Description
Product Disposal File
PDM
Description
Product Data Management
PE
Description
Periodical
PHST
Description
Packaging, Handling, Storage and Transportation
PLCS
Description
Product Life Cycle Support
P/N
Description
Part Number
PMTR
Description
Preventative Maintenance Task Requirement
PNR
Description
Part number
PO
Description
Perform once
PP
Description
Program Plan
PPH
Description
Policy and Procedure Handbook
RC
Description
Review Conference
RCM
Description
Reliability Centered Maintenance
RDL
Description
Reference Data Library
RFC
Description
Request For Clarification
SB
Description
Service Bulletin
SD
Description
Significant Detail
SI
Description
Structural Item
SLS
Description
Shop Loadable Software
SMA
Description
Scheduled Maintenance Analysis
SNS
Description
Standard Numbering System
SOW
Description
Statement of Work
SRU
Description
Shop Replaceable Unit
SSA
Description
Software Support Analysis
SSC
Description
Software Support Concept
SSI
Description
Structural Significant Item
ST
Description
Sub-Task
SUA
Description
System Under Analysis
SW
Description
Software
TNA
Description
Training Needs Analysis
UML
Description
Unified Modeling Language™
UoF
Description
Unit of Functionality
WAN
Description
Wide Area Network
WBS
Description
Work Breakdown Structure
ZAM
Description
Zonal Analysis Module
Concept Scheme (Values List)
General Glossary
Chapter
21.2
Paragraph
2
General Glossary
Description
Terms used throughout this specification.
Concepts for this Scheme:
Availability
Description
Availability is the measure of the degree to which an item is in an operable and ready-for-use state at the start of a mission or operation, when the mission or operation is called for at an unknown time. This is sometimes called operational readiness.
Code
BEI
Breakdown Element Identifier
Description
The Breakdown Element Identifier is a code that identifies the breakdown structure of all system items within the LSA. The breakdown can include software items.
Code
BER
Breakdown Element Revision
Description
The Breakdown Element Revision is a code which indicates that an alternative equipment or component occupies the same position in the breakdown and, therefore, the same installation position.
Code
BIT
Built In Test
Description
Built-In Test are implemented on items to enable them to carry out some self-testing up to a given degree.
Usually, three types of BIT are implemented:
- power-on BIT (P-BIT) executed at start-up of the item
- continuous BIT (C-BIT) periodically and automatically executed during the operation of the item, without any intervention from the operating crew
- initiated BIT (I-BIT) executed upon order from the operator or from the maintenance team
Each of these types of tests detects specific categories of failures.
They are characterized by:
- a detection rate that gives the percentage of functions or items whose failure is detected
- a localization or isolation rate that gives the percentage of detected failures that are associated without ambiguity to the failure of an identified replaceable unit
- a false alarm rate
Built-in tests are likely to:
- detect failures
- localize failed replaceable units
Localization can be:
- ambiguous, which means that the failure has been localized within a group of replaceable parts, not on a single replaceable part
- non-ambiguous, which means that the failed item has been identified and localized with an acceptable degree of certainty
Removing the ambiguity is the goal of troubleshooting analysis.
In terms of warning and signals, BIT results can be signaled to the operator through a warning or alarm (which is usually the case for critical failures).
Code
CI
Candidate Item
Description
A Candidate Item is an item that has been identified that requires analysis within the LSA process.
Code
CIL
Candidate Item List
Description
A Candidate Item List documents the CI’s that are to be analyzed (documentation of the selection of analysis tasks).
chemical abstract substance identification number
Description
Unique international identifier for a given substance.
Code
COTS
Commercial Off-The-Shelf
Description
Software or hardware, generally technology products, that is ready-made and available for sale, lease, or license to the general public.
common cause
Description
Some failures can lead to several malfunctions. For instance, the failure of a power supply leads to malfunction of all its supplied items. This type of failure with multiple impacts is called a common cause.
corrective
Description
All maintenance activities, which are carried out to reset a faulty maintenance item to full functionality.
Code
CRD
Customer Requirements Document
Description
The Customer Requirements Document contains all of the customer logistic requirements. This document must be available for the Guidance Conference.
damage
Description
A loss or reduction of functionality, excluding inherent failure (intrinsic reliabilities). Normally a maintenance task will be required. Damages can be grouped into damage families" (eg, concerning structures, typical damage can be identified like scratches, dents or cracks). These damage families are typical candidates for a standard repair procedure."
dangerous/toxic
Description
Substance which harms human beings and environment (animals, substance plants, etc).
Code
DEL
Data Element List
Description
List of selected data elements or an output of a data element tailoring process. This list can contain additional data elements required for a project, which are not predefined in any standard.
defect
Description
Any non-conformance of an item with its specified requirements is a defect. Note that a defect does not necessarily result in a failure of the item.
definition files
Description
Definition files, such as technical descriptions, interface definitions, wiring diagrams, description of sockets bounding, etc. This can be useful if the localization remains ambiguous after simple troubleshooting has been carried out and when it becomes necessary to carry out functional or electrical tests to help isolate the failed item.
demilitarization
Description
Operation which makes a defense Product unavailable for its intended military use.
detection
Description
Failure detection warns the operator that a failure has occurred.
direct replaceable
Description
Item that is directly replaceable on the Product.
deviation
Description
Authorized approval to depart from a particular requirement of a Product/equipment approved configuration documentation for a specified period of time. This allows the acceptance of an Product/equipment which departs from the particular requirement, but is considered as suitable for use ‘as is’ or after repair by an approved method.
disposal phase
Description
Last phase of a Product Life Cycle, where the Product is phased out of use.
disposal process
Description
Set of tasks to be performed on a Product at the end of its intended use.
external cause
Description
A cause is said to be external when an event independent of Product usage occurs eg, bird-strike.
failure
Description
Unacceptable reduction of functionality of an item where the item cannot continue its intended use. The failure occurs during proper usage of the item.
Code
FC
Failure Cause
Description
A Failure Cause is any circumstance during design, manufacture or use of the Product, which led to the failure.
failure mode
Description
A failure mode is a predicted or observed physical, mechanical, thermal or other process which leads to a failure. The result of this process is stated in relation to the operating conditions at the time of the failure.
failure rate
Description
The failure rate is the probability of failure per unit of time of items in operation.
Code
FMEA
Failure Modes and Effects Analysis
Description
A Failure Modes and Effects Analysis is a procedure for analysis of potential failure modes within a system for classification by severity or determination of the effect of failures on the system.
Code
FMECA
Failure Mode, Effects, and Criticality Analysis
Description
Failure Mode, Effects, and Criticality Analysis is an extension of Failure Mode and Effects Analysis (FMEA). In addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their consequences. The probability that a failure mode is caused by a fault item is calculated during the analysis. The severity of the consequences of this fault determines the remedial action required to correct the fault and return the item to service.
Code
FLS
Field Loadable Software
Description
Software that can be installed to one or several equipments on a Product without need to remove the equipment from its installation location.
firmware
Description
Software that can be loaded into a Line Replaceable Unit (LRU) or Shop Replaceable Unit (SRU) but requires the target to be dismounted from its installation on the operational system and requiring the replacement of a component.
fit form and function
Description
Where the physical interface, physical parameters that uniquely characterize or the function of a Product/equipment remain unchanged.
function breakdown
Description
A simple functional breakdown can start on top level of the Product as the root of the breakdown tree. The different functions of the Product must be documented from the main functions down to the sub-functions, etc, to the required depth. A functional breakdown must not contain any physical items.
functionality analysis
Description
Functional analysis describes and functions performed by the Product, systems, subsystems and sub-subsystems.
Each function of the system can be characterized by the flows or parameters that:
- it takes as inputs
- it requires as part of operating context
- it provides as outputs
The outputs provided by the characterization justify the inclusion of the items in the design. The results of the functionality analysis are used to identify the impact of a failed physical item or items on other associated functions. The results also indicate the detection and corrective action required preventing the failure and ensuring continuity and/or restoration of the items intended functionality.
functional symptom
Description
A functional symptom can be observed during a functional check and/or the failure of an item associated with the function.
Code
GC
Guidance Conference
Description
A conference at which the supplier and the customer agree the scope and depth of the LSA business processes and procedures.
Code
GCD
Guidance Conference Document
Description
A signed, contractual record of the agreements reached by the supplier and the customer. This document is an output of the Guidance Conference.
Code
ILS
Integrated Logistic Support
Description
Integrated Logistics Support is an integrated and iterative process for developing materiel and a support strategy that optimizes functional support, leverages existing resources, and guides the system engineering process to quantify and lower life cycle cost and decrease the logistics footprint (demand for logistics), making the system easier to support.
internal cause
Description
A cause is said to be internal when it comes from normal Product usage by itself (eg, excessive vibration).
labor time
Description
The sum of the man-hours taken to complete a task. If more than one person is working on a task at the same time, the time taken by each person must be summarized by skill level.
Code
LORA
Level Of Repair Analysis
Description
Level Of Repair Analysis is a prescribed procedure for determining the most economical and efficient level at which maintenance is performed.
Line Replaceable Unit
Description
An item, which can be removed and installed at the organizational (LRU) maintenance area.
localization
Description
Failure isolation that indicates an item or group of items that have failed. This isolation is usually associated with a failure detection.
Code
LSA
Logistic Support Analysis
Description
A structured approach to increase in maintenance efficiency and reduction of the cost of providing support by preplanning all aspects of Integrated Logistics Support.
LSA database
Description
A database that records the logistic data gathered as a result of the ILS processes.
life cycle
Description
Total Product lifespan since its initial feasibility phase, until its service withdrawal and disposal.
Code
LCC
Life Cycle Cost
Description
Life Cycle Cost is the cumulative cost of a Product over its life cycle from entry into service to disposal as determined by a process of economic analysis that allows for the assessment of the total cost of acquisition, ownership and disposal of the Product.
maintainability
Description
The measure of the ability of an item to be retained in, or restored to a specified condition, when maintenance is performed by personnel having specified skill levels, using prescribed procedures and resources, at each prescribed level of maintenance and the level at which maintenance can be carried out for the continuance of the Product's mission as limited by the design.
Code
MC
Maintenance Concept
Description
A strategy for providing maintenance support to ensure a Product meets its mission performance requirements.
Maintenance Plan
Description
A plan for conducting maintenance in the most efficient and cost effective manner such that the Product performs as intended, to meet its mission requirements.
The Maintenance plan specifies when, where, and how maintenance tasks are performed on the Product/equipment, including both:
- Preventive maintenance
- Corrective maintenance
The plan ensures that all required maintenance resources are in place to support deployment of the Product.
Code
MTA
Maintenance Task Analysis
Description
The Maintenance Task Analysis is a detailed analysis process that results in the identification of the procedures, spares and materials, tools, support equipment, personnel skill levels, estimated and elapsed times as well as any facility issues that must be considered for a corrective, repair or preventive maintenance task.
Code
MRI
Maintenance Relevant Item
Description
A Maintenance Relevant Item is an item that can be repaired or replaced in case of a failure or damage. Normally this item is automatically a potential LSA candidate, but not automatically an MSI.
Code
MSI
Maintenance Significant Item
Description
A Maintenance Significant Item is an item that was identified by any selection process as the result of a Scheduled Maintenance Analysis (SMA) procedure such as S4000M. An MSI can become a LSA candidate if the SMA identifies a scheduled task which is documented in the LSA database.
malfunction analysis
Description
Malfunctioning analysis aims to define actions to be taken in the event of a failure. It can cover two types of corrective actions:
- actions to be taken by the operating crew when a failure occurs during operation
- actions to be taken as part of the corrective maintenance
Only the second type of actions falls into the scope of this specification.
Code
MET
Mean Elapsed Time
Description
The average time expended, irrespective of the number of personnel, required to complete a task. The duration of the whole task can be calculated as the sum of times coming from the subtasks and from the referenced supporting tasks.
Code
MTBF
Mean Time Between Failures
Description
Mean Time Between Failures is the predicted elapsed time between inherent failures of a system during operation. MTBF can be calculated as the arithmetic mean (average) time between failures of a system. The MTBF is typically part of a model that assumes the failed system is immediately repaired (zero elapsed time), as a part of a renewal process. This is in contrast to the Mean Time To Failure (MTTF), which measures average time between failures with the modeling assumption that the failed system is not repaired.
Model Identifier
Description
The Model Identifier is a code, which uniquely identifies the Product. It is recommended to use the model identifier in conjunction with other identifiers within the entire ILS process.
Code
ORD
Operational Requirements Document
Description
The Operational Requirements Document defines the operational requirements in a qualitative way for the Product. This document must be available for the Guidance Conference.
physical breakdown
Description
A top down representation of hardware and software of a Product based on the engineering design model/drawings.
physical symptom
Description
A physical symptom characterizes a failure detected by visual inspection, measurement of a wear-out parameter, material degradation. It is detectable or measurable when the system is currently operated or if it is undergoing inspection or maintenance.
preventive maintenance
Description
Maintenance activities to prevent the occurrence of critical failures or damages in conjunction with safety, economical or ecological aspects. The Preventive Maintenance also includes activities after special events where these events, chronological intervals or other regular threshold cannot be defined.
Product
Description
Any platform, system or equipment (air, sea, land vehicle, equipment or facilities, civil or military). The term the Product is used in this specification to mean platforms, systems, subsystems, sub-subsystems, assemblies, equipment, LRU, components, parts etc.
realization
Description
The completion of a Product breakdown from a design breakdown, including different system/subsystem or components for the same installed location.
rectifying task
Description
A maintenance activity, which resolves an event such as failures, damages, special events or thresholds. A rectifying task contains subtasks in terms of referenced supporting tasks and/or definite working steps.
reliability
Description
The probability of failure free performance of a Product/equipment under stated conditions, or the probability that an item can perform its intended function for a specified interval under stated conditions, is a prime driver of support resources.
Code
RCM
Reliability Centered Maintenance
Description
Reliability Centered Maintenance is a disciplined logic or methodology used to identify scheduled maintenance tasks to maintain the inherent reliability of equipment at a minimum expenditure of resources.
scheduled maintenance
Description
Maintenance activities to prevent the occurrence of critical failures or damages in conjunction with safety, economical or ecological aspects. These maintenance tasks are defined with a corresponding interval or threshold (eg, after certain time, cycles, rounds, distance). Scheduled maintenance is a subset of preventive maintenance.
Scheduled Maintenance Analysis Candidate
Description
Element of the Product breakdown, which is identified as a potential candidate for which a scheduled or preventive maintenance task could be necessary.
Code
SMA
Scheduled Maintenance Analysis
Description
The analysis task for the identification of preventive and scheduled maintenance. Different methods are available to perform this analysis task such as S4000M.
Code
SLS
Shop Loadable Software
Description
Software that can be loaded into a LRU but that requires the target LRU to be dismounted from its installation in the system where it is located.
Code
SRU
Shop Replaceable Unit
Description
An item, which can only be changed at shop/rear level (cannot be removed and installed at the organizational maintenance area).
signature
Description
A list of physical symptoms, functional symptoms and BIT results that help detect and localize the failure.
Code
SSA
Software Support Analysis
Description
Software Support Analysis is the methodology to analyze software with the purpose to supply the customer with all necessary information to establish a cost effective Software Support Concept. This includes all equipment, tools, personnel, documentation, infrastructure and required skill and training respectively.
special event
Description
A special event is something that can occur during the life of the Product but cannot be considered as a normal way of operation. It can be due either to external causes, (eg, meteorological phenomenon or to out of bound use such as over G maneuver).
specific test
Description
Whenever BIT is unable to detect or localize failures, some specific equipment test equipment can be required. This specific test equipment can include:
- external measurement or test items
- external means used to simulate a function of the operating system
structural detail
Description
A specific area of the Structure Significant Item (SSI) which was identified by any selection process from an SMA procedure such as S4000M. For this detail, an SMA will be performed.
Code
SI
Structural Item
Description
A Structural Item is a part of the Product bodywork. It can be an LSA candidate as well as a Structure Significant Item.
Structure Significant Item
Description
An item which is identified by the selection process from a Scheduled Maintenance Analysis procedure such as S4000M.
substances
Description
Characterization (identification, risk, quantity, etc) and location of cartography all the tracked substances within a Product.
supply chain
Description
A supply chain consists of all organizations involved, directly or indirectly, in fulfilling a customer support requirements.
supply chain management
Description
The process of planning, implementing and controlling the operations of the supply chain as efficiently as possible.
supporting task
Description
A supporting task is a part of a complete maintenance activity. As a standalone task it cannot rectify an event such as failures, damages, special events or thresholds. A supporting task contains subtasks in terms of working steps.
testability
Description
Performances of BIT developed on some items of the system are often assessed using FMEA terms and results, but this is not mandatory, particularly when the item has been previously developed for another program. BIT can be characterized by:
- a list of functions or sub-functions that are tested - a detection rate that gives the percentage of functions or items whose failure is detected
- a localization or isolation rate that gives the percentage of detected failures that are associated without ambiguity to the failure of an identified item or component
- a "No Fault Found" rate
These analyses and their justification are used for malfunctioning analysis and for LSA FMEA, especially because they provide a list of failure reports (from BIT) giving failure codes or any other message that indicates which item or group of items is liable to have failed, therefore restraining greatly the number of items to be investigated as part of the troubleshooting.
Warnings are sent to the operating crew or to the maintenance team to indicate detected failures. These warnings are used as initial symptoms and not necessarily sent from the faulty item causing the failure.
Code
TNA
Training Needs Analysis
Description
task to identify the requirements for training for operational and maintenance activities.
troubleshooting
Description
Troubleshooting consists of localizing failed replaceable units when their failure is not obvious or previously achieved by other means (eg, built-in test). Troubleshooting is carried out after a failure has been detected.
Code
ID
unified identifier
Description
Designation for an identifier, which can be used across all logistic disciplines in the ILS process for a definite identification of any item.
Code
UoC
Usable on Code
Description
A Product, system or equipment identifier that indicates the configuration of a Product on which the item under analysis is used.