GEIASTD0007 Rev B Omega PS 0007 Outline Omega

GEIA-STD-0007 Rev B Omega. PS 0007

Outline • Omega. PS R 18. 1 Release • Summary of Changes from MIL-STD-13882 B • SAE and Rev C 8/27/2012 Supportability Standards - Graham Brum 2

Omega. PS R 18. 1 Release • R 18. 1 is the first Omega. PS release to include a GEIA-STD-0007 application • The list of applications now includes § § DEF-STAN 00 -60 – Issue 0 to Issue 4 MIL-STD 1388 -2 B DEF AUST 5692 – Issue 1 and Issue 2 GEIA-0007 – Rev B Login is through a separate URL. GUI is as per other core Applications. • Access to each Application is controlled by a key code and then by Team/Application access control 8/27/2012 Supportability Standards - Graham Brum 3

GEIA-STD-0007 Differences • The large majority of the 0007 application is drawn directly from the MIL-STD-1388 application • However – key differences make it impossible to move between the two applications seamlessly – data sets can be moved from 1388 to 0007 but not the reverse 8/27/2012 4

GEIA-STD-0007 Differences • ALC – ALCs are Alphanumeric • This improves flexibility and allows for an auditable record of changes required through extended inservice management 8/27/2012 5

GEIA-STD-0007 Differences • Enables capture of Digital Files § Enables data storage for IETMs or direct publications – Illustrated Parts CFTO is using this capability in DND configuration Add Document adds an item to the Library, Drop Document removes it, Show Document opens the file § All data types supported thus could store video as required Links appear here when a file has been associated with a Project. § Completely enables Initial Provisioning LCN and Provisioning Links are currently for DND process in DND by storing enabled SPTD for IP configuration of Omega. PS. Conferences 8/27/2012 6

GEIA-STD-0007 Differences Procedure GEIA-STD-0007 Task MIL-STD-1388 Sub-Task • Enables three tiered maintenance definition – procedure/task/subtask • Enables good map to SAP and excellent flexibility for creating maintenance documentation 7

GEIA-STD-0007 Differences • Enables all task resources at the Subtask level § This capability was introduced to Omega as an optional setting for the 1388 application several years ago and is consistent with DEF STAN 0060 § It allows for work scheduling and better mapping to S 1000 D Resources – Personnel, Support Equipment, Provisioned Items, Manuals 8/27/2012 8

GEIA-STD-0007 Differences • All Narratines have been increased to unlimited length § The restrictions imposed by 1388 have all been removed § Narratives now exist for: • Skills • Test Equipment • Support Equipment Recommendation Data Revision Remarks • Facilities • Provisioning Remark • Parts Manual Provisioning Nomenclature • Personnel Requirement • System Re-Design 8/27/2012 • Logistics Considerations • RAM Characteristics • Failure Mode Mission Phase Characteristics • FMEA Narrative • System/End Item Narrative • Additional Requirements • Unit Under Test Explanation • Electrical Ground • Transported End Item • Transportation 9

GEIA-STD-0007 Differences • Additional Reliability requirements § Required Mean Time Between Effective (or Essential) Functional Failure üLoss of mission essential function § Required Mean Time Between Non-Effective (or Non-Essential) Functional Failure üLoss of non-mission essential function § Required Mean Time Between System Aborts 8/27/2012 10

GEIA-STD-0007 Differences • Additional Sub-Task Work Area Code § Work Area Code Access ü Access Code identifying points of access for maintenance – equates to S 1000 D Access § Work Area Code Zone ü Code identifying where the work will occur – equates to S 1000 D Zone 8/27/2012 11

GEIA-STD-0007 Differences • Sub-Task Objective States § List of conditions required to complete a subtask üList is drawn from S 1000 D 8/27/2012 12

GEIA-STD-0007 Differences • Circuit Breaker Identification and State § Groups and States required to complete a sub-task üList is drawn from S 1000 D 8/27/2012 13

GEIA-STD-0007 Differences • Scheduled Maintenance Events Trigger may be a condition or another task § Defines dependencies for maintenance tasks üIn compliance with S 1000 D 8/27/2012 14

GEIA-STD-0007 Differences • Scheduled Maintenance Sampling § Defines when a task is to be completed on only a portion of the fielded items üIn compliance with S 1000 D 8/27/2012 15

GEIA-STD-0007 Differences • Additional NSNs § Allows for the identification of additional applicable NSN üThis requirement was a result of experience gained from CGCS and DRMIS When the original HA Reference is a specification rather than a MPN then actual MPNs can be added here associated with the applicable NSN 8/27/2012 16

SAE and Rev C • The Society of Automotive Engineers absorbed Tech. America in the June of 2013 § Therefore the LCLS committee responsible for GEIA-STD-0007 is now an SAE committee with the Aerospace and Defence Group § SAE committees rules do not require SAE membership in order to be a voting member üSAE wants a well balanced voting group 8/27/2012 17

SAE and Rev C • Rev C is being planned for 2015 § Items Pennant has submitted for consideration for Rev C are as follows üRemove the LCN – no inherent value added – only impediment would be any legacy requirement within the Do. D data/solution map üReplace the Task Code with a non intelligent identifier and explicitly store all hidden attributes – adjust any Do. D required reports. This will also give us an opportunity to identify any changes required to these Task identification attributes 8/27/2012 18

SAE and Rev C • Rev C is being planned for 2015 § Items Pennant has submitted for consideration for Rev C are as follows üAdd all data that only exists in LSA Report to be held in the database – any sums, calculations, etc. This will have the impact of moving us away from the reports and allow us to provide data. üIdentify any S 2000 M data elements that should be added to Material identification 8/27/2012 19

SAE and Rev C • Rev C is being planned for 2015 § Items Pennant has submitted for consideration for Rev C are as follows üIdentify any S 3000 L data elements that should be added – probably As Design/As Delivered with Configuration Management and Serialization comes in with this – to me the cut off is As Designed then As Delivered allowing us to ID serial numbers delivered by Part #/Assembly üIdentify any S 5000 F data elements that should be added 8/27/2012 20

SAE and Rev C • Rev C is being planned for 2015 § Items Pennant has submitted for consideration for Rev C are as follows üIdentify standard interface requirements to receive data from Engineering systems and provide data to Maintenance Management Systems/Material Management Systems 8/27/2012 21

Questions? 8/27/2012 22