SIMO RFP 80KSC027R0001 DRDs.pdf
PDF 2 MB Posted
- Solicitation number
- 80KSC027R0001
About this file
This file is a PDF portfolio cover page. The image displays an Adobe Acrobat binder graphic with the Adobe Reader logo and contains a message instructing users to open the PDF portfolio in Acrobat X or Adobe Reader X, or later versions for optimal viewing experience. A "Get Adobe Reader Now!" button is provided for users to download the required software. The document contains no substantive information regarding federal contract opportunities, products, services, timelines, or other procurement-related details.
View the file
Other files
Show all 15
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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
Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Data Requirement
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Page of
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Instruction Page of
J. Distribution
Totals
No.
Type
Data Requirement Description
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)
Code
Inspection
Acceptance
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:
Code
Description
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
Code
Description
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
Code
Description
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:
Code
Description
A Regular B Reproducible
Code
Description
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.
11.0.0.20130303.1.892433.887364
Data Requirement KSC FORM 16-246 Rev 06/13, Created 04/14 Version 1.0
04/14
KSC Forms
Data Requirement
06/13
1.0
CurrentMasterPage:
MasterPageCount:
DummyBTN:
submit:
DRL: SIMO
ItemNumber: 1.2-01
LineItemTitle: Safety and Health (S&H) Plan
OPR: COR
Type: 1
InspectAcceptance: 2
Frequency: AN/AR
InitialSub: See I. Remarks
AsOfDate: See I. Remarks
Remarks:
G. The initial submittal shall be due within 30 days after contract award for Government review and approval.
H. In order to ensure that the Plan remains current, the Contractor will annually submit a letter by October 1st stating that the Plan remains unchanged, or will submit changes/updates to the plan.
J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software.
Cell1: Initial submittal to the Contracting Officer and Contracting Officer's Representative (1A) Revisions submitted through the Government contract management portal (1D)
Cell1: 1
Cell1: 1
Cell2: A
Cell2: D
Title: Plan, Safety and Health (S&H)
TitleNumber: N/A
Use: To ensure the Contract is conducted in a safe manner and complies with all S&H directives, instructions, policies, and regulations as listed in this Contract. To verify the Contractor intends to be proactive in S&H practices so that employees have a safe work environment/conditions.
Date: 2026-10-28
Organization: KSC
References: N/A
Interrelationship: N/A
PreparationInformation:
1. The S&H Plan shall describe tasks and activities of the S&H management at each site where the Contractor is operational to assure identification, evaluation and elimination/control of S&H concerns. At a minimum, the plan shall include all requirements specified in NFS 1852.226-74, Safety and Health and other safety and health documents listed in Appendix J-01-03, Compliance Documents. In addition to compliance with NFS provision 1852.226-74, the S&H Plan shall comply with and provide the following:
a. Organizational charts(s) illustrating the functional relationships and lines of communication between the S&H organization and other organizational elements, including all subcontracts.
b. Descriptions of the S&H management functions within the organization including authorities, responsibilities, and the process through which management decisions will be made, and notification to NASA KSC S&H organizations of hazards, mishaps and close calls, corrective actions, and deviations/waivers to NASA S&H requirements.
c. Description of the responsibility, authority, and accountability of S&H personnel and other Contractor organizational elements involved in S&H to include subcontractor S&H personnel. Include the organizational unit responsible for the execution of S&H tasks and the position with the authority to resolve identified S&H issues.
d. Description of the management controls that will be used to ensure compliance to S&H regulations.
e. Contractor's S&H program structure in accordance with Occupational Safety and Health Administration Instruction, CSP 03-01-005, Voluntary Protection Programs (VPP) Policies and Procedures Manual, Chapter 4.
f. Policies, procedures, and techniques that will be used to ensure the S&H of the public, astronauts and pilots, the NASA workforce (including Contractor employees working on NASA contracts), and high-value equipment and property.
g. Description of the safety program measurement system, including internal audits, assessments, surveillances, inspections, safety measurements, safety metrics, and trend analysis to determine if the S&H program is effectively implemented. The performance measurement system should describe responsibility for identifying and implementing remedial actions, recurrence control, corrective actions, and preventative actions necessary to improve performance as indicated by the performance measurement system.
h. Mishap Preparedness and Contingency Plan that describes how support and services will continue in the event of a mishap, in accordance with KSC-PLN-2807, Mishap Preparedness and Contingency Plan. The Contractor shall describe the contractor’s mishap and close call response, reporting, and resolution process(es) including initial response, notifications, evidence gathering, investigation, release of the mishap or high-visibility close-call scene for continued operations, report of findings, approach to performing root cause analyses for mishap and close call investigations, and implementation of corrective actions.
i. Description of the safety analysis methodologies used to identify workplace and FSEU hazards and how developed mitigation will be implemented throughout the Contractor’s organizations for NASA KSC programs and projects. Include a System Safety Program Plan (SSPP) that describes how initial hazard and risk assessments are performed on SIMO controlled FSEU and used to determine any additional analyses required, in addition to the development/maintenance of those safety and reliability analyses.
j. Description of the Contractor's safety program and how it conforms with KNPR 8715.7, KSC Construction Contractor Safety and Health Practices Procedural Requirements for Construction, if applicable, including addressing subcontractor employee S&H.
k. Description of the Contractor's electrical safety program, including addressing subcontractor employee S&H.
l. The plan shall similarly address subcontractor employee S&H for those proposed subcontracts that contain one or more of the following conditions:
(1) The work will be conducted completely or partly on premises owned or controlled by the government.
(2) The work includes alteration, or repair of facilities in excess of the simplified acquisition threshold.
(3) The work, regardless of place of performance, involves hazards that could endanger the public, astronauts and pilots, the NASA workforce (including Contractor employees working on NASA contracts), or high value equipment or property, and the hazards are not adequately addressed by OSHA or Department of Transportation (DOT) regulations (if applicable).
The Contractor shall review the Plan annually and shall revise the Plan as required and when major organizational changes occur in the lines of communication between the S&H organization and other organizational elements or when procedures or processes have changed that affect organizational responsibility, authority, or accountability. The Contractor shall submit the revised plan to NASA within 30 days of the revision.
viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other
NRRS 5/13.A
Page of
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Instruction Page of
J. Distribution
Totals
No.
Type
Data Requirement Description
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)
Code
Inspection
Acceptance
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:
Code
Description
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
Code
Description
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
Code
Description
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:
Code
Description
A Regular B Reproducible
Code
Description
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.
11.0.0.20130303.1.892433.887364
Data Requirement KSC FORM 16-246 Rev 06/13, Created 04/14 Version 1.0
04/14
KSC Forms
Data Requirement
06/13
1.0
CurrentMasterPage:
MasterPageCount:
DummyBTN:
submit:
DRL: SIMO
ItemNumber: 1.2-02
LineItemTitle: Internal Surveillance Plan
OPR: COR
Type: 3
InspectAcceptance: 6
Frequency: AN/AR
InitialSub: See I. Remarks
AsOfDate: See I. Remarks
Remarks: G. The Contractor Internal Surveillance Plan is due within 30 days after contract award for Government review and approval.
H. The plan shall be reviewed annually and if changes, submit revisions by October 1st. Changes shall be identified and summarized on a change page summary log.
J. Type "D": Electronic submittal. Product shall be compatible with Microsoft Office suite of software.
Cell1: Initial submittal to the Contracting Officer and Contracting Officer's Representative (1A) Revisions submitted through the Government contract management portal (1D)
Cell1: 1
Cell1: 1
Cell2: A
Cell2: D
Title: Plan, Internal Surveillance
TitleNumber: N/A
Use: Provides Government insight into Contractor surveillance and measurement of Contractor performance, and the methodology for managing technical, operations, and interfaces between their contract, subcontractors, other contractors or entities, and the Government.
Date: 2026-10-28
Organization: KSC
References: N/A
Interrelationship: DRD 1.2-12, Risk Management Plan
PreparationInformation:
The Contractor shall develop and maintain an Internal Surveillance Plan that describes the Contractor's approach to surveillance and measurement of the significant areas of contractor performance including, but not limited to, the following:
1. Customer Satisfaction
2. Resource Management
3. Reporting and Deliverables
4. Measurement of Performance Metrics and Work Load Indicators
5. Internal Audits/Assessments
6. Preventive and Corrective Actions
7. Environmental Compliance
8. Continuous Improvement
9. Risk Management
10. ASQ/ISO 9001:2026 Compliance
11. Lines of responsibility, authority and communication
To implement the above areas of contract performance, the Contractor shall provide:
a. Narrative and graphical descriptions of the management, technical, and business approaches, strategies, policies and processes used to accomplish and monitor contractual tasks and performance; integrate cost, schedule and technical performance across all areas of the contract, including methods the contractor will employ to provide Government insight and data accessibility.
b. Organizational chart(s) illustrating the functional relationships and lines of communication between organizational elements including communication path with the Government technical authority.
c. Interfaces between the Contractor, subcontractor(s), NASA, and other contractors or entities pertinent to the accomplishment of contractual tasks.
d. The Contractor’s approach and rationale to performance management including specific performance objectives, measurements, standards, and tools which are used to manage, report, improve and adapt performance.
e. The Contractor’s approach to identifying, resolving, and prioritizing conflicts between contract performance and the Contractor’s work in support of multiple Government and commercial customers.
f. The Contractor’s acquisition strategy, including make/buy decisions and rationale, and subcontractor management.
g. The Contractor controls applicable to any tasks, activities and projects exceeding established cost or schedule baselines and discuss the Contractor’s approach and methods to recover, while ensuring the full scope of contracted effort is delivered in accordance with the contractual obligations.
h. The Contractor’s approach to minimizing the cost to the Government for Government-provided services and applications and Contractor purchased applications, in addtion to identifying, evaluating, capturing, implementing, and tracking Contractor identified cost savings.
i. The method by which the Contractor will provide the Government on-going access to data, both remotely and on-site, in a usable and readable format; and provide the Government the ability to locate and review all data used in performance of this contract, to include technical data, supporting data/information, and administrative and management information. The Contractor shall provide the Government unrestricted access to all data generated or compiled in the performance of this contract and shall respond within a reasonable amount of time to Government requests for data that is not immediately available. Data generated during contract performance will remain the property of the Government.
j. The interactive approach to jointly evaluating and updating the insight processes to improve joint NASA-Contractor team performance with established feedback and disposition points throughout the life of the contract. Process for resolving concerns and issues identified by NASA and its support services contractor’s and commercial parties. This shall include:
(1) The process to permit timely elevation of issues to NASA.
(2) The process of highlighting critical activities of interest (such as changes, decisions, key events, critical meetings) to NASA.
k. The process of providing the Government insight into all subcontractors and suppliers performing or supporting any critical work associated with this contract.
l. The Contractor shall provide a narrative which includes but is not limited to, the partnering approach and establishing a cooperative environment that ensures an effective working relationship between NASA and the Contractor. This approach shall describe the accommodations for Government personnel and its support services contractor(s), and timely and open access necessary to obtain a working-level understanding into all contractor activities. These accommodations shall include facility access, data, and any other information including technical and management processes required to meet contract requirements. The Internal Surveillance Plan shall identify instructions or training required to allow for meaningful NASA insight and participation.
m. The Contractor shall allow NASA participation in Contractor and subcontractor internal, external, ISO, and third-party audits upon request. NASA insight will consist of monitoring NASA-selected audits with the Contractor’s auditors and inspectors in order to provide understanding of the Contractor’s quality system and insight of their processes.
n. The Contractor’s approach to managing the contract scope, including performance management, teaming, communication, strategies, policies, processes for work planning, work prioritization, subcontractor management, Associate Contractor Agreements (ACAs), any efficiencies planned, and systems and processes to provide overall coordination of management activities under this contract. The Contractor shall provide staffing, organizational structure, reporting structures, management approaches, and processes used across the entire contract.
o. To support NASA insight, the Contractor shall provide access to designated NASA personnel and NASA support contractors at NASA Centers to Contractor database(s) where electronic files are posted and revisions maintained for all quality information such as: audit schedules, audit reports, Material Review Board (MRB) actions and minutes, nonconformances, discrepancy reports, anomalies, deviations and waivers, and data. This may take the form of read-only access to Quality Assurance database systems containing this information and to which the Contractor has regular and timely input.
Remarks: It is not intended that this plan duplicate other plans called for in other DRDs. This plan shall summarize the overall contract and reference or summarize other plans where appropriate and shall reference Contractor internal procedures where applicable.
viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other
NRRS 5/13.A
Page of
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Instruction Page of
J. Distribution
Totals
No.
Type
Data Requirement Description
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)
Code
Inspection
Acceptance
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:
Code
Description
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
Code
Description
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
Code
Description
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:
Code
Description
A Regular B Reproducible
Code
Description
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.
11.0.0.20130303.1.892433.887364
Data Requirement KSC FORM 16-246 Rev 06/13, Created 04/14 Version 1.0
04/14
KSC Forms
Data Requirement
06/13
1.0
CurrentMasterPage:
MasterPageCount:
DummyBTN:
submit:
DRL: SIMO
ItemNumber: 1.2-03
LineItemTitle: Contract Performance Metrics and Actuals Report
OPR: COR
Type: 3
InspectAcceptance: 6
Frequency: MO
InitialSub: N/A
AsOfDate: 30/10
Remarks:
J. Type "D": Electronic submittal. Product shall be submitted in Microsoft Excel.
Cell1: Government contract management portal
Cell1: 1
Cell2: D
Title: Report, Contract Performance Metrics and Actuals
TitleNumber: N/A
Use: To provide Government insight into Contractor performance and productivity in all areas of the contract and existing or potential problem areas
Date: 2026-10-28
Organization: KSC
References: N/A
Interrelationship: N/A
PreparationInformation:
Metrics: The Contractor shall develop, maintain, analyze, track, and report performance metrics for all performance standards identified in PWS Section 9.0. The Contractor shall provide a self-evaluation of the metric and report existing or potential problem areas with recommended solutions. The report shall identify contract title and contract number.
Actuals: The Contractor shall track and report, by customer identifiers (reference Tech Exhibit 1.2.1-1, Customer Identifiers), actual workload performance in the categories provided (see template). The Contractor shall also track and report all Core Work, Maintenance Support Request (MSR) tasks and Attachment J-05, Pre-priced IDIQ Work Catalog tasks by customer. Additionally, the Contractor shall develop other performance trends, and add actuals requested by the CO or COR.
viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other
NRRS 5/13.A
Page of
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Instruction Page of
J. Distribution
Totals
No.
Type
Data Requirement Description
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)
Code
Inspection
Acceptance
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:
Code
Description
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
Code
Description
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
Code
Description
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:
Code
Description
A Regular B Reproducible
Code
Description
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.
11.0.0.20130303.1.892433.887364
Data Requirement KSC FORM 16-246 Rev 06/13, Created 04/14 Version 1.0
04/14
KSC Forms
Data Requirement
06/13
1.0
CurrentMasterPage:
MasterPageCount:
DummyBTN:
submit:
DRL: SIMO
ItemNumber: 1.2-04
LineItemTitle: Personnel Certification, Licenses, and Training Plan and Report
OPR: COR
Type: 3
InspectAcceptance: 4
Frequency: AN/AR
InitialSub: See I. Remarks
AsOfDate: 365/30
Remarks:
F. Submitted on an annual basis, or more frequently when updates are required due to changes (i.e., personnel, certification, training).
G. Initial submittal be due within 30 days after contract award.
J. Type "D": Electronic submittal. Contractor format is acceptable.
Cell1:
Government contract management portal
Cell1: 1
Cell2: D
Title: Plan and Report, Personnel Certification, Licenses, and Training
TitleNumber: N/A
Use: To provide a baseline document for the identification, definition, and approach for personnel certification. Provides verification and Certificate of Conformance that required certifications, licenses, and training is obtained by the workforce.
Date: 2026-10-28
Organization: KSC
References: PWS 1.2.1 Nos. 3 and 4
Interrelationship: N/A
PreparationInformation:
1. Initial submittal shall include the following to ensure certifications, licenses, and training requirements will be met:
a. Approach to communicating (method and frequency) contract requirements to workforce.
b. Specific training programs, testing, education, and documentation for performing work or obtaining required certifications.
c. Certification program (i.e., apprenticeship, journeyman) to include, but not be limited to, program description, method to select operations or classifications requiring a certification, requirements/skills, certification process, on-the-job-training.
d. Specific operations, classifications, or hazardous work requiring training or certification. This can be determined by the operations and processes identified in the PWS.
e. Approach to maintaining knowledge, skills, and capabilities required to perform functional areas of the contract (to include project management, design, analysis, configuration management, operations, and sustaining engineering).
f. Approach and processes for providing and tracking the completion of necessary orientation, training, and certifications necessary for employees to assume and perform functions required by the PWS.
g. Schedule for the workforce to meet the above requirements.
2. Final and recurring submittals will include above information, as well as the following regarding the workforce:
a. Report of individual personnel and their respective Certification, Licenses, and Training.
b. Any Certification, Licenses, and Training in work.
c. Any missed requirements and the actions being taken to meet the requirement.
viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other
NRRS 5/13.A
Page of
KSC FORM 16-246 NS 06/13 (1.0) PREVIOUS EDITIONS ARE OBSOLETE. Validate prior to use.
NRRS 5/13.A
Instruction Page of
J. Distribution
Totals
No.
Type
Data Requirement Description
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)
Code
Inspection
Acceptance
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:
Code
Description
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
Code
Description
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
Code
Description
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:
Code
Description
A Regular B Reproducible
Code
Description
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,…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .