STATEMENT OF WORK CIVIL RESERVE AIR FLEET (CRAF) AEROMEDICAL EVACUATION SHIP SET 12 MAY 1988 [SELECTED PARAGRAPHS EXTRACTED FOR CLASSROOM USE ONLY] SECTION C - DESCRIPTION/SPECIFICATIONS 12 MAY 1988 TABLE OF CONTENTS PARA WBS level WBS Number TITLE PAGE 1. SCOPE 1 1.1 Objective 1 1.2 Program Description 1 1.2.1 Patient Transport Subsystem 1 1.2.2 Medical Oxygen Subsystem 1 1.2.3 Aeromedical Operations Subsystem 1 1.3 Background 1 2. LISTING OF APPLICABLE DOCUMENTS 2 2.1 Standards 2 2.2 Specifications 2 2.3 Other Documents 2 |1|2|3|4| 3. |X| | | | 1000 REQUIREMENTS FOR B-767 SHIP SETS 2 3.1 | |X| | | 1100 Hardware Development 2 3.1.1 | | |X| | 1110 Patient Transport Subsystem 2 3.1.2 | | |X| | 1120 Medical Oxygen Subsystem 2 3.1.3 | | |X| | 1130 Aeromedical Operations Subsystem 2 3.2 | |X| | | 1200 Training Supplies 2 3.3 | |X| | | 1300 Data 2 3.3.1 | | |X| | 1310 Data Management 2 3.3.2 | | |X| | 1320 Engineering Drawings & Associated Lists 3 3.3.3 | | |X| | 1330 Technical Publications 3 | 3.4* | |X| | | 1400 Logistics Management 3 3.4.1* | | |X| | 1410 Integrated Logistics Support (ILS) 3 3.4.2 | | |X| | 1420 Preoperational Support/Maintenance 3 3.4.3 | | |X| | 1430 Support Equipment 3 3.5 | |X| | | 1500 Test and Evaluation 4 3.5.1 | | |X| | 1510 Developmental Test & Evaluation (DT&E) 4 3.5.2 | | |X| | 1520 Operational Test & Evaluation (OT&E) 4 3.5.3 | | |X| | 1530 Upgrade of OT&E Prototype 4 3.6 | |X| | | 1600 Engineering 5 3.6.1 | | |X| | 1610 Systems Safety 5 3.6.2 | | |X| | 1620 Human Factors 5 3.6.3 | | |X| | 1630 Logistics Engineering 5 126.96.36.199 | | | |X| 1631 Maintainability 5 188.8.131.52 | | | |X| 1632 Reliability 5 184.108.40.206 | | | |X| 1633 Government/Industry Data Change Program 5 3.6.4 | | |X| | 1640 Packaging Handling and Transportability 5 3.6.5 | | |X| | 1650 Production/Manufacturing Management 5 3.6.6 | | |X| | 1660 Quality Assurance 5 3.6.7 | | |X| | 1670 FAA Supplemental Type Certification 5 • Not provided SECTION C - DESCRIPTION/SPECIFICATIONS 12 MAY 1988 PARA WBS level WBS Number TITLE PAGE 3.7 | |X| | | 1700 Program Management 6 3.7.1 | | |X| | 1710 Post Award Conference 6 3.7.2 | | |X| | 1720 Management Reviews 6 3.7.3 | | |X| | 1730 Functional Qualification Review (FQR) 7 3.7.4 | | |X| | 1740 Contract Work Breakdown Structure (CWBS) 7 3.7.5 | | |X| | 1750 Cost Management 7 3.7.6 | | |X| | 1760 Schedule Management 7 3.8 | |X| | | 1800 Configuration Management 8 3.8.1 | | |X| | 1810 Configuration Management Plan (CMP) 8 3.8.2 | | |X| | 1820 Configuration Identification 8 3.8.3 | | |X| | 1830 Configuration Control 8 3.8.4 | | |X| | 1840 Functional Configuration Audit 8 3.8.5 | | |X| | 1850 Nomenclature 9 3.9 | |X| | | 1900 Associate Contractor Agreements 9 4. |X| | | | 2000 REQUIREMENTS for MD-80 SHIP SETS 9 4.1 | |X| | | 2100 Hardware Development 9 4.1.1 | | |X| | 2110 Patient Transport Subsystem 9 4.1.2 | | |X| | 2120 Medical Oxygen Subsystem 9 4.1.3 | | |X| | 2130 Aeromedical Operations Subsystem 9 4.2 | |X| | | 2200 Training Supplies 10 4.3 | |X| | | 2300 Data 10 4.3.1 | | |X| | 2310 Data Management 10 4.3.2 | | |X| | 2320 Engineering Drawings and Associated Lists 10 4.3.3 | | |X| | 2330 Technical Publications 10 4.4 | |X| | | 2400 Logistics Management 11 4.4.1 | | |X| | 2410 Integrated Logistics Support (ILS) 11 4.4.2 | | |X| | 2420 Preoperational Support/Maintenance 11 4.4.3 | | |X| | 2430 Support Equipment 11 4.5 | |X| | | 2500 Test and Evaluation 11 4.5.1 | | |X| | 2510 Developmental Test & Evaluation (DT&E) 11 4.5.2 | | |X| | 2520 Operational Test & Evaluation (OT&E) 12 4.5.3 | | |X| | 2530 Upgrade of OT&E Prototype 12 4.6 | |X| | | 2600 Engineering 12 4.6.1 | | |X| | 2610 System Safety 12 4.6.2 | | |X| | 2620 Human Factors 13 4.6.3 | | |X| | 2630 Logistics Engineering 13 220.127.116.11 | | | |X| 2631 Maintainability 13 18.104.22.168 | | | |X| 2632 Reliability 13 22.214.171.124 | | | |X| 2633 Govt/Industry Data Exchange Program 13 4.6.4 | | |X| | 2640 Packaging Handling and Transportability 14 Critique: WBS level and WBS number columns show a good outline, but what is the “value added?” If this extra information includes any mistakes, misinterpretations, or conflicts, they are the responsibility of the government. Note paragraph 4 in the Table of Contents, requirements for MD80 shipsets. Are we trying to build one or two shipsets? This SOW gives the contractor the leeway, and almost requires, a unique shipset for both configurations; and also could result in double charging of some costs. What we really wanted was one shipset designed for the B- 767 and adaptors for the MD80. Rather than paragraph 4, an additional sub- paragraph (3.10 Adaptors for MD80) may have clarified the requirements. SECTION C - DESCRIPTION/SPECIFICATIONS 1. SCOPE 1.1. Objectives. This statement of work covers design, development, and test of the Civil Reserve Air Fleet (CRAF) Aeromedical Evacuation Ship Set (AESS). The data to be delivered as a result of performing the task prescribed by this statement of work are specified in the Contract Data Requirements List (CDRL). Critique: The scope should focus on mission need and related constraints. Design, develop and test are fine; however, we also wanted integration, manufacturing and assembly. CDRL information goes in sect 3 requirements, not in the scope. 1.2 Program Description. The CRAF AESS program will enable B-767 and MD-80 aircraft to be used in the role of aeromedical evacuation. The CRAF AESS must be able to endure long periods of storage and be capable of easily and quickly transforming the commercial aircraft into an aeromedical evacuation mode. The CRAF AESS will consist of three primary subsystems; patient transport subsystem, medical oxygen subsystem, and the aeromedical operations subsystem. (MD-80" as used in this Statement of Work refers only to the MD-81, MD-82, and MD-83 models of the MD-80 series of aircraft) 1.2.1 Patient Transport Subsystem (PTS). The PTS will be the CRAF AESS subsystem providing patient handling during flight operations. The PTS will include: litters, stanchions, straps for attaching equipment, and seats for ambulatory patients and crew. 1.2.2 Medical Oxygen Subsystem (MOS). The MOS is the CRAF AESS subsystem providing oxygen to those patients requiring it continuously as well as emergency oxygen for all passengers. The MOS includes: liquid oxygen storage container(s), filling system, and distribution system. 1.2.3 Aeromedical Operations Subsystems (AOS). The AOS includes equipment necessary for aeromedical operations during flight. The AOS includes: electrical distribution, lighting, storage for medical equipment and supplies, food preparation and storage, lavatory facilities, and water supply system. Critique: Paragraphs 1.2.1, 1.2.2, and 1.2.3, are written like detail specifications and, in fact, may limit contractor flexibility. 1.3 Background. The concept of operations for the B-767 and MD-80 aircraft are described in the System Operational Capability (SOC), see Appendix B. In the event of conflict, the System Specification, Appendix A to this SOW, takes precedence over the SOC. Critique: The System Operational Capability Document (or an Initial Capabilities Document; Capabilities Development Document; or Capabilities Production Document) are warfighter requirements and represent the government program manager’s contract with the user. It’s generally better to share this information with the contractor informally, rather than reference it in the contract and risk interpretation conflicts (which the government almost always loses). SECTION C - DESCRIPTION/SPECIFICATIONS 3. PHASE ONE: REQUIREMENTS FOR B-767 SHIP SETS (WBS 1000) The contractor shall comply with the following: 3.1 Hardware Development. (WBS 1100) The contractor shall design, develop, fabricate and test the CRAF AESS to conform to all the requirements of Appendix A, the system specification, HSD-FY86-003, and all future specifications detailing the CRAF AESS performance/hardware. The contractor shall ensure all items listed in Addendum I to Appendix A are compatible with CRAF AESS use. Producibility shall be a major concern during the design, development, fabrication, and test effort. Critique: The statement “all future specifications…” is a tragic error. It’s not measurable, predictable, and will allow the contractor to bid in enormous risk. The statement “producibility shall be a major concern…” is not measurable, clear or well defined, and will allow the contractor to bid in enormous risk. The statement is included only to pacify government senior management (fact). 3.1.1 Patient Transport Subsystem. (WBS 1110) The contractor shall design, develop, fabricate, test and integrate a patient handling subsystem into the CRAF AESS. The contractor shall design the equipment to be common to the B-767 and the MD-80 Series wherever possible. Critique: The statement “ …wherever possible” is not clear, measurable, or verifiable and is basically meaningless. 3.1.2 Medical Oxygen Subsystem. (WBS 1120) The contractor shall design, develop, fabricate, test and integrate a medical oxygen subsystem into the CRAF AESS. The contractor shall design the equipment to be common to the B-767 and the MD-80 Series wherever possible. Critique: The statement “ …wherever possible” is not clear and is basically meaningless. 3.1.3 Aeromedical Operations Subsystem. (WBS 1130) The contractor shall design, develop, fabricate, test and integrate an aeromedical operations subsystem into the CRAF AESS. The contractor shall design the equipment to be common to the B- 767 and the MD-80 Series wherever possible. Critique: The statement “ …wherever possible” is not clear and is basically meaningless. 3.2 Training Supplies. (WBS 1200) The contractor shall video tape the operational use and emergency procedures for the CRAF AESS configured aircraft. The contractor may tape during operational test and evaluation (OT&E). The following data item is applicable: CDRL Seq No L003 DI-ILS-80090/T Videotape Presentation 3.3 Data. (WBS 1300) 3.3.1 Data Management. (WBS 1310) The contractor shall establish and maintain data management procedures to ensure the data necessary to support the CRAF AESS program are available in the proper form at the proper time. The contractor shall monitor and review all data required by this contract and shall recommend additions, deletions, and alterations to the data requirements of this contract when such action may result in more economical or better use of the data. The contractor shall minimize duplication of effort in the development and preparation of applicable data items by cross referencing. The following data items are applicable: CDRL Seq No A004 DI-A-3027A/T Data Acquisition List/Internal Data CDRL Seq No M003 DI-MISC-80167 Contract Data Status and Schedule Report SECTION C - DESCRIPTION/SPECIFICATIONS 3.3.2 Engineering Drawings and Associated Lists. (WBS 1320) The contractor shall document the design of the CRAF AESS in engineering drawings and associated lists in accordance with (IAW) DOD-STD-100C and DOD-D-1000B as set forth below. The data shall fully disclose information necessary to evaluate, test, manufacture and reprocure the system. The contractor shall host six in-process reviews with the government to ensure the drawings meet the required standards. Critique: Though six in-process reviews are measurable, they are not clear. The reviews need to be defined in terms of agenda, entrance and exit criteria, level of effort (i.e., number and type of contractor personnel/support) type (i.e., PDR, CRD, PCA/FCA.) DOD-STD-100C Engineering Drawing Practices 22 Dec 78 Notice 4 4 May 83 DOD-D-1000B Drawings, Engineering and Associated Lists 28 Oct 77 Amend 3 13 May 83 The following data items is applicable: CDRL Seq No E007 DI-E-7031/T Drawings, Engineering and Associated Lists Critique: The first question is do we need to buy the drawings, technical data packages (TDP?) Buying and maintaining TDPs is very expensive. Unless the government is going to maintain, repair, or support the system organically, we may not need the drawings and could realize a huge cost savings. Of course, if the government intends to maintain, repair, or support, the TDP is a must. 3.4.2 Preoperational Support/Maintenance. (WBS 1420) The contractor shall provide spares and repair parts, support equipment, and special test equipment necessary throughout the development, developmental tests, and operational tests of CRAF AESS. The contractor shall perform, document, and maintain records of all preoperational and preventative maintenance of the test article(s), and all equipment stored within, including auxiliary, special and support equipment until the Government formally accepts the test article after FQR. The contractor shall document the preoperational and preventive maintenance actions. Preoperational maintenance shall include the government equivalent of intermediate, organizational, and depot maintenance. The contractor shall brief support and maintenance issues at design reviews. Critique: General comment: There are too many different, unique tasks included in one paragraph, and also in one sentence. Each unique task should be separate. The statement “… until the government formally accepts the test article after FQR,” is open- ended. 3.4.3 Support Equipment (SE). (WBS 1430) The contractor shall design the CRAF AESS such that it can be maintained and installed by the airline owning the B-767s with their existing support equipment and tools. Critique: This meaning of this statement is not clear. Are we tasking the contractor to survey all 767 owners to determine the baseline for existing support equipment? This baseline should be in the system specification. SECTION C - DESCRIPTION/SPECIFICATIONS 3.5 Test and Evaluation. (WBS 1500) 3.5.1 Development Test and Evaluation (DT&E). (WBS 1510) The contractor shall be a member of the Test Plan Working Group (TPWG). The contractor shall attend two TPWG meetings at Brooks AFB, Texas. The contractor shall plan for system and configuration items testing. Based on the preliminary design and systems performance specifications, including the Type B specification(s) the contractor shall establish detailed test criteria for DT&E, to include qualification of the final full scale development system. The contractor shall conduct tests in accordance with the approved test plans and procedures to demonstrate the CRAF AESS satisfies specification requirements. The contractor shall provide test facilities, equipment and resources necessary to support DT&E. The contractor shall document and correct all deficiencies identified during DT&E. The contractor shall correct all deficiencies identified during independent safety-of-flight testing conducted by USAFSAM. The following data items are applicable: CDRL Seq No T001 DI-T-3702A/T Contractor Test Plans/Procedures CDRL Seq No T002 DI-T-3718A/T Test Reports - General Critique: Too many tasks are grouped together. The resources necessary (i.e., level of effort/number and type of personnel) for the two Test Planning Working Group (TPWG) meetings should be included. Actually, seven TPWG meetings were held. The statement “… document and correct all deficiencies…” is open ended, ill defined, unlimited, and makes no distinction of who is at fault. Also, contractor involvement at “independent testing” can be tricky and must be strictly monitored. 3.5.2 Operational Test and Evaluation (OT&E) - Contractor Support. (WBS 1520) The contractor shall support a seven day Air Force sponsored OT&E. OT&E is expected to be an exercise of the AESS configured CRAF aircraft from the United States to the Federal Republic of Germany and back (total mission duration approximately 3 days). The contractor shall fabricate one CRAF AESS system prototype for OT&E. The contractor shall perform a systems functional check out to verify test articles are ready and safe for OT&E. The contractor shall correct all deficiencies identified during routine inspections or routine maintenance prior to OT&E. The contractor shall supply technical support of system operations, observe deficiencies, and recommend changes to correct operational deficiencies identified during OT&E. The contractor shall document, report, and correct design deficiencies identified during OT&E. The following data item is applicable: CDRL Seq No R001 DI-RELI-80253/T Failed Item Analysis Report Critique: The “seven day” support is unnecessarily limiting, what if it takes eight days. The statement “The contractor shall fabricate one CRAF AESS system prototype for OT&E” does not belong here in this test paragraph. The last two sentences were all well meaning, but created problems. They need to be clearer and delineate the specific tasks required. Also, rules and laws exist that can limit contractor involvement in OT&E. 3.5.3 Upgrade of Operational Test and Evaluation (OT&E) Prototype. (WBS 1530) The contractor shall upgrade the OT&E prototype after conclusion of testing to the final, intended production configuration. This upgrade shall include correction of all deficiencies identified during testing, and shall conform to the final Level III drawing package submitted during Phase I. Critique: “Upgrading the prototype” and “conforming to final level III drawing package” are conflicting requirements. What they really wanted was the drawing package updated often with the hardware fixes. SECTION C - DESCRIPTION/SPECIFICATIONS 3.6 Engineering (WBS 1600) The following data item is applicable: CDRL Seq No A005 DI-A-3028B Abstract of New Technology (ANT) Critique: Omitted the engineering requirements and tasks. 3.6.1 System Safety (WBS 1610) The contractor shall establish and maintain a system safety program IAW the general requirements of MIL-STD-882B as set forth below. The contractor shall document all identified hazards and determine the Real Hazard Index (RHI) for each hazard. Prior to any testing, the contractor shall follow the safety order of precedence to resolve catastrophic and critical, and guard against marginal hazards. The contractor shall track and fully resolve catastrophic, critical and marginal hazards. The contractor shall perform a Preliminary Hazard Analysis, a System Hazard Analysis, and an Operating & Support Hazard Analysis (PHA, SHA, O&SHA). The SHA shall be accomplished using the fault hazard analysis technique to evaluate the hazards. The contractor shall analyze all engineering change proposals and requests for deviation/waiver for system safety impact. The contractor shall revise previously accepted hazard analysis reports as necessary when changes make the reports inaccurate or incomplete. MIL-STD-882B System Safety Requirements 30 Mar 84 PARA 4.1 System Safety Program 4.2 System Safety Program Objectives 4.3 System Safety Design Requirements 4.4 System Safety Precedence 4.5 Risk Assessment TASK 100 System Safety Program 105 Hazard Tracking and Risk Resolution 106 Test and Evaluation Safety 202 Preliminary Hazard Analysis 204 System Hazard Analysis 205 Operating and Support Hazard Analysis 211 Safety Review of Engineering Change Proposals and Requests for Deviations and Waivers (126.96.36.199) The following data item is applicable: CDRL Seq No S001 DI-SAFT-80101/T System Safety Hazard Analysis Report CDRL Seq No S002 DI-SAFT-80103/T Engineering Change Proposal System Safety Report CDRL Seq No S003 DI-SAFT-80104/T Waiver or Deviation System Safety Report Critique: This many unique tasks that should be listed individually. Good job tailoring requirements. SECTION C - DESCRIPTION/SPECIFICATIONS 3.7 Program Management. (WBS 1700) The contractor shall establish a program management office with responsibilities for planning, directing, and controlling the CRAF AESS full-scale development as well as planning for production. 3.7.1 Post Award Conference (PAC). (WBS 1710) The contractor shall host a PAC to be chaired by the government no later than 30 days after contract award. The purpose of this meeting is to ensure all parties concerned understand the scope of this contract. The contractor shall take and distribute accurate minutes of the meeting. The following data item is applicable: CDRL Seq No A007 DI-A-7089/T Conference Minutes Critique: If you’re concerned about “accurate minutes,” take them yourself. 3.7.2 Management Reviews. (WBS 1720) The contractor shall plan for and host formal technical reviews. The contractor shall conduct the following formal technical reviews to the agreed upon schedule. Preliminary Design Review (PDR), Critical Design Review (CDR), and Production Readiness Review(s) (PRR). The contractor shall conduct the reviews IAW MIL-STD-1521B. The contractor shall present Producibility assessments and issues at all design reviews. The contractor shall host a PRR(s) after OT&E IAW MIL-STD-1521B. The contractor is encouraged to combine similar FAA certification meetings with the design reviews, if possible. MIL-STD-1521B Technical Reviews and Audits for Systems, 4 June 85 Equipment, and Computer Programs Notice 1 19 Dec 85 All Paragraphs except 2 Appendices D, E, and K The following data items are applicable: CDRL Seq No A006 DI-A-7088 Conference Agenda CDRL Seq No A007 DI-A-7089/T Conference Minutes Critique: “… agreed upon schedule” is not clear or referenced to any written schedule. Furthermore, technical reviews should be event-based, i.e., conducted when the program has achieved the entrance criteria to the review. Rather than referencing an entire standard, tailor or call out the specific requirements. Also, good luck coordinating with the FAA. SECTION C - DESCRIPTION/SPECIFICATIONS 3.7.4 Contract Work Breakdown Structure (CWBS). (WBS 1740) The contractor shall develop and maintain a CWBS using the project summary work breakdown structure (Appendix C of this SOW) as a baseline. The negotiated CWBS will provide a basis for further evolutionary extension by the contractor to lower levels during the performance of the contract. The contractor shall use the CWBS as the primary framework for contract planning, budgeting, cost, and schedule status reporting. The contractor shall identify within the CWBS all subcontracted elements or tasks. During the performance of the contract, the contractor cannot change the CWBS or associated definition at levels three or above, or for any reporting elements, without the written approval of the contracting officer. The contractor may make changes at lower levels as deemed necessary without Government approval; however, the changes must be within the constraints set forth in the definitions of the higher-level CWBS elements. MIL-STD-881A Work Breakdown Structure for Defense Material 25 April 75 Items All except section 2 The following data item is applicable CDRL Seq No A003 DI-A-3023 Contract Work Breakdown Structure Critique: Tailor the standard to the applicable appendix. 3.7.5 Cost Management. (WBS 1750) The contractor shall use a cost management system of his own design for planning and controlling cost and for measuring performance. The Air Force CRAF AESS program manager or his designated representatives will visit the contractor's facility to gain an understanding of how the contractor is generating cost schedule information to fulfill C/SSR contract requirements. During the visit the contractor shall provide a description or review of his system in actual operation. After a mutual understanding is gained, the contractor shall notify the Contracting Officer (CO) and the Air Force Program Manager of changes to procedures used during the contract and explain the new method and reason for the change. The contractor shall analyze, determine, and integrate life cycle cost (LCC) considerations into the overall program management and system design responsibilities. The contractor shall emphasize designing a system with an optimum balance between LCC and operational effectiveness. The following data items are applicable: CDRL Seq No F001 DI-F-6004B/T Contract Funds Status Report (CFSR) CDRL Seq No F002 DI-F-6010A Cost/Schedule Status Report (C/SSR) Critique: “The contractor shall use a cost management system of his own design for planning and controlling cost and for measuring performance” is a fine example of a performance – based requirement. The statement “… shall emphasize designing” is not clear or measurable.
Pages to are hidden for
"CIVIL RESERVE AIR FLEET _CRAF_ AEROMEDICAL EVACUATION "Please download to view full document