What JCIDS Document is used to build upon the Initial Capabilities Document
|
The IT Box model in the JCIDS Manual facilitates more efficient and timely software development by reducing the requirements documents required to go through the JCIDS process. An Information Systems Initial Capabilities Document (IS-ICD), a variant of the regular ICD, which outlines the “IT Box” is approved via the JCIDS process. Subsequent requirements documents, alternatives to CDDs and CPDs, are streamlined and incrementally approved. Requirements oversight and approvals are delegated to a flag-level oversight board within a Service or Component. This provides IS programs greater flexibility to incorporate evolving technologies and achieve faster responses from requirement validation processes. Show
The IT Box model is appropriate for:
IT Box is are NOT appropriate for:
The following diagram is tailored from one in the JCIDS Manual as an example of using two document types. Actual names, content, and approval process are at the discretion of the delegated oversight authority.
The Requirements Definition Package (RDP) (or equivalent) is a first level refinement of one or more capability requirements identified in an IS-ICD or IS-CDD, and is co-developed by the operational user (or representative) and the program office. The RDP (or equivalent) identifies the KPPs (including updates to the NR KPP), KSAs, and APAs necessary to scope and cost a specific implementation of a capability solution. The RDP (or equivalent) may also identify non-materiel changes that need to be implemented to fully realize the IS capability solution. The RDP (or equivalent) is approved by the delegated oversight authority identified in the IS-ICD or IS-CDD. The Capability Drop (CD) (or equivalent) could describe the performance characteristics of a relatively small increment of a capability solution included in a software build necessary for partial deployment of the overall capability solution, typically developed and fielded within a short period of time. It could be developed through a rapid prototyping effort with the user to ensure it meets their needs. A CD (or equivalent) could be developed directly from the definitions in the IS-ICD in the event of a more timely need for the capability solution. More commonly, multiple CDs (or equivalents) would be derived from an RDP (or equivalent) or IS-CDD to deliver the overall capability solution defined in the RDP (or equivalent) or IS-CDD. The IS-ICD is the preferred method for implementing the IT Box model, but IS-CDDs may be used in cases where a validated ICD contains capability requirements which can be addressed by a combination of IS and non-IS capability solutions and the IT Box construct is applicable to the IS portion of the capability solution(s). IS-CDDs may be used for MDAP and MAIS programs to comply with statutory requirements for a CDD while allowing for other flexibilities of the IT Box model. IS-CDD are also appropriate for use in cases where a validated CDD was generated before the IT-Box construct was introduced, and the Sponsor wants to revalidate under the IT-Box construct. The IS-CDD outlines a similar IT Box and upon approval via JCIDS, requirements oversight and subsequent documentation approval is delegated to the identified flag-level requirements board. See the JCIDS Manual for full details on IT Box applicability, documentation, and process details. Aligning IT Box and Agile
IT Box provides programs great flexibility to iteratively define and document their requirements. Programs using an Agile methodology often manage requirements via user stories via product, release, and sprint backlogs (or equivalent). Programs may consider tailoring the notional RDPs and CDs as outlined in the JCIDS manual with release and sprint backlogs. The Joint Capabilities Integration and Development System JCIDS is 10 years old and ripe for review. A central output document of the JCIDS process is an Initial Capabilities Document ICD used by the Department of Defense to define gaps in a functional capability area and define new capabilities required. The research team analyzed 10 years of ICDs to identify methods and trends. The team found that several methodologies were favored and a convergence emerged in format and necessary content. Additionally, potential shortfalls in current best practices of interest to implementers and decision makers are identified. Guidelines and best practices are presented to create more effective, concise, and complete ICDs. It may come as a surprise to many acquisition practitioners that the historically unstable, formal written procedures and processes that embody the Defense Acquisition System and Joint Capabilities Integration and Development System JCIDS are now over 10 years old. During this time, the Department of Defense DoD has published significant revisions and updates to the JCIDS-related documents, including Department of Defense Instruction DoDI 5000.02 entitled, Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System Manual DoD, 2013 Joint Requirements Oversight Council JROC, 2012. The current system s longevity may be partially attributable to its utilization of modern management approaches, further enabled by a slow convergence of the Joint Strategic Planning System set in motion by the Goldwater-Nichols Act Goldwater-Nichols, 1986. With its focus on Joint development and deconfliction of capabilities, JCIDS uses a portfolio management approach and streamlined documentation to elevate user requirements relatively quickly and vet them against current capabilities.
APPROVED FOR PUBLIC RELEASEWhat JCIDS document is used to build upon the initial ICD?The format for the ICD is found in the Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS Manual).
What are the JCIDS documents?Joint Capabilities Integration and Development System (JCIDS) Documentation. The JCIDS process provides the baseline requirements for documentation, review, and validation of capability requirements, at all classification levels, across the Department.
Who approves the initial capabilities document?(2) The term “initial capabilities document” means any capabilities requirement document approved by the Joint Requirements Oversight Council that establishes the need for a materiel approach to resolve a capability gap.
|
