UG1500229 4 Iss C DACAS (Arbortext Editor Tool)

A
_
D
o
c
_
N
a
t
c
o
Tool User Guide

UG1500229.4 _
N
a
t
c
Issue: C o
_
C
o
d
e
A
_
D
DACAS (Arbortext Editor Tool) for System Description

o
c
_
C
o
(SD), Maintenance Procedure (MP), Aircraft Fault p

y
r
i
Isolation (AFI), Electrical Standard Practices (ESP) and g

h
t
_
F
Aircraft Structural Repair (ASR) Products o

o
t
e
r
V
_
<SUM M ARY_BE
GI N>
SUMMARY:
N
PURPOSE/SCOPE: a
t
c
o
_
B
o
This Tool User Guide defines how to use DACAS (Arbortext Editor Tool) to produce System x
1
Descriptions (SD), Maintenance Procedures (MP), Aircraft Fault Isolation (AFI), Electrical Standard V
_
Practices (ESP) and Aircraft Structural Repair (ASR). N

a
t
c
o
_
B
o
This tool User Guide is applicable to A350, A380, A320 family and A330 family. x
1
a
V
_
Applicable Discipline(s): N
a
 Aircraft Maintenance (AM)

t
c
o
 Aircraft Fault Isolation (AFI)

_
B
o
 Electrical Standard Practices (ESP) x

2
 Aircraft Structural Repair (ASR)

V
_
N
a
t
c
o
_
B
o
x
2
a
V
_
N
a
t
c
o
_
B
o
x
2
b
V
_
N
a
t
c
o
_
B
o
x
3
V
_
N
a
t
<SUM M ARY_END
> c
o
_
Document Owner: Authorizer for Application: B
o
x
3
a
V
_
N
a
t
Name: DUGRAVOT Stephane Name: NOWACZKOWSKI, Genevieve c

o
_
Function: Head Of TD Methods & Tools B

o
Function: Technical Data Products Methods & x
3
Tools Leader - SEDBDI Transformation - SEDBI b
V
_
N
a
t
c
o
_
B
o
x
4
© AIRBUS SAS 2019. ALL RIGHT S RESERVED. CONFIDENT IAL AND PROPRIET ARY DOCUMENT . V
_
Printed Copies are not controlled. Conf irm this is the latest issue av ailable through the Hub . N
Page 1 of 474 a
t
c
o
_
B
o
DACAS (Arbortext Editor Tool) for System Description (SD),
Maintenance Procedure (MP), Aircraft Fault Isolation (AFI), Electrical
UG1500229.4
Standard Practices (ESP) and Aircraft Structural Repair (ASR) Products Issue: C
TABLE OF CONTENTS
1 Introduction ...................................................................................................................... 8
2 Condition of Use ............................................................................................................... 9
3 Document Map View....................................................................................................... 10
3.1 Structure View ................................................................................................................ 11
3.2 Content View.................................................................................................................. 12
4 Menu Tabs and Toolbars ................................................................................................ 13
4.1 "File" Tab........................................................................................................................ 13
4.2 "Edit" Tab ....................................................................................................................... 14
4.3 "Find" Tab ...................................................................................................................... 15
4.4 "View" Tab...................................................................................................................... 16
4.4.1 How to Expand and Collapse...................................................................................... 17
4.5 "Insert" Tab .................................................................................................................... 18
4.6 "Table" Tab .................................................................................................................... 20
4.7 "Tools" Tab..................................................................................................................... 21
4.8 "Window" Tab................................................................................................................. 21
4.9 "DACAS" Tab ................................................................................................................. 22
4.9.1 "DACAS" Tab for Description and Procedure .............................................................. 22
4.9.2 "DACAS" Tab for AFI/TSM ......................................................................................... 23
4.10 Toolbars ......................................................................................................................... 24
4.10.1 Edit toolbar ................................................................................................................ 24
4.10.2 Mark-Up Toolbar ........................................................................................................ 25
4.10.3 Table Toolbar............................................................................................................. 26
5 Features of Arbortext Editor Tool..................................................................................... 27
5.1 Markup Management ...................................................................................................... 27
5.2 Tags............................................................................................................................... 28
5.2.1 How to Insert a Tag .................................................................................................... 28
6 Structure of Documentary Units (DU or UD) .................................................................... 30
6.1 Description Sub-Element with Configuration Management ............................................... 30
6.1.1 To create a DU – A350 context................................................................................... 32
6.1.2 To create DU – A380 context...................................................................................... 37
6.2 Description Sub-Element without Configuration Management .......................................... 39
6.2.1 To Create a Description Sublevel Tag: "descriptSubLevel" .......................................... 39
6.3 Task Sub-Element with Configuration Management......................................................... 42
6.3.1 To Create a Subtask Tag: "subtinv" ............................................................................ 42
6.3.2 To Create a Step Structure for Fault Confirmation (FC)/Fault Isolation (FI) .................. 48
© AIRBUS SAS 2019. ALL RIGHT S RESERVED. CONFIDENT IAL AND PROPRIET ARY DOCUMENT .
Printed Copies are not controlled. Conf irm this is the latest issue av ailable through the Hub .
Page 2 of 474
UG1500229.4
6.4 Task Sub-Element without Configuration Management .................................................... 51
6.4.1 To Create a Step Structure for Subtask Tag: "Step" .................................................... 51
7 Placeholder .................................................................................................................... 56
7.1 Context........................................................................................................................... 56
7.2 Tags Allowing Placeholders ............................................................................................ 57
8 How to Tag in Arbortext Editor Tool................................................................................. 58
8.1 To Insert a Paragraph Tag: "para" ................................................................................... 58
8.1.1 Generate a Line Break Tag: "para split" ...................................................................... 59
8.2 To Insert a List................................................................................................................ 60
8.2.1 Not Numbered List Tag: "randomList" ......................................................................... 60
8.2.2 Sequential List Tag: "sequentialList" ........................................................................... 63
8.3 To Insert a Note Tag: "note" ............................................................................................ 64
8.3.1 Add a Second Note Tag: "note split" ........................................................................... 66
8.3.2 Create a Random List inside the Note Tag: "attentionRandomList" .............................. 67
8.3.3 Create a Para inside the Note Tag: "notePara" ........................................................... 68
8.3.4 Create a Typical Sentence inside the Note Tag: "ts".................................................... 68
8.4 To Insert a Warning Tag: "warning" ................................................................................. 69
8.4.1 Insert a Placeholder ................................................................................................... 71
8.4.2 "Dangerous" Warning ................................................................................................. 73
8.5 To Insert a Caution Tag: "caution" ................................................................................... 75
8.6 To Insert a Typical Sentence Tag: "ts"............................................................................. 79
8.6.2 To Insert a Specific Typical Sentence in a Fault Confirmation-A350 context ................ 83
8.6.3 To Insert a Specific Typical Sentence in a Fault Isolation-A350 context ....................... 87
8.7 To Insert a Table Tag: "table".......................................................................................... 90
8.7.1 How to Use the "Span cells" Function ......................................................................... 96
8.7.2 How to Create a Header ........................................................................................... 102
8.7.3 Insert Tag(s) Inside a Table ...................................................................................... 103
8.7.4 How to Use the "Split Cells" Function........................................................................ 105
8.7.5 To Insert a Table Template Tag: "table template" ...................................................... 107
8.7.6 To Insert a Table Footnote Reference Tag: "footNoteRef" ......................................... 109
8.7.7 To Insert a Repair Material Table Tag: "matItem" & "repairMatItem" .......................... 113
8.8 To Allocate a Training Objective Tag: "trainingObj"-A350 context................................... 117
8.9 To Insert a FIN Tag: "fin"............................................................................................... 119
8.9.1 To Insert a FIN ......................................................................................................... 119
8.9.2 To Insert a FOR FIN List Tag: "ForfinList" ................................................................. 128
Page 3 of 474
UG1500229.4
8.9.3 To Insert FORFIN in Tables...................................................................................... 135
8.9.4 To tag a Circuit Breaker in a FIN............................................................................... 137
8.10 To insert an equipment list tag: “equlst”-A380 context.................................................... 140
8.11 To Insert a Measurement Conversion Tag: "quantity" .................................................... 144
8.11.1 To Modify a Measurement Conversion...................................................................... 146
8.12 To Insert a Reference Tag ............................................................................................ 149
8.12.1 Description Tag: "refDescription" .............................................................................. 149
8.12.2 Description Title LVL1 tag "refDescriptTitle1" ............................................................ 154
8.12.3 Task Tag: "refTask".................................................................................................. 157
8.12.4 Task Method Tag: "refTaskMethod"-A350 concept.................................................... 161
8.12.5 Task Tag: "refTaskSol"-A380 context........................................................................ 164
8.12.6 Task for Corrective Action Tag: "refCorTask" ............................................................ 166
8.12.7 Task for Corrective Action Tag: "refCorPageBlock”-A380 context .............................. 170
8.12.8 Task for Corrective Action Tag: "externalCorRef”-A380 context ................................. 172
8.12.9 Wiring Tag: "refWiring" ............................................................................................. 175
8.12.10 Graphic Tag: "graphicRef" ........................................................................................ 178
8.12.11 Step Tag: "stepRef".................................................................................................. 181
8.12.12 Internal Reference Tag: "internalRef"........................................................................ 183
8.12.13 External Reference Tag: "externalRef"...................................................................... 185
8.12.14 Fault Confirmation Tag: "refFaultConf"...................................................................... 193
8.12.15 ESP Description Tag: "refEspmDesc" ....................................................................... 196
8.12.16 ESP Description Solution Tag: "refEspmDescSol"..................................................... 200
8.12.17 ESP Task Tag: "refEspmTask" ................................................................................. 205
8.12.18 ESP Task Solution Tag: "refEspmTaskSol" ............................................................... 209
8.12.19 MPD Tag: "mpdRef"................................................................................................. 214
8.12.20 CDL Tag: "afmRef"................................................................................................... 222
8.12.21 MMEL Tag "mmelRef"-A350 context......................................................................... 228
8.12.22 MMEL Tag "mmelRef"-A380 context......................................................................... 237
8.12.23 Fastener Tag: "refFastener"...................................................................................... 241
8.12.24 PDRS Tag: refPdrs .................................................................................................. 242
8.12.25 Reference to Subtasks Tag: “refSubtask”.................................................................. 246
8.13 To Insert a Panel or Door Tag: "access" ........................................................................ 249
8.13.1 Insert Placeholder (only for A350)............................................................................. 252
8.14 To Insert Consumable Tags .......................................................................................... 254
8.14.1 Consumable Tag: "consumable" ............................................................................... 254
8.14.2 To Insert a Consumable in a Note Tag: "nConsumable" ............................................ 260
8.14.3 General Consumable Tag: "generalConsumable" ..................................................... 261
Page 4 of 474
UG1500229.4
8.14.4 To Insert a General Consumable in a Note Tag: "nGeneralConsumable"................... 266
8.14.5 Engine Consumable Tag: "engConsumable"............................................................. 267
8.14.6 Vendor Consumable Tag: "vendorConsumable" ....................................................... 270
8.15 To Insert Circuit Breaker Tags....................................................................................... 273
8.15.1 Circuit Breaker Tags in the Procedure ...................................................................... 273
8.15.2 Circuit Breaker Tags in a C/B Table (Subtask 865) ................................................... 276
8.15.3 Circuit Breaker Tag: "cb" .......................................................................................... 283
8.15.4 To insert a List of Circuit Breakers: “autocbsublist”-A380 context............................... 285
8.15.5 To insert an SSPC tag: “SSPC”-A380 concept.......................................................... 290
8.16 To Insert Torque Value Tags......................................................................................... 292
8.16.1 Specific Torque Value Tag: "tor" ............................................................................... 292
8.16.2 Standard Torque Value Tag: "tors" ........................................................................... 295
8.16.3 To Modify Torque Value Data ................................................................................... 296
8.17 To Insert Tool Tags....................................................................................................... 299
8.17.1 Standard Tool Tag: "stdTool" .................................................................................... 300
8.17.2 To Insert a Standard Tool in a Note: "nStdTool" ........................................................ 308
8.17.3 Specific Tool Tag: "specificTool"............................................................................... 309
8.17.4 To Insert a Specific Tool in a Note: "nSpecificTool" ................................................... 318
8.17.5 Interchangeable Tools Tag: "interchTools" ................................................................ 319
8.17.6 COC Tool Tag: "cocTool"-A380 context .................................................................... 323
8.18 To Insert Expendable Tag: "expd"-A350 context............................................................ 327
8.18.1 Insert Placeholder .................................................................................................... 330
8.19 To Insert Expendable Tag: "expd"-A380 context............................................................ 335
8.20 To Insert Expendable Tag: "expEngine"-A380 context ................................................... 341
8.21 To Insert an Expendable Vendor Tag: "expdVendor" ..................................................... 342
8.22 To Insert an Expendable COC Tag: "expdCoc"-A380 context ........................................ 347
8.23 To Insert a Required Condition Tag: "reqCondition"....................................................... 350
8.24 To Insert an Action Tag: "action" ................................................................................... 352
8.25 To Insert a List of Choices Tag: "ListOfChoices" ............................................................ 353
8.26 To Insert Question/Answer Tags: "stepQuestion" and "stepAnswer" .............................. 357
8.27 To Insert a Line Replaceable Unit Tag: "lru" .................................................................. 363
8.28 To Insert a Non Line Replaceable Unit tag: "nlru" .......................................................... 365
8.29 To Insert a Fault Wire Tag: "faultwire"-A350 concept ..................................................... 367
8.30 To Insert a Fault Wire Tag: "faultwire"-A380 concept ..................................................... 376
8.31 To Insert a Wire Extremities tag: "wrg" .......................................................................... 381
Page 5 of 474
UG1500229.4
8.32 To Insert Superscript and Subscript Tags: "superScript" and "subScript"........................ 385
8.33 To Insert a Software Component Tag: "sw" ................................................................... 386
8.34 To Insert On-Board Link Tags ....................................................................................... 390
8.34.1 BITE Test tag: "biteTest" .......................................................................................... 390
8.34.2 DataLoading tag: "dataLoading" ............................................................................... 394
8.34.3 System Indication Report tag “SysInfoReport”_A380 context..................................... 397
8.34.4 ACMS System Pages Tag: "acms" ........................................................................... 400
8.35 To Insert an Illustration Item Tag: "item" ........................................................................ 402
8.36 To Insert a Standard Part Number Tag: "standardPN" ................................................... 404
8.37 To Insert bonding Tags ................................................................................................. 408
8.37.1 Bonding Process Tag: "bondingProcess" .................................................................. 408
8.37.2 TestMethod Tag: "bondingTestMethod" .................................................................... 412
8.37.3 Bonding Value Tag: "bondingValue" ......................................................................... 415
8.37.4 Bonding Final Protection Tag: "bondingFinalProtection" ............................................ 418
8.38 To Insert Metallic and Non-Metallic Materials Tag: "memat" & "nmemat" ........................ 422
8.39 To Insert Repair Category Tag: "category" .................................................................... 425
8.40 To Insert a To Be Defined (TBD) Tag: "TBD" ................................................................. 427
8.41 To insert a manual Highlight tag : “Highlight” ................................................................. 429
8.42 To insert zoning tag ...................................................................................................... 432
8.43 To insert accessPanel tag ............................................................................................. 435
9 To Delete ..................................................................................................................... 438
9.1 To Delete Circuit Breaker(s) inside a Circuit Breaker Table............................................ 438
10 File Tab........................................................................................................................ 440
10.1 Load a Copy................................................................................................................. 441
10.2 Save a Copy................................................................................................................. 442
10.3 Local Preview............................................................................................................... 443
11 Copy/Paste Function .................................................................................................... 445
12 Save in Repository/Save in Repository with Generate PDF............................................ 446
12.1 Save in Repository........................................................................................................ 446
12.2 Save in Repository with Generate PDF ......................................................................... 448
12.3 Process to Generate a PDF File.................................................................................... 449
12.4 Where to Find the PDF Document................................................................................. 450
12.5 Link with AWO.............................................................................................................. 451
12.6 PDF Preview ................................................................................................................ 455
Page 6 of 474
UG1500229.4
12.7 Revision Bars ............................................................................................................... 461
13 Consistency Check....................................................................................................... 462
14 Save Locally/Local Preview........................................................................................... 464
14.1 Save Locally................................................................................................................. 464
14.2 Local Preview............................................................................................................... 465
15 Appendix A. Correspondence between DACAS and GIPSY tags ................................... 468
16 Referenced Documents ................................................................................................ 472
17 Glossary....................................................................................................................... 472
Record of Revisions................................................................................................................. 473
Page 7 of 474
DACAS (Arbortext Editor Tool) for System Description (SD), Maintenance Procedure UG1500229.4
(MP), Aircraft Fault Isolation (AFI), Electrical Standard Practices (ESP) and Aircraft
Structural Repair (ASR) Products Issue: C
1 Introduction
This document defines how to use the Arbortext Editor tool to author the following Technical Data products:
 System Descriptions (SD)
 Maintenance Procedures (MP)
 Aircraft Fault Isolation (AFI for A350 and TSM for A380) and its Task Supporting Data (TS)
 Electrical Standard Practices (ESP)
 Aircraft Structural Repair (ASR)
Page 8 of 474
2 Condition of Use
Before starting in the Arbortext Editor tool, it is mandatory to crea te:
 a Preparation Work Order (PWO)
and
 an Authoring Work Order (AWO) in Generic Authoring Management System (GAMS).
Note: PWO and AWO creations are described in M20316.3 " ".
Important information: Access to CITRIX server is mandatory to work properly in the Arbortext Editor tool.
Page 9 of 474
3 Document Map View
The author can enter the data in the Arbortext Editor tool: either in the left window "Structure view" or in the right window "Content View".
Page 10 of 474
3.1 Structure View
The "Structure view" presents a graphical, hierarchical view of your document

structure.
Each element in the document occupies a line in the "Structure view". The lines are
indented to represent the hierarchical relationships of elements.
You can use the "Structure view" for viewing and navigating your document.
Page 11 of 474
3.2 Content View
The advantage of this view is that the relationship between content and
tags is most obvious.
Most of the text content is located between a pair of tags.
Page 12 of 474
4 Menu Tabs and Toolbars
This paragraph presents the most commonly used functions contained in the different tabs.
4.1 "File" Tab
Save: the document is saved locally in the Citrix environment.
Load a copy: Save a copy of the document in a specific file.

Save a copy: Save a copy of the document in a specific file with a
consistency check (more details in paragraph 10 File Tab).
Local preview: a preview is generated without PDF generation (more

details in paragraph 10 File Tab).
Page 13 of 474
4.2 "Edit" Tab
This tab contains functions used to manage text edition like the "Copy", "Paste", "Cut", "Delete" functions.
Page 14 of 474
4.3 "Find" Tab
This tab contains functions used to find elements in the document.
Use this function to find textual content.
Use this function to find the XML structure (tag or attributes).
Page 15 of 474
4.4 "View" Tab
This tab contains functions used to manage the layout of the document.
Click "Collapse/Expand Divisions".

Ref. Para. 4.4.1 How to Expand and Collapse
This function allows to synchronize the display of the

structure view with the content view.
Several options are available to display the content:

 "Full Tags":
 Complete xml view.
 "Partial Tags":
 Most xml tags are hidden.
 "No Tags":
 Only textual content.
Page 16 of 474
4.4.1 How to Expand and Collapse
Expand and collapse function:
Click "-" to collapse an element in the Document Map.
Click "+" to expand an element in the Document Map.
Page 17 of 474
4.5 "Insert" Tab
Use the "Insert" tab to insert markups, symbols, bookmarks, comments, etc.
You can enter a symbol using the <Symbol > element.
1. Put the cursor in the text, where the symbol is needed, and press the "Enter" key.
2. In the "Insert" menu, select "Symbol".
Page 18 of 474
An "Insert Symbol" window opens:
3. Select the required symbol
4. Click the "Insert" button to confirm the selection
Result:
Page 19 of 474
4.6 "Table" Tab
This tab contains functions used to manage table(s) in the document.
Ref. paragraph 8.7 To Insert a Table Tag: "table" to create a table inside the document.
Insert, delete, select or modify attributes of

row(s), column(s) or cell(s).
Divide a cell into several cells.
Convert a selected row to a header row.
Convert a selected row to a footer row.
Display the "Table Properties" pop-up window.
Page 20 of 474
4.7 "Tools" Tab
This tab contains orthographic tools to correct the document.
Display the "Spelling: English (US)" pop-up window for the spelling
correction of the text content.
4.8 "Window" Tab

This tab contains function used to manage the layout configuration.
No split screen
Left/right split screen
Top-bottom split screen
By default split screen
Page 21 of 474
4.9 "DACAS" Tab
This tab contains specific DACAS functions that are not only linked to the Arbortext Editor tool.
4.9.1 "DACAS" Tab for Description and Procedure

Applicability (green = applicable, grey = not applicable):
A350 A380 A320 Family A330 Family
SD MP FI TS SPD SPP ASR ASR MP SD TP TO MP SD TP TO MP SD TP TO
Description Procedure
X X N/A X X X X X X X N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
Used to update the content filled in at the creation of the Quantity/Torque tags.
Used to launch the editing checks (for more details, ref. paragraph 13 Consistency Check).
Display the DACAS version.
Save in Repository to save the document (for more details ref. paragraph 12 Save in
Repository/Save in Repository with Generate PDF).
For more details, ref. paragraph 12.5 Link with AWO
Page 22 of 474
4.9.2 "DACAS" Tab for AFI/TSM
SD MP FI TS SPD SPP ASR ASR MP SD TP TO
MP SD TP TO MP SD TP TO
N/A N/A X N/A N/A N/A N/A N/A N/A N/A X X TBD TBD TBD TBD TBD TBD TBD TBD
Used to update the content filled in at the creation of the

Quantity/Torque tags.
Used to launch the editing checks (for more details, ref. Para. 13
Consistency Check).
Displays the DACAS version.
Used to save in a temporary folder in SAP (for more details, ref. Para 12
Save in Repository/Save in Repository with Generate PDF).
For Graphical Editor use only:

For more details, ref. UG1500229.2 "DACAS and yEd for AFI".
Import decision tree graph is not valid for A380, A320 and A330
family.
Page 23 of 474
4.10 Toolbars
The toolbars contain icons. These icons are shortcuts to the functions described in the previous chapters.
4.10.1 Edit toolbar

The "Edit" toolbar contains buttons used to invoke several editing operations:
Cut Copy Paste Undo Redo
Save Spelling Insert a table
Document map (switch between structure view and content view)
Find and replace text elements Switch between left/right split and no split
Switch between top/bottom split and no split
Note: Do not use the crossed icons .
Page 24 of 474
4.10.2 Mark-Up Toolbar
The "Mark-up" toolbar contains buttons used to manage markups in a document.
Insert mark-ups Change the tag display
Modify attributes Select element content Collapse/Expand divisions
Find selection
Page 25 of 474
4.10.3 Table Toolbar
The "Table" toolbar contains buttons used to manage tables in the document.
Insert row above Delete row Vertically top align Horizontally centre align Modify borders
Insert Cell Right Span Cells Vertically bottom align Horizontally justified
Insert Cell Right Unspan cells Horizontally left align Table tag display
Insert row below Delete cell Vertically centre align Horizontally right align
Page 26 of 474
5 Features of Arbortext Editor Tool
5.1 Markup Management
Content start Content end

delimiter delimiter
Start of the tag End of the tag
Paragraph start Paragraph end

delimiter delimiter
Page 27 of 474
5.2 Tags
Each type of content in the Arbortext Editor tool is tagged. Depending on the cursor location, different tags are permitted.
5.2.1 How to Insert a Tag
1. Put the cursor where you want to insert a tag and press the "Enter" key.
Page 28 of 474
Then, a pop-up menu appears, giving all the permitted tags (in the current context):
2. Select the tag to be inserted.
Result:
Page 29 of 474
6 Structure of Documentary Units (DU or UD)
Before authoring in Arbortext, the author must structure the descriptions and tasks in Documentary Units (DU). This paragraph gives information
related to these structures.
6.1 Description Sub-Element with Configuration Management

In the descriptions, the DU is the lowest level of configuration management.
You can create your DU either in SAP:

 Ref. UG1500229.1 DACAS (SAP iPPE Module) for AM product,
 Ref. UG1500229.2 DACAS (SAP iPPE Module) and yEd for Aircraft Fault Isolation (AFI) product,
 Ref. UG1500229.3 DACAS (SAP iPPE Module) for Electrical Standard Practices (ESP) product),
 Ref. UG1500229.6 DACAS (SAP iPPE Module) for Aircraft Structural Repair (ASR) product
or in Arbortext Editor.
Important information: if a DU has been created in Arbortext, the basic solution is automatically created in SAP/iPPE.
To create several solutions, it is mandatory to use the impact link through DACAS SAP/iPPE. For more details, ref. UG1500229.5 Configuration
management User Guide.
Note: Deletion of DUs is not possible in the Arbortext Editor tool.

X N/A N/A X X N/A X N/A N/A X N/A X TBD TBD TBD TBD TBD TBD TBD TBD
Page 30 of 474
For A350: The DU can have two levels of indentation, DU2 for level 2, DU3 for level 3 and lower.
For A380, specific DUs with two levels of indentation can be created:
LVL1 title Level 1 indenture title
UD2 UD2 (corresponding to the level 2 title)
UD3 (corresponding to the level 3 title)
The UD6 is created automatically when
UD3/UD6 the sequence for UD3 is ended
UD4 Component Location Table
UD5 Circuit Breaker Table
Text
The UD9 is created automatically when
UD0/UD9 the sequence for UD0 is ended
Page 31 of 474
6.1.1 To create a DU – A350 context
In the following part, you will find the way to create DUs for A350
6.1.1.1 To Create a DU Level 2 Tag: "DescriptLevel2Inv"
1. Put the cursor between the "title" and "descripLevel1"

tags and press the "Enter" key.
Page 32 of 474
A pop-up menu appears:
2. Select the "descriptLevel2Inv" tag.
Page 33 of 474
Result in Arbortext:
3. Give a title to the Level 2 DU.
Page 34 of 474
6.1.1.2 To Create a DU Level 3 Tag: "DescriptLevel3Inv"
1. Put the cursor after the "title" tag and press the "Enter" key.
2. Select the "descriptLevel3Inv" tag.
Page 35 of 474
3. Give a title to the Level 3 DU.
Page 36 of 474
6.1.2 To create DU – A380 context
LVL 1 titles are created from PPE, you can refer to DACAS guides UG1500229.1 and UG1500229.2
Once the LVL1 has been created, you can create DUs from Arbortext editor:
1. Put the cursor after the title tag and press the "Enter" key.
2. Choose the type of UD you want.
You will find all the rules regarding UD creation in DACAS guides UG1500229.1 and UG1500229.2
2. Select sequence number on 4 digits

and click OK
Page 37 of 474
Page 38 of 474
6.2 Description Sub-Element without Configuration Management
6.2.1 To Create a Description Sublevel Tag: "descriptSubLevel"

A "SubLevel" can be created only after a level 3DU title.
If the DU has content, the cursor must be located after the last paragraph delimiter at the end of the DU content.
Thus it is possible to create up to 3 sub-levels:
Page 39 of 474
1. Put the cursor after the last paragraph delimiter and press the "Enter" key.
2. Select the "descriptSubLevel" tag.
Page 40 of 474
3. Give a title to the sublevel.
Page 41 of 474
6.3 Task Sub-Element with Configuration Management
Subtask, Common Information and Step for AFI are managed in configuration management.
The Subtask is the equivalent of the Document Unit of the description.
Important information: If a DU has been created in Arbortext, the basic solution is automatically created in SAP/iPPE.
Note: Deletion of Subtask Invariant and Step Invariant is not possible in the Arbortext Editor tool.
6.3.1 To Create a Subtask Tag: "subtinv"

ASR ASR
SD MP FI TS SPD SPP MP SD TP TO MP SD TP TO MP SD TP TO
N/A X X N/A N/A X N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
Rules for A350:

 For MP, the subtask creation is permitted inside the Job Set-Up, Procedure and Close-Up paragraphs.
Select the following infocodes:
 101 Aircraft System Configuration
 102 Close-up
 200 Maintenance Practices
 300 Servicing
 401 Removal/Installation
 402 Deactivation/Reactivation
 500 Test/Check after installation (MP04, MP14)
Page 42 of 474
 500 Adjustment/test (MP04, MP05, MP06, MP14)
 600 Inspection/Check
 700 Cleaning/Painting
 800 Approved repairs
 865 C/B opening/closing
 999 Expendables
 For FI: the subtask creation is permitted in the Job Set-Up and Close-Up paragraphs only.
 421 Fault Isolation procedure
 429 Fault Confirmation procedure
 For SPP: the subtask creation is permitted inside Job Set-Up, Procedure and Close-Up paragraphs.
 020 Remove/disconnect item
 200 Inspection check
 350 Repair
 420 Install/Reconnect Item
 760 Electrical Check
 910 Miscellaneous
 912 Electrical Procedure
 916 Clean and apply surface protection
 941 Aircraft/System configuration
 942 Close-up
 960 Replace
 For ASR, subtask creation is permitted inside the Procedure paragraph.

Page 43 of 474
 50 Removal of parts, material, paint, fastener, particles, adhesives, etc.
 160 Cleaning, preparation of repair area, masking
 205 Structure inspections for ADL and Repair
 282 Evaluation of damage/determination and rework
 450 Fitting and installation, cleaning, any sealing
 452 Composite material application and curing
 841 Determination and cutting
 843 Preparation of parts and material, countersinking and drilling
 919 Restore surface protection, any protective treatments
 972 Damage recording
Rules for A380, A320 Family and A330 Family: please refer to TDG0037.4 AIRCRAFT MAINTENANCE TASKORIENTED SUPPORT SYSTEM
(AMTOSS)
Page 44 of 474
1. Put the cursor after the delimiters and press the "Enter" key.
2. Select the "subtinv" tag.
A pop-up window comes up:
3. Select the Infocode, using the scrolling menu.
4. In the second field, select the Basic Configuration (except

for ESP and AFI products for which "Basic" is automatically
filled in).
5. Click "OK".
Page 45 of 474
A confirmation window comes up:
6. Click "OK".
7. Locate the cursor between the SubtaskTitle tags and

enter the title of the subtask. “SubtaskTitle” tags
automatically appear for the A350 program only.
Except for ASR, where the title is automatically filled in:
Page 46 of 474
Page 47 of 474
6.3.2 To Create a Step Structure for Fault Confirmation (FC)/Fault Isolation (FI)
ASR ASR
N/A N/A X N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
CAUTION: Step structure for A350 AFI must be built according to a specific order (tree -like structure).
For more details, refer to TDG0209.1 "AFI Authoring" and UG1500229.2 DACAS (SAP/iPPE Module) and yEd for AFI product.
Page 48 of 474
1. Put the cursor in the fault procedure and press the "Enter" key.
2. Click the "stepInv" tag.
3. Enter the title of the step
4. Put the cursor between the two delimiters and press

the "Enter" key.
5. Select the "stepBlock" tag.
Page 49 of 474
6. Put the cursor between the "stepBlock" tags and press the "Enter" key.
7. Select the required tag in the

pop-up menu.
Page 50 of 474
6.4 Task Sub-Element without Configuration Management
6.4.1 To Create a Step Structure for Subtask Tag: "Step"

ASR ASR
N/A X N/A N/A N/A X N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
Use the <step> tag to create the indentation of the subtask.
At first, you must create a subtask (ref. paragraph 6.3.1 To Create a Subtask Tag: "subtinv").
Example:
Sub-steps can be inserted into an existing step (recursive structure).
Thus it is possible to create up to 4 sub-levels:
Page 51 of 474
1. Create a subtask and give a title.
2. Press the "Enter" key.
Page 52 of 474
Structural Repair (ASR) Products 3. Select the "step" tag. Issue: C
4. Enter the text content of the step (1).
5. Put the cursor after the last paragraph delimiter and before the last "Step" tag, then press the "Enter" key.
6. Select the "step" tag.
Page 53 of 474
7. Enter the text content of the substep (a).
To insert 2 following substeps, you can press enter and choose the tag step (the step split function can no longer be used):
It will give this result:
Page 54 of 474
Result in Arbortext: Follow the same process for subsequent sub-levels:
Page 55 of 474
7 Placeholder
7.1 Context
A placeholder is created when data is not yet available.
There are two possibilities: either the data is not yet in the dedicated databases (examples: FIN, Consumable, etc.) or the data is not yet created
in DACAS (example: ref. task and description, graphic, etc.)
Two types of placeholders are allowed:

 Well formatted placeholder: the complete identifier of the data is known.
For example: A FIN already initialized at the Design Office, but not yet in the TDFIN database.
 Not Well formatted placeholder: the complete identifier is not yet defined.
For example: A reference to another Task or Description not yet authored.
The main differences between these 2 types of placeholders are:
 The well formatted placeholder will be automatically replaced by the real data once it is available in the associated database.
 The “Not Well formatted” placeholder is never automatically replaced by the real data. It is under the author’s responsibility to replace the
placeholder by the real data.
The “Not Well formatted placeholder” will be replaced by textual content in the final product (when it is authorized).
Depending on the tag type and the availability of the data, well-formatted or not well formatted placeholder will be used. Each case is described in
the corresponding paragraph.
Page 56 of 474
7.2 Tags Allowing Placeholders
Tags for which the placeholder is allowed are:
 Warning,  Access,
 Cautions,  Consumable,
 Typical sentence,  General consumable,
 FIN,  Circuit breaker,
 Description reference,  Open circuit breaker,
 Descriptive title LVL1 reference,  Close circuit breaker,
 Task reference,  Standard tools,
 Task method reference,  Specific tools,
 Task for corrective action reference,  Interchangeable tools,
 Wiring reference,  Expendable,
 Graphic reference,  LRU,
 Fault Confirmation reference,  Bonding process,
 ESP description reference,  Test method,
 ESP description solution reference,  Bonding value,
 ESP task reference,  Bonding final protection.
 ESP task solution reference,
 MPD reference,
 AFM reference,
 MMEL reference,
Page 57 of 474
8 How to Tag in Arbortext Editor Tool
8.1 To Insert a Paragraph Tag: "para"

ASR ASR
X X X X X X X X X X X X TBD TBD TBD TBD TBD TBD TBD TBD
The <para> tag is used to create a paragraph.
Use the <para> tag to enter a block of text.
Page 58 of 474
8.1.1 Generate a Line Break Tag: "para split"
The "para split" element is used to generate line breaks.
Example:
Put the cursor where the line break is needed

Select the "para split" element:
Page 59 of 474
8.2 To Insert a List
8.2.1 Not Numbered List Tag: "randomList"

ASR ASR
Use the <randomList> tag to write the text in a not numbered list format.
Note: In a random list, there are three possible levels of indentation.
Page 60 of 474
8.2.1.1 To Continue a Random List Tag: "listItem split"
When you are in a random list and when you want to continue the random list, use the <listItem split> tag.
The <listItem split> tag allows generating line breaks.
Location of the cursor

Press "Enter" and Select the "listItem split" element:
Page 61 of 474
8.2.1.2 To Continue with Text after a Random List
Use the <para> tag to continue the text in normal flow after a random list.
Location of the cursor

Select the <para> tag:
Page 62 of 474
8.2.2 Sequential List Tag: "sequentialList"
ASR ASR
Sequential lists are used to enter text in numbered list form.
Note: There is only one level of indentation in a sequential list.
Use the <sequentialList> tag to generate a sequential list.
Page 63 of 474
8.3 To Insert a Note Tag: "note"
ASR ASR
Use the <note> tag to insert a note.
1. Put the cursor in between the triangle delimiters and press the "Enter" key.
2. Select the note tag.
Page 64 of 474
It is possible to enter free text:
Or press the “enter” key, the following pop-up appears and select the tag.
Page 65 of 474
8.3.1 Add a Second Note Tag: "note split"
Information: The <note split> tag cannot be used anymore, to insert a second note you can put the cursor after the first <note> tag, press the
“enter” key and select the <note> tag:
Page 66 of 474
8.3.2 Create a Random List inside the Note Tag: "attentionRandomList"
Page 67 of 474
8.3.3 Create a Para inside the Note Tag: "notePara"
8.3.4 Create a Typical Sentence inside the Note Tag: "ts"
Page 68 of 474
8.4 To Insert a Warning Tag: "warning"
ASR ASR
Warnings have been predefined and stored in the DACAS Database. If the necessary Warning is missing from the DACAS table, the author must
send a request to the Warning database administrator (ref. AP5111 for the specific form).
Use the <warning> tag to insert a warning.
1. Put the cursor after the "subtask title" tag and press the "Enter" key.
2. Select the "warning" tag.
Page 69 of 474
3. Fill in the search criteria:

 Fill in the "Identifier" field (format W12345). If the identifier
is not fully known, enter the first characters followed by an
asterisk (e.g. W0000*).
 Fill in the "Content1" field (not mandatory).
 Fill in the "Category" field (not mandatory).
 Fill in the "Origin" field (not mandatory).
4. Click the "Search" button.
5. Select the requested warning.
6. Click "OK".
Page 70 of 474
8.4.1 Insert a Placeholder
8.4.1.1 "Not Well Formatted" Placeholder
If the author does not know the reference number to be tagged, the system will propose a “Not Well formatted” placeholder.
Information: The not well formatted placeholder will block the self-check in GAMS.
Page 71 of 474
2. Enter a summary of what will be in the warning.
3. Click "OK"
1. Click the "Placeholder" button.
Page 72 of 474
A "notWellFormatted"
mention appears in
the tag.
8.4.2 "Dangerous" Warning
Warnings related to Authority requirements (such as SFAR88, Critical Design Configuration Control Limitation (CDCCL)) must ha ve Dangerous
attribute = "Yes".
These specific warnings must be included in the "Safety Information" paragraph and also, where appropriate, before the relevant step in the
procedure.
If a necessary "Dangerous" warning is missing from the DACAS table, the author must send a request to the Warning database administrator (ref.
AP5111 for the specific form).
The product owner and Airbus Engineering Support specify the tasks in which a "Dangerous" warning must be tagged.
Page 73 of 474
8.4.2.1 To Delete a "Dangerous" Warning
In case of "Dangerous" warning deletion, a pop-window opens to confirm the deletion (to avoid any accidental deletion).
The "Dangerous" warning deletion must be confirmed.
Rule: Do not delete warnings with dangerous attribute = "Yes" without the agreement of the product owner.
Page 74 of 474
8.5 To Insert a Caution Tag: "caution"
ASR ASR
Cautions have been predefined and stored in the DACAS Database. If the necessary Caution is missing from the DACAS table, the author must
send a request to the Caution database administrator (ref. AP5111 for the specific form).
Use the <caution> tag to insert a caution.
2. Select the "caution" tag.
Page 75 of 474

 Fill in the "Identifier" field (format C12345). If the
identifier is not fully known, enter the first characters
followed by an asterisk (e.g. C0000*).
 Fill in the "Origin" field (not mandatory).
5. Select the requested caution.
6. Click "OK".
Page 76 of 474
Information: The not well formatted placeholder will block the self-check in GAMS.
Page 77 of 474
2. Enter a summary of what will be in the caution.
3. Click "OK"
mention appears in the tag.
Page 78 of 474
8.6 To Insert a Typical Sentence Tag: "ts"
ASR ASR
You can insert a typical sentence using the <ts> tag.
2. Select the "ts" tag.
Page 79 of 474
3. Fill in the search criteria fields:

 Fill in the "Identifier" field (format ST12345). If the
identifier is not fully known, enter the first characters
followed by an asterisk (e.g. ST00*).
5. Select the requested typical sentence.
6. Click "OK".
Page 80 of 474
Page 81 of 474
2. Enter a summary of what will be in the typical

sentence.
3. Click "OK"
Page 82 of 474
mention appears in
the tag.
8.6.2 To Insert a Specific Typical Sentence in a Fault Confirmation-A350 context

ASR ASR
A specific typical sentence "Go to the Fault Isolation" is mandatory in the final step of the Fault Confirmation.
Page 83 of 474
1. Put the cursor in the action of the final step and press the "Enter" key.
To fill the search data, ref. paragraph 8.6 To Insert a Typical Sentence Tag: "ts".
Note: The Typical Sentence "Go to Fault Isolation" is identified by the Category: "LNK_FI".
Page 84 of 474
Page 85 of 474
8.6.2.1 Insert a Placeholder
The placeholder must not be used in that case because only the
"LNK_FI" typical sentence is applicable.
Page 86 of 474
8.6.3 To Insert a Specific Typical Sentence in a Fault Isolation-A350 context
ASR ASR
A specific typical sentence "Go to the Close-up" is mandatory in the final step of the Fault Isolation procedure.
1. Put the cursor in the action of the final step and press the "Enter" key.
Page 87 of 474
To fill the search data, ref. paragraph 8.6 To Insert a Typical Sentence Tag: "ts".
Note: The "Go to the Close-up" Typical Sentence is identified by the Category: "LNK_CU".
Page 88 of 474
The placeholder must not be used in that case because only the
"LNK_CU" typical sentence is applicable.
Page 89 of 474
8.7 To Insert a Table Tag: "table"
ASR ASR
Use the <table> tag to insert a table.
Note: For AFI, put the cursor after an "action" tag.
2. Select the "table" tag.
Page 90 of 474
A pop-up window opens:
3. Select the number of rows and columns.
4. Click "OK".
Page 91 of 474
Note: "Table 1" is automatically written by

the system. It will disappear in the final
product. In case of multiple tables, use the
table title for suitable references.
Insert a title (not mandatory):

5. Put the cursor after the first table tag and
press the "Enter" key.
Page 92 of 474
Page 93 of 474
6. Select the "title" tag (not mandatory)
7. Enter the title of the

table (optional).
Page 94 of 474
8. Put the cursor in a cell and enter the free text.
Page 95 of 474
8.7.1 How to Use the "Span cells" Function
 Standard use:
1. Right-click a selection of cells to span them.
2. Select the "Span Cells" function.
Page 96 of 474
 Span function limitations (multiple cells spanned):
You can span two rows in one or several columns:
Two rows have been selected to

be spanned.
Page 97 of 474
Result:
It is also possible to span additional cells:
But it is not allowed to do so for all the columns of the table:
This case will generate issues during the AirN@v process and the production will be blocked. All the columns contain
two rows, but only one
Important information: To avoid these issues and get the same result, delete the row that is not needed. is visible.
Page 98 of 474
 Deep content splitting limitation (deep rows):
“Change bars — Deep splitting pages with change bars is not supported.”
Arbortext 6.0 M140 – Help Center
When spanning multiple rows together in such a way that the resulting row is deeper than the maximum height of the page: Arbortext will not correctly
support the splitting of the row onto mutiple pages when revision bars are displayed (ie. revised sub-task).
In such cases, this warning is raised while generating the PDFs:
 This limitation can cause some of the content of the spanned cell to be outside of the page and consequently not shown in the validation PDF.
NB: This limitation is only true for the PDF generated in DACAS, the task produced by Data Assembly for AirN@v will not suffer such limitations.
For instance, on the left-hand side: the Arbortext Editor view, and on the right: the related generated PDF view.
Page 99 of 474
Spanned rows deeper

than maximum height
allowed by A4
landscape page used
for PDF generation…
…leads to truncated
table and missing
content…
Page 100 of 474
 In order to avoid such display issues in the generated PDF: the row or column spanning (if deeper than a page) should be split into two or more
depending on the size of the table. For instance:
Correctly split table with

“Split” spanned rows content on both pages.
to accommodate A4
format.
Page 101 of 474
8.7.2 How to Create a Header
1. Select the row to be converted into a header.
2. Right-click in this area to open the pop-up. 3. Select the "Convert to Header Row" function.
Result:
Page 102 of 474
8.7.3 Insert Tag(s) Inside a Table
Depending on the product (SD, MP, ESP, AFI, ASR), several tags are permitted inside the cells of a table.
1. Put the cursor in a cell and press the "Enter" key.
2. Select the "para" tag.
Page 103 of 474
3. Put the cursor between the para tags and press the "Enter" key.
Page 104 of 474
8.7.4 How to Use the "Split Cells" Function
1. Right-click a selection of cells to split into several rows or columns.
2. Select the "Split Cells" function.
3. Define the number of rows and

columns and click "OK".
Page 105 of 474
Result in Arbortext: The selection is split in several rows:
Page 106 of 474
8.7.5 To Insert a Table Template Tag: "table template"
ASR ASR
Use the <table template> tag to insert a table template (Maintenance Template).
Note: It is not possible to create placeholders for table templates.
1. Put the cursor and press "Enter" key.
2. Select the "Table Template" tag.
Page 107 of 474

 Fill in the "Identifier" field. If the
identifier is not fully known, enter
the first characters followed by an
asterisk (e.g. TM*)
 Fill in the "Table_Title" field.
5. Select the requested table template.
6. Click "OK".
Page 108 of 474
The table template "Action/Result" is inserted:
8.7.6 To Insert a Table Footnote Reference Tag: "footNoteRef"

ASR ASR
Use the <footNoteRef> tag to create a footnote reference in a table.
Page 109 of 474
1. Put the cursor before the last table tag and press the "Enter" key.
2. Select the "ftnote" tag.
Page 110 of 474
3. Put the cursor between the footnote tags and

enter the content of the note in free text.
Page 111 of 474
4. Put the cursor in the table where the reference must appear (inside para delimiters) and press the "Enter" key.
5. Select the "footNoteRef" tag.
7. Click "OK".
6. Select the related footnote identifier.
Page 112 of 474
8.7.7 To Insert a Repair Material Table Tag: "matItem" & "repairMatItem"

ASR ASR
N/A N/A N/A N/A N/A N/A N/A X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
The "Repair Materials" table appears in the "Job Set-Up Information" paragraph for repair procedures (infocode 664).
Page 113 of 474
Structural Repair
1. (ASR) Products
Put the cursor in a paragraph and press the "Enter" key. Issue: C
2. Select the "matItem" tag.
3. Enter repair 4. Enter repair 5. Enter repair 6. Enter repair

material item number material designation material quantity material additional info
In the subtask, insert a "repair MatItem" tag.
Page 114 of 474
7. Put the cursor in a paragraph and press the "Enter" key.
8. Select the "repairMatItem"

tag.
The "Internal Reference" window opens:
9. Select the reference identifier and click "OK".
Page 115 of 474
Page 116 of 474
8.8 To Allocate a Training Objective Tag: "trainingObj"-A350 context
ASR ASR
X N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
This tag is valid for SD01 ONLY.
When you allocate a Training Objective (TO) to a Level 2 or Level 3 paragraph, the corresponding TO definition will be used to create the title.
Use the "trainingObj" tag.
1. Put the cursor before the title tag and press the "Enter" key.
2. Select the "trainingObj" tag.
Page 117 of 474
The "Modify Attributes" window opens:
3. Select the value and click "OK".
Page 118 of 474
8.9 To Insert a FIN Tag: "fin"
ASR ASR
X X X N/A N/A N/A N/A N/A X X X N/A TBD TBD TBD TBD TBD TBD TBD TBD
8.9.1 To Insert a FIN

For A350:
The FIN element is only allowed in SD05 descriptions, in the "Function/Description" paragraph.
FIN for MP is used in the "forfinList", in the "From/To" tables, "wrg", "cbOpen", "cbClose, "data loading" and "sw" tags.
FIN for AFI is used in the "forfinList", in the "From/To" tables, in the "LRU", "wrg", "cbOpen" and "cbClose" tags.
Concerning FINs for circuit breakers and LRUs, follow the same process.
You can insert a FIN using the "fin" tag.
For A380:
The FIN element is only allowed in AMM descriptions, in UD2 or inside “para” element.
FIN for AMM task is used in the "forfinList", in “sysInfoReport”, in “para” element, in the "From/To" tables, in "cbOpen", "cbClose, "data loading"
and "sw" tags.
FIN for TSM task is used in the "forfinList", in the 865/875 subtask, in the "LRU", "wrg", "cbOpen" and "cbClose" tags.
Page 119 of 474
1. Put the cursor after the title tag and press the "Enter" key.
2. Select the "fin" tag.
Page 120 of 474
3. To insert a FIN Manufacturer: "AIRBUS"

Composition of the FIN AIRBUS: Prefix - Circuit Letter -
Suffix - Appended Letter - Supplementary Part
 Select FIN Manufacturer: "AIRBUS"

 Enter FIN Prefix or “*”
 Enter FIN Circuit Letter (mandatory)
 Enter FIN Suffix or “*”
 Enter FIN Appended Letter or “*”
 Enter FIN Supplementary part or “*”
4. Click "Search"
5. Select the FIN
6. Click "OK"
Page 121 of 474
8.9.1.1 Insert Placeholder
If the data is not available in TDFIN, the system will propose to create a "Well formatted" or a "Not Well formatted" placeholder.
8.9.1.1.1 "Well formatted" Placeholder
If the author knows the reference number to be tagged, but the data is not yet available in the FIN database, the system will propose a well formatted
placeholder.
Page 122 of 474
1. Enter the references.
3. A pop-up "No result corresponding to the search

criteria" appears.
Page 123 of 474
1. Remove all the asterisks from the fields.
3. Enter the comment if needed. It can

be the designation or a specific
comment for authoring purposes.
4. Click "OK".
Page 124 of 474
A "WellFormatted"
mention appears in the
tag.
8.9.1.1.2 "Not Well formatted" Placeholder
Page 125 of 474
1. Enter the circuit letter.
3. The expected data is not in the search results.
Page 126 of 474
4. Remove the FIN Circuit Letter.
6. Enter the corresponding designation to

the missing FIN.
7. Click "OK".
Page 127 of 474
mention appears in
the tag.
8.9.2 To Insert a FOR FIN List Tag: "ForfinList"

ASR ASR
X X X N/A N/A N/A N/A N/A X X X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a FOR FIN List using the <ForfinList> tag.
There are two possibilities to create a FOR FIN List:

 FOR FIN List for MP
 FOR FIN List for AFI
Page 128 of 474
8.9.2.1 FOR FIN List for MP
The creation of a FOR FIN List is possible in the Job Set-Up, Procedure or Close-Up paragraphs in an MP task.
Note: The FOR FIN List must be entered inside a step tag and at the beginning of the step tag (ref. paragraph. 6.4.1 To Create a Step Structure for
Subtask Tag: "Step"). FOR FIN List must be inserted either in a step or in a sub-step, but not in both at the same time.
1. Put the cursor just after the first step tag and press the "Enter" key.
2. Select the "forfinList" tag.
Page 129 of 474
3. Put the cursor between the tags and press the "Enter" key.
4. Select the "fin" tag, ref. para 8.9 To Insert a FIN Tag: "fin".
Page 130 of 474
Note: In Arbortext, even if the FOR FIN List is written inside the step, it will appear before the related step in the PDF document and in the final
product:
Page 131 of 474
8.9.2.2 FOR FIN List for AFI
The creation of a FOR FIN List is possible in the Job Set-Up, Procedure or Close-Up paragraphs in an AFI task.
There are two possible cases:

 In the Job Set-Up and/or Close-Up paragraph, the FOR FIN List must be entered inside a required condition list (for required condition list
creation, ref. Para. 8.23 To Insert a Required Condition Tag: "reqCondition").
 In the Procedure paragraph, the FOR FIN List must be entered inside a step block (for step block creation, ref. paragraph 6.3.2 To Create
a Step Structure for Fault Confirmation (FC)/Fault Isolation (FI)). Create a new step block for each FOR FIN List (ref. UG1500229.2 DACAS
for AFI product).
1. Put the cursor between the tags and press the "Enter" key.
2. Select the "forfinList" tag.
Page 132 of 474
3. Put the cursor and press the "Enter" key.
4. Select the "fin" tag (to tag the fin, ref. paragraph 8.9 To Insert a FIN Tag: "fin".
Page 133 of 474
The FOR FIN List has been inserted in the Job Set-Up paragraph:
Page 134 of 474
8.9.3 To Insert FORFIN in Tables
ASR ASR
N/A X X N/A N/A N/A N/A N/A X X N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
There are only a few cases with FINs in tables.
For Descriptions, FINs within tables will be authored manually in free text format (no specific tag):
For Tasks (except AFI), if there is a FORFIN in a table, it will be necessary to put the FIN outside of the table.
And to write the instructions in the table concerning this FIN.
Page 135 of 474
Page 136 of 474
8.9.4 To tag a Circuit Breaker in a FIN
ASR ASR
X X X X X X N/A N/A X X X X TBD TBD TBD TBD TBD TBD TBD TBD
Users can tag a C/B (RCCB type) as a FIN (or LRU). To do so, a “forfinList” tag must be created first, refer to paragraph 8.9.2 To Insert a FOR FIN List
Tag: "ForfinList" :
1. Put the cursor in a forfinList and press the "Enter" key.
2. Select the "fin" tag.
Page 137 of 474
1. Enter the circuit letter
2. Select the Fin Nature

CB (RCCB type)
3. Click "Search"
4. Select the CB
5. Click OK
Page 138 of 474
Page 139 of 474
8.10 To insert an equipment list tag: “equlst”-A380 context
A350 A380
ASR ASR
SD MP FI TS SPD SPP MP SD TP TO
N/A N/A N/A N/A N/A N/A N/A N/A N/A X N/A N/A
You can insert a FIN in a Component Location Table in an SD (refer to paragraph 6.1 Description Sub-Element with Configuration Management)
using the <equlst> tag. This tag calls the “equinv” tag.
1. Put the cursor in a DU4 content and press the "Enter" key.
Page 140 of 474
2. Select the "equlst" tag.
Page 141 of 474
3. Search for the requested FIN(s) (refer to 8.9 To Insert a FIN Tag: "fin"
for details).
Page 142 of 474
Page 143 of 474
8.11 To Insert a Measurement Conversion Tag: "quantity"
ASR ASR
X X X X X X N/A X X X X X TBD TBD TBD TBD TBD TBD TBD TBD
Use the <quantity> tag to insert a measurement conversion.
These units are compliant with TDS0041. For more details, ref. TDS0041" Units & Measurement for Technical Data Products".
1. Put the cursor in a para and press the "Enter" key.
2. Select the "quantity" tag.
Page 144 of 474
3. Select the requested "Category"
4. Select the requested "Unit from" and "Unit To".
"Converted Values" field with two decimal places after the

comma (corresponding to the Round-Up selection).
5. Fill in the "Value" field.

The converted values are automatically displayed.
6. Fill in the "Min" and "Max" fields for tolerance range.
7. Select the decimal place after the comma for 8. Click "OK".
the "Converted Values" field.
Page 145 of 474
8.11.1 To Modify a Measurement Conversion

You can modify a conversion using the <Modify quantity data > function.
1. Select the related quantity tag to be modified.
Page 146 of 474
2. In the "DACAS" menu, select "Modify Quantity Data".
Page 147 of 474
3. Change the values to be modified
4. Click "OK".
Page 148 of 474
8.12 To Insert a Reference Tag
8.12.1 Description Tag: "refDescription"

ASR ASR
X X X X N/A N/A X X X X X X TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to a description using the <refDescription > tag.
Page 149 of 474
2. Select the "refDescription" tag.
Page 150 of 474
3. Fill in the Search Criteria:

 Fill in the "CHSESU" field. If the CHSESU is not fully
known, enter the first digits followed by an asterisk (at
least the first four digits for example: 2371*).
 Select the "Topic" (TO1, STPD, etc., or the asterisk if the
PMS is not known). For A380, select TO5 for an AMM
description and FITSD for a TSM description (Task
Supporting Data).
 Fill in the "Title" field or leave it blank if the title is not
known (not mandatory).
5. Select the requested reference description.
6. Click "OK".
Page 151 of 474
If the data is not available, the system will propose only a "Not Well formatted" placeholder.
1. Enter a reference.
3. There is no result corresponding to the expected data.
Page 152 of 474
4. Click the "Placeholder" button. 5. Enter at least the CHSESU and the
title (if known) in the comments field.
6. Click "OK".
A "Not Well formatted" mention

appears in the tag.
Page 153 of 474
8.12.2 Description Title LVL1 tag "refDescriptTitle1"
ASR ASR
N/A N/A N/A X N/A N/A X X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to an LVL1 title using the <refDescriptTitle1> tag.

It can also be added in the Repair material table.
2. Select the "refDescriptTitle1" tag.
2. Select the “refDescription” tag. Page 154 of 474

known, enter the first digits followed by an asterisk (for
example: 51*).
 Select the TOPIC (STSC, TO1, *, etc.).
 Fill in the "Title" field (not mandatory).
5. Select the reference description LVL1TITLE.
6. Click "OK".
Page 155 of 474
For more details, ref paragraph 8.12.1.1.1 "Not Well formatted" Placeholder.
2. In the "Optional placeholder information" field, give at

least the CHSESU and the title of the level one paragraph"
1. Click the
"Placeholder" button.
3. Click "OK".
Page 156 of 474
mention appears in
the tag.
8.12.3 Task Tag: "refTask"

ASR ASR
X X X X N/A N/A X X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to a task using the <refTask> tag.
2. Select the "refTask" tag.
Page 157 of 474

known, enter the first digits followed by an asterisk, (for
example: 29*).
 Fill in the "Info_Code" field (not mandatory). Info_Code is
the functional code of the task ID. For example,
Info_Code is 562 for task “P_290000_562_04_T”.
5. Select the reference task.
6. Click "OK".
Page 158 of 474
For more details, ref. paragraph 8.12.1.1.1 "Not Well formatted" Placeholder.
Page 159 of 474
2. In the "Optional placeholder information" field, give

1. Click the at least the CHSESU, Infocode and a short
"Placeholder" button. description of the corresponding task.
3. Click "OK".
Page 160 of 474
8.12.4 Task Method Tag: "refTaskMethod"-A350 concept
ASR ASR
N/A X X N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to a task method using the <refTaskMethod > tag.
2. Select the "refTaskMethod" tag.
To fill in the search data, ref. paragraph 8.12.3 Task Tag: "refTask".
Page 161 of 474
Page 162 of 474
2. In the "Optional placeholder information" field,

give at least the CHSESU, Infocode and a short
description of the corresponding task.
3. Click "OK".
Page 163 of 474
8.12.5 Task Tag: "refTaskSol"-A380 context
A350 A380
ASR ASR
SD MP FI TS SPD SPP MP SD TP TO
N/A N/A N/A N/A N/A N/A N/A N/A X N/A X N/A
You can insert a cross-reference to a task specific solution using the <refTaskSol> tag.
2. Select the "refTaskSol" tag.
To fill in the search data panel, refer to paragraph 8.12.3 Task Tag: "refTask".
Page 164 of 474
Page 165 of 474
8.12.6 Task for Corrective Action Tag: "refCorTask"
ASR ASR
N/A X N/A N/A N/A N/A N/A N/A X N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a reference to a task for corrective action using the <refCorTask > tag.
Compared with the "Reftask" tag, the "refCorTask" tag has a specific behavior:
The "refCorTask" tag is generally used for inspection tasks. After the inspection, a cross-reference to the AM repair task is mentioned.
In AirN@v, in the Referenced Information table of the Job Set-Up information paragraph, the wording "for corrective action" with the AM repair task
number is displayed.
Page 166 of 474
2. Select the "refCorTask" tag.
Page 167 of 474
1. Click the
2. In the "Optional placeholder information" field, give at least

the CHSESU, Infocode and a short description of the
corresponding task.
3. Click "OK".
Page 168 of 474
tag.
Page 169 of 474
8.12.7 Task for Corrective Action Tag: "refCorPageBlock”-A380 context
ASR ASR
N/A N/A N/A N/A N/A N/A N/A N/A X N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a reference to a task for corrective action using the <refCorPageBlock> tag.
2. Select the “refCorPageBlock” tag.
Page 170 of 474
Page 171 of 474
8.12.8 Task for Corrective Action Tag: "externalCorRef”-A380 context
ASR ASR
You can insert an external reference to a task for a corrective action using the < externalCorRef > tag.
2. Select the “externalCorRef” tag.
Page 172 of 474
3. Select the related Manual using the drop-down menu.
4. Enter the CHSESU of the task to be referenced. The

mandatory format is NNNNNN.
5. Press the “Insert” button.
Page 173 of 474
Page 174 of 474
8.12.9 Wiring Tag: "refWiring"
ASR ASR
X X X X N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to a wiring using the <refWiring> tag.
1. Put the cursor in a paragraph (or an action for AFI) and press the "Enter" key.
2. Select the "refWiring"

tag.
Page 175 of 474

 Fill in the "ATA Chapter" field.
 Fill in the "ATA Section" field.
 Fill in the "ATA Subject" field.
Important information: CHSESU fields are
mandatory fields.
 Select the requested Diagram type.
 *: Unknown criterion
4. Click the "Search" button.  B: Block Diagram
 S: Detailed Diagram (Schematic)
 F: Functional Diagram
 W: Wiring Diagram
 C: Charts and Routing Diagrams
5. Select the wiring reference.  P: Panel Diagram
 D: Duplicated Diagram
6. Click "OK".
Page 176 of 474

give at least the CHSE and a title if possible.
1. Click the
3. Click "OK".
Page 177 of 474
mention appears in
the tag.
8.12.10 Graphic Tag: "graphicRef"

ASR ASR
X X X X X X x X X X X X TBD TBD TBD TBD TBD TBD TBD TBD
The <graphicRef> tag is used to refer to an illustration defined in the topic invariant of the Data Module.
Prior to inserting the "graphicRef", you must create the graphic invariant and solution.
Reminder: The UD illustration invariant has to be created in iPPE under the topic invariant before you create a reference in the Arbortext Editor tool
(ref. UG1500229.0 DACAS Introduction).
The title of a graphic illustration invariant appears in the reference of the illustration.
The reference to the illustration is mandatory to provide the illustration in the final product.
Note: Only illustrations of the topic invariant are proposed.
Page 178 of 474
1. Put the cursor between the delimiters and press the "Enter" key.
2. Select the "graphicRef"

tag.
Page 179 of 474

 Fill in the "Sequence" field (format: 1234) or enter an asterisk.
 Fill in the "Title" field or enter an asterisk.
5. Select the graphic reference.
6. Click "OK".
Page 180 of 474
If the graphic invariant and solution have been created before you insert the graphicRef, the search function shall raise the se graphic invariant and
solution. Thus, there is no need to insert a placeholder.
8.12.11 Step Tag: "stepRef"

ASR ASR
N/A X N/A N/A N/A X N/A X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
Use the <stepRef> tag to insert a reference to a step in a procedure.
2. Select the "stepRef" tag.

Page 181 of 474
3. Select the required step.
4. Click "OK".
Page 182 of 474
8.12.12 Internal Reference Tag: "internalRef"
ASR ASR
X X X X X X X X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert an internal reference using the <internalRef> tag.
2. Select the "internalRef" tag.
The "Internal Reference" window opens:
Page 183 of 474
All subtask identifiers (related to the current task or description solutions) are displayed.
3. Select the subtask identifier.
4. Click "OK".
Page 184 of 474
8.12.13 External Reference Tag: "externalRef"
ASR ASR
X X X X N/A N/A X X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
For ESP (SPD and SPP, ref. paragraph 8.12.13.1 External Reference for ESP only Tag: "externalRef").
You can insert an external reference using the <externalRef> tag.
The "externalRef" tag will insert in the text content, the data entered in the data criteria panel.
This tag is used to do a cross-reference to a batch of data modules (sub-product + 2 to 6 digits).
For example: Refer to ASR 511100
Note: There is no AirN@v navigation for external cross-references.
Page 185 of 474
2. Select the "externalRef" tag.
Page 186 of 474

 Select the requested manual (mandatory).
 Fill in the "Reference" field (mandatory).
 AC
4. Click "Insert".  ARM
 ASR
 ESP
 MP
 MSP
 NDT
 CMM (Mandatory Reference: CHSESU, and
mandatory "Supplier" field: XXXXX (Cage
Code)).
 IPD (Mandatory Reference: CHSESU).
 WBM (Mandatory Reference: X-XX-XX).
Page 187 of 474
CMM example:
Result:
Page 188 of 474
8.12.13.1 External Reference for ESP only Tag: "externalRef"

ASR ASR
N/A N/A N/A N/A X X N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert an external reference using the <externalRef> tag. The "externalRef" tag will insert in the text content, the data entered in the data
criteria panel.
This tag is used to do a cross-reference to a batch of data modules (ESP + 3, 4 or 6 digits).
For example: Refer to ESP 205150.
Note: There is no AirN@v navigation for external cross-references.
Page 189 of 474
2. Select the "externalRef" tag.
Page 190 of 474

 Only ESP manual is selectable (mandatory).
 Fill in the "Reference" field (3, 4 or 6 digits
mandatory).
 Fill in the Config Letter
4. Click "Insert".
Page 191 of 474
Page 192 of 474
8.12.14 Fault Confirmation Tag: "refFaultConf"
ASR ASR
You can insert a reference to a Fault Confirmation in a Fault Isolation task using the <refFaultConf> tag.
1. Put the cursor in the action of the step and press the "Enter" key.
2. Select the "RefFaultConf" tag.
Page 193 of 474

known, enter the first digits followed by an asterisk,
(for example: 25*).
 Fill in the "Sequence" field (last two digits of the task
ID (XX)) (not mandatory).
5. Select “Fault confirmation”.
6. Click "OK".
Page 194 of 474
If the fault confirmation task has been created before insertion of the "RefFaultConf", the search function shall raise this fault confirmation task.
Thus, there is no need to insert a placeholder.
Page 195 of 474
8.12.15 ESP Description Tag: "refEspmDesc"
ASR ASR
N/A X N/A N/A X X N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a cross-reference to an ESP description invariant (all vendors) using the <refEspmDesc> tag.
2. Select the "refEspmDesc" tag.
Page 196 of 474
 Fill in the "CHSESU" field. If the CHSESU is not fully known,
enter the first digits followed by an asterisk (at least first four
digits for example: 20*).
 Select the "Topic" or asterisk.
5. Select the ESP Description.
6. Click "OK".
Page 197 of 474
2. In the "Optional placeholder information" field, give at least

1. Click the the CHSESU.
3. Click "OK".
Page 198 of 474
Page 199 of 474
8.12.16 ESP Description Solution Tag: "refEspmDescSol"
ASR ASR
You can insert a cross-reference to an ESP description solution (specific vendor) using the <refEspmDescSol> tag.
2. Select the "refEspmDescSol" tag.
Page 200 of 474

 Fill in the "CHSESU" field at least four digits and asterisk (for
example: 2010*).
 Fill in the "Topic" field (not mandatory).
 Fill in the "Solution" field (not mandatory, last two digits of the
Description ID).
 Fill in the "Vendor" field (not mandatory).
 Select the aircraft specificity (ALL/NON COMPOSITE/
COMPOSITE (not mandatory).
5. Select the ESP Description solution.
6. Click "OK".
Page 201 of 474
Result in Arbortext (for an Airbus solution):
Result in Arbortext (for a Vendor solution):
Note: There is no obvious difference between an Airbus and a Vendor solution (only the solution number differs).
Page 202 of 474
Page 203 of 474

least the CHSESU and the vendor name.
1. Click the
3. Click "OK".
tag.
Page 204 of 474
8.12.17 ESP Task Tag: "refEspmTask"
ASR ASR
You can insert a cross-reference to an ESP task invariant (all vendors) using the <refEspmTask> tag.
2. Select the "refEspmTask" tag.
Page 205 of 474
3. Fill in the Search Criteria

known, enter the first digits followed by an asterisk
(for example: 20*)
 Fill in the "Info_Code" field (not mandatory)
 Fill in the "Title" field (not mandatory)
5. Select the ESP task.
6. Click "OK".
Page 206 of 474
Page 207 of 474

least the CHSESU, the Infocode and a short description of
the corresponding task.
1. Click the
3. Click "OK".
tag.
Page 208 of 474
8.12.18 ESP Task Solution Tag: "refEspmTaskSol"
ASR ASR
You can insert a cross-reference to an ESP task solution using the <refEspmTaskSol> tag.
2. Select the "refEspmTaskSol" tag.
Page 209 of 474

 Fill in the "CHSESU" field. If the CHSESU is not fully known, enter the
first digits followed by an asterisk (for example : 20*)
 Fill in the "Info_Code" field (not mandatory).
 Fill in the "Solution" field (not mandatory, last two digits of the Task ID).
 Fill in the "Vendor" field (not mandatory).
 Select the aircraft specificity (ALL/NON COMPOSITE/COMPOSITE)
(not mandatory).
5. Select the ESP task.
6. Click "OK".
Page 210 of 474
Result (Airbus solution):
Result (Vendor solution):
Note: There is no obvious difference between an Airbus and a Vendor solution (only the solution number differs).
In the "Optional placeholder information" field, give at least the CHSESU, the Infocode, a short description of the corresponding task and the vendor
name.
Page 211 of 474

least the CHSESU, the Infocode, a short description of the
corresponding task and the vendor name.
205342_600 Repair of Clamps
(Airbus)
1. Click the
3. Click "OK".
mention appears in
the tag. © AIRBUS SAS 2019. ALL RIGHT S RESERVED. CONFIDENT IAL AND PROPRIET ARY DOCUMENT .
Page 212 of 474
Page 213 of 474
8.12.19 MPD Tag: "mpdRef"
ASR ASR
N/A X N/A N/A N/A N/A N/A X X N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert an MPD reference using the <mpdRef > tag in the "Reason for the job" paragraph.
If an MPD reference has been tagged in a solution, this MPD reference must be tagged in all the solutions.
1. Put the cursor in the "Reason for the job" paragraph and press the "Enter" key.
2. Select the "reasPara" tag.
Paragraph delimiters appear:
Page 214 of 474
4. Select the "mpdRef" tag.
Page 215 of 474
5. Fill in the "MPD Reference" field in accordance with the MP Authoring rules
(Ref. TDG208.1 Aircraft Maintenance Procedure (MP) Authoring
(paragraph 5 – Maintenance Procedure related to MPD requirements)).
Important Information: In IMS-PA, the MPD reference does not have the
same format. For example: IMS-PA 38100000M0601 – in DACAS, it is
381000-00M06.
If the MPD reference is not fully known, enter at least the first two digits (23*).
7. Select the requested MPD reference.
8. Click "OK".
Page 216 of 474
If the data is not available in the database, the system will propose to create a "Well formatted" or a "Not Well formatted" placeholder.
If the author knows the reference number to be tagged, but the data is not yet available in the MPD database, the system will propose a well
formatted placeholder.
Page 217 of 474
1. Enter the MPD reference with the format expected by DACAS
3. A pop-up "No result corresponding to the search criteria"

appears.
Page 218 of 474
4. Click the "Placeholder" button. 5. Enter the comment if needed. It

can be the designation or a
specific comment for authoring
purposes.
6. Click "OK".
Page 219 of 474
A "WellFormatted" mention appears in the tag.
Page 220 of 474

give a short description of the scheduled
maintenance to be done in this task.
1. Click the
"Placeholder" button. 3. Click "OK"
A "notWellFormatted" mention appears in the tag.
Page 221 of 474
8.12.20 CDL Tag: "afmRef"
ASR ASR
You can insert a CDL reference using the <afmRef > tag in the "Reason for the job" paragraph.
1. Put the cursor in the "Reason for the job" paragraph and press the "Enter"
key.
2. Select the "reasPara"

tag.
Page 222 of 474
3. Press "Enter".
4. Select the "afmRef"

tag.
Page 223 of 474
5. Fill in the "CDL Reference" field in accordance with the MP Authoring rules
(Ref. TDG208.1 Aircraft Maintenance Procedure (MP) Authoring (paragraph
14.1.3 Maintenance Procedure related to AFM-MCDL requirements)).
Important Information: In IMS-PA, the CDL reference does not have the same
format. For example: IMS-PA 2711D03657, in DACAS the DispatchCondID is
D03657 and the Function Code is 27-11.
In IMS-PA, we speak about the CDL criterion, in DACAS this criterion is
under the AFM tag.
 Fill in the "DispatchCondID" field (format: D12345) or enter an
asterisk.
 Fill in the "Function_Code" field. Enter at least the first two digits (21*).
6. Click the "Search"

button.
7. Select the requested dispatch condition.
8. Click "OK".
Page 224 of 474
If the author knows the reference number to be tagged, but the data is not yet available in the CDL database, the system will propose a well
1. Enter the CDL reference with the format expected by

DACAS.

button.
3. A pop-up "No result corresponding to the search

criteria" appears.
Page 225 of 474

be the designation or a specific comment
for authoring purposes.
4. Click the "Placeholder"
button.
6. Click "OK".
A "WellFormatted" mention
appears in the tag.
Page 226 of 474
8.12.20.2 "Not Well formatted" Placeholder
For more details, refer to paragraph 8.12.1.1.1 "Not Well formatted" Placeholder.
2 In the "Optional placeholder information" field, give at

least a short description of the maintenance deviation
linked to this task.
1 Click the "Placeholder"

button.
3. Click "OK".
Result in Arbortext: mention appears in the tag.
Page 227 of 474
8.12.21 MMEL Tag "mmelRef"-A350 context
ASR ASR
N/A X N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert an MMEL reference using the <mmelRef > tag in the "Reason for the job" paragraph.
key.

tag.
Page 228 of 474
3. Press "Enter".
4. Select the "mmelRef"

tag.
Page 229 of 474
5. Fill in the "MMEL Reference" field in accordance with the MP Authoring rules
(Ref. TDG208.1 Aircraft Maintenance Procedure (MP) Authoring (ref. paragraph
14.1.2. Maintenance Procedure related to MMEL requirements)).
Important Information: In GAMS, the MMEL reference does not have the same
format.
For example:
In GAMS: WO description: 2831D01967, criteria title: 283103A,
In DACAS: DispatchCondID: D01967; Function Code: 28-31-03A
 Fill in the "DispatchCondID" field (format: D12345) or enter an asterisk.
6. Click the "Search"  Fill in the "Function_Code" field. Enter at least the first two digits (26*).
button.  Fill in the "Title" field (not mandatory).
7. Select the requested MMEL reference.
8. Click "OK".
Page 230 of 474
If the data is not available in the data base, the system will propose to create a "Well formatted" or a "Not Well formatted" placeholder.
If the author knows the reference number to be tagged, but the data is not yet available in the MMEL database, the system will propose a well
Page 231 of 474
1. Enter the MMEL reference with the

format expected by DACAS.

button.
3. A pop-up "No result corresponding to

the search criteria" appears.
Page 232 of 474

be the designation or a specific
comment for authoring purposes.
4. Click the
6. Click "OK".
Page 233 of 474
A "WellFormatted" mention appears in the tag.
Page 234 of 474
2. In the "Optional placeholder

information" field, give a short
description of the maintenance
deactivation linked to this task.
1. Click the
Page 235 of 474
tag.
Page 236 of 474
8.12.22 MMEL Tag "mmelRef"-A380 context
ASR ASR
You can insert an MMEL reference using the <mmelRef > tag in the "Reason for the job" paragraph.
key.

tag.
Page 237 of 474
3. Press "Enter".
4. Select the "mmelRef"

tag.
Page 238 of 474
5. Fill in the "MMEL Reference" field in accordance with the MP Authoring rules
(Maintenance Procedure related to MMEL requirements).
 Fill in the "DispatchCondID" field (format: D12345) or enter an asterisk.
 Fill in the "Function_Code" field. Enter at least the first two digits (26*).
7. Select the requested MMEL reference.

button.
8. Click "OK".
Page 239 of 474
To insert placeholder, refer to chapter 8.12.21.1 Insert Placeholder.
Page 240 of 474
8.12.23 Fastener Tag: "refFastener"
ASR ASR
N/A N/A N/A N/A N/A N/A X N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
The Fastener database Admin will add the approved Excel file in DACAS: Ref. UG1500229.6 DACAS (SAP iPPE Module) for ASR product.
You can insert a reference to a fastener (Excel file) using the <refFastener > tag.
1. Put the cursor in a paragraph and press the "Enter"

key.
2. Select the "refFastener"

tag.
Page 241 of 474
Important information: When a new version of the Fastener database is inserted by the Fastener Admin, there is no need to update your description.
The last version is automatically taken into account for the next Customer Data revision.
8.12.24 PDRS Tag: refPdrs

ASR ASR
N/A N/A N/A N/A N/A N/A X X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
Important information: No PDRS for contractual revision of September 2014
The PDRS Admin will add the PDRS PDF file in DACAS: Ref. UG1500229.6 DACAS (SAP IPPE Module) for ASR product.
You can insert a cross-reference to a fastener using the <refPdrs > tag.
Page 242 of 474

key.
2. Select the "refPdrs"

tag.
Page 243 of 474

 Fill in the "Description" field (format
PDRS_XXX). If the Description is not fully
known, enter an asterisk.

button.
5. Select the requested panel.
6. Click "OK".
Page 244 of 474
Important information: When a new version of PDRS is inserted by the PDRS Admin, there is no need to update your description/task.
The last version will be automatically taken into account for the next Customer Data Production.
Page 245 of 474
8.12.25 Reference to Subtasks Tag: “refSubtask”
ASR ASR
N/A N/A N/A N/A N/A N/A X X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
It is possible to reference a subtask in the repair domain with a “refSubtask” tag.
The possibility to reference a subtask is restricted to the type of tasks with function code 660.
2. Select the "refSubtask"

tag.

key.
Page 246 of 474
3. Fill in the search criteria.
6. Click "OK".
Page 247 of 474
Page 248 of 474
8.13 To Insert a Panel or Door Tag: "access"
ASR ASR
N/A X X N/A N/A N/A N/A X X N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert references for a panel or a door using the <access> tag.

key.
2. Select the "access"

tag.
Page 249 of 474
For A350 only

 Fill in the "IDRef" field (format 123ABC). If the IDRef is not
fully known, enter at least the first digit followed by an
asterisk (e.g. 1*).
 Select the "Type" (PANEL or DOOR).

button.
6. Click "OK".
Page 250 of 474
For A380
 If the Panel is fully known, fill in the "Panel From" field with
the full name (format 123AB).and the "Panel From" field
with an asterisk
 If the Panel is not fully known, enter at least the first three
digits followed by an asterisk (e.g. "Panel From" 121* and
"Panel To" 122*)
6. Click "OK".
Page 251 of 474
8.13.1 Insert Placeholder (only for A350)

8.13.1.1 "Well formatted" Placeholder
If the author knows the reference number to be tagged, but the data is not yet available in the ZAPDIS database, the system will propose a well
When the author does not know the door or panel that provides access to the working area, he must use a “Not Well formatted” placeholder.
The placeholder must be replaced by the real data before doing the self-check.
Page 252 of 474
2. In the "Optional placeholder information" field, give the

information of the zone that provides access to the
working area.
1. Click the 3. Click "Ok"

Result in Arbortext A "notWellFormatted" mention appears in the tag.
Page 253 of 474
8.14 To Insert Consumable Tags
A consumable is an item found in the Consumable Material List (CML) with an application code or material code.
A general consumable is an item which is not included in the CML (e.g. cotton lint free (rag), safety goggles, gloves, etc.). This general consumable
is managed by a Tech Data Administrator.
8.14.1 Consumable Tag: "consumable"

ASR ASR
N/A X X X X X N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a reference for consumable using the <consumable > tag.
key.
2. Select the "consumable"

tag.
Page 254 of 474

 Fill in the "Application Code" field (format:
08ABC1).
If the Application Code is not fully known,
enter the first digits followed by an asterisk
(e.g. 08A*) (not mandatory).
To retrieve the application code, refer to
4. Click the "Search" TDG0208.1 Aircraft Maintenance
button. Procedure (MP) Authoring.
 Fill in the "Specification" field (not
mandatory).
5. Select the requested consumable.
6. Click "OK".
Page 255 of 474
Page 256 of 474
If the data is not available, the system will only propose a "Not Well formatted" placeholder.
8.14.1.1.1 "Not well formatted" Placeholder
Page 257 of 474
2. In the "Optional placeholder information"

field, give the material name.
Aqueous Cleaner
3. Click "OK"
1. Click the
Page 258 of 474
Result in Arbortext: A "notWellFormatted" mention appears in the tag.
Page 259 of 474
8.14.2 To Insert a Consumable in a Note Tag: "nConsumable"
ASR ASR
This tag must be used in a note only.
In the final product (AirN@v), this data:

 will be transformed into text (no hyperlink),
 will not appear in the Job Set-Up Information,
 will not be shown in the favorites,
 will not appear in query 10.
Nevertheless, it will be automatically maintained if updated in the CML database.
The process is similar to the one for the “Consumable” tag. For more details, refer to paragraph 8.14.1 Consumable Tag: "consumable".
Page 260 of 474
8.14.3 General Consumable Tag: "generalConsumable"
ASR ASR
N/A X X X X X N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a general consumable using the <generalConsumable > tag.

key.
2. Select the
"generalConsumable" tag.
Page 261 of 474
3. Search criteria:
 The "Identifier" field is filled by default: CONS* (format:
CONSXXXXX). If the Identifier is not fully known, enter
the CONS*).
 "Designation" field (not mandatory).
5. Select the requested consumable.
6. Click "OK".
Page 262 of 474
Page 263 of 474
If the data is not available, the system will only propose a "Not Well formatted" placeholder.
Page 264 of 474

give the description of the material.
Sandpaper
1. Click the
"Placeholder" button. 3. Click "OK".
A "notWellFormatted" mention appears in the tag.
Page 265 of 474
8.14.4 To Insert a General Consumable in a Note Tag: "nGeneralConsumable"
ASR ASR

The process is similar to the one for the "General consumable" tag. For more details, refer to paragraph 8.14.3 General Consumable Tag:
"generalConsumable".
Page 266 of 474
8.14.5 Engine Consumable Tag: "engConsumable"
ASR ASR
N/A X N/A N/A N/A N/A N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a reference for an engine consumable using the <engConsumable > tag.
Note: In the final product, the engine consumable will appear in the consumable material list of the “Job Set-Up Information” paragraph.

key.
2. Select the "engConsumable"

tag.
Page 267 of 474
3. Enter the code manually.
4. Put the cursor after the code delimiter and press the "Enter"
key.
5. Select "name".
Page 268 of 474
6. Enter the name manually.
Note for A350 only TBC: The Engine Consumables are not in the CML, they are in a specific table in the AM task P_708000_398_00_0001_T.
Example in AirN@v:
In the “Job Set-Up Information” paragraph :
In the text of the procedure:
Page 269 of 474
8.14.6 Vendor Consumable Tag: "vendorConsumable"
ASR ASR
N/A X N/A N/A N/A N/A N/A X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a reference for vendor consumable using the <vendorConsumable > tag.
key.
2. Select the "vendorConsumable"

tag.
Page 270 of 474
3. Enter the code manually.
4. Put the cursor after the code delimiter and press

the "Enter" key.
5. Select "name".
6. Enter the name manually.
Page 271 of 474
7. Put the cursor after the name delimiter and press the
"Enter" key.
8. Select "manufacturerCode".
9. Enter the Manufacturer code

manually.
Page 272 of 474
8.15 To Insert Circuit Breaker Tags
To tag a circuit breaker, there are three possibilities:
 In the procedure, ins the cbOpen and cbClose tags.
 In subtask 865, in the CB table.
 In the DU5 for A380.
8.15.1 Circuit Breaker Tags in the Procedure
8.15.1.1 Circuit Breaker Tag: "cbOpen"

ASR ASR
N/A X X N/A N/A N/A N/A N/A X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
This tag is used when a CB must be opened in the procedure.
The text Open CB is automatically generated by DACAS.
Page 273 of 474

key.
2. Select the "cbOpen"

tag.
Page 274 of 474
3. Put the cursor after "Open CB" and press the "Enter" key.
Then, insert the "cb" tag. Refer to paragraph 8.15.3 Circuit Breaker
Tag: "cb".
8.15.1.2 Circuit Breaker Tag: "cbClose"

ASR ASR
This tag is used when a CB must be closed in the procedure.
The text Close CB is automatically generated by DACAS.
Use the same process as for the "cbOpen" tag. Refer to paragraph 8.15.1.1 Circuit Breaker Tag: "cbOpen".
Page 275 of 474
8.15.2 Circuit Breaker Tags in a C/B Table (Subtask 865)
ASR ASR
At first, you must create a subtask 865 or 875. Refer to paragraph 6.3.1 To Create a Subtask Tag: "subtinv".
The circuit breaker table header appears automatically.
Then insert the corresponding typical sentence: refer to para. 8.6 To Insert a Typical Sentence Tag: "ts".
Example:
Page 276 of 474
There are two possibilities:
1. Insert a list of circuit breakers applicable to the whole task but not to a specific item of equipment (cbsublist).
2. Insert a list of circuit breakers only applicable to a specific item of equipment (FIN) of the task (cbforfinlist).
8.15.2.1 To Insert a List of Circuit Breakers for all Equipment Tag: "cbsublist"
1. Put the cursor before the "cblist" tag delimiter and press the
"Enter" key.
2. Select the "cbsublist"

tag.
Page 277 of 474
3. Press the "Enter"

key.
4. Select the "cb"

tag.
To insert a "cb" tag, refer to paragraph 8.15.3 Circuit Breaker Tag: "cb".
Page 278 of 474
Result:
Page 279 of 474
8.15.2.2 To Insert a List of Circuit Breakers Applicable to One Specific Item of Equipment Tag: "cbforfinlist"
1. Put the cursor before the "cblist" tag delimiter and press the
"Enter" key.
2. Select the "cbforfinlist"

tag.
Following step:
3. Put the cursor after "FOR" and

4. Click the "fin"

tag.
To insert a FIN, refer to paragraph 8.9.1 To Insert a FIN.
Page 280 of 474
5. Put the cursor between the "cbsublist" tag delimiters
and press the "Enter" key.
6. Select the "cb"

tag.
To insert a "cb" tag, refer to paragraph 8.15.3 Circuit Breaker Tag: "cb".
Result:
Page 281 of 474
PDF preview example :
tag: "cbsublist"
tag: "cbforfinlist"
Page 282 of 474
8.15.3 Circuit Breaker Tag: "cb"
ASR ASR
The circuit breaker tag "cb" is used to define the circuit breaker with its FIN.
Example of "cb" tag used after an “Open CB” tag:
1. Put the cursor after "Open CB" and press the "Enter"
key.
2. Select the "cb"

tag.
Page 283 of 474

 Fill in the "FIN Prefix" field or enter an asterisk.
 Fill in the "FIN Circuit Letter" field (mandatory).
 Fill in the "FIN Suffix" field or enter an asterisk.
 Fill in the "FIN Appended Letter" field or enter an
asterisk.
 Fill in the "FIN Supplementary Part" field or enter an
asterisk.
 Select the "CB Type" (SSPC, C/B or RCCB) or
select the asterisk.
 Fill in the "Panel" field or enter an asterisk.
 Fill in the "ATA" field or enter an asterisk.
5. Select the requested circuit breaker.
6. Click "OK".
Page 284 of 474
Similar to the FIN placeholder (refer to paragraph 8.9.1.1 Insert Placeholder)
8.15.4 To insert a List of Circuit Breakers: “autocbsublist”-A380 context

ASR ASR
N/A N/A N/A N/A N/A N/A N/A N/A N/A X N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
At first, you must create a DU05, refer to paragraph Description 6.1Description Sub-Element with Configuration Management:
Page 285 of 474
1. Put the cursor in a DU5 paragraph and press the "Enter" key.
2. Select the "cblist" tag.
The circuit breaker table header appears automatically:
Page 286 of 474
3. Put the cursor in between the “cblist” tags and press the “Enter” key.
Page 287 of 474
4. Select the “cbsublist” tag to create a list of circuit breakers in a table (refer to paragraph 8.15.2.1 To
Insert a List of Circuit Breakers for all Equipment Tag: "cbsublist" for details.)
5. Or select the “autocbsublst” tag to create an automatic list of

CBs.
Page 288 of 474
NOTE: At this stage, the authoring of UD5 is finished for the “autocbsublst” tag. The system will implement the dedicated list of CBs later on, during the
production phase (DALI).
Page 289 of 474
8.15.5 To insert an SSPC tag: “SSPC”-A380 concept
ASR ASR
You can insert an SSPC table in the AMM task: “240000-860-802 Isolate the Systems when no Electrical Power is available”, using the <SSPC>
tag.
1. Put the cursor in a title just before the triangle and press the "Enter"
key.
2. Select the "SSPC"

tag.
Page 290 of 474
Note: The system will implement the dedicated list of CBs later on, during the production phase (DALI).
Page 291 of 474
8.16 To Insert Torque Value Tags
ASR ASR
8.16.1 Specific Torque Value Tag: "tor"

The <tor> tag is used for a specific torque value mainly obtained from Design Office documents (drawings).
2. Select the "tor"

tag.
Page 292 of 474
A. Torque value panel for A350 aircraft program:
3. Select the requested "Unit From".
4. Select the requested "Unit To".

It is not possible to put the same unit in “Unit From”
and in “Unit To”.
5. Fill in the "Min" and "Max" fields as required:

 For an exact value, fill in the "Min" and “Max”
fields with the same value.
 For a range of values, fill in the "Min" and "Max"
fields.
6. Fill in the decimal place after the comma as required.
7. Click "OK".
Page 293 of 474
B. Torque value panel for A380 aircraft program:
3. Select the requested "Unit From".
4. Fill in the "Min" and "Max" fields as

required:
 For an exact value, fill in the
"Min" and “Max” fields with the
same value.
 For a range of values, fill in the
"Min" and "Max” fields.
5. Fill in the decimal place after the comma

as required.
6. Fill in the sources:
 Type of document
 Reference
 AWO
 Verified (Y/N)
7. Click "OK".
Page 294 of 474
Note: The entered source elements will be contained in the tag:
8.16.2 Standard Torque Value Tag: "tors"

The "tors" tag is used for a standard torque value. The value is not found in Design Office documents (drawings) and is calculated by the author.
Use the same process as for the "tor" tag. Refer to paragraph. 8.16.1 Specific Torque Value Tag: "tor".
Page 295 of 474
8.16.3 To Modify Torque Value Data
Modify the torque value data using the "modify torque data" function in the Arbortext menu.
1. Select the "tor/tors" tag (including the tags).
Page 296 of 474
2. In the "DACAS" menu, select "Modify Torque Data".
The "Torque Value" window appears:
3. Modify the data as required.
Page 297 of 474
The torque values have been modified:
Page 298 of 474
8.17 To Insert Tool Tags
There are two categories of tools:
 The standard tools are not Airbus-specific and have no part number. The operator can buy these tools "off the shelf".
 The specific tools are required by Airbus. The operator must only use these tools during the maintenance procedure.
Both categories are managed in a dedicated database called "MADAME".
For additional information, refer to TDG208.1 Aircraft Maintenance (MP) Authoring.
Page 299 of 474
8.17.1 Standard Tool Tag: "stdTool"
ASR ASR
N/A X X N/A X X N/A X X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a standard tool using the <stdTool> tag.

key
2. Select the "stdTool"

tag.
Page 300 of 474
A. Search data for A350 Aircraft program:
 Fill in the "Reference" field (the format is 15 digits:
STT1234…12).
If the reference is not fully known, enter the first characters
followed by an asterisk (STT00001*).
 Fill in the "Content" field (Designation of the tool, not
mandatory).
 Fill in the "Group" field (Material Group, not mandatory).
5. Select the requested standard tool.
6. Click "OK".
Page 301 of 474
Result in Arborext:
Result in AirN@v :
By using the Standard Tool tag, the "No Specific" mention will be displayed in the "REFERENCE" column of the Tool list in AirN@v:
Page 302 of 474
B. Search data for A380 Aircraft program:
 Fill in the "Reference" field (the format is 15 numerical digits:
STT1234…12).
If the reference is not fully known, enter the first characters
followed by an asterisk (STT00001*).
 Fill in the "Content" field (Designation of the tool, not
mandatory).
 Fill in the "Group" field (Material Group, not mandatory).
6. Double-click inside the Quantity column

5. Select the requested standard tool.
and enter the required tool quantity or AR.
7. Click "OK".
Page 303 of 474
Result in Arborext:
If the author knows the reference number to be tagged, but the data is not yet available in the tool database, the system wil l propose a well formatted
placeholder.
Page 304 of 474
1. Enter the Standard Tool reference.

button.
3. A pop-up "No result corresponding to the

search criteria" appears.
Page 305 of 474
4. Click the "Placeholder"

button.
5. Enter the comment if needed. It can be the
designation or a specific comment for authoring
purposes.
6. Click "OK".
A "WellFormatted"
tag.
Page 306 of 474

give the designation of the tool.
Multimeter
1. Click the 3. Click "OK"

Page 307 of 474
8.17.2 To Insert a Standard Tool in a Note: "nStdTool"
ASR ASR
X X X N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD

Nevertheless, it will be automatically maintained if updated in the tool database.
The process is similar to the one for the “Standard Tool” tag. For more details, refer to paragraph 8.14.1 Consumable Tag: "consumable".
Page 308 of 474
8.17.3 Specific Tool Tag: "specificTool"
ASR ASR
You can insert a specific tool using the <specificTool> tag.

key.
2. Select the "specificTool"

tag.
Page 309 of 474
A. Search data for A350 Aircraft program:

 Fill in the "Reference" field (no specific format).
If the reference is not fully known, enter the first characters followed
by an asterisk (11*).
 Fill in the "Content" field (Designation of the tool, not mandatory)
 Fill in the "Group" field (Material Group of the tool, not mandatory).
5. Select the requested specific tool.
6. Click "OK".
Page 310 of 474
Result in AirN@v:
By using the “Specific tool” tag, the Part Number of the tool will be displayed in the "REFERENCE" column of the Tool list in AirN@v:
Page 311 of 474
B. Search data for A380 Aircraft program:

 Fill in the "Reference" field (no specific format).
If the reference is not fully known, enter the first characters followed
by an asterisk (98L7110H*).
 Fill in the "Content" field (Designation of the tool, not mandatory)
 Fill in the "Group" field (Material Group of the tool, not mandatory).
6. Double-click inside the Quantity column

5. Select the requested specific tool.
and enter the required tool quantity or AR.
7. Click "OK".
Page 312 of 474
If the author knows the reference number to be tagged, but the data is not yet available in the tool database, the system will propose a well formatted
placeholder.
Page 313 of 474
1. Enter the Specific Tool reference.

button.
3. A pop-up "No result corresponding to the

search criteria" appears.
Note: As there is no specific format for the specific tool reference, make sure that the entered reference is an existing reference (MADAME, TEM, etc.)
and keep the same structure (underscore, dash, etc.).
Page 314 of 474
4. Click the

purposes.
6. Click "OK".
A "WellFormatted"
tag.
Page 315 of 474
2. In the "Optional placeholder information"

field, give the designation of the tool.
Guide cone
3. Click "OK"
1. Click the
Page 316 of 474
Page 317 of 474
8.17.4 To Insert a Specific Tool in a Note: "nSpecificTool"
ASR ASR
X X X N/A N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD

The process is similar to the one for the “Specific Tool” tag. For more details, refer to paragraph 8.14.1 Consumable Tag: "consumable".
Page 318 of 474
8.17.5 Interchangeable Tools Tag: "interchTools"
ASR ASR
You can insert an interchangeable tool using the <interchTools> tag.
It is not possible to insert an "interchTools" tag mixing Standard tools and Specific tools.
Once the "interchTools" tag is inserted, the process is similar to the one for the “specific tools” tag and for the “standard tools” tag.
This table will appear automatically in AirN@v in the “Job Set-up Information” paragraph:
2. Job Set-up Information:
A. Fixtures, Tools Test and Support Equipment.

Reference Qty Designation
No Specific 1 ACCESS PLATFORM 8M (26 FT)
or
No Specific 1 ACCESS PLATFORM 8M (26 FT) (Adjustable)
Page 319 of 474

key.
2. Select the "interchgTools"

tag.

key.
4. Select "specificTool" or "stdTool" as required.
A. Insert the first tool by means of the search data panels, described in chapters 8.17.1 Standard Tool Tag: "stdTool" or 8.17.3 Specific Tool Tag:
"specificTool". In that example, a standard tool is chosen.
Page 320 of 474
4. The cursor must be located before the last "interchgTools" tag delimiter. Press the "Enter" key.
5. Select "stdTool".
B. Insert the interchangeable tool by means of the search data panels, described in chapters 8.17.1 Standard Tool Tag: "stdTool" or 8.17.3
Specific Tool Tag: "specificTool".
Result in Arbortext (A350 example):
Page 321 of 474
Result in Arbortext (A380 example):

Similar to the Standard Tool or Specific Tool placeholder (refer to paragraphs 8.17.1.1 Insert Placeholder and 8.17.3.1 Insert Placeholder)
Page 322 of 474
8.17.6 COC Tool Tag: "cocTool"-A380 context
ASR ASR
N/A N/A N/A N/A N/A N/A N/A N/A X N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a standard tool using the <cocTool> tag.

key
2. Select the "cocTool”

tag.
Page 323 of 474
3. Press the "Enter" key again.
4. Select the "ref” tag.
5. Enter the reference of the COC tool.
6. Enter the designation of the COC tool.
Page 324 of 474
To enter/modify the tool quantity:
1. Put the cursor just after the first tag of the “cocTool” tag and press the “Enter” key.
2. Press the icon below, located in the menu bar:
Page 325 of 474
3. A “Modify Attributes” pop-up opens. In the “qty” field, enter the required tool quantity or AR.
4. Press the “OK”

button
The quantity value appears inside the first tag.
Page 326 of 474
8.18 To Insert Expendable Tag: "expd"-A350 context
ASR ASR
You can insert expendable parts using the <expd> tag.
Important information: This tag is not to be used for Vendor CSN.
Complete these two steps to insert an expendable:

A. Create a subtask "999-EXPENDABLES". The expendable table in the "Job Set-Up" paragraph will appear automatically.
Note: Subtask "999-EXPENDABLES" is authorized for:

 MP02 Maintenance Practices
 MP03 Servicing
 MP04 Removal/Installation (LRU)
 MP05 Adjustment/Test
 MP06 Inspection/Check
 MP07 Cleaning and Painting
 MP14 Removal/Installation (LRI)
B. Link an expendable item in the "Procedure" paragraph.
A. Create a "999-EXPANDABLE" subtask in the "Job Set-Up" paragraph:
Refer to paragraph 6.3.1 To Create a Subtask Tag: "subtinv".
Page 327 of 474
2. Click the "expd"

tag.
1. Put the cursor in the first column/

second row and press the "Enter" key.
Page 328 of 474

 Fill in the "Figure-Item" field: Format: NNNNNNDD_DDD.
NNNNNN: 6 numerical values corresponding to the
CHSESU.
DD: 2 numerical values corresponding to the figure
number (from IPD CSN).
Then, enter an underscore.
DDD: 3 numerical values corresponding to the item
number (from IPD CSN).
If the Figure-Item is not fully known, enter the first digits
4. Click the "Search" button. followed by an asterisk (321274*).
5. Select the requested expendable.
6. Click "OK".
7. Fill in the Item number (in free text).
Page 329 of 474
8.18.1 Insert Placeholder
The format to tag a well-formatted placeholder is: CHSESU12-123
12: figure number (two digits).
123: item number of the IPD CSN (three digits).
Provide as many significant digits as you can.
Complete the unknown digit(s) with the number "9".
Use the "comments" field to give information on the targeted expendable.
In the same task, you must change the sequence number each time you tag a new expendable. In this cas e, decrease the last digit.
Example:
 32127499-999 with comment
Note: In that example, the Figure number and the Item number are not known.
Page 330 of 474
1. Fill in the "Figure-Item" field in

the correct format.
3. Enter the comment if needed. It can be

the designation or a specific comment for
authoring purposes. This information will
not appear in the final product.
4. Click "OK".
2. Click the "PlaceHolder"

button.
Page 331 of 474
The "Not Well formatted" placeholder must not be used.
Page 332 of 474
B. Link an expendable item in the "Procedure" paragraph:
When you mention an expendable item in the procedure paragraph, you must use the <expdItem> tag to link it to the "Expendable Parts"
table.
1. Put the cursor in a subtask of the “Procedure” paragraph and press the "Enter"
key.
2. Select the "expdItem"

tag.
3. Select the applicable item.

4. Click "OK".
Page 333 of 474
To insert the second item, redo steps 1 to 4:
Page 334 of 474
8.19 To Insert Expendable Tag: "expd"-A380 context
ASR ASR
You can insert expendable parts using the <expd> tag.
1. Put the cursor in the paragraph and press the "Enter" key.
2. Select the “expd” tag.
Page 335 of 474

 Fill in the "Figure-Item" field (IPC Figure Item):
The format is: NNNNNNDD_DDD, where:
 NNNNNN is 6 numerical values corresponding to the
CHSESU.
 DD is 2 numerical values corresponding to the figure
number (from IPC CSN).
Then, enter an underscore.
 DDD is 3 numerical values corresponding to the item
number (from IPC CSN).
4. Click the "Search" button. Note: If the Figure-Item is not fully known, enter the first digits
followed by an asterisk (for example: 321274*).
5. Select the requested expendable.
6. Double-click inside the related Item_Number

cell and enter the Item number of the AMM
illustration.
7. Click "OK".
Page 336 of 474

The format to tag a well-formatted placeholder is CHSESU12-123, where 12 is the figure number (two digits) and 123 is the item number of the
IPD CSN (three digits).
If the IPC Figure Item is known, fill in the field as explained above.
If the IPC figure Item is not known, provide as many significant digits as you can and complete the unknown digit(s) with the number "9".
Use the "comments" field to give information on the targeted expendable.
If in the same task, you must change the sequence number each time you tag a new expendable, decrease the last digit:
Page 337 of 474
Example:
Note: In that example, the Figure number and the Item number are not known.
Page 338 of 474
1. Fill in the "Figure-Item" field in the correct format.

Warning: use a hyphen between the CSN and the
Item number.
3. Enter the Item number in the AMM illustration.

purposes. This information will not appear in the
final product. The “To be defined” mention will
appear automatically if the field is left blank.
5. Click "OK".
2. Click the "PlaceHolder"

button.
Page 339 of 474
The "Not Well formatted" placeholder must not be used.
Page 340 of 474
8.20 To Insert Expendable Tag: "expEngine"-A380 context
ASR ASR
You can insert expendable parts for A380 and A318 PW6000 engines only, using the <expEngine> tag.
The tag mechanism to be used is similar to the “expCoc” tag. Refer to chapter 8.22 To Insert an Expendable COC Tag: "expdCoc" for details.
Page 341 of 474
8.21 To Insert an Expendable Vendor Tag: "expdVendor"
ASR ASR
You can insert an expendable using the <expdVendor> tag.
Expendables from the supplier contribution (xml file) are converted into the DACAS format using the "expdVendor" tag.
The "expdVendor" tag is also used in an Airbus procedure to tag an expendable not belonging to the IPD DM. In that case, the reference will be
the IPD Vendor DM.
Note: In the final product, the vendor CSN will appear in the “Job Set-Up Information” paragraph in the "Expendable Parts" table.
1. Put the cursor in the paragraph and press the "Enter"

key.
2. Select the "expdVendor"

tag.
Page 342 of 474

key.
4. Select "catalogSeqNumberRef".
Page 343 of 474
An "Insert data" window opens:
5. "modelIdentCode": Enter the Vendor Reference (for example:
"TRENTXWB" for Rolls Royce Trent XWB Engine).
"systemDiffCode": Enter A.
"systemCode": Enter the Chapter.
"subSystemCode": Enter the first digit of the section.

"subSubSystemCode": Enter the second digit of the section.
"assyCode": Enter the Subject.
"figureNumber": Enter the IPD figure number.
"itemLocationCode": Enter A.
"item": Enter the IPD item number invariant.
6. Click "Insert". "itemSeqNumberValue": Enter the item number variant (start with
000, then 00A, 00B, 00C, etc.).
Page 344 of 474
7. Put the cursor before the last delimiter of the "expdVendor" tag and press the "Enter" key.
8. Select "designation" or "item":

If the "designation" tag is selected, the "item" tag will be inserted by default. If only the "item"
tag is selected, no designation will be inserted.
Page 345 of 474
9. Enter the designation and the item number in free text.
Page 346 of 474
8.22 To Insert an Expendable COC Tag: "expdCoc"-A380 context
ASR ASR
You can insert a COC expendable using the <expdCoc> tag.
1. Put the cursor in the paragraph and press the "Enter"

key.
2. Select the "expdCoc"

tag.
Page 347 of 474
3. Press the “Enter” key again.
4. Select the “ref” tag.
Page 348 of 474
5. Enter the CSN and item variants.
6. Enter the Designation. 7. Enter the item number in the AMM

illustration.
Page 349 of 474
8.23 To Insert a Required Condition Tag: "reqCondition"
ASR ASR
Use the "ReqCond" tag to insert the required condition(s) in the Job-Set-Up or Close-Up paragraphs for the AFI.
1. Put the cursor between the triangle delimiters and press the "Enter" key.
2. Select the "reqConditionList" tag.
Page 350 of 474
3. Put the cursor between the reqConditionList tags and press the "Enter" key.
4. Select the "reqCondition"

tag.
Due to the S1000D data structure constraints, it is not permitted to have a reference to a Data Module inside a <reqCond> in an AFI subt ask (for
fault confirmation or fault isolation tasks).
This can happen when a Typical Sentence (TS) containing a reference to a DM (e.g. ST00054) has been tagged inside a <reqCond>.
If such typical sentence in AFI4s subtasks is mandatory:

 ask for a new typical sentence without the Data Module reference
 and then, add the reference to the Data Module outside of the <reqCond> tag.
This is only applicable to the AFI4s "Subtasks".
Page 351 of 474
8.24 To Insert an Action Tag: "action"
ASR ASR
You can insert an action in a "Procedure" paragraph of an AFI task using the <action> tag.
At first, a step structure for Fault Confirmation or Fault Isolation must be created. Ref. Para. 6.3.2 To Create a Step Structure for Fault Confirmation
(FC)/Fault Isolation (FI)
1. Put the cursor in a stepBlock and press the "Enter"
key.
2. Select the "action"

tag.
Page 352 of 474
8.25 To Insert a List of Choices Tag: "ListOfChoices"

ASR ASR
You can insert a <ListOfChoices> tag in a "Procedure" paragraph of an AFI task.
Use <ListOfChoices> tag to link a step to another one (without question).
Page 353 of 474
1. Put the cursor after the "action" tag delimiter and press the "Enter" key.
2. Select the "stepAnswer"

tag.
Page 354 of 474

key.
4. Select the "listOfChoices"

tag.

key.
6. Select the "choice" tag.
Page 355 of 474
A search panel appears:
7. Select the step and click "OK".
Result in Arbortext: The "Go To" link is automatically written with the reference of the selected step.
Page 356 of 474
8.26 To Insert Question/Answer Tags: "stepQuestion" and "stepAnswer"
ASR ASR
Use this tag to create a “step question” and a “step answer” in a "Procedure" paragraph of an AFI task.
1. Put the cursor after the "action" tag and press the "Enter"
key.
2. Select the "stepQuestion"

tag.
Page 357 of 474
3. Write the question in free text inside the "stepQuestion" tag.
4. Put the cursor after "stepQuestion" tag and press the "Enter"
key.
5. Select the "stepAnswer"

tag.
Page 358 of 474

key.
7. Select the "yesNoAnswer"

tag
8. Press the "Enter" key and select the "yesAnswer"

tag.
9. Select the "yesAnswer"

tag.
Page 359 of 474
10. Select the required step and click "OK".
Result in Arbortext: The "Yes" condition is automatically written with the reference of the selected step.
Page 360 of 474
Continue with the "No" answer:
11. Put the cursor before the last tag delimiter and press the "Enter" key.
12. Select the "noAnswer"

tag.
Page 361 of 474
13. Select the required step for the No answer (Final step in that example) and click OK.
Result in Arbortext: The "No" condition is automatically written with the reference of the selected step.
Page 362 of 474
8.27 To Insert a Line Replaceable Unit Tag: "lru"
ASR ASR
You can insert an LRU using the <lru> tag.
You must insert an <lru> tag in a "Procedure" paragraph and inside an action.
Use the <lru> tag to identify the faulty LRU.
Page 363 of 474
1. Put the cursor in an "action" tag and press the "Enter" key.
2. Select the "LRU"

tag.
To insert an LRU FIN, ref. paragraph 8.9.1 To Insert a FIN
Page 364 of 474
Similar to the FIN place holder, ref. paragraph 8.9.1.1 Insert Placeholder.
8.28 To Insert a Non Line Replaceable Unit tag: "nlru"

ASR ASR
SD MP FI TS SPD SPP Description Procedure MP SD TP TO MP SD TP TO MP SD TP TO
You can insert an NLRU using the <nlru> tag.
You must insert an <nlru> tag in a "Procedure" paragraph and inside an <action>.
Use the <NLRU> tag to identify the faulty NLRU.
Page 365 of 474
1. Put the cursor in an "action" tag and press the "Enter" key.
2. Select the "NLRU"

tag.
Result in Arbortext: 3. Enter the faulty NLRU in free text.
Page 366 of 474
8.29 To Insert a Fault Wire Tag: "faultwire"-A350 concept
ASR ASR
You can insert a fault wire using the <faultwire> tag.
You must insert a <faultwire> tag in a "Procedure" paragraph.
Use the <faultWire> tag to identify the extremities of the faulty wire (from a point to another point).
There are two possibilities to identify wire extremities:

 In free text
 With the connector FIN.
Note: Additional elements of the connector can be inserted manually in the "From/To" table, as the "Module-DPX" and the "PIN".
Depending on the type of connector, the way to fill in the "From/To" table may differ. For more details, ref. TDG0209.1 "AFI Authoring".
Page 367 of 474
1. Put the cursor after the "action" tag delimiter and press the "Enter" key.
2. Select the "faultWire"

tag.
Page 368 of 474
3. Put the cursor in the first row of the " From" column and press the "Enter"
key.
4. Select either the "textualWire" or the "wire" tag (the wire is selected in the
example):
 Use "TextualWire" for free text.
 Use "wire" to define the FIN of the connector.
Page 369 of 474
5. Put the cursor in the first row of the "Connector" column and press the "Enter"
key.
6. Select the "fin"

tag.
To insert a FIN, ref. paragraph 8.9.1 To Insert a FIN.
Page 370 of 474
6. Select either the "textualWire" or the "wire" tag:

Page 371 of 474
7. Put the cursor in the first row of the "Connector" column and press the "Enter" key.
8. Select the "fin"

tag.
Page 372 of 474
9. Put the cursor in the requested cell, and fill in the Module-DPX and PIN columns in free text as required.
Result:
If an additional wire is requested:
Page 373 of 474
Important information: Enter only one wire per line.
1. Select the entire row and right click.
2. Insert a row Below.
Page 374 of 474
In the new row, repeat the steps from 3 to 9 to insert an additional fault wire.
Page 375 of 474
Placeholder is applicable to the FIN connectors only. Ref. paragraph 8.9.1.1 Insert Placeholder.
8.30 To Insert a Fault Wire Tag: "faultwire"-A380 concept

N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert a fault wire using the <faultwire> tag.
Use the <faultWire> tag to identify the extremities of the faulty wire (from a point to another point).
There are two possibilities to identify wire extremities:

 In free text
 With the connector FIN.
Page 376 of 474
1. Put the cursor in the text and press the "Enter" key.
2. Select the "faultWire"

tag.
Page 377 of 474
A “Modify Attributes” pop-up window opens:
4. Press OK.
3. Enter “ to the “ in the lnktxt field.

Note: Leave a blank space before and after
that text.
5. Put the cursor in the text and press the "Enter" key.
6. Select either the "textualWire" or the "wire" tag (the wire is selected in the
example):
Page 378 of 474
7. Put the cursor between the “wrg” and the “pin” delimiters and press the "Enter"
key.
8. Select the "fin"

tag.
9. Put the cursor between the “fin” and the “pin” delimiters and press the "Enter"
key.
10. Select the "module"

tag.
Page 379 of 474
11. Enter the module and the pin in free text.
Repeat the same operation for the “faultWire To”.
Page 380 of 474
8.31 To Insert a Wire Extremities tag: "wrg"
ASR ASR
N/A N/A X N/A N/A N/A N/A N/A N/A N/A X N/A TBD TBD TBD TBD TBD TBD TBD TBD
You can insert wire extremities using the <wrg> tag.
Page 381 of 474
1. Put the cursor inside an "action" tag and press the "Enter" key.
2. Select the "wrg"

tag.
3. Put the cursor between the first "wrg" tag and the first "pin" tag and
4. Select the "fin"

tag.
Page 382 of 474
5. Put the cursor between the last "fin" delimiter and the first "pin" delimiter
and press the "Enter" key.
6. If necessary, select the "module"

tag.
7. Enter the module identifier in free text. 8. Put the cursor after "pin" and enter the pin identifier in free text.
Page 383 of 474
Repeat steps 1 to 8 for the second extremity:
Remark: For the second extremity (Electrical connector), no module has been selected.

The placeholder is applicable to the FIN connectors only. Ref. paragraph 8.9.1.1 Insert Placeholder.
Page 384 of 474
8.32 To Insert Superscript and Subscript Tags: "superScript" and "subScript"
ASR ASR
X X X X N/A N/A N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
Insert <superScript> element (exponent)
Insert <subScript> element (indice)
<SuperScript> and <SubScript> elements are used for formatting purpose.
Page 385 of 474
8.33 To Insert a Software Component Tag: "sw"

Use the <sw>tag to insert a software component. Then, insert a <fin> tag, and select a FIN through the FIN search panel.
Page 386 of 474
2. Select the "sw"

tag.
Page 387 of 474
2. Select the "fin"

tag.
Page 388 of 474

The placeholder is applicable to the FIN connectors only. Ref. paragraph 8.9.1.1 Insert Placeholder.
Page 389 of 474
8.34 To Insert On-Board Link Tags
The purpose of these tags is to enable links between Aircraft Documentation System (ADS) and A350 On -Board Systems (cockpit).
There are three different tags:

 Tag <biteTest>: Enable communication between the ADS and the A350 BITE Test.
 Tag<dataLoading>: Enable a communication between the ADS and the A350 Data Loading.
 Tag <acms>: Enable navigation from the consultation tool to Aircraft Condition and Monitoring System (ACMS) system pages.
8.34.1 BITE Test tag: "biteTest"

ASR ASR
Use the <biteTest> tag to insert a BITE test in the "Procedure" paragraph (for A350 only).
Page 390 of 474
2. Select the "biteTest"

tag.
Page 391 of 474
A "Modify Attributes" dialog window opens:
Page 392 of 474
3. Fill in the fields according to the data available in the XML file (from the
Design Office. For more details, ref. TDG0208.1 MP authoring):
 Fill in the "side" field (0, 1, 2, 3 or 4).
 Fill in the "sideName" field (name of the related system + side).
 Fill in the "systemId" field (identifier number of the related system).
 Select the "target" field (two possible values: CMS (Centralized

Maintenance System) or LMF (Local Maintenance Function). This
information depends of the domain (Avionic or AISD domain)). For
A380, select “OMS-BT”.
 Fill in the "testId" field (number of the test).

CAUTION: Several tests can be available for the same system. 4. Click "OK".
The BITE test is inserted in the textual content (in a different order):
target. systemId. side. testId. sideName.
Page 393 of 474
8.34.2 DataLoading tag: "dataLoading"
ASR ASR
The <dataLoading> tag must contain the hardware FIN of the related system.
Note: This tag will create a "LOAD" button in the final product.
2. Select the "dataLoading"

tag.
Page 394 of 474
4. Click "OK".
3. Select the required target: SDL

(Simplified Dataloading) or DLCS. For
A380, select “OMS-DL”.
The <dataLoading> tag has been inserted:
Then, insert the hardware <FIN> in the <dataLoading> tag:

Page 395 of 474
5. Put the cursor and press the "Enter"

key.
6. Click the "fin" tag.
Result in Arbortext for A350:
Result in Arbortext for A380:
Page 396 of 474
The placeholder is applicable to the hardware FIN of the related system only. Ref. paragraph 8.9.1.1 Insert Placeholder.
8.34.3 System Indication Report tag “SysInfoReport”_A380 context

ASR ASR
The <systInfoReport> tag must contain the hardware FIN of the related system.
2. Click the "sysInfoReport" tag.
Page 397 of 474
A “Modify Attributes” pop-up window opens:
3. In the “Target” field, select the

"OMS-SIR”.
4. Click the OK button.
The sysInfoReport tags appear in the text:
5. The cursor must be located inside the tags, then press the “Enter” key again.
Page 398 of 474
A FIN button appears:
6. Press the FIN button

Page 399 of 474
8.34.4 ACMS System Pages Tag: "acms"
ASR ASR
Use the <acms> tag to enable a link to the ACMS System Pages.
2. Select the "acms" tag.
Page 400 of 474
4. Click "OK".
3. Fill in the following fields:

 "pageId" (possible values from 101 to 200).
 "pageName".
 "tabId" (possible values from 01 to 10).
Note: This data is given by the Design Office.
Page 401 of 474
8.35 To Insert an Illustration Item Tag: "item"
ASR ASR
N/A X N/A N/A N/A X N/A X N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
Use this tag to insert an item number of an illustration.

2. Select "item" tag.
Page 402 of 474
3. Enter the related item number.
Page 403 of 474
8.36 To Insert a Standard Part Number Tag: "standardPN"
ASR ASR
Use <standardPN> tag to insert a Part Number (PN) in ESP Description and Procedure.
This tag will enable navigation in AirN@v.
1. Put the cursor in a title or a paragraph and press the "Enter" key.
2. Select the "standardPN"

tag.
Page 404 of 474
2. Put the cursor between the "shortPN"

delimiters and write the short Part Number
in free text.
After a save in repository or a save in repository with generate PDF, you will see that some short Par t Numbers will be highlighted in
orange in Arbortext:
It means that this short Part Number contains a special character that will not be accepted by the production process.
Here is the list of the unaccepted characters:
 ‘‘
 ‘.’
 ‘,’
 ‘–‘
 ‘—‘
Page 405 of 474
3. Put the cursor after the last "shortPN"

delimiter and press the "Enter" key.
4. Select the "cageCode" tag (Applicable

to Vendor "shortPN" only).
Page 406 of 474

 Fill in the "Code" field (Cage Code). If not known, enter the
first characters, followed by an asterisk (e.g. I90*).
 Fill in the "Name" field (Supplier Name) (not mandatory).
7. Select the requested cage code.
8. Click "OK".
Page 407 of 474
8.37 To Insert bonding Tags
ASR ASR
There are four different bonding tags:

 bondingProcess
 bondingTestMethod
 bondingValue
 bondingFinalProtection
8.37.1 Bonding Process Tag: "bondingProcess"
Use the <bondingProcess> tag for the preparation of the bonding. The selection of the requested process in the search data panel (bonding code)
will generate the corresponding task in the Arbortext content.
Example: The selection of the bonding code P03 (Xx) will generate in the text content: "Ref. task 20-51-20-250-03".
Page 408 of 474
1. Put the cursor outside of the para delimiters and press the "Enter" key.
2. Select the "bondingProcess"

tag.
Page 409 of 474
3. Fill in the search criteria (at least one field of type

textual content needs to be filled in to launch Search):
 Fill in the "Identifier" field.
 Fill in the "Bonding_Code" field.
Select P01, P02, etc. in accordance with the
bonding Process (Xx) given in the drawings.
 Fill in the "Content" field.
5. Select the requested bonding

process.
6. Click "OK".
Page 410 of 474
Do not use the placeholder function. If data is not available, contact the Tech Data Engineer in charge of the ATA.
Page 411 of 474
8.37.2 TestMethod Tag: "bondingTestMethod"
Use the <bondingTestMethod > tag to refer to the corresponding task (method Mz) to test the bonding value. The selection of the requested bonding
test method in the search data panel (bonding code) will generate the corresponding task in the Arbortext content with the typical sentence: "Do a
check of the bonding value".
Example: The selection of the method M1 (Mz) will generate in the text content: "Do a check of the bonding value Ref. Task 20-51-20-34B-03
TASK_P_BONDING_TEST_METHOD_PH00001".
1. Put the cursor in a step and press the "Enter" key.
2. Select the "bondingMethod"

tag.
Page 412 of 474

textual content needs to be filled in to launch Search):
Select M1, M2, etc. in accordance with the
bonding test Method (Mz) given in the
drawings.

test method.
6. Click "OK".
Page 413 of 474
Do not use the placeholder function. If data is not available, contact the Tech Data Engineer in charge of the ATA .
Page 414 of 474
8.37.3 Bonding Value Tag: "bondingValue"
Use the <bondingValue> tag to give the bonding value. The selection of the requested bonding value in the search data panel (bonding code) will
generate the typical sentence: "Make sure that the bonding value is not more than" with the corresponding value.
Example: The selection of the bonding value A5 (Cy) will generate in the text content: "Make sure that the bonding value is not more than
10 milliohms".
1. After the bonding test method tag, create a sub-level

step and press the "Enter" key.
2. Select the "bondingValue"

tag.
Page 415 of 474
3. Fill in the search criteria (at least one field of

type textual content needs to be filled in to launch
Search):
Select A1, A2, etc. in accordance with the
bonding Class (Cy) given in the drawings.

value.
6. Click "OK".
Page 416 of 474
Page 417 of 474
8.37.4 Bonding Final Protection Tag: "bondingFinalProtection"
Use the <bondingFinalProtection> tag to give the applicable material of the bonding final protection. The selection of the requested surface
protection code in the search data panel (bonding code) will generate the corresponding sentence: "Apply a thin layer of…" with the applicable
material application code.
Example: The selection of the bonding final protection FA026 (FAvvv code) will generate in the text content: "Apply a thin layer of CMLAPPLI_06ACA1,
then apply a thin layer of CMLMAT_464800".
Note: Depending on the Favvv code, the sentence will contain one or two application codes.
Page 418 of 474
1. Create a step to introduce the final protection.
2. Create a sub-level step and press the "Enter" key.
3. Select the "bondingFinalProtection"

tag.
Page 419 of 474

textual content needs to be filled in to launch
Search):
Select FA025, FA026, etc., in accordance
with the surface protection code (FAvvv)
given in the drawings.
6. Select the requested surface

protection code.
7. Click "OK".
Page 420 of 474
Page 421 of 474
8.38 To Insert Metallic and Non-Metallic Materials Tag: "memat" & "nmemat"
ASR ASR
You can insert a metallic material using the < memat > tag.
You can insert a non-metallic material using the < nmemat > tag.
This tag is allowed in the following contexts:

 In the comminfo content
 In the subtask content
 In the 4th column of the repair material table. Ref. para 8.7.7 To Insert a Repair Material Table Tag: "matItem" & "repairMatItem".
Page 422 of 474
key.
2. Select the "memat" tag.
3 Insert a reference.
Page 423 of 474
4. Put the cursor after the ref tags and press the "Enter"
key.
5. Select the "designation" tag.
6 Insert a designation.
Use the same process for the the "nmemat" tag.
Page 424 of 474
8.39 To Insert Repair Category Tag: "category"
ASR ASR
You can insert a repair category using the <category > tag.
key.
2. Select the "category" tag.
Page 425 of 474
4. Click "OK".
3. Select the "category".
Page 426 of 474
8.40 To Insert a To Be Defined (TBD) Tag: "TBD"
ASR ASR
X X X N/A X X N/A N/A N/A N/A N/A N/A TBD TBD TBD TBD TBD TBD TBD TBD
The "TBD" tag must be used to cover the missing data which are not in the privileged data (no placeholder). It will replace the current typical
sentence ST00450 "TBD".
The "TBD" tag must be systematically used, in order to identify missing values.
Insert a <TBD> tag in:

 SD: in the "para" tag.
 MP:
 In the "Reason for the job" paragraph: in the "reasPara" tag and "para" tag.
 In the "Additional Information" paragraph: in the "CommonInfoPara" tag and "para" tag
 In the "Component Weight" paragraph: in the "CommonInfoPara" tag and "para" tag
 In the "para" tag.
 AFI: In the "action" tag and "question" tag.
 ESP description: in the "para" tag.
 ESP task:
 In the "Reason for the job" paragraph: in the "reasPara" tag and "para" tag.
 In the "Additional Information" paragraph: in the "CommonInfoPara" tag and "para" tag
 In the "Component Weight" paragraph: in the "CommonInfoPara" tag and "para" tag
 In the "para" tag.
Page 427 of 474
key.
2. Select the "TBD" tag.
3. Insert the information you are waiting for.
4. Click "OK".
Page 428 of 474
8.41 To insert a manual Highlight tag : “Highlight”
ASR ASR NDT
X X X X X X X X X X X X X TBD TBD TBD TBD TBD TBD TBD TBD
The highlight is provided to the customer to describe the change of the technical data and its impact for the user of the tec hnical data.
The aim is to describe the impact of the change in the task for the user who will perform the procedure.
For A380, highlights are also valid for illustrations.
Page 429 of 474
1. Put the cursor after the effectivity and press the

"Enter" key.
2. Select the "highlightsList" tag.
3. In the highlightsList, press the “Enter” key and insert the “highlight”
tag
4. Write your highlight
Page 430 of 474
Important information: The highlight will be taken into account for production only if some changes have been made within the authoring
Result in the Highlight tab in PPE:
You will see the highlight in the Highlight tab in PPE at the level where you put it (in this example, at subtask level).
Page 431 of 474
8.42 To insert zoning tag
This tag allows declaring zones only in ATA 06-20-00 descriptions. It will be used by DALI to build up the “ZONE LIST” in the Manual Front Matter of
the AMM.
1. Put the cursor after the paragraph and press the
"Enter" key.
2. Select the "zoning" tag.
Page 432 of 474
1. Choose Zone-from and Zone-to
3. Select the Zone
3. Select the Zone

Click “OK” ????
Page 433 of 474
Page 434 of 474
8.43 To insert accessPanel tag
<accessPanel> tags allow to declare panels only in ATA 06-XX descriptions. This is later on used by DALI to build up the “PANEL LIST” in the
Manual Front Matter of the AMM
1. First you need to enter a <acclst>

tag
Then a search panel will open:
Page 435 of 474
1. Choose Panel From and Panel To
2. Click ”Search”
3. Select the panel
4. Click “OK”
Page 436 of 474
Page 437 of 474
9 To Delete
9.1 To Delete Circuit Breaker(s) inside a Circuit Breaker Table

To delete circuit breaker(s) inside a circuit breaker table, select the <cb> tag in Arbortext.
Select the entire content of the circuit breaker to be deleted.
The selected circuit breaker is highlighted in black.
Press either the "delete" key on the keyboard or select the "delete" button in the Arbortext "Edit" menu.
Page 438 of 474
Deletion is executed; the circuit breaker is deleted successfully.
Page 439 of 474
10 File Tab
Layout information is not stored in XML data: numbering, table display.
A dedicated layout is applied to raw data to display it properly in the Arbortext Editor tool, PDF previews.
If errors or problems are detected when adding new data, the layou t can be refreshed using the commands: "Load" and "Save a Copy".
Page 440 of 474
10.1 Load a Copy
The "Load a Copy" function allows the user to open a local copy in "READ-ONLY" mode.
Select Load a Copy
Click "Open"
Page 441 of 474
10.2 Save a Copy
The "Save a Copy" function allows the user to savea copy of the Arbortext Editor session.
Select "Save a Copy"
Click "Save".
Page 442 of 474
10.3 Local Preview
The preview is available in the "File" tab of the menu.
The illustration(s) will be positioned at the end of the document.
Select "Local Preview"
Page 443 of 474
Revision bars are displayed to highlight
the parts linked to an AWO.
Page 444 of 474
11 Copy/Paste Function
Copy/Paste is possible in the "BOOK ALL" mode only. For more details, ref. UG1500229.0 "DACAS Introduction".
Copy/Paste of textual elements inside paragraphs is allowed.
Copy/Paste of structural elements of the document is not allowed.
Page 445 of 474
12 Save in Repository/Save in Repository with Generate PDF
The user can choose a save in repository to save the document in CITRIX environment.
Do a SAVE IN REPOSITORY even if there is no modification and to not let your TOPIC locked.
12.1 Save in Repository

You save your work in the SAP Repository.
Open "Save in Repository" from the "DACAS" tab of the menu.
The Editor will be closed automatically after the text is transferred into the SAP repository.
Next time you open via "BOOK ALL", the content that is saved in the Repository is shown.
When you save your work with the "Save in Repository" function, two types of error are detected:
Page 446 of 474
 Warning: information for the user who can decide to continue
 Error: blocking for the current operation
Page 447 of 474
12.2 Save in Repository with Generate PDF
The generated PDF file will include the illustration(s) by default.
Note: The illustration(s) will be positioned at the end of the document.
A pop-up indicates the PDF generation:
A confirmation message appears:
Page 448 of 474
12.3 Process to Generate a PDF File
files
Page 449 of 474
12.4 Where to Find the PDF Document
In SAP/iPPE, you can find the generated PDF attached to the "Documents" Tab at the task solution level.
Select the line of the PDF in the "Documents" tab and click the glasses icon to open the PDF.
Page 450 of 474
12.5 Link with AWO
Only the parts linked with an AWO are editable.
The parts linked with no AWO are highlighted in grey except the protected data (Warning, references, etc.).
To link an AWO in ARBORTEXT, the user must:
Page 451 of 474
1. Select the complete grey part to be edited.
Page 452 of 474
2. Click "Link with AWO" in the DACAS tab.
3. Click the "OK"

button.
Page 453 of 474
Result: The grey highlight is disabled and the user can edit this part.
Notes:
The unlink of a part of the document cannot be done from Arbortext Editor.
All the link actions (AWO) are applied in SAP/iPPE tree at save in repository. Ref. UG1500229.1 DACAS (SAP/iPPE Module) for AM products,
UG1500229.2 DACAS (SAP/iPPE Module) and yEd for AFI product, UG1500229.3 DACAS (SAP/iPPE Module) for ESP product and UG1500229.6
DACAS (SAP/iPPE Module) for ASR product.
Page 454 of 474
12.6 PDF Preview
 The generated PDF file used for V&V contains:
 Textual information added by the author.
 Tagged data defined in a database and inserted by the author.
 Content/information defined or calculated by the layout.
 It is important to understand how the PDF file is structured, generated and displayed to perform an efficient proofreading , especially:
 How to distinguish tagged data from textual content.
 How to distinguish authored data from generated data.
 How to distinguish placeholders from "real" data.
Page 455 of 474
MSN list: defined by the layout
List of criteria related to the solution
Warning: Red
Caution: Amber
Tagged Data: highlighted in yellow
"Not applicable ": defined by the layout
Page 456 of 474
Job Set-Up Information paragraph: Built during the preview

generation.
Same rules as authored content:

Tagged data: Highlighted in Yellow
Placeholders: Highlighted in Yellow + Red
Page 457 of 474
In an ESPM task, the following references will also appear in the Job Set-up Information:
 refEspmDesc
 refEspmDescSol
 refEspmTask
 refEspmTaskSol
Page 458 of 474
Typical Sentence:
 Highlighted in Yellow
Placeholders (WF or NWF)

 Highlighted in Yellow + Red
Numbering:
 Defined by the stylesheet FORFIN:
 Highlighted in Blue
Page 459 of 474
Step label:
 Visible in PDF preview
 Only used for authoring phase
 Not produced in the final product
Yes/No answer:
 Defined by the layout
Page 460 of 474
12.7 Revision Bars
The PDF Preview includes revision bars only for sub-items in "REVI" in GAMS, ref. UG1600192.2 WB/SA/LR/MB/XWB Generic Authoring
Management System (GAMS).

Page 461 of 474
13 Consistency Check
You select "Consistency check" for verification Error and Warning.
Select "DACAS" menu
Select "Consistency Check"
A pop-up window opens.
The list of the errors appears
It is necessary to make the modifications before re-launching the "Consistency Check".
When there is no error or warning, a message confirms it.
Page 462 of 474
Page 463 of 474
14 Save Locally/Local Preview
14.1 Save Locally

The "Save Locally" function will save your work on your Citrix server.
Go to the "File" tab of the menu and click the "Save" symbol.
To quit the Arbortext Editor tool, click the "Exit" symbol.
If you leave the Arbortext Editor tool by closing the window, the system will req uest you to save before closing.
The subsequent opening session via BOOK ALL will display the content that has been saved locally.
Page 464 of 474
14.2 Local Preview
The preview is available in the "File" tab of the menu (with illustration by default).
The illustration(s) will be positioned at the end of the document.
Page 465 of 474
Result:

Note: The local preview includes revision bars only for sub-items in "REVI" in GAMS, ref. UG1600192.2 WB/SA/LR/MB/XWB Generic Authoring
Management System (GAMS).
Page 466 of 474
Page 467 of 474
15 Appendix A. Correspondence between DACAS and GIPSY tags
GIPSY TAG DACAS TAG

ASSC refTask
ASSC refDescription
ASSC externalRef
BT Bitetest
CB cb
CBC cbClose
CBLT cblist/autocbsublst
CBO cbOpen
CDL afmRef with new attribute refloc
CL equinv
CNSE engConsumable
CNSM consumable/material
consumable/application
CNSW generalConsumable
COR refCorTask
COR refCorPageblock
COR externalCorRef
Page 468 of 474
DL dataLoading
DO refDescription
DZAC acclst (only in ATA 06-XX
descriptions)
DZON zoning (only in ATA 06-20 description)
EXPC expdCOC
EXPD expd (no more managed as a table)
EXPE expdEngine
FIN fin
FORF forfinList (in steps)
cbforfinList (in 865/875 CB sub-tasks)

GT table
GT tableTemplate
GT cblist (in 865/875 CB sub-tasks)
GT stepInTable
GT equlst (in UD4 Component Location
list)
OD/ID tableTemplate (TTL1 or 2)
ILL Graphic node

JSUR refTaskSol
LRU lru
MMEL mmelRef
MPD mpdRef
NLRU nlru
Page 469 of 474
NUM quantity
OUTC cocTool
OUTW stdTool
OUTW specificTool
OUTW interchgTools
RFFG graphicRef
RFTK refTask (to MP and TP task)
SIR sysInfoReport
SRC new attributes (srctype, srcref, srcawo,
srcverif) in tag tor and tors
SSPC sspc
SW sw/fin
TO refDescription
TOR tor (with new attribute for src)
TORS tors (with new attribute for src)
EQU/EQUW TXTGRPHC
TS ts
W warning
caution
WRG faultWire (from to with “lnktxt”
attribute)
WRGN wrg (with <fin>,<module> and <pin>)

WRGT textualWire (for free text wire)
Page 470 of 474
ZAC access
ZONE N/A (filled in SAP PPE Associated
Data screen)
Page 471 of 474
UG1500229.4
16 Referenced Documents
Doc. Reference Title
UG1600192.2 WB/SA/LR/MB/XWB Generic Authoring Management System (GAMS).
UG1500229.0 DACAS Introduction
UG1500229.1 DACAS (SAP/iPPE Module) for AM Products
UG1500229.2 DACAS (SAP/iPPE Module) and yEd for AFI Product
UG1500229.3 DACAS (SAP/iPPE Module) for ESP Product
UG1500229.6 DACAS (SAP/iPPE Module) for ASR Product
TDG0058 Electrical Standard Practices (ESP) Authoring
TDG0208.1 Aircraft Maintenance Procedure (MP) Authoring
TDG0209.1 Aircraft Fault Isolation (AFI) Authoring
AIRCRAFT MAINTENANCE TASK
TDG0037.4
ORIENTED SUPPORT SYSTEM (AMTOSS)
17 Glossary
Always refer to LEXINET
AM Aircraft Maintenance
AWO Authoring Work Order
DACAS Data Centric Authoring System
DU or UD Document Unit
IO Illustration Order
MP Maintenance Procedures
PMS Pseudo Manual Sequence
PWO Preparation Work Order
SD System Description
SDD System Description Document
SDS System Description Section
TO Training Objective
Page 472 of 474
UG1500229.4
Record of Revisions
Issue Date Reasons for Revision
A June 2015 Initial issue
B January 2018  Pt 6.4.1, 8.3.1 - Split tags cannot be used
anymore
 Pt 8.7.1 - Span Cells limitation
 Pt 8.9.2.1 - Information on ForFin insertion
 Pt 8.9.4 - Tag a CB in a FIN
 Pt 8.11.2 - LVL1 title in repair material table
 Pt 8.11.21 - Ref to subtask
 Pt 8.12.1.1 - Well formatted placeholders for
panels
 Pt 12.6 - ESP references in Job Set-up
 Pt 8.13.1 - Consumable search panel changed
 Pt 8.31 - Short PN including incorrect dashes
 Pt 8.36 - Manual Highlights
C September 2018 TDAC Update:
 Pt 6.1.2 – Create a DU in 1380 context
 Pt 8 extended to A380
o PT 8.10 added – equlst in A380 context
o PT 8.12.5 added – refTaskSol in A380
context
o PT 8.12.7 added – refCorPageBlock in
A380 context
o PT 8.12.8 added – externalCorRef in
A380 context
o PT 8.12.22 added – mmelRef in A380
context
o PT 8.15.4 added – autocbsublist in A380
context
o PT 8.15.5 added – SSPC in A380
context
o PT 8.17.6 added – cocTool in A380
context
o PT 8.19 added – expd in A380 context
o PT 8.20 added – expdEngine in A380
context
o PT 8.22 added – expdCOC in A380
context
o PT 8.30 added – faultwire in A380
context
o PT 8.34.3 added – SysInfoReport in
A380 context
o PT 8.42 added – To insert zoning tag
o PT 8.42 added – To insert accessPanel
tag
Page 473 of 474
UG1500229.4
This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual property
rights are granted by the delivery of this document or the disclosure of its content. This document shall not be
reproduced or disclosed to a third party w ithout the express w ritten consent of AIRBUS S.A.S. This document and its
content shall not be used for any purpose other than that for w hich it is supplied. The statements made herein do not
constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the
supporting grounds for these statements are not show n, AIRBUS S.A.S. w ill be pleased to explain the basis thereof.
Page 474 of 474

UG1500229 4 Iss C DACAS (Arbortext Editor Tool)

Uploaded by

Document Information

Original Description:

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

UG1500229 4 Iss C DACAS (Arbortext Editor Tool)

Uploaded by

Copyright:

Available Formats

A

Tool User Guide

DACAS (Arbortext Editor Tool) for System Description

(SD), Maintenance Procedure (MP), Aircraft Fault p

Isolation (AFI), Electrical Standard Practices (ESP) and g

Aircraft Structural Repair (ASR) Products o

Practices (ESP) and Aircraft Structural Repair (ASR). N

 Aircraft Maintenance (AM)

 Aircraft Fault Isolation (AFI)

 Electrical Standard Practices (ESP) x

 Aircraft Structural Repair (ASR)

Name: DUGRAVOT Stephane Name: NOWACZKOWSKI, Genevieve c

Function: Head Of TD Methods & Tools B

The "Structure view" presents a graphical, hierarchical view of your document

Most of the text content is located between a pair of tags.

4.1 "File" Tab

Save: the document is saved locally in the Citrix environment.

Load a copy: Save a copy of the document in a specific file.

Local preview: a preview is generated without PDF generation (more

Use this function to find textual content.

Use this function to find the XML structure (tag or attributes).

Click "Collapse/Expand Divisions".

This function allows to synchronize the display of the

Several options are available to display the content:

Click "-" to collapse an element in the Document Map.

Click "+" to expand an element in the Document Map.

You can enter a symbol using the <Symbol > element.

2. In the "Insert" menu, select "Symbol".

3. Select the required symbol

4. Click the "Insert" button to confirm the selection

Insert, delete, select or modify attributes of

Divide a cell into several cells.

Convert a selected row to a header row.

Convert a selected row to a footer row.

Display the "Table Properties" pop-up window.

4.8 "Window" Tab

Left/right split screen

Top-bottom split screen

By default split screen

4.9.1 "DACAS" Tab for Description and Procedure

Display the DACAS version.

For more details, ref. paragraph 12.5 Link with AWO

Used to update the content filled in at the creation of the

Displays the DACAS version.

For Graphical Editor use only:

4.10.1 Edit toolbar

Cut Copy Paste Undo Redo

Save Spelling Insert a table

Document map (switch between structure view and content view)

Switch between top/bottom split and no split

Note: Do not use the crossed icons .

Insert mark-ups Change the tag display

Modify attributes Select element content Collapse/Expand divisions

Note: Do not use the crossed icons .

Note: Do not use the crossed icons .

5.1 Markup Management

Content start Content end

Start of the tag End of the tag

Paragraph start Paragraph end

5.2.1 How to Insert a Tag

2. Select the tag to be inserted.

6.1 Description Sub-Element with Configuration Management

You can create your DU either in SAP: