Vertical Take Off and Landing Tactical Unmanned Aerial Vehicle (VTUAV)
Statement of Objectives (SOO)
1.0 Program Scope
The Vertical Take Off and Landing Tactical Unmanned Aerial Vehicle (VTUAV) system is a joint USN/USMC system to provide an Intelligence, Surveillance, and Reconnaissance (ISR) capability to support littoral operations. This SOO will describe the Government’s acquisition philosophy and objectives for the Engineering and Manufacturing Development (EMD) and Low Rate Initial Production (LRIP) Phases of the VTUAV acquisition. The successful VTUAV system will be an affordable, versatile, and maintainable system that meets the Navy and Marine Corps requirements offering Best Value for the Government in an effective, economical, and timely manner.
The purpose of the VTUAV acquisition is to design, develop, test, and produce a product baseline for the VTUAV system sufficient to allow for a Milestone III (full rate production) decision. The Government requires the contractor to:
a. Deliver and test a VTUAV nsystem engineering development model (EDM) system.in accordance with the RFP
b. Deliver two up to three Low Rate Initial Production (LRIP) systems in accordance with the RFP.
c. Provide logistics analysis and support for Government test activities and to support a Milestone III decision.
d. Provide product baseline documents in sufficient depth to allow the Government to award a production contract.
e. Provide a detailed schedule to define the timeline, critical path, and key elements of the process to support the successful delivery of the VTUAV system. The schedule milestones should span from contract award through delivery of the third second LRIP and include a notional production timeline. with follow on capability The Government anticipates contract award in Feb 00, a Technical Evaluation test period, completion of Operational testing including the final report in January 03, and the Milestone III decision in February 03. The Government requires a 9 month window to perform the operational test and reporting to support a successful Milestone III decision and anticipates using the first LRIP system for operational this testing.
3.0 specifications and standards
If a Government specification or standard is not clearly required, the Government encourages the contractor to use Commercial, Industrial and Corporate specifications and standards in lieu of Government specifications and standards if they are preferred by the offeror. Government specifications and standards, if needed, should be used as guides, with any modifications, tailoring or partial application described. Foreign specifications and standards may be used if existing equipment from non-U.S. suppliers is being proposed.
4.3.1 Management Structure: The program will use an Integrated Product Team (IPT) management structure as a means to gain insight and provide timely exchange of information and data. The contractor shall establish an ACA with the Tactical Control System (TCS) System Integrator prime contractor.
4.3.2 Analysis: The Government will use the contractor’s Integrated Master Schedules (IMS), Risk Plan, CWBS, Earned Value Management System (EVMS), program reviews, and SOW, as tools to determine contractor’s progress, and critical path, key events, and risk.
4.3.3 Data Management:Transfer: The Government’s Oobjective is to use electronic media, as defined in the Government Data Management Concept of Operations, see section J attachment #4 of the RFP to improve for data transfer , to improve efficiency and affordability. Access to real time critical data is of the utmost importance. Any data deliverable required by CDRL shall meet the technical content of the data item descriptions (DIDs).
4.3.4 Other data or data not required per CDRL the contractor shall use the associated DID for guidance only.
Software Engineering: The Government’s goal objective is to have a contractor, and appropriate their subcontractors, with shall have a Level Three software development and support capability as determined by using the Software Engineering Institute (SEI) Capability Assessment Methodology or an equivalent process. The contractor shall ensure that Level Three software development and support capability exists within all sub-contractors in the program.
4.3.5 Programs: The Government"’s objective is to have,contractor shall have at a minimum, the following core programs: Risk Management, System Safety, Configuration Management, Operations Security and Communication, Cost commitment program in accordance to the H-xx Clause, Hazardous Materials Management Program (HMMP) and Environmental using as a guide the National Aerospace Standard 411, Systems Engineering Management, Logistics Management, Reliability and Maintainability, and Software Management.
4.3.6 Reviews: The program will have periodic reviews/audits such as: System Requirements Reviews, Integrated Baseline Reviews, Preliminary Design Reviews, Critical Design Reviews, Test Readiness Reviews, Functional Configuration Audits, Physical Configuration Audits, Software Reviews, Logistics Reviews, and other similar reviews/audits necessary to track program’s progress. IBR anticipated within 6 months of contract award.