Interoperability enabled by Communication and Information Systems (IO by CIS)

Put simply:

Systems, Units or Forces:
Who (The people or Systems)

To provide services to and accept services from:
What (Information Exchange)

Operate effectively together:
How Good (The Quality)

Use the services so exchanged:
Why (Reason and desired Effect)

Benefits and Contribution to Defence

IO enabled by CIS contributes to ‘Better Information Sharing’ and ‘Better Shared Understanding’. This in turn leads to better decisions, actions and effects.

Mandate

IO enabled by CIS management and assurance is mandated by the Vice Chief of Defence Staff (VCDS). It is mandatory for all UK MOD acquisition projects containing Communication and Information System (CIS) - regardless of financial approval category, lifecycle stage or operational theatre - unless agreed otherwise with the MOD Systems Engineering and Integration Group (SEIG).

Champion

The Systems Engineering & Interoperability Assurance (SEIA) team within SEIG acts as Champion of the subject.

Stakeholders
Key MOD stakeholders include:

• Head of Capability Desk Officers
• Requirements Managers
• Project Managers
• Project Interoperability Leads/Systems Engineers
• Project Integrated Logistics Support Managers
• Safety, Technology & Integration (STI) Leads
• Programme Support Functions (PSF)

Key Themes

IO enabled by CIS is about Managing the WHO, WHAT, HOW GOOD and WHY across the boundaries with other interfaced/interfacing projects.

This management manifests across the following key themes:

Theme 1 - Architectures, Requirements and Acceptance
Theme 2 - Management Boundaries and Interoperability Governance
Theme 3 - Interoperability (enabled by CIS) Management Through-Life

Topics

There are a total of 23 Topics within the 3 themes, many of which the project should be addressing as standard acquisition business. However, there may be an Interoperability aspect (activity or output) which the project must consider/manage.

For example: Address the ‘WHO, WHAT, HOW GOOD and WHY’ across the boundary for Security - not just the Project’s own Security.

Theme 1
• Concepts
• User Requirements
• System Requirements (Including MOD CIS Policy & Standards)
• Architectures
• Acceptance

Theme 2
• Stakeholders
• Business Agreements
• Implementation across Defence Lines of Development (DLODs)

Theme 3
• Interoperability Strategy and Implementation Plan (IS&P)
• Requirements Management
• Risk Management
• Acceptance Strategy
• Integrated Test, Evaluation and Acceptance (ITEA) Plan
• Security Accreditation
• Configuration Management
• Government Furnished Assets
• Investment Management
• Acquisition Strategy
• Procurement Strategy
• Transition Strategy and Plan
• Disposal Strategy and Plan
• Integrated Logistics Support Strategy
• Safety

IO enabled by CIS is a through-life consideration, with the greatest benefits gained from early application. The maturity of IO enabled by CIS management is currently measured over the CADM part of the CADMID lifecycle and is also aligned with the Systems Engineering lifecycle. The Project’s lifecycle stage will determine the activities required to ensure the IO enabled by CIS solution is adequately matured.

IO enabled by CIS must continue to be maintained and controlled through the Project’s In-Service Life. Considerations include:

• The impact of changes by other Projects/Services.
• The impact of your Project’s changes to other Projects/Services.
• The impact of the disposal of other Projects/Services.
• The impact of your Project’s disposal to other Projects/Services
• The impact of the Introduction of other Projects/Services.
• Architectural requirements and constraints imposed on increments of acquisitions.
• Backward compatibility of MOD CIS Policy and Standards.

Maturity Model

The 3 themes (and their underpinning topics) are mapped to the Systems Engineering timings to form an IO enabled by CIS Maturity Model (IOMM). The IOMM details what Project Teams ideally need to address in more detail, with each topic at each stage having multiple statements of what is required. These statements are essentially the same as the question-set used by the Assurance process (which is performed by SEIG).

Projects aim for all relevant statements to be true for their current (and any previous) stages to minimise IO enabled by CIS risks. However, every Project is different and the expectations of what should have been achieved (from an Assurance perspective) needs to be agreed between the project and SEIG.

Management

The following MOD management elements are required:

• An Interoperability Key User Requirement (IO KUR)
• An Interoperability (enabled by CIS) Strategy and Plan (IS&P)
• Participation in Interoperability (enabled by CIS) Assurance; including the application of relevant MOD CIS Policy and Standards

The Interoperability Strategy and Plan (IS&P) should:

• Predict the scope and complexity of the interoperability work-stream and issues that the acquisition is going to face.
• Direct, in outline, how the Project Team will manage that work-stream, and progress those issues.
• Identify how and when the predictions will be periodically refreshed in order to ensure their continuing validity.
• Describe in detail how the interoperability work-stream scoped in the Strategy will be managed in accordance with the direction in the Strategy.
• Describe in detail how interoperability requirements will be identified and complied with in accordance with MOD CIS policy.
• Describe in detail how the issues identified in the Strategy will be progressed to timely resolution.
• Give visibility and traceability of the totality of coverage of the subject throughout the TLMP document set, ensuring cohesiveness throughout.

Common Issues and Challenges with IO enabled by CIS Management

Issue 1     How and when interoperability requirements are identified.
Issue 2     Boundaries between Units, Forces, Information, Systems etc & implications.
Issue 3     Leadership and arbitration across boundaries.
Issue 4     MOD CIS Policy, and Standardisation.
Issue 5     CIS Standards.

Challenge 1 Managing the complexity of interdependencies.
Challenge 2 Managing complex multiple interfaces with a ‘System of Systems’.
Challenge 3 Conflicting different project drivers.
Challenge 4 Cross-Defence Lines of Development consideration and trading.
Challenge 5 Programme Management in pursuit of the delivery of Military Capability.

Interoperability Assurance

MOD SEIG does NOT provide an Assurance that the system being developed will be technically adequate or meet the requirement.

MOD SEIG provides IO enabled by CIS Management Assurance. This gives a level of confidence to the DE&S Investment Board, HOC CC&II (Core Head of Capability for C4I and Interoperability) and the Network Enabled Capability Senior Responsible Owner (NEC SRO) that:

• The Interoperability Requirements are understood (by the above) and are aligned to longer term NEC goals.
• The through life plans for Interoperability are in place.
• Adequate costing provision is made for Interoperability. 
• Interoperability risks are identified and have mitigation plans in place such that action can be taken to reduce the IO risk.

1. Failure - Did not consider Interoperabiliy
   Causes:
   • Lack of understanding of context.
   • No mandated Interoperability Key User Requirement.
   • Belief that responsibility ends at project boundary.
   
   
2. Failure - Did not manage Interoperability
   Causes:
   • Inadequate (or no) funds/resources to manage Interoperability.
   • No consideration of Standards.
   
   
3. Failure - Ill-informed Trade out of Interoperability
   Causes:
   • Need to cut costs within a single project without consideration of impact to others.
   • Lack of enforceable Internal Business Agreements.
   
   
4. Failure - Did not test Interoperability
   Causes:
   • Testing only from System of Interest perspective, not in context of overall mission(s).
   • Assuming the building to standards delivers Interoperability.

Potential Impacts (For all failures)

Performance/Capability

• None (Write-off).
• Loss (Ineffective and withdrawn).
• Partial (Workarounds needed).

Cost

• Unplanned cost burden to Defence Programme.
• Cost to rectify missed Interoperability.

Time

• Delay (Project Late).
• Delay (Related Projects late).
• Delay (Defence Enterprise late).

Industry involvement

Whilst there are many technical standards which have a bearing on Interoperability, there is currently no Defence Standard to cover IO by CIS as a management subject. However, one is planned in order to clarify terms, definitions and the process whereby Industry can respond in a common way to Invitations to Tender (ITT). This future Defence Standard is expected to be similar in terms of format to the current Defence Standard for Integrated Logistics Support (00-60) in that MOD could provide its Interoperability Plan in the ITT and Industry would provide their response to it.

Currently any Interoperability enabled by CIS requirements are recorded in the Project’s System Requirements Document (SRD) and supplied as part of the ITT.

Helpdesk

An Interoperability enabled by CIS and JSP600 Helpdesk is available for advice on the subject. All calls are logged noting it will not aid any commercial enterprise with their Tender Bid preparation. Any clarification questions (CQ) to ITTs concerning Interoperability must be channelled through the appropriate MOD Project Team’s Commercial Officer.

Helpdesk Telephone: +44(0)30679 34034

Helpdesk Email: DESSESEIG-JSP600-HELP@MOD.UK

Helpdesk Operating Times: 0900-1200Hrs and 1400-1600 Hrs
Monday to Friday Except for Public Holidays

In the event of your call not being taken, please leave an unclassified voicemail message with your name, telephone number and organisation. The Helpdesk will aim to return your call no later than 1 working day of receiving it.