PR_1300514649_Fleet_Battle_School_SOW.pdf
PDF 82 KB Posted
- Attached to
- Fleet Battle School Software Development Federal contract opportunity
- Solicitation number
- N66604-15-Q-3177
About this file
Fleet Battle School Software Development Statement of Work.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| N66604-15-Q-3177_RFQ_Questions_ _Answers_as_of_09-11-15.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PR 1300514649
FLEET BATTLE SCHOOL SOFTWARE DEVELOPMENT
STATEMENT OF WORK
1.0 BACKGROUND
The Chief of Naval Operations’ (CNO) Rapid Innovation Cell (CRIC) has tasked Naval
Undersea Warfare Center (NUWC) to develop a high-tactical naval war game in support of naval education, training, and concept development. In FY14-15, NUWC designed a manual war game, and CRIC has directed NUWC to support the creation of a computer war game based on this manual game. In FY15, a contract was placed to produce an
“alpha-version” prototype (Increment 1) of the game for delivery in September 2015.
Subsequently, CRIC has requested NUWC support for production of a final, distribution version (Increment 2) based on fleet inputs and feedback, to include scenarios which can be used to teach the game.
2.0 SCOPE
In FY14, Phase I of Fleet Battle School delivered a tabletop prototype war game for small-group war gaming at the high-tactical/low-operational level. Phase II in FY15/16 will develop a networked, cross-platform computer war game for Fleet Battle School.
Phase II is being executed in two increments, with the first increment delivering a user interface, autonomous adjudication and umpiring, and the second increment providing advanced rules, testing and scenarios to help users learn the game. This statement of work
(SOW) covers the upgrade of this software to Fleet Battle School Increment 2 based on fleet feedback on the Increment 1 prototype, including incorporation of improvements, development of scenarios, and finalizing software into a stand-alone deliverable.
3.0 APPLICABLE DOCUMENTS
3.1 Fleet Battle School game design documentation
4.0 REQUIREMENTS
In accordance with applicable documents and using GFI, the contractor shall upgrade existing Fleet Battle School Increment 1 to add scenarios, incorporate inputs from fleet stakeholders, and finalize into a stand-alone deliverable products.
4.1 TASK 1 – UPGRADE OF FLEET BATTLE SCHOOL SOFTWARE.
In accordance with Applicable Documentation and using Government Furnished
Information, the contractor shall upgrade Fleet Battle School software to include:
4.1.1 Create a series of scenarios which will walk players through the mechanics of gameplay.
PR 1300514649
4.1.2 Incorporate changes to the Fleet Battle School wargame based on the results of play testing and review with stakeholders.
4.1.3 Develop and deliver fully functioning versions of the Fleet Battle School software for single and multi-player use on the Widows 7+, OSX 10.8+, iOS 6+ and Android 4+ platforms in accordance with A001.
4.2 DELIVERABLES
The delivered product shall be able to be distributed electronically, and shall be unlimited use for any U.S. Navy users. The product will be a compiled executable and able to be installed and operated without additional training provided to stakeholders. (All training on use would be incorporated within scenarios or included documentation.)
5.0 PROGRESS REPORTS
The contractor shall deliver monthly updates to NUWC Code 60A, reporting changes incorporated and the most recent version of the Fleet Battle School software, in accordance with A002.
6.0 GOVERNMENT FURNISHED INFORMATION (GFI)
The Government shall provide the contractor the following documents/information as
GFI:
Fleet Battle School game rules, fleet feedback, and testing results to include:
6.1 Bug reports
6.2 Improvement requests from the fleet
File details come from the government source that posted it. Updated .