Explorer

• Introduction
• Skills and Training
• TLCM Governance: Groups and Roles
• Management Products
  • Capability Management Strategies
  • Capability Management Plans
• Ways of Working
  • Using Virtual Working
  • Using Capability Planning Assumption Lists (CPALs)
    • Recording Assumptions
    • CPAL Checklists
  • Options and How to Write one
• TLCM: Capability Planning The Six Stages
  • Stage 1: Capability Definition
  • Stage 2: Capability Goals
  • Stage 3: Baseline Review and Audit
    • Capability Perspective
    • Commercial Perspective
      • Developing the Commercial Perspective at CMG Level
      • Developing the Commercial Perspective at CPG Level
    • Financial Perspective
      • Collect Key Financial Pressures
      • Analyse Outcomes of Screenings
      • Define Pressures that Impact Capability Goals
      • Generate Summary of Pressures
    • Industrial Perspective
      • Industrial Perspective Report
    • Research Perspective
  • Stage 4: Shortfalls and Opportunity Analysis
  • Stage 5: Capability Investigations
    • Capability Investigation (CI) File
    • What does a CI File Comprise?
  • Stage 6: Endorse Capability Management Plan
    • Using Decision Conferences to Prioitise Options
• TLCM: Capability Delivery
  • Programme Board Roles and Responsibilities
  • Defence Lines of Development Owner Roles and Responsibilities
  • Programme Support Function
    • Planning and Scheduling
      • Planning and Scheduling at Programme Level
      • Planning and Scheduling at Project Level
    • Earned Value Management
    • Risk Management
  • Programme Management Plan
  • Trade-Off
• TLCM: What is Capability Generation?
  • The Levels of Integration
  • Capability Integration in Acquisition
    • Responsibilities of the Designated User
  • Capability Integration Products
    • Link to other Project Plans
    • Capability Integration Plan Responsibilities
• Requirements and Acceptance
• Urgent Operational Requirements
  • Introduction To UORs
  • UOR Process
    • Stage 1: Identify the Requirement
    • Stage 2: Identify and Agree the Solution
    • Stage 3: Procurement
    • Stage 4: Delivery Fielding and Integration
    • Stage 5: In-service and FOC
    • Stage 6: Review
    • End to End Equipment Support Framework
  • Authoritative Reference and SMEs
• Assured Capability in Defence
• COEIA
  • Managing Operational Analysis in your Project

Content

Capability Integration - Products

The Concepts of Employment (CONEMP) and Concepts of Use (CONUSE) are Applied Concepts generated by the User community and informed by the Analytical Concepts generated by the Defence Concepts and Doctrine Centre.

What is the CONEMP?

A CONEMP describes how a new capability will be employed and is primarily written to allow the requirements for that capability to be refined prior to Main Gate. It should not presuppose any specific solution.

A CONEMP is the Concept of Employment for a specific capability within a range of operations or scenarios. It is produced by the Joint and single-Service User staffs consistent with the provenance provided by one or more Analytical Concepts.

In support of acquisition management and to provide context to support the developed URD, a mature CONEMP will be required for Main Gate (MG).

In order to ensure that CONEMPs (and potentially CONUSEs) are delivered as quickly as possible, work on their production may well begin in parallel with developing associated analytical conceptual work, although the CONEMP will have to adapt and conform as the higher level conceptual documents develop.

Following Main Gate, but before ISD, the CONEMP is translated into the CONUSE and should now reflect a particular solution and how it will be used in the joint environment.

What is the CONUSE?

The CONUSE is a developed CONEMP. It describes the way in which a specified capability is to be employed in a range of activities, operations or scenarios. It is derived from the CONEMP for Main Gate in order to inform and support the System Requirement Document (SRD) as a capability approaches its In-Service Date (ISD). It will remain in existence throughout the life of a platform or equipment.

The CONUSE should be reviewed and updated regularly, with typical triggers being a major change in doctrine or policy, or the agreement of new requirements. Thus CONEMP and CONUSE evolve and develop over time as each equipment approaches entry into service. The CONUSE will remain extant through to OSD.

Further detail is available on a generic template for CONEMPs and CONUSEs [113KB DOC] and the mechanism by which CONEMPs and CONUSEs achieve endorsement [53KB DOC].

What is a Capability Integration Plan (CIP)?

The Capability Integration Plan (CIP) is a User tool designed to generate stakeholder confidence that all the wider issues associated with the procurement and development of a capability have been addressed.

It should be agreed with the Sponsor and acts as a focus for the integration of the new capability across all Defence Lines Of Development (DLOD). It identifies those actions that need to be taken, when, and by whom.

It assigns tasks across DLOD and harmonises responsibilities to ensure that the capability is delivered in a coherent and timely fashion.

Generic templates are available to assist in developing a full Capability Integration Plan [89KB DOC] or alternatively an Abbreviated CIP [32KB DOC] for use with smaller projects and Urgent Operational Requirements (UORs).

Change History

Change History