21 AUGUST 2007
PROGRAM MANAGER
USER MANUAL
for the
NAVAIR GENERIC
OPERATIONAL TEST PROGRAM SET
(OTPS)
REQUEST FOR PROPOSAL
(RFP)
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
2
Program Manager User Manual
25 December 2010
INTRODUCTION
This “Program Manager's User's Manual for the NAVAIR Generic Operational Test Program Set (OTPS) Request for Proposal (RFP)” is provided to inform and assist Support Equipment Team Leaders (SETLs), Program Managers (PMs) and Acquisition Managers in the use and tailoring of the NAVAIR Generic OTPS RFP for OTPS acquisition.
NOTE: These documents were formerly known as the Navy Red Team Package.
The latest version of the NAVAIR Generic OTPS RFP can be obtained from Melissa Alton, PMA260D22, Ed Holland, TAMI, or Jim Holliday, Eagle Systems. It is also available at: http://www.acq.osd.mil/ats/.
The package should be tailored to meet the procurement objectives set forth by the SETL and APML. Tailoring guidance can be found in Section 5.
Users of the NAVAIR Generic OTPS RFP are encouraged to seek assistance from the NAVAIR Generic OTPS RFP Integrated Product Team (IPT) representatives and discuss changes or new ideas with them. If the alternate approach is more advantageous for that particular acquisition, it could be beneficial for other OTPS acquisitions. Of course, it may be that the alternative approach is more advantageous for that particular acquisition only, due to specific and unusual program requirements.
The NAVAIR Generic OTPS RFP RECOMMENDATION FORM can be used to provide recommendations. If you have recommendations and/or changes, complete the form and send it to Ed Holland at or Jim Holliday at .
This Users Manual is divided into 5 sections. Brief definitions of the sections are as follows:
Section 1. OTPS PROCUREMENT PROCESS provides background information, lists
applicable acquisition documents, and discusses NAVAIR Instruction 13630.2D
Section 2. OTPS ACQUISITION lists typical Acquisition topics, discusses OTPS
Peculiar Acquisition Topics, and defines responsibilities for Acquisition Manager, PCO and COR.
Section 3. MILESTONE REVIEWS Figure 1 depicts the Defense Acquisition Management Framework as defined in DOD 5000.2 and provides guidance for Milestones A, B, and C.
Section 4. NAVAIR GENERIC OTPS RFP CONTENTS identifies the documents that make up the GENERIC OTPS RFP.
Section 5. TAILORING AND OTHER CONSIDERATIONS identifies the documents that can be tailored and provides guidance for the tailoring.
Table of Contents
Section Title
1. OTPS PROCUREMENT PROCESS
1.1 NAVAIR Generic OTPS RFP Background
1.2 Applicable Documents
2. OTPS ACQUISITION
2.1 Typical Acquisition Topics
2.2 OTPS Acquisition Manager (Team Leader) Responsibilities
2.3 Contracts
2.3.1 Procuring Contracting Officer (PCO)
2.3.2 Contracting Officer's Representative (COR)
3. MILESTONE REVIEWS
4. NAVAIR GENERIC OTPS RFP CONTENTS
4.1 Contract Schedule - Sections A-M
4.2 Exhibits/Contract Data Requirement List (CDRLs)
4.3 Attachments
5. TAILORING AND OTHER CONSIDERATIONS
5.1 Contract Sections
5.1.1 Special Topics
5.1.2 Contract Sections A-M
5.1.3 Exhibits
5.1.4 Attachment 1, Statement of Work
5.1.4.1 Engineering
5.1.4.2 Logistics
5.1.5 Attachment 5,Technical Manual Contract Requirements (TMCR)
5.1.6 Attachment 6, Provisioning Statement of Work (PSOW)
5.1.7 Attachment 7, Addressee List
5.1.8 Attachment 8, Technical Document Distribution Statements
List of Figures
Figure 1 - Defense Acquisition Management Framework
ii
Program Manager User Manual
25 December 2010
1. OTPS PROCUREMENT PROCESS
1.1 NAVAIR Generic OTPS RFP Background
NAVAIR's Red Team was formed in November 1989 as a service to Support Equipment Project Officers (SEPOs) (now referred to as Support Equipment Team Leaders (SETLs)), Program Managers (AIR-552), and Logistics Managers (AIR-417), with the following goals:
(a) Standardize Operational Test Program Set (OTPS) program requirements, deliverables, and procedures, ensuring lessons learned are considered
(b) Eliminate solicitation requirements that don't add value
(c) Simplify Request For Proposal (RFP) generation
(d) Reduce cost of proposal preparation
(e) Help ensure OTPSs are delivered on time
(f) Provide help to field activities involved in OTPS procurement
(g) Provide a forum for open exchange
(h) Incorporate lessons learned
The product that resulted was known as the “Red Team Package”. In order to more effectively communicate the nature of the product, this name has been changed to “NAVAIR Generic OTPS RFP”.
This RFP can be used as the starting point for all OTPS procurements within the Navy for Intermediate (I) Level OTPSs. The NAVAIR Generic OTPS RFP has been scrutinized by both Navy organizations and private industry. By using the NAVAIR Generic OTPS RFP as the starting point in preparing for OTPS procurements, there should be a marked decrease in both the time and manpower required to prepare that package for release. The completed, tailored package should represent the Navy's standardized procurement approach for OTPSs, modified to meet the specific needs of a particular program.
The NAVAIR Generic OTPS RFP is dynamic, and to be effective, it must be continually improved. This is only possible through effective feedback and open exchange between both government agencies and the private sector. The NAVAIR Generic OTPS RFP IPT welcomes any questions, comments, or suggestions from anyone. The NAVAIR Generic OTPS RFP IPT Team is:
TEAM LEADER Melissa Alton, PMA-260,
Patuxent River, MD; (301) 757-6887; fax (301) 757-6902
LOGISTICS Brian Cervenak,PMA160
Patuxent River, MD; (301) 757-6830; fax (301) 757-6902
TECHEVAL Greg Herold, NAVAIR Patuxent River 4.8
Patuxent River, MD; (301) 995-6443; fax (301) 995-6415
CONFIGURATION Jim Holliday, Eagle Systems Incorporated
MGR Virginia Beach, VA; (757) 498-5678; Fax (757) 498-5683
ADVISOR Ed Holland, Technology and Management International LLC (TAMI)
Manchester, NJ (609) 304-3251
1.2 Applicable Documents
The documents listed below are the principal documents relevant to the procurement of CASS OTPS. The latest revision of these documents should be consulted.
(a) NAVAIR INSTRUCTION 13630.2E, “Optimizing the Consolidated Automated Support System at All Levels of Maintenance from Factory to Field”
This instruction establishes policy, assign responsibilities, and provide procedures for optimizing the use of the Consolidated Automated Support System (CASS) Family and its associated Test Program Sets (TPSs) by the Naval Air Systems Command (NAVAIR) within the naval aviation maintenance process. The CASS Family includes the mainframe configurations of Hybrid, Radio Frequency, Communications/Navigation /Identification Friend or Foe (IFF), Electro-Optics, and High Power as well as the Reconfigurable Transportable CASS (RTCASS).
(b) NAVAIRINST 3960.2, Test and Evaluation
The Test and Evaluation Master Plan (TEMP) defines overall structure and objectives of the test and evaluation program, integrating necessary developmental, operational, and live fire test and evaluation activities, resources, schedule, management strategy, and evaluation criteria in a framework sufficient for generating other detailed test plans, schedules, and documents. A more thorough discussion of the TEMP process can be found on Wingspan in the NAVAIR Team Process Tool Kit under AIR 1.6 Processes. TEMPs are required for all Navy ACAT programs. The TEMP is reviewed for currency and updated, if required, at each milestone, when the acquisition program baseline is breached, or when the program changes significantly. A current approved TEMP is required for milestone decision reviews, conduct of testing, and for certification of readiness for operational test phases.
(c) NAVAIRINST 4200.36B, Acquisition Plans (APs)
Provides guidance on preparation, coordination, and approval of APs for NAVAIR and Naval Aviation PEO programs.
(d) NAVAIRINST 4200.37A, The Procurement Initiation Document (PID) Process
The Procurement Initiation Document Process delineates the PID process roles and responsibilities. It describes each player’s part in the process and the thresholds and reasons for holding Procurement Planning Conferences (PPCs) and Procurement Planning Agreements (PPAs). An example of a PPA is provided as an attachment to this instruction. This instruction is available through the NAVAIR website for instructions (i.e., http://www.nalda.navy.mil/instructions/ReportList.cfm).
(e) NAVAIRINST 4200.39A, 22 Jul 99, "Principles and Procedures for Competitive Source Selection Process and CH-1, Mar 14, 2000
To provide a common set of principles and procedures for competitive negotiated acquisitions of supplies and services conducted by the Naval Aviation Systems Team (TEAM) (i.e., Naval Air Systems Command (NAVAIR), its Naval Air Warfare Centers (NAWCs), its field activities, and the Naval Aviation Program Executive Offices (PEOs)).
(f) CASS USER’S LOGISTICS SUPPORT SUMMARY (ULSS) APPENDIX B
COMMON HAND TOOLS
Appendix B is a list of common hand tools required for CASS maintenance. It can be found by accessing https://pma260.navair.navy.mil. Click on CASS, click on DOCUMENTS click on CASS ULSS, and scroll down to APPENDIX B COMMON HAND TOOLS
2. OTPS ACQUISITION
An OTPS procurement typically takes a total of 18-24 months from requirements definition to contract award/funds obligation. The creation and processing of the RFP can increase this overall time. The use of the NAVAIR Generic OTPS RFP can help keep this time to a minimum. It will also create a consistent requirement to industry and a product of consistent performance for the user.
2.1 Typical Acquisition Topics
The following are typical acquisition topics that are normally addressed. They are not necessarily in sequential order. Those that have an asterisk (*) are addressed in the NAVAIR Generic OTPS RFP. The documents cited in paragraph 1.2 above are guidance documents for the acquisition process and the details are not provided here.
Acquisition Strategy
PR/Contracting Processing Times
Acquisition Plan
Source Selection Plan
Synopsis Requirement
Contract Type
Justification and Authorization
Type of Funds
Schedule
Security Classification
Small Business Application
Budget/Funds Availability
Typical Clauses
* Special Contract Requirements
* Data Rights
* Value Engineering
* Government Furnished Equipment/Government Furnished Material
* Warranties
* Options
* Evaluation Approach/Criteria
* Statement of Work (SOW)
* Specifications
* Integrated Logistics and Spares Acquisition Integrated in Production
* Reliability and Maintainability
* Safety
* Quality/Assurance
* Electromagnetic Environmental Operability
* Technical Evaluation (TECHEVAL)
* Production
* Potential/ Historical Problems
* Streamlining
2.2 OTPS Acquisition Manager (Team Leader) Responsibilities
(NOTE: Organizations may identify this person differently, i.e. Program Manager, IPT Leader, etc.)
(a) Become familiar with the Applicable Documents in Section 1.2 and utilize the information accordingly.
(b) Ensure that two sets of Ready For Issue (RFI) Units Under Test (UUTs) are available for delivery to the OTPS developer in accordance with program schedule requirements.
(c) Ensure that adequate source data on UUTs is available and determine its quality. If the UUT source data is inadequate for a competitive procurement, a sole source or organic procurement may be required.
(NOTE: The information below was prepared by Team 4.8.)
DATA REQUIREMENTS FOR TPS DEVELOPMENT
ITEM / Source / RequiredTechnical Data Package, Drawings / TDP / Yes
Assembly drawings of all assemblies (WRA and SRAs) / TDP / Yes
Parts lists / TDP / Yes
Interconnect diagrams for WRAs / TDP / Yes
Schematics for SRAs / TDP / Yes
Wire lists for WRAs w/o CCA motherboards / TDP / Yes
Theory of operation (may be available from Tech Pub / Tech Pub / Yes
Proprietary data / TDP
Programmable device source data (ROMs, PALs, EPROMs, FPGAs etc / TDP / Yes
Source code on OFPs and mission software / Yes
Built in Test source data / Yes
Test Requirements Documents (TRDs) / Yes
Test Specifications (WRAs only) / Yes
Acceptance test procedures / TDP / Yes
Factory test procedures / Yes
Environmental requirements / Yes
Interface Control Documents (ICD) manufacturer’s / Yes
Engineering Change Notice / Proposal (ECN / ECP) / Yes
Assembly drawings of all assemblies (WRA and SRAs)
Used to identify parts location
Physical size and structure of UUT.
Used for designing holding fixtures
Parts lists
Used to identify piece parts by type and manufacturer
Used to identify UUT mating connector type and manufacturer
Interconnect diagrams for WRAs
Required to determine how the WRA functions
Used to aid in fault isolation
Determine buss structure
Schematics for SRAs
Identifies the function of the UUT
Wire lists for WRAs w/o CCA motherboards
Required to determine how the WRA functions
Used to aid in fault isolation
Determine buss structure
Can be eliminated if interconnecting diagram is provided
Theory of operation (may be available from Tech Pub
Provides theory of operation
Allows functional testing
Proprietary data
Any proprietary data rights need to be disclosed
May require non disclosure agreement with OEM
Programmable device source data (ROMs, PALs, EPROMs, FPGAs etc
Required to perform DATPG testing of devices
Source code on OFPs and mission software
Required if OFP is to be tested
Required if OFP is to be reloaded after testing and repair
Required if OFP provides Self Test capability
Built in Test source data
Required to make full use of BIT capabilities
Shortens run times
Allows I level to capitalize on O level testing
Test Requirements Documents (TRDs)
Nice to have
Provides all testing requirements as identified by developer
Not always technically correct
Acceptance test procedures
Provides minimum tests required to ensure that the UUT is RFI
Factory test procedures
Allows capitalization on existing effort
Environmental requirements
Required if the UUT has specific cooling requirement, liquid, forced air etc.
May be able to determine requirements from the WRA tech pub
Interface Control Documents (ICD) manufacturer’s
Provides how each circuit is designed to be used (design interface) in the system.
Should also provide special timing characteristics, waveforms, and functional / logic specifications.
Engineering Change Notice / Proposal (ECN / ECP)
Provides information on changes to the baseline or any proposed changes.
(d) CASS Configurations
1. Determine the CASS configurations/quantities required to test the UUTs. The use of the CASS SSM is the best approach to determine the CASS configuration needed. Contact Salvatore Licci, NAWCADLKE, at (732) 323-7734 for assistance.
2. In accordance with NAVAIRINST 13630, the Weapon Systems PMA will review the method used to determine and the resultant CASS configurations/quantities required with PMA260 and to assess impact to the Fleet and CASS program.
NOTE: The Weapons System PMA will prepare a Histogram showing the number and type of CASS needed plotted against a monthly time line. The time shall be for the entire period of performance. It shall be broken into the following segments, if included in the contract:
Development
Integration
First Article Test
TECHEVAL