SOW_3D_mapping.pdf

PDF 127 KB Posted

Attached to
3D Mapping Engine Federal contract opportunity
Solicitation number
W91215-18-R-0001
Issued by
Department of the Army Materiel Command Contracting Command Redstone Arsenal

About this file

SOW 3D Mapping

View the file

Other files for this federal contract opportunity

Other files attached to 3D Mapping Engine, newest first.
File Type Posted
Approved_-_JA__Redacted_for_release.pdf 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

BASE CONTRACT STATEMENT OF WORK (SOW)

C-1.0 STATEMENT OF WORK BACKGROUND

The Special Operations Mission Planning Environment (SOMPE) program provides an integrated software suite of mission planning and execution tools for time critical command and control of globally distributed Special Operations Forces (SOF). The SOMPE Program automates time-intensive planning activities and provides enhanced situational awareness capabilities. SOMPE also provides an interoperable environment for adaptive war planning to collaborate, horizontally, vertically and in parallel, the development of the various components of mission plans. SOMPE spans all elements of USSOCOM including the Center for Special

Operations (CSO), Theater Special Operations Commands (TSOCs), Joint Special Operations

Task Force (JSOTF), Joint Special Operations Aviation Components (JSOAC), SOF warfighters and their warfighting platforms. The SOMPE program develops, integrates, fields, trains and sustains advanced software applications. Under this effort, a SOMPE 3-Dimensional (3D)

Mapping engine will be licensed, developed, modernized and sustained to support SOF requirements and technology enhancements.

C-1.1. Task 1 Software Development and Test Support

C-1.2. System/Software Requirements and Architecture Analysis

The Contractor shall document and analyze derived Special Operations mission planning system/software requirements and make implementation recommendations to include architectural approaches for satisfying user requirements/ mission planning needs. The

Contractor shall analyze the Special Operations mission planning architecture as it evolves. The

Contractor shall analyze existing mission planning software and recommend design and architecture enhancements. The Contractor shall also analyze existing software applications for migration to future systems.

C-1.3. Software Development

The Contractor shall develop/enhance/upgrade software modules, components, and/or tools as directed by the Special Operations Mission Planning Office (SOMPO) to include, but not limited to: core mission planning software and 3D. The Contractor shall review, define and document issues regarding software interfaces and implement improvements as directed by SOMPO.

Proposed software modules shall be developed/enhanced using commercially accepted practices.

The Contractor shall develop software tools that are compliant with Government-furnished interface documentation, as required. The Contractor shall provide pre-release (Beta) software prototypes to the Government for analysis and evaluation. All software products shall be designed for maximum code reuse.

C-1.4. Software Testing

The Contractor shall perform Formal Qualification Testing (FQT) for each software product in accordance with Contractor procedures prior to delivery to the Government. Contractor FQT shall assess the software tool’s basic functionality, maturity, reliability and verify that all requirements have been met. The Contractor shall deliver a test report with each software product.

C-1.5. Software Documentation

The Contractor shall provide software documentation as required by the SOMPE Test and

Evaluation Master Plan (TEMP). Such documentation includes, but is not limited to: Software

Requirements Specification (SRS), Software Version Description (SVD) with Release Notes, Software (including executable and source code), Software User’s Manual (SUM) and Software

Test Report (STR). The Contractor shall document software source code using commercially accepted methods. Software documentation shall be upgraded to coincide with platform and/or mission planning upgrades/enhancements.

C-2.1. Task 2 Software Project Management and Maintenance

C-2.2. Software Project Management. The Contractor shall plan, organize, staff, schedule, and manage software efforts using commercially accepted program management practices. The

Contractor shall also coordinate with other developers and interface with the Government as necessary for successful integration. The Contractor shall ensure technical and schedule data flow is maintained between all activities to prevent technical and schedule incompatibilities. The

Contractor shall provide cost, performance and schedule status on a regular basis. This includes regular program reviews detailing all on-going software development/sustainment activities.

C-2.3. Software Sustainment

The Contractor shall maintain/sustain mission planning software modules, components, and/or tools as directed by the SOMPO. The software shall be maintained using commercially accepted practices. The Contractor shall maintain software that is compliant with Government furnished

Interface Control Documents (ICDs), as required. The Contractor shall provide pre-release

(Beta) software to the Government for analysis and evaluation. The maintained software tools shall be designed for maximum code reuse.

C-3.1. Task 3 Software Licensing

C-3.2. Software Licenses and Data rights. The Contractor shall provide software and data in accordance with negotiated licensing with each delivery order.

C-4.0 The Base Contract Data Requirements Lists (CDRLs) listed below apply to this task order:

CDRL TITLE AUTHORITY

A001 Reserved

A002 Software Product Specification (SPS)/Version DI-IPSC-81441A/81442A

Description (SVD)

A003 Software Users Manual (SUM) DI-IPSC-81443A

A004 Software Requirements Specification (SRS) DI-IPSC-81433A

A005 Meeting Minutes/Notes DI-ADMIN-81505

A006 Computer Software Product End Items DI-MCCR-80700

A007 Letter Progress Report DI-MISC-80711A

C-4.1 The software documentation shall be in Contractor format.

C-4.2 The final delivery of all data items shall be in an electronic format on standard media (CD-

ROM/DVD-ROM, etc.). All product documentation items shall be delivered as MS-Office or

PDF compatible files. All source code, data, and project files required to build the product without error on its target system and run automated test without error shall be included in the final deliverable’s project media.

File details come from the government source that posted it.