Enhanced Automated Graphical Logistics Environment 0060 Workbook.pdf · 11.1.1.4 Establishing Query Selection Criteria .....11–9 11.1.1.5 Multiple Tables in ADHOC Queries – Joining

EAGLE WORKBOOK DEF STAN 00-60

VERSION 15

14 February 2017

A Product of Raytheon Company 2017 Raytheon Company

ALL RIGHTS RESERVED

U.S. Patents 4,847,795; 5,457,792; 5,493,679; 5,737,532; 7,930,052; 8,560,105

Made in the U.S.A

Enhanced

Automated

Graphical

Logistics

Environment

COPYRIGHT 2017 RAYTHEON COMPANY

UNPUBLISHED WORK - ALL RIGHTS RESERVED.

This document does not contain technology or Technical Data controlled under

either the U.S. International Traffic in Arms Regulations or the U.S. Export

Administration Regulations.

This document shall not be published, or disclosed to others, or duplicated in

whole or in part without written permission of Raytheon Company.

All other company and product names used herein may be the trademarks or

registered trademarks of their respective companies.

Information in this manual may change without notice and does not represent a

commitment on the part of Raytheon Company and its subsidiaries.

Revision History

Printed April 2001 First Edition

Printed July 2001 First Edition, Revised

Printed January 2001 Second Edition

Printed January 2006 Second Edition Revised

Printed October 2008 Third Edition

Printed February 2011 Fourth Edition

Printed February 2012 Fifth Edition

Printed February 2013 Fifth Edition Reprinted

Printed February 2014 Sixth Edition

Printed July 2014 Sixth Edition Updated

Printed February 2015 Seventh Edition

Printed September 2015 Seventh Edition Updated

Printed February 2016 Eighth Edition

Printed September 2016 Eighth Edition Revised

Printed February 2017 Ninth Edition

Printed February 2017

The EAGLE Software Package has become the best of its

kind thanks, in large part, to its clients. We would like to

take this opportunity to thank all of you for your

suggestions, insights and support. In addition, we want to

renew our commitment to you, our valued clients.

EAGLE Workbook DEF STAN 00-60 Version 15

TABLE OF CONTENTS

EAGLE WORKBOOK DEF STAN 00-60 TABLE OF CONTENTS

v

TABLE OF CONTENTS

SECTION 1 THE EAGLE INTERFACE ................................................................... 1-3

1.0 INTRODUCTION ............................................................................................................... 1-3 1.1 CONVENTIONS USED IN DOCUMENTATION ............................................................. 1-3

1.1.1 General Conventions .................................................................................................... 1-3 1.1.2 Mouse Conventions ...................................................................................................... 1-4 1.1.3 Keyboard Conventions ................................................................................................. 1-4 1.1.4 Window Conventions ................................................................................................... 1-4 1.1.5 End Items and Student Ids ............................................................................................ 1-5

1.2 ADMINISTRATION ........................................................................................................... 1-5 1.2.1 Administrative User Ids and Passwords ....................................................................... 1-5

1.3 STANDARDS AND EAGLE LSAR DATABASE CONFIGURATIONS ......................... 1-6 1.3.1 DEF-STAN-00-60 ........................................................................................................ 1-6

1.3.1.1 System Default Settings......................................................................................... 1-6 1.3.1.2 End Item Default Settings...................................................................................... 1-7

1.4 LOGGING IN TO EAGLE .................................................................................................. 1-7 1.5 THE NAVIGATOR ............................................................................................................. 1-8

1.5.1 Using Navigator Functions ......................................................................................... 1-10 1.5.2 Home Tab Functions .................................................................................................. 1-10

1.5.2.1 Home Tab Filter .................................................................................................. 1-10 1.5.2.2 Basic Finder ......................................................................................................... 1-11

1.5.3 Favorites Tab Functions ............................................................................................. 1-13 1.5.4 Recent Tab Function................................................................................................... 1-15 1.5.5 Classic Navigator ....................................................................................................... 1-15

1.6 EAGLE MAIN SCREEN HEADER .................................................................................. 1-17 1.7 THE MENU BAR .............................................................................................................. 1-17 1.8 THE MAIN TOOLBAR .................................................................................................... 1-18

1.8.1 EAGLE Help .............................................................................................................. 1-18 1.8.2 Item Help .................................................................................................................... 1-18 1.8.3 DB Help ...................................................................................................................... 1-18 1.8.4 Graphical Functions ................................................................................................... 1-19

1.9 REPORTS/PROCESS MENU AND FUNCTION SPECIFIC TOOLBARS ..................... 1-19 1.9.1 Using the Reports Process Menu or Function Specific Toolbar ................................. 1-20

1.10 SELECTING END ITEM ................................................................................................ 1-20 1.11 DISCIPLINE OUTPUTS ................................................................................................. 1-21

SECTION 2 ENTERING CROSS FUNCTIONAL DATA ....................................... 2-3

2.0 INTRODUCTION ............................................................................................................... 2-3 2.1 ESTABLISHING AN END ITEM ACRONYM CODE ...................................................... 2-3


vi

2.2 ASSIGNING LCNS ............................................................................................................. 2-6 2.3 ASSIGNING A PCCN AND UOC TO SYSTEM / END ITEM LEVEL LCN .................... 2-13 2.4 MAPPING LCNS TO SYSTEM/END ITEM UOCS ........................................................ 2-15 2.5 ASSIGNING SERIAL NUMBER UOCS TO SYSTEM/END ITEM LCNS ..................... 2-18 2.6 MAPPING LCNS TO SYSTEM/END ITEM SERIAL NUMBER UOCS ......................... 2-21 2.7 ADDING CAGE CODES .................................................................................................. 2-24 2.8 ADDING REFERENCE NUMBER INFORMATION ..................................................... 2-26 2.9 APPLYING REFERENCE NUMBERS TO AN LCN (PART APPLICATION) .............. 2-28 2.10 ASSIGNING PART UOCS TO SYSTEM/END ITEM LCNS......................................... 2-30 2.11 ESTABLISHING TECHNICAL MANUAL CODES ..................................................... 2-33

SECTION 3 ENTERING OPERATIONS AND MAINTENANCE

REQUIREMENTS DATA ............................................................................................ 3-3

3.0 INTRODUCTION ............................................................................................................... 3-3 3.1 ADDING OPERATIONS AND MAINTENANCE DATA ................................................. 3-3

SECTION 4 ADDING RELIABILITY, AVAILABILITY AND

MAINTAINABILITY DATA ....................................................................................... 4-3

4.0 INTRODUCTION ............................................................................................................... 4-3 4.1 ADDING RELIABILITY AND MAINTAINABILITY DATA .......................................... 4-3 4.2 ADDING RAM CHARACTERISTICS DATA ................................................................... 4-4 4.3 ADDING RAM CHARACTERISTICS NARRATIVE ....................................................... 4-6 4.4 ADDING RAM LOGISTICS CONSIDERATIONS NARRATIVE DATA ........................ 4-7 4.5 ADDING RAM INDICATOR CODE DATA ..................................................................... 4-8 4.6 ADDING WAR/PEACE RAM INDICATOR CHARACTERISTICS DATA .................. 4-10 4.7 ADDING FAILURE MODE AND RCM ANALYSIS DATA .......................................... 4-11 4.8 ADDING FAILURE MODE AND RELIABILITY CENTERED MAINTENANCE

NARRATIVE .......................................................................................................................... 4-13 4.9 ADDING FAILURE MODE TASK DATA ...................................................................... 4-13 4.10 ADDING MISSION PHASE OPERATIONAL MODE DATA ...................................... 4-16 4.11 ADDING RAM CRITICALITY DATA AND FAILURE MODE INDICATOR MISSION

PHASE CODE CHARACTERISTICS DATA ........................................................................ 4-17 4.12 ADDING RAM FAILURE MODE INDICATOR MISSION PHASE CODE

CHARACTERISTICS NARRATIVE DATA ......................................................................... 4-18

SECTION 5 ENTERING TASK ANALYSIS DATA ................................................ 5-3

5.0 INTRODUCTION ............................................................................................................... 5-3 5.1 CREATING TASKS............................................................................................................ 5-3

5.1.1 Adding a New Task ...................................................................................................... 5-5 5.1.1.1 Adding Original Tasks .......................................................................................... 5-5


vii

5.1.1.1.1 Specifying Facilities Requirements in Task Analysis................................... 5-10 5.1.1.2 Adding Reference Tasks ...................................................................................... 5-13

5.1.2 Cloning Tasks ............................................................................................................. 5-18 5.1.3 Sorting Task Codes .................................................................................................... 5-27

5.2 ADDING SUBTASKS TO TASKS ................................................................................... 5-28 5.2.1 Adding Original Subtasks ........................................................................................... 5-29 5.2.2 Adding Reference Subtasks ........................................................................................ 5-31 5.2.3 Changing Subtask References .................................................................................... 5-34 5.2.4 Breaking References ................................................................................................... 5-38

5.3 ADDING NARRATIVE DATA TO SUBTASKS ............................................................. 5-39 5.4 ADDING SUPPORTING DATA FOR TASKS ................................................................ 5-45

5.4.1 Adding Task Data ....................................................................................................... 5-45 5.4.1.1 Assigning Support Equipment ............................................................................. 5-45 5.4.1.2 Assigning Provisioning Items .............................................................................. 5-49

5.4.2 Adding Support Data to Subtasks ............................................................................... 5-52 5.4.2.1 Assigning Personnel ............................................................................................ 5-52

5.4.3 Assigning Workloads ................................................................................................. 5-53 5.5 ASSIGNING TASK NARRATIVE TO A TECH MANUAL ............................................ 5-56

SECTION 6 ENTERING FACILITIES CONSIDERATIONS DATA .................... 6-3

6.0 INTRODUCTION ............................................................................................................... 6-3 6.1 ADDING FACILITIES DATA ............................................................................................ 6-3

6.1.1 Adding New Facility Data ............................................................................................ 6-4 6.1.2 Linking Facilities Data to Task Requirements ............................................................. 6-6

SECTION 7 ENTERING PERSONNEL SKILLS CONSIDERATIONS DATA ... 7-3

7.0 INTRODUCTION ............................................................................................................... 7-3 7.1 ADDING PERSONNEL DATA .......................................................................................... 7-3 7.2 ASSIGNING PERSONNEL PHYSICAL AND MENTAL REQUIREMENTS TO A

TASK ........................................................................................................................................ 7-5

SECTION 8 ENTERING TRANSPORTABILITY ENGINEERING ANALYSIS

DATA .............................................................................................................................. 8-3

8.0 INTRODUCTION ............................................................................................................... 8-3 8.1 ADDING TRANSPORTATION DATA ............................................................................. 8-3

8.1.1 Adding Transportation Shipping Mode Data ............................................................... 8-6 8.1.2 Adding Transported End Item Data .............................................................................. 8-7 8.1.3 Adding Transported End Item Narrative ...................................................................... 8-8 8.1.4 Adding Transport by Fiscal Year Data ......................................................................... 8-9 8.1.5 Adding Transportation Narrative................................................................................ 8-10


viii

SECTION 9 ENTERING SUPPORT EQUIPMENT AND TRAINING

MATERIALS REQUIREMENTS DATA .................................................................. 9–3

9.0 INTRODUCTION ............................................................................................................... 9–3 9.1 ADDING SUPPORT EQUIPMENT AND UNIT UNDER TEST INFORMATION .......... 9–3 9.2 ADDING SUPPORT EQUIPMENT ................................................................................... 9–5

9.2.1 Assigning SERD Numbers ........................................................................................... 9–6 9.2.2 Adding Support Equipment Data ................................................................................. 9–8

9.2.2.1 Adding Support Equipment Narrative ................................................................... 9–8 9.2.2.2 Adding a SERD Name and Administrative Data ................................................... 9–9

9.2.3 Running a SERD Report ............................................................................................ 9–10 9.2.4 Support Equipment and Unit Under Test Data Tabs .................................................. 9–14

SECTION 10 ENTERING PACKAGING AND PROVISIONING

REQUIREMENTS DATA .......................................................................................... 10-3

10.0 INTRODUCTION ........................................................................................................... 10-3 10.1 ADDING REFERENCE NUMBER INFORMATION ................................................... 10-3

10.1.1 Adding CAGE Codes (XH) ...................................................................................... 10-5 10.1.2 Adding Reference Number Information (HA).......................................................... 10-8 10.1.3 Adding Additional Reference Number Information (HB) ........................................ 10-9

10.2 ADDING PART APPLICATIONS (HG RECORDS) ................................................... 10-11 10.3 MAINTAINING OTHER PROVISIONING DATA ELEMENTS USING THE

VIEW/EDIT PROVISIONING DATA WINDOW ............................................................... 10-15 10.3.1 Maintaining Provisioning Data (Table HA) ........................................................... 10-16 10.3.2 Entering Provisioning Remarks .............................................................................. 10-17 10.3.3 Adding Provisioning UOC Data ............................................................................. 10-17 10.3.4 Adding Item Packaging Requirement Data ............................................................ 10-18 10.3.5 Adding Design Change Information ....................................................................... 10-20

SECTION 11 AD HOC REPORTING..................................................................... 11–3

11.0 INTRODUCTION ........................................................................................................... 11–3 11.1 SQL TRANSACTION STATEMENTS .......................................................................... 11–3

11.1.1 New Query ............................................................................................................... 11–3 11.1.1.1 Query Table Selection ....................................................................................... 11–4 11.1.1.2 Query Column Selection ................................................................................... 11–6 11.1.1.3 Generating the AdHoc Report ........................................................................... 11–8 11.1.1.4 Establishing Query Selection Criteria ............................................................... 11–9 11.1.1.5 Multiple Tables in ADHOC Queries – Joining Tables ...................................... 11–9 11.1.1.6 Where Criteria ................................................................................................. 11–16 11.1.1.7 Sort Criteria ..................................................................................................... 11–17

11.1.2 Adding Comments to Queries ................................................................................ 11–19


ix

11.1.3 Saving Report Information ..................................................................................... 11–20 11.1.3.1 Saving Query Scripts ....................................................................................... 11–21 11.1.3.2 Saving Report Output ...................................................................................... 11–22 11.1.3.3 Recall Query .................................................................................................... 11–22 11.1.3.4 Recalling Queries from the Database .............................................................. 11–23

11.1.4 Updating the Database with Query Results ............................................................ 11–26 11.1.4.1 Updating the Database (Query Results Window) ............................................ 11–26 11.1.4.2 Updating the Database (Multi-Cell Cut, Copy, Paste Window) ...................... 11–28

11.1.5 Key Field Updates and Parent Table Deletes ......................................................... 11–33 11.1.6 Loading External Data ............................................................................................ 11–34

SECTION 12 INTERPRETING ERROR MESSAGES ......................................... 12–3

12.0 INTRODUCTION ........................................................................................................... 12–3 12.1 ERROR MESSAGES IN EAGLE ................................................................................... 12–3

12.1.1 Security Violations ................................................................................................... 12–3 12.1.2 Unique Constraint Violation ..................................................................................... 12–4 12.1.3 Integrity Constraint – Parent Key Not Found ........................................................... 12–5 12.1.4 Integrity Constraint – Child Record Found .............................................................. 12–6 12.1.5 Cross Edit Violations ................................................................................................ 12–7 12.1.6 Rule Bound to a Column Violations ......................................................................... 12–8

LCNS TO BOM .................................................................................. A–3

STRUCTURED QUERY LANGUAGE ........................................... B–3

INDEX ................................................................................................................................ 3


x


LIST OF

ILLUSTRATIONS

EAGLE WORKBOOK DEF STAN 00-60 LIST OF ILLUSTRATIONS

xiii

LIST OF ILLUSTRATIONS

FIGURE PAGE Figure 1. System Defaults – DEF STAN 00-60 ........................................................................... 1-6 Figure 2. End Item Defaults – Issue 5 Selected ............................................................................ 1-7 Figure 3. EAGLE Login Window ................................................................................................ 1-8 Figure 4. The Navigator Tree View ............................................................................................. 1-9 Figure 5. AdHoc Discipline – Visual Query Builder Function Selected .................................... 1-10 Figure 6. Navigator Home Tab – Filter Applied. ....................................................................... 1-11 Figure 7. Navigator Home Tab – Provisioning Finder Function Selected.................................. 1-12 Figure 8. Provisioning Finder ..................................................................................................... 1-12 Figure 9. Provisioning Finder – Records Returned C% Filter .................................................... 1-13 Figure 10. Favorites Tab – Manage Favorites ............................................................................ 1-14 Figure 11. Manage Favorites Window - Add ............................................................................. 1-14 Figure 12. Recent Tab – Recently Utilized Functions ................................................................ 1-15 Figure 13. Main Screen – File>>Open ....................................................................................... 1-16 Figure 14. Classic Navigator – AdHoc>>New Query ................................................................ 1-16 Figure 15. EAGLE Main Screen - Header ................................................................................. 1-17 Figure 16. EAGLE Main Screen – Menu Bar ............................................................................ 1-17 Figure 17. Main Toolbar ............................................................................................................ 1-18 Figure 18. Function Specific Toolbar ......................................................................................... 1-19 Figure 19. Select an End Item Window ....................................................................................... 1-21 Figure 20. Save Rows As Window ............................................................................................. 1-22 Figure 21. Navigator - End Item (XA) Maintenance .................................................................... 2-4 Figure 22. End Item Data Maintenance Window - TRAININGXX End Item ............................. 2-4 Figure 23. End Item Data Maintenance Window - TRAININGXX End Item ............................. 2-5 Figure 24. End Item Data Maintenance – Scrolled Right ............................................................. 2-6 Figure 25. Navigator - LCN (XB) Maintenance ........................................................................... 2-7 Figure 26. End Item Bicyclexx – XB Records ............................................................................. 2-7 Figure 27. LSA Control Number Data Maintenance Window ..................................................... 2-8 Figure 28. LSA Control Number Data Maintenance Window - Adding Sys EI Identifier ........... 2-9 Figure 29. LSA Control Number Data Maintenance Window - Logistics Decision Office .......... 2-9 Figure 30. LCN Data Maintenance – ‘A01’ Entered .................................................................. 2-10 Figure 31. LCN Data Maintenance Window – ‘A03’ Selected .................................................. 2-11 Figure 32. LCN Data Maintenance Window – ‘ALC 02’ .......................................................... 2-12 Figure 33. LCN Data Maintenance Window – ALC ‘02’ Records ............................................ 2-12 Figure 34. Navigator - System/EI (XC) Maintenance ................................................................ 2-13 Figure 35. System/End Item Maintenance – LCN ‘A’ ALC ‘02’ Selected ................................ 2-14 Figure 36. System/End Item Maintenance Window – UOC and PCCN .................................... 2-15 Figure 37. Navigator - LCN to System/EI (XF) Maintenance ................................................... 2-15 Figure 38. LCN System/End Item UOC Maintenance Window – LCN A ................................. 2-16 Figure 39. LCN System/End Item UOC Maintenance Window – LCN A01 ............................. 2-17 Figure 40. LCN System/End Item UOC Maintenance Window – LCN BIKE03 ...................... 2-18 Figure 41. Navigator – System/EI SN (XD) Maintenance ......................................................... 2-19


xiv

Figure 42. System/End Item Serial Number Maintenance Window ........................................... 2-19 Figure 43. System/End Item Serial Number Maintenance – ALC ‘02’ ...................................... 2-20 Figure 44. System/End Item Serial Number Maintenance – S/N UOC: A ................................. 2-20 Figure 45. Navigator - LCN to S/N UOC (XE) Maintenance .................................................... 2-21 Figure 46. Mapping of LCNs to Serial Number UOCs .............................................................. 2-22 Figure 47. LCN to Serial Number Usable On Code Window – LCN ‘A01’ .............................. 2-23 Figure 48. LCN to Serial Number Usable On Code Window – LCN ‘A03’ .............................. 2-24 Figure 49. Navigator - CAGE Code (XH) Maintenance ............................................................ 2-25 Figure 50. CAGE Code Data Maintenance Window - Adding CAGE Information ................... 2-26 Figure 51. Navigator - Part (HA) Maintenance .......................................................................... 2-27 Figure 52. Part Number Data Maintenance - Adding Reference Number Information .............. 2-27 Figure 53. Part Number Data Maintenance - Adding 2nd Reference Number ............................ 2-28 Figure 54. Navigator - Part App. (HG) Maintenance ................................................................. 2-29 Figure 55. Part Application Provisioning Data Maintenance ..................................................... 2-29 Figure 56. Part Application Provisioning Data Maintenance Window - Backfill ...................... 2-30 Figure 57. Navigator - Prov. System/EI (HO) Maintenance ...................................................... 2-31 Figure 58. Provisioning/End Item Usable On Code Maintenance – T% Entered ....................... 2-31 Figure 59. Provisioning/End Item Usable On Code Maintenance Window ............................... 2-32 Figure 60. Provisioning/End Item Usable On Code Maintenance Window – TR1 UOC ........... 2-33 Figure 61. Navigator Home Tab - Tech Manual Discipline ....................................................... 2-34 Figure 62. Maintain Tech Manual Codes Window – TM1......................................................... 2-34 Figure 63. Maintain Tech Manual Codes - TMT ....................................................................... 2-35 Figure 64. Navigator - Operations Maintenance .......................................................................... 3-3 Figure 65. Operations and Maintenance Finder ........................................................................... 3-4 Figure 66. Operations and Maintenance Requirement Window ................................................... 3-5 Figure 67. Navigator - War/Peace Requirements ......................................................................... 3-6 Figure 68. War and Peace Requirements – Record 1 of 5 ............................................................ 3-7 Figure 69. Navigator – Recent Tab .............................................................................................. 3-8 Figure 70. Operations and Maintenance Finder – LCN A05 ........................................................ 3-8 Figure 71. Reliability Requirement - Annual Operating Requirements ....................................... 3-9 Figure 72. Navigator Home Tab – RAM Finder Function Selected ............................................. 4-3 Figure 73. Navigator - Reliability + Maintainability Finder ........................................................ 4-4 Figure 74. RAM Characteristics – Top Shown ............................................................................ 4-5 Figure 75. RAM Characteristics Window .................................................................................... 4-6 Figure 76. RAM Characteristics Narrative Window .................................................................... 4-7 Figure 77. RAM Logistics Considerations Narrative Window .................................................... 4-8 Figure 78. RAM Indicator Characteristics Window – Top Shown .............................................. 4-9 Figure 79. RAM Indicator Characteristics Window – Mean Time Between: .............................. 4-9 Figure 80. RAM Indicator Characteristics Window – Time Between: ...................................... 4-10 Figure 81. War/Peace RAM Window ........................................................................................ 4-11 Figure 82. Fail Mode (FM) and RCM Analysis Window .......................................................... 4-12 Figure 83. RAM Failure Mode + RCM Narrative Window ....................................................... 4-13 Figure 84. Failure Mode Task Window...................................................................................... 4-14 Figure 85. Task Selection Window ............................................................................................ 4-15 Figure 86. Failure Mode Task Window – Task Type ................................................................. 4-16 Figure 87. Mission Phase Operational Mode Window ............................................................... 4-17


xv

Figure 88. Failure Mode IMPCC Characteristics ....................................................................... 4-18 Figure 89. RAM FM IMPCC Narrative Window ....................................................................... 4-19 Figure 90. Navigator - Task Analysis ........................................................................................... 5-3 Figure 91. Task Analysis Finder – Records Returned .................................................................. 5-4 Figure 92. Task Analysis Finder Window – ALC ‘01’ Selected .................................................. 5-5 Figure 93. Task Information Window - New Task....................................................................... 5-6 Figure 94. Task Information Window - INSPECT ....................................................................... 5-7 Figure 95. Create Task Code ........................................................................................................ 5-8 Figure 96. Task Information Window – Task Code Created ........................................................ 5-9 Figure 97. Annual Operating Requirements ............................................................................... 5-10 Figure 98. Task Information Window – Facilities Tab>>Facilities Required ............................ 5-11 Figure 99. No Facility Selected! Dialog Box ............................................................................. 5-11 Figure 100. Task Information Window – Facilities Added ........................................................ 5-12 Figure 101. Task Info. Tab – Facilities Tab Selected ................................................................. 5-12 Figure 102. Error Message – Table FE Rule C .......................................................................... 5-13 Figure 103. Task Information Window – REPAIR FLAT ......................................................... 5-14 Figure 104. Reference Task Finder – REPAIR FLAT TIRE ..................................................... 5-15 Figure 105. Task Information Window – Top Shown ................................................................ 5-15 Figure 106. Task Information Window - Reference ................................................................... 5-16 Figure 107. Task Information - Viewing Referenced Task Information .................................... 5-17 Figure 108. ORIGINAL Task Information................................................................................. 5-17 Figure 109. Task Analysis Finder – ALC ‘00’ ........................................................................... 5-18 Figure 110. Clone Tasks Window – Top Shown ........................................................................ 5-19 Figure 111. Subtask Cloning Options ........................................................................................ 5-20 Figure 112. Clone Tasks Window – Create a Reference Task Selected ..................................... 5-20 Figure 113. Clone Tasks Window – INSPECT BICYCLE ........................................................ 5-21 Figure 114. Clone Tasks Window – Reference All its Subtasks ................................................ 5-21 Figure 115. Clone Tasks Window – Adjust Seat Height ............................................................ 5-22 Figure 116. Task Cloning Destination LCN Finder ................................................................... 5-23 Figure 117. LSA Control Number Data Maintenance Window - Copying Tasks ...................... 5-24 Figure 118. Task Cloning Destination LCN Finder Results ....................................................... 5-25 Figure 119. Cloning Destination LCN ....................................................................................... 5-25 Figure 120. Task Information Window - Task Cloning Results ................................................. 5-26 Figure 121. Task Analysis Finder – ALC ‘00’ Selected ............................................................ 5-27 Figure 122. Specify Sort Columns Window. .............................................................................. 5-28 Figure 123. Task Analysis Finder – ALC ‘01’ Selected. ........................................................... 5-29 Figure 124. Subtask Information Window – New Subtask Tab ................................................. 5-30 Figure 125. Subtask Information Window – Subtask Identification .......................................... 5-30 Figure 126. New Subtask No. - 2 ............................................................................................... 5-31 Figure 127. Reference Subtask Finder – Query Results ............................................................. 5-32 Figure 128. Subtask Information - Viewing Referenced Subtask Information .......................... 5-33 Figure 129. Original Subtask Information .................................................................................. 5-34 Figure 130. Task analysis Finder – BIKE ALC ‘03’ .................................................................. 5-35 Figure 131. Subtask Information Window – Reference Information Tab .................................. 5-36 Figure 132. Reference Subtask Finder - Changing Subtask References .................................... 5-37 Figure 133. Save Reference Subtask Changes ........................................................................... 5-37


xvi

Figure 134. Subtask Information Window – Subtask 3 .............................................................. 5-38 Figure 135. Subtask Information Window - Reference Information Tab ................................... 5-39 Figure 136. Main Screen – Tools>>Options .............................................................................. 5-40 Figure 137. Options – Editor: ‘NONE’ ...................................................................................... 5-40 Figure 138. Task Analysis Finder – LCN ‘BIKE’ ALC ‘01’ Selected ....................................... 5-41 Figure 139. Narrative Editor - Subtask 1 – Element Code Checked .......................................... 5-42 Figure 140. Narrative Editor - Subtask 2 .................................................................................... 5-43 Figure 141. Source Data Modified – Reference Subtask Check Window .................................. 5-44 Figure 142. Task Information - Support Equipment .................................................................. 5-46 Figure 143. Task Support Equipment Window .......................................................................... 5-46 Figure 144. Task Support Equipment ......................................................................................... 5-47 Figure 145. Task Information - Support Equipment Added ....................................................... 5-48 Figure 146. Task Information Window – Peculiar/Common Tool Message Box ...................... 5-48 Figure 147. Task Info. Tab - Misc Tab....................................................................................... 5-49 Figure 148. Task Information - Provisioned Items ..................................................................... 5-50 Figure 149. Task Provisioned Items Window ............................................................................ 5-51 Figure 150. Task Information - Provisioned Items Added ......................................................... 5-52 Figure 151. Subtask Information – Personnel ............................................................................ 5-53 Figure 152. Subtask Information Window - Workload Tab – Person ID Codes ........................ 5-54 Figure 153. Subtask Information Window - Workload Tab – Job Duty Codes .......................... 5-55 Figure 154. Subtask Information Window - Workload Tab ....................................................... 5-55 Figure 155. Task Information - Tech. Manuals .......................................................................... 5-57 Figure 156. Tech. Manuals Tab – 00-60 Data button ................................................................. 5-57 Figure 157. Additional Task/Tech Manual Data Window ......................................................... 5-58 Figure 158. Navigator – Facilities Finder ..................................................................................... 6-3 Figure 159. Facilities Finder – Records Returned ........................................................................ 6-4 Figure 160. Facilities Finder – Record Added ............................................................................. 6-5 Figure 161. Facility Window ........................................................................................................ 6-5 Figure 162. Task Selection Window ............................................................................................ 6-7 Figure 163. Operations + Maintenance Task Facility Requirements – Task Selected ................. 6-8 Figure 164. Navigator - Personnel Skills...................................................................................... 7-3 Figure 165. Personnel Skills Finder (GA) Window – Skill Specialty Code ................................. 7-4 Figure 166. Personnel Skills – Personnel Skills Finder (GB,GC,GD) ......................................... 7-4 Figure 167. New or Modified Skill Finder ................................................................................... 7-5 Figure 168. Physical and Mental Req Finder (GE) ...................................................................... 7-6 Figure 169. Physical and Mental Requirements Narrative Finder ................................................ 7-6 Figure 170. Physical and Mental Requirements Narrative Finder ................................................ 7-7 Figure 171. New or Modified Skill Specialty Code Finder .......................................................... 7-7 Figure 172. Subtask Personnel Requirement Finder .................................................................... 7-8 Figure 173. Physical and Mental Requirements Narrative Window ............................................ 7-9 Figure 174. Navigator –Transportation Finder Selected .............................................................. 8-3 Figure 175. Transportation Finder – Records Returned ............................................................... 8-4 Figure 176. Transportation Window ............................................................................................ 8-5 Figure 177. Transportation Ship Mode Window – Top Shown ................................................... 8-6 Figure 178. Transportation Ship Mode Window – Bottom Shown .............................................. 8-7 Figure 179. Transported End Item Window – Top Shown .......................................................... 8-7


xvii

Figure 180. Transported End Item Window – Bottom Shown ..................................................... 8-8 Figure 181. Transported End Item – Narrative Button Active ..................................................... 8-8 Figure 182. Transported End Item Narrative Window ................................................................. 8-9 Figure 183. Transport by Fiscal Year Window .......................................................................... 8-10 Figure 184. Transportation Narrative Window .......................................................................... 8-11 Figure 185. Navigator - Support Equipment ............................................................................... 9–4 Figure 186. SERD Finder Window – Records Returned ............................................................. 9–4 Figure 187. Support Equipment Window - Adding..................................................................... 9–6 Figure 188. SERD Finder – TH-1001 Selected ........................................................................... 9–7 Figure 189. SERD Recommendation Data Window ................................................................... 9–7 Figure 190. Support Equipment Data Window - Narrative Tab .................................................. 9–9 Figure 191. Support Equipment Data Window - Admin. Data Tab .......................................... 9–10 Figure 192. Reports/Process – Reports>>LSA-070 .................................................................. 9–11 Figure 193. LSA-070 SERD Standard Parameters Tab ............................................................. 9–12 Figure 194. LSA-070 SERD Specific Parameters Tab .............................................................. 9–12 Figure 195. Report Generator Completion Message ................................................................. 9–13 Figure 196. Save Report to Table ZD ....................................................................................... 9–13 Figure 197. Document Imported Dialog Box ............................................................................ 9–14 Figure 198. Navigator – Provisioning Finder Selected .............................................................. 10-4 Figure 199. Provisioning Finder – Records Returned ................................................................ 10-4 Figure 200. Provisioning Finder – All Parts Displayed .............................................................. 10-6 Figure 201. New Part Information Window - CAGE Code Data ............................................... 10-7 Figure 202. New Part Information Window – New Cage Code Added ..................................... 10-7 Figure 203. New Part Information Window – Find: T ............................................................... 10-8 Figure 204. New Part Information Window - Reference Number.............................................. 10-8 Figure 205. New Part Information Window – Reference Number Data Cont’d ........................ 10-9 Figure 206. Provisioning Finder – Top Portion ........................................................................ 10-10 Figure 207. Provisioning Finder – Record Returned ................................................................ 10-10 Figure 208. View/Edit Provisioning Data Window – HB Tab Selected ................................... 10-11 Figure 209. Part Application Information – HG Window ........................................................ 10-12 Figure 210. Part Application - LCN Finder Window ............................................................... 10-12 Figure 211. LCN Finder Window – Save Changes .................................................................. 10-13 Figure 212. Part Application Information - HG (SMR Code) .................................................. 10-14 Figure 213. Provisioning Finder – Added Part Application Information ................................. 10-15 Figure 214. View/Edit Provisioning Data - Summary Tab ...................................................... 10-15 Figure 215. View/Edit Provisioning Data Window - HA Tab Selected .................................... 10-16 Figure 216. Adding Provisioning Remarks – HI Tab ............................................................... 10-17 Figure 217. Adding Provisioning UOC Data ........................................................................... 10-18 Figure 218. Adding Item Packaging Requirement Data ........................................................... 10-19 Figure 219. Select Packaging Data Window ............................................................................ 10-19 Figure 220. View/Edit Provisioning Data Window – HF Tab ................................................. 10-20 Figure 221. View/Edit Provisioning Data Window – HP Tab ................................................. 10-21 Figure 222. Navigator Discipline - New Query Function Selected ........................................... 11–4 Figure 223. New Query Window .............................................................................................. 11–5 Figure 224. New Query Window (portion) - Functional Area Selected .................................... 11–5 Figure 225. New Query - Table Name ‘HA’ Selected .............................................................. 11–6


xviii

Figure 226. New Table Column Selection ................................................................................ 11–7 Figure 227. Query Results for New Query - Simple Query ...................................................... 11–8 Figure 228. Join CriteriaWindow – HA Joined to HG ............................................................ 11–10 Figure 229. New Query window - Table HO Selected ............................................................ 11–11 Figure 230. Join Criteria - HG Joined to HO .......................................................................... 11–12 Figure 231. New Query Window – Table XC Selected .......................................................... 11–13 Figure 232. Join Criteria - HO Joined to XC ........................................................................... 11–14 Figure 233. Join Criteria Window – LCNSEIHO Selected ..................................................... 11–15 Figure 234. New Query Window for Multi-Table Query ........................................................ 11–15 Figure 235. Where Criteria Window – Table XC Selected ..................................................... 11–17 Figure 236. Sort (Order By) Criteria Window......................................................................... 11–18 Figure 237. Query Results for New Query – 41 Rows Returned ............................................ 11–19 Figure 238. Adhoc Comments Window .................................................................................. 11–20 Figure 239. Query Save Window ............................................................................................ 11–21 Figure 240. Navigator – AdHoc>>Recall Query..................................................................... 11–23 Figure 241. Query Save Window – Recalling Saved Queries ................................................. 11–24 Figure 242. Recall Query Window – XC.UOCSEIXC ‘LH3’ ................................................ 11–25 Figure 243. Query Results Window – 'LH3' Usable on Code ................................................. 11–25 Figure 244. New Query – Table HG ....................................................................................... 11–26 Figure 245. Where Criteria Window - SMRCODHG ............................................................. 11–27 Figure 246. Editing Data in the Query Results Window ......................................................... 11–28 Figure 247. Where Criteria Window ....................................................................................... 11–29 Figure 248. New Query Window – MC% ............................................................................... 11–30 Figure 249. Query Results for New Query – Alt Editor .......................................................... 11–31 Figure 250. Alt Editor – Cells Copied ..................................................................................... 11–32 Figure 251. Query Results Window – Key Field Changes ...................................................... 11–34 Figure 252. Security Violation .................................................................................................. 12–4 Figure 253. Unique Constraint Violation – Key Values Exist .................................................. 12–5 Figure 254. Integrity Constraint Violation – Parent Key Not Found ........................................ 12–6 Figure 255. Integrity Constraint - Child Record Found ............................................................ 12–7 Figure 256. Cross Edit Violation Message ................................................................................ 12–8 Figure 257. Rule Bound to a Column Error Message (Oracle) ................................................. 12–9 Figure 258. Navigator-Assign LCNs to BOM ............................................................................ A–3 Figure 259. Automatically Assign LCNs ................................................................................... A–4 Figure 260. EAGLE: Clipboard Format Pop Up ........................................................................ A–5 Figure 261. Automatically Assign LCNs Window – Top Shown .............................................. A–5 Figure 262. Automatically Assign LCNs Window – Bottom Shown ......................................... A–6 Figure 263. Clipboard Format-Paste Clipboard ......................................................................... A–6 Figure 264. Automatically Assign LCNs – Clipboard Data Added ........................................... A–7 Figure 265. Automatically Assign HG Indenture Codes? .......................................................... A–8 Figure 266. Automatically Assign LCNs- Calculate LCNs ....................................................... A–8 Figure 267. Database Error Messages Window ......................................................................... A–9 Figure 268. Automatically Assign LCNs - Addl Parts/TM Data ..............................................A–10


THE EAGLE

INTERFACE

SECTION 1

EAGLE WORKBOOK DEF STAN 00-60 SECTION 1 THE EAGLE INTERFACE

1-3

SECTION 1 THE EAGLE INTERFACE

1.0 INTRODUCTION

This section provides a brief overview of the Enhanced Automated Graphical Logistics

Environment (EAGLE).

1.1 CONVENTIONS USED IN DOCUMENTATION

Before using EAGLE, it is important to understand the terms and notation conventions used in the

documentation.

1.1.1 General Conventions

The word “choose” is used for carrying out a menu command or a command button in

a dialog box.

The word “select” is used for highlighting the object that the next action is to affect,

and for selecting a specific dialog box option.

Commands that are chosen are given with the menu name preceding the command

name. For example, the phrase “choose File>>Open Project ...” means choose the

Open Project... command from the File menu. This naming convention describes the

sequence that should be followed in choosing a command --- select the menu first,

and then choose the command.

Data fields that should be entered by the user into the application are enclosed in

single quotation marks preceded by the words ‘type in’ or ‘enter’.

The word “Discipline” applies to a main area or application within EAGLE. For

example, the Provisioning Discipline or the Task Analysis Discipline.

The word “Function” or “Discipline Function” applies to the individual functions

within a discipline. For example, the Provisioning Discipline has a Provisioning

Finder Function, an Enter New Part Function, and a UOC Maintenance Function.

The word “STEP” is used to indicate that the following instructions are steps that

should be performed by the user while taking the training class. Each step or user

action is preceded by a bullet symbol (• ).

Button names, key stroke combinations, menu items and tabs are in bold print to help

emphasize what is being typed in or selected with the mouse.


1-4

1.1.2 Mouse Conventions

The word “click” means to press and immediately release the mouse button without

moving the mouse. For example, “Click on OK”.

The phrase “double-click” means to click the mouse button twice in rapid succession.

For example, “Double-click the EAGLE icon to start EAGLE”.

The phrase “drag” means to press and hold the mouse button while you move the

mouse; then, release the button.

1.1.3 Keyboard Conventions

Key names match the names shown on most keyboards and appear in bold caps. For

example the Shift key appears as SHIFT.

A plus (+) sign used between two key names indicates both keys must be pressed at

the same time. For example, “Press SHIFT+F1 means press the Shift key and hold it

down while you press the F1 key.

A comma (,) between two key names indicates that those keys must be pressed

sequentially. For example, “Press ALT+F,O“ means press the Alt key and the F key

at the same time and release them, and then press the O key and release it.

1.1.4 Window Conventions

Initial windows for most Discipline Functions (applications) are Data Finders. The

menu and toolbars provide the primary methods of performing processes within the

Data Finders.

Editable items in a window have a white background while objects that can’t be

edited have a silver background.

Windows do not have close buttons on them. When the user is done with a window,

any data changes should be saved and the window should be closed by clicking the

appropriate icon in the window title bar.

Response windows cannot be closed using the normal window conventions. They

will have an Ok or Cancel button for response, and they will close upon completion.

Checkboxes are square objects on a window that allow selection of certain criteria.

They are designed so that more than one checkbox can be checked at a time.


1-5

Radio buttons are circular objects on a window that allow selection of certain criteria.

They are designed so that only one radio button can be selected at a time.

Tabs exist on a window providing methods of accessing different areas of the

window. When a tab is clicked on, the window changes to reflect the tab information.

When an item is deleted using the Delete button, the deletion doesn’t take place until

the Save button is chosen. The only exception to this rule is in the Drawing

Application since drawings may be stored in a different database than the LSAR data.

1.1.5 End Items and Student Ids

The workbook makes reference to End Item ‘Bicyclexx’ and Ids such as ‘Studentxx’.

The ‘xx’ is used as a placeholder for specific assigned numbers like ‘01, 02, 03’ etc.

During training classes with a number of students present, specific numbers for the

‘xx’ placeholders will be provided. Always utilize the specific number assigned

when entering data for training purposes.

1.2 ADMINISTRATION

1.2.1 Administrative User Ids and Passwords

Database Administrator

The Database Administrator (EAGLE) is a special userid. Logging on with this

userid gives one the ability to create, modify, and/or delete database objects, act as

the Security Administrator and work with the data in the database regardless of

EAGLE Security or ORACLE standard security. The default password for the

database administrator can be obtained from the EAGLE help desk.

Security Administrator

The Security Administrator (EAGLESA) is another special userid. Using this id

allows one to create users on the system. It does not have DBA authority, cannot

manipulate any data in the LSAR tables and cannot use the EAGLE disciplines. The

security administrator has the responsibility to define users and resources to EAGLE

Security System. The default password for the security administrator can be obtained

from the EAGLE help desk.


1-6

1.3 STANDARDS AND EAGLE LSAR DATABASE CONFIGURATIONS

EAGLE LSAR is compliant with the following Standards:

DEF STAN 00-60

MIL-STD-1388-2B

GEIA-STD-0007

For your specific system to operate as designed, System and End Item settings must be made.

1.3.1 DEF-STAN-00-60

1.3.1.1 System Default Settings

As shown in Figure 1 DEF STAN 00-60 has been selected from the Specification Type drop

down list. DEF STAN 00-60 ISSUE 3 has been selected from the Country Code drop down list.

These two fields are required for the DB to operate per the specification. The Use Database

Triggers checkbox is checked and should always be checked unless a specific purpose has been

identified. Please contact the EAGLE Help Desk in this case for direction.

Figure 1. System Defaults – DEF STAN 00-60


1-7

1.3.1.2 End Item Default Settings

As shown in Figure 2 an End Item record has been created for End Item ‘Bicyclexx’. Issue 5 has

been selected from the Specification Issue/Revision field. This End Item record must be

established prior to LSAR data being entered into the DB.

Figure 2. End Item Defaults – Issue 5 Selected

1.4 LOGGING IN TO EAGLE

In order to access an EAGLE logistics database, a user must log in as shown in Figure 3. The

information required to log in includes a user name, password, and database server name. The

information for accessing the various databases should be provided to the user by the EAGLE

system administrator. After entering all the required information, choose OK to log on to the

database.

Note: It is possible that your database is case sensitive and may require the user to use upper case

or lower case.

To log in to EAGLE, enter the appropriate data on the EAGLE Login screen as shown in Figure

3. This data will be used to log the user onto the LSAR database:

Enter the User Name, User Password, and Database Server information provided by

the EAGLE instructor or your system administrator

Choose the button to log in to the EAGLE database


1-8

Figure 3. EAGLE Login Window

1.5 THE NAVIGATOR

Once logged into EAGLE, the Navigator (Figure 4) is displayed within the Main screen. The

Navigator has a Home tab a Favorites tab and a Recent tab as well as a Filter for ease of

navigation to the desired Discipline and Discipline(s) Functions.


1-9

Figure 4. The Navigator Tree View

Utilizing the Expand Icon to the left of the Disciplines will display the various ‘Functions’ –

specific application programs contained within Disciplines – beneath the Disciplines as shown in

Figure 5

In Figure 5 the Navigator is shown with the AdHoc Discipline expanded and the Recall Query

function selected. The default header is displayed. This header is editable. Please contact the

EAGLE Help Desk for information regarding this feature.


1-10

Figure 5. AdHoc Discipline – Visual Query Builder Function Selected

1.5.1 Using Navigator Functions

In EAGLE, data to be reviewed or maintained is usually located using a type of Navigator

Function known as a Data ‘Finder’. Finders consist of two basic parts; the Search Criteria input

boxes and the Record Retrieved window. Generally, retrieved records are not editable in the

Retrieved Record window. Other Functions in the Navigator allow records to be added, changed

or deleted.

1.5.2 Home Tab Functions

1.5.2.1 Home Tab Filter

As shown in Figure 6 with the Home tab selected and entering the word ‘TASK’ in the Filter box,

the Navigator is filtered to return only Disciplines with Functions that contain the word ‘TASK’.


1-11

To clear the filtering, click the icon to the right of the Filter box

Figure 6. Navigator Home Tab – Filter Applied.

1.5.2.2 Basic Finder

As mentioned. Finders consist of two basic parts; the Search Criteria input boxes and the Record

Retrieved window.

As shown in Figure 7, the Navigator Home tab is selected, ‘PROV’ has been entered in the Filter

field and the Provisioning Discipline has been expanded and the Provisioning Finder function has

been selected. Double-clicking on the Provisioning Finder function or choosing the

button on the Main toolbar will result in the Provisioning Finder window being displayed (Figure

8).


1-12

Figure 7. Navigator Home Tab – Provisioning Finder Function Selected

A typical EAGLE Finder window is displayed as shown in Figure 8. No records are returned as

yet. The Finder window will allow for filtering by entering data in the Finder fields or by clicking

available checkboxes contained in the window. In this case the Display Only Parts that Have

An Application checkbox is checked.

Figure 8. Provisioning Finder


1-13

With the Reference Number filter ‘C%’ entered and the Display Only Parts That have an

Application checkbox checked, clicking the button on the Main toolbar will result in a

query being performed and the records displayed as shown in Figure 9.

Figure 9. Provisioning Finder – Records Returned C% Filter

1.5.3 Favorites Tab Functions

As shown in Figure 10, the Favorites tab is selected in the Navigator and the button is

displayed on the Function Specific toolbar. Clicking the Man. Favs button will result in the

Manage Favorites window being displayed.


1-14

Figure 10. Favorites Tab – Manage Favorites

As shown in Figure 11, click on the Function desired, click the button and then

choose the button on the Main toolbar to add a favorite. Choose the

button to remove a Favorite.

Figure 11. Manage Favorites Window - Add


1-15

1.5.4 Recent Tab Function

As shown in Figure 12, the Recent tab is selected in the Navigator. The five most recent functions

having been utilized are displayed. You may access the desired functions finder by clicking the

record.

Figure 12. Recent Tab – Recently Utilized Functions

1.5.5 Classic Navigator

If desired, the Classic Navigator is available for use. As shown in Figure 13, you may select

File>>Open from the Main toolbar. This will result in the Classic Navigator being displayed for

use (Figure 14).


1-16

Figure 13. Main Screen – File>>Open

The Discipline(s)/Function(s) available in the Classic Navigator will be as they were with the

Tree Navigator. At the time the User ‘Studentxx’ was created, the Users Navigator was modified.

The Disciplines and Discipline Functions remain the same for user ‘Studentxx’ with either the

Classic or Tree Navigator selected.

Figure 14. Classic Navigator – AdHoc>>New Query

To return to the New Navigator once the Classic Navigator has been chosen, you may select

File>>Close from the Main toolbar.


1-17

1.6 EAGLE MAIN SCREEN HEADER

The Main Screen header (Figure 15 yellow rectangle) displays which User is logged in, the server

logged into and the EAGLE client Version being utilized and the Build number of the client.

Figure 15. EAGLE Main Screen - Header

1.7 THE MENU BAR

The Menu bar (Figure 16 yellow rectangle) is similar to other graphical control elements which

contain drop down menus. The menu bar supplies a common area for window and application

specific menus to provide access to functions such as, copy, save edit and find/replace.

Additionally, a Reports/Process item and Tools selection are provided for more specific EAGLE

functionality.

Figure 16. EAGLE Main Screen – Menu Bar


1-18

1.8 THE MAIN TOOLBAR

The Main Toolbar, illustrated in Figure 17 (yellow rectangle), is displayed at the top of the

EAGLE Window. This toolbar contains buttons that perform generic functions used throughout

EAGLE and remains the same for all disciplines. Commonly used functions such as Print, Undo,

Cut, Copy, Paste, Clear, Execute, Save, Insert, Delete, Drawing, Artwork, Exit, Help and Item

Help are available here. The Main toolbar buttons are enabled and disabled depending on their

applicability to the discipline/function being used.

Figure 17. Main Toolbar

1.8.1 EAGLE Help

A Help button that retrieves a menu with indexed contents that can be searched on keywords or

strings is available from the Main Toolbar. Topics are logically linked and structured to answer

frequently asked questions. Bookmarks can be defined for quick reference to often-visited topics

and a History button logs the path of activity for easy retrieval of an earlier topic. In addition to

EAGLE help information, the Help button provides access to the on-line version of DEF STAN

00-60.

1.8.2 Item Help

The Item Help button is used for context sensitive help. A single click toggles the item help

enabling the user to display specific Help for a window, database table or field. When Item Help

is enabled, a “?” shadowing the cursor indicates help is available. Clicking on the window

displays the Help topic for that area of the window. (This can be a help topic for the window, a

database table or a field). When the Item Help cursor is active, a single click of the Item Help

button will disable item help.

1.8.3 DB Help

The Database Schema Help function provides access to dynamic database schema help. When

selected, the Database Schema Help function will launch a Table Explorer window.


1-19

1.8.4 Graphical Functions

Artwork and Drawing buttons on the Main toolbar provide links to engineering drawings or

supporting illustrations. When cross references to engineering drawings or artwork have been

established for a CAGE Code/Reference Number combination selected in a Finder, the Artwork

and/or Drawing buttons are activated. Clicking the Artwork or Drawing button will display the

graphical file in the EAGLE Viewer. Use of the functions in the Graphics Discipline, including

addition of artwork/drawings and creation of cross-references is detailed in the EAGLE Additional

Disciplines manual.

1.9 REPORTS/PROCESS MENU AND FUNCTION SPECIFIC TOOLBARS

The Reports/Process menu displays a list of topics for which more information is available. It also

displays a summarized list of applicable data reports. The information displayed in this menu will

vary depending on which Discipline/Function is currently active. Once a topic is selected from the

list, the data relating to that topic will be displayed in a window for further manipulation. In

addition, the Reports/Process menu provides access to all standard LSAR reports applicable to the

active discipline.

Figure 18. Function Specific Toolbar


1-20

The Function Specific Toolbar is located left of the Navigator window. The buttons perform the

same functions as the options listed under the Reports/Process menu and provide a short cut to

using the menu. Figure 18 illustrates a sample Function Specific toolbar.

1.9.1 Using the Reports Process Menu or Function Specific Toolbar

To use the Reports/Process Menu or Function Specific Toolbar

1. From the appropriate Data Finder, click on the desired record from the records retrieved

section.

2. Select the Reports/Process Menu (ALT+R) and click on the topic category of interest.

Or, click the equivalent button from the Function Specific Toolbar. (In general, the topic

category of interest represents the various tables covered by the discipline.)

3. All data relating to the topic will be displayed in a window with the Data Finder’s key

fields displayed in gray at the top. From here the data for the retrieved record may be

changed, deleted or inserted in the provided data window.

4. Adding and deleting data in editable fields is accomplished by selecting the information

in the data window and choosing Insert or Delete buttons from the Main Toolbar or the

Data Menu (ALT+D). Data modifications may be made by typing the data into the data

window directly or by cutting and pasting like most Window applications.

5. Once data entry is complete, the record must be saved to have it posted to the database by

pressing the Save button from the Main Toolbar or ALT+D,S.

1.10 SELECTING END ITEM

The DEF STAN 00-60 version of EAGLE uses end item to control access to the data in the

database. Therefore, an end item must be selected prior to using EAGLE. Clicking the

button at the left of the Main toolbar will result in the ‘Please Select an end Item’ window (Figure

19) being displayed. Once an end item has been selected as shown in Figure 19, it can be saved in

the configuration setup so that the next time EAGLE is run, the end item will be defaulted. This

end item selection is used by all the EAGLE disciplines, therefore eliminating the need for the

user to select an end item from end item drop down list boxes as is required in other versions of

EAGLE. Only End Items for which the user has been assigned privileges are available.


1-21

You may utilize the Filter: box to assist in selecting the correct End Item.

Figure 19. Select an End Item Window

1.11 DISCIPLINE OUTPUTS

The majority of the Navigator Disciplines provide methods of saving data to external files. The

AdHoc Discipline has a unique way of saving the output of queries. For more information on

saving the output from the AdHoc Discipline, refer to Paragraph 11.1.3.2. Most of the remaining

disciplines allow data displayed on a window to be saved to a file.

Data that is displayed in Maintenance Windows (windows that allow editing of data) may be

saved in most of the disciplines. The Data is saved by using the File>>Save As menu item or

ALT-F, A. After the File>>Save As menu item has been chosen, the Save Rows As Window,

illustrated in Figure 20, is displayed prompting the user for the name and type of file to save the

database rows in.

Once the data has been saved to a file, it can be accessed whenever necessary using an appropriate

application. For example, if the data is saved in Excel Format (*.XLS), Microsoft Excel should be

used to access the data for future use.


1-22

Figure 20. Save Rows As Window


ENTERING CROSS

FUNCTIONAL DATA

SECTION 2

EAGLE WORKBOOK DEF STAN 00-60 SECTION 2 ENTERING CROSS FUNCTIONAL DATA

2-3

SECTION 2 ENTERING CROSS FUNCTIONAL DATA

2.0 INTRODUCTION

This section provides an overview of the cross functional tables (X tables) of DEF STAN 00-60.

The key data elements of the X Tables form a common thread that serves to tie together the

various logistics considerations documented in a DEF STAN 00-60 database. With few

exceptions (facilities requirements and personnel skills considerations) X table data must be

established prior to populating other tables.

Note: It is important to remember that an End Item Default record must be established before

data can be created against the specific end Item. See 1.3.1.2 before proceeding to 2.1

When establishing an EAGLE relational database, the first table that must be populated is table

XA. The XA table establishes the key field of End Item Acronym Code (EIAC) which is used to

distinguish the end item documented in the relational database. The end item is broken down

(either physically or functionally) in table XB with the introduction of key fields of LCN, ALC

and LCN Type.

2.1 ESTABLISHING AN END ITEM ACRONYM CODE

Creating the EIAC and LCN Structure is the first step in establishing an EAGLE logistics

database.

STEP To create an EIAC and LCN structure do the following as shown and described:

Choose the button on the Main toolbar and select the ‘TRAININGXX’

End item available

Access the LCN Maintenance Discipline from the Navigator utilizing the Home tab

and Filter box as shown in Figure 21 and double-click End Item (XA) Maintenance


2-4

Figure 21. Navigator - End Item (XA) Maintenance

The End Item Data Maintenance window will be displayed (Figure 22) with

‘Records:0’

Figure 22. End Item Data Maintenance Window - TRAININGXX End Item

Data may be entered into the End Item Data Maintenance window using the mouse and the

keyboard. Once all information has been entered, the Save button must be chosen to add all data

displayed on the screen to the database.


2-5

Info: This step will illustrate adding a new EIAC and LCN Structure in the XA table as shown

in Figure 23. This example uses an LCN structure of ‘1322222211’. This implies that an

LCN may have up to 10 indenture levels with the LCNs first indenture level being a one

digit character (i.e. LCN ‘A’) and the LCNs second indenture level having three

additional characters (i.e. LCN ‘A001’). Note that the LCN structure of ‘1322222211’ is

a total of 18 characters which is the maximum number of characters allowed for an LCN

structure. Also, if an LCN is longer than the length of the LCN Structure, the LCN

indenture code is mandatory. For example, if the LCN Structure is ‘42222’, any LCN

longer than 12 requires an LCN indenture code.

Activate the End Item Data Maintenance screen for Insert (Figure 23) by clicking in

the window

Choose the Insert button on the Main toolbar

Enter ‘TRAININGXX’ in the End Item field as shown in Figure 23

Enter ‘1322222211’ into the LCN Structure box

Figure 23. End Item Data Maintenance Window - TRAININGXX End Item

Scroll to the right and enter '1995' in the Initial Bin Cost box (Figure 24)

Select 'Pound Sterling' from the Initial Bin Cost Cur. Code drop down list box

After this data has been entered, choose the Save button on the Main toolbar


2-6

Figure 24. End Item Data Maintenance – Scrolled Right

Close the End Item Data Maintenance window

Note: The ‘TRAININGXX’ end item was added in this step to illustrate how to add a new end

item. For training purposes, an end item has been established containing bicycle data.

Therefore, the end item used for the remainder of the workbook will be the BICYCLEXX

end item assigned by the EAGLE instructor (BICYCLE01, BICYCLE02, etc.)

2.2 ASSIGNING LCNs

The LSA Control Number Data Maintenance window is used to add an EIAC, LCN, ALC, LCN

Type, and all other XB table information.

To illustrate adding of LCNs, a top level LCN and a lower level LCN will be added. To add a top

level LCN, which signifies an ‘A’ indenture level or end item LCN, we will enter the following

data as shown in Figure 27. In this example the LCN type of ‘P’ is used to represent a physical

LCN. An ‘F’ for functional LCN is also allowed in the logistic or LCN tables; however, only

LCN type ‘P’ is allowed in the provisioning tables.

STEP To assign an LCN, access the LCN Maintenance Discipline using the Navigator Home

tab and Filter box and select LCN (XB) Maintenance as illustrated in Figure 25. Before

assigning LCNs, an EIAC must exist in the XA table. If an EIAC does not exist, refer to

Paragraph 2.1.

Make sure the BICYCLEXX end item assigned by the EAGLE instructor is selected

(Figure 27)

Double-click the LCN (XB) Maintenance function as shown in Figure 25


2-7

Figure 25. Navigator - LCN (XB) Maintenance

The LSA Control Number Data Maintenance finder window is displayed

Choose the Execute button on the Main toolbar to view the existing Table XB records

(LCNs) (Figure 26)

Figure 26. End Item Bicyclexx – XB Records


2-8

Choose the button on the Main toolbar

The End Item is defaulted to the selected end item as shown in Figure 27

Enter ‘A’ into the LCN box

Enter ‘02’ into the ALC (for alternate LCN of 2) box

Enter ‘P’ (for LCN type of Physical) into the Type box

Enter ‘TRAINING BICYCLE’ into the LCN Name box

Enter ‘A’ into the LCN Indenture Code box

Figure 27. LSA Control Number Data Maintenance Window

Because an XC record (System/EI) will be established for this record in a later exercise, do the

following as shown in Figure 28 and described:

Scroll to the right and choose ‘End Item’ from the Sys. End Item Identifier box

In addition, to enable Reliability and Maintainability Information to be documented, a RAM

Indicator Code of ‘Y’ is required. To set this value, do the following:

Scroll to the right and choose ‘RAM info documented/LCN’ from the R.A.M.

Indicator box


2-9

In addition, transportation information may be documented against this LCN at a later date, so a

valid Sect. Item Transp. Indic. is required. To set this value, do the following:

Scroll to the right and choose ‘Sectionalized item’ from the Sect. Item Transp. Indic.

box (Figure 28)

Figure 28. LSA Control Number Data Maintenance Window - Adding Sys EI Identifier

In addition, ILS Logistic Decision Office and Engineering Authority Logistic Decision Office data

are to be entered. To enter this data, do the following as shown (Figure 29) and described:

Scroll to the right and enter 'LOGISTICS' in the ILS Logistic Decision Office box

Enter 'ENGINEERING' in the Eng. Auth. Logistic Decision Office box.


Figure 29. LSA Control Number Data Maintenance Window - Logistics Decision Office


2-10

STEP To illustrate adding a lower level LCN, enter the following data (Figure 30):


Choose the Insert button on the Main toolbar. The End Item is defaulted to the

selected end item

Enter ‘A01’ into the LCN box


Enter ‘P’ (for LCN type of Physical) into the Type box

Enter ‘FRAME ASSEMBLY’ into the LCN Name box

Enter ‘B’ into the LCN Indenture Code box


Figure 30. LCN Data Maintenance – ‘A01’ Entered

Choose the Execute button on the Main toolbar to retrieve all LCN records against

the BICYCLE end item you have been assigned

Note: In these examples, the lower level LCN entered was neither a system or end item;

therefore, the System/End Item Identifier box was left blank. In addition, transportation

information will not be added so the Sect. Item Trans. Indic. box was left as the default

‘Not Sectionalized’ and RAM information will not be added so the R.A.M. Indicator box

was left as the default ‘RAM info. not documented/LCN’.


2-11

STEP To illustrate adding another lower level LCN, do the following as shown in Figure 31 and

described:

Scroll down the LCN list and select LCN ‘A03’ with ALC ‘00’

Figure 31. LCN Data Maintenance Window – ‘A03’ Selected

Choose Data>>Duplicate Record on the Main toolbar to insert a record above the

highlighted record

Enter ‘02’ into the ALC (for alternate LCN of 2) box as shown in Figure 32 for the

new record


2-12

Figure 32. LCN Data Maintenance Window – ‘ALC 02’


STEP To view the LCNs added in the above paragraphs, do the following. Figure 33 illustrates

the ‘BICYCLEXX’ LCNs with ALC ‘02’:

Enter ‘02’ into the ALC query box at the top of the window

Choose the Execute button on the Main toolbar to retrieve the records (3)

Close the LSA Control Number Data Maintenance window

Figure 33. LCN Data Maintenance Window – ALC ‘02’ Records


2-13

2.3 ASSIGNING A PCCN and UOC TO SYSTEM / END ITEM LEVEL LCN

STEP To assign a PCCN and UOC to a system or end item level LCN, access System/EI (XC)

Maintenance from the LCN Maintenance Discipline using the Navigator and Filter box as

shown in Figure 34:

Note: If Paragraph 2.2 was not completed, the LCN data needed for this paragraph will not

exist. Without this data, PCCNs and UOCs cannot be assigned.

At this point, a top level LCN of ‘A’ with lower level LCNs of ‘A01’ and ‘A03’, all ALC ‘02’

have been added. A UOC/PCCN is added to LCNs representing a system/end item or an ‘A’

indenture coded item. Lower level LCNs are linked to a UOC/PCCN through its corresponding

system/end item LCN/ALC. In the following exercises, a UOC/PCCN will be added for the top

level LCN ‘A’ in table XC and then the lower level LCN ‘A01’ will be linked to this UOC/PCCN.

STEP To illustrate adding a UOC and a PCCN to a system/end item or LCN with an indenture

level of ‘A’, do the following as shown in Figure 34 and described:


Double-click the System/EI (XC) Maintenance function as shown in Figure 34

The System/EI Maintenance finder window is displayed

Figure 34. Navigator - System/EI (XC) Maintenance


2-14

Make sure the Show only System/End Item LCNs checkbox is checked as shown in

Figure 35

Choose the Execute button on the Main toolbar or ALT-Q,E to query the database

After data is returned, select the record with LCN ‘A’ and ALC ‘02’

Figure 35. System/End Item Maintenance – LCN ‘A’ ALC ‘02’ Selected

Scroll to the right so that the UOC and PCCN columns are displayed in the window as

shown in Figure 36

Enter ‘TR1’ into the UOC box

Enter ‘H5T80B’ into the PCCN box

After this data has been entered chose the Save button on the Main toolbar

Close the System/End Item Maintenance window


2-15

Figure 36. System/End Item Maintenance Window – UOC and PCCN

2.4 MAPPING LCNS TO SYSTEM/END ITEM UOCS

STEP To map LCNs to UOCs representing system/end item level LCNs, access LCN to System

/EI (XF) Maintenance from the LCN Maintenance Discipline using the Navigator and

Filter box as shown (Figure 37) and described:


Double-click the ‘LCN to system/EI (XF) Maintenance function as shown Figure 37

Figure 37. Navigator - LCN to System/EI (XF) Maintenance


2-16

The LCN System/End Item UOC Maintenance window will be displayed

Enter ‘2’ into the ALC search criteria box as shown in Figure 38

Choose the Execute button on the Main toolbar to retrieve the data

Make sure that the record with LSA Control Number (LCN) = ‘A’, ALC=’02’, and

LCN Name ‘TRAINING BICYCLE’ is selected in the upper portion of the window

Select the record with the LCN ‘A’ and UOC ‘TR1’ from the scrolling list box on the

bottom left of the window

Choose the button to add the UOC to LCN ‘A’, ALC '02'.

Choose the Save button on the Main toolbar

Your screen should reflect Figure 38 at this point

Figure 38. LCN System/End Item UOC Maintenance Window – LCN A

Select the record with LSA Control Number (LCN) = ‘A01’, ALC=’02’, and LCN

Name ‘FRAME ASSEMBLY’ in the upper portion of the window as shown in Figure

39

Select the record with the LCN ‘BIKE’ and UOC ‘TR1’ from the scrolling list box on

the bottom left of the window


2-17

Choose the button to add the UOC to LCN ‘A’, ALC '02'


Figure 39. LCN System/End Item UOC Maintenance Window – LCN A01

Select the record with LSA Control Number (LCN) = ‘A03’, ALC=’02’, and LCN

Name ‘DRIVE ASSEMBLY’ in the upper portion of the window as shown in Figure

40

Select the record with the LCN ‘A’ and UOC ‘TR1’ from the scrolling list box on the


Choose the button to add the UOC to LCN ‘A03’, ALC '02'.


Close the LCN System/End Item Usable On Code Maintenance window

Note: When an HO record is added for physical LCN types (LCN Type of 'P'), a corresponding

XF record is generated automatically if the user has not done so.


2-18

Figure 40. LCN System/End Item UOC Maintenance Window – LCN BIKE03

In the previous steps, a new bicycle configuration (LCN 'A', ALC '02') was established as well as

two lower level LCNs (LCN 'A01', ALC '02' and LCN 'A03', ALC '02') that make the new bicycle

a distinct configuration. Items that are common between the new bicycle configuration and the

baseline bicycle configuration (LCN 'A', ALC '0') can be added to the new bicycle configuration

by mapping the baseline items to the new bicycle configuration using the LCN System/End Item

Usable On Code Maintenance Window (Figure 38, Figure 39, Figure 40).

2.5 ASSIGNING SERIAL NUMBER UOCS TO SYSTEM/END ITEM LCNS

When documenting complex systems where small quantities of a particular configuration may

exist (aircraft, ships, satellites, etc.), configuration is often documented by serial number. Serial

number ranges that comprise a configuration and the corresponding system/end item UOC are

stored in Table XD.


2-19

STEP To assign a serial number UOC to a system/end item level LCN, access System/EI SN

(XD) Maintenance from the LCN Maintenance Discipline using the Navigator Home tab

and Filter box as shown in Figure 41

Note: A top level LCN with an associated PCCN and UOC must exist to assign a serial number

UOC.


Double-click the System/EI SN (XD) Maintenance function as shown in Figure 41

Figure 41. Navigator – System/EI SN (XD) Maintenance

The System/End Item Serial Number Maintenance window will be displayed

Enter ‘A’ into the (LCN) finder field as shown in Figure 42


Select the record with LCN of ‘A’ and ALC of ‘02’

Click in the right portion of the window under Serial Number Range: (nothing

happens)

Figure 42. System/End Item Serial Number Maintenance Window


2-20


Blank data fields should appear (Figure 43)

Figure 43. System/End Item Serial Number Maintenance – ALC ‘02’

Enter ‘100’ into the From: box as shown in Figure 44

Enter ‘200’ into the To: box

Enter ‘A’ into the S/N UOC box

After this data has been entered choose the Save button on the Main toolbar

Close the System/End Item Serial Number Maintenance window

Figure 44. System/End Item Serial Number Maintenance – S/N UOC: A


2-21

2.6 MAPPING LCNs TO SYSTEM/END ITEM SERIAL NUMBER UOCs

When configuration control is managed by serial number, LCNs are mapped to the system/end

item serial number range on which they are used by the system/end item serial number UOC. The

cross reference information between LCNs (from Table XB) and the system/end item serial

number UOC (from Table XD) is established in Table XE.

STEP To map an LCN to a Serial Number UOC, access LCN to S/N UOC (XE) Maintenance

from the LCN Maintenance Discipline using the Navigator Home tab and Filter box as

shown in Figure 45

Note: A system/end item serial number UOC must exist for an LCN to be tied to a serial

number UOC. We did this in the previous STEP.


Double-click the LCN to S/N UOC (XE) Maintenance function as shown in Figure 45

The LCN to Serial Number Usable On Code window is displayed

Figure 45. Navigator - LCN to S/N UOC (XE) Maintenance

Enter ‘2’ into the ALC finder box as shown in Figure 46


Notice in Figure 46 that the bottom left hand part of the screen displays LCNs from

Table XB


2-22

Select the record with LCN ‘A’, ALC of ‘02’ and S/N UOC of ’A’ from the box in

the middle of the window as shown in Figure 47

Select the record with LCN ‘A’ and ALC of ‘02’ from the scrolling list box on the


Choose the button to map LCN ‘A’, ALC of ‘02’ to the S/N UOC of

‘A’ (serial numbers 100 to 200 of LCN ‘A’, ALC ‘02’)

Choose the Save button on the Main toolbar to save the data record to Table XE

Figure 46. Mapping of LCNs to Serial Number UOCs

Map LCN 'A01' and ALC of '02' to the S/N UOC of ‘A’ as described in the previous

three bullets

Choose the Save button. Your screen should reflect Figure 47


2-23

Figure 47. LCN to Serial Number Usable On Code Window – LCN ‘A01’

Map LCN 'A03' and ALC of '02' to the S/N UOC of ‘A’ as described in the previous

three bullets

Choose the Save button. Your screen should reflect Figure 48


2-24

Figure 48. LCN to Serial Number Usable On Code Window – LCN ‘A03’

Close the LCN to Serial Number Usable On Code window

2.7 ADDING CAGE CODES

CAGE Codes can be added through the LCN Maintenance Discipline or the Provisioning

Discipline. Paragraph 10.1.1 addresses addition of CAGE codes using the Provisioning

Discipline. This paragraph will address adding CAGE codes using the LCN Maintenance

Discipline. The best method to add multiple CAGE codes into the database is using the LCN

Maintenance Discipline. The Provisioning Discipline provides a method to add new CAGE codes

when adding reference numbers as a convenience for entering the data in one place.

Info: Before reference (part) numbers may be entered into the relational database, CAGE

Codes (source of supply information) must be established in the XH table. As shown in

Figure 50, the CAGE Code Data Maintenance Window is used to enter a source of

supply’s CAGE, Name, and address information into table XH.


2-25

STEP To add a new CAGE Code, access the LCN Maintenance Discipline using the Navigator

Home tab and Filter box as shown in Figure 49 and select CAGE (XH) Code

Maintenance:

Double-click the CAGE Code (XH) Maintenance function as shown in Figure 49

Figure 49. Navigator - CAGE Code (XH) Maintenance

The CAGE Code Data Maintenance window is displayed

STEP To illustrate adding CAGE information, do the following as shown in Figure 50 and

described. Note: The only required field is CAGE Code:

Make sure the BICYCLEXX end item assigned by the EAGLE instructor is displayed

in the header

Click in the screen (nothing happens)

Choose the Insert button on the Main toolbar. A blank row is inserted

Enter ‘12345’ into the CAGE box as shown in Figure 50

Enter ‘EDINBURGH BICYCLE CO-OP’ into the Name box

Enter ’8 ALVANLEY TERRACE’ into the Street box

Enter ‘BRUNTFIELD EDINBURGH’ into the City box

Scroll to the right and enter ‘UK’ into the State box

Enter ‘SCOTLAND’ into the Nation box.

Enter ‘EH9 1DU’ into the Postal Zone box



2-26

Click the button to view the additional information

fields available

Close the Additional CAGE Code Data Maintenance window

Close the CAGE Code Data Maintenance window

Figure 50. CAGE Code Data Maintenance Window - Adding CAGE Information

2.8 ADDING REFERENCE NUMBER INFORMATION

Reference numbers can be added through the LCN Maintenance Discipline or the Provisioning

Discipline. Paragraph 10.1.2 addresses addition of reference number data using the Provisioning

Discipline. This paragraph will address addition of reference numbers using the LCN

Maintenance Discipline.

STEP To add a new reference (part) number, access the LCN Maintenance Discipline using the

Navigator Home tab and Filter box and select Part (HA) Maintenance as shown in Figure

51:

Double-click Part (HA) Maintenance as shown in Figure 51


2-27

Figure 51. Navigator - Part (HA) Maintenance

The Part Number Data Maintenance window is displayed

Make sure the BICYCLEXX end item assigned by the EAGLE instructor is displayed

in the header

Choose the Insert button on the Main toolbar. A blank row is inserted

Note: Before assigning reference numbers, the manufacturer’s CAGE code must exist in the

XH table. If it does not, refer to Section 2.7 on how to add a CAGE code.

Enter ‘12345’ into the CAGE Code box as shown in Figure 52

Enter ‘MC-TBIKE’ into the Reference Number box

Enter ‘BICYCLE ASSEMBLY’ into the Item Name box


Figure 52. Part Number Data Maintenance - Adding Reference Number Information


2-28

STEP Enter a second reference number by doing the following:


Enter ‘12345’ into the CAGE Code box as shown in Figure 53

Enter ‘TFRAME’ into the Reference Number box

Enter ‘FRAME ASSEMBLY’ into the Item Name box


Close the Part Number Data Maintenance window

Figure 53. Part Number Data Maintenance - Adding 2nd Reference Number

2.9 APPLYING REFERENCE NUMBERS TO AN LCN (PART APPLICATION)

At this point, a top level LCN of ‘A’ with lower level LCNs of ‘A01’ and ‘A03’ ALC ‘02’has

been established. In addition, CAGE code ‘12345’ has been established along with reference

numbers ‘MC-TBIKE’ and ‘TFRAME’. The HG table is used to associate a reference number

(HA) with the part indenture structure characterized through an LCN (XB).

Note: If Paragraphs 2.2 and 2.8 were not completed, this reference number cannot be applied to

an LCN in the database. The required fields for applying reference numbers to an LCN

are CAGE code, reference number, end item, LCN, ALC, and LCN type.

STEP To apply a reference number to an LCN, access the Part App. (HG) Maintenance function

from the LCN Maintenance Discipline using the Navigator Home tab and Filter box as

shown in Figure 54:


Double-click the Part App. (HG) Maintenance function as shown in Figure 54


2-29

Figure 54. Navigator - Part App. (HG) Maintenance

The Part Application Provisioning Data Maintenance window is displayed


Enter ‘12345’ into the CAGE box as shown in Figure 55

Enter ‘TFRAME’ into the Reference Number box

Enter your assigned ‘BICYCLEXX’ end item into the End Item box



Enter ‘P’ (for LCN type of Physical) into the Type


Figure 55. Part Application Provisioning Data Maintenance


2-30

STEP In the previous STEP, we were able to create an HG record by applying an existing HA

(Ref Num) record to an existing XB (LCN) record. In this STEP, we will use a Backfill

capability to create the XH, HA, XB and HG records together:

Choose the Insert button on the Main Toolbar

Check the Backfill XB/XH/HA checkbox as shown in Figure 56

Enter ‘12346’ into the CAGE box

Enter ‘TFRAME-1’ into the Reference Number box


Enter ‘04’ into the ALC box

Enter ‘P’(for LCN type of Physical) into the Type box

Note the Item Name and LCN Name fields are now active. Enter ‘TEST FRAME’

into the Item Name and LCN Name fields


Close the Part Application Provisioning Data Maintenance window

Figure 56. Part Application Provisioning Data Maintenance Window - Backfill

2.10 ASSIGNING PART UOCs TO SYSTEM/END ITEM LCNS

The HO table maps component parts in the part application provisioning table, table HG, to the

model of an end item or major system within an end item. This enables the reuse of data

documented against items common to multiple models of an end item or major system.

STEP To assign a part UOC to a system/end item level LCN, access Prov. System/EI (HO)

Maintenance from the LCN Maintenance Discipline using the Navigator Home tab and

Filter box as shown in Figure 57:


Double-click the Prov. System/EI (HO) Maintenance function as shown in Figure 57


2-31

Figure 57. Navigator - Prov. System/EI (HO) Maintenance

The Provisioning System/End Item Usable On Code Maintenance window is

displayed

Enter 'T%’ in the Reference Number search criteria box as shown in Figure 58

Choose the Execute button to retrieve the data

Select the record with CAGE ‘12345’, Reference Number ‘TFRAME’ and LCN

‘A01’, ALC ‘02’ from the box in the middle of the window

Figure 58. Provisioning/End Item Usable On Code Maintenance – T% Entered


2-32

Notice in Figure 59 that the bottom left hand part of the screen displays the available UOCs for the

System/End Item configuration. The bottom right hand part of the window will display UOCs that

the selected record (in this case LCN ‘A01’ ALC ‘02’, CAGE code ‘12345’, and reference number

‘TFRAME’) is used in when selected.

Figure 59. Provisioning/End Item Usable On Code Maintenance Window

STEP To complete the addition of a part UOC to a system/end item LCN, do the following:

Select the record with LCN ‘A’ ALC ‘02’and UOC ‘TR1’ from the scrolling list box

on the bottom left of the window as shown in Figure 60

Choose the button to add the UOC to LCN ‘A01’

After the UOC is added to the bottom right box of the window which indicates that it

is added to LCN ‘A01’, choose the Save button on the Main toolbar

Close the Provisioning/End Item Usable On Code Maintenance Window


2-33

Figure 60. Provisioning/End Item Usable On Code Maintenance Window – TR1 UOC

2.11 ESTABLISHING TECHNICAL MANUAL CODES

A Technical Manual Code must be established in order to produce technical publication output

products from EAGLE. The Maintain Tech Manual Code Function in the Tech Manual Discipline

is used to add technical manual codes.

STEP To establish a technical manual code, access the Maintain Tech Manual Code function

from the Tech Manual Discipline utilizing the Navigator Home tab and Filter box as

shown in Figure 61:


Double-click the Maintain Tech Manual Code function as shown in Figure 61


2-34

Figure 61. Navigator Home Tab - Tech Manual Discipline

The Maintain Tech Manual Codes window is displayed (Figure 62)

Figure 62. Maintain Tech Manual Codes Window – TM1


2-35

Choose the Insert button on the Main toolbar to create a blank record

Enter ‘TMT’ in the TM Code field as shown in Figure 63

Enter ‘TRAINING TM’ for the TM Number

Enter 'EAGLE BICYCLE DEMONSTRATION MANUAL' in the Technical

Publication Title box


Close the Maintain Tech Manual Codes window and return to the Navigator

Figure 63. Maintain Tech Manual Codes - TMT


2-36


ENTERING

OPERATIONS &

MAINTENANCE

REQUIREMENTS DATA

SECTION 3

EAGLE WORKBOOK DEF STAN 00-60 SECTION 3 ENTERING O & M REQUIREMENTS DATA

3-3

SECTION 3 ENTERING OPERATIONS AND MAINTENANCE REQUIREMENTS DATA

3.0 INTRODUCTION

This section provides an overview of the operations and maintenance requirement tables (A tables)

of DEF STAN 00-60. The A tables are intended to consolidate information related to the

anticipated operation of systems, the environment in which these systems will be operated and

maintained, and the maintenance requirements that must be met. This information is documented

for an entire system and any subsystems for which maintenance requirements are imposed.

Information in the A tables is generally derived from contract specifications and different

Operations and Maintenance (O&M) requirements can be documented for wartime and peacetime.

3.1 ADDING OPERATIONS AND MAINTENANCE DATA

STEP To illustrate how to add data into the Operation and Maintenance Requirement Tables (A

Tables), specifically the Operations and Maintenance Requirements (AA) Table, do the

following:

Access the Operations Maintenance Discipline from the Navigator utilizing the Home

tab and Filter box and select the O & M Requirements (AA,AG,AH,AI) function as

shown in Figure 64

Double-click the O & M Requirements (AA,AG,AH,AI) function

Figure 64. Navigator - Operations Maintenance

The Operations and Maintenance finder is displayed


3-4

Choose Execute on the Main toolbar

Scroll down and select the record with LCN ‘A05’ and ALC ‘00’ as shown in Figure

65

Choose the button from the Function Specific toolbar

Figure 65. Operations and Maintenance Finder

Click the button if the ‘No Records Found’ message box appears

The Operations and Maintenance Requirement window is displayed

Enter the sample data shown in Figure 66. Some of the fields are drop down list

boxes. When a field contains a drop down list box, the user can select the desired

value. A short cut to the drop down list box is to type the first letter or code of the

desired value and the rest of the value should fill in automatically when ENTER or

TAB is pressed. This will save users time once they are familiar with the EAGLE

application


3-5

Figure 66. Operations and Maintenance Requirement Window


Close the Operations and Maintenance Requirement window

Close the Operations and Maintenance Finder window


Tables), specifically the War Peace Operations and Maintenance Requirements (AB)

Table, do the following:

Utilizing the Navigator Home tab and Filter box select War/Peace Requirements

(AB,AC,AD,AE,AF) function from the Operations Maintenance discipline as shown

in Figure 67

Double-click the War/Peace Requirements function as shown in Figure 67


3-6

Figure 67. Navigator - War/Peace Requirements

The War/Peace Requirements window is displayed

Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve the

requested data. Record (1 of 4) should be highlighted

Choose the Insert button on the Main toolbar. CAUTION: If you fail to choose

Insert, you will be editing existing data!

Enter data for LCN ‘A05’ with ALC ‘0’ as shown in Figure 68 (record 1 of 5). Some

of the fields are drop down list boxes. When a field contains a drop down list box, the

user can select the desired value. A short cut to the drop down list box is to type the

first letter or code of the desired value and the rest of the value should fill in

automatically. This will save users time once they are familiar with the application.


3-7

Figure 68. War and Peace Requirements – Record 1 of 5


Close the War and Peace Requirements window


Tables), specifically the Reliability Requirement Table or AG Table, do the following:

Access the Operations Maintenance Discipline from the Navigator utilizing the

Recent tab and click the O & M Requirements (AA,AG,AH,AI) function as shown in

Figure 69


3-8

Figure 69. Navigator – Recent Tab

The Operations and Maintenance Finder is displayed

Enter ‘A05’ into the LCN finder field as shown in Figure 70

Choose the Execute button on the Main toolbar or ALT+Q,E

Select the record with LCN ‘A05’ and ALC ‘00’

Figure 70. Operations and Maintenance Finder – LCN A05


3-9

Click the button on the Function Specific toolbar

Click the button to ‘No Records Found’

Enter the data as shown in Figure 71. Some of the fields are drop down list boxes.

When a field contains a drop down list box, the user can select the desired value. A

short cut to the drop down list box is to type the first letter or code of the desired

value and the rest of the value should fill in automatically. This will save users time

once they are familiar with the EAGLE application.


Figure 71. Reliability Requirement - Annual Operating Requirements

Close the Reliability Requirement window

Close the Operations and Maintenance Finder


3-10


ENTERING

RELIABILITY,

AVAILABILITY &

MAINTAINABILITY

DATA

SECTION 4

EAGLE WORKBOOK DEF STAN 00-60 SECTION 4 ENTERING RAM DATA

4-3

SECTION 4 ADDING RELIABILITY, AVAILABILITY AND MAINTAINABILITY DATA

4.0 INTRODUCTION

The Reliability, Availability and Maintainability tables (B tables) in EAGLE document the

function of each repairable item that comprises the system under analysis; outline the maintenance

concept to be utilized for design and support planning purposes; and identify any design

conditions such as fail safe requirements and environmental or nuclear hardness considerations

imposed on the system. Also documented in the B tables are item reliability, maintainability, and

related availability characteristics resulting from the failure modes and effects, criticality, and

maintainability analyses and accommodate a narrative description of any analysis related to the

potential redesign of an item.

4.1 ADDING RELIABILITY AND MAINTAINABILITY DATA

STEP To illustrate how to add data into the Reliability, Availability and Maintainability Tables

(B Tables), do the following:

Access the Reliability & Maintainability Discipline from the Navigator by utilizing

the Home tab and Filter box and select the RAM Finder as illustrated in Figure 72

Double-click the RAM Finder function

Figure 72. Navigator Home Tab – RAM Finder Function Selected


4-4

The Reliability + Maintainability Finder is displayed

Select ‘ALL’ from the RAM Ind. drop down list and make sure the Show all LCNs

radio button is selected as shown in Figure 73

Choose the Execute button on the Main toolbar

Note: When the Show all LCNs radio button is selected, all LCNs from Table XB meeting the

search criteria are returned. If the Only LCNs with RAM Data radio button is selected,

only LCNs with data in Table BA that meet the search criteria are returned.

4.2 ADDING RAM CHARACTERISTICS DATA

STEP To illustrate how to add data into the Reliability & Maintainability Tables, specifically

the RAM Characteristics or BA Table, do the following from the Reliability +

Maintainability Finder shown in Figure 73:

Select the record with LCN ‘A01AK’ and ALC ‘00’

Note: The RAM Indicator field (RAMINDXB) for the selected record must be set to ‘Y’ to

allow Reliability, Availability and Maintainability data in the B tables

Select ‘Y’ from the RAM Ind. for the record selected


Figure 73. Navigator - Reliability + Maintainability Finder


4-5



The RAM Characteristics window is displayed (top shown)

Select 'End Item can be dispatched' from the Minimum Equip List Indicator drop

down list box as shown in Figure 75

Enter '1' in the Conversion Factor box

Enter '1' in both the Fault Isolation Ambiguity Group 1 and Group 2 boxes

Enter '92' in the Fault Isolation Percent Failure Group 1 box

Enter '90' in the Fault Isolation Percent Failure Group 2 box

Enter '95' in both the BIT Detectability Level Percentage Group 1 and Group 2 boxes

Enter '2' in the BIT Cannot Duplicate % box

Enter '10' in the BIT Retest OK % box

Enter 'HISTORY DATABASE' in the Failure Rate Data Source box

Select 'Unclassified' from the Security Clearance drop down list box

Select 'No' from the Connectors Logistics Considerations drop down list box

Select 'N/A' from the Test Points Logistics Considerations drop down list box

Select 'Y' for all other Logistics Considerations

Figure 74. RAM Characteristics – Top Shown


4-6

Select App./Sel. by Gov. for organic supp. from the Support Concept drop down list

box as shown in Figure 75 (Scroll down)

Enter '36000' in the Wearout Life box and select a corresponding MB of ‘Operating

Hours' from the MB drop down list box

Enter '20' in the Authorized Life box

Select 'Years' from the Authorized Life Measurement Base drop down list box

Enter '1A-2B/REG-3B/FB/LR/ESD-4/ESD' in the Maintenance Concept Options

Option 1 box

Enter '100000' in the Maintenance Concept Cost Option 1 box

Select 'Pound Sterling' from the Maintenance Concept Cost Currency Code box

Figure 75. RAM Characteristics Window


Close the RAM Characteristics Window

4.3 ADDING RAM CHARACTERISTICS NARRATIVE


the RAM Characteristics Narrative or BB Table, do the following from the Reliability +

Maintainability Finder:



4-7


The RAM Characteristics Narrative window is displayed

Select RAM Item Function from the drop down list box as shown in Figure 76

Enter the following narrative ‘Provides support for the rider.’ To enter text for a

different narrative, select one of the other types of narrative from the drop down list

box and enter the information.

Figure 76. RAM Characteristics Narrative Window


Close the RAM Characteristics Narrative window

4.4 ADDING RAM LOGISTICS CONSIDERATIONS NARRATIVE DATA


the RAM Logistics Considerations Narrative or BC Table, do the following from the

Reliability + Maintainability Finder:



The RAM Logistics Considerations Narrative window is displayed

Select D. SR (Safety) from the drop down list box as shown in Figure 77

Enter the following narrative ‘Bicycle seat is safe when proper attire is worn.’ To

enter text for a different narrative, select one of the other types of narrative from the

drop down list box and enter the information


4-8

Figure 77. RAM Logistics Considerations Narrative Window


Close the RAM Logistics Considerations Narrative window

4.5 ADDING RAM INDICATOR CODE DATA


the RAM Indicator Characteristics or BD Table, do the following from the Reliability &




Click the button when the ‘No Records Found’ message box appears

The RAM Indicator Characteristics window is displayed (top shown)

Select 'Measured' from the RAM Indicator Code drop down list box as shown in

Figure 80

Enter '1' for Achieved Availability

Enter '0.999448' for Inherent Availability

Enter '5.0' for Inherent Maintenance Factor

Enter '1.18' for Max. Time to Repair

Enter '95' for Percentile

Enter '0.30' for both Mean Time to Repair Operational and Technical

Enter '0.018' for Failure Rate and select 'Operating Hours' from the MB drop down

list box


4-9

Figure 78. RAM Indicator Characteristics Window – Top Shown

Enter '763.4' for Mean Time Between Failures Operational and select 'Operating

Hours' from the corresponding MB drop down list box as shown in Figure 79

Enter '543.5' for Mean Time Between Failures Technical and select 'Operating Hours'

from the corresponding MB drop down list box

Enter '3' for Mean Time Between Maintenance Actions Operational and select

'Operating Hours' from the corresponding MB drop down list box

Enter '3' for Mean Time Between Maintenance Actions Technical and select

'Operating Hours' from the corresponding MB drop down list box

Enter '999' for Mean Time Between Maintenance Induced and select 'Operating

Hours' from the corresponding MB drop down list box

Enter '515.2' for Mean Time Between Maintenance Inherent and select 'Operating

Hours' from the corresponding MB drop down list box

Enter '3' for Mean Time Between Maintenance No Fault and select 'Operating Hours'

from the corresponding MB drop down list box

Enter '80' for Mean Time Between Prev. Maint. and select 'Operating Hours' from the

corresponding MB drop down list box

Figure 79. RAM Indicator Characteristics Window – Mean Time Between:


4-10

Scroll to the right and enter '10000' for Time Between: Overhauls and select

'Operating Hours' from the corresponding MB drop down list box as shown in Figure

80

Enter '8' for Time Between: Removals and select 'Operating Hours' from the

corresponding MB drop down list box

Enter '1' for Confirmed Fault Rate/1000 Hours

Figure 80. RAM Indicator Characteristics Window – Time Between:


Close the RAM Indicator Characteristics window

4.6 ADDING WAR/PEACE RAM INDICATOR CHARACTERISTICS DATA

STEP To illustrate how to add data into the Reliability + Maintainability Tables, specifically the

War/Peace RAM Indicator Characteristics or BE Table, do the following from the





The War/Peace RAM window is displayed

Select ‘Measured’ from the RAM Indicator Code drop down list box as shown in

Figure 81

Select ‘Peacetime’ from the RAM Operational Requirement Indicator drop down list

box


4-11

Enter ‘20’ for Administrative and Logistic Delay Time

Enter ‘98’ for Operational Availability

Enter ‘5’ for Standby Time

Figure 81. War/Peace RAM Window


Close the War/Peace RAM window

4.7 ADDING FAILURE MODE AND RCM ANALYSIS DATA

Results of Reliability Centered Maintenance (RCM) Analysis are documented in table BF for each

failure mode defined. These results consist of a Y/N answer to each applicable question in the

RCM logic tree. The actual questions that comprise the RCM logic tree are generally contained in

specifications and not documented in the EAGLE database however the specification utilized is

documented in Table AA.

STEP To illustrate how to add data into the Reliability + Maintainability Tables, specifically the

Failure Mode and RCM Analysis Results or BF Table, do the following from the




Click button to ‘No Records Found’

The Fail Mode (FM) and RCM Analysis window is displayed

Enter ‘F001’ for the Failure Mode Indicator as shown in Figure 82

Enter ‘.15’ for the Failure Mode Ratio.

Select ‘Yes’ from the Reliability Centered Maintenance (RCM) Logic Results drop

down list box for questions 01, 04, and 06. Select 'No' for 02


4-12

Enter ‘B’ for RCM Disposition A

Enter ‘F’ for RCM Disposition B

Enter ‘G’ for RCM Disposition F

Note: To utilize the Perform RCM Analysis functionality, the User must be assigned the

‘Common’ End Item established in the LSAR DB.

Figure 82. Fail Mode (FM) and RCM Analysis Window


Close the Fail Mode (FM) and RCM Analysis window


4-13

4.8 ADDING FAILURE MODE AND RELIABILITY CENTERED MAINTENANCE

NARRATIVE


the Failure Mode and RCM Narrative or BG Table, do the following from the Reliability

+ Maintainability Finder:



The RAM Failure Mode + RCM Narrative window is displayed

Select ‘F001’ from the Select FM Indicator drop down list as shown in Figure 83

Select ‘D. Failure Cause’ from the Select Type of Narrative drop down list

Enter ‘Attaching bolts not properly torqued.’ in the narrative box. To enter text for a

different narrative, select one of the other types of narrative from the drop down list

and enter the information

Figure 83. RAM Failure Mode + RCM Narrative Window

Choose the Save button on the Main toolbar.

Close the RAM Failure Mode + RCM Narrative window

4.9 ADDING FAILURE MODE TASK DATA


the Failure Mode Task Data or BH Table, do the following from the Reliability +



4-14

Select the record with LCN ‘A01AK’ and ALC ‘00’.



The Failure Mode Task window is displayed

Click the button on the Failure Mode Task window as shown in

Figure 84. This opens the Task Selection window

Figure 84. Failure Mode Task Window

Note: No task data currently exists against LCN ‘A01AK’, ALC ‘00’. Later, in Section 5, we

will create task data in Table CA. Tasks can also be created from the Task Selection

window by selecting the Create New Task button however for the purpose of this

exercise we will assign a task from LCN ‘A’, ALC ‘00’.

Select ‘F001’ from the Failure Mode Indicator drop down list as shown in Figure 85

Enter ‘A’ in the LSA Control Number box


4-15

Enter ‘00’ in the ALC box

Enter ‘D%’ in the Task Code box

Choose the button on the Task Selection window

Select the record with Task Code of ‘DACOBAA’

Choose the button on the Task Selection window

Figure 85. Task Selection Window

You are returned to the Failure Mode Task window

Select ‘Preventative (calendar)’ from the Task Type drop down list as shown in

Figure 86


4-16

Figure 86. Failure Mode Task Window – Task Type


Close the Failure Mode Task window

4.10 ADDING MISSION PHASE OPERATIONAL MODE DATA

Mission phase operational mode data is not LCN/ALC specific (mission phase codes are assigned

to an end item). Therefore, since mission phase codes have already been established for the

baseline bicycle, mission phase codes will already exist in the training database. For the purpose

of this exercise a new mission phase code will be established, however, the previously established

mission phase codes will be used in subsequent exercises.


the Mission Phase Operational Mode Data or BL Table, do the following from the




The Mission Phase Operational Mode window is displayed

Choose the Insert button from the Main toolbar

Select ‘D’ from the Code drop down list as shown in Figure 87

Enter ‘BICYCLE STORAGE’ for the Operational Mode


4-17

Figure 87. Mission Phase Operational Mode Window


Close the Mission Phase Operational Mode window

4.11 ADDING RAM CRITICALITY DATA AND FAILURE MODE INDICATOR MISSION

PHASE CODE CHARACTERISTICS DATA


the RAM Criticality or BK Table and the Failure Mode Indicator Mission Phase Code

Characteristics or BI Table, do the following from the Reliability + Maintainability

Finder:




The Failure Mode IMPCC Characteristics window is displayed


4-18

Select ‘B’ from the Mission Phase Code drop down list as shown in Figure 88

Select ‘Minor’ from the Safety Hazard Severity Code drop down list

Select ‘F001’ from the Failure Mode Indicator drop down list

Enter ‘.5’ for the Failure Effect Probability

Select ‘Occasional’ from the Failure Probability Level drop down list

Enter ‘2’ for Operating Time

Select ‘Operating Hours’ for the Operating time Measurement Base

Select 'Not Significant' from the System Equipment Importance Code drop down list

box

Note: If Automatic Calculations are on, Failure Mode Criticality Number and RAM Item

Criticality Number will be calculated. They will not appear in Figure 88 until the RAM

Finder has been refreshed (the query re-executed) and the Failure Mode IMPCC

Characteristics Window reopened.

Figure 88. Failure Mode IMPCC Characteristics

Choose the Save button from the Main toolbar

Close the Failure Mode IMPCC Characteristics window

4.12 ADDING RAM FAILURE MODE INDICATOR MISSION PHASE CODE

CHARACTERISTICS NARRATIVE DATA


RAM Failure Mode Indicator Mission Phase Code Characteristics (MPCC) Narrative or

the BJ Table, do the following from the Reliability + Maintainability Finder:



The RAM FM IMPCC Narrative window is displayed


4-19

Select ‘F001’ from the Select FM Indicator drop down list Figure 89

Select ‘B’ from the Select Mission Phase Code drop down list

Select ‘B. Compensating Operator Action Provisions’ from the Select Type of

Narrative drop down list

Input the following narrative ‘Include socket wrench in the tool bag in case seat

becomes loose.’

Figure 89. RAM FM IMPCC Narrative Window


Close the RAM FM IMPCC Narrative window

Close the Reliability + Maintainability Finder


4-20


ENTERING TASK

ANALYSIS DATA

SECTION 5

EAGLE WORKBOOK DEF STAN 00-60 SECTION 5 ENTERING TASK ANALYSIS DATA

5-3

SECTION 5 ENTERING TASK ANALYSIS DATA

5.0 INTRODUCTION

The Task Analysis tables (C Tables) document maintenance task requirements for each repairable

assembly comprising the system/end item. This includes maintenance procedures, task times and

frequencies, personnel skills, tools/support equipment, facilities, and supply support requirements.

5.1 CREATING TASKS

Access the Task Analysis Discipline from the Navigator and select the Task Analysis Finder

function by utilizing the Home tab and Filter box as shown in Figure 90.

STEP To illustrate how to use the Task Analysis Finder, do the following as shown and

described:


Double –click the Task Analysis Finder function as shown in Figure 90

The Task Analysis Finder is displayed

Figure 90. Navigator - Task Analysis


5-4

Choose the Execute button from the Main Toolbar to return the records as shown in

Figure 91

Notes about this Finder:

1. If the Display Only LCNs With Tasks checkbox is checked and the LCNs radio button is

selected, only data for LCNs with tasks assigned that meet the search criteria will be

returned.

2. If the Display Only LCNs With Tasks checkbox is checked and the LCNs and Task

Codes radio button is selected, records will be returned for each task that meets the search

criteria. A large amount of data may be returned if specific search criteria are not

entered!

3. If the Display Only LCNs With Tasks checkbox is checked and the Display Data Module

Codes radio button is selected, only LCNs with tasks linked to data modules will be

returned. Records will be displayed for each task linked to a data module, and the Data

Module Code search criterion box will be enabled. A large amount of data may be

returned if specific search criteria are not entered!

4. If the Display Only LCNs With Tasks checkbox is not checked, all LCNs that meet the

search criteria will be returned (whether or not task data exists in Table CA).

5. There are many separate processes that can be performed from the Task Analysis Finder.

The next few paragraphs outline some of the major task processes that are most

commonly performed.

Figure 91. Task Analysis Finder – Records Returned


5-5

5.1.1 Adding a New Task

New tasks may be added to existing LCNs in the Task Analysis Discipline. If an LCN does not

already exist, the LCN should be added using the LCN Maintenance Discipline from the

Navigator. The process for adding a new task to an LCN is outlined below.

Task Codes may be created as original or reference tasks. Original tasks may contain data in non-

key fields of table CA and may also contain data in tables subordinate to table CA (tables CB

through CM except CJ). Reference tasks contain only data in key fields and referencing key

fields in table CA and never contain data in tables subordinate to table CA. Reference tasks are

used to avoid duplication of data and to insure consistency between like tasks. The only data

required for task references are the keys for the Task Requirement (CA) Table including those

identified in paragraph C.7.1(a) of DEF STAN 00-60 (PART0) ANNEX C.

5.1.1.1 Adding Original Tasks

STEP To illustrate how to add a new task into the Task Analysis Tables, specifically the Task

Requirement or CA Table, do the following as shown and described:

Select the record with LCN ‘A’, ALC ‘01’ as shown in Figure 92


The Task Information window is displayed

Figure 92. Task Analysis Finder Window – ALC ‘01’ Selected


5-6

Info: The Task Information window has tabs which represent the different types of information

that can be stored in the database (Support Equipment, Provisioned Items, etc.) Note that

no tasks exist. This is indicated by the ‘No Tasks Found’ information in the Task

Code/Task Identification drop down list. The New Task tab is already selected.

As shown in Figure 93, the box at the lower left of the window contains

‘Recommended Action Verbs’. This drop down list may be used to select action verbs

to begin the Task Identification

Figure 93. Task Information Window - New Task

Use the scroll bar and select ‘INSPECT’ from the list as shown in Figure 94

Click the button to insert ‘INSPECT in the Task Identification box

Enter ‘BICYCLE’ after the word ‘INSPECT’ as shown

Click the button


5-7

Figure 94. Task Information Window - INSPECT

The Create/Modify Task Code window is displayed

STEP To create a new task code, do the following from the Create/Modify Task Code window

as shown in Figure 95 and described:

Select or enter ‘A’ from the Step 1: Select FUNCTION drop down list box

Select or enter ‘G’ from the Step 2: Select INTERVAL drop down list box

Select or enter ‘C’ from the Step 3: Select O/M LEVEL drop down list box

Select or enter ‘O’ from the Step 4: Select SERVICE drop down list box

Select or enter ‘C’ from the Step 5: Select OPERABILITY drop down list

Click the button to assign the sequence code for the sixth

and seventh position of the task code. Notice the button is now enabled

indicating a complete task code

Choose the button to return to the Task Information window


5-8

Figure 95. Create Task Code

Choose the button to complete addition of the new task (Figure 96)


5-9

Figure 96. Task Information Window – Task Code Created

The Annual Operating Requirements Finder is displayed

Since task code ‘AGCOCAA’ has a ‘G’ in the second position of the task code, it is an

unscheduled task code. For unscheduled tasks, an annual operating requirement must be identified

for calculation of task frequency. This is accomplished by entering an AOR LCN, AOR ALC,

AOR LCN type, and AOR measurement which match a set of key values established in Table AG

(AOR). Therefore, the following window (Figure 97) is displayed when the Done button is

chosen. At this point, the AOR Requirements must be selected.

STEP To illustrate how to complete adding a task code by establishing the annual operating

requirements, do the following from the Annual Operating Requirement Finder as shown

in Figure 97

Select the desired annual operating requirements by highlighting the row with LCN

‘A’ and ALC ‘01’

Choose the button to return to the Task Information window


5-10

Figure 97. Annual Operating Requirements

At this point the new task has been added and the other tabs on the Task Information Window can

be used to add any additional information. Links to provisioning data (through the CI table) can

be established using the Provisioned Items tab, links to support equipment (through the CG table)

can be established using the Support Equipment tab, and tasks can be linked to tech manuals

through the Tech. Manuals tab. For information on how to accomplish any of these links refer to

Paragraphs 5.4 - 5.5

5.1.1.1.1 Specifying Facilities Requirements in Task Analysis

STEP To illustrate how to document a facilities requirement in table CA, do the following as

shown and described:

Select the Facilities tab from the Task Information window as shown in Figure 98

Make sure the task code created in the previous exercise (AGCOCAA/INSPECT

BICYCLE) is selected in the Task Code/Task Identification drop down list box

Select 'Required' from the Are facilities required for the performance of this task?

drop down list


5-11

Figure 98. Task Information Window – Facilities Tab>>Facilities Required


Note: A message is displayed (Figure 99) indicating that ‘A Facility Requirement has been

identified; however, no Facility has been selected for this task. It is not necessary to

identify a facility at this time. However, this message will be displayed each time the

Facilities tab is selected for tasks where a requirement has been identified but no facilities

have been added.

Figure 99. No Facility Selected! Dialog Box


5-12

Select "BICYCLE REPAIR VAN' from the Available Facilities list (Figure 100)

Choose the button

Choose the Save button on the Main Toolbar. The Facility Name is added to the Task

Facility Requirements and the ‘No Facilities message’ is removed

Figure 100. Task Information Window – Facilities Added

Additionally, if a Task Facility Requirement is identified and Facilities have not been identified as

required (no database entry) as shown in Figure 101, choosing the Save button will result in an

error message being displayed as shown in Figure 102

Figure 101. Task Info. Tab – Facilities Tab Selected


5-13

The error message shown in Figure 102 indicates Rule C. on Table FE is being violated.

Figure 102. Error Message – Table FE Rule C

5.1.1.2 Adding Reference Tasks

Reference tasks are created the same way original tasks are created; however, only key fields are

required to be entered for reference tasks. These keys are the EIAC, LCN, ALC, LCN type, task

code, referenced EIAC, referenced LCN, referenced ALC, referenced LCN type, and referenced

task code. Mandatory fields are task ID and task frequency.

STEP To illustrate how to create a reference task, steps similar to those in the previous

paragraph are used. Therefore, the multiple steps are summarized in the following:

Select the New Task tab in the Task Information window (Figure 103)

Enter ‘REPAIR FLAT’ for the Task Identification

Enter ‘JGCOAAA’ directly in the Task Code box

This task is to be a’ reference task’. Do not click the Done button at this point

Click the button from the Task Information window as

shown in Figure 103. This will allow selection of an existing task for reference

information


5-14

Figure 103. Task Information Window – REPAIR FLAT

The Reference Task Finder window is displayed

STEP To continue adding a reference task code, do the following from the Reference Task

Finder as shown in Figure 104. This Finder was retrieved by choosing the Reference an

Existing Task button from the Task Information window:


Make sure ‘A’ is in the LCN query box

Enter ‘RE%’ into the Task Identification finder box as shown in Figure 104

Choose the button from the Reference Task Finder window to extract a list

of available LCNs and Task Codes for referencing

Scroll down the list if necessary and select the task to reference by highlighting the

‘JGCOAAA’ task for LCN ‘A’ and ALC ‘00’

Choose the button


5-15

Figure 104. Reference Task Finder – REPAIR FLAT TIRE

You are returned to the Task Information window

Notice in Figure 105 that the Task Identification box has been changed to reflect the

referenced task’s identification ('REPAIR FLAT' now reads 'REPAIR FLAT TIRE')

Choose the button

Figure 105. Task Information Window – Top Shown


5-16

A referenced task has now been added. Notice as shown in Figure 106 that once a

task is a reference task, the title of the Task Information window is changed to reflect

that ‘This task references another task!!’ This feature lets the user know that the task

being edited is not the original. Notice also, an 'R' in the Task Code/Task

Identification field

Figure 106. Task Information Window - Reference

STEP To illustrate how to view referenced and referencing task information, do the following

from the Task Information window as shown in Figure 107:

Make sure task code 'JGCOAAA' is selected

Choose the General tab from the Task Info. tab

Choose the button


5-17

Figure 107. Task Information - Viewing Referenced Task Information

Figure 108 is displayed

Note that the title in the Task Information window now states ‘ORIGINAL’ Task

Information.

Figure 108. ORIGINAL Task Information

Note: In order to edit data for a task, an ORIGINAL task must be selected. For example, once

the View Original Task button has been pressed and the REFERENCE Task

‘JGCOAAA’ information for LCN ‘BIKE’ ALC ‘00’ is displayed, support equipment,

provisioned items etc. may be added to the task.


5-18

Close the Task Information window

5.1.2 Cloning Tasks

Cloning task information is very useful when creating like or similar tasks. Not only does the

cloning save time, it keeps data consistent. There are two ways to perform cloning of task data

from one LCN to another LCN. Copying performs an actual copy of all task data (Table CA and

its subordinate tables CB through CM, except CJ) from the original LCN to a new LCN. When

copying is performed, data is duplicated. This method of cloning is suitable for a task that is

similar enough to an original task that the original task can be used as a ‘basis’ for creating the

new task. However, if the original task is identical to the new task, it is more efficient to create a

reference copy. A reference copy creates a new task that refers to an original task. The advantage

to this type of cloning is that the task data can be maintained in only one place. Therefore, if a

change needs to be made to a task, the original task is changed and the reference tasks are changed

as well.

The capability to clone tasks is provided through the Task Analysis Discipline using the Task

Analysis Finder.

STEP To illustrate how to clone tasks, do the following from the Task Analysis Finder as

shown in Figure 109 and described:

Check the Only LCNs With tasks checkbox under ‘Display’


Select the record with LCN ‘A’ and ALC ‘00’ from the Task Analysis Finder

Figure 109. Task Analysis Finder – ALC ‘00’


5-19


The Clone Tasks window is displayed (top shown)

The Clone Tasks Window (Figure 110) displays all available tasks (records:22) for the selected

LCN/ALC (LCN ‘A’ with ALC ‘00’) that can be cloned. The six radio buttons at the top of the

window can be used to globally set the options for cloning tasks and subtasks. The radio buttons

in the middle of the window under ‘Task cloning Options’ will allow for the specific cloning of

the task that is selected. These radio buttons are used to designate the type of clone to be made for

each specific task. The default option is ‘Copy Task’ which creates a new task that copies the

original. Since each task listed has the option of referencing, copying, or not cloning at all, every

task must be marked for the appropriate action.

The next row of three radio buttons is used to set the default cloning type for all subtasks for the

task selected in the window.

Figure 110. Clone Tasks Window – Top Shown

The bottom portion of the Clone Tasks window (Figure 111) provides for the customizing of the

subtask cloning options as well as selection of Destination LCN to Clone to.


5-20

Figure 111. Subtask Cloning Options

In the following STEP, all tasks documented against LCN 'A', ALC '00' are to be cloned to a new

BICYCLEXX ‘ALC’. Most tasks will be cloned as reference tasks; however, two tasks are to be

‘copied’ to the new ALC.

STEP To continue with the cloning of LCN 'A', ALC '00', do the following as shown and

described:

Select the ‘Create a reference task’ radio button from the radio buttons listed at the

top of the window as shown in Figure 112. This is always a good first step to prevent

inadvertent copying!

Figure 112. Clone Tasks Window – Create a Reference Task Selected


5-21

Select Task Code ‘AACOCAA’ (Figure 113)

Choose the Copy Task radio button from the Task Cloning Options to the right of the

selected task

Figure 113. Clone Tasks Window – INSPECT BICYCLE

Select Reference All its subtasks from the ‘In general, how do you want to handle

subtasks for the task selected above’ section (Figure 114)

Figure 114. Clone Tasks Window – Reference All its Subtasks

Select Task Code 'DACOBAA' as shown in Figure 115

Choose the Copy Task radio button from the Task Cloning Options

Select Copy all its subtasks from the ‘In general, how do you want to handle subtasks

for the task selected above’ section

Choose the button


5-22

Figure 115. Clone Tasks Window – Adjust Seat Height

The Task Cloning Destination LCN Finder window will be displayed. This window is used to

select the LCN to which the tasks will be cloned.

STEP To create a new LCN for the data to be cloned to, do the following as shown and

described:


as shown in Figure 116

Make sure ‘A’ is in the LCN box to retrieve only ‘A’ level LCNs

Choose the button

Choose the button to create a new LCN for cloning


5-23

Figure 116. Task Cloning Destination LCN Finder

The LSA Control Number Data Maintenance window will be invoked

STEP To continue with creating the destination LCN, do the following as shown in Figure 117

and described:


Enter ‘A’ into the LSA Control Number (LCN) query box

Choose the button

Insert a blank record by choosing the button

Enter ‘A’ into the LSA Control Number (LCN) box


Enter ‘P’ into the Type box

Enter ‘CLONE BICYCLE’ into the LCN Name box

Enter 'A' into the LCN Indenture Code box


5-24

Choose the button to add the new LCN

Choose the button to return to the Task Cloning Destination LCN Finder

Figure 117. LSA Control Number Data Maintenance Window - Copying Tasks

STEP To finish selecting the destination LCN for the copy, do the following as shown in Figure

118 and described:

Choose the button to display the newly added LCN

Select the record with LCN ‘A’ and ALC ‘03’ from the cloning destination list

Choose the button to return to the Clone Tasks window


5-25

Figure 118. Task Cloning Destination LCN Finder Results

Choose the button to perform the copy (Figure 119)

Figure 119. Cloning Destination LCN

The Task Cloning Status screen will be displayed during the Clone process

Close the Clone Tasks window


5-26

STEP To view the ‘Cloned Tasks’ do the following as shown and described:

With the Task Analysis Finder displayed, click the Execute button on the Main

toolbar and Select LCN ‘A’, ALC ‘03’


Click the Task Code/Task Identification drop down to view the results as shown in

Figure 120

All tasks should be reference tasks except for Task Codes 'AACOCAA' and

'DACOBAA'.

Figure 120. Task Information Window - Task Cloning Results



5-27

5.1.3 Sorting Task Codes

When a large number of tasks exist for an LCN/ALC, it is often useful to sort the tasks in an order

other than the default order. Default is task code (Figure 122).

STEP To sort tasks do the following from the Task Analysis Finder as shown and described:


(Figure 121)

Check the ‘Only LCNs With Tasks’ checkbox

Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve the records

Select the record with LCN of ‘A’, ALC of ‘00’

Choose the button on the Function Specific toolbar

Figure 121. Task Analysis Finder – ALC ‘00’ Selected

Tasks may be sorted by positions 1 through 5 of the Task Code (Task Function Code, Task

Interval Code, Operations/Maintenance Level Code, Service Designator Code, or Operability

Code) or the Task Identification.


5-28

Click the button on the Task Information window located to the right

of ‘Task Identification’

The Specify Sort Columns window is displayed

Drag and Drop ‘task_code_interval’ from the Source Data list to the Columns area as

shown in Figure 122

Choose the button

Figure 122. Specify Sort Columns Window.

Verify that the tasks are now sorted by Task Interval (2nd position of Task Code) by

pulling down the Task Code/Task Identification drop down list


5.2 ADDING SUBTASKS TO TASKS

Subtasks may be created as original or reference subtasks. Original subtasks are subtasks that

contain applicable data in Table CB and its subordinate tables, whereas reference subtasks contain

“pointers” to other records in Table CB. Reference subtasks are used to avoid duplication of data.

The only data the reference subtask needs is the required keys for the Subtask Requirement (CB)

Table. Reference subtasks should only be used when the data of the Subtask Requirement (CB)

Table and its subordinate tables (tables CC and CD) are the same for the referenced and

referencing subtask.


5-29

5.2.1 Adding Original Subtasks

STEP To illustrate how to add a new subtask into the Task Analysis Tables, specifically the

Subtask Requirement or CB Table, do the following from the Task Analysis Finder as


Select the record with LCN ‘A’, ALC ‘01’ from the Task Analysis Finder as shown in

Figure 123


The Subtask Information window is displayed

Figure 123. Task Analysis Finder – ALC ‘01’ Selected.

Note: Notice as shown in Figure 124, that for the ‘BICYCLEXX’ End Item and the ‘A’ LCN

with ALC ‘01’ there are no subtasks. This is indicated by the ‘No Subtasks Found’

information in the Subtask/Subtask Identification drop down list box. The New Subtask

Tab is defaulted, and the window has tabs which represent the different types of

information that can be stored in the database.

Make sure Task Code ‘AGCOCAA’ is selected from the Task Code drop down list

Make sure the New Subtask tab is selected


5-30

Figure 124. Subtask Information Window – New Subtask Tab

Enter ‘PREPARE BICYCLE FOR INSPECTION’ in the Subtask Identification box


Make sure the Subtask Numbering radio button has ‘Enter as LAST Subtask’ selected

Choose the button

Figure 125. Subtask Information Window – Subtask Identification

Note: As was done in the Task Window, you may have elected to choose an action verb from

the scrolling list on the left to start the process.


5-31

STEP Add another subtask by doing the following:

Click on the New Subtask tab (Figure 126)

Enter ‘INSPECT BICYCLE’ in the Subtask Identification box

Enter ‘5’ in the New Subtask No. box

Choose the button

Figure 126. New Subtask No. - 2

Note: Subtasks may be inserted as the first subtask, last subtask or between existing subtasks.

If a subtask is inserted as the first subtask, existing subtasks will be renumbered as

required. If a subtask is inserted as the last subtask, the next sequential subtask number

will be assigned to the subtask. If a subtask is inserted between existing subtasks, the

Renumber Subtask Window will be opened to allow the user to “place” the new subtask

in the desired sequence. A subtask number may be specified (as in the previous step),

provided the subtask number does not already exist in the task under analysis. Tip: To

avoid renumbering subtasks each time a new subtask is entered between existing

subtasks, maintain a “gap” between existing subtasks whenever possible.

5.2.2 Adding Reference Subtasks

Reference subtasks are created the same way original tasks are created; however, only key fields

are required to be entered for reference subtasks. These keys are the EIAC, LCN, ALC, LCN

type, task code, subtask number, referenced subtask EIAC, referenced subtask LCN, referenced

subtask ALC, referenced subtask LCN type, reference subtask task code and referenced subtask

number.


5-32

To create a reference subtask, the Reference an Existing Subtask button is used to select which

subtask the new subtask is going to reference. It is presumed that the Subtask Information

window is displayed.

STEP To illustrate how to add a reference subtask, do the following s from the Subtask

Information window:

Select the New Subtask tab

Enter ‘10’ in the New Subtask No. box

Choose the button from the Subtask Information

window. The Reference Subtask Finder is displayed

Make sure ‘A’ is in the LCN query box as shown in Figure 127

Choose the button at the bottom of the Reference Subtask Finder

Select the subtask to reference by highlighting subtask ‘3’ for LCN ‘A’ with ALC

‘00’ and Task Code ‘AACOCAA’ as shown in Figure 127

Choose the button

Figure 127. Reference Subtask Finder – Query Results


5-33

Choose the button in the Subtask Information window

A referenced subtask has now been added. Notice that once a subtask is a reference subtask, the

title of the Subtask Information window is changed to reflect the subtask references another

subtask (Figure 128). This feature lets the user know that the subtask being edited is not the

original. Users may toggle back and forth between the referenced subtask and the referencing

subtask.

STEP To illustrate how to view referenced and referencing subtask information, do the

following:

Select Subtask ‘10’ the ‘POST INSPECTION PROCEDURES’ subtask from the

Subtask Information Window

Choose the Subtask Information tab noting that the title in the Subtask Information

Window states that the subtask references another subtask.

Choose the button to see which subtask is being

referenced

Figure 128. Subtask Information - Viewing Referenced Subtask Information


5-34

Note that the title in the Subtask Information window now states that the information

displayed is the ORIGINAL Subtask Information (Figure 129)

Close the Subtask Information window

Figure 129. Original Subtask Information

Note: To perform maintenance on a Subtask, an original subtask must be selected. For

example, you may not Edit/Add Personnel or Workload information with the Referencing

Subtask selected., the tabs for selection are disabled (grayed out) until the View Original

Subtask button is chosen.

5.2.3 Changing Subtask References

STEP To illustrate how to change a subtask reference, do the following as shown and described.

Make sure to select the correct LCN/ALC:

Select the record with LCN ‘A’, ALC ‘03’ from the Task Analysis Finder as shown in

Figure 130


5-35

Figure 130. Task analysis Finder – BIKE ALC ‘03’


Select Task Code ‘AACOCAA’ from the Task Code/Task Identification drop down

list as shown in Figure 131

Select Subtask ‘2’ from the Subtask drop down list

Choose the Reference Information tab. Note that this subtask references a similar

subtask from the ALC '00' bicycle (Subtask being referenced: section)

Click the button

The Reference Subtask Finder is displayed


5-36

Figure 131. Subtask Information Window – Reference Information Tab

Make sure ‘A’ is in the LCN query box (Figure 132)

Enter ‘1’ into the ALC query field

Choose the button from the Reference Subtask Finder window to extract a

list of available subtasks for referencing

Select the subtask to reference by highlighting Subtask ‘5’ for LCN ‘A’ with ALC

‘01’ and Task Code ‘AGCOCAA’ as shown in Figure 132

Choose the button to return to the Subtask Information window


5-37

Figure 132. Reference Subtask Finder - Changing Subtask References

Note the Subtask being referenced info has changed (Figure 133)

Choose the button

Figure 133. Save Reference Subtask Changes


5-38

Choose the button to ‘Save Reference Subtask Changes’

Choose the button on the Delete Subtask Selected! Dialog box (The

old subtask is deleted and a new subtask is created that references a similar subtask

from the ALC '01' bicycle).


5.2.4 Breaking References

If a subtask references another subtask, is referenced by other subtasks, is part of a task that

references another task, or is part of a task that is referenced by other tasks, all tasks and subtasks

are changed if the narrative is edited. If this is not desired, the task and/or subtask reference

link(s) should be broken prior to editing the narrative.

STEP To illustrate breaking a subtask reference link, do the following as shown and described:

Select the record with LCN ‘A’, ALC ‘01’ from the Task Analysis Finder


Select Task Code ‘AGCOCAA’ from the Task drop down list

Select Subtask’ 10 R POST INSPECTION PROCEDURES’ from the Subtask drop

down list

Choose the Reference Information tab from the Subtask Information window

Choose the button (Figure 134)

Figure 134. Subtask Information Window – Subtask 3


5-39

Note in Figure 135 the header indicates only ‘Subtask Information’, that Subtask ‘10’

no longer has a ‘R’ after it and there is no information in the Subtask being

referenced: area


Figure 135. Subtask Information Window - Reference Information Tab

Info: Reference ‘Task’ links can be similarly changed or broken by choosing the Reference

Information tab from the Task Information window. When reference task links are

broken, all tables subordinate to table CA are copied from the original task to the

referencing task. Also, Subtasks (table CB) are copied as subtask references.

5.3 ADDING NARRATIVE DATA TO SUBTASKS

Narrative Data for Subtasks can be added using the Task Analysis Discipline from the Navigator.

Once the Task Analysis Finder has been activated, the button from the Function

Specific toolbar is used to perform adding/maintenance of the subtask narrative.

STEP: To insure proper editing of the Narrative, do the following as shown and described:

Select Tools>>Options from the Menu bar as shown in Figure 136


5-40

Figure 136. Main Screen – Tools>>Options

The Options window is displayed

Select the Publishing and Reports tab

Make sure ‘NONE’ is selected from the Editor: drop down list as shown in Figure

137

Choose the button

Figure 137. Options – Editor: ‘NONE’

STEP To illustrate how to access and use the Task Analysis Narrative Editor, do the following

as shown and described:

Make sure LCN ‘BIKE’ ALC ‘01’ is selected in the Task Analysis Finder as shown

in Figure 138


5-41

Figure 138. Task Analysis Finder – LCN ‘BIKE’ ALC ‘01’ Selected


The Narrative Editor is displayed

Make sure Task Code ‘AGCOCAA’, Subtask ‘1’ is chosen as shown in Figure 139

Check the Allow Editing checkbox to enable editing in the Narrative Editor box

Enter the narrative text ‘Mount bicycle on repair stand by clamping repair stand

clamp to the bicycle frame's top tube.’ (displayed in Figure 139) into the Narrative

Editor box

Next, click on the first line of text entered, then check the Element Code box


5-42

Figure 139. Narrative Editor - Subtask 1 – Element Code Checked


Notice the Allow Editing checkbox is disabled and the Element Code box disappears

Note: The procedural step above was identified with an Element Code to indicate the procedure

is the smallest logically and reasonably definable unit of behavior required to complete

the subtask action. In addition, since this subtask contained multiple lines of text, the

Element Code was associated with the first line.

STEP Edit a second Subtask Narrative by doing the following as shown and described:

Select Subtask ‘5’ from the Subtask/Subtask Identification box

Check the Allow Editing checkbox to enable editing of the Narrative

Enter the narrative text ‘Physically inspect bicycle by looking for rust on spokes,

chain, and frame.’ displayed in Figure 140 into the Narrative Editor box

Click on the first line of text then click on the Element Code box


5-43

Figure 140. Narrative Editor - Subtask 2


The Source Data Modified-Reference Subtask Check window Figure 141 is

displayed.

Since Subtask 2 is a task that is referenced by another subtask, Figure 141 will be displayed to

allow the user options for saving the narrative change. Three options are available. These options

consist of changing the original subtask only, changing the original subtask and leaving all or

some of the referencing tasks the same, or only changing the referencing subtasks.

The first option for saving narrative changes to subtasks is to change the original subtask and all

references to it. This option is the default option and is shown in Figure 141. The ‘DO NOT

CHANGE the reference subtasks selected below’ radio button is marked; however, no subtasks are

selected from the provided list so that all reference subtasks still point to the original subtask.

Therefore, the original subtask is changed and all reference subtasks are in effect changed since

they still reference the original subtask.

The second option for saving narrative changes to subtasks is to change the original subtask, but

leave some of the referencing tasks the same. For this option, the ‘DO NOT CHANGE the

reference subtask selected below’ radio button is marked, and any referencing subtasks that the

user wishes to remain the same should be highlighted/selected from the list. The original subtask

will be changed, and any selected referencing subtasks will remain the same. Therefore, the

referencing subtasks remaining the same will become original tasks containing the original

narrative before the change was made.


5-44

The third option for saving narrative changes to subtasks is to change only the referencing

subtasks while leaving the original subtask alone. For this option, the ‘CHANGE ONLY the

referenced subtasks selected below (DO NOT change the Original)’ radio button is marked. The

original subtask will not contain the narrative change, however, any referenced subtasks selected

will be changed. Therefore, the selected referencing subtasks will become original tasks

containing the changed narrative, while the original task will remain unchanged.

STEP Doing the following as shown in Figure 141 and described will determine which subtasks

will be affected by the narrative changes:

Choose the ‘DO NOT CHANGE the reference subtasks selected below’ radio button

Choose the button to ensure that all of the referencing subtasks will be

affected

Choose the button

Figure 141. Source Data Modified – Reference Subtask Check Window


5-45

Choose the button on the EAGLE: ‘Do Note Change Selected’

dialog box to save the narrative change to the original subtask which in effect changes

the text for the referencing subtask as well since it references the original subtask

Close the Narrative Editor window

5.4 ADDING SUPPORTING DATA FOR TASKS

Supporting Data for Tasks can be added using the Task Analysis Discipline from the Navigator.

5.4.1 Adding Task Data

5.4.1.1 Assigning Support Equipment

In order to assign support equipment to a task, the support equipment (EA record) must already

exist. For instructions on how to create support equipment (EA) records, refer to Paragraph 9.1

about adding support equipment records. In order for a support equipment item to be available for

assignment to a task, it must have an item category code (SEICCDEA) of ‘7’, ‘8’, ‘M’, ‘D’, ‘1’,

‘H’, ‘4’, ‘5’, ‘6’, ‘2’, ‘G’, ‘N’, ‘P’, ‘R’, ‘3’, ‘S’, ‘T’, ‘F’, ‘J’, ‘U’, ‘V’, ‘AC’, ‘AD’, or ‘AF’. The

Support Equipment Discipline can be used to change the item category code if necessary.

It is presumed that LCN ‘A’ with ALC ‘01’ is selected in the Task Analysis Finder as described

previously. In order to assign support equipment to a task, a Task Support Equipment (CG) record

must be created. The CG record provides a link from the support equipment tables to the task

analysis tables. This allows documenting of support equipment required to complete a task.

STEP To illustrate how to assign support equipment, do the following as shown in Figure 142

and described below:

With LCN ‘A’, ALC ‘01’ selected in the Task Analysis Finder, choose the

button from the Function Specific toolbar

Make sure Task Code 'AGCOCAA' is selected in the Task Code /Task Identification

drop down box (Figure 142)

Select the Support Equipment tab

Any support equipment assigned to the task will be displayed. In this case ‘Records:

0’ is shown

Click the button


5-46

Figure 142. Task Information - Support Equipment

After the Add Resources button is chosen, the Task Support Equipment window appears allowing

the user to query the database for selection of desired support equipment to add to the task.

Choose the button as shown in Figure 143 to search the database

for all EA records that exist against your end item

Figure 143. Task Support Equipment Window


5-47

Select the Support Equipment with CAGE of ‘SE999’ and SE Reference Number of

‘RS-9’

Choose the button

Figure 144. Task Support Equipment

Choose the button to confirm adding the support equipment to the

task

The Task Information window is re-displayed

STEP To complete the addition of support equipment, do the following as shown in Figure 145

and described:

Enter ‘1’ into the Qty box

Select ‘Each’ from the Unit of Measure drop down list box



5-48

Figure 145. Task Information - Support Equipment Added

Note in the top portion of the window (Figure 146), ' No Peculiar/Common Tool/SE

Requirement Message Box – Continue?' dialog box is displayed

Figure 146. Task Information Window – Peculiar/Common Tool Message Box

Info: When the performance of a task requires tools or support equipment, a Tool/Support

Equipment Requirement Code should be documented in Table CA. (A code of ‘S’

indicates a Peculiar tool/SE requirement, a code of ‘C’ indicates a Common tool/SE

requirement, or a code of ‘B’ indicates both a Peculiar and Common tool/SE

requirement.) Also, when test equipment is required, the field Task Condition B in Table

CA should contain a value of ‘Y’. Similarly, when special tools are required, the field

Task Condition C in Table CA should contain a value of ‘Y’.


5-49

STEP To identify the support equipment as a peculiar or special tool, do the following as shown

and described:

Choose the Task Info. tab as shown in Figure 147

Choose the Misc tab at the far right

Check the ‘Special Tool Required’ checkbox under the Task Conditions.

Select ‘ ’ from the Tool/SE Requirements drop

down list

Figure 147. Task Info. Tab - Misc Tab


Notice the message disappears from the window

5.4.1.2 Assigning Provisioning Items

In order to assign provisioning items to a task, the provisioned item (HG record) must already

exist. For instructions on how to create provisioned item (HG) records, refer to Paragraph 2.9

about applying reference numbers to an LCN using the LCN Maintenance Discipline. Once an

HG record is created, the item category code needs to be set to an appropriate value (‘Q’, ‘W’,

‘Y’, ‘X’, ‘K’, ‘L’, ‘Z’, ‘9’, ‘AA’, ‘AB’, ‘AD’, or ‘AE) in order for it to be a provisioned item. The

Provisioning Discipline can be used to change the item category code in the HG tab on the

View/Edit Provisioning Data Window.


5-50

As described in the paragraph above, in order to assign provisioning items to a task, a Task

Provisioned Item (CI) record must be created. The CI record provides a link from the

provisioning tables to the task analysis tables. This allows documenting of spare and repair parts

needed to support the task.

STEP To illustrate how to assign provisioned items, do the following and described:

It is presumed that LCN ‘A’ with ALC ‘01’ is selected in the Task Information

window, and that the ‘INSPECT BICYCLE’ task is selected as shown in Figure 148

Click the Provisioned Items tab

Any provisioned items assigned to the task will be displayed. In this case, ‘Records:

0’ is displayed

Make sure the ‘Show All’ checkbox is checked so that all Item Category Codes (ICC

Elements) are selected

Choose the button

After the Add Resources button is chosen, the Task Provisioned Items window appears allowing

the user to query the database for selection of desired provisioning items to add to the task.

Figure 148. Task Information - Provisioned Items


5-51

Choose the button (Figure 149) to search the database for all HG

records that exist in your end item

Select the record with CAGE ‘99999’ and reference number ‘ESL749ZF’ from the

list of provisioned items

Choose the button

Choose the button to confirm adding the provisioned item to the task

Figure 149. Task Provisioned Items Window

The Task Information window is re-displayed

STEP To complete the addition of provisioned items, do the following as shown in Figure 150:

Enter ‘1’ into the Qty box

Select ‘Each’ from the Unit of Measure box


5-52

Figure 150. Task Information - Provisioned Items Added



5.4.2 Adding Support Data to Subtasks

5.4.2.1 Assigning Personnel

In order to assign personnel to subtasks, a Subtask Personnel Requirement (CD) record must be

created. The CD record provides a link from the personnel skills tables to the task analysis tables.

This allows documenting of personnel skills required to complete a task.

STEP To illustrate how to assign personnel to a subtask, do the following as shown in Figure

151 and described below:

Make sure LCN ‘A’ ALC ‘01’ is selected in the Task Analysis Finder

Choose button from the Function Specific toolbar

The Subtask Information window is displayed


5-53

Make sure Task Code 'AGCOCAA' is selected from the Task Code/Task

Identification drop down list box as shown in Figure 151

Make sure subtask '1' is selected from the Subtask/Subtask Identification drop down

list box

Select the Personnel tab

Enter ‘A’ into the Person Identifier box

Select ‘14B’ from the Available SSCs box in the left hand corner of the window by

double-clicking on it

Enter ‘5.0’ in the Subtask Mean Man-Minutes box

Select ‘SSC is adequate’ from Skill Specialty Evaluation Code box


Figure 151. Subtask Information – Personnel

5.4.3 Assigning Workloads

It is assumed that Paragraph 5.4.2.1 has been completed and personnel have been assigned to a

subtask. In order to assign workloads to subtasks, a Subtask Task Inventory (CK) record must be

created. The CK record provides a link from the personnel skills tables, the job and duty tables,

and the task analysis tables. This allows documenting of workload requirements to complete a

subtask.


5-54

STEP To illustrate how to assign workloads for a subtask, do the following as shown in Figure

152 and described below. Note that Figure 152 contains the results after the following

has been performed:

Choose Workload tab from the Subtask Information window

Make sure the Person ID Codes tab is selected

Select the ‘A’ from the Available Person Identifiers records

Choose the button to assign the Person Id Code: for the workload

Figure 152. Subtask Information Window - Workload Tab – Person ID Codes

Choose the Job/Duty Codes tab

Scroll down the Job/Duty Codes list if necessary and choose the record with Job Code

‘A1’ and Duty Code ‘1’ as shown in Figure 153

Choose the button to assign the Job/Duty codes


5-55

Figure 153. Subtask Information Window - Workload Tab – Job Duty Codes

Choose the Workload Text tab

Highlight the narrative rows to get the Workload ‘From: and To:’ lines from the

workload text (click on the first line then click on the last line while holding down the

Shift key) as shown in Figure 154

Choose the button to assign the Job/Duty codes

Figure 154. Subtask Information Window - Workload Tab


5-56


Note: If additional workload assignments need to be made, the button on the bottom

left of the Workload tab is used to add another workload.


5.5 ASSIGNING TASK NARRATIVE TO A TECH MANUAL

Task narrative can be assigned to a tech manual by using the Task Analysis Discipline from the

Navigator. Before task narrative can be assigned to a tech manual, a tech manual code must

already exist.

It is presumed that LCN ‘A’, ALC ‘01’ is selected in the Task Analysis Finder as described above.

STEP To illustrate how to assign task narrative to a tech manual, do the following as shown in

Figure 155 and described below. Note that Figure 155 contains the results after the Task

Information window has been activated and the Tech. Manuals tab has been chosen and

the TM1 Code chosen:


Select the Tech. Manuals tab to display the available technical manual codes

Click to ‘No Records Found’ message

Highlight the technical manual ‘TM1’ which will contain the given task

Choose the button



5-57

Figure 155. Task Information - Tech. Manuals

Choose the button as shown in Figure 156

Figure 156. Tech. Manuals Tab – 00-60 Data button

The Additional Task/Tech Manual Data window is displayed (Figure 157)

Select 'Amendment Required' from the Requirements drop down list box

Enter '1001001' in the ID Number box


5-58

Enter 'Manual must be completed before bicycles are delivered to the fleet.' in the

Comments box

Choose the button

Figure 157. Additional Task/Tech Manual Data Window

The data entered is saved and the Additional Task/Tech Manual Data window is

closed


Close the Task Analysis Finder


ENTERING

FACILITIES

CONSIDERATIONS

DATA

SECTION 6

EAGLE WORKBOOK DEF STAN 00-60 SECTION 6 ENTERING FACILITIES CONSIDERATIONS DATA

6-3

SECTION 6 ENTERING FACILITIES CONSIDERATIONS DATA

6.0 INTRODUCTION

This section provides an overview of the Facilities Considerations tables (F tables) of

DEF STAN 00-60. The F tables identify and justify all proposed special and additional facilities

requirements that are identified as a result of the operational/maintenance task analysis.

6.1 ADDING FACILITIES DATA

Access the Facilities Discipline from the Navigator and select the Facilities Finder as illustrated in

Figure 158.

STEP To illustrate how to use the Facilities Finder, do the following as shown and described:

Make sure the BICYCLEXX end item assigned by the instructor is selected

Double-click the Facilities Finder function as shown in Figure 158

The Facilities Finder is displayed

Figure 158. Navigator – Facilities Finder

Make sure ‘E.All’ is selected from the Facility Type drop down as shown in Figure

159

Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve all facility

names


6-4

6.1.1 Adding New Facility Data

New Facility data is initially entered into the Facilities Finder. Once the Facility is added in the

Facilities Finder, the Reports/Process menu items or the Function Specific buttons are used to

enter in the various Facility data.

STEP To illustrate how to add data into the Facilities Tables do the following from the

Facilities Finder as shown (Figure 159) and described. This step will establish a new

Facility in the FA (Facility) Table. An additional step will be required to enter the

remaining FA Table data into the database:



Figure 159. Facilities Finder – Records Returned

Enter ‘BICYCLE SALES AND REPAIR SHOP’ into the empty Facility Name box as

shown in Figure 160

Enter ‘199345’ into the empty Facility Cat. Code box

Select ‘Test facility’ from the Facility Type drop down list


STEP To illustrate how to add data into the Facilities Tables, specifically the FA Table, do the

following as shown in Figure 160, Figure 161 and described. Note that Figure 161 is the

result after the data has been saved to the database:

Select the ‘BICYCLE SALES AND REPAIR SHOP’ record from the Facilities

Finder


6-5

Figure 160. Facilities Finder – Record Added


The Facility window is displayed

Enter ‘H1N’ into the Dwg. Class box (Figure 161)

Enter ‘ER23-00-1-12’ into the Drawing Number box

Enter ‘AA’ into the Rev. box

Enter ‘000030’ into the Facility Area box

Select ‘Square Foot Super Foot’ from the Unit of Measure box

Enter ‘1’ into the Constr. Unit Of Meas. Price

Select 'Pound Sterling' from the Currency Code drop down list box

Select ‘Square Foot Super Foot’ from the Constr. Unit of Meas. box

Figure 161. Facility Window


6-6

Note: If the drawing exists in the EAGLE database, the Drawing Number and Rev. box can be

filled by using the Find Drawing button and selecting the drawing.


Close the Facility window and return to the Facilities Finder

6.1.2 Linking Facilities Data to Task Requirements

In order to link Facilities data to Task Requirements, The Facility (Table FA) data must already

exist in the database. Therefore, it is presumed that Paragraph 6.1.1 has been completed.

STEP To illustrate how to link data from the Facilities Tables (F tables) to the Task Tables

(CA), do the following from the Facilities Finder:

Note: Facility Tables are linked to the Task Tables through the Operations and Maintenance

Task Facility Requirement (FE) Table.

Make sure the ‘BICYCLE SALES AND REPAIR SHOP’ facility is selected in the

Facilities Finder

Choose the button from the Function specific toolbar


The Operation + Maintenance Task Facility Requirements window is displayed (not

shown)

Choose the button

The Task Selection window is displayed

STEP To continue linking data from the Facilities Tables (F tables) to the Task Tables (CA), do

the following from the Task Selection window as shown in Figure 162:

Enter ‘1’ into the ALC finder box

Choose the button

Select the record with LCN ‘A’ and Task Code ‘AGCOCAA’

Choose the button


6-7

Figure 162. Task Selection Window

You are returned to the Operation + Maintenance Task Facility Requirements window

Scroll to the right and enter '36' into the Docking Interval box as shown in Figure 163



6-8

Figure 163. Operations + Maintenance Task Facility Requirements – Task Selected

Close the Operations +Maintenance Task Facility Requirements window

Close the Facilities Finder


ENTERING

PERSONNEL SKILLS

CONSIDERATIONS

DATA

SECTION 7

EAGLE WORKBOOK DEF STAN 00-60 SECTION 7 PERSONNEL SKILLS CONSIDERATIONS DATA

7-3

SECTION 7 ENTERING PERSONNEL SKILLS CONSIDERATIONS DATA

7.0 INTRODUCTION

The Personnel Skill Considerations tables (G tables) describe and justify any new or modified

personnel skills required to support the system/equipment.

7.1 ADDING PERSONNEL DATA

Access the Personnel Skills Discipline from the Navigator and select the Skill Specialty Code

Finder (GA) utilizing the Home tab and Filter box as illustrated in Figure 164.

STEP To illustrate how to use the Skill Specialty Code Finder (GA) and create a New Skill

Specialty Code, do the following as shown in Figure 164, Figure 165 and described:


Double-click the Skill Specialty Code Finder (GA) function

Figure 164. Navigator - Personnel Skills

The Personnel Skills Finder is displayed

Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve all Skill

Specialty Codes


Enter ‘23A’ into the Skill Specialty Code box as shown in Figure 165

Select ‘Intermediate’ from the Skill Level box

Enter ‘20000.00’ into the Training Cost box

Select 'US Dollar' from the Currency Code drop down list box


7-4

Figure 165. Personnel Skills Finder (GA) Window – Skill Specialty Code


Close the Personnel Skills Finder (GA) window

STEP To illustrate how to add data into the Personnel Skill Consideration Tables, specifically

the New or Modified Skill Table or GB Table, do the following as shown and described:


Double-click the Personnel Skills Finder function (GB,GC,GD) as shown in Figure

166

Figure 166. Personnel Skills – Personnel Skills Finder (GB,GC,GD)


7-5

The New or Modified Skill Finder is displayed



Enter ‘23B’ in the New or Modified Skill Specialty Code box as shown in Figure 167

Select ‘Advanced’ from the New or Modified Skill Level drop down list

Enter ‘23A’ into the Skill Specialty Code box

Enter ‘TRAINING’ into the Duty Position Requiring a New or Revised Skill box

Select ‘Unclassified’ from the Security Clearance Required drop down list

Select 'Petty Officers' from the Training Level Rank drop down list

Select 'Operating & Restricted Maintenance' from the Training Level Skill drop down

list

Figure 167. New or Modified Skill Finder


Close the New or Modified Skill Finder

7.2 ASSIGNING PERSONNEL PHYSICAL AND MENTAL REQUIREMENTS TO A TASK

After a new Personnel Skill has been entered in the database, unique physical and mental

personnel attributes required to perform a task can be entered. The Physical and Mental

Requirements Narrative (GE) Table is used to store this information.


7-6

STEP To illustrate how to add data into the Personnel Skill Consideration Tables, specifically

the Physical and Mental Requirements Narrative Table or GE Table, do the following as



Utilizing the Navigator Home tab and Filter box as shown in Figure 168, select the

Physical/Mental Req Finder (GE) from the Personnel Skills Discipline

Double-click the Physical/Mental Req Finder (GE) Function

Figure 168. Physical and Mental Req Finder (GE)

The Physical and Mental Requirements Narrative Finder is displayed


Choose the button to ‘No Records Found’ message box

A row is inserted as shown in Figure 169

Figure 169. Physical and Mental Requirements Narrative Finder


7-7

STEP The Physical and Mental Requirements Narrative Finder allows data to be added by

selecting from skills and subtask information already in the database. Do the following

from the Physical and Mental Requirements Narrative Finder to select a New or Modified

Skill Specialty Code:

Choose the button as shown in Figure

170

The New or Modified Skill Specialty Code Finder is displayed

Figure 170. Physical and Mental Requirements Narrative Finder

Select the record with ‘23B’ in the New or Modified Skill Specialty Code box as

shown in Figure 171

Choose the button

The Physical and Mental Requirements Narrative Finder is re-displayed

Figure 171. New or Modified Skill Specialty Code Finder

STEP The Physical and Mental Requirements Narrative Finder allows data to be added by

selecting from skills and subtask information already in the database. Do the following

from the Physical and Mental Requirements Narrative Finder to select Task and Subtask

information:


7-8

Choose the button

The Subtask Personnel Requirement Finder is displayed

Enter ‘1’ in the ALC finder box

Choose the button (Figure 172)

Select the record with LCN ‘A’, ALC ‘01’, Task Code ‘AGCOCAA’, and Subtask ‘1’


Choose the button

You are returned to the Physical and Mental Requirements Narrative Finder

Figure 172. Subtask Personnel Requirement Finder

STEP To Save the data in the Physical and Mental Requirements Narrative Finder and retrieve

the Narrative window for adding the narrative data to the GE Table, do the following as




The Physical and Mental Requirements Narrative window is displayed


7-9

STEP To complete adding data into the Personnel Skill Consideration Tables, specifically the

Physical and Mental Requirements Narrative Table or GE Table, do the following as


Select Subtask ‘1’ and Person ID ‘A’ from the drop down list box as shown in Figure

173

Enter the narrative ‘This requires patience.’ as shown into the narrative box


Figure 173. Physical and Mental Requirements Narrative Window

Close the Physical and Mental Requirements Narrative window

Close the Physical and Mental Requirements Narrative Finder


7-10


ENTERING

TRANSPORTABILITY

ENGINEERING

ANALYSIS DATA

SECTION 8

EAGLE WORKBOOK DEF STAN 00-60 SECTION 8 ENTERING TRANSPORTABILITY DATA

8-3

SECTION 8 ENTERING TRANSPORTABILITY ENGINEERING ANALYSIS DATA

8.0 INTRODUCTION

The Transportability Engineering Analysis tables (J tables) document transportability shipping

mode data for the end item. For end items that are sectionalized for transport, the J tables should

be completed for each section of the end item. Transportability data can only be documented for

items identified with a sectionalized item transportation indicator in table XB (SECITMXB of

"Y") or a transportation end item indicator in table XC (TRASEIXC of "Y").

8.1 ADDING TRANSPORTATION DATA

Access the Transportation Discipline from the Navigator by utilizing the Home tab and Filter box

as shown in Figure 174 and select the Transportation Finder.

STEP To illustrate how to use the Transportation Data Finder, do the following as shown in

Figure 174, Figure 175 and described below:


Double-click the Transportation Finder function as shown in Figure 174

The Transportation Finder is displayed

Figure 174. Navigator –Transportation Finder Selected


8-4

Make sure the Show all LCNs radio button is selected as shown in Figure 175

Choose the Execute button on the Main toolbar or ALT+Q,E on the keyboard

Select the record with LCN ‘A’ and ALC ‘01’

Figure 175. Transportation Finder – Records Returned

Note: When the Show all LCNs radio button is selected, all LCNs from Table XB meeting the

search criteria are returned. If the Only LCNs with Transportation Data radio button is

selected, only LCNs with data in Table JA that meet the search criteria are returned.

STEP To illustrate how to add data into the Transportation Tables, specifically the

Transportation Table or JA Table, do the following as shown in Figure 176 and

described:



8-5

Click the button to ‘No Records Found’ message box

The Transportation window is displayed

Select 'Both Shipping Modes + Trans. E.I.' from the Transportation Indicator drop

down list box as shown in Figure 176

Select 'Special considerations required' from the Environmental Handling

Transportation Indicator drop down list

Enter 'CASEW-II-7-00' in the Transportation Contract Number box

Enter 'ALL WEATHER GROUND SUPERIORITY BICYCLE' in the Shipping

Name box

Enter 'MOBILE' in the Military Unit Type box


Close the Transportation window

Figure 176. Transportation Window


8-6

8.1.1 Adding Transportation Shipping Mode Data

STEP To illustrate how to add shipping mode data, do the following as shown in Figure 177

and described:

Select the record with LCN ‘A’ and ALC ‘01’ from the Transportation Finder



The Transportation Ship Mode window is displayed

Enter ‘1’ for the Transportation Character Number as shown in Figure 177

Select ‘Rail’ from the Transportation Character Mode Type drop down list

Select ‘Crate’ from the Shipping Configuration drop down list

Figure 177. Transportation Ship Mode Window – Top Shown

Enter '2' in the EIAC Length box as shown in Figure 178

Enter '1' in the EIAC Width box

Enter '2' in the EIAC Height box

Select 'Metre' from the EIAC DIM UOM box


8-7

Figure 178. Transportation Ship Mode Window – Bottom Shown


Close the Transportation Ship Mode window

8.1.2 Adding Transported End Item Data

STEP To illustrate how to add transported end item data, do the following as shown and

described:

Select the record with LCN ‘A’ and ALC ‘01’ from the Transportation Finder



The Transported End Item window is displayed

Enter ‘1’ for the Transported Conf. Number as shown in Figure 179

Select ‘Skid’ from the Mobility Type drop down list

Figure 179. Transported End Item Window – Top Shown


8-8

Enter ‘1’ for Skid Number of Skids (Figure 180)

Enter ‘25’ for Skid Area

Select ‘Square Foot/Super Foot’ for Skid Area Unit of Measure

Figure 180. Transported End Item Window – Bottom Shown


Choose the Execute button in the Main Toolbar to refresh the screen. The

button at the top right is now active

8.1.3 Adding Transported End Item Narrative

STEP To illustrate how to add transported end item narrative data, do the following as shown in

Figure 181, Figure 182 and described:

Click the button in the upper right corner of the Transported End Item

Window shown in Figure 181

The Transported End Item Narrative window is displayed

Figure 181. Transported End Item – Narrative Button Active


8-9

Select ‘1’ from the Select Transported Configuration Number drop down list as

shown in Figure 182

Select ‘A Skid’ from the Select Mobility Type drop down list

Select ‘B. Skid Remarks’ from the Select Type of Narrative drop down list box

Enter ‘The bicycle is transported on a skid 6 inches wide by 5 feet long.’

Click the button to save the transported end item narrative

Figure 182. Transported End Item Narrative Window

Choose the button when prompted 'Do you want to save changes?'

Close the Transported End Item window

8.1.4 Adding Transport by Fiscal Year Data

STEP To illustrate how to add Transport by Fiscal Year data, do the following as shown and

described:

Select the record with LCN ‘A’, ALC ‘01’ from the Transportation Finder

Choose button from the Function Specific toolbar



8-10

The Transport by Fiscal Year window is displayed

Enter ‘2017’ for the Fiscal Year as shown in Figure 183

Enter ‘100’ for the 1st Quarter Procurement Quantity

Enter ‘100’ for the 2nd Quarter Procurement Quantity

Enter ‘200’ for the 3rd Quarter Procurement Quantity

Enter ‘200’ for the 4th Quarter Procurement Quantity

Figure 183. Transport by Fiscal Year Window

Choose the Save button on the Main toolbar.

Close the Transport by Fiscal Year window

8.1.5 Adding Transportation Narrative

STEP To illustrate how to add transportation narrative data, do the following as shown and

described:

Select the record with LCN ‘A’, ALC ‘01’ from the Transportation Finder


The Transportation Narrative window is displayed

Select ‘D. Regulatory requirements’ from the Select Type of Narrative drop down list


Enter the following narrative: ‘Bicycles must be transported with ungreased chains in

environmentally sensitive areas.’


8-11

Figure 184. Transportation Narrative Window


Close the Transportation Narrative window

Close the Transportation Finder


8-12


ENTERING SUPPORT

EQUIPMENT AND

TRAINING MATERIALS

REQUIREMENTS

DATA

SECTION 9

EAGLE WORKBOOK DEF STAN 00-60 SECTION 9 ENTERING SE AND TRAINING MATERIAL DATA

9–3

SECTION 9 ENTERING SUPPORT EQUIPMENT AND TRAINING MATERIALS

REQUIREMENTS DATA

9.0 INTRODUCTION

This section provides an overview of the Support Equipment and Training Material Requirements

tables (E tables) and the Unit Under Test (UUT) Requirements and Description Tables (U Tables)

of DEF STAN 00-60. The E tables document information pertaining to existing or new support,

test, or training equipment required to operate or maintain the system/end item. The U tables

identify the UUT and those hardware and software elements required to test the UUT with off-line

support/test equipment. The unique combination of these elements required for a specific UUT

and support/test equipment configuration is a Test Program Set (TPS). In addition to defining the

TPS elements, this information provides the configuration identification of the UUT (i.e., the UUT

and the support/test equipment to be used in the test). This information is established for each

UUT that has a requirement to be tested by the support/test equipment documented. Additionally,

Calibration and Measurement Requirement Summary (CMRS) information is captured in these

tables.

9.1 ADDING SUPPORT EQUIPMENT AND UNIT UNDER TEST INFORMATION

Note: In order to add support equipment to the Support Equipment tables, reference number

data for the support equipment item must exist in table HA.

Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter

box and select the SERD Finder as illustrated in Figure 185.

STEP To illustrate how to use the SERD Finder, do the following as shown and described:

Make sure the BICYCLEXX end item assigned is selected

Double-click the SERD Finder function as shown in Figure 185


9–4

Figure 185. Navigator - Support Equipment

The SERD Finder is displayed

Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve all support

equipment records

Figure 186. SERD Finder Window – Records Returned


9–5

Info: The button on the Function Specific toolbar is used to add or delete a

reference number from the Support Equipment (EA) Table. SERD Numbers are assigned

using the button and the button allows documentation of

alternate NSNs of items which may be substituted for the particular support/training

equipment item.

The Reports/Process>>Alternate NSN menu item allows documentation of alternate NSNs of

items which may be substituted for the particular support/training equipment item. Additionally,

the buttons on the Function Specific toolbar may be utilized.

9.2 ADDING SUPPORT EQUIPMENT

STEP To illustrate how to add data into the Support Equipment Tables, specifically Support

Equipment or EA Table, do the following as shown and described:

With the SERD Finder displayed, make sure the BICYCLEXX end item assigned by

the EAGLE instructor is selected


The Support Equipment window is displayed

Enter ‘SE%’ into the CAGE Code query box as shown in Figure 187


All Reference Numbers that have CAGE Code ‘SE999’ are returned on the left

Select the record with CAGE Code ‘SE999’ and Reference Number ‘TH-1001’ from

the Item Identification box on the left

Choose the button to add the Cage Code/Reference Number to the

Support Equipment List


9–6

Figure 187. Support Equipment Window - Adding


Close the Support Equipment window and return to the SERD Finder

9.2.1 Assigning SERD Numbers

STEP To illustrate how to assign a SERD number, do the following from the SERD Finder as

shown:

Make sure the BICYCLEXX end item assigned is selected in the SERD Finder

Enter ‘TH%’ into the Reference Number finder field as shown in Figure 188

Choose the Execute button from the Main toolbar

Select the record with the SE CAGE ‘SE999’ and Reference Number ‘TH-1001’


Click the button to No Records Found’ message box


9–7

Figure 188. SERD Finder – TH-1001 Selected

The Support Equipment Recommendation Data window is displayed

Enter ‘0000001234’ into the SERD Number box as shown in Figure 189

Enter ‘ A’ into the SERD Revision box

Enter ‘20170317’ into the SERD Date of Initial Submission box

Enter ‘20170704’ into the SERD Date of Revision Submission box

Select ‘Approved’ from the SERD Status drop down list

Figure 189. SERD Recommendation Data Window


9–8


Close the SERD Recommendation Data window

9.2.2 Adding Support Equipment Data

Support Equipment information is added/maintained through the Support Equipment Data

window.

The Support Equipment Data Window consists of many tabs representing the various types of data

areas pertaining to the SERD report. Since there are multiple rows of tabs in the Support

Equipment Data Window, each row of tabs is brought to the front of the window when it is clicked

on. Therefore, it appears that the tabs are changing positions when in fact they are just being

brought to the front of the window to allow the data to be maintained.

9.2.2.1 Adding Support Equipment Narrative

STEP To illustrate how to add narrative for a piece of support equipment, do the following from

the SERD Finder as shown and described:


Select the record with the SE Reference Number of ‘TH-1001’


The Support Equipment Data window is displayed

Choose the Narrative tab as shown in Figure 190

Select ‘B. Description + function of SE’ from the Select Type of Narrative drop down

list

Enter 'The THANDLE provides a support mount for inspecting the bicycle assembly.'

in the Narrative box



9–9

Figure 190. Support Equipment Data Window - Narrative Tab

9.2.2.2 Adding a SERD Name and Administrative Data

STEP To illustrate how to add a SERD name to a piece of support equipment, do the following


Choose the Admin. Data tab on the Support Equipment Data window as shown in

Figure 191

Enter ‘BICYCLE’ into the End Article Designator box

Enter ‘HANDLE, T-EXTENSION’ into the SE Full Item Name box

Select ‘Yes’ from the Sketch box drop down list

Enter ‘N000XX-16-C-1234’ into the Contract Number field

Select ‘Contractor Furnished’ from the Cont. Furn. EQ. Govt. Furn. EQ. drop down

list

Select ‘Peculiar tools’ from the SE Item Category Code Drop down list


9–10

Figure 191. Support Equipment Data Window - Admin. Data Tab


Close the Support Equipment Data window

9.2.3 Running a SERD Report

The SERD Discipline provides the convenience of running many reports from the SERD Finder.

STEP To illustrate how to run an LSA-070 report from the SERD Discipline, do the following

as shown in Figure 192, Figure 193, Figure 194 and described:

Make sure the BICYCLEXX end item assigned is selected in the SERD Finder

window

Select the record with CAGE ‘SE999’ and Reference Number ‘TH-1001’ from the

SERD Finder

Choose Reports/Process>>Reports>>LSA-070 - Support Equipment

Recommendation Data from the Menu bar as illustrated in Figure 192

The LSA-070 SERD window is displayed


9–11

Figure 192. Reports/Process – Reports>>LSA-070

Note: Parameters used to run reports in EAGLE are saved in Parameter files. The Standard

Parameters shown in Figure 193 are supplied in an L070.prm file installed with EAGLE.

These parameters can be changed using the following instructions.

STEP To enter the standard parameters information for the SERD report, do the following as


Select the Standard Parameters tab by clicking on it

Enter the appropriate file name and directory for the Report File by selecting it with

the Browse button or entering it in manually

Enter the appropriate file name and directory for the Message File by selecting it with

the Browse button or entering it in manually

Info: When the LSA-070 report is run from the SERD Finder, the Specific Parameters are

inherited from the record selected in the SERD Finder.


9–12

Figure 193. LSA-070 SERD Standard Parameters Tab

STEP To enter the specific parameters information for the SERD report, do the following as


Select the Specific Parameters tab by clicking on it as shown in Figure 194

Make sure ‘TH-1001’ is in the Reference: box

Make sure ‘SE999’ is in the Cage box:

Choose the Execute button on the Main Toolbar to generate the SERD report

Figure 194. LSA-070 SERD Specific Parameters Tab

Choose if prompted to overwrite the report and/or message file


9–13

The EAGLE: Report Generator Completion Message may be displayed as shown in

Figure 195

STEP To view the SERD report after it has been generated, do the following as shown and

described:

Choose the button to display the SERD Report

Figure 195. Report Generator Completion Message

Choose the button when prompted to copy the report to Table ZD as

shown in Figure 196

Figure 196. Save Report to Table ZD


9–14

Click the button on the Document Imported dialog box as shown in

Figure 197

Figure 197. Document Imported Dialog Box

After viewing the report, close the Report Display Window

Close the LSA-070 SERD Parameter Window

Respond Yes if asked to save the parameters

Close the SERD Finder

9.2.4 Support Equipment and Unit Under Test Data Tabs

The button and the button on the Function Specific toolbar will retrieve

data windows that have multiple tabs on them. Instead of covering each of the tabs in detail, the

following tables are supplied to show which part of the SERD report the data is displayed in and

what LSAR tables are affected by each tab. The first table contains the Support Equipment Data

tabs and the second table contains the Unit Under Test Data tabs.


9–15

Table 1. Support Equipment Data Tabs - Table and SERD Relationships.

Support Equipment Data

Tabs

Support

Equipment

Tables Affected

SERD Report Section

Narrative EE Section 1. Description of RQMTS

(HEADER)

Admin. Data EA, EF, EH Section 2 Administrative Data

(HEADER) and Price Data Section

Physical Data EA Section 2 Administrative Data - Physical

Data Section

GFAE (System Equipment

Required)

EM Section 2 Administrative Data - System

Equipment Required (GFAE)

Articles Requiring Support UB, UA Section 2 Administrative Data - Articles

Requiring Support (ARS)

Rev. Remarks EG Section 2 Administrative Data

(HEADER) - Revision Remarks

Supercedure EK Section 3

Supercedure/Deletion/Distribution Data

(HEADER)

Allocation Data EA, EB Section 3.

Supercedure/Deletion/Distribution Data -

Allocation Data (HEADER)

Authorizations ED Section 3

Supercedure/Deletion/Distribution Data -

Specific Authorizations (HEADER)

Design Data EJ Section 4 Design Data (HEADER)

ILS Data EL Section 5 ILS Data (HEADER)

Parameters EC Section 6 SE Parameters and UUT

Related Information (HEADER)

Supplement EA N/A

UUT Data UM, UN N/A

Input Power Source EI N/A


9–16

Table 2. Unit Under Test Data Tabs - Table and SERD Relationships.

Unit Under Test Data

Tabs

Support

Equipment

Tables Affected

SERD Report Section

UUT Information UA, UB Section 6 SE Parameters and UUT Related

Information (HEADER) - UUT Related

Information (HEADER)

UUT Parameters UG Section 6 SE Parameters and UUT Related

Information (HEADER) - UUT Parameters

(HEADER)

Fault Isolation UH Section 6 SE Parameters and UUT Related

Information (HEADER) - Fault Isolated

Replaceable Units (HEADER)

Operational Test Programs UC, UD Section 6 SE Parameters and UUT Related

Information (HEADER) - Operational

ATE/TMDE Test Program (HEADER)

Test Position Instructions UD, UE Section 6 SE Parameters and UUT Related

Information (HEADER) - Test Program

Instruction (HEADER)

Test Adapters/Cables UI, UJ Section 6 SE Parameters and UUT Related

Information (HEADER) - Adapter/Cable

Set/Interconnecting Device (HEADER)

ATE UK, UL Section 6 SE Parameters and UUT Related

Information (HEADER) - ATE Test Station

(HEADER)

UUT Remarks UF Section 6 SE Parameters and UUT Related

Information (HEADER) - UUT Related

Remarks (HEADER)


ENTERING

PACKAGING AND

PROVISIONING

REQUIREMENTS

DATA

SECTION 10

EAGLE WORKBOOK DEF STAN 00-60 SECTION 10 ENTERING PACKAGING AND PROVISIONING DATA

10-3

SECTION 10 ENTERING PACKAGING AND PROVISIONING REQUIREMENTS DATA

10.0 INTRODUCTION

The Packaging and Provisioning Requirements (H tables) document packaging and provisioning

requirements including non-application dependent part data related to provisioning screening and

cataloging, packaging, and common maintenance data. Also documented in the H tables are data

items used to document data requirements for initial support requirements determination, repair

parts manual, and design change information. This section of the EAGLE Workbook provides an

overview of the creation and maintenance of H table data using the EAGLE Provisioning

Discipline.

10.1 ADDING REFERENCE NUMBER INFORMATION

When creating a logistics database, provisioning or parts data must be entered into the system.

The keys required to add part data in the database are the CAGE Code and the reference number.

The reference number information is stored in Table HA (Item Identification Table) and CAGE

Code information is stored in Table XH (Commercial and Government Entity Table).

To add reference number information into the database, access the Provisioning Finder from the

Provisioning Discipline utilizing the Navigator Home tab and Filter box as shown in Figure 198.

STEP To illustrate how to use the Provisioning Finder, do the following as shown and

described:


Double-click the Provisioning Finder function as shown in Figure 198

The Provisioning Finder is displayed

Info: The provisioning finder may be used to search for part data in table HG (only parts that

have an application) or table HA (parts with or without applications). If the 'Display

Only Parts That Have an Application' checkbox is unchecked, all part data for parts

meeting the selection criteria will be returned, including data for parts that do not have

HG entries.


10-4

Figure 198. Navigator – Provisioning Finder Selected

Make sure the ‘Display Only Parts That Have an Application’ checkbox is checked as

shown in Figure 199

Choose the Execute button on the Main toolbar or ALT+Q,E

Figure 199. Provisioning Finder – Records Returned


10-5

10.1.1 Adding CAGE Codes (XH)

CAGE Code information can be entered in two ways. The method chosen to add CAGE Codes

depends on the user’s intent. The two methods are summarized below:

The first method of adding new CAGE Codes is using the LCN Maintenance Discipline. This

method should be used if new CAGE Codes need to be entered without reference number

information. The LCN Maintenance Discipline is also used to add multiple CAGE

Codes. For instructions on how to use this method, refer to Paragraph 2.7.

A second method of adding CAGE Codes may be used if a reference number is to be added with a

CAGE Code that doesn’t already exist. Normally, when entering reference number

information into the database, the Provisioning Discipline is used. Therefore, new CAGE

codes can be entered for reference numbers from the Provisioning Discipline.

It is presumed that the Provisioning Finder has been executed as described in Paragraph 10.1.

After data has been retrieved from the Provisioning Finder, new provisioning parts may be added

using the button on the Function Specific toolbar.

STEP To illustrate adding a new CAGE code, do the following from the Provisioning Finder as


With the Provisioning finder displayed as shown in Figure 200 with records returned,

in this example with the ‘Display Only Parts That Have An Application’ checkbox

unchecked



10-6

Figure 200. Provisioning Finder – All Parts Displayed

The New Part Information window is displayed

Once the New Part Information window as shown in Figure 201 is displayed, reference number

information may be added. The reference number information includes CAGE Codes; therefore,

an Enter New CAGE button has been added to the New Part Information window for ease in

adding new CAGE Codes while entering reference number information.

STEP To illustrate adding a CAGE Code into the EAGLE database, do the following from the

New Part Information window as shown in Figure 201, Figure 202 and described:


Choose the button

A blank row is inserted


10-7

Figure 201. New Part Information Window - CAGE Code Data

Enter ‘TCAGE’ into the CAGE Code box as shown in Figure 202

Enter ‘BIKES PLUS’ into the Name box


Figure 202. New Part Information Window – New Cage Code Added


10-8

10.1.2 Adding Reference Number Information (HA)

STEP Do the following in the New Part Information window to add a new reference number

with the new CAGE Code as shown in Figure 203, Figure 204 and described:

Find ‘TCAGE’ from the CAGE Code list. Note: The TCAGE entered in paragraph

10.1.1 appears alphabetically towards the bottom of the list so scroll down to find it or

enter ‘T’ in the Find: field as shown in Figure 203:

Click on the TCAGE record. The Item Identification portion of the window is

activated

Figure 203. New Part Information Window – Find: T

Enter ‘WH-ATB-36-TC’ into the Reference Number box as shown in Figure 204

Enter ‘HANDLE BAR’ into the Item Name: box

Enter ‘1234’ into the FSC portion of the NATO Stock Number

Enter ‘456789123’ into the NIIN portion of the NATO Stock Number

Figure 204. New Part Information Window - Reference Number


10-9

Enter '9' in the Special Material Content Code: box (Figure 205)

Enter ‘24.95’ into the Unit of Measure Price box

Select 'Pound Sterling' from the Unit of Measure Price Currency Code: drop down list

Select ‘EACH’ from the Unit of Measure drop down list (if not defaulted)

Select ‘2’ from the Ref. Num. Variation Code drop down list

Select ‘Design control reference’ from the Ref. Num. Category Code: box

Figure 205. New Part Information Window – Reference Number Data Cont’d

Choose the Save button

Close the New Part Information window

10.1.3 Adding Additional Reference Number Information (HB)

It is presumed that the Provisioning Finder remains open from the previous STEP.

Note The additional reference number CAGE code must exist in table XH before it can be used

with the additional reference number.

STEP To add an additional reference number (HB) record, do the following as shown and

described:

Enter ‘T%’ into the CAGE Code Finder box as shown in Figure 206

Uncheck (if checked) the 'Display Only Parts That Have An Application' checkbox


10-10

Figure 206. Provisioning Finder – Top Portion

Choose the Execute button on the Main toolbar. Figure 207 is displayed

Make sure to select the record with Item Name ‘HANDLE BAR’ as shown


The View/Edit Provisioning Data window is displayed

Figure 207. Provisioning Finder – Record Returned

Choose the HB tab as shown in Figure 208

Enter ‘99999’ into the ARN Cage Code box

Enter ‘2350101-100’ into the Additional Reference Number box


10-11

Figure 208. View/Edit Provisioning Data Window – HB Tab Selected


Close the View/Edit Provisioning Data window

10.2 ADDING PART APPLICATIONS (HG RECORDS)

It is presumed that the Provisioning Finder has been selected from the Provisioning Discipline

using the Navigator and that the previous STEPs have been completed.

STEP To illustrate adding an HG record, do the following as shown and described:

Select the record where the CAGE is ‘TCAGE’ and the Reference Number is ‘WH-

ATB-36-TC’ from the Provisioning Finder


The Part Application Information - HG Window is displayed

Click the button (Figure 209)


10-12

Figure 209. Part Application Information – HG Window

The LCN Finder window is displayed

STEP Search for an existing LCN to link the reference number information to by doing the

following:

Choose the button at the bottom of the LCN Finder window

Since the LCN to which reference number ‘WH-ATB-36-TC’ is to be linked has not

been established, it can be created

Choose the button. A blank row is inserted (Figure 210)

Figure 210. Part Application - LCN Finder Window


10-13

Enter ‘A01AB’ into the LSA Control Number (LCN) box as shown in Figure 211


Select ‘P’ from the Type drop down list

Enter ‘HANDLE BAR’ into the LCN Name box

Choose the button

Make sure that LCN ‘A01AB’ with ALC ‘02’ is selected as shown in Figure 211

Choose the button

Figure 211. LCN Finder Window – Save Changes

Choose the button when prompted 'Do you want to save HG

changes?'


10-14

STEP Cont’d:

Enter '1' for Quantity per Assembly as shown in Figure 212

Enter ‘PAOZZ’ in the Source, Maintenance, and Recoverability (SM&R) Code box

Note: The button may be used to select each position of the SMR Code

from drop-down lists.

Select ‘Repair Part (non-rep consumable)’ from the Item Category Code: drop down

list


Close the Part Application Information - HG Window

Figure 212. Part Application Information - HG (SMR Code)

Choose the Execute button on the Main toolbar to display the added part application

information

Use the scroll bar to view the added part application information as shown in Figure

213


10-15

Figure 213. Provisioning Finder – Added Part Application Information

10.3 MAINTAINING OTHER PROVISIONING DATA ELEMENTS USING THE VIEW/EDIT

PROVISIONING DATA WINDOW

The View/Edit Provisioning Data Window allows provisioning data to be entered or updated by

individual table. When a record is selected from the Provisioning Finder and the

button is selected, a Summary Tab containing information from tables HA, HB and HH is initially

displayed as shown in Figure 214 as an example.

Figure 214. View/Edit Provisioning Data - Summary Tab


10-16

Also available are tabs for provisioning tables, HA-HR. (Tables HS-HV are accessed through

another window.) To review, maintain or establish data in any of these tables for the record

selected in the Provisioning Finder, click on the tab for the desired table.

10.3.1 Maintaining Provisioning Data (Table HA)

It is presumed that the Provisioning Finder has been selected from the Provisioning Discipline

using the Navigator and records are displayed by choosing the Execute button.

STEP To illustrate maintaining provisioning data, do the following as shown and described:

Make sure the record with CAGE Code ‘TCAGE’ and Reference Number ‘WH-ATB-

36-TC’ is selected


Choose the HA tab as shown in Figure 215

Scroll down and enter ‘100’ in the Haz. Waste Storage Cost: box

Select 'Pound Sterling' from the Haz. Waste Stor. Cost Cur. Code: drop down list

Enter '5' in the Unit Weight (+ Formatted Value) box

Select 'Kilogram' from the Unit Weight UOM drop down list

Select 'Repairable Item, Does Not Need IPC' from the Spare Parts Classification drop

down list (right column, scrolled up from the view shown in Figure 215


Figure 215. View/Edit Provisioning Data Window - HA Tab Selected


10-17

10.3.2 Entering Provisioning Remarks

STEP To illustrate adding provisioning remarks; do the following as shown and described. It is

assumed the View/Edit Provisioning window remains open from the previous STEP:

Choose the HI tab

Make sure is selected from the drop down list box

(right side of screen) as shown in Figure 216

Enter the following provisioning remarks narrative: 'Handlebar, P/N WH-ATB-36-

TC, will no longer be available from BIKES PLUS effective 11/01/2017.'


Figure 216. Adding Provisioning Remarks – HI Tab

10.3.3 Adding Provisioning UOC Data

It is assumed the View/Edit Provisioning window remains open from the previous STEP.

STEP To illustrate adding provisioning UOC data, do the following as shown and described:

Choose the HO tab as shown in Figure 217

Select the record with UOC of 'TR1' from the list of XC records (box on lower left

corner)

Choose the button to add an HO record. (mapping the HANDLEBAR to

the ALC ‘02’ BICYCLE



10-18

Figure 217. Adding Provisioning UOC Data

10.3.4 Adding Item Packaging Requirement Data

It is assumed the View/Edit Provisioning window remains open from the previous STEP.

STEP To illustrate adding item packaging requirement data, do the following as shown and

described:

Choose the HF tab as shown in Figure 218

Choose the button


10-19

Figure 218. Adding Item Packaging Requirement Data

The Select Packaging Data window is displayed

Select '0 No Packing Reqd.' as shown in Figure 219

Choose the button to return to the View/Edit Provisioning Data window

Note: As an alternative to using the Available Codes button, the user may select the appropriate

entry for Degree of Protection Code from the drop down list.

Figure 219. Select Packaging Data Window

Scroll to the right and enter '5' in the Unit Pack Weight (+ Formatted Value): box as

shown in Figure 220

Select 'Kilogram' from the Unit Pack Weight UOM: drop down list

Enter '50' in the Unit Pack Length: box

Enter '25' in the Unit Pack Width: box

Enter '10' in the Unit Pack Depth: box


10-20

Select 'Each' from the Unit Pack Size UOM: drop down list


Your screen should reflect Figure 220

Figure 220. View/Edit Provisioning Data Window – HF Tab

10.3.5 Adding Design Change Information

It is assumed the View/Edit Provisioning Data window remains open from the previous STEP.

STEP To illustrate adding Design Change Information, do the following as shown and

described:

Choose the HP tab as shown in Figure 221

Enter ‘ECP-0001-2017’ for Change Authority Number:



10-21

Figure 221. View/Edit Provisioning Data Window – HP Tab

Close the View/Edit Provisioning Data window

Close the Provisioning Finder


10-22


AD HOC REPORTING

SECTION 11

EAGLE WORKBOOK DEF STAN 00-60 SECTION 11 AD HOC REPORTING

11–3

SECTION 11 AD HOC REPORTING

11.0 INTRODUCTION

The AdHoc Discipline allows the user to define and generate unique or one-shot reports based on

a particular instance, or ad hoc need, rather than the generation of standard reports. If certain ad

hoc reports are required to be run periodically, or complex reports are developed, they can be

stored in the database or to disk as a file.

User-friendly screens are provided to assist the user in constructing the transaction statements

necessary to produce the desired report. These screens generate the actual SQL statements that

operate on the relational database to assemble the desired data.

Once a query is created and executed, the resulting data is displayed. These results can be saved,

printed or updated. Updates performed on the AdHoc results data are posted back to the database

when the data is saved. Editing permissions on tables are set by the database administrator.

11.1 SQL TRANSACTION STATEMENTS

The constructs involved in an SQL transaction are familiar to anyone with some programming

experience in a high-level language (BASIC, Pascal, C, etc.). Although this familiarity is not

absolutely necessary, it will help in understanding the concepts and principles involved in the

underlying SQL transaction. Appendix A provides a detailed overview of SQL.

11.1.1 New Query

Access the AdHoc Discipline from the Navigator and select the New Query Function as illustrated

in Figure 222.

Double-click the New Query Function as illustrated in Figure 222 or click the button

on the Main toolbar. The New Query window will be displayed as shown in Figure 223.


11–4

Figure 222. Navigator Discipline - New Query Function Selected

11.1.1.1 Query Table Selection

The database table for the query must be selected first. The columns shown in the DATABASE

TABLES box on the left side of the screen display the different database tables available.

The TABLE NAME column displays the table name that will be used in the query. Tables that are

to be used in the query should be highlighted. Once a table is selected for a query, the Database

Columns box on the right is updated to reflect the current column information. Each time a table

is selected, the columns are updated to reflect the correct table columns.

In order to select a database table from the DATABASE TABLES box, single click on the

database table. If a database table is no longer desired, double-click on the database table and it

will be deselected.


11–5

Figure 223. New Query Window

Since there are so many tables used in the EAGLE database, the DATABASE TABLES list can

take time to scroll through to find the table needed. To make selecting a table more efficient, a

functional area drop down list box has been added above the DATABASE TABLES list as shown

in Figure 224. In this example, the CROSS REFERENCE DATA (X Tables) option is selected

from the functional area drop down list. After the selection, the DATABASE TABLES list

automatically scrolls to the X Tables on the right.

Figure 224. New Query Window (portion) - Functional Area Selected


11–6

A second option is available to make Table selection more efficient. Utilize the Find Table:

Finder box (Figure 225), by entering the desired Table. Figure 225 is shown after Table HA has

been selected in the next STEP.

STEP To illustrate how to select a table to be used in the query, do the following from the New

Query window as shown in Figure 225 and described:


Enter ‘H’ in the Find Table: field

Select Table HA from the Table Selections and notice that the columns are

automatically filled in on the right hand side of the screen under DATABASE

COLUMNS

Figure 225. New Query - Table Name ‘HA’ Selected

Now that a table is selected, the columns for the query must be selected.

11.1.1.2 Query Column Selection

The DATABASE COLUMNS box on the right hand side of the window allows selection of the

various columns from a table for queries. If a table is not selected, only the column headers are

displayed. As table columns or fields are selected, they are put in the query area at the bottom of

the window. These fields will be used in the generation of the final query on the database.


11–7

In order to select database columns or fields, single click on the database column. If a selected

column is no longer desired, double-click on the database column and it will be deselected. The

radio buttons at the top of the column list allow the user to select different types of queries. For

example, the ALL (NAMES) radio button selects all the columns in the table and puts their name

in the query.

STEP To illustrate how to select the table columns to be used in the query, do the following

from the New Query window as shown in Figure 226. It is presumed that the table has

already been selected as shown in the previous STEP:

Choose the ONLY KEY/MANDATORY radio button to select columns from the

table that are keys

Choose the ITNAMEHA field by clicking on it in the DATABASE COLUMNS list

Notice that the query statement is being built at the bottom of the screen as the radio button and

the Column Name is selected.

Figure 226. New Table Column Selection


11–8

11.1.1.3 Generating the AdHoc Report

STEP To generate a report (query) click the Execute button on the Main toolbar or ALT+Q, E.

Figure 227 illustrates the AdHoc Query Results for New Query:


Notice that the Query Results for New Query window title bar contains the time the query was

executed so that the user knows when the query was ran. In addition, the New Query window title

bar is also updated with the execute time. This allows the user to identify which query script goes

with which results in the case that more than one query or results window is open.

Info: Columns may be rearranged in the Query Results window by dragging a column header

to the desired location. Additionally, clicking the button will

compress the column data to the left

Close the Query Results for New Query window

Leave the New Query window open for the next STEP

Figure 227. Query Results for New Query - Simple Query


11–9

11.1.1.4 Establishing Query Selection Criteria

A query without selection criteria returns all rows in a table. This could be a large amount of data.

To narrow down the amount of data returned to a more precise set, selection criteria can be

established. The Select Criteria buttons on the function specific toolbar are used to create

selection criteria for the query.

The Select Criteria buttons allow Where, Sort, and Join conditions to be set for queries. These

conditions are used in queries to control which data should be selected, how the data should be

sorted, and what join requirements exist between tables. When a Select Criteria button is selected,

a window appears displaying a dialog edit box with options for creating the desired condition.

The Where and Sort buttons are always available after a table and its columns are selected.

However, the Join button is only available if two or more tables are selected.

11.1.1.5 Multiple Tables in ADHOC Queries – Joining Tables

In the following steps, multiple tables will be added to the query from the previous step (HA

Query). Whenever multiple tables are included in a query, data in the tables must be related or

‘joined’. This insures that valid data will be returned.

STEP Add LCN and SMR Code information from table HG to the query by doing the following


Make sure your New Query window is open from the previous STEP

Scroll down if necessary and select Table ‘HG’ from the Table Selections and notice

that the columns are automatically filled in on the right hand side of the screen under

DATABASE COLUMNS

Choose the following fields from the DATABASE COLUMNS list by clicking on

them: ‘LSACONXB’, ‘ALTLCNXB’, ‘QTYASYHG’, ‘SMRCODHG’ (scroll down

about halfway)

STEP Join tables HA and HG by doing the following as shown and described:


The Join Criteria window is displayed

Notice under Join Common Fields on the right side, the Matching Join radio button is selected.


11–10

Choose the button. The Join criteria is added in the window as

shown in Figure 228

Choose the button

Figure 228. Join CriteriaWindow – HA Joined to HG

NEXT The HO table links Part Applications in the HG table to a System/End Item UOC in table

XC. So that we may query for a single BICYCLE configuration by UOC, we must add

table HO to the query.

STEP Add UOC cross reference data from table HO to the query by doing the following as


Scroll down and select Table ‘HO’ from the Table Selections and notice that the

columns are automatically filled in on the right hand side of the screen under

DATABASE COLUMNS


11–11

Choose the following fields from the DATABASE COLUMNS list by clicking on

them: ‘LCNSEIHO’, ‘ALCSEIHO’

Figure 229. New Query window - Table HO Selected

STEP Join tables HG and HO by doing the following as shown and described:

Choose the button from the Function Specific toolbar. The Join Criteria

window is displayed

Select the ‘HG’ table from the TABLE 1 drop down list as shown in Figure 230

Select the ‘HO’ table from the TABLE 2 drop down list

Choose the button

Choose the button


11–12

Figure 230. Join Criteria - HG Joined to HO

STEP Add UOC from table XC to the query by doing the following as shown and described:

Enter ‘XC’ into the Find Table: field as shown in Figure 231

Select Table ‘XC’ from the Table Selections and notice that the columns are

automatically filled in on the right hand side of the screen under DATABASE

COLUMNS.

Choose ‘UOCSEIXC’ from the DATABASE COLUMNS list by clicking on it


11–13

Figure 231. New Query Window – Table XC Selected

NEXT Be careful when doing the next STEP. We will not use the Matching Join option;

individual columns will be selected for this portion of the exercise. The Join Common

Fields is not used when joining table HO to table XC because two sets of LCN/ALC data

exists in table HO. Use of the Join Common Fields in this case would cause erroneous

results.

STEP Join tables HO and XC by doing the following as shown and described:


The Join Criteria window is displayed

Select the ‘HO’ table from the TABLE 1 drop down list as shown in Figure 232

Select the ‘XC’ table from the TABLE 2 drop down list

Select ‘EIACODXA’ from the TABLE 1 (HO) field list by clicking on it

Select ‘EIACODXA’ from the TABLE 2 (XC) field list. Notice the join criteria are

generated in the white space


11–14

Figure 232. Join Criteria - HO Joined to XC

STEP Continue joining tables HO and XC by doing the following:

Click on ‘LCNSEIHO’ (TABLE 1) (scroll down)

Click on ‘LSACONXB’ (TABLE 2) as shown in Figure 233

Click on ‘ALCSEIHO’ (TABLE 1)

Click on ‘ALTLCNXB’ (TABLE 2)

Click on ‘LCNTYPXB’ (TABLE 1)

Click on ‘LCNTYPXB’ (TABLE 2)

Choose the button


11–15

Figure 233. Join Criteria Window – LCNSEIHO Selected

At this point, your New Query should match the New Query window shown in Figure 234. Leave

the New query window open for the next STEP.

Figure 234. New Query Window for Multi-Table Query


11–16

11.1.1.6 Where Criteria

The Where criteria restricts which data is included in the query results. A Where clause may be

created by typing it at the end of the SQL statement in the bottom of the window, or by using the

Where button located on the Function Specific toolbar. Whenever a database column is compared

to a character string, the character string must be enclosed in single quotes . Double quotes should

never be used.

STEP To illustrate how to create selection criteria to be used in the query, do the following

from the Where Criteria window as shown and described:


The Where Criteria window is displayed

Select table ‘XC’ from the TABLE/COLUMNS drop down list as shown in Figure

235

Select ‘UOCSEIXC’ from the Column Name

Select the ‘=‘ Operator, which is followed by a single quote to start the search string

Enter ‘LX2’ in the Where Criteria window followed by a ‘single’ quote

Choose the button to return to the New Query Window


11–17

Figure 235. Where Criteria Window – Table XC Selected

11.1.1.7 Sort Criteria

The Sort Criteria allows selection of which column or field to sort on and what order they should

be sorted. The sort choices are ascending (ASC) or descending (DESC) order. Appropriate

operators are inserted into the Sort (Order By) window when multiple columns or fields are

required.

STEP Enter Sort Criteria by doing the following as shown and described. It is assumed the New

Query window is open and displays the results of the previous STEP:


The Sort (Order by) Criteria window is displayed

Select 'HG' from the Table Name list in the lower left side of the Sort (Order By)

Criteria window as shown in Figure 236

Click on the ‘LSACONXB’ column

Click on the ‘ALTLCNXB’ column


11–18

Choose the button

Figure 236. Sort (Order By) Criteria Window


Click the button as shown in Figure 237

Your screen should reflect the results shown


11–19

Figure 237. Query Results for New Query – 41 Rows Returned

This query has returned a top down breakdown of the baseline bicycle LCN ‘A’ ALC ‘00’ (UOC

‘LX2’).


11.1.2 Adding Comments to Queries

STEP To illustrate adding comments or documentation to queries, do the following as shown

and described:

In the New Query window, make sure the cursor is placed at the end of the query

developed in the previous exercises


11–20


The Adhoc Comments window is displayed

Enter the following comment ‘This query was developed for the EAGLE Training

Class by Studentxx aka (your name)’ as shown in Figure 238

Choose the button

Figure 238. Adhoc Comments Window

Notice in the New Query window that the comment narrative has been added to the top of the

query, bracketed by ‘/*’ and ‘*/’.

Execute the Query using the Execute button on the Main toolbar

Close the Query Results window

11.1.3 Saving Report Information

Once a report has been created using the New Query window, it can be saved to a file. In

addition, the SQL query statement that was used to create the report can be saved to the database

as a file for future use. It is helpful to save the SQL query statement for queries that are used

often. This saves time by providing the ability to recall an existing query instead of having to

create it every time. For more information on recalling queries, refer to Paragraph 11.1.3.3.


11–21

11.1.3.1 Saving Query Scripts

The ability to save the SQL query statement that produced the AdHoc report results is a very

powerful tool. Once an SQL query statement has been saved into the database or a script file, it

can be re-used at any time by recalling the query as shown in Paragraph 11.1.3.3. When queries

are saved to disk, the process is similar to opening a file in the Windows operating system and will

not be performed here.

STEP Do the following to save the query script to the database for later use in Paragraph

11.1.3.3:

Make sure the New Query window is open from the previous STEP


Choose the button on the Query Location dialogue box

In the Saved Queries window as shown in Figure 239 select ‘Provisioning’ from the

Query Type drop down list from the data portion of the window (purple rectangle)

Enter ‘Query to Generate Topdown Breakdown of Bicycle Assembly’ in the

Comments: box

Figure 239. Query Save Window

Choose the button on the Query Save window

Choose the button to return to the New Query window


11–22

11.1.3.2 Saving Report Output

The ability to save query results is provided by the File>>Save As menu item. Once a query has

been executed and the Query Results Window is displayed, the output can be saved as various file

types. Some of the common types are Excel Format (*.XLS), Text Format (*.TXT), and dBase

Format (*.DBF). However, the most commonly used is the Excel Format (*.XLS).

When a report is saved in Excel Format, the keys can be edited in Excel and then loaded back into

the database as new data using AdHoc. For specific examples on loading external data into the

database using AdHoc, refer to Paragraph 11.1.6.

In order to save report results, the Query Results window must be displayed with the output.

STEP To save report results, do the following:

Execute the Query (topdown breakdown) using the Execute button on the Main

toolbar or ALT+Q, E.

STEP Do the following as described to save the report output:

Choose the File>>Save As menu item

The Save Rows As window is displayed

Select the Training Folder (if provided) from the Save in: drop down list

Enter ‘Training1’ for File Name:

Make sure the Save as type is Excel Format (*.XLS)

Choose the button

Close the Query Results window

Close the New Query window

The student may use MS Excel to view, edit, or format the report output.

11.1.3.3 Recall Query

The Recall Query function allows queries to be recalled from either the database or a disk. In the

exercise below, the query saved to the database in paragraph 11.1.3.1 will be recalled, edited and

executed.

Access the AdHoc Discipline from the Navigator and select the Recall Query Function as

illustrated in Figure 240.


11–23

11.1.3.4 Recalling Queries from the Database

STEP To recall the query saved to the database in paragraph 11.1.3.1, do the following as



Double-click the Recall Query function as shown in Figure 240

The Query Location Dialogue box is displayed

Figure 240. Navigator – AdHoc>>Recall Query

Choose the button on the Query Location dialogue box

The Saved Queries window is displayed

Select ‘Provisioning’ from the Query Type drop down list (purple rectangle) as shown

in Figure 241

Choose the button on the Saved Queries window


11–24

Note: If multiple Provisioning query type records exist, a scroll bar will appear on the window,

enabling the user to scroll through the returned records.

Select the query titled ‘Query to Generate Topdown Breakdown of Bicycle

Assembly’ in the Comments: box

Make sure this is the Query developed by ‘Studentxx’ aka (your name)

Choose the button to open the saved query

The Recall Query window is displayed

Figure 241. Query Save Window – Recalling Saved Queries

At this point the query may be edited in the text window. The original query produced a top down

breakdown of the baseline bicycle.

STEP To edit the query to produce a top down breakdown of an alternate bicycle configuration,

do the following as shown and described:

Change XC.UOCSEIXC = ‘LX2’ to ‘LH3’ in the Recall Query window as shown in

Figure 242




11–25

Figure 242. Recall Query Window – XC.UOCSEIXC ‘LH3’

The Query Results for Recall Query window is displayed

Click the button

Note that the ‘ALC 01’ configuration BICYCLEXX is displayed ‘LH3’ UOC

Figure 243. Query Results Window – 'LH3' Usable on Code


11–26

Close the Query Results for Recall Query window

Close the Recall Query window

11.1.4 Updating the Database with Query Results

After a query has been executed and the Query Results window is displayed, the data can be

updated. However, the only time data can be updated is when all keys fields of a table are

displayed. There are two ways to update the data results. The first method is using the Query

Results window and the second method is using the ‘Multi-Cell Cut, Copy, Paste’” option. The

Multi-Cell Cut, Copy, Paste option should only be used to update blocks of data (multiple cells in

multiple rows) from blocks (matching size) of data on the Windows clipboard. The Multi-Cell

Cut, Copy, Paste option should not be used to load new records or to update single fields.

11.1.4.1 Updating the Database (Query Results Window)

STEP To illustrate editing query results using the Query Results window, do the following as


Access the AdHoc Discipline utilizing the Navigator and select the New Query

Function

Double-click the New Query Function

The New Query window is displayed

Select the HG table from the Database Tables list as shown in Figure 244

Select the ‘Only Key/Mandatory’ radio button

Select the ‘SMRCODHG’ field from the Database Columns list

Figure 244. New Query – Table HG


11–27

Select the button on the Function Specific toolbar

The Where Criteria window is displayed

From the TABLE/COLUMNS list, select the ‘SMRCODHG’ column as shown in

Figure 245

From the OPERATORS list, select ‘is null' (The ‘is null’ operator will find records

for which data has not been established for the column.)


Figure 245. Where Criteria Window - SMRCODHG


Replace the ‘Null’ (blanks) in the SMRCODHG column with ‘PAOZZ’ as shown in

Figure 246


11–28

Figure 246. Editing Data in the Query Results Window


Note: The Query Results window will be updated after the data is saved. Since there are no

longer any records that meet the selection criteria (null SMR code), a ‘No Records

Found’ message is displayed.

Click the button on the ‘No Records Found Dialog’ box

Close the Query Results and New Query Windows

11.1.4.2 Updating the Database (Multi-Cell Cut, Copy, Paste Window)

The second method for updating data in the AdHoc Discipline is the ‘Multi-Cell Cut, Copy, Paste’

option. By choosing the button on the Function Specific toolbar, the user is taken into

a spreadsheet environment that allows them to perform multi-cell cut, copy, and paste functions.

STEP To illustrate the Multi-Cell Cut, Copy, Paste function, do the following as shown and

described:

From the Navigator open the New Query window by double clicking on the New

Query function of the Adhoc Discipline

Select the HA table form the Database Tables list

Select the ‘ALL (NAMES)’ radio button


11–29


From the TABLE/COLUMNS list, select the ‘REFNUMHA’ column (Figure 247)

From the OPERATORS list, select ‘like’ (The “like” enables wild card queries).

Since REFNUMHA is an alphanumeric field, a single quote is placed after the like

operator (For fields defined as alphanumeric or character data, search criteria must be

enclosed in single quotes)

After the single quote, type ‘MC%’ (The % wildcard character will return any

characters, any length string)

Close the search criteria string with a single quote (')


Figure 247. Where Criteria Window


11–30

Select the button from the Function Specific toolbar

Select 'REFNUMHA' from the COLUMN NAME list


Your New Query window should reflect Figure 248

Figure 248. New Query Window – MC%


The Query Results for New Query window is displayed

Notice that all reference numbers (ha.refnumha) begin with ‘MC’


The data is exported to the Multi-Cell Cut, Copy, Paste editor


11–31

Note: We will copy and paste two cells in the spreadsheet.

Click on the ha.inamecha field for ha.refnumha of ‘MC-168119’ (The value selected

should be ‘77777’) as shown in Figure 249

Hold the shift key down and select the ha.inamecha for the next record (The value

should also be (‘77777’)

Figure 249. Query Results for New Query – Alt Editor


Place the cursor in the ha.inamecha field for ha.inamecha of ‘MC-JY-100’ as shown

in Figure 250


The data on the clipboard is pasted into the ha.inamecha field for the two BRAKE

ASSY


11–32

Figure 250. Alt Editor – Cells Copied



Note: To perform the exercise in paragraph 11.1.6, an excel spreadsheet containing table HA

data will be required. At this time we will create such a spreadsheet by saving the data

used in this exercise.

STEP To save the data from the Query Results window do the following as shown and

described:

With the New Query window open from the previous STEP, choose the Execute

button on the Main toolbar

Choose File >> Save As menu option. You may also choose the button on

the Function Specific toolbar and open a spreadsheet (careful of leading zero’s)

The Save Rows As window is displayed

Select Training folder (if provided) from the Save in: drop down list

Enter ‘Training 2’ in the File Name box

Choose the button on the Save Rows As window




11–33

11.1.5 Key Field Updates and Parent Table Deletes

When changes are made to key fields, the change must be applied to all child tables of the table

changed. In EAGLE, this is accomplished through ‘stored procedures’, collections of SQL

statements for which execution plans have already been figured out. When selected, the ‘Flow

key field changes down to child tables’ checkbox executes the appropriate stored procedure for the

table selected when changes are saved. Changes can be edits to key fields or parent table record

deletes. When an edit is made to a key field, an update stored procedure is executed. Similarly,

when a record with dependent data is deleted, a delete stored procedure is executed.

STEP To illustrate key field updates, do the following as shown and described:



Select the CA table from the Database Tables list



From the TABLE/COLUMNS list, select the ‘TASKCDCA’ column

From the OPERATORS list, select ‘like’ (The ‘like’ enables wild card queries)

After the single quote, type ‘A%’ (The % wildcard character will return any


Close the search criteria string with a single quote (')



The Query Results for New Query window is displayed

Select the record with ca.lsaconxb of 'A', ca.altlcnxb of '00', and ca.taskcdca of

'AACOCAA' as shown in Figure 251

Edit the third position of the task code (ca.taskcdca column) from a 'C' to a 'D'. (This

changes the maintenance level for the task from operator/crew to depot.)

Check the ‘Flow key field changes down to child tables’ checkbox


11–34

Figure 251. Query Results Window – Key Field Changes


The change is applied to the CA Table and all of its child tables



11.1.6 Loading External Data

Data can be loaded from external files into the database using AdHoc. AdHoc performs its

external data loading using the Windows concept of copying and pasting to the Clipboard. Data is

most commonly loaded from an Excel Spreadsheet, so the AdHoc Discipline has a Paste

Spreadsheet option. The data is actually copied out of the spreadsheet and inserted into the

AdHoc Query Results window. In order to insert data from a spreadsheet, all columns in the

selected table must exist in the Query Results window.

STEP Load the spreadsheet created in Paragraph 11.1.4.2 (Training2) into the database using

AdHoc by doing the following as shown and described:



Select the HA table form the Database Tables list



11–35


From the TABLE/COLUMNS list, select the ‘REFNUMHA’ column

From the OPERATORS list, select ‘like” (The “like” enables wild card queries).

Since REFNUMHA is an alphanumeric field, a single quote is placed after the like

operator (For fields defined as alphanumeric or character data, search criteria must be

enclosed in single quotes)

After the single quote, type ‘MC%’ (The % wildcard character will return any


Close the search criteria string with a single quote (‘)



Open the ‘Training 2.XLSX’ saved in Paragraph 11.1.4.2 with MS Excel

Note: Because the data in the spreadsheet already exists in the database, a key field must be

changed in order to establish new records.

Use Excel to change the ‘MCs’ in the REFNUMHA column to ‘NCs’ in your

spreadsheet

Select the entire spreadsheet (except for the header row) With the NC% and copy it to

the clipboard (CTRL-C)

Return to the Query Results window

Choose button on the Function Specific toolbar

Click the button to rows added message


Note: The new records will not be displayed when the query results are refreshed because the

‘NC’ part numbers do not meet the search criteria in the original query.



Change the ‘MC%’ in the where criteria box to ‘NC%’


11–36


Choose the Execute button on the Main Toolbar. Notice that all reference numbers

(REFNUMHA) begin with ‘NC’




INTERPRETING

ERROR MESSAGES

SECTION 12

EAGLE WORKBOOK DEF STAN 00-60 SECTION 12 INTERPRETING ERROR MESSAGES

12–3

SECTION 12 INTERPRETING ERROR MESSAGES

12.0 INTRODUCTION

This section provides information on common types of error messages in EAGLE and provides a

methodology for interpreting their meanings. The error messages displayed in EAGLE vary

depending on the database system in use. For Oracle systems, there are six common types of error

messages that can occur.

12.1 ERROR MESSAGES IN EAGLE

For EAGLE databases on Oracle systems, the six common error types are:

1) Security Violations

2) Unique Constraint Violations

3) Integrity Constraint Violation – Parent Key Not Found

4) Integrity Constraint Violation – Child Record Found

5) Data Element Cross Edit Violation

6) Violation of a Rule Bound to a Column

12.1.1 Security Violations

Security violations in EAGLE result when a user attempts to access, add, modify or delete data

without having the appropriate permissions. On Oracle versions of EAGLE, users must have a set

of permissions established. These permissions are based on End Item and ownership codes. In

order to access a data record, a user must have permission on the End Item and have a select

ownership associated with their userid that matches the ownership code of the record being

accessed. To modify or delete existing data, a user must have permission on the End Item and

have an ownership code associated with their userid matching the ownership code of the record

being modified or deleted. To add a new record, a user must have permission on the End Item. If

this is the case, the ownership code associated with the user's userid will be attached to the record.

Figure 252 is an example of an error message displayed when a security violation occurs.


12–4

By clicking the button the error message, the Structured Query Language (SQL)

for the failed transaction can be displayed as well as the ORA error and the procedure. Additional

information on the EAGLE security system is available in the EAGLE Security Manual which is

available by contacting the EAGLE Help Desk.

Figure 252. Security Violation

12.1.2 Unique Constraint Violation

In relational databases, rows of data in a table are defined by key fields. In order to establish a

new record in a table, the key fields defining the record must be unique to existing records.

Whenever a new record is inserted or an existing record is modified so that the key fields defining

the record are the same as an existing record, a unique constraint violation occurs. As shown in

Figure 253, after clicking the button an example of a unique constraint error

message. In most cases, the ‘Key Values Exist’ section of EAGLE error messages provides

enough information to interpret the error message. In this case, the ‘unique constraint

(EAGLE.PK_XB) violated’ message indicates that the key fields defining the XB table record

being inserted (or modified) already exist in table XB.


12–5

Figure 253. Unique Constraint Violation – Key Values Exist

12.1.3 Integrity Constraint – Parent Key Not Found

In relational databases, rows of data in a table are defined by key fields. Key fields ‘flow down’

from higher level tables to ‘child tables’ as ‘Foreign Keys’ which relate the data in the child table

to its ‘parent table’. Whenever a record is inserted or modified in a child table, the foreign key

fields must match the key fields of its parent table(s).

If an attempt is made to insert or modify a record in a child table so that its foreign keys do not

match the key fields of its parent tables, an Integrity Constraint Violation – Parent Key Not Found

error results. Figure 254 is an example of an Integrity Constraint Violation – Parent Key Not

Found error message. In most cases, the ‘Data is missing from a parent table’ section of EAGLE

error message provides enough information to interpret the error message. By clicking the

button, additional information for the failed transaction can be displayed.


12–6

Figure 254. Integrity Constraint Violation – Parent Key Not Found

12.1.4 Integrity Constraint – Child Record Found

In relational databases, rows of data in a table are defined by key fields. Key fields ‘flow down’

from higher level tables to ‘child tables’ as ‘Foreign Keys’ which relate the data in the child table

to its ‘parent table’. Key fields cannot be modified or records deleted in parent tables if data in

child tables is dependent on the existence of the parent keys. Whenever records are deleted or

keys modified in parent tables for which child data exists in lower level tables, an Integrity

Constraint - Child Record Found results. Figure 255is an example of an Integrity Constraint

Violation – Child Record Found error message. In most cases, the "***** Database Error

Message: *****" section of EAGLE error messages provides enough information to interpret the

error message. In this case, the ‘integrity constraint (EAGLE.HE_HA_FOREIGN) violated –

child record found’ message indicates child data in table HE exists that is dependent on the

record being modified/deleted in table HA. Also, by scrolling down the error message the SQL

for the failed transaction can be displayed.


12–7

Figure 255. Integrity Constraint - Child Record Found

12.1.5 Cross Edit Violations

The cross edits defined in each table definition in DEF STAN 00-60 place restrictions on data that

can be entered. Figure 256 is an example of a cross edit violation. In most cases, the

"***** Database Error Message: *****" section of EAGLE error messages provides enough

information to interpret the error message. In this case, the ‘Table JA not loaded. Either

XC.TRASEIXC OR XB.SECITMXB Must Be Y. – JA.a’ message indicates cross edit

paragraph ‘a’ of the JA table cross edits has been violated. (This cross edit states: ‘The

transportability area can only be used if an item has been identified by a Sectionalized Item

Transportation Indicator (SECITMXB) table XB, or by a Transportation End Item Indicator

(TRASEIXC) table XC’.) Unlike error messages discussed in paragraphs 12.1.1 - 12.1.4, the error

code help information displayed for cross edit violations are unique to the specific cross edit

violated. By scrolling down the error message after clicking the button the SQL

for the failed transaction can be displayed.


12–8

Figure 256. Cross Edit Violation Message

12.1.6 Rule Bound to a Column Violations

The data element definitions (DEDs) in DEF STAN 00-60 are enforced in EAGLE with rules on

the column to which they apply. Figure 257 is an example of the type of error message displayed

when data in violation of a DED is entered. In most cases, the "***** Database Error Message:

*****" section of EAGLE error messages provides enough information to interpret the error

message. In this case, the ‘Table XH, COMMERCIAL AND GOVERNMENT ENTITY

(CAGE) CODE (CAGECDXH): Input value ‘QWE1’ is invalid’ message indicates that DED

046 has been violated. Unlike error messages discussed in paragraphs 12.1.1 - 12.1.4, the error

code help information displayed for DEDs is unique to the specific DED violated.


12–9

By clicking the button, the SQL for the failed transaction can be displayed as

shown in Figure 257. In this example a four digit CAGE code was entered (QWE1). Per DED

046, CAGE Code is defined as a ‘5 X F’ data element, meaning CAGE Codes must always

contain five characters.

Figure 257. Rule Bound to a Column Error Message (Oracle)


12–10


ASSIGN LCNs TO

BILL OF MATERIALS

APPENDIX A

EAGLE WORKBOOK DEF STAN 00-60 APPENDIX A LCNs TO BOM

A–3

LCNs TO BOM

EAGLE provides a method for automatically generating LCNs using the Assign LCNs to BOM

Function of the LCN Maintenance Discipline. The input file is a file that is commonly referred to

as a Bill of Materials (BOM) file. It must contain the indenture code, CAGE code, reference

number, and reference number description. In addition, this file must be in top down break down

sequence with indenture codes assigned. The easiest way to use the BOM file with EAGLE is to

have it in an Excel Spreadsheet. For this exercise, a BOM Excel Spreadsheet has been created for

training and will be used in the following paragraphs.

STEP To Automatically Assign LCNs to a BOM and import the data do the following as shown

and described:

Access the Assign LCNs to BOM Function from the LCN Maintenance discipline using

the Navigator Home tab and Filter box as shown in Figure 258

Double-click the Assign LCNs to BOM Function

The Automatically Assign LCNs window is displayed

Figure 258. Navigator-Assign LCNs to BOM

Because the TRAINBOM.XLS file that we will use for this exercise contains data that already

exists in our BICYCLEXX End Item, we will select the NEWBIKEXX End Item.

Make sure to check if there is an End Item Default record established. The BOM will not load

without it.


A–4

In order to perform this exercise, the TRAINBOM.XLS file provided must be open in Excel and

all the data selected for copying. The TRAINBOM.XLS file is located in the EAGLE root

directory, and has been placed in the Training Folder provided.

Copy the BOM data (clipboard) in the spreadsheet provided to the clipboard

Make sure NEWBIKEXX is selected as End Item as shown in Figure 259

Click the button as shown

Figure 259. Automatically Assign LCNs

The EAGLE: Clipboard Format Pop Up is displayed

The data in your spreadsheet must be in the format shown in Figure 260

Click the button


A–5

Figure 260. EAGLE: Clipboard Format Pop Up

Enter ‘A’ in the Start LCN data box as shown in Figure 262

Choose the radio button for Alphanumeric under LCN Data Type. Alphanumeric allows

for the most Indenture Levels and the most items at each level

Check the Skip I’s and O’s checkbox to exclude the use of I’s and O’s in the LCN’s

Make sure the six checkboxes in the Tables to Fill area are checked as shown

Figure 261. Automatically Assign LCNs Window – Top Shown


A–6

Enter ‘1’ for LCN Gap: and ‘1232222211’ for LCN Structure: Note that the ‘1’at the

beginning of the LCN Structure corresponds to the ‘A’ in the Start LCN data field. If you

were to choose ‘AA’ as your Start LCN, the first indenture level in the LCN Structure:

data field would have to be a ‘2’. As an example, the BICYCLEXX End Item used for

our training has an LCN structure of ‘4222222’ and a corresponding Start LCN of

‘BIKE’

Choose the button

Figure 262. Automatically Assign LCNs Window – Bottom Shown

The EAGLE: Clipboard Format Pop Up is displayed

Choose the button to ‘Is the Clipboard data in this order?’

Figure 263. Clipboard Format-Paste Clipboard


A–7

The records are added as shown in Figure 264

Choose the button

Figure 264. Automatically Assign LCNs – Clipboard Data Added

The Automatically Assign HG Indenture Codes? Pop Up is displayed (Figure 265)

At this point, you may choose Yes or No to the Automatically Assign HG Indenture

Codes? Pop Up


A–8

Figure 265. Automatically Assign HG Indenture Codes?

Figure 266 is displayed

Click the button

Choose the button

Figure 266. Automatically Assign LCNs- Calculate LCNs


A–9

The Assign LCNs to BOM – Populate database Results window is displayed (Figure 267)

Figure 267. Database Error Messages Window

Close the Results window

Info: In the Tables to Fill portion of the window as shown in Figure 268, notice the additional

checkboxes. This capability is provided in the event your BOM contains additional parts

information/TM data. There is another BOM File located in the EAGLE Root directory

(trainbom-new.xls) to utilize for this exercise if you so choose.

At some point the Calculate LCNs Function may not allow for your specific needs. This next step

offers a method to change/add LCNs and populate the Database.

STEP Do the following to Assign LCNs to a BOM and import the Data:

With the Automatically Assign LCNs window open as shown in Figure 268

Click in the data window

Choose Edit >> Copy Datawindow from the Menu bar


A–10

Figure 268. Automatically Assign LCNs - Addl Parts/TM Data

Open a new sheet in Excel and Paste Clipboard

Change the LCNs. In this case use find ‘A’ and replace with ‘B’

Highlight all rows of data in the spreadsheet

Copy to clipboard

Return to the BOM window

Choose Edit >> Clear Window from the Main toolbar

Save Changes ‘Yes’

From the Main toolbar choose Edit >> Paste Spreadsheet

Choose the Populate Database button


STRUCTURED

QUERY

LANGUAGE

APPENDIX B

EAGLE WORKBOOK DEF STAN 00-60 APPENDIX B STRUCTURED QUERY LANGUAGE

B–3

STRUCTURED QUERY LANGUAGE

B.0 INTRODUCTION

This appendix contains a brief overview of the most commonly used SQL commands. It is not

intended to be a comprehensive document on SQL syntax. A good reference guide would be one

of the following.

Microsoft SQL Server

Transact-SQL User’s Guide

Document No. SY27439-0192

The Guide To SQL Server

Aloke Nath

Addison-Wesley Publishing

B.1 CONVENTIONS USED IN THIS APPENDIX

CONVENTION PURPOSE

UPPERCASE Transact-SQL statements, and any other portions of syntax

that must appear exactly as shown.

italic Represents table names and columns names.

[brackets] Enclose optional items. Type only the information within the

braces, not the braces themselves.

| (vertical bar) Separates items inside a set of braces or brackets. The vertical

bar means you can choose only one of the items.

B.2 SQL AND RELATIONAL DATABASE MANAGEMENT

SQL, originally an acronym for “Structured Query Language”, is a unified language for defining,

querying, modifying, and controlling the data in a relational database. Its name is officially

pronounced “ess-cue-ell”, but many people say “sequel”. With SQL you can query, insert, update

and delete data in a database. SQL works on database systems like SYBASE, Oracle, and

Microsoft Access.


B–4

B.2.1 Tables, Columns, and Rows

In a relational database system, users see data as tables or relations. Each row, or record, of a

table describes one occurrence of an entity - a Part Number, Serial Number combination. Each

Column describes one characteristic of the entity. Below is an example of a table:

sys_cd part_no serial_no

-------- ------------------- ------------

A3 12345678-104 100

A3 12345678-130 200

A3 12345678-130 210

A5 12345678-130 300

A5 12345680-100 100

B.2.2 Data Elements

B.2.2.1 Key Fields

Keys uniquely define a row of data in a table.

B.2.2.2 Data Types

Each column in a database has a datatype. It specifies data characteristics of the column. Below

are a few examples:

Character: Hold letters, numbers, and special characters. The two general types are fixed-

length character (char) and variable-length character (varchar).

Whole-number: Integers only, no fractions or decimals. These are often known by such

names as number, integer, int, smallint, and tinyint.

Decimal: Numbers with fractions. Exact decimal numbers are known as decimal or numeric.

Approximate decimal numbers have names like real, double, and float.

Date and Time: Record date, time, and combinations of date and time.


B–5

B.3 QUERYING DATABASES

B.3.1 SELECT Syntax

The SELECT statement specifies the columns you want to retrieve. The FROM clause specifies

the tables where the columns are located. The Where clause specifies the rows in the tables you

want to see. The ORDER BY clause specifies the sort order of the data.

The basic SELECT syntax is:

SELECT select_list

FROM table_list

WHERE search_conditions

ORDER BY column name

The following SELECT statement finds the part number and serial number of failed parts in the

defect table for parts sorted by part number and serial number:

select part_no, serial_no

from defect

where sys_cd = ‘A3’ order by part_no, serial_no

The complete syntax of the SELECT statement include the following phrases and keywords:

SELECT [ALL | DISTINCT] select_list

FROM table_name

WHERE search_conditions

GROUP BY [table_name].column_name

HAVING search_conditions

ORDER BY [table_name].column_name [ASC | DESC]

B.3.1.1 Selecting All Columns From A Table

To select all columns, use the * wildcard. The following SELECT statement selects all columns

from the defect table:

select *

from defect



B–6

B.3.1.2 Eliminating Duplicates When Selecting

The DISTINCT keyword will eliminate all duplicates for the selected columns. The following

SELECT statement selects only unique part numbers from the defect table:

select distinct part_no

from defect


B.3.1.3 Counting Rows

To count the rows in a tables use the COUNT() function. The following SELECT counts the total

number of failed parts:

select count(*)

from defect

where sys_cd = ‘A3’

B.3.2 WHERE Clause

The WHERE clause in a SELECT statement specifies the criteria for which rows to retrieve.

Search conditions in the WHERE clause include:

Comparison operators (such as =, <>, < and >)

where serial_no > 200

Ranges (BETWEEN and NOT BETWEEN)

where serial_no between 100 and 500

Lists (IN, NOT IN)

where part_no in (‘12345678-104’, ‘12345678-106’, ‘12345678-130’)

Pattern Matches (LIKE and NOT LIKE)

where part_no like ‘12345678%’ where part_no like ‘12345678____’

Combination of these conditions (AND, OR)

where serial_no > 200 and part_no like ‘12345678%’


B–7

B.3.2.1 Like and Wildcards

The LIKE keyword selects rows containing fields that match specified portions of character

strings.

SYMBOL MEANING

LIKE ‘5%’ 5 followed by any string of 0 or more characters

LIKE ‘_n’ an, in, on (and so on)

This query finds all part numbers that begin with 12345678. This SELECT statement will return

four records:

select part_no

from defect

where part_no like ‘12345678%’

Wildcards are special characters that expand and perform as a substitute for specific information

within an argument. Wildcards act as jokers do in a deck of cards.

WILDCARD MEANING

% Any string of zero or more characters

_ Any single character

Wildcards used without LIKE are interpreted as literals rather than as a pattern; they represent

only their own values. The following query attempts to find all part numbers that begin with

12345678, however, since LIKE is not used, only part numbers that equal 12345678% will be

found.

select part_no

from defect

where part_no = ‘12345678%’


B–8

Queries can also be written to search for the wildcard characters themselves. To use the wildcards

as characters in a LIKE match string rather than as wildcards, use special characters and

‘ESCAPE’ to search for the specific character.

SYMBOL MEANING

LIKE ‘5$%’ escape‘$’ 5%

LIKE ‘&_n’ escape ‘&’ _n

Example Query: select Refnumha

from HA

where Refnumha like ‘%$_%’ escape ‘$’

Example Result: 3819_500-102

T6_5544AA

B.3.2.2 Comparison Operators

Transact-SQL uses the following comparison operators:

OPERATOR MEANING

= equal to

> greater than

< less than

>= greater than or equal to

<= less than or equal to

<>,!= not equal to

!> not greater than

!< not less than

B.3.2.3 Logical Operators

The logical operators AND and OR are used to connect search conditions in WHERE clauses.

When more than one logical operator is used in a statement, NOT is evaluated first, then AND and

finally OR.

This select statement retrieves all of the 12345678 and 87654321 part numbers (five rows).

select *

from defect

where part_no like ‘12345678%’ and part_no like ‘87654321 %’ order by part_no


B–9

B.3.2.4 Unknown Values: IS NULL and IS NOT NULL

When you see NULL in a column, it means that the user or application has made no entry in that

column. A data value for the column is unknown or not available. NULL is not the same as zero

or blank. The following select statement selects all the records from the DEFECT table where the

serial_no is null.

select *

from defect

where serial_no IS NULL

order by part_no

B.3.2.5 Character Strings and Quotation Marks

Character strings and dates must be enclosed in single quotation marks when you enter or search

for them. Although double quotation marks are allowed, single quotation marks are preferred for

compliance with Industry standards. To specify literal single quotation marks (or apostrophes)

within a character entry, use two consecutive single quotation marks, as shown in the following

example:

select *

from faildesc

where fail_desc like ‘%DON’’T KNOW%‘ or fail_desc like ‘%TBD%‘


B–10

B.3.3 Joining Two or More Tables

B.3.3.1 Inner Joins

An inner join would be used when a data match from one table to another is desired. The

following query will match all of the failure narrative with the failure data.

select evaluation.part_no, evaluation.serial_no,

evaluation.basic_failure_no,

evaluation.failure_dash_no,

faildesc.line_no, faildesc.fail_desc

from evaluation, faildesc

where evaluation.basic_failure_no =

faildesc.basic_failure_no and

evaluation.failure_dash_no =

faildesc.failure_dash_no

order by evaluation.part_no, evaluation.serial_no,

evaluation.basic_failure_no,

evaluation.failure_dash_no,

faildesc.line_no

B.3.3.2 Outer Joins

In inner joins, only matching rows are include in the results. If non matching rows are desired in

the results of a join, an outer join should be used. The Oracle equivalent for an outer join uses the

(+) operators as shown below. The example queries below will retrieve all part information and

their defect code, if the part failed testing. An outer join is required in this case since not all parts

fail testing..

Oracle: select evaluation.part_no, evaluation.serial_no,

evaluation_qty, defect_cd

from evaluation, defect

where evaluation.sys_cd = defect.sys_cd(+) and

evaluation.part_no = defect.part_no(+) and

evaluation.serial_no = defect.serial_no(+)


INDEX

EAGLE WORKBOOK DEF STAN 00-60 INDEX

Index - 3

INDEX

A

A Table, 3-3

Additional Reference Number

adding, 10-9

AdHoc, 11–3

adding comments to queries, 11–19

generating reports, 11–8

key field updates and parent table deletes, 11–

33

loading external data, 11–34

New Query, 11–3

New Query Function, 11–3

query, 11–3

Query Results, 11–26

Recall Query, 11–22

Recalling Queries, 11–23

saving reports, 11–17, 11–20, 11–22

updating database, 11–26

Administrative User Ids and Passwords

Database Administrator, 1-5

Security Administrator, 1-5

Assigning LCNs, 2-6

Assigning Serial Number UOCs to System/End

Item LCNs, 2-18

C

CAGE Code

adding, 2-24, 10-5

methods of adding, 10-5

Character Strings, B–9

Columns, B–4

Comparison Operators, B–8

Conventions, 1-3

general, 1-3

keyboard, 1-4

mouse, 1-4

window, 1-4

Copying Tasks, 5-18

D

Data Elements, B–4

Data Types, B–4

DEF-STAN-00-60

End Item Default Settings, 1-7

System Default Settings, 1-6

Discipline, 1-3

AdHoc, 11–3

Facilities, 6-3

LCN Maintenance, 2-3

Operations Maintenance, 3-3, 3-7

Personnel, 7-3

Provisioning, 10-3

Reliability & Maintainability, 4-3

Support Equipment, 9–3

Task Analysis, 5-3

Transportation, 8-3

E

EAGLE

login, 1-7

End Item Acronym Code

creating, 2-3

ERROR MESSAGES, 12–3

Data Element Cross Edit Violations, 12–7

Integrity Constraint – Child Record Found,

12–6

Integrity Constraint - Parent Key Not Found,

12–5

Rule Bound to a Column Violations, 12–8

Security Violations, 12–3

Unique Constraint Violation, 12–4

F

Facilities

adding, 6-4

linking to task, 6-6

Facilities Discipline

Facilities Finder, 6-3


Index - 4

Facilities Finder, 6-3

Finder

data, 1-10

J

JOIN

inner join, B–10

outer join, B–10

Joining Tables, 11–9

K

Key Fields, B–4

L

LCN

lower level, 2-10

top level, 2-6

LCN (XB) Maintenance, 2-6

LCN Maintenance

Assign LCNs to BOM Function, A–3

LCN Structure

LCNs to BOM, A–6

LCN to System/EI (XF) Maintenance, 2-15

LCNs

Assigning, 2-6

LOGGING IN TO EAGLE, 1-7

Logical Operators, B–8

M

Mapping LCNs to System/End Item Serial

Number UOCs, 2-21

N

Navigatior

Home Tab Filter, 1-10

Navigator

Classic Navigator, 1-15

Favorites Tab, 1-13

Recent tab, 1-15

Using the, 1-10

NULL, B–9

O

O&M Requirements

Reliability, AOR, 3-7

Operations Maintenance Discipline, 3-3, 3-7

P

Part Applications

adding, 10-11

PCCN

assigning system. See Reference Number:part

usage

Personnel Skills Discipline

adding skills, 7-4

Personnel Physical and Mental Requirements,

7-5

Skill Specialty Code Finder (GA), 7-3

Prov. System/EI (HO) Maintenance, 2-30

Provisioning

Adding an HG record, 10-11

Adding Design Change Information, 10-20

Adding Item Packaging Requirement Data, 10-

18

Adding UOC Data, 10-17

Entering Provisioning Remarks, 10-17

New Part Information, 10-6

Summary Tab, 10-15

Table HA, 10-16

View/Edit Provisioning Data, 10-19

Provisioning Data

maintaining, 10-15

Q

Query

saving scripts, 11–21

selecting column(s), 11–6

selecting table(s), 11–4

selection criteria, 11–9

Sort, 11–17

Where, 11–16

R

Reference Number

adding, 2-26, 10-3

adding information, 10-8

additional. See Additional Reference Number


Index - 5

methods of adding, 10-5

part application, 2-28

part usage, 2-13

References

breaking, 5-38

Relational Database, B–3

Reliability & Maintainability Discipline, 4-3

Adding Failure Mode and RCM Analysis

Data, 4-11

Adding Failure Mode and RCM Narrative, 4-

13

Adding Failure Mode Indicator Mission Phase

Code Characteristics Data, 4-17

Adding Failure Mode Task Data, 4-13

Adding Mission Phase Operational Mode

Data, 4-16

Adding Ram Characteristics Data, 4-4

Adding RAM Characteristics Narrative, 4-6

Adding RAM Criticality Data, 4-17

Adding RAM Failure Mode Indicator Mission

Phase CodeCharacteristics Narrative, 4-18

Adding RAM Indicator Code Data, 4-8

Adding RAM Logistics Considerations

Narrative Data, 4-7

Adding War/Peace RAM Indicator

Characteristics Data, 4-10

RAM Finder, 4-3

Reports/Process Menu, 1-19–1-20

using, 1-20

Rows, B–4

S

SELECT, B–5

SERD Finder, 9–3

SERD Numbers

assigning, 9–6

SERD Report

running, 9–10

Skills

adding, 7-4

Personnel Physical and Mental Requirements,

7-5

Sorting Task Codes, 5-27

Specifying Facilities Requirements in Task

Analysis, 5-10

SQL, 11–3, B–3

Subtask

adding as original, 5-29

adding as reference, 5-31

adding narrative, 5-39

assign personnel, 5-52

assign workload, 5-53

reference, 5-28

view reference, 5-33

Subtask References

Changing, 5-34

Support Equipment

adding, 9–5

adding SE data, 9–8

adding SE narrative, 9–8

administrative data, 9–9

SERD name, 9–9

T

Tables, B–4

Task

adding as original, 5-5

adding as reference, 5-13

adding narrative. See Subtask : adding

narrative

adding to LCN, 5-5

AOR, 5-9

assigning provisioning items, 5-49

assigning support equipment, 5-45

copying. See Copying Tasks

original, 5-5

reference, 5-5

tech manual narrative, 5-56

view reference, 5-16

Task Analysis Discipline, 5-3

Task Analysis Finder, 5-3

Tasks

crreating, 5-3

Technical Manual Code

establishing, 2-33

Technical Support, 5

Toolbar

Function Specific, 1-20

Graphical Functions, 1-19

Help, 1-18

Item Help, 1-18

main, 1-18

Selecting an End Item (Oracle only), 1-20

Transportation Discipline

adding data, 8-4

Adding Shipping Mode Data, 8-6

Adding Transport by Fiscal Year Data, 8-9

Adding Transportation Narrative, 8-10


Index - 6

Adding Transported End Item Data, 8-7

Adding Transported End Item Narrative, 8-8

Transportation Finder, 8-3

Transportation Finder, 8-3

U

Unit Under Test

Data Tabs, 9–14

Unit Under Test Data

tab/table relationships, 9–16

UOC

assigning part. See Prov. System/EI (HO)

Maintenance

assigning system. See Reference Number:part

usage

W

WHERE, B–6

Wildcards, B–7


STUDENT

NOTES

STUDENT NOTES

SN - 3

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

STUDENT NOTES

SN - 4

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

Technical support is provided by the EAGLE Team of Raytheon Company. Phone support is

available Monday through Friday from 8:00 a.m. to 4:30 p.m. Mountain Standard Time. EAGLE

technical support personnel can be reached at (520) 663-6673. Training on the EAGLE product is

available.

Are you ready for EAGLE? Join Team EAGLE and find out what it’s like to soar. Give your

logistics software product the EAGLE advantage. For more information on becoming part of

Team EAGLE, contact:

Raytheon Company

Team EAGLE

(520) 663-6673

email [email protected]

Enhanced

Automated

Graphical

Logistics

Environment

mailto:[email protected]

Documents

Enhanced Automated Graphical Logistics Environment 0060 Workbook.pdf · 11.1.1.4 Establishing Query Selection Criteria .....11–9 11.1.1.5 Multiple Tables in ADHOC Queries – Joining