ils council san diego 2015 09 24
play

ILS Council San Diego, 2015-09-24 NAGSMA 1 NATO UNCLASSIFIED AGS - PowerPoint PPT Presentation

ILS Council Presentation 24 September 2015 San Diego The Application of ASD Standards in the NATO AGS Program Gianni Bascelli NAGSMA ILS Manager ILS Council San Diego, 2015-09-24 NAGSMA 1 NATO UNCLASSIFIED AGS Core System The Assets


  1. ILS Council Presentation 24 September 2015 San Diego The Application of ASD Standards in the NATO AGS Program Gianni Bascelli NAGSMA ILS Manager ILS Council San Diego, 2015-09-24 NAGSMA 1 NATO UNCLASSIFIED

  2. AGS Core System “The Assets Under Procurement” Air Support 5 UAVs with Pilot Trainers Mission Crew Trainer MP-RTIP Radar & System-Wide Simulation Capability AIS Training Management Ground NATO AGS Operations Centre (NAOC) MGEC (2 Operations Areas) 2 Deployable UAV MGCC MGCC Control Element (DUCE) 6 Mobile General 2 Transportable General Ground Stations (MGGS) Ground Stations (TGGS) 1 Air Vehicle Mission Command & Control (AVMC2) (comprising TGGS Exploitation (comprising Mobile Ground 1 Mission Operations Support (MOS) Additional Remote and Mobile Ground Comms Exploitation and Comms Workstations Components) Components) Fixed – MOB Sigonella, Italy Deployable NAGSMA 2 NATO UNCLASSIFIED

  3. NATO AGS System Architecture Ku SatCom INMARSAT UHF SatCom NAEW National Air Assets ISR Data Dissemination UAV C2 NAME-08-0000 Clear UHF Voice ATC Communications NATO Secret WAN LOS WBDL National Airborne ISR MGGS ATC RWS Interoperable National Ground Stations TGGS CSOP NAGSMA 3 NATO UNCLASSIFIED 3 NATO-09-002B

  4. AGS Mission “…provide NATO decision makers, from the political down to the tactical level, with near real ‐ time, continuous unrestricted, unfiltered surveillance information in all weather conditions concerning friendly, neutral and opposing forces, from a stand ‐ off position.” NAGSMA 4 NATO UNCLASSIFIED

  5. S-Series Standard Application The NATO AGS Design and Development phase requires the application of the:  S1000D v 4.0.1  S2000M v 4.0  S3000L v 1.0  v 1.1  Application of the S1000D and S2000M followed normal tailoring and application  process. S2000M:  Chapter 1A applicable for the provisioning data during Design and  Development NATO will implement also the other chapters to manage the provisioning  process during system lifecycle NAGSMA 5 NATO UNCLASSIFIED

  6. S3000L Application NATO AGS is one of the first program that include the S3000L in the specification,  therefore there is no much experience in its application. To apply the S3000L the following steps have been carried on:  Participation to S3000L committee to acquire information on the evolution of  the standard Organization of workshops involving AGS Program’s Prime and Sub  Contractors and consultants identified to have experience in LSA database implementation and on S3000L use cases Organization of workshops to produce the tailoring document of the S3000L  for the NATO AGS (v 1.0 and v 1.1) Management of interim deliveries for LSA not in line with the S3000L  Identification of tools to be used to implement the S3000L  Mapping of the existing data towards the S3000L data model  Definition of processes for the generation of the S3000L dataset  NAGSMA 6 NATO UNCLASSIFIED

  7. S3000L Application The application of the LSA for AGS is not an easy process due to:  Complex tailoring of the standard.   Even if the LSA process remain similar to previous standards, S3000L has a different approach in identifying relationship on data elements  Tailoring requires a deep analysis also to verify DE relationships and applicability It would be useful to have a Business Process to guide in the tailoring which may also be used as guideline for data validation Support to Design Review:   No development and review process described in the S3000L It would be useful to identify the mandatory steps to be accomplished by LSA during the design and development phase in conjunction with the other ILS disciplines NAGSMA 7 NATO UNCLASSIFIED

  8. S3000L Application Reuse of existing LSA analyses:   Normally LSA data bases are already in house for developed items and the data set for COTS and NDI produced from various suppliers need to be integrated  Mapping of the existing data elements into the S3000L is not sufficient, additional data need to be added to have an S3000L consistent set of data A data element mapping among S3000L and the ones of the main used standard would be useful to have a seamless use of the DEDs. This may also address the additional S3000L required DEDs for the implementation of the database NAGSMA 8 NATO UNCLASSIFIED

  9. S3000L Application Lack of availability of commercial tools that fully implement the S3000L:   Currently the application of the S3000L requires adaptation of the LSA database to accommodate its tailoring  Building of the LSA database required the data mapping of the existing data elements produced under different standards (MIL-STD-1388/ DEF STD 00-60) and proper verification Validation rules of the imported/migrated LSA data into the S3000L is not defined but is essential. It would be useful to define the validation rules as part of the standard considering the use of the DEDs by different standards The definition of data exchange schemas is the key for relation among the  S3000L and other standards and data bases  The definition of the data exchange schema requires a tailoring activity of the S3000L but that has to take into account the use of the DEDs for other standards and support processes Definition of data exchange schemas among ASD standards should be part of a dedicated activity NAGSMA 9 NATO UNCLASSIFIED

  10. S3000L Application Configuration Management and LSA: Prime/ Physical Breakdown ERP Integrator Air Entities Product (Physical) Breakdown Physical Breakdown Subs Ground Entities BEI BEI is utilised also as CI number for the CM  The BEI are managed within the LSA database that becomes the reference  database for both Physical and Functional Breakdown During Operation and Support, the “as Maintained” configuration need to be  managed The LSA database become the reference also for CM as it can manage various  types of breakdown For AGS, 2 different BEIs are used to manage Physical and Functional Breakdowns  NAGSMA 10 NATO UNCLASSIFIED

  11. AGS Life Cycle Overview AGS Program comprises of 2 phases: Acquisition Phase – AGS Core and Support Assets Acquisition  Operation and Support (O&S) Phase – I-ISS, ISS and Operations  AGS System Delivery NATO Ownership & Operation Initial In-Service Support In-Service Support Design Development & Steady-State 20 Years Production O&S MOB Infrastructure Delivery NAGSMA 11 NATO UNCLASSIFIED

  12. AGS Life Cycle Scenario Support performed by: • NATO Force • Support Agency NSPA Deployed Location Main Operative Base Support Contracts and Support Agreements to consider the Support Scenario and System Management: • AWC - DMS – Field Services – Change Management – KPIs – SLA - …….. NAGSMA 12 NATO UNCLASSIFIED

  13. AGS Life Cycle Scenario Life Cycle Management of System and Design & Development Support System Aiworthiness Materiel Support Waerhouse breakdown and Safety Technical Technical Configuration Analysis Publication Life Cycle Cost Management FMECA Support CSDB LOG FMEA Equipment Maintenance Engineering and Field Support Logistic Services SMA Personnel and database (MSG-3, RCM) Training Support Personnel and Performances Training Infrastructure MTA (KPI) and Facilities Infrastructure SW Support Supply Chain Software and Facilities Analysis Support Assets Software Deployment and Support Planning NAGSMA 13 NATO UNCLASSIFIED

  14. S-Series Implementation Consideration  The S3000L is considered very powerful but still difficult to be implemented. From User prospective, suggestion for improvement are:  To include Validation rules for data imported/migrated  To include a Business Process for its implementation  To include a mapping of DEDs among S3000L and the main used standard for LSA (1388/DEF STD)  Integration among the ASD standards is not complete. To be able to use them it is essential to develop common data exchange schema  It would be useful to define the validation rules also for the data used and exchanged among different ASD standards databases NAGSMA 14 NATO UNCLASSIFIED

Recommend


More recommend