S1000D To S3000L Interchange Specification: Issue 1.0 2011-03-31

S1000D to S3000L interchange
specification
Issue 1.0 2011-03-31

S1003X-B6865-01003-00
Copyright and user agreement
1 Copyright
Copyright (C) 2009, 2011 AeroSpace and Defence Industries Association of Europe - ASD.
All rights reserved. No part of this document may be reproduced or transmitted in any form or by
any means, electronic or mechanical, including photocopying and recording, or by any
information storage or retrieval system, except as may be expressly permitted by the Copyright
Act or in writing by the Publisher.
S1003X™ is a trade mark owned by ASD.
All correspondence and queries should be directed to:
ASD
Monsanto Building
270 Avenue de Tervuren
B-1150 Brussels
Belgium
2 Agreement for use of the specification S1003X™ suite of

information
2.1 Definitions
S1003X™ suite of information means, but is not limited to:
− the S1000D and S3000L interchange specification - S1003X

− examples (eg XML instances, pdf files, style sheets) and schemas
− any other software or information under the heading “S1003X™ suite of information”,
available for download from www.asd-stan.org
Copyright Holder means AeroSpace and Defence Industries Association of Europe (ASD).
2.2 Notice to user

By using all or any portion of S1003X™ suite of information you accept the terms and
conditions of this User Agreement.
This User Agreement is enforceable against you and any legal entity that has obtained
S1003X™ suite of information or any portion thereof and on whose behalf it is used.
2.3 License to use

As long as you comply with the terms of this User Agreement, the Copyright Holders grant to
you a non-exclusive license to use S1003X™ suite of information.
2.4 Intellectual property rights

S1003X™ suite of information is the intellectual property of and is owned by the Copyright
Holder. Except as expressly stated herein, this User Agreement does not grant you any
intellectual property right in the S1003X™ suite of information and all rights not expressly
granted are reserved by the Copyright Holder.
2.5 No modifications
You must not modify, adapt or translate, in whole or in part, S1003X™ suite of information.
You may however add business rules.
Applicable to: All S1003X-A-00-00-0000-00A-021A-A
DMC-S1003X-A-00-00-0000-00A-021A-A_001_00_EN-US.doc 2011-03-31 Page 1

S1003X-B6865-01003-00
2.6 No warranty
S1003X™ suite of information is being delivered to you "as is". The Copyright Holder does not
warrant the performance or result you may obtain by using S1003X™ suite of information.
The Copyright Holder makes no warranties, representations or indemnities, express or implied,
whether by statute, common law, custom, usage or otherwise as to any matter including without
limitation merchantability, integration, satisfactory quality, fitness for any particular purpose, or
non-infringement of third parties rights.
2.7 Limitation of liability

In no event will the Copyright Holder be liable to you for any damages, claims or costs
whatsoever or any consequential, indirect or incidental damages, or any lost profits or lost
savings or for any claim by a third party, even if the Copyright Holder has been advised of the
possibility of such damages, claims, costs, lost profits or lost savings.
2.8 Indemnity
You agree to defend, indemnify, and hold harmless the Copyright Holder and its parents and
affiliates and all of their employees, agents, directors, officers, proprietors, partners,
representatives, shareholders, servants, attorneys, predecessors, successors, assigns, and
those who have worked on the preparation, publication or distribution of the S1003X™ suite of
information from and against any and all claims, proceedings, damages, injuries, liabilities,
losses, costs, and expenses (including reasonable attorneys' fees and litigation expenses),
relating to or arising from your use of the S1003X™ suite of information or any breach by you
of this User Agreement.
2.9 Governing law and arbitration

This User Agreement will be governed by and construed in accordance with the laws of the
Kingdom of Belgium.
In the event of any dispute, controversy or claim arising out of or in connection with this User
Agreement, or the breach, termination or invalidity thereof, the parties agree to submit the
matter to settlement proceedings under the ICC (International Chamber of Commerce) ADR
Rules. If the dispute has not been settled pursuant to the said Rules within 45 days following the
filing of a Request for ADR or within such other period as the parties may agree in writing, such
dispute shall be finally settled under the Rules of Arbitration of the International Chamber of
Commerce by three arbitrators appointed in accordance with the said Rules of Arbitration. All
related proceedings should be at the place of the ICC in Paris, France.
The language to be used in the arbitral proceedings shall be English.
End of data module

S1003X-B6865-01003-00
Table of contents
The listed documents are included in Issue 1.0, dated 2011-03-31, of this publication.
Chapter Data module title Data module code Applic
Chap 1 Background S1000D-A-09-00-0000-00A-040A-A All

Chap 2 Introduction S1000D-A-09-01-0000-00A-040A-A All
Chap 3 Principles for product breakdown S1000D-A-09-02-0000-00A-040A-A All
structures
Chap 4 S1000D Procedure and schedule S1000D-A-09-02-0100-00A-040A-A All
Schemas vs S3000L
Chap 5 S1000D Data requirements S1000D-A-09-02-0200-00A-040A-A All
Chap 6 S3000L data required to populate S1000D-A-09-02-0300-00A-040A-A All
S1000D data modules
Chap 7 S1000D feedback to S3000L S1000D-A-09-03-0000-00A-040A-A All
Chap 8 Use of DEX for S1000D and S3000L S1000D-A-09-03-0100-00A-040A-A All
data exchange
Chap 9 Samples with S1000D and S3000L S1000D-A-09-03-0200-00A-040A-A All
instantiations
End of data module

S1003X-B6865-01003-00
Chapter 1
Background
Table of contents Page

Background .................................................................................................................................... 1
References ..................................................................................................................................... 1
1 Background...................................................................................................................... 1
1.1 Purpose ........................................................................................................................... 1
1.2 MTDTT ............................................................................................................................. 1
1.3 Deliverables ..................................................................................................................... 2
List of tables
1 References ...................................................................................................................... 1
References
Table 1 References
Chap No./Document No. Title
DEX1AD DEX1A&D - Aerospace and defense business DEX for

exchange of product breakdown for support
exchange of a task specification
S1000D International specification for technical publications using
a common source database
S3000L International procedure specification for Logistics Support
Analysis - LSA
1 Background
1.1 Purpose
The purpose of this interface specification (S10003X) is to specify data required from the
Product Development and Logistic Support Analysis (LSA) activities, in order to produce the
maintenance procedure, maintenance planning, applicability cross-reference table and
conditions cross-reference table data modules in S1000D.
The content of the interface specification is defined based on the S1000D Schema and S3000L
data model respectively.
1.2 MTDTT
This issue of the interface specification has been developed by the S1000D Maintenance Task
Data Task Team (MTDTT). The scope of work for the MTDTT is to:
− Develop a specification of data required for the exchange of product structures between
ASD specifications. Product structure, including its associated applicabilities is normally tied
to the product design, often done within a Product Data Management (PDM) system. In

Chap 1
S1003X-B6865-01003-00
other words, the product structure from design must fit into the S1000D/S3000L
support/maintenance structure and its applicability model.
− Develop specification of LSA data required to produce S1000D Maintenance Procedures
and Maintenance Planning data modules. This specification will define the information
needed to be exchanged between an S3000L LSA database and the S1000D Common
Source Data Base (CSDB).
− Specify changes required for the CSDB data storage and configuration control, in order to
track and manage Product and Task data being imported, using the PLCS-based
Aerospace and Defense Data Exchange Specifications.
1.3 Deliverables
− DEX1A&D - Aerospace and Defense business DEX for

exchange of product breakdown for support (DEX1AD). DEX1AD is compliant with the
OASIS standard DEX 1 (D001) Product Breakdown for Support. This aerospace and
defense business specific DEX contains all product related data required for the production
of maintenance procedures in S3000L and S1000D, including applicabilities as defined
within S3000L and S1000D.
− DEX3A&D - Aerospace and defense business DEX for exchange

of a task specification (DEX3AD). DEX3AD is compliant with the OASIS standard DEX 3
(D003) Task Set. This aerospace and defense business specific DEX contains the S3000L
task related data, required for the production of maintenance procedure and maintenance
planning data modules in S1000D.
− S1000D change proposals required for enabling integration with S3000L.
− This S1000D and S3000L interface specification.

Chap 1
End of data module
S1003X-B6865-01003-00
Chapter 2
Introduction

Introduction .................................................................................................................................... 1
References ..................................................................................................................................... 1
1 Introduction ...................................................................................................................... 1
List of tables
1 References ...................................................................................................................... 1
References
Table 1 References

Analysis - LSA
1 Introduction
This issue of S1003X supports the data exchange between S3000L at Issue 1.0 and S1000D at
Issue 4.0.1.
S1003X is divided into:
− S1000D data requirements:

• S1000D identification and status section, ie the part which is common to all S1000D
data module schemas
• S1000D procedural information, ie the procedural Schema, defining the details for
maintenance procedures
• S1000D maintenance planning information, ie the maintenance planning Schema, and
its subsections:
− Time limits, which capture information about periodicities and life details for
equipment or systems
− Task definitions, which capture the information about individual tasks to be carried
out on a system
− Inspection definitions, which capture groups of maintenance tasks or inspection
types
− Maintenance allocation, which captures maintenance functions along with
maintenance levels and time associated for each task
• S1000D Applicability cross-reference table
• S1000D Condition cross-reference table

Chap 2
S1003X-B6865-01003-00
− A summary of the constructs in the S3000L data model that can be used to populate the
S1000D Schemas.
End of data module Chap 2

S1003X-B6865-01003-00
Chapter 3
Principles for product breakdown structures

Principles for product breakdown structures .................................................................................. 1
References ..................................................................................................................................... 1
1 Principles for product breakdown structures ................................................................... 1
List of tables
1 References ...................................................................................................................... 1
References
Table 1 References

GEIA-STD-0007 Logistics Product Data
1 Principles for product breakdown structures

There are many different principles for how to define product breakdown structures. The
MTDTT work focused on the ability to support the following two approaches:
− First, the traditional LSA approach. The principle behind this approach is that, for the
breakdown structure, all elements are identified in accordance with one breakdown
philosophy, ie the identification of the respective breakdown element defines its position in
the breakdown structure. Examples of this kind of breakdown are LCN-structures in GEIA-
STD-0007, and SNS structures in S1000D. Common to these approaches are that the
breakdown element identifiers are critical for navigation.
− Second, the product data model approach. The principle behind this approach is that
breakdown elements define “logical” elements such as systems, functions, hardware
positions, and the possible realizations of those elements are defined as parts. Breakdown
structures are defined by explicit associations between the parent and its child elements,
which means that the identification of the respective breakdown element doesn't need to
reflect its position in the breakdown. These structures are often seen in PDM systems.
The identification of the advantages and disadvantages with each approach is out of scope of
this specification. However, the MTDTT work identified problems for S1003X to define one
straightforward mapping, since S3000L supports both approaches, whilst S1000D is based on
the first approach. Therefore S1003X addresses both approaches.

S1003X-B6865-01003-00
Chapter 4
S1000D Procedure and schedule Schemas vs S3000L

S1000D Procedure and schedule Schemas vs S3000L ................................................................ 1
References ..................................................................................................................................... 1
1 S1000D Procedure and schedule Schemas vs S3000L ................................................. 1
1.1 S1000D vs S3000L views on a procedural task .............................................................. 2
1.2 S1000D vs S3000L views on packaged tasks ................................................................ 4
1.3 Populating S1000D data modules based on the S3000L data model............................. 6
1.3.1 Populating S1000D procedural data modules ................................................................. 6
1.3.2 Populating S1000D taskDefinition ................................................................................... 7
1.3.3 Populating S1000D inspectionDefinition ......................................................................... 8
1.3.4 Populating S1000D maintAllocation ................................................................................ 9
1.3.5 Populating S1000D timeLimitInfo .................................................................................. 10
List of tables
1 References ...................................................................................................................... 1
List of figures
1 Example of a breakdown of a repair procedure (rectifying task) in S3000L ................... 3
2 S1000D procedural data module relationship to S3000L task structure ......................... 4
3 S3000L concept of packaged task, procedural task and limit (thresholds) ..................... 5
4 S1000D structure of inspectionDefinition, taskDefinition and referenced procedures .... 6
5 Mapping of S3000L procedural tasks onto S1000D procedural data modules ............... 7
6 S1000D taskDefinition relationship to S3000L tasks....................................................... 8
7 S1000D inspectionDefinition relationship to S3000L tasks ............................................. 9
8 S1000D maintAllocation relationship to S3000L ........................................................... 10
9 S1000D timeLimitInfo relationship to S3000L ............................................................... 11
References
Table 1 References

Analysis - LSA
1 S1000D Procedure and schedule Schemas vs S3000L

It is important for the reader to understand the different views of a task taken from an LSA
perspective compared to the one taken from a technical publications perspective.

Chap 4
S1003X-B6865-01003-00
The difference in views of a task, relates both to the view of a single procedural task, as well as
how to package (group) tasks, eg for a scheduled inspection.
The major reason for this is that S3000L has a supplier/vendor perspective, while S1000D has a
maintainer's perspective. S1000D organizes the data in a way that simplifies the optimization of
tasks that need to be scheduled for a product in operation.
1.1 S1000D vs S3000L views on a procedural task

The difference in views of a procedural task and its content is reflected in the mapping between
the S1000D elements and the S3000L data model. This mapping is described in detail for each
S1000D schema.
The result of the LSA Maintenance Task Analysis (MTA) is a set of tasks that are triggered by
identified events, eg a scheduled threshold, a failure, or a special event. These tasks are also
referred to as rectifying tasks in S3000L. Each rectifying task is self contained, which means
that it contains every step required in order to regain the operational status of an end item, ie
the maintenance task starts with the perspective that the end item is not targeted for any other
maintenance action. However, each rectifying task is structured so that subtasks, or groups of
subtasks, are defined separately as supporting tasks. A supporting task can be reused by many
rectifying tasks.
Fig 1 is taken from S3000L and shows the breakdown of a repair procedure (rectifying task) into
a set of subtasks.

Chap 4
S1003X-B6865-01003-00
Repair procedure
(for equipment 401)
Subtask 01 Reference on: Fault location procedure
Subtask 02 Remove Cover #01 (opening 4 quick fasteners)
Subtask 03 Reference on: Remove Cover #02
Working Step 01 Open 24 screws for removal of Cover #02
Working Step 02 Remove cover plate
Working Step 03 Remove sealing
Subtask 04 Reference on: Remove equipment 401
Working Step 01 Remove electrical connector E01-013
Working Step 02 Open safety screws S01 and S02
Working Step 03 Open attaching screws A01 to A07
Working Step 04 Remove equipment 401 from housing
Subtask 05 Reference on: Disassemble equipment 401
Working Step 01 ……………
……….. ……………
Subtask 06 Remove defective component 05
Subtask 07 Install new component 05
Subtask 08 Reference on: Assemble equipment 401
Subtask 09 Reference on: Install equipment 401
Subtask 10 Reference on: Test function of equipment 401
Subtask 11 Reference on: Install Cover #02
Subtask 12 Install Cover #01
ICN-B6865-S1003X0001-001-01
Fig 1 Example of a breakdown of a repair procedure (rectifying task) in S3000L
This approach is different from the approach taken by S1000D. Subtasks required for
preparation and close up are not defined as explicit procedural steps in S1000D, but are defined
as a set of required conditions.
The S1000D view of a task is defined from an operators/maintainers perspective, where
synchronization and optimization between maintenance tasks are important when a set of pre
conditions are met.
Fig 2 shows the relationship between a procedural task in S3000L and the content of an
S1000D procedural data module. The S1000D preliminary requirements (the element
<preliminaryRqmts>) section summarizes the S3000L start up subtasks, the S1000D
main procedure (the element <mainProcedure>) covers the S3000L core subtasks, and
finally the S1000D close up requirements (the element <closeRqmts>) summarizes the
1
S3000L close up subtasks.
1
Start up, core and close up categorization of subtasks in S3000L has been
introduced in order to enable integration between ASD specifications, and
especially the integration between S3000L and S1000D.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0002-001-01
Fig 2 S1000D procedural data module relationship to S3000L task structure
A main difference between these approaches is that S1000D defines the objective states, in no
particular order, before and after the main procedure steps whereas S3000L defines these
objective states within an explicit order of subtasks.
1.2 S1000D vs S3000L views on packaged tasks

A packaged task in S3000L is regarded as just another task, which references other tasks in the
same way as a rectifying task in S3000L can reference a set of supporting tasks as its subtasks.
The packaging of tasks in S3000L is described from the perspective of scheduled maintenance,
eg a major periodic inspection.
Fig 3 shows how a packaged task is defined within S3000L.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0003-001-01
Fig 3 S3000L concept of packaged task, procedural task and limit (thresholds)
S1000D task structure can start with the inspection (the element
<inspectionDefinition>), which relates to one or many tasks (the element
<taskDefinition>), which in turn relates to one or many procedural data modules. This
is shown in Fig 4.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0004-001-01
Fig 4 S1000D structure of inspectionDefinition, taskDefinition and referenced procedures
There is no straightforward way of mapping a packaged task in S3000L to the structure of the
elements <inspectionDefinition> and <taskDefinition> and referenced
procedures, as defined within the S1000D maintenance planning information schema. However,
a proposed mapping is presented at Para 1.3.
1.3 Populating S1000D data modules based on the S3000L data model
S3000L has introduced the attribute "S1000D_task_type" for task, which makes it
possible to populate the procedural and maintenance planning data modules in S1000D.
1.3.1 Populating S1000D procedural data modules

The starting point for the mapping of S3000L is the breakdown of the product in focus. Each
2
element in the product breakdown must correspond to a hardware/System identification in
S1000D.
Each breakdown element, in the S3000L product breakdown, can then be associated with one
or many tasks. S3000L tasks being categorized as procedural tasks, using the attribute
"S1000D_task_type", can then be mapped onto a set of S1000D procedural data
modules as shown in Fig 5.
2
Hardware/System identification in S1000D consists of a model identification code,
a system difference code, a Standard Numbering System (SNS) and the
disassembly code/disassembly code variant.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0005-001-01
Fig 5 Mapping of S3000L procedural tasks onto S1000D procedural data modules
The objective for any project using both specifications must have the same granularity of a
procedural task. This means that each procedural task defined in S3000L, would have a one-to-
one relationship with a corresponding procedural data module in S1000D.
1.3.2 Populating S1000D taskDefinition

There is no structural concept in S3000L that directly corresponds to an S1000D taskDefinition.
However, S1000D taskDefinition’s can be populated on a per S3000L task basis, ie there is one
instance of taskDefinition per S3000L task, where the taskDefinition contains the task limit and
references to the procedural task to be performed when the limit is met as shown in Fig 6.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0006-001-01
Fig 6 S1000D taskDefinition relationship to S3000L tasks
1.3.3 Populating S1000D inspectionDefinition

The clustering and packaging of maintenance tasks into S1000D inspectionDefinition can be
accomplished in accordance with S3000L packaged tasks, ie each packaged task defined in
S3000L (eg 500 flight hours scheduled maintenance package) can correspond to an instance of
inspectionDefinition.
A mapping includes the identification of a packaged task in S3000L, along with its time limit
(threshold) and references to its procedural subtasks as shown in Fig 7.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0007-001-01
Fig 7 S1000D inspectionDefinition relationship to S3000L tasks
1.3.4 Populating S1000D maintAllocation

S1000D Issue 4.0 introduced a new branch called maintenance allocation (the element
<maintAllocation>) within the schema for maintenance planning information. This
branch is used for the Maintenance Allocation Chart (MAC) and captures maintenance functions
along with maintenance levels and time associated for each task.
The maintenance allocation branch can be populated from the selection of a breakdown
element node in a physical product breakdown as shown in Fig 8.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0008-001-01
Fig 8 S1000D maintAllocation relationship to S3000L
Note
The dotted lines in between functions and data modules in the figure above show that there
is no explicit reference to a procedural data module from the maintenance allocation
function.
1.3.5 Populating S1000D timeLimitInfo

The S1000D timeLimitInfo can be supported by S3000L, through the identification of all the
hardware parts that have a defined operational authorized life, which can be installed on the
product in focus.
These parts are indicated by the hardware element realization, which associates breakdown
elements within a product and its possible realizations, ie parts, as shown in Fig 9.

Chap 4
S1003X-B6865-01003-00
ICN-B6865-S1003X0009-001-01
Fig 9 S1000D timeLimitInfo relationship to S3000L

S1003X-B6865-01003-00
Chapter 5
S1000D Data requirements

1 General ............................................................................................................................ 2
1.1 Introduction ...................................................................................................................... 2
1.2 How to use this chapter ................................................................................................... 2
2 S1000D Identification and status section ........................................................................ 2
2.1 Introduction ...................................................................................................................... 2
2.2 Identification and status section requirements ................................................................ 3
2.3 Notes for Table 2 ........................................................................................................... 40
3 S1000D Maintenance procedure ................................................................................... 40
3.1 Introduction .................................................................................................................... 40
3.2 Preliminary requirements ............................................................................................... 41
3.3 Notes for Table 3 ........................................................................................................... 75
3.4 Main procedure .............................................................................................................. 75
4 S1000D Maintenance Planning Information .................................................................. 84
4.1 Introduction .................................................................................................................... 84
4.2 S1000D schedule Schema requirements ...................................................................... 84
4.2.1 Task definition................................................................................................................ 84
4.3 Inspection definition ..................................................................................................... 114
4.4 Time limit information .................................................................................................. 120
4.5 Maintenance allocation ................................................................................................ 128
5 S1000D Applicability schemas .................................................................................... 145
5.1 Introduction .................................................................................................................. 145
5.2 Applicability cross-reference table ............................................................................... 145
5.3 Condition cross-reference table................................................................................... 150
6 Common information repository .................................................................................. 174
List of tables
1 References ...................................................................................................................... 2
2 identAndStatusSection - Elements and attributes ........................................................... 4
3 PreliminaryRqmts (Preliminary requirements) - Elements and attributes ..................... 42
4 mainProcedure - Elements and attributes ..................................................................... 76
5 taskDefinition - Elements and attributes ........................................................................ 85
6 inspectionDefinitions - Elements and attributes .......................................................... 115
7 timeLimitInfo - Elements and attributes ....................................................................... 121
8 maintAllocations - Elements and attributes ................................................................. 129
9 applicCrossRefTable - Elements and attributes .......................................................... 146
10 condCrossRefTable - Elements and attributes ............................................................ 151

Chap 5
S1003X-B6865-01003-00
References
Table 1 References

S2000M International specification for material management
Analysis - LSA
1 General
1.1 Introduction
This chapter describes how elements in the S1000D Schemas for data modules containing
maintenance procedures, maintenance planning, the applicability cross-reference table and the
conditions cross-reference table can be populated with data sourced from S3000L Logistics
Support Analysis (LSA).
1.2 How to use this chapter

Reading guide for the tables defined in this chapter.
The S1000D Schema elements and attributes which are mapped against S3000L are identified
in the left column. The identification of the respective element/attribute is given in its context, ie
its parent elements are defined as well.
Example 1:
− The cell that indicates the element <thresholdValue>, as used in the context of the
element <taskDefinition><limit><threshold>, contains:
<taskDefinition>
<limit>
<threshold>
<thresholdValue>
Example 2:
− The cell that indicates the attribute @toleranceLow of the element <tolerance>,
as used in the context of the element <taskDefinition><limit><threshold>,
contains:
<taskDefinition>
<limit>
<threshold>
<tolerance@toleranceLow>
2 S1000D Identification and status section

2.1 Introduction
The identification and status section (the element <identAndStatusSection>) gives
all the identification elements required to address and control the data module. It also provides

Chap 5
S1003X-B6865-01003-00
the status elements for information on the security, quality and technical status together with the
applicability of the overall data module content.
Note
The element <identAndStatusSection> is common to all S1000D Schemas.
2.2 Identification and status section requirements

Table 2 describes the elements and attributes in the element
<identAndStatusSection> that are considered candidates for being created (or
derived from data being created) during the S3000L LSA process, and therefore also being
candidates for being transferred via either DEX1AD or DEX3AD.

Chap 5
S1003X-B6865-01003-00
Table 2 identAndStatusSection - Elements and attributes

S1000D Issue 4.0 S1000D Issue 4.0 S3000L Element name/AD Mapping - How to get from S3000L to S1000D (Business rules)
Element/Attribute name Element/Attribute DEX reference
definition
<dmAddress> The model identification Product_variant_i 'Product_variant_identifier' classified as

<dmIdent> code (MI). dentifier 'Model_identification_code'
Notes
<dmCode@modelIdentCod
AD DEX reference: 1. Defined in 1388-2b using the combination of End Item Acronym
e> Code and Usable On Code (EIAC). Also known as Model id.
− DEX1AD section
Product and project - 2. Defined in S2000M using the MOI data element.
Template table #6 or Business rule decision point - Values for model identifiers:
Template table #8
At the beginning of a project/program, decide and agree (between systems
engineering, logistics support analysis, and tech pubs) the vaules for the
attribute <dmCode@modelIdentCode>.
<dmAddress> System difference code Breakdown_element If explicit it can be part of the

<dmIdent> (SDC) indicates variants _identifier, 'Breakdown_element_identifier' for an aggregate
at the system, subsystem Breakdown_element breakdown element at any level of indenture in the product.
<dmCode@systemDiffCod
and sub-subsystem level.
e> _relationship_typ A 'Breakdown_element_identifier' that is defined using the
e principles defined in S1000D must be classified as
'ASD_system_hardware_identification_code'. The
SDC is then part of the identifier.
AD DEX reference for System difference can also be derived from possible usage of
Breakdown_element_identif 'Breakdown_element_relationship' between aggregate
ier:
breakdown elements at any level of indenture, where the
− DEX1AD section 'Breakdown_element_relationship_type' is set to
Breakdown aggregated 'Alternative_breakdown_element' (DEX reference:
element - Template
DEX1AD section Breakdown aggregated element - Template table #174).
table #170 or Template
table #171 Notes
AD DEX reference for 1. Defined in 1388-2b using System Logistic Usable On Code

Chap 5
S1003X-B6865-01003-00
definition
Breakdown_element_relati (SLUOC).
onship_type: 2. The S1000D principles for identifying an LSA-candidate contain:
− DEX1AD section − Model identification code
Breakdown aggregated
element - Template − Systems difference code
table #174 − System code
− Subsystem code
− Subsubsystem code
− Assembly code
− Disassembly code
− Disassembly code variant
The sum of these is referred to as the
'ASD_system_hardware_identification_code'.
<dmAddress> Data modules must reflect Breakdown_element Each Breakdown_element and Part being identified as being LSA
<dmIdent> the breakdown of the _identifier or candidates in S3000L can have an associated
Product. The initial Part_identifier 'Breakdown_element_identifier' or 'Part_identifier' being
<dmCode@systemCode>
breakdown is described classified as
<dmCode@subSystemCode by the Standard
> 'ASD_system_hardware_identification_code'. The
Numbering System AD DEX reference for
<dmCode@subSubSystemC (SNS). attributes <dmCode@systemCode>, <
Breakdown_element_identif
ode> ier: dmCode@subSystemCode>, <
<dmCode@assyCode> dmCode@subSubSystemCode> and < dmCode@assyCode>
− DEX1AD section
are then part of the identifier.
Hardware element
realization - Template This requires that the
table #130 or Template 'ASD_system_hardware_identification_code' being
table #131 associated with the respective LSA_candidate
or (Breakdown_element/Part), is established at design or during the

Chap 5
S1003X-B6865-01003-00
definition
− DEX1AD section LSA process.
Software element It is also possible to relate each Breakdown_element and Part to
realization - Template
Breakdown_elements in a separate S1000D Breakdown using
table #111 Breakdown_element_relationship. This
or Breakdown_element_relationship must then be classified as
'Design_to_S1000D_SNS_relationship'. The unique
− DEX1AD section
identifier for each Breakdown_element in the S1000D Breakdown will
element - Template then be the
table #170 or Template 'ASD_system_hardware_identification_code'.
table #171 A separate S1000D breakdown can be defined based on feedback data
or from S1000D to S3000L.
− DEX1AD section The common denominator for each breakdown element and part must be
Breakdown zone the 'Breakdown_element_identifier' and
element - Template 'Part_identifier' as established by design.
Note
table #184
Defined in 1388-2b using the Logistics Control Number (LCN).
AD DEX reference for
Part_identifier:
− DEX1AD section
Hardware part -
Template table #50 or
Template table #53
or
− DEX1AD section
Software part -
Template table #82

Chap 5
S1003X-B6865-01003-00
definition
<dmAddress> Identifies the breakdown Part_identifier Can be included in the

<dmIdent> condition of an assembly or 'ASD_system_hardware_identification_code' (ie a
to which maintenance Breakdown_element type of 'Part_identifier' or
<dmCode@disassyCode>
information applies or the
_identifier 'Breakdown_element_identifier') for Part and
order in which assemblies
are disassembled. Breakdown_element, respectively. Whether the
'ASD_system_hardware_identification_code' is is
Breakdown_element_identif defined for the Part or Breakdown_element is dependent upon the
ier: philosophy for the breakdown.
− DEX1AD section Refer to mapping under the element

Hardware element <dmIdent><dmCode@SystemCode> above.
realization - Template Note
Defined in 1388-2b using the Logistics Control Number (LCN).
table #131
or
− DEX1AD section
Software element
table #111
or
− DEX1AD section
element - Template
table #171
or

Chap 5
S1003X-B6865-01003-00
definition
− DEX1AD section
Breakdown zone
element - Template
table #184
Part_identifier:
− DEX1AD section
Hardware part -
Template table #53
or
− DEX1AD section
Software part -
Template table #82
<dmAddress> Designates alternative Part_identifier Refer to mapping under the element

<dmIdent> items of equipment or or <dmIdent><dmCode@disassyCode> above.
components differing Breakdown_element Note
<dmCode@
slightly in design, but not
disassyCodeVariant> enough to warrant a _identifier Defined in 1388-2b using the Alternative LCN (ALC).
change of the SDC.
ier:
− DEX1AD section
Hardware element

Chap 5
S1003X-B6865-01003-00
definition
table #131
or
− DEX1AD section
Software element
table #111
or
− DEX1AD section
element - Template
table #171
or
− DEX1AD section
Breakdown zone
element - Template
table #184
Part_identifier:
− DEX1AD section
Hardware part -
Template table #53
or
− DEX1AD section
Software part -

Chap 5
S1003X-B6865-01003-00
definition
Template table #82
<dmAddress> Identifies the type of Information_code 'Information_code' associated with Task.

<dmIdent> information within a data
module. 'Information_code' is used to categorize the task/subtask in
<dmCode@infoCode> AD DEX reference: S3000L by allocating S1000D Information Codes (IC).
− DEX3AD section Task When allocating the 'project specific "Not given" ICs', their allocation must
definition - Template be harmonized between S3000L and S1000D.
table #6 If multiple tasks with the same ‘Information_code’ are associated
with a specific instance of Breakdown_element or Part, then these
tasks can be candidates for being identified using different Information Code
Variants (ICV).
A task which contains multiple subtasks with the same
'Information_code' can be a candidate for being split into multiple
data modules, identified using different ICVs.
Example
Performance of an automated test (IC 342), using different test equipments
can require different maintenance procedures.
Business rule decision point - Multiple tasks and subtasks:
Decide wether to break tasks and subtasks down and identify them using
the ICV.
<dmAddress> Identifies any variation in N/A Notes

<dmIdent> the activity defined by the 1. There is no explicit variant code in S3000L.
IC.
<dmCode@ 2. Defined in 1388-2b using Task Function within the Task Code
infoCodeVariant>

Chap 5
S1003X-B6865-01003-00
definition
<dmAddress> Identifies where the Maintenance_locat Maintenance_location_code is defined in S3000L using

<dmIdent> maintenance task will be ion_code reference data that corresponds to the
carried out. <dmCode@itemLocationCode> code values A, B, C, D:
<dmCode@itemLocationC
ode> AD DEX reference: − Maintenance_location_code = ‘On_product_task’
equals <dmCode@itemLocationCode = ‘A’>
− DEX3AD section
Subtask by definition - − Maintenance_location_code =
Template table #44 ‘Off_product_on_major_assembly_task’ equals
<dmCode@itemLocationCode = ‘B’>
− Maintenance_location_code =
‘Off_product_on_bench_task’ equals
<dmCode@itemLocationCode = ‘C’>
− Maintenance_location_code =
‘On_and_off_product_task’ equals
<dmCode@itemLocationCode = ‘D’>.
Note
Maintenance_location_code is assigned to the respective
subtask in S3000L, and not to the overall task.
<dmAddress> Must reflect the Breakdown_element If there is a 'Breakdown_element_name' or 'Part_name'

<dmAddressItems> nomenclature of the _name or which is classified as ‘Breakdown_element_techname’ or
hardware or function. Part_name
<dmTitle> 'Part_techname' respectively, then use that name to populate the
<techName> element <techName>.
AD DEX reference for Note
Breakdown_element_name If Breakdown_elements and Parts have multiple names, but
:
no explicit ‘_techname’, then a project business rule needs to be
− DEX1AD section established that determines which

Chap 5
S1003X-B6865-01003-00
definition
Hardware element 'Breakdown_element_name' or 'Part_name' to use for
realization - Template populating the element <techName>.
table #132
Business rule decision point - Multiple names for breakdown elements
or and parts:
− DEX1AD section If Breakdown_elements and Parts have multiple names, but no
Software element
explicit ‘techname’, decide which name to use to populate the element
table #152 <dmTitle><techName>.
or
− DEX1AD section
element - Template
table #172
or
− DEX1AD section
Breakdown zone
element - Template
table #185
Part_name:
− DEX1AD section
Hardware part -
Template table #52
or
− DEX1AD section
Software part -
Template table #83

Chap 5
S1003X-B6865-01003-00
definition
Normally the information Task_name
<dmAddress> The Task_name is used to populate the element <infoName>. However,
name is the short
<dmAddressItems> tasks can have multiple names.
description of the
<dmTitle> information code. AD DEX reference: Business rule decision point - Multiple names for tasks:
<infoName> However, projects can If tasks have multiple names, but no explicit ‘infoName’, decide which name
decide to modify (or − DEX3AD section Task
definition - Template to use to populate the element <dmTitle><infoName>.
extend) the information
name to one that is more table #1 or Template
suitable, table #4
<dmStatus> The security classification Security_class <security@securityClassification> can be derived from

<security@ of the complete data the security classification of Breakdown_element, Part,
module.
securityClassification Security_class AD DEX Task_requirement, Task or Subtask in S3000L.
> reference for Note
Breakdown_element and Security classification for a breakdown element or part must be
Part: propagated to the respective task being associated with the
− DEX1AD section breakdown element/part.
Security classification -
Template table #320
Security_class AD DEX
reference for Task,
Subtask_by_definition and
Task_requirement:
− DEX3AD section
Template table #320

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Project rule. N/A

<security@
commercialClassificati
on>
<dmStatus> Project rule. N/A
<security@caveat>
<dmStatus> Contains the authorized N/A This element is seldom used

<techStandard> technical standard and
associated data to be
entered, describing the
information basis used to
write the data module.
<dmStatus> The authority that owns N/A

<techStandard> the source data from
which the data module is
<authorityInfoAndTp>
written. Describing the
<authorityInfo> information basis used to
write the data module.

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Technical publication Task_identifier@ In order to establish an S1000D feedback to S3000L, this field must contain
<techStandard> baseline to which the data Identifier, the Task_identifier, Task_revision_identifier and
module is written. Task_identifier@ optionally Task_revision_status, from which the data module is
<authorityInfoAndTp>
<techPubBase> Identifier_set_b being developed. Tasks can, however, have multiple identifiers.
y_organization, Business rule decision point - Multiple identifiers for tasks:
Task_revision_id If tasks have multiple identifiers, decide which identifier to use to populate
entifier, the element <authorityInfoAndTp><techPubBase>.
Task_revision_st Note
atus A data module can be developed for more than one S3000L task,
which means that this element will contain more than one set of task
AD DEX reference for identification information.
Task_identifier@Identifier,
Task_identifier@Identifier_
set_by_organization and
Task_revision_identifier:
− DEX3AD section Task
definition - Template
table #3
Task_revision_status:
table #10)
<dmStatus> For those projects that Breakdown_element Breakdown_element_identifier for the Breakdown element
<systemBreakdownCode> are producing data _identifier being used within a physical breakdown, ie the associated Breakdown

Chap 5
S1003X-B6865-01003-00
definition
modules that are in line attribute 'Breakdown_type' indicates a "Physical" value (DEX
with other logistic AD DEX reference: reference: DEX1AD section Breakdown structure - Template table #36).
databases, the system
breakdown code can be − DEX1AD section Associations between the "functional" and "physical" breakdown elements in
Hardware element S3000L can be established as either:
used to capture the
physical breakdown code. realization - Template − A Breakdown_element_relationship between two
table #130 or #134 Breakdown_elements, where the
or 'Breakdown_element_relationship_type' value is set
− DEX1AD section to
Software element ‘Functional_physical_breakdown_element_relati
realization - Template onship’ (DEX reference: DEX1AD section Hardware element
table #150 or #154 realization - Template table #134, or section Software element
realization - Template table #154)
− Usage of the same Breakdown_element within multiple types of
Breakdowns, ie the Breakdown element has multiple instances of
'Breakdow_element_usage_in_breakdown', which
relates the Breakdown element to different types of Breakdowns of the
same Product (eg one "functional" breakdown and one "physical"
breakdown) (DEX reference: DEX1AD section Hardware element
realization - Template table #130, or section Software element
realization - Template table #150)
Business rule decision point - Multiple identifiers for breakdown
elements:
If Breakdown elements have multiple identifiers, decide which identifer to
use to populate the element
<dmStatus><systemBreakdownCode>.
Notes
1. Defined in 1388-2b using Logistics Control Number (LCN) - Physical.

Chap 5
S1003X-B6865-01003-00
definition
2. Defined in S2000M using the Text Element Identifier (TEI) ILS.
<dmStatus> Used to capture the N/A This element is redundant with the element <functionalItemRef>
<functionalItemCode> functional breakdown below. The use of is this element is therefore deprecated.
code.
<dmStatus> Uniquely identify an item Breakdown_element Breakdown element being used within a functional or family breakdown, ie
<functionalItemRef> performing a function in a the associated Breakdown attribute 'Breakdown_type' indicates a
system at a given 'Functional' value (DEX reference: DEX1AD section Breakdown structure -
position. AD DEX reference: Template table #36).
− DEX1AD section Note
Hardware element
realization - Template Functional item ref can be either exact or by family.
table #130
or
− DEX1AD section
Software element
table #150

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> The functional item Breakdown_element Breakdown_element_identifier for the Breakdown element
<functionalItemRef@fu number value. _identifier being used within a functional breakdown, ie the associated Breakdown
nctionalItemNumber> attribute 'Breakdown_type' indicates a 'Functional' value (DEX
reference: DEX1AD section Breakdown structure - Template table #36).
AD DEX reference:
− DEX1AD section elements:
Hardware element
realization - Template If Breakdown elements have multiple identifiers, decide which identifer to
table #130 or #134 use to populate the attribute
<functionalItemRef@functionalItemNumber>.
or
Notes
− DEX1AD section
Software element Also refer to the mapping for element <dmStatus>
realization - Template <systemBreakdownCode> above.
table #150 or #154 1. Defined in 1388-2b using Logistics Control Number (LCN) -
Functional.
2. Defined in S2000M using the attribute ILS.
3. This element has double meanings. Both specific function and
generic functions are addressed.
4. Use of generic functions need to be Harmonized with S4000M.
<dmStatus> Indicates whether it is an N/A If functionalItemNumber is populated then set the value of the attribute
<functionalItemRef@fu exact functional item <functionalItemRef@functionalItemType> to 'Exact'.
number (a given item) or
nctionalItemType>
a family functional item
number (generic code for
one component which has
more than one position.
Eg: seats, lights).

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Supplier NCAGE code Part_identifier@I The Part that can realize the functional breakdown element is identified via
<functionalItemRef@ma (for example in case of a dentifier_set_by_ either:
component provided by
nufacturerCodeValue> organization − Hardware_part_realization (DEX reference: DEX1AD
external company).
section Hardware element realization - Template table #143)
AD DEX reference: − Software_part_realization (DEX reference: DEX1AD
section Software element realization - Template table #164).
− DEX1AD section
Hardware part - Assign the id for the Organization that 'owns' the Part_identifier,
Template table #50 or where Organization_identifier@Identifier_class
#53 equals 'NCAGE_code'.
or Note
− DEX1AD section Identifier_set_by_organization is part of the S3000L
Software part -
data type Id.
#82

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Coding of the functional Breakdown_element The Breakdown_element_name can be used to populate the
<functionalItemRef> item number _name element <name>. However, the breakdown element can have multiple
nomenclature. names.
<name>
AD DEX reference: Business rule decision point - Multiple names for breakdown
elements:
− DEX1AD section
Hardware element If Breakdown elements have multiple names, decide which name to use to
realization - Template populate the element <functionalItemRef><name>.
table #132
or
− DEX1AD section
Software element
table #152
<dmStatus> To ensure the traceability N/A When this is used, it is generated by Tech Docs and the master DMC is
<sourceDmIdent> of the master data exchanged with S3000L and not the DME customer deliverable DMCs.
module, related to its
instances, it is possible to
record the identification of
the source data module
from which an instance
has been derived.
<dmStatus> Contains a pointer to the N/A

<applicCrossRefTableRe Applicability Cross-
reference Table (ACT)
f>
data module that applies
to the data module.

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> The overall applicability Applicability_sta An Applicability_statement associated with a Task in S3000L
<applic> for an entire data module. tement can equal the element <applic> for the entire data module.
Refer to Note 5 at Para 2.3.
AD DEX reference: Business rule decision point – Use of applicability:
− DEX3AD section Decide how to use applicability for the project/program both initially and
Textual (not- through life with revisions.
computable) Examples:
applicability statement -
Template table #370 − Define permitted product attributes (Refer to Para 5.2 on applicability
cross-reference table).
or
− Define permitted conditions (Refer to Para 5.3 on condition cross-
− DEX3AD section Dated reference table).
applicability statement
applicability statement - − Define task generality and usage of applicability at, for example,
Template table #380 task/subtask/task resource levels.
or
− DEX3AD section
Applicability statement
by assertion of serial
number - Template
table #390
or
− DEX3AD section
by assertion of
condition parameters
(except serial number) -
Template table #400

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Provides human readable Applicability_sta Applicability_statement_description for the associated

<applic> applicability information. tement_descriptio Applicability_statement.
<displayText> n
<simplePara>
AD DEX reference:
− DEX3AD section
Textual (not-
computable)
Template table #372
or
− DEX3AD section Dated
applicability statement
Template table #382
or
− DEX3AD section
number - Template
table #392
or
− DEX3AD section
by assertion of
Template table #402

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Provides applicability Logical_operator Use of

<applic> information in a subclasses ‘AND’ and 'Applicability_evaluation_by_logical_operator' and
computable format which ‘OR’, respectively the 'Logical_operator' subclasses 'AND' or 'OR',
<evaluate@andOr>
can be used to support respectively:
dynamic display of the
annotated content. If 'Logical_operator' subclass 'AND' is used, then set the
AD DEX reference:
attribute <evaluate@andOr> to 'and'.
− DEX3AD section
Applicability statement If 'Logical_operator' subclass 'OR' is used, then set
using logical operators the attribute <evaluate@andOr> to 'or'.
- Template table #420

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> Provides applicability Applicability_eva Use of either

<applic> information in a luation_by_assert 'Applicability_evaluation_by_assertion_of_clas
computable format which ion s_instance' or
<assert>
can be used to support
'Applicability_evaluation_by_assertion_of_cond
dynamic display of the
annotated content, by ition'.
AD DEX reference:
specifying the product
attribute or condition to − DEX3AD section
test and the values to test Applicability statement
against. by assertion of serial
number - Template
table #390
or
− DEX3AD section
by assertion of
Template table #400
<dmStatus> Either the product Condition_type_na Type of condition or value to be asserted:

<applic> identifier from the ACT me, Condition_type_name:
data module) or condition Condition_identif
<assert@applicPropert
identifier from the CCT − The value given in Condition_type_name, if the applicability
yIdent> data module) to test. ier,
statement refers to an instance of Condition_statement which
Maintenance_level
in turn refers to an instance of Condition_type as its
_type,
Condition_definition.
Maintenance_locat
ion, − The value of the attribute <assert@applicPropertyIdent>
Operating_locatio is exchanged in two different ways using DEX3AD. This is due to that
the condition type value can be defined as either a property value or as
n_type, a class value. If the condition type value is represented as a property

Chap 5
S1003X-B6865-01003-00
definition
Operating_locatio then use the value defined in Template table #406 input parameter
n, ‘property_class_name’ to populate the attribute
Breakdown_element < assert@applicPropertyIdent>. If the condition type
, Part, User, value is represented as a class value then use the value defined in
Customer, Template table #400 input parameter ‘para_class’ to populate the
attribute <assert@applicPropertyIdent>.
Contract,
Product_variant, Condition_identifier:
Product_variant_r − The value given in Condition_identifier, if the applicability
ealization and statement refers to an instance of Condition_statement which
Product_usage_pha in turn refers to an instance of Condition_by_identifier as
se its Condition_definition.
Note
AD DEX reference for The value of the attribute
Condition_type: <assert@applicPropertyIdent> is exchanged using
− DEX3AD section Template table #408 input parameter ‘id’.
assertion - Template
table #406 if the Maintenance_level_type:
condition type value is − populate the attribute <assert@applicPropertyIdent> with string
represented as a value ‘maintenanceLevel’, if the applicability statement refers to an
property in the DEX instance of Maintenance_level_type
− DEX3AD section Maintenance_location:
assertion - Template − populate the attribute <assert@applicPropertyIdent> with
table #400 if the string value ‘maintenanceLocation’, if the applicability statement refers
condition type value is to an instance of Maintenance_location
represented as a class
value in the DEX Operating_location_type:

Chap 5
S1003X-B6865-01003-00
definition
AD DEX reference for − populate the attribute <assert@applicPropertyIdent> with
Condition_by_identifier: string value ‘operatingLocationType’, if the applicability statement refers
− DEX3AD section to an instance of Operating_location_type
Applicability statement Operating_location:
table #408 − populate the attribute <assert@applicPropertyIdent> with
AD DEX reference for string value ‘operatingLocation’, if the applicability statement refers to an
Maintenance_level_type: instance of Operating_location
− DEX3AD section Breakdown_element:
Applicability statement − populate the attribute <assert@applicPropertyIdent> with
assertion and its
string value ‘breakdownElement’, if the applicability statement refers to
reference to DEX3AD
section Task an instance of Breakdown_element
assignment - Template Part:
table #154
− populate the attribute <assert@applicPropertyIdent> with
AD DEX reference for string value ‘part’, if the applicability statement refers to an instance of
Maintenance_location:
Part
− DEX3AD section
Applicability statement − populate the attribute <assert@applicPropertyIdent> with
assertion and its string value 'partSerialNumberRange', if the value refers to an instance
reference to DEX3AD of Part which in turn refers to an instance of
section Task Block_of_serialized_items (DEX reference: DEX3AD
assignment - Template section Applicability statement by assertion of serial number - Template
table #152 table #390)
AD DEX reference for User:
Operating_location_type:
− DEX3AD section string value ‘user’, if the applicability statement refers to an instance of
Applicability statement User
assertion and its

Chap 5
S1003X-B6865-01003-00
definition
reference to DEX3AD Customer:
section Task
assignment - Template − populate the attribute <assert@applicPropertyIdent> with
table #158 string value ‘customer’, if the applicability statement refers to an
instance of Customer
Operating_location: Contract:
− DEX3AD section − populate the attribute <assert@applicPropertyIdent> with
Applicability statement string value ‘contract’, if the applicability statement refers to an instance
assertion and its of Contract
reference to DEX3AD
section Task Product_variant:
assignment - Template − populate the attribute <assert@applicPropertyIdent> with
table #156
string value 'productVariant', if the value refers to an instance of
AD DEX reference for Product_variant
Breakdown_element:
− DEX3AD section string value 'endItemSerialNumberRange', if the value refers to an
instance of Product_variant which in turn refers to an instance
assertion and its
references to either of Block_of_serialized_items (DEX reference: DEX3AD
DEX1AD section section Applicability statement by assertion of serial number - Template
Breakdown element table #390)
realization (Template Product_variant_realization:
tables #130 and #150),
or DEX1AD section − populate the attribute <assert@applicPropertyIdent> with
Aggregated breakdown string value 'productConfiguration', if the value refers to an instance of
element (Template Product_variant_realization
table #170)
Product_usage_phase:
AD DEX reference for Part:
− DEX3AD section string value ‘productUsagePhase’ if the value refers to an instance of

Chap 5
S1003X-B6865-01003-00
definition
assertion and its Product_usage_phase
references to DEX1AD
Note
section Part - Template
tables #50 and #80 Refer to Para 5 - Applicability.
− DEX3AD section
number - Template
table #390
− DEX3AD section
assertion and its
section Product and
Project - Template
table #22
Customer:
− DEX3AD section
assertion and its
section Product and
Project - Template
table #19
Contract:
− DEX3AD section

Chap 5
S1003X-B6865-01003-00
definition
assertion and its
section Product and
Project - Template
table #15
Product_variant:
− DEX3AD section
assertion and its
section Product and
Project - Template
table #15
− DEX3AD section
number - Template
table #390
Product_variant_realization
:
− DEX3AD section
assertion and its
section Product variant
applicability - Template
table #203

Chap 5
S1003X-B6865-01003-00
definition
− DEX3AD section
table #410
<dmStatus> Indicates whether the Condition_type, The value to populate the attribute
<applic> applicability property Condition_by_iden <assert@applicPropertyType> is derived from the type of
identifier value references tifier, class that is being used in the
<assert@applicPropert
a product attribute or a Applicability_evaluation_by_assertion:
yType> condition. Maintenance_level
_type, − The attribute <assert@applicPropertyType> shall be set to
Maintenance_locat 'condition' if the
ion, Applicability_evaluation_by_assertion referes to
Operating_locatio an instance of:
n_type, • Condition_type
Operating_locatio • Condition_by_identifier
n, • Maintenance_level_type
Breakdown_element
• Maintenance_location
, Part, User,
Customer, • Operating_location_type
Contract, • Operating_location
Product_variant, • Breakdown_element
Product_variant_r • Part
ealization and
• Customer
Product_usage_pha
se • User
• Contract

Chap 5
S1003X-B6865-01003-00
definition
Refer to AD DEX • Product_usage_phase
references defined for the
− The attribute <assert@applicPropertyType> shall be set to
<dmStatus><applic
'prodattr' if the
><assert@applicP Applicability_evaluation_by_assertion referes to
ropertyIdent> an instance of:
attribute above.
• Product_variant
• Product_variant_realization
Note
Refer to Para 5 - Applicability.
<dmStatus> The values and/or ranges Condition_type_c The value to assert (ie value that can populate the attribute
<applic> to test against. lass_value, <assert@applicPropertyValues>) must equal one of the
<assert@applicPropert Condition_type_p following:
yValues> roperty_value, − Condition_type_class_value if:
Maintenance_leve • The Condition_definition refers to a
l_type_name, Condition_type whose condition type value is
Maintenance_loca represented as a class value (DEX reference - DEX3AD section
tion_name, Applicability statement assertion - Template table #400)
Operating_locati • if the Condition_definition refers to a
on_type_name, Condition_by_identifier whose value is
Operating_locati represented as a class value (DEX reference - DEX3AD section
on_name, Applicability statement assertion - Template table #408)
Breakdown_elemen − Condition_type_property_value if the
t_identifier, Condition_definition refers to a Condition_type
Part_identifier, whose condition type value is represented as a property (DEX reference
Organization_nam - DEX3AD section Applicability statement assertion - Template table
e #406)

Chap 5
S1003X-B6865-01003-00
definition
Contract_identif − Maintenance_level_type_name, if the attribute
ier, <assert@applicPropertyIdent> is defined as
Product_variant_ 'maintenanceLevel’
identifier, − Maintenance_location_name, if the attribute
Product_variant_ <assert@applicPropertyIdent> is given the value
realization_iden 'maintenanceLocation’
tifier, − Operating_location_type_name, if the attribute
Serial_number_lo <assert@applicPropertyIdent> is given the value
wer_bound, 'operatingLocationType’
Serial_number_up
− Operating_location_name, if the attribute
per_bound and
<assert@applicPropertyIdent> is given the value
Product_usage_ph 'operatingLocation’
ase
− Breakdown_element_identifier, if the attribute
AD DEX reference for 'breakdownElement’
Condition_type_class_valu
e:
elements:
− DEX3AD section
If Breakdown elements have multiple identifiers, decide which identifer to
use to populate the attribute
<assert@applicPropertyValues>.
table #405 if the
Condition_definition − Part_identifier, if the attribute
refers to a <assert@applicPropertyIdent> is given the value 'part’
Condition_type whose
condition type value is Business rule decision point - Multiple identifiers for parts:
represented as a class If parts have multiple identifiers, decide which identifer to use to populate
value (ie the attribute <assert@applicPropertyValues>.
Condition_type_class_v
− Organization_name if the attribute

Chap 5
S1003X-B6865-01003-00
definition
alue) <assert@applicPropertyIdent> is given the value 'user' or
− DEX3AD section ‘customer’
Applicability statement − Contract_identifier if the attribute
assertion - Template <assert@applicPropertyIdent> is given the value
table #409 if the
'contract'
Condition_definition
refers to a Business rule decision point - Multiple identifiers for contracts:
Condition_by_identifier If contracts have multiple identifiers, decide which identifer to use to
whose value is populate the attribute <assert@applicPropertyValues>.
value (ie − Product_variant_identifier, if the attribute
Condition_type_class_v <assert@applicPropertyIdent> is given the value
alue) 'productVariant'
AD DEX reference for Business rule decision point - Multiple identifiers for product variants:
Condition_type_property_v
If product variants have multiple identifiers, decide which identifer to use to
alue:
populate the attribute <assert@applicPropertyValues>.
− DEX3AD section
Applicability statement − Product_variant_realization_identifier, if the
assertion - Template attribute <assert@applicPropertyIdent> is given the value
table #407 if the 'productConfiguration'
Condition_definition − Serial_number_lower_bound and
referes to a
Condition_type whose
Serial_number_upper_bound , if
value is represented as <assert@applicPropertyValue is given the value
a property (ie 'endItemSerialNumberRange'
Condition_type_propert − Product_usage_phase if the attribute
y_value)
AD DEX reference for ‘productUsagePhase’
Maintenance_level_type_n
Notes
ame:
1. In an integration of S1000D and S3000L positive statements should

Chap 5
S1003X-B6865-01003-00
definition
− DEX3AD section always be used, ie the assert value should always be 'true'.
Applicability statement 2. Refer to Para 5 - Applicability.
assertion and its
reference to DEX3AD
section Task
assignment - Template
table #154
Maintenance_location_nam
e:
− DEX3AD section
assertion and its
reference to DEX3AD
section Task
table #152
Operating_location_type_n
ame:
− DEX3AD section
assertion and its
reference to DEX3AD
section Task
table #158
Operating_location_name:
− DEX3AD section

Chap 5
S1003X-B6865-01003-00
definition
assertion and its
reference to DEX3AD
section Task
table #156
ier:
− DEX3AD section
assertion and its
references to either
DEX1AD section
Breakdown element
realization (Template
tables #130/ #131 and
#150/#151), or
DEX1AD section
Aggregated breakdown
element (Template
table #170/#171)
Part_identifier:
− DEX3AD section
assertion and its
tables #50/#53 and

Chap 5
S1003X-B6865-01003-00
definition
#80/#82
Organization_name:
− DEX3AD section
assertion and its
section Product and
Project - Template
table #22, for User
− DEX3AD section
assertion and its
section Product and
Project - Template
table #19, for Customer
Contract_identifier:
− DEX3AD section
assertion and its
section Product and
Project - Template
table #15/#16
Product_variant_identifier:
− DEX3AD section

Chap 5
S1003X-B6865-01003-00
definition
assertion and its
section Product and
Project - Template
table #6/#8
_identifier:
− DEX3AD section
assertion and its
section Product variant
applicability- Template
table #201
Serial_number_lower_boun
d/
Serial_numbe_upper_boun
d:
− DEX3AD section
number - Template
table #390
− DEX3AD section

Chap 5
S1003X-B6865-01003-00
definition
table #410
<dmStatus> Provides a container for For detailed mapping of the elements of <applic> and its subelements
<referencedApplicGroup defining applicability refer to the <dmStatus><applic> mappings above. Refer to Note 5 at
> annotations that apply to Para 2.3.
various parts of the data
module. Such applicability This element can collect Applicability_statements used within an S3000L
annotations can be used Task and which are identified using the
to restrict the applicability Applicability_statement_identifier. These
for a substructure of the Applicability_satatements can then be referenced from within
data module, compared to the data module using the attribute <XXX@applicRefId>.
the applicability specified
for the whole data The only thing that will differ between the <dmStatus><applic>
module. mappings above and the
<dmStatus><referencedApplicGroup> mapping is the use of
the attribute <applic@id>
<dmStatus> The identifier of the Applicability_st Applicability_statement_identifier

<referencedApplicGroup element. atement_identifi Refer to the mapping details under the element
> er <dmStatus><referencedApplicGroup> above.
<applic@id>
AD DEX reference:
− DEX3AD section
Applicability statement -
Template tables #371,
#381, #391 and #402

Chap 5
S1003X-B6865-01003-00
definition
<dmStatus> A short explanation of the Task_revision_ch Task_revision_change_description

<reasonForUpdate> reason for updating of the ange_description
data module.
AD DEX reference:
table #18
<dmStatus> Contains an indication N/A

<productSafety> when a module is
transmitting information
that affects the safety of
the product's users.
<dmStatus> The skill level to which the N/A

<skillLevel@skillLeve data module has been
written.
lCode>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.3 Notes for Table 2

These notes are provided to give clarification to many of the entries in Table 2.
Note 1
The product breakdown is defined during design and is exchanged using DEX1AD. This
breakdown structure is used by both S1000D and S3000L as the anchor points for which
tasks and data modules are defined.
It is recognized that the S3000L process may identify additional candidate breakdown
elements that are not indicated in the breakdown as defined during design. However, these
additional candidates would always map back to the design breakdown structure in some
way. Zonal breakdown elements are examples of breakdown elements that might be
created during an LSA.
Note 2
For S1000D, the SNS will be applied to the breakdown elements. S1000D will allocate ICs
to data modules based on the S3000L Information_codes that are assigned to the tasks
and subtasks.
When the complete DMCs are built, they are exchanged back to S3000L environment to
give the traceability between tasks and data modules.
Note 3
Where S3000L "refers out" to an existing task narrative this must be exchanged with
S1000D so that S1000D sees that one data module is required for the task, used in multiple
places.
Note 4
When the need for ICV is exchanged a plain text definition for the allocation of the ICV must
be exchanged so that the element <infoName> is modified in S1000D appropriately.
For example SNS = wheel Infoname = remove ICV = front left or rear left, ICV = A, ICV = B,
respectively.
Note 5
The use of element <applic> and the element <referencedApplicGroup> are
the same throughout the schemas, and will not be repeated for each occurrence in the
schemas.
3 S1000D Maintenance procedure

3.1 Introduction
The Maintenance procedure schema is used to capture and represent procedural information.
The granularity of maintenance procedure data modules follows the breakdown given by the
SNS, and reflects the tasks identified in the maintenance plan.
The procedure covers all information necessary to carry out the task and describes:
− Any actions to be carried out or conditions that must be satisfied before the main procedure
is started (the element <preliminaryRqmts>), including personnel, required technical
information, support equipment, supplies and spares that are needed to perform the
procedure to its completion.
− The detailed procedural steps to be carried out (the element <mainProcedure>).
− Any actions that are required after the main procedure is complete, to return the product to
a serviceable condition or the conditions that must be satisfied to have the product in a
serviceable condition (the element <closeRqmts>).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Note
Maintenance procedures applies to Tasks being instances of both ‘Rectifying_task’,
‘Supporting_task’ and ‘Logistics_operational_task’, for which the value of
S1000D_task_type_code is set to 'Procedure_task' (DEX reference: DEX3AD section Task
definition – Template tables #2 and #5).The S1000D_task_type attribute defines how a
task in S3000L corresponds with the schemas defined in S1000D:
• 'Procedure_task' = S1000D proced Schema

• 'Package_task' = S1000D schedul Schema
Note
The element <warningAndCautions> is directly under the element <content>.
This is a collection element that can contain all the warnings and cautions that are needed
for the data module. These are then referenced from the warning or caution elements within
the data module. This element needs to be populated by the author.S1000D in accordance
with the procedural Schema
3.2 Preliminary requirements

Table 3 describes the elements and attributes in preliminaryRqmts (Preliminary requirements).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 3 PreliminaryRqmts (Preliminary requirements) - Elements and attributes

definition
<preliminaryRqmts> Contains the basic

<productionMaintData> information required for
the planning and
preparation of the task.
<preliminaryRqmts> Note
<productionMaintData> The element <thresholdInterval> is not to be used for the
<thresholdInterval> procedure data module. Refer to Para 4.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Zoning information (one Breakdown_element Can be derived from either:

<productionMaintData> or more). _identifier − 'Core' Subtasks, and their respective Subtask_in_zone
<zoneRef@zoneNumber> association with a Zone_element (DEX reference: DEX3AD section
AD DEX reference: Subtask by definition - Template table #47)
− DEX1AD section or
Breakdown zone − An assumption that the same as the Zone_element which can be
element - Template identified via the
table #183 or Template Hardware_element_in_zone_relationship for the
table #184 Hardware_element, on which the Task, and/or 'Core' Subtasks,
is being performed (DEX reference: DEX1AD section Breakdown zone
element - Template table #192).
The associated Zone_element must be categorized as zone, ie the
attribute Zone_element_type is set to 'Zone_element' (DEX
reference: DEX1AD section Breakdown zone element - Template table
#186).
Business rule decision point - Multiple identifiers for zone elements:
If zone elements have multiple identifiers, decide which identifer to use to
populate the attribute <zoneRef@zoneNumber>.
Note
Defined in 1388-2b using Work area code.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Breakdown_element Refer to the element <zoneRef@zoneNumber> above for mapping

<productionMaintData> _name information.
<zoneRef> Business rule decision point - Multiple names for zone names:
<name> AD DEX reference: If zone elements have multiple names, decide which name to use to
populate the element <zoneRef><name>.
− DEX1AD section
Breakdown zone
element - Template
table #185
<preliminaryRqmts> Describe any (one or Breakdown_element <accessPointRef@accessPointNumber> can be derived if

<productionMaintData> more) access points like _identifier either:
panels, doors, hatches.
<accessPointRef@acces − The Hardware_element to which the Task is assigned is related
sPointNumber> AD DEX reference: to another Hardware_element, using a
− DEX1AD section
Breakdown_element_relationship where the
Hardware element Breakdown_element_relationship_type value is set to
realization - Template ‘Access_point’ (DEX reference: DEX1AD section Hardware
table #130 or Template element realization - Template table #134)
table #131 or
− If the Task contains Subtask(s) which gives access, eg via an
access point. These subtasks will be categorized by
Information_code = 540 and must be 'Startup' subtasks.
DEX reference for identifying ‘Startup’ subtasks:
• DEX3AD section Subtask by reference - Template table #25, if
subtask by reference
or
• DEX3AD section Subtask by definition - Template table #41 if

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
subtask by definition
DEX reference for identifying ‘Information_code’:
• DEX3AD section Task definition - Template table #6 if subtask
by reference
or
• DEX3AD section Subtask by definition - Template table #43 if
subtask by definition
The value for the attribute
<accessPointRef@accessPointNumber> can then be set to
the identifier for breakdown element which is related via the
Task_target_item or Subtask_target_item relationship,
respectively
DEX reference for identifying Task_target_item or
Subtask_target_item:
• DEX3AD section Task assignment - Template table #140 for
task target item,
or
• DEX3AD section Subtask by definition - Template table #55 for
subtask target item).
Notes
1. This mapping applies to 'Closeup' subtasks as well, with the
exception that closeup subtasks will be categorized by
Information_code = 740.
2. Breakdown elements which can play the role of access points can
be verified by checking that the ‘Hardware_element_type’
equals 'Door_element', 'Control_panel' or

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
'Hatch_element' (DEX reference: DEX1AD section Hardware
element realization - Template table #133).
Business rule decision point - Multiple identifiers for zone elements:
If zone elements have multiple identifiers, decide which identifer to use to
populate the attribute
<accessPointRef@accessPointNumber>.
<preliminaryRqmts> Access point type. Hardware_element_ For mapping information refer to the attribute
<productionMaintData> type <preliminaryRqmts><productionMaintData>
<accessPointRef@acces <accessPointRef@accessPointNumber> above.
AD DEX reference:
sPointTypeValue> − DEX1AD section
Hardware element
table #133
<preliminaryRqmts> The name of the access Breakdown_element For mapping information refer to the attribute
<productionMaintData> point. _name <preliminaryRqmts><productionMaintData>
<accessPointRef> <accessPointRef@accessPointnumber> above.
<name> AD DEX reference: Business rule decision point - Multiple names for zone names:
− DEX1AD section If zone elements have multiple names, decide which name to use to
Hardware element populate the element <accessPointRef><name>.
table #132)

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Area where work is Breakdown_element Can be derived from:

<productionMaintData> accomplished. _name − 'Core' Subtasks, and their respective Subtask_in_zone
<workArea> association with Zone_element (DEX reference: DEX3AD section
AD DEX reference: Subtask by definition - Template table #47)
− DEX1AD section or
Hardware element − Be assumed to be the same as the Zone_element which can be
realization - Template identified via the
table #132 Hardware_element_in_zone_relationship for the
Hardware_element, on which the Task, and/or 'Core' Subtasks,
is being performed (DEX reference: DEX1AD section Breakdown zone
element - Template table #192).
The associated Zone_element must be categorized as a work area (ie
the attribute Zone_element_type is set to 'Work_area') (DEX
reference: DEX1AD section Breakdown zone element - Template table
#186).
Business rule decision point - Categorization of a zone as a work area:
Decide on the categorization of the zone element as a work area to
populate the element <workArea>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The unit of measure for all Subtask_duration/ The lowest common time unit for the Property_representations
<productionMaintData> taskDurations (startup, Task_duration that is used to represent the
procedure and closeup). Subtask_durations/Task_durations within the Task under
<taskDuration@unitOfM
easure> consideration.
AD DEX reference:
table #12 if task
duration,
or
− DEX3AD section
Subtask by definition -
Template table #46 if
subtask duration
<preliminaryRqmts> Duration for performing Subtask_duration/ Summarize (roll-up) the durations for all subtasks classified as
<productionMaintData> preliminary requirements. Task_duration 'Startup_subtask'.
<taskDuration@startup Notes
Duration> AD DEX reference: 1. Roll-up can also consider Subtask_timeline (DEX reference:
− DEX3AD section Task DEX3AD section Subtask by reference - Template tables #26 and
definition - Template #27).
table #12 if task 2. Roll-up must also consider Task_duration for any
duration, Subtask_by_reference.
or 3. Defined in 1388-2b using Elapsed Time.
− DEX3AD section 4. Refer to Note 1 at Para 3.3.
subtask duration

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<productionMaintData> the procedure. Task_duration 'Core_subtask' (incl.
<taskDuration@procedu 'Core_subtask_without_required_startup').
reDuration> AD DEX reference: Notes
− DEX3AD section Task 1. Roll-up can also consider Subtask_timeline (DEX

definition - Template reference: DEX3AD section Subtask by reference - Template
table #12 if task tables #26 and #27).
duration, 2. Roll-up must also consider Task_duration for
or Subtask_by_reference.
− DEX3AD section 3. Defined in 1388-2b using Elapsed Time
subtask duration Refer to Note 1 at Para 3.3.
<productionMaintData> the Requirements after Task_duration 'Closeup_subtask'.
job completion.
<taskDuration@closeup Notes
Duration> AD DEX reference: 1. Roll-up can also consider Subtask_timeline (DEX reference:
− DEX3AD section Task DEX3AD section Subtask by reference - Template tables #26 and
definition - Template #27).
table #12 if task 2. Roll-up must also consider Task_duration for
duration, Subtask_by_reference.
or
3. Defined in 1388-2b using Elapsed Time
− DEX3AD section
Template table #46 if Refer to Note 1 at Para 3.3.
subtask duration

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Required conditions are Subtask Defined by Subtasks where subtask_role is classified as
<reqCondGroup> actions to be done and/or 'Startup_subtask' (DEX reference: DEX3AD section Subtask by
conditions that must be reference - Template table #25, DEX3AD section Subtask by external
satisfied before you do AD DEX reference: reference - Template table #31, and DEX3AD section Subtask by definition
the procedure which is the − DEX3AD section - Template table #41).
subject of the data Subtask by reference -
module. Template table #25 if
Subtask by reference
or
− DEX3AD section
Subtask by external
reference - Template
table #30 if Subtask by
external reference
or
− DEX3AD section
Subtask by definition

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Used to indicate that Subtask_role For tasks in S3000L that has no 'Startup' subtasks, this is indicated by
<reqCondGroup> there are no required setting the value of Subtask_role for the first subtask to
actions/ conditions for the 'Core_subtask_without_required_startup'.
<noConds> AD DEX reference:
procedure.
− DEX3AD section
Subtask by reference -
subtask by reference
or
− DEX3AD section
Subtask by external
erefence - Template
table #31 if Subtask by
external reference
or
− DEX3AD section
Subtask by definition

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Simple action/ condition (Task_name &) The element <reqCondNoRef><reqCond> can be populated with a
<reqCondGroup> with no referenced data Subtask_name and concatenated string value made up from:
module or technical
<reqCondNoRef
publication (Simple text).
Subtask_objective − Task_name if the ‘Startup_subtask’ is an instance of
<reqCond> _state Subtask by reference (DEX reference: DEX3AD section Subtask
by reference - Template table #25)
AD DEX reference: − Subtask_name
− DEX3AD section Task − Subtask_objective_state
table #1 for Task_name Repeat for possible Subtask_by_reference within the referenced
task.
and
Notes
− DEX3AD section
Subtask by definition - 1. There must be one instance of the element
Template table #42 for <reqCondNoRef><reqCond> per
Subtask_name Subtask_by_definition being classified as
and 'Startup_subtask' (Subtask_role) and that has an
− DEX3AD section associated instance of 'Subtask_objective_state'.
Subtask by definition 2. Subtask_by_definition where the associated instance
Template table #49 for of 'Subtask_objective_state' is an instance of
Subtask_objective_stat
e
'Subtask_circuit_breaker_state' is defined as
separate required conditions within the element <reqCondGroup>
<reqCircuitBreakerList> and must not be instantiated
within this element.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Category of the condition, N/A for issue 4.0

<reqCondGroup> eg special environmental
conditions such as
<reqCondNoRef
reduced lighting,
<reqCond@reqCondCateg ventilation, and
ory> temperature.
<preliminaryRqmts> Simple statement for a N/A There is no notion of data modules when S3000L data is transferred to
<reqCondGroup> condition with a link to a S1000D.
data module that tells you
<reqCondDm>
how to satisfy that
condition.
<preliminaryRqmts> The publication module Publication_modul Publication_module_code for the

<reqCondGroup> code. e_code S1000D_publication_module being associated with
<reqCondPm> Subtask_by_external_reference, where Subtask_role
<pmRef> AD DEX reference: is defined as 'Startup_subtask' (DEX reference: DEX3AD section
<pmRefIdent> Subtask by external reference - Template table #31)
− DEX3AD section
<pmCode>
Subtask by external
table #34

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Issue information needed Publication_modul Publication_module_issue_number for the

<reqCondGroup> to address a particular e_issue_number S1000D_publication_module being associated with
destination data module
<reqCondPm> Subtask_by_external_reference.
issue.
<pmRef> AD DEX reference: Also refer to the mapping defined for element
<pmRefIdent> <reqCondGroup><reqCondPm><pmRef>
− DEX3AD section
<issueInfo@issueNumbe <pmRefIdent><pmCode> above.
Subtask by external
r> reference - Template
table #34
<preliminaryRqmts> Contains the required Publication_modul Publication_module_title for the

<reqCondGroup> action/condition e_title S1000D_publication_module being associated with
statement.
<reqCondPm> Subtask_by_external_reference.
<reqCond> AD DEX reference: Also refer to the mapping defined for
<reqCondGroup><reqCondPm><pmRef>
− DEX3AD section
Document- Template <pmRefIdent><pmCode> above.
table #345
<preliminaryRqmts> Contains, as text content, Document_identifi Document_identifier for the External_document being
<reqCondGroup> a code that identifies a er associated with Subtask_by_external_reference, where
non S1000D document,
<reqCondExternalPub> Subtask_role is defined as 'Startup_subtask' (DEX
such as an ISBN code or
<externalPubRef> reference: DEX3AD section Subtask by external reference - Template table
similar. AD DEX reference:
<externalPubRefIdent> #31).
<externalPubCode>
Subtask by external
reference - Template The required conditions would be described in other technical
table #32 documentation (which may or may not be in the LSAR).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Contains, as text content, Document_title Document_title for the External_document being associated
<reqCondGroup> a code that identifies a with Subtask_by_external_reference, where the
AD DEX reference:
<reqCondExternalPub> Subtask_role is defined as 'Startup_subtask'.
such as an ISBN code or − DEX3AD section
<externalPubRef> similar. Document - Template Also refer to the mapping defined for element
<externalPubRefIdent> table #348 <reqCondGroup><reqCondExternalPub>
<externalPubTitle> <externalPubRef><externalPubRefIdent>
<externalPubCode> above.
<preliminaryRqmts> Issue nformation Document_issue_id Document_issue_identifier for the External_document

<reqCondGroup> concerning a referred non entifier being associated with Subtask_by_external_reference,
S1000D document.
<reqCondExternalPub> AD DEX reference: where the Subtask_role is defined as 'Startup_subtask'.
<externalPubRef>
− DEX3AD section Also refer to the mapping defined for element
<externalPubRefIdent> Subtask by external <reqCondGroup><reqCondExternalPub>
<externalPubIssueInfo> reference - Template <externalPubRef><externalPubRefIdent>
<externalPubIssue> table #32 <externalPubCode> above.
<preliminaryRqmts> Contains the required N/A

<reqCondGroup> action/condition
statement.
<reqCondExternalPub>
<reqCond>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> (Required condition of Subtask_name One instance of the element

<reqCondGroup> circuit breakers) <reqCondCircuitBreaker><reqCond> per
<reqCondCircuitBreaker The required conditions Subtask_by_definition where Subtask_role is classfied as
AD DEX reference:
> (simple text statement) 'Startup_subtask' and the Subtask_by_definition has
<reqCond> that a list of circuit − DEX3AD section at least one associated instance of
breakers must be in. The Subtask by definition - Subtask_circuit_breaker_state (DEX reference: DEX3AD
schema gives the Template table #32
section Subtask by definition - Template tables #41 and #50, respectively).
capability to link from an
individual data module to The element <reqCond> can be populated with the Subtask_name.
further circuit breaker
information, held in the
CB Tech repository data
module.
<preliminaryRqmts> The category of the N/A

<reqCondGroup> condition, eg special
environmental conditions
<reqCondCircuitBreaker
such as reduced lighting,
> ventilation, and
<reqCond@reqCondCateg temperature.
ory>
<preliminaryRqmts> Contains the circuit N/A Note
<reqCondGroup> breaker lists information. S3000L defines the circuit breaker state per identified Circuit breaker.
>
<circuitBreakerDescrGr
oup>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The action to perform on N/A Note

<reqCondGroup> the whole set of circuit S3000L defines the circuit breaker state per identified Circuit breaker.
breaker described in the
table.
>
oup>
<circuitBreakerDescrSu
bGroup@circuitBreaker
Action>
<preliminaryRqmts> Indicates the particular N/A
<reqCondGroup> context for this set of
circuit breakers.
>
oup>
bGroup>
<functionItemRef>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The circuit breaker Circuit_breaker_i Circuit_breaker_identifier for the Circuit_breaker

<reqCondGroup> number. dentifier being associated with the Subtask_circuit_breaker_state
<reqCondCircuitBreaker (DEX reference: DEX3AD section Subtask by definition - Template table
> #50).
AD DEX reference:
oup> − DEX3AD section
Template table #51
bGroup>
<circuitBreakerDescr>
<circuitBreakerRef@ci
rcuitBreakerNumber>
<preliminaryRqmts> The circuit breaker type. Circuit_breaker_t Circuit_breaker_type for the Circuit_breaker being
<reqCondGroup> ype associated with the Subtask_circuit_breaker_state.
<reqCondCircuitBreaker Circuit_breaker_type is defined using reference data that
> corresponds to the S1000D
AD DEX reference:
<circuitBreakerDescrGr <circuitBreakerRef@circuitBreakerType> allowed
Subtask by definition - values:
Template table #52 − ‘Electronic_circuit_breaker_element’ (equals
bGroup> @circuitBreakerType 'eltro')
<circuitBreakerRef@ci − ‘Electro_mechanic_circuit_breaker_element’
rcuitBreakerType> (equals @circuitBreakerType 'elmec')
− ‘Dummy_circuit_breaker’ (equals
@circuitBreakerType 'clip')

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Action to perform on the Subtask_objective Subtask_circuit_breaker_state identifies the specific circuit
<reqCondGroup> circuit breaker. _state breakers by its id and its required state
<reqCondCircuitBreaker (Subtask_objective_state inherited from class
> Subtask_objective_state).
AD DEX reference:
<circuitBreakerDescrGr Circuit breaker state is defined using reference data that corresponds to the
S1000D <circuitBreakerRef@circuitBreakerAction>
<circuitBreakerDescrSu allowed values:
Template table #50
bGroup> − ‘Circuit_breaker_open’ (equals
<circuitBreakerDescr> @circuitBreakerAction ‘Open’ and ‘Verify_open’)
<circuitBreakerRef@ci
− ‘Circuit_breaker_closed’ (equals
rcuitBreakerAction>
@circuitBreakerAction ‘Closed’ and ‘Verify_closed’)
<preliminaryRqmts> The name of the circuit Circuit_breaker_n Circuit_breaker_name for the Circuit_breaker being
<reqCondGroup> breaker. ame associated with the Subtask_circuit_breaker_state.
>
AD DEX reference:
Template table #53
bGroup>
<name>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Describes/identifies any N/A Not defined for circuit breakers in S3000L.
<reqCondGroup> (one or more) access
points like panels, doors,
hatches.
>
oup>
bGroup>
<accessPointRef>
<preliminaryRqmts> Circuit breaker location in N/A

<reqCondGroup> the circuit breaker panel
by entering text.
>
oup>
bGroup>
<circuitBreakerLocatio
n>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Each person required to Task_personnel_re Summary of Task_personnel_resource for all Subtasks
<reqPersons> do the Procedure can be source where Subtask_role is defined as 'Core_subtask' (including
listed together with the its specialization
appropriate information as
‘Core_subtask_without_required_startup’).
defined by the project:
category, skill level, Note
trade/trade code and The absence of a specified quantity in Issue 4 indicates "As required",
estimated time spent per which is more in line with S3000L.
person.
<preliminaryRqmts> Contains the information Task_personnel_re Task_personnel_resource where

<reqPersons> on the required personnel source Task_personnel_resource_role doesn't begin with 'Man_'
for the task by grouping (DEX reference: DEX3AD section Task personnel resource - Template
<personnel>
the personnel by tables #110).
category, skill level and AD DEX reference:
trade/trade code together
with the number of
personnel resource -
personnel of a certain skill
Template table #110
(category, skill level,
trade).
<preliminaryRqmts> The number of personnel Task_number_of_pe Task_personnel_resource attribute

<reqPersons> for a certain combination rsonnel_resource Task_number_of_personnel_resource.
of category, skill level and
<personnel@numRequire
trade.
d> AD DEX reference:
Template table #115

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The typed in category Trade_name Trade_name for the Trade being associated with
<reqPersons> level of the person. Task_personnel_resource.
<personnel> AD DEX reference: Trade can be associated with a Task_personnel_resource
<personCategory@perso either directly as the selected Competence, or via Skill as the
nCategoryCode> personnel resource - Competence.
Template table #119
<preliminaryRqmts> The skill level of the Skill_level_name The Skill_level_name for the Skill_level being associated
<reqPersons> person. with Task_personnel_resource.
<personnel> (Not included in the current
personSkill@skillLeve version of AD DEXs)
lCode>
<preliminaryRqmts> Required trade code of Skill_code The Skill_code for the Skill being associated with
<reqPersons> the person. Task_personnel_resource.
<personnel> AD DEX reference:
<trade>
Template table #120

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Estimate of the time that Task_personnel_re Task_personnel_resource attribute

<reqPersons> the person will be source_labour_tim Task_personnel_resource_labour_time.
required on the task. The e
<personnel> Note
time must be given in
<estimatedTime> hours with one decimal, The attribute <estimatedTime@unitOfMeasure> is
eg 2,4 h, or days, eg 1,5 AD DEX reference: populated with the Unit given in the
d.
− DEX3AD section Task Task_personnel_resource_labour_time
personnel resource - Property_representation.
Template table #117
<preliminaryRqmts> Unit of measure for Task_personnel_re For mapping information refer to the element
<reqPersons> estimatedTime. source_labour_tim <preliminaryRqmts><reqPersons>
<personnel> e <personnel><estimatedTime> above.
<estimatedTime@unitOf
Measure> AD DEX reference:
Template table #117
<preliminaryRqmts> The skill information on Task_personnel_re Task_personnel_resource where the value of

<reqPersons> the required personnel for source Task_personnel_resource_role begins with 'Man_'.
the task when there are
<person>
requirements to
individually specify the AD DEX reference:
personnel.
Template table #110

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Alphabetic identifier of the Task_personnel_re Task_personnel_resource attribute

<reqPersons> person, starting from A. source_role Task_personnel_resource_role
<person@man> Extract the last letter from the reference data class used to determine the
AD DEX reference: Task_personnel_resource_role, eg ‘A’ from ‘Man_A’
Template table #110
<preliminaryRqmts> Category level of the Trade_name The Trade_name for the Trade being associated with
<reqPersons> person. Project has to list Task_personnel_resource.
AD DEX reference:
their codes, eg
<person>
Electrician, Propulsion − DEX3AD section Task Trade can be associated with a Task_personnel_resource
<personCategory@perso engineer, Maintainer. personnel resource - either directly as the selected Competence, or via Skill as the
nCategoryCode Template table #119 Competence.
<preliminaryRqmts> Represents the skill level Skill_level_name The Skill_level_name for the Skill_level being associated
<reqPersons> that the person must have with Task_personnel_resource.
attained to be able to
<person> (Not included in the current
perform his or her role in
<personSkill@skillLev the Procedure and is, eg version of AD DEXs)
elCode> Basic, Intermediate or
Advanced.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Trade or trade code of the Skill_code The Skill_code for the Skill being associated with
<reqPersons> person. Task_personnel_resource.
<person> AD DEX reference:
<trade>
Template table #120
<preliminaryRqmts> Estimate of the time that Task_personnel_re Task_personnel_resource_labour_time per required

<reqPersons> the person will be source_labour_tim personnel resource.
required on the task. e
<person> Note
<estimatedTime> The attribute <estimatedTime@unitOfMeasure> is
AD DEX reference: populated with the Unit given in the
− DEX3AD section Task Task_personnel_resource_labour_time
personnel resource - Property_representation.
Template table #117
<preliminaryRqmts> Unit of measure. Task_personnel_re For mapping information refer to the element
<reqPersons> source_labour_tim <preliminaryRqmts><reqPersons><person><estimated
<person> e Time> above.
<estimatedTime@unitOf
Measure> AD DEX reference:
Template table #117

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Support equipment Task_material_res Summary of Task_material_resource's for all Subtasks

<reqSupportEquips> including special tools, ource where Subtask_role is defined as 'Core_subtask' (including
required to accomplish its specialization
the Procedure. AD DEX reference:
‘Core_subtask_without_required_startup’) and
material resource by
Task_material_resource_category is set to
specification - Template ’Required_support_equipment_resource’.
table #60,
or
table #80
<preliminaryRqmts> Used to indicate that The absence of Task_material_resource with

<reqSupportEquips> there is no support Task_material_resource_category set
equipment.
<noSupportEquips> ’Required_support_equipment_resource’.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The name (nomenclature) Resource_specific Resource_specification_name if the

<reqSupportEquips> of the support equipment. ation_name or Task_material_resource is an instance of
<supportEquipDescrGrou Part_name Task_material_resource_by_specification (DEX
p> reference: DEX3AD section Task material resource by specification -
<supportEquipDescr> Template tables #67).
AD DEX reference:
<name> Part_name if the Task_material_resource is an instance of
Task_material_resource_by_reference (DEX reference:
specification - Template DEX3AD section Task material resource by reference - Template tables
table #68 if resource by #86)
specification Business rule decision point - Multiple names for hardware parts:
or If hardware parts have multiple names, decide which name to use to
− DEX1AD section populate the element <supportEquipDescr><name>.
Hardware part -
resource by reference
<preliminaryRqmts> Provide the link to the N/A Sourced from S2000M.

<reqSupportEquips> associated parts data Can not be provided by S3000L.
module.
<supportEquipDescrGrou
p>
<supportEquipDescr>
<catalogSeqNumberRef@
catalogSeqNumberValue>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The NATO Stock Number Resource_specific Resource_specification_identifier classified as

<reqSupportEquips> (NSN) of the support ation_identifier ’NSN_code’.
equipment.
<supportEquipDescrGrou AD DEX reference:
p> − DEX3AD section Task
<supportEquipDescr> material resource by
<natoStockNumber> specification - Template
<fullNatoStockNumber> table #67
<preliminaryRqmts> The manufacturer's Part_identifier@I Identified via either :

<reqSupportEquips> identification information. dentifier_set_by_ − Task_material_resource_by_reference (DEX
<supportEquipDescrGrou organization reference: DEX3AD section Task material resource by reference -
p> Template table #86)
<supportEquipDescr> AD DEX reference: − Task_material_resource_by_specification and
<identnumber> Resource_specification (DEX reference: DEX3AD section
<manufacturerCode> Task material resource by specification - Template table #67).
specification - Template Business rule decision point - Multiple identifiers for hardware parts:
table #70
If hardware parts have multiple identifiers, decide which identifier to use to
or populate the element <supportEquipDescr><identNo>.
− DEX1AD section
Hardware part -
#53.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Part number. Part_identifier@I For mapping information refer to the element
<reqSupportEquips> dentifier <preliminaryRqmts><reqSupportEquips><…>
<supportEquipDescrGrou <identnumber><manufacturerCode> above.
p> AD DEX reference:
<supportEquipDescr>
<identnumber>
<partAndSerialNumber> specification - Template
<partNumber> table #70
or
− DEX1AD section
Hardware part -
#53.
<preliminaryRqmts> Reference a tool for N/A (Reference to the CIR data module for the list of tool associated with the
<reqSupportEquips> projects which manage a procedure).
CIR.
<supportEquipDescrGrou
p>
<supportEquipDescr>
<toolRef@toolNumber>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> The quantity of support Task_material_res The element <reqQuantity> can be populated in two ways depending
<reqSupportEquips> equipment items. ource_quantity on how Task_material_resource_quantity is defined in the
<supportEquipDescrGrou data exchange:
p> AD DEX reference − If the Task_material_resource is assigned to the overall
<supportEquipDescr> Task in S3000L, then must that quantity be used (DEX reference:
<reqQuantity> DEX3AD section Task material resource by specification - Template
specification - Template table #60, or DEX3AD section Task material resource by reference -
table #66, Template table #80).
or − By rolling-up if the Task_material_resource is assigned to
− DEX3AD section Task individual subtasks (including subtasks by reference) (DEX reference:
material resource by DEX3AD section Task material resource by specification - Template
reference - Template table #60, or DEX3AD section Task material resource by reference -
table #85 Template table #80). This approch can also require the usage of
Subtask_timeline (DEX reference: DEX3AD section Subtask by
reference - Template table #26).
Note
The attribute <reqQuantity@unitOfMeasure> must be
populated with the Unit given in the
Task_material_resource_quantity property
representation.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Unit of measure for Task_material_res Refer to the mapping for the element
<reqSupportEquips> reqQuantity. ource_quantity <preliminaryRqmts><reqSupportEquips>
<supportEquipDescrGrou <supportEquipDescrGroup>
p> <supportEquipDescr><reqQuantity> above.
AD DEX reference:
<supportEquipDescr>
<reqQuantity@unitOfMe
asure> specification - Template
table #66,
or
table #85

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> A list of any consumables Task_material_res Summary of Task_material_resource's for all subtasks where
<reqSupplies> (such as oils, greases, ource Subtask_role is defined as 'Core_subtask' (including its
locking wire), materials specialization
(gasket sheet, sheet
metal) and expendables
(such as O-rings, gaskets, Task_material_resource_category is set to
tab washers) required to 'Required_consumable_resource'.
accomplish the For detailed mapping of the elements defined within the element
Procedure. <reqSupplies>, refer to the elements
<preliminaryRqmts><reqSupportEquips> above.
Note
The element <reqSupplies> does not contain any occurrences of
the element <toolref>.
<preliminaryRqmts> A list of any spares Task_material_res Summary of Task_material_resource's for all subtasks where
<reqSpares> required to accomplish ource Subtask_role is defined as 'Core_subtask' (including its
the Procedure. specialization
Task_material_resource_category is set
to'Required_spare_part_resource'.
For detailed mapping of the elements defined within the element
<reqSpares>, refer to the elements
<preliminaryRqmts><reqSupportEquips> above.
Note
The element <reqSpares> does not contain any element <toolref>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> If there are no safety Derived from the absence of Warning_caution_or_note

<reqSafety> requirements, then the associated with either the overall Task (revision), or any of its
element <noSafety> must
<noSafety> 'Startup_subtask' subtasks.
be used.
(DEX reference: DEX3AD section Task definition - Template table #22, or
DEX3AD section Subtask by definition - Template table #22)
<preliminaryRqmts> Any warnings applicable Warning_caution_o Warning_caution_or_note (where

<reqSafety> to the Procedure and the r_note Warning_caution_or_note_type =
Requirements after job
<safetyRqmts> 'Advisory_warning') associated with the Task itself or with any
completion in the data
<warning> module must be listed AD DEX reference: of its 'Startup' subtasks (Subtask_role =
<warningAndCautionPara here. ‘Startup_subtask’).
> Note
table #22 Safety conditions that must be in place BEFORE the procedure is
or carried out - not the same as Warnings and Cautions in the body of
the procedure.
− DEX3AD section
Template table #22

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<preliminaryRqmts> Any cautions applicable to Warning_caution_o Warning_caution_or_note (where

<reqSafety> the Procedure and the r_note Warning_caution_or_note_type =
<safetyRqmts> 'Advisory_caution') associated with the Task itself or with any
<caution> module must be listed AD DEX reference: of its 'Startup' subtasks (Subtask_role =
<warningAndCautionPara here. ‘Startup_subtask’).
> Note
table #22 Safety conditions that must be in place BEFORE the procedure is
or carried out - not the same as Warnings and Cautions in the body of
the procedure.
− DEX3AD section
Template table #22
<preliminaryRqmts> Any notes applicable to Warning_caution_o Warning_caution_or_note (where

<reqSafety> the Procedure and the r_note Warning_caution_or_note_type = 'Advisory_note')
<safetyRqmts> associated with the Task itself or with any of its 'Startup' subtasks
<note> module must be listed AD DEX reference: (Subtask_role = ‘Startup_subtask’).
<notePara> here.
table #22
or
− DEX3AD section
Template table #22

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
3.3 Notes for Table 3

These notes are provided to give clarification to many of the entries in Table 3.
Note 1
S3000L has the capability to capture supporting documentation that indicates that a
task/subtask or group of tasks/subtasks can be carried out in parallel. S1000D does not
support this.
Note 2
The same rules apply to the element <closeRqmts><reqCondGroup>.
Note 3
The same rules apply to spares (the element <reqSpares>) and supplies (the element
<reqSupplies>).
Note 4
Roll up of resources from S3000L subtasks to the S1000D element <reqCondGroup>
needs to be adressed.
3.4 Main procedure

Table 4 describes the elements and attributes in the S1000D <mainProcedure>
section. The element <mainProcedure> is referred to as main function (the element
<mainFunc>) in S1000D Issue 3.0 (and earlier).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 4 mainProcedure - Elements and attributes

Element/Attribute name Element/ Attribute DEX reference
definition
<mainProcedure@itemCh Characteristics of the item N/A

aracteristic> that is the subject of a
given procedural step.
<mainProcedure@indepe The whole procedure Task_personnel_re The attribute <mainProcedure@independentCheck> is set to ‘Yes’, if there
ndentCheck> must be supervised with a source_role is a Task_personnel_resource classified as
given qualification 'Required_work_supervisor' in every 'Core' subtask
(Subtask_role = ‘Core_subtask’, including its specialization
AD DEX reference:
‘Core_subtask_without_required_startup’)
Template table #110
<mainProcedure@skillL Lowest skill required for Skill_level_name The Skill_level_name for the Skill_level being associated
evelCode> the whole procedure with Task_personnel_resource where
(Not included in the current Task_personnel_resource_role is defined as
version of AD DEXs) ‘Required_work_performer’ or subclass thereof (DEX
reference: DEX3AD section Task personnel resource - Template table
#110).
Identifies the lowest skill required that can perform the whole task (in
practice the highest defined within the task).
Rules related to the skill codes needs to be defined for the project.
Business rule decision point - Definitions for skill codes:
Decide on the definitions of the values for the attribute
<mainProcedure@skillCode>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure@ Security and restrictive Security_class This could be derived from either the security classification of
<securityClassificatio marking. Breakdown_element, Part, Task_requirement, Task or
n> Subtask in S3000L.
AD DEX reference:
Security classification for a breakdown element/ part/software shall be
− DEX1AD section propagated to the respective task being associated with the breakdown
element/ part.
Template table #320 for
Breakdown_element
and Part, respectively
or
− DEX3AD section
Task,
Subtask_by_definition
and Task_requirement,
respectively

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> Contains a step in the Subtask Create one step per S3000L 'Core' subtask (Subtask_role =
<proceduralStep> procedure. ‘Core_subtask’, including its specialization
AD DEX reference:
‘Core_subtask_without_required_startup’, DEX
− DEX3AD section
Subtask by reference - reference: DEX3AD section Subtask by reference - Template table #25, or
Template table # DEX3AD section Subtask by external reference - Template table #31, or
DEX3AD section Subtask by definition - Template table #41).
or
− DEX3AD section
Subtask by external
table #30
or
− DEX3AD section
Template table #40

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> The whole step or Subtask_objective Checks can be defined as a separate Subtasks in S3000L, with
<proceduralStep@indep individual steps/substeps _state or Subtask_objective_state set to’Checked_activity’
must be checked by eg a Task_personell_re and/or have a Task_personell_resource with role defined as
endentCheck>
supervisor with a given
source_role ’Required_work_quality_assurance_resource’,
qualification.
Note
AD DEX reference: This includes all nested Subtask_by_reference.
− DEX3AD section
Subtask_objective_stat
e
or
Task_personell_resour
ce_role
<mainProcedure> Skill level required for the Skill_level_name The Skill_level_name for the Skill_level being associated
<proceduralStep@skill whole procedure and/or with Task_personnel_resource.
for individual steps/sub-
LevelCode> (Not included in the current Identifies the lowest skill required that can perform the whole subtask (in
steps using the attribute
skill. version of AD DEXs) practice the highest skill defined within the task). Rules related to the skill
levels needs to be defined for the project.
Note
This includes all nested Subtask_by_reference.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> Security and restrictive Security_class Security classification relevant for the subtask.
<proceduralStep@secur marking. This could be derived from either the security classification of
ityClassification> AD DEX reference:
Breakdown_element, Part, Task_requirement, Task or
Subtask in S3000L.
− DEX1AD section
Security classification - Security classification for a breakdown element/ part/software shall be
Template table #320 for propagated to the respective task being associated with the breakdown
Breakdown_element element/ part.
and Part, respectively
or
− DEX3AD section
Task,
Subtask_by_definition
and Task_requirement,
respectively

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> Title of the step or a Subtask_name/Task The Subtask_name if the Subtask is an instance of
<proceduralStep> sequence of substeps. _name Subtask_by_definition (DEX reference: DEX3AD section
<title> Subtask by definition - Template table #40).
AD DEX reference: The Task_name for the referenced Task if the Subtask is an
instance of Subtask_by_reference (DEX reference: DEX3AD
− DEX3AD section
Subtask by definition - section Subtask by reference - Template table #25).
Subtask_name
or
table #4 for Task_name
<mainProcedure> Any warnings applicable Warning_caution_o Warning_caution_or_note associated with the Subtask where
<proceduralStep> to the Procedural step. r_note Warning_caution_or_note_type =
<warning> 'Advisory_warning'.
<warningAndCautionPara AD DEX reference: Note
>
− DEX3AD section A warning that is placed in an element at level 1 applies to all the
Subtask by definition - element at the next level.
Template table #22

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> Any cautions applicable to Warning_caution_o Warning_caution_or_note associated with the Subtask where
<proceduralStep the Procedural step. r_note Warning_caution_or_note_type =
<caution> 'Advisory_caution'.
<warningAndCautionPara AD DEX reference: Note
>
− DEX3AD section A caution that is placed in an element at level 1 applies to all the
Subtask by definition - element at the next level.
Template table #22
<mainProcedure> Any notes applicable to Warning_caution_o Warning_caution_or_note associated with the Subtask where
<proceduralStep the Procedural step. r_note Warning_caution_or_note_type = 'Advisory_note'.
<note>
<notePara> AD DEX reference:
− DEX3AD section
Template table #22
<mainProcedure> Steps can also contain a Subtask and Subtasks which has an associated instance of
<proceduralStep> circuit breaker list. Subtask_circuit_b Subtask_circuit_breaker_state.
<circuitBreakerDescrGr reaker_state Subtask_circuit_breaker_state identifies the specific circuit
oup> breakers by its id and its required state.
Refer to the mapping details under the element
AD DEX reference: Refer
to the element <preliminaryRqmts><reqCondGroup><reqCondCircuit
<preliminaryRqmts><reqCo Breaker><circuitBreakerDescrGroup> above.
ndGroup><reqCondCircuit
Breaker><circuitBreakerDe
scrGroup>, and its
subelements, above

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<mainProcedure> Would capture the Subtask_descripti Subtask_description

<proceduralStep narrative of the subtask. on
Any indenturing to
<para>
substeps is a function of
the author. AD DEX reference:
− DEX3AD section
Template table #40

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
4 S1000D Maintenance Planning Information

4.1 Introduction
The schedul Schema contains maintenance planning information. The granularity of data
modules created using the schedul Schema, is determined by the application of the SNS.
This Schema has structural elements that provide for four types of maintenance planning
information. These are time limits information (the element <timeLimitInfo>), task lists
(the element <taskDefiniton>), inspection lists (the element
<inspectionDefinition>) and maintenance allocation (the element
<maintAllocation>).
4.2 S1000D schedule Schema requirements

4.2.1 Task definition
Table 5 describes the elements and attributes of the S1000D element
<taskDefinition>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 5 taskDefinition - Elements and attributes

definition
<taskDefiniton> Task information related Task Applies to Tasks being instances of Rectifying_task, for which the
to a system. value of S1000D_task_type_code is set to
AD DEX reference:
'Procedure_task' (DEX reference: DEX3AD section Task definition
- Template tables #2 and #5).
definition - Template Notes
table #1 1. The S1000D_task_type attribute defines how a task in
S3000L corresponds with the schemas defined in S1000D:
− 'Procedure_task' = S1000D proced scheme,
− 'Package_task' = S1000D schedul scheme.
2. Refer to Chap 3 - S1000D Procedure and Schedule schemas vs
S3000L for more details on the relationship between S3000L and
S1000D.
<taskDefiniton@taskId Identifier for the list of Task_identifier Task_identifier

ent> tasks.
Business rule decision point - Multiple identifiers for tasks:
AD DEX reference: If tasks have multiple idenitifiers, decide which identifier to use to populate
− DEX3AD section Task the attribute < taskDefiniton@taskIdent>.
table #3

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition@taskC Type of work to be done Information_code Tasks attribute Information_code.

ode> (eg GVI, DET, VSK).
Business rule decision point – map between task codes and
AD DEX reference: information codes:
− DEX3AD section Task Decide on the map between valid values for the attribute
definition - Template <taskDefinition@taskCode> and the Information Code.
table #6
<taskDefinition@worth Indicate whether the tasks N/A Should come from S4000M.
inessLimit> are mandatory or Can not be provided by S3000L.
recommended.
<taskDefinition@reduc Indicate any reduced N/A S3000L does not identify the minimum tasks.
edMaint> maintenance information.
<taskDefinition@skill Skill level required for the Skill_level_name Skill_level derived from Skill_code.
LevelCode> task. (Is defined by the
Business rule decision point - Definitions for skill codes:
project).
(Not included in the current Decide on the definitions of the values for the attribute
version of AD DEXs) <taskDefinition@skillCode>.
<taskDefinition@skill Main technical ability Trade_name Either Trade_name derived via Skill_code, or Trade_name as
Type> required of the person the Competence related directly to the Task_personnel_resource
performing the task eg (DEX reference: DEX3AD section Task personnel resource - Template
Airframe, Electrical, AD DEX reference:
tables #110 and #118).
Avionic, Engine, etc. − DEX3AD section Task Business rule decision point – Main technical ability:
Template table #119 Decide on the definitions of the main technical abilities pertaining to the task
for the attribute <taskDefinition@skillCode>.
Also refer to the mapping for attribute
<taskDefinition@skillLevelCode> above.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition@appli Applicability for the whole Applicability_sta Note

cRefId> taskDefinition level. tement Mapping of Applicability is described at Table 2.
<taskDefinition@autho The authority that N/A

rityName> determined how these
attributes should be
populated (eg FAA-
Federal Aviation
Authority).
<taskDefinition@autho The document that N/A

rityDocument> records that
determination.
<taskDefinition Any general information Task Note

<task> about the task. From an S3000L perspective, there is just one task per taskDefinition.
This is the same instance of Task as is identified in element
AD DEX reference:
<taskDefinition> above.
table #1
<taskDefinition> Contains a short textual Task_name Task_name

<task> description of the task.
<taskTitle> AD DEX reference:
table #1

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Contains a fuller textual Task_name Task_name

<task> description of the task.
Note
<taskDescr> AD DEX reference: There is no more complete textual description for the task in S3000L
− DEX3AD section Task than the Task_name.
table #1
<taskDefinition> The origination of the Authority_driven_ If the Task is associated with an instance of
<rqmtSource> requirement. task_requirement Authority_driven_task_requirement, as the justification
for the Task.
AD DEX reference:
requirement- Template
table #211

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Code that indicates the Task_requirement_ Task_requirement_authority_source_type is defined

<rqmtSource@sourceOfR source of the requirement. authority_source_ using reference data that corresponds to the S1000D
Values of this code type <rqmtSource@sourceOfRqmt> allowed values:
qmt>
include MSG3, CMR and
AD. − ‘Authoritative_source_task_requirement’ (equals
AD DEX reference: <rqmtSource@sourceOfRqmt> value 'AD')
− DEX3AD section Task − ‘Scheduled_maintenance_program_task_requireme
requirement- Template nt’ (equals <rqmtSource@sourceOfRqmt> value 'MSG3')
table #211
− ‘Certification_maintenance_task_requirement’
(equals <rqmtSource@sourceOfRqmt> value 'CMR')

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition Document number of the Document_identifi Document_identifier or Document_name from a Document

<rqmtSource@sourceIde source of requirement or er or being assigned to Authority_driven_task_requirement in
the title of the source if no Document_title the role of 'Directive' (DEX reference: DEX3AD section Document -
nt>
number is available. Template table #346).
AD DEX reference:
− DEX3AD section
Document - Template
table #347 for
document identifier
or
− DEX3AD section
Document - Template
table #348 for
document title
<taskDefinition> Level of approval of the N/A

<rqmtSource@approval> source.
<taskDefinition> Issue number of the Document_issue_id For mapping information refer to the attribute
<rqmtSource> source document. entifier <taskDefinition><rqmtSource@sourceIdent> above.
<issueInfo@issueNumbe
r> AD DEX reference:
− DEX3AD section
Document - Template
table #346

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> The date of the source to Document_issue_da For mapping information refer to the attribute
<rqmtSource> distinguish it from te <taskDefinition><rqmtSource@sourceIdent> above.
previous sources with the
<issueDate@year /
same document number.
@month / @day> AD DEX reference:
− DEX3AD section
Document - Template
table #351
<taskDefinition> Failure effect category. N/A

<rqmtSource>
<sourceType@sourceCri
ticality>
<taskDefinition> Resources that are From an S3000L perspective, there no way to group tasks on this level, ie
<preliminaryRqmts> required before the task there is just one task per taskDefinition, which means that the content in the
can be performed. element <taskDefinition> <preliminaryRqmts> equals the
<preliminaryRqmts> defined for Procedural information above.
Refer to the mapping for Procedural information above.
<taskDefinition> Refers to data modules or For mapping information refer to <mainProcedure> above.
<refs> other publications that
represent the
accomplishment
instructions for the task.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Details of the destination N/A There is no notion of data modules when S3000L data is transferred to
<refs> data module that is S1000D.
referred from some other
<dmRef>
S1000D context, such as
a data module.
<taskDefinition> Contains, as text content, Document_identifi If there are one or more 'Core' subtasks within the Task which are
<refs> a code that identifies a er instances of Subtask_by_external_reference, which in turn
<externalPubRef> referes to an External_document, then create one instance of the
<externalPubRefIdent> similar. AD DEX reference: element <externalPubRef> for each External_document
<externalPubCode> being identified (DEX reference: DEX3AD section Subtask by external
− DEX3AD section reference - Template table #30 and Template table #31).
Subtask by external
table #32
<taskDefinition> Contains, as text content, Document_title Refer to the mapping defined for element
<refs> a code that identifies a <taskDefinition><refs><externalPubRef>
non S1000D document, <externalPubRefIdent><externalPubCode> above.
<externalPubRef> AD DEX reference:
<externalPubRefIdent> similar. − DEX3AD section
<externalPubTitle>
Document - Template
table #348

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Contains issue Document_issue_id Refer to the mapping defined for element
<refs> information concerning a entifier <taskDefinition><refs><externalPubRef>
referred non S1000D <externalPubRefIdent><externalPubCode> above.
<externalPubRef>
document.
<externalPubRefIdent> AD DEX reference:
<externalPubIssueInfo
− DEX3AD section
<externalPubIssue>
Subtask by external
table #32
<taskDefinition> Contains the items Publication_modul If there are one or more 'Core' subtasks within the Task which are
<refs> forming a unique e_code instances of Subtask_by_external_reference, which in turn
identification of the
<pmRef> referes to an S1000D_publication_module, then create one
destination data module.
<pmRefIdent> AD DEX reference: instance of the element <pmRef> for each
<pmCode> S1000D_publication_module being identified (DEX reference:
− DEX3AD section
DEX3AD section Subtask by external reference - Template table #30 and
Subtask by external
Template table #31).
table #34
<taskDefinition> Issue information needed Publication_modul Refer to the mapping defined for element
<refs> to address a particular e_issue_number <taskDefinition><refs><pmRef>
destination data module <pmRefIdent><pmCode> above.
<pmRef>
issue.
<pmRefIdent> AD DEX reference:
<issueInfo@issueNumbe
− DEX3AD section
r> Subtask by external
table #34

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Provides a grouping of Part Retrieved via Task_usage for the Task (DEX reference: DEX3AD
<equipGroup> information used to section Task assignment - Template table #140).
describe equipment that is
<equip> Part information can be derived from the Task_target_item being
the subject of, used in or
associated to the task. associated with the Task_usage, if the Task_target_item either is
a Part, or a Hardware_element.
If the Task_target_item is an instance of Hardware_element,
then the instance(s) of Part can be derived from the respective
Hardware_element_realization that is defined for the
Hardware_element (DEX reference: DEX1AD section Hardware
element realization - Template table #143).
<taskDefinition> Nomenclature for the Part_name Part_name

<equipGroup> equipment that belongs to
For mapping information refer to the element <taskDefinition>
the system for which the
<equip> AD DEX reference: <equipgroup><equip> above.
list of tasks is relevant.
<name>
− DEX1AD section Business rule decision point - Multiple names for hardware parts:
Hardware part If hardware parts have multiple names, decide which name to use to
reference - Template populate the element <equip><name>.
table #34

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> NATO Stock Number for Resource_specific Resource_specification_identifier classified as

<equipGroup> the equipment that ation_identifier 'NSN_code'.
belongs to the system for
<equip> The Resource_specification_identifier identifies an
which the list of tasks is
<natoStockNumber> relevant. AD DEX reference: Resource_specification which is defined for an NATO stock
<fullNatoStockNumber> item. The Resource_specification is associated with the
− DEX3AD section
Material resource by identified Part by a Resource_realization relationship (DEX
specification - Template reference: DEX3AD section Material resource by specification - Template
table #67 table #67)
For Part mapping information refer to the element <taskDefinition>
<equipgroup><equip> above.
Business rule decision point - Multiple NSNs for hardware parts:
If hardware parts have multiple NSNs, decide which NSN to use to populate
the element <natoStockNumber><fullNatoStockNumber>.
<taskDefinition> The manufacturer's Part_identifier@I For mapping information refer to the element
<equipGroup> identification information dentifier_set_by_ <taskDefinition><equipgroup><equip> above.
for the equipment that organization
<equip> Business rule decision point - Multiple identifiers for hardware parts:
belongs to the system for
<identNumber> which the list of tasks is If hardware parts have multiple identifiers, decide which identifier to use to
<manufacturerCode> relevant. AD DEX reference: populate the element <identNumber><manufacturerCode>.
− DEX1AD section
Hardware part -
Template table #53

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Contains the part number. Part_identifier@I For mapping information refer to the element <taskDefinition>
<equipGroup> dentifier <equipgroup><equip> above.
<equip> Business rule decision point - Multiple identifiers for hardware parts:
<identNumber> AD DEX reference: If hardware parts have multiple identifiers, decide which identifier to use to
<partAndSerialNumber> populate the element <partAndSerialNumber><partNumber>.
− DEX1AD section
<partNumber>
Hardware part -
Template table #53
<taskDefinition> Link to the associated N/A Should come from S2000M.

<equipGroup> parts data module for the Can not be provided by S3000L.
equipment that belongs to
<equip>
the system for which the
<catalogSeqNumberRef@ list of tasks is relevant.
<taskDefinition> Used instead of the Breakdown_element Breakdown_element_name
<name> element <equip> for _name Retrieved via Task_usage for the Task (DEX reference: DEX3AD
structural and other items
section Task assignment - Template table #140).
that do not have part
numbers. AD DEX reference:
− DEX1AD section
Hardware element
table #132

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Indicate the level of Skill_code or Identify level of supervision either by:
<supervisorLevel@supe supervision that is Trade_name − Look at the attribute
appropriate for the task.
rvisorLevelCode> <mainProcedure@independentCheck> and the attribute
AD DEX reference: <proceduralStep@independentCheck> values for the
included (procedural) task, and based on competence (ie trade or skill)
− DEX3AD section Task identify the "highest" level required.
Template table #120 if − Identify if there is any Task_personnel_resource with
skill code Task_personnel_resource_role =
or 'Required_work_supervisor', that is directly associated
with the Task being associated with the element
personnel resource - <taskDefinition> (DEX reference: DEX3AD section Task
Template table #119 if personnel resource - Template table #110).
trade name Business rule decision point – Identify the level of supervision:
Decide whether to source the required supervisor level from the attribute
<mainProcedure@independentCheck> or from the
Task_personnel_resource_role with a value of
'Required_work_supervisor'.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition Determine when a task Task_limit Use the Task_limit defined for the rectifying or operational task.
<limit> must be performed.
Note
AD DEX reference: A constraint in taskDefinition is that applicability can only be defined at
− DEX3AD section the taskDefinition level, and not on the limit level, whereas S3000L
Discrete task limit - permits applicability at both levels.
Template table #170
or
− DEX3AD section
Periodic task limit -
Template table #200
<taskDefinition> Valid limit type values: Discrete_task_lim Use one instance of the element
<limit@limitTypeValue − "PO" = Perform once it <limit@limitTypeValue='PO'> per:
> Periodic_task_lim − Instance of Discrete_task_limit, where the threshold for the
− "OC" = On condition
it Discrete_task_limit is an instance of
− "PE" = Perform Repeat_task_limit Parameter_threshold (DEX reference: DEX3AD section
periodically
Discrete task limit - Template tables #170, #181, #183 and #184)
AD DEX reference: − Instance of Periodic_task_limit that has an instantiation of
− DEX3AD section Initial_task_limit (DEX reference: DEX3AD section
Discrete task limit - Periodic task limit - Template table #203)
Template table #170 if One <limit@limitTypeValue='OC'> per:
Discrete_task_limit
− Instance of Discrete_task_limit, with no defined threshold,
or
but there is a Task_limit_description (DEX reference:
− DEX3AD section DEX3AD section Discrete task limit - Template tables #170 and #201)
Template table #200 if − Instance of Discrete_task_limit, where the threshold for the
Periodic_task_limit Discrete_task_limit is an instance of

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
(incl. Event_threshold (DEX reference: DEX3AD section Discrete
Repeat_task_limit) task limit - Template tables #170, #185, #188 and #190)
One <limit@limitTypeValue='PE'> per:
− Instance of Repeat_task_limit being referenced from an
instance of Periodic_task_limit. (also refer to the mapping
for the element <limit><limitRange> below) (DEX reference:
DEX3AD section Periodic task limit - Template table #204)
Note
If any of the thresholds defined for Discrete_task_limit,
Periodic_task_limit or Repeat_task_limit in
S3000L has more than one associated instance of
Threshold_definition, then these will be regarded as
"whichever comes first", and will result in one instance of the element
<limit> per associated instance of
Threshold_definition.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Indicates the condition Task_limit_descri Use Task_limit_description where the Task_limit is an
<limit@limitCond> type of the limit, ie ption, instance of Discrete_task_limit and there is no threshold for the
maritime flight, dirty LSA_failure_mode_ Discrete_task_limit (DEX reference: DEX3AD section Discrete
conditions
description or task limit - Template table #171).
Special_event_tit Use Failure_mode_description or Special_event_title
le where Task_limit is an instance of Discrete_task_limit,
and the threshold for the Discrete_task_limit is an instance of
AD DEX reference: LSA_failure_mode_related_threshold or
− DEX3AD section
Special_event_related_threshold, respectively. The text
Discrete task limit - populating the condition attribute can eg be a concatenated string using
Template table #187 if Event_threshold_number_of_event_occurrences and
LSA_failure_mode_des Special_event_title or
cription LSA_failure_mode_description, respectively (DEX reference:
or DEX3AD section Discrete task limit - Template table #185 and Template
table #188).
− DEX3AD section
Discrete task limit - Note
Template table #188 if If the attribute <limit@limitTypeValue> equals "OC", then
Special_event_title must the <limit@limitCond> describe the condition.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> If the task is based on Sampling_method_r Sampling_method_ratio (DEX reference: DEX3AD section
<limit> sampling information. atio Discrete task limit - Template table #173)
<sampling> Note
AD DEX reference: If a Sampling_method_ratio is given, it must be defined as a value
representing percentage.
− DEX3AD section
Discrete task limit - Example:
Template table #175 "20" in S1000D means "20%",
or
− DEX3AD section
Template table #175

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> If the task is based on any Parameter_thresho Parameter_threshold

<limit> threshold information ld
<threshold>
AD DEX reference:
− DEX3AD section
Discrete task <limit> -
Template table #181
or
− DEX3AD section
Template table #203
or
− DEX3AD section
Template table #204
<taskDefinition> Unit of measure for Threshold_value The unit given in the

<limit> threshold. Parameter_threshold/Threshold_value/Property_rep
<threshold@thresholdU resentation.
AD DEX reference:
nitOfMeasure>
− DEX3AD section
Discrete task limit -
Template table #184
or
− DEX3AD section
Template table #184

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Contains the value N/A

<limit> "threshold" or "interval",
and it specifies the
<threshold@thresholdT
starting point of the
ype> threshold. It can be "from
the beginning" of the
maintenance program or
from "the last time the
inspection was
performed."
<taskDefinition> Value Threshold_value The value given in the

<limit> Parameter_threshold/Threshold_value/Property_rep
<threshold> resentation.
AD DEX reference:
<thresholdValue>
− DEX3AD section
Template table #184
or
− DEX3AD section
Template table #184

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Tolerances related to yhr Threshold_value If the Property_representation for Threshold_value is

<limit> value of the limit of type Value_with_tolerances_property, then the optional
threshold.
<threshold> AD DEX reference: element <toleranceLow> will be populated with
<tolerance@toleranceL Lower_offset_value given in the Threshold_value, and the
− DEX3AD section
ow / toleranceHigh> Discrete task limit -
element <toleranceHigh> will be populated with Upper_offset_value
Template table #184 given in the Threshold_value (DEX reference: DEX3AD section
Data type Prp - Template table #607).
or
− DEX3AD section
Template table #184
<taskDefinition> Defines if the task Task_name Navigate from the Task under consideration and backwards through the
<limit> belongs to a particular Subtask_by_reference to any Task that is of type
inspection type.
<inspectionType@inspe AD DEX reference: 'Packaged_task'. ie
ctionTypeCategory> S1000D_task_type='Packaged_task',(DEX references: DEX3AD
section Subtask by reference - Template table #25 and DEX3AD section
Task definition - Template table #5) and populate the attribute
<inspectionType@inspectionTypeCategory> with
table #4
Task_name.
One occurrence of the element
<inspectionType@inspectionTypeCategory> per usage
of the Task under consideration in a Task of type 'Packaged_task'

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> If the task is based on Will be populated with 'after' when:

<limit> some trigger event. − Task_limit is an instance of Discrete_task_limit which
<trigger@releaseEvent has resulted in an instantiation of the element
> <limit@limitTypeValue= 'PO'>, and where the
Discrete_task_limit instance has at least one instantiation of
trigger (DEX reference: DEX3AD section Discrete task limit - Template
table #180 and Template table #190).
Note
The particular type of <inspectionDefinition> relates to a
grouping of maintenance tasks which gives the ability to express that
the task refers to an inspection threshold eg monthly inspection.
<taskDefinition> Indicate any tasks that Example: 10 flight hours after engine installation.
<limit> must be performed before
the inspection.
<trigger>
<refs>
<taskDefinition> Details of the destination N/A

<limit> data module that is
<trigger>
<refs> a data module.
<dmRef>
<taskDefinition> Details of the destination N/A

<limit> publication module that is
<trigger>
<refs> a data module, another
<pmRef> publication module, etc.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Identification of a Task Identify tasks in S3000L that triggers the performance of the S1000D task.
<limit> referenced non S10000D Refer to the element
publication or document. <taskDefinition><limit><trigger@releaseEvent>
<trigger>
<refs> above for more mapping details.
<externalPubRef> Note
The S3000L task can be regarded as an external document.
<taskDefinition> Contains, as text content, Task_identifier Task_identifier for the Task being associated with
<limit> a code that identifies a Task_related_threshold.
<trigger> AD DEX reference:
<refs> similar. − DEX3AD section
<externalPubRef>
<externalPubRefIdent> Template table #190
<externalPubCode>
<taskDefinition> Contains, as text content, Task_name Task_name for the Task being associated with
<limit> a code that identifies a Task_related_threshold.
<trigger> AD DEX reference:
<refs> similar. − DEX3AD section Task Note
<externalPubRef>
definition - Template The Task being referenced in DEX3AD section Discrete task limit
<externalPubRefIdent> table #1 or Template Template table #190, refers to a Task being defined in accordance
<externalPubTitle> table #4
with DEX3AD section Task definition Template table #1. However, the
refered task does not have to be included in the same data exchange.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Contains, as text content, N/A

<limit> issue designation of a non
S1000D document.
<trigger>
<refs>
<externalPubRef>
<externalPubRefIdent>
<externalPubIssueInfo>
<externalPubIssue>
<taskDefinition> References or threshold Threshold_value or Threshold_value or

<limit> information. Event_threshold_n Event_threshold_number_of_event_occurrences for
<trigger> umber_of_event_oc the instance of Threshold_definition being associated as a
<threshold> currences trigger.
<thresholdValue> It is populated if the condition described under the mapping for element
<taskDefinition><limit> <trigger@releaseEvent> is
AD DEX reference:
fulfilled.
− DEX3AD section
Discrete task limit - If any of the trigger defined for Discrete_task_limit has more
Template table #184 if than one associated instance of Threshold_definition, then
threshold value these will be regarded as "whichever comes first", and will result in one
or instance of the element <threshold> per associated instance of
− DEX3AD section
Threshold_definition.
Discrete task limit - Example:
Template table #182 if After two hard landings.
number of event
occurrences

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Unit of measure for the Threshold_value, Unit of measure defined for the Threshold_value, or the text string
<limit> threshold. LSA_failure_mode_ defined in the LSA_failure_mode_description,
<trigger> description, Special_event_title or Task_name.
<threshold@thresholdU Special_event_tit For mapping information refer to the element
nitOfMeasure> le or Task_name <taskDefinition><limit><trigger><threshold>
<thresholdValue> above.
AD DEX reference:
− DEX3AD section
Threshold_vale
or
− DEX3AD section
LSA_failure_mode
or
− DEX3AD section
Special_event
or
table #190 if Task

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Tolerances for the Threshold_value If the Property_representation for Threshold_value is

<limit> threshold value. of type Value_with_tolerances_property, then the optional
<trigger> AD DEX reference: element <toleranceLow> will be populated with
<threshold> Lower_offset_value given in the Threshold_value, and the
− DEX3AD section
<tolerance@toleranceL element <toleranceHigh> will be populated with
ow / toleranceHigh> Template table #184 if Upper_offset_value given in the Threshold_value (DEX
Parameter threshold reference: DEX3AD section Data type Prp - Template table #607).
Note
There is no representation of tolerances for Event_thresholds
in S3000L
<taskDefinition> Any limit range Repeat_task_limit If an instance of Periodic_task_limit has more than one
<limit> information. and associated instance of Repeat_task_limit (DEX reference:
<limitRange> Subsequent_repeat DEX3AD section Periodic task limit - Template table #200), then these
_relationship needs to be organized using the element <limit> and the elements
<limitRange>. One instance of the element <limit> per
AD DEX reference: Repeat_task_limit with an associated element <limitRange>,
derived from the Subsequent_repeat_relationship threshold
− DEX3AD section
values.
Template tables #200 The order in which the element <limit> is defined must be derived from
and #205 the S3000L Subsequent_repeat_relationships (DEX
reference: DEX3AD section Periodic task limit - Template table #205).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> The inspection must be Parameter_thresho Repeat_task_limit threshold or the

<limit> performed after this range ld Subsequent_repeat_relationship trigger (DEX reference:
has been reached. DEX3AD section Periodic task limit - Template table #203).
<limitRange>
<limitRangeFrom> AD DEX reference: The element <limitRangeFrom> for the first instance of
− DEX3AD section
Repeat_task_limit (as ordered by
Periodic task limit - Subsequent_repeat_relationship) is set to:
Template tables #203 − The threshold value for the first Repeat_task_limit (DEX
and #183 reference: DEX3AD section Periodic task limit - Template table #203).
The element <limitRangeFrom> for each subsequent
Repeat_task_limit is set to:
− The trigger value for the respective subsequent
Repeat_task_limit (DEX reference: DEX3AD section Periodic
task limit - Template table #203)
<taskDefinition> Unit of measure for the Threshold_value The unit defined in the Property_representation of the
<limit> limit range from threshold Threshold_value.
value.
<limitRange> AD DEX reference: For more mapping details refer to the element
<limitRangeFrom> <taskDefinition><limit><limitRange>
− DEX3AD section
<threshold@thresholdU <limitRangeFrom> above.
nitOfMeasure> Template table #184

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Value for the limit range Threshold_value The value defined in the Property_representation of the
<limit> from threshold. Threshold_value.
<limitRangeFrom> <taskDefinition><limit><limitRange>
− DEX3AD section
<threshold> <limitRangeFrom> above.
<thresholdValue> Template table #184
<taskDefinition> The inspection must be Parameter_thresho The element <limitRangeTo> is set to:
<limit> performed before this ld
range has been reached. − The trigger for the Subsequent_repeat_relationship
<limitRange> (DEX reference: DEX3AD section Periodic task limit - Template table
<limitRangeTo> AD DEX reference: #203), where the Repeat_task_limit under consideration is
referred to as the preceding Repeat_task_limit.
− DEX3AD section
Periodic task limit - Note
Template tables #203 The last instance of Repeat_task_limit, as ordered by the
and #183
Subsequent_repeat_relationship, will have no given
value, and will leave the element <limitRangeTo> empty.
<taskDefinition> Unit of measure for the Threshold_value The unit defined in the Property_representation of the
<limit> limit range to threshold Threshold_value.
value.
<limitRange> For more mapping details refer to the element
AD DEX reference:
<limitRangeTo> <taskDefinition><limit><limitRange>
− DEX3AD section
<threshold@thresholdU <limitRangeTo> above.
nitOfMeasure> Template table #184

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition> Value for limit range to Threshold_value The value defined in the Property_representation of the
<limit> threshold. Threshold_value.
<limitRangeTo> <taskDefinition><limit><limitRange>
− DEX3AD section
<threshold> <limitRangeTo> above.
<thresholdValue> Template table #184
<taskDefinition> Contains text giving Remark_text Remarks being associated with the Task_limit in S3000L
<limit> further information about
the inspection.
<remarks>
AD DEX reference:
<simplePara>
− DEX3AD section
Remark - Template
table #360
<taskDefinition> Contains text giving Remark_text Remarks being associated with the Task under consideration.
<remarks> further information about
the inspection.
<simplePara>
AD DEX reference:
− DEX3AD section
Remark - Template
table #360
<taskDefinition> Provides a relationship N/A

<relatedTask> between two tasks.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<taskDefinition@appli Applicability information Applicability_sta Applicability_statement associated with Task.

cRefId> associated with the tement Business rule decision point – Use of applicability:
taskDefinition.
Decide how applicability will be used when associated to instances of
− For AD DEX reference Task_limit in S3000L.
refer to the element Refer to generic discussion on applicability above (Table 2) above.
<dmStatus><reference
dApplicGroup> in Table
2 above

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
4.3 Inspection definition

Table 6 describes the elements and attributes in the S1000D element
<inspectionDefinition>.
The <inspectionDefinition> branch of the schedule Schema contains information

about inspections. Inspections are a way to group tasks that are related to the topic or intent of
the inspection, eg weekly inspections, greasing inspections, post flight inspections.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 6 inspectionDefinitions - Elements and attributes

definition
<inspectionDefinition> Information about Task Task where the S1000D_task_type is set to 'Packaged_task'.
inspections or groups of
tasks. 'Packaged_task' corresponds to scheduled maintenance packages
AD DEX reference: in S3000L.
− DEX3AD section Task S1000D_task_type attribute in S3000L also defines how the task
definition - Template corresponds with the schemas defined in S1000D:
table #1 − 'Procedure_task' = S1000D proced scheme
− 'Package_task' = S1000D schedul scheme
The Task_target_item for a 'Package_task' must be a
Breakdown_element (incl Zone_elements) that corresponds to a
System/Subsystem level in S1000D.
<inspectionDefinition> Inspection identification Task_identifier Task_identifier for the Task under consideration.
<inspection@id> Business rule decision point - Multiple identifiers for tasks:
AD DEX reference: If tasks have multiple identifiers, decide which identifier to use to populate
− DEX3AD section Task the attribute <inspection@id>.
table #3

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<inspectionDefinition> Provides a structure that Task_limit For mapping information refer to the element
<inspection> is designed to specify the <taskDefinition><limit> in Table 5 above.
interval between
<limit> AD DEX reference: Note
inspections, or the
threshold before which an − DEX3AD section Do not use the mapping for element
inspection must be Discrete task limit - <limit><inspectionType> as it is described in Table 5
performed. Template table #170 above.
or Business rule decision point - Use of applicability:
− DEX3AD section Decide how applicability will be used when associated to instances of
Periodic task limit - Task_limit in S3000L.
Template table #200
<inspectionDefinition> Any remarks that are Remark_text If there is a Remark being associated with the Task representing the
<inspection> considered appropriate. inspection task then use Remark_text (possibly concatenated with
<remarks> AD DEX reference: Remark_date and Remark_provided_by_organization).
<simplePara>
− DEX3AD section
Remark - Template
table #360
<inspectionDefinition> List all the tasks that Subtask_by_refere The set of Subtask_by_reference being used within the Task
<taskGroup> belong to the inspection nce representing the inspection (DEX reference: DEX3AD section Subtask
or group of tasks. by definition - Template table #25).
AD DEX reference: All instances of Subtask, within a Task of type 'Package_task'
in S3000L, must be Subtask_by_reference.
− DEX3AD section
Subtask by reference -
Template table #25

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<inspectionDefinition> The individual task. Task Task (DEX reference: DEX3AD section Subtask by definition - Template
<taskGroup> table #24) being refered to via Subtask_by_reference (DEX
<taskItem> AD DEX reference: reference: DEX3AD section Subtask by definition - Template table #25).

Subtask by reference - There must be one instance of the element <taskItem> per
Template table #24 instance of Subtask_by_reference.
<inspectionDefinition> Sequential number to Subtask_identifie For more mapping details refer to the element
<taskGroup> indicate the task position r <inspectionDefinition><taskGroup><taskItem> above
in a sequence.
<taskItem@taskSeqNumb
er> AD DEX reference:
− DEX3AD section
Template table #25
<inspectionDefinition> The task itself. Task_identifier Task_identifier for the task being referenced as a subtask for the
<taskGroup> Packaged task
<taskItem@taskName> For more mapping details refer to the element
AD DEX reference:
<inspectionDefinition><taskGroup><taskItem> above.
− DEX3AD section
Subtask by definition - Business rule decision point - Multiple identifiers for tasks:
Template table #1 or If tasks have multiple identifiers, decide which identifier to use to populate
section Task definition - the attribute < taskItem@taskName>.
Template table #3

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<inspectionDefinition> Required skill level for the Skill_level_name The Skill_level_name for the Skill_level being associated
<taskGroup> task. with Task_personnel_resource (for the Task being referenced
<taskItem@skillLevelC (Not included in the current via Subtask_by_reference).
ode> version of AD DEXs) Identifies the lowest skill required that can perform the whole task (in
practice the highest defined within the task). Rules related to the skill codes
needs to be defined for the project.
Refer to element <mainProcedure@skillLevelCode> under
Para 3.4 'Main procedure' above.
<inspectionDefinition> Applicability at the task Applicability_sta Applicability_statement being associated with

<taskGroup> item level. tement Subtask_by_reference.
<taskItem@applicRefId Refer to discussion on applicability in Table 2 element
> <dmStatus><applic> above.
For AD DEX reference
refer to the element Business rule decision point – Use of applicability:
<dmStatus><applic> in
Decide how applicability will be used when associated with the attribute
Table 2 above
<taskItem@applicRefId>.
<inspectionDefinition> A short textual description Task_name For more mapping details refer to the element
<taskGroup> of the task. <inspectionDefinition><taskGroup><taskItem> above
<taskItem> AD DEX reference:
<task> Note
<taskTitle>
definition - Template The Task being referenced in DEX3AD section Subtask by
table #4 reference Template table #24, refers to a Task being defined in
accordance with DEX3AD section Task definition Template table #1.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<inspectionDefinition> A fuller textual description Task_name For more mapping details refer to the element
<taskGroup> of the task. <inspectionDefinition><taskGroup><taskItem><task
<taskItem> ><taskTitle> above
AD DEX reference:
<task>
<taskDescr>
table #4
<inspectionDefinition> Refer to data modules or N/A

<taskGroup> other publications that
represent the
<taskItem>
accomplishment
<refs> instructions for the task.
<dmRef>
<inspectionDefinition> Refer to data modules or N/A

<taskGroup> other publications that
represent the
<taskItem>
accomplishment
<refs> instructions for the task.
<externalPubRef>
or
<pmRef>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
4.4 Time limit information

Table 7 describes the elements and attributes in the S1000D element <timeLimitInfo>.
Note
There is no reference to any identified task (data module) from element
<timeLimitInfo>, as this branch of the Schema refers only to parts and their
potential life limit or storage limit.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 7 timeLimitInfo - Elements and attributes

definition
<timeLimitInfo> Time limit, periodicities Hardware_part_ope The data module will contain a list of life limited parts, ie Parts in S3000L
and life details information rational_authoriz that has at least one associated instance of
relating to a system. ed_life Hardware_part_operational_authorized_life (DEX
reference: DEX1AD section Hardware part - Template table #74).
<timeLimitInfo@timeLi The identifier of the <time N/A

mitIdent> limit.
<timeLimitInfo@skillL Skill level required of the N/A

evelCode> person who will perform
the task.
<timeLimitInfo> Equipment that belongs to Part The Part having a life limit (DEX reference: DEX1AD section Hardware
<equipGroup> the system. part - Template table #50).
<equip>
<timeLimitInfo> Nomenclature Part_name Note

<equipGroup> If a the Part has multiple names, a project specific business rule,
<equip> AD DEX reference: determined at the beginning of the project, is required that determines
<name> which Part_name to use.
− DEX1AD section
Hardware part - For mapping information refer to the element
Template table #52 <taskDefinition><equipgroup><equip> in Table 5 above.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo> Catalogue sequence N/A Should come from S2000M.

<equipGroup> number Can not be provided by S3000L.
<equip>
<catalogSeqNumberRef@
<timeLimitInfo> The NATO Stock Number Resource_specific For mapping information refer to
<equipGroup> ation_identifier <taskDefinition><equipgroup><equip> in Table 5 above.
<equip>
<natoStockNumber> AD DEX reference:
<fullNatoStockNumber>
− DEX3AD section
Material resource by
specification - Template
table #67
<timeLimitInfo> The manufacturer's Part_identifier@I For mapping information refer to

<equipGroup> identification information dentifier_set_by_ <taskDefinition><equipgroup><equip> in Table 5 above.
<equip> organization
<identNumber>
<manufacturerCode>
AD DEX reference:
− DEX1AD section
Hardware part -
Template table #53

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo> Part_identifier@I For mapping information refer to

<equipGroup> dentifier <taskDefinition><equipgroup><equip> in Table 5 above.
<equip>
<identNumber> AD DEX reference:
<partAndSerialNumber>
− DEX1AD section
<partNumber>
Hardware part -
Template table #53
<timeLimitInfo> Quantity of items of N/A

<reqQuantity> equipment
<timeLimitInfo> Unit of measure N/A

<reqQuantity@unitOfMe
asure>
<timeLimitInfo> Can represent categories N/A
<timeLimitCategory> such as "safety related"
or "non-safety related".

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo> Container element Hardware_part_ope

<timeLimit> rational_authoriz
ed_life
AD DEX reference:
− DEX1AD section
Hardware part –
template table #74
<timeLimitInfo> Defines the type of limit, 'Hard_time' Fixed string value ‘Hard time' (= lt02 in S1000D).
<timeLimit> eg 'between major
overhaul'.
<limitType@limitUnitT
ype>
<timeLimitInfo> Value and tolerance. Hardware_part_ope Populated with the Value given in the
<timeLimit> rational_authoriz Property_representation for the
<limitType> ed_life Hardware_part_operational_authorized_life.
<threshold> Note
AD DEX reference: The
− DEX1AD section Hardware_part_operational_authorized_life
Hardware part - attribute can have a Lower_offset_value and an
Template table #75 Upper_offset_value, if the
Property_representation is an instance of the
Value_with_tolerances_property.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo> Unit of measure for Hardware_part_ope The attribute <threshold@thresholdUnitOfMeasure> will be

<timeLimit> threshold value. rational_authoriz populated with the unit given in the attribute
<limitType> ed_life Hardware_part_operational_authorized_life.
<threshold@thresholdU
nitOfMeasure> AD DEX reference:
− DEX1AD section
Hardware part -
Template table #75
<timeLimitInfo> Hardware_part_ope The element <thresholdValue> will be populated with value given in
<timeLimit> rational_authoriz the Hardware_part_operational_authorized_life.
<limitType> ed_life
<threshold>
<thresholdValue> AD DEX reference:
− DEX1AD section
Hardware part -
Template table #75

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo Tolerances for the Hardware_part_ope If the Property_representation for

<timeLimit> threshold value. rational_authoriz Hardware_part_operational_authorized_life is of
<limitType> ed_life type Value_with_tolerances_property, then the optinonal
<threshold> element <toleranceLow> will be populated with
<tolerance@toleranceL AD DEX reference: Lower_offset_value given in the
ow / toleranceHigh> Hardware_part_operational_authorized_life, and the
− DEX1AD section
element <toleranceHigh> will be populated with
Hardware part -
Template table #75 Upper_offset_value given in the
Hardware_part_operational_authorized_life (DEX
reference: DEX3AD section Data type Prp - Template table #607).
<timeLimitInfo> Remarks at the limit type N/A

<timeLimit> level.
<limitType>
<remarks>
<timeLimitInfo> Remarks at the timeLimit Remark_text Remark being associated with the
<timeLimit> level. Hardware_part_operational_authorized_life property.
<remarks> Remark_text can possibly be concatenated with Remark_date and
AD DEX reference:
<simplePara> Remark_provided_by_organization.
− DEX3ADsection
Remark – Template
table #360

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<timeLimitInfo@applic Applicability_sta Applicability_statement being associated with the instance of

RefId> tement class Hardware_part_operational_authorized_life.
Business rule decision point – Use of applicability:
For AD DEX reference Decide how applicability will be used when associated with instances of
refer to the element Hardware_part_operational_authorized_life in
<dmStatus><applic> in S3000L.
Table 2 above
Refer to discussion on applicability in Table 2 element
<dmStatus><applic> above.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
4.5 Maintenance allocation

There are two different approaches to addressing maintenance allocation. These are:
− Display only the root node along with all its associated tasks, and all the tasks associated
with its repairable descendent elements
− Display the root node and all its descendent repairable nodes (hardware elements and/or
parts) along with their respective associated tasks
The mappings of S3000L, shown in Table 8 reflect the latter of the two approaches.
This mapping is based on the following specific business rule:
− There will be one instance of the element

<maintAllocationGroup><componentAssy> per repairable hardware
element where the hardware element has no identified part realization in S3000L.
− There will be one instance of the element
<maintAllocationGroup><componentAssyGroup> per repairable hardware
element where the hardware element has at least one part realization in S3000L.
Note
The first instance of the element <componentAssy> within the element
<maintAllocationGroup><componentAssyGroup> reflects the hardware
element. The following instances of the element <componentAssy> will reflect each
repairable Part that can realize the hardware element (including repairable Parts being
included in parts list for the Part that can realize the hardware element) in S3000L.
Table 8 describes the between the elements of S3000L and the elements and attributes within
the S1000D element <maintAllocation>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 8 maintAllocations - Elements and attributes

definition
<maintAllocation> The maintenance

allocation designates the
overall authority and the
responsibility for the
performance of
maintenance functions on
the identified end item or
component.
<maintAllocation> The title which describes N/A This title is assigned by the S1000D author.
<title> the maintenance
Product_variant and
The name of the selected
allocation.
Breakdown_element can be used
<maintAllocation> Used to group functional Breakdown_element There is one instance of the element <maintAllocationGroup>
<maintAllocationGroup> items together. per repairable/replaceable Breakdown_element being part of the
selected section of the physical breakdown of the Product (DEX reference:
AD DEX reference:
DEX1AD section Breakdown structure - Template table #36).
− DEX1AD section
Hardware element
table #130

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> The identifier of the Breakdown_element Breakdown_element_identifier that identifies the respective
<maintAllocationGroup maintenance allocation _identifier repairable "Physical" breakdown element.
group.
@id> Business rule decision point - Multiple identifiers for breakdown
elements:
AD DEX reference:
If breakdown elements have multiple identifiers, decide which identifier to
− DEX1AD section
use to populate the attribute <maintAllocationGroup@id>.
Hardware element
table #130 or #134
<maintAllocation> The competency level N/A

<maintAllocationGroup required of the person
who will perform the task.
@skillLevelCode>
<maintAllocation> The functional item group Breakdown_element Breakdown_element_identifier for an associated Breakdown
<maintAllocationGroup> of the end item. The _identifier element being used in a "Functional" breakdown of the Product (DEX
functional group applies to reference: DEX1AD section Breakdown structure - Template table #36).
<groupNumber>
repairable assemblies and
This can be derived from either a
subassemb-lies, ie spares AD DEX reference:
(any repairable Breakdown_element_relationship being classified as
− DEX1AD section 'functional_physical_relationship", (DEX reference:
component required for
Breakdown Aggregated DEX1AD section Hardware element realization - Template table #134) or
the maintenance or repair
Element - Template
of an end item), but not to using the same Breakdown_element_identifier as above
table #130 or #134
repair parts (any (<maintAllocationGroup@id>) if the breakdown element is used
consumable, non- within both breakdown structures.
repairable component
required for the
maintenance or repair of
an end item).

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Breakdown_element Note

<maintAllocationGroup> Direct usage of the element <componentAssy> within the
<componentAssy> element <maintAllocationGroup> will only be used for
breakdown elements that has no defined Part realization.
<maintAllocation> The name or Breakdown_element Breakdown_element_name

<maintAllocationGroup> nomenclature of the item. _name
<componentAssy>
<name> AD DEX reference:
− DEX1AD section
Hardware element
table #132
<maintAllocation> Text string used to give N/A This is assigned by the S1000D author.
<maintAllocationGroup> further information about
the component assembly.
<componentAssy>
<typeDesignation>
<maintAllocation> Maintenance action Task There is one instance of the element <maintQualifier> per
<maintAllocationGroup> qualification such as Rectifying_task being associated with the repairable
maintenance function,
<maintQualifier> AD DEX reference: Breakdown_element (DEX reference: DEX3AD section Task
maintenance level
assignment - Template table #140).
estimated work time, any − DEX3AD section Task
tools and/or test definition - Template
equipment and any table #1
remarks.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> The maintenance function Task_name The Task_name associated with the Task under consideration (refer to
<maintAllocationGroup> to be performed on the the mapping defined for element <maintAllocation>
item listed (eg inspection,
<maintQualifier> AD DEX reference: <maintAllocationGroup><maintQualifier> above).
test, and service).
<maintFunction@functi Business rule decision point - Map between information codes and
on> definition - Template maintenance functions:
table #1 or Template Decide on the map between information codes and the values for the
table #4 attribute <maintFunction@function>.
Business rule decision point - Multiple names for tasks:
If tasks have multiple names, decide which name to use to populate the
attribute <maintFunction@function>.
<maintAllocation> The lowest authorized -

<maintAllocationGroup> maintenance level and the
associated estimated
<maintQualifier>
work time to perform the
<maintLevelGroup> maintenance.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Estimated work time. Task_total_labour Task_total_labour_time, attribute of the Task under
<maintAllocationGroup> _time or consideration.
<maintQualifier> Task_personnel_re This could also be calculated by summarizing either:
<maintLevelGroup> source_labor_time − All Task_personnel_resource_labour_times for all the
<maintLevel> Task_personnel_resources being associated directly with
AD DEX reference: the Task (DEX reference: DEX3AD section Task personnel resource
− DEX3AD section Task - Template table #110).
definition - Template − All Task_personnel_resource_labour_times for all the
table #14 for task total Task_personnel_resources being associated with any of the
labour time 'Core' Subtask(s) of the Task (DEX reference: DEX3AD section
or Task personnel resource - Template table #110 and Template table
− DEX3AD section Task #41).
personnel resource - Note
S1000D, Issue 4.0 uses a simple string to capture the man-hours
task personnel
associated with the maintenance level for the maintenance task being
resource labor time
documented.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> The maintenance level is Maintenance_level The name of the Maintenance_level_type etc being associated
<maintAllocationGroup> specified by selecting an _type_name with the Maintenance_level_allocation for the Task and
enumerated value for the
<maintQualifier> Task_usage under consideration.
maintenance level code
<maintLevelGroup> this element is used to AD DEX reference: Required business rule. If the task doesn't have an associated maintenance
<maintLevel@maintLeve gather the information level type it should transform its associated
lCode> about the lowest
Maintenance_location, Operating_location_type or
authorized maintenance Operating_location into a maintenance level (DEX reference:
table #154
level and the associated DEX3AD section Task assignment - Template table #152, Template table
estimated work time to #156, and Template table #158, respectively).
perform the maintenance.
The maintenance level is
specified by selecting an
maintenance level code.
<maintAllocation> A reference to a required N/A This is assigned by S1000D author. It can be derived from
<maintAllocationGroup> tool or test equipment that Task_material_resource_by_reference or
is contained in the tools Task_material_resource_by_specification, where the
<maintQualifier>
list within the
<toolsRefs> resource is identified as Support_equipment. Codes could be
maintenance allocation
assigned to each individual tool but S3000L does not have a data element
data.
for this.
<maintAllocation> A reference to remarks N/A

<maintAllocationGroup> contained in the remarks
list within the
<maintQualifier>
<remarksRefs> data.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Used when there is a Breakdown_element The element <componentAssyGroup> will be used for S3000L
<maintAllocationGroup> requirement to subdivide /Part elements that have one or many Part realizations which are repairable.
the list into
<componentAssyGroup>
subassemblies.
AD DEX reference:
− DEX1AD section
Hardware element
table #130 and its
reference to a
Hardware part
realization (DEX1AD
section Hardware_part
- Template table #50
<maintAllocation> The name or Part_name Part_name

<maintAllocationGroup> nomenclature of the item. The first instance of the element
<componentAssyGroup> <componentAssyGroup><componentAssy> shall reflect the
AD DEX reference:
<componentAssy> hardware element, and shall therefore follow the mapping being defined
− DEX1AD section under the element
<name>
Hardware part - <maintAllocation><maintAllocationGroup>
Template table #52
<componentAssy><name> above.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Text string used to give N/A This is assigned by the S1000D author.
<maintAllocationGroup> further information about
the component assembly.
<componentAssy>
<typeDesignation>
<maintAllocation> Maintenance Task There is one instance of the element <maintQualifier> per
<maintAllocationGroup> actionqualification such as Rectifying_task being associated with the repairable the Part
maintenance function, that can realize the hardware element itself (DEX reference: DEX3AD
<componentAssyGroup> AD DEX reference:
maintenance level section Task assignment - Template table #140).
<maintQualifier> estimated work time, any − DEX3AD section Task Note
tools and/or test definition - Template
equipment and any table #1 The first instance of the element
remarks. <componentAssyGroup><componentAssy> shall reflect
the hardware element, and shall therefore follow the mapping being
defined under the element
<maintAllocation><maintAllocationGroup>
<maintQualifier>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> The maintenance function Task_name The Task_name associated with the Task under consideration (refer to
<maintAllocationGroup> to be performed on the the mapping defined for element <maintAllocation>
item listed (eg inspection,
<componentAssyGroup> AD DEX reference: <maintAllocationGroup>
test, and service).
<maintQualifier> <componentAssyGroup><maintQualifier> above).
<maintFunction@functi Business rule decision point - Map between information codes and
on> table #1 or Template maintenance functions:
table #4 Decide on the map between information codes and the value4s for the
Business rule decision point - Multiple names for tasks:
If tasks have multiple names, decide which name to use to populate the
<maintAllocation> The lowest authorized -

<maintAllocationGroup> maintenance level and the
associated estimated
work time to perform the
<maintQualifier> maintenance.
<maintLevelGroup>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Estimated work time. Task_total_labour Task_total_labour_time, attribute of the Task under
<maintAllocationGroup> _time or consideration.
<componentAssyGroup> Task_personnel_re This could also be calculated by summarizing either:
<maintQualifier> source_labor_time − All Task_personnel_resource_labour_times for all the
<maintLevelGroup> Task_personnel_resources being associated directly with
<maintLevel> the Task (DEX reference: DEX3AD section Task personnel resource
AD DEX reference:
− DEX3AD section Task - Template table #110).
definition - Template − All Task_personnel_resource_labour_times for all the
table #14 for task total Task_personnel_resources being associated with any of
labour time the 'Core' Subtasks of the Task (DEX reference: DEX3AD section
or Task personnel resource - Template table #110 and Template table
− DEX3AD section Task #41).
personnel resource - Note
S1000D, Issue 4 uses a simple string to capture the man-hours
task personnel
associated with the maintenance level for the maintenance task being
resource labor time
documented.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> The maintenance level is Maintenance_level The name of the Maintenance_level_type etc being associated
<maintAllocationGroup> specified by selecting an _type_name with the Maintenance_level_allocation for the Task and
<componentAssyGroup> Task_usage under consideration.
maintenance level code
<maintQualifier> and is used to gather the AD DEX reference: If the task doesn't have an associated maintenance level type it should
<maintLevelGroup> information about the transform its associated Maintenance_location,
<maintLevel@maintLeve lowest authorized Operating_location_type or Operating_location into a
lCode> maintenance level and the maintenance level (DEX reference: DEX3AD section Task assignment -
table #154
associated estimated Template table #152, Template table #156, and Template table #158,
work time to perform the respectively).
maintenance. The
maintenance level is
specified by selecting an
maintenance level code.
<maintAllocation> A reference to a required N/A

<maintAllocationGroup> tool or test equipment that
is contained in the tools
list within the
<maintQualifier> maintenance allocation
<toolsRefs> data.
<maintAllocation> A reference to remarks N/A

<maintAllocationGroup> contained in the remarks
list within the
<maintQualifier> data.
<remarksRefs>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation Used to list both special S3000L does not maintain a separate tools list. All tools/test equipment are
<maintPlanning and common tools and associated with the Task as resources.
test equipment required to
<toolsList>
maintain the equipment
as indicated in the
maintenance allocation.
<maintAllocation> Used to capture the tools N/A This is assigned by S1000D author.
<maintPlanning> and test equipment list
title.
<toolsList>
<title
<maintAllocation> Used to capture data N/A S3000L does not group tools or test equipment.
<maintPlanning> about the tool or test
equipment.
<toolsList>
<toolsListGroup>
<maintAllocation> Used to provide an id for N/A This is assigned by S1000D author based on all the tools and test
<maintPlanning> the purposes of equipment captured by the elements
crossreferencing. The task_material_resource_by_reference or
<toolsList>
element also allows for task_material_resource_by_specification. It could be
<toolsListGroup@tools string data in the event assigned in S3000L, but element does not exist.
ListCode> that a particular code
suchas "A", "B", or "C" is
used to identify the tool in
the maintenance
allocation data.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Used to capture the This can be generated from the tools being used for the respective tasks.
<maintPlanning> lowest authorized
maintenancelevel.
<toolsList>
<toolsListGroup>
<maintLevel>
<maintAllocation> The enumerated attribute Maintenance_level The lowest authorized maintenance level can be derived in two ways:
identifying the lowest
<maintPlanning> _type_name − By identifying the lowest Maintenance_level_type being
authorized maintenance
<toolsList> associated with any Task being associated with the tool (DEX
level.
<toolsListGroup> AD DEX reference: reference: DEX3AD section Task material resource -Template table
<maintLevel@maintLeve #140 and Template table #150, respectively),
lCode> assignment - Template − By identifying the lowest Maintenance_level_type being
table #154 associated with a Task within which the tool is being used as a
resource (DEX reference: DEX3AD section Task material resource by
reference - Template table #80, Template table #86, and Template table
#70, respectively).
<maintAllocation> Used to identify the tool or Part_name The Part_name for the
<maintPlanning> test equipment. A basic 'Required_support_equipment_resource' identified by
name or noun should be
<toolsList> the task_material_resource_by_reference (DEX
used. AD DEX reference:
<toolsListGroup> reference: DEX3AD section Task material resource by reference - Template
− DEX1AD section table #80 and Template table #86, respectively).
<name>
Hardware part -
Template table #52 Business rule decision point - Multiple names for parts:
If parts have multiple names, decide which name to use to populate the
element <toolsListGroup><name>.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Provides an identifier for Resource_specific Resource_specification_identifier classified as

<maintPlanning> the equipment thatfollows ation_identifier ’NSN_code’for the the
the coding system
<toolsList> 'Required_support_equipment_resource’ identified by
determined by NATO, and
<toolsListGroup> Ministries or Departments AD DEX reference: the task_material_resource_by_reference (DEX
<natoStockNumber> of Defense. reference: DEX3AD section Task material resource by reference - Template
− DEX3AD section Task table #86).
specification - Template
table #67
<maintAllocation> Used to indicate the tool N/A

<maintPlanning> number.
<toolsList>
<toolsListGroup>
<toolRef>
<maintAllocation> The tool number. Resource_specific Task_material_resource_by_specification attribute

<maintPlanning> ation_identifier Resource_specification_identifier where the
<toolsList> Task_material_resource is an instance of
<toolsListGroup> AD DEX reference: Task_material_resource_by_specification.
<toolRef@toolNumber> Note
material resource by (Reference to the CIR data module for the list of tool associated with
specification - Template the procedure).
table #67

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Used to list remarks S3000L does not maintain a list of remarks.
<maintPlanning> pertinent to the
maintenance functions
<toolsList>
listed in maintenance
<remarksList> allocation data. The
purpose is to provide a list
for referencing from
maintenance allocation.
When remarks are
indicated in the
maintenance allocation,
the remarks list must be
included.
<maintAllocation> Used to capture the N/A This is assigned by the S1000D author.
<remarksList> remarks list title.
<title>
<maintAllocation> Used to capture remarks N/A

<remarksList> pertinent to
themaintenance of the
<remarksGroup>
assemblies and
subassemblies. It includes
elements for remarks
listcode and remarks.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<maintAllocation> Used to provide an id for N/A This is assigned by the S1000D author. It could be derived from the remarks
<remarksGroup> the purposes of associated with a task or the tools/test equipment. The element does not
crossreferencing. The exist in S3000L.
<remarksCode>
element also allows for
string data in the event
that a particular code
suchas "A", "B", or "C" is
used to identify the
remark in the
data.
<maintAllocation> Used to capture the N/A This can be derived from remarks being associated with either the task or
<remarksGroup> remarks about the data. the tool.
<remarks>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
5 S1000D Applicability schemas

5.1 Introduction
Applicability, in S1000D, provides the mechanism to identify the context for which a data
module or parts of a data module is valid. This context is usually associated with the physical
configuration of the Product but can include other aspects such as tool availability and
environmental conditions. Applicability capabilities can vary greatly, from a simple annotation
placed in the content of a data module to managing the life cycle of applicability which includes
product definition, applicability authoring and product instance configuration tracking.
The applicability mechanism is supported by the applicability annotation within data modules
and by three specific data module types:
− the Applicability Cross-reference Table (ACT) data module

− the Conditions Cross-reference Table (CCT) data module
− the Products Cross-reference Table (PCT) data module
The ACT data module is used to declare product attributes that can affect the applicability of
data. Product attributes are properties of the Product that will typically not change throughout
the service life of a product instance (eg model or serial number).
The CCT data module is used to declare any type of condition that can affect the applicability of
data. Conditions can be technical, operational, environmental or any other type of condition that
can affect technical data. Technical conditions are typically tied to the configuration of the
Product (eg service bulletins or modifications). The state of technical conditions can change
throughout the service life of a product instance. (eg location of maintenance, availability of
tools, regulatory rules, temperature, wind speed and sandy conditions).
The PCT data module is a repository for defining product instances and the specific values for
product attributes and conditions for each product instance. It is a formal method of defining
product instances and the configuration of each product instance. This part of the applicability
model is out of scope of S3000L, and therefore not considered in the following mapping tables.
5.2 Applicability cross-reference table

<applicCrossRefTable> in the ACT Schema.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 9 applicCrossRefTable - Elements and attributes

Element/Attribute name Element/Attribute DEX referenc
definition
<applicCrossRefTable> A list of attributes of the Product_variant, The elements in S3000L that can be regarded as being candidates for
<productAttributeList> product. The values for Product_variant_r populating the product attributes list in S3000L are:
product attributes will
typically not change
ealization and − Product_variant
Block_of_serializ
throughout the service life
ed_items − Product_variant_realization
of product instance.
− Block_of_serialized_items
<applicCrossRefTable> Is used to declare a single A fixed mapping in between the entities and attributes in S3000L and
<productAttributeList> attribute of the Product, product attributes in S1000D is required.
such as "serial number" or A proposed mapping is defined under attribute
<productAttribute>
"model". <applicCrossRefTable>
<productAttributeList><productAttribute@id>
below.
<applicCrossRefTable> The identifier of the Product_variant, When mapping between Applicability_statements in S3000L,
<productAttributeList> element Product_variant_r and the definition of product attributes in S1000D:
<productAttribut
<productAttribute@id> ealization and − Define a product attribute with @id= 'productVariant' in the
e>. Block_of_serializ ACT, if there is at least one instance of
ed_items Applicability_evaluation_by_assertion in S3000L
that refers to an instance of Product_variant (DEX reference:
DEX3AD section Applicability statement assertion Template table #400,
and its reference to DEX1AD section Product and Project - Template
Product_variant:
table #15).
− DEX3AD section
− Define a product attribute with @id=
assertion Template 'productConfiguration' in the ACT, if there is at least one
table #400, and its instance of

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
reference to DEX1AD Applicability_evaluation_by_assertion_of_cla
section Product and ss in S3000L that refers to an instance of
Project - Template
Product_variant_realization (DEX reference: DEX3AD
table #15
section Applicability statement assertion Template table #400, and its
AD DEX reference for references to DEX1AD section Product variant applicability - Template
Product_variant_realization table #203).
:
− Define a product attribute with @id=
− DEX3AD section 'endItemSerialNumberRange' in the ACT, if there is at least
one instance of
assertion Template
table #400, and its Applicability_evaluation_by_assertion_of_cla
references to DEX1AD ss in S3000L that refers to an instance of Product_variant
section Product variant which in turn refers to a Block_of_serialized_items (DEX
applicability - Template reference: DEX3AD section Applicability statement by assertion of serial
table #203 number Template table #390, and its reference to DEX1AD section
AD DEX reference for Product and Project for the Part representing the
Block_of_serialized_items: Product_variant).
− DEX3AD section
number Template table
#390, and its reference
to DEX1AD section
Product and Project for
the Part representing
the Product_variant

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<applicCrossRefTable> Name of the product Product_variant, Refer to the mapping for the attribute <productAttribute@id>
<productAttributeList> attribute. Product_variant_r above. Proposed names for the respective element
<productAttribute> ealization and <productAttribute><name> are:
<name> Block_of_serializ − 'Model' for instances of Product_variant
ed_items
− 'Product configuration' for instances of
− 'End item serial number' for instances of Product_variant which
refers to Block_of_serialized_items
<applicCrossRefTable> Text which can be used to Product_variant, Refer to the mapping for the attribute <productAttribute@id>
<productAttributeList> help automated Product_variant_r above. Proposed display names for the respective element
generation the human ealization and <productAttribute><displayName> are:
<productAttribute>
readable display text on
<displayName> an applicability Block_of_serializ − 'Model' for instances of Product_variant
annotation. ed_items
− 'Config' for instances of Product_variant_realization
− 'SN' for instances of Product_variant which refers to
Block_of_serialized_items
<applicCrossRefTable> Contains further Product_variant, Refer to the mapping for the attribute <productAttribute@id>
<productAttributeList> clarification of the Product_variant_r above. Proposed descriptions for the respective product attribute <descr>
meaning of the product ealization and are:
<productAttribute>
attribute.
<descr> Block_of_serializ − 'A model defines a specific variant of the generic product. Model is also
ed_items known as Usable On Code.’
− 'A product configuration defines a specific assembly of the model.’
− 'Serial number defines a range of end items.’

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<applicCrossRefTable> Allowable values for the Product_variant_i When populating the element <enumeration>:
<productAttributeList> product attribute. dentifier, − For the attribute value <productAttribute@id=
<productAttribute> Product_variant_r 'productVariant'>, populate the element <enumeration>
<enumeration ealization_identi with the identifiers for the defined instances of
@applicPropertyValues fier Product_variants in S3000L
> (Product_variant_identifier).
AD DEX reference for Business rule decision point - Multiple identifiers for product variants:
Product_variant_identifier: If product variants have multiple identifiers, decide which identifier to use to
− DEX1AD section populate the attribute <inspection@id>.
Product and Project -
− For <productAttribute@id= 'productConfiguration'>, populate
Template table #6/#8
the element <enumeration> with the identifiers for the defined
Product_variant_realization instances of Product_variant_realization in S3000L
_identifier: (Product_variant_realization_identifier).
− DEX1AD section − For <productAttribute@id='serialNumber'>, let the element
Product variant <enumeration> be blank.
applicability- Template
table #201 Also refer to the mapping for the attribute <productAttribute@id>
above.
<applicCrossRefTable> Reference to the CCT N/A This is assigned by the S1000D author.
<condCrossRefTableRef> data module for this
project.
<applicCrossRefTable> Reference to the PCT N/A This is assigned by the S1000D author.
<productCrossRefTableR data module for this
project.
ef>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
5.3 Condition cross-reference table

<condCrossRefTable> in the CCT Schema.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Table 10 condCrossRefTable - Elements and attributes

definition
<condCrossRefTable> A list of common types of Condition_by_iden The elements in S3000L that can be regarded as being candidates for
<condTypeList> conditions which will be tifier, populating the condition type list in S1000D are:
used as a basis for
defining specific
Condition_type, − Condition_by_identifier
Maintenance_level
conditions.
_type, − Condition_type
Maintenance_locat − Maintenance_level_type
ion, − Maintenance_location
Operating_locatio
n_type, − Operating_location_type
Operating_locatio − Operating_location
n,
− Breakdown_element
Breakdown_element
, Part, User, − Part
Customer, Contract − User
and
− Customer
Product_usage_pha
se − Contract
− Product_usage_phase
Condition_by_identifier:
− DEX3AD section
table #408

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
Condition_type:
− DEX3AD section
table #406 if the
condition type value is
represented as a
property in the DEX
− DEX3AD section
table #400 if the
condition type value is
value in the DEX
Maintenance_level_type:
− DEX3AD section
assertion and its
reference to DEX3AD
section Task
table #154
Maintenance_location:
− DEX3AD section
assertion and its
reference to DEX3AD

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
section Task
table #152
Operating_location_type:
− DEX3AD section
assertion and its
reference to DEX3AD
section Task
table #158
Operating_location:
− DEX3AD section
assertion and its
reference to DEX3AD
section Task
table #156
Breakdown_element:
− DEX3AD section
assertion and its
references to either
DEX1AD section
Breakdown element
realization (Template

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
tables #130 and #150),
or DEX1AD section
Aggregated breakdown
element (Template
table #170)
AD DEX reference for Part:
− DEX3AD section
assertion and its
tables #50 and #80
− DEX3AD section
number - Template
table #390
− DEX3AD section
assertion and its
section Product and
Project - Template
table #22
Customer:
− DEX3AD section

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
assertion and its
section Product and
Project - Template
table #19
Contract:
− DEX3AD section
assertion and its
section Product and
Project - Template
table #15
− DEX3AD section
table #410
<condCrossRefTable> Is used to define a single A fixed mapping in between the entities and attributes in S3000L and
<condTypeList> condition type of the condition types in S1000D is required.
Product. The mapping for the attribute
<condType>
<condCrossRefTable><condTypeList><condType@id>
below defines a proposed mapping.
<condCrossRefTable> The identifier of the Condition_type_na The following business rule is recommended for mapping between
<condTypeList> element <condType>. me, Applicability_statements in S3000L, and the definition of
<condType@id> Condition_by_iden condition types in S1000D:

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
tifier, Condition_type_name
Maintenance_level − Define one instance of the element <condType> per instance of
_type, defined Condition_type in S3000L and populate the attribute
Maintenance_locat <condType@id> with the Condition_type_name.
ion,
Note
Operating_locatio
n_type, The value that is to populate the attribute <condType@id> is
Operating_locatio exchanged in two different ways using DEX3AD. This is due to that the
condition type value can be defined as either a property value or as a
n, class value. If the condition type value is represented as a property
Breakdown_element then use the value defined in DEX3AD section Applicability statement
, Part, User, by assertion of condition parameter - Template table #406 input
Customer, Contract parameter ‘property_class_name’ to populate the attribute
and <condType@id>. If the condition type value is represented as a
Product_usage_pha class value then use the value defined in DEX3AD section Applicability
se statement by assertion of condition parameter - Template table #400
input parameter ‘para_class’ to populate the attribute
<condType@id>.
Condition_by_identifier
− Define one instance of the element <condType> which identifies
valid values for Condition_by_identifier applicability
statements. Populate the attribute <condType@id> with
‘serviceBulletin’
Maintenance_level_type, Maintenance_location,
Operating_location_type, and Operating_location
− Define one instance of the element <condType> which contains all
instances of Maintenance_level_type,

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
Maintenance_location, Operating_location_type
and Operating_location. Populate the attribute
<condType@id> with ‘location’
Breakdown_element
relevant instances of Breakdown_element. Populate the attribute
<condType@id> with ‘positionInProduct’
Part
relevant instances of Part. Populate the attribute
<condType@id> with ‘partNumber’
User
relevant instances of User. Populate the attribute
<condType@id> with ‘userOrganization’
Customer
relevant instances of Customer. Populate the attribute
<condType@id> with ‘customerOrganization’
Contract
relevant instances of Contract. Populate the attribute
<condType@id> with ‘contract’

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
Product_usage_phase
relevant instances of Product_usage_phase. Populate the
attribute <condType@id> with ‘productUsagePhase’
<condCrossRefTable> The name of the condition Condition_type_na For mapping information refer to element <condType@id> above.
<condTypeList> type. me, Proposed names for the respective instance of the element
<condType> Condition_by_iden <condType><name> are:
<name> tifier,
Condition_type_name
Maintenance_level
_type, − The value that is to populate the element <condType><name> for
Maintenance_locat the respective Condition_type must be the same value as is
ion, used to populate the attribute <condType@id>. (DEX references:
Operating_locatio DEX3AD section Applicability statement by assertion of condition
parameter - Template tables #406 and #400)
n_type,
Operating_locatio Condition_by_identifier
n, − The instance of the element <condType> which defines valid values
Breakdown_element for Condition_by_identifier must populate the element
, Part, User, <name> with the fixed string value ‘Service bulletin type’
Customer, Contract Maintenance_level_type, Maintenance_location,
and
Product_usage_pha
se − The instance of the element <condType> which defines all relevant
and Operating_location must populate the element <name>
with the fixed string value ‘Location for task performance’

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
Breakdown_element
− The instance of the element <condType> which defines all relevant
instances of Breakdown_element must populate the element
<name> with the fixed string value ‘Position in product (end item)’
Part
instances of Part must populate the element <name> with the fixed
string value ‘Part numbered item’
User
instances of User must populate the element <name> with the fixed
string value ‘User organization’
Customer
instances of Customer must populate the element <name> with the
fixed string value ‘Customer’
Contract
instances of Contract must populate the element <name> with the
fixed string value ‘Contract’
Product_usage_phase
instances of Product_usage_phase must populate the element
<name> with the fixed string value ‘Product usage phase’

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condCrossRefTable> Further clarification of the Condition_type_na For more mapping information refer to also<condType@id> above.
<condTypeList> meaning of the condition me, Proposed descriptions for the respective instance of the element
type, Condition_by_iden
<condType> <condType><descr> are:
<descr> tifier,
Condition_type_name
Maintenance_level
_type, − The value that is to populate the element <condType><descr> for
Maintenance_locat the respective Condition_type can be retrieved from the Reference Data
Library (RDL). The value to use must be the description for the
ion,
respectice class used to populate the attribute <condType@id>.
Operating_locatio (DEX references: DEX3AD section Applicability statement by assertion
n_type, of condition parameter - Template tables #406 and #400)
Operating_locatio Condition_by_identifier
n,
Breakdown_element − The instance of the element <condType> which defines valid values
, Part, User, for Condition_by_identifier must populate the element
Customer, Contract <descr> with the fixed string value ‘Service bulletin type’
and Maintenance_level_type, Maintenance_location,
Product_usage_pha Operating_location_type, and Operating_location
se
and Operating_location must populate the element
<descr> with the fixed string value ‘Location for task performance’
Breakdown_element
instances of Breakdown_element must populate the element

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<descr> with the fixed string value ‘Position in product (end item)’
Part
instances of Part must populate the element <descr> with the fixed
string value ‘Part numbered item’
User
instances of User must populate the element <descr> with the fixed
string value ‘User organization’
Customer
instances of Customer must populate the element <descr> with
the fixed string value ‘Customer’
Contract
instances of Contract must populate the element <descr> with
the fixed string value ‘Contract’
Product_usage_phase
instances of Product_usage_phase must populate the element
<descr> with the fixed string value ‘Product usage phase’
<condCrossRefTable> Allowable values for the Condition_type_cl For more mapping information refer to <condType@id> above.
<condTypeList> condition type. ass_value, Proposed allowable values for the respective instance of the attribute
<condType> Condition_type_pr <condType> <enumeration@applicPropertyValues>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<enumeration operty_value, are:
@applicPropertyValues Condition_by_iden Condition_type_class_value and
> tifier, Condition_type_property_value
Maintenance_level − The values that are to populate the attribute
_type_name, <condType><enumeration@applicPropertyValues>
Maintenance_locat for the respective instance of Condition_type, can be retrived
ion_name, from the defined property and class values which are referenced by the
Operating_locatio respective Condition_type (DEX references: DEX3AD section
n_type_name, Applicability statement by assertion of condition parameter - Template
Operating_locatio tables #405 for Condition_type_class_value, and and
n_name, Template table #406 Condition_type_property_value).
Breakdown_element Note
_identifier, Property values should concatenate both the value itself and its unit, eg
Part_identifier, ’16-30 Miles_per_hour’ which can be a defined value range for
Organization_name a Wind speed property.
(User and Customer),
Condition_by_identifier
Contract_identifi
er and − The instance of the element <condType> which defines valid values
Product_usage_pha for Condition_by_identifier must populate the attribute
se <enumeration@applicPropertyValues> with the values
that are referenced by Condition_by_identifier (DEX
reference: DEX3AD section Applicability statement by assertion of
condition parameter - Template tables #409)
Note
Proposed values in Template table #409 are
‘Pre_activity_state’ and ‘Post_activity_state’,
which would result in the value <enumeration

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
applicPropertyValues=”Pre_activity_state”|”‘Po
st_activity_state”> of the attribute
<enumeration@applicPropertyValues>
Maintenance_level_type_name,
Maintenance_location_name,
Operating_location_type_name, and
Operating_location_name
− The instance of the element <condType> which defines instances of
Operating_location_type and Operating_location
must populate the attribute
<enumeration@applicPropertyValues> with the names,
or codes, that identifies the organization, or type of organization, which
are referenced by any applicability statement (DEX reference: DEX3AD
section Applicability statement by assertion of condition parameter
Template table #400, and its reference to DEX3AD section Task
assignment - Template tables #152, #154, #156 and #158).
Breakdown_element_identifier
Breakdown_element, must populate the attribute
<enumeration@applicPropertyValues> with the
Breakdown_element_identifiers which are referenced by
any applicability statement (DEX reference: DEX3AD section
Applicability statement by assertion of condition parameter Template
table #400, and its reference to either:
o DEX1AD
section Hardware element realization - Template table #130 for

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
hardware elements
o DEX1AD
section Breakdown aggregated element - Template table #170
for aggregated elements
o DEX1AD
section Breakdown zone element- Template table #183 for zone
elements
Part_identifier
Part, must populate the attribute
Part_identifiers which are referenced by any applicability
statement (DEX reference: DEX3AD section Applicability statement by
assertion of condition parameter Template table #400, and its reference
to either:
o DEX1AD
section Hardware part- Template table #50 for hardware parts
o DEX1AD
section Software part - Template table #80 for software parts
Organization_name (User)
User must populate the attribute
<enumeration@applicPropertyValues> with the names
that identifies the user organizations which are referenced by any
applicability statement (DEX reference: DEX3AD section Applicability
statement by assertion of condition parameter Template table #400, and
its reference to DEX1AD section Product and Project - Template table

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
#22)
Organization_name (Customer)
Customer must populate the attribute
<enumeration@applicPropertyValues> with the names
that identifies the customer organizations which are referenced by any
#19)
Contract_identifier
Contract must populate the attribute
Contract_identifiers which are referenced by any
#15)
Product_usage_phase
Product_usage_phase must populate the attribute
<enumeration@applicPropertyValues> with the values
that are used to define Product_usage_phase (DEX reference: DEX3AD
section Applicability statement by assertion of condition parameter -
Template tables #410)

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condCrossRefTable> A list of specific Condition_type_na For more mapping information refer to also<condType@id> above.
<condList> conditions which have an me,
effect on the applicability Condition_by_iden
of technical data.
tifier,
Maintenance_level
_type,
Maintenance_locat
ion,
Operating_locatio
n_type,
Operating_locatio
n,
Breakdown_element
, Part, User,
Customer, Contract
and
Product_usage_pha
se
<condCrossRefTable> Identification of the Condition_type_na For mapping between Applicability_statements in S3000L, and the definition
<condList> generic type of condition me, of conditions in S1000D:
that the specific condition Condition_by_iden
<cond> Condition_type_name
is based on
tifier, − Define one instance of the element <condList><cond> per
Maintenance_level instance of defined Condition_type in S3000L (refer to the
_type, mapping defined for attribute
Maintenance_locat <condTypeList><condType@id> above.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
ion, Note
Operating_locatio There will be a one to one relationship between the elements defined
n_type, for Condition_types under the element
Operating_locatio <condTypeList><condType> above, and the elements
n, defined for Condition_types defined in the element
Breakdown_element <condList><cond>
, Part, User, Condition_by_identifier
Customer, Contract
and − Define one instance of the element <condList><cond> per
Product_usage_pha instance of Condition_by_identifier
se Maintenance_level_type, Maintenance_location,
− Define one instance of the element <condType> for
Operating_location_type and
Operating_location.
Note
There will be a one to one relationship between the elements defined
for Maintenance_level_type,
Maintenance_location,
Operating_location, under the element
<condTypeList><condType> above, and the elements
defined for Maintenance_level_type,
Maintenance_location,
Operating_location defined in the element

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condList><cond>
Breakdown_element
Breakdown_element.
Note
for Breakdown_element under the element
defined for Breakdown_element defined in the element
<condList><cond>
Part
− Define one instance of the element <condType> for Part.
Note
for Part under the element <condTypeList><condType>
above, and the elements defined for Part defined in the element
<condList><cond>
User
− Define one instance of the element <condType> for User.
Note
for User under the element <condTypeList><condType>
above, and the elements defined for User defined in the element
<condList><cond>

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
Customer
− Define one instance of the element <condType> for Customer.
Note
for Customer under the element
defined for Customer defined in the element
<condList><cond>
Contract
− Define one instance of the element <condType> for Contract.
Note
for Contract under the element
defined for Contract defined in the element
<condList><cond>
Product_usage_phase
Product_usage_phase.
Note
for Product_usage_phase under the element
defined for Product_usage_phase defined in the element

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condList><cond>
<condCrossRefTable> Identification of the Condition_type_na For mapping refer to the element <condList><cond> above.
<condList> generic type of condition me, Values are to be populated according to the values defined for the
that the specific condition Condition_by_iden
<cond@condTypeRefId> attribute<condTypeList><condType@id> above.
is based on
tifier, Note
Maintenance_level
There must be one instance of the element <condList><cond>
_type,
per instance of Condition_by_identifier, which refers
Maintenance_locat
back to the attribute <condTypeList><condType@id>
ion,
defined for Condition_identifier
Operating_locatio
n_type,
Operating_locatio
n,
Breakdown_element,
Part, User,
Customer, Contract
and
Product_usage_pha
se

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condCrossRefTable> Condition_type_na For mapping refer to the element <condList><cond> above.

<condList> me, Note
<cond@id> Condition_identif Values are to be populated according to the mapping defined in the
ier, attribute <condTypeList><condType@id> above except for
Maintenance_level instances of Condition_by_identifier.
_type,
Instances of the element <condList><cond> which defines
Maintenance_locat
instances Condition_by_identifier must populate the
ion,
attribute <cond@id> with the respective
Operating_locatio
n_type, Condition_identifier (DEX reference: DEX3AD section
Applicability statement by assertion of condition parameter - Template
Operating_locatio tables #408)
n,
Breakdown_element
, Part, User,
Customer, Contract
and
Product_usage_pha
se

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condCrossRefTable> Name of the condition. Condition_type_na For mapping refer to the element <condList><cond> above.
<condList> me, Note
<cond> Condition_name, Values are to populated according to the mapping defined for element
<name> Maintenance_level <condTypeList><condType><name> above except for
_type, instances of Condition_by_identifier.
Maintenance_locat
Instances of the element <condList><cond> which defines instances
ion,
of Condition_by_identifier must populate the element
Operating_locatio
<name> with the respective Condition_name).
n_type,
Operating_locatio Note
n, Condition_name is not included in the current version of DEX3AD.
Breakdown_element
, Part, User,
Customer, Contract
and
Product_usage_pha
se
<condCrossRefTable> Text which can be used to N/A
<condList> help automated
generation of human
<cond>
readable display text on
<displayName> an applicability
annotation.

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
definition
<condCrossRefTable> Further clarification of the Condition_type_na For mapping refer to the element <condList><cond> above.
<condList> meaning of the condition. me, Note
<cond> Condition_descrip Values are to be populated according to the mapping defined for
<descr> tion, element <condTypeList><condType><descr> above
Maintenance_level except for instances of Condition_by_identifier.
_type,
Instances of the element <condList><cond> which defines instances
Maintenance_locat
of Condition_by_identifier must populate the element
ion,
<descr> with the respective Condition_description).
Operating_locatio
n_type, Note
Operating_locatio Condition_description is not included in the current version
n, of DEX3AD.
Breakdown_element
, Part, User,
Customer, Contract
and
Product_usage_pha
se
<condCrossRefTable> Reference additional N/A
<condList><cond><refs> material with the
condition.
<condCrossRefTable> The incorporation status N/A

<incorporation> of technical conditions in
the documentation

Chap 5
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
6 Common information repository

The possible population of data modules following the CIR Schema will be investigated in a
future issue of S1003X.

S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Chapter 6
S3000L data required to populate S1000D data modules

1 S3000L data required to populate S1000D data modules .............................................. 3
1.1 Summary of data from S3000L required by S1000D ...................................................... 3
1.2 Business rules ................................................................................................................. 4
2 Units of functionality ........................................................................................................ 4
2.1 S3000L UoF Project ........................................................................................................ 4
2.1.1 Contract ........................................................................................................................... 5
2.1.2 Customer ......................................................................................................................... 6
2.1.3 User ................................................................................................................................. 6
2.1.4 Product_variant................................................................................................................ 7
2.1.5 Block_of_serialized_items ............................................................................................... 8
2.2 UoF Product Usage ......................................................................................................... 9
2.2.1 Maintenance_level_type .................................................................................................. 9
2.2.2 Maintenance_location .................................................................................................... 10
2.2.3 Operating_location ........................................................................................................ 11
2.2.4 Operating_location_type ................................................................................................ 11
2.3 UoF Breakdown Structure ............................................................................................. 12
2.3.1 Breakdown ..................................................................................................................... 13
2.3.2 Breakdown_element_usage_in_breakdown ................................................................. 13
2.3.3 Breakdown_element ...................................................................................................... 14
2.3.4 Breakdown_element_relationship ................................................................................. 15
2.4 UoF Part ........................................................................................................................ 15
2.4.1 Hardware_part ............................................................................................................... 17
2.4.2 Hardware_part_operational_authorized_life ................................................................. 18
2.4.3 Software_part ................................................................................................................ 18
2.5 UoF Breakdown Element Realization ............................................................................ 20
2.5.1 Hardware_element (see section on UoF Breakdown Structure) ................................... 21
2.5.2 Hardware_element_revision .......................................................................................... 22
2.5.3 Hardware_element_realization ...................................................................................... 22
2.5.4 Software_element_realization ....................................................................................... 22
2.6 UoF Breakdown Zone Element ..................................................................................... 22
2.6.1 Zone_element ................................................................................................................ 23
2.6.2 Hardware_element_in_zone_relationship ..................................................................... 24
2.7 UoF Product Variant Applicability .................................................................................. 24
2.7.1 Product_variant_applicability ......................................................................................... 24
2.7.2 Product_variant_realization_applicability ...................................................................... 24
2.7.3 Product_variant_realization ........................................................................................... 25
2.8 UoF LSA-FMEA and Special Events ............................................................................. 26
2.8.1 Special_event ................................................................................................................ 28
2.8.2 LSA_failure_mode ......................................................................................................... 28
2.8.3 Product_usage_phase ................................................................................................... 28
2.9 UoF LSA Candidate Task Requirement ........................................................................ 29
2.9.1 Authority_driven_task_requirement ............................................................................... 30
2.10 UoF Task ....................................................................................................................... 30
2.10.1 Task ............................................................................................................................... 33
2.10.2 Task_change ................................................................................................................. 34
2.10.3 Warning_caution_or_note ............................................................................................. 34
2.10.4 Subtask .......................................................................................................................... 35
2.10.5 Subtask_timeline ........................................................................................................... 36

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.10.6 Subtask_by_definition ................................................................................................... 36

2.10.7 Subtask_in_zone ........................................................................................................... 37
2.10.8 Subtask_target_item ...................................................................................................... 37
2.10.9 Subtask_objective_state ................................................................................................ 37
2.10.10 Subtask_circuit_breaker_state ...................................................................................... 38
2.10.11 Circuit_breaker .............................................................................................................. 38
2.11 UoF Task Resources ..................................................................................................... 40
2.11.1 Task_material_resource ................................................................................................ 42
2.11.2 Resource_specification ................................................................................................. 42
2.11.3 Task_personnel_resource ............................................................................................. 43
2.11.4 Trade ............................................................................................................................. 43
2.11.5 Skill ................................................................................................................................ 44
2.11.6 Skill_level ....................................................................................................................... 44
2.12 UoF Task Usage (Part 1) ............................................................................................... 45
2.12.1 Planned_task_usage ..................................................................................................... 47
2.12.2 Sampling_by_ratio ......................................................................................................... 47
2.12.3 Task_limit....................................................................................................................... 47
2.12.4 Discrete_task_limit......................................................................................................... 47
2.12.5 Periodic_task_limit ......................................................................................................... 47
2.12.6 Initial_task_limit ............................................................................................................. 47
2.12.7 Repeat_task_limit .......................................................................................................... 47
2.12.8 Subsequent_repeat_relationship ................................................................................... 48
2.12.9 Parameter_threshold ..................................................................................................... 48
2.12.10 Event_threshold ............................................................................................................. 49
2.12.11 Task_related_threshold ................................................................................................. 50
2.13 UoF Security Classification ............................................................................................ 50
2.13.1 Security_class................................................................................................................ 51
2.14 UoF Document............................................................................................................... 51
2.14.1 S1000D_pulication_module ........................................................................................... 54
2.14.2 External_document ........................................................................................................ 54
2.14.3 Document_assignment .................................................................................................. 55
2.15 UoF Remark .................................................................................................................. 55
2.15.1 Remark .......................................................................................................................... 56
2.16 UoF Applicability Statement .......................................................................................... 57
2.16.1 Applicability_statement .................................................................................................. 59
2.16.2 Logical_operator subclasses AND and OR, respectively .............................................. 59
2.16.3 Condition_by_identifier .................................................................................................. 59
2.16.4 Condition_type ............................................................................................................... 60
2.16.5 Condition_type_class_value .......................................................................................... 60
2.16.6 Condition_type_property_value ..................................................................................... 60
List of tables
1 References ...................................................................................................................... 3
List of figures
1 S3000L UoF Project ........................................................................................................ 5
2 S3000L UoF Product Usage............................................................................................ 9
3 S3000L UoF Breakdown Structure ................................................................................ 13
4 S3000L UoF Part ........................................................................................................... 16
5 S3000L UoF Breakdown Element Realization .............................................................. 21
6 S3000L UoF Breakdown Zone Element ........................................................................ 23

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
7 S3000L UoF Product Variant Applicability .................................................................... 25

8 S3000L UoF LSA-FMEA and Special Events ............................................................... 27
9 S3000L UoF LSA Candidate Task Requirement........................................................... 30
10 S3000L UoF Task .......................................................................................................... 32
11 S3000L UoF Task Resources ....................................................................................... 41
12 S3000L UoF Task Usage (Part 1) ................................................................................. 46
13 S3000L UoF Security Classification .............................................................................. 51
14 S3000L UoF Document ................................................................................................. 53
15 S3000L UoF Remark ..................................................................................................... 56
16 S3000L UoF Applicability Statement ............................................................................. 58
References
Table 1 References

S2000M International specification for material management
Analysis - LSA
1 S3000L data required to populate S1000D data modules

1.1 Summary of data from S3000L required by S1000D
This chapter summarizes data elements in S3000Lwhich can be used to populate the elements
in the S1000D maintenance procedure, maintenance planning information, applicability cross-
reference table and conditions cross-reference table, data modules. This summary is defined
from an S3000L perspective, and ordered by the S3000L unit of functionalities.
Note
− S1000D maintenance procedure Schema is referred to as PROCED in the defined
usages for the respective S3000L class and attribute below
− S1000D maintenance planning information Schema is referred to as SCHEDUL in the
defined usages for the respective S3000L class and attribute below
− S1000D applicability cross-reference table is referred to as APPLICCROSSREFTABLE
in the defined usages for the respective S3000L class and attribute below
− S1000D conditions cross-reference table is referred to as CONDCROSSREFTABLE in
the defined usages for the respective S3000L class and attribute below
Each S3000L Unit of Functionality (UoF) contains a short description of the UoF and the data
model as defined in S3000L. Classes and attributes which can be used to populate (or derive a
value which can populate) at least one element in any of the S1000D schemas within scope for
S1003X are highlighted with blue boxes and lines, respectively. However, other classes and
attributes may also be of interest, eg for navigational purposes.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
1.2 Business rules

Business rules required for a seamless integration between S3000L and S1000D are discussed
per S3000L UoF. These business rules also serve as the rules for tailoring the DEX1AD and
DEX3AD.
2 Units of functionality
2.1 S3000L UoF Project
The first data elements defined during Logistics Support Analysis (LSA) are those required for
defining the project (often referred to as the LSA program) and the product in focus (often
referred to as the end item).
A project can be related to one or many contracts, where contracts can be organized into a
chain of associated contracts, eg subcontracts.
Each contract is associated with at least one customer and one contractor. Each contract
includes one or many contracted product variants, where a contracted product variant relates to
a specific variant of a generic product.
A contracted product variant may also include information on the quantity of contracted product
variant and/or the serial number range, as known by the customer.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN-B6865-S1003X0019-002-01
Fig 1 S3000L UoF Project
Data elements required by the S1000D procedural, maintenance planning and/or applicability
schemas are:
2.1.1 Contract
Contract can be used to derive:
− Any instance of the attribute <applic><assert@applicPropertyIdent> in
the PROCED and SCHEDUL schemas, including the identification and status section
− Any instance of the attribute <applic><assert@applicPropertyType> in the
PROCED and SCHEDUL schemas, including the identification and status section
− CONDCROSSREFTABLE

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− CONDCROSSREFTABLE <condCrossRefTable><condTypeList>
<condType><name>
<condType><descr>
− CONDCROSSREFTABLE <condCrossRefTable><condList>
<cond@condTypeRefId>
− CONDCROSSREFTABLE <condCrossRefTable><condList><cond@id>
− CONDCROSSREFTABLE <condCrossRefTable><condList><cond><name>
<condCrossRefTable><condList><cond><descr>
Contract_identifier can be used to populate:

− Any instance of the attribute <applic><assert@applicPropertyValues> in
<condCrossRefTable><condTypeList><condType>
2.1.2 Customer
Customer can be used to derive:
<condCrossRefTable><condTypeList><cond@id>
<condType><name>
<condType><descr>
Organization_name (inherited from Organization) can be used to populate:

2.1.3 User
User can be used to derive:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00

<condType><name>
<condType><descr>
Organization_name (inherited from Organization) can be used to populate:

2.1.4 Product_variant
Product_variant can be used to derive:
− APPLICCROSSREFTABLE
<applicCrossRefTable><productAttributeList>
<productAttribute@id>
<productAttribute><name>
<productAttribute><displayName>
Product_variant_identifier can be used to populate:

− <dmIdent><dmCode@modelIdentCode>
<productAttribute><enumeration@applicPropertyValues>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.1.5 Block_of_serialized_items
Block_of_serialized_items can be used to derive:
Serial_number_lower_bound (Block_of_serialized_items) can be

used to populate:

Serial_number_upper_bound (Block_of_serialized_items) can be

used to populate:

Use of Product variant identification (Product_variant_identifier) must include

'Model_identification_code'.
Business rule decision point - Choice of organization identifier:
− Determine which Organization_identifier to use for populating the

corresponding S1000D elements if organizations have multiple
Organization_identifiers and Organization_names.
Business rule decision point - Use of Products within Products:
− Decide how to use of Products within Products, and how to apply model identification codes
for Products within Products.
Business rule decision point - Strategy for defining system difference:
− Define a strategy for defining system difference (use of

Product_variant_applicability,
Breakdown_element_identifiers or
Breakdown_element_relationships).
Business rule decision point - Use of block serialized items:
− Decide how to use of Block_of_serialized_items at different product levels for

nested products.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.2 UoF Product Usage

The UoF Product Usage defines the conditions under which the contracted product variant is to
be operated and maintained. This includes, for example, maintenance levels and operating
locations.
ICN-B6865-S1003X0020-002-01
Fig 2 S3000L UoF Product Usage
Schemas are:
2.2.1 Maintenance_level_type
Maintenance_level_type can be used to derive:
<condType><name>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
<condType><descr>
Maintenance_level_type_name can be used to populate:

− SCHEDUL
<maintAllocation><maintAllocationGroup><maintQualifier>
<maintLevelGroup><maintLevel@maintLevelCode>
− SCHEDUL <maintAllocation><maintAllocationGroup>
<componentAssyGroup> <maintQualifier><maintLevelGroup>
<maintLevel@maintLevelCode>
− SCHEDUL <maintAllocation><maintPlanning><toolsList>
<toolsListGroup> <maintLevel@maintLevelCode>
2.2.2 Maintenance_location
Maintenance_location can be used to derive:
<condType><name>
<condType><descr>
Maintenance_location_name can be used to populate:


Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.2.3 Operating_location
Operating_location can be used to derive:
<condType><name>
<condType><descr>
Operating_location_type_name can be used to populate:

2.2.4 Operating_location_type
Operating_location_type can be used to derive:
− Any instance of the attribute <applic><assert@applicPropertyIdent> in the
<condType><name>
<condType><descr>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Operating_location_name can be used to populate:

Business rule decision point - Use of maintenance level types:
− Decide on the use of maintenance level types, maintenance locations, operating location
types and operating locations.
2.3 UoF Breakdown Structure

The UoF Breakdown Structure can be used to define one or many types of breakdowns for a
specific Product. A breakdown can be eg functional, physical, system, zonal, or hybrid ie being
a mixture of these.
Each breakdown can have one or many breakdown revisions (design iterations), where each
breakdown revision references the breakdown element revisions that are included in the
specific revision of the breakdown. These references are done using the
Breakdown_element_usage_in_breakdown class. These references to the
breakdown element (revisions) are then organized hierarchically using the
Breakdown_element_structure class.
Using this construct, a defined breakdown element (revision) can be part of many breakdowns
and revisions thereof. A breakdown element (revision) can then be positioned differently in the
respective breakdown and revision thereof. Eg one and the same breakdown element (revision)
can be used in both a functional and physical breakdown.
However, each instance of Breakdown_element_usage_in_breakdown and

Breakdown_element_structure are unique for a specific breakdown revision, and
can therefore only be used once.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN-B6865-S1003X0021-002-01
Fig 3 S3000L UoF Breakdown Structure
Schemas are:
2.3.1 Breakdown
Breakdown_type can be used to derive:
− <dmStatus><systemBreakdownCode> in the identification and status section
− <dmStatus><functionalItemRef> in the identification and status section
− SCHEDUL
<maintAllocation><maintAllocationGroup><groupNumber>
2.3.2 Breakdown_element_usage_in_breakdown
Breakdown_element_usage_in_breakdown is used with the
Breakdown_element_structure and can be used to derive:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.3.3 Breakdown_element
Breakdown_element (Hardware_element/Software_element/
Aggregated_element/Zone_element)can be used to derive:
− SCHEDUL <taskDefinition><equipGroup><equp>
<condType><name>
<condType><descr>
Breakdown_element_identifier can be used to either derive or populate:

− <dmIdent><dmCode@systemDiffCode> in the identification and status section
− <dmIdent><dmCode@systemCode> in the identification and status section
− <dmIdent><dmCode@subSystemCode> in the identification and status section
− <dmIdent><dmCode@subSubSystemCode> in the identification and status
section
− <dmIdent><dmCode@assyCode> in the identification and status section
− <dmIdent><dmCode@disassyCode> in the identification and status section
− <dmIdent><dmCode@disassyCodeVariant> in the identification and status
section
− <dmStatus><functionalItemRef@functionalItemNumber> in the
identification and status section
− PROCED <preliminaryRqmts><productionMaintData>
<accessPointRef@ accessPointNumber>
− SCHEDUL <maintAllocation><maintAllocationGroup@id>
− SCHEDUL
Breakdown_element_name can be used to either derive or populate:

− <dmTitle><techName> in the identification and status section

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− <functionalItemRef><name> in the identification and status section

<accessPointRef><name>
− SCHEDUL <taskDefinition><name>
<componentAssy><name>
2.3.4 Breakdown_element_relationship
Breakdown_element_relationship_type can be used to derive:
− <dmIdent><dmCode@systemDiffCode> in the identification and status section
section
− PROCED
<preliminaryRqmts><productionMaintData><accessPointRef>
− SCHEDUL
Business rule decision point - Strategy for the product breakdown:
− Define the strategy for the product breakdown and identification of its breakdown elements
and possible realizations thereof, ie parts. This is required in order to populate (or derive)
the values of the elements <dmCode>, <systemBreakdownCode>, and
<functionalItemRef>, as well as the different types of breakdown element names
using the elements <techName> and <functionalItemRef><name>. This also
includes the use of the S3000L attribute Breakdown_type.
Business rule decision point - Strategy for relating multiple Breakdowns:
− Define the strategy for relating multiple Breakdowns (if required), eg relating a functional
Breakdown with a physical Breakdown, a design Breakdown with an S1000D Breakdown.
Business rule decision point - Defining access panels:
− Define the strategy for defining access panels.

Business rule decision point - Choice of identifier name:
− Determine which identifier and name, respectively, to use for populating the corresponding
S1000D elements if breakdown elements have multiple
Breakdown_element_identifiers and Breakdown_element_names.
2.4 UoF Part

The UoF Part is used to represent hardware items as well as software.
Part is an abstract class, ie an instance of a Part needs to be either a Hardware_part or a

Software_part.
Parts can be used to realize breakdown elements in a breakdown of a product, as well as play
the role of a resource in one or many tasks.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Parts can be organized into Bill-of-Materials (BOM), ie parts can consist of other parts.
Materials (often hazardous) are defined separately, and are then associated with the Parts in
which it is being used.
ICN-B6865-S1003X0022-002-01
Fig 4 S3000L UoF Part
schemas are:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.4.1 Hardware_part
Hardware_part can be used to derive:
− Any instance of the attribute <applic><assert@applicPropertyIdent in the
<condType><name>
<condType><descr>
Part_identifier (inherited from Part) can be used to either derive or populate:

section
section
− <dmStatus><functionalItemRef@manufacturerCodeValue> in the
− PROCED <preliminaryRqmts><reqSupportEquips>
<supportEquipDescrGroup>
<supportEquipDescr><identNumber><manufacturerCode>
<supportEquipDescrGroup> <supportEquipDescr><identNumber>
<partAndSerialNumber><partNumber>
− PROCED <preliminaryRqmts><reqSupplies><supplyDescrGroup>
<supplyDescr><identNumber><manufacturerCode>
<supplyDescr><identNumber>
− PROCED <preliminaryRqmts><reqSpares><spareDescrGroup>
<spareDescr><identNumber><manufacturerCode>
<spareDescr><identNumber><partAndSerialNumber><partNumber>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL <taskDefinition><equipGroup><equip><identNumber>
<manufacturerCode>
− SCHEDUL <taskDefinition><equipGroup><equip><identNumber>
− SCEHDUL <timeLimitInfo><equipGroup><equip><identNumber>
<manufacturerCode>
− SCEHDUL <timeLimitInfo><equipGroup><equip><identNumber>
Part_name (inherited from Part) can be used to populate:

<supportEquipDescrGroup> <supportEquipDescr><name>
<supplyDescr><name>
<spareDescr><name>
− SCHEDUL <taskDefinition><equipGroup><equip><name>
− SCEHDUL <timeLimitInfo><equipGroup><equip><name>
− SCHEDUL
<maintPlanning><maintAllocationGroup><componentAssyGroup>
<componentAssy><name>
− SCHEDUL (maintPlanning)
<maintPlanning><toolsList><toolsListGroup><name>
2.4.2 Hardware_part_operational_authorized_life
Hardware_part_operational_authorized_life can be used to either derive
or populate:
− SCHEDUL <timeLimitInfo>
− SCHEDUL <timeLimitInfo><timeLimit><limitType>
<threshold@thresholdUnitOfMeasure>
− SCHEDUL
<timeLimitInfo><timeLimit><limitType@limitUnitType>
− SCHEDUL <timeLimitInfo><timeLimit><limitType>
<threshold><thresholdValue>
− SCHEDUL <timeLimitInfo><timeLimit><limitType><threshold>
− SCHEDUL <timeLimitInfo><timeLimit><limitType><threshold>
<tolerance@toleranceHigh>
2.4.3 Software_part
Software_part can be used to derive:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00

<condType><name>
<condType><descr>
Part_identifier (inherited from Part) can be used to either derive or populate:

section
section
Part_name (inherited from Part) can be used to populate:

Business rule decision point - Product breakdown and identification of its Breakdown
elements:
− Define the strategy for the product breakdown and identification of its Breakdown elements
and possible realizations thereof, ie parts. This is required in order to enable the population
of the different types of breakdown element identifiers defined in S1000D, ie <dmCode>,
<systemBreakdownCode> and <functionalItemCode>, as well as the
different types of breakdown element names <techName>
and<functionalItemRef><name>. This also includes the use of the S3000L
attribute Breakdown_type.
Business rule decision point - Choice of identifier name:
− Determine which identifier and name, respectively, to use for populating the corresponding
S1000D elements if parts have multiple Part_identifiers and Part_names.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Business rule decision point - Populating limit type:
− Determine how to populate <timeLimitInfo><timeLimit><limitType>

using Hardware_part_operational_authorized_life.
2.5 UoF Breakdown Element Realization

The UoF Breakdown Element Realization is used to:
− Define hardware and software breakdown elements along with their realizations in terms of
hardware and software parts, respectively.
− Distinguish hardware and software breakdown elements from other types of breakdown
elements such as systems, zones, etc.
Note
The Hardware_element and Software_element classes are both
specializations of the class Breakdown_element which means that, wherever the
class Breakdown_element is being used in the data model,
Hardware_element or Software_element can be used instead.
Note
The Hardware_element_revision and Software_element_revision
classes are both specializations of the class Breakdown_element_revision
which means that, wherever the class Breakdown_element_revision is being
used in the data model, Hardware_element_revision or
Software_element_revision can be used instead.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN-B6865-S1003X0023-002-01
Fig 5 S3000L UoF Breakdown Element Realization
schemas are:
2.5.1 Hardware_element (see section on UoF Breakdown Structure)

Hardware_element_type can be used to either derive or populate:
− PROCED

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− PROCED
<preliminaryRqmts><productionMaintData><accessPointRef@
accessPointTypeValue>
2.5.2 Hardware_element_revision
Functional_replaceability can be used to derive:
Repairability can be used to derive:
2.5.3 Hardware_element_realization
Hardware_element_realization can be used to derive:
− SCHEDUL <taskDefinition><equipGroup><equip>
2.5.4 Software_element_realization
Software_element_realization can be used to derive:
Business rule decision point - Values for hardware element type:
− Define valid values for Hardware_element_type.
2.6 UoF Breakdown Zone Element

The UoF Breakdown Zone Element is used to distinguish between zonal breakdown elements
and other types of breakdown elements (eg hardware, software).
Note:
Zone elements can be used to define eg defined zones within a product as well as generic
work areas, eg mechanical workshop.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN-B6865-S1003X0024-002-01
Fig 6 S3000L UoF Breakdown Zone Element
Schemas are:
2.6.1 Zone_element
Breakdown_element_identifier (inherited from Breakdown_element) can
be used to populate:
<zoneRef@zoneNumber>
Breakdown_element_name (inherited from Breakdown_element) can be used to

populate:
− PROCED
<preliminaryRqmts><productionMaintData><zoneRef><name>
− PROCED <preliminaryRqmts><productionMaintData><workArea>
Zone_element_type can be used to derive:

− PROCED <preliminaryRqmts><productionMaintData><zoneRef>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.6.2 Hardware_element_in_zone_relationship
Hardware_element_in_zone_relationship can be used to derive:
Business rule decision point - defining zones and work areas:
− Define the strategy for defining zones and work areas.
2.7 UoF Product Variant Applicability

The UoF Product Variant Applicability enables the definition of product models which are
available or delivered to the customer in different configurations or variations. A variation or
configuration of a product is defined by applying restrictions to the generic product breakdown
and its breakdown elements realizations, respectively.
Note
Product data standards, eg ISO 10303 often use the term effectivity to describe product
design related restrictions, where the restriction defines the planned usage of components
in the context of a particular product configuration.
The Product Variant Applicability UoF enables specification of valid use of:
− Breakdown elements in the context of a Breakdown_revision.

− Parts in the context of a particular Product_variant_realization (also often
referred to as a Product configuration).
This UoF defines two types of product design related applicabilities:
2.7.1 Product_variant_applicability
The Product_variant_applicability:
− Constrains the usage of a Breakdown_element_revision within a

Breakdown_revision to a specific Product_variant (also known in GEIA-
STD-0007 as Usable On Code).
− Constrains the zonal location (Zone_element_revision) for a
Hardware_element_revision to a specific Product_variant.
2.7.2 Product_variant_realization_applicability
The Product_variant_realization_applicability:
− Constrains a Hardware_element_realization, Software_element_

realization and/or Parts_list_entry to a specific realization of a
Breakdown_revision.
Note
Information regarding Product_variant_applicabilities, and
Product_variant_realization_applicabilities, are often received
from the design department as part of the product definition. This information often
originates from of some kind of PDM-system.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0026-002-01
Fig 7 S3000L UoF Product Variant Applicability
schemas are:
2.7.3 Product_variant_realization
Product_variant_realization can be used to derive:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Product_variant_realization_identifier can be used to populate:

the PROCED and SCHEDUL schemas, including the identification and status section .
Business rule decision point - Defining system difference:
− Define the strategy for defining system difference (use of

Product_variant_applicability,
Breakdown_element_identifiers or
Breakdown_element_relationships).
2.8 UoF LSA-FMEA and Special Events

The UoF LSA-FMEA and Special Events supports the recording of portions of the results from
the following LSA activities:
− LSA - FMEA (Failure Mode and Effect Analysis)

− Damage analysis
− Special event analysis
− Testability analysis.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0027-002-01
Fig 8 S3000L UoF LSA-FMEA and Special Events

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Schemas are:
2.8.1 Special_event
Special_event_title can be used to populate:
− SCHEDUL <taskDefinition><limit@limitCond>
− SCHEDUL <taskDefinition><limit><trigger>
− SCHEDUL
<inspectionDefinition><inspection><limit@limitCond>
− SCHEDUL <inspectionDefinition><inspection><limit><trigger>
2.8.2 LSA_failure_mode
LSA_failure_mode_description can be used to populate:
− SCHEDUL
2.8.3 Product_usage_phase
Product_usage_phase can be used to derive or populate:
the PROCED and SCHEDUL schemas, including the identification and status section.
− Any instance of the attribute
<dmStatus><applic><assert@applicPropertyType> in the PROCED
and SCHEDUL schemas, including the identification and status section
− Any instance of the attribute
<dmStatus><applic><assert@applicPropertyValues> in the PROCED
and SCHEDUL schemas, including the identification and status section
<condType><name>
<condType><descr>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Business rule decision point - Values for the special event title:
− Define valid values for Special_event_title.
Business rule decision point - Values for the product usage phase:
− Define valid values for Product_usage_phase.
2.9 UoF LSA Candidate Task Requirement

The LSA Candidate Task Requirement UoF supports early recordings of task requirements,
which will be refined during the detailed maintenance task analysis, software and data loading
analysis, etc.
Objectives for documenting task requirements are eg to:
− Produce input to the LSA review, and together with the customer define maintenance
concepts for the respective LSA candidate, before any detailed task analysis is being
carried out.
− Identify product design changes that will result in increased maintainability, testability, etc.
A task requirement can also be associated with the source for the requirement, ie the driver for
the task. The requirement for a task may be derived from any type of logistics support analysis
task.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0028-002-01
Fig 9 S3000L UoF LSA Candidate Task Requirement
Schemas are:
2.9.1 Authority_driven_task_requirement
Task_requirement_authority_source_type can be used to populate:
− SCHEDUL <taskDefinition><rqmtSource@sourceOfRqmt>
Business rule decision point -Use of authority driven task requirement:
− Define how to use of Authority_driven_task_requirement.
Business rule decision point - Values for task requirement authority source type:
− Define valid values for Task_requirement_authority_source_type.
2.10 UoF Task

The UoF Task supports a detailed definition of a task, both maintenance task and operational
task.
The Task procedure is described using a set of Subtasks. A Subtask can either be defined
within the Task under consideration, or be a Task in its own right which is referenced via
Subtask_by_reference.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Note
A Subtask that is being defined and described within a Task cannot be referenced by any
other Task.
There is also the possibility to define a time line (schedule) for the Subtasks contained within a
Task. This can be used for the purpose of optimizing resource requirements and/or be the basis
for creating job cards in eg a fleet management system.
Note
The Task UoF has been designed to support integration between S3000L and the S1000D
procedure and schedule schemes, respectively.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0029-002-01
Fig 10 S3000L UoF Task
Schemas are:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.10.1 Task
Task_identifier can be used to populate:
− <authoritInfoAndTp><techPubBase> in the identification and status section
− SCHEDUL <taskDefinition@taskIdent>
− SCHEDUL
<taskDefinition><limit><trigger><refs><externalPubRef>
<externalPubRefIdent><externalPubCode>
− SCHEDUL <inspectionDefinition><inspection@id>
− SCHEDUL
<inspectionDefinition><inspection><limit><trigger><refs>
<externalPubRef><externalPubRefIdent><externalPubCode>
− SCHEDUL
<inspectionDefinition><taskGroup><taskItem@taskName>
Task_revision_identifier can be used to populate:

− <authoritInfoAndTp><techPubBase> in the identification and status section
Task_revision_status can be used to populate:

− <techStandard><techPubBase> in the identification and status section
Task_name can be used to derive:

− <dmTitle><infoName> in the identification and status section
− PROCED
<preliminaryRqmts><reqCondGroup><reqCondNoRef><reqCond>
− PROCED <closeRqmts><reqCondGroup><reqCondNoRef><reqCond>
− PROCED <mainProcedure><proceduralStep><title>
− SCHEDUL <taskDefinition><task><taskTitle>
− SCHEDUL <taskDefinition><task><taskDescr>
− SCHEDUL <taskDefinition><limit>
<inspectionType@inspectionTypeCategory>
− SCHEDUL
<externalPubRefIdent><externalPubTitle>
− SCHEDUL <taskDefinition<limit><trigger>
− SCHEDUL <inspectionDefinition><inspection><limit>
− SCHEDUL
<externalPubRef><externalPubRefIdent><externalPubTitle>
− SCHEDUL
<inspectionDefinition><taskGroup><taskItem><task><taskTitl
e>
− SCHEDUL <inspectionDefinition><taskGroup><taskItem>
<task><taskDescr>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL
<maintFunction@function>
<maintQualifier><maintFunction@function>
Information_code can be used to derive or populate:

− <dmIdent><dmCode@infoCode> in the identification and status section
− <dmIdent><dmCode@infoCodeVariant> in the identification and status section
− SCHEDUL <taskDefinition@taskCode>
Task_duration can be used to calculate:

<taskDuration@startupDuration>
<taskDuration@procedureDuration>
<taskDuration@closeupDuration>
<taskDuration@unitOfMeasure>
Task_total_labour_time can be used to populate:

− SCHEDUL
<maintLevelGroup><maintLevel>
<componentAssyGroup><maintQualifier><maintLevelGroup>
<maintLevel>
S1000D_task_type can be used to derive or populate:

− PROCED or SCHEDUL (<taskDefinition>, <inspectionDefinition>,
<timeLimitInfo> and <maintAllocation>) scheme
− SCHEDUL <taskDefinition><limit>
2.10.2 Task_change
Task_change_description can be used to populate the elements:
− <dmStatus><reasonForUpdate> in the identification and status section
2.10.3 Warning_caution_or_note
Warning_caution_or_note can be used to derive or populate the elements:
− PROCED <preliminaryRqmts><reqSafety><noSafety>
− PROCED <preliminaryRqmts><reqSafety><safetyRqmts><warning>
<warningAndCautionPara>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− PROCED <preliminaryRqmts><reqSafety><safetyRqmts><caution>
− PROCED
<preliminaryRqmts><reqSafety><safetyRqmts><note><notePara>
− PROCED <mainProcedure><proceduralStep><warning>
− PROCED <mainProcedure><proceduralStep><caution>
− PROCED <mainProcedure><proceduralStep><note><notePara>
Warning_caution_or_note_type can be used to distinguish between the elements:

− Use of <warning>, <caution> or <note>
2.10.4 Subtask
Subtask_identifier can be used to populate:
− SCHEDUL <inspectionDefinition><taskGroup>
<taskItem@taskSequenceNumber>
Subtask_role can be used to derive the elements:

− PROCED
− PROCED <preliminaryRqmts><reqCondGroup><noCond>
− PROCED <closeRqmts><reqCondGroup><noCond>
− PROCED
− PROCED <preliminaryRqmts><reqCondGroup><reqCondPm><pmRef>
− PROCED <closeRqmts><reqCondGroup><reqCondPm><pmRef>
− PROCED
<preliminaryRqmts><reqCondGroup><reqCondExternalPub>
− PROCED <closeRqmts><reqCondGroup><reqCondExternalPub>
− PROCED
<preliminaryRqmts><reqCondGroup><reqCondCircuitBreaker>
<reqCond>
− PROCED
<closeRqmts><reqCondGroup><reqCondCircuitBreaker><reqCond>
− PROCED
<circuitBreakerDescrGroup><circuitBreakerDescrSubGroup>
− PROCED <closeRqmts><reqCondGroup><reqCondCircuitBreaker>
− PROCED <preliminaryRqmts><reqPersons>
− PROCED <preliminaryRqmts><reqSupplies>
− PROCED <preliminaryRqmts><reqSpares>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
<supportEquipDescrGroup> <supportEquipDescr><reqQuantity>
<supplyDescr><reqQuantity>
− PROCED
<preliminaryRqmts<reqSpares><spareDescrGroup><spareDescr>
<reqQuantity>
− PROCED <preliminaryRqmts><reqSafety>
− PROCED <mainProcedure>
− PROCED <mainProcedure@independentCheck>
− PROCED <mainProcedure><proceduralStep>
− SCHEDUL <taskDefinition@skillLevelCode>
− SCHEDUL <taskDefinition><refs>
− SCHEDUL
<maintLevel>
2.10.5 Subtask_timeline
Subtask_time_line_event and Subtask_timeline_lag can be used to
derive:
− PROCED
<reqQuantity>
2.10.6 Subtask_by_definition
Subtask_name can be used to either derive or populate:
− PROCED

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− PROCED
<reqCond>
− PROCED
<closeRqmts><reqCondGroup><reqCondCircuitBreaker><reqCond>
− PROCED <mainProcedure><proceduralStep><title>
Information_code can be used to derive:

− <dmIdent><dmCode@infoCodeVariant> in the identification and status section
− PROCED
Subtask_description can be used to populate:

− PROCED <mainProcedure><proceduralStep><para>
Subtask_duration can be used to derive:

<taskDuration@unitOfMeasure>
Maintenance_location_code can be used to populate:

− <dmIdent><dmCode@itemLocationCode> in the identification and status
section
2.10.7 Subtask_in_zone
Subtask_in_zone can be used to derive:
2.10.8 Subtask_target_item
Subtask_target_item can be used to derive:
− PROCED
2.10.9 Subtask_objective_state
Subtask_objective_state can be used to either derive or populate:
− PROCED

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− PROCED <mainProcedure><proceduralStep@independentCheck>
2.10.10 Subtask_circuit_breaker_state
Subtask_objective_state (inherited from Subtask_objective_state) can be used to
either derive or populate:
− PROCED
<circuitBreakerRef@circuitBreakerAction>
<circuitBreakerDescr><circuitBreakerRef@circuitBreakerAc
tion
<circuitBreakerRef@circuitBreakerAction>
2.10.11 Circuit_breaker
Circuit_breaker_identifier can be used to populate:
− PROCED
<circuitBreakerRef@circuitBreakerNumber>
Circuit_breaker_type can be used to populate:

− PROCED
<circuitBreakerDescr><circuitBreakerRef@circuitBreakerTy
pe>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
<circuitBreakerRef@circuitBreakerType>
− PROCED
<mainProcedure><proceduralStep><circuitBreakerDescrGroup>
<circuitBreakerDescrSubGroup><circuitBreakerDescr>
<circuitBreakerRef@circuitBreakerType>
Circuit_breaker_name can be used to populate:

− PROCED
<circuitBreakerDescr><name>
<circuitBreakerDescr><name>
− PROCED
<mainProcedure><proceduralStep><circuitBreakerDescrGroup>
<circuitBreakerDescrSubGroup>
<circuitBreakerDescr><circuitBreakerName>
All instances of Subtask, within a Task of type “Package” in S3000L, must be

Subtask_by_reference.
Business rule decision point - Rules for procedural and packaged tasks:
− Define rules for organizing “Procedural” and “Packaged” tasks.

Business rule decision point - Rules for task name:
− Define rules for Task_name, based on S1000D Information code names.
Business rule decision point - Use of S1000D information codes:
− Determine how to use of S1000D information codes to categorize S3000L Tasks and
Subtask_by_definition, and rules for letting more than one Task, being
associated with a specific instance of Breakdown_element or Part, having the same
Information_code.
Business rule decision point - Use of information codes:
− Define rules for letting more than one subtask within a Task having the same
Information_code.
Business rule decision point - Use of project specific information codes:
− Define rules defining project specific “Not given” information codes.

Business rule decision point - Mapping S1000D information codes to task codes:
− Decide on the mapping between S1000D information codes and SCHEDUL

<taskDefinition@taskCode>.
Business rule decision point - Rolling up different task durations:
− Define rules for summarizing (roll-up) the different types of S1000D task_Durations.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Business rule decision point - Populating no safety:
− Decide how, in the absence of Warning_caution_or_note (where

Warning_caution_or_note_type = 'Warning') associated with the Task itself
or with any of its subtasks populate PROCED
<preliminaryRqmts><reqSafety><noSafety>.
Business rule decision point - Checking subtasks:
− Define rules for indicating that a subtask must be checked, by use of either a dedicated
Task_personnel_resource (role = 'Quality_assurance'), or by
Subtask_objective_state ('Task_checked').
Business rule decision point - Mapping information codes:
− Decide on the mapping between S1000D information codes and

<mainenanceAllocation><maintFunction@function> values.
2.11 UoF Task Resources

The UoF Task Resources supports a detailed definition of resources needed, either per
subtask, or aggregated per task.
Task resources can be either:
− Material resources, eg spares, tools, consumables

− Facilities, eg hangars, power
− Personnel resources, eg defined skills
− Documents.
Material and facility resources can be defined both in terms of specifications, and in terms of
actual parts.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0030-002-01
Fig 11 S3000L UoF Task Resources
schemas are:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.11.1 Task_material_resource
Task_material_resource_quantity can be used to populate:
<supportEquipDescr><reqQuantity@unitOfMeasure>
<supplyDescr><reqQuantity@unitOfMeasure>
− PROCED
<reqQuantity>
− PROCED
<reqQuantity@unitOfMeasure>
Task_material_resource_category can be used to derive:

− PROCED <preliminaryRqmts><reqSupplies>
− PROCED <preliminaryRqmts><reqSpares>
2.11.2 Resource_specification
Resource_specification_identifier can be used to populate:
<supportEquipDescr><natoStockNumber><fullNatoStockNumber>
<supplyDescr><natoStockNumber><fullNatoStockNumber>
<spareDescr><natoStockNumber><fullNatoStockNumber>
− SCHEDUL
<taskDefinition><equipGroup><equip><natoStockNumber>
− SCEHDUL <timeLimitInfo><equipGroup><equip><natoStockNumber>
<toolsListGroup> <natoStockNumber><fullNatoStockNumber>
<toolsListGroup> <toolRef@toolNumber>
Resource_specification_name can be used to populate:

<supportEquipDescrGroup> <supportEquipDescr><name>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
<supplyDescr><name>
<spareDescr><name>
2.11.3 Task_personnel_resource
Task_personnel_resource_role can be used to either derive or populate:
− PROCED <preliminaryRqmts><reqPersons><personnel>
− PROCED <preliminaryRqmts><reqPersons><person>
− PROCED <preliminaryRqmts><reqPersons><person@man>
− PROCED <mainProcedure@independentCheck>
− PROCED <mainProcedure@skillLevelCode>
− PROCED <mainProcedure><proceduralStep@independentCheck>
− SCHEDUL <taskDefinition><supervisorLevel>
<taskItem@skillLevelCode>
Task_number_of_personnel_resource can be used to populate:

− PROCED
<preliminaryRqmts><reqPersons><personnel@numRequired>
Task_personnel_resource_labour_time can be used to populate or calculate:

− PROCED
<preliminaryRqmts><reqPersons><personnel><estimatedTime>
− PROCED <preliminaryRqmts><reqPersons><personnel>
<estimatedTime@unitOfMeasure>
− PROCED <preliminaryRqmts><reqPersons><person><estimatedTime>
− PROCED <preliminaryRqmts><reqPersons><person>
<estimatedTime@unitOfMeasure>
− SCHEDUL
<maintLevel>
2.11.4 Trade
Trade_name can be used to populate:
<personnel><personCategory@personCategoryCode>
<person><personCategory@personCategoryCode>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL <taskDefinition@skillType>
− SCHEDUL
<taskDefinition><supervisorLevel@supervisorLevelCode>
2.11.5 Skill
Skill_code can be used to populate:
− PROCED <preliminaryRqmts><reqPersons><personnel><trade>
− PROCED <preliminaryRqmts><reqPersons><person><trade>
− SCHEDUL
<taskDefinition><supervisorLevel@supervisorLevelCode>
2.11.6 Skill_level
Skill_level_name can be used to populate:
<personnel><personSkill@skillLevelCode>
<person><personSkill@skillLevellCode>
− PROCED <mainProcedure@skillLevelCode>
− PROCED <mainProcedure><proceduralStep@skillLevelCode>
− SCHEDUL <taskDefinition@skillLevelCode>
<taskItem@skillLevelCode>
Business rule decision point - Values for task material resource category:
− Define valid values for Task_material_resource_category.
Business rule decision point - Populating no support equipment:
− Define rules for how the absence of Task_material_resources populates

PROCED <preliminaryRqmts><noSupportEquips>.
Business rule decision point Use of task personnel resource role:
− Decide on the use of Task_personnel_resource_role, and valid values.
Business rule decision point - Checking subtasks:
− Decide on rules for indicating that a subtask must be checked, by use of either a dedicated
Task_personnel_resource (role = 'Quality_assurance'), or by
Subtask_objective_state ('Task_checked').
Business rule decision point - Values for skill codes:
− Define valid values for Skill_code.
Business rule decision point - Values for trade names:
− Define valid values for Trade_name.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Business rule decision point - Values for skill level codes:
− Define valid values for Skill_level.
2.12 UoF Task Usage (Part 1)

The UoF Task Usage (Part 1) supports detailed definitions for:
− Identifying the breakdown element or part on which an operational or rectifying task is to be

performed.
− What initiates an operational or rectifying task to be performed on a breakdown element or
a part (task limits).
− Where the operational or rectifying task is to be performed.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0031-002-01
Fig 12 S3000L UoF Task Usage (Part 1)

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
schemas are:
2.12.1 Planned_task_usage
Planned_task_usage can be used to derive:
− SCHEDUL <taskDefinition><equipGroup><equip>
2.12.2 Sampling_by_ratio
Sampling_method_ratio can be used to populate:
− SCHEDUL <taskDefinition><limit><sampling>
− SCHEDUL <inspectionDefinition><inspection><limit><sampling>
2.12.3 Task_limit
Task_limit_description can be used to populate:
− SCHEDUL <inspectionDefinition><inspection><limit@limitCond>
2.12.4 Discrete_task_limit
Discrete_task_limit can be used to derive:
− SCHEDUL <taskDefinition><limit@limitTypeValue>
− SCHEDUL <taskDefinition><limit><trigger@releaseEvent>
− SCHEDUL
<inspectionDefinition><inspection><limit@limitTypeValue>
<trigger@releaseEvent>
2.12.5 Periodic_task_limit
Periodic_task_limit can be used to derive:
− SCHEDUL
2.12.6 Initial_task_limit
Initial_task_limit can be used to derive:
2.12.7 Repeat_task_limit
Repeat_task_limit can be used to derive:
− SCHEDUL <taskDefinition><limit><limitRange>
− SCHEDUL

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL
<inspectionDefinition><inspection><limit><limitRange>
2.12.8 Subsequent_repeat_relationship
Subsequent_repeat_relationship can be used to derive:
− SCHEDUL <taskDefinition><limit><limitRange>
− SCHEDUL
2.12.9 Parameter_threshold
Parameter_threshold can be used to derive:
Threshold_value can be used to populate:

− SCHEDUL
<taskDefinition><limit><threshold@thresholdUnitOfMeasure>
− SCHEDUL <taskDefinition><limit><threshold><thresholdValue>
− SCHEDUL <taskDefinition><limit><threshold>
− SCHEDUL <taskDefinition><limit><threshold>
− SCHEDUL <taskDefinition><limit><limitRange><limitRangeFrom>
− SCHEDUL <taskDefinition><limit><limitRange><limitRangeFrom>
<threshold> <thresholdValue>
− SCHEDUL <taskDefinition><limit><limitRange><limitRangeTo>
− SCHEDUL <taskDefinition><limit><limitRange><limitRangeTo>
− SCHEDUL <taskDefinition><limit><trigger><threshold>
<thresholdValue>
<threshold><thresholdValue>

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL
<inspectionDefinition><inspection><limit><threshold>
− SCHEDUL
<inspectionDefinition><inspection><limit><threshold>
− SCHEDUL
<limitRangeFrom><threshold@thresholdUnitOfMeasure>
− SCHEDUL
<limitRangeFrom><threshold><thresholdValue>
− SCHEDUL
<limitRangeTo> <threshold@thresholdUnitOfMeasure>
− SCHEDUL
<limitRangeTo> <threshold><thresholdValue>
<threshold> <tolerance@toleranceLow>
<threshold> <tolerance@toleranceHigh>
2.12.10 Event_threshold
Event_threshold_number_of_event_occurrences can be used to derive or
populate:
<thresholdValue>
− SCHEDUL
− SCHEDUL

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.12.11 Task_related_threshold
Task_related_threshold can be used to derive:
− SCHEDUL
− SCHEDUL
<externalPubRef>
Business rule decision point:
− Define valid unit of measures for Parameter_threshold attribute

Threshold_value.
Business rule decision point - Use of tasks, failure modes and special events:
− Decide on the use of Tasks, LSA failure modes and Special events as thresholds and
triggers.
Business rule decision point - Use of the ‘Whichever comes first’ value:
− Decide on the use of 'Whichever comes first' value for all threshold and triggers.
Business rule decision point - Definition for sampling:
− Define all sampling using percentage.
2.13 UoF Security Classification

The UoF Security Classification supports the assignment of security classes to objects that
needs special handling with respect to, availability, distribution, presentation etc.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0032-001-01
Fig 13 S3000L UoF Security Classification
Schemas are:
2.13.1 Security_class
Security_class can be used to either derive or directly populate:
− <dmStatus><security@securityClassification> in the identification
and status section
− PROCED <mainProcedure@securityClassification>
− PROCED
<mainProcedure><proceduralStep@securityClassification>
Business rule decision point - Applying security classifications:
− Define rules for applying Security_class per Breakdown_element, Part,

Task_requirement, Task or Subtask_by_definition, and how these can
be propagated into the different
<mainProcedure@securityClassification> attributes.
2.14 UoF Document

The UoF Document supports a flexible way of assigning documents to different types of objects
in the data model.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Note
There are some previously proposed (even mandatory) associations with the Document
class in the data model. This UoF adds the ability to define any type of additional Document
information which is of relevance for an instance of the classes that implements the
Document_assignment_interface. An example of additional Document
information can be 'Design_document' for a Part. This is not explicit in the data model
but can be added using this UoF, by defining the Document_assignment_role of
class Document_assignment as 'Design_document'.
Note
The S3000L data model defines two specializations of Document:
− S1000D data modules, which just contains information for being able to identify a
specific instance of a data module
− S1000D publication modules, which just contains information for being able to identify
a specific publication module instance
− External documents, which contains more metadata about the document itself.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0033-002-01
Fig 14 S3000L UoF Document
Schemas are:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.14.1 S1000D_pulication_module
Publication_module_code can be used to populate:
<pmRefIdent><pmCode>
<pmRefIdent><pmCode>
− SCHEDUL <taskDefinition><refs><pmRef><pmRefIdent><pmCode>
Publication_module_issue_number can be used to populate:

<pmRefIdent><issueInfo@issueNumber>
<pmRefIdent><issueInfo@issueNumber>
− SCHEDUL <taskDefinition><refs><pmRef><pmRefIdent>
<IssueInfo@issueNumber>
Publication_module_title can be used to populate:

− PROCED
<preliminaryRqmts><reqCondGroup><reqCondPm><reqCond>
− PROCED <closeRqmts><reqCondGroup><reqCondPm><reqCond>
2.14.2 External_document
Document_identifier can be used to populate:
− PROCED
− SCHEDUL <taskDefinition><rqmtSource@sourceIdent>
− SCHEDUL <taskDefinition><refs><externalPubRef>
<externalPubRefIdent> <externalPubCode>
Document_title can be used to populate:

− PROCED

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
<externalPubRefIdent> <externalPubTitle>
Document_issue_identifier can be used to populate:

− PROCED
<externalPubRef><externalPubRefIdent>
<externalPubIssueInfo> <externalPubIssue>
<externalPubRef><externalPubRefIdent>
<externalPubIssueInfo> <externalPubIssue>
− SCHEDUL
<taskDefinition><rqmtSource><issueInfo@issueNumber>
<externalPubRefIdent>
<externalPubIssueInfo><externalPubIssue>
Document_issue_date can be used to populate:

− SCHEDUL <taskDefinition><rqmtSource><issueDate@year>
− SCHEDUL <taskDefinition><rqmtSource><issueDate@month>
− SCHEDUL <taskDefinition><rqmtSource><issueDate@day>
2.14.3 Document_assignment
Document_assignment_role can be used to derive:
− PROCED <preliminaryRqmts><reqCondGroup><reqCondPm>
− PROCED <closeRqmts><reqCondGroup><reqCondPm>
− PROCED
Business rule decision point - Values for document assignment roles:
− Define permitted values for Document_assignment_role, and how to use these

across the ASD specifications.
2.15 UoF Remark

The UoF Remark supports a flexible way of assigning remarks to instances of almost any class
in the data model.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN- B6865-S1003X0034-002-01
Fig 15 S3000L UoF Remark
Schemas are:
2.15.1 Remark
Remark_text can be used to populate:

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
− SCHEDUL <taskDefinition><limit><remarks><simplePara>
− SCHEDUL <taskDefinition><remarks><simplePara>
<remarks><simplePara>
− SCHEDUL
<inspectionDefinition><inspection><remarks><simplePara>
− SCHEDUL <timeLimitInfo><timeLimit><remarks><simplePara>
Business rule decision point - Use of remarks:
− Decide how to use remarks.
2.16 UoF Applicability Statement

The Condition_type class defines types of conditions to be used in applicability
statements, where the specific type of condition to be used cannot be derived from any other
class being defined within the S3000L data model.
Note
Examples on condition types that cannot be derived from the use of any other class in the
S3000L data model, and therefore needs to be defined as instances of
Condition_type, are:
− Service_bulletin
− Operational_environment
− Operational_scenario
− Operational_state
Note
An example of a class in the data model which can be used to define a condition is the
Customer class. The values that can be used in a condition are the instances of that class,
ie the values already exist in the LSA database.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
ICN-B6865-S1003X0035-002-01
Fig 16 S3000L UoF Applicability Statement

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
schemas are:
2.16.1 Applicability_statement
Applicability_statement_identifier can be used to populate:
− <referenceApplicGroup><applic@id> in the identification and status section
− Any instance of the attribute <XXX@applicRefId> in the PROCED and SCHEDUL
schemas, including the identification and status section.
Applicability_statement_description can be used to populate:
− Any instance of <applic><displayText><simplePara> in the PROCED and
SCHEDUL schemas, including the identification and status section.
2.16.2 Logical_operator subclasses AND and OR, respectively

Logical_operator subclasses AND and OR can be used to derive:
− Any instance of <applic><evaluate@andOr> in the PROCED and SCHEDUL
schemas, including the identification and status section.
2.16.3 Condition_by_identifier
Condition_by_identifier can be used to derive:
<condType><name>
<condType><descr>
Condition_identifier can be used to populate:

− Any instance of the attribute <applic><assert@applicPropertyIdent> in the
CONDCROSSREFTABLE <condCrossRefTable><condList><cond@id>
Condition_name can be used to populate:

Condition_description can be used to populate:


Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
2.16.4 Condition_type
Condition_type can be used to derive:
<condType><descr>
Condition_type_name can be used to populate:

<condType><name>
2.16.5 Condition_type_class_value
Condition_type_class_value can be used to populate:
2.16.6 Condition_type_property_value
Condition_type_property_value can be used to populate:
<enumeration@applicPropertyValues
Business rule decision point - Product attributes and conditions in applicability:
− Define permitted product attributes and conditions that can be used in applicability
statements.
Business rule decision point - task generality in applicability:
− Define task generality and usage of applicability for eg task, subtask, task resource and task
usage.

Chap 6
S1003X-B6865-01003-00 S 1003X-B6865-01003-00
Business rule decision point Use of condition types and condition type values:
− Define Condition_types and Condition_type_values.

S1003X-B6865-01003-00
Chapter 7
S1000D feedback to S3000L

S1000D feedback to S3000L ......................................................................................................... 1
References ..................................................................................................................................... 1
1 S1000D feedback to S3000L........................................................................................... 1
List of tables
1 References ...................................................................................................................... 1
References
Table 1 References

Analysis - LSA
1 S1000D feedback to S3000L

In producing the technical publications using S1000D a set of additional data is created, as well
as data coming from S3000L being refined. This can mean that eg tasks coming out of S3000L
can be either split into multiple data modules, or be a single data module. In order to document
the S3000L tasks in the resulting S1000D data modules the corresponding data modules must
have the <techPubBase> element populated with the S3000L task identifications, ie
task_identifier including identifier_set_by_organization,
task_revision_identifier, and optionally task_revision_status.
Therefore the key data to be exchanged from an S1000D CSDB back to the S3000L data base
is the cross references between the S1000D data modules codes and its corresponding S3000L
task identification. This includes the information being defined in the elements <dmCode>,
<language>, <issueNumber> and <techPubBase> within the
<identAndStatusSection>.

Chap 7
End of data module
S1003X-B6865-01003-00
Chapter 8
Use of DEX for S1000D and S3000L data exchange

Use of DEX for S1000D and S3000L data exchange .................................................................... 1
References ..................................................................................................................................... 1
1 Use of DEX for S1000D and S3000L data exchange ..................................................... 1
List of tables
1 References ...................................................................................................................... 1
List of figures
1 Tailoring of the aerospace and defense DEX using S1003X .......................................... 2
References
Table 1 References
Chap 6 S3000L data required to populate S1000D data modules

Analysis - LSA
1 Use of DEX for S1000D and S3000L data exchange

The aerospace and defense DEX1AD and DEX3AD provide a standard method for providing
product and task data defined by S3000L. The exchange of data between S3000L and S1000D
represents a subset of these DEX. S1003X provides a roadmap for tailoring these DEX. Fig 1
shows the use of the DEX and S1003X to exchange product and task data.

Chap 8
S1003X-B6865-01003-00
ICN-B6865-S1003X0036-001-01
Fig 1 Tailoring of the aerospace and defense DEX using S1003X
The tailoring details are defined in the Chap 6 S3000L data required to populate S1000D data
modules.

S1003X-B6865-01003-00
Chapter 9
Samples with S1000D and S3000L instantiations

1 Introduction ...................................................................................................................... 2
1.1 Purpose ........................................................................................................................... 2
2 Introduction ...................................................................................................................... 2
2.1 Key concepts ................................................................................................................... 2
2.2 S1000D Schedule Schemas and S3000L ....................................................................... 2
2.2.1 S1000D Schema.............................................................................................................. 2
2.2.2 S3000L model.................................................................................................................. 3
3 Examples with S1000D and S3000L instantiations ......................................................... 4
3.1 Simple case ..................................................................................................................... 4
3.1.1 Threshold equals, Repeat case. ...................................................................................... 5
3.1.2 Threshold does not equal, Repeat. ................................................................................. 5
3.2 One time only case .......................................................................................................... 5
3.3 Whichever comes first case............................................................................................. 5
3.4 Sampling, repeat and threshold case .............................................................................. 5
3.5 Subsequent, repeat (trigger) case ................................................................................... 5
3.6 Multiple trigger case ........................................................................................................ 5
3.7 Threshold after trigger using threshold case ................................................................... 5
3.8 Trigger and whichever comes first case .......................................................................... 5
Threshold after trigger using <refs> ................................................................................ 5
3.9 case ................................................................................................................................. 5
3.10 Subsequent repeat (limit range) case ............................................................................. 6
3.11 More than one threshold case ......................................................................................... 6
3.12 Complex cases ................................................................................................................ 6
3.12.1 Complex case, two groups case...................................................................................... 6
3.12.2 Complex case with notes ................................................................................................. 6
List of tables
1 References ...................................................................................................................... 2
2 Simple case - Threshold equals - Repeat ....................................................................... 7
3 Simple case - Threshold does not equal - Repeat .......................................................... 8
4 One time only................................................................................................................... 9
5 Whichever comes first ................................................................................................... 10
6 Sampling, repeat and threshold..................................................................................... 11
7 Subsequent - Repeat (trigger) ....................................................................................... 13
8 Multiple trigger ............................................................................................................... 14
9 Threshold after trigger using threshold .......................................................................... 15
10 Trigger and whichever comes first................................................................................. 16
11 Threshold after trigger using <refs> .............................................................................. 17
12 Subsequent repeat (limrange) ....................................................................................... 18
13 More than one threshold ................................................................................................ 20
14 Complex case - Two groups .......................................................................................... 21
15 Complex case with notes ............................................................................................... 23

Chap 9
S1003X-B6865-01003-00
List of figures
1 S1000D Limit schema ..................................................................................................... 3
2 S3000L Uof Task Usage (Part 1) .................................................................................... 4
References
Table 1 References

Analysis - LSA
1 Introduction
1.1 Purpose
The purpose of this chapter is to present threshold and inspection examples with the
corresponding S1000D and S3000L instantiation.
2 Introduction
The examples deal with limits and thresholds as defined in the schedule (maintenance
planning) Schema and its inspection definition, task definition and time limit branches, using the
elements <inspectionDefinition>, <taskDefinition> and
<timeLimitInfo>, respectively. identAndStatusSection
2.1 Key concepts

The key concepts addressed in these examples are:
− Limit
• Perform once
• Periodic
• On condition
− Threshold (with variations)
− Trigger (with variations)
− Sampling
− Whichever comes first
2.2 S1000D Schedule Schemas and S3000L
2.2.1 S1000D Schema
On the S1000D side of these examples are elements and attributes that are defined in the
inspection definition branch of the schedule Schema, and specifically the element <limit>.
Refer to Fig 1.

Chap 9
S1003X-B6865-01003-00
ICN-B6865-S1003X0037-001-01
Fig 1 S1000D element <limit>
2.2.2 S3000L model

On the S3000L side of these examples is the S3000L model abstract that represents the Unit of
Functionality (UoF) Task Usage (Part 1). Refer to Fig 2.

Chap 9
S1003X-B6865-01003-00
ICN-B6865-S1003X0038-001-01
Fig 2 S3000L Uof Task Usage (Part 1)
3 Examples with S1000D and S3000L instantiations

The examples given show the mapping between S1000D and S3000L covering the key
concepts described at Para 2.1.
3.1 Simple case

There are two types of simple case examples given.

Chap 9
S1003X-B6865-01003-00
3.1.1 Threshold equals, Repeat case

The threshold equals, repeat case is a limit that triggers a task to be performed at a threshold
that has a given value and the interval between the thresholds is equal (eg perform the task
every 1000 flight hours). Refer to Table 2.
3.1.2 Threshold does not equal, Repeat

The threshold does not equal, repeat case is a limit that triggers a task is be performed at
thresholds that have given values and the intervals between them are not equal (eg perform the
task at 5000 flight hours the first time and then every 1000 flight hours thereafter). Refer to
Table 3.
3.2 One time only case

The one time only case is a limit that triggers a task to be performed once when the threshold
occurs (eg perform the task once at 2000 flight hours). Refer to Table 4.
3.3 Whichever comes first case

The whichever comes first case is a limit that triggers a task to be performed at threshold "A" or
threshold "B", whichever occurs first and then repeated at the next occurrence of threshold "A"
or threshold "B", whichever occurs first (eg perform the task at 2000 flight hours or at the one
year point, whichever comes first and repeat the task every 2000 flight hours or at the one year
point whichever comes first). Refer to Table 5.
3.4 Sampling, repeat and threshold case

The sampling, repeat and threshold case is a limit that triggers a task to be performed on a
sample of the fleet at a given threshold and then repeated at regular thresholds on another
sample or all of the fleet. (eg perform the task on 50% of the fleet at 2000 flight hours and at the
next 2000 flight hours, perform the task on the remaining 50% and at the next 2000 flight hours,
perform the task on all the fleet). Refer to Table 6.
3.5 Subsequent, repeat (trigger) case

The subsequent, repeat (trigger) case is a limit that triggers a task to be performed at threshold
"A", then repeated at every occurrence of that threshold until a given limit is reached. The task
is then performed repeatedly at a threshold "B" (eg perform the task every 6000 miles until
30000 miles and then every 3000 miles thereafter). Refer to Table 7.
3.6 Multiple trigger case

The multiple trigger case is a limit that triggers a task to be performed after a given number of a
th
different task has been performed (perform the task at the 6 oil change). Refer to Table 8.
3.7 Threshold after trigger using threshold case

The threshold after trigger using threshold case is a limit that triggers a task to be performed at
a given threshold after a different task has been performed at its threshold (eg perform the task
500 miles after the brake check task that is performed every 3000 miles). Refer to Table 9.
3.8 Trigger and whichever comes first case

The trigger and whichever comes first case is a limit that triggers a task to be performed at
either a given threshold or after a given task (eg perform the task at 4000 flight hours or after
the engine has been changed, whichever comes first). Refer to Table 10.
3.9 Threshold after trigger using references case

The threshold after trigger using the element <refs> case is a limit that triggers a task to be
performed at a given threshold after a different referenced task has been performed (eg perform
the task at 6000 miles after the (refer to oil change) task). Refer to Table 11.

Chap 9
S1003X-B6865-01003-00
3.10 Subsequent repeat (limit range) case

The subsequent repeat (limit range) case is a limit that triggers a task to be performed at every
occurrence of threshold "A", until a given limit and then repeated at every occurrence of
threshold "B" (eg perform the task every 8000 flight hours until 48000 flight hours and then
repeat the same task every 4000 flight hours). Refer to Table 12.
3.11 More than one threshold case

The more than one threshold case is when a limit triggers a task to be performed at threshold
"A" and then the same task is performed at threshold "B", where both thresholds start from the
same point (eg perform the task at 8000 flight hours. Perform the task again at 48000 flight
hours (ie 40000 flight hours after the task is performed the first time)). Refer to Table 13.
3.12 Complex cases

There are two types of complex case examples given.
3.12.1 Complex case, two groups case

The complex case, two groups case is a limit that triggers a task to be performed after threshold
"A" or threshold "B", whichever comes first.
The task is then performed repeatedly at every occurrence of threshold "C" or threshold "D",
whichever come first until limit "1" or limit "2" is reached, whichever comes first.
The task is then performed repeatedly at every occurrence of threshold "E" or threshold "F",
whichever comes first.
For example:
− Perform the task at 6000 miles or at the six month point (whichever comes first).
− Repeat the same task at every 12000 miles or at every occurrence of the next one year
point (whichever comes first) until 50000 miles or the five year point (whichever comes first).
− Then repeat the same task every 6000 miles or every occurrence of the next six month
point (whichever comes first).
Refer to Table 14.
3.12.2 Complex case with notes

The complex case with notes is a limit that triggers a task to be performed at threshold "A" or
threshold "B" and at either threshold a note is applied. The same task is then performed
repeatedly at every occurrence of threshold "C" or every occurrence of threshold "D" or at the
vendor’s recommendation. Refer to Table 15.

Chap 9
S1003X-B6865-01003-00
Table 2 Simple case - Threshold equals - Repeat
0 1000 2000 3000 4000 Perform at 1000 flight hours and repeat every 1000 flight hours thereafter.
Threshold Repeat
1000 FH 1000 FH
S1000D mapping S3000L mapping
<limit limitTypeValue="PE"> An instance of Periodic_task_limit with no instance of

<threshold thresholdUnitOfMeasure="FH"> initial_threshold, a repeat association with an associated instance of
<thresholdValue>1000</thresholdValue> Repeat_task_limit which has a threshold where the
</threshold> Threshold_definition is an instance of Parameter_threshold with the
</limit> attribute Threshold_value set to the value = "1000" and Unit = "Flight_hour".

Chap 9
S1003X-B6865-01003-00
Table 3 Simple case - Threshold does not equal - Repeat
0 5000 10000 15000 20000 Perform at 5000 flight hours and repeat every 10000 flight hours thereafter.
Threshold Repeat
5000 FH 10000 FH
<limit limitTypeValue="PO"> An instance of Periodic_task_limit with an instance of

<threshold thresholdUnitOfMeasure="FH"> initial_threshold where the Threshold_definition is an instance of
<thresholdValue>5000</thresholdValue> Parameter_threshold with the attribute Threshold_value set to Value =
</threshold> "5000" and Unit = "Flight_hour" and a repeat association with an associated
</limit> instance of Repeat_task_limit which has a threshold where the
<limit limitTypeValue="PE"> Threshold_definition is an instance of Parameter_threshold with the
<threshold thresholdUnitOfMeasure="FH"> attribute Threshold_value set to the value = "10000" and Unit =
<thresholdValue>10000</thresholdValue> "Flight_hour".
</threshold>
</limit>

Chap 9
S1003X-B6865-01003-00
Table 4 One time only

0 2000 3000 4000 5000 Perform at 2000 flight hours.
Threshold Repeat
2000 FH N/A
<limit limitTypeValue="PO"> An instance of Discrete_task_limit with no instance of the trigger association and a
<threshold thresholdUnitOfMeasure="FH"> threshold where the Threshold_definition is an instance of
<thresholdValue>2000</thresholdValue> Parameter_threshold with the attribute Threshold_value set to the value =
</threshold> "2000" and Unit = "Flight_hour".
</limit>

Chap 9
S1003X-B6865-01003-00
Table 5 Whichever comes first

0 2000 3000 4000 5000 Repeat at every 2000 flight hours or 1 year, whichever comes first.
FH
0 1 2 3 4
YR
Version Threshold Repeat
1 2000 FH 2000 FH
1 1 YR 1 YR
<limit limitTypeValue="PE"> An instance of Periodic_task_limit with no instance of initial_threshold

<threshold thresholdUnitOfMeasure="FH"> and a repeat association with an associated instance of Repeat_task_limit which
<thresholdValue>2000</thresholdValue> has two instances of threshold, ie two associated instances of
</threshold> Threshold_definition where the first instance is an instance of
<threshold thresholdUnitOfMeasure="YR"> Parameter_threshold with the attribute Threshold_value set to the value =
<thresholdValue>1</thresholdValue> "2000" and Unit = "Flight_hour". The second instance is an instance of
</threshold>
Parameter_threshold with the attribute Threshold_value set to the value =
</limit>
"1" and Unit = "Year".

Chap 9
S1003X-B6865-01003-00
Table 6 Sampling, repeat and threshold

First check at 4000 FH on 20% on the fleet, then repeat at every 8000 flight cycles on
0 4k 8k 12k 16k 20k 24k 28k 32k 36k 20% of the fleet, until 20000 flight hours for all the fleet after which repeat every 4000
FH flight hours on the whole fleet.
20% 100%
Sampling Threshold Repeat

20% 4000 FH 8000 FH
All 20000 FH 4000 FH
<limit limitTypeValue="PO"> An instance of Periodic_task_limit with an associated instance of

<sampling>20</sampling> Sampling_by_ratio (which is a specialization of Sampling) with the attribute
<threshold thresholdUnitOfMeasure="FH"> Sampling_method_by_ratio set to the value = "20" and Unit = "Percentage"
<thresholdValue>4000</thresholdValue> and an initial_threshold where the Threshold_definition is an instance
</threshold> of Parameter_threshold with the attribute Threshold_value set to the value =
</limit> "4000" and Unit = "Flight_hour" and two instances of the repeat association, ie it has
<limit limitTypeValue="PE"> two associated instances of Repeat_task_limit where the first instance of
<sampling>20</sampling> Repeat_task_limit has a threshold which is an instance of
<threshold thresholdUnitOfMeasure="FH">
<thresholdValue>8000</thresholdValue>
"8000" and Unit = "Flight_hour". The second Repeat_task_limit has a
</threshold>
<limitRange> threshold which is an instance of Parameter_threshold with the attribute
<limitRangeFrom> Threshold_value set to the value = "4000" and Unit = "Flight_hour".
<threshold thresholdUnitOfMeasure="FH"> The two instances of Repeat_task_limit are associated with each other via an
<thresholdValue>4000</thresholdValue> instance of Subsequent_repeat_relationship with the preceding association is
</threshold> associated with the first instance of Repeat_task_limit and the succeeding

Chap 9
S1003X-B6865-01003-00
<limitRangeto> association is associated with the second instance of Repeat_task_limit and the
<threshold thresholdUnitOfMeasure="FH"> trigger association is associated with an instance of Parameter_threshold with the
<thresholdValue>20000</thresholdValue> attribute Threshold_value set to the value = "20000" and Unit = "Flight_hour".
</threshold>
</limit>
<limit limitTypeValue="PE">
</threshold>
<limitRange>
<limitRangeFrom>
</threshold>
</limitRangeFrom>
</limitRange>
</limit>

Chap 9
S1003X-B6865-01003-00
Table 7 Subsequent - Repeat (trigger)

Repeat at every 8000 flight cycles until 48000 flight cycles after which repeat every 4000
0 8k 16k 24k 32k 40k 48k 56k 64k 72k flight cycles.
1 8000 FH 8000 FH
2 48000 FH 4000FH

<threshold thresholdUnitOfMeasure="FC"> and two instances of the repeat association, ie it has two associated instances of
<thresholdValue>8000</thresholdValue></threshold> Repeat_task_limit where the first instance of Repeat_task_limit has a
<limitRange><limitRangeFrom> threshold which is an instance of Parameter_threshold with the attribute
<threshold thresholdUnitOfMeasure="FH"> Threshold_value set to the value = "8000" and Unit = "Flight_cycle". The
<thresholdValue>0</thresholdValue> second Repeat_task_limit has a threshold which is an instance of
<limitRangeto><threshold thresholdUnitOfMeasure="FH">
<thresholdValue>48000</thresholdValue></limit>
"4000" and Unit = "Flight_cycle". The two instances of Repeat_task_limit
are associated with each other via an instance of
<threshold thresholdUnitOfMeasure="FC">
<thresholdValue>4000</thresholdValue></threshold> Subsequent_repeat_relationship where the preceding association is
<trigger releaseEvent="After"> associated with the first instance of Repeat_task_limit. The succeeding association
<threshold thresholdUnitOfMeasure="FC"> is associated with the second instance of Repeat_task_limitand the trigger
<thresholdValue>48000</thresholdValue> association is associated with an instance of Parameter_threshold with the attribute
</threshold></trigger></limit> Threshold_value set to the value = "48000" and Unit = "Flight_cycle".

Chap 9
S1003X-B6865-01003-00
Table 8 Multiple trigger

Engine changes................................ Perform after 5 engine changes
Trigger Threshold Repeat
After 5 N/A N/A

engine
changes
<limit limitTypeValue="PO"> There are two alternative ways to represent this. The first is to make an implicit reference to
<trigger releaseEvent="After"> the "Engine change" Task which is an instance of Discrete_task_limit with no
<threshold instance of the trigger association and a threshold where the Threshold_definition
thresholdUnitOfMeasure="Engine Change"> is an instance of Parameter_threshold with the attribute Threshold_value set
<thresholdValue>5</thresholdValue> to the value = "5" and Unit = "Engine_change".
</threshold> 2. Explicit reference to the "Engine change" Task (preferred) with an instance of
</trigger> Discrete_task_limit with no instance of the trigger association and a threshold
</limit> where the Threshold_definition is an instance of
Task_related_threshold which is associated with the instance of Task that
describes the "Engine Change" and the attribute
Event_threshold_number_of_event_occurrences set to the value = "5"
(which is inherited from Event_threshold).

Chap 9
S1003X-B6865-01003-00
Note
If the example would have described "every fifth engine change" then use
Periodic_task_limit
Table 9 Threshold after trigger using threshold

Engine Change Perform 10 hours after engine changes
10 Hours
FC
After 10 Hrs N/A

engine
changes
<limit limitTypeValue="PO"> There are two alternative ways to represent this:

<threshold thresholdUnitOfMeasure="Hours"> 1. Implicit reference to the "Engine change" Task which is an instance of
<thresholdValue>10</thresholdValue> Discrete_task_limit with a trigger where the associated
<trigger releaseEvent="After"> Threshold_definition is an instance of Parameter_threshold with the
<refs><dmRef>...dmc of Engine Change..> attribute Threshold_value set to the value = "1" and Unit = "Engine_change" and
</trigger>
a threshold where the Threshold_definition is an instance of
</limit>
Parameter_threshold with the attribute
Threshold_value set to the value = "10" and Unit = "Hour".

Chap 9
S1003X-B6865-01003-00
2. Explicit reference to the "Engine change" Task (preferred) which is an instance of

Discrete_task_limit with a trigger where the associated
Threshold_definition is an instance of Task_related_threshold which
is associated with the instance of the Task that describes the "Engine Change". The attribute
Event_threshold_number_of_event_occurrences is set to the value = "1"
(which is inherited from Event_threshold) and a threshold where the
Threshold_definition is an instance of Parameter_threshold with the
attribute Threshold_value set to the value = "10" and Unit = "Hour".
Note
If the example would have described "every fifth engine change" then use
Periodic_task_limit.
Table 10 Trigger and whichever comes first

Perform after 40000 flight cycles or 1 engine change, whichever comes first.
0 8k 16k 24k 32k 40k 48k 56k 64k 72k

FC

in trigger
After 40.000 FC N/A
engine
changes

Chap 9
S1003X-B6865-01003-00
<limit limitTypeValue="PO"> There are two alternative ways to represent this:

<trigger releaseEvent="After"> 1. Implicit reference to the "Engine change" Task which is an instance of
<threshold thresholdUnitOfMeasure="FC"> Discrete_task_limit with no instance of the trigger association and two instances of
<thresholdValue>40000</thresholdValue> threshold association, ie it has two associated instances of Threshold_definition
</trigger> where the first instance of Threshold_definition is an instance of
<trigger releaseEvent="After">
<refs><dmRef>...dmc of Engine Change..>
</trigger> "1" and Unit = "Engine_change". The second instance of
</limit> Threshold_definition is an instance of Parameter_threshold with the
attribute Threshold_value set to the value = "40000" and Unit =
"Flight_cycle".
2. Explicit reference to the "Engine change" Task (preferred) which is an instance of
Discrete_task_limit with no instance of the trigger association and two instances of
threshold association, ie it has two associated instances of Threshold_definition
where the first instance of Threshold_definition is an instance of
Task_related_threshold which is associated with the instance of the Task that
describes the "Engine Change". The attribute
Event_threshold_number_of_event_occurrences is set to the value = "1"
(which is inherited from Event_threshold). The second instance of
Threshold_definition is an instance of Parameter_threshold with the
attribute Threshold_value set to the value = "40000" and Unit =
"Flight_cycle".
Table 11 Threshold after trigger using <refs>

Engine Change Perform 10 hours after engine change
10 Hours

Chap 9
S1003X-B6865-01003-00
After 10 Hrs N/A

engine
changes
<limit limitTypeValue="PO"> An instance of Discrete_task_limit with a trigger where the associated

<threshold thresholdUnitOfMeasure="Hours"> Threshold_definition is an instance of Task_related_threshold which
<thresholdValue>10</thresholdValue> is associated with the instance of the Task that describes "Engine Change" and the attribute
<trigger releaseEvent="After"> Event_threshold_number_of_event_occurrences set to the value = "1"
<refs>[engine change reference]</refs> (which is inherited from Event_threshold) and a threshold where the
</trigger> Threshold_definition is an instance of Parameter_threshold with the
</limit>
attribute Threshold_value is set to the value = "10" and Unit = "Hour".
Table 12 Subsequent repeat (limrange)

0 8k 16k 24k 32k 40k 48k 56k 64k 72k Repeat at every 8000 flight cycles until 48000 flight cycles after which repeat every 4000
FC flight cycles

Chap 9
S1003X-B6865-01003-00
1 8000 FC 8000 FC
2 48000 FC 4000 FC

<threshold thresholdUnitOfMeasure="FC"> and two instances of the repeat association, ie it has two associated instances of
<thresholdValue>8000</thresholdValue> Repeat_task_limit where the first instance of Repeat_task_limit has a
<limitRange> threshold which is an instance of Parameter_threshold with the attribute
<limitRangeFrom> Threshold_value set to the value = "8000" and Unit = "Flight_cycle". The
<threshold <thresholdUnitOfMeasure="FC"> second Repeat_task_limit has a threshold which is an instance of
<limitRangeto>
"4000" and Unit = "Flight_cycle". The two instances of Repeat_task_limit
<threshold <thresholdUnitOfMeasure="FC">
are associated with each other via an instance of
</limit> Subsequent_repeat_relationship with the preceding association is associated
<limit limitTypeValue="PE"> with the first instance of Repeat_task_limit and the succeeding association is
<threshold thresholdUnitOfMeasure="FC"> associated with the second instance of Repeat_task_limit The trigger association is
<thresholdValue>4000</thresholdValue></threshold> associated with an instance of Parameter_threshold with the attribute
<limitRange> Threshold_value set to the value = "48000" and Unit = "Flight_cycle".
<limitRangeFrom> Note
<threshold <thresholdUnitOfMeasure="FC">
The same representation as defined under the example on "Subsequent Repeat (trigger) "
<thresholdValue>48000</thresholdValue> above
</limit>

Chap 9
S1003X-B6865-01003-00
Table 13 More than one threshold

0 8k 16k 24k 32k 40k 48k 56k 64k 72k Perform at 8000 flight cycles. Perform again at 48000 flight cycles.
FC
Version Threshold -
1 8000 FC -
2 48000 FC -
<limit limitTypeValue="PO"> One instance of Discrete_task_limit with no instance of the trigger association and
<threshold thresholdUnitOfMeasure="FC"> a threshold where the Threshold_definition is an instance of
</threshold> "8000" and Unit = "Flight_cycles".
</limit>
<limit limitTypeValue="PO"> A second instance of Discrete_task_limit with no instance of the trigger
<threshold thresholdUnitOfMeasure="FC"> association and a threshold where the Threshold_definition is an instance of
</threshold> "48000" and Unit = "Flight_cycles".
</limit>
Note
The value "PO" of the attribute limitTypeValue of the element <limit> is always
“from the beginning”

Chap 9
S1003X-B6865-01003-00
Table 14 Complex case - Two groups

0 8k 16k 24k 32k 40k 48k 56k 64k 72k After 8000 flight cycles or 16000 flight hours (whichever comes first), repeat every 4000
FC flight cycles or 8000 flight hours (whichever comes first) until 48000 flight cycles or
96000 flight hours (whichever comes first), after which repeat every 8000 flight cycles
0 16k 32k 48k 64k 80k 96k 112k 128k 144k or 16000 flight hours (whichever comes first).

1 8000 FC 4000 FC
1 16000 FH 8000 FH
2 48000 FC 8000 FC
2 96000 FH 16000 FH
<limit limitTypeValue="PE"> An instance of Periodic_task_limit with two instances of

<threshold thresholdUnitOfMeasure="FC"> initial_threshold associations, ie two associated instances of
<thresholdValue>4000</thresholdValue> Threshold_definition where the first instance is an instance of
</threshold> Parameter_threshold with the attribute Threshold_value set to the value =
<threshold thresholdUnitOfMeasure="FH"> "8000" and Unit = "Flight_cycle".
</threshold> The second instance is an instance of Parameter_threshold with the attribute
<limitRange> Threshold_value set to the value = "16000" and Unit = "Flight_hour".
<limitRangeFrom> Two instances of the repeat association, ie the Periodic_task_limit has two
associated instances of Repeat_task_limit where the first instance of
</threshold>
Repeat_task_limit has two instances of the threshold association, ie it has two
associated instances of Threshold_definition where the first instance of

Chap 9
S1003X-B6865-01003-00
</limitRangeFrom> Threshold_definition is an instance of Parameter_threshold with the

<limitRangeto> attribute Threshold_value set to the value = "4000" and Unit = "Flight_cycle".
The second instance of Threshold_definition is an instance of
</threshold> Parameter_threshold with the attribute Threshold_value set to the value =
</limitRangeto> "8000" and Unit = "Flight_hour".
<limitRange> The second instance of Repeat_task_limit has two instances of the threshold
<limitRangeFrom> association, ie it has two associated instances of Threshold_definition where the
<threshold thresholdUnitOfMeasure="FH"> first instance of Threshold_definition is an instance of
Parameter_threshold withthe attribute Threshold_value set to the value =
</threshold>
"8000" and Unit = "Flight_cycle".
</limitRangeFrom>
<limitRangeto> The second instance of Threshold_definition is an instance of
<threshold thresholdUnitOfMeasure="FH"> Parameter_threshold with the attribute Threshold_value set to the value =
<thresholdValue>960000</thresholdValue> "16000" and Unit = "Flight_hour".
</threshold>
The two instances of Repeat_task_limit are associated with each other via an
</limitRangeto>
</limitRange> instance of Subsequent_repeat_relationship where the preceding association
</limit> is associated with the first instance of Repeat_task_limit. The succeeding
<limit limitTypeValue="PE"> association is associated with the second instance of Repeat_task_limit
<threshold thresholdUnitOfMeasure="FC"> There are two instances of the trigger association ie the
<thresholdValue>8000</thresholdValue> Subsequent_repeat_relationship has two associated instances of
</threshold> Threshold_definition where the first instance of Threshold_definition is
<threshold thresholdUnitOfMeasure="FH"> an instance of Parameter_threshold with the attribute Threshold_value set to
<thresholdValue>16000</thresholdValue> the value = "48000" and Unit = "Flight_cycle".
</threshold>
<limitRange> The second instance of Threshold_definition is an instance of
<limitRangeFrom> Parameter_threshold with the attribute Threshold_value set to the value =
<threshold thresholdUnitOfMeasure="FC"> "96000" and Unit = "Flight_hour".
</threshold>
</limitRangeFrom>

Chap 9
S1003X-B6865-01003-00
</limitRange>
<limitRange>
<limitRangeFrom>
</threshold>
</limit>
Note
Neither the element <limrange> nor the element <trigger> are repeatable elements
so cannot express two version groupings.
Table 15 Complex case with notes

First check at 8000 FC or 16000 FH and apply NOTE 1, then repeat at every 4000 flight
0 4k 8k 12k 16k 20k 24k 28k 32k 36k
FC cycles or 8000 flight hours or according to Vendor Recommendation.
AND NOTE 1 OR VR OR VR OR VR OR VR OR VR OR VR OR VR
0 8k 16k 24k 32k 40k 48k 56k 64k 72k
FH
Vers i o n T h res h o l d Rep ea t
1 8000 F C 4000 F C
1 16000FH 8000FH
1 ANDNOTE1 ORVR

Chap 9
S1003X-B6865-01003-00
<limit limitTypeValue="PO"> Note

<threshold thresholdUnitOfMeasure="FC"> There is currently no way to represent Threshold_definition as textual description
<thresholdValue>8000</thresholdValue> in S3000L.
</threshold>
</threshold>
</limit>
<limit limitTypeValue ="PO">
<remarks>
<simplePara>NOTE 1</simplePara>
</remarks>
</limit>
</threshold>
</threshold>
<remarks>
<simplePara>EG</simplePara>
</remarks>
</limit>

Chap 9
End of data module

S1000D To S3000L Interchange Specification: Issue 1.0 2011-03-31

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S1000D To S3000L Interchange Specification: Issue 1.0 2011-03-31

Uploaded by

Copyright:

Available Formats

S1000D to S3000L interchange

Issue 1.0 2011-03-31

Copyright and user agreement

2 Agreement for use of the specification S1003X™ suite of

− the S1000D and S3000L interchange specification - S1003X

2.2 Notice to user

2.3 License to use

2.4 Intellectual property rights

Applicable to: All S1003X-A-00-00-0000-00A-021A-A

DMC-S1003X-A-00-00-0000-00A-021A-A_001_00_EN-US.doc 2011-03-31 Page 1

2.7 Limitation of liability

2.9 Governing law and arbitration

Applicable to: All S1003X-A-00-00-0000-00A-021A-A

End of data module

Chapter Data module title Data module code Applic

Chap 1 Background S1000D-A-09-00-0000-00A-040A-A All

Applicable to: All S1003X-A-00-00-0000-00A-009A-A

End of data module

Table of contents Page

DEX1AD DEX1A&D - Aerospace and defense business DEX for

Applicable to: All S1003X-A-01-00-0000-00A-040A-A

− DEX1A&D - Aerospace and Defense business DEX for

− DEX3A&D - Aerospace and defense business DEX for exchange

Applicable to: All S1003X-A-01-00-0000-00A-040A-A

Table of contents Page

S1000D International specification for technical publications using

− S1000D data requirements:

Applicable to: All S1003X-A-02-00-0000-00A-040A-A

Applicable to: All S1003X-A-02-00-0000-00A-040A-A

End of data module Chap 2

Principles for product breakdown structures

Table of contents Page

S1000D International specification for technical publications using

1 Principles for product breakdown structures

Applicable to: All S1003X-A-03-00-0000-00A-040A-A

End of data module Chap 3

S1000D Procedure and schedule Schemas vs S3000L

Table of contents Page

S1000D International specification for technical publications using

1 S1000D Procedure and schedule Schemas vs S3000L

Applicable to: All S1003X-A-04-00-0000-00A-040A-A

1.1 S1000D vs S3000L views on a procedural task

Applicable to: All S1003X-A-04-00-0000-00A-040A-A

Subtask 01 Reference on: Fault location procedure

Subtask 02 Remove Cover #01 (opening 4 quick fasteners)

Subtask 03 Reference on: Remove Cover #02

Working Step 01 Open 24 screws for removal of Cover #02

Working Step 02 Remove cover plate

Working Step 03 Remove sealing

Subtask 04 Reference on: Remove equipment 401

Working Step 01 Remove electrical connector E01-013

Working Step 02 Open safety screws S01 and S02

Working Step 03 Open attaching screws A01 to A07

Working Step 04 Remove equipment 401 from housing

Subtask 05 Reference on: Disassemble equipment 401

Working Step 01 ……………

Subtask 06 Remove defective component 05

Subtask 07 Install new component 05

Subtask 08 Reference on: Assemble equipment 401

Subtask 09 Reference on: Install equipment 401

Subtask 10 Reference on: Test function of equipment 401

Subtask 11 Reference on: Install Cover #02

Subtask 12 Install Cover #01