DRFP 80KSC027R0001 DRDs.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

Data Requirement

KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use. NRRS 5/13.A

Contract Application Information for DRL SIMO A. Item Number 2.1-06

B. Line Item Title Construction of Facilities (CoF) and Local Authority (LA) Five-year Program Plans

C. OPR

COR

D. Type

E. Inspect / Accept

F. Frequency

AN

G. Initial Sub.

See I. Remarks

H. As of Date See 8. Preparation

I. Remarks

G. The initial submittal shall be due within 60 days after contract effective date.

J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software.

7. Interrelationship:

DRD 2.1-01, Five-year Maintenance Plan DRD 2.1-02, Annual Work Plan (AWP) DRD 2.1-03, Deferred Maintenance Report

J. Distribution Totals Government contract management portal No. Type

1 D

Data Requirement Description

1. Title Plans, CoF and LA Five-year Program

2. Number N/A

3. Use For communicating the NASA investment plan for institutional and programmatic Facilities, Systems, Equipment, and Utilities (FSEU) assets and seeking Center and/or Headquarters authorization and funding.

4. Date 09/14/2026

5. Organization

KSC

6. References

7. Interrelationship

8. Preparation Information

The Contractor shall develop and maintain CoF and LA program (5-year) plans that include estimates and prioritized project plans based on the KSC Master Plan, Deferred Maintenance (DM), maintenance data, Facility Condition Assessments (FCAs), personnel moves and office modifications, and environmental and energy goals/federal mandates.

The Contractor shall review and update the Plans for currency, accuracy, and relative priority at least once per year. Update the estimates annually to account for escalation and any changed conditions.

Submission shall be in alignment with budget calls for CoF and LA Programs which occur at different times of the year and may vary from year to year.

Instruction Page 1 of 1

Instructions for Completing Contract Application Information A. Line Item Number - Sequentially number line items beginning with number 001.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data requirement. Use approved organization code.

D. Type - Enter "Type of Data" code as follows:

Code Description 1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list to the procuring activity.

5 Data to be retained by the contractor and reviewed by NASA on request.

E. Inspect / Accept - Enter inspection Acceptance code as follows:

Code Inspection Acceptance

1 Source Source 2 Destination (OPR) Destination (OPR) 3 Source Destination (OPR)

4 Certificate of Conformance (Mandatory) 5 Certificate of Conformance (Optional) 6 No Inspection Required No Acceptance Required

F. Frequency of Submission - Enter the frequency of submission code as follows:

AD As Directed AN Annual AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery MO Monthly OT One-Time

PC Per Contract PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission PS Per System PT Per Test

PV Per Vehicle QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period UR Upon Request WK Weekly

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

I. Remarks: Enter in this space.

a. Minor exceptions to the DRD.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

d. Additional submittal information, if necessary.

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy codes are as follows:

A Regular B Reproducible

C Microfilm, Aperture Cards D Others (Explain in remarks, Item J)

Example Entries: Enter the total number of copies by type in the space provided.

IS-PRO-2 (1A) = One regular copy. IS-PO-3 (5, A, 1B) = Five Regular copies, One Reproducible copy.

Instructions for Completing Data Requirement Description General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in support of NASA programs.

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of the data. Subsequent words should be appropriate modifiers.

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

5. Organization - Identify the installation preparing the DRD.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data requirement.

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does not cause a conflict with other DRDs.

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all necessary details of preparation to satisfy the originator's formal requirements.

2.1-07

Mission Readiness Briefings

AR

J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software and posted to the Government contract management portal one day prior to the review. Briefings to be conducted in support of mission milestones.

Briefings, Mission Readiness

To perform a comprehensive internal integrated assessment of each pending mission or mission milestone.

5. Organization

KSC

8. Preparation Information

1. The Contractor shall deliver and present readiness briefings of each pending mission milestones and missions launched from KSC and CCSFS as required by the Government (e.g., before launch or major mission milestone). The readiness reviews and the associated briefings shall provide the required detailed insight to certify the completion or disposition of all tasks and planned work required to prepare for flight readiness. The briefings shall discuss the identification, elimination, or mitigation of safety or technical risks throughout the complete life cycle (design, development, manufacture, test, operations, maintenance, and disposal) of assigned facilities, systems, equipment, and utilities (FSEU) to ensure the safe performance of assigned mission objectives. These activities include (1) analytical methods, both quantitative and qualitative, as appropriate, in the assessment of the FSEU to assist the decision process for risk identification and mitigation; (2) exception, deviations, or waivers from safety requirements or other requirements with safety or mission success impact; and (3) assessment of significant off-nominal performance.

2. The Mission Readiness Briefings shall document the Contractor's support organizations readiness summaries for issues/status.

Attributes to be discussed include personnel availability, training and certifications; projected work hour deviations; currency and completion of required documentation (plans, drawings, procedures, preventive maintenance job plans); validations and visual checks; the identification of open work (unfinished maintenance, service, repair, calibration, modification, and/or anomaly/close call) affecting mission milestone readiness status; status of configured spares; concerns and constraints; and waivers and deviations.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

2.1-08

Facility and Equipment Readiness Reports

AR

G./H. Reports shall be submitted to the Government 45 days prior to major facility milestones (e.g., rollout, first lift in a facility), hazardous operations, scheduled spacecraft or payload support equipment (hereinafter referred to collectively as "payload") arrival/ established milestones, unless otherwise specified in the Launch Site Support Plan (LSSP). The Contractor shall verify processing facilities and equipment readiness a minimum of 30 days prior to operation or milestone, in a presentation at the Government led readiness reviews.

J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software

Reports, Facilities and Equipment Readiness

To verify that the facility and institutional equipment: 1) are ready to support processing and testing; and 2) meets established requirements. This includes first time payload processing as well as repeat processing.

5. Organization

KSC

See 8. Preparation Information

8. Preparation Information

I. Scope: All processing facilities, systems, and equipment for which the Contractor is assigned responsibility.

II. Statement of Facilities and Equipment Readiness (SoR):

A) The Contractor shall deliver a SoR to address the overall readiness of all processing facilities, systems, equipment, and commodities required to support the operation, milestone, processing, or testing throughout the required period. The SoR shall include all changes and modifications that have occurred since the last SoR. This verification statement shall be provided no less than 14 days prior to the operation or milestone.

III. Letter of Facilities and Equipment Readiness (LoR):

A) The Contractor shall deliver a LoR for continuous operational, non-hazardous facilities, whenever a repetitive customer or program payload is scheduled for delivery, the Contractor shall prepare and submit a LoR instead of the SoR described in II. A) above.

B) The LoR shall address any processing facility, systems, and equipment changes and modifications that have occurred since the last SoR or LoR. The Contractor shall verify in the LoR that all new requirements for facilities and ground equipment have been identified and satisfied.

C) An LoR shall be provided for transfers between previously activated facilities (e.g., payload returned from orbit to be processed for another flight. The intent is to make sure something hasn't gone out of maintenance after the spacecraft left and it has to return for planned or unplanned reasons).

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

2.1-09

Planning Rough Order of Magnitude (ROM) Accuracy Report

MO

30/10

J. Type "D": Electronic submittal. Product shall be submitted in Microsoft Excel and posted to the Government contract management portal.

Report, Planning ROM Accuracy

Determine accuracy of ROM estimates for projects.

5. Organization

KSC

8. Preparation Information

Contractor shall show comparison of initial project ROM to initially awarded task order value for the previous month's awarded task orders. Comparison shall clearly show both dollar and percentage variation from awarded project value. Report shall be rolling and include information from all previous months.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

2.1-10

Government-furnished Property Maintenance Plan

G. The initial submittal shall be due within 30 days after contract award for Government review and approval.

J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software.

Plan, Government-furnished Property Maintenance

See FAR 52.245-1, Government Property, paragraph (f)(1)(ix) and NFS 1852.245-83, Real Property Management Requirements, paragraph (b).

5. Organization

KSC

See 8. Preparation Information

8. Preparation Information

1. The plan shall describe Contractor’s maintenance program. The Contractor’s maintenance program shall enable the identification, disclosure, and performance of normal and routine preventative maintenance and repair. In addition, the program must provide for each asset assigned a heavy equipment number on Attachment J-10, Government-furnished Property the following: a schedule for normal and routine preventative maintenance activities to include frequencies.

2. The plan shall provide the information required by NFS 1852.245-83, Real Property Management Requirements, for real property.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

3.2.12-01

Bridge Inspections and Shoreline Report

F. Annual (AN) for railroad bridge reports and biennial (BE) for highway bridge reports.

G. and H. The Contractor shall provide a Bridge Inspection and Shoreline Report within 60 days after contract effective date.

Subsequent reports are due at 2 year intervals from initial submittal date for highway bridges and at 1 year intervals from initial submittal date for railroad bridges.

J. Type "D": Electronic submittal. Contractor format is acceptable.

Report, Bridge Inspections and Shoreline

To fulfill the requirement of bridge safety inspections per Code of Federal Regulations (CFR) 23CFR650 Subpart C, National Bridge Inspection Standards and 49CFR237 Subpart E, Bridge Inspection as specified in Performance Work Statement (PWS).

5. Organization

KSC

8. Preparation Information

The report shall be prepared in accordance with Florida Statute 335.074, Safety Inspection of Bridge; 23CFR650 Subpart C, National Bridge Inspection Standards; 49CFR237 Subpart E, Bridge Inspection; and consistent with American Association of State Highway and Transportation Officials (AASHTO) Manual for Bridge Element Inspection; Federal Highway Association (FHWA) IP-86026, Inspection of Fracture Critical Bridge Members; FHWA IP-90-017, Evaluating Scour at Bridges; FHWA-NHI-10-027, Underwater Bridge Inspection; the guidelines published in Florida Department of Transportation (FDOT) "Bridge Management System Coding Guide;" American Railway Engineering and Maintenance of Way Association (AREMA) Bridge Inspection Handbook; ENG-I- BI01, Internal Biennial Inspection of Bridges at KSC and NASA Guide for Bridge and Culvert Evaluation.

Provide a separate report for each KSC bridge and one consolidated bridge shoreline inspection report.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

3.2.12-02

Traffic Control Devices Inspection Report

365/15

F. and G. Initial submittal shall be due within 60 days after contract effective date, and subsequent reports are due at 1 year intervals from initial submittal date.

Report, Traffic Control Devices Inspection

To fulfill the requirement of maintaining traffic control devices per the Manual of Uniform Traffic Control Devices (MUTCD) retroreflectivity standards and as specified in the Performance Work Statement (PWS).

5. Organization

KSC

8. Preparation Information

The report shall include the following in accordance with PWS Section 3.2.12.3 System Specific Operations:

1. Traffic control signage assessment, sign inventory with sign attributes, inspection date, and applicable notes.

2. Pavement marking assessment, inspection date, and applicable notes.

3. Helipad markings/windsock/lighting assessment, inspection date, and applicable notes.

4. Traffic signal assessment, inspection date, and applicable notes.

5. Provide a consolidated list of missing, damaged, end of service life, or otherwise non-conforming traffic control devices.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

3.2.12-03

Saturn Channel Waterway Survey Report

BE

04/01/27

730/30

F. and G. Initial Submittal April 1, 2027, and subsequent reports are due at 2 year intervals from initial submittal date.

Report, Saturn Channel Waterway Survey

To monitor depth of the Saturn Channel and plan for future required dredging.

5. Organization

KSC

8. Preparation Information

The Saturn Channel begins at its intersection with the Canaveral Barge Canal one-quarter mile west of the Canaveral Lock and proceeds northerly in the Banana River, terminating at the LC-39 Wharf and Hangar AF Wharf. The Saturn Channel is 18.2 miles long, 125 feet wide, and has a design depth of 12 feet plus 1-foot overdepth below mean low water. The Saturn Channel alignment is identified by the use of aids to navigation. Include the KARS Park Cut in scope. The KARS Park Cut originates at the boat ramp at KARS Park, extends eastward 1 mile to intersect with the Saturn Channel, is 75 feet wide, and has a design depth of 5 feet plus 1-foot overdepth.

The Contractor shall provide a consolidated Saturn Channel Waterway Survey Report. The report shall include the following:

1. Take a water profile along the centerline and each toe edge of the channel.

2. Provide drawings of the channel survey with plan and cross-section views; identify channel makers.

3. Calculate the quantity of dredge material (per channel cut, widener, and turn basin) that needs to be removed to achieve the design depth of 12 feet below mean low water and with 1-foot over-depth allowance.

4. Use cross-sections of 2,000 foot intervals in the main channel, 100-foot intervals in the wideners, and 50-foot intervals in the Launch Complex 39 Unloading Facility and Hangar AF turn basins. Closer cross-sections can be used (as required by site conditions) for greater detail on the channel survey.

5. Interpretation of survey information for channel maintenance requirements and the implementation of maintenance dredging efforts.

6. 5-year dredging plan including maintenance dredging effort by channel section and associated estimated costs.

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide preparation information for data required in

1. Title - Enter the title or type of document required. The first word of the title should be a principal noun which best establishes the basic concept of

Examples: Plan, Project Development (SIVB); Specification, Test (GSE); Report, Quarterly Progress; Proposal, Engineering Change (ECP)

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

2. Number - Enter the appropriate number assigned to the DRD. This number will identify the appropriate data category.

3. Use - Enter a synopsis of the use of the document, stating reason for the requirement.

4. Date - Enter date of preparation.

6. References - List applicable documents by number, (NASA Management Manual, Mil Specifications, Federal Standards, NASA Procurement

Regulation, etc.) to which the preparing office (e.g., NASA installation, contractors, etc.) may refer for additional information concerning the data

7. Interrelationship - Enter all affected approved DRDs within the scope of the program when the DRD under preparation creates a significant impact or interface relationship with existing DRDs. Include a brief narrative of the impact or relationship created and a statement that the new DRD does

8. Preparation Information - Provide ample information for preparation of the data required by the data requirements description; include all

3.2.3-01

Protective Systems Out-of-Service Log

DA

Daily

G. Reports to be submitted starting second day after contract effective date.

Log, Protective Systems Out-of-Service

To ensure Console operators, fire fighting personnel, maintenance engineers and technicians are aware of impaired systems on Kennedy Space Center (KSC). This information is vital to responding fire department personnel and Maintenance and Operations (M&O) personnel.

5. Organization

KSC

8. Preparation Information

Contractor shall prepare a daily report of all Fire Alarm, Fire Suppression, Traffic, and Tornado Area Warning Systems that have been temporarily impaired. The list will include System type, Equipment Number, Facility Number, Operational Status, Estimated Completion Date (ECD)/Status, Start Date, Work Order Number (WON), Comments regarding basic scope and progress of work associated with the WON. The Impairment list shall also be subdivided into the following categories:

1. Impairments (Repair/Corrective action)

2. Impairments with Action Pending (Field Change Orders)

3. KSC Daily Support (Safing of fire alarm systems in support of work/activity that may cause false alarms)

4. KSC Traffic Systems Status

5. KSC Tornado Area Warning Systems (TAWS) Status

6. KSC Long Term Impairments With Action Pending Funding

B. Line Item Title - Enter the title of the data item, as shown in the Statement of Work (SOW), the RFP and / or as directed by the CTM.

C. OPR (Office of Primary Responsibility) - Enter the organization designated to exercise technical and / or administrative control over the data

1 Data requiring written approval by the procuring activity prior to implementation into the procurement or development program.

2 Data submitted to the procuring activity for review not later than three weeks prior to project implementation. Data shall be considered approved unless the contractor has been notified of disapproval prior to project implementation.

3 Data submitted to the procuring activity for coordination, surveillance, or information.

4 Data retained by the contractor to be made available to the procuring activity upon request. The contractor shall furnish a list

AR As Required BE Biennial BM BiMonthly (every two months) BW BiWeekly (every two weeks) DA Daily DD Deferred Delivery

PD Per Failure PE Per Event PF Per Facility PG Per Program PI Per Equipment End Item PJ Per Project PL Per Launch Flight Mission

QU Quarterly RD As Released RT One Time & Revisions SA Semi Annually SM Semi Monthly TY Three Year Period

G. Initial Submittal - Enter the date of initial submittal as follows: Month/Day/Year: If calendar date is not scheduled, enter number of days preceding, or following, event to which the data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item J, if necessary.

H. As Of Date - For "Onetime Only" submittals, enter date by Month/Day/Year. For recurring submittals, enter number coding (e.g., 30/10, 90/10, 15/5), etc. The first digit(s) indicate the number of calendar days from the reporting period's (Block F) start to the data preparation cut off. The second digit(s), after the slash, indicate the number of calendar days from the cut off to the submittal date. Example: If Block F were"MO" and Block H were "30/10", the data would include the entire month and would be submitted within 10 days thereafter.

b. Stipulation of specific forms when multiple forms are authorized on the DRD.

c. The paragraph, page, etc., in an existing contract where the data requirement is specific. (This data may be removed at final approval.)

J. Distribution - Enter organizational symbol, number of copies, and type of copy code(s) (in parenthesis) required for each office. Type of copy

General - The Data Requirement Description (DRD) will be prepared to describe the content and provide…