UNCLASSIFIED MILCIS Session 2.5b Land Network Integration Centre (LNIC) Update 13 Nov 13

Size: px

Start display at page:

Download "UNCLASSIFIED MILCIS Session 2.5b Land Network Integration Centre (LNIC) Update 13 Nov 13"

Corey Collins
5 years ago
Views:

1 UNCLASSIFIED MILCIS 0 Session.5b Land Network Integration Centre (LNIC) Update Nov Mr Adam Mead Contractor to the Commonwealth Land TDL Manager / Land URN Manager Army Headquarters Scope Role of the (LNIC) The LRN Introduction to VMF URN Management and the role of LNIC GN TDL Planning Configuration Control Note: Unclassified nature prevents some discussion

2 Network Integration Challenge The Problem The Network is a System, but hasn t been developed as a system Lack of architecture at the start Lack of coordinated capability delivery Focussed on specialist services/applications, Not how they exchange information No balance between applications/services, bearers and network devices (capacity) Understanding requirements 4

3 The Problem Multiple network segments and security domains Data dissemination between strategic services (DSN) and tactical services (BMS) Currently no bridge between these segments to share information Access to coalition networks Many different functions With their own information requirements No application delivers all the functions 5 LAND NETWORK INTEGRATION CENTRE 6

4 Need for an LNIC Need to understand the problem and the solutions learn by doing is most effective better understand our requirements and the shortfalls in capability Ability to reduce the risk in decision making Need to integrate as part of design (not post design) More complexity means greater management responsibility (at highest level) 7 LNIC s Role Inform Army s networking decisions and support the development of Army s Land Network Capability. 8 4

5 Organisation ARMY HEADQUARTERS CA DCA CCMA PCHAP-A HMSP-A COFS DGRES-A DGMOD-A DGSP-A DESD-A LNIC 9 LNIC Effects Develop Land Network Capability Manage Land Network Capability Inform Land Network Development Integrate and Support Land Network Capability 0 5

6 Develop Land Network Capability Spt to Operations Build networks to fulfil OURs ODEN/ODEN-E BLOS OUR Ongoing training and support Land Reference Network - Learn by doing More on this later. Manage Land Network Capability Network Configuration Control URN Management VMF / tactical messaging implementation EPLRS Plan One Army Plan 6

7 Inform Land Network Development Inform requirements Learn by Doing Trials and demonstrations TDMA SATCOM Network access control Troposcatter MANET networks Coalition interoperability testing Develop networking concepts Integrate and Support Land Network Capability Integrate delivered capabilities Fix the here and now Take network-wide approach, focussing on information exchanges Alternate interfaces Develop Mission Secret Network Support networking activities Maintain niche networking capability 4 7

8 What is the LRN? Army s effort to define the future network Transform conceptual into practical ( learn by doing ) Directed task to build a reference network to investigate the required : Services Network devices Bearers Concentrating on the Deployed Land Place in the Network (BG to Div) Evolutionary development ( month dev cycle) Dangerously close to delivering capability 5 Gaps identified No coherent Network No mechanism to share information between strategic/operational planners (DSN) and tactical elements (BMS). Drive to host warfighter apps on DSN Adhoc arrangements for sharing coalition information at tactical level Integration of various tactical systems (BMS) is piecemeal, with no platform (networking device) to conduct integration. Capacity at the Tactical Edge COALTIO N Strategic Services DSN DRN? Tactical Systems 6 8

9 Need for a Mission Secret Network Single network domain to host warfighter applications Trusted Network devices and information exchange bearers to support CP based (LAN) and COALTIO mobile users N Prov a platform to integrate applications Prov trusted interface points to DSN and Coalition Rel domains Strategic Services DSN DRN MISSION SECRET NETWORK 7 Core Messages. Current Cap Dev process doesn t work for networking systems Too slow for technology cycle Unitary purchase with long LOT vs rate of technological advancement Piecemeal approach produces unfunded gaps Lack of integrated solutions. De-synchronised DCP all too common 8 9

10 Core Messages. Learn by Doing provides an alternate method Evolve the capability Origin of LRN 4. Often poorly defined requirements for CIS components of projects 9 Variable Message Format and Unit Reference Number Management 0 0

Variable Message Format (VMF) Predetermined message format Share digital tactical data (C, SA, Fires, log, Int) between systems Common standard used by major allies for message level interoperability

11 Variable Message Format (VMF) Predetermined message format Share digital tactical data (C, SA, Fires, log, Int) between systems Common standard used by major allies for message level interoperability HEADER BODY MIL-STD MIL-STD To Eg. K05. Position Report From Entity Priority Latitude / Longitude SEC Class Altitude / Elevation etc Speed Direction MIL-STD 88-0 Multi National Experiment 0 Coalition Picture

12 Why Variable Message Format? Common standard Used by major allies More countries moving towards VMF Proven success for interoperability in coalition operations Whether VMF exchange is the most appropriate depends on the situation. Success will be a golf bag approach to interoperability options. Other data exchange options available include; -XML -MIP -USMTF/ASMTF Unit Reference Numbers (URN) Used in VMF interface Globally unique Assigned by Role (some exceptions) Assigned to HQs, CPs, platforms and individuals using VMF systems ORBAT + IERs = Data Product (creates address book) HEADER MIL-STD BODY MIL-STD To (URN) From (URN) Priority SEC Class etc Eg. K05. Position Report Entity (URN) Latitude / Longatude Altitude / Elevation Speed Land Network Integration Direction Centre 4

13 K05. K0. URN Case. How does the URN work? Intent: Save bandwidth on data exchange by transmitting URN rather than all data stored in the look up table (Unit Long Name / Unit Short Name / Service / Nationality / MIL-STD 55 Symbol Code). URN URN Commanding O CO 5 RAR A AS SFG-AS.. URN Commander st... CMDR Bde A AS SFG-U- URN4 URN st Health Combat Sup S... CSR HSB Ops Ops A AS SFG-U-s. SFG-E.. URN5 URN4 7 th Health Combat Sup 7CSSB HSB Ops Ops A AS SFG-U-s. URN456 Key: Common look up tables from accurate data products K0. Case.. URN789 5 URN Management Philosophy - Data Products LNIC create and manage a range of data products Specific to Ex / Op / Acty Specific to System being loaded (type of file / fields req d etc) Tech management exists to Unit level MOUs in place for LNIC to manage RAN and RAAF URN requirements Accurate Data Products result from accurate ORBAT and IERs Permanent URNs are assigned to roles and platforms, by system Spare URNs are allocated to formations, for temporary assignment Uncontrolled URNs are for use in training rooms, labs, demos etc LNIC will release all URN data products via SharePoint All URNs used MUST BE AUTHORISED for use 6

14 Current URN Management Issues Initial URN assignment takes considerable resources Lack of understanding by POs of the importance of data products Conflict exists between Unit entity names vs BG/CT constructs Long lead times for some system data products Insufficient coalition standardisation Eg MIL-Symb, naming conventions etc US Joint URN Repository not effectively used has a large number of negatives for Australia 7 GN TDL Planning Understand the difference between Network capabilities and application interoperability capabilities Can the required networks connect Physical / Technical / Security implications Understanding of system interoperability What is / is not possible MIL-STD versions inherent within the systems Messages employed Message sets required in message threads to execute an operations event Understanding latency between systems 8 4

15 GN TDL Planning Coalition Interoperability JOC responsibilities vs LNIC responsibilities URNs may remain extant Naming conventions / deploying forces / type of deployment The Multi-TDL Network (MTN) Army positions within JICC What does Land require from the MTN? What does Land need to contribute to the MTN? RA Sigs should be the TDL SMEs within Army RA Sigs is currently unprepared in many aspects Current lack of a RLP and appropriate skill set 9 Configuration Control Concept Software versions do not remain static Difficult to approach CM across all systems Will be based on the Army endorsed architecture and IER requirements For a networked force, Army requires a configuration control authority assessing interoperability 0 5

16 Configuration Control Concept Does not replace current engineering rigor from within DMO Will align upgrades with other Army efforts Software will not be authorised for use within Army until approved by the configuration control authority Conclusion VMF is proven as current best means for tactical interoperability Lack of coordinated capability delivery Poorly scoped requirements results in poorly considered capability URN Data Products requires planning and ongoing management Feel free to engage and visit 6

17 7

UNCLASSIFIED. ADF Tactical Data Link Authority Ground Network Capability Assurance Services UNCLASSIFIED

UNCLASSIFIED. ADF Tactical Data Link Authority Ground Network Capability Assurance Services UNCLASSIFIED UNCLASSIFIED MilCIS 2013 TDL Stream, Session 2.5a ADF Tactical Data Link Authority Ground Network Capability Assurance Services Mr. Josh Roth Ground Networks Manager joshua.roth1@defence.gov.au 02 626