Attachment_3_-_Data_Requirements.pdf

80KSC018R0020

ATTACHMENT 3

DATA REQUIREMENTS LIST (DRL) /

DATA REQUIEMENTS DESCRIPTIONS (DRDs)

FOR

REFUSE COLLECTION AND DISPOSAL SERVICES

JOHN F. KENNEDY SPACE CENTER (KSC), FLORIDA

80KSC018R0020 ATTACHMENT 3

All plans, schedules, reports, submittals, logs, and information provided to the Government shall be electronic and compatible with

Microsoft Office 2003 or higher, such as Excel, Word, and others. “Compatible” means the document can be opened using the appropriate Microsoft Office component without any discernible effect on the text (e.g., loss of data) or the formatting of the document:

DATA REQUIREMENTS LIST

DRL NUMBER: REVISION

Basic

PROJECT/SYSTEM

KSC Refuse Collection and Disposal Services

CONTRACT NUMBER PREPARATION DATE

TBD TBD

CONTRACTOR TECHNICAL APPROVAL

TBD TBD

ATTACHMENT NUMBER EXHIBIT NUMBER

N/A

ITEM

NO.

TITLE CHANGE STATUS

1 Quality Management System, PWS paragraph 4.2.2.

2 Service Plan and Schedule, PWS paragraph 1.1.

3 Disposal Report and Documentation, PWS paragraph 1.6.3.

4 Damage, Injury and Incident Reports, PWS paragraph 4.11.1

80KSC018R0020 ATTACHMENT 3

INSTRUCTIONS FOR COMPLETING CONTRACT

APPLICATION INFORMATION

A. LINE ITEM NO. 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 organizational 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 CODE INSPECTION ACCEPTANCE

1 Source Source 4 Certificate of Conformance (Mandatory) 2 Destination (OPR) Destination (OPR) 5 Certificate of Conformance (Optional) 3 Source Destination (OPR) 6 No Inspection Required No Acceptance Required

F. FREQ. OF SUBM. - Enter the frequency of submission code as follows:

CODE DESCRIPTION CODE DESCRIPTION CODE DESCRIPTION

AD AS DIRECTED PC PER CONTRACT PV PER VEHICLE

AN ANNUAL PD PER FAILURE QU QUARTERLY

AR AS REQUIRED PE PER EVENT RD AS RELEASED

BE BIENNIAL PF PER FACILITY RT ONE TIME & REVISIONS

BM BIMONTHLY (every two months) PG PER PROGRAM SA SEMI ANNUALLY BW BIWEEKLY (every two weeks) PI PER EQUIPMENT END ITEM SM SEMI MONTHLY

DA DAILY PJ PER PROJECT TY THREE YEAR PERIOD

DD DEFERRED DELIVERY PL PER LAUNCH FLIGHT MISSION UR UPON REQUEST

MO MONTHLY PS PER SYSTEM WK WEEKLY

OT ONE TIME PT PER TEST

G. INITIAL SUBMITTAL- Enter 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.

J. 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 specified. (This data may be removed at final approval.)

d. Additional submittal information, if necessary.

K. 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 DEFINITION CODE DEFINITION

A Regular C Microfilm, Aperture Cards B Reproducible D Other, (Explain in remarks, Item J).

EXAMPLE ENTRIES: IS-PRO-2 (1A) = One regular copy.

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

Enter the total number of copies by type in the space provided

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 established 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)

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 installations, 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.

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.

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 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 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