REG NASA-LLIS-4578-2012 Lessons Learned - Programs Selecting Data Management Tools Without Establishing A Technical Data Architecture.pdf

1、Public Lessons Learned Entry: 4578 Lesson Info: Lesson Number: 4578 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Programs Selecting Data Management Tools Without Establishing A Technical Data Architecture Abstract: Technical data architecture and standards were not defined early

2、in the Constellation Program. Tools, such as Cradle, Windchill (official data repository), IRMA (risk management), Primavera (schedules), etc., were selected without developing the data architecture and requirements for the tools. The Constellation Program prime contracts were put in place without c

3、onsistent data delivery requirements and data rights being addressed. The prime contractors delivered inconsistent data in various formats and the contractors claimed that certain data was proprietary, making it difficult for the Government to obtain the necessary data in uniform formats. Descriptio

4、n of Driving Event: Tools were chosen at the beginning of the Constellation Program without first establishing the data architecture and defining what standards, protocols, data formats, and metadata would be levied on CxP prime contracts for data delivery. Lack of uniform data delivery requirements

5、 resulted in the Program prime contractors not being required to provide consistent technical data in consistent, useable formats. This caused problems and wasted resources in translating the data into useable formats and getting access to all required data (due to data rights issues). Lesson(s) Lea

6、rned: Technical data architecture and standards definitions along with data rights should be established at the program level so projects will have the same, if not similar, data applications, processes, data deliveries, and transfer of data at equipment turnover (commonly known as DD250). An exampl

7、e of this issue is the Logistics Management Information (LMI) data. LMI data should have been defined in Data Requirements Deliverables (DRDs) in either standard (i.e. ISO) or native formats and should have been uniform across projects in the Constellation program. If data is delivered in pdf files

8、rather than native formats or standard formats such as IGES, STEP, etc., it is very difficult for that data to transfer digitally from design/development through manufacturing and ultimately to the operations, maintenance and sustaining organizations systems. Obtaining the required data and putting

9、it into required formats was time consuming and wasted resources. Recommendation(s): Ensure a technical data architecture and data standards and formats are defined early in the program before tools are selected and prime contracts are awarded. Incorporate uniform DRDs into all program prime contrac

10、ts. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Technical Data Architecture Information Technology/Systems Early requirements and standards definition Additional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Project: Constellation Approval Info: Approval Date: 2012-11-07 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-