290 likes | 1.24k Views
GEIA-STD-0007 Rev B. OmegaPS 0007. Outline. OmegaPS R18.1 Release Summary of Changes from MIL-STD-1388-2B SAE and Rev C. OmegaPS R18.1 Release. R18.1 is the first OmegaPS release to include a GEIA-STD-0007 application The list of applications now includes
E N D
GEIA-STD-0007 Rev B OmegaPS 0007
Outline • OmegaPS R18.1 Release • Summary of Changes from MIL-STD-1388-2B • SAE and Rev C Supportability Standards - Graham Brum
OmegaPS R18.1 Release • R18.1 is the first OmegaPS 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-2B • DEF AUST 5692 – Issue 1 and Issue 2 • GEIA-0007 – Rev B • Access to each Application is controlled by a key code and then by Team/Application access control Login is through a separate URL. GUI is as per other core Applications. Supportability Standards - Graham Brum
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
GEIA-STD-0007 Differences • ALC – ALCs are Alphanumeric • This improves flexibility and allows for an auditable record of changes required through extended in-service management
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 • All data types supported thus could store video as required • Completely enables Initial Provisioning process in DND by storing SPTD for IP Conferences Add Document adds an item to the Library, Drop Document removes it, Show Document opens the file Links appear here when a file has been associated with a Project. LCN and Provisioning Links are enabled currently for DND configuration of OmegaPS.
GEIA-STD-0007 Differences • Enables three tiered maintenance definition – procedure/task/subtask • Enables good map to SAP and excellent flexibility for creating maintenance documentation GEIA-STD-0007 Task MIL-STD-1388 Sub-Task Procedure Task Sub-Task
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 S1000D Resources – Personnel, Support Equipment, Provisioned Items, Manuals
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 • 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
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
GEIA-STD-0007 Differences • Additional Sub-Task Work Area Code • Work Area Code Access • Access Code identifying points of access for maintenance – equates to S1000D Access • Work Area Code Zone • Code identifying where the work will occur – equates to S1000D Zone
GEIA-STD-0007 Differences • Sub-Task Objective States • List of conditions required to complete a subtask • List is drawn from S1000D
GEIA-STD-0007 Differences • Circuit Breaker Identification and State • Groups and States required to complete a sub-task • List is drawn from S1000D
GEIA-STD-0007 Differences • Scheduled Maintenance Events • Defines dependencies for maintenance tasks • In compliance with S1000D Trigger may be a condition or another task
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 S1000D
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
SAE and Rev C • The Society of Automotive Engineers absorbed TechAmerica 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
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 DoD data/solution map • Replace the Task Code with a non intelligent identifier and explicitly store all hidden attributes – adjust any DoD required reports. This will also give us an opportunity to identify any changes required to these Task identification attributes
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 S2000M data elements that should be added to Material identification
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 S3000L 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 S5000F data elements that should be added
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