CDRL_A001.PA32.GD_7.3M_Antenna.pdf

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contractor Officer for the Contract/PR No. Listed in Block E.

A. CONTRACT LINE ITEM NO.

B. EXHIBIT

A

C. CATEGORY:

TDP _________ TM- _________ OTHER SAFT

D. SYSTEM / ITEM

GD 7.3M ANTENNA

E. CONTRACT / PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

SYSTEM SAFETY PROGRAM PLAN

3. SUBTITLE

Safety Systems/Work Management Plan

4. AUTHORITY (Data Acquisition Document No.)

FAA-DI-SAFT-102

5. CONTRACT REFERENCE

SOW Section 6.0

6. REQUIRING OFFICER

NSWC Corona PA32

7. DD 250 REQ.

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

LT ASREQ ASREQ b. COPIES

8. APP CODE C 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft

Final

A N/A ASREQ Reg Repr o

16. REMARKS

Blk 8 - Approval shall be for relevant content; the government has 10 days to review, and the contractor has 10 days to incorporate any changes and return to the government.

Blk 9 - "DISTRIBUTION STATEMENT C: Distribution authorized to U. S. Government agencies and their contractors only (Administrative Use). (08 May 2013). Other requests for this document shall be referred to the Naval Surface Warfare Center, Corona Division, CA, Code CM013."

Blk 10, 12, 13 - The System Safety Program Plan shall be delivered no later than 30 days PRIOR to a scheduled move date. Once the move date has been set, by the COR/Tech POC, the date shall be communicated to the contractor, via email.

Blk 14 - ELECTRONIC COPIES WILL BE EMAILED TO CODE CM013 IN

MICROSOFT OFFICE FORMAT: jessica.ostarcevic@navy.mil and joseph.edgman@navy.mil

*A sample safety plan is available upon request (joseph.edgman@navy.mil).

COR/Tech POC

Khai Trinh

1 1

15. TOTAL 1 1

G. PREPARED BY

//s// Khai H. Trinh

H. DATE

02/22/2016

I. APPROVED BY

J. DATE

03/15/2016

DD Form 1423–1, FEB 2001 Previous editions are obsolete Page __1__ of __1__ Pages

DATA ITEM DESCRIPTION

1. TITLE

System Safety Program Plan

2. IDENTIFICATION NUMBER

FAA-DI-SAFT-102

3. DESCRIPTION/PURPOSE

3.1 The Contractor shall detail in the System Safety Program Plan (SSPP) the Contractor’s program scope, safety organization, program milestones, requirements and criteria, hazard analyses, safety data, safety verification, audit program, training, accident/incident reporting, and interfaces.

4. APPROVAL DATE (YYYY/MM/DD) 5. OFFICE OF PRIMARY RESPONSIBLILITY (OPR)

OFFICE OF SYSTEM ARCHITECTURE AND INVESTMENT ANALYSIS (ASD)

6. APPLICATION/INTERRELATIONSHIP

6.1 This Data Item Description (DID) contains the format and content preparation instructions for the SSPP.

7. PREPARATION INTRUCTIONS

7.1 Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract and in accordance with the NAS Modernization System Safety Management Program (SSMP) in the Acquisition Management System FAST Toolset.

7.2 Format. The SSPP format shall be “contractor selected.” Unless the effective presentation would be degraded, the initially selected format must be used for all subsequent submissions.

7.3 Content. The SSPP includes details of those methods the contractor uses to implement each system safety task called for in the Government provided Integrated Safety Plan (ISP), the Statement of Work, and those safety-related documents listed in the contract for compliance. Examples of safety-related documents include Occupational Safety and Health Administration (OSHA) regulations and other national standards, such as the National Fire Protection Association (NFPA). The SSPP lists all requirements and activities required to satisfy the system safety program objectives, including all appropriate, related tasks. A complete breakdown of system safety tasks, subtasks, and resource allocations of each program element through the term of the contract is also included. A baseline plan is required at the beginning of the first contractual phase (e.g., Demonstration and Validation or Full-Scale Development) and is updated at the beginning of each subsequent phase (e.g., Production) to describe the tasks and responsibilities for the follow-on phase.

The SSPP shall contain the following items:

7.3.1 Program Scope: The plan shall include a systematic, detailed description of the scope and magnitude of the overall SSPP and its tasks. This includes a breakdown of the project by organizational component, safety tasks, subtasks, events, and responsibilities of each organizational element, including resource allocations and the contractor’s estimate of the level of effort necessary to effectively accomplish the contractual task.

7.3.2 System Safety Organization: Detail the System Safety Organization, including the following information:

The system safety organization or function as it relates to the program organization

Responsibility and authority of all personnel with significant safety interfaces

The staffing plan of the system safety organization for the duration of the contract

The procedures by which the contractor will integrate and coordinate the system safety efforts

MM/DD/YYYY Previous editions are obsolete Page 1 of 2

Block 7, PREPARATION INSTRUCTIONS (Continued)

The process by which contractor management decisions will be made

Who/Organization that does the work

Organization that approves the work internally

Organization that receives the work

How the contractor will interface with the program office and FAA NAS Modernization System Safety Working Group (SSWG)

7.3.3 Program Milestones: Briefly describe the safety tasks and products. Include a program schedule (e.g., Gantt chart) of the safety tasks, including start and completion dates, reports, design reviews, and estimated staff loading.

7.3.3.1 Work Products: Describe work products (i.e., Subsystem Hazard Analysis, System Hazard Analysis, Operating and Support Hazard Analysis, and Health Hazard Assessment).

7.3.4 Requirements and Criteria: Describe the Safety Performance Requirements (performance requirements can be stated using, e.g., qualitative values, accident risk values, or standardized values); Safety Design Requirements (the program team should establish specific safety design requirements for the overall system) and required documentation (include description of risk assessment procedures (types of analyses to be performed) and safety precedence (the method of controlling specific unacceptable hazards); and in accordance with the NAS System Engineering Manual (SEM), Section 4.3.

7.3.5 Hazard Analyses: Describe the specific analyses to be performed during the program. The analysis techniques and formats should be qualitative or quantitative to identify risks, their hazards and effects, hazard elimination, or risk reduction requirements, and how these requirements are to be met, in accordance with NAS

SSMP.

7.3.6 Safety Data: Provide a list of system safety tasks, contract data requirements list (CDRL) having safety significance, and the requirement for a contractor system safety data file. The data in the file is not deliverable but is to be made available for the procuring activity's review on request.

7.3.7 Safety Verification: Describe the safety verification test and/or assessment program to be used to demonstrate the safety verification process, in accordance with SEM, Section 4.12.

7.3.8 Audit Program: Describe the techniques and procedures to be used for the audit program.

7.3.9 Training: Once the hazards related to training have been identified, describe the procedures to be applied in training operator, maintenance, and test personnel.

7.3.10 Accident/Incident Reporting: Describe the details and timing of the notification process for the program and the method of ensuring that the incidents/accidents are translated to hazards. Once the hazards are identified, they must be incorporated into a hazard tracking system.

7.3.11 Interfaces: Describe the requirements used to coordinate all the different interfaces of the contract, in accordance with SEM, Section 4.7.

MM/DD/YYYY Previous editions are obsolete Page 2 of 2