Attachment A. CDM - Core Capabilities.pdf

Configuration and Data Management (CDM)

1.0 CORE CAPABILITIES

1.1 Technology, Innovations, and Process Improvements

The Contractor shall:

1.1.1 Promote CDM innovations, improvements, and modernization by identifying, developing, and recommending new and applicable technologies, processes, and methods. This applies in every area of Program/Project formulation and execution, but particularly in the areas of Model

Based Engineering (MBE), Model Based Systems Engineering (MBSE), and other areas related to Digital Integration and Transformation.

1.1.2 Obtain knowledge and understanding of Model Based Systems Engineering (MBSE) methodology approaches and apply their utilization effecting Systems Engineering (SE)

Technology, Innovations, and Process Improvements (TIPI) (i.e., architecture data elements, and architecture design and modeling).

1.1.3 Promote and utilize digital engineering applications, particularly MBSE methodology

(Processes , tools, workforce) technology as they apply to any CDM process, function, and configuration baselines.

1.1.4 Consult with Programs, Projects, Activities (PPAs) and engineering management, if required, to assure technology and process improvements are aligned with focused areas for technology development.

1.1.5 Support development of the TIPI Plan and implementation as required by Section 3.2.5.

1.2 Configuration Management (CM)

1.2.1 CM Planning

The Contractor shall:

1.2.1.1 Provide expertise and support PPA CM planning throughout the PPA life cycle.

1.2.1.2 Work with the PPA and organizational management to develop a CM process environment in which CM is to be performed and to provide for continuous monitoring and improvement of the PPA CM processes.

1.2.1.3 Work with the PPA in planning and developing the strategy that meets the requirements for visibility and control of the functional characteristics of HW/SW Configuration Items (CIs) over their life cycle (the term CI is used to refer to both hardware CIs and Computer Software

Configuration Items (CSCI)).

1.2.1.4 Develop or support development (e.g., write, provide input to, review), and maintain CM planning documentation (e.g., Configuration Management Plan (CMP) or a combined

Configuration and Data Management Plan), throughout the life cycle of the PPA.

1.2.1.5 Provide input to CM sections of a PPA plan, systems engineering management plan, or other related PPA documentation.

1.2.1.6 Assure that a strategy for conducting CM for CIs and configuration data is prepared and documented in a CMP.

1.2.2 Configuration Identification

The Contractor shall:

1.2.2.1 Provide expertise and support to the PPA configuration identification process for CIs.

1.2.2.2 Work with PPA management, Chief Engineer, Lead Systems Engineer (LSE), and the responsible design organization to identify CIs and associated baselines including, but not limited to, functional, allocated, product, and as-deployed (see NASA/SP-6105).

1.2.2.3 Work with PPA management, Chief Engineer, LSE, and the responsible design organization to identify configuration documentation and models associated with each CI.

1.2.2.4 Work with PPA management, Chief Engineer, LSE, and the responsible design organization to develop CIs and effectivity identifiers.

1.2.2.5 Assign and apply unique identifiers to a product, its components, and associated documents, as required.

1.2.2.6 Maintain document revision relationships to product configurations or baselines, as required.

1.2.2.7 Support the engineering release process

1.2.3 Configuration Control

1.2.3.1 Provide expertise and support to the PPA configuration control process.

1.2.3.2 Develop, implement, and manage change management processes for hardware, software, data products, and PPA unique forms.

1.2.3.3 Assist PPA management in the development and maintenance of control board charters and operations.

1.2.3.4 Serve as Secretariat for assigned boards (e.g., Configuration Control Boards, Program/Project Control Boards, Element Control Boards, Engineering Review Boards, Working

Groups).

1.2.3.5 Ensure Change Requests (CRs), Deviation/Waiver Approval Requests (DARs), Preliminary Interface Revision Notices (PIRNs), Interface Revision Notices (IRNs), and other change documentation are received and entered into a configuration status accounting (CSA) database or other CSA tools.

1.2.3.6 Provide guidance on drafting and submitting change documentation.

1.2.3.7 Participate in change documentation screening processes.

1.2.3.8 Assign CR numbers, change package numbers, directive numbers, document numbers, and other identifiers. Maintain associated tracking database(s) or log(s).

1.2.3.9 Coordinate and provide CM expertise in reviews of CRs, Engineering Change Proposals

(ECPs), DARs, other change documentation and documents.

1.2.3.10 Schedule board meetings and other types of approval meetings.

1.2.3.11 Develop and maintain control board schedules, agendas, meeting minutes, directive actions, board actions, memos, reports, tracking logs, lists, and databases.

1.2.3.12 Serve as Change Package Engineer (CPE) for CDM related documents and data items.

1.2.3.13 Develop Project unique templates and forms (e.g., templates for control board presentations, Project Control Board Directive (CBD) forms).

1.2.3.14 Establish tracking procedures and process for the control of directive actions and other board actions.

1.2.3.15 Coordinate and document action closure with appropriate objective evidence.

1.2.3.16 Perform change package management, to include but not limited to: ensuring a CPE, or equivalent responsible person, and evaluators are assigned; assisting the CPE in the evaluation process; coordinating tabletop reviews; collecting and integrating evaluator comments;

coordinating with the CPE to ensure the CPE has prepared a recommended disposition and is ready to present to the applicable board; and ensuring final board presentation charts are available for the applicable board meeting.

1.2.3.17 Prepare CBDs or equivalent method for documenting decisions and approvals and obtain concurrences and approvals.

1.2.3.18 Maintain board and change package records.

1.2.3.19 Process ECPs and DARs received from contractors through the appropriate board.

1.2.5 Configuration Status Accounting

1.2.5.1 Provide expertise and support the PPA CSA process.

1.2.5.2 Develop or support development of Project specific CSA capabilities (e.g., CSA database and CSA reports).

1.2.5.3 Enter and maintain data in the PPA CSA system.

1.2.5.4 Generate and provide CSA and CM metrics reports

1.2.6 Configuration Verification and Audits

1.2.6.1 Provide expertise and support to PPA configuration verification and audits. Assure that the PPA configuration verification and audits utilize processes to verify that CIs have been properly identified, approved, released, and controlled throughout the PPA life cycle, and that the proper data has been maintained and reports generated to verify the configuration.

1.2.6.2 Lead or participate in the PPA audit planning.

1.2.6.3 Develop plans for Functional Configuration Audits (FCA) and Physical Configuration

Audits (PCA).

1.2.6.4 Identify documentation required to perform FCA and PCA.

1.2.6.5 Develop CM System Audit Plans.

1.2.6.6 Serve as a member of audit teams.

1.2.6.7 Support and provide CM expertise in the on-going PPA configuration verification process throughout the PPA life cycle. Support requirements verification closure activities.

1.3 Data Management

1.3.1 Data Management Planning

1.3.1.1 Provide expertise and support PPA DM planning.

1.3.1.2 Provide knowledge and expertise to work with the PPA and organizational management to develop, implement, control, and maintain the PPA data architecture.

1.3.1.3 Develop or support development (e.g., write, provide input, review), and maintain DM planning documentation (e.g., Data Management Plan (DMP) or a combined Configuration and

Data Management Plan), throughout the life cycle of the PPA.

1.3.1.4 Provide input to DM sections of the PPA plan, systems engineering management plan, and other related PPA documentation.

1.3.1.5 Work with PPA management to develop Data Requirements Lists (DRLs) or equivalent lists of data products.

1.3.1.6 Maintain the DRL throughout the life cycle of the PPA, as required.

1.3.1.7 Assist in development of PPA DPD, as required.

1.3.2 Data Identification/Definition, Preparation, and Control

1.3.2.1 Provide expertise and support PPA data definition (e.g., authoritative data).

1.3.2.2 Work with PPA manager to establish data preparation and control processes, and approval authorities.

1.3.2.3 Assign document numbers and maintain associated logs.

1.3.2.4 Provide Data Quality Assurance (DQA) for data products ensuring that the process follows the steps defined by the PPA and the corresponding checklist, if available. DQA includes, but is not limited to, ensuring that prescribed documentation formatting is followed, and approved changes have been completely incorporated into document revisions, and verifying that a document is ready to be delivered to the corresponding Board for final disposition and implementation.

1.3.2.5 Maintain appropriate data availability and security in accordance with Agency and Center policies.

1.3.2.6 Develop and maintain PPA documentation libraries/databases to include, but not limited to: implementing and maintaining a PPA filing system for documentation and records in the libraries; receiving, collecting, and organizing data from diverse sources; and implementing and managing electronic filing systems.

1.3.2.7 Capture associated metadata for each posted document in DM and PPA databases or websites.

1.3.2.8 Develop and maintain PPA documentation master lists.

1.3.2.9 Provide DM support for PPA milestone reviews, technical reviews, design reviews, technical meetings, and associated briefings to include, but not limited to, data receipt processing, tracking and delivery, and reviewing data planning and data package development.

1.3.2.10 Post documents, design models, and other data to review sites and other appropriate databases.

1.3.2.11 Assist with capture and disposition of review comments.

1.3.2.12 Provide status reports for reviews and other activities.

1.3.2.13 Provide action capturing and action tracking support for reviews and meetings.

1.3.2.14 Convert PPA files from hard copy to electronic media by scanning, organizing, cataloging, labeling, indexing, performing quality checks, and any other associated tasks.

1.3.2.15 Provide support for Acceptance Reviews and assembling Acceptance Data Packages

(ADPs).

1.3.2.16 Establish and maintain processes for controlling PPA unique forms.

1.3.2.17 Support the development and management of external interfaces and cross-Program agreements.

1.3.2.18 Perform data integration between interfacing organizations and software tools/systems.

1.3.2.19 Provide specialized data management support (e.g., requirements data management within a requirements management tool) as required by the PPA.

1.3.3 Receipt and Release

1.3.3.1 Perform PPA Receipt and Release Desk (R&RD) functions in accordance with Center and PPA defined processes.

1.3.3.2 Receive, process, and store data deliverables from prime contractors and prime contractor’s data systems; Center engineering releases; interfacing PPAs; other Centers and facilities; and design organizations and other organizations, as applicable.

1.3.3.3 Record, manage, and track account deliverables and related data.

1.3.3.4 Ensure data is routed through appropriate control and approval processes.

1.3.3.5 Manage the release of PPA documentation through PPA defined processes, when engineering release is not required.

1.3.3.6 Notify PPA personnel of documentation release.

1.3.4 Records Management

1.3.4.1 Provide expertise and support the PPA records management process.

1.3.4.2 Provide records management support in accordance with NPR 7123.1, NPR 1441.1, NRRS 1441.1, and applicable Center records management requirements.

1.3.4.3 Collect, retain, maintain, and prepare data records information for distribution to internal and external customers to meet PPA goals.

1.3.4.4 Develop and evaluate records assessment and management processes, plans, and analyses, and assist with other system management functions.

1.3.4.5 Provide data records related information for trade studies, trade tree development, and decision-making processes.

1.3.4.6 Serve as records custodian and maintain records filing information in accordance with task requirements or Center-specific requirements.

1.3.4.7 Create and maintain PPA records accounting including, but not limited to, records plans, file plans, and Master Records Index (MRI), in accordance with Center policies.

1.3.4.8 Assist the PPA in performing records management and archival in accordance with PPA records plans.

1.3.4.9 Disposition PPA records in accordance with NRRS 1441.1.

1.3.5 Information, Database, and Website Management

1.3.5.1 Provide expertise and support PPA information, database, and website management.

1.3.5.2 Coordinate with PPA management in the development and upgrade, maintenance, administration, and management of PPA CDM databases and websites (e.g., PPA SharePoint site).

1.3.5.3 Develop and maintain data access portals, Wikis, and data storage and retrieval processes.

1.3.5.4 Develop queries, data views, filters, and reports.

1.3.5.5 Manage access to the PPA database and website.

1.3.5.6 Manage PPA data products within the database and website.

1.3.5.7 Provide software integration and development of IM systems and databases.

1.3.5.8 Perform integration and analysis, if necessary, of data, products, and system tools.

1.3.5.9 Work with PPA lead to ensure consistency in data representation including across related

PPAs, as applicable.

1.3.5.10 Integrate processes with software tools.

1.3.5.11 Maintain access lists and grant access requests in accordance with established procedures.

1.3.5.12 Upload documents.

1.3.5.13 Implement version control.

1.3.5.14 Organize data for efficient and logical data storage.

1.3.5.15 Perform data entry, retrieval, and archival.

1.3.5.16 Assist PPA personnel in locating data.

1.4 Engineering Checking and Release

The scope of this work is to provide CDM support for performing Engineering Release and

Engineering Documentation, Drawing, and Computer Aided Design (CAD) Model Checking functions.

Note 1: “Engineering release is an action whereby configuration information is officially made available for its intended use. Engineering release is used to formally release configuration information to all stakeholders involved with requirements, design, manufacturing, quality, logistics, and management, and provides a single source for authenticated information.” (See

SAE-EIA-649-2 Configuration Management Requirements for NASA Enterprises.)

Note 2: “The engineering checking function consists of reviewing engineering drawings, models, and book form documentation for conformance with applicable NASA, military, and industry documentation (e.g., standards, best practices, handbooks, specifications, directives, and manuals) with respect to format and engineering and technical attributes and dimensions, recommending changes to the originator, and verifying implementation of the agreed to changes.” (Source: ED10-OWI-001, MSFC Engineering Documentation Checking.)

1.4.1 Perform engineering drawing and CAD model checking in accordance with Center requirements and policy.

1.4.2 Examine engineering drawings of parts, assemblies, and installations to detect errors in design documents.

1.4.3 Evaluate engineering drawings and CAD models to ensure adherence to Center and industry design standards, policies, and procedures.

1.4.4 Ensure consistency between drawings and associated parts lists.

1.4.5 Determine practicality of design, material selection, available tooling, and fabrication process by applying knowledge of drafting and manufacturing methods.

1.4.6 Work with design and engineering personnel to resolve drawing/model and design discrepancies.

1.4.7 Review book form documents (e.g., specifications, ICDs) for adherence to Center and PPA specific requirement and guidelines.

1.4.8 Perform release of engineering drawings, CAD models, and associated design information in accordance with Center release requirements and policy.

1.4.9 Work with customers to identify and collect information required for release of a product.

1.4.10 Perform data entry into the release system.

1.4.11 Resolve release system discrepancies.

1.4.12 Identify and maintain checking and release records in accordance with NPR 1441.1 and

Center-specific requirements.

1.4.13 Perform administration of the release system.

1.4.14 Develop and maintain work instructions and process documents related to checking and release processes.

1.5 Additional CDM Functions

The Contractor shall perform the following additional CDM functions:

1.5.1 Attend PPA team meetings, working group meetings, and other meetings, as required.

1.5.2 Participate in ISO Audit activities including, but not limited to, providing data to auditors upon request and being interviewed by auditors.

1.5.3 Perform special assignments related to one or more CDM functions and systems engineering, if necessary, as it relates to CDM.

1.6 Guidance and Training

1.6.1 Provide guidance and training in CDM policy, processes, and tools.

1.6.2 Provide guidance for implementing and tailoring CDM processes as appropriate for the

PPA mission type and risk classification.

1.6.3 Provide expert guidance and training in the use of Government-provided CDM electronic systems and software, data storage systems, content management systems, Wikis, websites, databases, and other Government-provided or PPA unique automated systems and tools.

1.6.4 Develop and maintain PPA unique CDM work instruction.