SOURCES SOUGHT
58 -- Joint Threat Emitter Increment 2
- Notice Date
- 3/4/2009
- Notice Type
- Sources Sought
- NAICS
- 334511
— Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing
- Contracting Office
- Department of the Air Force, Air Force Materiel Command, Hill AFB OO-ALC, OO-ALC/PKXB, 6038 Aspen Ave (Bldg 1289), Hill AFB, Utah, 84056
- ZIP Code
- 84056
- Solicitation Number
- FA8217-09-R-JTE2
- Archive Date
- 4/3/2009
- Point of Contact
- Michael Scott Arbon,, Phone: 8015862246, Christine J. Parker,, Phone: 8017776171
- E-Mail Address
-
michael.arbon@hill.af.mil, christine.parker@hill.af.mil
- Small Business Set-Aside
- N/A
- Description
- JOINT THREAT EMITTER INCREMENT 2 (JI2) REQUEST FOR INFORMATION NOTE: This RFI is not a new requirement. This RFI supplements previous RFI's FA8217-08-R-JTE2, FA8217-08-R-XXX2, FA8217-08-R-TBD2, and FA8217-08-R-TBD. Overview: The purpose of this Request for Information is to assist Hill AFB Utah, Range Threat Systems Program Office (RTSPO) in Market Research of Industry to determine the extent of effort and estimated cost necessary to reach a Technical Readiness Level 6 (TRL 6) necessary for the JI2 program to proceed to the Engineering and Manufacturing Development (EMD) Milestone B phase. The RTSPO is proposing a phased acquisition approach for the JI2 program. Multiple contractors may be selected through source selection to participate in the Technology Development (TD) phase (1st contract award). The purpose of the TD phase is for selected contractors to verify appropriate software/hardware TRL and complete a Preliminary Design Review (PDR) that includes a formal PDR report and associated design drawings and documentation for government approval and recommendation to the Milestone Decision Authority to enter the Milestone B (EMD) phase. The second phase of the program (EMD phase) will provide a 2nd contract award, which will employ full and open competition. Contractors involved during the first phase (TD) may choose to submit the designs developed when submitting their respective proposals. Other contractors not participating in the 1st contract phase will NOT be excluded from this 2nd phase and may also submit proposals for consideration. One contractor will be selected for the EMD phase to develop a complete pre-production unit, perform factory and field level testing (Site Acceptance Test) and complete Functional and Physical Configuration Audits to qualify the design. If the design meets all requirements and is accepted by the government, the 2nd contract will also contain an option to produce up to 20 production units. The government is requesting a minimum of government purpose data rights for 1st and 2nd contract. For the purpose of this RFI, no information is required or requested for this phase. Request for Information: This Request For Information is for the 1st contract award (TD phase) only, and requests each interested contractor provide the following information: (1) test approach to reach TRL 6 (test, verification test reports, etc); (2) schedule to reach PDR/TRL 6 and (3) estimated cost necessary to reach a PDR that includes TRL 6 documentation, design package and reports for both the software and the hardware associated with a total JI2 system (top-level system description is below). Recent Change in Policy Discussion: Recent changes in Government Acquisition Policy have changed emphasis on Technical Readiness Levels for both hardware and software necessary to proceed to the next Milestone acquisition phase. Recently, the Milestone Decision Authority approved program entrance post-Milestone A (TD phase) (see red program entrance diamond below for reference). The TRL 6 is a requirement necessary to enter Milestone B (EMD phase). The TRL 6 must be proven through appropriate tests or validation and included in a formal Preliminary Design Review (PDR) report for government approval scheduled prior to Milestone B. Below is the Milestone chart extracted from DODI 5000.02 (Dec 08) http://www.dtic.mil/whs/directives/corres/pdf/500002p.pdf : TRL Level 6 Discussion: The TRL level definition is contained in the Technology Readiness Assessment Deskbook (2005) https://acc.dau.mil/CommunityBrowser.aspx?id=154268&lang=en-US and further interpreted below for hardware and software. Hardware TRL 6: Definition: System/subsystem model or prototype demonstration in a relevant environment. Description: Representative model or prototype system, which is well beyond that of TRL 5, is tested in a relevant environment. This represents a major increase in a technology's demonstrated readiness. Examples include testing a prototype in a high fidelity laboratory environment or in a simulated operational environment. Interpretation: TRL 6 can be declared for any level of the system or a sub-system, however, the demonstration that TRL 6 has been met must be accomplished at a hardware level that matches that of a deliverable sub-system in the final system configuration. Prototype(s) tested may consist of a scaled down version (number of repeated elements) of the sub-system, as long as the characteristics of the subset used can be shown to be representative of the entire sub-system. For example, a phased array antenna sub-array consisting of approximately 10% of its total number of elements is the minimum that is determined to be acceptable. Full capability to control this sub-array and process information from the array will be required as part of the prototype. Software TRL 6: Definition: Module and/or subsystem validation in a relevant end-to-end environment. Description: A level at which the engineering feasibility of a software technology is demonstrated. This level extends to laboratory prototype implementations on full-scale realistic problems in which the software technology is partially integrated with existing hardware/ software systems. Interpretation: Software TRL 6 must include all sub-assembly and total system interactions simulated or integrated with existing hardware sub-systems. Independent sub-systems with hardware in the loop sub-assembly simulations are preferred. TRL level Related Term Definitions: Model: A functional form of a system, generally reduced in scale, near or at operational specification. Models will be sufficient to allow demonstration of the technical and operational capabilities required of the final system. Prototype: A physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility of a particular technology or process, concept, end item, or system. Relevant Environment: Testing environment that simulates the key aspects of the operational environment the system is expected to operate in. Operational Environment: Environment that addresses all the operational requirements and specifications required of the final system to include platform/packaging. High Fidelity: Addresses form, fit, and function. A high-fidelity laboratory environment would involve testing with equipment that can simulate and validate all system specifications within a laboratory setting. Simulated Operational Environment: Either (1) a real environment that can simulate all the operational requirements and specifications required of the final system or (2) a simulated environment that allows for testing of a virtual prototype. Used in either case to determine whether a developmental system meets the operational requirements and specifications of the final system. JI2 System Description: The following is a top-level description of the JI2 system. This description is not intended to be all inclusive, but should be used to answer this RFI: The development and delivery of a threat emitter system (as identified in the fourth paragraph of the "overview" section above) will be an unclassified, high-fidelity emitter system that shall emulate some or all of the signals of the SA-15B. The minimum signals to represent are the SA-15B target acquisition and tracking radar signals, but desire full emulation. The emitter system is expected to have a minimum of two radars, one for acquisition and the second (phased array) for target tracking and missile guidance. Both will include the capability to initiate a track using skin tracking and emulate the SA-15B system operation. The target tracking radar will be capable of tracking multiple targets simultaneously. The acquisition radar will operate while the system is on the move or at a fixed location. The target tracking radar will operate while the system is not-moving, or with a minimum delay when the system transitions from a moving to a non-moving condition. The threat emitter must be designed to operate in a military ground mobile environment. The total threat emitter weight will be less than 10K pounds (5K pounds is an Objective) and transportable on a single commercially available vehicle. It is recommended the system be attached to skid pallet(s) and must not permanently attached to the vehicle for ease of removal to meet airlift transportability requirements. The system will be operable on commercial power and with a generator. The generator will be transported with the system during mobile deployment and operation of the system. Inclusion of the generator weight within the 10K pound total weight limit is desired. Environmental testing for shock, vibration, thermal (Operational between-40 degrees Fahrenheit to +125 degrees Fahrenheit) will be used to verify environmental compliance. The system must be helicopter transportable without dismantling. The threat emitter shall be capable of being deployed for training use in forward operating locations and deployed at improved (e.g. graded roads and concrete pads) and unimproved (e.g. no roads, no pad - literally anywhere on a range) sites. The threat emitter shall have the capability to receive, display, measure and store target track related data and provide feedback in ADDS/ICADS/TENA format for Aircrew Debriefing. The threat emitter shall support ACMI inputs from the range for initial pointing. The displays for the system will be accomplished using a single computer that is operated by a single operator, and will be remotely locatable from the rest of the emitter system hardware using either GFP radio or Ethernet (specific system architecture is currently under development and more specifics will be supplied with formal System Specifiction. The threat emitter shall be designed as a modular system that will require no specialized off-board calibration equipment. The modularity will also facilitate minor repairs within 20 minutes to four hours, and complex repairs within two to eight hours. The Mean Time Between Failure of the total system shall be no less than 500 hours, with the objective of 1000 hours or greater. The system shall be designed for a system Up-Time Ratio of 8 hours per day (Threshold) or 16 hours per day (Objective), 5 days per week, and 48 weeks per year for the 20 year life of the system. The threat emitter shall be designed to meet 90 to 100 percent availability of the entire threat emitter during the operational period of the system. Contact Information: Please respond to: Department of the Air Force, Air Force Materiel Command, OO-ALC/84 CBSG/PKR; Attn: M. Scott Arbon; 6039 Wardleigh Road, Bldg. 1206; Hill AFB; UT 84056-5838 (or e-mail: Michael.arbon@hill.af.mil). Phone number: (801) 586-2246. This is not an RFP or an Invitation for Bid, nor is it to be construed as a commitment by the Government. The Government does not intend to make an award on the basis of this Sources Sought Synopsis/Request for Information or otherwise pay for the information solicited herein. Copies of the submitted information will be reproduced and reviewed, and may be used to develop an RFP for development of the threat emitter. Point of Contact: Scott Arbon, Contract Negotiator; see phone number and additional details under the "Please respond to:" section above.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=717fcf83315117f0370c334ad85a0046&tab=core&_cview=1)
- Record
- SN01761431-W 20090306/090304215801-42427ef74bfd49d2186fa05ca2dc602b (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |