PWS_28_Aug_14.pdf

PERFORMANCE WORK STATEMENT FOR THE

UNITED STATES TRANSPORTATION COMMAND AND

THE MILITARY SURFACE DEPLOYMENT AND

DISTRIBUTION COMMAND

USTRANSCOM Geospatial Information System

28 August 2014

This page is intentionally left blank

PERFORMANCE WORK STATEMENT

Table of Contents

SECTION TITLE

1 DESCRIPTION OF SERVICES

2 DELIVERABLES

3 SERVICE DELIVERY SUMMARY

4 GOVERNMENT-FURNISHED AND CONTRACTOR-FURNISHED EQUIPMENT

5 GENERAL INFORMATION

6 SECURITY

7 CYBER SECURITY

Appendices

A TERMS AND DEFINITIONS

B NON-DISCLOSURE AGREEMENT

C APPLICABLE DOCUMENTS

D ESTIMATED WORKLOAD

E GOVERNMENT FURNISHED EQUIPMENT LIST

PERFORMANCE WORK STATEMENT (PWS)

FOR

1. DESCRIPTION OF SERVICES

1.1 Background

1.1.1 The United States Transportation Command (USTRANSCOM) and its component service commands require a solution to provide a geospatial services and a common set of information technology tools and applications for execution, reporting, visualization, collaboration and dissemination of geospatial information. Central to this is a collaboration suite of tools along with a central geospatial data catalog and services. This capability need for an enterprise Geospatial Information Systems (GIS) mapping solution and a repository for all the GIS related data, builds on the Enterprise Geospatial

Information System (EGIS) enterprise tool. This requirement focuses on sustaining, enhancing, creating new capability, and integrating the GIS common tool set for visualization and exposing geospatially referenced information to support situational awareness and collaboration. The solution will integrate into and with a variety of applications and portals. The GIS mapping solution is based on Esri ArcGIS technology which supports a robust set of functions required for consistent data visualization throughout the enterprise and forms the baseline for enterprise geospatial services. USTRANSCOM also requires a web-based geospatial system that enhances its mission to manage and improve the global deployment and distribution. This requirement is currently satisfied by the Intelligent Road and Rail Information System

(IRRIS®). The new system will replicate IRRIS® as-is capability and business rules acting as a real-time global asset tracking system that enables transportation users to obtain detailed, timely and relevant information about road conditions, construction, traffic events and weather that might interfere with the surface movement of cargo within a particular geographic location. It also allows the real-time tracking and management of transportation assets using geospatial technology to reduce operational burdens and provide ad-hoc reporting and alerting tools. This system will directly support the Defense Transportation

Tracking Service (DTTS) and Defense Courier Division (DCD) at USTRANSCOM with mission specific capabilities based on their business rules. Additionally, geospatial analytic tools enable transportation engineers and analysts to conduct quick table top analysis of transportation infrastructure and natural/manmade conditions that affect that infrastructure. Interoperability between this system and

EGIS is highly critical to this procurement.

1.1.2. USTRANSCOM EGIS provides a GIS framework on the SIPRNET/NIPRNET environments to enable the sharing of geospatial data and imagery across the Command. EGIS includes the enterprise map viewer, enterprise catalog and enterprise collaboration solution. EGIS provides a place where enterprise GIS data is discoverable throughout the Command. The GIS Analyst and operational users will be able to search for data created by other GIS initiatives within the Command to be used in conjunction with their requirements to produce map products. This continued partnership leverages

Command hardware, software, data, and analysis resources to incorporate the most useful and relevant information for USTRANSCOM GIS (TGIS) users. The TGIS provides an integrated web enabled real-time geospatial mission management and tracking of critical assets in the Defense Transportation System, web-based geospatial engineering analysis, and situational awareness capabilities. The TGIS will require data exchange interfaces, integration of appropriate web services, and application business rules to satisfy mission requirements. The TGIS and EGIS must operate from the same support hardware and COTS software to maintain hardware and program management efficiencies required by the government.

1.2 Scope

The scope of this PWS consists of technical and analytical expertise including services required to meet the information needs for transportation engineering, mission management, security, and analysis. This

PWS is established to support the Surface Deployment and Distribution Command Transportation

Engineering Agency (SDDCTEA) need to meet military transportation and mobility deployment objectives on a worldwide basis. The primary intention is technical refresh of the program to acquire full government purpose rights and provide support and develop the current EGIS baseline capabilities. All development, enhancements, and sustainment activities will be based on current business processes, rules and capabilities and to sustain, enhance and further develop the new system with transportation decision support solutions to better provide for the military’s mobility goals. This system is deployed in several environments and has a staging (NIPR & SIPR) and production (SIPR & NIPR) environment. The system will be developed and hosted in the SDDC Common Computing Environment on the NIPRNET and hosted on existing government equipment on the USTRANSCOM SIPRNET.

The task areas and associated specific tasks are:

Task 1: Contract Level and Project Management

Task 2: Program Development

Task 3: Data Sustainment and Maintenance, Security, and Documentation

Task 4: Program Sustainment

Task 5: Enhancements and New Development

Task 6: Configuration Management

Task 7: Information Assurance

Task 8: EGIS Sustainment and Enhancements

1.3 Specific Tasks

1.3.1 Task 1: Contract Level and Project Management

This task consists of the functional activities relating to the administration and management of this effort. The contractor shall provide project management of contractor personnel performing tasks in this contract. The contractor shall designate a lead point of contact for technical issues. The contractor shall provide a centralized program management capability at the contractor site. This function shall encompass administrative, clerical, documentation, and related functions that provide general support for the program. The contractor shall provide support by preparing documents such as briefings, point papers, and meeting minutes related to status of the performance of this contract. The contractor shall be required to provide support in the specific areas outlined below in this PWS.

1.3.1.1 Task 1 Subtask 1: Monthly Status Reporting (MSR)

The MSR shall include a brief synopsis of the efforts completed, deliverables provided, activities scheduled for the following month, and conferences and trips conducted/attended during the reporting period. If an employee traveled during the reporting period, the MSR shall include travel expenses and receipts. The MSR shall identify problem areas. The MSR is due monthly at the close of business of the

5th duty day of the month following the report month.

1.3.1.2 Task 1 Subtask 2: In Progress Review (IPR)

The contractor shall meet with the Contracting Officer’s Representative (COR) periodically as the COR may require, to discuss any problems with current tasks, assignment of future tasks and to obtain

Government decisions or guidance necessary to contractor performance. IPRs will be held weekly or more often at the discretion of the COR.

1.3.1.3 Task 1 Subtask 3: Task Order Management Plan

The contractor shall provide a Task Order Management Plan describing the functional approach, organizational and financial resources, supporting organizational structure and management controls that the contractor shall employ in accordance with tasks and deliverables in this PWS. The draft plan shall be submitted within 15 business days of award. The Government will have 10 business days to review the plan and provide comments. The contractor shall have five business days from receipt of the

Government’s comments to submit the final plan.

1.3.1.4 Task 1 Subtask 4: Employment Status Report

The contractor shall provide an employee status report (listing/spreadsheet) containing names and labor categories of personnel supporting the tasks identified in paragraph 1.3. The report shall be provided within thirty (30) calendar days after contract award and updates to the COR no later than 4:00 PM central time the first work day of the following week after contractor staffing levels or personnel are changed.

1.3.1.5 Task 1 Subtask 5: Contractor Manpower Report (CMR)

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for Military Surface Deployment and Distribution

Command via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with

2015. Contractors may direct questions to the help desk at: http://www.ecmra.mil.

1.3.2 Task Area 2: Program Development

The Contractor shall develop the TGIS by reviewing existing architectural and requirements documents for the existing system, interviewing current system user communities established by the Configuration

Control Board (CCB), documenting requirements and business rules for CCB review, and developing capability per CCB and Program Manager (PM) priority. System architecture shall make use of the

COTS products currently in use with EGIS and IRRIS ® to the greatest extent possible. The Contractor shall comply with industry standard development processes, requirements set forth by the SDDC

Business Systems NIPRNET Enclave and Software Development Environment (SDE) and the

USTRANSCOM SIPRNet Demilitarized Zone (DMZ) in developing a system meeting the requirements set forth by the CCB and PM. Development, testing and fielding shall comply with all security and current DIACAP DOD 8510.01, the migration to the Risk Management Framework or the current governance for the certification and accreditation process. The contractor shall identify and document all interface, data, software, hardware and technical artifacts to include full system documentation requirements for the Systems Information repository in the USTRANSCOM Information Tool Suite

(ITS). Contractor-provided software development services shall meet all technical requirements as outlined below.

1.3.2.1 Task 2 Subtask 1: Software Development

The contractor shall prepare a Systems Engineering Management Plan (SEMP) that describes the contractor's technical approach and plan for the conduct, management, and control of the integrated systems engineering effort. The contractor’s SEMP shall be submitted for approval by the COR prior to initiating work. The contractor shall address technology upgrades and architecture improvements in the

SEMP.

The SEMP shall identify a spiral or agile methodology for the development of geospatial and mission management capabilities supporting the DTTS, DCS, and TEA Infrastructure requirements within the

SDDC MISSION ASSURANCE CATEGORY II/III ONCLAVE with the following minimum measures:

Configurable, intuitive user interfaces

Configurable business rules

Configurable external partner integration methods (connections and transports for external interfaces)

Visibility across all business processes and process steps for status and performance monitoring, alerts and error notifications, and analytics.

Web Services implementation using SDDC Business System Enclave (BSE) components

External and internal interface implementations using the SDDC BSE Enterprise Service Bus (ESB)

Maximum use of COTS software currently in use. Esri ArcGIS is the recommended mapping software for this requirement. Oracle is the recommended database software.

The SEMP shall include a strategy for incrementally replicating existing functionality. The SEMP shall incorporate these migrations as part of the implementation of the DTTS, DCS, and TEA Infrastructure capabilities.

The contractor shall include referenced lower level plans such as Configuration Management Plan (CMP) and Software Development Plan (SDP) in the SEMP to plan and execute a total system engineering effort.

The contractor shall prepare a SDP that contains the details of the software development requirements essential to proper software development control. The contractor shall use Government-provided “as is” architecture views to create “to be” architecture views SV-1, SV-6, StdV-1, and StdV-2. The

Government’s software development process includes the following phases:

Phase I Requirements Analysis as described in PWS paragraph 1.3.2.1.1

Phase II System and Software Design as described in PWS paragraph 1.3.2.1.2

Phase III Software Implementation and Integration described in PWS paragraph 1.3.2.1.3

1.3.2.1.1 Technical Requirements

As the Distribution Process Owner (DPO), USTRANSCOM is responsible for directing and supervising the execution of the Joint Deployment Distribution Enterprise (JDDE). The Command's critical mission requires close synchronization of military services, commercial providers, and coalition partners across a global environment.

Since being named DPO in 2003, USTRANSCOM has delivered a robust Joint Deployment and

Distribution Architecture (JDDA) documenting the "as is" state of the JDDE. The JDDA has been an essential resource over the last five years as USTRANSCOM led increasingly complex distribution-related activities supporting deployment, sustainment, and redeployment operating in multiple theaters.

To make better investment decisions and through continued process improvement efforts, USTRANSCOM shifted its architectural focus from the current state of the JDDE to the "to be" vision of its Net Centric future defined in terms of a Corporate Service Vision (CSV). The CSV establishes the goal of creating an enhanced version of the JDDA, referred to as the Joint Deployment and Distribution

Architecture-Enhanced (JDDA-E). The JDDA-E transforms the JDDE from a collection of program-centric stovepipes into an enterprise-governed, interoperable, service-oriented system driven by enterprise requirements.

The JDDA-E is designed to maximize service reuse opportunities, to focus investments, and ensure operational alignment. The JDDA-E ensures complete, actionable information for more reliable decisions. The following describes JDDA-E intended uses:

Requirements Management – Traces incoming requirements from submission through implementation utilizing an integrated corporate governance process

Portfolio Management and Capital Planning and Investment Control (CPIC) – Prioritizes the investments over time to build and sustain operational capabilities

Strategic Planning and Capability Analysis – Provides a framework for assessing capability readiness, risks, performance, and facilitates new capability development and risk mitigation

Business Process Management – Improves agility and operational performance of business processes through active monitoring of existing operations and verification of new practices through modeling and simulation prior to implementation

Standardization – Prescribes the standard processes, information exchanges, and data to be used across the JDDE

Program Support and Guidance – Articulates the roles of programs within the JDDE and, by extension, their alignment to other DOD and Federal Enterprise Architectures (EAs). It also provides programs with knowledge of existing, standards-based options that they can “adopt” before they “buy” or “create”

The TGIS System program is part of the JDDE and, as such, is expected to adhere to the guidance and rules specified in the JDDA-E reference models (Governance, Mission, Performance, Service, Information Technical, and Program and Initiative) for BPM approach, SOA, information sharing, data management, performance measurement, etc. to support the DPO’s CSV.

The TGIS system, as an Acquisition Category (ACAT) III program, is required to comply with DODD

5000.01 and DODI 5000.02. The TGIS system is required to submit DODAF artifacts views in Joint

Capability Integration and Development System (JCIDS) requirements documents, Information Support

Plans (ISPs), and Tailored ISPs (TISPs). The Contractor shall assist the Government in developing and updating these documents. The Contractor shall extract architecture information from ARIS and/or develop architecture artifacts that will support the required documents. DODAF artifacts shall include, but not be limited to, All views, Operational views, Systems and Services views, and Technical Standard views IAW the most current version of CJCSI 6212.01.

The Contractor shall ensure that all information technology (IT) products and services comply with the requirements listed in PWS paragraph 1.3.

1.3.2.1.2 Additional Requirements

Electronic Data Interchange (EDI). The Contractor shall provide, develop, integrate and implement EDI interfaces as required to support current and future interfaces with TGIS. The Contractor shall use an EDI translation software as approved in writing by the Government.

Extensible Markup Language (XML) and Web Browsers. The Contractor shall implement cross browser functionality in TGIS system code design and selection of its associated development tools and COTS product selections. In the development of client browser page content, the Contractor shall maximize the use of international, national and industry best practices and standards that are supported by multiple browser entities. The Contractor’s development solutions shall conform to the most widely adopted versions of the following web content standards and references. If the Contractor proposes other or additional content standards these shall be submitted in writing for approval by the Government prior to use.

ECMA-262 3d Edition, 1999, ISO/IEC 16262

W3C Document Object Model http://www.w3.org/DOM/DOMTR

W3C eXtensible Markup Language XML

W3C Cascading Style Sheets

In selection of client browser coding practices, the Contractor shall develop and select coding techniques that are interoperable and compatible with the following browsers: Microsoft Internet Explorer, Mozilla

Firefox, and Chrome as indicated in Table 1-1.

Applications

Internet

Explorer

(all versions above 8)

Mozilla

Firefox

(all general release versions)

Chrome

(all versions above 15)

All All Users All Users All Users

Table 1-1: Web Browsers Matrix

User Registration and Authentication. The Contractor shall coordinate access control and authentication for TGIS through the SDDC Electronic Transportation Acquisition (ETA) Single Sign-on System or current service offered by the MISSION ASSURANCE CATEGORY II/III ONCLAVE or designated by the government. The Contractor shall enforce role-based access throughout the application. ETA will provide the role information through use of the ETA Triple Data Encryption Standard (TDES) encrypted token. The Government shall be responsible for user registration approval and user management.

Communications

The Contractor shall support the Government to ensure the TGIS allows for optimal connectivity with low user impact and reach to provide access and to meet data volume requirements, transaction requirements, and system source data capacity requirements) for services at U.S. military installations and activities as well as transportation providers worldwide. The TGIS shall support two communications entry points: The Defense Information Switched Network (DISN) and the DISA DMZ.

The Contractor shall support the Government to ensure TGIS provides the capability to allow Internet

(e.g., commercial Internet Service Provider), Unclassified but Sensitive Internet Protocol Router Network

(NIPRNet) and Secure Internet Protocol Router Network (SIPRNet) access to SDDC, USTRANSCOM, military and Government domains.

1.3.2.1.1 Phase I Requirements Analysis

The contractor shall document current system capabilities derived from existing documentation, system information, training and security documents provided by the Government. The contractor shall document current system business rules derived from existing documentation provided by the

Government. The contractor shall provide a level of effort required to create system business rules. The contractor shall develop a methodology to interview and capture requirements, business rules, processes and procedures from existing user communities established by the CCB membership. The contractor shall capture information, requirements, business rules and processes and incorporate them into the

SEMP.

The contractor shall conduct collaborative requirements analysis sessions with the Government. The contractor shall analyze, verify, and clarify the requirements identified for each release. For each requirement, the contractor shall also identify and include the derived requirements in the updated requirements documentation. Derived requirements are requirements resulting from the allocation of technical requirements to logical functional architectures from requirements analysis that may not be apparent to the Government but are part of the scope of the effort. The contractor shall identify opportunities to migrate existing functionality to the TGIS and incorporate these migrations into development of capabilities supporting DTTS, DCS, and TEA Infrastructure.

During requirements analysis the contractor shall create business process models. The business process models shall contain enough details for implementation including variants and exceptions for completeness. The contractor shall determine the task type for each individual business process task

(abstract, user, manual, service, business rule, script, or other custom types) and label them in the business process models accordingly. The contractor shall manage changes to requirements such as textual description, business process models, and traceability between them and in combination with a requirements management tool selected by the contractor.

The contractor shall provide business process models and a Requirements Traceability Matrix (RTM).

The RTM shall include “shall” statements and traceability from “shall” statements to business rules, business processes, and supporting process tasks.

Exit Criteria for Requirements Analysis: Upon the COR’s written approval of the business process models and RTM, or determination by the COR that the requirements process is otherwise satisfied by the contractor’s proposal and methodology, the contractor shall have met the exit criteria for Phase I.

1.3.2.1.2 Phase II System and Software Design

The contractor shall begin Phase II System and Software Design upon successfully meeting the exit criteria from Phase I Requirements Analysis. In support of Phase II, the contractor shall:

1. Suggest and develop a system development approach (spiral or agile) and testing schedule for approval by the CCB and PM.

2. Upon approval of requirement 1, develop the TGIS in the SDDC Business Systems NIPRNET

Enclave Software Development Environment.

3. Develop a user acceptance plan including user stories and performance metrics to measure against. Conduct user acceptance testing of developed capability with user communities directed by the PM and CCB.

4. Develop documentation capturing all relevant information required to support approval of

Authority to Operate, DIACAP, and implementation of the system in the production MISSION

ASSURANCE CATEGORY II/III ONCLAVE.

The contractor shall analyze the business processes and requirements from the requirements analysis phase and the existing IRRIS® implementation to propose high-level design decisions focusing on business processes, process tasks, information exchanges, and data objects in business process models that require automation. Possible high-level design decisions for each process task, information exchange, and data object inputs/outputs requiring automation include, but are not limited to, the following:

Select business processes and process steps

Create new adaptable (web) services

Create new external and internal interfaces

Create new data entities in database and/or in a PMO approved data exchange format.

Create new user interface applications

Automate business rules Wrap and reuse existing software (COTS and GOTS) modules

Migrate existing functionality to newly designed business process execution, reusable services, automated business rules, and user interface applications

The contractor shall create and update DODAF architecture views for software design that affects the architecture. The contractor shall create and populate Data Information Viewpoint and Service Viewpoint with views based on all the other software design documentation delivered.

The contractor shall document external interface design changes in new and existing interface documents

(e.g., Interface Design Description [IDD], Interface Requirements Specification [IRS], Interface Control

Agreement [ICD]).

Exit Criteria for Phase II System and Software Design: Upon the COR’s approval of IT business process models, release-level SDD, design documentation updates to be made in the DBDD, DODAF architecture views, external interface documents, User Role Matrix, and TGIS business rules, the contractor shall have met the exit criteria for Phase II. Phase II exit criteria is also satisfied if the full suite of aforementioned requirements is adopted from the legacy system.

1.3.2.1.3 Phase III Software Implementation and Integration

The contractor shall complete development of designs that have successfully exited Phase II System and

Software Design. During Phase III the contractor shall conduct functional progress review sessions every two (2) weeks. The contractor shall provide a development environment for verification of requirements interpretation and implementation throughout Phase III.

The contractor shall provide updated architecture documentation.

The contractor shall conduct internal peer reviews for all new software module and web service implementation to ensure quality and compliance to design and coding standards specified in delivered

SDP.

The contractor shall monitor process performance based on the process performance requirements defined during Phase I Requirements Analysis. Exit Criteria for Phase III Software Implementation and

Integration: The software release successfully meets user acceptance testing criteria and is successfully implemented in the Production environment on all domains and NIPR COOP.

1.3.3 Task Area 3: Data Sustainment and Maintenance, Security, and Documentation This includes requirements in support of the fielded TGIS and subsequent life cycle product support, including maintenance. Sustainment includes implementation of support systems integration strategies;

application of diagnostics, prognostics and other condition-based maintenance techniques; identification of technology insertion opportunities; identification of operations and support cost reduction opportunities and COOP location to include software patches, hot-fixes, security patches, support for security scans, hardware maintenance and upgrades (support), acquisition and management of relevant commercially available support data (i.e. weather, traffic, imagery) and other items necessary for the successful operations of the TGIS. The contractor shall provide System Administration, Configuration Management, Architecture, and Database Admin/Business Intelligence Engineering Design in support of TGIS

Management Support and Documentation.

1.3.3.1 Task 3 Subtask 1: User Interface/Report Improvement

The contractor shall enhance the user interface making it more intuitive for the end user. The contractor shall modify up to 5 (five) new reports annually for specific user requirements as directed by the COR.

Hours allotted for the 5 new/enhanced reports is 500 hours.

1.3.3.2 Task 3 Subtask 2: Data Sharing

The contractor shall develop, on an annual basis as directed by the PMO, the capability to download data sets and provide web services to other applications in the enterprise to include the EGIS catalog. The contractor shall modify TGIS abilities to import 2 (two) geospatial data sets annually from multiple platforms and create web services to provide TGIS data sets to other applications as directed. Hours allotted for the 1 new geospatial data set is 300 hours.

1.3.3.3 Task 3 Subtask 3: Static Data Updates

The contractor shall update existing TGIS data. These data types are typically static (infrastructure).

Dynamic data, such as weather and traffic information, are separate tasks.

The contractor shall install the most current Homeland Security Infrastructure Program (HSIP) Gold data on an annual basis.

To the maximum extent possible, the contractor shall utilize commercial vendor tile map services and government agency (e.g. National Geospatial Intelligence Agency) tile map services to provide reliable, up-to-date imagery and map overlay information to the TGIS user.

The contractor shall actively incorporate the most current enterprise data from USTRANSCOM stakeholders EGIS catalog and data identified during monthly Enterprise GIS stakeholder meetings to include all relevant metadata. The contractor shall review all existing infrastructure layers for the latest reliable information to include, but not limited to, the following:

Static Data Sets o Military Installation data sets from several sources to include DISDI catalog, TEA and the

Components. Provide verification to PMO on the different data sets reviewed. Review and compare DISDI data with individual military commands data. (annual basis) o National Bridge Inventory (NBI) Bridge Data (annual basis) o USTRANSCOM generated Infrastructure Data - Ports Infrastructure Data Base (PIDB), Modernized Integrated Data Base (MIDB), Joint Operations Critical Infrastructure Program

(J3 CIP) data - (quarterly basis) o Federal Railroad Administration (FRA) Data (annual basis) o Federal Department of Transportation Data (annual basis) o United States Army Corp of Engineers (USACE) Infrastructure Data (annual basis) o State Department of Transportation (DOT) Links (annual basis) o Power Project Platform (PPP) Routes (quarterly basis) o Highway Performance Monitoring System (HPMS) (annual basis) o Maintain documents available in the EGIS catalog

1.3.3.4 Task 3 Subtask 4: Incorporate Dynamic Data

The contractor shall incorporate 2 (two) dynamic data feed annually into TGIS as directed by the PMO.

These data feeds will be made available by web service in the appropriate format. Hours allotted for 1 dynamic data feed is 200 hours.

1.3.3.5 Task 3 Subtask 5: Sustain Dynamic Data

The contractor shall maintain and provide the following dynamic data services to TGIS users:

Dynamic Data:

Provide enhanced real-time traffic flow data (NIPRnet) for all available markets, to include, at a minimum the US, Canada, and Europe. This traffic data must include, at a minimum, speed data, closures, delays, and accidents. This data must incorporate with automated alerting tools developed to support the TEA Highways for National Defense program.

Routing – Provide routing capability to include but not limited to; address to address, latitude and longitude, and Defense Table of Distances (DTOD).

Weather, to include real-time radar, storm tracks, hurricane tracks, forecasts, watches/warnings, and alerts.

Wildfire Information from the Geospatial Multi-Agency Coordination Center

All current Tracking Interfaces and Services o Tracking Data Feeds

Commercial Vessel Visibility (CVV)

Defense Courier Division (DCD)

Defense Transportation Tracking System (DTTS)

Global Freight Management (GFM)

Mobile Terminal Site (MTS)

Northern Distribution Network (NDN)

Premium Automated Identification Technology (AIT)

Radio Frequency (RF) ITV o NGI, Military Grid Reference System (web service) o ESRI, Layers (web service)

Canadian Provinces

Countries

Lat/Long Grid

U.S. States

World Airports o US Census Bureau, Common – 2010 Census Block Population (web service) o Military Installations - Army National Guard Boundaries (web service)

Data Feeds

1.3.3.6 Task 3 Subtask 6: Test and Evaluation (T&E)

The contractor shall provide test coverage using appropriate samples for test validation and norming for any TGIS enhancements and development effort. T&E includes reliability checks, predictive validity, and content validity, construct validity, test administration, test reporting and test and item bias. The contractor shall test all software upgrades to database environments and Operating System upgrades/patches to ensure no adverse system impact results from server changes. The contractor shall provide a report of areas tested and results.

1.3.3.7 Task 3 Subtask 7: Training and Self-Help Material

The contractor shall update TGIS Help and Tooltips to reflect code updates, new functionality and enhancements quarterly.

1.3.3.8 Task 3 Subtask 8: System Management Support (SMS)

The contractor shall provide System Administration, Configuration Management, Architecture, and

Database Admin/Business Intelligence Engineering Design in support of TGIS Management Support and

Documentation:

System Administration. This element includes tasks such as: Act as Information Assurance Security

Officer; apply patches and scan system hardware/software when notified by Information Assurance

Project Manager (IAPM) and TGIS Program Manager; update and maintain Defense Transportation

Tracking System (DTTS) specific client software; ensure Plan of Action and Milestones (POA&Ms) are updated and complete; provide 24x7 on-call response capability to system issues during non-standard duty hours as required (DTTS operational issues, Enterprise Geographical Information Systems (GIS) issues and Classified TGIS issues as required); perform bi-weekly code releases on unclassified and classified systems; assist TGIS Program Manager with DOD Information Assurance Certification &

Accreditation Process (DIACAP) sustainment documentation requirements; and maintain TGIS unclassified and classified equipment inventory and coordinate property book updates. Other tasks include the following tasks:

Hardware inventories.

Server availability monitoring and metrics.

Software inventory and installation.

Anti-virus and anti-malware management.

User's activities monitoring.

Capacity monitoring.

Security management.

Storage management.

Network capacity and utilization monitoring.

Anti-manipulation management

Configuration Management. This element includes tasks such as: Maintain and staff engineering change requests for new and enhanced functionality, ensure Configuration Management

Documentation is maintained in accordance with DIACAP and the TGIS Configuration Review

Board charter, conduct risk assessment of new functionality requests, maintain Corporate Resource

Information Source (CRIS) database, and coordinate Continuity of Operations (COOP) plan exercise annually, maintain white list, ensure ASIs are planned, documented and executed, ensure firewall requests and necessary actions to support firewall mods are carried out.

Architecture and Engineering Design. This element includes tasks such as: Advise TGIS Program

Manager in design and execution of system architecture, ensure equipment recommendations meet

DOD security standards, and assist Program Manager in the development of architecture products.

1.3.4. Task 4: Program Sustainment

The contractor shall update tools and applications as needed to support changes to the TGIS information technology or business environments and related business rules. The contractor shall meet with the COR, the PM and/or the Government’s Configuration Management (GCM) weekly to discuss current capabilities and prioritize any proposed changes to existing Configuration Control Board (CCB) priorities. These meetings are held in the Functional PM’s conference area at Scott Air Force Base (AFB).

1.3.4.1 Task 4 Subtask 1: Sustain Program Capabilities

The contractor shall support the Government by managing the TGIS application. Application management and administration activities shall include the following:

Review vulnerabilities, develop implementation plan, and install patches as they become available

Ensure Database Administrator (DBA) accounts are not used for non-DBA activities. Application user accounts provide access to application database objects to perform a particular application function to application user accounts. Privileges granted to application user accounts will follow the principle of least privilege and include only those privileges required to perform the assigned function.

Contractor shall provide support to maintain, implement and enhance servers, databases and applications that includes, but is not limited to, tuning and performing backups, database tuning and backups, system patching, and other information assurance compliance. The contractor shall load all applications and COTS/GOTS software within the test and development environments, and assist the

Government’s system administrators in loading application, and COTS/GOTS software within the

NIPR and SIPR Production, Staging, and development servers.

1.3.4.2 Task 4 Subtask 2: Sustain Existing Documentation

The contractor shall sustain, review and update system documentation, to include database, system, and software/application documentation. Documentation shall be updated with each quarterly release or reviewed at least annually if no quarterly updates were required. Documents shall be delivered within 30 days of each release.

The contractor shall provide an After Action Report (AAR) within two business days to the TGIS PMO for every system outage, to indicate start and stop time, reason for outage, and solution. The AAR shall follow standard SDDC procedures. A system outage is defined as a user unable to log into the application.

For example, DTTS operators are unable to process BOLs or receive DEN notifications, or DCD is unable to track their missions. The Enterprise Change Control Tool (CCT), Serena, is used to capture and automate system outages. Part of its capabilities is to capture the information for an outage and automate its after-action reporting.

1.3.4.3 Task 4 Subtask 3: Disaster Recovery and Contingency Operations

1.3.4.3.1 Maintain Disaster Recovery Environment

The contractor shall complete all required application configurations to ensure TGIS is correctly installed and configured to operate at SDDC’s alternate site. To ensure operationally correct software, the contractor shall install and configure application software at the alternate site within one (1) business day of installing and configuring the same software on the Production site.

1.3.4.3.2 Disaster Recovery Plan

The contractor shall update the TGIS plan for disaster recovery and contingency operations in coordination with the enterprise Disaster Recovery Exercise (DRE) solution and SDDC’s MISSION

ASSURANCE CATEGORY II/III ONCLAVE if applicable. The plan shall include crisis emergency management (onsite and offsite) (technical and functional); disaster recovery; pre and post emergency operations requirements; and fail-over management.

1.3.4.3.3 Contingency Operations

The contractor shall provide support to the Government during contingency or emergency operations

IAW approved disaster recovery and contingency operations plans. The contractor shall ensure resources and key personnel are available throughout an emergency IAW the established plan.

1.3.4.4 Task 4 Subtask 4: System Support

1.3.4.4.1 Software and Hardware Maintenance

The contractor shall provide support for database, application software, and hardware in the production, training, staging, test, and development environments hosted within the MISSION ASSURANCE

CATEGORY II/III ONCLAVE, USTRANSCOM and SDDC for TGIS. Hardware maintenance is only required in the SIPRNET environments. This includes, but not limited to, tuning and performing backups, database tuning, system patching, and other information assurance compliance. The contractor shall load all applications and COTS software within the test and development environments, and assist the Government’s system administrators in loading application, and COTS software within the NIPR and

SIPR Production, Staging, and Development servers.

1.3.4.4.2 Operational Support

The contractor shall provide a support role to the Government for virtually hosted systems in monitoring server and database performance, ensuring connectivity, and complying with all security and certification and accreditation requirements in the staging and production environments. The contractor shall participate in the enterprise change management processes. The contractor shall identify and document current and planned interface, data, software or technical changes. The contractor shall introduce proposed software, interface and technical changes to the contractor’s Change management (CM) for promotion and implementation of those changes in the SDDC environment. Oracle and ESRI software are the recommended geospatial and database products. Supporting the TGIS hardware environment requires knowledge of the following:

Configuration skills within an n-Tier enterprise architecture and network topology

Linux based servers

Network Connectivity via NIPRNET, SIPRNET TRANSCOM and the SDDC Local

Area Network (LAN)

Microsoft Windows /Windows 7 client workstations

The contractor shall test and troubleshoot the TGIS after USTRANSCOM, SDDC and MISSION

ASSURANCE CATEGORY II/III ONCLAVE outages/upgrades that typically occur during non-duty hours. The contractor will coordinate with the EIP team if they discover any issues after the outage, and may be required to assist the EIP team to restart some services to bring TGIS back to normal operations.

Typical MISSION ASSURANCE CATEGORY II/III ONCLAVE maintenance outages occur on alternating Sundays, usually twice each month.

1.3.4.4.3 Functional User Support

The contractor shall provide routine support to TGIS users and TGIS PMO to include analyzing and resolving day-to-day operational issues in the TGIS. The contractor will assist in providing technical configuration knowledge and facilitate knowledge transfer to the Government SMEs to include operating and querying database reports, opening and tracking Technical Assistance Requests (TARs), and assisting with data extraction from TGIS.

1.3.4.4.4. Tier II and III Support

The contractor shall provide Tier II and III support during agency operating hours as defined in 4.1, and have a designated on-call person available for all non-operating hours. Additionally, the contractor shall support the Government by resolving Tier II and Tier III support questions. The contractor will provide input to assist in the enhancement of Help Desk Tier I procedures and operations and will provide feedback to Tier I regarding solution to all tickets that have been escalated in order to permit population of this information into the Help Desk solution database. The contractor shall be responsible for monitoring impacts on systems and the user community, and provide advice, assistance, and recommendations related to impacts that arise during design, development, implementation, testing, fielding, maintenance, and support of TGIS.

1.3.4.4.5 Program Management Support

The contractor shall provide operational and technical support to the TGIS PMO. Specific activities shall include:

Providing short-term advisory and technical services to assist Government SMEs with evaluating potential changes to TGIS features and functionality

Planning for integration of new and existing systems with existing architecture to satisfy interface requirements

Providing expert recommendations on problems or validating the approach to resolving functional or technical issues

Preparing Standard Operating Procedures (SOPs) for TGIS

Best practices

1.3.5 Task 5: System Enhancements (OPTIONAL)

Task Area 5 is reserved for potential use and cannot be quantified until a future date. The option may be exercised and negotiated during the life of this contract. Automated information systems may require enhancements to the existing capabilities or the development of new capabilities as business requirements and operational needs change. Therefore, the contractor shall develop new solutions for the TGIS functional community, to include custom databases, new/updated features within the DTTS, DCD or TEA applications, and reports, to streamline or supplement SDDC business processes. The contractor PM shall attend weekly meetings, and provide weekly feedback, with the COR and the TGIS Technical and

Functional PMO to review the status of all ongoing updates, repairs and changes to existing capabilities and discuss and validate new workflow solutions using the CCB priorities to track. The contractor shall also follow normal configuration management (CM) processes as defined in Task 5.

Enhancements to TGIS may include, but are not limited to geospatial capabilities to support functional community and new capabilities based on emerging business needs. Typically, routine (minor) changes include changes to database reports, additional data feeds, mapping layers and the addition of new data elements. Routine changes within the TGIS program average less than 160 man-hours to configure and test.

1.3.6 Task 6: Configuration Management (CM)

The contractor shall provide CM support for the TGIS program. The contractor’s CM processes must complement the Government’s CM (GCM) processes. The TGIS PMO and Contractor’s Configuration

Manager (CCM) shall work closely with the Government’s Enterprise Support Services (ESS)

Configuration Manager.

1.3.6.1 Task 6 Subtask 1: CM Planning

The CCM shall provide input to the TGIS Configuration Management Plan (CMP) and utilize processes that are consistent with and complement the GCM processes. The TGIS program uses the CMP that defines the Government’s current CM processes. The contractor shall provide updates to the CMP to define their developmental CM processes. The CMP includes the following:

Contactor’s configuration management processes and procedures

Methods, procedures, and controls

Baselines (versioning)

Change control

Configuration status accounting

CM audits of total configuration to include hardware, software, and firmware

CM Repository (Dimensions will be the delivery repository for source code prior to deployment-Government will provide network connection)

CM Process

1.3.6.2 Task 6 Subtask 2: Change Control

The contractor shall provide change control for all TGIS baselines and configuration items to include documentation, hardware, COTS software, application, source, and executable code. The Government will provide the contractor with web access to the SDDC Enterprise Change Control Tool (CCT), currently supported by Serena Business Management (SBM) software. The Government’s CCT is a tool shared by the TGIS PMO staff and the contractor staff and is programmed to support the TGIS configuration management process within the MISSION ASSURANCE CATEGORY II/III ONCLAVE.

The contractor shall comply with all G6 CM standards and processes.

The contractor shall evaluate all Change Requests. The contractor shall provide their evaluation upon request. Evaluations include, but shall not be limited to: requirement clarification, requirements analysis, determination if the requirement is feasible, cost (labor hours) estimation, adherence to standards, training impacts, and the consequences of the proposed change. This information shall be provided to the

Government for evaluation via the CCT and as a separate document depending upon the amount of information required or provided. This evaluation shall help the PMO staff and the contractor to determine how many, and which, change requests shall be rolled into each release, and will help to determine dependencies within the software development life cycle (SDLC).

The contractor shall conduct a physical and functional configuration audit of each code baseline/release delivered to the Government. The Government reserves the right to participate in the audits if desired, and will coordinate Government participation with the contractor.

1.3.6.3 Task 6 Subtask 3: Asset Management

The contractor shall provide updates to the Government on hardware and software inventory (as appropriate), warranties, maintenance support agreements, software licensing, and accountability for equipment purchases and upgrades. The Government will maintain and update the enterprise asset database that identifies all existing infrastructure assets, hardware, and COTS software. The contractor shall provide status of baselines, configuration items, and status of all outstanding enhancements and defects.

1.3.6.4 Task 6 Subtask 4: Configuration Control Board (CCB)

The CCM shall participate in the Government’s CCB. The CCM shall act as the liaison between the

Government and contractor to provide any additional information that the CCB requires. The contractor shall participate in a weekly Enterprise CCB meetings. Participation will help ensure contractor activities are focused in the areas the Government deems important, and changes within the Government’s

MISSION ASSURANCE CATEGORY II/III ONCLAVE are properly vetted across all affected programs. The contractor shall submit enterprise CCB documentation no later than 2 hours prior to CCB.

The contractor shall participate in weekly TGIS CCB meetings. The contractor shall analyze new requirements prior to the meeting and provide information to the Government team in order to prioritize program level requirements.