Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JANUARY 16, 2005 FBO #1147
MODIFICATION

A -- U.S. Army Simulation, Training and Instrumentation Command and Army Research Institute Broad Agency Announcement

Notice Date
1/14/2005
 
Notice Type
Modification
 
NAICS
541330 — Engineering Services
 
Contracting Office
Department of the Navy, Naval Air Systems Command, Naval Air Warfare Center Training Systems Division, 12350 Research Parkway Code 253, Orlando, FL, 32826-3224
 
ZIP Code
32826-3224
 
Solicitation Number
N61339-01-R-0023
 
Response Due
1/28/2005
 
Archive Date
2/12/2005
 
Point of Contact
Vanessa Dobson, Contract Specialist, Phone 407-208-4348, Fax 407-380-4164,
 
E-Mail Address
vanessa_dobson@stricom.army.mil
 
Description
The U.S. Army Research, Development and Engineering Command Simulation and Training Technology Center (formerly STRICOM) publicized Broad Agency Announcement (BAA) N61339-01-R-0023 in the CBD on 01 March 2001. This notice calls for White Paper Submissions in reference to the research interest entitled, 7.0 ?Additional Research Topics, LVC-IA Joint Seamless Interoperable Training Environment. The Technical Point of Contact for this specific white paper submission: Mr. Mark Jozwiak, PEO STRI, PM FF (S), (407) 384-3729, mark.jozwiak@us.army.mil (email contact preferred). The Contractual Point of Contact: Ms. Gloria Bailey, NAVAIR Orlando TSD, Code 25343. PROGRAM OBJECTIVES: The objective of the Live, Virtual, Constructive Integrated Architecture (LVC-IA) program is to create a Joint, Integrated LVC environment & capability that allows Army forces to routinely train/operate in the Contemporary Operating Environment (COE) / Joint Operating Environment (JOE) as part of a Joint Task Force (JTF). The objective LVC-IA is to: 1. Implement a standardized set of protocols, specifications, and standards that permit interoperability and integration among Army & Joint LVC components. 2. Provide an integrated LVC environment that ensures compatibility and interoperability for all TADSS and fully embeds into Future Force Battle Command System, while linking to and stimulating Joint Command and Control (JC2) systems. 3. Provide ?Plug and Train? capability to support operations, mission planning-rehearsal, on demand, anytime, and anywhere, while training in a Joint context. 4. Permits interoperability and integration among- a. Joint Family of Simulations (JFOM)(JNTC Efforts). b. Common Training Instrumentation Architecture (CTIA). c. Synthetic Environment (SE) Core. d. Army Constructive Training Federation (ACTF). e. Test and Training Enabling Architecture (TENA). f. Other Potential LVC components (FCS FoS, WIN-T?). g. Embeds into and stimulates JC2. PROGRAM SCOPE: The required research is for the development of the LVC-IA Technology Development Strategy (TDS) and technical direction for the LVC-IA base program Analysis of Alternatives (AoA). The acquisition framework for the base LVC-IA program incorporates a Technology Development Phase focused on the development, maturation, and evaluation of the technologies needed for the capability under consideration. This phase of activities concentrate on maturing those technologies (consistent with recommended Technology Readiness Levels) and demonstrating readiness to proceed with program initiation. This document is developed during the Concept Refinement phase for the base LVC-IA program to support the program?s Milestone A decision. The TDS outlines the plan for conducting the Technology Development phase, to include: a.) Rationale for adopting an evolutionary or single-step-to-full-capability strategy; description of how the program will be divided into technology spirals and development increments tied to the AoA. b.) Cost, schedule and performance goals for the total R&D program; and specific goals and test plans for the first technology spiral synchronized with the AoA finding. The TDS is done concurrently and simultaneously with the LVC-IA base program AoA. This AoA is an analysis of the operational effectiveness and estimated life cycle costs for alternative materiel systems required to meet or eliminate identified gaps and shortfalls in the existing operational capabilities. During this TDS effort, in conjunction with AoA, you will provide the technical direction for the future LVC Integrated Architecture. Your technical recommendations will be required to assist TRADOC (TRAC WSMR & NSC) and the PEO with the AoA analysis and evaluation of a range of specific hardware and software alternatives identified in the Initial Capabilities Document (ICD) and to focus on how to provide the needed capabilities while reducing cost and risk. Additionally, the AoA provides information and data to document rationale for adopting an evolutionary or single-step strategy with cost, schedule and performance goals for the total R&D program and specific goals and test plans for the first technology spiral, which will assist in the development of the recommended technology development strategy. The AoA and TDS should provide independent assessment of the final results and document these results in the following key AoA assessment categories: 1. Important Aspects of the Study Plan Followed. a. Deviations from the planned effectiveness and cost analyses are understood and documented to conform to AoA study plan standards. b. Address how oversight guidance and all appropriate issues were addressed. c. Study Plan has been updated over the course of the study. d. Purpose and tasking were appropriate for the study. 2. Scenarios Appropriate and Approved. a. Address training scenario validation and approval. b. Scenarios used were appropriate, providing reasonable results. c. Army and Joint architectures have been considered for impact. 3. Models, Simulations and Accreditation Reasonable. a. Accreditation report covering models and data certification signed. b. Models, simulation and data worked appropriately. c. Identify models and simulation shortfall; include workarounds. 4. Final Operational Concepts Are Reasonable. a. Have the user sanction employment concepts (basing, deployment, doctrine, and other limitations, etc.) been identified? b. Verify the viability of logistics concepts (maintenance, supply, personnel, etc.). c. Account for interdependencies with existing operational live, virtual and constructive systems and key support systems (navigation, communications, weather, etc.). 5. Effectiveness Methodology Successfully Executed. a. Determine the military worth of alternatives to the user. b. Discuss effectiveness assumptions. c. Follow a logical and reasonable analysis approach. d. Evaluate a range of independent alternatives for the final analysis. f. Give a convincing rationale for early elimination of alternatives. 6. Cost Analysis Methodology Successfully Executed. a. Discuss costing assumptions. b. Identify sources for cost inputs. c. Summarize the cost review process. d. Present cost results by alternative. e. Discuss CAIV implications. 7. Presentation of Final Results Support the AoA Findings. a. Discuss the ability of the cost-effectiveness comparison methodology to differentiate among alternatives. b. Outline decision criteria and its impact in making the final selection. c. Present cost-effectiveness comparison results at the MOE level and at higher levels of aggregation if appropriate. d. Present clear and reasonable results. e. Present and interpret sensitivity analyses addressing the threats, alternative performance, etc. f. Identify and interpret methodology shortcomings relative to each alternative. g. All AoA conclusions are supported with briefed results? TECHNOLOGY DEVELOPMENT STRATEGTY: The TDS at a minimum contains the following items: a. Planned acquisition approach, including a summary of the considerations and rationale supporting the chosen approach.? To Spiral develop the Army?s LVC Integrating Architecture by leveraging the existing Army and DoD programs into a joint, seamless, interoperable Training Environment that approximates the Warfighter?s Operational Environment.? b. For the preferred, evolutionary acquisition approach, whether spiral or incremental, DoD Instruction 5000.2 requires the following details- I. A preliminary description of how the program will be divided into technology spirals and development increments; II. The limitation on the number of prototype units that may be produced and deployed during technology development; III. How prototype units will be supported; IV. Specific performance goals and exit criteria that must be met before exceeding the number of prototypes that may be produced under the research and development program. b. A discussion of the planned strategy to manage research and development. This discussion must include and briefly describe the overall cost, schedule, and performance goals for the total research and development program. To the extent practicable, the total research and development program should include all planned technology spirals or increments. c. A complete description of the first technology demonstration. The description must contain specific cost, schedule, and performance goals, including exit criteria, for the first technology spiral demonstration. d. A test plan. A description of how the first technology spiral demonstration will be evaluated to determine whether the goals and exit criteria for the Technology Development phase have been achieved. The test plan is focused on the evaluation of the technologies being matured during the Technology Development phase. This plan is distinct from the separately developed and approved Test and Evaluation Strategy discussed in detail in section 9.6.1 of the Defense Acquisition Guidebook. The Test and Evaluation Strategy takes a broader view and is the tool used to begin developing the entire program test and evaluation strategy, including the initial test and evaluation concepts for Technology Development, System Development and Demonstration, and beyond. WHITE PAPER SUBMISSIONS: Any responsible offeror capable of satisfying the needs identified in this announcement may submit a white paper. White paper submissions are encouraged as early as possible but must be received at PEO STRI no later than 1600 EDT on 28 JAN 05. No extensions will be granted. White papers must address requirements defined above and shall not exceed 10 pages in length. The white papers should address the knowledge, skills and experience of individuals performing the research; resumes are not to be submitted with the white paper. Only unclassified white papers will be accepted. The white papers shall contain a rough order of magnitude (ROM) for this effort. The white papers will be reviewed to determine that the proposed effort is within the scope and interest of this solicitation. Proposals will only be solicited from white papers deemed to best meet the program objectives. White papers will be evaluated by a technical review board using the following criteria listed in descending order of importance: (1) the overall scientific and/or technical merits of the proposal. (2) The potential contributions and/or transition of the effort to the Army simulation, training and instrumentation mission and the extent to which the research effort will contribute to high priority Army interests. (3) The skills, knowledge and experience of the proposed principal investigator, team leader, and other key personnel who are critical to the achievement of the proposal objectives. (4) The offeror's capabilities, related experience, facilities, techniques, or unique combination of these which are integral factors for achieving the proposal objectives. (5) The reasonableness and realism of proposed costs and fees, if any, and the availability of funds. Cost reasonableness and realism will be assessed, but this assessment is of a lower priority than the technical evaluation. To be eligible for award a white paper must be submitted. Preference will be given to Small Business offerors; further preference will be given to 8(a) Business offerors. Offerors will be notified whether or not their white paper was favorably received on or about 04 FEB 05. Favorable review of a white paper does not constitute selection of the proposed effort for contract award and will not establish a binding commitment for the Government to fund the effort in whole or part. Upon notification, the Government will issue a request for proposal letter to the qualified offerors, who best meet the program objectives. Contractors who receive a request for proposal should be aware that potential contract award(s) will contain NAVAIR clause 5252.209-9510, Organizational Conflicts of Interest (services)(sep 1999). This clause can be located at: http://www.peostri.army.mil/BAA/home.jsp. If proposals are solicited, proposals are due no later than 1600 EDT on 07 MAR 05. The requirements for proposal preparation and submission can be found at http://www.peostri.army.mil/BAA/home.jsp. This announcement is an expression of interest only and does not commit the government to reimburse any proposal preparation cost for responding. The cost of proposal preparation in response to this announcement are not considered an allowable expense to the normal bid and proposal indirect costs as specified in FAR 31.205-18. Any request for white paper or submission of a full proposal does not guarantee award. The Government reserves the right to cancel this requirement at any time and shall not be liable for any cost of proposal preparation or submission. Within the meaning of the Federal Acquisition Regulation (FAR) at 6.102 and 35.016, this announcement constitutes the Government's solicitation for this effort. There will be no other solicitation issued in regard to this requirement. Offerors should be alert for any BAA amendments that may be published. The white papers should be provided in hardcopy and electronic form. MAIL WHITE PAPERS TO: US Army PEO-STRI, Attn: Mr. Mark Jozwiak , PM FF (S), 12350 Research Parkway, Orlando, Fl 32826 no later than 1600 EDT on 28 JAN 2005.
 
Place of Performance
Address: 12350 Research Parkway, Orlando FL 32826.
Zip Code: 32826
Country: U.S.A
 
Record
SN00735420-W 20050116/050114212245 (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.