Link 16 Infrastructure (A very brief overview) Briefing to IDLS 2007

Transcription

1 Link 16 Infrastructure (A very brief overview) Briefing to IDLS 2007 David Clarke Technical Manager perational SyntheSys St. Hilda s Business Centre Whitby North Yorkshire Y22 4ET T: +44 (0) F: +44 (0) E: david_clarke@synthesys.co.uk W:

2 Acquisition, management and sustainment of a TDL capability requires a supporting infrastructure that provides support at all levels and gives the appropriate direction to ensure a cohesive, integrated and system-centric capability that meets national and international needs

3 Context Briefing based on Extensive Link 16 experience and expertise within the Company Current work for UK MD Studies carried out for UK MD, Swedish FMV and Danish AMC (now DAL) Current UK practice used to generate practical examples Not that it is perfect but it has been in use for some time and is evolving to best practice A VERY quick overview focusing on some key aspects only

4 Infrastructure M E T H D L G y M E T H D L G y

5 Restrictions Not possible within the timescales to cover all the aspects that are required to support a Link 16 capability Briefing timetable! Briefing will look at an overview of each element (hidden slides) Focus on following key aspects: and the relationship to specifications Configuration & Configuration Control

6 Methodology M E T H D L G y M E T H D L G y

7 Methodology Underpinning all is the methodology or the processes used Traditional we have created bespoke processes to address TDLs in the misguided view that TDLs are unique In fact they are just information exchange systems with both hard and soft interfaces, exactly is in the commercial arena The lesson to be learned is that perfectly adequate and proven commercial practices can be applied to TDLs Standard systems engineering practices Application of systems engineering practices allows for I assurance to be applied at all levels in a systematic and coherent fashion We ll see how that can be applied as we go through

8 M E T H D L G y M E T H D L G y

9 is the core on which the whole infrastructure is built should ensure that correct direction and information will be provided to form a robust infrastructure We will go into policy and how its feeds standards and specifications later

10 and doctrine are the bedrock of a TDL infrastructure Doctrine provides the overall aim and policy provides the direction to get there In the TDL arena, doctrine is provided at the upper echelons of government Defence From that flows policy TDL policy Link policies The Link 16 policy is more than a CNPS It is an integrated suite of sub-policies

11 Subordinate Policies The Joint Link 16 CNPS should mandate a series of subordinate policies covering: engineering approach Technical management Data management Configuration management Interface management Safety management Electromagnetic environment effects and spectrum supportability Training Integrated logistics support Recording and Analysis

12 CNPS Key aspects of a Link 16 CNPS Joint Provides a system-centric (system of systems) approach A CNPS Interprets, describes, and refines national defence policy and doctrine to provide a common frame of reference that guides and informs platforms on their TDL implementation. Describes a nation s aspirations for international operations and, as such, provides guidance on interoperability requirements. Provides the basis for a system-of-systems approach to platform implementation and facilitates the identification of IRs and IERs Be an integrated element of the systems engineering approach Lower level documentation provides the platform requirements These flow directly from the Link 16 Joint CNPS

13 IS System Specification Paradigm User Requirements System Requirements Subsystem Requirements Integration Tests System Tests Acceptance Tests Module Requirements Module Tests Implement

14 Application to TDL System of CNPS System URD Validation System Acceptance System SRD System STS Traceability Matrix System ADD System ATS SSDD

15 Flow Verification NEC TDL CNPS DTDL- IRS Standards MIL-STD MIL-STD Validation P-Specs MIL-STD MIL-STD Networthiness Contractor Platform FAT Data Link Acceptance Platform SAT Network Acceptance perational Acceptance Acceptance Compliance

16 M E T H D L G y M E T H D L G y

17 All successful Link 16 infrastructures have a robust top down organisation that Addresses the issues raised in the various policy documents Enables the management function of the TDL capability at both system and platform level Is Joint Provides interfaces with the international community

18 JTDLA Top level Defence Command body Joint TDL Authority incorporating 3 key roles Programme Manager perational Capability Manager Design Authority Key outputs would be Policies and concepts of use Support to operations Input to procurement and sustainment processes All subsequent organisation flows from the JTDLA

19 Generic Link 16 Structure Joint TDL Authority Command level Tactical Commands User Groups Joint Network Design Procurement Joint Data Link perations Centre Test and Evaluation Support Commands Joint Network HQ level Unit Groups System CC Standards CM Platform CC Unit level

20 Support to JTDLA Any Link 16 organisation works through complex of meetings, some virtual but most real The meeting structure involves both national and international It is the international interfaces that will provide the most benefit to assuring Interoperability

21 International Link 16 Meetings Terminals and associated software/firmware MIDS International Review Board (MIRB) JTIDS International Configuration Review Board (JICRB) Implementation and Interoperability Working Group (I&IWG) Message standards NAT Data Link Working Group (DLWG) Network Sub-Group (NMSG) Implementation testing I Requirements, Testing and Support Working Group (IRTSWG) Tactical Data Link I Testing Syndicate (TDLITS)

22 International Link 16 Meetings perational forums Coalition Warrior I Demonstration (CWID) JTIDS Frequency Spectrum Multi-National Working Group (MNWG) and European JTIDS/MIDS Cross- Border Coordination Meeting (EJCC) Strategic Commanders Advisory Panel on Data Link (SCAPDLM) Multi-Link Users Conference Major Exercises Symposiums International Data Link Symposium (IDLS) NAT Tactical Data Link Symposium (NTDLS)

23 Meeting Inter-relationship MIRB I&IWG Implementation data DLWG Issues of interest to both terminal communities JICRB NMSG CWID ften co-located NM information SCAPDLM IRSTWG MNWG Multi-Link Users Conference TDLITS EJCC

24 Typical National Link 16 Meetings TDL JTDLA Tactical User Groups (UK examples) HQ lead JTIDS perational Sub-Working Group Focus on users at the system level Group/platform lead JTIDS User Group Focus on specific platform issues Network Network Steering Group (UK example) Focus on UK network design and problem issues Testing and evaluation Standards maintenance - CM (UK examples) TDL CCB System and platform maintenance -CC (UK examples) TIDS CCB TPEG

25 Meeting Support to JTDLA TDL Board DLWG TDL CM Meeting TDL CC Meeting MIDS/Link 16 Testing National perator s Forum MIRB/MIDS IP JICRB TDL Network Meeting TDLITS NMSG EJCC

26 M E T H D L G y M E T H D L G y

27 Typical activities include: Test and evaluation Whole life test planning I management Certification/accreditation Configuration management (CM) Standards Implementations (CC) In-service support Network design Network management Security management Crypto management Risk management Training Concentrate on standards and implementation maintenance

28 Standards and Implementation Maintenance Definitions Configuration (CM) of message standards CM process focuses on standards and documents Configuration Control (CC) of MIDS terminals, associated firmware/software and implementations CC process focuses on systems Aspects of CM to manage system documents

29 CM Issues Maintenance of MIL-STD-6016 Any associated national/platform documents Interaction with international community Degree of interaction Full Guardians of the Interface Targeted National interest Watching Nil Standards management

30 CM Supporting Structures Decision making body Established by TDL CM policy Expert technical advice Link 16 Platform implementation Controlling agency versight Audit trail

31 Typical CM Process Change Proposal Review Change Proposal Determine impact Prepare national position Submit national position System Platforms Apply implementation CC Amend national documents

32 Example - UK Standards Source DLWG Nation UK DLCP or Revision Initial Analyses IA6/contractor Distribution for comment FRIA FSR SPIA Response if not agree TSEN Response? All platform review meeting TDL CCB UK position input to DLWG UK Position DLWG DLCP DLCP Approved IDLS Withdrawn Stand 311

33 CC Issues Aims Possess and use accurate MIDS terminal, associated firmware/software and implementation states to maximise I. Record and resolve MIDS terminal, associated firmware/software problems Record and resolve MIDS implementation problems to obtain maximal operational performance from MIDS/Link 16-equipped platforms. Allow intelligent interaction with the equipment provider in this instance, the MIDS IP Implementation

34 CC Supporting Structures Decision making body Established by TDL CM policy Expert technical advice MIDS terminal Platform implementation Controlling agency versight Audit trail

35 Typical Implementation Process - 1 Record implementation Manage change Problem Report (PR) Terminal upgrade

36 Typical Implementation Process 2 Manage Change Platform internal PR Problem Report (PR) Record PR Assess PR for I impact I PR Platform - fix or accept Fix System fix or accept Update PR database Update platform implementation records Raise Change Proposal? Record I issue

37 UNCLASSIFIED Example - UK CC Structure TIDS CCB ( Platform & System CM) 2 - T Y P H N N I M R D R1 * N I M R D M R A 4 A S T R A T / A A R / F S T A S E N T R Y E-3 T R N A D F3 N M S R N F L E E T S K A S a C * A M G R A P / A M R A P TPEG SUB-GRUPS * T R N A D G R 4 * H A R R I E R G R 9 ARMY RAF RN Single Service/ Platform CM s * L E A P P * R N T 45 R N M W S & F Extraordinary TPEG

38 Example - UK Top Level CM/CC NEC/ISR1* SC NAT C3B DLNAA NAT DLWG NAT (eg. TDLITS) TDL CCB (Message Standards & Data Link Protocols) TIDS CCB (Platform & System CM) INTERNATINAL (eg. JICRB/MIRB) UK (eg. PECCB) Single Service/ Platform CM s RN/ARMY/RAF/DE&S

39 M E T H D L G y M E T H D L G y

40 The MIDS system consists of Hardware Terminals Platforms Host implementations Engineering support Initialisation Data Preparation Facilities Network design, planning and management tools Cryptographic devices and keys Test tools Rigs SIMPLE interface units Standards Conformance tools Interoperability assessment tools Software MIDS terminal software/firmware Platform host software CM/CC supporting databases Training Rig CBT

41 System Documentation Standards Specifications Policies and other directives Standard perating Procedures Training Manuals Test scripts I assessments Structures JTDLA Subsidiary organisations JDLC CM CC Test & Evaluation Procurement Training Unit level

42 System Personnel and command Procurement perational Meetings National International support All form the MIDS system and must be catered for, managed and maintained as a system within the framework established by policy and supervised by the JTDLA

43 A quick run through what constitutes a MIDS/Link 16 infrastructure Key issues Joint approach System-centric approach Founded on a policy suite Managed from the highest level Underpined by supportable, standardised management techniques and engineering practices

44 Questions

45 Further

46 Infrastructure M E T H D L G y M E T H D L G y

47 This functional area covers the management techniques that can be applied to TDL management Using the same principle from the Methodology slide that a TDL (Link 16) can be viewed as an information system and standard commercial practices and processes applied Two examples will be given, covered again only as an overview PRINCE engineering models for acquisition

48 PRINCE as Applicable to TDL NT a lesson in PRINCE PRINCE is a general purpose project management method that can be utilised for management of any type or size of project. It is compatible with BS and is supported by the Central Computer and Telecommunications Agency (CCTA) and the Association of Project Managers (APM). Day-to-day system management Programme Executive JTDLA Programme Manager Capability Manager Design Authority

49 Design Authority This role is that of a senior engineer and, as such, the key activities are to: Develop and maintain the MIDS / Link 16 System design, including: Establish the System design. Ensure that the System design is suitable for inservice operation. Maintain the integrity of the System design throughout the engineering life-cycle. Ensure consistency of system products and subsystems (e.g. platform JTIDS / MIDS systems) with the design. Preparation, maintenance, and custody of specifications, drawings, and other data associated with the design of the system.

50 Design Authority Provide technical support to systems engineering management processes. Establish a Design Authority infrastructure, including: Inclusive representation of stakeholders involved in all life-cycle processes. Mechanisms for reporting and discussing issues, both internal and external to the Interoperability Directorate. Conduct regular System Design Reviews (SDRs). These take a system-of-systems view and ensure that a coherent perspective is maintained as the system-of-system evolves.

51 Common SE Models Waterfall Model System Definition Analysis Design Fabrication Testing Maintenance

52 Common SE Models Prototyping Requirements Gathering Quick Design Refine Requirements Engineer Product Build Prototype Customer Evaluation

53 Common SE Models Spiral Planning based on customer comments Initial requirements gathering and project planning Plan Initial Capability Toward a Completed System Assess (Customer Evaluation) Act (Engineering) Second Capability Customer Evaluation JDN Backbone DSDM (UK) Third Capability