6. SOF RAPTOR II SOW - DO 5 - Radio SIM - 02 Oct 08c.doc

Code 4.9.1.5

MODSOW

STATEMENT OF WORK

FOR

Special Operations Forces Requirements Analysis, Prototyping, Training, Operations and Rehearsal II (SOF RAPTOR II) Delivery Order 5 Tactical Radio Training Simulation Development 02 October 2008 Prepared by U.S. Army PEO Simulation, Training and Instrumentation (PEO STRI) 12350 Research Parkway

Orlando, FL 32826-3276 11.

SCOPE

11.1 Background

12.

APPLICABLE DOCUMENTS

12.1 Government documents

12.2 Non-Government documents

13.

REQUIREMENTS

13.1 General

13.1.1 Program Management

13.1.1.1 Technical and Management Work Planning

13.2 Common Requirements

13.2.1 System Design

13.2.2 Software Development

13.2.3 Systems Engineering

13.2.4 Minimum Software and Technical Data Rights

13.2.5 Conferences and Reviews

13.2.6 Parts Standardization

13.2.7 System Safety Tasks

13.2.8 System Test and Evaluation

13.2.9 Integrated Logistics Support Program

13.2.10 Configuration Management Program

13.2.11 Facility Requirements

13.2.12 Disposition of Hardware

13.2.13 Contractor Logistics Support Contractor Liaison

13.2.14 Information Assurance

13.3 Tactical Radio Training Simulation Development Detailed Requirements

13.3.1 Phase 1 - Functional Requirements Definition / Instructional Design

13.3.2 Phase 2 – ARC-231 Radio Simulation Software Development

Statement of Work

For

Special Operations Forces Requirements Analysis, Prototyping, Training, Operations and Rehearsal II (SOF RAPTOR II) Delivery Order 5 SOF Tactical Radio Training Simulation Development

1. SCOPE

This Statement of Work (SOW) defines the SOF Tactical Radio Training Simulation Development requirement for SOF RAPTOR II, Delivery Order 5: Tactical Radio Training Simulation Development. Project tasks include analysis, design, development, implementation, and testing.

Unless otherwise noted in this SOW, requirements for Delivery Order 5 are defined in the Basic SOF RAPTOR II SOW, PEO-STRI-08-W053. In case of a conflict between the requirements and documents cited herein and the Basic SOF RAPTOR II SOW, this Delivery Order Statement of Work will take precedence. With the exception of Paragraph 3.3, and its subparagraphs, paragraph numbering of this Delivery Order SOW mirrors the paragraph numbering of the Basic SOW.

1.1 Background

The expense of tactical radios as well as their high demand in the field limits the number that can be provided in formal training courses. Additionally, the more the radios are used for training, the more wear and tear they endure, leading to increased resources spent on repairs and reduced availability in the field. Accurate, timely secure communication is vital to the success of every SOF mission. Current training methodology using the tactical radios creates a bottleneck in formal training courses resulting in extended training days or in some cases excessive expense caused by actual platform light-off. Most training bottlenecks occur because the complexity of the radio setup procedures typically enables only one student to input required settings at a time. Moreover, the screen size on the radio is such that only one student can clearly see the display. Correctly setting up the radio and understanding all its modes and operations is essential to using it to its full extent. The development of a tactical communications simulation is required to ensure continued SOF combat readiness, maintain training pace, and meet required end strengths of skilled personnel.

2. APPLICABLE DOCUMENTS

The documents referenced below are in addition to those referenced in the Basic SOW.

2.1 Government documents

(Copies of the above document are available from PEO STRI.)

2.2 Non-Government documents

(Unless otherwise noted, copies of the above documents are available from PEO STRI.)

3. REQUIREMENTS

The SOW provides the top-level requirements for the systems engineering, design, development, integration, hardware, software, personnel, supervision, management, materials, services, equipment, facilities, testing, technical, logistics, clerical, and delivery of a complete training package for the SOF Tactical Radio Training Simulation Development.

3.1 General

The following General requirements are in addition to, and clarify the requirements identified in the Basic SOW.

3.1.1 Program Management

Conduct all Program Management activities as applicable and in accordance with the Basic SOW requirements.

3.1.1.1 Technical and Management Work Planning

Develop a Technical and Management Work Plan (TMWP) in accordance with the Basic SOW requirements. (DI-MGMT -81117)

3.1.1.3 Work Scheduling

The Contractor shall develop an Integrated Master Schedule (IMS) in accordance with CDRL (DI-MGMT -81650). The Contractor shall produce a description of work processes and timing of the work effort detailed in the TMWP. Establish a master schedule including metrics that provide accurate and timely performance tracking information throughout the life cycle of the program. The IMS shall be used as the primary tracking tool for technical and schedule status. All tasks outlined in the IMS shall be related to specific TMWP accomplishments. The IMS supports the TMWP and provides a schedule for all the tasks, events, significant accomplishments and accomplishment criteria described in the TMWP. The IMS shall also outline the detailed tasks and the corresponding calendar schedules (dates) necessary to show each significant accomplishment to be achieved. Those level of effort, or equivalent tasks, that are not critical to the successful execution of the program, may be limited or summarized at a higher level. Schedule relationships reflecting excessive lead or lag time should be avoided. If excessive lead or lag times cannot be avoided, they must be explained.

The IMS shall contain details of the reviews as well as a sufficient number of design reviews with defined entry and exit criteria to ensure design requirements and delivery schedules are being met. The design review entry/exit criteria for all design/review meetings shall include:

(Entry) Delivery and Government review (with comments for changes to be incorporated) of all CDRL items (or associated sections/volumes thereof for incremental design reviews) scheduled for submission at the associated design/review level.

(Entry) Closure of all previous action items related to the system(s) design.

(Entry) Submittal and acceptance of the agenda for each design review.

(Exit) Government certification (via e-mail/correspondence) of the associated design/review.

(Exit) Satisfactory discussion of the CDRL items that were part of the entry criteria.

(Exit) Satisfactory discussion of the schedule, if updated.

(Exit) Satisfactory discussion of the risk assessment/mitigation plans.

(Exit) Successful resolution and closure of all newly generated action items related to the system(s) design.

(Exit) Availability of presentation briefing materials, and submittal and Government acceptance of the design review minutes.

Design Reviews – preliminary and critical design reviews will be held at the contractor’s facilities and IAW with this SOW.

Preliminary Design Review – The basis for the preliminary design review will be the Front End Analysis (FEA).

Critical Design Review – The basis for the critical design review is the Instructional Media Development Plan (IMDP). The completion of the IMDP initiates the start of formal configuration management by the Contractor of the technical baseline. Any changes to that baseline can only be accomplished with the approval of the Government.

The Contractor shall also include any other logic needed to recreate the schedule from the tabular data (e.g., directed or fixed dates or other assumptions not readily apparent in the tabular format). Constraints (other than “as soon as possible”) and directed dates plus the rationale supporting the need for each constraint or directed date in the schedule shall be identified and explained. Any activity with a greater duration of 90 days, unless it is a level of effort task, should be divided into activities with smaller durations and shall be explained in a narrative.

3.1.5 Government Furnished Property (GFP) and Government Furnished Information (GFI) The Government will provide a sample of a tactical radio simulation (AN/148) as an example GUI (Graphical User Interface).

3.1.6 Government Purpose Rights

The Contractor shall provide the Government an Unlimited Rights License (See DFARS 252.227-7013/7014) in all deliverable technical data, computer software and computer software documentation. The Unlimited Rights License shall be irrevocable, fully paid up, perpetual and world-wide. For example, the Government will not pay royalties, recurring license fees, or run-time fees, use taxes, or any similar additional payments.

3.2 Common Requirements

The following Common Requirements shall be required of this Delivery Order, as noted below.

3.2.1 System Design

The Tactical Radio Training Simulation Development design encompasses two phases (as defined in 3.3): Functional Requirements Definition / Instructional Design and Radio Simulation Software Development. A TMWP shall be developed to document management and technical approach for the overall System Design.

3.2.2 Software Development

Software Development will be in accordance with the Basic SOW and additionally include the attributes as defined in Paragraph 3.3.2

3.2.3 Systems Engineering

Systems Engineering processes will be followed in accordance with the Basic SOW.

3.2.4 Minimum Software and Technical Data Rights

The Tactical Radio Training Simulation software shall have no runtime licenses associated with it. The intent of this requirement and associated unstated requirements is to produce a PC Training Simulation that is easily distributable. Minimum Software and Technical Data Rights are not applicable to this Delivery Order. All technical data and computer software, including but not limited to source files, 2D and 3D imagery, 3D models and wire-frames, video, audio, animations, design documentation, runtime licenses, other support documentation and instructional content, developed by the Contractor are contemplated to be developed with Government Funding and not Private funding. Therefore, the Contractor shall provide the Government an Unlimited Rights License to all such technical data and computer software. If the Contractor is involved in any future efforts with the Government, pursuant to the Government’s Unlimited Rights as provided for under this Contract, The Contractor warrants that the Government shall not be charged again for the technical data and computer software developed under this contract when provided to, or expected to be used by, or for the use by any Government agency, organization, or Command including, but not limited to any modifications, including derivative works, and any integrated products created through a non-degradable interface to the technical data or computer software.

3.2.5 Conferences and Reviews

Conferences and Reviews will be conducted as applicable and in accordance with the Basic SOW requirements.

3.2.6 Parts Standardization

Parts Standardization is not applicable to this Delivery Order.

3.2.7 System Safety Tasks

System Safety Tasks are not applicable to this Delivery Order.

3.2.8 System Test and Evaluation

System Test and Evaluation will be conducted as applicable and in accordance with the Basic SOW requirements. (DI-NDTI-80603)

3.2.9 Integrated Logistics Support Program

Integrated Logistics Support Program will be conducted as applicable and in accordance with the Basic SOW requirements.

3.2.10 Configuration Management Program

Configuration Management Program will be conducted as applicable and in accordance with the Basic SOW requirements.

3.2.11 Facility Requirements

Facility Requirements are not applicable to this Delivery Order.

3.2.12 Disposition of Hardware

Disposition of Hardware is not applicable to this Delivery Order.

3.2.13 Contractor Logistics Support Contractor Liaison

Contractor Logistics Support Contractor is not applicable to this Delivery Order.

3.2.14 Information Assurance

Information Assurance will be conducted as applicable and in accordance with the Basic SOW requirements. (DI-MISC-80711A )

3.3 Tactical Radio Training Simulation Development Detailed Requirements The Tactical Radio Training Simulation Development shall be conducted in two phases and will include Government participation.

3.3.1 Phase 1 - Functional Requirements Definition / Instructional Design Using the GFE (AN/148 radio simulation) as a representative example in terms of instructional design complexity, the Contractor shall develop an Instructional Media Design Package (IMDP) consisting of the design strategy and the technical specifications that support development of tutorials associated with defined training requirements. The Contractor shall provide a prototype lesson/tutorial as part of the IMDP. (DI-SESS-81520B) The design strategy includes but is not limited to:

a. Lesson/tutorial topic content

b. Script story boards including: audio/graphic production requirements, screen conventions, performance standards, timing, sequencing and branching requirements.

c. Flow charts including: level of student activity, remediation requirements, assessment (pre-test, post-test, self-check and remediation) strategy where appropriate as indicated in the FEA, including embedded questions at appropriate intervals.

3.3.2 Phase 2 – ARC-231 Radio Simulation Software Development Using the GFI (ARC-231 Technical Manual) the Contractor shall develop a Software Design Description (DI-IPSC 81435A) that includes these requirements:

a. Commonly Used Programming Language (C++, .Net, Java). The software shall be developed with a commonly used programming language: C++, .Net, Java. The intent of this requirement and associated unstated requirements is to produce a Computer Based Training (CBT) that allows for the ease of re-use, design changes, and interoperability post initial delivery.

b. Low Processor Usage. The software shall utilize a low percentage of the host machine’s processor. This value should be in the range of less than 10% of machine processor usage on a typical 1.8 GHz machine. The intent of this requirement and associated unstated requirements is to produce a CBT that is agile and can be placed on a machine running multiple simulation tasks and not hinder training.

c. Animated Radio Panel. The software shall give the user an animated graphical user interface that mimics the same motions of mechanical elements present on the radio of interest (knobs, switches, buttons, etc.). This animation shall be maintained in conjunction with the above stated requirement regarding low processor usage. The intent of this requirement and associated unstated requirements is to produce a CBT that offers training in the area of knobology and has the technical ability to offer the user an animated front-end interface to the simulation of the radio similar to the actual radio itself.

d. No Installation Procedure. The software shall not require install procedures except for the placing of a folder containing necessary files on a host machine. No registry manipulation shall occur. No third party runtime tools requiring licensing fees shall be placed on the host machine. The intent of this requirement and associated unstated requirements is to produce a CBT that yields as little hindrance as possible on the end user with regards to use of the CBT on their host machines which may be configured to not allow installation of software products.

e. Configuration. The software shall contain a configuration file in a common configuration file format, such as XML, that can be used to set basic runtime parameters. The intent of this requirement and associated unstated requirements is to produce a CBT that gives the user an ability to set a number of parameters that satisfies their specific training scenario.

f. Windows OS Compatible. The simulation software shall be compatible and developed to operate within a windows environment, specific target being Windows XP or higher, loaded with necessary networking equipment. Any specific elements, such as fonts, etc, shall be included as resources and run in a Windows XP or higher environment without any additions to Windows. It is acceptable to assume common environments such as Flash, .Net Framework, Java runtimes, Acrobat Reader, etc., will be present on Windows machines hosting the simulation software. The intent of this requirement and associated unstated requirements is to produce a PC simulation that will easily run on the operating system that is widely used and present in the SOF community.

g. Functional Radio Model. The software shall contain a software model that simulates the same characteristics present on an actual radio. The characteristics this radio model shall have should match, at a minimum, those that are present in the DIS standard (IEEE Standard 1278) and the actual radio itself. Such elements being frequency values, power values, squelch values, crypto parameters, modulation, etc.

1) The radio model shall also contain the necessary values associated with equipment that interfaces to the radio such as crypto loading devices.

2) In tutorial modes, the radio model shall be stimulated at each step of the tutorial where necessary. This radio model shall also react upon backward navigation within a tutorial lesson. The radio model shall constantly be updated regardless of mode.

3) This software radio model shall be dynamic enough to not only hold present radio simulation values and stored radio simulation values, but present an easily accessible set of get/set methods for these values. It shall also mimic the radio with regards to values being saved or stored upon power-off. The radio model shall also mimic the audio feedback that the real radio employs. The intent of these requirements and associated unstated requirements is to produce a CBT that at its core contains a radio model which can be used for distributed simulation communications. The intent of these requirements and associated unstated requirements is to produce a CBT that at its core contains a radio model which can be used for distributed simulation communications.

h. Free Play Mode. The software shall contain a “free play” mode that provides a simulation of the radio that has no lesson based element to it. The free play radio simulation shall act the same as if a user were stimulating an actual radio. The radio model shall react accordingly. The intent of these requirements and associated unstated requirements is to produce a CBT that allows a free play mode giving the user the ability to learn by discovery as well as provide an interface to a radio simulation which can be used in other simulation/training events.

i. Modular Software Design. The software shall follow software design patterns that effectively modularize the different rudiments of the software. The radio model, instructional tutorial content, front-end animated interface, etc., shall be modularized as best as possible. Overlap of these areas is expected, but effort shall be placed into modularizing these different software models. The intent of these requirements and associated unstated requirements is to produce a CBT that allows for code re-use on different radio simulations as well as the ability for elements of the software to be used in other non lesson based simulators.

j. Networked. The Radio CBT shall have the ability to operate in a networked mode. In this mode each CBT present on a network shall have knowledge of each other. The software for this networked mode shall follow typical IP network protocols.

k. DIS/HLA based Communications Infrastructure. The simulation software, in line with the above stated requirement, shall have the ability to operate in a networked mode (selectable by a configuration file) that provides a network infrastructure which can be used to accommodate DIS/HLA based network communications. These communications shall give the Radio simulation the ability to communicate with one another as well as other simulations following the same simulation standards. The networked DIS/HLA based communications shall require low bandwidth and low processor usage (less than 5%). The intent of these requirements and associated unstated requirements is to produce a Radio PC simulation that can be used in larger training/simulation events.

l. Solutions for Simulation Unique Shortcomings. The Radio CBT shall provide a set of solutions that solves shortcomings that are found in simulations of equipment. Often real equipment can’t be fully simulated with a mouse point and click simulator. For instance, some equipment requires two buttons to be pressed simultaneously, with a mouse based point and click simulator, this cannot be accomplished since the interface of the host machine (Windows) does not allow it. A solution must be enacted to handle these anomalies that will mitigate human factors concerns as well as minimize the burden on the end-user. Solutions for these anomalies must be presented and accepted by the Government. The intent of the stated requirement is to produce a CBT that has a solution in place to handle the inherent shortcomings a simulation of a piece of equipment imposes.

m. Menu/Link Driven CBT. The Radio CBT shall provide an interface that contains an easy to navigate lesson menu that is selectable via mouse clicks and requires no typing. This CBT shall be a mouse point and click simulator developed to also operate on touch screen systems. The intent of these requirements is to produce a CBT that is easy to navigate and requires only a mouse or touch interface.

n. Single Window Interface. The Radio CBT shall be contained within a single window interface. The intent of this requirement and associated unstated requirements is to produce a contained CBT thereby allowing a simple interface for the user.

o. Interface Design Document. The Radio CBT developer shall provide a complete Interface Design document describing the software architecture and interfaces. The intent of this requirement and associated unstated requirements is to produce a document that sufficiently describes the software thus allowing for easy interfacing, modifying, or leveraging of the developed software. (DI-IPSC-81436A)

PAGE