Contract Data Requirements List 000000000000000000000000000000000000000000000001111 111101010101010101001010101010010100000000000000000 000000000000000000000000000000010101010101010101001 by xfq12691

VIEWS: 204 PAGES: 26

Contract Data Requirements List document sample

More Info
									000000000000000000000000000000000000000000000001111
111101010101010101001010101010010100000000000000000
000000000000000000000000000000010101010101010101001
111111111111111111111111111111111111111111111111111
111111111111111111111111111111111111111111111111011
111111110100101001001010101010100101010010101010100
000000000000000000000000000000111111111111111000000
                    JLTV Section C
000000000000011111111111111111111100000000000000000
                    Scope of Work
000000000000000000000000000000000000000000000000000
000000000000000011111111111110101010100010100101010
100101010101001010010101111111111111111111111111111
111111111111111111111111111111111111111111111111111
111111111111111111111111111111111111111111111100000
000000000000111111111111000000000000010100110010101
001010101001000000000000000000000000000000000000000
                          ~1~
  C.2 Program Structure/Management

• Integrated Product Teams (IPTs). IPTs, shall be established to serve
  as the primary management tool for this contract.
   • Number/structure of IPTs proposed by the KTR
   • Minimum shall include, COST, ENGINEERING, SUPPORTABILITY, RISK,
     T&E, and PROJECT MANAGEMENT


• Integrated Master Plan (IMP). The Contractor shall develop and deliver
  a detailed IMP that supports the Government IMP

• Integrated Master Schedule (IMS). The Contractor shall develop an
  IMS that supports the Contractor-developed IMP.

• Advanced Collaborative Environment (ACE)—Is the primary means of
  communication/information sharing for this project.


                                 ~2~
  C.3 Cost & Schedule Control
• The Contractor shall collect and analyze data, and prepare documents
  including the Cost and Software Data Reports (CSDR), consisting of
  the Contractor Cost Data Reports (CCDR) and Software Resources
  Data Reports (SRDR)), Contract Performance Reports (CPR), and
  Contract Funds Status Reports (CFSR), per section C.3 of the
  contract.



• The Contractor shall establish, maintain, and use an integrated
  performance management system in the performance of this contract.
  Central to this integrated system shall be a validated Earned Value
  Management System (EVMS) in accordance with DFARS 252.242-
  7002, per section C.3.3 of the contract




                                 ~3~
C.4 Risk Management
• The Contractor shall develop, implement, and deliver a Risk
  Management Plan following the concepts in the RISK
  MANAGEMENT GUIDE FOR DOD ACQUISITION. The plan shall
  identify and mitigate program risks in the areas of cost, schedule,
  and performance per section C.4 of the contract

• Risk management reviews/reporting shall be an integral part of all
  technical reviews, risk review board meetings, program
  management reviews, and IPT meetings, per section C.4 of the
  contract.




                                ~4~
  C.5 Meetings/Reviews

• “All program and technical meetings, conferences,
  and reviews, shall be hosted by the Contractor”
  • Start of Work Meeting at Contractor facility within 20 days of award
  • Pre-TRR likely to be at Contractor facility
  • For planning/cost estimating purposes, assume all remaining
    meeting locations not specifically called out in the contract are to
    be hosted by the contractor in the Warren/Selfridge area.
  • Whenever possible, meetings and reviews shall be conducted by
    electronic means, e.g. telecon, video-telecon, web-based meeting
    software.

• Meeting schedule/frequency is called out per section
  C.5 of the contract.



                                  ~5~
  C.5 Meetings/Reviews

• Start of Work / System Requirements Review (SRR)
• Integrated Baseline Review (IBR)
• TD – Preliminary Design Review (PDR)
• TD – Critical Design Review (CDR)
• TD – Test Readiness Review (TRR)




                           ~6~
       C.6 SDD Planning Documents
Overview
• The Contractor shall support the development of the following System Development and
  Demonstration (SDD) documents and certifications, including.
   •   Consideration of Technologies Issues
   •   Clinger-Cohen Act (CCA)
   •   DIACAP Compliance
   •   Spectrum Certification Compliance
   •   Manpower Estimates
   •   Core Logistics Analysis
   •   Source of Repair Analysis,
   •   Technology Development Strategy
   •   Modular Open System Architecture (MOSA)
   •   Technology Maturity Assessment
   •   Component Cost Analysis,
   •   Test and Evaluation Master Plan (TEMP)
   •   Supportability Strategy
   •   Integrated Logistics Assessment (ILA)
   •   Systems Engineering Plan (SEP).
CDRL
• System Specification. The Contractor shall develop and deliver a JLTV FoV System
  Specification that is performance based. The specification shall represent the
  Contractor's recommended performance for the JLTV FoV that would be carried into
  subsequent program phases. The specification shall include all sub-configurations and
  trailers, per Section C.6 of the contract, (CDRL A016, DIIPSC-81431A)


                                           ~7~
   C.7 Systems Engineering (SE)
• C.7.1 General.
  • A copy of the government SEP has been provided and was be
    briefed separately
• C.7.2 SEMP Requirements
  • Develop and document the plan for implementing SE based upon
    • IMS & IMP
    • Processes
    • SEP
    • SOW
    • Technical Authority
    • Technical Organization and Teams
    • Trades
    • Other Plans

• SOW Section CDRL Listing
  • A017 – Systems Engineering Management Plan


                                  ~8~
      C.8 Hardware Requirements

• SOW Section Overview
  • C.8.1. System Level Design Document
  • C.8.2 Systems Integration Lab (SIL)
  • C.8.3 Problem Reporting Metrics
  • C.8.4 Computing Resource Metrics
  • C.8.5 Computing Resource Utilization.
  • C.8.6 System Requirement Compliance
  • C.8.7 Trade Studies
     •C.8.7.1 Compliance Trade Studies
     •C.8.7.2 Design Trade Studies
  • C.8.8 Weight Accounting
  • C.8.9 Power Budget Accounting



                                  ~9~
    C.8 Hardware Requirements (cont.)

• SOW Section CDRL Listing
  • CDRL A018
    • The Contractor shall develop a requirements compliance matrix that tracks
      achievement of all JLTV FoV PD requirements.
  • CDRL A019
    • The Contractor shall develop and deliver to the Government a trade study for any
      requirement that is deemed to be unachievable as tracked on the Compliance Matrix.




                                          ~10~
      C.9 Software
• Overview
  •   C.9.1 Software Gap Analysis (SGA)
  •   C.9.2 Software Development Plan (SDP)
  •   C.9.3 Software Build/Download Process (SB/DP)
  •   C.9.4 Source Code
  •   C.9.5 Capabilities Certification
       • The Contractor shall have and maintain at least a CMMI Level III Software
         Engineering Institute (SEI) certification for all business units and subcontractors
         performing software development work.
  • C.9.6 Software Metrics
  • C.9.6.1 Software Design
       • C.9.6.2 Source Lines of Code
       • C.9.6.3 Software Integration and Test
       • C.9.6.4 Problem Reporting Metrics


• CDRLs
  • A020 – Source Code
       • All NDI/COTS/GOTS/GFE software shall be delivered in the prototypes with
         appropriate licenses and without restrictions for usage in its intended vehicle
         application. The source code developed by the Contractor under this contract shall be
         owned by the Government and delivered separately from the vehicles.

                                               ~11~
   C.10 Interoperability Requirements

• Overview
  • C.10.1 Systems Interoperability
     • The Contractor shall be responsible for systems interoperability. Systems
       interoperability shall, at a minimum, include interoperability of all hardware,
       software and, logistics systems included in the family of JLTVs. Integration
       of GFE shall not degrade demonstrated interoperability between GFE
       components.


• CDRLs
  • There are no CDRLs in this section




                                         ~12~
    C.11 Configuration Management (CM)

• SOW Section Overview
  • C.11.1 Configuration Management.
  • C.11.1.1 Configuration and Data Management Plan.


• SOW Section CDRL Listing
  • A021 – Configuration and Data Management Plan
    • The Configuration and Data Management Plan shall address:
      – responsibilities, business processes and standards, methods/tools and procedures
        to identify, develop, document, record, control, store, transmit, implement, validate,
        and verify JLTV Conceptual Design Drawings/Models Technical Data and
        Simulation-based Design Model Data.
      – the process for management and control of Government Furnished Information
        e.g. drawings, models, and technical documents as integrated into the Contractor's
        JLTV design, analysis and engineering documentation.




                                           ~13~
      C.12 Lifecycle Product Data Management
• SOW Section Overview
  •   C.12.1 Data Management System.
  •   C.12.2 Technical data.
  •   C.12.2.1 Simulation-based Design Model Data.
  •   C.12.2.2 Conceptual/Technology Development Design Drawings/Models Technical Data.
• SOW Section CDRL Listing
  • A022 – Simulation-based Design Model Data
       • Simulation-based Design Model Data shall contain
         – engineering design concepts parametric data,
         – analysis units of measure,
         – analysis identification and composition,
         – finite element data suitable for linear/non-linear analysis using implicit/explicit methods,
         – configuration and document management data,
         – material test data (elastic and plastic stress-strain curves for tension, compression and torsion),
         – product geometry shape (3-D CAD geometry idealized suitable for generating required analysis models that
           includes appropriate geometric simplifications) defect-free topology,
         – Metadata Attributes. – All JLTV CAD, CAE, part, assembly, data and documentation shall incorporate User-
           Defined Metadata Attributes into the data/document property parameters for Government configuration and
           data management requirements.
         – Solid Model Validation Checks – solid model data geometric validation properties (GVP) checks on CAD and
           CAE solid models.
         – Geometry and Drawing/CAD Creation Standard. - geometry data creation standard shall contain identification
           of data format types, application of geometric shapes, boundaries, materials, surface finishes, annotations,
           notes, metadata attributes, part relationships and associations.
       • Simulation-based Design Model Data shall be prepared in an ISO 10303-209 (STEP AP209).



                                                        ~14~
   C.12 Lifecycle Product Data Management (cont’d)

• SOW Section CDRL Listing
  • A023 – Conceptual/Technology Development Design Drawings/Models
    Technical Data
     • Conceptual/Technology Development Design Drawings/Models Technical Data
       shall include:
       – Item Identification Traceability – Reference of technical data/documents and part or
         identifying numbers
       – Conceptual Design and Technology Development Data Construction. – configuration item
         definition documents for parts, assemblies, and system levels.
       – Drawing and Solid Model Data Properties Disclosure – Shall disclose as a minimum, the
         functional, physical, and interface requirements for each configuration item by means of
         graphic and textual representation.
       – Conceptual Design and Technology Development Data Exchange Export. – delivered in a
         product data management (PDM) schema format using ISO 10303 STEP Application
         Protocol 214.
       – The Conceptual Design/Technology Development Content – per TDP Worksheets
       – Metadata Attributes. – All JLTV CAD, CAE, part, assembly, data and documentation shall
         incorporate User-Defined Metadata Attributes into the data/document property parameters
         for Government configuration and data management requirements.
       – Solid Model Validation Checks – solid model data geometric validation properties (GVP)
         checks on CAD and CAE solid models.
       – Geometry and Drawing/CAD Creation Standard. - geometry data creation standard shall
         contain identification of data format types, application of geometric shapes, boundaries,
         materials, surface finishes, annotations, notes, metadata attributes, part relationships and
         associations.



                                              ~15~
   C.13 C4ISR

• Overview
  • C.13.1 C4ISR/EW A-Kit/B-Kit electronics breakdown
  • C.13.2 Antenna placement
  • C.13.3 Cross-Domain Approach


• CDRLs Listing
  • A024 – Cross Domain Approach
    • The Contractor shall develop a Cross-Domain approach for the JLTV FoV
      which will be delivered to and approved by the Government. Net-centric
      warfare requires information sharing across security domains, which in turn,
      generates significant security challenges. Traditional information assurance
      solutions to support cross-domain information sharing have focused heavily
      on preventive measures, restricting information flow and reducing the risk of
      information compromise.



                                       ~16~
   C.14 Technology and Growth Plan

• Overview
  • C.14.1 Technology & Growth Plan
    • C.14.1.1 C4ISR/EW Growth
    • C.14.1.2 Reliability Growth
    • C.14.1.3 Fuel Efficiency System Optimization
    • C.14.1.4 Power Generation Growth
    • C.14.1.6 Diagnostics/Prognostics Growth
    • C.14.1.7 Technology Readiness Level (TRL) Assessment


• CDRLs
  • A025 – Technology & Growth Plan
    • The Contractor shall consider in its FoV design the growth capability/open
      architecture needed to accomplish performance improvements in the areas
      below, as well as a Technology Readiness Level assessment for the
      delivered sub-configuration.

                                      ~17~
      C.15 Modeling and Simulation
• SOW Section Overview
  •   C.15.1 Contractor M&S.
  •   C.15.2 The Contractor's M&S output/results and data
  •   C.15.3 Contractor Support of Government M&S.
  •   C.15.4 M&S Data Submissions
       • C.15.4.1 Crashworthiness Analysis.
       • C.15.4.2 Propulsion System Analysis.
       • C.15.4.3 Mobility and Ride Dynamics Analysis.
       • C.15.4.4 Operational Effectiveness Analysis.
• SOW Section CDRL Listing
  • A026 – Modeling & Simulation Plan
       • A plan to address the Modeling and Simulation of the following key areas: Mobility,
         Thermal, Structure, Signature Management, Survivability, Transportability, Crash
         Worthiness and RAM.
  • Data to be provided for use of Government Modeling and Simulation:
       • A027 – Crashworthiness Analysis
       • A028 – Propulsion System Analysis
       • A029 – Mobility and Ride Dynamics Analysis
       • A030 – Operational Effectiveness Analysis



                                              ~18~
     C.16 Safety Requirements
• SOW Section Overview
  • C.16.1 Safety Engineering Principles and Program
     • C.16.1.1 Safety Assessment Report (SAR)
     • C.16.1.2 Hazard Tracking and Hazard Log
        – C.16.1.2.1 The Contractor shall document and track all hazards from identification until the hazard is
          eliminated or the associated risk is reduced to a level acceptable to the Government.
        – C.16.1.2.2 Disposition and Closeout. All hazards shall receive final disposition by the Government. All hazards
          closed out in the log shall identify the Government official who authorized the closeout. Closed out Hazards
          shall remain on the Hazard Log.
     • C.16.1.4 Environmental Safety Occupational and Health (ESOH) Review Support.

• SOW Section CDRL Listing
  • A031 – Safety Engineering Principles and Program
     • The System Safety Program Plan (SSPP) describes the planned safety tasks and activities
       necessary to execute a comprehensive and effective System Safety Program.
  • A032 – Safety Assessment Report (SAR)
     • The Safety Assessment Report (SAR) identifies all potential and actual Safety and Health Hazards
       associated with the JLTV.
  • A033 – Hazard Log
     • A central file or document called a ―Hazard Log‖ (HL) shall be maintained on the ACE, and shall
       include all hazards identified through testing and other analyses IAW Severity Categories and
       Probability Levels provided in Attachment 19, System Safety Program Guidance.



                                                       ~19~
  C.17 Environmental Compliance
• C.17.1 Environmental Compliance
• C.17.2 Hazardous Materials (HAZMAT) Management
  • C.17.2.1 No use of specified HAZMAT w/o Govt approval
    • C.17.2.1.1 No Class I or II ODS
    • C.17.2.1.2 Lead
  • C.17.2.2 Hazardous Materials Management Report (HMMR)
  • C.17.2.3 Hazardous Materials (HAZMAT) in Packaging

• SOW Section CDRL Listing
  • A034 – Hazardous Materials Management Report
    • The Hazardous Material Management Report which identifies all
      hazardous materials required for system prototype build and
      sustainment, including the processing of vehicle components.




                                    ~20~
            C.18 HSI and MANPRINT
  • Design has a direct connection to crew functionality at all
    levels

  • Optimize total system performance at acceptable cost and
    within human constraints

  • Minimum Soldier/Marine related manpower and training
    costs, while retaining maximum combat effectiveness
    through system design

  • Note: Elements further defined in the Purchase Description
    (PD) and Contract Data Requirements (CDRLs)



Preproposal Conference, 19-21 Feb 08
                                       ~21~
            C.19 Integrated Logistics Support
       • ILS is an integral part of the design, development and integrations
         process. Because of this we will focus on:
       • Maintenance Support:
          • Two Level: FIELD and SUSTAINMENT (Army & USMC)
       • Operator Maintenance Procedures and Tasks
       • Bills of Material
       • Commonality Assessment
       • Limited Supportability Demonstration (LSD) Plan, Demo, & Report
       • Publications: TMs and IETMs
       • System Support Packages for Test
       • Tester Training Operator/Crew
       • Load Plan
       • Conditioned Based Maintenance Plus (CBM+)

Preproposal Conference, 19-21 Feb 08
                                         ~22~
            C.19 Integrated Logistics Support

      • Statement of Work (SOW)
      • Purchase Description (PD)
      • Contract Data Requirements (CDRL) List:
                  •   Human Factor Analysis                      CDRL A035
                  •   Bill of Materials                          CDRL A036
                  •   Commonality Assessment                     CDRL A037
                  •   Limited Supportability Demo Plan           CDRL A038
                  •   Limited Supportability Demo Report         CDRL A039
                  •   Draft Technical Manuals (TMs)              CDRL A040
                  •   Draft Interactive Electronic TMs (IETMs)   CDRL A041
                  •   System Support Package List                CDRL A042
                  •   Tester Training Plan                       CDRL A043
                  •   Load Plan                                  CDRL A044




Preproposal Conference, 19-21 Feb 08
                                                       ~23~
 C.20 Reliability, Availability, Maintainability (RAM) Program

• C.20.1 RAM Program
  • C.20.1.1 RAM Case Report
• C.20.2 RAM Predictions
  • C.20.2.1 Test Deficiencies
• C.20.3 RAM Modeling and Analysis
• C.20.4 Diagnostics
• SOW Section CDRL Listing
  • A045 – RAM Case Report
       • The Case Report shall support the Contractors claim in meeting or exceeding
         the RAM requirements specified in the purchase description. The RAM Case
         Report shall summarize the Contractor’s approach and framework for providing
         progressive assurance that the system will meet the reliability requirements
         specified in the purchase description.
  •   A046 – Reliability Prediction and Documentation of Supporting Data
  •   A047 – Reliability Block Diagrams
  •   A048 – RAM Modeling and Analysis
  •   A049 – Diagnostics

                                        ~24~
   C.21 GFE / GFI Integration & Installation

• Overview
  • C.21.1 The Contractor shall integrate all mission equipment to include
    GFE, Contractor Furnished Equipment (CFE) and Contractor
    Developed Equipment (CDE). Integration shall include providing
    space, power, weight allocation, heat load, cabling, cableways, all
    through hull connections, all other hardware and software interfaces
    and CFE mission equipment necessary to meet the requirements as
    stated in the Purchase Description (Attachment 1).
  • C.21.2 GFE/GFI List. A list of the types and quantities of GFE and GFI
    may be found at Attachment 21.


• CDRLs
  • There are no CDRLs in this section




                                   ~25~
000000000000000000000000000000000000000000000001111
111101010101010101001010101010010100000000000000000
000000000000000000000000000000010101010101010101001
111111111111111111111111111111111111111111111111111
111111111111111111111111111111111111111111111111011
111111110100101001001010101010100101010010101010100
000000000000000000000000000000111111111111111000000
                    JLTV Section C
000000000000011111111111111111111100000000000000000
                    Scope of Work
000000000000000000000000000000000000000000000000000
000000000000000011111111111110101010100010100101010
100101010101001010010101111111111111111111111111111
111111111111111111111111111111111111111111111111111
111111111111111111111111111111111111111111111100000
000000000000111111111111000000000000010100110010101
001010101001000000000000000000000000000000000000000
                          ~26~

								
To top