logistics - raytheon eagle workbook v13.pdfprinted november 2004 first edition, revised printed may...

MAINTENANCE MANAGEMENT INFORMATION SYSTEM

MMIS WORKBOOK

VERSION 13

30 January 2015

A Product of Raytheon Company 2014 Raytheon Company

ALL RIGHTS RESERVED U.S. Patents 5,457,792; 5,493,679; 5,737,532,4,847,795

Made in the U.S.A.

Enhanced

Automated

Graphical

Logistics

Environment

COPYRIGHT 2015 RAYTHEON COMPANY

UNPUBLISHED WORK - ALL RIGHTS RESERVED.

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.

Excerpts from Logistics Product Data (ANSI/GEIA-STD-0007), Copyright ©

(2007), Government Electronics and Information Technology Association. All

Rights Reserved. Reprinted by Permission.

Revision History

Printed May 2002 First Edition

Printed December 2003 First Edition, Revised

Printed November 2004 First Edition, Revised

Printed May 2010 Second Edition

Printed September 2011 Third Edition

Printed July 2012 Third Edition, Revised

Printed October 2012 Third Edition, Reissued

Printed January 2013 Fourth Edition

Printed January 2014 Fourth Edition, Revised

Printed January 2015

.

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 MMIS Workbook Version 13

TABLE

OF

CONTENTS

MMIS WORKBOOK TABLE OF CONTENTS

v

TABLE OF CONTENTS

SECTION 1 INTRODUCTION ................................................................................... 1-4

1.0 INTRODUCTION .................................................................................................. 1-4 1.1 LSA/LSAR ............................................................................................................. 1-4 1.2 EAGLE ................................................................................................................... 1-4 1.3 RELATIONAL DATABASE ................................................................................. 1-5

1.3.1 Relationships Between Tables ......................................................................... 1-5 1.3.2 End Items ......................................................................................................... 1-6 1.3.3 Eagle Database Structure and LSAR ............................................................... 1-6

1.4 MMIS ..................................................................................................................... 1-8

1.4.1 MMIS Home Page ........................................................................................... 1-8

1.5 CONVENTIONS USED IN DOCUMENTATION ............................................................ 1-9

1.5.1 General Conventions ..................................................................................... 1-10 1.5.2 Mouse Conventions ....................................................................................... 1-11 1.5.3 Window Conventions .................................................................................... 1-12 1.5.4 Use of Icons in MMIS ................................................................................... 1-13

SECTION 2 MMIS MAIN MENU AND NAVIGATION ......................................... 2-3

2.0 INTRODUCTION .................................................................................................. 2-3 2.1 MAIN MENU ......................................................................................................... 2-3 2.2 CHANGING PASSWORD .................................................................................... 2-5 2.3 RETRIEVING RECORDS ..................................................................................... 2-6

SECTION 3 PROJECT SETUP ................................................................................. 3–3

3.0 INTRODUCTION ................................................................................................. 3–3 3.1 ADDING A PROGRAM CODE ........................................................................... 3–3 3.2 VIEWING AND EDITING A PROGRAM CODE ............................................... 3–6 3.3 ADDING CUSTOMER INFORMATION .......................................................... 3–10 3.4 ADDING COST ACCOUNT INFORMATION ................................................. 3–10


vi

SECTION 4 DOCUMENT SYSTEM ......................................................................... 4-3

4.0 INTRODUCTION .................................................................................................. 4-3 4.1 UPLOADING AND VIEWING A DOCUMENT .................................................. 4-3

SECTION 5 ECP SYSTEM ......................................................................................... 5-3

5.0 INTRODUCTION .................................................................................................. 5-3 5.1 ADDING A NEW ECP........................................................................................... 5-4 5.2 ATTACHING A DOCUMENT TO AN ECP ......................................................... 5-7

SECTION 6 CONTRACT SYSTEM .......................................................................... 6-3

6.0 INTRODUCTION .................................................................................................. 6-3 6.1 ADDING A NEW CONTRACT NUMBER .......................................................... 6-3 6.2 ADDING CONTRACT LINE ITEM ..................................................................... 6-5

SECTION 7 ASBUILT CONFIGURATION ............................................................. 7-3

7.0 INTRODUCTION .................................................................................................. 7-3 7.1 CREATING AN ASBUILT MASTER TEMPLATE ............................................. 7-4 7.2 ASBUILT MASTER REPORTS .......................................................................... 7-13

7.2.1 Approved Build State Breakdown Report ..................................................... 7-14 7.2.2 AsBuilt Master Config Report ....................................................................... 7-16 7.2.3 AsBuilt Master History Report ...................................................................... 7-17 7.2.4 The AsBuilt Master Config vs HG Report .................................................... 7-19

7.3 CREATING AN ASBUILT CONFIGURATION ................................................ 7-20 7.4 RELEASING AN ASBUILT CONFIGURATION .............................................. 7-31

SECTION 8 ASMAINTAINED CONFIGURATION ............................................... 8-3

8.0 INTRODUCTION .................................................................................................. 8-3 8.1 REMOVING AN ASSEMBLY .............................................................................. 8-3 8.2 ASMAINTAINED CONFIGURATION REPORTS .............................................. 8-8 8.3 IMPORTING AN ASSEMBLY ............................................................................. 8-9


vii

SECTION 9 INVENTORY MANAGEMENT ........................................................... 9-3

9.0 INTRODUCTION .................................................................................................. 9-3 9.1 CREATING SITE DATA ....................................................................................... 9-3 9.2 CREATING LOCATION DATA ........................................................................... 9-7

9.2.1 Viewing Location Data .................................................................................... 9-9

9.3 CHANGING THE LOCATION OF A SERIALIZED PART................................. 9-9

9.3.1 Viewing Serialized Part Location History ..................................................... 9-12

9.4 ATTACHING AN ENGINEERING CHANGE PROPOSAL (ECP) TO A SERIALIZED PART9-14

SECTION 10 FRACAS SYSTEM ............................................................................. 10-3

10.0 INTRODUCTION .............................................................................................. 10-3 10.1 ADDING A FRACAS SYSTEM RECORD ....................................................... 10-3 10.2 CREATING A FRACAS DEFECT REPORT .................................................... 10-4 10.3 ADDING DEFECTIVE PART INFORMATION .............................................. 10-7 10.4 EDITING CORRECTIVE ACTION INFORMATION ................................... 10-11 10.5 FIELD FRACAS .............................................................................................. 10-13

10.5.1 Using the Field FRACAS Return (FFR) Wizard ....................................... 10-13 10.5.2 Finding and Editing an Existing Record in the Field FRACAS ................ 10-20 10.5.3 Creating a New Record in the Field FRACAS .......................................... 10-24 10.5.4 Deleting a Record from the Field FRACAS .............................................. 10-25

SECTION 11 TRAVELER SYSTEM ....................................................................... 11-3

11.0 INTRODUCTION .............................................................................................. 11-3 11.1 CREATING AN OPERATION .......................................................................... 11-3 11.2 CREATING A ROUTE ...................................................................................... 11-7

11.2.1 Cloning a Route ......................................................................................... 11-13

11.3 CREATING A TRAVELER ............................................................................ 11-15


viii

11.4 ADDING A ROUTE TO A TRAVELER ......................................................... 11-21 11.5 CLOSING OPERATIONS ON A TRAVELER ............................................... 11-25 11.6 CREATING A CHILD TRAVELER ............................................................... 11-27

SECTION 12 ACTION LOG SYSTEM ................................................................... 12-3

12.0 INTRODUCTION .............................................................................................. 12-3 12.1 ACTION LOG MAINTENANCE ...................................................................... 12-3

12.1.1 Creating a new Action ................................................................................. 12-4 12.1.2 Adding an Additional Action....................................................................... 12-7 12.1.3 Alternative Ways to Enter Actions .............................................................. 12-8 12.1.4 Part Look Up ............................................................................................. 12-10 12.1.5 Clone A Record ......................................................................................... 12-11

SECTION 13 PURCHASE ORDERS ...................................................................... 13–3

13.0 INTRODUCTION ............................................................................................. 13–3 13.1 CREATE VENDORS ........................................................................................ 13–3 13.2 CREATE PURCHASE ORDER........................................................................ 13–5 13.3 RECEIVING PARTS ........................................................................................ 13–7 13.4 DOCUMENTS .................................................................................................. 13–8

SECTION 14 PART UPGRADE ............................................................................... 14-3

14.0 INTRODUCTION .............................................................................................. 14-3 14.1 UPDATING A SERIALIZED PART ................................................................. 14-3 14.2 UPGRADING A SERIALIZED PART .............................................................. 14-9

SECTION 15 MMIS ADHOC .................................................................................. 15–3

15.0 INTRODUCTION ............................................................................................. 15–3 15.1 DATABASE TABLES ...................................................................................... 15–3 15.2 QUERIES .......................................................................................................... 15–4

15.2.1 Query Examples ......................................................................................... 15–6 15.2.2 MMIS Adhoc Screen Description ............................................................ 15–10 15.2.3 MMIS Adhoc Query Exercise .................................................................. 15–13


ix

SECTION 16 MMIS DASHBOARD ......................................................................... 16-3

16.0 INTRODUCTION .............................................................................................. 16-3 16.1 CREATING A MMIS DASHBOARD ............................................................... 16-4 16.2 ADDING CONTENT TO YOUR MMIS DASHBOARD.................................. 16-5 16.3 EDITING YOUR MMIS DASHBOARD ........................................................... 16-8

SECTION 17 SKILL TESTS .................................................................................... 17–3

17.0 INTRODUCTION ............................................................................................. 17–3 17.1 SKILL TEST 1................................................................................................... 17–3 17.2 SKILL TEST 2................................................................................................... 17–4 17.3 SKILL TEST 3................................................................................................... 17–5 17.4 SKILL TEST 4................................................................................................... 17–7 17.5 SKILL TEST 5................................................................................................... 17–7 17.6 SKILL TEST 6................................................................................................... 17–8

APPENDIX A STRUCTURED QUERY LANGUAGE ........................................... A–3 APPENDIX B EAGLE LCNS TO BOM IMPORT .................................................. B–3 INDEX ................................................................................................................................ 3


x


LIST

OF

ILLUSTRATIONS

MMIS WORKBOOK LIST OF ILLUSTRATIONS

xiii

LIST OF ILLUSTRATIONS

FIGURE PAGE

Figure 1. MMIS Home Page ........................................................................................... 1-9

Figure 2. MMIS Home Page - MMIS Login .................................................................. 2-3

Figure 3. MMIS Login Window ..................................................................................... 2-4

Figure 4. Main Menu - Passwords Selected. ................................................................... 2-5

Figure 5. Password Maintenance .................................................................................... 2-6

Figure 6. Inventory Management - Site Maint ................................................................ 2-7

Figure 7. Site Identification Information Finder - End Item Selected ............................ 2-7

Figure 8. Site Identification Finder - Query Results ....................................................... 2-8

Figure 9. Site Identification Information Finder - Query Results ................................... 2-9

Figure 10. Site Identification Information Finder - Query Results B% .......................... 2-9

Figure 11. Site Identification Information Finder - Query Results Underscore ............ 2-10

Figure 12. Project Setup - Programs .............................................................................. 3–4

Figure 13. Program Identification Finder - New Button ................................................ 3–5

Figure 14. Program Identification Information Maintenance - TST Entered ................ 3–5

Figure 15. Program Identification Finder - Query Results TST .................................... 3–7

Figure 16. Program Identification Information Maintenance - Current Information ..... 3–8

Figure 17. Detail Program Information - Program Type: drop down list ...................... 3–8

Figure 18. Document Tracking System - New Document .............................................. 4-4

Figure 19. Document Tracking System - Document Category ....................................... 4-5

Figure 20. Explorer User Prompt - Bicycle Assembly ................................................... 4-6

Figure 21. Document Tracking System - Bicycle Assembly ID ..................................... 4-7

Figure 22. Document Tracking System - View Document Link .................................... 4-8

Figure 23. Document Window - Bicycle Assembly Image Retrieved ............................ 4-9

Figure 24. ECP Finder .................................................................................................... 5-4

Figure 25. LCN Record Finder - Configuration Items Unchecked ................................. 5-5

Figure 26. LCN Record Finder - Query Results ............................................................. 5-5

Figure 27. ECP Details - MMIS DEMO ECP ................................................................ 5-6

Figure 28. Select Documents - Query Results ................................................................ 5-8

Figure 29. Ref. Data - Document Added ........................................................................ 5-9

Figure 30. Ref. Data - Image Viewed ............................................................................. 5-9

Figure 31. Contract Information Maintenance - New Contract ...................................... 6-4

Figure 32. CLIN Maintenance ........................................................................................ 6-5

Figure 33. CLIN Detail Information Maintenance ......................................................... 6-6

Figure 34. Asbuilt - Table(s) HG and ZABCM .............................................................. 7-3

Figure 35. Search AsBuilt Master Configurations .......................................................... 7-4


xiv

Figure 36. Create New AsBuilt Master Configuration - Query Results ......................... 7-5

Figure 37. AsBuilt Master Configuration Maintenance - Top Level Part ...................... 7-6

Figure 38. Insert New AsBuilt Master Part Window - Partial Query Results. ............... 7-7

Figure 39. AsBuilt Master Configuration Maintenance - Lower Indenture Added ........ 7-7

Figure 40. Insert New AsBuilt Master Part - Available Subcomponents ....................... 7-9

Figure 41. AsBuilt Master Configuration Maintenance - Subcomponents Added... .... 7-10

Figure 42. Create New AsBuilt Master Configuration Window - ESL749ZF displayed..7-

11

Figure 43. Top Level Part Information - ESL749ZF displayed .................................... 7-12

Figure 44. AsBuilt Master Configuration Maintenance - Subcomponents Added... .... 7-12

Figure 45. Search AsBuilt Master Configurations - AsBuilt Master Reports Menu .... 7-13

Figure 46. AsBuilt Master Reports Menu – Enlarged .................................................. 7-14

Figure 47. Approved Build State Breakdown Report - Bicycle Assembly ................... 7-15

Figure 48. AsBuilt Master Config Report - MC-168119 .............................................. 7-16

Figure 49. AsBuilt Master History Report – Partial ..................................................... 7-18

Figure 50. AsBuilt Master Config vs HG Report – ALCs ............................................ 7-19

Figure 51. Search AsBuilt Configurations .................................................................... 7-20

Figure 52. Create New AsBuilt Configuration - Query Results ................................... 7-21

Figure 53. Create New AsBuilt Configuration - New Serial # ..................................... 7-22

Figure 54. AsBuilt vs AsBuilt Master Compare - Before Save .................................... 7-22

Figure 55. AsBuilt vs AsBuilt Master Compare - After Save....................................... 7-23

Figure 56. Search AsBuilt Configurations - Query Results .......................................... 7-24

Figure 57. Create New AsBuilt Configuration - New Serial Number .......................... 7-25

Figure 58. AsBuilt vs AsBuilt Master Compare - Before Import ................................. 7-26

Figure 59. Import Existing AsBuilt Configuration - LCN BIKE01.............................. 7-27

Figure 60. AsBuilt vs AsBuilt Master Compare - After Import ................................... 7-28

Figure 61. AsBuilt vs AsBuilt Master Compare - Sibling Serial Numbers ............ 7-29

Figure 62. AsBuilt vs AsBuilt Master Compare - Subassemblies Added ..................... 7-30

Figure 63. Search AsBuilt Configurations - TOP% Query results ............................... 7-31

Figure 64. AsBuilt Configuration Maintenance - Confirm Release ............................. 7-32

Figure 65. AsBuilt Configuration Release - Flow down .............................................. 7-33

Figure 66. Select CAVS, Contract and Location Information - RFI Selected .............. 7-34

Figure 67. Search AsBuilt Configurations - Green Light ............................................. 7-37

Figure 68. Search AsMaintained Configurations - Query Results .................................. 8-4

Figure 69. AsMaintained vs AsBuilt Compare - Unchanged ......................................... 8-5

Figure 70. AsMaintained vs AsBuilt Compare - Color Key Expanded .......................... 8-5

Figure 71. Remove Part – Part Information - TZH1000. ................................................ 8-6

Figure 73. AsMaintained vs AsBuilt Compare - Subassembly Removed (Red) ............ 8-7

Figure 74. AsMaintained vs AsBuilt Compare - Report Dropdown ............................... 8-8

Figure 75. AsMaintained / AsBuilt Master Part Number Absences Report – Example . 8-9

Figure 76. Search AsMaintained Configurations - Sub Assembly removed ................ 8-10


xv

Figure 77. AsMaintained vs AsBuilt Compare - Sub Assembly Removed .................. 8-11

Figure 78. Import Existing AsMaintained Configuration - Frame Assembly .............. 8-12

Figure 79. AsMaintained vs AsBuilt Compare - Assembly Imported .......................... 8-13

Figure 80. AsMaintained Break Down Report - Current Configuration (3 of 3)… ...... 8-14

Figure 81. AsMaintained Break Down Report - Previous Configuration (1 of 3)... ..... 8-15

Figure 82. AsMaintained Configurations - Snapshots .................................................. 8-16

Figure 83. Site Identification Information Finder ........................................................... 9-4

Figure 84. Site Identification Information Finder - Query Results ................................. 9-4

Figure 85. Site Identification Information Maintenance - TB saved .............................. 9-5

Figure 86. Location Identification Maintenance with data entered ................................ 9-8

Figure 87. Site Maintenance – Post Save ........................................................................ 9-8

Figure 88. Serialized Inventory Finder ......................................................................... 9-10

Figure 89. Serialized Inventory Finder - Query Results ............................................... 9-11

Figure 90. Change Location - Save Changes ................................................................ 9-12

Figure 91. Serialized Inventory History - History Results ............................................ 9-13

Figure 92. ECP Finder - Query Results ........................................................................ 9-14

Figure 93. ECP Details ................................................................................................. 9-15

Figure 94. Ref. Data - ECP Information ....................................................................... 9-16

Figure 95. Select Serial Inventory ................................................................................ 9-17

Figure 96. Select Serial Inventory - TOP% Query Results ........................................... 9-17

Figure 97. Ref. Data - Serialized Inventory Added ...................................................... 9-18

Figure 98. Create New FRACAS Defect - Query Results” .......................................... 10-5

Figure 99. FRACAS Defects Maintenance Screen (Upper) - Defect Number ............. 10-5

Figure 100. FRACAS Defects Maintenance Screen (Lower) ....................................... 10-6

Figure 101. Defective & Replacement Parts window ................................................... 10-8

Figure 102. Select Serialized Defective Part window ................................................... 10-9

Figure 103. Defective & Replacement Parts window - Data Entered ......................... 10-10

Figure 104. FRACAS Defects Maintenance ............................................................... 10-11

Figure 105. Corrective Action window - Data Entered .............................................. 10-12

Figure 106. Main Menu - FFR Wizard ....................................................................... 10-14

Figure 107. FFR Wizard - Select a Squadron ............................................................. 10-15

Figure 108. FFR Wizard - Select a Part Number ........................................................ 10-16

Figure 109. FFR Wizard - Select a Serial Number ..................................................... 10-17

Figure 110. FFR Wizard - Select a Customer ............................................................. 10-18

Figure 111. FFR Wizard - FFR Main ......................................................................... 10-19

Figure 112. Field FRACAS Defects Information Finder ............................................ 10-20

Figure 113. Field FRACAS Defects - Query Results ................................................. 10-21

Figure 114. FRACAS Defects Maintenance ............................................................... 10-22

Figure 115. FRACAS Defects Maintenance - Part Information ................................. 10-23

Figure 116. FRACAS Defects Maintenance - TOPLEVEL1 ..................................... 10-25

Figure 117. Field FRACAS Defects - Query Results ................................................. 10-26


xvi

Figure 118. FRACAS Defects Maintenance - Confirm Delete................................... 10-26

Figure 119. Part Routing Operations Information Finder ............................................. 11-4

Figure 120. Part Routing Operations Information Maintenance - Before Save ............ 11-5

Figure 121. Depot Route Information Finder ............................................................... 11-7

Figure 122. Depot Route Information Finder - New Record ........................................ 11-9

Figure 123. Depot Route Information Finder - New Record Saved ............................. 11-9

Figure 124. Routing Operation Information Maintenance - Site Added .................... 11-10

Figure 125. Routing Operation Information Maintenance - Find Operation .............. 11-11

Figure 126. Routing Operation Information Maintenance - Operation Added….. ..... 11-12

Figure 127. Depot Route Information Finder - Query Results ................................... 11-13

Figure 128. Clone Depot Route - Rev. 1 .................................................................... 11-14

Figure 129. Depot Route Information Finder - Rev. 1 Added .................................... 11-15

Figure 130. Traveler Identification Information Finder .............................................. 11-16

Figure 131. Part Number/Serial/Number Search - Query Results .............................. 11-16

Figure 132. Create MMIS Tracking Number – Data Entered ..................................... 11-17

Figure 133. Traveler Identification Information Maintenance ................................... 11-18

Figure 134. ECPs Section – Expanded ....................................................................... 11-19

Figure 135. FRACAS Defects Section - Expanded .................................................... 11-20

Figure 136. Traveler Route Maintenance ................................................................... 11-21

Figure 137. Routes Available ..................................................................................... 11-22

Figure 138. Traveler Routes - Demo Route (-) Added ............................................... 11-23

Figure 139. Traveler Route Maintenance - Route Information Added ....................... 11-24

Figure 140. Traveler Route Maintenance - Route Information Expanded .................. 11-25

Figure 141. Traveler Route Maintenance - Operation Completed .............................. 11-26

Figure 142. Defective & Replacement Parts window ................................................. 11-28

Figure 143. Select Serialized Defective Part .............................................................. 11-29

Figure 144. Defective & Replacement Parts window - Before Save .......................... 11-30

Figure 145. Defective & Replacement Parts window - After Save ............................ 11-31

Figure 146. Create MMIS Tracking Number - Child Traveler ................................... 11-32

Figure 147. Traveler Identification Information Maintenance - Child Traveler….. ... 11-33

Figure 148. Child Traveler Information - Before expansion ...................................... 11-34

Figure 149. Child Traveler Information - After expansion ......................................... 11-34

Figure 153. Action Log Edit Screen ............................................................................. 12-5

Figure 154. Action Log Edit Screen After Saving ........................................................ 12-6

Figure 155. Action Log Finder with Records ............................................................... 12-8

Figure 156. Inline Entry ................................................................................................ 12-9

Figure 157. MMIS AdHoc Screen ............................................................................. 15–10

Figure 158. MMIS AdHoc – Tables .......................................................................... 15–11

Figure 159. MMIS Adhoc - Table HA ....................................................................... 15–11

Figure 160. MMIS AdHoc - Database Columns Expanded ....................................... 15–12

Figure 161. MMIS Adhoc - SQL Query Displayed ................................................... 15–12


xvii

Figure 162. AdHoc Tables - Table HG. ..................................................................... 15–13

Figure 163. MMIS AdHoc - Columns Selected ......................................................... 15–14

Figure 164. MMIS AdHoc - SQL Statement Displayed ............................................ 15–14

Figure 165. MMIS AdHoc - Where Window ............................................................ 15–15

Figure 166. AdHoc Where Window - LSACONXB Selected ................................... 15–16

Figure 167. AdHoc Where Window - Operator List.................................................. 15–16

Figure 168. MMIS AdHoc Where Window - Completed Where Clause .................. 15–17

Figure 169. MMIS AdHoc - Query Results ............................................................... 15–19

Figure 170. MMIS Query results - Exported to Excel ............................................... 15–20

Figure 171. MMIS Homepage ...................................................................................... 16-3

Figure 172. Blank MMIS Dashboard ............................................................................ 16-4

Figure 173. MMIS Dashboard Report Selection .......................................................... 16-5

Figure 174. MMIS Dashboard - Parameter Form ......................................................... 16-6

Figure 175. MMIS Dashboard - Traveler Parts Report ................................................ 16-7

Figure 176. MMIS Dashboard with Multiple Reports - Example ................................ 16-7

Figure 177. MMIS Dashboard - Header with Options .................................................. 16-8

Figure 178. MMIS Dashboard Report Header in Edit Mode ........................................ 16-9

Figure 179. MMIS Dashboard – Traveler Serial Numbers Report ............................. 16-10

Figure 180. Moving Report to New Location - Example ........................................... 16-11

Figure 181. Navigator-Assign LCNs to BOM .............................................................. B–4

Figure 182. Automatically Assign LCNs ...................................................................... B–5

Figure 183. Clipboard Format-Clipboard Format Button ............................................. B–6

Figure 184. Clipboard Format-Paste Clipboard ............................................................ B–8

Figure 185. Automatically Assign LCNs-Paste Clipboard ........................................... B–9

Figure 186. Automatically Assign HG Indenture Codes? .......................................... B–10

Figure 187. Automatically Assign LCNs- Calculate LCNs ........................................ B–11

Figure 188. Database Error Messages-View Results .................................................. B–12

Figure 189. Automatically Assign LCNs-Addl Parts/TM Data .................................. B–14


xviii


SECTION 1

INTRODUCTION

MMIS WORKBOOK SECTION 1 INTRODUCTION

1-3


1-4

SECTION 1 INTRODUCTION

1.0 INTRODUCTION

This section provides a brief overview of LSA/LSAR, Enhanced Automated Graphical

Logistics Environment (EAGLE) and the EAGLE Maintenance Management Information

System (MMIS).

1.1 LSA/LSAR

For the purposes of this Workbook, all references to Logistics Support Analysis (LSA)

and Logistics Support Analysis Record (LSAR) are based upon the use of the MIL-STD-

1388-Specification; Specifically 1388-1 and 1388-2B.

Logistics Support Analysis. The LSA provides a foundation for the Integrated Logistics

Support (ILS) program by generating source data and maintenance plans, which will

direct other ILS elements such as training, technical publication, provisioning and in the

case of MMIS, PBL Support.

Logistics Support Analysis Record. The LSAR documents data across all ILS functional

areas. This characteristic makes the LSAR an ideal vehicle for integration of systems

engineering design, manufacturing, and product support databases for lifecycle

management of a system. The relational design of LSAR data is intended to facilitate

such integration and to encourage independent development of useful ad hoc queries

which promote use of the data in the design process.

1.2 EAGLE

EAGLE is a relational database built on the MIL-STD-1388-2B specification. This

military standard lays out how a relational LSAR database should be structured and

functions.

The EAGLE frontend (Client) allows for ease of use in the entry, editing maintenance

and reporting of the data stored in the LSAR Database.


1-5

1.3 RELATIONAL DATABASE

A relational database is a set of tables, which relate to each other. Each table has

columns and rows. A table is somewhat like an Excel spreadsheet. Each column has a

pre-defined data type (DED), such as text, numbers, and so forth. Under that column,

you can only put in that type (you cannot put text in a number column, for instance).

Tables also contain rows, each of which holds data. When we get data from EAGLE, we

are usually getting rows from a table. Each row has a set of columns called keys. These

keys make that row unique in the table: no other row in the table can have the same set of

keys.

Tables may have multiple columns that are keys. For instance, we have the following

row, where keys are bold face: (A, B, C, D, E). D and E are common data. A, B, and C

are keys. We cannot have another row that has A, B, and C as keys in this table because

it already contains a row with those keys. We may have a row with (A, B, D, D, E).

1.3.1 Relationships Between Tables

The relational database relates tables through key structures. We have what are called

parent tables and child tables. Child tables ‘point to’ parent tables by inheriting the key

structure of the parent table. Assume we have a parent table, A, which has the key

structure (EIACODXA, LCNSTRXA). Now we have a child table, B, with the key

structure (EIACODXA, LSACONXB, ALTLCNXB, LCNTYPXB) (all keys). Now,

table A relates to table B through the EIACODXA column. That is, any row in B will

have to have a corresponding row in A with the same EIACODXA.

This structure creates safeguards for the data. As you will see later, almost every table in

EAGLE has the EIACODXA (End Item) column in it. At the top of the EAGLE

database there is a table, XA, which holds the end item data and only has EIACODXA as

a key. This creates stronger structural integrity through the database. That row in XA

cannot be deleted without all rows in child tables of XA being deleted first. If XA is

copied, all child data must be copied also. All child table data with the same

EIACODXA is known to relate to that end item.

The set of columns in a table which relate to a parent table is called the foreign key or

each column with this characteristic is called a foreign key. The other keys are called

primary keys. Note that key structures still have to be unique. That is, for every record


1-6

in a child table, you know that there is one and only one record in their parent table.

Some tables, however, have multiple parents.

1.3.2 End Items

As mentioned before, table XA contains End Item data. Generally an end item is a top

level product, such as a tank, bicycle, helicopter, and so forth. It is used to identify the

project/program that is being worked on currently. When working in EAGLE or MMIS,

you will work with data from one End Item at a time. This ensures that data between

projects is not confused and accidentally entered incorrectly.

Technically speaking, the End Item column in XA, EIACODXA, is a 10 character

alphanumeric column. This means it contains 10 characters, where characters are letter

and/or numbers. Upper case and lower case letters are usually seen as the same thing

inside the database, so for our purposes A = a [Note: upper and lower case characters

are different on some columns, usually comments, but it isn’t common].

1.3.3 Eagle Database Structure and LSAR

Table XA is parent table of almost all other tables in EAGLE. It contains the

EIACODXA, end item acronym code, which serves to define the End Item

for underlying tables. When an LSAR structure is used, an LCN structure is

required.

Table XB holds the LCN (Logistics Support Analysis Control Number) data

for the database. All tables with LCN data in them will hang off this table or

a child of this table. The keys for this table are EIACODXA (End Item),

LSACONXB (LCN), ALTLCNXB (ALC), LCNTYPXB (LCN Type).

Table XH houses the Commercial and Government Entity Code (CAGE

code). It is a child of XA, and therefore contains EIACODXA. It also has

CAGECDXH (CAGE code) as a primary key. A CAGE code is something

like a code for a vendor. This table also contains an address and name for the

contract and government entity.


1-7

Table HA combines a CAGE code with a Reference number. This Reference

number is used to identify individual parts. This table gives you an overview

of what parts you have and who makes them. It contains additional

information about the part, such as the name and National Stock Number

(NSN). Table HA’s keys are EIACODXA, CAGECDXH, and REFNUMHA

(Reference Number).

Table HG is a child of both XB and HA. It combines an LCN structure from

XB with a Reference number and CAGE code from HA. Its keys are keys

from both XB and HA, combined.

In XA there is the LCNSTRXA column, which describes the LCN structure.

For the item above, it would be 42, signaling that the first overall part is 4

characters long, and then the next indenture level down is 2. The second

indenture level could contain, say, the frame and the wheels at BIKEAA and

BIKEAB. From there, we can also have an LCN structure of 422, which lets

us drill down lower. Say on the frame there is the seat, BIKEAAAA, the

handle bars, BIKEAAAB, and the forks, BIKEAAAC.

A second Key in Table XB is ALC. This allows for alternate configurations.

You could have BIKEAA with ALC 0 and BIKEAA with ALC 1 which may

be 2 different types of bike frames. You would use reference numbers and

CAGE codes to differ on what company and part the frame is, but if the

frame has different specifications, such as one being a men’s frame, one

being a woman’s frame, then you would use ALC to specify alternate

configuration for the bicycle. These configurations would drill down from

there, and all of the LCN structure would have to be stored with a different

ALC.


1-8

1.4 MMIS

MMIS is an acronym for Maintenance Management Information System, and like

EAGLE, MMIS is a set of relational tables that exist inside of an Oracle Database

Management System. In fact MMIS is just an extension of the EAGLE database.

Typically, EAGLE is used to capture bill of materials, reliability, task analysis, technical

manuals and provisioning data. MMIS is typically used for managing the maintenance,

material management, and repair of fielded systems in a depot environment.

MMIS is a Web Based Application. As mentioned before, MMIS is an extension of the

Eagle Tables. The MMIS Configuration data is based upon the Part Application

Provisioning Table (HG). This provides for greater data/hardware configuration

integrity.

MMIS may also be used to manage Engineering Change Proposals, Failure Reporting

and Corrective Action, program related documentation, and contract data requirements.

These areas will be covered in more detail in the Workbook. Unlike EAGLE, MMIS is

accessed using a standard web browser such as Microsoft Internet Explorer. Therefore,

MMIS can be easily deployed globally because it does not need to be installed and

updated on each user’s machine. In addition, the MMIS software is designed to run on

many different operating systems such as Microsoft Windows, HP Unix, Linux and

SunOS. In terms of security and authentication, MMIS uses the same user ids and

passwords that EAGLE users. Consequently, if desired, a user account can be set up to

allow the user to log into the database repository with EAGLE or MMIS.

1.4.1 MMIS Home Page

The MMIS home page (Figure 1) is accessed using a web browser by typing the IP

address or URL of the MMIS server into the address text box. When this happens, a

request is made to a web server that has the MMIS software installed on it. When a user

initially reaches the MMIS home page, only a small amount of information will be

available to him or her.


1-9

Figure 1. MMIS Home Page

1.5 Conventions Used In Documentation

Before using MMIS, it is important to understand the terms and notation conventions

used in the documentation.


1-10

1.5.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.

The words “Window”, “Screen” and “Page” are used interchangeably.

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 MMIS.

For example, the Project Setup Discipline or the AsBuilt Discipline.

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

functions within a discipline. For example, the Project Setup Discipline has

a Customers Function, a Programs Function, and a User ID 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 (•).


1-11

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.5.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-12

1.5.3 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.

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.

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-13

1.5.4 Use of Icons in MMIS

Generally, while working in MMIS, placing the cursor over an icon will provide a

description of that icons function for that specific situation. In some areas, icons may be

used for different functions.

Icons are used in the same manner as buttons, in that choosing an icon and clicking on it

will provide an action.

Move. Used to move a data record.

Edit. Used to edit record data.

Insert. Used to insert an assembly (record) into a next higher assembly.

Delete. Used to delete records.

Show AsBuilt-AsMaintained differences (AsMaintained has been released and

changed).

Unrelease AsBuilt from AsMaintained.

Show AsBuilt-AsMaintained differences (AsMaintained has been released and

imported into another system.

Used to show AsBuilt Configuration Breakdown Picture (XLS spreadsheet or

HTML).

Release AsBuilt to AsMaintained.

View Part History.


MMIS MAIN MENU

and NAVIGATION

SECTION 2

MMIS WORKBOOK SECTION 2 MMIS MAIN MENU and NAVIGATION

2-3

SECTION 2 MMIS MAIN MENU and NAVIGATION

2.0 INTRODUCTION

This section provides an overview of the MMIS Main Menu and Navigation tools

provided.

Figure 2. MMIS Home Page - MMIS Login

2.1 MAIN MENU

STEP To access the MMIS Main Menu and Login perform the following from the

MMIS Homepage (Figure 2):


2-4

Choose the button. Figure 3 is displayed.

Figure 3. MMIS Login Window

After entering the correct User Name: and Password: the user will have access to all

disciplines within MMIS that the administrator has deemed appropriate and necessary.

The menu is customizable for the specific user, so different users may have different

options available to them.

Hovering over a menu option (Figure 4) will display any sub-disciplines if they exist. A

greater-than character (->) at the right side of the menu entry shows that a sub-discipline

should exist.


2-5

Figure 4. Main Menu - Passwords Selected.

2.2 CHANGING PASSWORD

Your user id and password are assigned to you by your system administrator. Typically

rules regarding password structure are up to the administrator for your MMIS system.

STEP To change your password, perform the following from the Main Menu:

Choose Project Setup -> Passwords (Figure 4). The Password Maintenance

screen is displayed (Figure 5)

Enter your new password in the New Password: text box

Enter your new password in the Verify New Password: text box

Choose the button


2-6

Your new password will be validated and will be required the next time you log into

MMIS.

Figure 5. Password Maintenance

2.3 RETRIEVING RECORDS

When data is queried and retrieved from MMIS it is generally done through a “Finder

Screen”. The Site Identification Information Finder (Figure 7) will be used throughout

this section to demonstrate some of the basic elements of retrieving records in MMIS.


2-7

Figure 6. Inventory Management - Site Maint

Figure 7. Site Identification Information Finder - End Item Selected


2-8

Nearly all finder screens in MMIS have the End Item drop down on them. In Figure 7,

the End Item drop down has been used to select “BICYCLEXX”. It is highly

recommended that users check to make sure which End Item is selected before

performing a search. We arrived at the Site Identification Finder (Figure 7) by

Navigating to Main Menu -> Inventory Management -> Site Maint as shown in Figure 6.

This is important as some customizations in MMIS will not be shown unless an End Item

is selected. Once an End Item is selected and a query performed, that End Item will be

the default on other MMIS screens. The End Item can still be changed to search other

End Items.

The simplest way to search is to choose the End Item and Choose the Query button

(Figure 8). This can be a slow process though when there are thousands of records.

Figure 8. Site Identification Finder - Query Results

To limit the number of records returned, additional search criteria can be added, such as

Site Description. The next example shows the results of entering “RAYTHEON -

FOREST, MS” (without the quotes) into the Site Description finder field and then

choosing the button (Figure 9).


2-9

Figure 9. Site Identification Information Finder - Query Results

Only records that match all search requirements will be returned. For instance, in the

example above, putting “AZ” into the Site Code box also would have caused no results

to be returned because no records exist with “AZ” as the Site Code and “RAYTHEON -

FOREST, MS” as the Site Description.

If you want to match a group of records or limit the results without typing the entire

description you can include wildcards into your searches. Two wildcards are used in

MMIS: percent (%) and underscore (_). The percent matches zero or more of any

character or characters and the underscore must match exactly one character.

Figure 10. Site Identification Information Finder - Query Results B%


2-10

To get all records with a Site Description starting with B, a “B%” (no quotes) can be

entered into the Site Description text box. The results of that Query are shown in Figure

10.

The underscore is less commonly used, but works well when a pattern exists. For

instance, if we wanted to find all records with a three-character Site Description, we may

enter “___” (3 underscores) in the Site Description text box. The results of that Query

are shown in Figure 11.

Figure 11. Site Identification Information Finder - Query Results Underscore

Most finders also offer the ability to sort the results. Once the search criteria are entered

and the results returned, clicking on the column header will sort the results without

refreshing the page.

Regardless of the search parameters used, once the query has executed, the rows returned

will display summary information, and will generally have links to other screens which

contain detail information, or related information.

On this screen (Figure 11), clicking on the Site Code link (blue text) will take the user to

a detail information screen where the record can be edited. Choosing the icon will

take the user to a screen to delete the record. In addition, most finders have a

button, which allows the user to insert a new record.

In summary, the finder screens in MMIS allow users to locate information and then add,

edit, or delete records in the system.


PROJECT SETUP

SECTION 3

PROJECT SETUP

MMIS WORKBOOK SECTION 3 PROJECT SETUP

3–3

SECTION 3 PROJECT SETUP

3.0 INTRODUCTION

Under the project setup area, there are many sub-disciplines. However, in this training

session we will focus on only the base information that is needed by other areas of

MMIS. If you would like more information on a particular area, we can discuss those

areas further in class.

Keep in mind the system administrator has the capability to customize the MMIS menu

based on a user profile, and is able to add and remove menu items for each user.

3.1 ADDING A PROGRAM CODE

A “Program Code”, in the MMIS system is simply a 3 character code used to identify a

specific program. This code is used in the work order system (Traveler), to create a

unique work order number that can be traced to a particular program. Therefore, when

we create a new work order, one of the pieces of information we will be asked for is the

“Program Code”. The MMIS database table that will be inserted into in this exercise is

“ZPGM”.


3–4

Figure 12. Project Setup - Programs

STEP Log into the MMIS system using the User Name: and Password: assigned by

your instructor. From the Main Menu (Figure 12), perform the following:

Navigate to Project Setup -> Programs

The Program Identification Finder is displayed (Figure 13). If “ALL” is

displayed in the End Item: text box, select your correct End Item assigned

by the Eagle Instructor.


3–5

Figure 13. Program Identification Finder - New Button

Choose the button. The Program Identification Information

Maintenance window will be displayed (Figure 14). Figure 14 is shown after

data has been entered.

Figure 14. Program Identification Information Maintenance - TST Entered

Enter “TST” into the Program Code data field

Select “Air Force” from the Program Type: drop down list

Enter “Training Program” into the Program Name: data field

Choose the button


3–6

Info: Upon choosing the button, MMIS will post an “INSERT” statement to the

Oracle database to update the table that stores the program information.

3.2 VIEWING AND EDITING A PROGRAM CODE

STEP To View and Edit a Program Code, perform the following from the Program

Identification Information Maintenance screen (Figure 14):

Note: There are two back buttons, one on your web browser, and one on the program

edit screen.


3–7

Choose the button on the program edit screen. The Program

Identification Finder will be displayed

Enter “TST” in the Program Code finder box

Choose the button. Figure 15 will be displayed

Figure 15. Program Identification Finder - Query Results TST

Choose the “TST” hyperlink. The Program Identification Information

Maintenance Window will be displayed with the current information (Figure

16)


3–8

Figure 16. Program Identification Information Maintenance - Current Information

Select “Navy “ from the “Program Type:” drop down list, as shown in

Figure 17

Figure 17. Detail Program Information - Program Type: drop down list


3–9

Choose the button. The changes are then saved to the database

automatically using an “UPDATE” statement

STEP Perform the following Self Test:

Add a new program code to the database called “RDR”

Designate this as an Army program. The program name is “THOR”.

Save the changes to the database, and navigate back to the Program

Identification Finder

Add a new program code to the database called “ITT”.

Designate this as an Army program. The program name is “ITT

TRAINING”

Save the changes to the database, and navigate back to the Program

Identification Finder

Delete the ITT program code


3–10

3.3 ADDING CUSTOMER INFORMATION

The Customer application is used to maintain customer information for use with the

FRACAS application within MMIS.

STEP To add customer information, perform the following:

Navigate to Project Setup -> Customers. The Customer Information Finder

is displayed

Make sure the correct End Item is selected

Choose the button to view existing records, if any exist

Choose the button. The Customer Information Maintenance window

is displayed

Enter and Save the following Customer records as shown:

3.4 ADDING COST ACCOUNT INFORMATION

The Cost Account function is used to establish cost account data against which repair

actions are charged. Part numbers may be associated with Cost Accounts, enabling users

to identify the correct cost account to be charged for repairs made to an item.

STEP To add Cost Account information, perform the following:


3–11

Navigate to Project Setup -> Cost Accounts. The Cost Account Finder is

displayed


Choose the button. The Cost Account Information Maintenance

window is displayed.

Enter “R-2010-1” in the Charge Number: text box and “Sustaining Repair” in

the Charge Number Description: text box

Choose the button

Choose the button

Choose the button

Enter “R-2010-2” in the Charge Number: text box and “ECP Incorporation”

in the Charge Number Description: text box

Choose the button


3–12


DOCUMENT SYSTEM

SECTION 4

MMIS WORKBOOK SECTION 4 DOCUMENT SYSTEM

4-3

SECTION 4 DOCUMENT SYSTEM

4.0 INTRODUCTION

The MMIS document system is a module that allows the user to upload binary and text

documents into the database. Virtually any format can be stored and viewed from MMIS.

The document itself is stored in table ZD as a Binary Large Object, or BLOB.

When the BLOB is accessed using MMIS is it rendered on the client browser using the

application that is associated with the MIME type of the document that is downloaded.

For example, if an MS-Word document was stored in the database your computer would

most likely have MS-Word associated with a MIME type of “.doc”. Therefore, when the

document is downloaded, MS Word will open and launch the document.

Throughout the MMIS application there are areas where documents can be attached.

These records are all stored in table ZD, but are cross referenced using either cross

reference tables, or embedded html tags.

4.1 UPLOADING AND VIEWING A DOCUMENT

STEP To upload a document, perform the following:

Navigate to Documents -> Doc Viewer. The Document Tracking System

window is displayed

Make sure your correct End Item is selected

Choose the button. Figure 18 is displayed


4-4

Figure 18. Document Tracking System - New Document

Choose the button

Browse to “Bicycle Assembly 1.jpg” on your desktop. Another file may be

available as directed

Choose the button

Note: This will automatically fill in both the Document ID text box and the Type drop

down with data. You can edit the Document ID field, but a conflict will occur if a

document with the same Document ID, type, and revision already exists in the

documents table.


4-5

Figure 19. Document Tracking System - Document Category

Choose the button located to the right of the Document Category:

drop down as shown in Figure 19

The Explorer User Prompt is displayed (Figure 20)


4-6

Figure 20. Explorer User Prompt - Bicycle Assembly

At the prompt, Enter “BICYCLE ASSEMBLY” in the data field

Choose the button. Notice the Document Category: folder is

OPEN and a drop down list box is available (Figure 21)

Select “BICYCLE ASSEMBLY” from the drop down list

Choose the button. Notice that the BICYCLE ASSEMBLY 1 image

appears in the document list at the left side of the screen


4-7

Figure 21. Document Tracking System - Bicycle Assembly ID

Note: This process has put the document with the Document ID of “BICYCLE

ASSEMBLY 1.JPG” in the CATEGORIZED -> BICYCLE ASEMBLY Folder,

which can be used for organizational purposes. You can create Sub Categories

for more organization of document placement.

STEP To view the uploaded document, perform the following:

Click on the “BICYCLE ASSEMBLY 1.JPG” hyperlink (Figure 22) to

launch the document. Depending on browser settings, the image may display

inside the document window (Figure 23).


4-8

Figure 22. Document Tracking System - View Document Link


4-9

Figure 23. Document Window - Bicycle Assembly Image Retrieved

STEP Perform the following Self Test:

Upload the “Brake Assy.BMP” from the desktop as was done in Section 4.1

for the Bicycle Assembly

Place this document in Document Category “Controls Assembly”

View the Uploaded Document


4-10


ECP SYSTEM

SECTION 5

MMIS WORKBOOK SECTION 5 ECP SYSTEM

5-3

SECTION 5 ECP SYSTEM

5.0 INTRODUCTION

The Engineering Change Proposal (ECP) Discipline is located under the Configuration

Management section of the MMIS Main Menu. This area allows the user to input ECPs,

ECP detail information, and cross reference ECPs to many other areas such as:

Drawings

Illustrations

Documents

Tech Manuals

Serialized Inventory

AsMaintained Configuration

Contract Line Items

Routes

Part Application

In addition, the ECP Discipline allows for user defined approval flows to be created and

attached to an ECP.


5-4

5.1 ADDING A NEW ECP

STEP To add a new ECP perform the following:

Navigate to Configuration Management -> Engineering Change Proposals.

The ECP Finder is displayed (Figure 24)

Figure 24. ECP Finder




5-5

Figure 25. LCN Record Finder - Configuration Items Unchecked

Uncheck the Show only LCNs designated as Configuration Items:

checkbox as shown

Enter “BIKE” in the LCN finder text box


Figure 26. LCN Record Finder - Query Results

Choose the icon to the left of the record with LCN “BIKE”, ALC “0”.

The ECP Details window is displayed (Figure 27). Figure 27 is shown with

data entered and saved


5-6

Figure 27. ECP Details - MMIS DEMO ECP

Leave “(Auto Generate)” as the ECP Number

Select “Active 1” from the Review Status drop down list

Select “1” from the ECP Classification: drop down list

Enter “MMIS DEMO ECP” in the ECP Title: data box

Enter “This is a demo ECP” in the Change Proposal: text box

Choose the button


5-7

5.2 ATTACHING A DOCUMENT TO AN ECP

STEP To attach a document to an ECP, perform the following. These instructions

assume the user is continuing from the ECP Details window:

Choose the button. Ref. Data window is displayed. No figure

is shown at this time

Choose the button. The Select Documents window is

displayed (Figure 28). Figure 28 is shown after the next Query

Choose the “Attach an Existing Document” button.

Note: The query has returned documents that can be associated with an ECP. This

information is stored in table ZD in the EAGLE/MMIS database.


5-8

Figure 28. Select Documents - Query Results

Choose the icon next to the record with “BICYCLE ASSEMBLY 1” as

the Document ID. The Ref. Data window is re-displayed (Figure 29)

Choose the button

Choose the button

Note: This is the image that was uploaded into the Document System. Documents may

be uploaded using both MMIS and EAGLE (Document Storage) Functionality.


5-9

Figure 29. Ref. Data - Document Added

Choose the hyperlink, BICYCLE ASSEMBLY 1 to view the image (Figure

30)

Figure 30. Ref. Data - Image Viewed


5-10


CONTRACT

SYSTEM

SECTION 6

MMIS WORKBOOK SECTION 6 CONTRACT SYSTEM

6-3

SECTION 6 CONTRACT SYSTEM

6.0 INTRODUCTION

The Contract System Discipline allows the user to create and maintain information about

the contracts related to a program. The Contract Function is used to document the

processing and tracking of contractual data.

6.1 ADDING A NEW CONTRACT NUMBER

STEP To illustrate how to add a new contract number to the MMIS System, perform

the following:

Navigate to Contracts -> Contract Setup. The Contract Identification Finder

is displayed

Make sure you have your correct assigned End Item selected

Choose the button to view contracts that are already loaded into the

system

Choose the button to add a new contract. The Contract Information

Maintenance window is displayed (Figure 31). Figure 31 is shown after data

has been entered and saved


6-4

Figure 31. Contract Information Maintenance - New Contract

Enter “N00898” in the GSO (Contract Code) text box. This element is also

known as a “DODAAC”

Enter “N00898-6-D-0211” in the Contract Number: text box

Enter “0001” in the Delivery Order Number: text box

Enter “Training System Repairs and Maintenance” in the Contract

Description: text box

Choose the button


6-5

6.2 ADDING CONTRACT LINE ITEM

STEP To add a Contract Line Item (CLIN), perform the following from the Contract

Information Maintenance window (Figure 31):

Choose the button. The ClIN Maintenance window (Figure 32) is

displayed

Figure 32. CLIN Maintenance

Choose the button. The CLIN Detail Information Maintenance

window is displayed (Figure 33). Figure 33 is shown after the data has been

entered


6-6

Figure 33. CLIN Detail Information Maintenance

Enter “1” in the CLIN text box

Select “Repair” from the Type: drop down list

Enter “Repair of Training Systems” in the Description: text box

Choose the button


AsBUILT

CONFIGURATION

SECTION 7

MMIS WORKBOOK SECTION 7 AsBUILT CONFIGURATION

7-3

SECTION 7 AsBUILT CONFIGURATION

7.0 INTRODUCTION

The AsBuilt Configuration system allows users to enter the serialized configuration of a

system. Each AsBuilt therefore has a “Top Level” part number and serial number, and

child records that point to it. Before entering data into the AsBuilt system, the user must

create what is called an AsBuilt Master Template. The AsBuilt Master template is a list

of all the components that are required to be serialized in a system. This template is a

subset of all available parts in the database.

Table

HG

Has All Parts and

Breakdown parts

( could be thousands of

parts)

Table ZABCM

Is a subset of HG.

Only the parts that are

serialized reside here.

ZABCM is a template for

Asbuilt data.

Figure 34. Asbuilt - Table(s) HG and ZABCM


7-4

7.1 CREATING AN AsBUILT MASTER TEMPLATE

STEP To create an AsBuilt Master Template from the Main Menu perform the

following:

Figure 35. Search AsBuilt Master Configurations

Navigate to AsBuilt -> AsBuilt Master Config. The Search AsBuilt Master

Configurations screen is displayed (Figure 35)


Choose the button. The Create New AsBuilt Master Configuration

window is displayed (Figure 36). Figure 36 is shown after the next Query is

performed

Enter the text “%168%” in the Part Number text box

Choose the button. The results of the Query are displayed (Figure

36)

Note: Wild cards are used to speed up the process of lookup up a part number. In this

example, the user is presented with 2 matches on the substring “168”.


7-5

Figure 36. Create New AsBuilt Master Configuration - Query Results

Enter “A” in the Revision text box in the row that has the Part Number

“MC-168119” and ALC of “0”. Choose the icon to the left of that row.

The AsBuilt Master Configuration Maintenance Window (Figure 37) will be

displayed. A Top Level Part Number has now been established


7-6

Note: Checking the “Include Children” check box would create a template for all the

parts that are sub-indentured to the current level. Generally, this will not be a

good idea, as you most likely will not need to serialize every component in a bill

of materials (BOM).

Figure 37. AsBuilt Master Configuration Maintenance - Top Level Part

STEP To add subcomponents at the next indenture level of the AsBuilt Master

Template, perform the following from the AsBuilt Master Configuration

Maintenance window (Figure 37):

Choose the icon next to record with Part Number “MC-168119”. (This

is a Query performed for all available subcomponents located at the next

lower indenture level). The Insert New AsBuilt Master Part window is

displayed (Figure 38)


7-7

Figure 38. Insert New AsBuilt Master Part Window - Partial Query Results.

Enter “A” in the New Part Rev. text box for Part # “ESL749ZF”

Choose the icon to the left of the record

Repeat the above to add Part #’s “MC-DA-0034S”, “MC-CA-99036”, “MC-

FWA-4X44T”and “MC-RWA-7Y56T” using New Part Rev “A” for all

Figure 39. AsBuilt Master Configuration Maintenance - Lower Indenture Added


7-8

At this point your data should reflect Figure 39.

STEP To add subcomponents at the next level of the AsBuilt Master Template, in this

case subcomponents to the Frame Assembly, Part Number “ESL749ZF”, perform

the following from the AsBuilt Master Configuration Maintenance window

(Figure 39):

Choose the icon next to record with Part Number “ESL749ZF” (This is a

Query performed for all available subcomponents located at the next lower

indenture level). The Insert New AsBuilt Master Part window is displayed

(Figure 40)


7-9

Figure 40. Insert New AsBuilt Master Part - Available Subcomponents

From the Insert New AsBuilt Master Part window (Figure 40) add Part #’s

“FSS-749” and “WH-ATB-36”, both with New Part Rev. “A” to the AsBuilt

Master Template (as done in the previous STEP)

When finished adding these subcomponents, your screen should reflect Figure 41


7-10

Figure 41. AsBuilt Master Configuration Maintenance - Subcomponents Added...

Note: These steps will generally need to be done when initializing the MMIS data. If

you have a spreadsheet representation of the template, an MMIS analyst may be

able to assist you in base-lining the system AsBuilt Master Template data.

Info: AsBuilt Master Templates can be created for any level provided that the system

parts hierarchy exists in table HG. Furthermore, if systems are going to be built

at lower levels and then imported into a higher level assembly, an AsBuilt Master

Template can be built for each sub component, and built up in that manner as

well. If you are using part number revisions, multiple revisions of a part number

can be entered into the template, For example, the revisions A, B and C could

have been added for part number ESL749ZF.


7-11

STEP To build an AsBuilt Master Configuration for the subcomponent Part Number

“ESL749ZF” perform the following:

Navigate back to the Search AsBuilt Master Configurations window

Note: From this screen you can query all the AsBuilt Master configurations in the

MMIS system, and edit their attributes if necessary.

Choose the button

The Create New AsBuilt Master Configurtion window is displayed

Enter “ESL%” in the Part Number text box


Figure 42. Create New AsBuilt Master Configuration Window - ESL749ZF displayed..

Enter “A” in the Revision text box

Choose the icon. Figure 43 is displayed


7-12

Figure 43. Top Level Part Information - ESL749ZF displayed

Choose the icon and add the Part Numbers “FSS-749” and “WH-ATB-

36 to the template, using the New Part Rev. “A”

Figure 44. AsBuilt Master Configuration Maintenance - Subcomponents Added...

At this point your data should be as shown in Figure 44.

We have now created a template for a high level assembly, and a lower level assembly.

In a later Section, you will be using these templates to create serialized part

configurations.


7-13

7.2 AsBUILT MASTER REPORTS

There are several reports that can be run from the AsBuilt Master Template finder. Some

of these reports may be exported to MS-Excel for offline use. The following STEPS will

allow you to access the AsBuilt Master Reports menu.

STEP To access the AsBuilt Master Reports menu, perform the following:

Navigate back to the Search AsBuilt Master Configurations finder

Choose the button

Choose the icon on the left side of either Top Level record as shown in

Figure 45. This will activate a menu that displays the report options

(Figure 46)

Figure 45. Search AsBuilt Master Configurations - AsBuilt Master Reports Menu


7-14

Figure 46. AsBuilt Master Reports Menu – Enlarged

7.2.1 Approved Build State Breakdown Report

The ABCM Breakdown Picture is a simple visual aid to view the structure of the AsBuilt

Master Template.


7-15

STEP To access the Approved Build State Breakdown Report, perform the following:

Choose the Report icon on the left side of the Top Level record with Part

Number “MC-168119” as shown Figure 45

As shown in Figure 46, choose ‘ABCM Breakdown Picture”. Figure 47 is

displayed

Figure 47. Approved Build State Breakdown Report - Bicycle Assembly


7-16

7.2.2 AsBuilt Master Config Report

The AsBuilt Master Config Report shows the AsBuilt Master in tabular format. This

report may be exported to MS-Excel.

STEP To access the AsBuilt Master Config Report, perform the following:

As shown in Figure 46, choose ‘Breakdown Report”. Figure 48 is displayed

Figure 48. AsBuilt Master Config Report - MC-168119


7-17

7.2.3 AsBuilt Master History Report

The AsBuilt Master History Report displays all of the changes applied to a particular

template and also the date of those changes. This report may be exported to MS-Excel.

STEP To access the AsBuilt Master History Report, perform the following:

As shown in Figure 46, choose ‘Config History”. Figure 49 is displayed


7-18

Figure 49. AsBuilt Master History Report – Partial


7-19

7.2.4 The AsBuilt Master Config vs HG Report

The AsBuilt Master Config vs HG Report displays all of the alternate part numbers

and/or part numbers that share the same LCN as an LCN in the AsBuilt Master Template.

Figure 50 shows an additional part number at the “BIKE” LCN, and the “BIKE05” LCN

and highlights them in red. This report may be exported to MS-Excel

STEP To access the AsBuilt Master Config vs HG Report, perform the following:

As shown in Figure 46, choose ‘Master VS HG Report”. Figure 50 is

displayed

Figure 50. AsBuilt Master Config vs HG Report – ALCs


7-20

7.3 CREATING AN AsBUILT CONFIGURATION

As mentioned, the AsBUILT is the serialized configuration of a system. In this section

you will use the templates created previously to create an AsBuilt Configuration.

STEP To illustrate how to create an AsBuilt Configuration, perform the following from

the Main Menu as described below:

Navigate to: AsBuilts -> AsBuilt Config. The Search AsBuilt Configurations

window is displayed (Figure 51)

Figure 51. Search AsBuilt Configurations

Note: Using this finder you can query by top-level part number / serial number or child

part number / serial number. However, only the top level part for each

configuration will be displayed in the finder results.


7-21


Choose the button. The Create New AsBuilt Configuration window is

displayed


Choose the button. Here you should see the AsBuilt Master

templates that are available to create an AsBuilt Configuration from (Figure

52)

Figure 52. Create New AsBuilt Configuration - Query Results

Enter the serial number “TZH1000” in the New Serial Number text box for

the record that has Part Number “ESL749F”, Part Revision “A” as shown

in Figure 53


7-22

Figure 53. Create New AsBuilt Configuration - New Serial #

Choose the icon. This will save the top level part number and serial

number to the database. Figure 54 is displayed

Figure 54. AsBuilt vs AsBuilt Master Compare - Before Save

Note: The template that you created in the last section is being used to display the

components that need to be serialized, as well as the revisions.


7-23

Enter “T500” and “T600” into the first and second available SN: text boxes

displayed in Figure 54. Here you are entering the serial numbers of the child

parts for the system that you are serializing

Choose the button. Figure 55 is displayed. This will save both

records to the database. The database table that is being updated is called

ZABC

Note: Once you have saved the configuration, it will become available to be consumed

by a higher level AsBuilt configuration. Also, as shown in Figure 55 the red text

that identifies each part is now black, indicating that the required part number has

been serialized.

Figure 55. AsBuilt vs AsBuilt Master Compare - After Save

The next STEP will illustrate how to create a higher level serialized assembly that will

enable us to import the assembly just created as a sub-assembly.


7-24

STEP To illustrate how to create a higher level assembly AsBuilt Configuration,

perform the following as described below:

Navigate back to the Search AsBuilt Configurations window (Figure 51)

Choose the button. Figure 56 is displayed with the AsBuilt record

that was created in the previous STEP shown

Figure 56. Search AsBuilt Configurations - Query Results

Choose the button. The Create New AsBuilt Configuration window is

displayed

Enter “MC-168119” in the Part Number text box and “A” into the Part

Revision text box. This will limit the number of records returned when we

query


7-25

Choose the button. Enter “TOPLEVEL1” in the New Serial

Number text box for the record returned as shown in Figure 57

Figure 57. Create New AsBuilt Configuration - New Serial Number

Choose the icon. Figure 58 is displayed


7-26

Figure 58. AsBuilt vs AsBuilt Master Compare - Before Import

In the Top Level Part Information area, choose the Icon (Import Button).

Figure 59 is displayed


7-27

Figure 59. Import Existing AsBuilt Configuration - LCN BIKE01


7-28

Choose the icon to import the subassembly. Figure 60 is displayed.

Note: Now that the subassembly has been imported (in black), it is no longer

its own AsBuilt and it has been consumed by the next higher assembly

Figure 60. AsBuilt vs AsBuilt Master Compare - After Import

Enter Serial Numbers ‘TZH1001”, “TZH1002”, “TZH1003”, “TZH1004” in

the sibling components SN: text boxes as shown in Figure 61


7-29

Figure 61. AsBuilt vs AsBuilt Master Compare - Sibling Serial Numbers



7-30

Figure 62. AsBuilt vs AsBuilt Master Compare - Subassemblies Added

Again, once complete each line that describes a Part # / SN: will change from red text to

black text. At this point all eight of the parts above have been added to table ZABC.

Info: When data is inserted into this table a unique identifier is created for the top level

component called a config -id. This is a globally unique value assigned to each

part within a given AsBuilt. Although the configid is not displayed on this

screen, it does reside in the ZABC table, and is used behind the scenes by MMIS

for many purposes.


7-31

7.4 RELEASING AN AsBUILT CONFIGURATION

When an AsBuilt configuration is released, essentially the entire assembly is being

“locked down” so that it cannot be modified. Furthermore, when it is released, it also

“baselines” or “backfills” many different areas of MMIS, such as serialized inventory,

which is used to track the geographic location of a unit, and FRACAS, which is used to

create defect part and corrective action reports for failed units (Error! Reference source

ot found.).

STEP To illustrate how to release an AsBuilt Configuration, perform the following:

Navigate to AsBuilts -> AsBuilt Config. The Search AsBuilt Configurations

window is displayed

Enter “TOP%” in the Top Serial Number finder box


Figure 63. Search AsBuilt Configurations - TOP% Query results

Choose the Release AsBuilt to AsMaintained icon

The AsBuilt Configuration Maintenance window is displayed (Figure 64)


7-32

Figure 64. AsBuilt Configuration Maintenance - Confirm Release

Info: On the next page, Figure 65 is shown as a reference for the process involved and

the Flowdown of the Create AsBuilt Master thru the Release AsBuilt to

AsMaintained Configuration system.


7-33

Create AsBuilt Master

Template

Create AsBuilt Configuration

Release AsBuilt

Configuration

Creates AsMaintained

Configuration

Baseline

Creates Serialized Inventory

Records

Create FRACAS System

Records

FRACAS Defect ReportsTRAVELER

Records

AsMaintained Configuration

Changes

Figure 65. AsBuilt Configuration Release - Flow down


7-34

Choose the button as shown

in Figure 64. Figure 66 is displayed. Figure 66 is shown with “Ready for

Issue” selected

Figure 66. Select CAVS, Contract and Location Information - RFI Selected

Select “Ready For Issue” from the CAVS Code: drop down list


7-35

Info: CAVS Code designates the status of the item. In our test case, the unit will be

designated as “Ready for Issue”. If we choose to pick a CAVS code for the unit,

the status will flow down to the each sub-assembly of the unit.

Select “N00898” as the GSO (Contract Code) from the drop down list in

the Choose Contract section

Info: The Contract information exists in a table that is maintained in the Contracts area

of MMIS. The application will display all contracts applicable to the end item

we are currently working with. This information is entered through the Contracts

-> Contract Setup function (SECTION 6).

In the Choose Location section of the window, choose the drop down option

“GO H3”

Info: This Location Information will also flow down the AsBuilt configuration and set

the geographic location of the component to that of the top level parent part.

Sites and locations reside in database tables in MMIS that are maintained by

navigating to: Inventory Management->Site Maintenance or Inventory

Management->Location Maintenance or Inventory Management->Bin

Maintenance. Creating and modifying these locations is covered in the Inventory

Management section.


7-36

Choose the button

When this button is pressed many actions are performed. If a FRACAS System record

does not exist for each serialized part in the configuration, it will be created. If serialized

part inventory information does not exist for the serialized configuration, it will be

created. Furthermore, when the serialized part inventory location gets created, it will

move all sub-assemblies of the part to the same location of the parent. In addition, it will

set the “consumed” flag of those sub-assemblies to “Consumed”, and it will set the top

level consumed flag to “Not Consumed”. If a user tries to change the geographic location

of a part that is consumed, he or she will be informed that the part exists inside of another

part, and will need to be removed before it can be moved.

Upon returning to the Search AsBuilt Configurations screen (Figure 67):

Choose the button


7-37

Figure 67. Search AsBuilt Configurations - Green Light

Notice that the wrench icon next to the record has been replaced with a “green light”

icon. This icon indicates that the AsBuilt is complete, and that the configuration is now

released to the AsMaintained Discipline (SECTION 8).

If the AsMaintained Configuration of this item were to change in the future, the green

light icon will change color, indicating that the AsMaintained configuration no longer

matches the AsBuilt configuration.


7-38


AsMAINTAINED

CONFIGURATION

SECTION 8

MMIS WORKBOOK SECTION 8 AsMAINTAINED CONFIGURATION

8-3

SECTION 8 AsMAINTAINED CONFIGURATION

8.0 INTRODUCTION

After an AsBuilt system is released, a copy of the entire system is created in table

ZAMC, the AsMaintained configuration table. From the point that the Asbuilt is

released, all configuration changes will be done in the AsMaintained system. The

difference between AsBuilt and AsMaintained is that the AsBuilt records the system

configuration at the point it was initially entered, and AsMaintained contains the current

configuration as it changes over time.

8.1 REMOVING AN ASSEMBLY

Conceptually, removing an assembly is like deleting or moving a windows file folder

from one directory to another. When an assembly is removed, all of its sub-indentured

parts are removed as well. For example, if we were removing an engine from a truck, we

are also removing the engine’s cylinder heads, intake manifold, pistons, etc, from the

truck.

STEP To prepare to remove a component from the AsMaintained system, perform the

following:

Navigate to AsBuilts -> AsMaintained Configuration. The Search

AsMaintained Configurations window is displayed (Figure 68). Figure 68 is

shown after the next Query.


8-4

Make sure the correct BICYCLEXX end item assigned by the EAGLE

instructor is selected


Figure 68. Search AsMaintained Configurations - Query Results

The Search AsMaintained Configurations finder is used like other Data Finders. Note the

various icons to the left of the returned record.

Choose the icon. The AsMaintained vs AsBuilt Compare screen is



8-5

Figure 69. AsMaintained vs AsBuilt Compare - Unchanged

Since we have not modified the AsMaintained Configuration, there are no differences

highlighted between the AsBuilt and AsMaintained. However, after a change is made,

the modified part number will change color. The screen provides a COLOR KEY (Figure

70), explaining what each of the four colors mean.

Figure 70. AsMaintained vs AsBuilt Compare - Color Key Expanded


8-6

STEP To remove an assembly from an AsMaintained configuration, perform the

following as shown in (Figure 69) and described below:

Choose the icon (Remove Subassembly) to the right of the record with

NAME: “FRAME ASSEMBLY” ... PART#: “ESL749ZF”. The

AsMaintained Remove Part Window is displayed (Figure 71)

Figure 71. Remove Part – Part Information - TZH1000.

Change the CAVS Code: from “Ready For Issue” to “In Repair”

Choose the button to confirm removal of the assembly.


8-7

Info: Since you are removing an assembly that is at a particular location, status, and on

a particular contract, MMIS will ask you if you want to change any of these

values when the assembly is removed. By default, the values of the parent are

used, but you may change them at this point, or at a later point in time

Figure 72. AsMaintained vs AsBuilt Compare - Subassembly Removed (Red)

Note: The subassembly that was removed is shown in Red. This indicates that it is no

longer part of the MC-168119 / TOPLEVEL1 assembly.


8-8

8.2 AsMAINTAINED CONFIGURATION REPORTS

STEP To display the various AsMaintained Configuration Reports, perform the

following as shown in Figure 73 and described below. It is assumed the previous

STEP has been performed and the AsMaintained vs AsBuilt compare screen is as

shown in Figure 72:

Choose the icon to the left of the Top Level Part record (Figure 73)

Select the “Part Number Absences” Report. Figure 74 is displayed

Figure 73. AsMaintained vs AsBuilt Compare - Report Dropdown


8-9

Figure 74. AsMaintained / AsBuilt Master Part Number Absences Report – Example

8.3 IMPORTING AN ASSEMBLY

Importing an assembly in the AsMaintained system is similar to importing an assembly in

the AsBuilt system. In this Section, you will be importing the assembly that you

removed in the previous section.

STEP Return to the Search AsMaintained Configurations finder and query for all

records. You will notice that the subassembly that was removed above is now its

own configuration, and its status is In Repair (Figure 75)


8-10

Figure 75. Search AsMaintained Configurations - Sub Assembly removed

NOTE: In between the double bars in Figure 75, are a few more columns.

STEP To import the assembly that we removed in Section 8.1, perform the following

from the Search AsMaintained Configurations window:

Choose the icon on the left side of the Serial Number “TOPLEVEL1”

Record. The AsMaintained vs AsBuilt Compare window is displayed

(Figure 76). Note the text for the sub assembly is in red


8-11

Figure 76. AsMaintained vs AsBuilt Compare - Sub Assembly Removed

Choose the icon to the right of the record with NAME: “FRAME

ASSEMBLY”, PART# “ESL749ZF”. Then select

The Import Existing AsMaintained Configuration window is displayed

(Figure 77)


8-12

Figure 77. Import Existing AsMaintained Configuration - Frame Assembly

Info: The records that are displayed on this screen (Figure 77) are the standalone units

that exist in the AsMaintained system, at same level as the record selected in

Figure 76, and are compliant with the AsBuilt Master template. When you select

a record here, the entire assembly will be imported, and will no longer be a

standalone system (it will be consumed). To understand this conceptually,

assume that you have removed a radar system from a higher level assembly for

repair. If you had many serialized radar systems ready for issue, you would need

to choose one. That is what we will do next.

Choose the icon to import the “ESL749ZF” assembly. The

AsMaintained vs AsBuilt Compare window is re-displayed (Figure 78)


8-13

Figure 78. AsMaintained vs AsBuilt Compare - Assembly Imported

Note that the assembly has been imported and that the text has changed from red to black.

STEP To view AsMaintained Configurations, perform the following:

Return to the Search AsMaintained Configurations finder and query for all

records. Notice that the subassembly that was imported no longer shows up

because it is now in another assembly––


8-14

Choose the icon to the left of the record that is displayed. The

AsMaintained Break Down Report is displayed (Figure 79)

Figure 79. AsMaintained Break Down Report - Current Configuration (3 of 3)…

This report shows all of the configurations of the top level assembly throughout its

lifetime. Pressing the will take you to a previous configuration of the system

(Figure 80).


8-15

Figure 80. AsMaintained Break Down Report - Previous Configuration (1 of 3)...

Return to the Search AsMaintained Configurations finder and query for all

records. Again, notice that the subassembly that was imported is no longer

displayed because it is again in another assembly

Choose the icon to the left of the record that is displayed. The

AsMaintained Configurations window is displayed (Figure 81). This

window displays the current configuration and the previous configuration

side by side


8-16

Figure 81. AsMaintained Configurations - Snapshots


INVENTORY

MANAGEMENT

SECTION 9

MMIS WORKBOOK SECTION 9 INVENTORY MANAGEMENT

9-3

SECTION 9 INVENTORY MANAGEMENT

9.0 INTRODUCTION

The Inventory Management discipline within MMIS can work with or without using the

AsBuilt system in MMIS. However, if you are using the AsBuilt system, it is generally a

good idea to start with an AsBuilt, and release the AsBuilt into inventory, provided that

the data is available. In this section we will briefly describe some of the functions within

the Inventory Management, using the AsBuilt records created in the previous sections.

9.1 CREATING SITE DATA

This section will guide you through the process of adding “Site” information to MMIS.

The meaning of what constitutes a “SITE” should be discussed by the parties involved in

entering data into the system, but typically it is a code that is used to identify a

geographic location, at a high level. This code can therefore be thought of as a shorthand

“alias” for a location. For example, AZ could be used to designate a site in Arizona, GO

could be used to identify a repair site in Goleta California, or UT could be utilized for a

Site in Utah.

Note: These Site Codes can be bulk loaded as well if needed using EAGLE.

STEP To create Site Data, perform the following:

Navigate to: Inventory Management -> Site Maint. The Site Identification

Information Finder is displayed (Figure 82).


9-4

From this finder, you can query for site information, delete site information,

or insert new site information.

Figure 82. Site Identification Information Finder


Chose the button. Figure 83 is displayed with returned records

Figure 83. Site Identification Information Finder - Query Results

Choose the button. The Site Identification Information Maintenance

window is displayed (Figure 84). Figure 84 is shown after the following data

has been entered and saved


9-5

Figure 84. Site Identification Information Maintenance - TB saved

Enter “TB” in the Site Code text box

Enter “Tubac Repair Facility” in the Site Description: text box

Enter “2931 W Hollister” in the Site Address 1: text box

Enter “Tubac” in the Site City Name: text box

Enter “AZ” in the Site State/Province: text box

Select “United States” from the Site Country Code: drop down list

Select “Commercial” from the Agency: drop down list

Choose the button. (Figure 84)


9-6

STEP As a Self Test, perform the following:

Add the Site Code “SA”, with the Site Description: “South Australia

Depots”, to MMIS

Add the Site Code “KP”, with the Site Description: “Keyport”, to MMIS

Delete the Site Code “KP” from MMIS


9-7

9.2 CREATING LOCATION DATA

Each Site that is entered into MMIS can have none, one, or many locations. For example,

a location could be a building or room at a repair facility.

STEP To create Location Data, perform the following:

Navigate to: Inventory Management -> Site Maint. (Figure 82).

Choose the site code “SA”

Choose the tab in the middle of the Site Maintenance Screen

(Figure 84).

Choose the button. (Figure 85) is displayed.

Enter “ADELAIDE ADF BLDG 20” in the Location text box

Enter “ADELAIDE ADF BLDG 20 Repair Depot” in the Location

Description: text box

Choose the button


9-8

Figure 85. Location Identification Maintenance with data entered

Figure 86. Site Maintenance – Post Save

Note: If the previous Self Test was NOT performed, this record will not be returned.


9-9


Add “ADELAIDE ADF BLG 30” as a new Location to the “SA” site with

Location Description: “Aux Repair Depot”

9.2.1 Viewing Location Data

To view the location information that is in the database, you can use the Location

Identification Information Finder.

For example, if you wanted to see all locations at the “SA” Site, you would navigate to:

Inventory Management -> Location Maint then enter your search criteria in the query

parameter text boxes, and choose the query button.

9.3 CHANGING THE LOCATION OF A SERIALIZED PART

Changing the location of a serialized part can be done directly from the Serialized Part

Information Finder.

STEP To illustrate how to change the location of a serialized part, perform the

following:

Navigate to Inventory Management -> Serialized Inventory. The Serialized

Inventory Finder is displayed (Figure 87)


9-10

Figure 87. Serialized Inventory Finder

At this point you may enter the serial number, and/or part number of the part in the query

parameters text boxes.


Enter “TOP%” in the Serial Number text box

Choose the button. The Serialized Inventory Finder is displayed

with the Query results (Figure 88)


9-11

Figure 88. Serialized Inventory Finder - Query Results


9-12

At this point, the user can change the part location by clicking on the site and location

column dropdowns.

Figure 89. Change Location - Save Changes

Use the Site Code and Location drop down list to change the Location to

“SA, Adelaide ADF Building 20”

Choose the button. On the Serialized Inventory Finder, “SA” should be

displayed in the Site Code text box and “Adelaide ADF Building 20” should

be displayed in the Location text box

9.3.1 Viewing Serialized Part Location History

Each time a part changes its associated status, contract, or location, a record is created in

a history table that shows where the part moved from, and what date it was moved.

To get to the screen to view the history data for a particular part, choose the icon on

the Serialized Inventory Finder on the row for which you wish to view the history.


9-13


Change the location of the “TOPLEVEL1” serial number assembly to 3

different locations. Make sure to return the asset to the “SA” Site when

finished as shown in Figure 90

View the serialized part history for the “TOPLEVEL1” serial number

assembly to see where it has been moved

Example output is shown in Figure 90. The current location will always be at the bottom

of the screen, and the oldest will be at the top.

Figure 90. Serialized Inventory History - History Results


9-14

9.4 Attaching an Engineering Change Proposal (ECP) to a Serialized Part

Although the Engineering Change Proposal (ECP) Area exists outside of the Inventory

Management Discipline, we will discuss it here briefly to let the user know how it relates

to Serialized Inventory.

STEP To illustrate how to associate a Serialized Part with an ECP, perform the

following from the Main Menu:

Navigate to: Configuration Management -> Engineering Change Proposals.

The ECP Finder will be displayed

Make sure you have your correct assigned End Item selected

Choose the button to view all ECPs for your End Item (Figure 91)

Figure 91. ECP Finder - Query Results

For the record with ECPTitle “MMIS DEMO ECP” displayed, choose the

ECP Number hyperlink (blue) to display the ECP Details screen (Figure 92)


9-15

Figure 92. ECP Details

Choose the button at the top of the screen. The Ref. Data



9-16

Figure 93. Ref. Data - ECP Information

Choose the button at the top of the screen. The

Select Serial Inventory window is displayed (Figure 94)


9-17

Figure 94. Select Serial Inventory

Enter “TOP%” into the Serial Number text box

Choose the button. One record should be returned (Figure 95)

Figure 95. Select Serial Inventory - TOP% Query Results

Check the Check Box next to the “TOPLEVEL1” record

Choose the button. The Ref. Data window is redisplayed with the

associated Serialized Inventory (Figure 96)


9-18

Figure 96. Ref. Data - Serialized Inventory Added

On the Ref Data screen (Figure 96), you see that the serialized part you added to this ECP

is displayed, and that it’s Incorporated Flag is set to “NO” and Incorporated Date is

blank. This means that the ECP needs to be completed on this unit. The NOTE: in blue is

reminding you to choose the icon.

Choose the icon

When we create a “Traveler” for this unit, the outstanding ECP information related to this

record will be displayed. The Traveler System is introduced in SECTION 11


FRACAS SYSTEM

SECTION 10

MMIS WORKBOOK SECTION 10 FRACAS SYSTEM

10-3

SECTION 10 FRACAS SYSTEM

10.0 INTRODUCTION

The Failure Reporting and Corrective Action System (FRACAS) in MMIS allows users

to create FRACAS defect reports, identify defective parts, and store corrective action

information related to those defects.

10.1 ADDING A FRACAS SYSTEM RECORD

STEP To create a new FRACAS System record in MMIS, perform the following:

Navigate to FRACAS -> FRACAS System. The FRACAS System Assembly

Finder is displayed.

Make sure your correct End Item is selected.

Choose the button. The Insert FRACAS System finder is displayed

Enter “BIKE” in the LCN text box

Choose the button.

Choose the button next to the record with LCN of BIKE and ALC of 00

Enter “TOPLEVEL1” in the Serial Number text box.


10-4

Choose the customer number “98765” from the Customer dropdown.

Choose the button.

10.2 CREATING A FRACAS DEFECT REPORT

STEP To create a new FRACAS defect report using MMIS, perform the following:

Navigate to: FRACAS -> FRACAS Defects. The FRACAS Defects

Information Finder is displayed


Choose the button. The Create New FRACAS Defect screen is

displayed

Enter TOP% in the Serial Number text box


Choose the icon. The FRACAS Defects Maintenance Screen is displayed

(Figure 98, Figure 99)


10-5

Figure 97. Create New FRACAS Defect - Query Results”

Figure 98. FRACAS Defects Maintenance Screen (Upper) - Defect Number


10-6

Info: Note that the Defect Number is auto-generated by the system. The Report

Number and Failure Event Id fields are both blank, and need to be filled out

before saving. The format of these values is up to the user, and if the FRACAS

report is generated from a Traveler record, by default the work order number of

the Traveler is used as the Failure Event ID. Typically, the Failure Event ID is

used to group failure reports together. For example, when one unit fails, there

may be more than one reason for the failure. Therefore, each reason may be

investigated and grouped together using this field.

Figure 99. FRACAS Defects Maintenance Screen (Lower)


10-7

Enter “MMIS-87” as the Report Number and as the Failure Event Id:

Select “Operation Critical” from the Defect Classification: drop down list

Select ‘Confirmed Failure” from the Defect Type: drop down list

Leave the Report Status: as “Open”

Select “Production Reliability Acceptance Test” from the Program Phase:

drop down list

Select “VIBRATION FAILURE” from the Failure Mode: drop down list

Choose the button

10.3 ADDING DEFECTIVE PART INFORMATION

STEP To add defective part information, perform the following from the FRACAS

Defects Maintenance page:

Choose the Defective & Replacement Parts button at the top of the page.

The Defective & Replacement Parts window is displayed (Figure 100)


10-8

Figure 100. Defective & Replacement Parts window

Choose the “Select Serialized Defective Part” button. Figure 101 is

displayed


10-9

Figure 101. Select Serialized Defective Part window

Choose the icon next to the record with Part # “MC-CA-99036, SN:

TZH1002”. Figure 102 is displayed

Choose the button

Figure 102 shows that the part you have selected has been identified as the defective part

for this FRACAS defect report. If the defect occurred at a lower, un-serialized part level,

you could choose to use the BOM Defect. Part List option. This will drill down through

the complete bill of materials, rather than the AsMaintained configuration of the unit.


10-10

Figure 102. Defective & Replacement Parts window - Data Entered

Selecting the defective part in this manner can be used to identify problems with a

particular part number, or even serial number, over time.


10-11

10.4 EDITING CORRECTIVE ACTION INFORMATION

STEP To edit Corrective Action information, perform the following:

From the Defective & Replacement Parts window (Figure 102), choose the

button. The FRACAS Defects Maintenance screen is displayed

(Figure 103)

Figure 103. FRACAS Defects Maintenance


10-12

Choose the button at the top of the screen. The Corrective

Action window is displayed (Figure 104). Figure 104 is shown with data

entered

Figure 104. Corrective Action window - Data Entered

Select “Workmanship-Vendor” from the Root Cause: drop down list

Select “Supplier - Mfg” from the C/A Code: drop down list

Enter “Waiting on Vendor” into the Root Cause Narrative: field


10-13

Choose the button. This will insert a record into the table

ZFRACAS1COMP

Info: Many narrative fields exist on this screen that are used to capture the root cause

and related information, and can accept up to 4000 characters of text. Keep in

mind, that if you use AdHoc Queries (SECTION 15) to find data records, you

can use wild cards before and after a string to search for text.

10.5 FIELD FRACAS

The Field FRACAS Return (FFR) was designed to allow field reps (who might be located

on a ship) to enter some basic information about a failure for the workers at the Depot.

10.5.1 Using the Field FRACAS Return (FFR) Wizard

Note: This results in a FRACAS record being created.


10-14

Figure 105. Main Menu - FFR Wizard

STEP To utilize the FFR Wizard perform the following from the Main Menu:

Navigate to FRACAS -> FFR Wizard (Figure 105)

Select your assigned End Item

Choose the button

Select “South Australia Depots” from the Select a Site list

Choose the button


10-15

Figure 106. FFR Wizard - Select a Squadron

At the Select a Squadron screen, we have three options: 1. Select a known squadron from

the list, 2. Type in a new squadron, or 3. Skip squadron selection. For this example, we

will type today’s date into the textbox, in the format DDMMYY.

Enter today’s date in data field to the right of the USE This Squadron -->

button. The format is DDMMYY (Figure 106). Choose the USE This

Squadron --> button

At the Select a Part Number screen (Figure 107), if no Serialized Inventory data exists for

the Site, then we would have to type in a new Part Number, then select it and click the

button, or type it into the textbox and click on the


10-16

button. In this case, we have Part Numbers to choose

from.

Note: If no part numbers are displayed, make sure in the Self Test, (9.3.1) you returned

your Serialized Inventory to Site Code “SA”.

Figure 107. FFR Wizard - Select a Part Number

Choose Part Number “MC-168119” from the list as shown in Figure 107

Choose the button


10-17

Figure 108. FFR Wizard - Select a Serial Number

If the Serial Number we wanted did not exist in the dropdown, we could type

“TOPLEVEL1” into the Serial textbox and choose the icon (Figure 108).


10-18

Choose Serial #: “TOPLEVEL1” from the Select a Serial Number list as

shown in Figure 108

Choose the button

Figure 109. FFR Wizard - Select a Customer

Choose “SAS - GOLETA (98765)” from the list as shown Figure 109



10-19

Figure 110. FFR Wizard - FFR Main

Note: At this point your window should reflect Figure 110. All of your selections, as

well as a few other fields should be displayed. If any FFR/FRACAS records

already exist for this part, they will show up under the “Current FFR’s” section.

In this case FFR/Defect Number 166 is shown.

STEP At this point NO records have been created! To create the FFR record, perform

the following:

Choose the button

Enter “Part failed for unknown reason.” (no quotes) into the Failure

Description (4,000 character limit): text box

Choose the button. This will be return you to the same screen for

further editing of this record, if necessary


10-20

At this point, the FFR entry is complete.

Choose the button to see the record that was created. You may

choose the icon to edit the record again

10.5.2 Finding and Editing an Existing Record in the Field FRACAS

STEP To Edit an existing record in the Field FRACAS perform the following:

Navigate to FRACAS -> Field FRACAS. Figure 111 is displayed

Figure 111. Field FRACAS Defects Information Finder


10-21

Make sure that your correct End Item is selected

Note: When there are many records in the FRACAS System, the page return can

become slow. To limit the number of records, use the query fields on the Finder

screen if necessary


Figure 112. Field FRACAS Defects - Query Results

Choose the Part Number “MC-168119”, (which is a hyperlink to the Edit

screen) with TFR Number “MMIS-87”. The FRACAS Defects

Maintenance window is displayed (Figure 113 and Figure 114)


10-22

Figure 113. FRACAS Defects Maintenance

In the Main Information Section of the page (Figure 114), select “Under

Review” from the Status: drop down list

Choose the Save Main Information button


10-23

Figure 114. FRACAS Defects Maintenance - Part Information

Info: All fields are edited in a similar way. The page is broken up into several sections

(Scroll Down). Each section has its own Save button. So that data is not lost, it

is recommended that you save each section as you go. It is also recommended

that you save a section before clicking on any other button in the same section, as

some buttons take you to other screens.


10-24

10.5.3 Creating a New Record in the Field FRACAS

STEP To add a new record in the Field FRACAS, perform the following:

Navigate to FRACAS -> Field FRACAS. The Field FRACAS Defects



Choose the button. The Create New FRACAS Defect window is

displayed

Enter “MC%” into the Part Number field

Choose the button

Locate the part that has Serial Number “TOPLEVEL1”

Choose the icon. Figure 115 is displayed. At this point, the record is

created and you may add details to the record at this time.


10-25

Figure 115. FRACAS Defects Maintenance - TOPLEVEL1

10.5.4 Deleting a Record from the Field FRACAS

STEP To delete a record from the Field FRACAS, perform the following:

Navigate to: FRACAS -> Field FRACAS. The Field FRACAS Defects


Enter “MC%” into the Part Number field

Choose the button


10-26

Info: The Defect Number (“Defect No.” on the Finder screen) is not guaranteed to be

unique, but in general it is unique. If you know the Defect Number, enter that as

a query parameter to quickly find your record.

Locate the part that you want to delete in the Query Results (Figure 116)

Choose the icon that corresponds to the third record TFR Number “2”.

Figure 117 is displayed

Figure 116. Field FRACAS Defects - Query Results

Figure 117. FRACAS Defects Maintenance - Confirm Delete

Choose the button to confirm the delete when prompted


TRAVELER SYSTEM

SECTION 11

MMIS WORKBOOK SECTION 11 TRAVELER SYSTEM

11-3

SECTION 11 TRAVELER SYSTEM

11.0 INTRODUCTION

The Traveler System is a work order system that allows serialized parts to be put on

routes that consist of operations that occur at particular locations. This section will guide

the user through creating operations, creating routes, and adding operations to routes. In

addition it will show the user how to add routes to a traveler, and close the operations in

those routes.

11.1 CREATING AN OPERATION

An operation can be thought of as a step or a procedure. This section will show the user

how to create an operation. These operations will later be grouped into sets called routes.

STEP To illustrate how to use the Traveler System, specifically how to create an

Operation perform the following from the Main Menu:

Navigate to: Workflow -> Operations Maint. Figure 118 is displayed


11-4

Figure 118. Part Routing Operations Information Finder

Make sure the End Item assigned by the EAGLE instructor is selected

Choose the button. The Part Routing Operations Information

Maintenance window is displayed (Figure 119). Figure 119 is shown with

data entered


11-5

Figure 119. Part Routing Operations Information Maintenance - Before Save

Enter “991” into the Operation Num text box

Enter “Test 1874AS5310 per TSTP 182.89” in the Description text box

Select “Generic” from the Operation Type drop down list

Select “No” from the Quality Check: drop down list

Enter “1” in the Standard Hours: text box

Choose the button


11-6

At this point, you have created an operation that can now be added to a route. If you

wanted to add additional operations, you would repeat the STEP above, making sure to

use a distinct operation number each time. Once all of your operations have been added,

they should only need to be updated occasionally. Advanced users may choose to “tag”

the operation by choosing the “Create” button. This allows HTML tags to be placed

around parts of the description.


11-7

11.2 CREATING A ROUTE

In this next STEP we are going to create a route and add the operation created previously

to the route. A route can consist of one or many operations, at a particular location.

Think of a route as a path for operations to be performed.

STEP To illustrate how to create a route and add an operation to it, perform the

following:

Navigate to: Workflow -> Route Maint. The Depot Route Information

Finder is displayed (Figure 120)

Figure 120. Depot Route Information Finder


11-8

Choose the button. A blank record is returned for edit (Figure 121)

Enter “Demo Route” in the Route Id text box

Enter “-“ in the Rev. (Route Revision) text box

Enter “Demo Route” in the Route Description text box

Select “Repair” from the Route Type drop down list

Choose the button.is displayed. Note the additional icons to the left,

in the middle and to the right of the saved record


11-9

Figure 121. Depot Route Information Finder - New Record

Figure 122. Depot Route Information Finder - New Record Saved

Now that the route has been saved, we are able to add an operation or set of operations to

the route.

Choose the “Route Operations” tab. The Routing Operation Information

Maintenance window is displayed (Figure 123)


11-10

Figure 123. Routing Operation Information Maintenance - Site Added

In the Attach Operations to Route: section of the window, select “SA”

from the Site drop down list. This is the Site where this operation will be

completed

Select “ADELAIDE ADF BUILDING 20” from the Location drop down list

In the Operations Finder section of the window (the mini-finder), enter

“991” into the Operation Number field

Choose the button. The results of the query are displayed in the

bottom section of the window (Figure 124)


11-11

Figure 124. Routing Operation Information Maintenance - Find Operation

Choose the icon to add the Operation to the Route. Figure 125 is

displayed

Press the button.


11-12

Figure 125. Routing Operation Information Maintenance - Operation Added…..

The Operation will now be shown at the top of the screen in the Attached

Operations section of the window (Figure 125)

At this point you could add more operations to the route using the same process as above.

Also, if you are revising a route, but wish to keep a version of the old route, you can

“clone” a route.


11-13

11.2.1 Cloning a Route

STEP To ‘clone’ a route, perform the following from the Depot Route Information

Finder as shown in Figure 125 and as described below:

Navigate to Workflow -> Route Maint


Figure 126. Depot Route Information Finder - Query Results

Choose the (Clone Record) icon to the left of the record with Route Id

“DEMO ROUTE”. The Clone Depot Route window is displayed (Figure

127)


11-14

Figure 127. Clone Depot Route - Rev. 1

In the “Clone Route Information:” section, enter “1” in the Rev. text box as

shown

Choose the button. The Depot Route Information Finder is

redisplayed with the updated route information


11-15

Figure 128. Depot Route Information Finder - Rev. 1 Added

11.3 CREATING A TRAVELER

Now that we have created an operation, and attached it to a route, we can now create a

Traveler (or work order). The Traveler generates a unique identifier that is used to track

the progress of work being completed on a particular serialized unit. The traveler is

tracked by end item, cage code, part number, serial number and sptnum (originally spare

part tracking number, but now used as a work order number). In order for a Traveler to

be created, the end item, cage code, part number and serial number must first exist in the

serialized inventory table (ZHAEXTSN).

STEP To create a Traveler perform the following from the Main Menu as described:

Navigate to: Workflow -> Travelers. The Traveler Identification Information

Finder is displayed (Figure 129)


11-16

Figure 129. Traveler Identification Information Finder


Choose the button. The Part Number/Serial/Number Search window is


Figure 130. Part Number/Serial/Number Search - Query Results

Enter “TOP%” in the Serial Number text box

Choose the button

Since only one record would be returned, the browser should automatically

continue to the “Create MMIS Tracking Number” Window (Figure 131)

If not, choose the icon next to the record.


11-17

Figure 131. Create MMIS Tracking Number – Data Entered

Select “SA - South Australian Depots” from the Location Site: drop down

list

Select “TST” from the Program: drop down list

Choose the button

Wait while the Traveler updates its background information. At this point, a record has

been inserted into table ZTRAVELER. In addition, depending on your MMIS

configuration, a record may have been initialized in the FRACAS system. Figure 132

should be displayed.


11-18

Figure 132. Traveler Identification Information Maintenance


11-19

Once the Traveler has saved, the user is presented with many options, such as selecting a

contract number, entering receiving carrier information, adding bill of lading information,

changing the location of the asset, etc.

If there are outstanding ECPS open for this Traveler, they will be displayed on this screen

as well. Figure 133 shows the ECPs section expanded.

Figure 133. ECPs Section – Expanded

In addition to the above data elements, the user can enter discrepancy and disposition

information on this screen (Figure 134). This information is fed back into the FRACAS

system, where it can be grouped and analyzed accordingly.


11-20

Figure 134. FRACAS Defects Section - Expanded

The options (in blue) are links to the detailed information related to the FRACAS record

that gets populated for each discrepancy (Figure 134).

Selecting the “Edit” hyperlink will take the user to the FRACAS Maintenance screen.

Selecting the “MAF Info” link will take the user to a screen where they can enter MAF

data such as MAF Squadron and MAF BUNO number. (MAF stands for Maintenance

Action Form- it is used by the US Navy).

Selecting the “FRACAS Defect Part” link will take the user to a screen where they can

identify the defective part in the system, update AsMaintained Configuration, and if

needed, create a “Child Traveler” that will be attached to the current Traveler, and

possibly routed to a different site, and location for further trouble shooting or repair


11-21

11.4 ADDING A ROUTE TO A TRAVELER

STEP To add a route to a Traveler, perform the following:

From the Traveler Identification Information Maintenance window (Figure

132), choose the button. The Traveler Route Maintenance


Figure 135. Traveler Route Maintenance


11-22

Note: The attached ECP shows up on this screen as it did in Figure 132. If a route were

attached to the ECP the user could add the attached route from this screen. Note

also, that by choosing the icon next to the ECP, you will be taken to the ECP

Details screen. The ECP Details screen will open in a new browser window.

Close the ECP Details screen, if open and return to the Traveler Route

Maintenance window

Choose the button. The Route Selection window is displayed.

Figure 136 shows the “Routes” section of the window

Figure 136. Routes Available


11-23

Select “DEMO ROUTE (-)” and choose the button. The

Route you selected appears in the Traveler Routes section of the window

Figure 137. Traveler Routes - Demo Route (-) Added

Choose the button. This will save your changes to the database and

return you to the Traveler Route Maintenance Screen (Figure 138)


11-24

Figure 138. Traveler Route Maintenance - Route Information Added


11-25

11.5 CLOSING OPERATIONS ON A TRAVELER

Closing an operation within a route will record the time and date the operation was closed

as well as the User id of the person who completed the operation.

Choosing the icon next to the Route ID will save any changes related to the route.

To delete a route, click the icon next to the Route ID.

STEP To close an operation within a route, perform the following from the Traveler

Route Maintenance window (Figure 139):

Check the Ok check box for the operation (right center of the record). Enter

the narrative as shown into the Operation Comment text box. Clicking in the

text box will expand the text box for edit

Figure 139. Traveler Route Maintenance - Route Information Expanded


11-26

Figure 140. Traveler Route Maintenance - Operation Completed

Choose the icon next to the Route ID. The red background behind the

route description will turn green (Figure 140) when all routes have been

completed and orange when a route is started, but not completed

Note: Choosing the Operation Comment text box will allow the user to view the

complete comment for the operation.


11-27

11.6 CREATING A CHILD TRAVELER

A “Child” Traveler is a Traveler that is generated from another Traveler. For example, if

a depot was doing repair work on an engine, a child Traveler may be created to do

cylinder head repair.

STEP To create a Child Traveler, perform the following:

From the Traveler Route Maintenance Page (Figure 140), choose the

button. The Traveler Identification Information Maintenance page is


Choose the “FRACAS Defect Part” link, located in the right area of the

FRACAS Defects section. The Defective & Replacement Parts window is



11-28

Figure 141. Defective & Replacement Parts window


11-29

Choose the Select Serialized Defective Part button. The Select Serialized

Defective Part window is displayed (Figure 142)

Figure 142. Select Serialized Defective Part

Choose the icon next the CONTROLS ASSEMBLY record, Part#

“MC-CA-99036”. This action designates this part as a defective component

found in the top level system. The Defective & Replacement Parts window

is re-displayed (Figure 143)


11-30

Figure 143. Defective & Replacement Parts window - Before Save

Choose the button. The Create Traveler button (Top Left) now

appears on the screen (Figure 144)


11-31

Figure 144. Defective & Replacement Parts window - After Save

Choose the Create Traveler button. The Create MMIS Tracking Number

window is displayed (Figure 145). Figure 145 shown with data entered


11-32

Figure 145. Create MMIS Tracking Number - Child Traveler

Select “GO - Goleta” from the Location Site: drop down list”

Select “TST” from the Program: drop down list

Select 98765 from the Customer Code drop down list

Enter a Tracking Number in the Tracking Id: text box or Leave 00000 for

Automatic Assignment

Choose the button. A Child Traveler has now been created. The

Traveler Identification Information Maintenance window is displayed

(Figure 146)


11-33

Figure 146. Traveler Identification Information Maintenance - Child Traveler…..

Note: Choosing the Email Notify button will send out emails to all individuals in the

ZEMPLOYEE table that are attached to the Site of the Child Traveler.

Info: When you query for a Traveler on the Traveler Identification Information Finder

screen (Figure 147), and a Child Traveler exists, you will see the icon that can

be expanded to show the Child Traveler information.


11-34

Figure 147. Child Traveler Information - Before expansion

Figure 148. Child Traveler Information - After expansion


ACTION LOG

SECTION 12

MMIS WORKBOOK SECTION 12 ACTION LOG SYSTEM

12-3

SECTION 12 ACTION LOG SYSTEM

12.0 INTRODUCTION

MMIS includes an Action Log system for tracking user defined actions. These actions

can be used to track tasks completed against specific parts, or be used for more generic

tasks that are not covered in other areas of MMIS.

12.1 ACTION LOG MAINTENANCE

The MMIS Action Log is controlled through the Action Log finder. Here, you can add,

remove, edit, and report on actions within the system.


12-4

12.1.1 Creating a new Action

New actions are created through the Action Log Finder

STEP To create a new Action, perform the following:

Navigate to Workflow -> Action Log Finder

Ensure that the end item your trainer has provided is set

Choose the button

Select “GO” from the Site: drop down list

Select “H3 Sil” from the Location: drop down list

Select “Work in Progress” from the Action Status: list

Enter “MMIS Training” in the Action Comment: text field. Figure 149. Action

Log Edit Screenshows the edit screen after data has been entered

Choose the button. Figure 150 is displayed.


12-5

Figure 149. Action Log Edit Screen


12-6

Figure 150. Action Log Edit Screen After Saving


12-7

12.1.2 Adding an Additional Action

After pressing the “Save” button, the Action Log Edit screen changes as shown in Figure

150. Action Log Edit Screen After Saving to include the “New Record Button”

STEP To insert an additional record into the Action Log do the following:

Choose the button

Select “GO” from the Site: drop down list

Select “H3 Sil” from the Location: drop down list

Enter “MMIS Training” in the Action Comment: text field

Choose the button

Choose the button to return to the Action Log Finder screen


12-8

12.1.3 Alternative Ways to Enter Actions

Upon returning to the Action log finder, observe that the two records displayed are

editable. These can be updated by changing them inline. Additionally, new records can be

added from the finder screen without ever navigating to the edit screen.

Figure 151. Action Log Finder with Records

STEP Add additional records using the finder interface

On the Action Log Finder Choose the button. Figure 152 is displayed.

Note that Figure 152 is shown after data has been entered.

Enter “Inline Action” in the Action Comments: text field

Choose “GO” from the Site: drop down list

Choose “H3 Sil” from the Location: drop down list

Choose the icon


12-9

Figure 152. Inline Entry


12-10

12.1.4 Part Look Up

Look up part and serial number in the action log edit

STEP Part Look Up

On the Action Log Edit click the button

Click the button

Select a Part by clicking on the Icon


12-11

12.1.5 Clone A Record

Records can also be cloned from the finder screen without ever navigating to the edit

screen.

STEP Clone records using the finder interface

On the Action Log Finder Choose the (Clone) Icon

Edit any fields you wish

Choose the icon


12-12


SECTION 13

PURCHASE ORDERS

MMIS WORKBOOK SECTION 13 PURCHASE ORDERS

13–3

SECTION 13 PURCHASE ORDERS

13.0 INTRODUCTION

Purchase Orders are used to organize Serialized and Non-Serialized part orders

and receipts from vendors. You can track the progress of an order from initial

setup, sent to vendor, partial receipt and full receipt. When a part is received, it’s

entered into the Serialized or Non-Serialized inventory at the location you

specified.

13.1 CREATE VENDORS

Summary: Each purchase order is organized under a specific vendor. Parts the

vendor is responsible for are assigned to the vendor in the vendor setup screens.

When the purchase order is created under that vendor, you can select to order and

receive from that vendor’s list of parts. So before we create any purchase orders,

we’ll need to the vendor and vendor part data that the purchase orders will feed

off of.

Go to Main Menu -> Part Management -> Vendor Management.

Select an End Item and click on the ‘New’ button.

You must enter a Vendor CAGE Code and a Vendor Name.

Set the Vendor Type to ‘Procure’ or ‘Both’ and the Active flag to ‘Yes’.

The Vendor CAGE Code must exist in the LSAR table XH before it can

be used for a vendor(XH is the table used to store CAGE codes).


13–4

The CAGE code for the vendor does not need to match the cage code you

will ultimately receive and store the part under. Select the ‘Save’ button.

Figure 190

After the vendor is created, you can add parts to it by going to the ‘Linked

Parts’ tab. Click on the ‘Select New Part’ button to add new parts that will

be controlled beneath this vendor. Click on the arrow button next to a part

to add it to the list. After a part is added, you can specify additional

information like price and vendor part number.

Figure 191


13–5

Once your parts list is complete, Go to the Purchase Order system by going to

Main Menu -> Part Management -> Purchase Orders.

13.2 CREATE PURCHASE ORDER

Go to Main Menu -> Part Management -> Purchase Orders.

Click on the ‘New’ button on the Purchase Order Finder screen.

Select an End Item, and click on the ‘Look up Vendor’ button to look up

and select the vendor that you had created previously.

Enter information into the other optional fields as desired.

Click on the ‘Save’ button to create the new Purchase Order.

After the purchase order saves, you should be presented with a screen with

four tabs: PO Details, PO parts, Non Serialized PO Parts and Documents.

Figure 192


13–6

PO Parts is the list of serialized parts attached to your Purchase Order. To

add a new serialized part to your purchase order, click on the ‘PO Parts’

tab and then click on ‘Select New Part’. You’ll be prompted with a Part

Finder dialog. The parts listed on this dialog are the parts that are attached

to the Vendor. If you want to add more line of the same part, you can

change the quantity under ‘Number of parts’ before hitting the arrow. Hit

the arrow to add a part and then close the Part Finder dialog.

Your PO Parts list should now have a line for each part added. Each line

has additional information you can choose to fill out and track, like the

Carrier, Account number, Receiving document number(rcdn), Price and

more. Assuming you’re creating this Purchase Order before the parts have

been received from the vendor, we can return to the ‘PO Details’ tab and

click on the ‘Send PO to Vendor’ button.

This will automatically set the ‘Set to Vendor Date’ and change the PO

Status to ‘Sent’.

Figure 193


13–7

13.3 RECEIVING PARTS

Receiving a part entails giving the part a serial number(If it’s serialized) or

a contract(If it’s non-serialized), and assigning a site, location, shelf and

bin to receive the part at.

Click on the tab titled ‘PO Parts’ on the Purchase Order Edit screen.

You can choose whether to receive each PO Line at the same location, or

at different locations. If you want to save a number of them at the same

location, select values in the ‘Default Receiving’ box at the top of the tab.

The screen will then use these selected values to populate the site

information when you receive a part.

Click on the ‘Receive Now’ checkbox on a PO line to receive a part.

This will automatically fill out a number of the required fields, like receive

date and who performed the receipt. If a required field isn’t yet filled out,

you will be greeted with a dialog informing you which data still needs to

be entered.

Figure 194

After you’ve populated the receive data, click on the ‘Save’ button at the

top of the tab. This will perform the receipt and enter the received part into

inventory.


13–8

13.4 DOCUMENTS

Documents associated with a Purchase Order can be attached through the

‘Documents’ tab from the Purchase Order Edit screen. This is a good

place to store and track shipping documents, receiving documents,

correspondence and other information.


PART UPGRADE

SECTION 14

MMIS WORKBOOK SECTION 14 PART UPGRADE

14-3

SECTION 14 PART UPGRADE

14.0 INTRODUCTION

The Part Upgrade/Update tool allows users to update or upgrade a serialized part

or a traveler. The update process is allows the user to make corrections to the

CAGE Code, Part Number and/or serial number of a serialized part. Performing

an update or upgrade on a serialized part can potentially have an effect on the

following disciplines: FRACAS, Traveler, and As Maintained.

14.1 UPDATING A SERIALIZED PART

Updating a serialized part is generally necessary to make corrections on a

serialized part’s CAGE code, part number or serial number. Performing an update

to a serialized part will flow the changes down to any traveler, FRACAS or

AsMaintained records that are associated.

An update performs the following steps:

1. Updates the serialized part record with the updated/new keys

(CAGE code, part number, and/or serial number) chosen.

2. Updates all travelers against the serialized part.

a. Updates any FRACAS record attached to the traveler.

3. Updates FRACAS System and FRACAS Defects records against

the serialized part.

4. Updates As Maintained if the original serialized part was in a

configuration.

STEP

To update a serialized part perform the following:


14-4

Navigate to: Inventory Management > Serialized Inventory. The

Serialized Inventory Finder is displayed (Figure 195).

Figure 195


Enter ‘TOPLEVEL1’ into the Serial Number text field in the finder

box.

Click the button.

Only one record should be returned. Click the part number hyper-link. The

Serialized Part Information Maintenance screen is displayed below (Figure 196)

Figure 196


14-5

Click the button. The Part Update Wizard is now


Figure 196

The button and button are displayed

at the bottom of the page. The button displays a Part

Picker dialog. This dialog provides a finder to search all parts in

MMIS (Table HA). The displays a Serialized

Part Picker dialog. This dialog provides a finder to search all serialized

parts in MMIS. Selections made in both dialogs will fill in the ‘New

Keys’ fields.

Info: The functionality might be used in instances

where two serialized part records exist, but represent one part in

actuality. For example, one serialized part record exists with an

incorrect serial number of ‘001’ and exists another serialized part under

the same CAGE Code, Part number but with a serial number of ‘0001’,

which was correctly left padded to four digits with zeroes. Both

serialized part records in MMIS are considered two distinct parts, but

they represent the same part. The serialized part update wizard might


14-6

be used to merge these two records. To fix this situation the part update

wizard would be used from the serialized part with a serial number of

‘001’ and fill in a serial number of ‘0001’ in the ‘New Keys’ serial

number field.

In this example, a correction will be made to the serial number. Enter

‘TOPLEVEL’ into the Serial Number field associated with the ‘New

Keys’ as shown below (Figure 197)

Figure 197

Click the button, this will prompt an alert message as

shown below (Figure 198)

Figure 198


14-7

Upon updating a serialized part, the old record will be deleted and a

new record with the updated keys will be created. Click the OK button

to continue. The wizard will proceed and now an ‘Options’ and

‘Current Part Information’ panel will be displayed. (Figure 199)

Figure 199

The ‘Current Part Information’ panel illustrates all records associated

with the current serialized part and will be updated upon completion of

the wizard. The ‘Options’ panel displays options that are required to be

selected in order to continue with the part update. In this case the part

being updated is a top level part in an As Maintained configuration.


14-8

The part update wizard allows selection of which As Built Master to

follow. Select the first option ‘A’ under ‘Part Rev.’

Figure 200

Click the button near the top of the screen to perform

the part update.

Click the button near the top

of the screen to return to the Serialized Part Information Maintenance

screen for the updated part. The Serialized Part Information at the top of

the screen will now show the part keys with the updated serial number.

Figure 201

Click the button on the Serialized Part Information Maintenance

screen to return to the Serialized Part Finder.

Enter ‘TOPLEVEL’ into the Serial Number text field in the finder box

and click the button.

One record should be returned. Scroll completely to the right.


14-9

Notice the ‘Previous Part Number’ and ‘Previous Serial Number’

columns show the previous serial number before the part update.

14.2 UPGRADING A SERIALIZED PART

A key difference of an upgrade compared to an update in MMIS is when an

upgrade occurs both versions of the part will exist in inventory after the

upgrade is performed. However, the previous version of the part will be

marked as historic leaving the current version of the part as the only active

version of the part in serialized inventory. In order for the upgrade to be

possible the part upgrade must be listed as an alternate in the Alternates

Management system. Alternates management can be accessed in the menu

through Main Menu > Part Management > Alternates Management. Verify

the upgrade flag in the alternate record is set to ‘Yes’.

An upgrade performs the following steps:

1) If the upgrade part does not exist in serialized inventory, then it will

be created.

a. Data such as the contract, site, location shelf and bin from

the previous part will be used when creating the upgrade

part in serialized inventory.

2) Open travelers created against the previous version of the part are to

be moved to the upgrade part if the option is selected.

a. ETI Hours against the open traveler will be moved over to

the upgrade part.

b. Moves any associated FRACAS defects.

3) Upgrade the previous version of the part in As Maintained

configuration to the upgrade part.

4) Mark previous version of the part as historic.

STEP To upgrade a serialized part perform the following:

Navigate to Main Menu > Inventory Management > Serialized

Inventory.


14-10

Info: A part upgrade path is pre-defined under the training end item and can

be viewed in the Alternates Management system below. Part number ‘MC-

CA-99036A’ is listed as an upgrade to the part number ‘MC-CA-99036’.

Figure 202

Enter ‘TZH1002’ into the Serial Number text field in the finder box.

Click the button

Click the hyperlink. The Serialized Part Information

Maintenance screen is now displayed.

Click the button. The Part Upgrade Wizard screen is now

displayed.

Click the button. A Part Picker dialog is now displayed in

the screen. This finder will display the results of any parts that are listed as

an upgrade part to the current part. The Alternates Management system

maintains this information.

Click the button. One record will be returned.

Click the icon next to the record with a Part Number ‘MC-CA-

99036A’. The dialog will close and the ‘New Keys’ fields will now be

populated with the upgrade part CAGE Code and Part Number.


14-11

Figure 203


14-12

Click the button, this will prompt an alert message as

shown below (Figure 204).

Figure 204

Upon updating a serialized part, the old record will be deleted and a

new record with the updated keys will be created. Click the OK button to

continue. The wizard will proceed and now an 'Options' and 'Current Part

Information' panel will be displayed.

For the option labelled ‘Open traveler(s) exists on the original part.

Select an option below.’ Select the option ‘Copy Open Travelers’. This

will move all open travelers from the previous version of the part to the

upgrade part.

For the option labelled ‘LCNs/ALCs do not exist for the upgrade part.’

Select the option ‘BIKE05’ under the column ‘New LCN’, this will

automatically populate the drop down under ‘New ALC’ with a selection

of ‘01’.

Info: The LCN/ALC combination of BIKE05/00 exists only for the

previous version of the part. The upgrade version is listed only at

BIKE05/01. Because of this difference the LCNs must be mapped

for associated FRACAS records when performing the upgrade.

For the option labelled ‘Upgrade part in AsMaintained?” Select the first

option with an LCN/ALC/Part Rev. of BIKE05/ALC/A. This allows As

Maintained to be updated at a new LCN/ALC/Part Revision combination.


14-13

The options selected should be the same as the image below Figure

(205)

Figure 205

Click the button near the top of the screen to perform

the upgrade.

After part is upgraded click the

button near the top of the screen

to return to the Serialized Part Information Maintenance screen for the

upgraded part. The Serialized Part Information at the top of the screen will

now show the part keys for the upgraded part. (Figure 206)

Figure 206


14-14

Click the button on the Serialized Part Information Maintenance

screen to return to the Serialized Part Finder.

Enter ‘TZH1002’ into the Serial Number text field and check the

checkbox under ‘Show Historic’ in the finder box.

Click the button. Two records should be displayed in the

results. Scrolling to the right of the screen, notice the ‘Historic’ column as

checked for the previous version of the part. Also notice the ‘Previous Part

Number’ and ‘Previous Serial Number’ columns for the upgrade part are

filled.

Figure 207


MMIS ADHOC

SECTION 15

MMIS WORKBOOK SECTION 15 MMIS ADHOC

15–3

SECTION 15 MMIS ADHOC

15.0 INTRODUCTION

MMIS Adhoc is an MMIS module that allows users to create customized queries using

standard SQL syntax, and execute those queries on the MMIS database. This section will

provide an introduction into basic SQL syntax, and demonstrate how SQL can be used

specifically in the context of the MMIS database.

SQL is an acronym for Structured Query Language, and is computer language designed

for the management and retrieval of data in a relational database management system

(RDMS). In addition to retrieving data from the database, SQL can be used to insert,

update, and delete records from the database, as well as grant and revoke privileges on

objects used in the database. MMIS does not support execution of SQL statements that

modify data, but can be used to retrieve records from the database, and save the results to

a spreadsheet. In order to use SQL, the user does require some knowledge concerning

the underlying database tables in the system being queried.

15.1 DATABASE TABLES

A key concept in a relational database is the concept of a “table”. A table is very similar

to a spreadsheet in that it has rows and columns that have values. Each row represents a

record, or part of a record, and each column represents a field in the record. Some fields,

such as key fields are mandatory, while others are conditional or optional. In addition,

tables can have relationships with other tables.


15–4

15.2 QUERIES

The most common operation in SQL databases is the query, which is performed with the

declarative SELECT keyword. SELECT retrieves data from a specified table, or multiple

related tables, in a database. While often grouped with Data Manipulation Language

(DML) statements, the standard SELECT query is considered separate from SQL DML,

as it has no persistent effects on the data stored in a database. Note that there are some

platform-specific variations of SELECT that can persist their effects in a database, such

as the SELECT INTO syntax that exists in some databases.

SQL queries allow the user to specify a description of the desired result set, but it is left

to the devices of the database management system (DBMS) to plan, optimize, and

perform the physical operations necessary to produce that result set in as efficient a

manner as possible. An SQL query includes a list of columns to be included in the final

result immediately following the SELECT keyword. An asterisk ("*") can also be used as

a "wildcard" indicator to specify that all available columns of a table (or multiple tables)

are to be returned. SELECT is the most complex statement in SQL, with several optional

keywords and clauses, including:

The FROM clause which indicates the source table or tables from which the data

is to be retrieved. The FROM clause can include optional JOIN clauses to join

related tables to one another based on user-specified criteria.

The WHERE clause includes a comparison predicate, which is used to restrict the

number of rows returned by the query. The WHERE clause is applied before the

GROUP BY clause. The WHERE clause eliminates all rows from the result set

where the comparison predicate does not evaluate to True.


15–5

The GROUP BY clause is used to combine, or group, rows with related values

into elements of a smaller set of rows. GROUP BY is often used in conjunction

with SQL aggregate functions or to eliminate duplicate rows from a result set.

The HAVING clause includes a comparison predicate used to eliminate rows

after the GROUP BY clause is applied to the result set. Because it acts on the

results of the GROUP BY clause, aggregate functions can be used in the

HAVING clause predicate.

The ORDER BY clause is used to identify which columns are used to sort the

resulting data, and in which order they should be sorted (options are ascending or

descending). The order of rows returned by an SQL query is never guaranteed

unless an ORDER BY clause is specified.


15–6

15.2.1 Query Examples

Say for example you have a table called “BOOKS” that looks like the following:

Title Author Description Cost Price

Robinson

Crusoe Daniel Defoe Adventure 7.99 14.99

Rain Of Gold

Victor

VillaSenor Adventure 3.99 8.99

Grapes Of

Wrath John Steinbeck Drama 5.01 10.15

This table is populated with 3 rows, and has 5 columns: Title, Author, Description, Cost

and Price. The Cost is how much we paid for the book, and Price is how much we intend

to sell the book for.


15–7

If we wanted to select every column and every row from the table above, we could

execute an SQL statement such as the one below.

SELECT * FROM BOOKS

The key word “SELECT” identifies the columns you wish to be returned from the table

specified in the FROM clause. The “*” is a wildcard, and in this case is telling the

database that we wish to view all columns selected in the table.

If we only wanted to see the books in the BOOKS table, but did not wish to see any other

information we could has written the query differently.

SELECT TITLE FROM BOOKS

Title

Robinson

Crusoe

Rain Of Gold

Grapes Of

Wrath


15–8

Or we could have chosen to list only the TITLE and the PRICE

SELECT TITLE, PRICE FROM BOOKS

Title Price

Robinson

Crusoe 14.99

Rain Of Gold 8.99

Grapes Of

Wrath 10.15

As mentioned above, the WHERE clause is used to filter the rows that are returned in a

query. For example if we wanted to see all books written by John Steinbeck, we could

execute the query:

SELECT * FROM BOOKS WHERE AUTHOR = ‘John Steinbeck’


Grapes Of



15–9

We could also use the WHERE clause to query for all records that cost more than $5.00.

SELECT * FROM BOOKS WHERE COST > 5


Robinson

Crusoe Daniel Defoe Adventure 7.99 14.99

Grapes Of


Notice that when using a WHERE clause all string arguments are enclosed by single

quotes, while numeric arguments are not.


15–10

15.2.2 MMIS Adhoc Screen Description

Figure 153. MMIS AdHoc Screen

The Adhoc screen shown in Figure 153 is divided up into 3 main sections. We navigated

to this screen by choosing Main Menu -> AdHoc. The “Tables” section (Figure 154)

describes all of the tables that are accessible utilizing the Adhoc Tool.


15–11

Figure 154. MMIS AdHoc – Tables

The second Main section of the AdHoc window is the “Database Columns” section

(Figure 155, Figure 156)

Entering a table name in the Tables Search: text box, will filter the tables by name.

When a table is selected in the Tables box, the columns in the table will be displayed in

the Database Columns box (Figure 155, Figure 156).

Figure 155. MMIS Adhoc - Table HA


15–12

Figure 156. MMIS AdHoc - Database Columns Expanded

The third Main section of the AdHoc window is the SQL Text Area (Figure 157). This

area displays the SQL Query as it is completed

Figure 157. MMIS Adhoc - SQL Query Displayed

Figure 157 shows that Table HA has been selected, the button has been

selected in the Database Columns section, and the SQL query is displayed in the SQL

text area.


15–13

15.2.3 MMIS Adhoc Query Exercise

STEP To create a Query in MMIS, perform the following:

Navigate to Main Menu -> Adhoc. (Figure 153) is displayed


Enter “HG” in the Tables Search: box. Table HG, Part Application

Provisioning becomes active (Figure 158)

Figure 158. AdHoc Tables - Table HG.

Choose the Button. Figure 159 is displayed


15–14

Figure 159. MMIS AdHoc - Columns Selected

Use the mouse, WHILE HOLDING THE CTRL KEY, to also select

“QTYASYHG” from the Database Columns list box as shown in Figure

160

Figure 160. MMIS AdHoc - SQL Statement Displayed


15–15

Notice that in the SQL Text area (Figure 160), an SQL statement has been created that

can be executed.

Figure 161. MMIS AdHoc - Where Window


Click on the Column LSACONXB as shown in (Figure 162)


15–16

Figure 162. AdHoc Where Window - LSACONXB Selected

Figure 163. AdHoc Where Window - Operator List


15–17

Select “like” from the operator list box (Figure 163)

Choose the apostrophe ( ) button

Enter “BIKE01%”

Choose the apostrophe ( ) button

Figure 164. MMIS AdHoc Where Window - Completed Where Clause

At this point, your window should reflect Figure 164.

Choose the Button. You are returned to the Main AdHoc

Window with the here Statement added to the SQL Query


15–18

At this point you are ready to execute your query. Notice that the SQL has been

generated for you. If you are an expert in SQL you could have typed the query into the

SQL text box by hand, or pasted it in from another document.

Examining the SQL created, we see that our WHERE clause is limiting the rows returned

to LCNs that begin with the string “BIKE01”. From a conceptual view, we are asking for

a complete list of part numbers that comprise the “BIKE01” system which in our case is

the ESL749ZF Frame Assembly.


15–19

SELECT HG.CAGECDXH, HG.REFNUMHA, HG.EIACODXA, HG.LSACONXB,

HG.ALTLCNXB, HG.LCNTYPXB, QTYASYHG

FROM HG

WHERE (HG.LSACONXB LIKE 'BIKE01%')


Figure 165. MMIS AdHoc - Query Results


15–20

Notice that the all of the records returned have an LCN that begins with the string

“BIKE01”. The number of records returned is defaulted to 50 records per page, and you

can scroll through each page by pressing the button if necessary.


Figure 166. MMIS Query results - Exported to Excel


MMIS

DASHBOARD

SECTION 16

MMIS WORKBOOK SECTION 16 MMIS DASHBOARD

16-3

SECTION 16 MMIS DASHBOARD

16.0 INTRODUCTION

The MMIS Dashboard allows users to see custom reports directly on their MMIS

Homepage. These reports are custom to each user and can be set up with custom

parameters to allow the user to see exactly the data that is relevant to them.

Figure 167. MMIS Homepage


16-4

16.1 CREATING A MMIS DASHBOARD

STEP To create a MMIS Dashboard, perform the following:

Login to MMIS to view the standard MMIS Home Page as shown in Figure

167

Choose the Create Dashboard Link at the bottom of the MMIS Home Page.

This will create a blank MMIS Dashboard for the MMIS User (Figure 168)

Figure 168. Blank MMIS Dashboard


16-5

16.2 ADDING CONTENT TO YOUR MMIS DASHBOARD

STEP To add content to your MMIS Dashboard, perform the following:

Login to MMIS to view the standard MMIS Home Page as shown in Figure

167

Choose the Add Icon ( ). This will display a list of available reports

for the MMIS Dashboard (Figure 169)

Choose your desired report by clicking in the specific report window. The

Parameter Form is displayed (Figure 170) for the report selected

Figure 169. MMIS Dashboard Report Selection


16-6

Note: You may use the scroll bar on side bottom of the virtual window to move up and

down to select different reports. You may also use the search feature.

Figure 170. MMIS Dashboard - Parameter Form

Select or add parameters for the report

Choose the Button to view the report in your MMIS Dashboard

(Figure 171)


16-7

Figure 171. MMIS Dashboard - Traveler Parts Report

The report parameters can be changed at any time. Also, multiple reports with different

parameters are allowed in the MMIS Dashboard. Example only shown in Figure 172

Figure 172. MMIS Dashboard with Multiple Reports - Example


16-8

16.3 EDITING YOUR MMIS DASHBOARD

STEP To edit your MMIS Dashboard, perform the following:

Choose the Edit Icon ( ). This will put the MMIS Dashboard in Edit

Mode (Figure 173). Each report in your MMIS Dashboard will then have a

header with options

Figure 173. MMIS Dashboard - Header with Options

Choose the (edit) link on the report header (Figure 173). The parameter

selection screen for the report is displayed (Figure 174) Figure 174 is shown

with the Serial Number radio button selected.


16-9

Figure 174. MMIS Dashboard Report Header in Edit Mode

Select the Serial Number radio button as shown in Figure 174



16-10

Figure 175. MMIS Dashboard – Traveler Serial Numbers Report

To delete a report from your MMIS Dashboard choose the Delete Icon ( ) in the

header of the report.

To move a report, simply Click and Drag the Header to a new position on the MMIS

Dashboard. Available positions are displayed as dotted borders. Available positions will

appear in each column once you drag the report over that column. Example shown in

Figure 176.


16-11

Figure 176. Moving Report to New Location - Example

Once changes are complete you must choose the Save button ( ) to save your

changes.


16-12


SKILL TESTS

SECTION 17

MMIS WORKBOOK SECTION 17 SKILL TESTS

17–3

SECTION 17 SKILL TESTS

17.0 INTRODUCTION

This section provides an opportunity to show your stuff.

17.1 SKILL TEST 1

Summary: You have been assigned a new job for a new contract that Raytheon has won

for repairing “Widgets (Part Number MC-DA-0034S)”

The Contract Code is N00043. Your customer in this case is the U.S. Navy.

The Contract Number for this effort is N00043-09-D-03111.

The delivery order number is 0011

The following line items are included in this contract.

Line Number: 1

Type: Administrative


17–4

Description: Provide FRACAS information for FRB monthly meetings.

Line Number: 2

Type: Administrative

Description: Provide AsBuilt Documentation of Widget

Line Number: 3

Type: Repair

Description: Repair and maintain Widget

Line Number: 4

Type: Modification

Description: Incorporate Engineering Modifications to the Widget

Task 1: Enter the Contract and Contract Line Item Information into MMIS

17.2 SKILL TEST 2

Your next task is to create an AsBuilt Master Template for the part numbers you are

required to serialize in the Widget.


17–5

All revisions are ‘A’

The parts you are required to serialize are shown below:

Task 2: Create an AsBuilt Master Template for the above parts list.

17.3 SKILL TEST 3

Your next task is to serialize 2 units, using the template above.

CAGE Ref Num Item Name LCN ACL

99999 MC-DA-0034S WIDGET BIKE03 0

99999 MC-PA-TU-604 PEDAL ASSEMBLY BIKE03AA 0

99999 TU-604L PEDAL BIKE03AA01 0

99999 PA65E PEDAL ARM BIKE03AA03 0

99999 KMC-UG50 CHAIN BIKE03AB 0

99999 MRX-170-71 DERAILLUER ARM BIKE03AC 0

99999 FD-CT91-T DERAILLUER ASSEMBLY BIKE03AD 0


17–6


17–7

17.4 SKILL TEST 4

Your next task is to release both of the systems created above as “Ready For Issue”.

Attach them to the contract created in skills test 1 (N00043-09-D-03111).

Choose “GO GP Stores” as the location.

17.5 SKILL TEST 5

Assume that an ECP has been created for the Widget.

This ECP is a class 1 ECP, and is titled “Widget Upgrade”

This ECP must be attached to both SN’s WID5000 and WID5001, so that when they are

inducted via attrition, the changes can be made.

Create the above ECP in MMIS, and attach it to both units listed above.


17–8

17.6 SKILL TEST 6

WID5001 fails in the field, and is inducted for repair. The repair site is “GO Goleta”, and

the program is “TST”.

After the unit is inducted, it was found that the Pedal Assembly was found to be the cause

of the defect.

Create a traveler for WID5001, remove the Pedal Assembly, and create a child traveler

for the Pedal Assembly. Also, incorporate any outstanding ECPS on the un


STRUCTURED QUERY

LANGUAGE

APPENDIX A

MMIS WORKBOOK APPENDIX A STRUCTURED QUERY LANGUAGE

A–3

APPENDIX A STRUCTURED QUERY LANGUAGE

A.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

A.1 CONVENTIONS USED IN THIS APPENDIX

CONVENTION PURPOSE

UPPERCASE Transact-SQL statements, and any other portions of

syntax that must appear exactly as shown.


A–4

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.

A.2 SQL AND RELATIONAL DATABASE MANAGEMENT

SQL is a high-level language for relational database systems. With SQL you can query,

insert, update and delete data in a database. SQL works on database systems like

SYBASE, Oracle, and Microsoft Access.


A–5

A.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

A.2.2 Data Elements

A.2.2.1 Key Fields

Keys uniquely define a row of data in a table.

A.2.2.2 Data Types

Each column in a database has a datatype. It specifies data characteristics of the column.

ORACLE data types include the following:


A–6

Numbers: NUMBER INTEGER

Character: CHAR VARCHAR2

LOB*: BLOB CLOB

Date: DATE

*= Binary Large Object


A–7

A.3 QUERYING DATABASES

A.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 = ‘3’


A–8

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]


A–9

A.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

where sys_cd = ‘A3’


A.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



A.3.1.3 Counting Rows


A–10

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



A–11

A.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

*BETWEEN and NOT BETWEEN are inclusive

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%’


A–12

A.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.

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.


A–13

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%’

A.3.2.2 Comparison Operators

Oracle databases use the following comparison operators:

OPERATOR MEANING

= equal to

> greater than


A–14

< less than

>= greater than or equal to

<= less than or equal to

<>,!= not equal to

A.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.

select *

from defect

where part_no like ‘12345678%’ and

part_no like ‘87654321 %’

order by part_no


A–15

A.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

A.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%‘


A–16

A.3.3 Joining Two or More Tables

A.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

A.3.3.2 Outer Joins

In inner joins, only matching rows are included in the results. If nonmatching rows are

desired in the results of a join, an outer join should be used. Oracle outer joins use the (+)


A–17

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(+)


A–18


EAGLE LCNs

TO BOM IMPORT

APPENDIX B

MMIS WORKBOOK APPENDIX B EAGLE LCNs TO BOM IMPORT

B–3

APPENDIX B EAGLE LCNs TO BOM IMPORT

B.0 INTRODUCTION

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.


B–4

Figure 177. Navigator-Assign LCNs to BOM


B–5

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.In order to perform this exercise, the TRAINBOM.XLS

file must be open in Excel and all the data selected for copying. The TRAINBOM.XLS

file is located in the EAGLE root directory C:Program Files\RSC\EAGLE2B Oracle.

Once these records have been copied to the clipboard in Excel, the following steps can be

completed.

Figure 178. Automatically Assign LCNs


B–6

B.1 IMPORTING BOM

Because the TRAINBOM.XLS file contains data that already exists in our BICYCLEXX

End Item, we have selected the NEWBIKEXX End Item. This End Item must be

selected before Assign LCNs to BOM is executed from the Navigator or entered

manually.

STEP Perform the following to Automatically Assign LCNs to a BOM and import the

Data utilizing EAGLE:

Access the Assign LCNs to BOM Function from the LCN Maintenance

discipline using the Navigator as shown in Figure 177 . The Automatically

Assign LCNs Window is displayed and defaults as shown (Figure 178)

Make sure NEWBIKEXX is selected as End Item

Figure 179. Clipboard Format-Clipboard Format Button


B–7

Choose the Clipboard Format button. The Clipboard Format popup window

is displayed (Figure 179). The data in your spreadsheet must be in this

format. Click OK

Enter ‘A’ in the Start LCN data box

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

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’


B–8

Figure 180. Clipboard Format-Paste Clipboard

Choose the Paste Clipboard button. Choose Yes to ‘Is the Clipboard data in

this order?’ (Figure 180)


B–9

Figure 181. Automatically Assign LCNs-Paste Clipboard

The records are added as shown in Figure 181.


B–10

Figure 182. Automatically Assign HG Indenture Codes?


B–11

Choose the Calculate LCNs button. The Automatically Assign HG Indenture

Codes? Window is displayed as shown in Figure 182. At this time our

spreadsheet does not contain HG Indenture Codes, so Click ‘No’ to ‘Would

you like the Table HG Indenture Codes to be assigned/calculated? Figure

183 is displayed

Figure 183. Automatically Assign LCNs- Calculate LCNs


B–12

Figure 184. Database Error Messages-View Results

Choose the Populate Database button. Note the View Results button

becomes active

Choose the View Results button. The Database Error Messages Window,

Figure 184, is displayed

Choose the OK button to return to the Automatically assign LCNs Window


B–13

In the ‘Tables to Fill’ portion of the window, use the scroll bar on the right and scroll

down to the bottom to view additional checkboxes (Figure 185). 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.


B–14

Figure 185. Automatically Assign LCNs-Addl Parts/TM Data

B.2 CHANGE/ADD LCNs

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 Perform the following to Change/Add LCNs to a BOM and import the Data. Be

sure to “Click” in the data window when you ‘Copy Datawindow’ and ‘Paste

Spreadsheet’:


B–15

With the Automatically Assign LCNs window open as shown in Figure 185,

from the Main Toolbar choose Edit >> Copy Datawindow

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, Copy to clipboard

In the Automatically Assign LCNs window, from the Main Toolbar Edit >>

Clear Window

From the Main Toolbar choose Edit >> Paste Spreadsheet

Choose the Populate Database button


B–16


INDEX

MMIS WORKBOOK INDEX

Index - 3

INDEX

A

ADHOC

Creating Queries in MMIS, 15–6

Introduction, 15–3

QUERIES, 15–3

Query Examples, 15–4

AsBUILT Configuration

Introduction, 7-3

AsBUILT CONFIGURATION

Creating, 7-14

Releasing, 7-23

AsBUILT MASTER REPORTS, 7-9

AsBUILT MASTER TEMPLATE

Creating, 7-3

AsBuilt Master Templates

Information, 7-8

AsMAINTAINED CONFIGURATION

Importing an Assembly, 8-8

Introduction, 8-3

Removing an Assembly, 8-3

AsMaintained Configurations

Viewing, 8-11

C

CAVS Code, 7-26

Character Strings, A–10

Columns, A–4

Comparison Operators, A–8

Contract Line Item

Adding, 6-4

Contract Number

Adding, 6-3

Contract System

Introduction, 6-3

Conventions, 1-8

general, 1-8

mouse, 1-9

window, 1-10

COST ACCOUNT INFORMATION

Adding, 3–8

CUSTOMER INFORMATION

Adding, 3–8

D

Data Elements, A–4

Data Types, A–4

Database Structure, 1-5

Discipline, 1-9

Document System

Introduction, 4-3

Self Test, 4-9

Uploading and Viewing, 4-3

E

EAGLE, 1-3

MMIS WORKBOOK INDEX

Index - 4

EAGLE LCNs TO BOM IMPORT, B–3

IMPORTING BOM, B–5

ECP

Adding, 5-3

Attaching a Document, 5-6

ECP System

Introduction, 5-3

End Items, 1-5

F

FIELD FRACAS, 10-11

Creating New Record, 10-20

Deleting a Record, 10-21

FFR Wizard, 10-12

FRACAS SYSTEM

Corrective Action Information, 10-9

Defect Report, Creating, 10-3

Introduction, 10-3

I

Icons in MMIS, 1-10

INVENTORY MANAGEMENT

Introduction, 9-3

J

JOIN

inner join, A–10

outer join, A–11

K

Key Fields, A–4

L

LESSONS LEARNED MAINTENANCE

Create a Lessons Learned Record, 12–8

Lessons Learned Record

Lessons Learned Wizard, 12–11

LESSONS LEARNED SYSTEM

CATEGORY/ISSUE MAINTENANCE, 12–3

FACILITY MAINTENANCE, 12–5

IMPACT MAINTENANCE, 12–4

Introduction, 12–3

LESSONS LEARNED MAINTENANCE, 12–

8

PLATFORM MAINTENANCE, 12–6

SYSTEMS MAINTENANCE, 12–7

LOCATION DATA

Changing Location of Serialized Part, 9-8

Location History Viewing. See Serialized

Inventory

Viewing, 9-8

Logical Operators, A–8

Logistics Support Analysis, 1-3

Logistics Support Analysis Record, 1-3

M

MAIN MENU

Login, 2-3

MMIS, 1-6

MMIS DASHBOARD

Creating, 16-4

Editing, 16-7

Introduction, 16-3

MMIS Home Page, 1-7

N

NULL, A–10

MMIS WORKBOOK INDEX

Index - 5

P

PASSWORDS

Changing, 2-5

Program Code

Self Test, 3–7

PROGRAM CODE

Adding, 3–3

Viewing and Editing, 3–5

PROJECT SETUP, 3–3

R

Relational Database, A–3

RELATIONAL DATABASE, 1-4

Relationship Between Tables, 1-4

RETRIEVING RECORDS, 2-6

Rows, A–4

S

SELECT, A–5

SERIALIZED INVENTORY

Attaching ECP. See ECP

SITE DATA

Creating. See Inventory Management

SQL, A–3

T

Table HA, 1-5

Table HG, 1-6

Table XA, 1-5, 1-6

Table XB, 1-5

Table XH, 1-5

Tables, A–4

Tasblre XB ALC, 1-6

Technical Support, 9

TRAVELER SYSTEM

Adding a Route, 11-15

Cloning a Route, 11-9

Closing an Operation, 11-18

Creating A Route, 11-5

CREATING A TRAVELER, 11-11

Creating An Operation, 11-3

Introduction, 11-3

W

WHERE, A–7

Wildcards, A–7

MMIS WORKBOOK INDEX

Index - 6


STUDENT

NOTES

STUDENT NOTES

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

STUDENT NOTES

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

STUDENT NOTES

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

STUDENT NOTES

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

STUDENT NOTES

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

_______________________________________________________

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