Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF APRIL 23, 2005 FBO #1244
SOLICITATION NOTICE

R -- Engineering and Technical Support for the Electronic Proving Ground (EPG), Fort Huachuca, Arizona

Notice Date
4/21/2005
 
Notice Type
Solicitation Notice
 
NAICS
541330 — Engineering Services
 
Contracting Office
ACA, White Sands Missile Range, Directorate of Contracting, Bldg 143, 2nd Floor, Crozier Street, White Sands Missile Range, NM 88002-5201
 
ZIP Code
88002-5201
 
Solicitation Number
W9124Q-05-R-EPGCDP
 
Response Due
4/25/2005
 
Archive Date
6/24/2005
 
Small Business Set-Aside
Total Small Business
 
Description
This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. The Electronic Proving Ground, Fort Huachuca, Arizona is soliciting proposals for the following requirement (No Substitutes): STATEMENT OF WORK FOR ENGINEERING and TECHNICAL SUPPORT OF TH E C3 DRIVER SIMULATION AND SCENARIO SUPPORT. 1. SCOPE. This Statement of Work (SOW) describes the engineering and technical support to be provided by the Contractor to the U.S. Army Electronic Proving Ground (USAEPG), Test Technology Division (TTD), For t Huachuca, AZ, for the development and support for the C3 Driver Simulation and Scenario capabilities. 2. TASK REQUIREMENT. C3 Driver is an ongoing program supporting the Army Battle Command System (ABCS), and follow-on C4I system, developmental, inter operability, and operational testing with system-of-system version deliveries. Version 1.0 was completed in June 2002 and delivered to all ABCS developers and the Central Test Support Facility (CTSF), Ft. Hood, TX. Version 1.0 enhancements and Version 2. 0 development began immediately following the initial delivery. Version 2.0 will include the development of operational mission threads and the development of divisional and brigade level scenarios gamed and documented using existing TRAC tolls and simula tions and subsequently transferred into the onboard C3 Driver simulation tool: Command and Control Low Overhead Driver (C2 LOD). Version 2.0 goals include the enhancement of the on-board simulation (C2 LOD) by improving its flexibility and functionality i n the following areas: a) running and tracking automated mission threads using simulation vignettes; b) running a full scenario simulation using the scripted TRAC scenarios; c) providing the capability for dynamic interaction with real-world ABCS boxes (i. e., accepting simulation inputs/commands from such boxes); and d) preparing for follow-on Version 2.0 enhancements as identified by the C3 Driver customers. Additionally, the contractor will be required to support C3 Driver engineering and design work. 3 . METHODOLOGY. The contractor will use the task-based methodology described below to accomplish this statement of work. 3.1Mission thread development. Accomplishment of these tasks may require travel to Fort Hood, TX; Fort Monmouth, NJ; and Fort Leaven worth, KS for development, implementation, and review of threads. 3.1.1 The contractor will implement database and simulation enhancements supporting ABCS 6.4 and Software Blocking mission threads within Flexible Analysis and Mission Effectiveness System ( FLAMES)/C2 LOD as appropriate. The contractor will decode the mission threads and messages with appropriate cognitive behaviors. 3.1.2 The contractor will implement existing and additionally developed mission threads for ABCS 6.4 and Software Blocking ( SWB) for use in the testing of such systems-of-systems at developer laboratories, the CTSF, and during other C3 Driver support test and training events (e.g., 4th Infantry Division Warfigher). The contractor will become familiar with the formats, required data, and issues involved in the development of such threads. Thread formats include (but may not be restricted to) MS Excel/Access databases and MS PowerPoint slides. The mission threads will be provided by TRAC. 3.1.3 The contractor will support an d participate in ABCS 6.4 and SWB thread meetings. This includes C3 Driver thread, design, and engineering meetings/conferences as appropriate. Required support under this paragraph includes briefing current status and schedule, recording pertinent meeti ng information and providing a brief summary, co-developing outbriefs, and similar tasks. 3.1.4 The contractor will assist in the development of a scripted bri efing describing thread development. Required support under this paragraph includes providing scripted briefing material describing the C2LOD/FLAMES mission thread implementation process, reviewing the final briefing, and similar tasks. 3.2Scenario devel opment. Accomplishment of these tasks may require travel to Fort Leavenworth, KS; White Sands Missile Range, NM; and Fort Hood, TX for research, transfer, and validation review. 3.2.1 The contractor will implement the C3 Driver Version 2.0 brigade-level operational scenario within the FLAMES database and C2 LOD simulation. These specifically include: one South-West Asia (SWA) unit-of-employment (UEx)/divisional level scenario and one or two North-East Asia (NEA) unit-of-action (UA)/brigade level scenario (s). TRAC analysts will provide appropriate scenario documentation and assistance. 3.2.2 The contractor will assist the C3 Driver TRAC analysts to ensure the concept of operation, the forces, and the equipment implemented in the dynamic simulation are c onsistent with the operational scenario. The contractor will work closely with the TRAC analysts to understand the flow of battle and events across the various battlefield functional areas (i.e., maneuver, fires, combat service support, air defense, etc.) . 3.2.3 The contractor will improve the communications and situational awareness networks associated with the entities represented in the scenario. Required support under this paragraph includes incorporating TRADOC-developed role behaviors as used in th e Common Message Generator (CMG), implementing simulation techniques to improve C2LOD/FLAMES representations, incorporating existing United States Air Force (USAF) developed air defense representations, and similar tasks. 3.2.4 The contractor will improv e the interface with other C3 Driver applications in order to satisfy C3 Driver system-of-system requirements. 3.2.5 The contractor will develop scenario generation enhancements. 3.2.6 The contractor will support, as appropriate, TRAC analysts in the pr eparation of written dynamic scenario documentation that describes the events and decisions that occurred during the brigade-level scenario. Required support under this paragraph includes assisting in reviewing the scenario representation in C2LOD/FLAMES, providing simulation outputs, reviewing draft and final briefings, and similar tasks. 3.2.7 The contractor will support scenario and simulation development meetings. These include TRAC meetings as well as C3 Driver engineering and design meetings. Req uired support under this paragraph includes briefing achievements and current status and schedule, recording pertinent meeting information and providing a brief summary, co-developing outbriefs, and similar tasks. 3.3 Dynamic, interactive capability deve lopment. This task may require travel to Fort Hood, TX; Fort Huachuca, AZ; and Fort Leavenworth, KS. 3.3.1 The contractor will implement the capability for (real-time) interaction between real-world operators on C4I boxes (to include ABCS) and simulated entities within the C3 Driver system-of-systems, specifically including the C3 Driver on-board simulation (C2 LOD). This capability will include a number of messages and commands that allow the simulation and active soldiers/players to interact. The mes sages and commands will, at a minimum, allow interactions in the following areas: fire support, maneuver, air defense, and intelligence, surveillance, and reconnaissance (ISR). 3.3.2 The contractor will assist in the preparation of written documentation o n this interactive capability. Required support under this paragraph includes the documentation of techniques to accomplish this interaction, the development of a scripted briefing describing the C2LOD/FLAMES aspects of the interaction, reviewing the fin al proposal documentation, and similar tasks. 3.4 Preparation for C3 Driver Version 2.0 follow-on efforts. This task may require travel to Fort Hood, TX; Fort Huachuca, AZ; and Fort Leavenworth, KS. 3.4.1 The contractor will assist in the TRAC assessment of the capability to represent EW and IW aspects (jamming, intercept, deceptive communications, hacking, etc.) in the C3 Driver simulations (i.e., C2 LOD and AWARS). Required support under this paragraph includes development of documentation describing the C2LOD/FLAMES capability in EW/IW, reviewing TRAC-developed final documentation, and similar tasks. 3.4.2 The contractor will prepare plans for the further enhancement of the C3 Driver on-board simulation and databases to incorporate additional functionality for mission threads and additional scenarios; the latter to include the incorporation of Electronic Warfare (EW) aspects. 3.4.3 The contractor will im plement critical design changes in the C3 Driver on-board simulation (C2 LOD) as determined by the C3 Driver customers, the C3 Driver Study Director, and the TRAC Study Director. 3.5 Additional C3 Driver development and design efforts. This task may req uire travel to Fort Hood, TX; Fort Huachuca, AZ; Annapolis, MD; and Fort Leavenworth, KS. 3.5.1 The contractor will be required to support C3 Driver engineering and design tasks and meetings. Required support under this paragraph includes briefing achiev ements and current status and schedule, recording pertinent meeting information and providing a brief summary, co-developing and presenting outbriefs, and similar tasks. 3.6 Provide documentation as appropriate. The contractor will provide to the C3 Dri ver Study Director and the TRAC Study Director meeting/conference reports within 3 days of such events and other documentation as required by the above points of contact (POCs). 3.7 All mission thread and scenario products prepared by the contractor will be the property of ATEC. 4. GOVERNMENT-FURNISHED SUPPORT. 4.1 Data and documents required from the Government to support this Task Order will be furnished through EPG by TRAC-FLVN, Joint and Combined Operations Directorate or by ATEC. 4.2 Through EPG TRAC-FLVN will provide mission threads, scenario data, and additional documentation as required to support tasks 3.1, 3.2, 3.3, and 3.4 above. 4.3 Access to the Secure Internet Protocol Routing Network (SIPRNET). Although typical work will be conducted at the unclassified level, this task order requires the contractor to conduct development up to and including the SECRET level and to communicate with and pass data between other government agencies via the SIPRNET. 5. PERSONNEL. The contractor must me et the requirement for clearance for access to classified information up to and including SECRET before the task begins. 6. WORKSPACE. All work will be performed primarily in a secure facility and workspace provided by the contractor using contractor-ow ned equipment. Secondarily, the work will be conducted in the secure facility and workspace provided by TRAC at Fort Leavenworth, or in designated facilities at the CTSF, Fort Hood, Texas. 7. PROGRESS REPORTS. The contractor will teleconference informa lly each week with the C3 Driver Project Director and other C3 Driver personnel. The schedule and content for these contacts will be determined mutually between the contractor and the C3 Driver Project Director. Quarterly In-Progress Reviews (IPRs) will be conducted. The contractor will be fully accessible to government personnel during normal working hours. 8. DELIVERY SCHEDULE. 8.1 PERIOD OF PERFORMANCE. The period of performance for this delivery order is 2 May 2005 through 30 September 2005. 8.2 SCHEDULE OF REPORTS AND DELIVERABLES. Status reports are due the last working day of the month in July and October. Specific deliverables are as specified in the methodology and tasks described above; these deliverables are to be provided to the C3 Dri ver Project Director in coordination with the C3 Driver system delivery schedule. 8.3 ASSUMPTIONS. The following assumptions will be used: 8.3.1 Deliverabl es will be assessed based upon specific requirements identified within each task. 8.3.2 EPG and C3 Driver project standards, security procedures, methods, and tools will be followed and/or used. 8.3.3 Any concerns over deliverables will be addressed t o the Ternion Study Lead. 9. OPERATIONS AND COMMUNICATIONS SECURITY. Contractor personnel will comply with the following Operations and Communications Security procedures under this SOW: 9.1 All draft deliverables under this SOW and working papers asso ciated with them will be shredded prior to recycling or disposal. Drafts in electronic media will be deleted or erased prior to reusing the diskette or space on a PC hard drive or shared server space. Final versions of products under this SOW will be del ivered to the government as specified elsewhere. 9.2 Apply -For Official Use Only- cover sheets to all draft and final deliverables under this SOW. 9.3 Contractor personnel may disclose to non-DoD personnel, other than contractor personnel executing this same SOW, on ly the general nature of their work under this SOW (i.e. I work for ____ Corp providing support for Army officer personnel management.) 9.4 Contractor personnel will not transmit any sensitive information over unclassified information networks. Contracto r personnel may consult with the COR if they are uncertain whether particular information is sensitive. 9.5 Government furnished telecommunication and electronic communication systems and equipment, specifically including electronic mail systems, are for official use only in furtherance of the SOW. 9.6 Contractor personnel will limit Internet access to the minimum time necessary to accomplish the official inquiry or research in furtherance of the SOW. 9.7 Contractor personnel will respect all electronic communication advisories, virus warnings, and use restrictions on government-furnished telecommunications and electronic communications systems and equipment and give access to government automation security and maintenance personnel upon request. 9.8 Con tractor personnel shall review the provisions of AR 25-2, Information Assurance, prior to using government-furnished telecommunications and electronic communications systems and equipment. The contractor shall provide evidence of this review to the COR fo r each member of the contractor staff working on this SOW. 9.9 Contractor personnel having access to classified information will have the appropriate security clearance and shall handle classified information consistent with Army information security standards as instructed by the COR. FOB Destination (Fort Huachuca, Arizona 85613). Pay ment will be made by Government Credit Card under Net 30 Terms. Offers are due no later than 1600 hours, Monday, 25 April 2005 and shall be submitted electronically at virginia.miller@epg.army.mil. EVALUATION CRITERIA / PROCEDURES: Offers will be evaluate d based on the following best value criteria in descending order of importance: Meeting the Requirement, Proposed Delivery Schedule, Past Performance and Price. For additional information, contact Virginia J. Miller, Contracting Officer, at (520) 538-39 78 or virginia.miller@epg.army.mil. The Synopsis/ solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2001-22 and 2001-23. This is a Small Business Set Aside. The following FAR provisio ns apply to this acquisition: 52.212-1, Instruction to Offerors Commercial items, and 52.212-2, Evaluation of Commercial Items, applies to theacquisition. Offerors shall include a completed copy of FAR provision 52.212-3, Offeror Representations and C ertifications Commercial Items, and furnish Offeror's Federal Tax Identification Number, Cage Code, Central Contractor Registration Number, DUNS Number and applicable FSC Codes with this offer. FAR Clauses 52.212-4, Contract Terms and Conditions Commercia l Items and 52.212-5, Contract Terms and Conditions Requi red Implementing Statutes or Executive Orders Commercial Items apply to this acquisition. FAR 52.219-8, Utilization of Small Business Concerns. The government reserves the right to select for award, all, some, or none of the proposals received in respons e to this announcement.
 
Place of Performance
Address: ACA, Southern Region, Electronic Proving Ground (EPG) Banister Hall, SFCA-SR-WS, 2000 Arizona Street Fort Huachuca AZ
Zip Code: 85613-7063
Country: US
 
Record
SN00793527-W 20050423/050421212017 (fbodaily.com)
 
Source
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.