1、 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MSFC-STD-555 National Aeronautics and REVISION: J Space Administration EFFECTIVE DATE: June 17, 2013 George C. Marshall Space Flight Center Marshall Space Flight Center, Alabama 35812 EE12 MSFC TECHNICAL STANDARD MSFC ENGINEER
2、ING DOCUMENTATION STANDARD Approved for Public Release; Distribution Unlimited Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effectiv
3、e Date: June 17, 2013 Page 2 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Cancelled) Document Revision Effective Date Description Revision D 10/6/2000 General Revision Deleted document preparation requirements excludi
4、ng drawings and parts lists. Data included in MWI 7120.4. Previous history retained as part of superseded or cancelled MSFC Documentation Repository files. Revision E 1/8/2002 Para 2.j Replaced CM-INST-002 with MSFC Forms, All MSFC forms are accessible at http:/ starbase.msfc.nasa.gov:8000/forms. Pa
5、ra 4.2.2, deleted or CM-INST-002. Para 5.1.2.1 deleted and renumbered subsequent paragraphs. Para 5.2.2 deleted last sentence, Forms and preparation instructions can be found in CM-INST-002. Para 5.2.3 deleted per CM-INST-002 in last sentence. Tables I, II, III, and IV, deleted references to CM-INST
6、-002. Para 5.4.1.b deleted (see CM-INST-002). Revision F 5/13/2002 CONTENTS added 4.4.4. ICMS Database Reports. Deleted paragraph 2.1and paragraphs k., l., and m. and renumbered paragraphs accordingly. 4.1.c., deleted that is authorized for release. 4.1.d. deleted 2nd sentence. 4.2.2.a. deleted 2nd
7、sentence. 4.3.2.2, replaced in accordance with MIL-STD-130 and MIL-STD-129, part and bulk marking, respectively. with as shown below. To satisfy RCAR 177, paragraphs 4.3.3.3 a. through c. are changed to read: 4.3.3.3 Matched Set Dash Numbers. Dash numbers shall be assigned to two or more matched or
8、machined parts that are not interchangeable. The following rules apply: a. When an assembly is created having matched parts, each part must be identified with a dash number and a separate EPL. b. The next higher assembly(s) will identify each matched part in the drawing(s) and the EPL(s) until they
9、are reassembled as a matched set. The assembling drawing will have a note stating Matched Set next to the find numbers. This note number will also be added to the EPL. c. Matched parts drawing requirements shall be per MSFC-STD-2806. 4.4.2 Replaced sentence with The Release Desk shall be the single
10、point of release for MSFC in-house projects flight and flight-related ground support equipment (GSE) configuration documentation in accordance with the documentation approval matrix contained in each projects configuration management plan. 4.4.2.a., replace text with The Release Desk may release non
11、-configuration documentation as defined in the projects data management plan. Delete NOTE: Manufacturing must sign all FEOs and FEPLs. Added new paragraphs 4.4.4 through 4.4.4.5. ICMS Database Reports. 4.5.1, deleted according to the requirements of MIL-STD-100 and. 4.5.2 Replaced text with: A compl
12、ete set of original drawings and parts lists and a listing of all specifications and standards and ancillary documents used for the design definition shall be obtained and placed in the MSFC Repository. When available, drawing trees, indentured part lists, and/or associated listings shall also be pl
13、aced in the MSFC Repository. MSFC Form 2896 shall accompany the package. 4.5.3.b, 2nd para, add and documented in the configuration management plan after systems engineer 5.2.2, delete MSFC Form 421-1, in first sentence and added shall be prepared according to the format specified in MSFC-STD-2806 a
14、nd Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effective Date: June 17, 2013 Page 3 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS
15、 THE CORRECT VERSION BEFORE USE Status (Baseline/ Revision/ Cancelled) Document Revision Effective Date Description 5.3.4, 1st sentence changed to read Although the Secretariat is responsible to review the package, the Release Desk also reviews each approved package to ensure that all the required f
16、orms are included and properly completed. Change 2nd sentence to read: If corrections are required, the Release Desk shall return the package to the Secretariat who in turn will forward to the OPR designee. 5.3.7, 1st sentence changed to read: Although the Secretariat is responsible to review the pa
17、ckage, the Release Desk also reviews each approved change package to ensure that all the required forms are included and properly completed. Change 2nd sentence to read as follows: “If corrections are required, the Release Desk shall return the package to the Secretariat who in turn will forward to
18、the OPR designee. Revision G 7/25/2002 Paragraph 3 - deleted duplicate definitions contained in cited documents (2.c and 2.d); deleted forms from definitions (2.e, 2.f, 2.g, 2.i, 2.j, 2.k, 2.l, and 2.n) and added form numbers to form titles when used in the text. 5.2.1.f., Added 2 new sentences at t
19、he end of paragraph: An EO shall not be written to delete parts that were added by a previous EO that has not been incorporated. The EO must be canceled and reissued in accordance with paragraph 5.2.1.g. Revision H 9/9/2009 Updated language to utilize shall for requirements in accordance with the Ru
20、les Review. General - Updated document to current requirements and applicable documents. Added definition for Effectivity Code. Para 4.1.6 Updated ED03 to ED11. Para 4.2.1 clarified procedure for drawing revisions (RCAR 235). Added Para 4.3.2 Establishing Effectivity Codes. Para 4.3.3.1, renumbered
21、4.3.4, added requirements for serial/lot numbering format and re-use. Para 4.3.3.2.1, renumbered 4.3.6, clarified use of new and previous CAGE Codes. Para 4.3.3.4, renumbered 4.3.7, added requirements for part number re-identification. Added Para 4.5.5 Preparation of an Envelope Drawing (RCAR 235).
22、Added Para 4.6, Software and Firmware Identification Requirements. Added Para 5.1.1.3 and Para 5.1.1.4 to describe update of the component drawing revision on assembly Engineering Parts Lists (EPLs) when component drawings are revised (RCAR 259). Para 5.1.3 Changing Effectivities clarified title and
23、 contents. Updated Figure 1 to better describe EPL revisions. Updated Para 5.2.1 to describe EO incorporation by drawing revision and Revised and Redrawn procedure (RCAR 235). Para 5.2.2 added Engineering Order (EO) numbering requirements and use of the EO Number Request and Trending System. Para 5.
24、3 combined initial and release package processing into the same paragraphs. Para 5.4 Updated document cancellation sections. Revision J 6/17/2013 Revision J release was authorized by the MSFC Technical Standards Document Control Board (DCB) through the Multiprogram Document Management System (MPDMS)
25、. Document was restructured to include requirements and guidance that are applicable to release of MSFC configuration documentation from the following documents which are being cancelled: MPR 8040.1, MSFC Configuration Management, MPR 8040.2, Product Identification and Traceability, MWI 8040.5, Floo
26、r Engineering Order and Floor Engineering Parts Lists (FEOs/FEPLs), and ED-OWI-005, MSFC Engineering Release, Use of the ICE Windchill system as the release database is incorporated as new scope. Both ICMS and ICE Windchill are now identified as valid release systems for MSFC Release. Provided by IH
27、SNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effective Date: June 17, 2013 Page 4 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS THE CORRECT VERS
28、ION BEFORE USE FOREWORD This standard specifies the requirements, instructions, and guidance for releasing Marshall Space Flight Center (MSFC) configuration documentation through the MSFC Release Desk using the Integrated Configuration Management System (ICMS) or the Integrated Collaborative Environ
29、ment (ICE) Windchill system. This standard shall be used only for MSFC programs/projects. The intent of this standard is to achieve a high level of configuration traceability for release and change of documents, parts, engineering parts lists (EPLs), drawings, and computer-aided design (CAD) models.
30、 The change processes defined in this standard allow change of parts-EPLs separate from the drawing-model and utilize engineering orders (EOs) to release auxiliary changes to parts and drawings. These mechanisms focus change documentation on only the elements that are changing, and aid in expediting
31、 changes while maintaining traceability. Traceability and responsiveness are critical when communicating the configuration requirements and configuration changes to personnel who build or procure the hardware/software and those who verify that configuration requirements have been met. The ICMS and I
32、CE Windchill release databases are described in this standard because both systems are utilized by the MSFC Release Desk to release data at MSFC. ICMS is a part and release database that captures part data through EPLs and captures the relationship between the parts, EPLs, drawings, EOs, and effecti
33、vities. ICMS identifies the official released data, produces the official released EPL and EO reports, provides indentured parts list (IPL) reports by effectivity, and maintains part history for all released parts. ICE Windchill is a product data management system and a part and release database. IC
34、E Windchill captures part data in Windchill Technology (WT) Part objects, CAD drawing and CAD model data in CAD Document objects, and non-CAD drawings, EPLs, EOs, and other data types in document objects. ICE Windchill captures the relationships between WT Parts, EPLs, drawings, CAD models, EOs, and
35、 effectivities, and identifies the official released data and authorized configurations by effectivity. ICE Windchill captures linkages between WT Part-WT Part, CAD drawing-CAD model, CAD model-CAD model, and WT Part-CAD-documents. Release and change control of the inter-related part, drawing, and C
36、AD model objects drive specific part, drawing, and CAD model identification and structuring requirements, which enable more flexible change processing while maintaining a high level of traceability. For both ICMS and ICE Windchill, the MSFC Release Desk transmits released data to the MSFC Documentat
37、ion Repository who serves as the official record custodian and distribution point. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effe
38、ctive Date: June 17, 2013 Page 5 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE TABLE OF CONTENTS PARAGRAPH PAGE DOCUMENT HISTORY LOG 2 FOREWORD 4 1. SCOPE .7 2. APPLICABLE AND REFERENCE DOCUMENTS .7 2.1 Applicable Documents 7 2.2 Reference Documents 8 3. DEFINITIONS
39、AND ACRONYMS .8 4. GENERAL REQUIREMENTS 9 5. DETAILED REQUIREMENTS .13 6. NOTES .13 APPENDICES A. Definitions .14 B. Acronyms 19 C. Project Code, Board Code, Program Control Number (PCN), Change Request (CR), Deviation-Waiver Approval Request (DAR), Control Board Directive (CBD), and Configuration I
40、tem (CI) and Effectivity Identifiers 21 D. Technical Approval Matrix .26 E. Part, Drawing, CAD Model, and Document Numbering and Version-Revision Identifiers .28 F. Software, Firmware, and Configurable Logic Device Identification .34 G. Serial and Lot Number Requirements and Guidance .38 H. Material
41、 Traceability Level Requirements and Guidance 42 I1. Engineering Parts List (EPL) Preparation, Numbering, and Versions in ICMS 44 I2. WT Part and Engineering Parts List (EPL) Preparation and Numbering in ICE Windchill .47 J. Drawing Preparation . 50 K. CAD Model Preparation in ICE Windchill . 53 L.
42、Release-Change Rules to Maintain Relationships between WT Parts, Drawings, and CAD Models in ICE Windchill . 54 M1. Engineering Order (EO) Preparation and Numbering in ICMS . 56 M2. Engineering Order (EO) Preparation and Numbering in ICE Windchill . 60 N1. Effectivity Application and Change in ICMS
43、63 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effective Date: June 17, 2013 Page 6 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS
44、 THE CORRECT VERSION BEFORE USE N2. Effectivity Application and Change in ICE Windchill 65 O. Initial Release, Change, and Cancellation Process . 66 P. Floor EO/Floor EPL (FEO/FEPL) Process 70 Q. Guidance on Part Number Re-identification 72 R. Requirements for Design Responsibility Transfer 74 S. MS
45、FC Release Desk Functions, Reports, and Release Records 76 TABLES I. Drawing, Engineering Parts List (EPL), and Engineering Order (EO) Package Preparation for ICMS Initial or Change Release .10 II. Document Package Preparation for ICMS Initial or Change Release .10 III WT Part, Drawing, EPL, EO, and
46、 CAD Model Package Preparation for ICE Windchill Initial or Change Release .11 IV. Document Package Preparation for ICE Windchill Initial or Change Release .12 V. Technical Approval Matrix 27 VI. Number and Name of ICE Windchill Part, Drawing, and CAD Model Objects .32 VII. EPL Re-identification Ste
47、ps for Effectivity Changes in ICMS 46 VIII. Records Related to MSFC Release Processes79 FIGURES 1. Serial and Lot Traceability in Drawing Hierarchy (Guidance) .40 2. Change Request and Release Process .66 3. Part Number Re-identification Decision Tree (Guidance) 73 Provided by IHSNot for ResaleNo re
48、production or networking permitted without license from IHS-,-,-MSFC Technical Standard EE12 Title: MSFC Engineering Document No.: MSFC-STD-555 Revision: J Documentation Standard Effective Date: June 17, 2013 Page 7 of 80 CHECK THE MASTER LIST-VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1. SCOPE 1.1 Scope and Purpose This standard specifies the requirements, instructions, and guidance for releasing MSFC configuration documentation through the MSFC Release Desk. This standard identifies the requirements
