SPECIAL NOTICE
69 -- Request for Information (RFI) for Army Low Overhead Training Toolkit (ALOTT)
- Notice Date
- 4/12/2012
- Notice Type
- Special Notice
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- PEO STRI Acquisition Center, 12350 Research Parkway, Orlando, FL 32826-3276
- ZIP Code
- 32826-3276
- Solicitation Number
- W900KK-12-ALOTT
- Archive Date
- 7/11/2012
- Point of Contact
- MILTON L WASHINGTON, 407 381-8854
- E-Mail Address
-
PEO STRI Acquisition Center
(milton.washington@us.army.mil)
- Small Business Set-Aside
- N/A
- Description
- The U.S. Army Program Executive Office for Simulation, Training & Instrumentation (PEO STRI) is contemplating a new small business, single award Indefinite Delivery/Indefinite Quantity (ID/IQ) Contract for the Army Low Overhead Training Toolkit (ALOTT) to support 'home station' training. The period of performance is anticipated to be one year plus four, one year options. The bulk of this planned contract will be for software development efforts which will Include Post Deployment Software Support (PDSS). This Request for Information (RFI) solicits industry's feedback on capabilities currently available to meet the attached ALOTT requirement. The North American Industry Classification System (NAICS) Class Code is 541511. Intent of this RFI: It is the intent of this RFI to accomplish two things: 1) Request capability statements/information from potential offerors to be utilized by PEO STRI as support in our continuous market research toward supporting upcoming ALOTT requirements. Capability statements will not be utilized for any purpose other than for market research only. 2) Potentially invite offerors that respond with capability statements by the due date as specified in this RFI in for one-on-one sessions to assist us in determining the proper acquisition strategy, type of contract and to achieve our overall objectives under the ALOTT program. One-on-one sessions may also include access to early proof of concept software. PROGRAM BACKROUND: As documented in the subparagraph 6.b.(14) of the Joint Land Component Constructive Training Capability JLCCTC Capabilities Production Document approved in August 2006, The United States Army requires a low overhead Mission Command training simulation capability to bridge the training simulations gap between large scale JLCCTC supported exercises and non-simulation supported unit training cycles. The User community increasingly demands training aids and tools that are easy and 'cheap' to prepare, use, and recover. Large complex simulation architectures as currently provided by the JLCCTC are too resource-intensive and inflexible. Especially for the enabling training in basic and lower-intermediate levels of Mission Command tasks as practiced under the crawl-walk-run training approach, for collective training at echelons below brigade or at any echelon when the Training Audience is relatively small or focused on a limited range of training tasks, and for institutional training and education. Implementation of the Army's planned Regional Simulation Center concept requires that a low cost/low overhead solution to be fielded, with Users properly trained in its use, prior to the scheduled consolidation, to provide MCTCs, units, and schools/Centers of Excellence the capability to support locally-executed collective Mission Command training and education. The ALOTT program was originally conceived as the Low Overhead Simulation/Stimulation Capability (LOSSC) and use cases were developed to communicate the functional capabilities and training objectives required to support low-overhead training. Reference the LOSSC Use Case attachments for more information about the original objectives and requirements. These use cases provided the basis for development of the program's technical requirements, which are defined in the separate documents attached. These use cases and requirements, for example, define objective low overhead metrics and Mission Command systems with which the ALOTT applications must interface. The Initial proof of concept software technology developed early to support the attached Use Cases may be obtained during the one-on-one discussions (a power point describing the design of the product is attached). DISCUSSION: PEO STRI is contemplating the award of a small business, single award Indefinite Delivery/Indefinite Quantity (ID/IQ) Contract for the Army Low Overhead Training Toolkit (ALOTT) to support the Warfighter. The contract's primary focus will be on the development of a low overhead, collective mission command training exercise toolkit. The objective requirements must be met within a one year build cycle culminating in a validation test event for army acceptance testing. The following tasks and services are anticipated to be the major part of the contract's scope: Software Modification and Enhancement Full Spectrum Battlefield Representations/Outcomes at the "crawl" and "walk" skill levels AAR tools to support individual/small group self-assessment Stimulation/Simulation of Mission Command systems New software development as additional Use Cases/requirements are developed in support of ALOTT External Interfaces LVC-IA, CCTT, CFFT, HITS, AVCATT, VBS2, etc. Reuse or rapid rebuild (less than 4 hours) of exercise scenarios used in other constructive training applications (such as OneSAF and WARSIM) Training and Proficiency Development Rapid and repetitive training on how to operate ALOTT programs Interactive Multimedia Instruction Development of tutorials to support individual/small group self-instruction Software support for database development, troubleshooting, etc. Commonality in software, data, and processes across ALOTT products; for example, "Common adapter" providing interface to stimulating Mission Command and Network Systems (MCNS) Terrain/Map data Process for developing and coordinating exercise scenarios (e.g., task organization information) User-defined event queuing and injection into the simulation Common databases across the ALOTT applications Ability to import scenarios from other applications for use in ALOTT (JCATS, WARSIM, LVC-IA, etc.) Fielding Providing Training to the Sustainment Fielding Team Post Deployment Software Support Authority to Operate Ability to obtain ATO/CON Have the necessary security and DAICAP cert requirements satisfied. Running under HBSS REQUEST FOR INFORMATION: Are you an awardee under STOC II? How does your solution address training and education in the Military Decision Making Process (MDMP)? What capabilities exist regarding a "common" Mission Command (MC) adapter (a two way interface between ALOTT and MC systems) that can be leveraged to support the ALOTT requirements? Are there cost effective and efficient alternative solutions to a common adapter (code reuse) that would support the objective of stimulating/simulating the various Mission Command systems? Considering the requirement to stimulate multiple MC systems, what capabilities (if any) exist and can be leveraged to minimize sustainment costs for maintaining linkages to evolving MC systems? (I.e. how would you minimize the cost of updating ALOTT every time a new MC system version or emerging MC system is released?) Can your software solution(s) meet the threshold requirements disclosed in the attached use cases? How does your software application(s) model entity behavior and effects (e.g., simulation engine, game engine, other)? Is your software solution(s) GOTS? If not, what is the licensing structure? This includes ownership and distribution rights for software, libraries, data files, and executables. How does your solution support common terrain representation and generation while eliminating licensing costs and minimizing redistribution restrictions. Given hardware constraints, security concerns and the desire for no cost licensing for ALOTT, how would you solve mapping and terrain requirements while keeping low sustainment costs in mind? If your solution involves multiple software applications, what standards/approach will you use to achieve a common look-and-feel for all tools in the ALOTT toolkit (common look-and-feel addresses, but not necessarily limited to, setup, initialization, menus, exercise control functions, GUIs, reports)? Given the Current ALOTT short train-up time requirements: What innovative technologies can be leveraged to improve (reduce) the train-up time for users of the ALOTT? What innovative technologies can reduce operator workload (e.g., wizards and automation to rapidly create a large number of events, intended for injection during runtime)? How will you use authoritative data from Project Director Tactical Network Initialization (PD TNI) to initialize the task organization and mission command data? What capabilities and solutions exist that, during runtime, can associate training audience tasking/decisions to consequences/outcomes, for the purpose of AAR and learning? Given the requirements stated in the use cases (and the footprint restrictions), what capabilities exist and could be leveraged to allow a feed to BCS3 and AFATDS using your solution? What capabilities exist for hosting ALOTT applications in a cloud environment, providing hosting services on a backend server that support lightweight (thin) web enabled clients? Would your solution provide flexibility to migrate easily to a cloud environment if required at a future date? Describe your program management and systems engineering approach to managing multiple concurrent ALOTT baselines. Address the following key process areas: Project planning and management, subcontractor management, quality assurance, risk management, software configuration management, requirements management, software development, testing, verification, validation, sustainment, performance assessment and improvement, information assurance, Highlight areas where your systems engineering and management processes provide "value added" by improving effectiveness, efficiency, and quality for ALOTT's multiple, independent, concurrent product development and fielding efforts. Provide related experience examples where the proposed approach was effectively employed on other simulation programs. If you are planning to team this effort, how would you plan to manage workload distribution to your subcontractors'? Specifically, what portions/functions would you plan to sub-contract? Please provide examples of where you have teamed and sub-contracted efforts that were successful. RESPONSES REQUIRED: Responses to this RFI should be no more than 17 pages total (including cover page). Please include point of contact (name, title, address, phone/fax, email) and Product/Project Name Brief product/project description that includes the following: System design (a graphic is a plus), technical requirements, Operational functions or missions supported, any supporting information and how the system is currently being used and by whom (include references). Please provide your insight and the answers to the questions/comments above as well as any relevant feedback to the following individuals, no later than 4 May 2012: Procuring Contracting Officer: Milton Washington, email: milton.washington@us.army.mil, 407-381-8854. All correspondence on this matter should be directed to the Procuring Contracting Officer (PCO), Mr. Milt Washington 407-381-8854, or email milton.washington@us.army.mil. Technical questions can be directed to Mr. Stephen Bushway, Project Director. DISCLAIMER: This notice does not constitute an invitation for bids or a Request for Proposal (RFP) and is not a commitment by the U.S. Government to procure subject products. No solicitation document exists at this time. The submission of this information is for PLANNING PURPOSES ONLY. CONTRACTING OFFICE ADDRESS: PEO STRI Acquisition Center, 12350 Research Parkway, Orlando, FL 32826-3276 POINTS OF CONTACT(S): Milt Washington, PCO, 407-381-8854; Milton.washington@us.army.mil Roy Whitehead, APM JLCCTC, 407-484-5434; Roy.j.whitehead@us.army.mil Stephen Bushway, Project Director for ALOTT, 407-384-5545 Stephen.bushway@us.army.mil
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/USA/STRICOM/W900KK/W900KK-12-ALOTT/listing.html)
- Record
- SN02720407-W 20120414/120412235051-dd047a8579b024f2af47022c0a7a698f (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 |