U_TFDM_Sustainment_Retirement_SOW_20200109_F.docx

National Geospatial-Intelligence Agency

STATEMENT OF WORK

Topographic Feature Data Management (TFDM) Sustainment and Retirement

5 January 2020

Contents

List of Tables

UNCLASSIFIED

Page iii

UNCLASSIFIED

(U) Introduction

(U) Background

(U) The Topographic Feature Data Management (TFDM) program provides topographic feature data management services across the National System for Geospatial-Intelligence (NSG). Specific services include conversion, ingest, maintenance, and dissemination of topographic feature data and workflow management of data production and maintenance processes. NGA is seeking to gain application efficiencies by transforming business processes, management tools, and data models associated with topographic feature production, management, and dissemination.

(U) NGA Source Operations and Management Directorate (NGA/S) has deployed TFDM data production and maintenance operations to the SECNet. Topographic feature data is usually classified as “Unclassified/Limited Distribution” and will be disseminated at all the Secret and Top Secret security levels within the NSG enterprise; however, the classification level can be set on a case by case basis and maintained according to its classification level.

(U) TFDM Program Plan

(U) TFDM was developed and fielded through an incremental delivery process. The TFDM Full Operating Capability (FOC) satisfying the TFDM Users’ CONOPS plus subsequent decisions was delivered to production in July 2014. TFDM replaced the legacy GIDI/GIFD system and provides web-based access and data dissemination capabilities along with workflow management.

(U) The current TFDM functionality and mission is slated to be incrementally assumed by the Foundation GEOINT Modernization efforts beginning in FY18 and concluding in FY20 at which point TFDM will be decommissioned. System engineering will be needed to ensure the required TFDM functionality is properly assumed by newer FG services.

(U) Scope

(U) This SOW addresses the required Operations and Maintenance (O&M), functionality transition and decommissioning requirements for TFDM for the stated period of performance.

(U) NGA operates its IT Services with an ASP/ISP split of responsibility.

(U) The government requires the contractor to fully understand and maintain a relationship with all the Infrastructure Service Providers (ISPs) to ensure a fully operational capability across the National System for Geospatial Intelligence (NSG). As the scope of this SOW is constrained to ASP efforts and necessary interface with the ISP(s) to achieve ASP goals, the government expects the contractor to work with all the ISP entities to ensure a complete and operationally viable system.

(U) The contractor should review the TFDM Documentation to understand the TFDM architecture and the ASP/ISP responsibility split. The government has levied general and specific requirements for the accomplishment of ISP coordination tasks in this SOW.

(U) The government is also levying requirements for supporting and in some cases, implementing the transition of the data and the functionality of the TFDM system into assuming capabilities throughout the Period of Performance of this SOW. Following the complete transition, the contractor shall decommission the TFDM system.

(U) The contractor shall interface with the Enterprise Call Center to satisfy user issues.

(U) The Enterprise utilizes a process to assess impacts across systems for incoming change requests. The contractor shall provide the capability to assess impacts to the TFDM system for incoming change requests and respond to these requests.

(U) Applicable Documents The following documents are available either on the internet or are among the documents included the Contractor Bidder Library.

The documents listed in Table 1 are reference documents. Note: Some of the reference document versions listed herein may have been updated between the time of writing of this document and the award of this contract.

Table 1 - (U) Reference Documents

NSG Application Schema (NAS), Version 6.0

NAS Version 7.0

NSG Metadata Foundation (NMF) – Part 1: Conceptual Schema Profile, Version 2.1

NSG Metadata Implementation Specification (NMIS) – Part 2: XML Exchange Schema, Version 2.1

NSG Metadata Implementation Specification (NMIS) – Part 2: XML Exchange Schema - XSD, Version 2.1

Note: NSG documents are found at https://nsgreg.nga.mil/overview.jsp

OpenGIS Web Service Common Implementation Specification, Version 2.0.0

OpenGIS Web Map Context Implementation Specification, Version 1.1

OpenGIS Filter Encoding Implementation Specification, Version 2,0

OpenGIS Catalogue Service Implementation Specification, Version 2.0.2

OpenGIS Web Feature Service (WFS) Implementation Specification, 1.1.0

OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0

OpenGIS Geography Markup Language (GML) Encoding Standard, 3.2.1

OGC Geography Markup Language (GML) Simple Features Profile, Version 3.2.1

OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification, 1.1.0

OGC Keyhole Mark-up Language (KML) 2.2.0, OpenGIS Implementation Specification Web Processing Service (WPS), 1.0.0

Geographic Information – Metadata with Technical Corrigendum 1, 19115

Geographic Information – Metadata – Part 2: Extensions for imagery and gridded data, 19115-2

Geographic Information – Metadata – XML schema implementation

Note: OGC documents are found at http://www.opengeospatial.org

NGA Instruction for Preparing NGA Web Pages, NI 8955.5R5, 22 May 2009

NGA Configuration, NI7400.1R4, 9 June 2006

NGA Property Management, NI7410.4R8, 1 October 2004

The documents listed in Table 2 are compliance documents. The contractor shall comply with the TFDM System Documents listed in Table 2. During performance, the contractor will deliver revised compliance documents. Upon formal written acceptance by the Government of the revised compliance document, it shall be the compliance document of record for this statement of work.

Table 2 - (U) TFDM System Documents TFDM_System Requirement Document (SRD), Revision A, 15 July 2015

TFDM_User Concept of Operations (CONOPS), v1.3, 26 March 2012

TFDM_Version Description Document (VDD), latest

TFDM_System Engineering Plan (SEP), v1.1, 21 October 2011

TFDM_Configuration Management Plan (CMP), v2.1, 10 July 2013

TFDM_Test Plan and Test Cases (per delivery version), v2.6.x

Topographic Data Store (TDS) Data Content Specification (TDS DCS) Version 6

Topographic Profile of NAS 7.0

(U) Description of Work

(U) General Approach

(U) The activities identified within Section 3.1 General Approach are inherent to all CLINs and shall be priced accordingly.

(U) System Engineering Approach

(U) The contractor shall utilize the TFDM system engineering approach as documented in the TFDM System Engineering Plan (SEP) when working system issues. Note: The government does not require the contractor to use specific software tools to implement the approach.

(U) The contractor shall maintain and update the TFDM SEP. (CDRL 5)

(U) Configuration Management

(U) The contractor shall utilize the TFDM configuration management approach as documented in the TFDM Configuration Management Plan (CMP). Note: The government does not require the contractor to use specific software tools to implement the approach.

(U) The contractor shall maintain and update the TFDM CMP. (CDRL 6)

(U) Software Maintenance Flow Approach

(U) The work needed to perform TFDM software maintenance updates and put those updates into production at NGA involves several organizations. Please refer to the diagrams in Appendix A for the process used to move the software maintenance updates through the testing process. The following diagram shows the flow through the three environments for the process.

Figure 3 - (U) Software Maintenance Environments

(U) The first column represents the Contractor (CTR) Lab environment. The second column represents the on-site testing environment which validates software maintenance actions and the third column represents the on-site operational environment. The Contractor Lab is normally housed in an off-site contractor facility in (for this contract) a secure area. The Contractor shall standup the lab equipment to simulate the on-site testing and operations environments; the Contractor Lab will not need to replicate the on-site footprints. The method of delivery of code from one environment to another depends on the classification level of the code, size of code and current NGA procedures.

(U) For this contract, in most cases, the code will be Unclassified; therefore, it can be hand-carried, mailed or downloaded from a contractor controlled file server/website. All media coming on-site will be inspected prior to release. Real data may be used during testing at the contractor site; proper handling of classified material will be used to deliver this data to the secure Contractor Lab. Movement of code and data within the on-site environments will be facilitated by the Infrastructure Service Providers.

(U) Again, in most cases, the code will be Unclassified; however, due to the potential use of real data for testing, all personnel working in the CTR Lab and/or having access to potentially classified code or data must have appropriate clearances.

(U) Communication

(U) The contractor shall work with the designated Government personnel across the NGA Directorates to assure operation of the system. The contractor shall be proactive in alerting customers of impending/on-going operations that may impact their use of the system.

(U) The contractor shall document all software customizations and configuration changes required to satisfy the TFDM Operations and Sustainment activity.

(U) The contractor shall support demonstration events to highlight key capabilities of the TFDM Service.

(U) Coordination with ISP

(U) The contractor shall coordinate with the ISP providers to ensure TFDM is functional 97% of the time including unplanned outages.

(U) Specific Requirements

(U) Program Management

(U) The Program Management activities are inherent to all CLINs and shall be priced accordingly.

(U) The contractor shall provide a management structure to manage the overall contract activity. The contractor shall assign a single point of contact and a back-up point of contact to serve as the interface to the Government. The contractor shall provide monthly status reports that depict cost, schedule, and performance and issue characteristics of the program. In addition, the contractor shall provide weekly status reports (e.g. quad charts). Due date of the weekly report will be agreed upon by the Government and the contractor after award. The contractor shall generate and maintain a program plan that includes all activities required to operate and maintain the TFDM system (CDRL 3).

(U) The Program Plan shall include, but is not limited to:

· Master Plan and schedule

· Configuration Management Plan

· Technical approach

· Project goals and outcomes

· Organizational requirements with roles and responsibilities

· Risk statements and risk mitigation plan

(U) The Contractor shall submit a Monthly Project Status Report (PSR). The PSR shall contain a brief description of each task/deliverable, date of assignment, due dates, current status of work towards completion, authorized budget, total dollars spent, a summary of staffing requirements, and a list of outstanding Government or Program topics that must be resolved. The Contractor shall use industry standard management precepts to establish a budget baseline, collect milestones for completing tasks, and identify performance concerns early. In preparing the report, the Contractor shall provide a monthly analysis to compare actual accomplishments to what had been planned. The report period shall cover the previous month (CDRL 8).

(U) To ensure accuracy of financial reporting and invoicing, the Contractor shall provide financial data following the precepts found in DD Form 2734, the Contract Funds Status Report (CFSR) and Contract Schedule Status Report (CSSR) or equivalents (CDRL 14).

(U) The report shall include monthly and cumulative expenditures for labor, travel and materials. These reports shall be delivered by e-mail in a format compatible with Microsoft Office 2010 or current version identified by the government.

(U) The contractor shall deliver an Integrated Master Schedule (IMS). This IMS shall reflect all programmatic meetings, CDRL delivery dates and milestones (CDRL 4).

(U) The contractor shall be available to discuss program status with the Government PM and/or PMO members on an as needed basis.

(U) The contractor shall create and execute plans to accomplish the following milestones:

TFDM Decommissioning Plan (CDRL 7)

(U) The contractor shall generate and provide weekly status quad charts (CDRL 1).

(U) The contractor shall generate meeting minutes for all meetings during which decisions, issues or actions impacting the program or system are discussed (CDRL 2).

(U) The contractor shall hold a monthly Program IPT meeting during which the following will be discussed:

Activities Accomplishments Planned Work Items Schedule Risks

(U) System Sustainment

(U) The Contractor(s) shall sustain operations and perform adaptive maintenance on the Topographic Feature Data Management (TFDM) system throughout the Period of Performance until all necessary functionality is available in the enterprise, at the determination of the Government, at which time the Contractor(s) shall transition and decommission the system. Sustainment includes monitoring the system for issues, accepting and responding to problem reports utilizing Remedy (NGA Enterprise Incident Reporting System), assisting users in relation to problem reports and potentially performing software fixes or configuration changes in response to problem reports. Adaptive maintenance includes modifying the TFDM applications to ensure that they continue to function properly in a changed or changing environment. The TFDM contractor shall also coordinate with the FGMod contractors when performing TFDM software changes to ensure mitigation of any potential impacts to FGMod.

(U) The contractor shall follow standard NGA processes for putting a new build into the operational environment. The contractor shall work with the ISPs to ensure the system remains up and operational during/after the planned data center move.

(U) The contractor shall review, assess and provide documentation to support Request for Changes (RFC). The number of RFC’s received varies; for planning purposes assume one RFC every month with an estimated 8 hour time requirement.

(U) The contractor shall support the TFDM and NGA Engineering Reviews and Boards as required. For planning purposes, assume 16 hours per month.

(U) The contractor shall perform the work required utilizing industry standard Agile processes to investigate, status, fix and close approved Discrepancies Reports (DRs) to the customer and government program office satisfaction. An example set of DRs is provided in the Contractor Bidders Library (CBL). The contractor shall work with the Government Program Office (GPO) and customers to determine which DRs will be worked in what order utilizing industry standard Agile engineering processes. The contractor shall utilize the NGA Enterprise Incident Reporting system (Remedy) for this effort. In the table below: (1)’DRs per Month’ indicate a historical monthly average of changes per complexity; and (2)‘ Hours per DR’ includes all the work required to make the change and put it into production; this includes all integration, testing and deployment activities. Although the number, complexity, severity and priority of DRs vary over time, the average number and complexity of DRs to be resolved per month is set forth in the Table 3. The numbers in Table 3 are applicable to the entire period of performance.

Table 3 - (U) DR Metrics

(U) The contractor shall test and deploy builds generated as a result of DR corrections and/or security required changes utilizing the accepted NGA processes. For planning purposes, assume one corrective build deployment per month using a process similar to those shown in Appendix B (U) Example Test Process. Corrective builds may include incorporating upgrades to the underlying COTS software. (CDRLs 12 and 13)

(U) The contractor shall support ASP IAVA resolution. The contractor shall develop a plan of action memorandum (POAM) and coordinate with ISP contractors for IAVA resolution. For planning purposes, assume this will require 20 hours per 6-month period.

(U) The contractor shall support TFDM in accordance with the NGA system sustainment process. The contractor shall ensure the system is up and operational 97% of the time including unplanned outages.

(U) The contractor shall generate and provide a weekly O&M status report. This report shall include at a minimum (CDRL 8):

List and status of current DR’s System usage metrics Upcoming ISP work that may affect TFDM operations

(U) The contractor shall provide daily tier 2 and tier 3 maintenance support with on-call support after business hours, holidays and weekends for TFDM in compliance as the Application Service Provider (ASP). It is understood the contractor is not responsible for Infrastructure Service Provider (ISP) issues, but the contractor shall work with the ISP as needed to resolve problems and to deploy baseline updates. For planning purposes, assume 10 – 15 calls of .5 hours each per month. The daily core hours supported are 0800-1700 M-F and on-call as needed outside of those hours; for planning purposes assume 8 hours of off-hours calls per month. Calls/tickets assigned to TFDM are to be responded to within one (1) hour and the contacted for follow-up within two (2) hours.

(U) The contractor shall achieve and maintain the System Security Plan (SSP) and appropriate security documentation for TFDM to ensure compliance with Intelligence Community Directive (ICD) 503. This includes performing all requisite security engineering and acquiring all required security approvals to include the ATC, ATT and ATO as needed during system sustainment. Information on the current security approvals is located in the CBL.

(U) Enhancement Backlog Work Off

(U) No further enhancements will be made to the TFDM system under this contract except as needed to meet security requirements or to allow data synchronization with FGMod. The TFDM contractor will work with the FGMod contractor to ensure any changes made to FGMod do not cause issues in any parts of the legacy TFDM system that is still operational. It is planned that at some point in this contract the legacy portions of TFDM will be retired and replaced by FGMod.

(U) TFDM Functionality Transition to Assuming Systems

(U) The Contractor(s) shall operate and maintain the Topographic Feature Data Management (TFDM) legacy retiring system until all necessary functionality is available in the enterprise, at the determination of the Government, at which time the Contractor(s) shall transition and decommission the system.

(U) The Contractor shall coordinate and collaborate on transition efforts with others as directed by the Government—to include but not limited to: Other government developers, development contractors and engineers to accomplish the goals of FG modernization. Transition activities will necessitate coordination with Foundation GEOINT Modernization efforts. The Contractor shall perform the following work in support of this transition:

(U) The contractor shall support the TFDM data and functionality transition to Foundation GEOINT Modernization efforts to include but not limited to:

Attending TEMS to provide TFDM expertise and engineering/coding/operations guidance to influence the design of the replacement solutions Reviewing and inputting into engineering documentation and briefings Providing requested data to the assuming systems’ teams Modifying TFDM legacy components as needed to stay in sync/compliant with FGMod data production Supporting Planning and testing meetings as requested by the government

(U) The Contractor shall report transition work and status of integration work performed for input into the program’s IMS and Monthly Status Report.

(U) TFDM Decommission

(U) The contractor shall develop and execute the TFDM Decommissioning Plan when the option is exercised per the contract. (CDRL 7) The Plan shall detail all activities required to archive the system data, documentation and records; all work needed to remove the system software from its hosted hardware; all tasks required to turn in unneeded hardware and software licenses and the schedule required to execute the work within the required timeframe.

(U) The contractor shall perform all activities necessary to transition relevant equipment, data, software, and documentation to a government identified agent according to applicable contract clauses and NGA processes. The period of performance for the TFDM decommissioning is six (6) weeks.

(U) The contractor shall develop a decommission plan to hand-off all equipment, data, software, system configuration items, scripts, documentation, and any other relevant materials generated during the performance of this contract to a government selected agent (CDRL 7).

(U) The contractor shall execute the decommission plan.

(U) The contractor shall interface with the ISP to ensure an orderly shutdown of the system.

(U) The contractor shall ensure system users are alerted of the impending shutdown monthly in the quarter preceding the shutdown date.

3.2.5.5 (U) If time remains on the PoP after TFDM is shut down, the contractor shall support FGMod operations, as directed by the government, until the end of the PoP.

(U) Personnel Qualifications

(U) The contractor shall provide personnel with the qualifications as defined in the following sections. NOTE: Key personnel shall be in place on day 1 of the contract. Remaining personnel shall be in place within 30 days of contract award.

(U)Prime Program Manager (PM) –KEY PERSONNEL

(U) Required qualifications of the Prime PM:

· Master’s Degree in Business, Engineering, or Computer Science

· 5+ years PM experience within the IC Community with similar complexity system utilizing Esri products (e.g., ArcGIS, Workflow Manager, Mapping and Charting Solutions) and Oracle Relational Database (RDB)

· Prime/Sub Contract Teaming Experience

· Experience managing a distributed team

· Certifications: PMP, ITIL Desired qualifications of the Prime PM:

· Experience with Citrix

· Experience with NGA’s Remedy system

· Experience with Apache Tomcat

· Experience with OpenSSL (U)O&S Team Lead –KEY PERSONNEL

(U) Required qualifications of the O&S Team Lead:

· Bachelor’s Degree in Engineering or Computer Science

· 5 years O&S experience within the IC Community with similar complexity system utilizing Esri products (e.g., ArcGIS, Workflow Manager, Mapping and Charting Solutions) and Oracle Relational Database (RDB)

· 3 years supervisory experience within the IC Community

· 10 years experience building and managing Linux servers, Windows servers, and ArcGIS server sites

· Extensive experience with NGA’s networks and operations, including boards and processes required to successfully deploy builds into operations

· Certifications: Security+

(U) Desired qualifications of the O&S Team Lead:

· Experience with Citrix

· Experience with NGA’s Remedy system

· Experience with NGA’s XACTA system

(U) Senior Software Engineer

(U) Required qualifications of the Senior SW Engineer

· 15 years experience building and managing Linux servers, Windows servers, and ArcGIS server sites

· 10+ years experience with ArcGIS suite of GIS applications, including Mapping and Charting Solutions and Workflow Manager

· Extensive experience troubleshooting and resolving issues with ArcGIS applications

· Extensive knowledge of ArcGIS interaction with Oracle databases

· Extensive experience with Apache Tomcat

· Extensive experience with OpenSSL

· Certifications: Security+

(U) Desired qualifications of the Senior SW Engineer:

· Experience with Citrix

· Experience with NGA’s networks and operations

· Experience with load balancers and NGA’s GEOAxIS authentication

(U) Principal Software Engineer

(U) Required qualifications of the Principal SW Engineer

· 10 years experience building and managing ArcGIS server sites and ArcGIS portal sites

· 7 years experience with ArcGIS suite of GIS applications, including Mapping and Charting Solutions and Workflow Manager

· Experience troubleshooting and resolving issues with ArcGIS applications

· Knowledge of ArcGIS interaction with Oracle databases

· Experience with Apache Tomcat

· Experience with OpenSSL

· Certifications: Security+

(U) Desired qualifications of the Principal SW Engineer:

· Experience with Citrix

· Experience with load balancers and NGA’s GEOAxIS authentication

(U) Test Engineer

(U) Required qualifications of the Test Engineer

· 5 years experience testing GIS applications

· 7 years experience testing ArcGIS applications including Workflow Manager

· Experience testing in a CITRIX environment

(U) Desired qualifications of the Test Engineer:

· Experience with NGA’s networks and operations

(U) System Requirements

(U) The system requirements for TFDM are managed using the TFDM System Requirements Document (SRD). The contents of the SRD are managed and controlled by the NGA Configuration Control Board change management process.

(U) The contractor shall deliver all artifacts as stated in Table 4 - (U) Deliverables.

(U) The government will review all deliverables and acceptance will be transmitted by the COR or Contracting Officer.

(U) The contractor shall deliver all executable code and source code used for a versioned build. A versioned build contains all the files and data used to deploy the system into production; these files are normally bundled as .zip files or similar. The delivery may be made in various ways such as using a company based Content Management System from which the government may download or on media such as a hard drive or disk via hand delivery or registered mail. (CDRL 11)

Table 4 - (U) Deliverables

(U) General Requirements

(U) Place of Performance

(U) The bulk of this effort shall be conducted at the NGA facility in Springfield VA. The contractor shall perform development work and integration testing at the contractor’s facility prior to delivering the software to NGA for integration and test.

(U) Contractor shall support test events in the Washington D.C. and St. Louis areas. Technical exchange meetings and reviews may be held in NGA facilities. NGA will provide office space or computer resources for full-time O&S and on-site support.

(U) Travel

(U) Travel within the metropolitan D.C. area and to St Louis MO area may be required. For planning purposes, assume one 3day/2night trip every six months.

(U) The Contractor shall submit anticipated destinations, number of personnel, duration, and associated costs to NGA. All travel will be specifically authorized via email by the COR prior to departure. Trip Reports will be submitted to the COR within ten days of completion of travel. (CDRL 10)

(U) Security

(U) Contractor personnel having access to potentially classified code and/or data must possess TS/SCI level clearances on day one of the Period of Performance. The contractor must possess a Top Secret Defense Security Service granted Facility clearance allowing performance of classified work. The contractor must provide SCIF workspace that is accredited to store and process TS/SCI information. All classified reports and briefings shall be portion marked in accordance with the information being presented. Vendors working off-site on COTS products do not need clearances for purposes of this contract.

(U) In accordance with DD Form 254, Contractor personnel are required to have TS/SCI clearances for access to NGA facilities and when performing maintenance activities within classified environments. NGA will sponsor security clearances and Common Access Cards (CAC) for required program personnel. Security requirements shall be accomplished by the Contractor and will be per DoD Information Technology Security Certification and Accreditation Process (DIACAP). The DD Form 254, Contract Security Classification Specification, is the document used by NGA for NGA Contractor security.

(U) Safety

(U) The Contractor shall adhere to all applicable federal, state, and local laws and regulations for fire protection, safety, and occupational health and industrial hygiene. The Contractor must comply with all Department of Labor and OSHA rules and regulations 26CFR 19.0 (General Industries).

(U) Government Furnished Equipment/Information (GFE/GFI)

(U) The government will provide the technical and operational documentation for the currently fielded TFDM system.

(U) The contractor shall define the GFE/GFI required to support the execution of their proposed approach.

The Government will provide access to NGA facilities and other contractor facilities (to include badges) for cleared personnel working this effort. The Government will provide access to NGA networks for information exchange (e-mail capability) but will not provide permanent/assigned computer resources or office space for anything other than full-time O&S and on-site support.

(U) Example Test Process

(U) A minor release is one that is usually as result of a patch where no associated software or system is affected; the software’s version number is usually incremented such as v2.4.1 to v2.4.2.

Figure A-1 - (U) Test Process Minor

(U) A major release is one that is usually as result of a complex update and/or associated software or system is affected; the software’s version number is usually incremented such as v2.4 to v2.5.

Figure A-2 - (U) Test Process Major Page A-2 image2.png image3.png image4.png image1.jpeg