Spec1000BR 4.1 2017.1 FINAL

ATA Spec 1000BR_4.
Civil Aviation Business

Rules for S1000D issue 4.1
1000BR Revision 2017.1
Use of this document is subject to the warranty provisions and license agreement contained on pages i, ii, and iii.
PRODUCT LICENSE AGREEMENT
AIR TRANSPORT ASSOCIATION OF AMERICA, INC. ("ATA") PRODUCT LICENSE

AGREEMENT
IMPORTANT -- PLEASE READ THIS ENTIRE AGREEMENT CAREFULLY
BEFORE USING THIS DOCUMENT
YOU AGREE TO BE BOUND BY THE TERMS OF, AND BECOME PARTY TO, THIS AGREEMENT. THIS
AGREEMENT IS APPLICABLE TO THE ACCOMPANYING MERCHANDISE (THE "MERCHANDISE"), THE
INFORMATION RESIDING THEREON OR ON INTERNET WEB SITES ACCESSIBLE EXCLUSIVELY VIA
LINKS FROM THE MERCHANDISE (THE "CONTENT") AND THE RELATED SOFTWARE
(COLLECTIVELY, THE "LICENSED PRODUCT"). IF YOU DO NOT AGREE TO BE BOUND BY THE TERMS
OF AND BECOME PARTY TO, THIS AGREEMENT, YOU CANNOT USE ANY PART OF THIS DOCUMENT
AND CANNOT SHARE IT WITH OR FORWARD IT TO ANY OTHER PERSON OR ENTITY.
IMPORTANT INFORMATION
The Licensed Product contains specifications, practices and other information relating to the covered topics. ATA
does not mandate the use of all or any part of the Licensed Product and your decision to use the Licensed Product
is entirely voluntary, your decision and at your own risk. You may choose to use the Content in whole, in part, or
not at all.
There may be practices, standards and/or governmental requirements applicable to your operations that exceed, or
vary from, the Licensed Product. You are solely responsible for determining if such practices, standards or regulatory
requirements exist and whether they apply to your activities, and for complying with those that are applicable. Such
practices, standards and regulatory requirements can change significantly over time. Unless ATA expressly states
otherwise in writing, nothing in this Agreement shall be interpreted as requiring ATA to provide you with updates,
revisions, or information about any development or action affecting the Licensed Product.
The Licensed Product has been compiled by ATA and/or its licensors. ATA and/or its licensors reserve title to and
ownership of the Licensed Product and all copyrights and any other intellectual property rights in it.
DESCRIPTION OF LICENSE
Upon your acceptance of this Agreement, you will be permitted to access the information for which you have
obtained the license described and limited below.
The extent of permissible access to the Licensed Product to you and within your company depends on the type of
Licensed Product that ATA has provided to you. Access is as follows:
1. If you purchased the Licensed Product for individual use ("single-user"), access to the Licensed Product shall be
limited to employees in your company, not to any third parties, and only one concurrent user.
2. If you purchased the Licensed Product for multiple person use ("multi-user") or you are a member of the ATA E-
Business Program, you can allow access to the Licensed Product to employees within your company, not to any
third parties, and have multiple concurrent users. Such employees shall be bound by all the provisions of this
Agreement.
3. Single user and multi-user employees may use the Licensed Product for the internal business purposes of your
company, and each may print a single copy of any Licensed Product for purposes of designing, structuring or
modifying any of your company's products or services as authorized below.
The license that this Agreement provides you is subject to any applicable payment and is non-exclusive, non-
transferable and worldwide. ATA can terminate this license if you materially fail to comply with the terms of this
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page i
Agreement.
This Agreement does not authorize you to, and you shall not:
1. Alter, modify, translate, adapt or create derivative works based on the Licensed Product or any related software.
Notwithstanding the foregoing prohibition, you may include or apply elements of the Licensed Product in a work
that you exclusively produce.
2. Use the Licensed Product on any unsecured network or permit any third party to access or use the Licensed
Product except as expressly permitted in this Agreement or in a separate agreement.
3. Use the Licensed Product or any part thereof in any manner that infringes the intellectual property or other rights
of another entity or person, including ATA.
4. Sublicense or assign this Agreement.
5. Indicate that ATA endorses, approves, or certifies your application of the Licensed Product, including, without
limiting the generality of the foregoing prohibition, your use of specifications contained in the Licensed Product.
ATA CREDIT
If the Licensed Product is used to design, structure or modify any of your or your company's products or services,
you must reference, in a commercially reasonable location, the fact that the Licensed Product has been so used.
LIMITED WARRANTY
ATA warrants that at the time of delivery, THE LICENSED PRODUCT will be free from defects in materials and
workmanship. In the event of a breach of the foregoing warranty, as your sole and exclusive remedy and ATA's sole
liability, ATA will replace any LICENSED PRODUCT having defects in materials or workmanship at no charge,
provided you inform ATA within 30 days after your receipt of the Product.
WARRANTY DISCLAIMER
EXCEPT AS EXPRESSLY STATED ABOVE, THE LICENSED PRODUCT IS PROVIDED "AS IS" AND ATA
HEREBY EXPRESSLY DISCLAIMS, ON BEHALF OF ITSELF AND ALL PERSONS WHO CONTRIBUTED
TO THE CREATION, PUBLICATION, REVISION AND/OR MAINTENANCE OF THE LICENSED PRODUCT,
ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT. NEITHER ATA NOR ANY PERSON WHO CONTRIBUTED TO THE CREATION,
PUBLICATION, REVISION OR MAINTENANCE OF THE LICENSED PRODUCT WARRANTS THAT THE
LICENSED PRODUCT WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE LICENSED
PRODUCT WILL BE ERROR FREE, OR THAT IT IS ACCURATE, COMPLETE, CURRENT OR RELIABLE.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page ii
LIMITATION OF LIABILITY
IN NO EVENT WILL ATA OR ANY PERSON WHO CONTRIBUTED TO THE CREATION, PUBLICATION,
REVISION, OR MAINTENANCE OF THE LICENSED PRODUCT BE LIABLE FOR INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR THE INABILITY TO USE,
THE LICENSED PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES; WITHOUT
LIMITING THE GENERALITY OF THE FOREGOING LIMITATIONS OF LIABILITY, NEITHER ATA NOR
ANY PERSON WHO CONTRIBUTED TO THE CREATION, PUBLICATION, REVISION, OR MAINTENANCE
OF THE LICENSED PRODUCT IS RESPONSIBLE FOR LOST PROFITS OR REVENUE, LOSS OF THE USE
OF THE LICENSED PRODUCT, LOSS OF DATA, OR THE COST OF ANY SUBSTITUTE PRODUCT. IN NO
CASE SHALL THE AGGREGATE LIABILITY OF ATA AND ALL PERSONS WHO CONTRIBUTED TO THE
CREATION, PUBLICATION, REVISION, OR MAINTENANCE OF THE LICENSED PRODUCT EXCEED
EITHER (1) THE AMOUNT OF THE ANNUAL E-BUSINESS PROGRAM MEMBERSHIP FEE YOU PAID FOR
THE YEAR IN WHICH SUCH LIABILITY AROSE, IF YOU ARE AN E-BUSINESS PROGRAM MEMBER, OR,
IF YOU ARE NOT SUCH A MEMBER, (2) THE PRICE YOU PAID TO PURCHASE THE LICENSED PRODUCT
FROM ATA. IN ADDITION, THE THIRD-PARTY PUBLISHER OF THE LICENSED PRODUCT WILL NOT BE
LIABLE FOR ANY DAMAGE OR LOSS OF ANY KIND ARISING OUT OF OR RESULTING FROM YOUR
POSSESSION OR USE OF THE LICENSED PRODUCT (INCLUDING DATA LOSS OR CORRUPTION),
REGARDLESS OF WHETHER SUCH LIABILITY IS BASED IN TORT, CONTRACT OR OTHERWISE.
This Agreement shall be governed in its interpretation and enforcement by the laws of the District of Columbia,
without regard to its choice of law principles.
This is the entire agreement between the parties about the subject matter of this Agreement. Any change to this
Agreement must be in writing and agreed to by both parties.
Comments about or suggested changes to the Licensed Product should be sent to:
ATA e-Business Department Air Transport Association of America, Inc. 1275 Pennsylvania Avenue, NW, Suite 1300
Washington, DC 20004-1707 USA
Or
admin@ataebiz.org
YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT AND AGREE TO
IT, AND THAT YOU HAVE THE AUTHORITY TO AGREE TO IT ON BEHALF OF YOUR COMPANY. IF
YOU DO NOT AGREE TO BE BOUND BY THE TERMS OF, AND BECOME PARTY TO THIS AGREEMENT,
YOU CANNOT USE ANY PART OF THIS DOCUMENT AND CANNOT SHARE IT WITH OR FORWARD IT
TO ANY OTHER PERSON OR ENTITY.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page iii
Table of Contents
Important Information About This Document ........................................................................... ix
Highlights .................................................................................................................................... x
Revision: 2017.1 ..................................................................................................................... x
Chapter 1. Introduction ............................................................................................................. 1
1-1. Background ..................................................................................................................... 1
1-2. Purpose............................................................................................................................ 1
1-3. Scope ............................................................................................................................... 1
1-4. S1000D version............................................................................................................... 2
1-5. S1000D Change Proposal Form (CPF) process .............................................................. 2
Chapter 2. General Civil Aviation Usage ................................................................................. 3
2-1. General Civil Aviation Business Rules........................................................................... 3
2-2. Civil Aviation Attribute Values .................................................................................... 70
2-3. Reserved for future use ................................................................................................. 71
2-4. General Civil Aviation Business Rules Exchange (BREX) ......................................... 72
Chapter 3. Component Maintenance Publication Usage ........................................................ 73
3-1. Component Maintenance Publication Business Rules .................................................. 73
3-2. Layout rules and examples - Component maintenance data modules ........................ 146
3-2-1. Introduction ......................................................................................................... 146
1. References ............................................................................................................... 146
2. Sections ................................................................................................................... 147
3. Topics ...................................................................................................................... 147
3-2-2. Rules and examples............................................................................................. 148
1. All data modules ..................................................................................................... 149
2. Descriptive data modules ........................................................................................ 184
3. Procedural data modules ......................................................................................... 184
4. Fault information data modules .............................................................................. 184
5. Topic specific rules and examples .......................................................................... 185
6. Functional and technical descriptions section......................................................... 257
7. Maintenance and servicing section ......................................................................... 257
8. Illustrated parts data section.................................................................................... 257
3-2-3. Packaging ............................................................................................................ 276
1. CMP Package .......................................................................................................... 276
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page iv
Appendix A. References ....................................................................................................... 277
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page v
List of Tables
Table 1 Revision Highlights ..............................................................................................................x
Table 2 General Civil Aviation Business Rules................................................................................. 3
Table 3 CMP Business Rules .......................................................................................................... 73
Table 4 S1000D References ........................................................................................................ 146
Table 5 Topic prefixes ................................................................................................................. 162
Table 6 References ...................................................................................................................... 277
List of Figures
Fig 1. (Sheet 1 of 3) Headers and footers ............................................................................. 151
Fig 2. (Sheet 1 of 6) Section, topic and data module separators ......................................... 155
Fig 3. (Sheet 1 of 11) Numbering.......................................................................................... 165
Fig 3. (Sheet 10 of 11) Numbering ....................................................................................... 174
Fig 3. (Sheet 11 of 11) Numbering ....................................................................................... 175
Fig 4. (Sheet 1 of 7) Applicability .......................................................................................... 177
Fig 5. (Sheet 1 of 6) Title information .................................................................................. 187
Fig 6. (Sheet 1 of 3) Configuration (CONF) ........................................................................... 195
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page vi
Fig 7. (Sheet 1 of 2) Copyright statements (COPY) ............................................................... 199
Fig 7. (Sheet 2 of 2) Copyright statements (COPY) ............................................................... 200
Fig 8. (Sheet 1 of 2) Administrative and legal statements (ADMIN) .................................... 202
Fig 8. (Sheet 2 of 2) Administrative and legal statements (ADMIN) .................................... 203
Fig 9. (Sheet 1 of 2) Safety statements (SAFE) ..................................................................... 205
Fig 9. (Sheet 2 of 2) Safety statements (SAFE) ..................................................................... 206
Fig 10. (Sheet 1 of 3) List of effective data modules (LOEDM) .............................................. 208
Fig 11. (Sheet 1 of 2) Change record (CR) .............................................................................. 212
Fig 11. (Sheet 2 of 2) Change record (CR) .............................................................................. 213
Fig 12. (Sheet 1 of 3) Highlights (HIGH) .................................................................................. 215
Fig 13. (Sheet 1 of 2) Lists of abbreviations (LOA) ................................................................. 219
Fig 13. (Sheet 2 of 2) Lists of abbreviations (LOA) ................................................................. 220
Fig 14. (Sheet 1 of 2) Lists of terms (LOT)............................................................................... 221
Fig 14. (Sheet 2 of 2) Lists of terms (LOT)............................................................................... 222
Fig 15. (Sheet 1 of 2) Lists of symbols (LOS) ........................................................................... 223
Fig 15. (Sheet 2 of 2) Lists of symbols (LOS) ........................................................................... 224
Fig 16. (Sheet 1 of 2) Technical standard record (TSR) .......................................................... 226
Fig 16. (Sheet 2 of 2) Technical standard record (TSR) .......................................................... 227
Fig 17. (Sheet 1 of 4) Table of contents (TOC)........................................................................ 229
Fig 18. (Sheet 1 of 3) List of Illustrations (LOI) ....................................................................... 234
Fig 19. (Sheet 1 of 2) List of tables (LOTBL) ............................................................................ 237
Fig 19. (Sheet 2 of 2) List of tables (LOTBL) ............................................................................ 238
Fig 20. (Sheet 1 of 3) List of applicable specifications and documentation (LOASD) ............ 240
Fig 21. (Sheet 1 of 2) List of suppliers (LOSUP) ...................................................................... 244
Fig 21. (Sheet 2 of 2) List of suppliers (LOSUP) ...................................................................... 245
Fig 22. (Sheet 1 of 3) Lists of support equipment (LOSE) ....................................................... 247
Fig 23. (Sheet 1 of 3) Lists of supplies (LOSU) ........................................................................ 250
Fig 24. (Sheet 1 of 3) List of spares (LOSP) ............................................................................. 254
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page vii
Fig 25. (Sheet 1 of 2) Numerical index (IPD) .......................................................................... 259
Fig 25. (Sheet 2 of 2) Numerical index (IPD) .......................................................................... 260
Fig 26. (Sheet 1 of 2) Equipment designator index (IPD) ....................................................... 262
Fig 26. (Sheet 2 of 2) Equipment designator index (IPD) ....................................................... 263
Fig 27. (Sheet 1 of 2) Illustration (IPD) ................................................................................... 271
Fig 27. (Sheet 2 of 2) Illustration (IPD) ................................................................................... 272
Fig 28. (Sheet 1 of 3) Detail parts list (IPD)............................................................................. 273
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page viii
Important Information About This Document
Read Before Using This Document
This document contains recommended specifications that have been developed for the covered
topics. ATA does not mandate their use. You must decide whether or not to use the
recommendations in this document. You may choose to use them in whole, in part, or not at
all.
There may be practices, standards and/or regulatory requirements applicable to your operations
that exceed the recommendations in this document. You are solely responsible for determining
if such practices, standards or requirements exist and whether they apply to your activities, and
for complying with those that are applicable. Such practices, standards and requirements can
change significantly over time.
ATA does not guarantee, promise or warrant that the specifications in this document will meet
the needs of your operations. This is a determination that you must make and for which ATA
is not responsible.
IMPORTANT NOTICE: This document is intended to be used only in an electronic

environment. ATA accepts no responsibility or liability for any material
printed from this document.
For Additional Information

For more information or to order additional publications, refer to the Airlines for America
(A4A) Publications website at https://publications.airlines.org/, e-mail pubs@airlines.org, or
call +1 202-626-4062.
For Technical Information and Change Submissions

Errata information for ATA Publications is available at the A4A Publications Web page.
For technical information or to recommend an alteration or amendment to this specification,
please submit the recommendation and any supporting documentation to ATA:
ATA Change Request (CR) Process and Forms:
https://www.ataebiz.org/specifications/Change_Requests/
E-mail: admin@ataebiz.org
Phone: +1 202-626-4062
Fax: +1 202-626-4081
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page ix
Highlights
Release History
• Revision 2017.1 – October 2017
• Revision 2015.1 – December 2015
• Revision 2009.2 – December 2009
• Revision 2009.1 – March 2009 – Original Issue
Revision: 2017.1
Table 1 Revision Highlights
Location in
Change Description
Specification
Section 2-1 Updated the General Civil Aviation Business Rules for S1000D issue 4.1.
Reorganized the content to use a tabular format.
Section 2-2 Moved from Appendix A.

Added new value "pc55, Moisture sensitive" to partCharacteristic.
Changed the definition of code pu72 in partUsageCode from "Manufacturer Part
Number" to "Original Part Number".
Added new value "psd86, Stringer" to significantParaDataType.
Section 2-4 Inserted a new section with a link to the General Civil Aviation BREX data
module.
Chapter 3 Introduced a new chapter for Component Maintenance Publication Usage
Section 3-1 Specified Component Maintenance Publication Business Rules for S1000D issue
4.1.
Section 3-2 Updated the Component Maintenance DM layout rules and examples, and moved
this section from Appendix B.
Appendix A Moved from Appendix C.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page x
Chapter 1. Introduction
1-1. Background
S1000D is an international specification for the procurement and production of technical
publications. Initially developed by the AeroSpace and Defence Industries Association of
Europe (ASD) [former European Association for Aerospace Industries (AECMA)], S1000D is
now administered jointly by ASD, Aerospace Industries Association (AIA), and Air Transport
Association of America (ATA).
S1000D was originally based on ATA Spec 100 and intended for use in the European defense
community, and has since expanded into a global specification, including support for civil air
transport industry requirements. After review of existing standards, the ATA e-Business
Steering Committee determined that next generation technical data standards for the civil
aviation industry should be developed in S1000D to provide a single global standard for both
civil and military applications.
1-2. Purpose
S1000D is designed to allow tailoring of the data for various products/projects through
development of project-specific business rules. In S1000D, Business Rule Decision Points
(BRDPs) are provided to denote specific implementation topics or questions which projects or
organizations must decide in the form of business rules.
In this context, the use of S1000D within the civil aviation industry constitutes a single project
for which a single set of business rules apply. If a business rule decision point is not answered
by the civil aviation business rules, it is available for individual projects to decide. The purpose
of this document is to provide the specific business rules required for implementation of
S1000D in the civil aviation industry.
ATA Spec 1000BR uses a layered approach. Business rules for general Civil Aviation usage
are defined in [Section 2-1]. Additional business rules for specific information types are also
defined. Civil Aviation business rules for Component Maintenance Publications are defined in
[Section 3-1]. Additional information-specific business rules may be added in future revisions
of this specification. These information-specific business rules must be fully compliant with
the general Civil Aviation business rules but may define further constraints to S1000D usage.
1-3. Scope
This document specifies the business rules for the exchange of required S1000D content
between parties in the Civil Aviation industry (e.g., OEMs, operators, MROs, etc.). It is not
intended to serve as a data provider’s authoring guideline.
Copyright 2017, Air Transport Association of America, Inc., d/b/a Airlines for America. All rights reserved. Page 1
1-4. S1000D version
This document is based on Issue 4.1 of S1000D. The decision to update data and systems to
support this and future issues of S1000D should be agreed between data providers and data
receivers. Sufficient notice should be provided to data receivers to allow them the time
necessary to prepare.
1-5. S1000D Change Proposal Form (CPF) process

The ATA Technical Data Working Group (TDWG) is the focal point for all S1000D change
proposals from the Civil Aviation community. Any interested party may request a change to
S1000D. To do so, an S1000D CPF must be submitted to ATA (https://specring.com/). The
CPF is used to summarize the proposed changes and provide justification.
Civil Aviation CPFs are referred to the TDWG for online review and comment. If there are
objections or comments needing resolution, then they will be discussed in an upcoming TDWG
meeting (including web/phone conferences). Upon consensus approval by the meeting
participants, a CPF will be submitted to the S1000D Steering Committee as a Civil Aviation
proposal for modification to S1000D.
If there are no objections or comments during the online review period, then a CPF will be
submitted directly to the S1000D Steering Committee with no further TDWG review required.
Contact admin@ataebiz.org for assistance.
Chapter 2. General Civil Aviation Usage
This chapter contains guidance for Civil Aviation implementation of S1000D. Specific rules for Civil Aviation usage of S1000D
are included where appropriate. Unless otherwise noted, it is recommended that Civil Aviation applications use the S1000D
specification as written.
2-1. General Civil Aviation Business Rules

This table lists the BRDPs as found in S1000D and provides the Civil Aviation business rules in the column titled, "General Civil
Aviation Usage". Where the Civil Aviation usage states "No Civil Aviation business rule", then it is left to the individual project
to make the decision. A checkmark in the column titled, "BREX Rule" indicates business rules which can be programmatically
enforced with the Civil Aviation Business Rules Exchange (BREX) data module.
Table 2 General Civil Aviation Business Rules

BRDP BREX
BRDP Title BRDP General Civil Aviation Usage
Number Rule
S1-00001 Use of "I" and "O" Decide whether and when to use the The use of alpha characters "I" and "O" in S1000D data shall
alpha characters "I" and "O". be compliant with ATA iSpec 2200, Specification 2000, and
the CSDD.
S1-00002 List of permitted CAGE codes Create a list of permitted CAGE codes No Civil Aviation business rule.
and/or names of the originator and/or names of the originator
companies to be companies.
used for the technical
publications
S1-00003 Issue of S1000D to be used Decide which issue or issues of S1000D No Civil Aviation business rule.
to be used.
S1-00004 Information sets to be used Decide which information sets, given in The following Information sets shall not be used:
S1000D and/or project specific, to be • Crew/Operator information
used. • Mass and balance information
• Weapon loading information
• Battle damage assessment and repair information
• Aircrew information
• Land/Sea specific information sets
S1-00005 Publications to be produced Decide which publications to be No Civil Aviation business rule.
produced.
S1-00006 Schemas to be used Decide which Schemas to be used and in Civil Aviation shall use the schemas and information sets per
which information set they are to be the following table. Additions to this list may be requested by
used. contacting admin@ataebiz.org and are subject to approval by
the ATA Technical Data Working Group.
BRDP BREX
Number Rule
Information Sets Schemas

Description and operation comrep - CIR applic
comrep - CIR
warning/caution
container
descript
Maintenance information - comrep - CIR applic
Maintenance Procedures comrep - CIR
warning/caution
container
descript
proced
Maintenance information - comrep - CIR applic
Fault isolation comrep CIR
warning/caution
container
descript
fault
proced
Maintenance information – comrep - CIR applic
Non destructive Testing comrep - CIR
warning/caution
container
descript
proced
Maintenance information – descript
Storage proced
Wiring data comrep - CIR applic
container
descript
proced
wrngdata
Illustrated parts data comrep - CIR applic
comrep - CIR part
descript
ipd
List of applicable descript
publications
BRDP BREX
Number Rule
Maintenance planning container
information descript
pm
schedule
Equipment information comrep
container
descript
fault
ipd
pm
proced
Illustrated tool and support descript
equipment information
Service bulletins container
descript
pm
proced
sb
Common information and descript
data cir
Training descript
Structure repair information proced
descript
comrep - CIR applic
comrep - CIR
warning/caution
Engine maintenance proced
information
Power plant build-up proced
Engine standard practices proced
descript
Note: The following schemas appliccrossreftable
can be used in addition to
those called out by the brex
information sets.
condcrossreftable
ddn
dml
prdcrossreftable
BRDP BREX
Number Rule
xcf
xlink
S1-00007 Use of optional elements and Decide whether and how to use each No Civil Aviation business rule.
attributes optional element and attribute in its
structural context.
S1-00008 Possible deliverables Decide on the possible deliverables, such No Civil Aviation business rule.
as:
S1000D objects (eg, data modules,

publication modules, illustration sheets
and multimedia objects, data
management lists) using file based
transfer.
Page-oriented publications and/or

interactive electronic technical
publications.
S1-00009 Frequency of data exchanges Decide on the frequency of data Revisions for new programs will be provided no less often than
exchanges. quarterly. Data once issued shall be kept current by revision
service throughout the service life of the equipment/items
covered. It is acceptable for mature programs to lengthen their
revision service where activity does not warrant quarterly
revisions.
S1-00010 Zone and access point Decide whether to use a zoning and Zoning rules must be used in civil aviation applications for the
identification system access identification system. uses described in paragraph 2.
S1-00011 Method for zoning and Decide which method to use for zoning Civil aviation applications must use the identification system
identifying access points and identifying access points. described in ATA iSpec 2200 chapter 3-1-3, paragraph 3.3,
Access Door Areas and Panel Identification.
S1-00012 Define security classification Decide which values to use for the Only 01 or the values in Spec 1000BR Appendix A shall be
values and terms (attribute attribute securityClassification and used.
securityClassification) allocate suitable definitions. Refer to ✓
Chap 3.9.6.1.
S1-00013 Use and markings of security Determine how the security No Civil Aviation business rule.
classifications (attribute classifications will be used.
securityClassification)
S1-00014 Application of caveats Determine if the policies that apply to No Civil Aviation business rule.
security marking, instructions, etc, and
how those markings are required to be
applied within the given project.
BRDP BREX
Number Rule
S1-00015 Retention of security Decide on the retention of security No Civil Aviation business rule.
classifications classifications.
S1-00016 Presentation of security Decide on how the security No Civil Aviation business rule.
classifications classifications will be marked and/or
indicated.
S1-00017 Rules for QA Decide on the rules for QA of data No Civil Aviation business rule. Refer to guidance in Chapter
modules and deliverables. 3.7 of S1000D.
S1-00018 Rules for first and second Decide on the rules for first and second If provided in a Data Module, second verifications will be
verification verification. For example, such a rule ignored. Refer to guidance in Chapter 3.7 of S1000D.
might be that all data modules that have
a safety related procedure must have first
verification carried out "On object".
S1-00019 Review cycle process Decide on the review cycle processes No Civil Aviation business rule.
and procedures.
S1-00020 Specify the language Decide which language to use for All data modules must be written in U.S. English.
producing data modules.
S1-00021 Use of ASD Simplified Technical Decide whether to use ASD-STE100® All Procedural data modules must use the writing rules and
English when producing data modules in English. vocabulary in ASD Simplified Technical English (ASD-
STE100). Use of STE is optional for other data module types.
S1-00022 Standard dictionary Decide which standard dictionary to use No Civil Aviation business rule.
for producing data modules.
S1-00023 Use of a terminology database Decide whether to use a terminology The ATA Common Support Data Dictionary shall be used for
or glossary database or a glossary. If used, agree on Civil Aviation maintenance terminology.
its content and management.
S1-00024 Use of a standard list of Decide whether to use a standard list of No Civil Aviation business rule.
abbreviations abbreviations. If used, agree on its
content and management.
S1-00025 Units of measurement Decide what unit of measurement to use Measurements shall be provided in both SI (metric) and
for primary and secondary units. Imperial/U.S. units. The first value shall be in the units used in
the original design.
S1-00026 Highlighting text Decide on which method to be used to Bold text only shall be used to emphasize text. Overline text
emphasize text. may be used only for marking vectors. ✓
S1-00027 Need of printable data Decide which parts of the documentation No Civil Aviation business rule.
(data modules and publications including
IETP) need to be printable.
S1-00028 Engineering numbers and Decide if schematics derived from No Civil Aviation business rule.
revision status within the engineering drawings include the original
illustration reproduction area drawing number and revision status
within the illustration reproduction area.
BRDP BREX
Number Rule
S1-00029 Use of color in the final Decide whether to use color in the final The use of color is permitted in accordance with the ATA
deliverable deliverable. iSpec 2200 3-1-12.4 Graphic Style Standards.
S1-00030 Use of general warnings, Decide whether to produce general Descriptive data modules using information code 012 shall
cautions and notes as separate warnings, cautions and notes in separate only be used for general warnings and cautions that are not
data modules descriptive data modules. specific to a particular procedure. Specific warnings and
cautions shall be provided in the data modules to which they
apply. Separate descriptive data modules shall not be used to
externalize notes.
S1-00031 Use of warning and/or caution Decide whether to use warning and/or Use of the Warnings and Cautions Common Information
collections caution collections, internal or external. Repositories (CIRs) is recommended.
S1-00032 Use of the attribute Decide whether and how to use the The attribute vitalWarningFlag must not be used in civil
vitalWarningFlag attribute vitalWarningFlag. aviation applications. ✓
S1-00033 Use of the attribute warningType Decide whether and how to use the The attribute warningType must not be used in civil aviation
attribute warningType. applications. ✓
S1-00034 Use of the attribute cautionType Decide whether and how to use the The attribute cautionType must not be used in civil aviation
attribute cautionType. applications. ✓
S1-00035 Use of the attribute noteType Decide whether and how to use the The attribute noteType must not be used in civil aviation
attribute noteType. applications. ✓
S1-00036 Presentation of the issue Decide whether to present the issue The issue number shall be presented on the title page. The
number and the inwork number number with or without the inwork inwork number may only be presented in unreleased
on the title page number on the title page. documents.
S1-00037 Use of LOEP or LOEDM Decide whether the use of LOEP or If a Data Module containing the LOEDM is provided, Info Code
LOEDM. 00S must be used. LOEP shall not be used. ✓
S1-00038 Presentation the of issue date or Decide whether to present the issue date Not applicable for Civil Aviation applications.
the issue number in the LOEP or the issue number (with or without
inwork number) for the LOEP entries.
S1-00039 Presentation of applicability Decide whether to present the Not applicable for Civil Aviation applications.
information in the LOEP applicability information for the LOEP
entries.
S1-00040 Presentation of the issue date or Decide whether to present the issue date Both issue date and issue number are required. Inwork
the issue number in the LOEDM or the issue number (with or without number shall not be presented.
inwork number) for the LOEDM entries.
S1-00041 Presentation of applicability Decide whether to present the No Civil Aviation business rule.
information in the LOEDM applicability information for the LOEDM
entries.
S1-00042 Use of Highlights with updating Decide whether to use Highlights with Highlights with updating instructions shall not be used.
instructions updating instructions or not.
S1-00043 Presentation of issue the date or Decide whether to present the issue date Not applicable for Civil Aviation applications.
the issue number in the or the issue number (with or without
Highlights inwork number) for the Highlights entries.
BRDP BREX
Number Rule
S1-00044 Presentation of applicability Decide whether to present the Not applicable for Civil Aviation applications.
information for the Highlights applicability information for the Highlights
entries.
S1-00045 Presentation of issue the date Decide whether to present the issue date Both issue date and issue number are required if no other
and the issue number in the and/or the issue number (with or without method for providing this information is used. Inwork number
TOC inwork number) that apply to the TOC shall not be presented.
entries.
S1-00046 Use of linear or hierarchically Decide whether to use a linear or a No Civil Aviation business rule.
subdivided TOC hierarchically subdivided TOC.
S1-00047 Country and language codes Decide on the country and language All Procedural data modules must use the languageIsoCode
codes to use, and apply them
consistently across the project.
(sx). All other data modules may use sx or en (English). No
Civil Aviation business rule for the value of countryIsoCode.
✓
S1-00048 Exchange of draft data modules Decide whether the project will allow the No Civil Aviation business rule.
exchange of draft data modules.
S1-00049 Definition of the issue date Decide on the definition of the issue date. No Civil Aviation business rule.
This can be, for example, the input date
(ie, the release to CSDB date), or the cut-
off date for the delivery, etc.
S1-00050 Source of the technical names Decide on the source of the technical No Civil Aviation business rule.
names and use them consistently across
the project. In all cases, the technical
name must reflect the item represented
by the SNS.
S1-00051 Rules for the information names Decide on which information codes apply All defined Information Codes in S1000D may be used.
to the project. Additionally, the following Information Codes may be used:
02A: Export Control
02B: Regulatory
Note: Use of these codes is pending release of a patch to the
S1000D Issue 4.1 Default BREX
S1-00052 Allocation of the information Decide on which information codes and No Civil Aviation business rule.
codes and the information associated information names to be
names used, and assign a Schema to be used
for each information code.
S1-00053 Data module change/revised Decide on the threshold that a data A status of "changed" is preferred in Civil Aviation
ratio module is considered revised rather than applications. In some cases when a data module has changed
changed. to such an extent that there is no value to the end user
including change markup, a status of "revised" may be used.
BRDP BREX
Number Rule
S1-00054 Use and definitions of the Decide on the use and definitions of the No Civil Aviation business rule.
attributes attributes commercialClassification and
commercialClassification and caveat.
caveat
S1-00055 Priorities and relationships of Decide on the priorities and relationships No Civil Aviation business rule.
the security attributes between the attributes
securityClassification, securityClassification,
commercialClassification and commercialClassification and caveat if
caveat they are used.
S1-00056 Use of the element Decide whether to include data restriction No Civil Aviation business rule.
<dataRestrictions> information.
S1-00057 Use of the attribute applicability Decide whether to differentiate data No Civil Aviation business rule.
in the element restrictions information based on Product
<dataRestrictions> configuration.
S1-00058 Use of the element Decide whether to include export No Civil Aviation business rule.
<restrictionInstructions> controls, handling, destruction notices
and disclosure instructions.
S1-00059 Use of the element Decide on the distribution information No Civil Aviation business rule.
<dataDistribution> contained in the element
<dataDistribution>.
S1-00060 Use of the element Decide whether and how to use the No Civil Aviation business rule.
<dataHandling> element <dataHandling>. For example,
the handling requirements and
procedures that must be applied to a
data module.
S1-00061 Use of the element Decide whether to use the element No Civil Aviation business rule.
<dataDestruction> <dataDestruction> and how to use it. For
example, the appropriate extent of
destruction instructions that must be
applied to a data module.
<dataDisclosure> element <dataDisclosure>. For example,
the requirements that must be applied to
a data module with regard to disclosure
instructions.
<supersedure> <supersedure> and how to use it. For
example, the requirements that must be
applied to a data module with regard to
supersedure notices.
BRDP BREX
Number Rule
<restrictionInfo> element <restrictionInfo>. For example,
the content and extent of restriction
information to include in a data module.
S1-00065 Use of the element <copyright> Decide whether and how to use the No Civil Aviation business rule.
and source of copyright element <copyright>. Any copyright
information information must be obtained from the
relevant authority.
S1-00066 Method of populating copyright Decide whether to populate copyright No Civil Aviation business rule.
information (in each data information in each data module or
module or in a consolidated data whether to cross-reference to a copyright
module) data module.
Note
While choosing the population method,
assess the impact of changes to
copyright information on updating of data
modules.
<policyStatement> <policyStatement>.
<dataConds> <dataConds>.
S1-00069 Use of the element <logo> Decide whether to use the element No Civil Aviation business rule.
<logo>and how it should be used at
presentation.
S1-00070 Use of the element Decide whether to use the element The attribute enterpriseCode is required unless the
<enterpriseName> and/or the <enterpriseName> and/or the attribute responsible partner company does not have a CAGE Code. In
attribute enterpriseCode for the enterpriseCode to capture the name and that case, the textual content of the element
responsible partner company CAGE code respectively, of the <enterpriseName> is required.
responsible partner company. If the ✓
name is used it must be done
consistently and be mandatory for the
project.
S1-00071 Use of the element Decide whether to use the element The attribute enterpriseCode is required unless the originator
<enterpriseName> and/or the <enterpriseName> and/or the attribute does not have a CAGE Code. In that case, the element
attribute enterpriseCode for the enterpriseCode to capture the name and <enterpriseName> is required.
responsible originator CAGE code respectively, of the
originator. If the name is used it must be
✓
done consistently and be mandatory for
the project.
BRDP BREX
Number Rule
<techStandard> <techStandard>.
<authorityInfo> element <authorityInfo>.
<techPubBase> element <techPubBase>. If used, agree
on acceptable values for the publication
baseline and where they are derived
from.
S1-00075 Use of the element Decide how to use the element No Civil Aviation business rule.
<authorityNotes> <authorityNotes>.
S1-00076 Use of the attribute applicRefid Decide whether to use attribute No Civil Aviation business rule.
of the element applicRefid on QA information.
<qualityAssurance>
S1-00077 Exchange of draft data modules Decide whether the project will allow the No Civil Aviation business rule.
exchange of draft data modules.
<systemBreakdownCode> <systemBreakdownCode>. If used, its
use must be consistent across the
project.
S1-00079 Use of the element Decide whether to use element No Civil Aviation business rule.
<functionalItemCode> <functionalItemCode>. If used, its use
must be consistent across the project.
<functionalItemRef> <functionalItemRef>. If used, its use must
be consistent across the project.
S1-00081 Use of the attribute Decide how to populate the attribute No Civil Aviation business rule.
functionalItemNumber of the functionalItemNumber of the element
element <functionalItemRef> <functionalItemRef> when this element is
used.
S1-00082 Use of the attribute Decide whether and how to use the If this attribute is used, it shall be populated with CAGE Code
manufacturerCodeValue of the attribute manufacturerCodeValue of the
element <functionalItemRef> element <functionalItemRef>. If used, the
element must be populated consistently
across the project.
S1-00083 Use of the element Decide whether to use the element The element <productSafety> shall be used only for Alert
<productSafety> <productSafety> and under what
circumstances.
Service Bulletins. ✓
S1-00084 Values for the attribute Define the values to use for the attribute The value "Alert" must be used.
safetyLabel safetyLabel. ✓
BRDP BREX
Number Rule
S1-00085 Use of the element <remarks> Decide whether to use the element No Civil Aviation business rule.
in the element <dmStatus> <remarks>. If used, its use must be
defined in the project business rules and
guidance given.
S1-00086 Use of the attribute applicRefId Decide whether and how to use the No Civil Aviation business rule.
of the element <remarks> within attribute applicRefId of the element
the element <dmStatus> <remarks> in the element <dmStatus>.
The element <remarks>can contain
remarks, which can be differentiated
based on Product configuration.
S1-00087 Use of export control Decide whether export control No Civil Aviation business rule.
regulations apply.
S1-00088 Content of export control details Decide on the requirements and No Civil Aviation business rule.
data module regarding export controls.
S1-00089 Standard wording for reasons Decide standard reason for update No Civil Aviation business rule.
for update sentences to be used. Reason for update
can be used to automatically generate a
highlights data module. Normally, a
project will mandate its use from issue
"002" upwards. Examples are:
Revised to incorporate modification XYZ
Deleted. Data module no longer required
S1-00090 Use of reason for update in Decide whether the element No Civil Aviation business rule.
conjunction with the production <reasonForUpdate> is used during the
process production process.
S1-00091 Use of applicability information Decide whether it is permissible to No Civil Aviation business rule.
differentiate reasons for update based on
Product configuration.
S1-00092 Use of change marks for tables Decide whether and how to use change For changes to content within a table, the element changed
marks for tables. will be marked. If the authoring tool does not allow markup
below the row level, then it is acceptable to apply change
markup to the individual row where the change occurs. For
new tables, change markup will be applied to the complete
table element. The table title will be marked only for changes
to the title.
S1-00093 Use of change marks for figures Decide whether and how to use change When modifying a graphic within a figure, change markup will
marks for figures. be applied only at the sheet level <graphic>. For new graphics
added to existing figures, change markup may be applied at
the sheet level and the figure level. For new figures, change
BRDP BREX
Number Rule
markup will be applied to the complete figure element. The
figure title will be marked only for changes to the title.
S1-00094 Extent of cross-referencing Decide on the extent of cross-referencing No Civil Aviation business rule.
within data modules and the methods
used for populating the various attributes.
S1-00095 Use of the element Use of the element <internalRef> in titles The element <internalRef> may be used for legacy data only.
<internalRef> in titles is strongly discouraged. However, decide
whether to use cross-references in titles.
S1-00096 Use of the attribute targetTitle Decide whether to use the attribute No Civil Aviation business rule.
targetTitle.
When used (populated), it is a tooltip in a
viewer application.
S1-00097 Presentation of the target titles Decide whether to present the target No Civil Aviation business rule.
in cross-references titles given in the element <title>.
Note
Presentation of the titles depends on the
presentation system and its settings.
S1-00098 Use of the textual content of the Decide whether to use the textual No Civil Aviation business rule.
element <internalRef> in cross- content of the element <internalRef>.
references
When used (populated), it must be
presented.
S1-00099 Use of the "identifiers" given in Decide whether to use any of the No Civil Aviation business rule.
the elements "identifiers" given in the elements
<reqSupportEquips>, <reqSupportEquips>, <reqSupplies>,
<reqSupplies>, <reqSpares> or <reqSpares> or <workLocation> as the
<workLocation> presented link (textual content of the
element <internalRef>), or as a tooltip in
a viewer application (value of the
attribute targetTitle).
Note:
The "identifiers" can be derived from the
content of the child elements or the
attributes of the four elements.
S1-00100 Use of the attribute Decide whether to use the attribute The values and definitions defined in S1000D chapter 3.9.6.1,
internalRefTargetType internalRefTargetType, which values to Table 25 shall be used.
use and allocate suitable definitions to
the values. Refer to Chap 3.9.6.1.
BRDP BREX
Number Rule
S1-00101 Define the format of the cross- Decide whether the values of the cross- No Civil Aviation business rule.
reference attributes id and reference attributes id and internalRefId
internalRefId must be prefixed by alpha characters that
identify the type of the target element.
Example:
Structure: Prefix followed by a hyphen
and a four digit number to make it unique
within the data module (eg, "par-0001").
Prefixes:
"fig" for figures and alternates
"tab" for tables
"mma" for multimedia and alternates
"sup" for supplies
"seq" for support equipment
"spa" for spares
"par" for levelled paragraphs and
alternates
"stp" for steps of procedure, fault
isolation, etc, and alternates
"gra" for graphics (multiple sheets)
"mmo" for multimedia objects
"hot" for hotspots (eg, "fig-0001-hot-
0002")
"pme" for parameters
"zon" for zones
"wla" for work locations
"mat" for single material or material sets
"acp for access points
BRDP BREX
Number Rule
Note
The four digit number has no connection
to, eg, the figure or table number which is
generated for data module presentation.
For example, the value of the attribute id
can be "fig-0345" for "Fig 1". Refer to
Para 2.1.
Note
Refer to Chap 3.9.5.2.1.10 for the
equivalent business rule decision point
regarding footnotes. Example: "ftn-0001".
S1-00102 Use and format of the attribute Decide whether to use the attribute No Civil Aviation business rule.
referredFragment of the element referredFragment and, if used, list the
<dmRef> precautions.
S1-00103 Use of issue information and Decide whether to use issue and in-work No Civil Aviation business rule.
language in data module numbers, as well as language and
references country codes of the destination data
module in data module references. In
making this decision, the project or
organization must be aware of the
implications of using the items when
referenced data modules are updated.
S1-00104 Use of title and issue date in Decide whether to use the title and the No Civil Aviation business rule.
data module references issue date of the destination data module
in data module references.
S1-00105 Use of issue information and Decide whether to use issue and in-work No Civil Aviation business rule.
language in publication module numbers, as well as language and
references country codes of the destination
publication module in publication module
references. In making this decision, the
project or organization must be aware of
the implications of using the items when
referenced publication modules are
updated.
S1-00106 Population of the element <refs> Decide if and how the element <refs> is No Civil Aviation business rule.
populated. If populated, the order of
items in the list must be specified.
S1-00107 Define the words before and Define the words before and after the No Civil Aviation business rule.
after the reference elements elements <dmRef>, <pmRef> and
BRDP BREX
Number Rule
<externalPubRef>. This is important as it
has implications on the stylesheets used.
Example: For one implementation, the
stylesheet can automatically generate the
words "Refer to data module: " when it
recognizes the element <dmRef>. This
will cause problems if the author has
written "Refer to " within the paragraph
before the element <dmRef>.
S1-00108 Use of titles for lists Decide whether to use titles for each of No Civil Aviation business rule.
the sequential, random and definition
lists.
S1-00109 Use of the attribute listItemPrefix Decide whether to use the attribute If the attribute listItemPrefix is used, only pf02 shall be used.
listItemPrefix, which values to use and
allocate suitable definitions to the values. ✓
Refer to Chap 3.9.6.1.
S1-00110 Use of definition list headers Decide whether to use definition list No Civil Aviation business rule.
headers.
S1-00111 Use of applicability information Decide whether and how to use the No Civil Aviation business rule.
on various caption group child attribute applicRefId of various
elements <captionGroup> child elements.
S1-00112 Use of color for Tables of Decide whether to use the attribute The attribute tableOfContentType shall not be used.
contents - attribute tableOfContentType, (eg, for Table of
tableOfContentType in the contents in Flight reference cards). ✓
element <captionGroup>
S1-00113 Use of the attributes rowsep and Decide whether the attributes rowsep No Civil Aviation business rule.
colsep in the element and colsep rules between <captionEntry>
<captionEntry> elements are required.
S1-00114 Use of the local use of spans Decide whether the element No Civil Aviation business rule.
within the element <captionEntry> spans are to be defined
<captionEntry> locally or by the element <spanspec>.
S1-00115 Use of the attribute color in the Decide whether to use the attribute color, The attribute color shall not be used.
element <caption> which values to use and allocate suitable
definitions to the values. Refer to ✓
Chap 3.9.6.1.
S1-00116 Use of attribute Decide whether and how to use the No Civil Aviation business rule.
systemIdentCode in captions attribute systemIdentCode.
S1-00117 Inline use of captions Decide whether inline captions affect the No Civil Aviation business rule.
text line spacing and how this is defined
S1-00118 Use of the element <title> Decide whether and how to use the No Civil Aviation business rule.
element <title>.
BRDP BREX
Number Rule
S1-00119 Use of cross-references from Decide whether to allow cross- The use of cross-references from titles is allowed for legacy
titles referencing from titles. data only. This does not apply to the use of cross-references
within <inlineSignificantData>, which are permitted.
S1-00120 Use of titles for the elements Decide whether titles can be included for No Civil Aviation business rule.
<levelledPara> and the elements <levelledPara> and
<proceduralStep> from sublevel <proceduralStep> from sublevel six thru
six thru eight for legacy data eight when converting legacy data to
S1000D.
S1-00121 Use of standard table types Decide if a list of standard table types No Civil Aviation business rule.
applies to the project (eg, inspection,
examination) and define what the
business rules are for these types in
terms of their presentation requirements
and certain textual values (eg, titles and
heading row values). Each of these
standard types must have a defined
value that can be applied to the table’s
attribute tabstyle.
S1-00122 Use of tables as graphics Decide if tables represented as graphics Graphics shall not be used to store tables with the exception
are allowed, and if they are, in what of legacy data and cases where the table data cannot be
situations they can be used. represented properly through use of the XML table format.
S1-00123 Use of applicability information Decide whether and how to use the Applicability is allowed at <table> and < row> levels but not at
of various table child elements - attribute applicRefId of various <table> <entry> level. Applicability is also allowed on entry sub-
attribute applicRefId of the
element <table>
child elements. The child elements can
be differentiated based on Product
elements. ✓
configuration.
S1-00124 Use of applicability information Decide whether and how to use the No Civil Aviation business rule.
for complete figures and attribute applicRefId of various <figure>
illustration sheets - attribute child elements. The child elements can
applicRefId of the element be differentiated based on Product
<figure> configuration.
S1-00125 Use of hotspots Decide whether to use hotspots. No Civil Aviation business rule.
S1-00126 Use of legends Decide whether to use legends. No Civil Aviation business rule.
S1-00127 Use of leading zeros in the Decide whether the element The use of leading zero(s) in <listItemTerm> must match the
element <listItemTerm> <listItemTerm> is to contain a leading leading zero usage in the figure callouts.
zero when using callout/item numbers.
The default is no leading zero.
S1-00128 Types of legends Decide on the strategy for legends. No Civil Aviation business rule.
Legends can appear as part of the
illustration or as text using the element
BRDP BREX
Number Rule
<legend>. The advantage of making the
legend part of the text is that:
the same illustration can have different
legends wherever it appears (eg, in multi-
language projects)
the text of the element <legend> can be
searched (this might not be the case if
the legend is part of the illustration)
items in the illustration can be linked to
the legend by the use of hotspots
the legend in the text can save space on
the illustration (particularly when the
legends are long)
S1-00129 Suitability of multimedia use Decide whether using multimedia is No Civil Aviation business rule.
suitable for the environment in which the
project will operate.
S1-00130 Permitted types of multimedia Decide what types of multimedia objects No Civil Aviation business rule.
are permitted.
S1-00131 Use of foldouts Decide whether to use the element The element <foldout> shall not be used. Oversize graphics or
<foldout> in which information sets it is tables may be accommodated through the object’s attributes,
allowed. e.g., reproductionHeight and reproductionWidth.
Note ✓
It is only used for page-oriented
publications, as it will not have an effect
in the screen view of an IETP.
S1-00132 Use of hotspots Decide whether and how to use hotspots. No Civil Aviation business rule.
If hotspots are to be used decide whether
hotspots can be used to link to graphical
objects from local text
hotspots can be used to link from
graphical objects to other graphical
objects or local text
BRDP BREX
Number Rule
hotspots can be used to link from
graphical objects to other data modules
S1-00133 Use of the element <parameter> Decide whether to use the element No Civil Aviation business rule.
<parameter> and how to use it. If used,
specify the attributes to be used within
the project.
<preliminaryRqmts> <preliminaryRqmts> in maintenance
planning, fault isolation, maintenance
checklist and/or process data modules.
<workAreaLocationGroup>> in element <workAreaLocationGroup>. The
the element <preliminaryRqmts> possibility of duplication and mismatch of
data given in the maintenance planning
information must be taken into account.
<workLocation> in the element element <workLocation>. If used, decide
<preliminaryRqmts> which data module types it will be used
with.
S1-00137 Use of the element <workArea> Decide whether and how to use the No Civil Aviation business rule.
in the element element <workArea>. If used, decide
<preliminaryRqmts> and the which data module types to use it.
element <checkListItem>
<installationLocation> in the element <installationLocation>. If used,
element <preliminaryRqmts> decide which data module types to use it.
<productItem> in the element element <productItem>. If used, decide
<preliminaryRqmts> which data module types to use it.
S1-00140 Use of the attribute Decide whether and how to use the No Civil Aviation business rule.
productItemName in the attribute productItemName.
element <preliminaryRqmts>
S1-00141 Use of the attribute Decide whether and how to use the No Civil Aviation business rule.
productItemType in the element attribute productItemType.
<preliminaryRqmts>
<taskDuration> in the element element <taskDuration>. The possibility
<preliminaryRqmts> and the of duplication and mismatch of data given
element <checkListItem> in the maintenance planning information
must be taken into account.
BRDP BREX
Number Rule
S1-00143 Include a circuit breaker list as Decide if a circuit breaker list is to be No Civil Aviation business rule.
part of the preliminary conditions considered as part of preliminary
- (element conditions and thus the use of the
<reqCondCircuitBreaker>) element, or if the circuit breaker settings
are part of the steps. In this latter case
the element <circuitBreakerDescrGroup>
in steps content can be used.
<reqPersons> in the element element <reqPersons>. For example, use
<preliminaryRqmts> either the element <personnel> or
<person> or use both elements.
S1-00145 Values for the attribute Define a list of categories (eg, Electrician, Refer to "Employee Skill Code" in the ATA Common Support
personCategoryCode in the
Propulsion engineer, Maintainer). Data Dictionary for permitted values. ✓
S1-00146 Values for the element <trade> Define a list of trades/trade codes. No Civil Aviation business rule.
in the element
<preliminaryRqmts>
<reqTechInfoGroup> in the element <reqTechInfoGroup>.
S1-00148 Use of the attribute Decide whether to use the attribute In addition to the codes listed in S1000D, Code "ti51" is to be
reqTechInfoCategory in the reqTechInfoCategory, which values to used for "External Publication" in Civil Aviation applications.
element <reqTechInfoGroup> use and allocate suitable definitions to
Note
Technical information needed, can be
✓
presented in Required technical
information (using the element
<reqTechInfoGroup>) and/or in the
Reference table (using the element
<refs> in the element <content>).
S1-00149 Listing of standard tools in Decide what types of standard tools or No Civil Aviation business rule.
Preliminary requirements toolkits to be identified and listed in the
table "Support equipment".
S1-00150 Use of the attribute id on the Decide whether to use the attribute id to No Civil Aviation business rule.
element <supportEquipDescr> create cross-references from the
in the element procedure to the support equipment
<preliminaryRqmts> listed in Preliminary requirements. The
attribute id on element
<supportEquipDescr> is used to
establish the link between the two and
BRDP BREX
Number Rule
will guarantee consistent use of
identification throughout the procedure.
The use of cross-references is
encouraged.
S1-00151 Use of the attribute Decide whether to use the attribute No Civil Aviation business rule.
materialUsage in the element materialUsage in the elements
<supportEquipDescr>, the <supportEquipDescr>, <supplyDescr>
element <supplyDescr> and the and <spareDescr> context and what
element <spareDescr> context values to be used.
S1-00152 Use of identification elements in Decide which elements The element <natoStockNumber> shall not be used.
the element <catalogSeqNumberRef>
<supportEquipDescr>, the <natoStockNumber>, <identNumber>, For <supportEquipmentDescr> and <supplyDescr> the
element <supplyDescr> and the <toolRef> and <materialSetRef> to use element <catalogSeqNumberRef> shall not be used. ✓
element <spareDescr> context for identification and how to populate
these elements.
S1-00153 Use of the element Decide whether and how to use the The element <natoStockNumber> shall not be used.
<natoStockNumber> in the element <natoStockNumber>.
element <supportEquipDescr>,
the element <supplyDescr> and ✓
the element <spareDescr>
context
<materialSetRef> in the element <materialSetRef> in the
elements <supportEquipDescr>, elements <supportEquipDescr>,
<supplyDescr> and <supplyDescr> and <spareDescr>
<spareDescr> context within the context.
S1-00155 Use of the attribute id on the Decide whether to use the attribute id to No Civil Aviation business rule.
element <supplyDescr> in the create cross-references from the
element <preliminaryRqmts> procedure to the supplies listed in
Preliminary requirements. The attribute id
on element <supplyDescr> is used to
encouraged.
S1-00156 Use of the attribute id on Decide whether to use the attribute id to No Civil Aviation business rule.
element <sparesDescr> in the create cross-references from the
element <preliminaryRqmts> procedure to the spares listed in
Preliminary requirements. The attribute id
on element <sparesDescr> is used to
BRDP BREX
Number Rule
will guarantee consistent use
encouraged.
<closeRqmts> in the process <closeRqmts> in the process data
data modules modules.
circuitBreakerAction in text circuitBreakerAction. If used, establish
element <circuitBreakerRef> writing rules to ensure that authors will be
consistent in the paragraph text and the
value of the attribute itself.
S1-00159 Use of the attribute checkSum in Decide whether to use and how to No Civil Aviation business rule.
text element populate the attribute checkSum.
<circuitBreakerRef>
S1-00160 Types of inline significant data Decide whether to use the attribute No Civil Aviation business rule.
to markup using the attribute significantParaDataType and which types
significantParaDataType in the of data to mark up and in what contexts.
text element It must also be considered that data
<inlineSignificantData> modules can be less portable if the
paragraph significant data types are
extended in the BREX file past the
standard types.
S1-00161 Use of the text element Decide whether to use quantity data No Civil Aviation business rule.
<quantity> markup and to what extent. The quantity
data markup can be used with or without
value and tolerance decomposition.
S1-00162 Types of quantity data to Decide whether to use the attribute Any of the pre-defined values in S1000D may be used. See
markup using the attribute quantityType, which values to use in Appendix A for additional Civil Aviation specific values that
quantityType in the text element what context and allocate suitable may also be used.
<quantity> definitions to the values. Refer to Chap
3.9.6.1.
Note
The project or the organization must also
consider that data modules can be less
portable if the quantity data types are
extended in the BREX file past the
standard types.
S1-00163 Use of the value (element Decide whether and how to use to use If <quantityValue> is used, any associated tolerances must
<quantityValue>) and tolerance the element <quantityValue> and the also be tagged using the <quantityTolerance> element. This
(element <quantityTolerance>)
BRDP BREX
Number Rule
decomposition in the text element <quantityTolerance> does not preclude providing a range of values using the
element <quantity> decomposition. quantityGroupType attribute.
S1-00164 Unit of measure to be used If using the value and tolerance No Civil Aviation business rule.
decomposition, decide at which level of
the markup the attribute
quantityUnitOfMeasure is to be included.
Allowable locations are on the parent
element <quantityGroup> which applies
to all child elements or on the individual
child elements <quantityValue> and
<quantityTolerance>. A consistent usage
of the attribute quantityUnitOfMeasure is
required to produce a consistent display
or printout to the user.
S1-00165 Use of attribute Decide whether to use the attribute No Civil Aviation business rule.
quantityUnitOfMeasure quantityUnitOfMeasure, which values to
Note
Due to the large number of units of
measure, it is expected that a project will
only use a small subset of the available
units of measure. It must also be
considered that data modules can be
less portable if the units of measure
types are extended by the BREX
mechanism past the standard types.
S1-00166 Use of the element <zoneRef> Decide whether to use the element If <zoneRef> is used, the attribute zoneNumber is required.
<zoneRef>, and how to use it.
Consideration for duplication and
mismatch of data given in the ✓
maintenance planning information has to
be taken.
S1-00167 Use of the element Decide whether to use the element If <accessPointRef> is used, the attribute accessPointNumber
<accessPointRef> <accessPointRef> and how to use it. is required.
mismatch of data given in the ✓
maintenance planning information has to
be taken.
accessPointTypeValue in the accessPointTypeValue, which values to
text element <accessPointRef>
BRDP BREX
Number Rule
S1-00169 Use of the text element Decide whether an index is required and An index is not required.
<indexFlag> to what level.
emphasisType in the text emphasisType, which values to use and
element <emphasis> allocate suitable definitions to the values.
S1-00171 Use of the symbols Decide whether and how to use symbols No Civil Aviation business rule.
using the text element <symbol>.
S1-00172 Use of footnotes Decide whether and how to use the text Footnotes may be used only in Preliminary Requirements and
element <footnote> and when used, tables.
decide whether their use is limited to
regular text and titles (inline) and/or to
✓
tables (table footnotes).
S1-00173 Types of footnote markers Decide on the types of footnote markers Only superscript numbers may be used ("num").
(attribute footnoteMark) to use. It is
recommended to use:
- only one type of footnote marker for
each of the table footnotes and the inline
✓
footnotes throughout a project
- superscripted numbers for both.
S1-00174 Markup of acronyms Decide whether and how to mark up No Civil Aviation business rule for the elements <acronym>
acronyms by the use of the text elements and <acronymTerm>.
<acronym> and <acroterm>. If used,
decide whether to use the attribute
acronymType, which values to use and
The attribute acronymType may contain only values "at01",
"at02", or "at03".
✓
allocate suitable definitions to the values.
verbatimStyle verbatimStyle, which values to use and
S1-00176 Presentation of controlled Decide the method of presentation for authorityName will be used to document the regulation source
content controlled content recorded by the (e.g., FAA, EASA). authorityDocument will be used to
attributes authorityName and document the regulation value (e.g., CDCCL, ETOPS).
authorityDocument.
S1-00177 Use of common information Decide whether to use the element No Civil Aviation business rule.
<commonInfo> in procedural,
BRDP BREX
Number Rule
maintenance planning, common
repositories, and/or fault data modules.
S1-00178 Markup method for common Decide which markup method to use for No Civil Aviation business rule.
information text common information text:
the method containing <note>, <para>
and <commonInfoDescrPara>
or
the method containing only
<commonInfoDescrPara>
S1-00179 Granularity of data in descriptive Decide on the level of granularity of the No Civil Aviation business rule.
data modules descriptive data modules.
S1-00180 Level of depth of descriptive Decide whether to exceed 5 levels of No Civil Aviation business rule.
data modules depth for new data.
S1-00181 Minimum para occurrences Decide whether to impose a minimum of No Civil Aviation business rule.
two occurrences of child elements
<levelledPara> and/or
<levelledParaAlts>.
S1-00182 Use of the optional element Decide whether to use the element No Civil Aviation business rule.
<commonInfo> <commonInfo>, when to use the element,
and give guidance and rules that will
make sure it is consistently used.
S1-00183 Use of the optional attribute The element <mainProcedure> and the The attribute skillLevelCode shall not be used by OEMs,
skillLevelCode element <proceduralStep> can contain however may be used by operators, MROs, etc.; for example
an indication of the skill level required for to develop job cards.
the whole procedure and/or for individual
steps/substeps using the attribute
skillLevelCode. Decide whether and how
to use the attribute skillLevelCode.
S1-00184 Use of the optional attribute The element <mainProcedure> and the The attribute independentCheck shall not be used by OEMs,
independentCheck element <proceduralStep> can contain a however may be used by operators, MROs, etc.; for example
check using the attribute to develop job cards.
independentCheck to indicate that the
whole procedure and/or individual
steps/substeps must be checked by a
supervisor with a given qualification.
Decide whether and how to use the
attribute independentCheck.
BRDP BREX
Number Rule
S1-00185 Use of the alternates concept Decide whether to use the alternates No Civil Aviation business rule.
within the element concept for steps, figures and multimedia
<mainProcedure> within the element <mainProcedure>.
This concerns the child elements
<proceduralStepAlts> (refer to
Para 2.4.2), <figureAlts> (refer to
Chap 3.9.5.2.1.7) and <multimediaAlts>
(refer to Chap 3.9.5.2.1.7).
S1-00186 Decide on the maximum number Decide on the maximum number of step A maximum of 8 levels is allowed.
of step levels in a procedure levels allowed in a procedure. Exceeding
five levels of depth is strongly
discouraged in development of new data.
It is recommended that additional levels
are only used in a conversion effort
where the existing data is authored to
this depth (maximum eight levels) and
restructuring of data is not feasible.
S1-00187 Decide on the minimum number Decide whether to allow for a single No Civil Aviation business rule.
of substeps in a step substep, or to insist on a minimum of two
substeps in a step.
Note
The Schema allows for a single substep.
S1-00188 Use of the optional attribute Decide whether to use the attribute The attribute keepWithNext shall not be used.
keepWithNext keepWithNext. ✓
S1-00189 Use of the optional attribute Decide whether and how to use the The attribute itemCharacteristic shall not be used.
itemCharacteristic attribute itemCharacteristic. ✓
S1-00190 Use of the optional attribute Decide whether to use the attribute No Civil Aviation business rule.
altsName altsName for the element
<proceduralStepAlts> for steps.
S1-00191 Use of titles for procedural steps Decide whether and how to use the If used, the element <title> shall be used to name the
element <title> for steps. procedural step or sequence of steps, but shall not contain the
action steps themselves.
S1-00192 Use of correlation fault concept Decide whether to use the correlated No Civil Aviation business rule.
fault concept.
S1-00193 Use of correlated fault Decide how to populate element No Civil Aviation business rule.
messages and warnings <warningMalfunction>, element
<assocWarningMalfunction> and element
<bitMessage> when using the correlated
fault concept.
BRDP BREX
Number Rule
S1-00194 Use of detection and description Decide whether the repetition of the No Civil Aviation business rule.
information elements detection and description information for
the basic fault which has been correlated
(element <faultDescr> and element
<detectionInfo>) is used. Projects can
consider that the detection and
description information can for example
be populated during IETP generation by
picking up the information in the detected
fault list data module describing the basic
faults.
S1-00195 Use of the attribute Decide whether to use the attribute The attribute independentCheck shall not be used by OEMs,
independentCheck in the independentCheck, which values to use however it may be used by operators, MROs, etc.
element <isolationProcedure>, and allocate suitable definitions.
<isolationStep> and
<isolationProcedureEnd>
S1-00196 Use of titles in fault isolation Decide whether to use the element If used, the element <title> shall be used to name the step or
steps <title> in fault isolation steps. sequence of steps, but shall not contain the action steps
themselves.
S1-00197 Values for the attribute Decide which values to use for the No Civil Aviation business rule.
inspectionTypeCategory attribute inspectionTypeCategoryand
allocate suitable definitions. .
S1-00198 Methodology of assigning tasks Decide on a methodology of assigning No Civil Aviation business rule.
into the element <taskGroup> tasks to groups.
S1-00199 Use of the attribute markerType Decide whether to use the attribute No Civil Aviation business rule.
markerType, which values to use and
allocate suitable definitions.
worthinessLimit worthinessLimit, which values to use and
reducedMaint reducedMaint, which values to use and
S1-00202 Values for the attribute Decide which values to use for the No Civil Aviation business rule.
sourceOfRqmt attribute sourceOfRqmt allocate suitable
definitions.
S1-00203 Use of the attribute approval Decide whether to use the attribute No Civil Aviation business rule.
approval, which values to use and
BRDP BREX
Number Rule
S1-00204 Use of the element Decide whether to use the element The element <preliminaryRqmts> shall be used.
<preliminaryRqmts> in the
element <taskDefinition>
<preliminaryRqmts>. ✓
S1-00205 Use of attribute Decide whether to use the attribute The attribute supervisorLevelCode shall not be used by
supervisorLevelCode supervisorLevelCode, which values to OEMs, however may be used by operators, MROs, etc.
S1-00206 Use of element Decide whether to use of the element No Civil Aviation business rule.
<timeLimitCategory> <timeLimitCategory> and define the
values for the attribute
timeLimitCategoryValue.
S1-00207 Not applicable for Civil Aviation applications.
thru S1-
00214
initialProvisioningProjectNumber initialProvisioningProjectNumber (IPPN).
(IPPN) The codes must not be duplicated within
a project.
S1-00216 Use of the element Decide whether and how to use the The element <natoStockNumber> shall not be used.
<natoStockNumber> (NATO NATO Stock Number, split it into its three
stock number) fields using the attributes
natoSupplyClass,
natoCodificationBureau and ✓
natoItemIdentNumberCore or to fill it as a
whole in the child element
<fullNatoStockNumber>.
S1-00217 Use of hotspots in IPD data Decide whether to use the generic No Civil Aviation business rule.
modules hotspot mechanism in IPD data modules.
S1-00218 Use of the attribute partStatus in Decide whether to use the attribute No Civil Aviation business rule.
the element <itemSeqNumber> partStatus in the element
<itemSeqNumber>, which values to use
and allocate suitable definitions to the
values. Refer to Chap 3.9.6.1.
<partSegment> in the element <partSegment> to store the part data in
<itemSeqNumber> the IPD data module each time the part is
listed or whether to store the part data
once externally in the part CIR data
module.
Note
BRDP BREX
Number Rule
The element <partSegment> must be
used for S2000M IPD data modules.
S1-00220 Use of the element Decide whether and how to use the If used, <partKeyword> must contain the value provided in the
<partKeyword> in the element element <partKeyword>. ATA Spec 2000 Initial Provisioning data.
<itemSeqNumber>
<physicalSecurityPilferageCode <physicalSecurityPilferageCode> and
> in the element <techData> define a list of values. When S2000M is
within the element used, the list must be as stated in the
<itemSeqNumber> data element definition for the S2000M
element PSC.
S1-00222 Use of the attribute Decide on the range and definitions of If used, the list of allowable UOM values must be those
unitOfMeasure in the element the values for the attribute defined in the ATA Spec 2000 Unit of Measure Code (UNT).
<unitOfIssueQualificationSegme unitOfMeasure.
nt> within the element
<itemSeqNumber> Note
When the IP data modules are created
from S2000M, the list of allowed UOM
✓
values must contain those defined in the
data element definition in S2000M. When
S2000M is used, it is strongly
recommended to use the S2000M UOM
values throughout the project.
S1-00223 Use of the element Decide on the method of identification of No Civil Aviation business rule.
<optionalPart> in the element the optional part.
<partRefGroup> within the
element <itemSeqNumber>
S1-00224 Use of the element Decide on the method of identification of Preferred spare parts shall be identified by Part Number and
<preferredSparePart> in the the preferred spare part. Manufacturer Code.
element <partRefGroup> within
the element <itemSeqNumber>
S1-00225 Use of the element Decide on the method of identification of No Civil Aviation business rule.
<alteredFromPart> in the the altered from part.
element <partRefGroup> within
S1-00226 Use of the element Decide on the method of identification of Manufactured from parts shall be identified by Part Number
<localFabricationMaterial> the local fabrication material. and Manufacturer Code.
<selectOrManufactureFromIdent <selectOrManufactureFromIdent>. If
> in the element used, decide on its range and the
definition of the values to be used.
BRDP BREX
Number Rule
<partLocationSegment> within
S1-00228 Use of restricted operation notes Decide whether to use the element No Civil Aviation business rule.
<restrictedOperationNote>.
<usableOnCodeEquip> in the element <usableOnCodeEquip>. If used,
element <applicabilitySegment> decide on its range and the definition of
within the element the values to be used. When S2000M is
<itemSeqNumber> used, the list must be as stated in the
data element definition for the S2000M
element UCE.
<usableOnCodeAssy> in the element <usableOnCodeAssy>. If used,
element UCA.
S1-00231 Use of the element Decide whether and how to use the If used, the list of allowable values must be those defined in
<interchangeability> in the element <interchangeability>. If used, the ATA Spec 2000 Interchangeability Code (INC).
within the element
<itemSeqNumber>
the values to be used. When S2000M is
used, the list must be as stated in the
✓
element ICY.
thru S1-
00235
S1-00236 Use of the attributes Decide whether to use the attributes No Civil Aviation business rule.
condNumber, condNumber, manufacturerCodeValue
manufacturerCodeValue and and condType.
condType in the element
<changeAuthorityData> within
S1-00237 Use of the BREX to define the Decide whether to use the BREX for the No Civil Aviation business rule.
non S2000M elements definition of the non S2000M elements.
S1-00238 Use of wiring data description Decide whether to produce wiring data Wiring data description data modules shall not be used.
data modules description data modules in order to
reflect all decisions concerning elements ✓
and attributes of the wiring data Schema.
S1-00239 Use of the element <wireType> Decide on the definition of wire type No Civil Aviation business rule.
content/codes.
BRDP BREX
Number Rule
S1-00240 Use of the element Decide whether and how to use the wire The element <wireSeqNumber> shall not be used. The wire
<wireSeqNumber> sequential number. sequential number must be included in the <wireNumber>
element.
Note:
The element <wireSeqNumber> must be
✓
used if the wire sequential number is not
given in the element <wireNumber>.
S1-00241 Use of the element Decide whether and how to use electrical No Civil Aviation business rule.
<electricalEquipConnection> equipment connection information, in
particular define the values of attribute
connectionType consistently.
thru S1-
00249
<commonInfo> in CIR element <commonInfo> in CIR.
S1-00251 Use of the attribute altNumber in Decide whether to use the attribute No Civil Aviation business rule.
the functional items CIR altNumber, which values to use and
the circuit breakers CIR altNumber, which values to use and
S1-00253 Use of the attribute Decide which values (eg, subzones) to No Civil Aviation business rule.
zoneRefType use for the attribute zoneRefType and
the zones CIR altNumber, which values to use and
S1-00255 Use of the attribute Decide which values (eg, subaccess No Civil Aviation business rule.
accessPointRefType points) to use for the attribute
accessPointRefTypeand allocate suitable
definitions.
the access points CIR altNumber, which values to use and
S1-00257 Use of the attribute lowestLevel Decide which values to use for the The attribute lowestLevel shall not be used by OEMs; however
in the supplies CIR attribute lowestLevel and allocate it may be used by operators.
suitable definitions. Refer to
Chap 3.9.6.1.
S1-00258 Use of the supply requirement Decide whether to implement supply No Civil Aviation business rule.
CIR data module or not requirement CIR data module.
BRDP BREX
Number Rule
S1-00259 Use of a single or multiple Decide whether there is one single No Civil Aviation business rule.
supply requirement CIR data supply requirement CIR data module or
module several depending on the SNS. The
application of the SNS determines the
granularity of these data modules.
S1-00260 Use of the attribute toolRefType Decide which values to use for the No Civil Aviation business rule.
in the tools CIR attribute toolRefType and allocate
suitable definitions.
the tools CIR altNumber, which values to use and
S1-00262 Use of the attribute Decide which values (eg, servicing, No Civil Aviation business rule.
taskCategoryCode in the tools maintenance, overhaul, repair) to use for
CIR the attribute taskCategoryCode and
S1-00263 Use of the attribute Decide whether to manage the system No Civil Aviation business rule.
systemDiffCode in the element difference code in the functional and/or
<functionalPhysicalAreaIdent> physical areas CIR data module.
S1-00264 Use of the attributes Decide whether to manage the No Civil Aviation business rule.
disassyCode and disassembly code and disassembly
disassyCodeVariant in the variant code in the functional and/or
element physical areas CIR data module.
<functionalPhysicalAreaIdent>
S1-00265 Use of the container data Decide whether to use the container data No Civil Aviation business rule.
module module.
S1-00266 Use of applicability within Decide whether applicability annotations If the container DM is delivered as part of the exchange
container data module content are duplicated from the referenced data package, applicability shall be duplicated from the referenced
modules to the container data module. data modules to the container data module.
S1-00267 Conducting a performance Decide whether to conduct a No Civil Aviation Business Rule.
analysis performance analysis to determine
factors that can affect performance and
gaps in job performance or a training
needs analysis to determine training
requirements.
S1-00268 Developing learning objectives Decide whether to develop learning No Civil Aviation Business Rule.
objectives in accordance with task
analysis items. Learning objectives ought
to be developed in accordance with task
analysis items that support system
maintenance and operational
procedures. Aligning learning objectives
with task analysis items in the early
BRDP BREX
Number Rule
content preplanning stages will foster
reusable data and content alignment.
Refer to Chap 3.9.7 for content
preplanning discussions.
S1-00269 Packaging lesson plans in Decide whether to package lesson plans No Civil Aviation Business Rule.
SCORM content packages in SCORM content packages.
S1-00270 Define life cycle need for Define life cycle need for analysis No Civil Aviation Business Rule.
performance analysis data information and requirements resulting
from a Performance Analysis for the
client organization and human
performance system affected by the
product.
S1-00271 Define life cycle need for Define life cycle need for analysis No Civil Aviation Business Rule.
training needs analysis data information and requirements resulting
from a Training Needs Analysis for a
training intervention.
S1-00272 Use of element <dmRef> to link Decide whether to use of the element No Civil Aviation Business Rule.
content data to learning <dmRef> to establish references to
objective items content data supporting learning
objective items.
S1-00273 Use of the attribute Decide whether to assign weighted No Civil Aviation Business Rule.
weightingFactor values to individual interactions.
S1-00274 Use of the attribute attempts Decide whether to allow multiple No Civil Aviation Business Rule.
response attempts for interaction items.
checkListCategory checkListCategory, which values to use
<checkListIntervals> <checkListIntervals>.
<checkListProcedure> element <checkListProcedure> and its
subelements.
<equipmentNotAvailable> <equipmentNotAvailable>.
S1-00279 Define maximum number of Projects must decide the maximum No Civil Aviation business rule.
steps levels in number of step levels allowed.
<checkListProcedure>
S1-00280 Use of the attribute sbTopicType Decide which topic type values are Only the following pre-defined values are allowed and must be
in the element <sbRevisionInfo> mandatory, which are optional and the
sequence in which they must be
provided in the order listed: ✓
BRDP BREX
Number Rule
delivered in the element "sbtt09", Compliance (Optional)
<sbRevisionInfo>. Refer to Chap 3.9.6.1. "sbtt21", Additional work (Optional)
"sbtt22", Revision reason (Mandatory)
"sbtt23", Revision history (Mandatory)
"sbtt24", Revision sequence (Mandatory)
See Appendix A for additional project-specific values that may
also be used.
S1-00281 Use of the attribute sbTopicType Decide which topic type values are No Civil Aviation business rule.
in the element <sbSummary> mandatory, which are optional and the
sequence in which they must be
delivered in the element <sbSummary>.
S1-00282 Use of the attribute sbTopicType Decide which topic values are Only the following pre-defined values are allowed and must be
in the element <sbPlanningInfo> mandatory, which are optional and the provided in the order listed. All are mandatory. Use the
sequence in which they must be subelement <noInfo> if the topic type is not applicable.
delivered in the element
<sbPlanningInfo>. Refer to Chap 3.9.6.1. "sbtt05" Applicability
"sbtt06" Concurrent requirements
"sbtt07" Reason
"sbtt08" Description
"sbtt09" Compliance
"sbtt10" Approval
"sbtt11" Manpower ✓
"sbtt12" Weight and balance
"sbtt13" Electrical load data
"sbtt14" Software accomplishment summary
"sbtt15" Referenced documentation
"sbtt16" Documentation affected
"sbtt17" Industry support information
also be used.
S1-00283 Use of the attribute sbTopicType Decide which topic type values are Any of the pre-defined values may be used. See Appendix A
in the element mandatory, which are optional and the for additional project-specific values that may also be used.
<sbAdditionalInfo> sequence in which they must be
delivered in the element ✓
<sbAdditionalInfo>. Refer to
Chap 3.9.6.1.
S1-00284 Use of the attribute Decide whether to use the attribute No Civil Aviation business rule. Note: this attribute is not found
sbModificationClassification sbModificationClassification, which in Chap 3.9.6.1.
values to use and allocate suitable
definitions to the values. Refer to
Chap 3.9.6.1.
BRDP BREX
Number Rule
S1-00285 Use of the attribute Decide whether to use the attribute Any of the pre-defined values may be used. See Appendix A
genericPropertyType in the genericPropertyType, which values to for additional project-specific values that may also be used.
element
<genericPropertyGroup> in the
✓
element <sbManagementInfo>
S1-00286 Use of the attribute Decide whether to use the attribute Any of the pre-defined values may be used. See Appendix A
sbMaterialType sbMaterialType, which values to use and for additional project-specific values that may also be used.
allocate suitable definitions to the values. ✓
S1-00287 Use of the element Decide whether the use of the element If the Service Bulletin contains procured material information,
<sbProcurementInfo> <sbProcurementInfo> then use of the element <sbProcurementInfo> is required,
however there is no Civil Aviation business rule regarding its
is allowed directly within the element location.
<sbMaterialSet>
is allowed only within definitions of
individual material sets or
is allowed only directly within definitions
of individual spares, supplies and support
equipment
S1-00288 Use of the element Decide whether the use of the element No Civil Aviation business rule.
<sbIndustrySupport> <sbIndustrySupport>
is allowed directly within <sbMaterialSet>
of individual spares, supplies and support
equipment
sbMaterialIdent sbMaterialIdent.
sbMaterialIssue sbMaterialIssue.
S1-00291 Use of the attribute Decide whether to use the attribute Only the following pre-defined values are allowed:
genericPropertyType in the genericPropertyType, which values to
element use and allocate suitable definitions to "gpt10", Disposition for removed spare that can be on
<genericPropertyGroup> within
the element
the values. Refer to Chap 3.9.6.1. customer shop
"gpt11", Support code for removed spare
✓
<sbIndividualRemovedSpare> The predefined values are "gpt10" and
"gpt11".
BRDP BREX
Number Rule
also be used.
S1-00292 Use of the attribute Decide whether to use the attribute Only the following pre-defined values are allowed:
materialUsage in the element genericPropertyType, which values to
<sbRemovedSpareDescr> use and allocate suitable definitions to "mu01", Discarded
the values. Refer to Chap 3.9.6.1. "mu02", Retained
"mu06", Modified to ✓
also be used.
sbReplacementType sbReplacementType.
S1-00294 Content of the element Decide whether to use the element Not applicable for Civil Aviation applications.
<productIntroName> <productIntroName>.
S1-00295 Use of the element Decide whether and how to use the Not applicable for Civil Aviation applications.
<productAndModel> element <productAndModel> and its
child elements.
<dataRestrictions> in the element <dataRestrictions> and its child
element <frontMatterTitlePage> elements.
<enterpriseSpec> in the element element <enterpriseSpec>.
<frontMatterTitlePage>
S1-00298 Use of the element Decide whether to use the element Not applicable for Civil Aviation applications.
<enterpriseLogo> <enterpriseLogo> and if it is populated
from the element <logo> given in the
Identification and status section.
S1-00299 Method of populating the Decide whether and how to use the Not applicable for Civil Aviation applications.
element <publisherLogo> element <logo> in the Identification and
status section to populate the element
<publisherLogo>.
S1-00300 Use of the attribute Decide whether to use the attribute Not applicable for Civil Aviation applications.
barCodeSymbology barCodeSymbology and which barcode
symbology to be used.
<frontMatterInfo> element <frontMatterInfo> including the
allowed values of attribute
frontMatterInfoType and their
interpretation as titles at presentation.
Note
BRDP BREX
Number Rule
The content given in the element <title>
takes precedence over the interpretation
of the value of attribute
frontMatterInfoType.
S1-00302 Use of the element <title> in the Decide whether to use the content of the Not applicable for Civil Aviation applications.
element <frontMatterInfo> element <title> or the interpretation of the
value of the attribute frontMatterInfoType
as the title of the Front matter
information.
S1-00303 Use the element <reducedPara> Decide whether to use the introductory Not applicable for Civil Aviation applications.
in the element paragraph and on the wording of any
<frontMatterTableOfContent> standard phrase.
S1-00304 Use of hierarchical Table of Decide whether to use a hierarchical Not applicable for Civil Aviation applications.
contents Table of contents and on the number of
levels.
S1-00305 Use of the element <pmRef> in Decide whether publications have to be Not applicable for Civil Aviation applications.
the element <tocEntry> listed by the publication only or also by its
individual data modules.
S1-00306 Use of issue number and/or Decide whether to use and present the Not applicable for Civil Aviation applications.
issue date in the Table of issue number
contents (<issueInfo>/<externalPubIssueInfo>)
and/or the issue date
(<issueDate>/<externalPubIssueDate>)
for the entries in the Table of contents.
<numberOfPages> in the <numberOfPages> and if the number of
element <tocList> pages are to be presented.
S1-00308 Use of HIGH with updating Decide whether to use HIGH with Not applicable for Civil Aviation applications.
instruction updating instruction.
S1-00309 Use the element <reducedPara> Decide whether to use the introductory Not applicable for Civil Aviation applications.
in the element paragraph and on the wording of any
<frontMatterLists> standard phrase for each of the front
matter list.
S1-00310 How to store total number of Decide on the use of <footnoteRemarks> Not applicable for Civil Aviation applications.
pages for S1000D publications to store the total number of pages for a
complete S1000D publication (PM).
S1-00311 How to store total number of Decide on the use of <footnoteRemarks> Not applicable for Civil Aviation applications.
pages for non-S1000D to store the total number of pages for a
publications complete non-S1000D publication.
BRDP BREX
Number Rule
S1-00312 Use of the attribute Decide whether to use the attribute No Civil Aviation Business Rule.
scoEntryType scoEntryType, which values to use and
S1-00313 Use of the element Decide whether and how to use the No Civil Aviation Business Rule.
<contentDescription> in the element <contentDescription> (eg, to add
element <scoContent> information about the training resource).
S1-00314 Use of the element Decide whether and how to use the No Civil Aviation Business Rule.
<contentDescription> in the element <contentDescription> (eg, to add
element <trainingStep> information about the content defined in
the training step).
S1-00315 Use of the element Decide whether the optional element No Civil Aviation Business Rule.
<contentDescription> <contentDescription> must be used to
add information about the content
defined in the training step.
S1-00316 Use of the element <applic> in Decide how to use the element <applic> This remains a project specific decision but the following
the data module status and and to populate its child elements and guidelines have to be considered:
content attributes across the project.
- Consistent population of applicability annotations:
For a given element in a given DM, applicability may be
optional. It is up to the project to decide if applicability has to
be systematically populated at a given level or not. In case of
no systematic applicability population, the applicability of the
DM or of the parent element has to be taken into account.
- Consistent population of elements and attributes from an
applicability annotation (element <applic>), i.e. consistent use
of displayed text and/or formula:
The applicability annotations can be composed either of text to
be displayed, or of a computable formula with assertions or
both.
Although no rule is enforced because of legacy data,a formula
should be used wherever possible.
Options for a systematic formula would be to:
- either provide a generic assertion in the formula which
corresponds to "All A/C"
- or provide a textual assertion in the formula in the element
<assert> content.
BRDP BREX
Number Rule
S1-00317 Use of the element Decide whether the element The following two cases are to be considered:
<displayText> in the element <displayText> is populated by the 1) The human readable applicability annotation to be
<applic> technical author or generated from the displayed can be calculated from the computable formula:
computable branch or some other source The project can choose to generate systematically the element
when using the human readable branch <displayText> or not.
of applicability. If the element <displayText> is not generated, it is up to the
IETP to generate the human readable applicability annotation
from the computable formula.
2) The human readable applicability annotation to be
displayed is manually authored:
The manual authoring of the human readable applicability
annotation shall only be used:
- to summarize a complex formula, or
- when no formula is possible.
If the applicability annotation is manually authored, the
element <displayText> has to be populated.
In any case, if <displayText> is used, it must not contradict the
computable applicability annotation.
S1-00318 Use of the attribute Decide whether to use the attribute If the element <displayText> is not generated or populated, it
applicDisplayClass within the applicDisplayClass, when using the is up to the project to decide whether attribute
element <applic> computable applicability annotation applicDisplayClass needs to be used or not.
branch.
If used, the following values shall be used:
"confirmed" for assertions without conditions. By comparison
to ATA iSpec 2200, it could correspond to assertions that are
equivalent to <effect>/@effrg.
"conditional" for assertions with conditions. By comparison to
ATA iSpec 2200, it could correspond to assertions that are
equivalent to <sbeff> or <coceff>. It also concerns operational
condition assertions.
The project can define additional values if necessary.
S1-00319 Use of textual applicability Decide if textual applicability annotations The use of textual applicability annotations is allowed but
annotations in the element are allowed in the element <assert> remains a project specific decision.
<assert> in the element when using the computable applicability
<evaluate> annotation branch or if every element In terms of filtering and display, a textual assertion has to be
<assert> should reference a declared always evaluated as true and thus has to be systematically
product attribute or condition. displayed (if the rest of the formula is evaluated as true).
Recommendation: the textual applicability statement must be
BRDP BREX
Number Rule
worded so that it implies a true or false answer. E.g. "If
window is scratched" and MSN 001.
S1-00320 Use of the attribute valuePattern Decide whether to specify the allowable This remains a project specific decision but when used the
and the element <enumeration> values for a product attribute achieved by following rules have to be applied:
or to use open text when using using both the attribute valuePattern and
ACT the element <enumeration> or to allow For a given product attribute defined in the ACT, either an
open text without using the attribute enumeration or a value pattern or an open text is allowed. The
valuePattern and the element combination of enumeration and value pattern is not allowed.
<enumeration>.
<displayName> in the element <displayName>.
<productAttribute> when using
ACT
S1-00322 Method of defining multiple Decide whether to use a single element No Civil Aviation business rule.
values or ranges for the element <enumeration> containing the entire set
<enumeration> in the ACT or to use multiple elements
<enumeration> where each contains only
one value or range.
S1-00323 Use of the attribute valuePattern Decide whether to specify the allowable Only one of <enumeration>, valuePattern, or open text may be
and the element <enumeration> values for a product attribute achieved by used for a given condType. Open text is not recommended.
or to use open text when using using both the attribute valuePattern and
CCT the element <enumeration> or to allow
open text without using the attribute
valuePattern and the element
<enumeration>.
S1-00324 Method of defining multiple Decide whether to use a single element No Civil Aviation business rule.
values or ranges for the element <enumeration> containing the entire set
<enumeration> in the CCT or to use multiple elements
<enumeration> which each contain only
one value or range.
<displayName> in the element <displayName>.
CCT
S1-00326 Constraining conditions by use Decide whether to constrain allowable No Civil Aviation business rule.
of the element <dependency> in conditions based on other condition
the element <cond> in the CCT values by use of the element
<dependency>.
S1-00327 Product attributes and Decide which product attributes and The following minimum set of civil aviation standard product
conditions to include in the PCT conditions to include in the PCT. attributes and condition types are defined. This definition is
Conditions that represent operational or based on the current ATA standard. All the product attributes
environmental properties will usually not do not have to be used.
BRDP BREX
Number Rule
be included in the PCT as they are not
associated with a product instance. Product instance identifiers
1. Manufacturing serial number (MSN): product attribute id =
msnbr
2. Customer Effectivity Code: product attribute id = cec
In case of consortiums, customer should be associated to the
customer effectivity code to ensure the uniqueness. The
current ACT schema does not allow association between
product attributes.
The following options are possible:
- Prefix the customer effectivity code with the customer code.
- Use MSN instead of CEC in the applicability annotations.
- Create a product attribute for the customer.
3. Model: product attribute id = model
4. Model Type: product attribute id = modtype
5. Aircraft Registration number: product attribute id = acn
6. Line Number: product attribute id = linenbr
7. Variable Engineering Number: product attribute id = venbr
Product instance properties
1. Aircraft nomenclature.
Attributes need to be defined to discriminate Product major
configurations (e.g. Product families). The definition of these
high-level aircraft nomenclature product attributes is left to the
project.
2. Aircraft basic engineering number: product attribute id =
benbr
3. Engine: product attribute id = esnbr (engine set number) or
enbr (engine number) depending on the engine data
granularity level. (only applies to Aircraft ACT)
4. Component: product attribute id = cmpset or cmp
depending on the component data granularity level.
5. Operator: product attribute id= operator
6. Part Number: product attribute id = pnr
7. Manufacturer Code: product attribute id = mfr
Product instance properties
1. Aircraft nomenclature.
BRDP BREX
Number Rule
Attributes need to be defined to discriminate Product major
configurations (e.g. Product families). The definition of these
high-level aircraft nomenclature product attributes is left to the
project.
2. Aircraft basic engineering number: product attribute id =
benbr
3. Engine: product attribute id = esnbr (engine set number) or
enbr (engine number) depending on the engine data
granularity level. (only applies to Aircraft ACT)
4. Component: product attribute id = cmpset or cmp
depending on the component data granularity level.
5. Operator: product attribute id= operator
6. Part Number: product attribute id = pnr
7. Manufacturer Code: product attribute id = mfr
Condition types
1. Service bulletins: condition type id = sb, enumeration =
PRE|POST|Rejected|Scheduled|Embodied|NotReported
Only one of the sets PRE|POST or
Rejected|Scheduled|Embodied|NotReported may be used in a
project’s SB conditions in its PCT.
The only allowable service bulletin applicability assertion
values for DMs are "PRE" and "POST".
When using Rejected|Scheduled|Embodied|NotReported in a
PCT, the service bulletin applicability assertion value of:
• PRE resolves to true if the SB condition is Rejected, or
• PRE resolves to false if the SB condition is Embodied, or
• POST resolves to true if the SB condition is Embodied, or
• POST resolves to false if the SB condition is Rejected, or
• PRE and POST each resolve to true if the SB condition is
Scheduled or NotReported.
NOTE: When using
Rejected|Scheduled|Embodied|NotReported in a PCT be
aware that this use diverges from the evaluation rules in
S1000D chapter 7.8.
When using PRE|POST in a PCT, the service bulletin
applicability assertion value of:
• PRE resolves to true if the SB condition is PRE, or
• PRE resolves to false if the SB condition is POST, or
BRDP BREX
Number Rule
• POST resolves to true if the SB condition is POST, or
• POST resolves to false if the SB condition is PRE, or
• PRE and POST each resolve to true if the SB condition is
null or missing.
2. Customer Originated Change condition type id = coc
3. Engineering orders: condition type id = eo, enumeration =
PRE|POST|Scheduled|Embodied
"PRE" and "POST" values shall only be used in element
<applic>.
"Scheduled" and "Embodied" values shall only be used in
element <product> of the PCT.
The BREX can be used to enforce this rule.
4. Modification: condition type id = mod
5. Flight qualification (ETOPS, …): condition type id = fqual or
opsreg (for operation
regulations) or regcond (for regulation conditions),
enumeration = TRUE|FALSE
Projects are allowed to add other product attributes or
condition types.
S1-00328 Translation of the "S1000D Decide whether to translate and use the No Civil Aviation business rule.
interpretation" of configurable "S1000D interpretation" of configurable
attribute values attribute values in the languages adopted
by the project.
Note
At no time must a project allocate values
outside the ranges given in the
subchapters.
S1-00329 Application of project specific Decide whether to use any project Project-configurable attribute values and their meanings shall
values for configurable attributes specific attribute values, which values to be registered by TDWG and published in Appendix A of ATA
use and allocate suitable definitions and Spec 1000BR. Projects may not use a registered value for
interpretations. other than its stated meaning. Projects may request additional
project-configurable attribute values. See instructions in
Note Appendix A.
There are specific business rules
decision points for some of the
configurable attributes given in the
authoring chapters. Refer to Chap 3.9.5
and its subchapters.
BRDP BREX
Number Rule
S1-00330 Application of project specific Decide if any project specific attribute No Civil Aviation business rule.
values for the attribute values are needed for the attribute
quantityUnitOfMeasure quantityUnitOfMeasure. If needed,
decide which project specific values to
use for the attribute
quantityUnitOfMeasure and allocate
S1-00331 Data module coding strategy Decide on the data module coding No Civil Aviation business rule.
strategy to use for the Product and/or the
project.
S1-00332 Allocation of Product model Decide which model identification codes No Civil Aviation business rule.
identification code to use for the Product.
S1-00333 Allow the use of one or several Decide whether to allow the use of one or No Civil Aviation business rule.
model identification codes several model identification codes.
S1-00334 Allocation of system difference Decide which system difference code No Civil Aviation business rule.
code values to be used for the Product.
S1-00335 UOC as system difference code Decide whether to use UOC as the No Civil Aviation business rule.
system difference code.
S1-00336 Product SNS structure Decide which SNS structure to use for The ATA iSpec 2200 SNS, or both the S1000D "Air vehicle,
the Product. engines and equipment" and S1000D "Maintained SNS -
Generic" SNSs shall be used.
S1-00337 Use of material item category Decide on the use of the material item For Civil Aviation projects which use the "Air vehicle, engines
code category code. and equipment" SNS (Chapter 8.2.5), for System 42, Chapter
8.2.5 Table 26 shall be used. For System 46, Chapter 8.2.5
Table 31 shall be used. In joint civil/defense programs, the
Material Item Category Code "J" shall be used for Systems 42
and 46 in Civil Aviation data modules, and "E" shall be used
for Systems 42 and 46 in Defense data modules. All other
usage of Material Item Category Code is optional.
S1-00338 Number of characters in Decide whether to use two or four Either 2 or 4 digit SNS assembly codes are allowed. Numbers
assembly code characters for unit or assembly. beginning with 9000 and up are reserved for airline data
modules.
S1-00339 Responsible partner company Decide which responsible partner Not applicable for Civil Aviation applications.
codes for non-chapterized company codes to use for non-
illustrated parts data modules chapterized illustrated parts data
modules.
S1-00340 Responsible partner company Decide which responsible partner No Civil Aviation business rule.
codes for non-chapterized, non- company codes to use for non-
S2000M illustrated parts data chapterized, non-S2000M illustrated
modules parts data modules.
BRDP BREX
Number Rule
S1-00341 Unique identifier for non- Decide which unique identifiers to use for No Civil Aviation business rule.
chapterized, non-S2000M non-chapterized, non-S2000M illustrated
illustrated parts data modules parts data modules.
S1-00342 Use of the disassembly code Decide whether to use one, two or three One, two, or three characters may be used. The values "Z",
variant characters for the disassembly code
variant and how to populate.
"ZZ" and "ZZZ" are reserved for the container data modules. ✓
S1-00343 Use of numeric values in the Decide whether to use numeric values in Numeric values are not allowed. The value "Z" is reserved for
information code variant addition to alphabetic values in the
information code variant.
the container data module. ✓
S1-00344 Use of CAGE code and/or Decide which method to be used for the No Civil Aviation business rule.
model identification code based ICN.
ICN
S1-00345 Presentation of ICN within the Decide whether the ICN is presented The ICN must be presented. For page-oriented publications,
illustration reproduction area within the illustration reproduction area. the ICN must be presented outside the illustration reproduction
area. Optionally, the ICN may also be presented inside the
illustration reproduction area.
S1-00346 Security classifications to be Decide whether to use the project´s or No Civil Aviation business rule.
used for CAGE code based ICN the originator's classification rules.
S1-00347 Structure and rules for ICN for Decide which structure to use for the ICN No Civil Aviation business rule.
model identification code based (eg, only numerical, fixed length, use of
ICN character set).
S1-00348 Allocation of responsible partner Decide which values on responsible No Civil Aviation business rule.
company codes for model partner company codes to be used.
identification code based ICN
S1-00349 Security classifications to be Decided which security classifications to No Civil Aviation business rule.
used for model identification use.
based ICN
S1-00350 Use of data management Decide whether to use the data No Civil Aviation business rule.
requirement list management requirement list for
specification and exchange of CSDB
planning information.
S1-00351 Object types to be listed in the Decide whether to list publication No Civil Aviation business rule.
data management requirement modules and/or IPD illustrations in the
list data management requirement list.
S1-00352 Use of CSDB status list Decide whether to use the CSDB status The CSDB status list (CSL) must be provided with each
list for exchange of CSDB status exchange package when Publication Modules are not used.
information. The CSL may be provided when Publication Modules are
used.
S1-00353 Objects types to be tracked by Decide what CSDB objects types are to No Civil Aviation business rule.
the CSDB status list be tracked in the CSDB status list, and at
a minimum these must be data modules,
BRDP BREX
Number Rule
illustrations/multimedia objects and
publication modules.
S1-00354 CSDB object issues to be Decide whether to include only the latest No Civil Aviation business rule.
included in the CSDB status list issues of CSDB objects or all issues in
the CSDB status list.
S1-00355 Data management requirement Decide whether the issue date of a data No Civil Aviation business rule.
list issue date management requirement list must be
the input date (the release to CSDB
date), the cut-off date for the information,
the planning date or some other more
appropriate date.
S1-00356 Use of the comment form Decide whether to use the comment The comment form shall not be used.
form. ✓
S1-00357 Use of attribute commentPriority Decide which values to use for the The element <commentPriority> shall not be used. See
attribute commentPriority and allocate BRDP-S1-00356.
suitable definitions. Refer to Chap
3.9.6.1.
S1-00358 Use of the attribute Decide which values to use for the The attribute responseType shall not be used. See BRDP-S1-
responseType in the element attribute responseType and allocate 00356.
<commentResponse> suitable definitions. Refer to Chap
3.9.6.1.
S1-00359 Allowed file types for Decide which file types are allowed for No attachments are allowed. See BRDP-S1-00356.
attachments to comment forms attachments to comment forms.
S1-00360 Raster graphic resolution Decide which resolution to use for raster No Civil Aviation business rule.
graphics.
S1-00361 Use of photographs Decide whether photographs will be The use of photographs is permitted in accordance with the
used. If used, for what purposes. ATA iSpec 2200 3-1-12.4 Graphic Style Standards.
S1-00362 Use of logotypes in the Decide whether logotypes are used in No Civil Aviation business rule.
publication module the publication module and the usage in
front matter data module.
<systemBreakdownCode> in the <systemBreakdownCode>. If used,
publication module status define the content of the element
information consistent across the project.
S1-00364 Use of the element <remarks> Decide whether to use the element No Civil Aviation business rule.
in the publication module status <remarks>. If used, its use must be
information defined in the project business rules and
guidance given.
S1-00365 Use of the attribute pmIssuer Decide on the use of the attribute CAGE Code shall be used.
pmIssuer.
BRDP BREX
Number Rule
S1-00366 Use of a project specific BREX Decide whether to develop and use a No Civil Aviation business rule.
data module project specific BREX data module.
S1-00367 Use of layered BREX data Decide whether to apply a layered BREX No Civil Aviation business rule.
modules data module structure. This decision is
related to, but not entirely dependent on,
whether a layered business rules
structure applies.
S1-00368 Applicable sets of business Decide which set or sets of business No Civil Aviation business rule.
rules rules are allowed within the given project
or the organization. Accordingly, decide
which BREX data modules will be used
to reflect those business rules.
S1-00369 Use of the BREX data module to Decide whether to use the BREX data No Civil Aviation business rule.
exchange SNS module for exchange of information on
the applied SNS.
S1-00370 Include restrictions in using Decide whether to use the BREX data The BREX shall not be used to impose restrictions on the
various illustration, multimedia module to impose any restrictions in the formats for graphic/multimedia objects.
object or other data information use of various formats for illustrations,
formats multimedia objects or other data.
S1-00371 Use of the process data module Decide whether to use the process data Process data modules shall not be used.
module. ✓
S1-00372 Use of the generic IC 951 for Decide whether to use IC 951 for IC 951 shall not be used.
identification of process data identification of process data modules.
modules
S1-00373 Use of multiple instances of Decide whether to generate multiple No Civil Aviation business rule.
CSDB object instances of CSDB objects to generate
several customized instances of any one
object issue. If so, decide how the
attributes extensionProducer and
extensionCode must be used.
S1-00374 Use of the CIR concept (internal Decide whether to use the CIR concept. No Civil Aviation business rule.
databases for common
information)
S1-00375 Use of CIR data modules Decide whether to produce CIR data No Civil Aviation business rule.
modules.
S1-00376 Internal/External use of CIR Decide whether the CIR data modules CIR data modules may be provided as deliverables to the
data modules are to be used only internally to the customer.
manufacturer or integrator, as part of the
production/integration environment
("internal repositories") or if the CIR data
BRDP BREX
Number Rule
modules are also a deliverable to the
customer.
S1-00377 Types of CIR data modules to Decide which CIR data module types to No Civil Aviation business rule.
be used be used. In order to avoid any
redundancy and inconsistency, care must
be paid on some types, depending on
other project specific decisions, for
example tailoring of the S2000M (IPD
data modules vs Part CIR data module).
S1-00378 Delivery of CIR-dependent data Decide whether CIR-dependent data CIR-dependent data modules may be delivered to the
module modules are delivered to customer, as it customer. If CIR-dependent data modules are delivered, then
implies a specific process to retrieve the the corresponding CIR data modules must also be delivered.
self-standing data modules from the CIR-
dependent data module and the CIR data
module.
S1-00379 Publishing of CIR data modules Decide whether and which CIR data No Civil Aviation business rule.
module types to be published.
S1-00380 Use of one or several data Decide whether there is one single or No Civil Aviation business rule.
modules for a CIR type several data modules for a dedicated
type of CIR data module within a Project
or for a specific model identification code.
S1-00381 Use of implicit or explicit Decide whether to use implicit or explicit No Civil Aviation business rule.
reference method to CIR data references, or both between content
module specific data elements and the CIR data
modules.
Note
It is recommended to use only one
method to avoid difficulties which might
appear during the publishing process.
S1-00382 Use of alternates groups in data Decide whether to use alternates group No Civil Aviation business rule.
module content elements. If used, which groups and in
which data modules types.
S1-00383 Mix of alternates groups and Decide whether alternates groups and Intermixing of alternates groups and elements at a given level
elements elements can be mixed in a given
structure.
of the XML hierarchy is not allowed. ✓
S1-00384 Use of container data modules Decide whether to use container data No Civil Aviation business rule.
modules.
S1-00385 Identification of container data Decide which identification method to use The data module code must be the common data module
module for container data modules. The chosen
method must be used systematically.
code of all the alternates,
- with "Z", “ZZ”, or "ZZZ" set in the disassyCodeVariant
✓
BRDP BREX
Number Rule
attribute and
- "Z" set in the infoCodeVariant attribute.
Example:
Container DM AE-A-42-21-06-01Z-720Z-A
Alternate 1 DM AE-A-42-21-06-01A-720A-A
Alternate 2 DM AE-A-42-21-06-01B-720A-A
S1-00386 Use of applicability within Decide whether applicability annotations If the container DM is delivered as part of the exchange
container data module content are duplicated from the referenced data package, applicability shall be duplicated from the referenced
modules to the container data module. data modules to the container data module.
S1-00387 Use of applicability Decide if the project will use applicability. Civil Aviation must use applicability.
S1-00388 Applicability functionality Define the required functionality for The full range of applicability functionality is allowed. At the
applicability. aircraft level, filtered applicability must be used.
S1-00389 Use of applicability data module If functionality is limited to print and static For filtered applicability at the aircraft level, ACT, CCT and
types (ACT, CCT, and PCT) display, decide if applicability data PCT DMs are required. CCT must contain at least the list of
module types (ACT, CCT, and PCT) will condition types.
be used.
For projects using static applicability, population of
<displayText> only in applicability annotations is sufficient.
S1-00390 Product attribute and conditions Define a consistent naming and Refer to Business Rule S1-00327 for a list of product attribute
naming and identification identification scheme for product and condition type names.
scheme attributes and conditions, when ACT and
CCT data modules are implemented.
S1-00391 Presentation of content that is Specify the method that content is No Civil Aviation business rule.
not applicable presented which is not valid for the
current maintenance context. The
content can be removed, hidden or de-
emphasized in some manner.
S1-00392 Providing the human readable Decide whether to also provide the Refer to BRDP-S1-00317.
part of applicability human readable part of applicability or
rely on the viewer to build the human
readable part, when providing the
computer processing part of applicability.
S1-00393 Number of ACT, CCT and PCT Decide whether to provide one instance This remains a project specific decision but multiple instances
data module instances of each data module types (ACT, CCT are allowed. Method for segregation must follow the Product
and PCT) or to segregate the project into breakdown (e.g. an aircraft family, an Engine model, a
multiple instances of each data module component…). A product instance must be described in only
type, and the method for segregation. one PCT.
S1-00394 Classifying product attributes Decide how to divide the properties of the This remains a project specific decision. A minimum set of
and conditions an ACT data Product into product attributes or product attributes and condition types has been defined (Refer
module condition types. to BRDP-S1-00327).
BRDP BREX
Number Rule
For project specific data, it is up to the project to define if it is a
product attribute or a condition type.
S1-00395 Configuration management of Decide on the extent of configuration It is allowed to add product attribute values or new product
product attributes an ACT data management and editing access to be attributes.
module applied to product attributes within an It is not allowed to change product attribute names without
ACT data module. advance communication and agreement with customers.
Communication 6 months before the change is recommended.
S1-00396 Use of the incorporation status Decide whether to use the incorporation No Civil Aviation business rule.
list in a CCT data module status list in the CCT data module.
S1-00397 Scope of the product instances Decide which product instances are This remains a project specific decision.
in a PCT data module contained in a PCT data module. Options Some DMs may be customized for each customer (e.g.
include listing all product instances in proced) and some may be not be customized (e.g. Schedule).
service or listing only the product
instances within an organization. It is recommended:
- to deliver only the customer product instances in the PCT
(Applies to aircraft) or
- to deliver all product instances in the PCT where specific
customer information is not specified. (Applies to engine and
component).
S1-00398 Use of a published or a transient Decide whether to publish a static issue For projects requiring filtered applicability as described in
PCT data module of the PCT data module or use the data BRDP-S1-00389, the PCT must be delivered in its XML form.
module as a transient transfer
mechanism between an external system
and a viewer.
S1-00399 Management of the product Decide how to maintain the list of product No Civil Aviation business rule.
instance configurations in PCT instance configuration specifications and
data modules the associated values for product
attributes and conditions.
S1-00400 Use of the ACT catalog data Decide whether to use the ACT catalog No Civil Aviation business rule.
module data module.
S1-00401 Internal or external definition of Decide whether the supplier applicability No Civil Aviation business rule.
supplier applicability attributes attributes are defined in the ACT data
module or if the supplier definition is
used.
S1-00402 Use of attribute scoEntryType Decide whether to use the attribute No Civil Aviation business rule.
scoEntryType to indicate the required
resource type.
S1-00403 Technical information object Decide which properties associated to No Civil Aviation business rule.
properties to be included in the the technical information objects (eg,
data module at delivery names, short names) to store within the
data module when delivered.
BRDP BREX
Number Rule
S1-00404 Determine applicable systems Decide the applicable systems for land Not applicable for Civil Aviation applications.
for land and sea products and sea products.
S1-00405 How to use the element field Decide how to use the element field Not applicable for Civil Aviation applications. Refer to BRDP-
descriptions in the wiring data descriptions of the wiring data description S1-00238.
description Schema Schema in an interactive wiring
publication.
S1-00406 Use of introduction data Decide whether to produce introduction No Civil Aviation business rule.
modules for wiring publications data modules for wiring publications. If
required, the scope of these introduction
data modules must be defined.
S1-00407 Optional descriptive information Decide whether to produce descriptive No Civil Aviation business rule.
for connection units information for connection units including
illustrations and tables.
S1-00408 Optional descriptive information Decide whether to produce descriptive No Civil Aviation business rule.
for wires and harnesses information for wires and harnesses
including illustrations and tables.
S1-00409 Wiring standard practices data Define source and scope of wiring Descriptive data modules must not be used to deliver
modules standard practices data modules. Decide procedural information.
whether to prepare standard wiring
practice information as procedural or
descriptive data modules.
S1-00410 Wiring diagrams in an Decide whether to produce wiring No Civil Aviation business rule.
interactive wiring publication diagrams for an interactive wiring
publication.
S1-00411 Harness routing drawings Decide whether harness routing drawings No Civil Aviation business rule.
are to be simplified and how their layout
must look like.
S1-00412 Coding of harness installation Decide whether to code harness No Civil Aviation business rule.
drawing data modules installation drawing data modules by
using zone information. If decided to use
zone information for the coding, the
structure of the data module code is
possibly not appropriate. In this case, it
must be decided on changes of the
proposed structure for the Product (eg,
population of the zone information in the
unit or assembly group of the SNS
instead of in the subsystem/sub-
subsystem group).
S1-00413 Harness installation information Decide whether to prepare harness No Civil Aviation business rule.
installation information for each major
area in list form in addition to or instead
BRDP BREX
Number Rule
of harness installation and routing
drawings.
S1-00414 Coding of harness routing Decide whether to code harness routing No Civil Aviation business rule.
drawing data modules drawing data modules by using zone
information. If decided to use zone
information for the coding, the structure
of the data module code is possibly not
appropriate. In this case, it must be
decided on changes of the proposed
structure for the Product (eg, population
of the zone information in the unit or
assembly group of the SNS instead of in
the subsystem/sub-subsystem group).
S1-00415 Equipment and panel location Decide whether to produce separate data No Civil Aviation business rule.
drawings modules containing equipment and panel
location illustrations.
S1-00416 Production of electrical standard Decide whether to produce data modules No Civil Aviation business rule.
parts data containing electrical standard parts data.
S1-00417 Definition of required electrical Define the required information for each No Civil Aviation business rule.
equipment information electrical or electronic item of equipment
that has electrical connections.
S1-00418 Coding of electrical equipment Decide whether to code electrical No Civil Aviation business rule.
information data modules equipment information data modules by
using zone information. If decided to use
zone information for the coding, the
subsystem group).
S1-00419 Coding of harness data modules Decide whether to code harness data No Civil Aviation business rule.
modules by using zone information. If
decided to use zone information for the
coding, the structure of the data module
code is possibly not appropriate. In this
case, it must be decided on changes of
the proposed structure for the Product
(eg, population of the zone information in
the unit or assembly group of the SNS
BRDP BREX
Number Rule
subsystem group).
S1-00420 Generation of harness wire list Decide whether and how to generate No Civil Aviation business rule.
data modules harness wire list data modules for a
page-oriented or an interactive wiring
publication from the wiring data modules
that are based on the wiring Schema.
S1-00421 Generation of connection list Decide whether and how to generate No Civil Aviation business rule.
data modules connection list data modules for a page-
oriented or an interactive wiring
S1-00422 Generation of plug and Decide whether and how to generate No Civil Aviation business rule.
receptacle list data modules harness plug and receptacle list data
modules for a page-oriented or an
interactive wiring publication from the
wiring data modules that are based on
the wiring Schema.
S1-00423 Generation of terminal list data Decide whether and how to generate No Civil Aviation business rule.
modules terminal list data modules for a page-
S1-00424 Generation of splice list data Decide whether and how to generate No Civil Aviation business rule.
modules splice list data modules for a page-
S1-00425 Generation of earth point list Decide whether and how to generate No Civil Aviation business rule.
data modules earth point list data modules for a page-
S1-00426 Use of separate modules or the Decide if front matter is to be authored as The Front Matter schema shall not be used.
consolidated Front matter separate modules or use the
Schema for Equipment consolidated Front matter Schema. ✓
information sets
S1-00427 Level of detail to be provided in Decide what level of detail to provide in No Civil Aviation business rule.
the technical descriptions in the functional and technical descriptions.
Equipment information sets
BRDP BREX
Number Rule
S1-00428 Use of wiring Schema in Decide whether the Wiring data Schema The Wiring Data Description schema is not applicable for Civil
Equipment information sets and the Wiring data description Schema Aviation applications. Refer to BRDP-S1-00238. No Civil
are to be used or not. Interactive wiring Aviation business rule for the Wiring Data schema.
publication functionalities are only to be ✓
made available if the Wiring Schema is
used. Refer to Chap 3.9.5.2.9.
S1-00429 Level of detail to be provided in Decide what level of detail to provide in No Civil Aviation business rule.
the maintenance and servicing the maintenance and servicing data
data modules in Equipment modules.
information sets
S1-00430 Use of lists in Equipment Decide how to implement the lists of No Civil Aviation business rule.
information sets consumables, materials, expendables,
standard SE, special SE and tools.
S1-00431 Use of equivalent substitutes in Decide whether to use equivalent Equivalent substitutes shall be allowed. If substitute equipment
Equipment information sets substitutes for consumables, materials, and materials can be used, the phrase, "equivalent substitutes
expendables equipment and tools. may be used" shall be included.
S1-00432 Level of detail to be provided in Decide what the level of detail to provide No Civil Aviation business rule.
the IPD data modules in in the IPD modules.
thru S1-
00435
S1-00436 Use of external material Decide whether material information No Civil Aviation business rule.
information in service bulletins must be a part of the "core" SB data
module or if it can (depending on the
volume) be presented in one or more
referenced separate SB data modules.
Refer to Fig 2.
S1-00437 Treatment of alert and standard Decide whether or not to allow classifying Service Bulletins may be classified as Alert. Refer to ATA
service bulletins service bulletins as Alert. iSpec 2200 chapter 3-3-4.1.1.
S1-00438 Service bulletin compliance Decide whether to use the four Refer to Appendix A, Civil Aviation Attribute Values.
categories compliance categories or to define
others.
S1-00439 Minimum impact on weight in Decide the threshold for minimum impact The minimum impact on weight shall be in accordance with
service bulletins on weight that must be reported in a SB. ATA iSpec 2200 chapter 3-3-4.3.2.8.
S1-00440 Minimum impact on balance in Decide the threshold for minimum impact The minimum impact on weight shall be in accordance with
service bulletins on balance that must be reported in a ATA iSpec 2200 chapter 3-3-4.3.2.8.
SB.
S1-00441 Minimum impact on electrical Decide the threshold for minimum impact Reporting impact on electrical load shall be in accordance with
load to be reported in service on electrical load that must be reported in ATA iSpec 2200 chapter 3-3-4.3.2.9.
bulletins a SB.
BRDP BREX
Number Rule
S1-00442 Definitions and use of Decide on the precise definitions of All affected publications shall be provided in a single list,
maintenance and operational "maintenance publications" and therefore precise definitions of "maintenance publications" and
publications in service bulletins "operational publications" and whether to "operational publications" are not necessary.
separate them into different listings in the
Impact on publications.
S1-00443 Scope and depth of planning Agree on the scope and depth of the No Civil Aviation business rule.
information data modules for planning information.
training information sets
S1-00444 Scope and depth of training Agree on scope and depth of the training No Civil Aviation business rule.
information data modules for information.
S1-00445 Use of a full set of data modules Decide whether to use a full set of data No Civil Aviation business rule.
or a publication module for the modules or a publication module to carry
LOAP the listing of the applicable publications
and other documents including individual
data modules.
S1-00446 Schema to use for the Decide whether to use the Front matter The Front Matter schema shall not be used.
publication list data modules of
the LOAP
Schema or the Descriptive Schema for
the publication list data modules.
✓
S1-00447 One consolidated or several Decide whether to deliver the No Civil Aviation business rule.
separate publication list data publications and documents listed in one
modules for the LOAP data module/publication module (with
one or more lists presented as tables) or
as separate data modules/publication
modules (eg, by operational publications
or maintenance publications).
S1-00448 Inclusion of unpublished Decide whether to include publications No Civil Aviation business rule.
publications and documents in and documents that are not published.
the LOAP
Note
When used as a contractual document,
all publications and documents,
published or not, must be included.
S1-00449 Markup of the publication entry Decide whether to markup the publication No Civil Aviation business rule.
as a link in the LOAP entry as a link when using the Descriptive
Schema.
S1-00450 Include the manufacturer’s part Decide whether to include and present No Civil Aviation business rule.
No. or reference No. in the the manufacturer’s part No. or reference
LOAP No.
BRDP BREX
Number Rule
S1-00451 Use of language in the LOAP Decide whether to include and present No Civil Aviation business rule.
the language of the publication or
document in the entries.
S1-00452 Additional information in parts Decide whether to indicate additional No Civil Aviation business rule.
lists for engine maintenance information under the heading of the
information sets parts list "Remarks" (eg, modification
number applicable to the item).
thru S1-
00459
S1-00460 Front matter to be included in Decide which front matter is to be Civil Aviation publications shall present Front Matter
page-oriented publications and included (mandatory or optional) in each information per the following table regardless of the method of
IETP, respectively of the page-oriented publications and in generation or exchange.
the IETP. The decisions must be based
on the rules given in Chap 3.9.4.
Front Matter Service Other
Information Bulletins Publications
Title page Mandatory Mandatory
List of effective Do Not Use Do Not Use
pages (LOEP)
List of effective Optional Optional
data modules
LOEDM
Change record Do Not Use Mandatory for
CR page-oriented
publications.
Optional for
IETPs
Highlights HIGH Do Not Use Mandatory
Access illustration Do Not Use Do Not Use for
for page- page-oriented
oriented publications.
publications.
Optional for Optional for
IETPs IETPs
List of Optional Optional
abbreviations
LOA
List of terms LOT Optional Optional
BRDP BREX
Number Rule
List of symbols Optional Optional
LOS
Technical Optional Optional
standard record
TSR
Table of contents Optional Mandatory for
TOC page-oriented
publications.
Optional for
IETPs
List of applicable Do Not Use Optional
specifications and
documentation
LOASD
List of support Do Not Use Optional
equipment LOSE
List of supplies Do Not Use Optional
LOSU
List of spares Do Not Use Optional
LOSP
List of illustrations Optional Optional
LOI
Product cross- Optional Optional
reference table
PCT
Conditions cross- Optional Optional
reference table
CCT
Applicability Optional Optional
cross-reference
table ACT
S1-00461 Information codes Decide which information codes to be Civil Aviation shall use the basic front matter information
used, the basic (eg, 00R) or the codes (third character alpha).
alternative (eg, 002).
S1-00462 IPD as a standalone publication Decide if the IPD is produced as a No Civil Aviation business rule.
standalone publication or as a part of for
BRDP BREX
Number Rule
example an equipment maintenance
publication.
S1-00463 Optional parts data elements in Decide which of the optional data from Not applicable for Civil Aviation applications. This BRDP
IPD the parts data must be included and pertains to parts data as defined in S2000M and Civil Aviation
which optional elements must be does not use S2000M.
displayed.
S1-00464 Use of task sets in the CMP Decide whether to use task sets in the No Civil Aviation business rule.
CMP.
S1-00465 Use of placeholder data Decide whether "placeholder" data Placeholder DMs are required in Civil Aviation.
modules in the CMP modules are required for those topics
where data is not required or necessary.
S1-00466 Front matter to be used in the Decide what front matter data modules to Civil Aviation publications shall present CMP Front Matter
CMP be used and their content. information per the following table, regardless of the method of
generation or exchange.
Page- Include in
Title include in
oriented IETP
Title page Mandatory Do Not Use
List of effective pages Do Not Use Do Not Use
List of effective data Mandatory Mandatory
modules
Change record Mandatory Do Not Use
Highlights or transmittal Mandatory Mandatory
letter
Access illustration Do Not Use Mandatory
List of abbreviations Mandatory Mandatory
List of terms Mandatory Mandatory
List of symbols Mandatory Mandatory
Technical standard Mandatory Mandatory
record
Table of contents Mandatory Mandatory
List of applicable Mandatory Mandatory
specifications and
documentation
List of support Mandatory Optional
equipment
List of supplies Mandatory Optional
BRDP BREX
Number Rule
List of spares Optional Optional
List of illustrations Mandatory Mandatory
Product cross-reference Do Not Use Do Not Use
table
Conditions cross- Do Not Use Do Not Use
reference table
Applicability cross- Do Not Use Do Not Use
reference table
S1-00467 Use of access illustration for Decide whether to include access No Civil Aviation business rule.
component maintenance IETP illustration and its format for IETP.
S1-00468 Incorporating service bulletins Decide on the updating frequency for Service Bulletins shall be incorporated into the CMP in
into the CMP incorporating service bulletins into the accordance with ATA iSpec 2200 chapter 3-1-9.
CMP.
S1-00469 Provide IPD information as a Decide whether IPD information is to be IPD information shall not be provided as a separate
separate publication for the provided as a separate publication. publication for the CMP.
CMP
S1-00470 Inclusion of maintenance Decide whether to include maintenance Maintenance planning information shall not be included in the
planning information in the CMP planning information in the CMP. CMP.
S1-00471 Inclusion of removal and Decide whether to include removal and Removal and installation information shall not be included in
installation information in the installation information in the CMP. the CMP with the exception of engines.
CMP
S1-00472 Inclusion of test support data in Decide whether to include manufacturer's Test support data shall be provided in accordance with ATA
the CMP test support data and its format. iSpec 2200 chapter 3-3-3.2.2.
S1-00473 Use of the S1000D standard Decide whether to use the S1000D S1000D Chapter 6.2.3.6 is not applicable for Civil Aviation
page-oriented presentation standard page-oriented presentation applications. Civil Aviation applications shall use Section 3-2
chapters. given in Chap 6.2.2 and Chap 6.2.3 or to of ATA Spec 1000BR for layout rules for Component
use any other rules for presentation to Maintenance data modules. No Civil Aviation business rule for
meet specific project or organization other chapters in 6.2.2 and 6.2.3.
requirements. The business rules must
specify the information needed to
contract the desired presentation.
S1-00474 Use of mirrored headers and Decide whether to use mirrored headers No Civil Aviation business rule.
footers and footers.
S1-00475 Page size Decide on the page size (including sizes No Civil Aviation business rule.
when foldouts are allowed, see below)
per publication.
BRDP BREX
Number Rule
S1-00476 Presentation of foldouts in page- Decide in what circumstances (eg, Foldouts shall only be interspersed where used in page-
oriented publications interspersed or at the end of the oriented publications. Refer to BRDP-S1-00131.
publication) is presented in page-oriented
publications.
S1-00477 Presentation of inwork markings Decide whether to present the inwork No Civil Aviation business rule.
markings. The details must be
documented.
S1-00478 Presentation of "Produced by" - Decide whether to present or not the No Civil Aviation business rule for "Produced by" information.
"Printed in" responsible producer of the page- "Printed in" information shall not be presented.
oriented output and/or where the
publication was printed.
S1-00479 Presentation of publication Decide whether to use the S1000D Publication Module Code may be presented in accordance
module code standard page-oriented presentation with S1000D standard page-oriented rules or as defined in
rules for the publication module code or Spec 1000BR Section 3-2. For publications with non-mirrored
to create project or organization specific headers, "Outside" is considered to be the right side.
rules for its positioning and style within
the header.
S1-00480 Presentation of data module Decide whether to use the S1000D With the exception of Component Maintenance Publications,
code standard page-oriented presentation S1000D standard page-oriented rules shall be adopted. For
rules for the data module code or to publications with non-mirrored footers, "Outside" is considered
create project or organization specific to be the right side.
the footer.
S1-00481 Presentation of issue date Decide whether to use S1000D standard With the exception of Component Maintenance Publications,
page-oriented presentation rules for the S1000D standard page-oriented rules shall be adopted.
issue date or to create project or
organization specific rules for its
positioning in the bottom of the footer.
S1-00482 Presentation of page number Decide whether to use the S1000D With the exception of Component Maintenance Publications,
standard page-oriented presentation S1000D standard page-oriented rules shall be adopted. For
rules for the page number or to create publications with non-mirrored footers, "Outside" is considered
project or organization specific rules for to be the right side.
its positioning in the footer.
S1-00483 Page numbering of foldout Decide whether to use double numbering Double numbering of foldout pages shall be used when they
pages of pages when printed on one (right- are presented on right side only.
hand) side only (eg, 11/12, 13/14).
S1-00484 Presentation of applicability Decide whether to use the S1000D Applicability will be expressed where used and not the in the
annotation standard page-oriented presentation footer. Multiple applicabilities may be required on the same
rules for the applicability annotation or to page.
create project or organization specific
rules for the presentation.
BRDP BREX
Number Rule
S1-00485 Presentation of security Decide whether to present the security Security markings shall not be presented.
markings markings in sentence case instead of in
uppercase.
S1-00486 Presentation of commercial Decide whether to use the commercial No Civil Aviation business rule.
classification and/or caveat as classification (value of attribute
security markings commercialClassification) and/or national
caveat (value of attribute caveat) as an
alternative to the security classification
(value of the attribute
securityClassification).
S1-00487 Exclude presentation of security Decide whether to exclude the Security markings shall not be presented.
markings for unclassified presentation of security markings for
publications unclassified publications or not.
S1-00488 Presentation of safety Decide whether to use the S1000D S1000D standard page-oriented rules shall be adopted. For
classification standard page-oriented presentation publications with non-mirrored headers, "Outside" is
rules for the safety classification (attribute considered to be the right side.
safetyLabel of the element
<productSafety>) or to create project or
organization specific rules for the
presentation.
S1-00489 Presentation of the element Decide whether to present any of the No Civil Aviation business rule.
<logo> logotypes given in the element <logo>
and how this element is presented (eg,
size, color).
S1-00490 Presentation of "End of data Decide on the text that will be used to With the exception of Component Maintenance Publications,
module" statement identify the end of a data module, either "End of data module" shall be used.
"End of data module" or "End of" followed
by the data module title.
S1-00491 Placement of the end of data Decide whether to present the "End of" No Civil Aviation business rule.
module statement statement in the footer or in the body of
the page.
S1-00492 Use of double column text Decide whether to use double column No Civil Aviation business rule.
text, and under what circumstances.
Typography for double column page
layout must be documented.
S1-00493 Double sided printing of foldout Decide whether to use double sided No Civil Aviation business rule.
pages printing on foldout pages.
Note
A3L paper in A3L binders are normally
printed on both sides.
BRDP BREX
Number Rule
S1-00494 Presentation of the procedural Decide whether to present the titles for If the titles are provided they must be presented.
step titles from the element the element <proceduralStep> and to
<proceduralStep> which level.
S1-00495 Presentation of the crew drill Decide whether to present the titles for Not applicable for Civil Aviation applications.
step titles from the element the element <crewDrillStep> and to
<crewDrillStep> which level.
Note
Presentation of the titles for steps on
level six thru level eight are not given.
The use of these elements is
discouraged and their use and
presentation are project decisions.
S1-00496 Presentation of the document Decide whether to present the document No Civil Aviation business rule.
title title as a centerhead No. 1 and a
centerhead No. 2 or as a centerhead No.
1 only (including both element
<techName> and element <infoName>).
S1-00497 Number of sidehead levels to be Decide whether to present more than No Civil Aviation business rule.
presented in the Table of three sidehead levels in the table of
contents contents.
S1-00498 Presentation of List of tables Decide whether to present the List of No Civil Aviation business rule.
tables.
S1-00499 Present the prefix "Table" in the Decide whether to present the prefix No Civil Aviation business rule.
List of tables "Table" before the table number in the
List of tables.
S1-00500 Presentation of List of figures Decide whether to present the List of No Civil Aviation business rule.
figures.
S1-00501 Present the prefix "Fig" in the Decide whether to present the prefix No Civil Aviation business rule.
List of figures "Fig" before the figure number in the List
of figures.
S1-00502 Presentation (layout) of titles Decide whether to use the S1000D No Civil Aviation business rule for type size and leading. See
standard presentation rules for titles BRDP-S1-00504 for Civil Aviation rules for justification.
(sidehead 1 thru sidehead 5 or if used
thru sidehead 8) or to create project or
organization specific rules such as type
size, leading and justification.
S1-00503 Presentation of the leveled para Decide whether to present the titles for If the titles are provided they must be presented.
titles from the element the element <levelledPara> on level six
<levelledPara> on level six thru thru eight.
eight
BRDP BREX
Number Rule
S1-00504 Use of the alternative method Decide whether to use the preferred or Civil Aviation will use the following alternative method:
for labeling procedural steps at the alternative method for labeling
presentation procedural steps. Information shall be prepared in modified block style.
Subdivisions of text shall be identified and each breakdown
shall be indented and labeled as shown by the following
example. Projects may define their own labels for indenture
levels below level 4.
1. asdf
A. asdf
(1) asdf
(a) asdf
S1-00505 Presentation of paragraphs of Decide whether to use the recommended No Civil Aviation business rule.
text presentation rules for type size, spacing
and justification.
S1-00506 Presentation of hierarchical Decide whether to use hierarchical Hierarchical indentation shall be used when steps are
indented steps, when used indented steps, when used without titles. presented without titles.
without titles in procedural steps
S1-00507 Prefixes to be used for random Decide whether to use a consistent set of The default prefix (pf02) shall be used/presented.
lists at presentation prefixes for random list throughout the
project.
✓
S1-00508 Presentation of footnote Decide whether to present the footnote Only superscript numbers may be used. Refer to BRDP-S1-
numbers markers as superscripted numbers 00173.
(default) or as numbers presented within
parenthesis.
S1-00509 Presentation of inline footnotes Decide whether to present the inline Not applicable for Civil Aviation applications. Refer to BRDP-
footnotes at the bottom of the page S1-00172.
(default) or at the end of the data
module.
S1-00510 Presentation of table footnotes Decide whether to present the footnotes No Civil Aviation business rule.
on the relevant page, if the table is split
over several pages. Refer to Fig 2 and
Fig 3.
S1-00511 Presentation of vertical lines in Decide whether to, in exceptional cases, Vertical lines in tables are permitted.
formal tables allow presentation of vertical lines in
formal table.
Note
The rendering of the table must be based
on the elements and attributes in the
XML files.
The author must apply elements and
BRDP BREX
Number Rule
attributes as defined in Chap 3.9.5.2.1.6
in order to achieve the layout described
in this chapter.
S1-00512 Use of the alternative individual Decide whether to use one of the The alternative methods are not allowed.
numbering of multi sheet alternative methods for individual
illustrations at presentation numbering of multi sheet illustrations.
The chosen method must be used
throughout the project.
S1-00513 Presentation of warnings and Decide whether to use the alternative In civil aviation applications, Warnings and Cautions within a
cautions rule to present the warnings before the Step must appear before the Step number.
step/para number.
Note
Projects must be aware of potential
hazards when allowing step numbers to
follow the warning and ensure that there
is a clear connection in the presentation
between the warning and the associated
steps.
S1-00514 Presentation of symbols in Decide whether to present symbols in No Civil Aviation business rule.
warnings and cautions warnings and cautions. The symbols
must be standardized and documented.
S1-00515 Use of symbolic presentation of Decide whether to use symbolic No Civil Aviation business rule.
warnings and cautions presentations of warnings and cautions.
S1-00516 Use of numbered notes within a Decide whether to use numbered notes Numbered notes are not allowed.
data module at presentation within a data module.
S1-00517 Display of change marks Decide whether to display change marks. Change marks shall be displayed.
S1-00518 Presentation of change marks Decide whether to use an alternative Alternative visual presentation as change marker shall not be
visual presentation as change marker allowed.
S1-00519 Presentation of change marking Decide whether to change mark Change marks shall be shown against the individual rows that
of individual table rows individual table rules at presentation. contain changes.
S1-00520 Presentation of data module Decide whether to present the data Title shall be presented.
titles in the reference table module title in the reference table
("Table 1 References").
S1-00521 Presentation of publication Decide whether to present the title Title shall be presented. Project to make the decision for which
module/non-S1000D publication (element <pmTitle>/<externalPubTitle>) title to use.
titles in the reference table or the short title (element
<shortPmTitle>/<shortExternalPubTitle>),
or both, in the reference table ("Table 1
References").
BRDP BREX
Number Rule
S1-00522 Order of presentation of Decide in which order the referenced No Civil Aviation business rule.
references in the reference table document is presented in the reference
table ("Table 1 References"): In order of
appearance, alphabetical order, data
modules before publications, etc.
S1-00523 Inline presentation of non- Decide whether to present the external Either or both of the external publication code (element
S1000D publication titles publication code (element <externalPubCode>) or the title (element <externalPubTitle>)
<externalPubCode>), the title (element shall be presented. The short title (element
<externalPubTitle>) or the short title <shortExternalPubTitle>) shall not be presented.
(element <shortExternalPubTitle>) as the
inline reference.
S1-00524 Presentation of the name of Decide whether to present the name No Civil Aviation business rule.
spares, supplies and support (element <name>) or the abbreviated
equipment alternate name (element <shortName>),
as the cross-reference in the text.
S1-00525 Use of the alternative method Decide whether to use the preferred or Applicability statements shall be presented before the steps or
for presentation of applicability the alternative method for presentation of paragraphs to which they apply.
statements applicability statements.
S1-00526 Decide on highlighting the Decide whether to highlight (bold) the No Civil Aviation business rule.
default heading and applicability default heading and applicability
statement at presentation statement at presentation.
S1-00527 Elements and attributes to be Decide which elements and attributes to Title pages may contain only information provided in data
presented on the Title page be presented on the Title page. module structured content.
Note
The decisions must be
coordinated/based on the Business rules
decision points given in Chap 3.9.5.2.16.
S1-00528 Size of the product illustration Decide on the height of the product No Civil Aviation business rule.
on the Title page illustration on the Title page, if used.
S1-00529 Elements and attributes to be Decide which elements and attributes to No Civil Aviation business rule.
presented on the Table of be presented on the Table of content
content page page.
Note
BRDP BREX
Number Rule
S1-00530 Elements and attributes to be Decide which elements and attributes to List of Effective Pages shall not be used.
presented on the List of effective be presented on the List of effective
pages pages.
Note ✓
S1-00531 Elements and attributes to be Decide which elements and attributes to No Civil Aviation business rule.
presented on the List of effective be presented on the List of effective data
Note
S1-00532 Elements and attributes to be Decide which elements and attributes to The following are required for Civil Aviation applications:
presented on the Highlights data be presented on the Highlights data
modules modules. • List header info
o Title
Note o Issue Number
o Introductory paragraph
The decisions must be • List content
coordinated/based on the Business rules o Data Module Code
decision points given in Chap 3.9.5.2.16. o Reason for update
o Page Number
The front matter schema shall not be used for exchange
purposes in Civil Aviation.
S1-00533 Use of rules and guidance for Decide whether to use the rules and S1000D chapter 6.3.1 may be used as guidance, but is not
IETP guidance for look and feel, and printed required.
output from an IETP detailed in Chap
6.3.1 or an alternate output specification.
S1-00534 Main menu bar functions in the Decide which, if any, of the basic set of In Civil Aviation, IETP providers should determine their own
IETP viewer main menu bar functions to mandate. functionality requirements.
S1-00535 Printing of classified data Decide whether to allow the printing of In Civil Aviation, IETP providers should determine their own
classified data. If not allowed, the print functionality requirements.
function must be disabled when classified
data is presented in the IETP viewer
S1-00536 Additional information bar in the Decide on the use of an additional In Civil Aviation, IETP providers should determine their own
IETP viewer information bar. If used, it must be functionality requirements.
BRDP BREX
Number Rule
decided which information to be available
in the additional information bar.
S1-00537 Use of the functionality matrix Decide whether to use the functionality No Civil Aviation business rule.
matrix. If used, fill in the functionality
matrix. Refer to Chap 6.4.2.
S1-00538 Modification of the functionality Decide on which functionality is required No Civil Aviation business rule.
matrix due to selection of in the technical publications.
information sets
S1-00539 Selection of functionality using Decide on which functionality is required No Civil Aviation business rule.
the functionality matrix in the technical publications.
S1-00540 Population of the element Decide the preferred syntax to identify No Civil Aviation business rule.
<externalPubCode> legacy data by a publication code.
pubCodingScheme pubCodingScheme. If used, decide on
the set of allowed coding schemes and
the syntax of those schemes.
S1-00542 Method to include legacy Decide whether to include legacy No Civil Aviation business rule.
information in an IETP information by encapsulating it in data
modules or by referencing it as external
publications using the publication
module.
S1-00543 IETP reference format Decide the syntax and semantics of the No Civil Aviation business rule.
links established to reference legacy
data.
S1-00544 Use of data compression Decide whether to use compression No Civil Aviation business rule.
techniques techniques on files being transferred and
which techniques to be used.
S1-00545 File formats for information Decide which file formats, besides the Civil Aviation applications may also use the Scalable Vector
objects S1000D standard formats, to use. Graphics (SVG) and ATA CGM Profile file formats. Other file
formats may be used upon project agreement.
S1-00546 Inclusion of RDF/DC metadata Decide on the inclusion of RDF/DC RDF/DC metadata shall not be used.
in data dispatch notes, data metadata in data dispatch notes, data
management lists and
comments
management lists and comments. It is
recommended that inclusion is applied
✓
consistently across all CSDB objects.
S1-00547 Format of generated display text Decide on the format for generating the No Civil Aviation business rule.
displayed applicability annotation from
the computable applicability annotation
that will best fulfill industry and/or
customer display requirements.
BRDP BREX
Number Rule
S1-00548 Modifying an assigned product Decide if modifications to PCT assigned Modifications to PCT assigned values are allowed.
attribute value in the PCT. values are allowed.
S1-00549 Translation of SNS titles and Decide whether to translate and use the Translation to languages other than U.S. English shall not be
definitions SNS titles and the definitions in the allowed.
languages adopted by the project.
S1-00550 Allocation of project specific Decide and agree on allocation of project Any new Information Codes needed by OEMs or operators
information codes specific information codes and give them should be submitted to CAWG to determine if they should be
short and full definitions. proposed to the Steering Committee for a specification change
based on urgency of need. If the proposal is unable to be
accepted for S1000D within a reasonable timeframe, then
CAWG would assign a project-specific code using a third-
character alpha. Civil Aviation approved project-specific info
codes will be maintained by CAWG. Codes consisting of three
alpha characters may be used by airlines for internal use only.
S1-00551 Translation of information code Decide whether to translate and use the Translation to languages other than U.S. English shall not be
definitions information code definitions in the allowed.
languages adopted by the project.
S1-00552 Translation of learn code Decide whether to translate and use the Translation to languages other than U.S. English shall not be
definitions learn code definitions in the languages allowed.
adopted by the project.
2-2. Civil Aviation Attribute Values
This section contains the Civil Aviation specific values for the project configurable attributes listed in S1000D chapter 3.9.6.1 and
3.9.6.2. Section 2-2 is included by reference into this specification. The current version can be accessed using the following link.
Section 2-2. Civil Aviation Attribute Values
Please contact admin@ataebiz.org if you would like to add attribute values to this list.
Note: This section is maintained in a separate file from the main Spec 1000BR document and may be revised
independently of the Spec 1000BR revision schedule.
2-3. Reserved for future use
2-4. General Civil Aviation Business Rules Exchange (BREX)
This section contains the Business Rules Exchange (BREX) data module. The BREX DM provides data recipients with the means
to programmatically enforce/validate certain business rules. Section 2-4 is included by reference into this specification. The current
version can be accessed using the following link.
Section 2-4. General Civil Aviation BREX
Note: This section is maintained in a separate file from the main Spec 1000BR document and may be revised
independently of the Spec 1000BR revision schedule.
Chapter 3. Component Maintenance Publication Usage
This chapter provides Civil Aviation guidance for use of S1000D to produce and publish Component Maintenance Publications.
Section 3-1 provides the Civil Aviation business rules in response to the S1000D Business Rule Decision Points (BRDPs). Section
3-2 provides Civil Aviation layout rules for Component Maintenance data modules.
3-1. Component Maintenance Publication Business Rules
This table contains business rules for Civil Aviation implementation of S1000D for Component Maintenance Publications
(CMPs). Specific rules for Civil Aviation usage of S1000D for CMPs are included where appropriate. In some cases, the Civil
Aviation CMP usage is denoted as the same as the General Civil Aviation usage and the CMP rule is hyperlinked to the General
rule. Where the CMP usage states "No Civil Aviation business rule", then it is left to the individual project to make the decision.
Table 3 CMP Business Rules
BRDP
BRDP Title BRDP Component Maintenance Publications Usage
Number
S1-00001 Use of "I" and "O" Decide whether and when to use the Per the following General Civil Aviation usage:
alpha characters "I" and "O". The use of alpha characters "I" and "O" in S1000D data
shall be compliant with ATA iSpec 2200, Specification
2000, and the CSDD.
S1-00002 List of permitted CAGE codes Create a list of permitted CAGE codes A list of permitted CAGE codes will not be used.
and/or names of the originator and/or names of the originator
companies to be companies.
used for the technical
publications
S1-00003 Issue of S1000D to be used Decide which issue or issues of S1000D Per the following General Civil Aviation usage:
to be used. No Civil Aviation business rule.
S1-00004 Information sets to be used Decide which information sets, given in Only the Equipment Information Set shall be used.
S1000D and/or project specific, to be
used.
S1-00005 Publications to be produced Decide which publications to be The publication to be produced is a Component Maintenance
produced. Publication (CMP).
S1-00006 Schemas to be used Decide which Schemas to be used and Per the following General Civil Aviation usage:
in which information set they are to be Civil Aviation shall use the schemas and information sets
used. per the following table. Additions to this list may be
requested by contacting admin@ataebiz.org and are
subject to approval by the ATA Technical Data Working
Group.
BRDP
Number
Information Sets Schemas
Description and comrep - CIR applic
operation comrep - CIR
warning/caution
container
descript
Maintenance information comrep - CIR applic
- Maintenance comrep - CIR
Procedures warning/caution
container
descript
proced
- Fault isolation comrep CIR
warning/caution
container
descript
fault
proced
– Non destructive comrep - CIR
Testing warning/caution
container
descript
proced
Maintenance information descript
– Storage proced
Wiring data comrep - CIR applic
container
descript
proced
wrngdata
Illustrated parts data comrep - CIR applic
comrep - CIR part
descript
ipd
List of applicable descript
publications
container
BRDP
Number
descript
Maintenance planning pm
information
schedule
Equipment information comrep
container
descript
fault
ipd
pm
proced
Illustrated tool and descript
support equipment
information
Service bulletins container
descript
pm
proced
sb
Common information and descript
data cir
Training descript
Structure repair proced
comrep - CIR applic
comrep - CIR
warning/caution
Engine maintenance proced
information
Power plant build-up proced
Engine standard proced
practices descript
Note: The following appliccrossreftable
schemas can be used in
addition to those called brex
out by the information
sets. condcrossreftable
ddn
dml
prdcrossreftable
BRDP
Number
xcf
xlink
S1-00007 Use of optional elements and Decide whether and how to use each Per the following General Civil Aviation usage:
attributes optional element and attribute in its No Civil Aviation business rule.
structural context.
S1-00008 Possible deliverables Decide on the possible deliverables, Per the following General Civil Aviation usage:
such as: No Civil Aviation business rule.
S1000D objects (eg, data modules,
publication modules, illustration sheets
and multimedia objects, data
management lists) using file based
transfer.
Page-oriented publications and/or
interactive electronic technical
publications.
S1-00009 Frequency of data exchanges Decide on the frequency of data Per the following General Civil Aviation usage:
exchanges. Revisions for new programs will be provided no less often
than quarterly. Data once issued shall be kept current by
revision service throughout the service life of the
equipment/items covered. It is acceptable for mature
programs to lengthen their revision service where activity
does not warrant quarterly revisions.
S1-00010 Zone and access point Decide whether to use a zoning and Zoning and access identification systems shall not be used for
identification system access identification system. CMPs.
S1-00011 Method for zoning and Decide which method to use for zoning Zoning and access identification systems shall not be used for
identifying access points and identifying access points. CMPs.
S1-00012 Define security classification Decide which values to use for the Only 01 shall be used.
values and terms (attribute attribute securityClassification and
securityClassification) allocate suitable definitions. Refer to
Chap 3.9.6.1.
S1-00013 Use and markings of security Determine how the security Security Classifications shall be used only within the Ident &
classifications (attribute classifications will be used. Status section and not within the Content section.
securityClassification)
S1-00014 Application of caveats Determine if the policies that apply to Caveats shall not be used.
security marking, instructions, etc., and
how those markings are required to be
applied within the given project.
BRDP
Number
S1-00015 Retention of security Decide on the retention of security Not applicable. See BRDP-S1-00013 and BRDP-S1-00014
classifications classifications.
S1-00016 Presentation of security Decide on how the security Not applicable. See BRDP-S1-00013 and BRDP-S1-00014
classifications classifications will be marked and/or
indicated.
S1-00017 Rules for QA Decide on the rules for QA of data For draft deliveries, "Unverified" is acceptable. For issued DMs,
modules and deliverables. only first verification will be used, and the verification type will
be "Tabletop", "On-Object", or "Tabletop and On-Object".
S1-00018 Rules for first and second Decide on the rules for first and second Per the following General Civil Aviation usage:
verification verification. For example, such a rule If provided in a Data Module, second verifications will be
might be that all data modules that have ignored. Refer to guidance in Chapter 3.7 of S1000D.
a safety related procedure must have
first verification carried out "On object".
S1-00019 Review cycle process Decide on the review cycle processes Per the following General Civil Aviation usage:
and procedures. No Civil Aviation business rule.
S1-00020 Specify the language Decide which language to use for Per the following General Civil Aviation usage:
producing data modules. All data modules must be written in U.S. English.
S1-00021 Use of ASD Simplified Technical Decide whether to use ASD-STE100® Per the following General Civil Aviation usage:
English when producing data modules in All Procedural data modules must use the writing rules and
English. vocabulary in ASD Simplified Technical English (ASD-
STE100). Use of STE is optional for other data module
types.
S1-00022 Standard dictionary Decide which standard dictionary to use Per the following General Civil Aviation usage:
for producing data modules. No Civil Aviation business rule.
S1-00023 Use of a terminology database Decide whether to use a terminology Per the following General Civil Aviation usage:
or glossary database or a glossary. If used, agree The ATA Common Support Data Dictionary shall be used
on its content and management. for Civil Aviation maintenance terminology.
S1-00024 Use of a standard list of Decide whether to use a standard list of Per the following General Civil Aviation usage:
abbreviations abbreviations. If used, agree on its No Civil Aviation business rule.
content and management.
S1-00025 Units of measurement Decide what unit of measurement to Per the following General Civil Aviation usage:
use for primary and secondary units. Measurements shall be provided in both SI (metric) and
Imperial/U.S. units. The first value shall be in the units used
in the original design.
S1-00026 Highlighting text Decide on which method to be used to Per the following General Civil Aviation usage:
emphasize text. Bold text only shall be used to emphasize text. Overline
text may be used only for marking vectors.
S1-00027 Need of printable data Decide which parts of the Per the following General Civil Aviation usage:
documentation (data modules and No Civil Aviation business rule.
BRDP
Number
publications including IETP) need to be
printable.
S1-00028 Engineering numbers and Decide if schematics derived from Per the following General Civil Aviation usage:
revision status within the engineering drawings include the No Civil Aviation business rule.
illustration reproduction area original drawing number and revision
status within the illustration reproduction
area.
S1-00029 Use of color in the final Decide whether to use color in the final Per the following General Civil Aviation usage:
deliverable deliverable. The use of color is permitted in accordance with the ATA
iSpec 2200 3-1-12.4 Graphic Style Standards.
S1-00030 Use of general warnings, Decide whether to produce general Per the following General Civil Aviation usage:
cautions and notes as separate warnings, cautions and notes in Descriptive data modules using information code 012 shall
data modules separate descriptive data modules. only be used for general warnings and cautions that are not
specific to a particular procedure. Specific warnings and
cautions shall be provided in the data modules to which
they apply. Separate descriptive data modules shall not be
used to externalize notes.
S1-00031 Use of warning and/or caution Decide whether to use warning and/or Per the following General Civil Aviation usage:
collections caution collections, internal or external. Use of the Warnings and Cautions Common Information
Repositories (CIRs) is recommended.
S1-00032 Use of the attribute Decide whether and how to use the Per the following General Civil Aviation usage:
vitalWarningFlag attribute vitalWarningFlag. The attribute vitalWarningFlag must not be used in civil
aviation applications.
S1-00033 Use of the attribute Decide whether and how to use the Per the following General Civil Aviation usage:
warningType attribute warningType. The attribute warningType must not be used in civil aviation
applications.
S1-00034 Use of the attribute cautionType Decide whether and how to use the Per the following General Civil Aviation usage:
attribute cautionType. The attribute cautionType must not be used in civil aviation
applications.
S1-00035 Use of the attribute noteType Decide whether and how to use the Per the following General Civil Aviation usage:
attribute noteType. The attribute noteType must not be used in civil aviation
applications.
S1-00036 Presentation of the issue Decide whether to present the issue Per the following General Civil Aviation usage:
number and the inwork number number with or without the inwork The issue number shall be presented on the title page. The
on the title page number on the title page. inwork number may only be presented in unreleased
documents.
S1-00037 Use of LOEP or LOEDM Decide whether the use of LOEP or Per the following General Civil Aviation usage:
LOEDM. If a Data Module containing the LOEDM is provided, Info
Code 00S must be used. LOEP shall not be used.
S1-00038 Presentation the of issue date or Decide whether to present the issue Per the following General Civil Aviation usage:
the issue number in the LOEP date or the issue number (with or Not applicable for Civil Aviation applications.
BRDP
Number
without inwork number) for the LOEP
entries.
S1-00039 Presentation of applicability Decide whether to present the Per the following General Civil Aviation usage:
information in the LOEP applicability information for the LOEP Not applicable for Civil Aviation applications.
entries.
S1-00040 Presentation of the issue date or Decide whether to present the issue Per the following General Civil Aviation usage:
the issue number in the LOEDM date or the issue number (with or Both issue date and issue number are required. Inwork
without inwork number) for the LOEDM number shall not be presented.
entries.
S1-00041 Presentation of applicability Decide whether to present the Applicability information shall not be shown in the LOEDM.
information in the LOEDM applicability information for the LOEDM
entries.
S1-00042 Use of Highlights with updating Decide whether to use Highlights with Per the following General Civil Aviation usage:
instructions updating instructions or not. Highlights with updating instructions shall not be used.
S1-00043 Presentation of issue the date or Decide whether to present the issue Per the following General Civil Aviation usage:
the issue number in the date or the issue number (with or Not applicable for Civil Aviation applications.
Highlights without inwork number) for the
Highlights entries.
S1-00044 Presentation of applicability Decide whether to present the Per the following General Civil Aviation usage:
information for the Highlights applicability information for the Not applicable for Civil Aviation applications.
Highlights entries.
S1-00045 Presentation of issue the date Decide whether to present the issue Issue date and issue number shall be presented in the LOEDM
and the issue number in the date and/or the issue number (with or and not in the TOC. Inwork number shall not be presented in
TOC without inwork number) that apply to the TOC.
TOC entries.
S1-00046 Use of linear or hierarchically Decide whether to use a linear or a A hierarchical TOC shall be used.
subdivided TOC hierarchically subdivided TOC.
S1-00047 Country and language codes Decide on the country and language Per the following General Civil Aviation usage:
codes to use, and apply them All Procedural data modules must use the
consistently across the project. languageIsoCode (sx). All other data modules may use sx
or en (English). No Civil Aviation business rule for the value
of countryIsoCode.
S1-00048 Exchange of draft data modules Decide whether the project will allow the Exchange of draft data modules is allowed. Refer to BRDP-S1-
exchange of draft data modules. 00077.
S1-00049 Definition of the issue date Decide on the definition of the issue For DMs the definition of the issue date is the date it is
date. This can be, for example, the input released. The same definition applies to PMs.
date (ie, the release to CSDB date), or
the cut-off date for the delivery, etc.
S1-00050 Source of the technical names Decide on the source of the technical The tech name will reflect the name of the hardware or
names and use them consistently function of the content and is not restricted to the system,
across the project. In all cases, the subsystem, or subsubsystem.
BRDP
Number
technical name must reflect the item
represented by the SNS.
S1-00051 Rules for the information names Decide on which information codes The following project-specific codes may be used:
apply to the project. 02A: Export Control
02B: Regulatory
Additionally all defined Information Codes in S1000D may be
used except for the following:
IC Description
004 Access illustration
029 Data structure
055 Location diagram
Functional item numbers common information
00E
repository
00F Circuit breakers common information repository
00H Zones common information repository
Access panels and doors common information
00J
repository
00R List of effective pages
Controls and indicators common information
00X
repository
0A1 Functional and/or physical areas repository
111 Controls and indicators (This code is used for crew)
112 Modes of operation (This code is used for crew)
Pre-operation procedure (This code is used for
121
crew)
Pre-operation procedures checklist (This code is
125
used for crew)
127 Establish operating position
Normal operation procedure (This code is used for
131
crew)
Normal operation procedures checklist (This code is
135
used for crew)
Emergency operation procedure (This code is used
141
for crew)
BRDP
Number
Emergency operation procedures checklist (This
145
code is used for crew)
146 Emergency shutdown operation procedure
Post-operation procedure (This code is used for
151
crew)
Post-operation procedures checklist (This code is
155
used for crew)
161 Special operation
162 Non-tactical operation
174 Towing
175 Taxiing
179 Debogging
Easily and quickly adjust after a battle damage
278
repair
279 Easily and quickly align after a battle damage repair
375 Shooting accidental discharge analysis
396 Flight control surface movement
397 Landing gear movement
525 Ammunition unloading
526 Deactivate launching device
540 Open for access procedure
665 Fly-in repair procedure
680 Battle damage repair procedure and data
687 Function test after battle damage repair
688 Battle damage repair kit
725 Ammunition loading
726 Activate launching device
727 Site location plans
728 Foundation preparation
740 Close after access procedure
831 Vehicle loading
841 Vehicle unloading
BRDP
Number
871 Set on condition
Handling procedure Not to be used for new projects.
912
Use IC 170 instead.
917 Non-S1000D publication
930 Service bulletin
Service bulletin data Not available for projects.
931 (Used for service bulletins following the rules in
Issue 4.0 or earlier issues.)
Planning information Not available for projects.
932 (Used for service bulletins following the rules in
Issue 4.0 or earlier issues.)
951 Generic process
952 Generic learning content
980 Environmental protection, fire-fighting and rescue
981 Air cleaning For example, filtering to obtain clean air
982 Sewage treatment
989 Fire-fighting and rescue
990 Neutralization and disposal
991 Neutralization of ordnance
996 Disposal of ordnance
S1-00052 Allocation of the information Decide on which information codes and Per the following General Civil Aviation usage:
codes and the information associated information names to be No Civil Aviation business rule.
names used, and assign a Schema to be used
for each information code.
S1-00053 Data module change/revised Decide on the threshold that a data Per the following General Civil Aviation usage:
ratio module is considered revised rather A status of "changed" is preferred in Civil Aviation
than changed. applications. In some cases when a data module has
changed to such an extent that there is no value to the end
user including change markup, a status of "revised" may be
used.
S1-00054 Use and definitions of the Decide on the use and definitions of the commercialClassification and caveats shall not be used.
attributes attributes commercialClassification and
commercialClassification and caveat.
caveat
BRDP
Number
S1-00055 Priorities and relationships of Decide on the priorities and securityClassification must always be 01.
the security attributes relationships between the attributes
securityClassification, securityClassification,
commercialClassification and commercialClassification and caveat if
caveat they are used.
S1-00056 Use of the element Decide whether to include data Per the following General Civil Aviation usage:
<dataRestrictions> restriction information. No Civil Aviation business rule.
S1-00057 Use of the attribute applicability Decide whether to differentiate data Per the following General Civil Aviation usage:
in the element restrictions information based on No Civil Aviation business rule.
<dataRestrictions> Product configuration.
S1-00058 Use of the element Decide whether to include export Per the following General Civil Aviation usage:
<restrictionInstructions> controls, handling, destruction notices No Civil Aviation business rule.
and disclosure instructions.
S1-00059 Use of the element Decide on the distribution information Per the following General Civil Aviation usage:
<dataDistribution> contained in the element No Civil Aviation business rule.
<dataDistribution>.
S1-00060 Use of the element Decide whether and how to use the Per the following General Civil Aviation usage:
<dataHandling> element <dataHandling>. For example, No Civil Aviation business rule.
the handling requirements and
data module.
S1-00061 Use of the element Decide whether to use the element Per the following General Civil Aviation usage:
<dataDestruction> <dataDestruction> and how to use it. No Civil Aviation business rule.
For example, the appropriate extent of
destruction instructions that must be
applied to a data module.
<dataDisclosure> element <dataDisclosure>. For No Civil Aviation business rule.
disclosure instructions.
<supersedure> <supersedure> and how to use it. For No Civil Aviation business rule.
supersedure notices.
<restrictionInfo> element <restrictionInfo>. For example, No Civil Aviation business rule.
the content and extent of restriction
information to include in a data module.
BRDP
Number
S1-00065 Use of the element <copyright> Decide whether and how to use the Per the following General Civil Aviation usage:
and source of copyright element <copyright>. Any copyright No Civil Aviation business rule.
information information must be obtained from the
relevant authority.
S1-00066 Method of populating copyright Decide whether to populate copyright Per the following General Civil Aviation usage:
information (in each data information in each data module or No Civil Aviation business rule.
module or in a consolidated whether to cross-reference to a
data module) copyright data module.
Note
While choosing the population method,
assess the impact of changes to
copyright information on updating of
data modules.
<policyStatement> <policyStatement>. No Civil Aviation business rule.
<dataConds> <dataConds>. No Civil Aviation business rule.
S1-00069 Use of the element <logo> Decide whether to use the element Per the following General Civil Aviation usage:
<logo>and how it should be used at No Civil Aviation business rule.
presentation.
<enterpriseName> and/or the <enterpriseName> and/or the attribute The attribute enterpriseCode is required unless the
attribute enterpriseCode for the enterpriseCode to capture the name responsible partner company does not have a CAGE Code.
responsible partner company and CAGE code respectively, of the In that case, the textual content of the element
responsible partner company. If the <enterpriseName> is required.
name is used it must be done
consistently and be mandatory for the
project.
<enterpriseName> and/or the <enterpriseName> and/or the attribute The attribute enterpriseCode is required unless the
attribute enterpriseCode for the enterpriseCode to capture the name originator does not have a CAGE Code. In that case, the
responsible originator and CAGE code respectively, of the element <enterpriseName> is required.
originator. If the name is used it must be
done consistently and be mandatory for
the project.
<techStandard> <techStandard>. No Civil Aviation business rule.
<authorityInfo> element <authorityInfo>. No Civil Aviation business rule.
BRDP
Number
<techPubBase> element <techPubBase>. If used, agree No Civil Aviation business rule.
on acceptable values for the publication
baseline and where they are derived
from.
S1-00075 Use of the element Decide how to use the element Per the following General Civil Aviation usage:
<authorityNotes> <authorityNotes>. No Civil Aviation business rule.
S1-00076 Use of the attribute applicRefid Decide whether to use attribute Per the following General Civil Aviation usage:
of the element applicRefid on QA information. No Civil Aviation business rule.
<qualityAssurance>
S1-00077 Exchange of draft data modules Decide whether the project will allow the Exchange of draft data modules is allowed. Refer to BRDP-S1-
exchange of draft data modules. 00048.
S1-00078 Use of the element Decide whether to use the element If systemBreakdownCode is included in the DMs it will be
<systemBreakdownCode> <systemBreakdownCode>. If used, its ignored.
use must be consistent across the
project.
S1-00079 Use of the element Decide whether to use element If functionalItemCode is included in the DMs it will be ignored.
<functionalItemCode> <functionalItemCode>. If used, its use
S1-00080 Use of the element Decide whether to use the element If functionalItemRef is used in the identAndStatusSection in the
<functionalItemRef> <functionalItemRef>. If used, its use DMs it will be ignored.
S1-00081 Use of the attribute Decide how to populate the attribute If functionalItemNumber is used in the identAndStatusSection in
functionalItemNumber of the functionalItemNumber of the element the DMs, it will be ignored.
element <functionalItemRef> <functionalItemRef> when this element
is used.
S1-00082 Use of the attribute Decide whether and how to use the The attribute manufacturerCodeValue of the element
manufacturerCodeValue of the attribute manufacturerCodeValue of the <functionalItemRef> shall not be used.
element <functionalItemRef> element <functionalItemRef>. If used,
the element must be populated
consistently across the project.
<productSafety> <productSafety> and under what The element <productSafety> shall be used only for Alert
circumstances. Service Bulletins.
S1-00084 Values for the attribute Define the values to use for the attribute Per the following General Civil Aviation usage:
safetyLabel safetyLabel. The value "Alert" must be used.
S1-00085 Use of the element <remarks> Decide whether to use the element If the element <remarks> is used in the DMs, it will be ignored.
in the element <dmStatus> <remarks>. If used, its use must be
defined in the project business rules
and guidance given.
BRDP
Number
S1-00086 Use of the attribute applicRefId Decide whether and how to use the If attribute applicRefId of the element <remarks> is used in the
of the element <remarks> within attribute applicRefId of the element DMs, it will be ignored.
the element <dmStatus> <remarks> in the element <dmStatus>.
The element <remarks>can contain
remarks, which can be differentiated
based on Product configuration.
S1-00087 Use of export control Decide whether export control Per the following General Civil Aviation usage:
regulations apply. No Civil Aviation business rule.
S1-00088 Content of export control details Decide on the requirements and Per the following General Civil Aviation usage:
procedures that must be applied to a No Civil Aviation business rule.
data module regarding export controls.
S1-00089 Standard wording for reasons Decide standard reason for update Per the following General Civil Aviation usage:
for update sentences to be used. Reason for No Civil Aviation business rule.
update can be used to automatically
generate a highlights data module.
Normally, a project will mandate its use
from issue "002" upwards. Examples
are:
Revised to incorporate modification XYZ
Deleted. Data module no longer
required
S1-00090 Use of reason for update in Decide whether the element Per the following General Civil Aviation usage:
conjunction with the production <reasonForUpdate> is used during the No Civil Aviation business rule.
process production process.
S1-00091 Use of applicability information Decide whether it is permissible to Per the following General Civil Aviation usage:
differentiate reasons for update based No Civil Aviation business rule.
on Product configuration.
S1-00092 Use of change marks for tables Decide whether and how to use change Per the following General Civil Aviation usage:
marks for tables. For changes to content within a table, the element changed
will be marked. If the authoring tool does not allow markup
below the row level, then it is acceptable to apply change
markup to the individual row where the change occurs. For
new tables, change markup will be applied to the complete
table element. The table title will be marked only for
changes to the title.
S1-00093 Use of change marks for figures Decide whether and how to use change Per the following General Civil Aviation usage:
marks for figures. When modifying a graphic within a figure, change markup
will be applied only at the sheet level <graphic>. For new
graphics added to existing figures, change markup may be
applied at the sheet level and the figure level. For new
figures, change markup will be applied to the complete
BRDP
Number
figure element. The figure title will be marked only for
changes to the title.
S1-00094 Extent of cross-referencing Decide on the extent of cross- Attribute usages as follows:
referencing within data modules and the
methods used for populating the various Required Attributes:
attributes. internalRefId
internalRefTargetType (see BRDP-S1-00100)
Optional Attributes:
applicRefId
authorityDocument
authorityName
changeMark *
changeType *
reasonForUpdateRefIds *
referredFragment
xLink (all)
Prohibited Attributes:
targetTitle
* = 4.2 issue
S1-00095 Use of the element Use of the element <internalRef> in The element <internalRef> shall not be used in titles.
<internalRef> in titles titles is strongly discouraged. However,
decide whether to use cross-references
in titles.
S1-00096 Use of the attribute targetTitle Decide whether to use the attribute The attribute targetTitle shall not be used.
targetTitle.
When used (populated), it is a tooltip in
a viewer application.
S1-00097 Presentation of the target titles Decide whether to present the target The attribute targetTitle shall not be used.
in cross-references titles given in the element <title>.
Note
Presentation of the titles depends on
the presentation system and its settings.
S1-00098 Use of the textual content of the Decide whether to use the textual The textual content of the element <internalRef> shall not be
element <internalRef> in cross- content of the element <internalRef>. populated.
references
When used (populated), it must be
presented.
BRDP
Number
S1-00099 Use of the "identifiers" given in Decide whether to use any of the The element <reqSupportEquipment> shall use <shortName>
the elements "identifiers" given in the elements and <toolRef @toolNumber>.
<reqSupportEquips>, <reqSupportEquips>, <reqSupplies>,
<reqSupplies>, <reqSpares> or <reqSpares> or <workLocation> as the The element <reqSupplies> shall use element <shortName>
<workLocation> presented link (textual content of the and <supplyRef @supplyNumber>.
element <internalRef>), or as a tooltip in
a viewer application (value of the
attribute targetTitle). The element <reqSpares> shall use <shortName> and either
<partRef@partNumberValue and @manufacturerCodeValue>
Note: or <catalogSeqNumberRef>.
The "identifiers" can be derived from the
content of the child elements or the If <shortName> is not provided, then <name> will be used.
attributes of the four elements.
CMPs shall not use <workLocation>.
S1-00100 Use of the attribute Decide whether to use the attribute Only these elements can be referenced when using an internal
internalRefTargetType internalRefTargetType, which values to ref.
use and allocate suitable definitions to "irtt01" Figure
the values. Refer to Chap 3.9.6.1. "irtt02" Table
"irtt03" Multimedia
"irtt04" Supply
"irtt05" Support equipment
"irtt06" Spares
"irtt07" Leveled Paragraph
"irtt08" Procedural Step
"irtt09" Graphic
"irtt10" Multimedia object
"irtt11" Hotspot
"irtt12" Parameter
S1-00101 Define the format of the cross- Decide whether the values of the cross- Patterns shall not be enforced.
reference attributes id and reference attributes id and internalRefId
internalRefId must be prefixed by alpha characters
that identify the type of the target
element. Example:
Structure: Prefix followed by a hyphen
and a four digit number to make it
unique within the data module (eg, "par-
0001").
Prefixes:
"fig" for figures and alternates
"tab" for tables
BRDP
Number
"mma" for multimedia and alternates
"sup" for supplies
"seq" for support equipment
"spa" for spares
"par" for levelled paragraphs and
alternates
"stp" for steps of procedure, fault
isolation, etc, and alternates
"gra" for graphics (multiple sheets)
"mmo" for multimedia objects
"hot" for hotspots (eg, "fig-0001-hot-
0002")
"pme" for parameters
"zon" for zones
"wla" for work locations
"mat" for single material or material sets
"acp for access points
Note
The four digit number has no
connection to, eg, the figure or table
number which is generated for data
module presentation. For example, the
value of the attribute id can be "fig-
0345" for "Fig 1". Refer to Para 2.1.
Note
Refer to Chap 3.9.5.2.1.10 for the
equivalent business rule decision point
regarding footnotes. Example: "ftn-
0001".
BRDP
Number
S1-00102 Use and format of the attribute Decide whether to use the attribute Per the following General Civil Aviation usage:
referredFragment of the element referredFragment and, if used, list the No Civil Aviation business rule.
<dmRef> precautions.
S1-00103 Use of issue information and Decide whether to use issue and in- If issue number and in-work number are used in the data
language in data module work numbers, as well as language and module reference, they must be included in the rendered data
references country codes of the destination data module reference. This means that for any given data module,
module in data module references. In multiple instances can be active simultaneously.
making this decision, the project or
organization must be aware of the
implications of using the items when
referenced data modules are updated.
S1-00104 Use of title and issue date in Decide whether to use the title and the The <dmTitle> and <issueDate> of the destination data module
data module references issue date of the destination data are optional. If the <dmTitle> element is present it shall be
module in data module references. rendered, otherwise the value shall be retrieved and rendered.
If the <issueDate> element is present it shall be rendered,
otherwise the value shall not be retrieved and rendered.
S1-00105 Use of issue information and Decide whether to use issue and in- In-work numbers shall not be used.
language in publication module work numbers, as well as language and
references country codes of the destination
publication module in publication
module references. In making this
decision, the project or organization
must be aware of the implications of
using the items when referenced
publication modules are updated.
S1-00106 Population of the element Decide if and how the element <refs> is Per the following General Civil Aviation usage:
<refs> populated. If populated, the order of No Civil Aviation business rule.
items in the list must be specified.
S1-00107 Define the words before and Define the words before and after the For <dmRef> preceed with "Refer to".
after the reference elements elements <dmRef>, <pmRef> and For <pmRef>, preceed with "Refer to".
<externalPubRef>. This is important as For <externalPubRef>, preceed with "Refer to".
it has implications on the stylesheets
used. Example: For one
implementation, the stylesheet can
automatically generate the words "Refer
to data module: " when it recognizes the
element <dmRef>. This will cause
problems if the author has written "Refer
to " within the paragraph before the
element <dmRef>.
S1-00108 Use of titles for lists Decide whether to use titles for each of Per the following General Civil Aviation usage:
the sequential, random and definition No Civil Aviation business rule.
lists.
BRDP
Number
S1-00109 Use of the attribute Decide whether to use the attribute Per the following General Civil Aviation usage:
listItemPrefix listItemPrefix, which values to use and If the attribute listItemPrefix is used, only pf02 shall be
allocate suitable definitions to the used.
S1-00110 Use of definition list headers Decide whether to use definition list Per the following General Civil Aviation usage:
headers. No Civil Aviation business rule.
S1-00111 Use of applicability information Decide whether and how to use the Per the following General Civil Aviation usage:
on various caption group child attribute applicRefId of various No Civil Aviation business rule.
elements <captionGroup> child elements.
S1-00112 Use of color for Tables of Decide whether to use the attribute Per the following General Civil Aviation usage:
contents - attribute tableOfContentType, (eg, for Table of The attribute tableOfContentType shall not be used.
tableOfContentType in the contents in Flight reference cards).
element <captionGroup>
S1-00113 Use of the attributes rowsep and Decide whether the attributes rowsep Per the following General Civil Aviation usage:
colsep in the element and colsep rules between No Civil Aviation business rule.
<captionEntry> <captionEntry> elements are required.
S1-00114 Use of the local use of spans Decide whether the element Per the following General Civil Aviation usage:
within the element <captionEntry> spans are to be defined No Civil Aviation business rule.
<captionEntry> locally or by the element <spanspec>.
S1-00115 Use of the attribute color in the Decide whether to use the attribute Per the following General Civil Aviation usage:
element <caption> color, which values to use and allocate The attribute color shall not be used.
suitable definitions to the values. Refer
to Chap 3.9.6.1.
S1-00116 Use of attribute Decide whether and how to use the The attribute systemIdentCode shall not be used.
systemIdentCode in captions attribute systemIdentCode.
S1-00117 Inline use of captions Decide whether inline captions affect Per the following General Civil Aviation usage:
the text line spacing and how this is No Civil Aviation business rule.
defined
S1-00118 Use of the element <title> Decide whether and how to use the If a page-oriented presentation is required, a primary step or
element <title>. paragraph in a DM must have a title, even if this replicates
techName and infoName.
S1-00119 Use of cross-references from Decide whether to allow cross- The use of cross-referencing in titles is not allowed.
titles referencing from titles.
S1-00120 Use of titles for the elements Decide whether titles can be included Titles can be included for the elements <levelledPara> and
<levelledPara> and for the elements <levelledPara> and <proceduralStep> from sublevel six thru eight when converting
<proceduralStep> from sublevel <proceduralStep> from sublevel six thru legacy data to S1000D.
six thru eight for legacy data eight when converting legacy data to
S1000D.
S1-00121 Use of standard table types Decide if a list of standard table types For paper presentations the attribute tabStyle shall have a
applies to the project (eg, inspection, value of "oversize" to render a table to an 11" x 17" page size.
BRDP
Number
examination) and define what the
business rules are for these types in The attribute orient shall be used to select either landscape or
terms of their presentation requirements portrait orientation of the table.
and certain textual values (eg, titles and
heading row values). Each of these Both attributes can be used independently or in conjunction
standard types must have a defined with each other.
value that can be applied to the table’s
attribute tabstyle.
S1-00122 Use of tables as graphics Decide if tables represented as graphics Per the following General Civil Aviation usage:
are allowed, and if they are, in what Graphics shall not be used to store tables with the
situations they can be used. exception of legacy data and cases where the table data
cannot be represented properly through use of the XML
table format.
of various table child elements - attribute applicRefId of various <table> Applicability is allowed at <table> and < row> levels but not
attribute applicRefId of the child elements. The child elements can at <entry> level. Applicability is also allowed on entry sub-
element <table> be differentiated based on Product elements.
configuration.
for complete figures and attribute applicRefId of various <figure> No Civil Aviation business rule.
illustration sheets - attribute child elements. The child elements can
applicRefId of the element be differentiated based on Product
<figure> configuration.
S1-00125 Use of hotspots Decide whether to use hotspots. Per the following General Civil Aviation usage:
No Civil Aviation business rule.
S1-00126 Use of legends Decide whether to use legends. Per the following General Civil Aviation usage:
No Civil Aviation business rule.
S1-00127 Use of leading zeros in the Decide whether the element Per the following General Civil Aviation usage:
element <listItemTerm> <listItemTerm> is to contain a leading The use of leading zero(s) in <listItemTerm> must match
zero when using callout/item numbers. the leading zero usage in the figure callouts.
The default is no leading zero.
S1-00128 Types of legends Decide on the strategy for legends. Legends shall use the <legend> element.
Legends can appear as part of the
illustration or as text using the element
<legend>. The advantage of making the
legend part of the text is that:
the same illustration can have different
legends wherever it appears (eg, in
multi-language projects)
the text of the element <legend> can be
searched (this might not be the case if
BRDP
Number
the legend is part of the illustration)
items in the illustration can be linked to
the legend by the use of hotspots
the legend in the text can save space
on the illustration (particularly when the
legends are long)
S1-00129 Suitability of multimedia use Decide whether using multimedia is Multimedia can only be used as supplemental information. The
suitable for the environment in which required information must be conveyed in text and graphics.
the project will operate.
S1-00130 Permitted types of multimedia Decide what types of multimedia objects Per the following General Civil Aviation usage:
are permitted. No Civil Aviation business rule.
S1-00131 Use of foldouts Decide whether to use the element Per General Civil Aviation usage. Refer to BRDP-S1-00121.
<foldout> in which information sets it is The element <foldout> shall not be used. Oversize
allowed. graphics or tables may be accommodated through the
object’s attributes, e.g., reproductionHeight and
Note reproductionWidth.
It is only used for page-oriented
publications, as it will not have an effect
in the screen view of an IETP.
S1-00132 Use of hotspots Decide whether and how to use Per the following General Civil Aviation usage:
hotspots. No Civil Aviation business rule.
If hotspots are to be used decide
whether hotspots can be used to link to
graphical objects from local text
whether hotspots can be used to link
from graphical objects to other graphical
objects or local text
whether hotspots can be used to link
from graphical objects to other data
modules
S1-00133 Use of the element <parameter> Decide whether to use the element Per the following General Civil Aviation usage:
<parameter> and how to use it. If used, No Civil Aviation business rule.
specify the attributes to be used within
the project.
BRDP
Number
S1-00134 Use of the element Decide whether to use the element Use of the element <preliminaryRqmts> is allowed.
<preliminaryRqmts> <preliminaryRqmts> in maintenance
planning, fault isolation, maintenance
checklist and/or process data modules.
S1-00135 Use of the element Decide whether and how to use the Use of the element <workAreaLocationGroup> is not allowed.
<workAreaLocationGroup>> in element <workAreaLocationGroup>.
the element The possibility of duplication and
<preliminaryRqmts> mismatch of data given in the
maintenance planning information must
be taken into account.
S1-00136 Use of the element Decide whether and how to use the Use of the element <workLocation> is not allowed.
<workLocation> in the element element <workLocation>. If used,
<preliminaryRqmts> decide which data module types it will
be used with.
S1-00137 Use of the element <workArea> Decide whether and how to use the Use of the element <workArea> is not allowed.
in the element element <workArea>. If used, decide
<preliminaryRqmts> and the which data module types to use it.
element <checkListItem>
S1-00138 Use of the element Decide whether and how to use the Use of the element <installationLocation> is not allowed.
<installationLocation> in the element <installationLocation>. If used,
element <preliminaryRqmts> decide which data module types to use
it.
S1-00139 Use of the element Decide whether and how to use the Use of the element <productItem> is not allowed.
<productItem> in the element element <productItem>. If used, decide
<preliminaryRqmts> which data module types to use it.
S1-00140 Use of the attribute Decide whether and how to use the Use of the attribute productItemName is not allowed.
productItemName in the attribute productItemName.
S1-00141 Use of the attribute Decide whether and how to use the Use of the attribute productItemType is not allowed.
productItemType in the element attribute productItemType.
<preliminaryRqmts>
S1-00142 Use of the element Decide whether and how to use the Use of the element <taskDuration> is not allowed.
<taskDuration> in the element element <taskDuration>. The possibility
<preliminaryRqmts> and the of duplication and mismatch of data
element <checkListItem> given in the maintenance planning
information must be taken into account.
S1-00143 Include a circuit breaker list as Decide if a circuit breaker list is to be Use of the element <circuitBreakerDescrGroup> is not allowed.
part of the preliminary considered as part of preliminary
conditions - (element conditions and thus the use of the
<reqCondCircuitBreaker>) element, or if the circuit breaker settings
are part of the steps. In this latter case
the element
BRDP
Number
<circuitBreakerDescrGroup> in steps
content can be used.
S1-00144 Use of the element Decide whether and how to use the Use of the element <reqPersons> is not allowed.
<reqPersons> in the element element <reqPersons>. For example,
<preliminaryRqmts> use either the element <personnel> or
<person> or use both elements.
S1-00145 Values for the attribute Define a list of categories (eg, Use of the attribute personCategoryCode is not allowed.
personCategoryCode in the Electrician, Propulsion engineer,
element <preliminaryRqmts> Maintainer).
S1-00146 Values for the element <trade> Define a list of trades/trade codes. Use of the element <trade> is not allowed.
in the element
<preliminaryRqmts>
S1-00147 Use of the element Decide whether and how to use the Use of the element <reqTechInfoGroup> is not allowed.
<reqTechInfoGroup> in the element <reqTechInfoGroup>.
S1-00148 Use of the attribute Decide whether to use the attribute Use of the attribute reqTechInfoCategory is not allowed.
reqTechInfoCategory in the reqTechInfoCategory, which values to
element <reqTechInfoGroup> use and allocate suitable definitions to
Note
Technical information needed, can be
presented in Required technical
information (using the element
<reqTechInfoGroup>) and/or in the
Reference table (using the element
<refs> in the element <content>).
S1-00149 Listing of standard tools in Decide what types of standard tools or Per the following General Civil Aviation usage:
Preliminary requirements toolkits to be identified and listed in the No Civil Aviation business rule.
table "Support equipment".
S1-00150 Use of the attribute id on the Decide whether to use the attribute id to Per the following General Civil Aviation usage:
element <supportEquipDescr> create cross-references from the No Civil Aviation business rule.
in the element procedure to the support equipment
<preliminaryRqmts> listed in Preliminary requirements. The
attribute id on element
<supportEquipDescr> is used to
encouraged.
BRDP
Number
materialUsage in the element materialUsage in the elements No Civil Aviation business rule.
<supportEquipDescr>, the <supportEquipDescr>, <supplyDescr>
element <supplyDescr> and the and <spareDescr> context and what
element <spareDescr> context values to be used.
S1-00152 Use of identification elements in Decide which elements For <supportEquipmentDescr>, the element
the element <catalogSeqNumberRef>
<supportEquipDescr>, the <natoStockNumber>, <identNumber>,
<materialSetRef> shall not be used.
element <supplyDescr> and the <toolRef> and <materialSetRef> to use
element <spareDescr> context for identification and how to populate See the following table for how to populate the
these elements. elements.
If the following Populate the following elements
branch is used
<identNumber> The <manufacturerCode> will contain
the CAGE code unless one is not
assigned, in which case the
manufacturer’s name will be used. If
the item is commercially available, in
place of the CAGE code, the word
"LOCAL" will be used.
The <partAndSerialNumber> will only
utilize the part number sub-element.
The <partNumber> element will contain
the part number or the specification
number of the item.
The <refs> sub-element, if used, will
not be rendered.
<toolRef> The <toolRef @toolNumber> attribute
will contain the tool identifier in the tool
CIR.
The <toolRef
@manuacturerCodeValue> attribute
will contain the CAGE code unless one
is not assigned, in which case the
manufacturer’s name will be used. If
the item is commercially available, in
place of the CAGE code, the word
"LOCAL" will be used.
The <toolRef @specific> attribute, if
used, will not rendered.
BRDP
Number
<supplyRef> The <supplyRef @supplyNumber>
attribute will contain the supply
identifier in the supply CIR.
The <supplyRef
@supplyNumberType> attribute will be
populated according to S1000D and
Civil aviation rules.
<materialSetRef> The <materialSetRef
@materialSetIdent> will contain the
part number of the material set itself.
The <materialSetRef
@materialSetIssue> If used it will
contain the revision number of the
material set indentification.
Items to be indentured under the
material set must use the
<embeddedSupportEquipDescr> or the
<embeddedSupplyDescr> elements.
<natoStockNumber> in the element <natoStockNumber>. The element <natoStockNumber> shall not be used.
element <supportEquipDescr>,
the element <supplyDescr> and
the element <spareDescr>
context
S1-00154 Use of the element Decide whether and how to use the Refer to BRDP-S1-00152.
<materialSetRef> in the element <materialSetRef> in the
elements <supportEquipDescr>, elements <supportEquipDescr>,
<supplyDescr> and <supplyDescr> and <spareDescr>
<spareDescr> context within the context.
S1-00155 Use of the attribute id on the Decide whether to use the attribute id to Per the following General Civil Aviation usage:
element <supplyDescr> in the create cross-references from the No Civil Aviation business rule.
element <preliminaryRqmts> procedure to the supplies listed in
Preliminary requirements. The attribute
id on element <supplyDescr> is used to
BRDP
Number
encouraged.
S1-00156 Use of the attribute id on Decide whether to use the attribute id to Per the following General Civil Aviation usage:
element <sparesDescr> in the create cross-references from the No Civil Aviation business rule.
element <preliminaryRqmts> procedure to the spares listed in
Preliminary requirements. The attribute
id on element <sparesDescr> is used to
will guarantee consistent use
encouraged.
<closeRqmts> in the process <closeRqmts> in the process data No Civil Aviation business rule.
S1-00158 Use of the attribute Decide whether to use the attribute Use of the attribute circuitBreakerAction is not allowed.
circuitBreakerAction in text circuitBreakerAction. If used, establish
element <circuitBreakerRef> writing rules to ensure that authors will
be consistent in the paragraph text and
the value of the attribute itself.
S1-00159 Use of the attribute checkSum Decide whether to use and how to Use of the attribute checkSum is not allowed.
in text element populate the attribute checkSum.
<circuitBreakerRef>
S1-00160 Types of inline significant data Decide whether to use the attribute The attribute significantParaDataType shall be ignored.
to markup using the attribute significantParaDataType and which
significantParaDataType in the types of data to mark up and in what
text element contexts. It must also be considered
<inlineSignificantData> that data modules can be less portable
if the paragraph significant data types
are extended in the BREX file past the
standard types.
S1-00161 Use of the text element Decide whether to use quantity data The element <quantity> shall be used only for quantitative
<quantity> markup and to what extent. The quantity values.
data markup can be used with or
without value and tolerance
decomposition.
S1-00162 Types of quantity data to Decide whether to use the attribute Per the following General Civil Aviation usage:
markup using the attribute quantityType, which values to use in Any of the pre-defined values in S1000D may be used. See
quantityType in the text element what context and allocate suitable Appendix A for additional Civil Aviation specific values that
<quantity> definitions to the values. Refer to Chap may also be used.
3.9.6.1.
Note
BRDP
Number
The project or the organization must
also consider that data modules can be
less portable if the quantity data types
are extended in the BREX file past the
standard types.
S1-00163 Use of the value (element Decide whether and how to use to use Per the following General Civil Aviation usage:
<quantityValue>) and tolerance the element <quantityValue> and the If <quantityValue> is used, any associated tolerances must
(element <quantityTolerance>) element <quantityTolerance> also be tagged using the <quantityTolerance> element.
decomposition in the text decomposition. This does not preclude providing a range of values using
element <quantity> the quantityGroupType attribute.
S1-00164 Unit of measure to be used If using the value and tolerance Per the following General Civil Aviation usage:
decomposition, decide at which level of No Civil Aviation business rule.
the markup the attribute
quantityUnitOfMeasure is to be
included. Allowable locations are on the
parent element <quantityGroup> which
applies to all child elements or on the
individual child elements
<quantityValue> and
<quantityTolerance>. A consistent
usage of the attribute
quantityUnitOfMeasure is required to
produce a consistent display or printout
to the user.
S1-00165 Use of attribute Decide whether to use the attribute Per the following General Civil Aviation usage:
quantityUnitOfMeasure quantityUnitOfMeasure, which values to No Civil Aviation business rule.
Note
Due to the large number of units of
measure, it is expected that a project
will only use a small subset of the
available units of measure. It must also
be considered that data modules can be
less portable if the units of measure
types are extended by the BREX
mechanism past the standard types.
S1-00166 Use of the element <zoneRef> Decide whether to use the element The element <zoneRef> shall not be used.
<zoneRef>, and how to use it.
mismatch of data given in the
BRDP
Number
maintenance planning information has
to be taken.
S1-00167 Use of the element Decide whether to use the element The element <accessPointRef> shall not be used.
<accessPointRef> <accessPointRef> and how to use it.
mismatch of data given in the
maintenance planning information has
to be taken.
S1-00168 Use of the attribute Decide whether to use the attribute The attribute accessPointTypeValue shall not be used.
accessPointTypeValue in the accessPointTypeValue, which values to
text element <accessPointRef> use and allocate suitable definitions to
S1-00169 Use of the text element Decide whether an index is required The element <indexFlag> shall not be used.
<indexFlag> and to what level.
emphasisType in the text emphasisType, which values to use and No Civil Aviation business rule.
element <emphasis> allocate suitable definitions to the
S1-00171 Use of the symbols Decide whether and how to use The element <symbol> shall be used for any inline graphic
symbols using the text element within a text based element.
<symbol>.
S1-00172 Use of footnotes Decide whether and how to use the text Per the following General Civil Aviation usage:
element <footnote> and when used, Footnotes may be used only in Preliminary Requirements
decide whether their use is limited to and tables.
regular text and titles (inline) and/or to
tables (table footnotes).
S1-00173 Types of footnote markers Decide on the types of footnote markers Per the following General Civil Aviation usage:
(attribute footnoteMark) to use. It is Only superscript numbers may be used ("num").
recommended to use:
- only one type of footnote marker for
each of the table footnotes and the
inline footnotes throughout a project
- superscripted numbers for both.
S1-00174 Markup of acronyms Decide whether and how to mark up Per the following General Civil Aviation usage:
acronyms by the use of the text No Civil Aviation business rule for the elements <acronym>
elements <acronym> and <acroterm>. If and <acronymTerm>.
used, decide whether to use the
attribute acronymType, which values to The attribute acronymType may contain only values "at01",
use and allocate suitable definitions to "at02", or "at03".
BRDP
Number
S1-00175 Use of the attribute Decide whether to use the attribute Use of the attribute verbatimStyle is not allowed.
verbatimStyle verbatimStyle, which values to use and
allocate suitable definitions to the
S1-00176 Presentation of controlled Decide the method of presentation for Per the following General Civil Aviation usage:
content controlled content recorded by the Error! Reference source not found.
attributes authorityName and
authorityDocument.
S1-00177 Use of common information Decide whether to use the element Per the following General Civil Aviation usage:
<commonInfo> in procedural, No Civil Aviation business rule.
maintenance planning, common
repositories, and/or fault data modules.
S1-00178 Markup method for common Decide which markup method to use for Per the following General Civil Aviation usage:
information text common information text: No Civil Aviation business rule.
the method containing <note>, <para>
and <commonInfoDescrPara>
or
the method containing only
<commonInfoDescrPara>
S1-00179 Granularity of data in descriptive Decide on the level of granularity of the Per the following General Civil Aviation usage:
data modules descriptive data modules. No Civil Aviation business rule.
S1-00180 Level of depth of descriptive Decide whether to exceed 5 levels of Level of depth will be restricted to 5 levels.
data modules depth for new data.
S1-00181 Minimum para occurrences Decide whether to impose a minimum of It is acceptable to have only 1 child <levelledPara>.
two occurrences of child elements
<levelledPara> and/or
<levelledParaAlts>.
S1-00182 Use of the optional element Decide whether to use the element If <commonInfo> is used, the <title> element is required.
<commonInfo> <commonInfo>, when to use the
element, and give guidance and rules
that will make sure it is consistently
used.
S1-00183 Use of the optional attribute The element <mainProcedure> and the Per the following General Civil Aviation usage:
skillLevelCode element <proceduralStep> can contain The attribute skillLevelCode shall not be used by OEMs,
an indication of the skill level required however may be used by operators, MROs, etc.; for
for the whole procedure and/or for example to develop job cards.
individual steps/substeps using the
attribute skillLevelCode. Decide whether
BRDP
Number
and how to use the attribute
skillLevelCode.
S1-00184 Use of the optional attribute The element <mainProcedure> and the Per the following General Civil Aviation usage:
independentCheck element <proceduralStep> can contain The attribute independentCheck shall not be used by
a check using the attribute OEMs, however may be used by operators, MROs, etc.; for
independentCheck to indicate that the example to develop job cards.
whole procedure and/or individual
steps/substeps must be checked by a
supervisor with a given qualification.
Decide whether and how to use the
attribute independentCheck.
S1-00185 Use of the alternates concept Decide whether to use the alternates The alt concept can be used for only the first level
within the element concept for steps, figures and (//content/procedure/mainProcedure/proceduralStepAlts).
<mainProcedure> multimedia within the element
<mainProcedure>. This concerns the
child elements <proceduralStepAlts>
(refer to Para 2.4.2), <figureAlts> (refer
to Chap 3.9.5.2.1.7) and
<multimediaAlts> (refer to
Chap 3.9.5.2.1.7).
S1-00186 Decide on the maximum Decide on the maximum number of step Per the following General Civil Aviation usage:
number of step levels in a levels allowed in a procedure. A maximum of 8 levels is allowed.
procedure Exceeding five levels of depth is
strongly discouraged in development of
new data. It is recommended that
additional levels are only used in a
conversion effort where the existing
data is authored to this depth (maximum
eight levels) and restructuring of data is
not feasible.
S1-00187 Decide on the minimum number Decide whether to allow for a single It is acceptable to have only 1 child <proceduralStep>.
of substeps in a step substep, or to insist on a minimum of
two substeps in a step.
Note
The Schema allows for a single
substep.
S1-00188 Use of the optional attribute Decide whether to use the attribute Per the following General Civil Aviation usage:
keepWithNext keepWithNext. The attribute keepWithNext shall not be used.
S1-00189 Use of the optional attribute Decide whether and how to use the Per the following General Civil Aviation usage:
itemCharacteristic attribute itemCharacteristic. The attribute itemCharacteristic shall not be used.
BRDP
Number
S1-00190 Use of the optional attribute Decide whether to use the attribute The attribute altsName shall not be used.
altsName altsName for the element
<proceduralStepAlts> for steps.
S1-00191 Use of titles for procedural steps Decide whether and how to use the A primary step in a DM must have a title, even if this replicates
element <title> for steps. techName and infoName.
A step must have a title if any of its sibling steps have a title.
A step can have a title only if its parent step has a title.
S1-00192 Use of correlation fault concept Decide whether to use the correlated Per the following General Civil Aviation usage:
fault concept. No Civil Aviation business rule.
S1-00193 Use of correlated fault Decide how to populate element Per the following General Civil Aviation usage:
messages and warnings <warningMalfunction>, element No Civil Aviation business rule.
<assocWarningMalfunction> and
element <bitMessage> when using the
correlated fault concept.
S1-00194 Use of detection and description Decide whether the repetition of the Per the following General Civil Aviation usage:
information elements detection and description information for No Civil Aviation business rule.
the basic fault which has been
correlated (element <faultDescr> and
element <detectionInfo>) is used.
Projects can consider that the detection
and description information can for
example be populated during IETP
generation by picking up the information
in the detected fault list data module
describing the basic faults.
independentCheck in the independentCheck, which values to use The attribute independentCheck shall not be used by
element <isolationProcedure>, and allocate suitable definitions. OEMs, however it may be used by operators, MROs, etc.
<isolationStep> and
<isolationProcedureEnd>
S1-00196 Use of titles in fault isolation Decide whether to use the element Per the following General Civil Aviation usage:
steps <title> in fault isolation steps. If used, the element <title> shall be used to name the step
or sequence of steps, but shall not contain the action steps
themselves.
S1-00197 Values for the attribute Decide which values to use for the Per the following General Civil Aviation usage:
inspectionTypeCategory attribute inspectionTypeCategoryand No Civil Aviation business rule.
allocate suitable definitions. .
S1-00198 Methodology of assigning tasks Decide on a methodology of assigning Not applicable for CMPs.
into the element <taskGroup> tasks to groups.
BRDP
Number
S1-00199 Use of the attribute markerType Decide whether to use the attribute Not applicable for CMPs.
markerType, which values to use and
S1-00200 Use of the attribute Decide whether to use the attribute Not applicable for CMPs.
worthinessLimit worthinessLimit, which values to use
and allocate suitable definitions.
S1-00201 Use of the attribute Decide whether to use the attribute Not applicable for CMPs.
reducedMaint reducedMaint, which values to use and
S1-00202 Values for the attribute Decide which values to use for the Not applicable for CMPs.
sourceOfRqmt attribute sourceOfRqmt allocate suitable
definitions.
S1-00203 Use of the attribute approval Decide whether to use the attribute Not applicable for CMPs.
approval, which values to use and
S1-00204 Use of the element Decide whether to use the element Not applicable for CMPs.
<preliminaryRqmts> in the <preliminaryRqmts>.
element <taskDefinition>
S1-00205 Use of attribute Decide whether to use the attribute Not applicable for CMPs.
supervisorLevelCode supervisorLevelCode, which values to
S1-00206 Use of element Decide whether to use of the element Not applicable for CMPs.
<timeLimitCategory> <timeLimitCategory> and define the
values for the attribute
timeLimitCategoryValue.
S1-00207 Per the following General Civil Aviation usage:
thru S1- Not applicable for Civil Aviation applications.
00214
initialProvisioningProjectNumber initialProvisioningProjectNumber No Civil Aviation business rule.
(IPPN) (IPPN). The codes must not be
duplicated within a project.
<natoStockNumber> (NATO NATO Stock Number, split it into its The element <natoStockNumber> shall not be used.
stock number) three fields using the attributes
natoSupplyClass,
natoCodificationBureau and
natoItemIdentNumberCore or to fill it as
a whole in the child element
<fullNatoStockNumber>.
BRDP
Number
S1-00217 Use of hotspots in IPD data Decide whether to use the generic Per the following General Civil Aviation usage:
modules hotspot mechanism in IPD data No Civil Aviation business rule.
modules.
S1-00218 Use of the attribute partStatus in Decide whether to use the attribute Per the following General Civil Aviation usage:
the element <itemSeqNumber> partStatus in the element No Civil Aviation business rule.
<itemSeqNumber>, which values to use
<partSegment> in the element <partSegment> to store the part data in No Civil Aviation business rule.
<itemSeqNumber> the IPD data module each time the part
is listed or whether to store the part data
once externally in the part CIR data
module.
Note
The element <partSegment> must be
used for S2000M IPD data modules.
<partKeyword> in the element element <partKeyword>. If used, <partKeyword> must contain the value provided in
<itemSeqNumber> the ATA Spec 2000 Initial Provisioning data.
S1-00221 Use of the element Decide whether to use the element The element <physicalSecurityPilferageCode> shall not be
<physicalSecurityPilferageCode <physicalSecurityPilferageCode> and used.
> in the element <techData> define a list of values. When S2000M is
within the element used, the list must be as stated in the
<itemSeqNumber> data element definition for the S2000M
element PSC.
S1-00222 Use of the attribute Decide on the range and definitions of The attribute unitOfMeasure shall not be used.
unitOfMeasure in the element the values for the attribute
<unitOfIssueQualificationSegme unitOfMeasure.
nt> within the element
<itemSeqNumber> Note
When the IP data modules are created
from S2000M, the list of allowed UOM
values must contain those defined in the
data element definition in S2000M.
When S2000M is used, it is strongly
recommended to use the S2000M UOM
values throughout the project.
S1-00223 Use of the element Decide on the method of identification of Either of the following methods to identify Optional parts shall
<optionalPart> in the element the optional part. be allowed:
BRDP
Number
<partRefGroup> within the • By Part Number and Manufacturer Code, or
element <itemSeqNumber> • By reference to the CSN where the part is described.
S1-00224 Use of the element Decide on the method of identification of Either of the following methods to identify Preferred Spare Parts
<preferredSparePart> in the the preferred spare part. shall be allowed:
element <partRefGroup> within • By Part Number and Manufacturer Code, or
the element <itemSeqNumber> • By reference to the CSN where the part is described.
S1-00225 Use of the element Decide on the method of identification of Either of the following methods to identify Altered From parts
<alteredFromPart> in the the altered from part. shall be allowed:
element <partRefGroup> within • By Part Number and Manufacturer Code, or
the element <itemSeqNumber> • By reference to the CSN where the part is described.
S1-00226 Use of the element Decide on the method of identification of Per the following General Civil Aviation usage:
<localFabricationMaterial> the local fabrication material. Manufactured from parts shall be identified by Part Number
and Manufacturer Code.
S1-00227 Use of the element Decide whether to use the element If the <selectOrManufactureFromIdent> element is used, the
<selectOrManufactureFromIdent <selectOrManufactureFromIdent>. If attribute selectOrManufactureValue must be f, t, m or r. (the
> in the element used, decide on its range and the value "p" cannot be used)
<partLocationSegment> within definition of the values to be used.
S1-00228 Use of restricted operation Decide whether to use the element Per the following General Civil Aviation usage:
notes <restrictedOperationNote>. No Civil Aviation business rule.
S1-00229 Use of the element Decide whether and how to use the The element <usableOnCodeEquip> will not be used.
<usableOnCodeEquip> in the element <usableOnCodeEquip>. If
element <applicabilitySegment> used, decide on its range and the
within the element definition of the values to be used.
<itemSeqNumber> When S2000M is used, the list must be
as stated in the data element definition
for the S2000M element UCE.
S1-00230 Use of the element Decide whether and how to use the One or several item variants are allowed, each being 1 to 3
<usableOnCodeAssy> in the element <usableOnCodeAssy>. If used, characters, separated by a comma and a space.
element UCA.
S1-00231 Use of the element Decide whether and how to use the The element <interchangeability> shall not be used.
<interchangeability> in the element <interchangeability>. If used,
element ICY.
BRDP
Number
00235
S1-00236 Use of the attributes Decide whether to use the attributes Per the following General Civil Aviation usage:
condNumber, condNumber, manufacturerCodeValue No Civil Aviation business rule.
manufacturerCodeValue and and condType.
condType in the element
<changeAuthorityData> within
S1-00237 Use of the BREX to define the Decide whether to use the BREX for the CMP will use a BREX to define non-S2000M elements.
non S2000M elements definition of the non S2000M elements.
S1-00238 Use of wiring data description Decide whether to produce wiring data Per the following General Civil Aviation usage:
data modules description data modules in order to Wiring data description data modules shall not be used.
reflect all decisions concerning
elements and attributes of the wiring
data Schema.
S1-00239 Use of the element <wireType> Decide on the definition of wire type Per the following General Civil Aviation usage:
content/codes. No Civil Aviation business rule.
S1-00240 Use of the element Decide whether and how to use the wire Per the following General Civil Aviation usage:
<wireSeqNumber> sequential number. The element <wireSeqNumber> shall not be used. The
wire sequential number must be included in the
Note: <wireNumber> element.
The element <wireSeqNumber> must
be used if the wire sequential number is
not given in the element <wireNumber>.
S1-00241 Use of the element Decide whether and how to use Wiring schema will not be used.
<electricalEquipConnection> electrical equipment connection
information, in particular define the
values of attribute connectionType
consistently.
00249
<commonInfo> in CIR element <commonInfo> in CIR. No Civil Aviation business rule.
S1-00251 Use of the attribute altNumber in Decide whether to use the attribute Per the following General Civil Aviation usage:
the functional items CIR altNumber, which values to use and No Civil Aviation business rule.
values.
S1-00252 Use of the attribute altNumber in Decide whether to use the attribute The circuit breaker CIR shall not be used.
the circuit breakers CIR altNumber, which values to use and
BRDP
Number
values.
S1-00253 Use of the attribute Decide which values (eg, subzones) to The zones CIR shall not be used.
zoneRefType use for the attribute zoneRefType and
S1-00254 Use of the attribute altNumber in Decide whether to use the attribute The zones CIR shall not be used.
the zones CIR altNumber, which values to use and
values.
S1-00255 Use of the attribute Decide which values (eg, subaccess The access points CIR shall not be used.
accessPointRefType points) to use for the attribute
accessPointRefTypeand allocate
S1-00256 Use of the attribute altNumber in Decide whether to use the attribute The access points CIR shall not be used.
the access points CIR altNumber, which values to use and
values.
S1-00257 Use of the attribute lowestLevel Decide which values to use for the Per the following General Civil Aviation usage:
in the supplies CIR attribute lowestLevel and allocate The attribute lowestLevel shall not be used by OEMs;
suitable definitions. Refer to however it may be used by operators.
Chap 3.9.6.1.
S1-00258 Use of the supply requirement Decide whether to implement supply Per the following General Civil Aviation usage:
CIR data module or not requirement CIR data module. No Civil Aviation business rule.
S1-00259 Use of a single or multiple Decide whether there is one single As there is only one SNS per CMP, only a single supply
supply requirement CIR data supply requirement CIR data module or requirement CIR per CMP is permitted.
module several depending on the SNS. The
application of the SNS determines the
granularity of these data modules.
S1-00260 Use of the attribute toolRefType Decide which values to use for the Per the following General Civil Aviation usage:
in the tools CIR attribute toolRefType and allocate No Civil Aviation business rule.
S1-00261 Use of the attribute altNumber in Decide whether to use the attribute Per the following General Civil Aviation usage:
the tools CIR altNumber, which values to use and No Civil Aviation business rule.
values.
S1-00262 Use of the attribute Decide which values (eg, servicing, Per the following General Civil Aviation usage:
taskCategoryCode in the tools maintenance, overhaul, repair) to use No Civil Aviation business rule.
CIR for the attribute taskCategoryCode and
BRDP
Number
S1-00263 Use of the attribute Decide whether to manage the system The functional and/or physical areas CIR shall not be used.
systemDiffCode in the element difference code in the functional and/or
<functionalPhysicalAreaIdent> physical areas CIR data module.
S1-00264 Use of the attributes Decide whether to manage the The functional and/or physical areas CIR shall not be used.
disassyCode and disassembly code and disassembly
disassyCodeVariant in the variant code in the functional and/or
element physical areas CIR data module.
<functionalPhysicalAreaIdent>
S1-00265 Use of the container data Decide whether to use the container Per the following General Civil Aviation usage:
module data module. No Civil Aviation business rule.
S1-00266 Use of applicability within Decide whether applicability annotations Per the following General Civil Aviation usage:
container data module content are duplicated from the referenced data If the container DM is delivered as part of the exchange
modules to the container data module. package, applicability shall be duplicated from the
referenced data modules to the container data module.
S1-00267 Conducting a performance Decide whether to conduct a The learning data module shall not be used.
analysis performance analysis to determine
factors that can affect performance and
gaps in job performance or a training
needs analysis to determine training
requirements.
S1-00268 Developing learning objectives Decide whether to develop learning The learning data module shall not be used.
objectives in accordance with task
analysis items. Learning objectives
ought to be developed in accordance
with task analysis items that support
system maintenance and operational
procedures. Aligning learning objectives
with task analysis items in the early
content preplanning stages will foster
reusable data and content alignment.
Refer to Chap 3.9.7 for content
preplanning discussions.
S1-00269 Packaging lesson plans in Decide whether to package lesson The learning data module shall not be used.
SCORM content packages plans in SCORM content packages.
S1-00270 Define life cycle need for Define life cycle need for analysis The learning data module shall not be used.
performance analysis data information and requirements resulting
from a Performance Analysis for the
client organization and human
performance system affected by the
product.
S1-00271 Define life cycle need for Define life cycle need for analysis The learning data module shall not be used.
training needs analysis data information and requirements resulting
BRDP
Number
from a Training Needs Analysis for a
training intervention.
S1-00272 Use of element <dmRef> to link Decide whether to use of the element The learning data module shall not be used.
content data to learning <dmRef> to establish references to
objective items content data supporting learning
objective items.
S1-00273 Use of the attribute Decide whether to assign weighted The learning data module shall not be used.
weightingFactor values to individual interactions.
S1-00274 Use of the attribute attempts Decide whether to allow multiple The learning data module shall not be used.
response attempts for interaction items.
checkListCategory checkListCategory, which values to use No Civil Aviation business rule.
S1-00276 Use of the element Decide whether to use the element Maintenance checklists shall not be used. Procedural DMs shall
<checkListIntervals> <checkListIntervals>. be used instead.
S1-00277 Use of the element Decide whether and how to use the Maintenance checklists shall not be used. Procedural DMs shall
<checkListProcedure> element <checkListProcedure> and its be used instead.
subelements.
S1-00278 Use of the element Decide whether to use the element Maintenance checklists shall not be used. Procedural DMs shall
<equipmentNotAvailable> <equipmentNotAvailable>. be used instead.
S1-00279 Define maximum number of Projects must decide the maximum Per the following General Civil Aviation usage:
steps levels in number of step levels allowed. No Civil Aviation business rule.
<checkListProcedure>
S1-00280 Use of the attribute Decide which topic type values are The Service Bulletin schema shall not be used.
sbTopicType in the element mandatory, which are optional and the
<sbRevisionInfo> sequence in which they must be
<sbRevisionInfo>. Refer to
Chap 3.9.6.1.
<sbSummary> sequence in which they must be
delivered in the element <sbSummary>.
S1-00282 Use of the attribute Decide which topic values are The Service Bulletin schema shall not be used.
<sbPlanningInfo> sequence in which they must be
<sbPlanningInfo>. Refer to
Chap 3.9.6.1.
BRDP
Number
<sbAdditionalInfo> sequence in which they must be
<sbAdditionalInfo>. Refer to
Chap 3.9.6.1.
S1-00284 Use of the attribute Decide whether to use the attribute The Service Bulletin schema shall not be used.
sbModificationClassification sbModificationClassification, which
values to use and allocate suitable
definitions to the values. Refer to
Chap 3.9.6.1.
element use and allocate suitable definitions to
<genericPropertyGroup> in the the values. Refer to Chap 3.9.6.1.
element <sbManagementInfo>
sbMaterialType sbMaterialType, which values to use
S1-00287 Use of the element Decide whether the use of the element The Service Bulletin schema shall not be used.
<sbProcurementInfo> <sbProcurementInfo>
is allowed directly within the element
<sbMaterialSet>
of individual spares, supplies and
support equipment
S1-00288 Use of the element Decide whether the use of the element The Service Bulletin schema shall not be used.
<sbIndustrySupport> <sbIndustrySupport>
is allowed directly within
<sbMaterialSet>
BRDP
Number
of individual spares, supplies and
support equipment
sbMaterialIdent sbMaterialIdent.
sbMaterialIssue sbMaterialIssue.
element use and allocate suitable definitions to
<genericPropertyGroup> within the values. Refer to Chap 3.9.6.1.
the element
<sbIndividualRemovedSpare> The predefined values are "gpt10" and
"gpt11".
materialUsage in the element genericPropertyType, which values to
<sbRemovedSpareDescr> use and allocate suitable definitions to
sbReplacementType sbReplacementType.
S1-00294 Content of the element Decide whether to use the element Per the following General Civil Aviation usage:
<productIntroName> <productIntroName>. Not applicable for Civil Aviation applications.
<productAndModel> element <productAndModel> and its Not applicable for Civil Aviation applications.
child elements.
<dataRestrictions> in the element <dataRestrictions> and its child Not applicable for Civil Aviation applications.
element <frontMatterTitlePage> elements.
<enterpriseSpec> in the element <enterpriseSpec>. Not applicable for Civil Aviation applications.
element <frontMatterTitlePage>
<enterpriseLogo> <enterpriseLogo> and if it is populated Not applicable for Civil Aviation applications.
from the element <logo> given in the
Identification and status section.
S1-00299 Method of populating the Decide whether and how to use the Per the following General Civil Aviation usage:
element <publisherLogo> element <logo> in the Identification and Not applicable for Civil Aviation applications.
status section to populate the element
<publisherLogo>.
barCodeSymbology barCodeSymbology and which barcode Not applicable for Civil Aviation applications.
symbology to be used.
BRDP
Number
<frontMatterInfo> element <frontMatterInfo> including the Not applicable for Civil Aviation applications.
allowed values of attribute
frontMatterInfoType and their
interpretation as titles at presentation.
Note
The content given in the element <title>
takes precedence over the
interpretation of the value of attribute
frontMatterInfoType.
S1-00302 Use of the element <title> in the Decide whether to use the content of Per the following General Civil Aviation usage:
element <frontMatterInfo> the element <title> or the interpretation Not applicable for Civil Aviation applications.
of the value of the attribute
frontMatterInfoType as the title of the
Front matter information.
S1-00303 Use the element Decide whether to use the introductory Per the following General Civil Aviation usage:
<reducedPara> in the element paragraph and on the wording of any Not applicable for Civil Aviation applications.
<frontMatterTableOfContent> standard phrase.
S1-00304 Use of hierarchical Table of Decide whether to use a hierarchical Per the following General Civil Aviation usage:
contents Table of contents and on the number of Not applicable for Civil Aviation applications.
levels.
S1-00305 Use of the element <pmRef> in Decide whether publications have to be Per the following General Civil Aviation usage:
the element <tocEntry> listed by the publication only or also by Not applicable for Civil Aviation applications.
its individual data modules.
S1-00306 Use of issue number and/or Decide whether to use and present the Per the following General Civil Aviation usage:
issue date in the Table of issue number Not applicable for Civil Aviation applications.
contents (<issueInfo>/<externalPubIssueInfo>)
and/or the issue date
(<issueDate>/<externalPubIssueDate>)
for the entries in the Table of contents.
<numberOfPages> in the <numberOfPages> and if the number of No Civil Aviation business rule.
element <tocList> pages are to be presented.
S1-00308 Use of HIGH with updating Decide whether to use HIGH with Per the following General Civil Aviation usage:
instruction updating instruction. Not applicable for Civil Aviation applications.
S1-00309 Use the element Decide whether to use the introductory Per the following General Civil Aviation usage:
<reducedPara> in the element paragraph and on the wording of any Not applicable for Civil Aviation applications.
<frontMatterLists> standard phrase for each of the front
matter list.
BRDP
Number
S1-00310 How to store total number of Decide on the use of Per the following General Civil Aviation usage:
pages for S1000D publications <footnoteRemarks> to store the total Not applicable for Civil Aviation applications.
number of pages for a complete
S1000D publication (PM).
S1-00311 How to store total number of Decide on the use of Per the following General Civil Aviation usage:
pages for non-S1000D <footnoteRemarks> to store the total Not applicable for Civil Aviation applications.
publications number of pages for a complete non-
S1000D publication.
S1-00312 Use of the attribute Decide whether to use the attribute The SCO schema shall not be used.
scoEntryType scoEntryType, which values to use and
S1-00313 Use of the element Decide whether and how to use the The SCO schema shall not be used.
<contentDescription> in the element <contentDescription> (eg, to
element <scoContent> add information about the training
resource).
S1-00314 Use of the element Decide whether and how to use the The SCO schema shall not be used.
<contentDescription> in the element <contentDescription> (eg, to
element <trainingStep> add information about the content
defined in the training step).
S1-00315 Use of the element Decide whether the optional element The SCO schema shall not be used.
<contentDescription> <contentDescription> must be used to
add information about the content
defined in the training step.
S1-00316 Use of the element <applic> in Decide how to use the element <applic> Either the <applicRef> or the <applic> element may be used.
the data module status and and to populate its child elements and However, either an <assert> or <evaluate> element tied to a
content attributes across the project. product attribute and/or condition is required for data modules
that are not applicable to "All".
Example:
ON P/N F53132000000 (POST SB A340322-53-001)
<evaluate andOr="and">
<assert applicPropertyIdent="pnr"
applicPropertyType="prodattr"
applicPropertyValues="F53132000000"/>
<assert applicPropertyIdent="SB-A340322-53-001"
applicPropertyType="condition"
applicPropertyValues="POST"/>
</evaluate>
S1-00317 Use of the element Decide whether the element Per the following General Civil Aviation usage:
<displayText> in the element <displayText> is populated by the The following two cases are to be considered:
<applic> technical author or generated from the 1) The human readable applicability annotation to be
BRDP
Number
computable branch or some other displayed can be calculated from the computable formula:
source when using the human readable The project can choose to generate systematically the
branch of applicability. element <displayText> or not.
If the element <displayText> is not generated, it is up to the
IETP to generate the human readable applicability
annotation from the computable formula.
2) The human readable applicability annotation to be
displayed is manually authored:
The manual authoring of the human readable applicability
annotation shall only be used:
- to summarize a complex formula, or
- when no formula is possible.
If the applicability annotation is manually authored, the
element <displayText> has to be populated.
In any case, if <displayText> is used, it must not contradict
the computable applicability annotation.
applicDisplayClass within the applicDisplayClass, when using the If the element <displayText> is not generated or populated,
element <applic> computable applicability annotation it is up to the project to decide whether attribute
branch. applicDisplayClass needs to be used or not.
If used, the following values shall be used:
"confirmed" for assertions without conditions. By
comparison to ATA iSpec 2200, it could correspond to
assertions that are equivalent to <effect>/@effrg.
"conditional" for assertions with conditions. By comparison
to ATA iSpec 2200, it could correspond to assertions that
are equivalent to <sbeff> or <coceff>. It also concerns
operational condition assertions.
The project can define additional values if necessary.
The <applic @applicDisplayClass> attribute, if used, will not be
rendered.
S1-00319 Use of textual applicability Decide if textual applicability Textual applicability annotations in the element <assert> are
annotations in the element annotations are allowed in the element not allowed.
<assert> in the element <assert> when using the computable
<evaluate> applicability annotation branch or if
every element <assert> should
reference a declared product attribute or
condition.
BRDP
Number
S1-00320 Use of the attribute valuePattern Decide whether to specify the allowable Per the following General Civil Aviation usage:
and the element <enumeration> values for a product attribute achieved This remains a project specific decision but when used the
or to use open text when using by using both the attribute valuePattern following rules have to be applied:
ACT and the element <enumeration> or to
allow open text without using the For a given product attribute defined in the ACT, either an
attribute valuePattern and the element enumeration or a value pattern or an open text is allowed.
<enumeration>. The combination of enumeration and value pattern is not
allowed.
<displayName> in the element <displayName>. No Civil Aviation business rule.
ACT
S1-00322 Method of defining multiple Decide whether to use a single element Per the following General Civil Aviation usage:
values or ranges for the element <enumeration> containing the entire set No Civil Aviation business rule.
<enumeration> in the ACT or to use multiple elements
<enumeration> where each contains
only one value or range.
S1-00323 Use of the attribute valuePattern Decide whether to specify the allowable Per the following General Civil Aviation usage:
and the element <enumeration> values for a product attribute achieved Only one of <enumeration>, valuePattern, or open text may
or to use open text when using by using both the attribute valuePattern be used for a given condType. Open text is not
CCT and the element <enumeration> or to recommended.
allow open text without using the
attribute valuePattern and the element
<enumeration>.
S1-00324 Method of defining multiple Decide whether to use a single element Per the following General Civil Aviation usage:
values or ranges for the element <enumeration> containing the entire set No Civil Aviation business rule.
<enumeration> in the CCT or to use multiple elements
<enumeration> which each contain only
one value or range.
<displayName> in the element <displayName>. No Civil Aviation business rule.
CCT
S1-00326 Constraining conditions by use Decide whether to constrain allowable Per the following General Civil Aviation usage:
of the element <dependency> in conditions based on other condition No Civil Aviation business rule.
the element <cond> in the CCT values by use of the element
<dependency>.
S1-00327 Product attributes and Decide which product attributes and The following minimum set of civil aviation standard product
conditions to include in the PCT conditions to include in the PCT. attributes and condition types are defined for CMP. This
Conditions that represent operational or definition is based on the current ATA standard. All the product
environmental properties will usually not attributes do not have to be used.
be included in the PCT as they are not
associated with a product instance.
BRDP
Number
Product instance identifiers
Required:
1. Part Number (PNR): product attribute id = pnr
2. Manufacturer Code (MFR): product attribute id = mfr
One or more required:
1. Model: product attribute id = model
2. Component Nomenclature: product attribute id = cmpnom
Optional:
1. Alternate Part Number: product attribute id = altpnr
2. Old Part Number: product attribute id = oldpnr
3. Old Manufacturer Code: product attribute id = oldmfr
Condition types
1. Service bulletins: condition type id = sb, enumeration =
PRE|POST.
The only allowable service bulletin applicability assertion values
for DMs are "PRE" and "POST".
When using PRE|POST in a PCT, the service bulletin
applicability assertion value of:
• PRE resolves to true if the SB condition is PRE, or
• PRE resolves to false if the SB condition is POST, or
• POST resolves to true if the SB condition is POST, or
• POST resolves to false if the SB condition is PRE, or
• PRE and POST each resolve to true if the SB condition is null
or missing.
S1-00328 Translation of the "S1000D Decide whether to translate and use the Per the following General Civil Aviation usage:
interpretation" of configurable "S1000D interpretation" of configurable No Civil Aviation business rule.
attribute values attribute values in the languages
adopted by the project.
Note
At no time must a project allocate
values outside the ranges given in the
subchapters.
BRDP
Number
S1-00329 Application of project specific Decide whether to use any project Per the following General Civil Aviation usage:
values for configurable specific attribute values, which values to Project-configurable attribute values and their meanings
attributes use and allocate suitable definitions and shall be registered by TDWG and published in Appendix A
interpretations. of ATA Spec 1000BR. Projects may not use a registered
value for other than its stated meaning. Projects may
Note request additional project-configurable attribute values. See
instructions in Appendix A.
There are specific business rules
decision points for some of the
configurable attributes given in the
authoring chapters. Refer to Chap 3.9.5
and its subchapters.
S1-00330 Application of project specific Decide if any project specific attribute Per the following General Civil Aviation usage:
values for the attribute values are needed for the attribute No Civil Aviation business rule.
quantityUnitOfMeasure quantityUnitOfMeasure. If needed,
decide which project specific values to
use for the attribute
quantityUnitOfMeasure and allocate
S1-00331 Data module coding strategy Decide on the data module coding Refer to BRDP-S1-00332 through BRDP-S1-00349.
strategy to use for the Product and/or
the project.
S1-00332 Allocation of Product model Decide which model identification codes Per the following General Civil Aviation usage:
identification code to use for the Product. No Civil Aviation business rule.
S1-00333 Allow the use of one or several Decide whether to allow the use of one Per the following General Civil Aviation usage:
model identification codes or several model identification codes. No Civil Aviation business rule.
S1-00334 Allocation of system difference Decide which system difference code Per the following General Civil Aviation usage:
code values to be used for the Product. No Civil Aviation business rule.
S1-00335 UOC as system difference code Decide whether to use UOC as the Per the following General Civil Aviation usage:
system difference code. No Civil Aviation business rule.
S1-00336 Product SNS structure Decide which SNS structure to use for Only the ATA iSpec 2200 SNS shall be used with the exception
the Product. that the chapter 00 breakdown from the S1000D "Maintained
SNS – Generic" is also allowed.
S1-00337 Use of material item category Decide on the use of the material item Per the following General Civil Aviation usage:
code category code. For Civil Aviation projects which use the "Air vehicle,
engines and equipment" SNS (Chapter 8.2.5), for System
42, Chapter 8.2.5 Table 26 shall be used. For System 46,
Chapter 8.2.5 Table 31 shall be used. In joint civil/defense
programs, the Material Item Category Code "J" shall be
used for Systems 42 and 46 in Civil Aviation data modules,
and "E" shall be used for Systems 42 and 46 in Defense
BRDP
Number
data modules. All other usage of Material Item Category
Code is optional.
S1-00338 Number of characters in Decide whether to use two or four The Assembly Code shall be 2 characters to support ATA Spec
assembly code characters for unit or assembly. 2000 requirements.
S1-00339 Responsible partner company Decide which responsible partner Per the following General Civil Aviation usage:
codes for non-chapterized company codes to use for non- Not applicable for Civil Aviation applications.
illustrated parts data modules chapterized illustrated parts data
modules.
S1-00340 Responsible partner company Decide which responsible partner Per the following General Civil Aviation usage:
codes for non-chapterized, non- company codes to use for non- No Civil Aviation business rule.
S2000M illustrated parts data chapterized, non-S2000M illustrated
modules parts data modules.
S1-00341 Unique identifier for non- Decide which unique identifiers to use Per the following General Civil Aviation usage:
chapterized, non-S2000M for non-chapterized, non-S2000M No Civil Aviation business rule.
illustrated parts data modules illustrated parts data modules.
S1-00342 Use of the disassembly code Decide whether to use one, two or three Per the following General Civil Aviation usage:
variant characters for the disassembly code One, two, or three characters may be used. The values "Z",
variant and how to populate. "ZZ" and "ZZZ" are reserved for the container data
modules.
S1-00343 Use of numeric values in the Decide whether to use numeric values Per the following General Civil Aviation usage:
information code variant in addition to alphabetic values in the Numeric values are not allowed. The value "Z" is reserved
information code variant. for the container data module.
S1-00344 Use of CAGE code and/or Decide which method to be used for the Per the following General Civil Aviation usage:
model identification code based ICN. No Civil Aviation business rule.
ICN
S1-00345 Presentation of ICN within the Decide whether the ICN is presented Per the following General Civil Aviation usage:
illustration reproduction area within the illustration reproduction area. The ICN must be presented. For page-oriented
publications, the ICN must be presented outside the
illustration reproduction area. Optionally, the ICN may also
be presented inside the illustration reproduction area.
S1-00346 Security classifications to be Decide whether to use the project´s or Per the following General Civil Aviation usage:
used for CAGE code based ICN the originator's classification rules. No Civil Aviation business rule.
S1-00347 Structure and rules for ICN for Decide which structure to use for the Per the following General Civil Aviation usage:
model identification code based ICN (eg, only numerical, fixed length, No Civil Aviation business rule.
ICN use of character set).
S1-00348 Allocation of responsible partner Decide which values on responsible Per the following General Civil Aviation usage:
company codes for model partner company codes to be used. No Civil Aviation business rule.
identification code based ICN
BRDP
Number
S1-00349 Security classifications to be Decided which security classifications to Per the following General Civil Aviation usage:
used for model identification use. No Civil Aviation business rule.
based ICN
S1-00350 Use of data management Decide whether to use the data Per the following General Civil Aviation usage:
requirement list management requirement list for No Civil Aviation business rule.
specification and exchange of CSDB
planning information.
S1-00351 Object types to be listed in the Decide whether to list publication Per the following General Civil Aviation usage:
data management requirement modules and/or IPD illustrations in the No Civil Aviation business rule.
list data management requirement list.
S1-00352 Use of CSDB status list Decide whether to use the CSDB status With the exception of engine CMPs, the CSDB Status List
list for exchange of CSDB status (CSL) shall be provided with each exchange package. The CSL
information. is optional for engine CMPs.
S1-00353 Objects types to be tracked by Decide what CSDB objects types are to Per the following General Civil Aviation usage:
the CSDB status list be tracked in the CSDB status list, and No Civil Aviation business rule.
at a minimum these must be data
modules, illustrations/multimedia
objects and publication modules.
S1-00354 CSDB object issues to be Decide whether to include only the For delivery of a CMP data package, only the latest issue of the
included in the CSDB status list latest issues of CSDB objects or all active objects delivered as part of the package and those
issues in the CSDB status list. deleted objects from the previous issue of the CSL will be
included in the subsequent CSL.
S1-00355 Data management requirement Decide whether the issue date of a data Per the following General Civil Aviation usage:
list issue date management requirement list must be No Civil Aviation business rule.
the input date (the release to CSDB
date), the cut-off date for the
information, the planning date or some
other more appropriate date.
S1-00356 Use of the comment form Decide whether to use the comment Per the following General Civil Aviation usage:
form. The comment form shall not be used.
S1-00357 Use of attribute commentPriority Decide which values to use for the Per the following General Civil Aviation usage:
attribute commentPriority and allocate The element <commentPriority> shall not be used. See
suitable definitions. Refer to Chap BRDP-S1-00356.
3.9.6.1.
S1-00358 Use of the attribute Decide which values to use for the Per the following General Civil Aviation usage:
responseType in the element attribute responseType and allocate The attribute responseType shall not be used. See BRDP-
<commentResponse> suitable definitions. Refer to Chap S1-00356.
3.9.6.1.
S1-00359 Allowed file types for Decide which file types are allowed for Per the following General Civil Aviation usage:
attachments to comment forms attachments to comment forms. No attachments are allowed. See BRDP-S1-00356.
BRDP
Number
S1-00360 Raster graphic resolution Decide which resolution to use for raster Per the following General Civil Aviation usage:
graphics. No Civil Aviation business rule.
S1-00361 Use of photographs Decide whether photographs will be Per the following General Civil Aviation usage:
used. If used, for what purposes. The use of photographs is permitted in accordance with the
ATA iSpec 2200 3-1-12.4 Graphic Style Standards.
S1-00362 Use of logotypes in the Decide whether logotypes are used in Per the following General Civil Aviation usage:
publication module the publication module and the usage in No Civil Aviation business rule.
front matter data module.
S1-00363 Use of the element Decide whether to use the element If systemBreakdownCode is included in the PMs it will be
<systemBreakdownCode> in <systemBreakdownCode>. If used, ignored by CMP. Refer to BRDP-S1-00078.
the publication module status define the content of the element
information consistent across the project.
S1-00364 Use of the element <remarks> Decide whether to use the element If used, <remarks> will be ignored.
in the publication module status <remarks>. If used, its use must be
information defined in the project business rules
and guidance given.
S1-00365 Use of the attribute pmIssuer Decide on the use of the attribute Per the following General Civil Aviation usage:
pmIssuer. CAGE Code shall be used.
S1-00366 Use of a project specific BREX Decide whether to develop and use a Per the following General Civil Aviation usage:
data module project specific BREX data module. No Civil Aviation business rule.
S1-00367 Use of layered BREX data Decide whether to apply a layered Per the following General Civil Aviation usage:
modules BREX data module structure. This No Civil Aviation business rule.
decision is related to, but not entirely
dependent on, whether a layered
business rules structure applies.
S1-00368 Applicable sets of business Decide which set or sets of business Per the following General Civil Aviation usage:
rules rules are allowed within the given No Civil Aviation business rule.
project or the organization. Accordingly,
decide which BREX data modules will
be used to reflect those business rules.
S1-00369 Use of the BREX data module Decide whether to use the BREX data Per the following General Civil Aviation usage:
to exchange SNS module for exchange of information on No Civil Aviation business rule.
the applied SNS.
S1-00370 Include restrictions in using Decide whether to use the BREX data Per the following General Civil Aviation usage:
various illustration, multimedia module to impose any restrictions in the The BREX shall not be used to impose restrictions on the
object or other data information use of various formats for illustrations, formats for graphic/multimedia objects.
formats multimedia objects or other data.
S1-00371 Use of the process data module Decide whether to use the process data Per the following General Civil Aviation usage:
module. Process data modules shall not be used.
BRDP
Number
S1-00372 Use of the generic IC 951 for Decide whether to use IC 951 for Per the following General Civil Aviation usage:
identification of process data identification of process data modules. IC 951 shall not be used.
modules
S1-00373 Use of multiple instances of Decide whether to generate multiple Per the following General Civil Aviation usage:
CSDB object instances of CSDB objects to generate No Civil Aviation business rule.
several customized instances of any
one object issue. If so, decide how the
attributes extensionProducer and
extensionCode must be used.
S1-00374 Use of the CIR concept (internal Decide whether to use the CIR concept. The CIR concept shall be used. See BRDP-S1-00377.
databases for common
information)
S1-00375 Use of CIR data modules Decide whether to produce CIR data Per the following General Civil Aviation usage:
modules. No Civil Aviation business rule.
S1-00376 Internal/External use of CIR Decide whether the CIR data modules CIR data modules are a deliverable to the customer. The
data modules are to be used only internally to the Enterprise CIR data module must be provided as a deliverable
manufacturer or integrator, as part of to the customer. Other CIRs must also be provided if
the production/integration environment referenced in the delivered data module.
("internal repositories") or if the CIR
data modules are also a deliverable to
the customer.
S1-00377 Types of CIR data modules to Decide which CIR data module types to For CMP usage:
be used be used. In order to avoid any Enterprise information - Required
redundancy and inconsistency, care Functional items - Not allowed
must be paid on some types, depending Parts - Optional
on other project specific decisions, for Zones - Not allowed
example tailoring of the S2000M (IPD Supplies - Optional
data modules vs Part CIR data module). Supplies, requirements - Optional
Tools - Optional
Applicability annotations - Optional
Warnings - Optional
Cautions - Optional
Circuit breakers - Not allowed
Functional and/or physical areas - Not allowed
Access points - Not allowed
Controls and indicators - Not allowed
S1-00378 Delivery of CIR-dependent data Decide whether CIR-dependent data Per the following General Civil Aviation usage:
module modules are delivered to customer, as it CIR-dependent data modules may be delivered to the
implies a specific process to retrieve the customer. If CIR-dependent data modules are delivered,
self-standing data modules from the then the corresponding CIR data modules must also be
CIR-dependent data module and the delivered.
CIR data module.
BRDP
Number
S1-00379 Publishing of CIR data modules Decide whether and which CIR data Per the following General Civil Aviation usage:
module types to be published. No Civil Aviation business rule.
S1-00380 Use of one or several data Decide whether there is one single or There shall be only one instance of each CIR type
modules for a CIR type several data modules for a dedicated allowed/delivered.
type of CIR data module within a Project
or for a specific model identification
code.
S1-00381 Use of implicit or explicit Decide whether to use implicit or explicit Per the following General Civil Aviation usage:
reference method to CIR data references, or both between content No Civil Aviation business rule.
module specific data elements and the CIR data
modules.
Note
It is recommended to use only one
method to avoid difficulties which might
appear during the publishing process.
S1-00382 Use of alternates groups in data Decide whether to use alternates group The only alts groups allowed are figureAlts, multimediaAlts,
module content elements. If used, which groups and in levelledParaAlts, proceduralStepAlts, toolAlts, and
which data modules types. supplyRqmtAlts. Refer to BRDP-S1-00185.
S1-00383 Mix of alternates groups and Decide whether alternates groups and Per the following General Civil Aviation usage:
elements elements can be mixed in a given Intermixing of alternates groups and elements at a given
structure. level of the XML hierarchy is not allowed.
S1-00384 Use of container data modules Decide whether to use container data Refer to BRDP-S1-00265.
modules.
S1-00385 Identification of container data Decide which identification method to Per the following General Civil Aviation usage:
module use for container data modules. The The data module code must be the common data module
chosen method must be used code of all the alternates,
systematically. - with "Z", “ZZ”, or "ZZZ" set in the disassyCodeVariant
attribute and
- "Z" set in the infoCodeVariant attribute.
Example:
Container DM AE-A-42-21-06-01Z-720Z-A
Alternate 1 DM AE-A-42-21-06-01A-720A-A
Alternate 2 DM AE-A-42-21-06-01B-720A-A
S1-00386 Use of applicability within Decide whether applicability annotations Per the following General Civil Aviation usage:
container data module content are duplicated from the referenced data If the container DM is delivered as part of the exchange
modules to the container data module. package, applicability shall be duplicated from the
referenced data modules to the container data module.
S1-00387 Use of applicability Decide if the project will use Per the following General Civil Aviation usage:
applicability. Civil Aviation must use applicability.
BRDP
Number
S1-00388 Applicability functionality Define the required functionality for Per the following General Civil Aviation usage:
applicability. The full range of applicability functionality is allowed. At the
aircraft level, filtered applicability must be used.
S1-00389 Use of applicability data module If functionality is limited to print and For filtered applicability at the component level the ACT, and
types (ACT, CCT, and PCT) static display, decide if applicability data PCT DMs are required. CCT is optional."
module types (ACT, CCT, and PCT) will
be used.
S1-00390 Product attribute and conditions Define a consistent naming and Refer to BRDP-S1-00327.
naming and identification identification scheme for product
scheme attributes and conditions, when ACT
and CCT data modules are
implemented.
S1-00391 Presentation of content that is Specify the method that content is Per the following General Civil Aviation usage:
not applicable presented which is not valid for the No Civil Aviation business rule.
current maintenance context. The
content can be removed, hidden or de-
emphasized in some manner.
S1-00392 Providing the human readable Decide whether to also provide the Per the following General Civil Aviation usage:
part of applicability human readable part of applicability or Refer to BRDP-S1-00317.
rely on the viewer to build the human
readable part, when providing the
computer processing part of
applicability.
S1-00393 Number of ACT, CCT and PCT Decide whether to provide one instance Only one instance is allowed for ACT, PCT, and CCT per CMP.
data module instances of each data module types (ACT, CCT Refer to BRDP-S1-00389.
and PCT) or to segregate the project
into multiple instances of each data
module type, and the method for
segregation.
S1-00394 Classifying product attributes Decide how to divide the properties of Refer to BRDP-S1-00327.
and conditions an ACT data the Product into product attributes or
module condition types.
S1-00395 Configuration management of Decide on the extent of configuration Per the following General Civil Aviation usage:
product attributes an ACT data management and editing access to be It is allowed to add product attribute values or new product
module applied to product attributes within an attributes.
ACT data module. It is not allowed to change product attribute names without
advance communication and agreement with customers.
Communication 6 months before the change is
recommended.
S1-00396 Use of the incorporation status Decide whether to use the incorporation Per the following General Civil Aviation usage:
list in a CCT data module status list in the CCT data module. No Civil Aviation business rule.
BRDP
Number
S1-00397 Scope of the product instances Decide which product instances are Per the following General Civil Aviation usage:
in a PCT data module contained in a PCT data module. This remains a project specific decision.
Options include listing all product Some DMs may be customized for each customer (e.g.
instances in service or listing only the proced) and some may be not be customized (e.g.
product instances within an Schedule).
organization.
It is recommended:
- to deliver only the customer product instances in the PCT
(Applies to aircraft) or
- to deliver all product instances in the PCT where specific
customer information is not specified. (Applies to engine
and component).
S1-00398 Use of a published or a transient Decide whether to publish a static issue Per the following General Civil Aviation usage:
PCT data module of the PCT data module or use the data For projects requiring filtered applicability as described in
module as a transient transfer BRDP-S1-00389, the PCT must be delivered in its XML
mechanism between an external system form.
and a viewer.
S1-00399 Management of the product Decide how to maintain the list of Per the following General Civil Aviation usage:
instance configurations in PCT product instance configuration No Civil Aviation business rule.
data modules specifications and the associated values
for product attributes and conditions.
S1-00400 Use of the ACT catalog data Decide whether to use the ACT catalog The ACT catalog data module will not be used.
module data module.
S1-00401 Internal or external definition of Decide whether the supplier applicability The minimum supplier applicability attributes shall be defined in
supplier applicability attributes attributes are defined in the ACT data the CMP ACT DM (the internal method). Refer to BRDP-S1-
module or if the supplier definition is 00327.
used.
S1-00402 Use of attribute scoEntryType Decide whether to use the attribute If scoEntryType is used it will be ignored.
scoEntryType to indicate the required
resource type.
S1-00403 Technical information object Decide which properties associated to Per the following General Civil Aviation usage:
properties to be included in the the technical information objects (eg, No Civil Aviation business rule.
data module at delivery names, short names) to store within the
data module when delivered.
S1-00404 Determine applicable systems Decide the applicable systems for land Per the following General Civil Aviation usage:
for land and sea products and sea products. Not applicable for Civil Aviation applications.
S1-00405 How to use the element field Decide how to use the element field Per the following General Civil Aviation usage:
descriptions in the wiring data descriptions of the wiring data Not applicable for Civil Aviation applications. Refer to
description Schema description Schema in an interactive BRDP-S1-00238.
wiring publication.
S1-00406 Use of introduction data Decide whether to produce introduction Per the following General Civil Aviation usage:
modules for wiring publications data modules for wiring publications. If No Civil Aviation business rule.
BRDP
Number
required, the scope of these introduction
data modules must be defined.
S1-00407 Optional descriptive information Decide whether to produce descriptive Per the following General Civil Aviation usage:
for connection units information for connection units No Civil Aviation business rule.
S1-00408 Optional descriptive information Decide whether to produce descriptive Per the following General Civil Aviation usage:
for wires and harnesses information for wires and harnesses No Civil Aviation business rule.
S1-00409 Wiring standard practices data Define source and scope of wiring Per the following General Civil Aviation usage:
modules standard practices data modules. Descriptive data modules must not be used to deliver
Decide whether to prepare standard procedural information.
wiring practice information as
procedural or descriptive data modules.
S1-00410 Wiring diagrams in an Decide whether to produce wiring Not used for CMPs.
interactive wiring publication diagrams for an interactive wiring
publication.
S1-00411 Harness routing drawings Decide whether harness routing Per the following General Civil Aviation usage:
drawings are to be simplified and how No Civil Aviation business rule.
their layout must look like.
S1-00412 Coding of harness installation Decide whether to code harness Not used for CMPs.
drawing data modules installation drawing data modules by
using zone information. If decided to
use zone information for the coding, the
subsystem group).
S1-00413 Harness installation information Decide whether to prepare harness Not used for CMPs.
installation information for each major
area in list form in addition to or instead
of harness installation and routing
drawings.
S1-00414 Coding of harness routing Decide whether to code harness routing Not used for CMPs.
drawing data modules drawing data modules by using zone
information. If decided to use zone
information for the coding, the structure
of the data module code is possibly not
appropriate. In this case, it must be
decided on changes of the proposed
BRDP
Number
structure for the Product (eg, population
of the zone information in the unit or
assembly group of the SNS instead of in
the subsystem/sub-subsystem group).
S1-00415 Equipment and panel location Decide whether to produce separate Not used for CMPs.
drawings data modules containing equipment and
panel location illustrations.
S1-00416 Production of electrical standard Decide whether to produce data Not used for CMPs.
parts data modules containing electrical standard
parts data.
S1-00417 Definition of required electrical Define the required information for each Per the following General Civil Aviation usage:
equipment information electrical or electronic item of No Civil Aviation business rule.
equipment that has electrical
connections.
S1-00418 Coding of electrical equipment Decide whether to code electrical Electrical equipment information data modules will not be used.
information data modules equipment information data modules by
using zone information. If decided to
use zone information for the coding, the
subsystem group).
S1-00419 Coding of harness data modules Decide whether to code harness data Harness data modules will not be used.
modules by using zone information. If
decided to use zone information for the
coding, the structure of the data module
code is possibly not appropriate. In this
case, it must be decided on changes of
the proposed structure for the Product
(eg, population of the zone information
in the unit or assembly group of the
SNS instead of in the subsystem/sub-
subsystem group).
S1-00420 Generation of harness wire list Decide whether and how to generate The Wiring schema will not be used for CMPs. Harness wire list
data modules harness wire list data modules for a data modules will use the Descript schema.
page-oriented or an interactive wiring
publication from the wiring data
modules that are based on the wiring
Schema.
BRDP
Number
S1-00421 Generation of connection list Decide whether and how to generate The Wiring schema will not be used for CMPs. Connection list
data modules connection list data modules for a page- data modules will use the Descript schema.
Schema.
S1-00422 Generation of plug and Decide whether and how to generate The Wiring schema will not be used for CMPs. Harness plug list
receptacle list data modules harness plug and receptacle list data data modules will use the Descript schema.
modules for a page-oriented or an
interactive wiring publication from the
wiring data modules that are based on
the wiring Schema.
S1-00423 Generation of terminal list data Decide whether and how to generate The Wiring schema will not be used for CMPs. Terminal list
modules terminal list data modules for a page- data modules will use the Descript schema.
Schema.
S1-00424 Generation of splice list data Decide whether and how to generate The Wiring schema will not be used for CMPs. Splice list data
modules splice list data modules for a page- modules will use the Descript schema.
Schema.
S1-00425 Generation of earth point list Decide whether and how to generate The Wiring schema will not be used for CMPs. Earth point list
data modules earth point list data modules for a page- data modules will use the Descript schema.
Schema.
S1-00426 Use of separate modules or the Decide if front matter is to be authored Per the following General Civil Aviation usage:
consolidated Front matter as separate modules or use the The Front Matter schema shall not be used.
Schema for Equipment consolidated Front matter Schema.
information sets
S1-00427 Level of detail to be provided in Decide what level of detail to provide in Per the following General Civil Aviation usage:
the technical descriptions in the functional and technical No Civil Aviation business rule.
Equipment information sets descriptions.
S1-00428 Use of wiring Schema in Decide whether the Wiring data Per the following General Civil Aviation usage:
Equipment information sets Schema and the Wiring data description The Wiring Data Description schema is not applicable for
Schema are to be used or not. Civil Aviation applications. Refer to BRDP-S1-00238. No
Interactive wiring publication Civil Aviation business rule for the Wiring Data schema.
functionalities are only to be made
BRDP
Number
available if the Wiring Schema is used.
Refer to Chap 3.9.5.2.9.
S1-00429 Level of detail to be provided in Decide what level of detail to provide in Per the following General Civil Aviation usage:
the maintenance and servicing the maintenance and servicing data No Civil Aviation business rule.
data modules in Equipment modules.
information sets
S1-00430 Use of lists in Equipment Decide how to implement the lists of Lists of consumables, materials, expendables, standard SE,
information sets consumables, materials, expendables, special SE, and tools will be generated from the preliminary
standard SE, special SE and tools. requirements.
S1-00431 Use of equivalent substitutes in Decide whether to use equivalent Per the following General Civil Aviation usage:
Equipment information sets substitutes for consumables, materials, Equivalent substitutes shall be allowed. If substitute
expendables equipment and tools. equipment and materials can be used, the phrase,
"equivalent substitutes may be used" shall be included.
S1-00432 Level of detail to be provided in Decide what the level of detail to Per the following General Civil Aviation usage:
the IPD data modules in provide in the IPD modules. No Civil Aviation business rule.
00435
S1-00436 Use of external material Decide whether material information Per the following General Civil Aviation usage:
information in service bulletins must be a part of the "core" SB data No Civil Aviation business rule.
module or if it can (depending on the
volume) be presented in one or more
referenced separate SB data modules.
Refer to Fig 2.
S1-00437 Treatment of alert and standard Decide whether or not to allow Per the following General Civil Aviation usage:
service bulletins classifying service bulletins as Alert. Service Bulletins may be classified as Alert. Refer to ATA
iSpec 2200 chapter 3-3-4.1.1.
S1-00438 Service bulletin compliance Decide whether to use the four Per the following General Civil Aviation usage:
categories compliance categories or to define Refer to Appendix A, Civil Aviation Attribute Values.
others.
S1-00439 Minimum impact on weight in Decide the threshold for minimum Per the following General Civil Aviation usage:
service bulletins impact on weight that must be reported The minimum impact on weight shall be in accordance with
in a SB. ATA iSpec 2200 chapter 3-3-4.3.2.8.
S1-00440 Minimum impact on balance in Decide the threshold for minimum Per the following General Civil Aviation usage:
service bulletins impact on balance that must be The minimum impact on weight shall be in accordance with
reported in a SB. ATA iSpec 2200 chapter 3-3-4.3.2.8.
S1-00441 Minimum impact on electrical Decide the threshold for minimum Per the following General Civil Aviation usage:
load to be reported in service impact on electrical load that must be Reporting impact on electrical load shall be in accordance
bulletins reported in a SB. with ATA iSpec 2200 chapter 3-3-4.3.2.9.
BRDP
Number
S1-00442 Definitions and use of Decide on the precise definitions of Per the following General Civil Aviation usage:
maintenance and operational "maintenance publications" and All affected publications shall be provided in a single list,
publications in service bulletins "operational publications" and whether therefore precise definitions of "maintenance publications"
to separate them into different listings in and "operational publications" are not necessary.
the Impact on publications.
S1-00443 Scope and depth of planning Agree on the scope and depth of the Per the following General Civil Aviation usage:
information data modules for planning information. No Civil Aviation business rule.
S1-00444 Scope and depth of training Agree on scope and depth of the Per the following General Civil Aviation usage:
information data modules for training information. No Civil Aviation business rule.
S1-00445 Use of a full set of data modules Decide whether to use a full set of data The LOAP shall not be used for CMPs.
or a publication module for the modules or a publication module to
LOAP carry the listing of the applicable
publications and other documents
including individual data modules.
S1-00446 Schema to use for the Decide whether to use the Front matter The LOAP shall not be used for CMPs.
publication list data modules of Schema or the Descriptive Schema for
the LOAP the publication list data modules.
S1-00447 One consolidated or several Decide whether to deliver the The LOAP shall not be used for CMPs.
separate publication list data publications and documents listed in
modules for the LOAP one data module/publication module
(with one or more lists presented as
tables) or as separate data
modules/publication modules (eg, by
operational publications or maintenance
publications).
S1-00448 Inclusion of unpublished Decide whether to include publications The LOAP shall not be used for CMPs.
publications and documents in and documents that are not published.
the LOAP
Note
When used as a contractual document,
all publications and documents,
published or not, must be included.
S1-00449 Markup of the publication entry Decide whether to markup the The LOAP shall not be used for CMPs.
as a link in the LOAP publication entry as a link when using
the Descriptive Schema.
S1-00450 Include the manufacturer’s part Decide whether to include and present The LOAP shall not be used for CMPs.
No. or reference No. in the the manufacturer’s part No. or reference
LOAP No.
BRDP
Number
S1-00451 Use of language in the LOAP Decide whether to include and present The LOAP shall not be used for CMPs.
the language of the publication or
document in the entries.
S1-00452 Additional information in parts Decide whether to indicate additional Per the following General Civil Aviation usage:
lists for engine maintenance information under the heading of the No Civil Aviation business rule.
information sets parts list "Remarks" (eg, modification
number applicable to the item).
00459
S1-00460 Front matter to be included in Decide which front matter is to be Refer to BRDP-S1-00466.
page-oriented publications and included (mandatory or optional) in each
IETP, respectively of the page-oriented publications and in
the IETP. The decisions must be based
on the rules given in Chap 3.9.4.
S1-00461 Information codes Decide which information codes to be Per the following General Civil Aviation usage:
used, the basic (eg, 00R) or the Civil Aviation shall use the basic front matter information
alternative (eg, 002). codes (third character alpha).
S1-00462 IPD as a standalone publication Decide if the IPD is produced as a Standalone IPDs will not be allowed.
standalone publication or as a part of for
example an equipment maintenance
publication.
S1-00463 Optional parts data elements in Decide which of the optional data from Per the following General Civil Aviation usage:
IPD the parts data must be included and Not applicable for Civil Aviation applications. This BRDP
which optional elements must be pertains to parts data as defined in S2000M and Civil
displayed. Aviation does not use S2000M.
S1-00464 Use of task sets in the CMP Decide whether to use task sets in the Task sets shall be allowed.
CMP.
S1-00465 Use of placeholder data Decide whether "placeholder" data Per the following General Civil Aviation usage:
modules in the CMP modules are required for those topics Placeholder DMs are required in Civil Aviation.
where data is not required or necessary.
S1-00466 Front matter to be used in the Decide what front matter data modules Per the following General Civil Aviation usage:
CMP to be used and their content. Civil Aviation publications shall present CMP Front Matter
information per the following table, regardless of the
method of generation or exchange.
BRDP
Number
Include in
Title include Page- IETPt Ttl
inaPge-orientedn oriented le page
Title page Mandatory Do Not
Usei Lst
of
effective
pagesoDo
Not Useoo
Not
Usei Lst
of
effective
data
moduleso
List of effective Do Not Do Not
pagesoDo Not Useoo Not Usei Lst
Useoo Not Uses Lst of
Uses Lst of of effective
effective data effective data
modulesoMndato data moduleso
orynandatoryge moduleso
List of effective Mandatory Mandatory
data
modulesoMndato
orynandatoryge
Change record Mandatory Do Not
Usei Hgh
hlights or
transmittal
letter
Highlights or Mandatory Mandatory
transmittal letter
Access Do Not Mandatory
illustration aD Not Usenanda
Usedandatory atoryt Lst
of
abbreviati
ons
List of Mandatory Mandatory
abbreviations
BRDP
Number
List of terms Mandatory Mandatory
symbolsoMndator
ryaandatoryni Tc
chnical standard
record
Technical Mandatory Mandatory
standard record
Table of contents Mandatory Mandatory
List of applicable Mandatory Mandatory
specifications and
documentationnM
andatoryrandator
ryL Lst of
support
equipment
List of support Mandatory Optionalf
equipment
List of Mandatory Optionalf
suppliesrMndator
rypptionalt Lst
of spares
BRDP
Number
List of spares Optionallpt Optionalf
tional Lst
of
illustration
sMMndato
orynandat
toryo Pod
duct
cross-
reference
table tD
Not
Use o Not
Useo Cn
nditions
cross-
reference
table tD
Not
Use o Not
Usep Ap
plicability
cross-
reference
table tD
Not
Use o Not
Use
illustrationsnMnd
datorytandatoryu
BRDP
Number
Product cross- Do Not Do Not
reference table Use o Not Useo Cn
nditions
Useo Cn cross-
nditions reference
cross- table tD
reference Not
table tD Use o Not
Not
Use o Not Usep Ap
plicability
Usep Ap cross-
plicability reference
cross- table tD
reference Not
table tD Use o Not
Not Use
Use o Not
Use
Conditions cross- Do Not Do Not
reference table Use o Not Usep Ap
plicability
Usep Ap cross-
plicability reference
cross- table tD
reference Not
table tD Use o Not
Not Use
Use o Not
Use
Applicability Do Not Do Not
cross-reference Use o Not Use
table tD Not Use Use
S1-00467 Use of access illustration for Decide whether to include access Per the following General Civil Aviation usage:
component maintenance IETP illustration and its format for IETP. No Civil Aviation business rule.
S1-00468 Incorporating service bulletins Decide on the updating frequency for Per the following General Civil Aviation usage:
into the CMP incorporating service bulletins into the Service Bulletins shall be incorporated into the CMP in
CMP. accordance with ATA iSpec 2200 chapter 3-1-9.
S1-00469 Provide IPD information as a Decide whether IPD information is to be Per the following General Civil Aviation usage:
separate publication for the provided as a separate publication. IPD information shall not be provided as a separate
CMP publication for the CMP.
BRDP
Number
S1-00470 Inclusion of maintenance Decide whether to include maintenance Per the following General Civil Aviation usage:
planning information in the CMP planning information in the CMP. Maintenance planning information shall not be included in
the CMP.
S1-00471 Inclusion of removal and Decide whether to include removal and Per the following General Civil Aviation usage:
installation information in the installation information in the CMP. Removal and installation information shall not be included
CMP in the CMP with the exception of engines.
S1-00472 Inclusion of test support data in Decide whether to include Per the following General Civil Aviation usage:
the CMP manufacturer's test support data and its Test support data shall be provided in accordance with
format. ATA iSpec 2200 chapter 3-3-3.2.2.
S1-00473 Use of the S1000D standard Decide whether to use the S1000D Per the following General Civil Aviation usage:
page-oriented presentation standard page-oriented presentation S1000D Chapter 6.2.3.6 is not applicable for Civil Aviation
chapters. given in Chap 6.2.2 and Chap 6.2.3 or applications. Civil Aviation applications shall use Section 3-
to use any other rules for presentation 2 of ATA Spec 1000BR for layout rules for Component
to meet specific project or organization Maintenance data modules. No Civil Aviation business rule
requirements. The business rules must for other chapters in 6.2.2 and 6.2.3.
specify the information needed to
contract the desired presentation.
S1-00474 Use of mirrored headers and Decide whether to use mirrored headers For printed pages, CMPs will use non-mirrored headers and
footers and footers. footers. Refer to Spec 1000BR Section 3-2.
S1-00475 Page size Decide on the page size (including sizes CMPs shall use A4 or ANSI A sizes. Foldout pages shall use
when foldouts are allowed, see below) A3 or ANSI B sizes. Projects shall not impose further
per publication. restrictions.
S1-00476 Presentation of foldouts in page- Decide in what circumstances (eg, Per the following General Civil Aviation usage:
oriented publications interspersed or at the end of the Foldouts shall only be interspersed where used in page-
publication) is presented in page- oriented publications. Refer to BRDP-S1-00131.
oriented publications.
S1-00477 Presentation of inwork markings Decide whether to present the inwork The issue number shall always be presented. The inwork
markings. The details must be number shall be presented only if the value is greater than "00".
documented. The inwork markings will be shown in accordance with Spec
1000BR Section 3-2.
S1-00478 Presentation of "Produced by" - Decide whether to present or not the Per the following General Civil Aviation usage:
"Printed in" responsible producer of the page- No Civil Aviation business rule for "Produced by"
oriented output and/or where the information. "Printed in" information shall not be presented.
publication was printed.
S1-00479 Presentation of publication Decide whether to use the S1000D For CMP presentation of Publication Module Code refer to
module code standard page-oriented presentation Spec 1000BR Section 3-2.
rules for the publication module code or
to create project or organization specific
the header.
BRDP
Number
S1-00480 Presentation of data module Decide whether to use the S1000D For CMP presentation of Data Module Code refer to Spec
code standard page-oriented presentation 1000BR Section 3-2.
rules for the data module code or to
create project or organization specific
the footer.
S1-00481 Presentation of issue date Decide whether to use S1000D For CMP presentation of Issue Date refer to Spec 1000BR
standard page-oriented presentation Section 3-2.
rules for the issue date or to create
project or organization specific rules for
its positioning in the bottom of the
footer.
S1-00482 Presentation of page number Decide whether to use the S1000D For CMP presentation of Page Number refer to Spec 1000BR
standard page-oriented presentation Section 3-2.
rules for the page number or to create
project or organization specific rules for
its positioning in the footer.
S1-00483 Page numbering of foldout Decide whether to use double Per the following General Civil Aviation usage:
pages numbering of pages when printed on Double numbering of foldout pages shall be used when
one (right-hand) side only (eg, 11/12, they are presented on right side only.
13/14).
S1-00484 Presentation of applicability Decide whether to use the S1000D Per the following General Civil Aviation usage:
annotation standard page-oriented presentation Applicability will be expressed where used and not the in
rules for the applicability annotation or the footer. Multiple applicabilities may be required on the
to create project or organization specific same page.
rules for the presentation.
S1-00485 Presentation of security Decide whether to present the security Per the following General Civil Aviation usage:
markings markings in sentence case instead of in Security markings shall not be presented.
uppercase.
S1-00486 Presentation of commercial Decide whether to use the commercial Commercial classification and/or caveat as security markings
classification and/or caveat as classification (value of attribute shall not be used. See BRDP-S1-00054.
security markings commercialClassification) and/or
national caveat (value of attribute
caveat) as an alternative to the security
classification (value of the attribute
securityClassification).
S1-00487 Exclude presentation of security Decide whether to exclude the Per the following General Civil Aviation usage:
markings for unclassified presentation of security markings for Security markings shall not be presented.
publications unclassified publications or not.
S1-00488 Presentation of safety Decide whether to use the S1000D Not used for CMPs.
classification standard page-oriented presentation
rules for the safety classification
BRDP
Number
(attribute safetyLabel of the element
<productSafety>) or to create project or
organization specific rules for the
presentation.
S1-00489 Presentation of the element Decide whether to present any of the Refer to Spec 1000BR Section 3-2.
<logo> logotypes given in the element <logo>
and how this element is presented (eg,
size, color).
S1-00490 Presentation of "End of data Decide on the text that will be used to "End of XXX" will be used, where XXX is the Data Module Code
module" statement identify the end of a data module, either without the DMC/DME prefix.
"End of data module" or "End of"
followed by the data module title.
S1-00491 Placement of the end of data Decide whether to present the "End of" Refer to Spec 1000BR Section 3-2.
module statement statement in the footer or in the body of
the page.
S1-00492 Use of double column text Decide whether to use double column Double column text may only be used for indices and lists.
text, and under what circumstances.
Typography for double column page
layout must be documented.
S1-00493 Double sided printing of foldout Decide whether to use double sided Double sided printing of foldout pages is not allowed.
pages printing on foldout pages.
Note
A3L paper in A3L binders are normally
printed on both sides.
S1-00494 Presentation of the procedural Decide whether to present the titles for Per the following General Civil Aviation usage:
step titles from the element the element <proceduralStep> and to If the titles are provided they must be presented.
<proceduralStep> which level.
S1-00495 Presentation of the crew drill Decide whether to present the titles for Per the following General Civil Aviation usage:
step titles from the element the element <crewDrillStep> and to Not applicable for Civil Aviation applications.
<crewDrillStep> which level.
Note
Presentation of the titles for steps on
level six thru level eight are not given.
The use of these elements is
discouraged and their use and
presentation are project decisions.
S1-00496 Presentation of the document Decide whether to present the Refer to Spec 1000BR Section 3-2.
title document title as a centerhead No. 1
and a centerhead No. 2 or as a
BRDP
Number
centerhead No. 1 only (including both
element <techName> and element
<infoName>).
S1-00497 Number of sidehead levels to be Decide whether to present more than Refer to Spec 1000BR Section 3-2.
presented in the Table of three sidehead levels in the table of
contents contents.
S1-00498 Presentation of List of tables Decide whether to present the List of Refer to Spec 1000BR Section 3-2.
tables.
S1-00499 Present the prefix "Table" in the Decide whether to present the prefix Refer to Spec 1000BR Section 3-2.
List of tables "Table" before the table number in the
List of tables.
S1-00500 Presentation of List of figures Decide whether to present the List of Refer to Spec 1000BR Section 3-2.
figures.
S1-00501 Present the prefix "Fig" in the Decide whether to present the prefix Refer to Spec 1000BR Section 3-2.
List of figures "Fig" before the figure number in the
List of figures.
S1-00502 Presentation (layout) of titles Decide whether to use the S1000D Refer to Spec 1000BR Section 3-2.
standard presentation rules for titles
(sidehead 1 thru sidehead 5 or if used
thru sidehead 8) or to create project or
organization specific rules such as type
size, leading and justification.
S1-00503 Presentation of the leveled para Decide whether to present the titles for Level 6-8 will not be used. Refer to BRDP-S1-00180.
titles from the element the element <levelledPara> on level six
<levelledPara> on level six thru thru eight.
eight
S1-00504 Use of the alternative method Decide whether to use the preferred or CMPs will use the following alternative method:
for labeling procedural steps at the alternative method for labeling 1. asdf
presentation procedural steps. A. asdf
(1) asdf
(a) asdf
1. asdf
a. asdf
(1) asdf
(a) asdf
S1-00505 Presentation of paragraphs of Decide whether to use the Refer to Spec 1000BR Section 3-2.
text recommended presentation rules for
type size, spacing and justification.
S1-00506 Presentation of hierarchical Decide whether to use hierarchical Per the following General Civil Aviation usage:
indented steps, when used indented steps, when used without Hierarchical indentation shall be used when steps are
without titles in procedural steps titles. presented without titles.
BRDP
Number
S1-00507 Prefixes to be used for random Decide whether to use a consistent set Per the following General Civil Aviation usage:
lists at presentation of prefixes for random list throughout The default prefix (pf02) shall be used/presented.
the project.
S1-00508 Presentation of footnote Decide whether to present the footnote Per the following General Civil Aviation usage:
numbers markers as superscripted numbers Only superscript numbers may be used. Refer to BRDP-
(default) or as numbers presented S1-00173.
within parenthesis.
S1-00509 Presentation of inline footnotes Decide whether to present the inline Per the following General Civil Aviation usage:
footnotes at the bottom of the page Not applicable for Civil Aviation applications. Refer to
(default) or at the end of the data BRDP-S1-00172.
module.
S1-00510 Presentation of table footnotes Decide whether to present the footnotes Footnotes shall be presented on the relevant page.
on the relevant page, if the table is split
over several pages. Refer to Fig 2 and
Fig 3.
S1-00511 Presentation of vertical lines in Decide whether to, in exceptional Per the following General Civil Aviation usage:
formal tables cases, allow presentation of vertical Vertical lines in tables are permitted.
lines in formal table.
Note
The rendering of the table must be
based on the elements and attributes in
the XML files.
The author must apply elements and
attributes as defined in Chap 3.9.5.2.1.6
in order to achieve the layout described
in this chapter.
S1-00512 Use of the alternative individual Decide whether to use one of the Per the following General Civil Aviation usage:
numbering of multi sheet alternative methods for individual The alternative methods are not allowed.
illustrations at presentation numbering of multi sheet illustrations.
The chosen method must be used
throughout the project.
S1-00513 Presentation of warnings and Decide whether to use the alternative Per the following General Civil Aviation usage:
cautions rule to present the warnings before the In civil aviation applications, Warnings and Cautions within
step/para number. a Step must appear before the Step number.
Note
Projects must be aware of potential
hazards when allowing step numbers to
follow the warning and ensure that there
BRDP
Number
is a clear connection in the presentation
between the warning and the
associated steps.
S1-00514 Presentation of symbols in Decide whether to present symbols in Per the following General Civil Aviation usage:
warnings and cautions warnings and cautions. The symbols No Civil Aviation business rule.
must be standardized and documented.
S1-00515 Use of symbolic presentation of Decide whether to use symbolic Symbolic presentations of warnings and cautions will not be
warnings and cautions presentations of warnings and cautions. allowed.
S1-00516 Use of numbered notes within a Decide whether to use numbered notes Per the following General Civil Aviation usage:
data module at presentation within a data module. Numbered notes are not allowed.
S1-00517 Display of change marks Decide whether to display change Per the following General Civil Aviation usage:
marks. Change marks shall be displayed.
S1-00518 Presentation of change marks Decide whether to use an alternative Per the following General Civil Aviation usage:
visual presentation as change marker Alternative visual presentation as change marker shall not
be allowed.
S1-00519 Presentation of change marking Decide whether to change mark Per the following General Civil Aviation usage:
of individual table rows individual table rules at presentation. Change marks shall be shown against the individual rows
that contain changes.
S1-00520 Presentation of data module Decide whether to present the data The References Table at the Data Module level is not used for
titles in the reference table module title in the reference table CMPs.
S1-00521 Presentation of publication Decide whether to present the title The References Table at the Data Module level is not used for
module/non-S1000D publication (element <pmTitle>/<externalPubTitle>) CMPs.
titles in the reference table or the short title (element
<shortPmTitle>/<shortExternalPubTitle>
), or both, in the reference table
S1-00522 Order of presentation of Decide in which order the referenced The References Table at the Data Module level is not used for
references in the reference table document is presented in the reference CMPs.
table ("Table 1 References"): In order of
appearance, alphabetical order, data
modules before publications, etc.
S1-00523 Inline presentation of non- Decide whether to present the external Both the external publication code (element
S1000D publication titles publication code (element <externalPubCode>) and the title (element <externalPubTitle>)
<externalPubCode>), the title (element shall be presented. The short title shall not be presented.
<externalPubTitle>) or the short title
(element <shortExternalPubTitle>) as
the inline reference.
S1-00524 Presentation of the name of Decide whether to present the name Refer to Spec 1000BR Section 3-2.
spares, supplies and support (element <name>) or the abbreviated
equipment
BRDP
Number
alternate name (element <shortName>),
as the cross-reference in the text.
S1-00525 Use of the alternative method Decide whether to use the preferred or Per the following General Civil Aviation usage:
for presentation of applicability the alternative method for presentation Applicability statements shall be presented before the steps
statements of applicability statements. or paragraphs to which they apply.
S1-00526 Decide on highlighting the Decide whether to highlight (bold) the Refer to Spec 1000BR Section 3-2.
default heading and applicability default heading and applicability
statement at presentation statement at presentation.
S1-00527 Elements and attributes to be Decide which elements and attributes to Refer to Spec 1000BR Section 3-2.
presented on the Title page be presented on the Title page.
Note
coordinated/based on the Business
rules decision points given in Chap
3.9.5.2.16.
S1-00528 Size of the product illustration Decide on the height of the product Refer to Spec 1000BR Section 3-2.
on the Title page illustration on the Title page, if used.
presented on the Table of be presented on the Table of content
content page page.
Note
3.9.5.2.16.
S1-00530 Elements and attributes to be Decide which elements and attributes to Per the following General Civil Aviation usage:
presented on the List of be presented on the List of effective List of Effective Pages shall not be used.
effective pages pages.
Note
3.9.5.2.16.
presented on the List of be presented on the List of effective
effective data modules data modules.
BRDP
Number
Note
3.9.5.2.16.
presented on the Highlights data be presented on the Highlights data
modules modules.
Note
3.9.5.2.16.
S1-00533 Use of rules and guidance for Decide whether to use the rules and Per the following General Civil Aviation usage:
IETP guidance for look and feel, and printed S1000D chapter 6.3.1 may be used as guidance, but is not
output from an IETP detailed in Chap required.
6.3.1 or an alternate output
specification.
S1-00534 Main menu bar functions in the Decide which, if any, of the basic set of Per the following General Civil Aviation usage:
IETP viewer main menu bar functions to mandate. In Civil Aviation, IETP providers should determine their own
functionality requirements.
S1-00535 Printing of classified data Decide whether to allow the printing of Per the following General Civil Aviation usage:
classified data. If not allowed, the print In Civil Aviation, IETP providers should determine their own
function must be disabled when functionality requirements.
classified data is presented in the IETP
viewer
S1-00536 Additional information bar in the Decide on the use of an additional Per the following General Civil Aviation usage:
IETP viewer information bar. If used, it must be In Civil Aviation, IETP providers should determine their own
decided which information to be functionality requirements.
available in the additional information
bar.
S1-00537 Use of the functionality matrix Decide whether to use the functionality Per the following General Civil Aviation usage:
matrix. If used, fill in the functionality No Civil Aviation business rule.
matrix. Refer to Chap 6.4.2.
S1-00538 Modification of the functionality Decide on which functionality is required Per the following General Civil Aviation usage:
matrix due to selection of in the technical publications. No Civil Aviation business rule.
information sets
S1-00539 Selection of functionality using Decide on which functionality is required Per the following General Civil Aviation usage:
the functionality matrix in the technical publications. No Civil Aviation business rule.
BRDP
Number
S1-00540 Population of the element Decide the preferred syntax to identify Refer to BRDP-S1-00541.
<externalPubCode> legacy data by a publication code.
pubCodingScheme pubCodingScheme. If used, decide on No Civil Aviation business rule.
the set of allowed coding schemes and
the syntax of those schemes.
S1-00542 Method to include legacy Decide whether to include legacy Per the following General Civil Aviation usage:
information in an IETP information by encapsulating it in data No Civil Aviation business rule.
modules or by referencing it as external
publications using the publication
module.
S1-00543 IETP reference format Decide the syntax and semantics of the Per the following General Civil Aviation usage:
links established to reference legacy No Civil Aviation business rule.
data.
S1-00544 Use of data compression Decide whether to use compression Per the following General Civil Aviation usage:
techniques techniques on files being transferred No Civil Aviation business rule.
and which techniques to be used.
S1-00545 File formats for information Decide which file formats, besides the Only S1000D standard, SVG, and ATA CGM Profile file formats
objects S1000D standard formats, to use. are permitted.
S1-00546 Inclusion of RDF/DC metadata Decide on the inclusion of RDF/DC Per the following General Civil Aviation usage:
in data dispatch notes, data metadata in data dispatch notes, data RDF/DC metadata shall not be used.
management lists and management lists and comments. It is
comments recommended that inclusion is applied
consistently across all CSDB objects.
S1-00547 Format of generated display text Decide on the format for generating the Per the following General Civil Aviation usage:
displayed applicability annotation from No Civil Aviation business rule.
the computable applicability annotation
that will best fulfill industry and/or
customer display requirements.
S1-00548 Modifying an assigned product Decide if modifications to PCT assigned Per the following General Civil Aviation usage:
attribute value in the PCT. values are allowed. Modifications to PCT assigned values are allowed.
S1-00549 Translation of SNS titles and Decide whether to translate and use the Per the following General Civil Aviation usage:
definitions SNS titles and the definitions in the Translation to languages other than U.S. English shall not
languages adopted by the project. be allowed.
S1-00550 Allocation of project specific Decide and agree on allocation of Per the following General Civil Aviation usage:
information codes project specific information codes and Any new Information Codes needed by OEMs or operators
give them short and full definitions. should be submitted to CAWG to determine if they should
be proposed to the Steering Committee for a specification
change based on urgency of need. If the proposal is unable
to be accepted for S1000D within a reasonable timeframe,
then CAWG would assign a project-specific code using a
BRDP
Number
third-character alpha. Civil Aviation approved project-
specific info codes will be maintained by CAWG. Codes
consisting of three alpha characters may be used by
airlines for internal use only.
S1-00551 Translation of information code Decide whether to translate and use the Per the following General Civil Aviation usage:
definitions information code definitions in the Translation to languages other than U.S. English shall not
languages adopted by the project. be allowed.
S1-00552 Translation of learn code Decide whether to translate and use the Per the following General Civil Aviation usage:
definitions learn code definitions in the languages Translation to languages other than U.S. English shall not
adopted by the project. be allowed.
3-2. Layout rules and examples - Component maintenance data
modules
3-2-1. Introduction
This chapter supplies guidance and instructions for presentation of civil aviation component
maintenance documentation when produced from S1000D data using Issue 4.1 schemas.
This chapter gives the rules for S1000D standard page-oriented presentation of a component
maintenance publication (CMP) and is based on the layout elements given in S1000D Chap
6.2.2 and iSpec 2200. It is used to build for example, Formatted Output Specification Instances
(FOSI), XSL (Extensible Style sheet Language) Style, etc. CMP structure and content are
based on S1000D Chap 5.3.1.4 and CMP common information sets based on S1000D Chap
5.2.1.9.
Note: In this document, chapter references are to S1000D specification chapters.
Some of the requirements outlined in this chapter can only be implemented in Issue 4.2 of the
S1000D specification.
Each issue of a CMP is a complete issue of the entire document. No partial issues are allowed.
Upon reissue of a CMP, the change markings and reason for updates that reside in the
unchanged DMs will be suppressed.
Should there be a conflict between this chapter and S1000D, this chapter shall take precedence.
1. References
Table 4 S1000D References

S1000D Chap No./Document No. Title
Chap 5.3.1.3 Common requirements - Illustrated parts data
Chap 5.3.1.4 Common requirements - Component maintenance
Chap 6.2.1 Page-oriented publications - Page layout, paper publications, headers

and footers
Chap 6.2.2 Page-oriented publications - Typography and layout elements
Chap 6.2.3.1 Layout rules and examples - Front matter data modules
Chap 6.2.3.2 Layout rules and examples - Descriptive data modules
Chap 6.2.3.3 Layout rules and examples - Procedural data modules
Chap 6.2.3.4 Layout rules and examples - Fault information data modules
Chap 6.2.3.5 Layout rules and examples - IPD publication
2. Sections
A CMP is divided into four main sections:
1. Front matter and introduction
2. Functional and technical descriptions
3. Maintenance and servicing
4. Illustrated parts data
3. Topics
Each section can address the following topics:
• Front matter and introduction
o Title page (TP)
o Configuration (CONF)
o Copyright statements (COPY)
o Administrative and legal statements (ADMIN)
o Safety statements (SAFE)
o List of effective data modules (LOEDM)
o Change record (CR)
o Highlights (HIGH)
o List of abbreviations (LOA)
o List of terms (LOT)
o List of symbols (LOS)
o Technical standard record (TSR)
o Table of contents (TOC)
o List of illustrations (LOI)
o List of tables (LOTBL)
o List of applicable specifications and documentation (LOASD)
o List of suppliers (LOSUP)
o List of support equipment (LOSE)
o List of supplies (LOSU)
o List of spares (LOSP)
o Introduction (INTRO)
• Functional and technical descriptions
o Description of function (FUNC)
o Technical description (DESC)
o Diagrams and schematics (SCHEM)
• Maintenance and servicing
o Task sets (TS)
o Servicing (SERVC)
o Examination, test, checks, and fault isolation (TEST)
o Disassemble (DIS)
o Repair (REP)
o Assemble (ASSY)
o Storage (STORE)
• Illustrated parts data
o Introduction (IPD)
o Numerical index (IPD)
o Equipment designator index (IPD)
o Detailed parts data (IPD)
Each of the sections and topics mentioned above has specific layout requirements when used
in a CMP.
3-2-2. Rules and examples

Within the graphic examples shown in this chapter, only those areas with callouts and/or those
that are shown in normal text are applicable to the subject matter. Those areas that are shown
using greyed-out text are not part of the actual figure example and are shown for context only.
1. All data modules
The following applies to each formatted page within any of the sections and topics of the CMP
with the exception of the title page.
1.1. Header and footer (Not including title page)
1.1.1. General headers and footers
The page header for each page in a CMP is composed of five items and shall appear on every
page:
• Company logo
• The text "COMPONENT MAINTENANCE PUBLICATION"
• Publication module code
• Component identity (model, part number, etc.)
• Horizontal rule (0.5pt line) as shown
The page footer for each page in a CMP is composed of five parts and shall appear on every
page except as indicated:
• The SNS of the CMP (which may or may not be the same as the SNS of the current
data module)
• The copyright statement for the CMP
• The section topic
• The date of the CMP
• The page number
Data module codes shall not be displayed in the header or footer of a CMP. The DMC for each
data module is to be displayed at the beginning of the text for that data module. Refer to [Data
module code ].
Pages should use non-mirrored headers and footers.
No additional information will be displayed in the header or footer.
An example of a CMP header and footer is shown in Fig 1. The layout of each of the above
components should follow this example exactly.
The header for each page (except for title page) in a CMP is composed of five items and shall
appear on every page:
• Company logo
• The text "COMPONENT MAINTENANCE PUBLICATION"
• Component identity (model, part number, etc.)
• Horizontal rule (0.5pt line) as shown
The footer for each page (except for title and section pages) in a CMP is composed of five
parts and shall appear on every page except as indicated:
data module)
• The section topic (Displayed on the @pmEntryType attribute value)
• The date of the CMP
• The page number
1.1.2. Section footers
Section footers will contain the following information:
data module)
An example of a CMP section footer is shown in Fig 1.
1.1.3. BRDPs addressed
BRDP-S1-00474 - Use of mirrored headers and footers: The non-mirrored headers and footers
will be presented as described in this chapter.
BRDP-S1-00479 - Presentation of publication module code: The publication module code will
be presented as described in this chapter.
BRDP-S1-00480 - Presentation of data module code: The data module code will be presented
as described in this chapter.
BRDP-S1-00481 - Presentation of issue date: The issue date will be presented as described in
this chapter.
BRDP-S1-00482 - Presentation of page number: The page number will be presented as
described in this chapter.
BRDP-S1-00489 - Presentation of the element <logo>: The element <logo> will be presented
Fig 1. (Sheet 1 of 3) Headers and footers
1.2. Separators
1.2.1. Section separators
Each section except the front matter must begin with a section separator. This separator
consists of a single page that displays the pmEntryTitle.
A section separator is shown in Fig 2. The last data module in a section must conclude with
the text "End of Section" where Section is the corresponding section title. An example of this
is shown in Fig 2.
1.2.2. Topic separators
Every topic will start on a new page. The first data module within each topic, except the title
page and detailed parts data topics, must have the topic title displayed at the top of the page
before any of the data module content begins.
A topic separator is shown in Fig 2. The last data module in a topic must conclude with the
text "End of Topic" where Topic is the corresponding topic title. An example of this is shown
in Fig 2.
1.2.3. Data module code separators
The DMC will be located preceding the content of that data module.
The <techName> and <infoName> will not be presented from the DM in CMPs.
At the conclusion of the data module, the DMC will be repeated preceded by the words "End
of". An example of this is shown in Fig 2.
BRDP-S1-00473 - Use of the S1000D standard page-oriented presentation chapters: The page-
oriented presentation will be presented as described in S1000D and this chapter.
this chapter.
BRDP-S1-00491 - Placement of the end of data module statement: The end of data module
statement will be presented as described in this chapter.
Fig 2. (Sheet 1 of 6) Section, topic and data module separators
1.3. Quality assurance
The <quality Assurance> statements will be presented immediately below the DMC using the
same format as the DMC. See various figures for examples.
• For <unverified>, the text "Unverified" will be placed below the DMC.
• For <firstVerification verificationType="tabtop">, the text "Verified by table-top" will

be placed below the DMC.
• For <firstVerification verificationType="onobject">, the text "Verified by

performance" will be placed below the DMC.
• For <firstVerification verificationType="ttandoo">, the text "Verified by table-top and

performance" will be placed below the DMC.
Note: <secondVerification> is not displayed by Civil projects.
1.4. Numbering
1.4.1. Paragraph numbering
The paragraph numbering in a CMP will follow the ATA iSpec 2200 standard paragraph
numbering format. However, when multiple data modules are used within the same topic, the
first level of paragraph numbering will continue in sequence with the next data module. This
numbering sequence does not restart until a new topic begins.
Refer to Table 5 for a listing of possible topics for each section and Fig 3 for an example of
paragraph numbering.
1.4.2. Table numbering
When multiple data modules are used within the same topic, the table numbering will continue
in sequence with the next data module. This numbering sequence does not restart until a new
topic begins.
The table numbers in a CMP are composed of three to four elements:
• The label of "Table".
• A prefix of the current topic followed by a dash. (Refer to Table 5 for a listing of
possible topic prefixes.)
• The sequential table number.
• The word "(Continued)" is used when a table spans more than one page.
Refer to Fig 3 for an example of table numbering.
1.4.3. Figure numbering
When multiple data modules are used within the same topic, the figure numbering will continue
topic begins.
The figure numbers in a CMP are composed of four elements:
• The label of "Figure".
• The sequential figure number.
• The sheet count shall be (Sheet 1 of X).
Refer to Fig 3 for an example of figure numbering.

1.4.4. References
Internal and external references will be in line with text. Refer to Fig 3 for examples of
references.
1.4.5. Page numbering
When multiple data modules are used within the same topic, the page numbering will continue
topic begins. Page numbering for the IPD section will start at one "1" for the first page of the
IPD Introduction topic and be continuous over all IPD topics.
The page numbers in a CMP are composed of three elements:
• The label of "Page".
• The sequential page number.
Table 5 Topic prefixes

Section Topic Prefixes
Front matter (no separator page) (no page number)
Title page TP
(topic title not displayed)
Configuration CONF
Copyright statements COPY
Administrative and legal statements ADMIN
Safety statements SAFE
List of effective data modules LOEDM
Change record CR
Highlights HIGH
List of abbreviations LOA
List of terms LOT
List of symbols LOS
Technical standard record TSR
Table of contents TOC
List of illustrations LOI
List of tables LOTBL
List of applicable specifications and LOASD

documentation
List of suppliers LOSUP
List of support equipment LOSE
List of supplies LOSU
List of spares LOSP
Introduction INTRO
Functional and technical (separator page) (no page number)

descriptions
Description of function FUNC
Technical description DESC
Diagrams and schematics SCHEM
Maintenance and (separator page) (no page number)

servicing
Task sets TS
Servicing SERVC
Examination, test, checks, and fault TEST

isolation
Disassemble DIS
Repair REP
Assemble ASSY
Storage STORE
Illustrated parts data (separator page) (no page number. Page numbers to be
continuous in this section starting
with introduction)
Introduction IPD
Numerical index IPD
Equipment designator index IPD
Detailed parts data IPD

(topic title not displayed)

BRDP-S1-00180 - Level of depth for descriptive data modules. The level of depth for
descriptive data modules will be presented as described in this chapter.
BRDP-S1-00186 - Max number of steps allowed in a procedure. The max number of steps in
a procedure will be presented as described in this chapter.
BRDP-S1-00502 - Presentation (layout) of titles: The (layout) of titles will be presented as
BRDP-S1-00504 - Use of the alternative method for labeling procedural steps at presentation:
The alternative method for labeling procedural steps will be presented as described in this
chapter.
BRDP-S1-00505 – Presentation of paragraphs of text. The paragraphs of text will be presented
Fig 3. (Sheet 1 of 11) Numbering
1.5. Applicability
Applicability statements will be displayed preceding the element they affect.
If no applicability is defined on a specific element, no applicability statement will be displayed.
Refer to Fig 4 for some applicability examples.
BRDP-S1-00526 - Decide on highlighting the default heading and applicability statement at
presentation: The default heading and applicability statement will be presented as described in
this chapter.
Fig 4. (Sheet 1 of 7) Applicability
2. Descriptive data modules
In general, descriptive data modules in a CMP will follow the same layout rules as in other
areas of this chapter. The following items will be consolidated at various levels of the
publication and are not required at the beginning of each data module:
• Table of contents
• List of figures
• List of tables
• References
The "table of contents", "list of figures", "list of tables" and "references" (<externalPubRef>
and <pmRef>) will be consolidated at the publication level and will not be displayed at the
Section, Topic, or data module level.
3. Procedural data modules
In general, procedural data modules in a CMP will follow the same layout rules as in other
areas of this chapter. The following items will be consolidated at various levels of the
• List of figures
• List of tables
• Support equipment
• Consumables, materials and expendables
• Spares
• References
The list of "support equipment", "consumables, materials and expendables", and "spares" will
be consolidated at the publication level and the Topic level and will not be displayed at the
data module level.
4. Fault information data modules
In general, fault information data modules in a CMP will follow the same layout rules as in
other areas of this chapter. The following items will be consolidated at various levels of the
• List of figures
• List of tables
• References
5. Topic specific rules and examples
5.1. Front matter topics
5.1.1. Title page
The positioning of these elements on the title page is shown in Fig 5. These elements should
be organized in such a fashion that they fit on a single page.
The optional component logo should be sized to fit the available space and to provide value.
The title page for a CMP must display the following information:
• Company logo/masthead
• Company manufacturer CAGE code
• Publication type ("COMPONENT MAINTENANCE PUBLICATION")
• Any data restriction information that applies to the entire publication. Such as:
o export control statement(s)
o copyright legend/indicator
• Publication issue number (The issue number shall always be presented. The inwork
number shall be presented only if the value is greater than "00".)
• Title page data module code (if authored)
• SNS of the CMP
• Issue date
• Page number
The title page must also display the following for each Product included in the CMP:
• Name of the component
• Product number (e.g. part number/model/series/type)
• Component logo (if room permits)
This topic is generated content from the publication module and data modules contained in the
CMP. This topic shall not be a data module and not have any data module coding presented.
BRDP-S1-00477 - Presentation of inwork markings: The inwork markings will be presented
BRDP-S1-00479 - Presentation of publication module code: The publication module code will
be presented as described in this chapter.
BRDP-S1-00480 - Presentation of data module code: The data module code will be presented
this chapter.
BRDP-S1-00482 - Presentation of page number: The page number will be presented as
BRDP-S1-00489 - Presentation of the element <logo>: The element <logo> will be presented
BRDP-S1-00527 - Elements and attributes to be presented on the title page: The elements and
attributes will be presented on the title page as described in this chapter.
BRDP-S1-00528 - Size of the product illustration on the title page: The size of the product
illustration will be presented on the title page as described in this chapter.
Fig 5. (Sheet 1 of 6) Title information
5.2. Configuration (CONF)
This topic will display at least one Product configuration table for each CMP end item and
describe the relationship between these part numbers and any other end item part number or
identification required by the project.
It will also provide an additional Previous publication table to display information for re-
identified and superseded publications if applicable.
This topic will include the introductory text as shown to explain the "PN" and "Pub class"
indicators used in each table.
This topic is static content and must reside in a data module. This topic shall be a physical data
module and will display the data module code on presentation.
5.2.1. Product configuration
Each Product configuration table will display one current CMP end item in the first row. This
is the PRIME identity for the table. Additional rows may be used as required to display all
alternate or alias part numbers assigned to that end item part number by entities other than the
original manufacturer. Additional rows should also be included to display obsolete part
numbers and previous manufacturers related to each CMP end item ("PRIME") part number.
The product configuration table will be provided as shown in Fig 6.
The first column in row will display the applicable "PN class" indicator. The "PN class" is used
to describe the relationship between these part numbers and any other end item part number or
identification required by the project. The first row in each table will display the "PRIME"
product information.
The product configuration shows current, associated, and historical product information
contained in this manual. The products are listed by PN class, which are defined as follows:
• "PRIME" - The PRIME is the current OEM’s top-level PN and MFR code covered by
this publication.
• "ALT" - The ALT represents an alternate to the PRIME for the same part. For example,
this could be an airframe manufacturer's part number.
• "PREV" – The PREV represents a legacy part number and MFR code to the PRIME
for the same part number that may still be supported.
• "OBS" - The OBS represents a part number and MFR code that is no longer supported
but is included in this manual for historical reference.
Each Product configuration table will also display the following columns:
• PN (Part number)
• MFR (Manufacturer's code)
• Component name
• Model
PN, MFR and component name will always be displayed.
5.2.2. Previous publications

In those cases where the CMP has been re-identified or when the contents of a different CMP
have been replaced by the PRIME CMP, a Publication configuration table will be provided as
shown in Fig 6.
The publication configuration shows active or superseded publication information about this
publication. The publications are listed by Pub class, which are defined as follows:
• "PRIME" – The PRIME represents the active publication.
• "PREV" - The PREV represents a legacy publication to the PRIME publication.
Fig 6. (Sheet 1 of 3) Configuration (CONF)
5.3. Copyright statements (COPY)
Extensive proprietary statements and explanatory text should be included in this topic. Refer
to Fig 7.
Fig 7. (Sheet 1 of 2) Copyright statements (COPY)
Fig 7. (Sheet 2 of 2) Copyright statements (COPY)
5.4. Administrative and legal statements (ADMIN)
Extensive administrative statements such as licensing and warranty statements and any
explanatory text should be included in this topic. Refer to Fig 8.
Fig 8. (Sheet 1 of 2) Administrative and legal statements (ADMIN)
Fig 8. (Sheet 2 of 2) Administrative and legal statements (ADMIN)
5.5. Safety statements (SAFE)
Publication level warnings and cautions should be displayed in this topic. This topic can also
contain other publication level safety statements or explanations.
Such statements should apply to the entire publication. This topic is not intended to be a
complete collection of all warnings and cautions in the publication. Procedure level safety
statements are still required to be provided and displayed appropriately in the procedure. Refer
to Fig 9.
Fig 9. (Sheet 1 of 2) Safety statements (SAFE)
Fig 9. (Sheet 2 of 2) Safety statements (SAFE)
5.6. List of effective data modules (LOEDM)
The LOEDM lists all of the data modules in the publication in the order of appearance in the
CMP. The following information must be shown:
• Data module title
• Data module code
• Issue number of the data module
• Issue date of the data module
• Status
These elements should be displayed as shown in Fig 10.

5.6.1. Status
The "Status" to be displayed in the CMP LOEDM is not the same as the <dmStatus> issueType
attribute from each data module.
The LOEDM reflects the status of the data modules used within this CMP. The following are
the status definitions:
• If the DM is new from the prior release of the publication, an "N" indicates that the
data module has been added to the CMP since the last release of the publication.
• If the DM is unchanged from the prior release of the publication, the entry is left blank.
• If the DM is changed from the prior release of the publication, a "C" indicates that the
data module existed in the previous revision of the CMP and has experienced a content
change.
BRDP-S1-00531 - Elements and attributes to be presented on the List of effective data
modules: The Elements and attributes used on the List of effective data modules will be
presented as described in this chapter.
Fig 10. (Sheet 1 of 3) List of effective data modules (LOEDM)
5.7. Change record (CR)
The change record displays a history of the CMP. The change record needs only display the
sequential issue numbers and issue dates of the CMP. For electronic publications there is no
need to record local incorporation of a change and therefore there is no need for a signature
record.
The change record is displayed in table format and must show at least the following
information:
• Issue number
• Issue date
An example of a change record is shown in Fig 11.

Fig 11. (Sheet 1 of 2) Change record (CR)
Fig 11. (Sheet 2 of 2) Change record (CR)
5.8. Highlights (HIGH)
The highlights page lists the content changes made to the data modules from one revision of
the CMP to the next.
The content of the highlights is obtained from the <reasonForUpdate> element with either the
@updateHighlight attribute set to "1" or not present. <reasonForUpdate> elements with the
@updateHighlight attribute set to "0" will not be reported to the HIGH.
The content of the highlights page will be displayed in a three-column table format.
The first column shall contain the DMC of the data module. The second column provides a
text description of the DM change. This shall be the content of each <reasonForUpdate>
element of the DM for each DM change since the last PM revision. The third column contains
the page number of the first page of the highlighted item.
If a data module has been added or deleted from the current issue of the CMP, the first column
shall contain the PMC of the publication module. The <reasonForUpdate> for the applicable
<pmEntry> shall contain the DMC and DM title of the added or deleted module and text
describing reason for the change.
An example of a CMP highlights page is shown in Fig 12.
BRDP-S1-00532 – Elements and attributes to be presented on the Highlights data modules:
The Elements and used on the highlights data modules will be presented as described in this
chapter.
Fig 12. (Sheet 1 of 3) Highlights (HIGH)
5.9. Lists of abbreviations, terms and symbols (LOA, LOT, LOS)
The lists of abbreviations, terms and symbols are three separate lists that are used to summarize
all of the abbreviations, terms and symbols used throughout the CMP.
These lists shall be displayed in two-column table format with the first column for the
abbreviation, term or symbol used in the CMP and the second column for the
definition/description.
An example of a list of abbreviations is shown in Fig 13. This list is generated based on the
@acronymType attribute with a value of "at01".
An example of a list of terms is shown in Fig 14. This list is generated based on the
@acronymType attribute with a value of "at02".
An example of a list of symbols is shown in Fig 15. This list is generated based on the
@acronymType attribute with a value of "at03". Because of an error in S1000D, graphic
symbols cannot be used in acronyms at this time.
These topics are generated content from the data modules contained in the CMP. These topics
shall not be a data module and not have any data module coding presented.
Fig 13. (Sheet 1 of 2) Lists of abbreviations (LOA)
Fig 13. (Sheet 2 of 2) Lists of abbreviations (LOA)
Fig 14. (Sheet 1 of 2) Lists of terms (LOT)
Fig 14. (Sheet 2 of 2) Lists of terms (LOT)
Fig 15. (Sheet 1 of 2) Lists of symbols (LOS)
Fig 15. (Sheet 2 of 2) Lists of symbols (LOS)
5.10. Technical standard record (TSR)
The TSR shall list all service bulletins for the components that are covered by the CMP and
present the following information:
• Service bulletin number
• Service bulletin title
• Service bulletin revision number
• Service bulletin date
• Issue number of the CMP when the service bulletin was incorporated
At a minimum, the TSR shall be displayed as a five-column table. An example of a technical

standard record showing service bulletins is shown in Fig 16.
Fig 16. (Sheet 1 of 2) Technical standard record (TSR)
Fig 16. (Sheet 2 of 2) Technical standard record (TSR)
5.11. Table of contents (TOC)
The TOC will display the entire contents of the CMP.
The TOC will display only the following titles and related page numbers.
• Section titles (page numbers are not applicable)
• Topic titles
• First level proceduralStep or levelledPara titles
The TOC entries will be displayed in order of appearance in the CMP. The section titles will
be displayed left justified and each subsequent level of titles will be indented to show the
document hierarchy. The page where each title is found will be shown right justified. An
example of a table of contents is shown in Fig 17.
BRDP-S1-00497 – Number of sidehead levels to be presented in the Table of contents: The
number of sidehead levels in the table of contents will be presented as described in this chapter.
Fig 17. (Sheet 1 of 4) Table of contents (TOC)
5.12. List of Illustrations and list of tables (LOI, LOTBL)
The LOI and LOTBL list all the figures and tables in the CMP and their page numbers.
These lists will show the illustration/table number and title. The title will be left justified on
the page and the page number of the CMP on which they appear will be right justified.
An example of a LOI is shown in Fig 18.
An example of a LOTBL is shown in Fig 19.
These topics are generated content from the publication module and data modules contained
in the CMP. These topics shall not be a data module and not have any data module coding
presented.
BRDP-S1-00498 – Presentation of List of tables: The list of tables will be presented as
BRDP-S1-00499 – Present the prefix "Table" in the List of tables: The prefix "Table" will be
BRDP-S1-00500 – Presentation of List of figures: The list of figures will be presented as
BRDP-S1-00501 – Present the prefix "Fig" in the List of figures: The prefix "Fig" will be
Fig 18. (Sheet 1 of 3) List of Illustrations (LOI)
Fig 19. (Sheet 1 of 2) List of tables (LOTBL)
Fig 19. (Sheet 2 of 2) List of tables (LOTBL)
5.13. List of applicable specifications and documentation (LOASD)
The LOASD will be presented as a two-column table. The first column lists the specification
or document number and the second column lists the document title. An example of a list of
applicable specifications and documentation is shown in Fig 20.
This topic is generated content from the data modules contained in the CMP. This topic shall
not be a data module and not have any data module coding presented.
Fig 20. (Sheet 1 of 3) List of applicable specifications and documentation (LOASD)
5.14. List of suppliers (LOSUP)
The LOSUP should list all enterprise identification and information for all enterprises
mentioned in the CMP.
The LOSUP will be shown as a two-column table. The first column shows the MFR code of
the enterprise and the second column shows all relevant enterprise information. An example
of a LOSUP is shown in Fig 21.
Fig 21. (Sheet 1 of 2) List of suppliers (LOSUP)
Fig 21. (Sheet 2 of 2) List of suppliers (LOSUP)
5.15. Lists of support equipment and supplies (LOSE and LOSU)
The LOSE and LOSU shall list all support equipment and supplies mentioned in the CMP.
An example of an LOSE front matter page is shown in Fig 22.
An example of an LOSU front matter page is shown in Fig 23.
If there are no support equipment or supplies, it is not necessary to include that table.
These topics are generated content from the data modules contained in the CMP. These topics
shall not be a data module and not have any data module coding presented.
Fig 22. (Sheet 1 of 3) Lists of support equipment (LOSE)
Fig 23. (Sheet 1 of 3) Lists of supplies (LOSU)
5.16. The list of spares (LOSP)
The LOSP shall list all spares mentioned in the CMP.
An example of an LOSP front matter page is shown in Fig 24.
Fig 24. (Sheet 1 of 3) List of spares (LOSP)
5.17. Introduction
Refer to Section 3-2-2.2, Descriptive data modules for presentation of descriptive data
modules.
6. Functional and technical descriptions section
modules.
7. Maintenance and servicing section
Refer to Section 3-2-2.3, Procedural data modules for presentation of procedural data modules.
Refer to Section 3-2-2.4, Fault information data modules for presentation of fault information
data modules.
8. Illustrated parts data section
This section describes the page-oriented presentation of the IPD.
This section consists of four topics:
• Introduction
• Numerical Index
• Equipment Designator Index
• Detailed Parts Data
The page numbers in this section must start with the prefix "IPD" and be continuous through
all four topics.
8.1. Introduction (IPD)
modules.
8.2. Numerical index
At a minimum, the numerical index will be presented as a four-column table, with the option
to include a fifth column to the right of the part number column for airline use to record the
"Airline stock number". It will list all part numbers presented in the Detailed parts data (DPD).
Every instance of a part number in the DPD will be listed along with the corresponding figure
number, item number, and quantity. For every line entry in the numerical index, there must be
a value in each column except for the airline stock number column, if included.
The numerical index will be presented in alphanumerical order and will sorted by part number
first, then by the figure number, and then by the item number.
Refer to Fig 25 for a numerical index example.
8.2.1. Part number
Every instance of a part number in the DPD will be listed here. They should be shown exactly
as they appear in the DPD part number column.
If the <overLengthPartNumber> element is populated it will also be displayed as a separate
line entry in the part number column.
8.2.2. Figure number
The Figure number column will display the corresponding IPD figure number for each location
of the part number in the DPD.
8.2.3. Item number
The Item column will display the corresponding IPD item number for each location of the part
number in the DPD. All item number variants must also be shown in this column. The dash (-
) character used to indicate non-illustrated items should not be included in this column of the
numerical index.
8.2.4. Quantity
The Quantity column will display the quantity, <quantityPerNextHigherAssy>, of the part for
each location of the part number in the DPD.
Fig 25. (Sheet 1 of 2) Numerical index (IPD)
Fig 25. (Sheet 2 of 2) Numerical index (IPD)
8.3. Equipment designator index (EDI)
If the detailed parts data (DPD) includes equipment designators an equipment designator index
(EDI) will be provided. For every equipment designator the table will display the equipment
designator along with the corresponding figure number, and item number. Geographic location
may also be shown. The table columns will be arranged in the following order:
• equipment designator
• geographic location (optional)
• IPD figure number
• IPD item number
Refer to Fig 26 for an equipment designator example.

8.3.1. Equipment designator
Each equipment designator in the DPD section will be listed in this column.
8.3.2. Geographic location (optional)
If geographic locations are provided for an IPD figure, the geographic location corresponding
to the equipment designator may be listed in this column.
8.3.3. Figure number
The figure column contains the applicable IPD figure number and variant.
8.3.4. Item number
The item column contains the applicable IPD item number and variant.
Fig 26. (Sheet 1 of 2) Equipment designator index (IPD)
Fig 26. (Sheet 2 of 2) Equipment designator index (IPD)
8.4. Detailed parts data (DPD)
The DPD topic of the CMP will contain the complete collection of DPD data modules required
to support maintenance of the CMP end item units. Each DPD data module will contain one
"IPD figure set" which consists of IPD illustrations with one or more sheets (Fig 27) and one
DPL table (Fig 28).
8.4.1. IPD figure set number
S1000D Chap 5.3.1.3 requires the IPD figure number to be the "running number" of figures
(IPD DMs) within an IPD publication with a single MI and SNS. To support reuse of DMs,
CMPs may contain IPD modules with different MIs and SNSs.
The IPD figure number will be derived from the IPD catalogSequenceNumber element for
each IPD DM. The IPD figure number will consist of the SNS, @figureNumber attribute and
@figureNumberVariant attribute. The IPD figure number will be displayed with the title for
each IPD illustration sheet and with the IPD detail parts list.
Example: 34-21-01-01A
8.4.2. IPD illustration label
Each IPD illustration sheet will display "IPD Figure:", plus the IPD figure number and <title>
from the <figure> element of the DM at the bottom of each illustration sheet.
Example: IPD Figure 34-21-01-03A Sprocket assembly (Sheet 1 of 6)
8.4.3. IPD detail part list (DPL)
IPD part detail information will be presented in a table format generally as described for paper
deliverables shown in S1000D Chap 5.3.1.3 and page-oriented presentation in S1000D Chap
6.2.3.5.
The table header will display the IPD figure number and <title> from the <figure> element of
the DM preceded by the text "IPD figure set", followed by the text " - Detail parts list". Refer
to Fig 28.
Example: IPD figure set 34-21-01-03A Sprocket assembly - Detail parts list
The information presented will include the following - column headings in following order:
• Item
• Part number
• MFR
• Description
• QNHA
• UOC
8.4.4. IPD item number

The IPD item number is made up of the item attribute from the applicable
<catalogSeqNumber> and the @itemSeqNumberValue attribute from the applicable
<itemSeqNumber>.
The item portion of the IPD item number will be displayed with leading "0" values from the
<catalogSeqNumber>.
The @itemVariant attribute from the <catalogSeqNumber> will not be displayed.
The numeric values of the @itemSeqNumberValue will not be displayed. Only alpha values
will be displayed.
Example: CSN item="001"ISN @itemSeqNumberValue ="00A"is displayed as "001A"
If no alpha variant is required, then the @itemSeqNumberValue attribute should consist of 3
zeros.
Example: CSN item="001"ISN @itemSeqNumberValue ="000"is displayed as "001"
When the itemSeqNumber/partLocationSegment/notIllustrated element is present, display a
dash "-" before the IPD item number.
Example: "-001A" indicates IPD item "001A" is not illustrated
8.4.5. Part number
The Part number column will display the content of @partNumberValue attribute within the
<partRef> element.
8.4.6. Manufacturer's code
The Manufactur's code column will display the content of manufacturerCodeValue attribute
within the <partRef> element.
8.4.7. Description
The Description column is used to display the basic description of the item and other
descriptive information.
8.4.7.1. Indentation
The first line of text in the Description column will begin with the number bullets derived from
the indenture attribute of the <catalogSeqNumber>. The quantity of bullets to be displayed is
equal to the indenture attribute minus 1.
Examples:
Indenture "1" show no bullets: "DESCRIPTION TEXT"
Indenture "2" show 1 bullet: ".DESCRIPTION TEXT"
Indenture "3" show 2 bullets: "..DESCRIPTION TEXT"
The period character will be used to indicate indentation.
8.4.7.2. Item name (DFP)
Display the item name immediately following the indentation periods. The item name is
typically the content of itemSeqNumber/partSegment/itemIdentData/descrForPart. If parts are
being referenced from a CIR the descrForPart text can be obtained from the referenced CIR
entry.
Example:
Indenture ="3", <descrForPart>HOUSING, MAIN</descrForPart>
Shown as "..Housing, Main".
8.4.7.3. Other Description Content

Supplementary information which relates to the part, its usage, interchangeability, part number
modification, and its location should also appear.
When these other elements/attributes are present, show their content as described in the
following:
Element: itemSeqNumber/partSegment/itemIdentData/overLengthPartNumber - Show the
words "ORIGINAL PART NUMBER -", followed by the element content.
Element: itemSeqNumber/partSegment/itemIdentData/limitedPartNumber - Show the words
"LIMITED PART NUMBER -", followed by the element content.
Element: itemSeqNumber/partSegment/itemIdentData/customerStockNumber - Show the
words "CUSTOMER STOCK NUMBER -", followed by the element content.
Element: itemSeqNumber/partSegment/procurementData/enterpriseRef/name - Show the
words "SUPPLIED BY", followed by the element content.
Example: Supplied by XYZ Corporation
Element: itemSeqNumber/partSegment/techData/fitmentCode Attribute: fitmentCodeValue

= 1 - Show "SEMI-FINISHED PART"
Element: itemSeqNumber/partSegment/techData/sparePartClass Attribute::
sparePartClassCode
0 – Show "NON-PROCURABLE PART"
1 – Show "EXPENDABLE PART"
2 – Will not display any text.
6 – Will not display any text.
The sparePartClassCode attribute value will be consistent with the value of the Spec 2000 spare
parts class (SPC) code.
Element: itemSeqNumber/partSegment/techData/specDocument Attributes:
manufacturerCodeValue and specDocumentNumber - Show the word "SPECIFICATION"
followed by the content of the specDocumentNumber attribute, followed in parenthesis by the
content of the manufacturerCodeValue attribute.
Example:
SPECIFICATION 12345678-999 (12345)
Element: itemSeqNumber/partSegment/techData/calibrationMarker - If this element is

present show the words "THIS PART REQUIRES CALIBRATION."
Element: itemSeqNumber/partSegment/techData/hazardousClass Attribute:
hazardousClassValue
hz01 – Show "WARNING – EXPLOSIVE PART"
hz02 – Show "WARNING – PART CAN CONTAIN COMPRESSED GASSES"
hz03 – Show "WARNING - PART CAN CONTAIN FLAMMABLE LIQUIDS"
Element: itemSeqNumber/partSegment/partRefGroup/replacedBy Attribute:

replacementCode - Show the text that corresponds to the project decision for the value of the
replacementCode attribute, followed by the content of the child element that defines the
replacing item.
The allowed values for the replacementCode attribute are:
<replacedBy replacementCode="SUPSD BY">
<replacedBy replacementCode="SUPSDS">
<replacedBy replacementCode="RPLD BY">
<replacedBy replacementCode="RPLS">
Element: itemSeqNumber/partSegment/partRefGroup/replacedBy Attribute:

replacementCode
SUPSD BY – Show "SUPERSEDED BY ITEM"
SUPSDS – Show "SUPERSEDES ITEM"
RPLD BY – Show "REPLACED BY ITEM"
RPLS – Show "REPLACES ITEM"
Element: itemSeqNumber/partSegment/partRefGroup/replacedBy - Show the applicable

words, followed by the catalogSeqNumberRef element that defines the related part.
Example:
The child element is a catalogSeqNumberRef with a value of "34-20-01-01A-050A",
the line would show: "REPLACED BY item 50A"
If the replacedBy element also contains a replacementCond element, show the contents of the
replacementCond element on a separate line directly under the replacedBy line.
Example:
REPLACED BY ITEM 050A
EXCEPT IN THE HEATER ASSY
Element: itemSeqNumber/partSegment/partRefGroup/optionalPart - Show the words

"OPTIONAL PART ITEM", followed by the catalogSeqNumberRef element that defines the
optional part.
Example:
the line would show: "OPTIONAL PART ITEM 050A"
Element: itemSeqNumber/partSegment/partRefGroup/preferredSparePart - Show the words

"PREFERRED SPARE ITEM", followed by the catalogSeqNumberRef element that defines
the preferred spare part.
Example:
the line would show: "PREFERRED SPARE ITEM 050A"
Element: itemSeqNumber/partSegment/partRefGroup/alteredFromPart - Show the words

"ALTERED FROM ITEM ", followed by the catalogSeqNumberRef element that defines the
altered from part.
Example:
The child element is a catalogSeqNumberRef with a value of "34-20-01-01A- 050A",
the line would show: "ALTERED FROM ITEM 050A"
If the alteredFromPart element also contains an alteredFromPartDescr element, show the

contents of the alteredFromPartDescr element on a separate line directly under the first
alteredFromPart element line.
Example:
"ALTERED FROM ITEM 050A"
"A LEAD-IN CHAMFER IS MACHINED IN THE VALVE BORE"
Element: itemSeqNumber/partSegment/partRefGroup/localFabricationMaterial - Show the

words "MANUFACTURED FROM ITEM", followed by the catalogSeqNumberRef element
that defines the manufactured from part.
Example:
The child element is a catalogSeqNumberRef with a value of "34-20-01-01A- 050A",
the line would show: "MANUFACTURED FROM ITEM 050A"
Element: itemSeqNumber/partLocationSegment/attachStoreShipPart Attribute:
attachStoreShipPartCode
1 – Show "ATTACHING PART"
2 – Show "STORAGE PART"
3 – Show "SHIPPING PART"
Element: itemSeqNumber/partLocationSegment/selectOrManufactureFromIdent Attribute:

selectOrManufactureValue
f – Show "DURING ASSEMBLY SELECT: ", then show the content of the
selectOrManufacture element. If the selectOrManufacture element is not present,
show "SELECT DURING ASSEMBLY".
t – Show "DURING TEST SELECT FROM: ", then show the content of the
selectOrManufacture element. If the selectOrManufacture element is not present,
show "SELECT DURING TEST".
m – Show "LOCALLY MANUFACTURE OR PROGRAM FROM: ", then show the

content of the selectOrManufacture element.
r – Show "REWORKED FROM: ", then show the content of the selectOrManufacture
element. The selectOrManufacture element must have content or the attribute value
"r" should not be used.
Element: itemSeqNumber/partLocationSegment/descrForLocation - Show the content of the

descrForLocation element.
Element: itemSeqNumber/functionalItemRef Attribute: functionalItemType value of "fit01"
Attribute: functionalItemNumber value of "YYYYY…"
If there is only one functionalItemRef element, show the text "REF DES: " then show the
content of the functionalItemNumber attribute.
Example: "REF DES: AR101"
If there are more than one functionalItemRef elements, then show the text "REF DES: ",
followed by the content of each functionalItemNumber attribute from each functionalItemRef
element, separated by commas.
Example: "REF DES: AR101, AR102, AR105"
8.4.8. Quantity per NHA (QNHA)

This column will display the content of the itemSeqNumber\quantityPerNextHigherAssy
element.
8.4.9. Usable on Code (UOC)
This column will display the content of the itemSeqNumber/applicabilitySegment/
usableOnCodeEquip or itemSeqNumber/applicabilitySegment/usableOnCodeAssy element as
applicable. If there is more than one element, separate each value with a comma and a space.
Example:
usableOnCodeEquip = "A"
usableOnCodeEquip = "B"
Display = "A, B"
Fig 27. (Sheet 1 of 2) Illustration (IPD)
Fig 27. (Sheet 2 of 2) Illustration (IPD)
Fig 28. (Sheet 1 of 3) Detail parts list (IPD)
3-2-3. Packaging
1. CMP Package
A CMP data package will be a .zip file consisting of the following:
• Data Dispatch Notification [ddn.xsd]
• Publication Module [pm.xsd]
• Data Modules
o Content DMs [descript.xsd, proced.xsd, fault.xsd, ipd.xsd]
o Supporting DMs [container.xsd, brex.xsd]
o Applicability Cross-Reference Table (ACT) [appliccrossreftable.xsd]
o Condition Cross-Reference Table (CCT) (optional) [condcrossreftable.xsd]
o Product Cross-Reference Table (PCT) [prdcrossreftable.xsd]
o Common Information Repositories (CIRs) [comrep.xsd]
▪ Parts (optional)
▪ Supplies (optional)
▪ Warnings (optional)
▪ Cautions (optional)
▪ Tools (optional)
▪ Enterprise
• ICNs
• CSL [dml.xsd] (optional for engine CMPs)
• PDF
Appendix A. References
Table 6 References
ATA iSpec 2200 ATA Specification 2200. Information Standards for Aviation
Maintenance.
ATA e-Business Program
(www.ataebiz.org)
NCAGE/CAGE NATO Support Agency (NSPA)

Codes (https://eportal.nspa.nato.int/ac135public/)
S1000D International Specification for Technical Publications

Aerospace and Defence Industries Association of Europe (www.asd-
europe.org) (www.s1000d.org)

Spec1000BR 4.1 2017.1 FINAL

Uploaded by

Document Information

Original Description:

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

Spec1000BR 4.1 2017.1 FINAL

Uploaded by

Copyright:

Available Formats

ATA Spec 1000BR_4.

Civil Aviation Business

1000BR Revision 2017.1

AIR TRANSPORT ASSOCIATION OF AMERICA, INC. ("ATA") PRODUCT LICENSE

IMPORTANT NOTICE: This document is intended to be used only in an electronic

For Additional Information

For Technical Information and Change Submissions

• Revision 2015.1 – December 2015

• Revision 2009.2 – December 2009

• Revision 2009.1 – March 2009 – Original Issue

Section 2-2 Moved from Appendix A.

Chapter 3 Introduced a new chapter for Component Maintenance Publication Usage

Appendix A Moved from Appendix C.

1-5. S1000D Change Proposal Form (CPF) process

2-1. General Civil Aviation Business Rules

Table 2 General Civil Aviation Business Rules

Information Sets Schemas

S1000D objects (eg, data modules,

Page-oriented publications and/or

Note: In this document, chapter references are to S1000D specification chapters.

Table 4 S1000D References

Chap 5.3.1.4 Common requirements - Component maintenance

Chap 6.2.1 Page-oriented publications - Page layout, paper publications, headers

Chap 6.2.2 Page-oriented publications - Typography and layout elements

Chap 6.2.3.2 Layout rules and examples - Descriptive data modules

Chap 6.2.3.3 Layout rules and examples - Procedural data modules

Chap 6.2.3.5 Layout rules and examples - IPD publication

o Title page (TP)

o Copyright statements (COPY)

o Administrative and legal statements (ADMIN)

o Safety statements (SAFE)

o List of effective data modules (LOEDM)

o Change record (CR)

o List of abbreviations (LOA)

o List of terms (LOT)

o List of symbols (LOS)

o Technical standard record (TSR)

o Table of contents (TOC)

o List of illustrations (LOI)

o List of tables (LOTBL)

o List of applicable specifications and documentation (LOASD)

o List of suppliers (LOSUP)

o List of supplies (LOSU)

o List of spares (LOSP)

• Functional and technical descriptions

o Description of function (FUNC)

o Technical description (DESC)

o Diagrams and schematics (SCHEM)

• Maintenance and servicing

o Task sets (TS)

o Examination, test, checks, and fault isolation (TEST)

• Illustrated parts data

o Numerical index (IPD)

o Equipment designator index (IPD)

o Detailed parts data (IPD)

3-2-2. Rules and examples

• The text "COMPONENT MAINTENANCE PUBLICATION"

• Publication module code

• Component identity (model, part number, etc.)

• Horizontal rule (0.5pt line) as shown

• The text "COMPONENT MAINTENANCE PUBLICATION"

• Component identity (model, part number, etc.)