1、CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MWI 7120.2 REVISION C EFFECTIVE DATE: February 4, 2009 EXPIRATION DATE: February 4, 2014 MARSHALL WORK INSTRUCTION ED01 DATA REQUIREMENTS IDENTIFICATION/ DEFINITION
2、Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 2 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives
3、/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Canceled) Document Revision Effective Date Description Baseline 5/14/99 Revision A 8/16/99 Organizational change to reflect systems engineer versus chief engineer in paragraph 6.3. Wor
4、ds added to paragraph 5.2.15 to clarify verification data category. Revision B 10/5/2004 Complete Revision. Updated URL. Font changed to Times New Roman as directed. Changed approval signature. Ensured requirements are stated as “Who/What Shall”. Made document easier to follow by reorganizing to mov
5、e CDRM data to the end. Addressed ACI requirements, especially marking of contractor data. Emphasized use of an overall DRL in lieu of IDRD format by removing IDRD data. Specified data fields that must be captured in the DRL for accounting/tracking. Eliminated the Reports of Work at the request of P
6、rocurement. Added a more efficient way to address requirements for a small procurement. Added recommended control process definitions to be applied to NASA-produced data. Added sample Contracting Officers letter. Supporting text remains in the body of document. The use of “will” for direction to NAS
7、A and “shall” for direction to the contractor in examples of contract language remains in the document. Revision C 2/4/2009 Revised 2. Applicability statement to address the applicability of this directive to the Michoud Assembly Facility; throughout document, revised paragraphs to reflect one requi
8、rement per line item and renumbered accordingly; 5. Definitions, shorten definitions 5.2 and 5.13; 6.3 removed reference to Appendix B and inserted DRM Web site, delete last sentence; 6.3.2.1.c deleted Page Revision Log (PRL); 6.3.2.2b.1 deleted Page Revision Log; Moved Data Type definitions to Chap
9、ter 2; 9. Records, identified record schedules; Chapter 1, renumbered to be in accordance with MPR 1410.2; Appendix B deleted sample DPD, inserted DPD/DRL flowchart for contracts; Appendix C inserted DRL development flowchart for NASA activity; Renumber Appendix C as Appendix D, deleted sample DRD a
10、nd moved “Instructions for Elements of a DRD” to Chapter 1; renumbered and labeled Appendix Z correctly; defined in house (NASA activity) categories in Z.1.1.1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requir
11、ements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 3 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE TABLE OF CONTENTS PARAGRAPH PAGE TABLE OF CONTENTS. 3 1. PURPOSE. 4 2. AP
12、PLICABILITY. 4 3. APPLICABLE DOCUMENTS 4 4. REFERENCES . 4 5. DEFINITIONS 4 6. INSTRUCTIONS 6 6.1 IDENTIFICATION/DEFINITION OF DATA REQUIREMENTS. 6 6.2 DEVELOPMENT OF A DATA REQUIREMENTS LIST (DRL) FOR ALL NASA ACTIVITIES 6 6.3 DATA PROCUREMENT DOCUMENT (DPD) DEVELOPMENT. 7 6.4 CENTER DATA REQUIREME
13、NTS MANAGEMENT .11 7. NOTES13 8. SAFETY PRECAUTIONS AND WARNING NOTES .13 9. RECORDS 13 10. PERSONNEL TRAINING AND CERTIFICATIONS 14 11. FLOW DIAGRAM .14 12. CANCELLATION14 CHAPTER 1 INSTRUCTIONS FOR EACH ELEMENT15 CHAPTER 2 DATA TYPES.18 APPENDIX A DATA CATEGORY DEFINITIONS .20 APPENDIX B DATA PROC
14、URMENT DOCUMENT DEVELOPMENT FLOW 23 APPENDIX C DATA REQUIREMENTS LIST DEVELOPMENT FLOW FOR NASA ACTIVITY 24 APPENDIX D STANDARD DRD DEVELOPMENT .25 APPENDIX Z GUIDANCE 26 Z.1 DRL Template With Sample Data and Preparation Instructions.26 Z.2 Sample Contracting Officers Letter28 Provided by IHSNot for
15、 ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 4 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY
16、 THAT THIS IS THE CORRECT VERSION BEFORE USE 1. PURPOSE The purpose of this Marshall Work Instruction (MWI) is to establish detailed instructions for identification and definition of data requirements for Center institutional activities and programs/projects in accordance with MPR 7120.3, “Data Mana
17、gement, Programs/Projects,” for Marshall Space Flight Center (MSFC) Data Management. 2. APPLICABILITY 2.1 This MWI applies to the personnel, programs, projects, and activities at MSFC and MSFCs Michoud Assembly Facility, including contractors and resident agencies to the extent specified in their re
18、spective contracts or agreements. (“Contractors,” for purposes of this paragraph, include contractors, grantees, Cooperative Agreement recipients, Space Act Agreement partners, or other agreement parties.) 2.2 Data may be generated by and/or acquired from contractors, principal investigators, in-hou
19、se MSFC organizations, other National Aeronautics and Space Administration (NASA) centers, or other Government organizations. 3. APPLICABLE DOCUMENTS a. NPR 1441.1, “NASA Records Retention Schedules (NRRS)” b. MPR 1440.2, “MSFC Records Management Program” c. MPR 7120.3, “Data Management, Programs/Pr
20、ojects” d. MPR 8040.1, “Configuration Management, MSFC Programs/Projects” e. Federal Acquisition Regulation (FAR), Clause 52.227-16, “Additional Data Requirements” 4. REFERENCES None 5. DEFINITIONS 5.1 Center Data Requirements Manager (CDRM). A specific organization or individual appointed to carry
21、out the Centers responsibility for development and maintenance of Center data requirements. The CDRM has the requisite authority to coordinate internal MSFC data requirement activities. 5.2 Contract. A mutually binding legal relationship obligating the seller to furnish the supplies or services (inc
22、luding construction) and the buyer to pay for them. It includes all types of Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page
23、 5 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE commitments that obligate the Government to an expenditure of appropriated funds and that, except as otherwise authorized, are in writing. 5.3 Contractor. A
24、n entity (i.e., individual, partnership, company, corporation, or association) having a product or services contract with a procuring activity. 5.4 Control Process for NASA-Produced or External Agreement Data Deliverables. Indicates the level of control that the requiring organization has assigned t
25、o the data. 5.5 Data Manager. An individual who establishes and administers the data management activities for a specific program, project, activity, or contract. 5.6 Data Procurement Document (DPD). A compilation of all documents that describe the data requirements of a particular task or project f
26、or contractual efforts. 5.7 Data Requirements Description (DRD). A detailed description of a required data item, including purpose, contents, format, maintenance requirements, and submittal requirements. 5.8 Data Requirements List (DRL). A list of required data items applicable to a specific NASA ac
27、tivity or contract. DRLs may be in the form of a NASA activity DRL which is developed to list all data requirements for a particular NASA activity that contains both NASA-produced data and contracted data, or a DPD/DRL. 5.9 Data Types for Contractual Efforts. The level of availability, review, appro
28、val, and control the Government exercises over the contractor-produced data. 5.10 External Agreement. An agreement with another NASA Center, Government agency, or international agency (e.g., Task Agreement, Memorandum of Understanding). 5.11 Functional Data Category. A category of data that has a de
29、fined scope based on the functional use of the data. Broad functional management categories which are to be used for classification of data requirements and apply to contractual and NASA activities are defined in Appendix A. 5.12 NASA Activity. A NASA activity is a Program/Project or activity that i
30、s funded through NASA, conducted onsite or in the immediate vicinity of a NASA Center, and that includes business, management, or technical tasks. 5.13 Office of Primary Responsibility (OPR). The NASA organization with primary responsibility for the content of specific data items or the organization
31、 responsible for the process represented by the document. For Standard DRDs the OPR is a unique engineering/management discipline designated responsibility for defining a particular data requirement, i.e., safety, logistics, configuration management, manufacturing, test. Provided by IHSNot for Resal
32、eNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 6 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT
33、THIS IS THE CORRECT VERSION BEFORE USE 5.14 Small Business Innovation Research (SBIR) Data. Data first produced by a contractor that is a small business firm in performance of a small business innovation research contract. 5.15 Solicitation. As used herein, includes Request for Proposal (RFP), Reque
34、st for Offer (RFO), Request for Quotation, or Invitation for Bid. 5.16 Standard DRD. A data requirement that has been identified for repetitive use. 5.17 Statement of General Requirements (SGR). An integral section of the DPD that contains the introduction and those general requirements applicable t
35、o the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRDs. 6. INSTRUCTIONS 6.1 Identification/Definition of Data Requirements. The requiring organization shall: 6.1.1 Identify the data requirements for each task or project in the formulatio
36、n phase. 6.1.2 Develop a DRL to define the data requirements for each NASA activity per paragraph 6.2. 6.1.3 Develop a DPD to define the data requirements for each procurement per paragraph 6.3. 6.1.4 The DRL or DPD developer shall request an identification number from the CDRM for each DRL and DPD.
37、 CDRM functions are described in paragraph 6.4. 6.2 Development of a DRL for all NASA Activities. The DRL provides the data requirements for a particular NASA activity and may include NASA-produced data and contracted data. At the start of an activity, the strategy and planning shall be reviewed to
38、determine the anticipated needs for data throughout the activity life cycle. 6.2.1 Because specific data requirements may not yet be known, it is recommended the data requirements of recent, similar activities be examined. This review shall consider data needed to support design, business, manufactu
39、ring, testing, operation and maintenance; and documentation needed for legal, historical, internal audit, or other valid purposes. 6.2.2 Related data that is needed to meet broader enterprise or external requirements shall also be included. 6.2.3 The data identified as a result of this review shall
40、be documented in the DRL. 6.2.3.1 DRL Preparation Instructions. a. The DRL developer shall document the activity DRL in the activitys Data Management (DM) Plan, or in a separate DRL document that can be referenced from the DM Plan. Provided by IHSNot for ResaleNo reproduction or networking permitted
41、 without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 7 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE b
42、. The DRL shall include the data requirement number, title, OPR, and submission dates or milestones for each data requirement. c. OPR Designees, Control Process, Approval Authority, Content Requirements or a link to that information, and any information deemed necessary by the Data Manager is recomm
43、ended to be included in the DRL. d. The DRL data item numbers shall be assigned in the same format as DRD identifiers described in paragraph 6.3.2.2e.(3)(b)(i). e. The DRL shall also reference any DPDs (by DPD and contract number) for contracts that are part of the activity. DRDs may be attached to
44、the DRL as described in paragraph 6.2.3.2. See Appendix Z for a NASA activity DRL template and completion guidance. 6.2.3.2 DRD for NASA Activity DRL. a. DRDs may be attached to the NASA activity DRL, if deemed necessary to describe the data requirement more fully than the DRL format allows. If DRDs
45、 are used in conjunction with the NASA activity DRL, the DRDs shall be prepared and identified in a manner similar to the DRD format described in 6.3.2.2e.(3)(a) for contracts. b. When DRDs are used in conjunction with the NASA activity DRL, “DPD NO.” shall be replaced with “DRL NO.” in DRD Item 1.
46、c. When DRDs are used in conjunction with the NASA activity DRL, “Data Type” shall be replaced with category level in DRD Item 2. NOTE: Due to the nature of the program or project structure, category levels will be determined on a project-by-project basis by the DM and CDRM. The category levels will
47、 be documented in the Data Management Plan. d. Formats for MSFC DRDs are controlled by the CDRM. Deviation from these formats shall be approved by the CDRM. e. Originators of data requirements management forms shall adhere to the guidelines and format requirements presented herein. 6.3 DPD Developme
48、nt. Each DPD shall meet the format and content requirements specified in the following paragraphs to ensure a quality and consistent product is provided to Procurement for incorporation into the contract. See the MSFC DRM Web site for a sample DPD at https:/masterlist.msfc.nasa.gov/drm/. Provided by
49、 IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Work Instruction ED01 Data Requirements MWI 7120.2 Revision: C Identification/Definition Date: February 4, 2009 Page 8 of 29 CHECK THE MASTER LIST at: https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 6.3.1 DPD
