raytheon INSTRUCTION complex 2122_RevB.pptx

qaaaaaaaaaaaaaaa

1. CSS EAGLE UPLOAD MANUAL FRONT-END Basic Engineering Work Instruction Owner: ILS department Manager

2. Table of contents: 1. PURPOSE, SCOPE AND APPLICABILITY – slide 3 2. EAGLE INTERFACE – FIRST CONTACT – slide 4-5 3. EAGLE TABLES RELATIONS – slide 6 4. LCN ENTRIES CREATION – slide 7-11 5. CAGE CODES – HOW TO ADD? – slide 12 6. ADDING CAGE CODES AND PROVISIONING ITEMS IN HG TABLE – slide 13 7. MAINTAINING OTHER PROVISIONING DATA ELEMENTS – slide 14 8. REFERENCE NUMBER INFORMATION – HOW TO ADD? – slide 15 9. TECHNICAL MANUAL CODE – HOW TO ADD? – slide 16-17 10. ADDING TASKS – slide 18-21 11. ADDING SUBTASKS TO TASKS – slide 22 12. ADDING REFERENCE SUBTASKS – slide 23 13. CLONING TASKS – slide 24-25 14. ADDING NARRATIVES TO SUBTASKS – slide 26 15. ADDING PERSONNEL DATA - slide 27 16. ADDING SUPPORT EQUIPMENT – SLIDE 28-31 17. ADDING SUPPORT EQUIPMENT DATA – SLIDE 32-33 18. ADDING SUPPORTING DATA TO TASKS – slide 34-35 19. ADDING SUPPORT DATA TO SUBTASKS – slide 36-37 20. INTERPRETING ERROR MESSAGES – SLIDE 38-4 3 2

3. back PURPOSE This CSS EAGLE Front-End upload procedure describes the general usage and features of the EAGLE(Enhanced Automated Graphical Logistics Environment) software. The instruction presents the process of filling with data the EAGLE software database. SCOPE AND APPLICABILITY The instruction is used to load the Maintenance plan information to a Logistic Support Analyses Records (LSAR), in this case, the EAGLE software database. The instruction can be used in all new projects where this approach of adding data into EAGLE software will be used. 1. PURPOSE, SCOPE AND APPLICABILITY

4. End item selection 2. EAGLE INTERFACE – FIRST CONTACT– 1/2 EAGLE LOG IN Always be sure you are in the correct “End item”!!! 4 back

5. 2. EAGLE INTERFACE – FIRST CONTACT– 2/2 Navigator Main Toolbar Finder Search action can be done scrolling down the info; Search can be done for a certain item using parts of the info and symbol ”%” can be found any info contained in Eagle and related to the section where the search is made; E.g. “HAN%” returns all the records starting with “HAN”; 5 back

6. 3. EAGLE TABLES RELATIONS Eagle Tables configuration Eagle tables are related one to another in a complex network; Is very important to understand the logic of this network when creating items or maintenance tasks with resources attached; 6 back

7. 4. LCN ENTRIES CREATION – 1/5 LCN is a code that represents the hardware breakdown of the system; LCNs can be 18 characters long, can be alpha, numeric or both; The structure is set in LCN Maintenance > End Item Data Maintenance: 42222 means 4 characters for the first level, then 2 for each subsequent level: (BIKE)(01)(AB)(01)… LCN(Logistic Control Number) entries can be added in “Breakdown structure” or using Navigator function “LCN Maintenance”; 7 back

8. 4. LCN ENTRIES CREATION – 2/5 LCN entries can be added also from LCN MAINTENANCE function, “Part App. (HG) Maintenance” table using special button for this action; E.g. filling the below data and clicking the “Backfill XB/XH/HA” button the new LCN entry with the name “BIKE09XZ” will be added to LCN tree(and in XB table); also the cage code “ABCDE” will be added to XH table and the provisioned item with reference number “88888” will be added in HA table; pressing “SAVE” button the new info will be saved in Eagle database; “Backfill” button “Part App. (HG) Maintenance” function 8 back

9. 4. LCN ENTRIES CREATION – 3/5 LCN entries can be added/modified directly in Breakdown structure, using insert, drag and drop or copy/paste functions; 9 back Steps: Expand Breakdown Structure function from the Navigator; Click on desired LCN entry where a new entry will be added; Click “Insert” button from horizontal menu of the Main Menu Toolbar; “Additional Breakdown Item Information” window will be displayed; Choose indenture level: Same indenture, Parent of Child of Target and click OK; New Breakdown Item LCN Assignment window will be displayed; click OK; A new “Additional Breakdown Item Information” window will be displayed; Fill the Breakdown Item field with the name of the new entry and LCN field with the LCN number; click OK; Breakdown Item warning window is displayed; click YES; New Breakdown Item Created window is displayed; click OK; The Breakdown structure will be displayed, with the new entry added; a. Adding LCN entries using INSERT function from the main menu bar

10. Steps: Expand Breakdown Structure function from the Navigator; Click on desired LCN entry that need to be copied; Click “COPY” button from horizontal menu of the Main Menu Toolbar; Click on the desired LCN entry from Breakdown Structure where the selected LCN entry will be copied; Click “PASTE” button from horizontal menu of the Main Menu Toolbar; “Additional Breakdown Item Information” window will be displayed; Choose indenture level: Same indenture, Parent of Child of Target and click OK; “New Breakdown Item LCN Assignment” window will be displayed; click OK; A new “Additional Breakdown Item Information” window will be displayed; Fill the LCN field with the LCN number; click OK; Breakdown Item warning window is displayed; click YES; New Breakdown Item Created window is displayed; click OK; The Breakdown structure will be displayed, with the new entry added; 4. LCN ENTRIES CREATION – 4/5 10 back b. Adding LCN entries using COPY/PASTE functions from the main menu bar

11. 4. LCN ENTRIES CREATION – 5/5 11 back Steps: Expand Breakdown Structure function from the Navigator; Click on desired LCN entry that will be moved using drag and drop function; Keep the Click button pressed and drag the item to the desired LCN entry where will be placed; release the click button when the item is on the desired position “Additional Breakdown Item Information” window will be displayed; Choose indenture level: Same indenture, Parent of Child of Target and click OK; New Breakdown Item LCN Assignment window will be displayed; click OK; A new “Additional Breakdown Item Information” window will be displayed; Fill the Breakdown Item field with the name of the new entry and LCN field with the LCN number; click OK; Breakdown Item warning window is displayed; click YES; New Breakdown Item Created window is displayed; click OK; The Breakdown structure will be displayed, with the new entry added; c. Adding/modifying LCN entries using drag and drop function

12. 5. CAGE CODES – HOW TO ADD? CAGE codes identify suppliers and customers and they are stored in XH table; CAGE Codes can be added through the LCN Maintenance Discipline or the Provisioning Discipline . The best method to add multiple CAGE codes into the database is using the LCN Maintenance Discipline and is presented below. 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. This method will be presented in the chapter that describe how to add Reference Number Information; Adding Cage codes using the LCN Maintenance Discipline Steps: Expand LCN Maintenance function from the Navigator; Double click on CAGE Code (XH) Maintenance; Click “Insert” button from horizontal menu; Fill the required fields with info provided by suppliers; Click “Save” button from the horizontal menu; 12 back

13. 6. ADDING CAGE CODES AND PROVISIONING ITEMS IN HG TABLE In HG table can be added provisioning items and cage codes and they will be added automatically in tables XB, XH and HA; also in HG table the new added provisioning items are assigned to designated LCNs(field “ LSA Control Number(LCN) ”) through this table; In HG table is also possible to chose the ITEM CATEGORY CODE (ICC) of the provisioning item; Steps: Expand LCN Maintenance function from the Navigator; Double click on “Part (HG) Maintenance”; Click “Insert” button from horizontal menu; Fill the required fields with info provided by suppliers; ICC code can be selected in the specific window; if the item is a Repair Kit, can be selected “Repair parts kit” or other desired category; Tick the Backfill XB/XH/HA option; Click “Save” button from the horizontal menu; The info will be automatic inserted in tables XB, XH and HA; 13 back

14. 7. MAINTAINING OTHER PROVISIONING DATA ELEMENTS maintaining other provisioning data elements can be done using the view/edit provisioning data window; The View/Edit Provisioning Data Window allows provisioning data to be entered or updated by individual table. Steps: Expand Provisioning function from the Navigator; Double click on “Provisioning Finder”; Click “Execute” button from horizontal menu; Select the desired item from the displayed list; Press the button from the left, vertical main menu; View /Edit Provisioning Data window is displayed; Provisioning data(remarks and other data) can be edited in tabs from HA to HR; After adding the desired data, choose the Save button on the Main toolbar; 14 back

15. 8. REFERENCE NUMBER INFORMATION – HOW TO ADD? Provisioning Parts data are stored in H tables; Reference numbers can be added through the LCN Maintenance Discipline or the Provisioning Discipline. Adding Reference Number data using the LCN Maintenance Discipline Steps: Expand LCN Maintenance function from the Navigator; Double click on “Part (HA) Maintenance”; Click “Insert” button from horizontal menu; Fill the required fields with info provided by suppliers; Click “Save” button from the horizontal menu; 15 back

16. 9. TECHNICAL MANUAL CODE – HOW TO ADD? - 1/2 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. a. Creating Technical Manual Code 16 back The Technical Manual (TM) Code is created on system level in the specific file Excel document (TDOP); E.g from ASRV project the file: G8501.505_TDOP_ASRV_ILS_RevA.xlsx column Q. The TM CODE can be found in the special created LSA folder “TECHNICAL MANUALS” in the Note file Technical Manual Code.txt. Note: If no system level Technical Manual Code is available enter TBD (To Be Determined)..

17. 9. TECHNICAL MANUAL CODE – HOW TO ADD? - 2/2 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. b. Adding Technical Manual Code Steps: Expand “Tech Manual” function from the Navigator; Double click on “Maintain Tech Manual Code” option; Click “Insert” button from horizontal menu; Fill the requested fields with requested info; Click “Save” button from the horizontal menu; 17 back

18. 10. ADDING TASKS – 1/4 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. Create maintenance tasks for LCNs: Steps: Expand “Task Analysis” function from the Navigator; Double click the “Task Analysis Finder” function ; Click “Execute” button from horizontal menu; a list of LCNs will appear; this list can be filtered after some options available in Task Analysis finder(LCNs with or without tasks, etc ); 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; 1. Access task Analysis discipline : 18 back

19. 10. ADDING TASKS – 2/4 New tasks may be added to existing LCNs in the Task Analysis Discipline. If an LCN does not already exist, first the LCN should be added using the LCN Maintenance Discipline from the Navigator. Steps: Select one of the LCNs from Task Analysis Finder; Click the button on the Function Specific toolbar; The Task Information window is displayed; 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; after the action verb an item name must be entered: e.g. “INSPECT(action verb) BYCICLE(item name)” Click the button to insert ‘INSPECT’ in the Task Identification box; Click the button. Select the needed values from the dropdown list, for the first 5 steps indicated in the “Create/Modify Task Code” window; Click the button to assign sequence code for the sixth and seventh position of task code. Now the button is enabled indicating a complete task code. The task code is displayed now: e.g. “AGCOCAA“. Chose “OK” button to return to Task Information window. Task frequency field must be filled. E.g. frequency “12” means the task is executed 12 times per year; frequency “0.2” means the task is executed every 5 years, etc ; Choose the button to complete addition of the new task. 2. Adding a new Task – adding original tasks : 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. 19 back

20. 10. ADDING TASKS – 3/4 If the 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 . 3. Adding “Annual Operating Requirements” Steps: Press “Done” button after creating the Task Code; the “Annual Operating Requirement Finder” is open; Select the desired annual operating requirements(hours, kilometers etc ) by highlighting the row with desired LCN; Choose the “OK” button to return to Task Information Window; After the new task has been added and 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. 20 back

21. 10. ADDING TASKS – 4/4 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. 4. Adding Reference Number data using the Provisioning Discipline Steps: Select the New Task tab in the Task Information window; 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; The Reference Task Finder window is displayed; Make sure the BICYCLEXX end item assigned by the EAGLE instructor is selected; Make sure ‘A’ is in the LCN query box; Enter ‘RE%’ into the Task Identification finder box; Choose the “Query” button from the “Reference Task Finder” window to extract a list of available LCNs and Task Codes for referencing; Choose the task to reference and after that choose the “OK” button to return to “Task Information” window; The task name 'REPAIR FLAT' now is 'REPAIR FLAT TIRE‘; choose “Done” button; Notice 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!!’ 21 back

22. 11. 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. subtasks can’t be added directly to an LCN; a task must be created first, an then the subtasks will be added to the task; Adding Subtasks Steps: Open Task Analysis Finder; Click “Execute” button from horizontal menu; a list of LCNs will appear; Select the record with desired LCN from the Task Analysis Finder; Choose the button on the Function Specific toolbar; The Subtask Information window is displayed; New Subtask Tab is active by default; Enter ‘PREPARE BICYCLE FOR INSPECTION’ in the Subtask Identification box(or other name for subtask); Make sure the Subtask Numbering radio button has ‘Enter as LAST Subtask’ selected; Choose the button; To add other subtasks the operations above will be repeated; 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. 22 back

23. 12. 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. Adding Reference Subtasks Steps: “Subtask Information” window is displayed; Select the “New Subtask” tab Choose the button from the “Subtask Information” window. The “Reference Subtask Finder” is displayed; Choose the button at the bottom of the Reference Subtask Finder; Select the subtask to reference by highlighting it; then choose the button; 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: “This subtask references another subtask!!” 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. 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. 23 back

24. 13. CLONING TASKS - 1/2 CLONING TASK information is very useful when creating like or similar tasks. The cloning saves time and it keeps data consistent. There are two ways to perform cloning of task data from one LCN to another LCN (existing LCN or new 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 (an existing one or a new created one). 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, or when a task must be moved from a System (BSMI, SWBS etc ) to another. REFERENCING 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. 24 back Steps: Open Task Analysis Finder; Check the “Only LCNs With tasks” checkbox under ‘Display’ Click “Execute” button from the main horizontal menu; a list of LCNs will appear; Select the record with desired LCN from the Task Analysis Finder; this LCN should contain the tasks that must be cloned; Choose the button on the Function Specific toolbar (left menu); The Clone task window will display all available tasks (Records:6), that can be cloned, for the selected LCN. For every task an option (the type of cloning) can be selected from the ‘Task cloning Options’; The default option is ‘Copy Task’ which creates a new task that copies the original. For every task from one LCN can be chosen one of the 3 options: Reference task, Do not clone, Copy task (this helps if not all the tasks are needed to be copied or referenced). See next slide

25. 13. CLONING TASKS – 2/2 CLONING TASK information is very useful when creating like or similar tasks. The cloning saves time and it keeps data consistent. There are two ways to perform cloning of task data from one LCN to another LCN (existing LCN or new LCN): 25 back Steps: Choose the button. 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. Use button to display all available LCN’s. Select the desired one where the chosen task to be cloned (copied or referenced) must be placed. Press button. The LCN number where the cloned task will be placed will be displayed in the ‘Cloning Destination’ section. Click button. After the action is processed, the ‘Clone tasks’ window can be closed. In ‘Task Analysis Finder’ window press “Execute” button from the main horizontal menu. The LCN’s with tasks will be displayed, including the new LCN containing the task that was cloned. To view the tasks that were cloned, press button from the left vertical menu.

26. 14. ADDING NARRATIVES TO SUBTASKS Narrative Data for Subtasks can be added using the Task Analysis Discipline from the Navigator. Adding Narrative Data to Subtasks Steps: Open Task Analysis Finder and select the desired LCN entry; Click the button on the Function Specific toolbar; The Narrative editor is displayed; Make sure that the desired task code and the desired subtask is selected; Check the Allow Editing checkbox to enable editing in the Narrative Editor box Enter the desired narrative text (manually or using Copy/Paste functions from PDF, Word, Excel etc ); Next, click on the first line of text entered, then check the Element Code box; Choose the Save button on the Main toolbar; now the Allow Editing checkbox is disabled and the Element Code box disappears; After that another subtask can be edited following the same steps; Preparation for editing: Select Tools>>Options from the Menu bar(see below figure); The Options window is displayed; Select the Publishing and Reports tab Make sure ‘NONE’ is selected from the Editor: drop down list; Choose the button. 26 back

27. 15. ADDING PERSONNEL DATA The Personnel Skill Considerations tables (G tables) describe and justify any new or modified personnel skills required to support the system/equipment. Adding Personnel Data Steps: Make sure the desired end item is selected; Double-click the Skill Specialty Code Finder (GA) function; the “Personnel Skills Finder” is now displayed; Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve all Skill Specialty Codes; Choose the Insert button on the Main toolbar; Enter ‘23A’ into the Skill Specialty Code box; 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; Choose the Save button on the Main toolbar; Close the Personnel Skills Finder (GA) window; 27 back

28. 16. ADDING SUPPORT EQUIPMENT – 1/4 In order to add support equipment to the Support Equipment tables, reference number data for the support equipment item must exist in table HA. Usage of SERD Finder Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder ; Double-click the SERD Finder function. The SERD Finder is displayed Choose the Execute button on the Main toolbar or ALT+Q,E to retrieve all support equipment records. The button on the Function Specific toolbar is used to add or delete a reference number from the Support Equipment (EA) Table. 6. 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. 28 back

29. 16. ADDING SUPPORT EQUIPMENT – 2/4 In order to add data into the Support Equipment Tables, specifically Support Equipment or EA Table, do the following steps: Adding Support Equipment Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder; Choose the button on the Function Specific toolbar. The support equipment window is displayed; Enter ‘SE%’ into the CAGE Code query box; Choose the Execute button on the Main toolbar; All Reference Numbers that have CAGE Code ‘SE999’ are returned on the left; Select the desired record (e.g. with CAGE Code ‘SE999’) and the desired Reference Number (e.g. ‘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; Choose the Save button on the Main toolbar; 29 back

30. 16. ADDING SUPPORT EQUIPMENT – 3/4 In order to assign a SERD number, do the following steps: Assigning SERD Numbers Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder; Enter ‘TH%’ into the Reference Number finder field ; Choose the Execute button from the Main toolbar; Select the desired record (e.g. with the SE CAGE ‘SE999’ and Reference Number ‘TH-1001’); Choose the button on the Function Specific toolbar.; Click the button to No Records Found’ message box; The Support Equipment Recommendation Data window is displayed; Enter ‘0000001234’ into the SERD Number box ; 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; Choose the Save button on the Main toolbar; Close the SERD Recommendation Data window; 30 back

31. 16. ADDING SUPPORT EQUIPMENT – 4/4 In order to add data into the Support Equipment Tables, specifically Support Equipment or EA Table, do the following steps: Adding Support Equipment Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder; Choose the button on the Function Specific toolbar. The support equipment window is displayed; Enter ‘SE%’ into the CAGE Code query box; Choose the Execute button on the Main toolbar; All Reference Numbers that have CAGE Code ‘SE999’ are returned on the left; Select the desired record (e.g. with CAGE Code ‘SE999’) and the desired Reference Number (e.g. ‘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; Choose the Save button on the Main toolbar; 31 back

32. 17. ADDING SUPPORT EQUIPMENT DATA – 1/2 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. Adding Support Equipment Narrative Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder; Select the record with the SE Reference Number of ‘TH-1001’ Choose the button from the Function Specific toolbar The Support Equipment Data window is displayed Choose the Narrative tab Select ‘B. Description + function of SE’ from the Select Type of Narrative drop down list Enter the desired text in the Narrative box Choose the Save button on the Main toolbar 32 back

33. Steps: Make sure that the desired End Item is selected; Access the Support Equipment Discipline from the Navigator utilizing the Home tab and Filter box and select the SERD Finder; Select the record with the SE Reference Number of ‘TH-1001’ Choose the button from the Function Specific toolbar The Support Equipment Data window is displayed Choose the Admin. Data tab on the Support Equipment Data window 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 Choose the Save button on the Main toolbar Close the Support Equipment Data window 17. ADDING SUPPORT EQUIPMENT DATA – 2/2 In order to add a SERD name to a piece of support, do the following steps Adding a SERD Name and Administrative Data 33 back

34. 18. ADDING SUPPORTING DATA TO TASKS – 1/2 In order to assign support equipment to a task, the support equipment (EA record) must already exist. 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. Assigning Support Equipment Steps: Open Task Analysis Finder and select the desired LCN entry with its task; Click the button from the Function Specific toolbar; Select the Support Equipment tab Any support equipment assigned to the task will be displayed. If no records is assigned ‘Records: 0’ is shown; Click the button. 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 to search the database for all EA records that exist against your end item; Select the desired Support Equipment and click button; The Task Information window is re-displayed. Enter ‘1’(or other value) into the Qty box. Select ‘Each’(or other value) from the Unit of Measure drop down list box; Choose the “Save” button; 34 back

35. 18. ADDING SUPPORTING DATA TO TASKS – 2/2 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 “Chapter 4 – LCN ENTRIES CREATION” 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. Assigning Provisioning Items Steps: Open Task Analysis Finder and select the desired LCN entry with its task; Click the button from the Function Specific toolbar; Select the Provisioned Items tab; Any provisioned items assigned to the task will be displayed. If no records is assigned ‘Records: 0’ is shown; Click the button. The “Task Provisioned Items” window appears allowing the user to query the database for selection of desired provisioned items to add to the task. Choose the button to search the database for all EA records that exist against your end item; Select the desired Provisioned Items and click button; The Task Information window is re-displayed. Enter ‘1’(or other value) into the Qty box. Select ‘Each’(or other value) from the Unit of Measure drop down list box; Choose the “Save” button; 35 back

36. 19. ADDING SUPPORT DATA TO SUBTASKS – 1/2 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. 1. Assigning Personnel Steps: Open Task Analysis Finder and select the desired LCN entry with its task; Click the button from the Function Specific toolbar and then select the desired subtask; Select the Personnel tab; Enter ‘A’ into the Person Identifier box Select a value (e.g. ‘14B’) from the Available SSCs box in the left hand corner of the window by double-clicking on it; Enter a value( e.g. ‘5.0’) in the Subtask Mean Man-Minutes box; Select ‘SSC is adequate’ from Skill Specialty Evaluation Code box; Choose the Save button on the Main toolbar; 36 back

37. Steps: Open Task Analysis Finder and select the desired LCN entry with its task; Click the button from the Function Specific toolbar and then select the desired subtask; Select the Workload tab; 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 Choose the Job/Duty Codes tab Scroll down the Job/Duty Codes list if necessary and choose the desired record (e.g. Job Code ‘A1’ and Duty Code ‘1’); Choose the button to assign the 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) Choose the button to assign the Job/Duty codes Choose the Save button on the Main toolbar 37 19. ADDING SUPPORT DATA TO SUBTASKS – 2/2 It is assumed that 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; 2. Assigning Workloads back

38. 20. INTERPRETING ERROR MESSAGES – 1/6 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: 1.Security Violations Example: 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. ; 38 back Security violations in EAGLE result when a user attempts to access, add, modify or delete data without having the appropriate permissions.

39. 20. INTERPRETING ERROR MESSAGES – 2/6 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. Example: By clicking the the unique constraint error message will be displayed; 39 back 2.Unique Constraint Violation

40. 20. INTERPRETING ERROR MESSAGES – 3/6 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. In most cases, the ‘Data is missing from a parent table’ section of EAGLE error message provides enough information to interpret the error message. Example: By clicking the button, additional information for the failed transaction can be displayed. 40 back 3. Integrity Constraint – Parent Key Not Found

41. 20. INTERPRETING ERROR MESSAGES – 4/6 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. In most cases, the "***** Database Error Message: *****" section of EAGLE error messages provides enough information to interpret the error message. Example: 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. 41 back 4. Integrity Constraint – Child Record Found

42. 20. INTERPRETING ERROR MESSAGES – 5/6 The cross edits defined in each table definition in DEF STAN 00-60 place restrictions on data that can be entered. In most cases, the "***** Database Error Message: *****" section of EAGLE error messages provides enough information to interpret the error message. Example: 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’.) Also, by scrolling down the error message the SQL for the failed transaction can be displayed. 42 back 5. Cross Edit Violations

43. 20. INTERPRETING ERROR MESSAGES – 6/6 The data element definitions (DEDs) in DEF STAN 00-60 are enforced in EAGLE with rules on the column to which they apply. In most cases, the "***** Database Error Message: *****" section of EAGLE error messages provides enough information to interpret the error message. Example: 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. Also, by scrolling down the error message the SQL for the failed transaction can be displayed. 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. 43 back 6. Rule Bound to a Column Violations