1、 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MPR 8070.1 BASELINE EFFECTIVE DATE: April 17, 2009 EXPIRATION DATE: April 17, 2014 MARSHALL PROCEDURAL REQUIREMENTS ED01 ADMINISTRATION OF MSFCS TECHNICAL STANDARDS
2、Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 2 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov
3、/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Canceled) Document Revision Effective Date Description Baseline 4/17/2009 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-M
4、arshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 3 of 30 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 Pre
5、face P.1 Purpose P.2 Applicability P.3 Authority P.4 Applicable Documents P.5 References P.6 Cancellation Document Content 1. Definitions 2. Responsibilities 3. Procedure 4. Records 5. Flow Diagram Figure 1 Example Format for MSFC Technical Standard Proposal Figure 2 MSFC Technical Standards DCB Flo
6、w Chapter 1 Technical Standards Order of Preference Chapter 2 Propose, Develop, Review, Approve, Implement, and Maintain NASA Technical Standards (Engineering) Chapter 3 Participate in Development or Revision of Non-NASA Technical Standards Chapter 4 Propose, Prepare, Control, Review, Approve, and M
7、aintain MSFC Technical Standards Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 4 of 30 CHECK THE MASTER LIST a
8、t https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE PREFACE P.1 PURPOSE This Marshall Procedural Requirement (MPR) establishes the responsibilities and procedures for technical standards activities at Marshall Space Flight Center (MSFC) fulf
9、illing the requirements of NPD 8070.6 and MPD 1280.1. P.2 APPLICABILITY a. This MPR 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 respective contracts or agreement
10、s. (“Contractors,” for purposes of this paragraph, include contractors, grantees, Cooperative Agreement recipients, Space Act Agreement partners, or other agreement parties.) b. This MPR is applicable to all organizations that develop, evaluate, select, tailor, and recommend application of technical
11、 standards for use in programmatic or organizational requirements; propose, develop, review, or concur with NASA Technical Standards; or that develop or review MSFC Technical Standards applicable to multiple programs and/or projects as defined in NPD 7120.4. P.3 AUTHORITY a. NPD 7120.4, “Program/Pro
12、ject Management” b. NPD 8070.6, “Technical Standards” c. MPD 1280.1, “Marshall Quality Management System Manual” P.4 APPLICABLE DOCUMENTS a. OMB Circular A-119, “Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities” b. NPR 1441.1,
13、“NASA Records Retention Schedules (NRRS)” c. NPR 7120.5, “NASA Space Flight Program and Project Management Requirements” d. NPR 7123.1, “NASA Systems Engineering Processes and Requirements” e. MPR 1280.4, “MSFC Corrective Action System” f. MPR 1440.2, “MSFC Records Management Program” Provided by IH
14、SNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 5 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/di
15、rectives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE g. MWI 1280.4, “MSFC Quality System Deficiency Notice System” h. MWI 2210.1, “MSFC Documentation Repository Input/Output and Data Management Project Requests” i. MWI 7120.4, “Documentation Preparation, Programs/Projects” j. Charter MC-0
16、6, MSFC Multiprogram/Project Common-Use Control Board (DCB) k. Process for Developing NASA Technical Standards (Engineering) Sponsored by the NASA Chief Engineer (Accessible in the NASA Technical Standards System at http:/standards.nasa.gov) P.5 REFERENCES None. P.6 CANCELLATION MPR 7120.2F dated Au
17、gust 22, 2005 Original signed by Robert M. Lightfoot Acting Director Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009
18、Page 6 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT CONTENT 1. DEFINITIONS 1.1 Applicable Document. Document called out in the body of a document required to carry out the procedure(s) specified i
19、n the document. 1.2 Controlled Electronic File. The electronic data file, secured under authority of the controlling organization, that is the original full-text file that was authorized through an electronic approval/release system, or the electronic file that has been verified to be identical to t
20、he approved original when data was authorized through a hardcopy approval/release process. The controlled electronic file represents the content of the official record, though it may or may not be designated as the official record copy. 1.3 Correct Version. The version that is approved/released by t
21、he controlling organization for use. In the case of external documents (e.g., applicable documents), the correct version is the one authorized for use by the organization that invokes the external document. 1.4 Deviation. A documented authorization releasing a program or project from meeting a requi
22、rement before the requirement is put under configuration control at the level the requirement will be implemented. 1.5 Historical Document. Any obsolete or canceled document retained for historical reference. 1.6 Limited Applicability. Applies to marking/using superseded or obsolete documents; user
23、has documented authority to use previous/obsolete document. 1.7 Maintaining Documentation. Providing storage, distribution, reproduction, document revisions, replacing documents in the field with the latest revisions, and disposition of obsolete and/or invalid documents (i.e., historical, limited ap
24、plicability, reference, documents, etc.) for Master List documentation. 1.8 Master List(s). Controlled list(s) of data that identify the correct version authorized for use. 1.9 Master List Custodian(s) (MLC). Individual(s) assigned to process and maintain documentation and create and update the mast
25、er list each time a document is added, revised, or canceled. 1.10 MSFC Technical Standard. A descriptive standard, specification, or handbook that is developed, sponsored, or adopted for common use by MSFC. MSFC Technical Standards in existence prior to the approval of this standard may be other doc
26、ument types (e.g., procedures, reports, requirements, plans, drawings). Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 20
27、09 Page 7 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1.11 MSFC Technical Standard Document Control Board (DCB). A functional body responsible for the review and disposition of all baselines, revisions, a
28、nd cancellations of MSFC technical standards. 1.12 Multiprogram/Project Common-Use Document. Previous term used for MSFC Technical Standards. 1.13 Multiprogram/Project Common-Use DCB. Previous term used for MSFC Technical Standard DCB. 1.14 NASA Technical Standards. NASA documents that contain commo
29、n and repeated use of rules, conditions, guidelines, or characteristics for products or related processes and production methods and related management systems practices. NASA technical standards may contain the definition of terms; classification of components; delineation of procedures; specificat
30、ion of dimensions, materials, performance, designs, or operations; measurement of quality and quantity in describing materials, processes, products, systems, services, or practices; test methods and sampling procedures; or descriptions of fit and measurements of size or strength. Within NASA the bro
31、ad term “standard” may include the following specific document types: handbooks, specifications, and standards developed by NASA. 1.15 NASA Technical Standards (Engineering). Agency-level technical standards, specifications, and handbooks whose development is sponsored by the NASA Chief Engineer. 1.
32、16 NASA Technical Standards (Office of Chief Information Officer (OCIO). Agency-level technical standards, specifications, and handbooks whose development is sponsored by the NASA Chief Information Officer. 1.17 NASA Technical Standards (Office of Safety and Mission Assurance (OSMA). Agency-level te
33、chnical standards, specifications, and handbooks whose development is sponsored by the NASA OSMA Office. 1.18 Non-NASA Technical Standards. Term used to describe both Voluntary Consensus Standards and Other Government (Non-NASA) Standards collectively. 1.19 Office of Primary Responsibility (OPR). Th
34、e NASA organization with primary responsibility for the content of specific data items or the organization responsible for the process represented by the document. OPR responsibilities may include preparing a document, controlling a document, and/or reviewing the technical content of a document subm
35、itted by a contractor or external organization. 1.20 Other Government (Non-NASA) Standards. Technical standards that are originated and published by Government agencies other than NASA (e.g., Department of Defense, Federal Aviation Administration). Provided by IHSNot for ResaleNo reproduction or net
36、working permitted without license from IHS-,-,-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 8 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE
37、CORRECT VERSION BEFORE USE 1.21 OPR Designee (OPRD). Individual(s) appointed by the office of primary responsibility who is/are responsible for a specific document within their area. 1.22 Revision. Any change, modification, or newly-edited version of a document. 1.23 Tailoring. The documentation and
38、 approval of the adaptation of the processes and approach to complying with requirements underlying the specific program or projects. Tailoring considerations include system size and complexity, level of system definition detail, scenarios and missions, constraints and requirements, technology base,
39、 major risk factors, and organizational best practices and strengths. Critical project considerations (e.g., public safety, security, litigation exposures) may preclude tailoring out required process activities, regardless of cost, manpower available, or other considerations. (From Systems Engineeri
40、ng Fundamentals, Defense Acquisition University, January 2001) (AS defined in NPR 7123.1). 1.24 Uncontrolled Copies. Copies printed from the Master List System or copies of the signed original document. 1.25 Use. Within the definition given in OMB Circular A-119, “use” means incorporation of a stand
41、ard in whole, in part, or by reference in a procurement action or as program or project requirements or guidance. 1.26 User. Any person who uses or refers to any document during the performance of a specific task. 1.27 Voluntary Consensus Standards (VCS). Technical Standards that are planned, develo
42、ped, coordinated, and published by domestic or international organizations using agreed-upon procedures (e.g., American Society of Mechanical Engineers, Government Electronics and Information Technology Association). These technical standards include provisions requiring that owners of relevant inte
43、llectual property agree that the intellectual property is made available on a non-discriminatory, royalty-free or reasonable royalty basis to all interested parties. 1.28 Waiver. A documented authorization releasing a program or project from meeting a requirement after the requirement is put under c
44、onfiguration control at the level the requirement will be implemented. 2. RESPONSIBILITIES 2.1 The MSFC Director, Engineering Directorate, or designated personnel, shall: 2.1.1 For all Engineering technical standards: 2.1.1.1 Ensure that mandatory engineering technical standards (i.e., those require
45、d by statute, NASA directive, or MSFC directive) are evaluated and selected for application as requirements on MSFC program/projects and contracts, or that a deviation or waiver is obtained for non-use. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,
46、-Marshall Procedural Requirements ED01 Administration of MSFCs MPR 8070.1 Revision: Baseline Technical Standards Date: April 17, 2009 Page 9 of 30 CHECK THE MASTER LIST at https:/repository.msfc.nasa.gov/directives/directives.htm VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 2.1.1.2 Ensure that
47、 non-mandatory engineering technical standards are evaluated and selected based on the Technical Standards Order of Preference in Chapter 1 for application as requirements on MSFC programs/projects and contracts. 2.1.1.3 Resolve Center technical issues for engineering-related technical standards. 2.
48、1.2 For NASA Technical Standards (Engineering) and Non-NASA Technical Standards: 2.1.2.1 Concur on MSFC proposals to develop NASA Technical Standards (Engineering) and to participate in development of VCS prior to Agency-wide evaluation and approval or disapproval by the NASA Chief Engineer. 2.1.2.2
49、 Provide MSFC discipline experts to develop Interim NASA Technical Standards as a priority. 2.1.2.3 Ensure that NASA Technical Standards (Engineering), technical standards proposed as mandatory, and VCS are technically reviewed by MSFC discipline experts and affected MSFC offices, departments, and laboratories, including program/p
