ICD Format

1
ICD Format

• Joint Functional Area.
• Cite the applicable functional area(s), JFCs, the
  range of military operations, and the timeframe
  under consideration.

BATTLESPACE AWARENESS Collect and process
battlespace information COMMAND AND
CONTROL Develop alternatives and disseminate
orders FORCE APPLICATION Cause effects on the
enemy PROTECTION Prevent an enemys effect on
us FOCUSED LOGISTICS Sustain and support the
force
2
ICD Format

• Required Capability
• Describe the particular aspects of the JFCs that
  the ICD addresses
• Explain why the desired capabilities are
  essential to the joint force commander to achieve
  military objectives
• Reference any CRDs that may be applicable to this
  ICD

3
ICD Format

• Concept of Operations Summary
• Describe
• mission areas the capability contributes to
• operational outcomes it provides
• effects it must produce to achieve those outcomes
• how it compliments the integrated joint
  warfighting force
• enabling capabilities are required to achieve its
  desired operational outcomes.

4
3170 Definitions
capability The ability to execute a specified
course of action. It is defined by an
operational user and expressed in broad
operational terms in the format of an initial
capabilities document or a DOTMLPF change
recommendation. In the case of material
proposals, the definition will progressively
evolve to DOTMLPF performance attributes
identified in the CDD and the CPD. capability
gaps - Those synergistic resources that are
unavailable but potentially attainable to the
operational user for effective task execution.
These resources may come from the entire range of
DOTMLPF solutions.
5
Defining Capabilities

• Defining Capabilities.
• In a capabilities-based approach, it is important
  to establish a common understanding of how a
  capability is conceived and how it is expressed
• The top down capabilities identification
  methodology provides a method to identify gaps in
  warfighting capabilities and assess associated
  risk(s)

6
ICD Format

• Definitions of the identified capabilities should
  satisfy two rules.
• Rule 1.
• Capability definitions must contain the required
  attributes with appropriate measures of
  effectiveness, e.g., time, distance, effect
  (including scale) and obstacles to be overcome.
• Rule 2.
• Capability definitions should be general enough
  so as not to prejudice decisions in favor of a
  particular means of implementation but specific
  enough to evaluate alternative approaches to
  implement the capability.
• The discussion above should capture the
  functional area analysis and functional needs
  analysis described in Enclosure A.

7
ICD Format

• Capability Gap
• Describe, in operational terms, the missions and
  functions that cannot be performed or are
  unacceptably limited.
• This discussion should also provide the linkage
  between the required capabilities and the
  appropriate JOCs, JFCs and integrated
  architectures.
• Describe, in broad terms, the attributes of the
  desired capabilities in terms of desired effects.
• Broad descriptions of desired effects help ensure
  that the required capabilities are addressed
  without constraining the solution to a specific,
  and possibly limited, materiel system.

8
We Have A Little Problem Here

• Capability Gap
• Describe, in operational terms, the missions and
  functions that cannot be performed or are
  unacceptably limited.
• This discussion should also provide the linkage
  between the required capabilities and the
  appropriate JOCs, JFCs and integrated
  architectures.
• Describe, in broad terms, the attributes of the
  desired capabilities in terms of desired effects.
• Broad descriptions of desired effects help ensure
  that the required capabilities are addressed
  without constraining the solution to a specific,
  and possibly limited, materiel system.

This definition refers to operational deficiencies
capability gaps - Those synergistic resources
that are unavailable but potentially attainable
to the operational user for effective task
execution. These resources may come from the
entire range of DOTMLPF solutions.
9
We Have A Little Problem Here

• Capability Gap
• Describe, in operational terms, the missions and
  functions that cannot be performed or are
  unacceptably limited.
• This discussion should also provide the linkage
  between the required capabilities and the
  appropriate JOCs, JFCs and integrated
  architectures.
• Describe, in broad terms, the attributes of the
  desired capabilities in terms of desired effects.
• Broad descriptions of desired effects help ensure
  that the required capabilities are addressed
  without constraining the solution to a specific,
  and possibly limited, materiel system.

This definition refers to needed DOTMLPF products
and services.
capability gaps - Those synergistic resources
that are unavailable but potentially attainable
to the operational user for effective task
execution. These resources may come from the
entire range of DOTMLPF solutions.
10
Both

• Capability Gap
• Describe, in operational terms, the missions and
  functions that cannot be performed or are
  unacceptably limited.
• This discussion should also provide the linkage
  between the required capabilities and the
  appropriate JOCs, JFCs and integrated
  architectures.
• Describe, in broad terms, the attributes of the
  desired capabilities in terms of desired effects.
• Broad descriptions of desired effects help ensure
  that the required capabilities are addressed
  without constraining the solution to a specific,
  and possibly limited, materiel system.

In the end, you are required to identify
operational deficiencies for functional and
mission areas ALL the DOTMLPF components needed
to resolve them
capability gaps - Those synergistic resources
that are unavailable but potentially attainable
to the operational user for effective task
execution. These resources may come from the
entire range of DOTMLPF solutions.
11
ORD versus CDD

• ORD
• Describes system capabilities
• Captures system performance (attributes and KPPs)
  
• Describes operational and organizational purpose,
  use, place in force structure
• Captures cost, support requirements, force
  program plans
• Can be updated prior to MSC

• CDD
• Describes the SDD effort to develop materiel
  solution for the increment
• Captures attributes and KPPs for the increment
• Describes the program to get to the complete
  solution
• Updated at/prior to each MS B
• Incorporates lessons learned

Some similarity in content . . . the CDD is
focused on development and demonstration effort
for the increment
12
CDD Guidance
Evolutionary Acquisition

• In an evolutionary acquisition program, the
  capabilities delivered by a specific increment
  may provide only a part of the ultimate desired
  capability
• Therefore, the first increments CDD must provide
  information regarding the strategy for achieving
  the full capability.
• Subsequent increments, leading to the full
  capability, are also described to give an overall
  understanding of the program preliminary
  approach.
• CDDs for subsequent increments will update the
  overall approach to reflect
• Lessons learned from previous increments
• Changes in the
• JOCs
• JFCs
• JICs
• integrated architectures
• other pertinent information
• Additionally, the AoA should be reviewed for its
  relevance for each program to each CDD increment
  and, if necessary, the AoA should be updated or a
  new one initiated.

13
CDD Flash Cards

• 1. Capability Discussion
• Cite applicable ICD(s)
• Provide an overview of the capability gap in
  terms of
• Mission area
• Relevant range of military operations,
• The timeframe under consideration.
• Describe the capability that the program delivers
  and how it relates to applicable
• Joint Operations Concepts
• Joint Functional Concepts
• Integrated Architectures
• Discuss how the current increment contributes to
  the required capability
• Discuss the operating environment of the system
• If the CDD is part of an FoS or SoS solution
• Identify the source ICD
• Discuss related
• CDDs
• CPDs
• Integrating DOTMLPF changes
• Required synchronization

• 2. Analysis Summary
• Summarize the analysis
• AoA
• Other supporting analysis conducted
• Include
• Alternatives
• Objective
• The criteria
• Assumptions
• Recommendation
• Conclusion
• Complete detailed documentation of the analysis
  conducted shall be an attachment

• 4. Threat Summary
• Summarize projected threat environment specific
  threat capabilities to be countered.

• 3. Concept of Operations Summary
• Describe
• Mission areas this capability contributes to
• Operational outcomes it provides
• Effects it must produce to achieve those outcomes
• How it compliments the integrated joint
  warfighting force
• Enabling capabilities are required to achieve its
  desired operational outcomes

14
CDD Flash Cards

• 5. Program Summary
• Summary of the overall program strategy for
  reaching full capability
• The relationship between the increment addressed
  by the current CDD and any other increments of
  the program
• You have to know your spiral acquisition approach
  by the time you send a CDD up for approval
• The timing of delivery of each increment is
  important
• Carefully address the considerations that are
  driving the incremental delivery plan
• Technologies to be developed
• Other systems in an FoS or SoS
• Inactivation of legacy systems
• For follow-on increments
• Discuss updates to the program strategy to
  reflect
• Lessons learned from previous increments
• Changes in JOCs, JFCs, or integrated
  architectures
• Other pertinent information
• Update acquisition status of previous increments

• 6. System Capabilities Required for the Current
  Increment
• Provide a description of each attribute
• List each attribute in a separate numbered
  subparagraph
• Include a supporting rationale for the capability
• Cite any analytic references
• When appropriate, the description should include
  any unique operating environments for the system
• Provide any additional information that the
  program manager should consider
• Present each attribute in output-oriented,
  measurable and testable terms
• For each attribute, provide a threshold and an
  objective value
• Program manager will use this information to
• Provide incentives for the developing contractor
• To weigh capability tradeoffs between threshold
  and objective values.
• Expressing capabilities in this manner enables
  the systems engineering process to develop an
  optimal product.
• If the objective and the threshold values are the
  same, indicate this by including the statement
  Threshold Objective.

15
CDD Flash Cards

• 7. Family of System and System of System
  Synchronization
• In FoS/SoS solutions, ensure
• Related solutions specified in other CDDs and
  CPDs remain compatible
• These related solutions should tie to a common
  ICD.
• Development is synchronized
• The CDD accurately captures the desired
  capabilities described in applicable CRDs.
• Discuss the relationship of system in this CDD to
  other systems contributing to the capability(s)
• Discuss overarching DOTMLPF changes required to
  make the FoS/SoS an effective military capability
• Provide a table that briefly describes the
  contribution this CDD makes to the capabilities
  described in the applicable ICDs and the
  relationships to CDDs and CPDs that also support
  these capabilities
• For these interfaces to be effective, it is
  essential the CDD sponsor review all related for
  applicability to the FoS or SoS addressed by this
  CDD
• JROC Interest
• Joint Impact
• Joint Integration
• ICDs
• CDDs
• CPDs

• 7. Family of System and System of System
  Synchronization, cont.
• Each CDD will crosswalk to applicable CRDs
  (Appendix A)
• Dont specify an attribute as a KPP simply
  because an applicable CRD specifies it as a KPP.
• Rather, show how attributes are responsive to
  applicable CRD standards and KPPs
• Show how attributes support the NR-KPP of the
  CRD(s) in accordance with references h and j.

• 6. System Capabilities Required for the Current
  Increment, cont.
• Provide tables summarizing specified KPPs and
  additional performance attributes in threshold
  objective format
• Also provide a general discussion of the
  additional performance attributes
• Develop the CDD NR-KPP, in accordance with the
  procedures described in references h and j, from
  the integrated architecture (as available) and/or
  appropriate CRDs.

• 8. National Security System and Information
  Technology System (NSS and ITS) Supportability
• For systems that receive or transmit information,
  provide
• an estimate of the expected bandwidth and
• quality of service requirements for support of
  the capability
• per-unit basis
• aggregate basis

16
CDD Flash Cards

• 9. Intelligence Supportability.
• For programs that produce, consume, process or
  handle intelligence data, requirements for
  intelligence support must be addressed as the
  basis for the intelligence certification
  discussed in Enclosure C.
• Identify, as specifically as possible, all
  projected requirements (throughout all
  acquisition phases) for
• intelligence products
• Information, or
• services (throughout all acquisition phases
• Include required performance, descriptive or
  qualitative attributes.
• Demonstrate that security considerations, such as
  classification levels and releasability
  requirements, have been addressed.
• Contact DIA/J-2 Intelligence Requirements
  Certification Office (J2P/IRCO) for assistance
• (DSN 225-4693/1999/8085
• SIPRNET http//www.dia.smil.mil/intel/j2/j2p/irco/
  main.html or
• JWICS http//j2irco.dia.ic.gov/irco/certification_
  process.html).

• 11. Assets Required to Achieve Initial
  Operational Capability (IOC).
• Describe the types and initial quantities of
  assets required to attain IOC.
• Identify the operational units (including other
  Services or government agencies, if appropriate)
  that will employ the capability
• Define the initial asset quantities (including
  initial spares, and training support equipment,
  if appropriate) needed to achieve IOC.

• 12. Schedule and IOC/Full Operational Capability
  (FOC) Definitions.
• Define what actions, when complete, will
  constitute attainment of IOC and FOC of the
  current increment.
• Specify the target date for IOC attainment

• 10. Electromagnetic Environmental Effects (E3)
  and Spectrum Supportability
• Describe the electromagnetic environment in which
  the system must operate and coexist with other
  systems
• US
• Allied
• Coalition
• Government
• Non-government
• Identify potential issues regarding E3
  interference from threat emitters.
• For systems that communicate via electromagnetic
  energy, spectrum certification is necessary to
  ensure adequate access to the electromagnetic
  spectrum.

17
CDD Flash Cards

• 13. Other Doctrine, Organization, Training,
  Materiel, Leadership and education, Personnel,
  and Facilities (DOTMLPF) Considerations
• Discuss any additional DOTMLPF implications
  associated with fielding the system that have not
  already been addressed in the CDD.
• Highlight the status (timing and funding) of the
  other DOTMLPF considerations
• Describe, at an appropriate level of detail, the
  key logistics criteria that will help
• Minimize the systems logistics footprint
• Enhance mobility
• Reduce the total ownership cost.
• Reliability
• Maintainability
• Transportability
• Supportability
• Detail any basing needs
• Forward and main operating bases
• Depot requirements
• Specify
• Facility
• Shelter
• Supporting infrastructure
• Environmental quality compliance

• Mandatory Appendices
• Appendix A. CRD/CDD/CPD Crosswalk(s).
• Formatting instructions are provided in reference
  g.
• Appendix B. Integrated Architecture Products.
• Include the required Architecture Framework View
  Products developed, whenever possible, from
  integrated architectures.
• Formatting instructions a provided in reference
  k.
• Mandatory
• AV-1
• OV-2
• OV-4
• OV-5
• OV-6C
• SV-4
• SV-5
• SV-6
• Draft IT Standards Profile generated by the DOD
  IT Standards Registry (DISR) online
• Initial Interconnectivity and Interoperability
  Capability (IIC) Profile (Interconnectivity
  Profile)
• NR-KPP statement
• IA Statement of Compliance

18
ORD versus CPD

• ORD
• Describes system capabilities
• Captures system performance (attributes and KPPs)
  
• Describes operational and organizational purpose,
  use, place in force structure
• Captures cost, support requirements, force
  program plans
• Can be updated prior to MS C

• CPD
• Captures information needed to produce an
  increment of capability
• Reflects developmental test results and design
  review
• Captures revised production attributes and KPPs
  for the increment
• Applies to a single production increment

Some similarity in content . . . the CPD is
focused on production of the increment
19
CPD Flash Cards
Verbiage identical to that in CDD section of the
3170

• 1. Capability Discussion
• Cite applicable ICD(s) and CDD
• Provide an overview of the capability gap in
  terms of
• Mission area
• Relevant range of military operations,
• The timeframe under consideration.
• Describe the capability that the program delivers
  and how it relates to applicable
• Joint Operations Concepts
• Joint Functional Concepts
• Integrated Architectures
• Discuss how the current increment contributes to
  the required capability
• Discuss the operating environment of the system
• If the CPD is part of an FoS or SoS solution
• Identify the source ICD
• Discuss related
• CDDs
• CPDs
• Integrating DOTMLPF changes
• Required synchronization

• 2. Analysis Summary
• Summarize the analysis
• AoA
• Other supporting analysis conducted
• Include
• Alternatives
• Objective
• The criteria
• Assumptions
• Recommendation
• Conclusion
• Complete detailed documentation of the analysis
  conducted shall be an attachment

• 4. Threat Summary
• Summarize projected threat environment specific
  threat capabilities to be countered.

• 3. Concept of Operations Summary
• Describe
• Mission areas this capability contributes to
• Operational outcomes it provides
• Effects it must produce to achieve those outcomes
• How it compliments the integrated joint
  warfighting force
• Enabling capabilities are required to achieve its
  desired operational outcomes

20
CPD Flash Cards

• 7. Family of System and System of System
  Synchronization
• In FoS/SoS solutions, ensure
• Related solutions specified in other CDDs and
  CPDs remain compatible
• These related solutions should tie to a common
  ICD.
• Development is synchronized
• The CDD accurately captures the desired
  capabilities described in applicable CRDs.
• Discuss the relationship of system in this CPD to
  other systems contributing to the capability(s)
• Discuss overarching DOTMLPF changes required to
  make the FoS/SoS an effective military capability
• Provide a table that briefly describes the
  contribution this CPD makes to the capabilities
  described in the applicable ICDs and the
  relationships to CDDs and CPDs that also support
  these capabilities
• For these interfaces to be effective, it is
  essential the CPD sponsor review all related for
  applicability to the FoS or SoS addressed by this
  CPD
• JROC Interest
• Joint Impact
• Joint Integration
• ICDs
• CDDs
• CPDs
• Each CPD (in Appendix A) will crosswalk to
  applicable CRDs
• Dont specify an attribute as a KPP simply
  because an applicable CRD specifies it as a KPP.
• Rather, show how attributes are responsive to
  applicable CRD standards and KPPs

• 5. Program Summary
• Provide a summary of the overall program strategy
  for reaching full capability
• The relationship between the production increment
  addressed by the current CPD and any other
  increments of the program.

• 6. System Capabilities Required for the Current
  Increment
• Provide a description for each attribute
• list each attribute in a separately numbered
  subparagraph
• Include a supporting rationale for the
  requirement and cite any analytic references.
• When appropriate, the description should include
  any unique operating environments for the system
• Present each attribute in output-oriented,
  measurable and testable terms.
• For each attribute, provide production threshold
  and objective values
• Program manager can use this information to
• Provide incentives for the production contractor
  to enhance performance through production
  improvements.
• Provide tables summarizing specified KPPs and
  additional performance attributes in
  threshold--objective format, as depicted below.
  Also provide a general discussion of the
  additional performance attributes.
• Develop the CPD NR-KPP, in accordance with the
  procedures described in references h and j, from
  the integrated architecture (as available) and/or
  appropriate CRDs.

21
CPD Crosswalking

• Capability
• CPD Contribution
• Related CDDs
• Related CPDs

• ICD Capability Description 1
• Brief description of the contribution made by
  this CPD
• CDD Title
• CPD Title

• ICD Capability Description 2
• Brief description of the contribution made by
  this CPD
• CDD Title
• CPD Title

22
CPD Flash Cards

• 8. Information Technology and National Security
  Systems (IT and NSS) Supportability
• For systems that receive or transmit information,
  provide
• an estimate of the expected bandwidth and
• quality of service requirements for support of
  the system(s)
• per-unit basis
• aggregate basis
• Estimate provided in the CPD should be a
  significant improvement over the
  rough-order-of-magnitude estimate provided in the
  CDD.
• The CPD information should be consistent with
  details provided by the program manager in the
  ISP that is updated and certified by J-6 for
  supportability before Milestone C.
• This description must explicitly distinguish IT
  and NSS support to be acquired as part of this
  program from the IT and NSS support to be
  provided to the acquired system through other
  systems or programs.

23
CPD Flash Cards

• 13. Other Doctrine, Organization, Training,
  Materiel, Leadership and education, Personnel,
  and Facilities (DOTMLPF) Considerations
• Discuss any additional DOTMLPF implications
  associated with fielding the system that have not
  already been addressed in the CPD.
• Describe, at an appropriate level of detail, the
  key logistics criteria that will help
• Minimize the systems logistics footprint
• Enhance mobility
• Reduce the total ownership cost.
• Reliability
• Maintainability
• Transportability
• Supportability
• Detail any basing needs
• Forward and main operating bases
• Depot requirements
• Specify
• Facility
• Shelter
• Supporting infrastructure
• Environmental quality compliance
• Safety and occupational health requirements

• 14. Other System Attributes.
• As appropriate, address attributes that tend to
  be design, cost, and risk drivers, including
• environmental quality
• HIS
• embedded instrumentation
• EA
• IA, and
• WARM requirements.
• In addition, address
• Conventional and initial nuclear weapons effects
• NBCC survivability
• Natural environmental conditions (such as
  climatic, terrain, and oceanographic factors)
• Unplanned stimuli (such as fast cook-off, bullet
  impact, and sympathetic detonation)
• Address safety issues regarding HERO.
• Define the expected mission capability (e.g.,
  full, percent degraded) in the various
  environments.
• Include applicable safety parameters, such as
  those related to
• System
• Nuclear
• Explosive, and

24
CPD Flash Cards
25
JCIDS Document Approval
This process is valid for all JCIDS documents -
ICDs at Milestone A, CDDs at Milestone B and
CPDs at Milestone C.
26
JCIDS Document Approval

• Contact JFCOM/conduct workshop/IPT prior to
  putting pencil to paper.
• CJCSI 3170.01D, dated 12 March 2004, page B-7,
  paragraph 2.c gives website (http//www.teao.saic.
  com/cbrtraining)
• Helps ensure document has valid joint
  requirements that can be mapped back to JOCs and
  Joint Functional Areas
• Draft ICD/CDD/CPD
• Submit for informal review
• Same reference as above
• Prepare Gatekeeper Binning Information paper (see
  binning process for requirements)
• Prepare DRAFT JROC Program Brief in accordance
  with JROC Admin Guide
• Submit Document to KMDS to begin JCIDS process

This process is valid for all JCIDS documents -
ICDs at Milestone A, CDDs at Milestone B and
CPDs at Milestone C.
27
JCIDS Document Approval
Knowledge Management Decision Support (KMDS).
Tool is the current relational database used to
support various Joint Staff functions. Document
is placed in KMDS to start the JCIDS process as
well as other times shown in the figure.
SIPRNET address https//jr
ockmds1.js.smil.mil/guestjrcz/gbase.guesthome
28
JCIDS Document Approval

• Sponsor upload document to KMDS (SIPRNET)
• Entire document
• Gatekeeper Information Paper (see binning process
  for requirements)
• Program POC Information
• Sponsor POC Information
• Go to Submit Documents
• Submit Capabilities Document
• Search
• Add New

Knowledge Management Decision Support (KMDS).
Tool is the current relational database used to
support various Joint Staff functions. Document
is placed in KMDS to start the JCIDS process as
well as other times shown in the figure.
SIPRNET address https//jr
ockmds.js.smil.mil/guestjrcz/gbase.guesthome
29
JCIDS Document Approval

• The Gatekeeper Process, addressed in CJCSI
  3170.01D, serves two functions
• Assigns validation/approval authority and a Joint
  Potential Designator (JPD)
• Joint Interest
• Joint Integration
• Independent
• Assigns Lead and Support FCB Responsibility
• Input is received by vote from the Executive
  Secretaries of the FCBs. On each Tuesday, the
  Gatekeeper, JS DJ8, makes assignment based on
  previous weeks voting. This is designed to take
  5 days.

30
JCIDS Document Approval

• Provide Gatekeeper Binning Information paper
  (Word document) providing the following
  information (no more than one page)
• Title of Program
• Name
• Short description (what it is)
• What it will provide to the warfighter
• Why it is coming to the Gatekeeper
• What type of analysis has the sponsor done
• Name and phone number of a POC that can answer
  any additional questions

• The Gatekeeper Process, addressed in CJCSI
  3170.01D, serves two functions
• Assigns validation/approval authority and a Joint
  Potential Designator (JPD)
• Joint Interest
• Joint Integration
• Independent
• Assigns Lead and Support FCB Responsibility
• Input is received by vote from the Executive
  Secretaries of the FCBs. On each Tuesday, the
  Gatekeeper, JS DJ8, makes assignment based on
  previous weeks voting. This is designed to take
  5 days.

31
JCIDS Document Approval

• After assignment of a lead and supporting FCB as
  well as a Joint Potential Designator (JPD) of
  Joint Interest, the document is sent out for 0-6
  Review. Accomplished by Service, COCOM, and
  Agency staffs.
• Comments from the reviewers are in one of three
  categories
• 1) Critical Non-concurrence in document until
  comment is satisfactorily resolved
• 2) Substantive section in document appears to
  be/is potentially unnecessary, incorrect,
  misleading, confusing or inconsistent
• 3) Administrative corrects typographical error,
  format or grammatical error

32
JCIDS Document Approval

• After assignment of a lead and supporting FCB as
  well as a Joint Potential Designator (JPD) of
  Joint Interest, the document is sent out for 0-6
  Review. Accomplished by Service, COCOM, and
  Agency staffs.
• Comments from the reviewers are in one of three
  categories
• 1) Critical Non-concurrence in document until
  comment is satisfactorily resolved
• 2) Substantive section in document appears to
  be/is potentially unnecessary, incorrect,
  misleading, confusing or inconsistent
• 3) Administrative corrects typographical error,
  format or grammatical error

• Provide brief, if required, to Supporting FCB
• Coordinated through Lead FCB
• Tentatively schedule FCB WG meeting and FCB
  meeting with FCB Lead
• Review Comments on KMDS to the document during
  the 25 day cycle
• Begin Adjudication through KMDS during review
  cycle if comments appear on KMDS
• Most comments will not be posted until the last
  days of the review period
• Receive Comment Resolution Matrix (CRM) from JS
  J8 (via KMDS)

33
JCIDS Document Approval

• Upon completion of 0-6 review, comments
  correlated into Comment Resolution Matrix (CRM)
• CRM given to document sponsor to begin the
  adjudication process
• Lead FCB Working Group will assist in comment
  resolution for unresolved comments (CJCSM
  3170.01A)
• Sponsors rationale must be annotated on the CRM.
• CRM will follow the document through to the next
  level review.
• 15 days is the goal for completion, not an
  absolute limit.
• If accomplisher quicker (though not common), Flag
  review can begin earlier.

34
JCIDS Document Approval

• Upon completion of 0-6 review, comments
  correlated into Comment Resolution Matrix (CRM)
• CRM given to document sponsor to begin the
  adjudication process
• Lead FCB Working Group will assist in comment
  resolution for unresolved comments (CJCSM
  3170.01A)
• Sponsors rationale must be annotated on the CRM.
• CRM will follow the document through to the next
  level review.
• 15 days is the goal for completion, not an
  absolute limit.
• If accomplisher quicker (though not common), Flag
  review can begin earlier.

• Contact reviewer to address comments on the CRM
• Fill in Sponsor section of the CRM with one of
  the responses below
• Accepted Sponsor accepts comments and
  incorporates into the document
• Partially Accepted Sponsor accepts some of the
  comment with rationale for what will be
  incorporated into the document to address comment
• Rejected Sponsor will not incorporate the
  comment with rationale
• Highlight all changes to the document for next
  review
• Attempt to resolve all comments
• Contact Lead FCB Working Group for assistance in
  resolving unresolved comments

35
JCIDS Document Approval

• 0-6 comments addressed
• Revised document is submitted to KMDS to be
  staffed for Flag Level Review.
• This revised Flag document (with comments made to
  original) submitted with the 0-6 CRM
• Annotated with sponsor comments

36
JCIDS Document Approval

• 0-6 comments addressed
• Revised document is submitted to KMDS to be
  staffed for Flag Level Review.
• This revised Flag document (with comments made to
  original) submitted with the 0-6 CRM
• Annotated with sponsor comments

• Submit Flag document with 0-6 Review comments
  incorporated
• All changes to the document made after O-6 review
  highlighted
• Submit 0-6 Review complete CRM with Sponsor
  comments included
• Go to Submit Documents
• Submit Capabilities Document
• Search
• Add New

37
JCIDS Document Approval

• Flag Review similar to 0-6 review but the
  document is signed by higher ranking people
• In many organizations, the same reviewers analyze
  the documents during both phases
• CRM is again collated and given to sponsor at the
  end of the review cycle
• DOTMLPF Change Request (DCR) enters at Flag
  review level IAW CJCSI 3180.01 and follows the
  remaining steps.

38
JCIDS Document Approval

• Flag Review similar to 0-6 review but the
  document is signed by higher ranking people
• In many organizations, the same reviewers analyze
  the documents during both phases
• CRM is again collated and given to sponsor at the
  end of the review cycle
• DOTMLPF Change Request (DCR) enters at Flag
  review level IAW CJCSI 3180.01 and follows the
  remaining steps.

• Incorporate any changes to JROC brief based on
  CRM and briefing with Supporting FCB
• Update schedule date for FCB WG meeting and FCB
  meeting with FCB Lead
• Functions of KMDS also require tentative dates
  for JCB and JROC

39
JCIDS Document Approval

• As with the 0-6 adjudication, all comments must
  be addressed as
• Accepted (A)
• Partially Accepted (P)
• Rejected (R)
• Sponsors rationale must be annotated on the CRM.
• Lead FCB Working Group will assist in comment
  resolution for unresolved comments (CJCSM
  3170.01A)
• CRM will follow the document through to the next
  level review.
• 15 days is the goal for completion, not an
  absolute limit.
• If accomplisher quicker (though not common), FCB
  WG can begin earlier.

40
JCIDS Document Approval

• As with the 0-6 adjudication, all comments must
  be addressed as
• Accepted (A)
• Rejected (R)
• Partially Accepted (P)
• Sponsors rationale must be annotated on the CRM.
• Lead FCB Working Group will assist in comment
  resolution for unresolved comments (CJCSM
  3170.01A)
• CRM will follow the document through to the next
  level review.
• 15 days is the goal for completion, not an
  absolute limit.
• If accomplisher quicker (though not common), FCB
  WG can begin earlier.

• Contact reviewer to address comments on the CRM
• Fill in Sponsor section of the CRM with one of
  the responses below
• Accepted Sponsor accepts comments and
  incorporates into the document
• Partially Accepted Sponsor accepts some of the
  comment with rationale for what will be
  incorporated into the document to address comment
• Rejected Sponsor will not incorporate the
  comment with rationale
• Attempt to resolve all comments
• Contact Lead FCB Working Group for assistance in
  resolving unresolved comments
• Required to resolve critical comments or forward
  to FCB/JCB/JROC

41
JCIDS Document Approval

• The document (now an FCB Draft) is submitted to
  KMDS with completed Flag CRM
• Part of the read-ahead that FCB members review
  prior to the formal meeting.
• Comments and other non-documented issues will be
  addressed at FCB WG prior to formal presentation
  at the FCB

42
JCIDS Document Approval

• The document (now an FCB Draft) is submitted to
  KMDS with completed Flag CRM
• Part of the read-ahead that FCB members review
  prior to the formal meeting.
• Comments and other non-documented issues will be
  addressed at FCB WG prior to formal presentation
  at the FCB

• Submit FCB Draft document with Flag Review
  comments incorporated
• Submit Flag Review complete CRM with Sponsor
  comments included
• Go to Submit Documents
• Submit Capabilities Document
• Search
• Add New

43
JCIDS Document Approval

• FCB Working Group (FCB WG)
• Listens to presentation
• Provides comments on format and content
• Provides free flow of information
• ID pertinent issues
• No minutes are taken
• Non-attribution environment
• Unresolved comments during review are also
  addressed
• Recommendations presented to the FCB by the FCB WG

44
JCIDS Document Approval

• FCB Working Group (FCB WG)
• Listens to presentation
• Provides comments on format and content
• Provides free flow of information
• ID pertinent issues
• No minutes are taken
• Non-attribution environment
• Unresolved comments during review are also
  addressed
• Recommendations presented to the FCB by the FCB WG

• Provide JROC Program Brief slides NLT 48 hours
  prior to the Working Group meeting
• Brief FCB WG
• Incorporate comments from Working Group meeting
• Provide updated slides to FCB Secretariat NLT 48
  hours prior to scheduled FCB meeting

45
JCIDS Document Approval

• The FCB is Chaired by a FO/GO
• Services, COCOMs and Agencies are represented by
  0-6 or equivalents
• Joint Staff FCB representative provides a context
  brief
• The program sponsor briefs the program
• Pertinent issues should have been discussed at WG
  with a recommended way ahead given to the sponsor
• After it is satisfied with the programs
  presentation and all information, the FCB
  forwards the program to the Joint Capabilities
  Board (JCB) with recommendations

46
JCIDS Document Approval

• The FCB is Chaired by a FO/GO
• Services, COCOMs and Agencies are represented by
  0-6 or equivalents
• Joint Staff FCB representative provides a context
  brief
• The program sponsor briefs the program
• Pertinent issues should have been discussed at WG
  with a recommended way ahead given to the sponsor
• After it is satisfied with the programs
  presentation and all information, the FCB
  forwards the program to the Joint Capabilities
  Board (JCB) with recommendations

• Joint Staff FCB representative will present
  Context Brief slides with recommendations from
  the FCB WG(s) and Supporting FCB, if required
• Brief JROC Program Brief
• Update brief per recommendations of the FCB

47
JCIDS Document Approval

• Joint Staff FCB representative accompanies
  program sponsor to Joint Capabilities Board (JCB)
  and Joint Requirements Oversight Council (JROC)
• Joint Staff FCB representative presents the
  context brief
• Sponsor presents program brief
• JCB will either request a paper JROC, no formal
  briefing to the JROC required, or send the
  program to the formal JROC for decision

48
JCIDS Document Approval

• Joint Staff FCB representative accompanies
  program sponsor to Joint Capabilities Board (JCB)
  and Joint Requirements Oversight Council (JROC)
• Joint Staff FCB representative presents the
  context brief
• Sponsor presents program brief
• JCB will either request a paper JROC, no formal
  briefing to the JROC required, or send the
  program to the formal JROC for decision

• Joint Staff FCB representative will present
  Context Brief slides with recommendations from
  the C2 FCB and Supporting FCB (if unresolved
  conflict)
• Brief JROC Program Brief
• Update brief per recommendations of the JCB
• Follow same schedule if required to continue to
  the JROC

49
JCIDS Document Approval
Submit JCIDS Document To KMDS
Sponsor prepares JCIDS Document
JCIDS document undergoes O-6 Review (25 Days)
Go to Binning Process
Submit revised JCIDS Document To KMDS
Sponsor adjudicates O-6 comments (15 Days)
Revised JCIDS document undergoes Flag Review
(21 Days)
Sponsor adjudicates Flag comments (15 Days)
When the JROC has completed the program review
(either formal or paper-JROC), the final
validated/approved document will be posted to KMDS
Submit revised JCIDS Document To KMDS
Sponsor presents program to FCB WG
Sponsor presents program to FCB
Sponsor presents program to JCB/JROC for
approval/validation
50
Function
Simplifying the Analysis
51
Why Function?

• The key to understanding where a problem is
  occurring and initiation of the formulation of
  architecture views which demonstrate which
  mission threads or business processes are/will be
  effected is understanding the organization and
  its component functions.
• Even though the mission of a hospital is provide
  quality and affordable patient care, support
  (sometimes referred as Administrative) is always
  broken out as a separate set of functions.
• While critical to the accomplishment of the
  overall mission, support functions and
  operational functions performance goals are
  slightly different.
• Support functions are judged solely on how well
  they support the front line.
• Operational functions are judged on the extent
  they meet command operational objectives.

52
Functions Health Care Example
Support and Operations Are Different
Example Biomedical Engineering and any
department which uses medical equipment are
functionally linked.
53
What is Function?
Merriam-Webster says

• professional or official position OCCUPATION
• the action for which a person or thing is
  specially fitted or used or for which a thing
  exists PURPOSE
• any of a group of related actions contributing to
  a larger action especially the normal and
  specific contribution of a bodily part to the
  economy of a living organism