Attachment_0076_-_Criticality_Analysis_Template_(25MAR2019).docx
DOCX document 33 KB Posted
- Attached to
- Optionally-Manned Fighting Vehicle (OMFV) Program Federal contract opportunity
- Solicitation number
- W56HZV-18-R-0174_
About this file
Attachment 0076 - Criticality Analysis Template
View the file
Other files for this federal contract opportunity
Show all 34
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 0076 – Criticality Analysis Template
W56HZV-18-R-0174
Attachment 0076 – Criticality Analysis Template
W56HZV-18-R-0174
DISTRIBUTION A. Approved for public release: distribution unlimited. If data is recorded in the tables, see paragraph 1.
1. SECURITY NOTICE: Contractor responses to the data requirements below are likely to be at the For Official Use Only (U/FOUO) level, and may be at the SECRET level. For security related guidance and procedures on how to mark, handle, and transmit classified information, contractors should refer to DoD 5220.22-M National Industrial Security Program Operating Manual, 28 Feb 2006, supporting DD 254, and the OMFV Security Classification Guide (U/FOUO) signed by PEO GCS on 28 January 2019.
All U/FOUO and higher responses should be marked with the following Distribution Statement:
DISTRIBUTION STATEMENT E: Distribution authorized to the Department of Defense Components only: Administrative or Operational Use; Export Controlled; Proprietary Information; Operations Security; Vulnerability Data [as appropriate], date of determination is 20190128. Other requests for this document shall be referred to the attention of the PM NGCV Security Manager at: Program Executive Office Ground Combat Systems (PEO GCS), ATTN: SFAE-GCS-N, 6501 East Eleven Mile Road, Warren, MI 48397-5000.
WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq). or the Export Administration Act of 1979, (Title 50, U.S.C., App. 2401 et seq). as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate IAW provisions of DoD Directive 5230.25.
This document contains information that may be EXEMPT FROM MANDATORY DISCLOSURE under the Freedom of Information Act (FOIA). Exemption 4 applies (AR 25-55, III.200 FOIA Exemptions). [Check AR 25-55 to verify if exemptions 1 and 3 also apply]
DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.
SECRET responses should use the following Classification/Declassification Instruction:
Classified by: List name, position title of the Derivative classifier and office of origin Derived from: OMFV SCG, 20190128 Declassify on: YYYYMMDD (Refer to declassification column to determine the date)
2. Criticality Analysis
· Document the results of the Criticality analysis in Table 1 below.
· Criticality should be assessed in terms of relative impact on the system’s ability to complete its mission if the component fails.
· Level I is total mission failure, Level II is significant/unacceptable degradation, Level III is partial/acceptable, and Level IV is negligible.
Table 1: Criticality Analysis Part 1 – Missions, Functions and Components
| Mission |
| Critical Functions |
| Supporting Logic-Bearing Components (Including HW/SW/Firmware) |
| System Impact |
(I,II,III,IV)
| Mission 1 |
| Data Fusion |
| Processor X |
| II |
| SW Module Y |
| I |
| Fire Control |
| Database Z |
| III |
| SW Module A |
| I |
| Critical Function 3 |
| Processor X |
| II |
| Sensor A |
| IV |
| Mission 2 |
| Critical Function 4 |
| Sensor B |
| I |
| Radar A |
| I |
| Critical Function 5 |
| Processor Y |
| II |
| SW Module B |
| II |
| Critical Function 6 |
| Database Y |
| III |
| Integrated Circuit A |
| I |
| Mission 3 |
| Data Fusion |
| Processor X |
| II |
| SW Module Y |
| I |
3. The Level I and Level II components identified in Table 1 shall then be prioritized for resources and attention based on a variety of factors. The results of this prioritization are in the Table 2 below.
Note: Additional blank columns are provided for program-specific analysis/prioritization variables. The program manager is ultimately responsible for prioritizing effort/resources against critical components, and the purpose of this table is to capture the rationale for that prioritization.
Table 2: Critical Component Prioritization Critical Components (Level I/II from Part 1) Missions Supported
| COTS / GOTS / Developmental Items |
| Legacy / New |
| Integrated Circuit? |
(Y/N, If Y: what kind?)
Specifically Designed for Military Use?
(Y/N)
| … |
| … |
| Overall CC Priority |
(H / M / L)
| Processor X |
| 2 |
| Development |
| New |
| Y: ASIC |
| Y |
H
| SW Module Y |
| 2 |
| Development |
| Legacy |
| N |
| Y |
M
| SW Module A |
| 1 |
| COTS |
| Legacy |
| N |
| N |
M
| Sensor B |
| 1 |
| GOTS |
| Legacy |
| N |
| Y |
M
| Radar A |
| 1 |
| GOTS |
| New |
| N |
| Y |
M
| Processor Y |
| 1 |
| Development |
| New |
| N |
| Y |
H
| SW Module B |
| 1 |
| COTS |
| Legacy |
| N |
| N |
M
| Integrated Circuit A |
| 1 |
| Development |
| New |
| Y: ASIC |
| Y |
H
UNCLASSIFIED
Attachment 0076, Page 4
UNCLASSIFIED
File details come from the government source that posted it.