Attachment 001 - Contract Data Requirements List (CDRLs) 12Feb26.xlsx

Working Task List

Complete Section M (DRAFT RFP) Jana 9/5/24 10/10/24

CDRL Review Sign Up

Dissemination

PEO GCS OPSEC# OPSEC-2026-232

CUI

CUI

CDRL Review Tracker

(How will the CDRL be used?)

Purpose (multi day event):

Introduction - general system description Capability (what was the system designed to do):

Include but not limited to:

Design/Requirements

Integration Plan

Test

DE/MBSE

Safety

• Hazard summary

Cyber

Logistics Support Aspects -

Content. The IBOM data shall contain the information specified by the Data Element Numbers. The data shall meet the requirements as specified in the Definition, Notes and Instructions, and Data Type columns. The indentured path to the system level shall be identified using the item/Next Higher Assembly (NHA) method. Fields for which data is not available. The data shall be included to the lowest indenture level (component level) for all items, including subcontractor items, which are not commercial items. See Attachment XXXX as the preferred format. Rows containing information for assemblies are completed with Bold text and a darker shading, while rows with sub-component parts are in standard font with a lighter color shading. Color shading follows indenture (e.g. if blue is used for indenture level B, all parts and assemblies at indenture level B will blue).

OEM Item Number: The item number assigned by the Original Equipment Manufacturer (OEM). This may be the same as the Manufacturer’s Item Number but more often than not it is different. Sometimes referred to the Configuration Part Number or the Drawing Number.

OEM Name: The full legal name of the entity that is providing the item referenced in Data Element 1 to the government. Sometimes referred to as the Prime Integrator or Prime.

OEM CAGE: Commercial and Government Entity (CAGE) code of the OEM referenced in Data Element Revision Designator: The revision number or letter of the item referenced.

Software / Firmware Version: The designator assigned to the version of software / firmware Required for all items containing software or firmware.

Indenture Level: A number which identifies an item's relative complexity as an assembly or function. This number represents the specific level of the item referenced within the system.

Required. Starts with the top level of the system as one.

Find Number: The reference number assigned to the item in lieu of the item’s identifying number on the drawing and entered as a cross-reference to the item number of the parts lists where the item name and identification number are given. See ASME Y14.100, appendix D, D-8 for a complete definition.

NHA Item Number: The OEM Item Number of the parent assembly of the item. If the referenced item is software or firmware then the NHA is the item the software is used on.

Required for all items except the top level assembly.

NHA CAGE: CAGE code of the OEM of the NHA.

Required for all items except the top level assembly.

Nomenclature: The name drawing title of the item. See ASME Y14.100, appendix C, C-4 for further information.

Required for all items.

Quantity: The count of the item per NHA.

Required for all items.

Provisioning Status: The item has been provisioned in a Services supply system (Yes or No).

Answer Yes or No.

Text (Yes, No) NSN: National Stock Number (NSN) of the item.

Required if the item has a NSN assigned.

Manufacturer’s Item Number: The item number assigned by the actual manufacturer of the item. This number will be used to monitor the item for obsolescence issues.

Required. This number may be the same as the item if the item is manufactured by the OEM.

Manufacturer’s Name: The full legal name of the entity that actually manufacturers the item referenced.

Manufacturer’s CAGE: The CAGE code of the entity that actually manufacturers the item.

Manufacturer’s Address: The physical address of the manufacturer of the item, including country.

Manufacturer’s Website: The web address of the manufacturer of the item.

Required if the manufacturer has a website.

Alternate For: The OEM item number of the alternate for the item.

Required if the item is an alternate for another item in the BOM.

Item Class: Identifies whether the item referenced is Commercial Off the Shelf (COTS) or a Nondevelopmental Item (NDI).

Required if the item is an assembly considered COTS, NDI. See the definitions section of 48 CFR 2.101 for definitions. Responses are: COTS or NDI.

Text (COTS, NDI) Item Type: Enter the type of the item based on the following: An assembly is comprised of components and potentially other assemblies, e.g. a circuit card or a transmission. A component is a single item of manufacture used to make an assembly, e.g. a microcircuit or a screw. Software is an item of a computer system that consists of data or computer instructions, in contrast to the physical hardware from which the system is built. Material is the products used manufacture the assembly, e.g. wire, fiberglass, steel, glue.

Required. Enter Component, Assembly, Material, or Software.

Firmware is not reported here, it is considered as an item of the hardware it is associated with.

Text (Component, Assembly, Material, Software) Sources: The count of manufacturing sources for the item referenced in.

Lead Time: The time between the manufacturers’ receipt of an order for the item and the delivery of the product.

Numeric (Months) Stock on Hand: The quantity of the item owned by the contractor and designated for use on this contract.

EOL: The End of Life (EOL) of the item. The EOL is the estimated last production date (month/year) of the referenced item. This date is provided by some commercial sources for electronic items, can be found in some manufacturer’s product roadmaps, or may be obtained by direct contact with the manufacturer.

Required. For estimates which, in the opinion of the contractor, are not firm use January as the month.

Date (mm/yyyy) EOL Type: EOL Type establishes whether the EOL originated from the item manufacture or was based on a prediction.

Choose from: Known or Predicted Text (Known, Predicted) Recommended Replacement Item: The item that the manufacturer recommends as a suitable replacement.

Required if available Cost Source (quote, purchase order, estimate, or other) Make or Buy Cost Extended Cost yes I-BOM Sample Provide a BOM in order to facilitate a Diminishing Manufacturing Sources and Material Shortages (DMSMS) assessment and examination for items common to other US Army systems.

Also serves as a Product Baseline for Engineering A004 ABCL-C Bill of Materials (BOM)

- This CDRL has unique data fields (columns) from the IBOM and therefore is not easily combined as a single CDRL

1. Format. As-built configuration list format shall be an electronic comma separated variables (csv). Each text file shall contain 20 columns describing the attributes of each hardware and software configuration item for a single end item.

2. Content. The ABCL-C shall contain all of the information identified and the following information:

2.1. File Construction.

2.1.1. Columns 1 and 2 shall describe the program and shall be the same for all rows.

2.1.2. Columns 3 through 18 shall describe each reportable item.

2.1.3. Columns 19 and 20 shall describe the end item and will be the same for all rows.

2.1.5. Row one shall contain information for the end item (the highest-level assembly in the file).

2.2. The report shall identify the end item as the highest-level assembly in the deliverable file.

2.2.1 Item shall be identified as a unique reportable individual missile, section, assembly, or component.

2.2.2 NHA shall be identified as the Next Higher Assembly of an item.

2.2.3 Manufacturer shall be identified by indicating the specific vendor that produced the reportable item.

2.2.4 CAGE Code shall be identified as Commercial and Government Entity Code.

2.2.5 CARL shall be identified as the Configuration Accounting Requirements List. A collection of hierarchical configuration structures (indentured drawing trees) for each end item part number produced. The drawing tree for each end item part number will contain an indentured list of primary and alternate reportable part numbers. Additional configuration data delivery requirements may also be documented.

a. Supply Chain Risk Management (SCRM) Plan defines the structured, contractor-proposed SCRM strategy relative to the products and services to be provided by the prime, its suppliers, and subcontractors. The SCRM plan will include a systematic process used to identify, assess, handle, and monitor supply chain risks associated with the product or service to be provided. This information will be used by the Government to maintain oversight of the contractor’s holistic SCRM Plan to effectively handle risks within the supply chain.

b. SCRM plan shall contain Cover and Title Page identify the following:

c. Revision Control. The SCRM plan shall contain a list of all revisions identifying the following information:

d. Table of Contents. The table of contents shall identify each major section title, paragraph number, and starting page number for each major section.

e. Section Contents. The SCRM Plan shall address each major section identified below:

f. SCRM Strategy. This section shall provide an overview of the contractor’s overall SCRM strategy. It will include how the contractor plans to identify, assess, handle, and monitor risks in the lifecycle supply chain that have the potential to jeopardize the integrity of assets, compromise related intellectual property, disrupt the flow of critical goods or services needed for continued Department of Defense (DoD) operations, unexpectedly drive materiel cost increases to programs, or compromise national security.

g. Responsible Organizational Component. This section shall include:

1. Contractor’s organizational SCRM construct;

2. Contractor’s primary and alternate focal points’ contact information to include names, duty titles, addresses, telephone numbers, and email addresses.

h. SCRM Processes and Procedures. This section shall describe:

1. Processes for: Protecting products and services throughout the entire lifecycle; identifying, assessing, handling, and monitoring potential supply chain threats, weaknesses, and vulnerabilities; and analyzing identified potential disruptions for the program’s supply chain, suppliers, products, technologies, and services;

2. Process for revising the SCRM Plan in accordance with government guidelines during the lifecycle of the program, and for providing a copy of the SCRM plan to the Government Product Support Manager or Program Manager.

i. Supply Chain Risk Identification. This section shall describe in detail:

commercial business tradecrafts employed to uncover and map supplier networks;

3. Process for communicating supply chain risks to affected stakeholders and the Government Program Support Manager or Program Manager.

j. Supply Chain Risk Assessment. This section shall include:

1. Process to scan the contractor’s supply chain network (to include sub-tier suppliers), applying risk categories, to identify and assess supply chain risks that could impact the Government’s program;

2. Contractor’s methodology for assessing all vendors or sources of supply to identify potential threats and vulnerabilities;

3. Processes for analyzing root causes and assigning a risk rating by assessing the likelihood of occurrence; and determining severity of impact to the contractor’s supply chain.

As described in DoDM 4140.01 Supply Chain Materiel Management Policy, SCRM owners assess supply chain risk by determining the severity of impacts to 1.) integrity of goods and services; 2.) assurance of supply; and 3.) economic efficiency to the contractor’s supply chain.

Processes for assessing SCRM risk impacts are specific to risks originating from the supply chain and do not encompass all enterprise or program risks. However, successful supply chain risk management does enable Program Managers to proactively manage risks associated with cost (economic efficiency), schedule (assurance of supply), and performance (integrity of products or services).

Product Support Manager or Program Manager on a quarterly basis.

k. Supply Chain Risk Handling. This section shall include:

1. Supply chain risk handling plans to combat identified and potential supply chain risks shall include the following:

(a) A descriptive title for each supply chain risk;

(b) Root cause or trigger of each risk;

(c) Possible risk handling plan to alleviate each risk; and

(d) Description of events and activities intended to accept, avoid, mitigate, or transfer the risk, success criteria for each planned event, and residual risk rating (acceptable level of risk). Reference DI-MGMT-82255A Supply Chain Risk Register.

l. Supply Chain Risk Monitoring. This section shall include:

1. Process for the persistent and comprehensive monitoring and re-evaluation of supply chain risks and corresponding risk handling plans;

m. SCRM Training. This section shall describe in detail:

1. SCRM training that promotes an understanding of the basics of SCRM as a practice, the nature of risks facing supply chains, and the recommended approaches;

Block 9: All documentation will be marked as Distribution Statement D or the foreign equivalent.

Blocks 10-13: Contractor shall submit a draft CDRL 60 days after contract award. USG will conduct a review within 15 days after receipt. Contractor shall propose a time for a four hour meeting to occur after the 15 day USG review period. The intent of the meeting will be to review any USG comments to the draft proposal. The final submission is due from the contractor 10 days after the review meeting.

A006 Product Level TDP TDP 30 Once DID: DI-SESS-80776B

RECOMMEND USING:

DI-SESS-81000F

Format. Deliverable TDP elements shall be in the Government’s format as specified on the TDP Option Selection Worksheet.

Product engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.3. The product design data shall document directly or by reference the following, as applicable:

(1) Details of unique processes, i.e., not published or generally available to industry, when essential to design and manufacture.

(2) Performance ratings.

(3) Dimensional and tolerance data.

(4) Critical manufacturing processes and assembly sequences.

(5) Toleranced input and output characteristics.

(6) Diagrams.

(7) Mechanical and electrical connections.

(8) Physical characteristics, including: form, finishes, and protective coatings.

(9) Details of material identification, including material condition, and mandatory treatments and coatings.

(10) Inspection, test, and evaluation criteria.

(11) Equipment calibration requirements.

(12) Quality assurance requirements.

(13) Hardware marking requirements.

(14) All required certifications, special inspections, and other environmental, operational and functional testing necessary to ensure intended performance.

(15) Vendor substantiation data.

(16) Requirements for programming software into devices or assemblies including: a description of the input media and procedures for validating that the software has been installed correctly.

(17) Special consideration items and processes.

d. Commercial engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.4,

e. Special Inspection Equipment (SIE) engineering design data and associated lists in accordance with MILSTD-31000B paragraph 5.4.2,

f. Special Tooling (ST) engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.3,

g. Specifications in accordance with MIL-STD-31000B paragraph 5.4.4,

h. Software documentation in accordance with MIL-STD-31000B paragraph 5.4.5,

i. Special Packaging Instructions (SPI) engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.6,

Product engineering design data and associated lists in accordance with MIL-STD-31000B paragraph 5.4.1.3. The product design data shall document directly or by reference the following, as applicable:

Dimensional and tolerance data.

Physical characteristics

Block 12: The contractor shall submit the first weekly reports within 1 business day of the first full week after arrival at the CONUS or OCONUS location.

Block 13: The FSR shall submit subsequent a weekly summary of their activity within 1 business day of the last business day of the activity report week. The Contractor report shall include damaged or non-repairable equipment. The contractor shall, for situations that may lead to or resulted in serious injury or loss of life, notify the Government by most expeditious means, and submit a follow-up report within 24 hours.

Block 14:

Electronic Submissions of data requirements shall be uploaded to the Contract Data Requirements List (CDRL) within the Governments Knowledge Center Portal located at: https://kcp.tacom.army.mil/sites/HBCTIDE/cdrl/SitePages/Canvas.aspx

The contractor will receive confirmation of each submission via the Governments KCP.

1. The contractor shall develop a cannon safety summary that outlines the safety activities conducted on the cannon assembly to be utilized in the proposed howitzer. The safety summary shall include:

a. The safety tests conducted on the cannon (reference appropriate military standards, international test operating procedures [ITOPs], or North Atlantic Treaty Organization Standardization Agreement/Allied Ordnance Publications STANAG/AOP])

b. The ammunition utilized in the safety tests.

c. Provide an engineering report for Safe Service Life testing and/or analysis of the cannon to include the tube, breech, and muzzle brake.

d. Provide an engineering report for wear testing of the cannon tube.

e. Provide an engineering report for reliability of the armament system.

f. The permissible maximum pressure (PMP), the cannon design pressure (CDP), and the proof pressure (PP).

g. Evidence that the cannon has been proofed.

h. The design of the charge used to proof the cannon

i. Provide the maximum rate of fire to include charge and ammunition suite, include the number of rounds that can be fired at this rate.

j. Provide the sustained rate of fire to include charge and ammunition suite

k. Describe the thermal limits for propellant cookoff and for projectile exudation.

l. Describe any automated armament monitoring to include recoil, thermal temperature, and ammunition handling.

m. Describe the impulse and margin that the gun mount and recoil are designed to and what were the design requirements .((Needed for US developmental ammunition))

n. All cannon condemnation limits and serviceability criteria required for safety inspections.

o. Provide pressure-time curves for interior ballistic environment for relevant charge levels, MIL-STD hot and cold in addition to ambient for each charge zone.

p. Ram velocity profile – velocity-time curve or similar to indicate expected environment imparted on the projectile (including seating event)

Block 9: All documentation will be marked as Distribution Statement D or the foreign equivalent.

Blocks 10-13: The report is to be submitted 30 days after contract award.

a. The Contractor shall prepare and provide a list of emitter frequencies in accordance with this CDRL. The contractor shall list the emitter frequencies for all items in the ecosystem provided to the US Government. This shall include, but not be limited to, radios,

The report must include, at a minimum, the information outlined below.

a. The Contractor shall prepare and provide a Critical Crew Drill report in accordance with this CDRL and contain the following additional requirements:

1. The contractor shall provide detailed crew drills for each of the following operations:

a. Emplacement

b. First Round Response (describing all actions taken from receipt of mission to the first round fired)

c. Displacement

d. Fire Mission Processing (describing all actions taken to complete fire missions after the first round fired)

e. Ammunition Rearm (Resupply of howitzer from resupply vehicle)

2. The contractor shall specify what the current U.S equivalent Military Occupational Specialty (MOS) is required for each crew member.

3. The Critical Crew Drill Report shall be developed using the notional U.S equivalent MOS for each crew member.

4. For each Critical Crew Drill operation, the contractor shall detail what each crew member duty/tasks are along with a timeline.

5. For each Critical Crew Drill operation, the contractor shall provide a task analysis that lists the equipment/human factors interfaces that each crew member interacts with when performing each task as well as the sensory, cognitive, and motor demands that the tasks impart on the users, who operate and maintain (i.e., troubleshoot) the system and its components. This shall include operator/crew supervision of automated functions. Critical Task Analysis Report (DI-HFAC-81399B) and the Human Engineering Systems Analysis Report (DIHFAC-80745C) are available as guidance.

6. The Critical Crew Drill Report shall provide basic dimensions, locations, and human factors requirements (e.g. hand wheel torques)

1. References. A list of source materials used in preparing the report. Include for example, government and contractor reports, standards, criteria, technical manuals and specifications. If references are numerous, put them in a bibliography as an appendix.

2. A system description. A brief identification of the system and its purpose. Address significant health hazard issues that are identified later in the report.

3. A background. A description of the system and its intended operation. Include pertinent components or subsystems which contribute most to a health hazard, The identity of the intended users and the type of protective clothing and equipment, if any, available to the user. A summary of the evaluations or assessments performed on system prototypes or developmental models.

4. Identification of health hazards issues. A description and discussion of each potential or actual health hazard issue of concern for each subsystem or component. A health hazard is an existing or likely condition, inherent to the operation, maintenance, transport or use of materiel that can cause death, injury, acute or chronic illness, disability, or reduced job performance of personnel by exposure to physiological stresses.

a. A system breakout. Use sub-paragraphs for each subsystem or component, with additional sub-paragraphs for each health hazard discussion. Include sufficient detail to clearly define the specific problem, issued involved and reasoning behind the analyses.

b. Material information. For each proposed and alternative material, include the following:

(1) Material identification. Include material identity; common or trade name; chemical name; chemical abstract service number; national stock number (NSN) or local stock number; physical form (solid, liquid, gas); and manufacturers and suppliers.

(2) Material use and quantity. Include component name, description, and code, and/or operations details for the material. Total system and program, life-cycle quantities to be used. For mixtures, concentrations for each ingredient.

(3) Hazard identification. The detrimental effects of the material on the system, personnel, environment, or facilities. Specific health hazards are: chemical hazards, physical hazards (noise, heat/cold stress, etc.), biological hazards, ergonomic hazards, ionizing and nonionizing radiation hazards, and other hazards that may be formed by the test, and operation

(4) A toxicity assessment. A description of the expected frequency, duration, and amount of exposure. Include the reference documentation and methods used to determine potency/toxicity assessment factors and calculations.

(5) Risk calculations. Include classification of severity and probability of occurrence, acceptable levels of risk, any missing information, and discussions or uncertainties in data or calculations.

(6) Likely routes of exposure. Include routes of exposure that personnel may be reasonably be exposed to. Federal Occupational Safety & Health Administration (OSHA) provides the following routes of exposure: Inhalation, Ingestion, Absorption, and injection.

(7) Up-to-date Safety Data Sheets (SDSs)

c. Noise and Blast Overpressure (BOP) exposure measurements. For each firing configuration, include the following:

(1) Steady-State noise exposures in excess of 85 dB.

(2) Impulse noise exposures in excess of 140 dB.

(3) Blast Overpressure exposures in excess of 4 psi.

5. An assessment of health hazard issues. Include an analysis of data, observations, findings, reports and other sources of information against health standards and criteria. A discussion of the potential effect of the health hazards identified. An assessment of the risk of the health hazards based on hazard severity and hazard probability as described in MIL-STD-882E, Change 1, System Safety. Include when the hazards may be expected under normal or unusual operating or maintenance conditions. Include analysis methodologies and techniques, information sources (including Safety Data Sheets), and standards and criteria for acceptable exposures and controls.

6. Recommendations. Include a description of the recommended actions that should be taken to eliminate, reduce or control each actual or potential health hazard described. Identify the effect that each action may have on the risk of the health hazard(s).

7. Summary. Include a summary of the major recommendations. 1) Used to identify potential health hazards that test personnel and Soldiers may be exposed to during system operation.

2) Determine if the system is at an acceptable level of risk for testing/TiC/general acquisition.

3) Understand whether mitigations will be reasonable and effective at reducing the risk of death, injury, damage, or environmental impact.

accordance with CDRL A021 – DI-SAFT-80102D detailing the system's safety risk to personnel, environment, the system itself, and other systems the contractor system can be reasonably expected to interact with. The report shall include at a minimum:

1. An introduction stating the purpose of the SAR, in narrative form.

2. A system description. The is section may be developed by referencing other program documentation such as technical manuals, system program plan, system specification, etc., and shall include the following:

a. The purpose and intended use of the system.

b. A brief historical summary of the system development.

c. A brief description of the system and its components. Include name, type, model number, and general physical characteristics of the overall system and its major subsystems and components. Software and its roles shall be included in this description.

d. As applicable, a description of any other system(s) which will be tested or operated in combination with this system.

e. As applicable, either photos, charts, flow/functional diagrams, sketches, or schematics to support the system description, test, or operation.

3. A system operations section. This section shall include:

a. A description or reference of the procedures for operating, testing, and maintaining the system. Discuss the safety design features and controls incorporated into the system as they relate to the operating procedures.

b. A description of any special safety procedures needed to assure safe operations, test, and maintenance, including emergency procedures.

c. A description of anticipated operating environments, and any specific skills required for safe operation, test, maintenance, transportation, or disposal.

d. A description of any special facility requirements or personal equipment to support the system.

4. A system safety engineering section. This section shall include:

a. A summary or reference of the safety criteria and methodology used to classify and rank hazardous conditions.

(1) Safety risk assessment criteria shall follow MIL-STD-882E, Change 1.

b. A description of or reference to the analyses and tests performed to identify hazardous conditions inherent in the system.

(1) A list of all hazards by subsystem or major component level that have been identified and considered from the inception of the program in an appendix to the SAR.

(a) A discussion of the hazards and the actions that have been taken to eliminate or control these items.

(b) A discussion of the effects of these controls on the probability of occurrence and severity level of the potential mishaps.

(c) A discussion of the residual risks that remain after the controls are applied or for which no controls could be applied.

(2) A discussion of or reference to the results of tests conducted to validate safety criteria requirements and analyses.

(3) A discussion of analyses and tests performed to address software safety risks and Level of Rigor (LoR), to include the following:

i. Summary of Safety-Related (SR), Safety-Critical (SC), and Non-Safety-Significant (NSS) functions identified.

ii. Summary of Software Criticality Index (SwCI) functional allocations.

iii. A statement of whether LoR tasks are complete, or in progress.

5. A conclusions and recommendations section. This section shall include:

a. A short assessment of the results of the safety program efforts. A list of all significant hazards along with specific safety recommendations or precautions required to ensure the safety of personnel and property. The list of hazards will be categorized as to whether or not they may be expected under normal or abnormal operating conditions.

b. For all hazardous materials generated by or used in the system:

(1) Materiel identification as to type, quantity, and potential hazards.

(2) Safety precautions and procedures necessary during use, storage, transportation, and disposal.

(3) A copy of the Safety Data Sheets (SDSs) as required.

c. A statement that the system does not contain or generate hazardous materials (i.e., explosive, toxic, radioactive, carcinogenic, etc.).

d. An attachment of all Final (if applicable) or Interim Hazard Classifications (FHCs/IHCs) generated for Ammunition and Explosive (A&E) materials and components:

Note: An IHC is required, at a minimum, for all ammunition items provided by the contractor.

(1) FHCs and IHCs shall be generated in accordance with TB 700-2 and AOP-7.

(2) FHCs and IHCS shall demonstrate that propellant sustainability testing was performed as part of the FHC/IHC procedure.

e. A statement signed by the contractor system safety manager and the program manager stating that all identified hazards have been eliminated or controlled and that the system is ready to test, operate, or proceed to the next acquisition phase. In addition, include recommendations applicable to the safe interface of this system with the other system(s).

6. A references section. This section shall include a list of all pertinent references, such as test reports, preliminary operating manuals and maintenance manuals. 1) Used to identify potential hazards that test personnel and Soldiers may be exposed to during system operation.

2) Determine if the system is at an acceptable level of risk for testing/TiC/general acquisition.

3) Used in the generation of a Safety Release.

1. A system description section. This will consist of summary descriptions of the physical and functional characteristics of the system and its components. Reference to more detailed system and component descriptions, including specifications and detailed review documentation shall be supplied when such documentation is available. The capabilities, limitations and interdependence of these components shall be expressed in terms relevant to safety. The system and components shall be addressed in relation to its mission and its operational environment. System block diagrams or functional flow diagrams may be used to clarify system descriptions. Software and its role(s) shall be included in this description.

2. A data section. This will consist of summaries of data used to determine the safety aspects of design features.

3. A hazard analysis results section. This will consist of a summary or a total listing of the results of hazard analysis. The following are the content and format requirements:

a. A summary of the results, to include the following:

(1) A discussion of specific analyses performed to address software safety risks and Level of Rigor (LoR), to include the following:

i. Summary of Safety-Related (SR), Safety-Critical (SC), and Non-Safety-Significant (NSS) functions identified.

ii. Summary of Software Criticality Index (SwCI) functional allocations.

iii. A statement of whether LoR tasks are complete, or in progress, and what LoR tasks were specified.

b. A listing of identified hazards, in narrative or matrix (sometimes called columnar or tabular) format, to include the following information:

(1) System/subsystem/unit. The particular part of the system that this analysis is concerned with. For example, if this item(s) applies to a radar system modulator, use “modulator.” If there are several modulators in the system, clearly specify which one the analysis pertains to.

(2) Component(s) failure mode(s). All component failure modes which can result in a hazard. Failure modes generally answer the question of “how” it fails.

(3) Subsystem failure mode(s). The subsystem failure mode descriptions for the system hazard analysis (SHA) are similar to the component descriptions provided in the subsystem hazard analysis (SSHA). However, emphasis is now placed on failure affecting interfacing subsystem operations.

(4) System component/phase. The particular phase/component that the analysis is concerned with. This could be a system, subsystem, component, software, operating/maintenance procedure or environmental condition.

(5) System event(s) phase. The configuration of phase of the mission the system is in when the hazard is encountered, for example, during maintenance, during flight, during pre-flight, full-power applied, etc., or it could be encountered in all system events.

(6) System operation description. A description of what is normally expected to occur as the result of operating the component/subsystem or performing the operating/maintenance action.

(7) Hazard description.

(a) A brief description of the hazard of hazardous material, for example, “Radiation leakage from radar set waveguide.”

(b) A complete description of the potential/actual hazards inherent in the item being analyzed, or resulting from normal actions or equipment failure, or handling of hazardous materials.

(8) Hazard identification/indication. A description of operator/crew indications which include all means of identifying the hazard to operational/maintenance personnel.

(9) Effect of hazard. The detrimental effects which could be inflected on the subsystem, system, other equipment, facilities or personnel, resulting from this hazard. Possible upstream and downstream effects shall also be described.

(10) Risk assessment. A risk assessment for each hazard (classification of severity and probability of occurrence). This is the assessment of the risk prior to taking any action to eliminate or control the hazard.

(a) Risk assessment criteria shall be in accordance with MIL-STD-882E, Change 1.

(11) Recommended action. The recommended action required to…