land battlespace communications interdisciplinary framework...
TRANSCRIPT
Electronic Systems Division – Communications Branch – Battlespace Communications SPO
Land Battlespace Communications
Interdisciplinary Framework for Architecture and
Engineering Development of Land Battlespace
Communications
by Dr Mansoor Syed@ MilCIS 2014, 13 November 2014
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
Presentation Introduction
1. Land Communications Development Problem Space
Systems Engineering perspective
ICT Perspective
Organisational Perspective/ Dilemma
Conclusions
2. BCS(L) Interdisciplinary Development Framework
Purpose, Scope, and Key Risks
Development Methodology
Development Process and Deliverables
Development Key Building Blocks
Product (End State) Realisation
Process Control
3. Q&A
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
1. Land Communications Development Problem Space
1.1 Systems Engineering Perspective
1. Project JP2072 is required to provide an integrated Battlespace Communications System (Land) (BCS(L).
2. BCS(L) collectively represents a System-of-Communications systems providing Voice, Data and Video services in Deployed Land Battlespace.
3. BCS(L) is delivered in predefined nodal construct in mounted and dismounted configuration.
4. BCS(L) interfaces with User Applications, Platforms (Land, Maritime, Air), Strategic Networks, Joint and Coalition Networks, Public Information Networks, Defence Information Networks, to name a few.
5. The System and Communications systems are required to be specified, verified and repeatedly delivered in nodal construct. Typically, ASDEFCON Complex 2 or higher, EIA-632 Systems Engineering process and Regulatory Framework TRAMM-L are applicable.
S UPPORT S YSTEM
TACSAT
R ANGE E XTENSION S YSTEM
TDRS (WB - LOS)
CNRS (NB - LOS)
L OCAL AREA S YSTEM
Switching System
Battlefield Transmission System
T ACTICAL C OMMS N ETWORKS B ATTLEFIELD T ELECOMMS N ETWORKS
Security Framework
Network Management
Phase 2BPhase 1 and Phase 2A
Phase 3 (Including tech refresh)
TACTICAL DATA SYSTEM
COMBAT RADIO SYSTEM
BATTLESPACE COMMUNICATIONS SYSTEM (LAND)
NETWORK MANAGEMENT
Phase 2BPhase 1 and Phase 2A
Phase 3 (Including tech refresh)
PERSONAL
RADIO
SYSTEM
SUPPORT SYSTEM
LOCAL AREA SYSTEM (inc. DLAN)
SWITCHING SYSTEM
BATTLEFIELD TRANSMISSION SYSTEM
BATTLEFIELD TELECOMMS NETWORKS
RANGE EXTENSION SYSTEM
TACTICAL COMMS NETWORKS
SECURITY FRAMEWORK
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
1. BCS(L) manifests itself in a Deployable Communications Network Infrastructure that will enable discrete Information Capabilities in the Land Battlespace environment.
The diagram is an Australianised version of the Future Combat Systems (FCS) Brigade Combat Team (BCT) Network diagram described on http://en.wikipedia.org/wiki/FCS_Network
1. Land Communications Development Problem Space
1.1 ICT Perspective
2. The Deployable Communications Network Infrastructure is built upon Communications, Network and Applications layers to enable Secured Information Services for the Users.
3. The Deployable Communications Network collectively represents Network-of-Networks formed by nodes. The networks are to be planned, managed and supported to enable required Information Services.
4. The Network interfaces with Strategic Networks, Joint and Coalition Networks, Public Information Networks, Defence Information Networks, to name a few.
5. The Network is required to be developed using ICT Architecture discipline and mapped to higher architectures/ ICT guidance (NBA, BTIA, PIN, SIE). Typically, DoDAF development process and ITIL are applicable. No Regulatory Framework.
SPECTRUM MANAGEMENTARCHITECTURE
INTEGRATION AND TEST FACILITY
COALITION INTEROPERABILITY
THEATRE BROADCAST
NETWORK
(Enablers)SIE
NGD
CYBER SECURITY
CROSS DOMAINDATA EXCHANGE
COMMUNICATIONS
LINK16
BTN TCN
CNRWGS
UHF TACSATHFTROPOSCATTER
LINE
PSTN
DTCNNBN
SIPRNETNIPRNET
BCS(M)
DSN
DRN
LINK11
LINK22
RADIO RELAY
VHF UHF
DLAN
PRE
TADILHC-TDREVMF
SDR
BASE RADIO
IRIDIUM
INMARSAT
JREAP
Battlespace Communications System (Land) BCS(L)
AIRMARITIME
UHF Satellite WGS SatelliteCHINOOK
AEWAC
JSF
MRH
ARH
BLACKHAWKInfantry BN
Artillery
Combat Engineer
MechanisedArmoured
Logistics Support
SF
CAV
UAV
UAV
InfantryCoy
InfantryCoy
BDE HQ
InfantryCoy
LHD
FFH
FFG
COALITION
SUBMARINE
C-130 C-17APOD/E
GBAMD
TELEMEDICINE
SITUATIONAL AWARENESS
APPLICATIONS
MILISPMKEYS MILITARY MESSAGING
BMS BMS-F
DTCS
COMMON OPERATING PICTURE
WEB SERVICES
IMAGERY
BMS-C2
BMS-AD
BMS-EW
STANDARDS
PROTOCOLS WNW
SRWAPCO-25
ANW2SCA 4.0
IPV4
IPV6
MANETSINCGARS
Hornet
SPECTRUM MANAGEMENTARCHITECTURE
INTEGRATION AND TEST FACILITY
COALITION INTEROPERABILITY
SPECTRUM MANAGEMENTARCHITECTURE
INTEGRATION AND TEST FACILITY
COALITION INTEROPERABILITY
THEATRE BROADCAST
NETWORK
(Enablers)SIE
NGD
CYBER SECURITY
CROSS DOMAINDATA EXCHANGE
COMMUNICATIONS
LINK16
BTN TCN
CNRWGS
UHF TACSATHFTROPOSCATTER
LINE
PSTN
DTCNNBN
SIPRNETNIPRNET
BCS(M)
DSN
DRN
LINK11
LINK22
RADIO RELAY
VHF UHF
DLAN
PRE
TADILHC-TDREVMF
SDR
BASE RADIO
IRIDIUM
INMARSAT
JREAP
Battlespace Communications System (Land) BCS(L)
AIRMARITIME
UHF Satellite WGS SatelliteCHINOOK
AEWACAEWAC
JSF
MRH
ARH
BLACKHAWKInfantry BN
Artillery
Combat Engineer
MechanisedArmoured
Logistics Support
SF
CAV
UAV
UAV
InfantryCoy
InfantryCoy
BDE HQ
InfantryCoy
LHD
FFH
FFG
COALITION
SUBMARINE
C-130 C-17APOD/E
GBAMD
TELEMEDICINE
SITUATIONAL AWARENESS
APPLICATIONS
MILISPMKEYS MILITARY MESSAGING
BMS BMS-F
DTCS
COMMON OPERATING PICTURE
WEB SERVICES
IMAGERY
BMS-C2
BMS-AD
BMS-EWTELEMEDICINE
SITUATIONAL AWARENESS
APPLICATIONS
MILISPMKEYS MILITARY MESSAGING
BMS BMS-F
DTCS
COMMON OPERATING PICTURE
WEB SERVICES
IMAGERY
BMS-C2
BMS-AD
BMS-EW
STANDARDS
PROTOCOLS WNW
SRWAPCO-25
ANW2SCA 4.0
IPV4
IPV6
MANETSINCGARS
STANDARDS
PROTOCOLS WNW
SRWAPCO-25
ANW2SCA 4.0
IPV4
IPV6
MANETSINCGARS
HornetHornet
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
1. Land Communications Development Problem Space
1.3 Organisational Perspective/ Dilemma
2013 2030
2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030
BCS(L) CAPABILITY SYSTEM – DEFENCE WIDE
BCS(L) PRIME
SYSTEM
JP2072 Wide
Phase 1, 2A, 2B, 3
BCS(L) REFERENCE ARCHITECTURE (ENTERPRISE, INFORMATION, SECURITY)
TC
N M
OU
NT
ED
Ma
terie
l S
yste
ms
TC
N D
ISM
OU
NT
ED
Ma
terie
l S
yste
ms
BT
N
Ma
terie
l S
yste
ms
JP2072 Area of Influence
BCS(L) PRIME
SYSTEM
JP2072 Wide
Phase 1, 2A, 2B, 3
BCS(L) PRIME
SYSTEM
JP2072 Wide
Phase 4
BCS(L) PRIME
SYSTEM
JP2072 Wide
Phase 1, 2A, 2B, 3
BCS(L) PRIME
SYSTEM
JP2072 Wide
Phase n
TC
N M
OU
NT
ED
Ma
terie
l S
yste
ms
TC
N M
OU
NT
ED
Ma
terie
l S
yste
ms
TC
N D
ISM
OU
NT
ED
Ma
terie
l S
yste
ms
TC
N D
ISM
OU
NT
ED
Ma
terie
l S
yste
ms
BT
N
Ma
terie
l S
yste
ms
BT
N
Ma
terie
l S
yste
ms
BCS(L) Architecture, Capability and Engineering Ownership Oulook
JP2072 Materiel Systems
JP2008 Materiel Systems
JP2047 Materiel Systems
JP2089 Materiel Systems
Notes:
1. The diagram is conceptual only. The time line is not exact.
2. The BCS() Prime System is an Evolving Construct made of
discrete acquisitions from JP2072 Phases
3. The PSI is responsible for the interfaces of the BCS(L) Prime System with
other materiel systems contributing to and/or part of BCS(L) Defence - wide
BCS(L) CDD BCS(L) CDDBCS(L) CDD
CIOG/ Capability Manager Ownership
DMO/ JP2072 Ownership
CDG Ownership
Capability Manager Ownership
Legend
JP2072 Phase
Responsibility
Land 200 Materiel Systems
Land 400 Materiel Systems
JP2048 Materiel Systems
SEA 1442 Materiel Systems
CISSO Materiel Systems
JP2072 PSI
Responsibility
JP2072 PSI
ResponsibilityJP2072 PSI
Responsibility
JP2072 PSI
Resposnibility
DMO/ JP2072 Ownership for Development & Configuration Management
DAEF / PIN
DSecA
NBA
IDA
BTIA
JP2072 Area of Responsibility
BCS(L) SYSTEM
ARCHITECTURE
for
PRIME SYSTEM
BCS(L) SYSTEM
ARCHITECTURE
for
PRIME SYSTEM
BCS(L) SYSTEM
ARCHITECTURE
for
PRIME SYSTEM
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
1. The System-of Systems / Network-of-Networks must be defined, specified, verified, and
delivered through a recognisable engineering process to ensure repeatable outcome,
ready for Technical Certification under TRAMM-L.
2. Engineering development could not be carried out only on the basis of typical Systems
Engineering. The ICT discipline must be embraced.
3. Processes, artefacts and outcome from traditional Systems Engineering and ICT
Architecture approaches need to be woven to guide the development process.
4. BCS(L) must, and has, embraced the shift from development of traditional military
Communications System to enduring and agile Communications Network Infrastructure
that enables Information Services in the Land Battlespace.
5. BCS(L) networks are to be built upon open interfaces allowing Communications,
Networking and Applications layers to be developed independent of each other. An
interface architecture needs to developed.
1. Land Communications Development Problem Space
1.4 Conclusions
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development
2.1 Purpose, Scope & Key Risks
Purpose:
To define and develop deployable Communications Network Infrastructure, that will enable discrete Information Capabilities in the Land battlespace environment.
Scope (Current):
Defence wide BCS(L) Reference Architecture (Business Architecture)
JP2072 wide BCS(L) Solution Architecture (Vendor Independent Solution)
JP2072 wide BCS(L) System Architecture (System and Operational Behaviour)
JP2072 wide BCS(L) Physical Architecture (Network System Design)
JP2072 wide BCS(L) Product Architecture (Recommended Product List)
Key Risks:
Unspecified end state
Legitimisation of children born before parents
Evolving BCS(L) Materiel System acquired through various vendors
System-of-systems integration (processes, data, materiel systems)
legacy and existing systems integration, phase-out and obsolescence
Capability interfaces (over 80 projects) and System interfaces
Technology evolution, and
most importantly System/ Network qualification
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.2 Development Methodology
BCS(L) Development is achieved through an interdisciplinary approach involving Architecture, CDD, Systems Engineering and Communications Engineering as applied to development of ICT systems, Communications systems, and large scale Defence systems.
Standards and Tools : (DoDAF-V2.02, WSAF, EIA 632) using (System Architect, CORE and DOORS)
Development Stage 1 is comprised of development and alignment of:
Business Reference Architecture (Capabilities – Activities – Business Services)
Capability Interface Definition (Capability System Interfaces, 8/80 projects)
Capability Definition (Integrated OCD/FPS/TCD)
System Definition (Materiel System, Support System, Materiel System Interfaces, Nodes, Security System, Comms Network System, Network Planning & Management System, HMI System, Spectrum, IP Addressing, Middleware).
Development Stage 2 is comprised of development and alignment of :
Solution Architecture (Tech Services – Vendor Independent Solution Patterns)
System Architecture (System Services – Behaviour Patterns - Functional Systems)
System Specifications (SSS, IRS, SSSPEC, HMISPEC)
Development Stage 3 is comprised of development and alignment of :
Physical Architecture (Communications Network System Design)
Product Architecture (Communications Products Recommendations/ Standardisation)
Technical/ Product Specifications / Recommended Product List
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.3 Development Process & Deliverables (Arch & Eng)
BCS(L) System Development Process – Definition Level Maturity
R
efe
ren
ce
Arc
hite
ctu
re a
nd
Ca
pa
bili
ty D
efin
itio
n L
og
ica
l S
olu
tio
n fo
r S
yste
m o
f S
yste
ms (
So
S)
L
og
ica
l S
olu
tio
n fo
r S
ub
-Syste
ms
Sub-system specification
and design follows the same
process as the SoS, for each
Sub-system specified in the
BCS(L)
INTERFACE
REQUIREMENTS
SPECIFICATIONS
OTHER
SUBSYSTEMS
NETWORK
CENTRIC
WARFARE
INITIATIVES
HUMAN MACHINE
INTERFACE
SPECIFICATIONS
BCS(L)
NETWORK
ARCHITECTURE
DESCRIPTION
BCS(L)
ENTERPRISE
ARCHITECTURE
DESCRIPTION
NETWORK & SYS
MANAGEMENT
DEFINITION
DESCRIPTION
SUPPORT
SYSTEM
SPECIFICATIONS
BCS(L)
SECURITY
ARCHITECTURE
DESCRIPTION
IP ADDRESSING
SCHEME
DEFINITION
DECSRIPTIONBCS(L)
COMMUNICATION
ARCHITECTURE
DESCRIPTION
INTEGRATED
DEFENCE
ARCHITECTURE
(IDA)
MIDDLEWARE
DEFINITION
DESCRIPTION
DEFENCE
ARCHITECTURE
ENGAGEMENT
FRAMEWORK
BCS(L)
TEST CONCEPT
DOCUMENT
(TCD)
REQUIREMENTS
ALLOCATION
INTEGRATED BATTLEFIELD
TELECOMMUNICATION
NETWORK (iBTN)
SPECIFICATIONS
SINGLE
INFORMATION
ENVIRONMENT
(SIE)
MISSION
SYSTEM
SPECIFICATIONS
NETWORKED
BATTLESPACE
ARCHITECTURE
(NBA 2020 +)
SYSTEM
SECURITY
DEFINITION
DESCRIPTION
UMBRELLA
OPERATIONAL
CONCEPT
DOCUMENT
COMMS & NW
DEFINITION
DESCRIPTION
CONCEPT OF
OPERATIONS
(CONOPS)
OPERATIONAL
CONCEPT
DOCUMENT
(OCD)
TACTICAL COMMUNICATION
NETWORK SPECIFICATIONS
SPECTRUM
MANAGEMENT
DEFINITION
DESCRIPTION
DEFENCE
CORPORATE
ARCHITECTURE
(DCA)
NODES ENG &
MATERIEL
DEFINITION
DESCRIPTION
BCS(L)
CAPABILITY
INTERFACE
DESCRIPTION
MATERIEL
SYSTEM
DEFINITION
DESCRIPTION
FUNCTION &
PERFORMANCE
SPECIFICATION
(FPS)
HUMAN
MACHINE
DEFINITION
DESCRIPTION
SUPPORT
SYSTEM
DEFINITION
DECSRIPTION
INTERFACE
DEFINITION
DESCRIPTION
BCS(L)
INFORMATION
ARCHITECTURE
DESCRIPTION
BCS(L) System Development Process – Design Level Maturity
R
efe
ren
ce
Arc
hite
ctu
re a
nd
Ca
pa
bili
ty D
efin
itio
n S
yste
m S
olu
tio
n fo
r S
yste
m o
f S
yste
ms (
So
S)
NETWORK
CENTRIC
WARFARE
INITIATIVES
SPECTRUM
MANAGEMENT
DESIGN
DESCRIPTION
NODES ENG &
MATERIEL
DESIGN
DESCRIPTION
SUPPORT
SYSTEM
SPECIFICATIONS
NETWORKED
BATTLESPACE
ARCHITECTURE
(NBA 2020 +)
HUMAN MACHINE
INTERFACE
SPECIFICATIONS
MISSION
SYSTEM
SPECIFICATIONS
BCS(L)
COMMUNICATION
ARCHITECTURE
DESCRIPTION
INTEGRATED
DEFENCE
ARCHITECTURE
(IDA)
NETWORK & SYS
MANAGEMENT
DESIGN
DESCRIPTION
BCS(L)
CAPABILITY
INTERFACE
DESCRIPTION
DEFENCE
ARCHITECTURE
ENGAGEMENT
FRAMEWORK
BCS(L)
SECURITY
ARCHITECTURE
DESCRIPTION
MATERIEL
SYSTEM
DESIGN
DESCRIPTION
UMBRELLA
OPERATIONAL
CONCEPT
DOCUMENT
SYSTEM
SECURITY
DESIGN
DESCRIPTION
DEFENCE
CORPORATE
ARCHITECTURE
(DCA)
MIDDLEWARE
DESIGN
DESCRIPTION
SINGLE
INFORMATION
ENVIRONMENT
(SIE)
BCS(L)
INFORMATION
ARCHITECTURE
DESCRIPTION
BCS(L)
ENTERPRISE
ARCHITECTURE
DESCRIPTION
INTERFACE
DESIGN
DESCRIPTION
COMMS & NW
DESIGN
DESCRIPTION
BCS(L)
NETWORK
ARCHITECTURE
DESCRIPTION
IP ADDRESSING
SCHEME
DESIGN
DESCRIPTION
INTERFACE
REQUIREMENTS
SPECIFICATIONS
EMC/ EMI
ANALYSIS
TECHNICAL
SPECIFICATIONS
x n
SUB-SYSTEM(S)
IRS X n
FMECA
SYSTEM SAFETY
HAZARD
ANALYSIS
RMA ANALYSIS
SYSTEM SAFETY
CASE REPORTS
DEVELOPMENT / PROCUREMENT /
IMPLEMENTATION / INTEGRATION
SUPPORT
SYSTEM
DESIGN
DESCRIPTION
HUMAN
MACHINE
DESIGN
DESCRIPTION
FUNCTION &
PERFORMANCE
SPECIFICATION
(FPS)
BCS(L)
TEST CONCEPT
DOCUMENT
(TCD)
CONCEPT OF
OPERATIONS
(CONOPS)
OPERATIONAL
CONCEPT
DOCUMENT
(OCD)
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
10
2. BCS(L) - Interdisciplinary Development Approach
2.3 Development Process & Deliverables (Architecture)
System Architecture
Refe
ren
ce
So
luti
on
Sys
tem
s
Ref DoDAF2.02
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.3 Development Process (System Behaviour Analysis)
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
12
2. BCS(L) - Interdisciplinary Development Approach
2.3 Development Process (Entities & Layers Alignment)
System Architecture
Solution Architecture
System Architecture
Solution Architecture
Higher Level Reference Architectures / Guidance/ Doctrine
Reference Architecture
BTIA NBA
Services (Business)
Systems
Operational ActivitiesInformation Classes
Capabilities1. Comms and Computer Support
2. Enabler C2
3. Enabler Joint Fires
4. Enabler ISR……
References
Conceptual Information DIV-1Logical Data DIV-2
Operational Information/Data
Flows between Activity
Nodes (OV-3)
Logical Data (DIV-2)
Physical Data (DIV-3)
Operational Information/Data
Flows between Activity
Nodes (OV-3)
Information/Data Flows
between Services (SvcV-2/6)
Detailed Logical Data (DIV-2)
Physical Data (DIV-3)
Detailed Data Flows from and into
System (SV
-
2/6)
Detailed Data Flows between(SvcV 2/6)
Data to Services definition
(SvcV-3A/B).
CDF Prep Directive
‘Defend Australia’
Services (Bus - Technical)
Systems
TCN, BTN, Satellite Network
Operational Activities
Services (Technical)
Operational Activities
ADDP
ADDP + CONOPS
Comms Services
Network Services
Information Enabling Services
Organisation1. Force Node
2. Formation Node
3. LO Node
4. CO Node……
CONOPS/ OCD Annex A
Information Classes
Information Flows
Data Flows
Comms Services
Bearer Svs
Network Services
Network Planning & Management Svs
System Management Svs
Bearer Svs Voice, Data, Video Svs
Network Planning and Management SvsNetwork Planning Svs
Network Management Svs
System Management SvsNetwork Switching Svs Network Control Svs
Documentation
Defence: Policy, Directives
BCS(L) Architecture Descriptions:
EAD, CAD, NAD, IAD, SecAD, CID Defence Wide / Portfolio
Program / Project
Project
Information Classes
Information Flows
Capabilities1. Comms and Computer Support
2. Enabler C2
3. Enabler Joint Fires
4. Enabler ISR……
Capabilities1. Comms and Computer Support2. Enabler C2
3. Enabler Joint Fires
4. Enabler ISR……
JP2072, JP2008
JP2072
JP2072 Ph1
JP2072 Ph2A
JP2072 Ph2B
JP2072 Ph3
SystemsTCN:
TDRS, CNRS, HFRS, TSRS. PRS
EPLRS/ 152/152A/117G/RAVEN
Documentation
CDG: CDD (UOCD/ OCD)
AHQ : CONOPS, others
BCS(L) Eng Descriptions:
MSDD, IDD, NEMDD, CNDD, NSMDD, HMDD, SECDD, etc
Documentation
CDG: CDD (OCD/FPS/ TCD)
AHQ: CONOPS, others
Proj : SAD, SSDD, SSDESC, SSS, CONEX, DOORS,
CORE Model, SIM Model, etc
BCS(L) Bearer System
BCS(L) Network SystemBCS(L) Security System
Arch. Views
BCS(L) Architecture Descriptions:
EAD, CAD, NAD, IAD, SecAD, CID
LOS (WB, NB), BLOS (WB, NB)
Services
DAEF
Organisation1. Force Node
2. Formation Node
3. LO Node
4. CO Node……
Organisation1. Force Node
2. Formation Node
3. LO Node
4. CO Node……
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.4 Development Key Building Blocks
1. Business Services / Operational Needs
2. Vendor Independent Solution Patterns (Tech Services + Activities + Systems)
3. Capability Definition Documents (OCD, TCD, FPS)
4. System Definition Descriptions (Solution Patterns + FPS Requirements/ Tech
Services)
5. System Specifications (SSS, IRS, HMISPEC, SSSPEC)
6. System Functional Analysis /Behaviour
7. System Configuration Items development
8. System Design Descriptions (Communications Network Design)
9. Technical/Product Specifications
10. System T&E artefacts
11. Technical Data
12. System Design Acceptance and Technical Certification under TRAMM-L
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.5 Product (End State) Realisation
Mission Simulation System (MSS)
Mission Reference System (MRS)
Battlespace Communications
Support Centre (BCSC)
RES
OTHER
NETWORKS
COMMUNICATIONS SUPPORT CENTRE ORGANISATIONAL FUNCTIONS
Decision
Support
SYSTEM
DEVELOPMENT
MISSION REFERENCE SYSTEM ELEMENTS
SIMULATION SYSTEM FUNCTIONS
Test &
Evaluation
Learning &
Training
System
Analysis &
Development
iBTN with
DLAN
PLATFORMS
- Mounted
- Dismounted
TCN
USER APPS
- C2
- Corporate
- etc
NODES
- Mounted
- Dismounted
ENABLERS
- NPMS
- Waveforms
- Network Apps
- IT Systems
- etc
SYSTEM
INTEGRATION & TEST
MATERIEL SYSTEM
SUPPORT
BCSC FACILITIES
MANAGEMENT
OPERATIONS &
NETWORK(S)
SUPPORT
ARCHITECTURE &
ENGINEERING
GOVERNANCE
CoA ACTIVITIES
- Decision Support
- Product Standards
- Technology
- OT&E
BCSC OPERATIONS
MANAGEMENT
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
2. BCS(L) - Interdisciplinary Development Approach
2.5 Process Control
DEFINEINTEGRATE /
IMPLEMENTDESIGN/ DEVELOPSPECIFY T&E
Above-the-Line Below-the-Line
- Reference Architecture
- Capability Definition
- System Definition
- Solution Architecture
- System Architecture
- System Specifications
- Physical Arch /Sys Design
- Product Arch/ Standards
- Tech Specifications
- Intersystem Test
- Integration Test
- Install. Specifications
- System Test
- Acceptance Test
- Operational Test
CDR, SDR-1 SDR-2 PDR, DDR TRR TRR TRR TRRTRR
CCB CCBCCBCCB
DA TC
CCB
CDR - Capability Definition Review
LEGEND
SDR - System Definition Review
DDR - Detail Design Review
PDR – Preliminary Design Review
TRR- Test Readiness Review
CCB – Configuration Control Board
DA – Design Accepatance
TC – Technical CertificationNote: Each Engineering
Review/ Gate is preceded with
an Architecture Review
ESD –COMMS BRANCH - BCSPO JP 2072 – Enabling network-centric warfare for Australia’s Land Forces
Questions