SOW-SCDS_Follow-On_FY24_V17_Clean_Draft.docx

UNCLASSIFIED

Source Content Dissemination Services Statement of Work (SOW)

01 November 2022 Prepared By: NGA/ST

Document Change History 01 NOV 2022

Table of Contents

Introduction Purpose

(U) This Statement of Work for the Source Content Dissemination Services (SCDS) describes the technical expertise and support required to provide for the operations and maintenance of the Agency’s dissemination service, which is intended to provide all users with an expedited ability to search, locate, and retrieve Source Foundation products. Potential evolutionary development of the SCDS system is also included in this SOW as options.

(U) Support for all capabilities and mission spaces should be in alignment with the following:

· NGA Strategy 2025

· NGA Technology Strategy

· NGA Software Way

SCDS Specific Terminology

(U) Purpose: Several phrases commonly used by communities that develop Foundation GEOINT (FG) have unique meanings within the SCDS program. This section intends to clarify these areas of potential misunderstanding.

(U) Ingest: Loading of FG products into S3 buckets for virus scanning, and the conditioning of those products to ensure their safe and secure archiving, and their searchability, discoverability and retrievability.

(U) Dissemination: Using of standards-compliant microservices to electronically disseminate FG artifacts in a system that allows for the flexibility to account for Common Access Card (CAC) users and GEOAxIS Identity and Access Management (IdAM) users, as well as challenges faced by resource limited customers. In terms of SCDS, digital dissemination is a front-end user function. SCDS does not provide for physical product dissemination (i.e. Print on Demand). Electronic dissemination will be handled through SCDS, hard-copy dissemination will remain a function handled by DLA. SCDS does not impact the development of FG products within NGA.

(U) Visualization: Rendering of FG product thumbnails for user exploration. SCDS does not provide layers for user manipulation in the system. SCDS will manage data flows of products and data; “visualization” in the end users’ context will remain within that product’s specified application (for example, SCDS will allow for discoverability on Map of the World using visualization resources, but the Map of the World application itself will allow for end user visualization resources).

(U) Product: Within the construct of SCDS, “products” refers to FG artifacts developed for wider dissemination among NGA partners. For the purpose of this document, an inclusive list of Products is provided in Table 1 at the end of this document.

Background

(U) The Source GEOINT Information Office (ST) developed SCDS to unify the handling, storage, and dissemination of FG in accordance with the FY22-26 Consolidated Intelligence Guidance (CIG) , and to meet the intent of the Director of National Intelligence’s “Intelligence Community Information Technology Enterprise (IC-ITE) Strategy.” SCDS provides NGA customers (IC, Department of Defense (DoD), and other Federal Government Agencies across the entire National System for Geospatial Intelligence (NSG) and Allied System for Geospatial Intelligence (ASG) with an easy to use, unified point of access to discover and retrieve FG products. SCDS’s unified access to FG products will replace numerous customer specific access points and will simplify the dissemination processes.

(U) This Statement of Work (SOW) describes the technical expertise, support and services required to maintain, operate, sustain, and potentially improve current and future services and capabilities, as a mission critical National Geospatial-Intelligence Agency (NGA) system capable of Ingest, Discovery, Cataloguing, and Dissemination of Geospatial Content.

(U) This effort is a successor contract to the SCDS family of contracts (i.e. Data Core Development Team [CDT], Foundation CDT, NGA Product Dissemination), and includes options for the evolutionary development of SCDS beyond its current construct.

Scope

(U) Provide technical expertise required to maintain, operate, sustain, implement and improve current and future services and capabilities developed and sustained by the SCDS.

(U) SCDS delivers capabilities and services to the UNCLASSIFIED, SECRET, and TOP SECRET networks.

(U) The Contractor will inherit code spanning multiple core operational capabilities (see below). The Contractor must maintain, operate, sustain, and potentially improve current and future services and capabilities .

(U) SCDS CORE CAPABILITIES (A MORE DETAILED EXPLANATION OF THESE CORE CAPABILITIES ARE CONTAINED IN APPENDIX A OF THIS SOW)

· Ingest: Scanning, conditioning, tagging, and movement to cloud storage

· Disclosure & Release: Foundation GEOINT Discovery and Release Tool (FGDRT) - Adjudication of NGA FG sharing requirements with foreign partners

· Source Foundation Catalog (SFC): Automated database for sharing content with NGA partners

· Dissemination Services: Allows for retrieval of ingested materials through organized search parameters established in the SFC

· Enterprise File Delivery: Support users’ requests for Source Foundation products, and provides for electronic delivery of those products on a one time, or recurring basis

· Mission Planning System Updater (MPSU): Allows users that subscribe to specific products to inventory differences between subscription holdings on the gateway vs. the customer’s holdings to update their local system

· Trans Shipper: Manages data flows between NGA and DLA to ensure regular updates

· Saber: Unified User Interface (UI) for NGA partners to access and retrieve products from SCDS

(U) This SOW is divided into three major efforts:

· OPERATIONS AND MAINTENANCE (REF SECTION 3.1)

(U) Operations and Management (O&M) effort is to acquire information systems’ FTEs to provide long term support, sustainment and maintenance to the SCDS system. Support, sustainment and maintenance taskings will include, but are not limited to updating SCDS system to align with NGA or USG updated requirements, conducting regular and adaptive maintenance, patches, code modernization, UI modification/refactoring, and version upgrades. In order to execute this tasking, the contractor must have or be able to obtain a service level agreement in place with NGA’s enterprise service center.

· GATEWAY MODERNIZATION (REF SECTION 3.2)

(U) Gateway Modernization taskings will include, but are not limited to resolving outstanding technical issues pertaining to final operationalization of SCDS system, ensuring SCDS coordination with the Saber User Interface and metrics team, and loading of historical archives into SCDS discoverable locales, to include proper conditioning and tagging of artifacts.

· EXPANSION OF SCDS FUNCTIONALITY (REF SECTION 3.3)

(U) Taskings for expansion of SCDS are options, and may include, but are not limited to, replacing and realigning SCDS workflows/APIs for optimization, automation of large bulk order for custom media, or expanding SCDS functionality to ingest, condition and provide for discoverability/dissemination for novel NGA product lines.

1.0 PERFORMANCE REQUIREMENTS

(U) The following sections describe the list of services that must be provided in support of this contract.

Operations and Maintenance

(U) Ensuring the operations, maintenance and sustainment of the SCDS system. Taskings (to include documentation) may include, but are not limited to:

· (U) Application Modernization: Refactoring or rewriting codes to reduce and/or eliminate technical debt.

· (U) Operational Support Tasks: Tasks required to support operational hardware and software, and ensure the operational capabilities are running efficiently and effectively (e.g. system health monitoring, ticket resolution, content/data dissemination, rapid content exposure for crisis response, chat room monitoring (i.e. RocketChat) and response).

· (U) Adaptive Maintenance: Modification to keep an application, system, or data repository usable in a changed or changing environment (i.e. re-architecting)

· (U) Corrective Maintenance: Identify, isolate and/or rectify a fault or problem to restore and/or correct the application, system, or data

· (U) Perfective Maintenance: Modification to improve performance and/or maintainability.

· (U) Technology Insertion: Incorporating new or improved technology.

· (U) Technology Refreshment: Modify SCDS cloud infrastructure or software for continued supportability throughout the lifecycle, as required.

· (U) Security Patching: Modification of systems and processes to streamline/accelerate the delivery and application of critical and non-critical security patches to operational systems.

· (U) UI Modification/Refactoring: Modification of SCDS/Saber interface based upon NGA or Users requirements to maintain certification or enhance User experience.

(U) NOTE: In order to execute this tasking, provider must have or be able to obtain a Service Level Agreement in place with NGA’s Enterprise Service Center.

1.1 GATEWAY MODERNIZATION

(U) Final optimization of the SCDS system. Taskings may include, but are not limited to resolution of outstanding punch list items pertaining to the SCDS system (SCDS architecture available in Appendix A), ensuring the SCDS system will effectively interact with Saber to provide a unified UI experience, ensuring metrics data flows within SCDS, and loading of historical archives into SCDS discoverable locales, to include proper conditioning and tagging of artifacts. Taskings (to include documentation) may include, but are not limited to:

1.1.1 Punchlist:

· (U) TBD – will be updated based on current contract completion milestones (UI and API handler switchovers)

1.1.2 Interface with Saber UI:

· (U) Contractor must work with the Saber team to ensure that all Source Foundation Products (Table 1) are either located in an SCDS discoverable location, or that Saber has connection to those sources that are not SCDS discoverable (by direction of the Contracting Officer (CO))

· (U) Contractor must ensure the long term sustainability of the SCDS system, to include Saber (once development is completed)

1.1.3 Metrics data flow:

· (U) Contractor must ensure that Business Analytics/Business Intelligence (BA/BI) and systems dedicated to support can access, assess and report on SCDS processed requests through SFC storage and API function. Such data access via API and/or database access (SQL, Oracle or other within SCDS) must include at a minimum:

· Saber customer database table

· Saber customer orders database tables (All FG from any source within Saber/SCDS)

· Event log occurrences for content streamed or otherwise sent from SCDS to external party/system (including product line and/or service and customer identifying information).

· (U) Contractor must update the Saber user interface menus per BA/BI requests that are validated by the PMO.

1.1.4 Cataloging:

· (U) Contractor must assure the effective ingest of Source Foundation products (Table 1), and other materials (as directed by the CO) to ensure their discoverability within SCDS.

Expansion of SCDS Functionality and/or Inclusion of Additional FG Materials

(U) Upon direction of the CO, prepare cost and technical estimates for NGA defined requirements pertaining to the further development of inherent SCDS Capabilities, or expansion of SCDS capabilities. Taskings may include, but are not limited to:

Expansion of SCDS Functionality:

Replace GDP API

Replace MPSU Rest Service

Replace MPSU Manifest Updater

Replace Transhipper API

Enhance Data Access Data Integrity

Creation of BA/BI data access API for FGDRT

Provide links to data oriented services (VCPS, NOME, MoW, etc.) to enable access to data and building of discrete provisional products

Provide geo-referenced and textual search means for discovery by users

SCDS synchronization with DLA (better wording from JP)

Integration and data flow into MEBS

Assured positioning, navigation, timing, and targeting (APNT&T)

Automation of large bulk order for custom media

Expand SCDS capacity to ingest, condition, store, discover, retrieve and deliver additional source foundation products, or entirely new product lines from wider NGA

Technical Expertise and Subject Matter Expert Support

(U) Contractor must provide technical expertise and support for the capabilities at GEOINT Services operations model milestones and customer engagement meetings.

General Requirements Program Management

(U) The contractor must provide all the tools, manpower and support required for successful execution of the contract. The contractor must provide a recommendation for tools, manpower, and support required for successful execution of the contract.

Kick-Off Meeting

(U) The contractor must support a kick-off meeting for the government and team members within one week of contract start date. Contractor will use industry best standards for test driven development. The contractor will introduce team members and staff and present and discuss organizational structure and administrative operations pertinent to this CDT.

CDT Management Reviews

(U) The contractor must participate in formal activity and program management reviews monthly at NGA East or West facilities (unless otherwise specified) and as directed by the Contracting Officer (CO). Management Reviews can be held virtually (WebEx, Zoom) on low/high side as directed by the CO (Government).

Financial Reporting CDRL 001

(U) The contractor must submit cost/financial reports monthly in a contractor-developed format that is subject to Government approval. This report must provide the Contracting Officer Representative (COR) with an actionable understanding of the contractor’s unliquidated obligations and burn rates by FY; these reports are to be reviewed with the COR during monthly Integrated Program Manager Reviews. The COR may request reviews of these deliverables outside of the quarterly schedule, as needed.

Personnel

(U) The contractor must establish a process to identify additional personnel when requested by the government within 30 days and assign appropriate resources to effectively administer the requirement. The contractor must provide the government notification within 30 days of personnel leaving the effort and backfill their positions within 30 days. The contractor must be responsible for any subcontract management necessary to integrate work performed on this contract and must be responsible and accountable for subcontractor performance.

Documentation CDRL 002

(U) The contractor must provide documentation related to all technical efforts executed under this contract. The contractor will deliver the documentation to the COR, product manager and/or others as requested by the COR or product manager. Documentation may include but is not limited to:

· Punch list close out actions

· Code and code artifacts

· Security documentation updates

· Verification of SCDS/Saber interface

· Verification of SCDS/BABI interface

· Documentation of loaded archived materials

· Capability performance test plans and/or results

· Risk Management Plan

· Staffing Plan Business Relations

(U) The contractor must have a single point of contact (with two designated backups) between the Government and contractor personnel to support business relations. The contractor must integrate and coordinate all activity required to execute this contract and manage the timeliness, completeness, and quality of problem identification. The contractor must provide corrective action plans, timely identification of issues (1 business day), and effective management of subcontractors.

Risk Management CDRL 003

(U) The contractor must develop and utilize its risk management plan (procedures, techniques, controls, and metrics) to provide for the early identification of CDT management risks; quantify risks in terms of cost, performance, and schedule impact; and to implement risk mitigations. Staffing risks must be a topic of discussion during CDT management reviews.

Other Direct Costs (O&M) Travel (Cost reimbursable – No Fee)

(U) The contractor may be required to travel to various locations within the Continental United States (CONUS) and Outside the Continental United States (OCONUS) in performance of this contract. All allowable travel arrangements must include a detailed travel estimate and be pre-approved by the CO and/or Contracting Office Representative (COR) prior to all travel. All allowable travel costs will be reimbursed based on costs incurred in accordance with the Joint Travel Regulations (JTR).

(U) The contractor must travel using the lowest cost mode of transportation commensurate with the mission requirements. When necessary to use air travel, the contractor must use the tourist class, economy class, or similar accommodations to the extent they are available and commensurate with the mission requirements and IAW with the JTR (civilians).

(U) All contractor personnel traveling to the applicable OCONUS locations must be responsible for completion of all required training and approvals prior to travel / deployment.

Cloud Services (Cost reimbursable – No Fee)

(U) The contractor may be required to purchase Amazon Web Services (AWS) government cloud compute and storage (or other product) for development and testing of the Data Services products. All purchases must be pre-approved by the CO and the COR prior to purchase. All AWS costs will be reimbursed based on costs incurred (cost reimbursement (CR) no fee basis).

(U) AWS Government cloud compute and storage (referenced above) is authorized only for development and testing. Stage and production environments should utilize GEOINT Services’ C2S resources on NIPR, SIPR, and JWICS.

(U) The contractor must make every effort to optimize AWS cloud usage to balance performance with cloud storage and compute costs. The contractor must provide the AWS cost breakdown along with the monthly reports. Efforts associated with this tasking should be included in the monthly financial reporting referenced in section 4.2 of this SOW.

(U) Government Furnished Software/Information (GFX/I)

(U) The Government will provide development and sustainment server environments (primarily Linux, Windows, and AWS/C2S), the software baselines, database licenses, and the software needed for configuration management.

Data Management

(U) The contractor must establish, document, and maintain all data for the program and provide data as directed by the government. The contractor must use sound data management discipline for developing, acquiring, controlling and delivering all required technical, management and other data. The contractor must ensure on-time delivery of data; data quality; accurate updates/revisions and corrections to data as required; and proper identification, marking and control of proprietary, For Official Use Only (FOUO), and classified data.

The Government will provide the Contractor a SCDS system, architecture and software as part of a Government Furnished Software (GFX) package.

Security Requirements

(U) The contractor team must include a minimum of three (3) Top Secret/Sensitive Compartmented Information (TS/SCI) cleared personnel for tasks as defined by the Government. Development activities may occur on both classified and unclassified domains at government and/or agreed upon contractor facilities in an area/space cleared for that work or above.

Unclassified Work Performance Security Requirements:

(U) Uncleared personnel are authorized to perform work on the GEOINT Service Data Services contract up to the UNCLASSIFIED level (with access to DoD Controlled Unclassified Information (CUI)).

(U) Any uncleared contractor who is working with CUI information must receive a favorable HSPD-12 or HSPD-12 tier 1 adjudication prior to accessing CUI information. Contractor personnel who require access for 60 days or less must receive a favorable HSPD-12 adjudication.

(U) NGA will sponsor the HSPD-12 or HSPD-12 Tier 1 background investigation for required program personnel.

(U) Only United States personnel (foreign nationals with the contract company are prohibited from working on this contract) are authorized to perform work or have access to the information for this contract.

(U) The Contractor must portion mark all material in accordance with the information.

(U) Contractors must abide by the DD Form 254 - Contract Security Classification Specification, and applicable security policies and regulations.

(U) The Contractor must follow all applicable NGA, IC, DoD and foreign mission partner information security, operational security, and cybersecurity policies and guidance when accessing and transmitting data over networks during performance of contractual requirements.

(U) The contractor will have access up to the appropriate domains, up to TS/SCI (as needed) while on this contract. In the performance of this, contractor will have access to and be exposed to DoD CUI. The contractor must not release to anyone outside the Contractor’s organization any unclassified information, regardless of medium (e.g. film, tape, document), pertaining to any part of this contract or any program related to this contract, unless the Contracting Officer has given prior written approval or in performance of a project that has been scoped and negotiated by NGA with the contractor. Release and disclosure guidance provided to subcontractors must be “all release and disclosure request must be submitted through the prime contractor to NGA”.

(U) All government furnished information released to the contractor or created in the performance of this contract will be destroyed by the contractor or returned to the NGA upon termination of the contract; or when no longer required in the performance of the contract as directed by the COR.

(U) Uncleared contractors visiting NGA, Other Government Agencies (OGA), or foreign mission partner facilities will receive the appropriate visitor badge and will be escorted as appropriate. The visitor badge must be returned at the end of each visit day. NOTE: NGA, OGA, and foreign mission partners reserve the right to refuse access to any personnel.

(U) Contractor personnel are forbidden from bringing prohibited and/or unauthorized, Portable Electronic Devices (PEDs) items on and/or into on any NGA, OGA, or foreign mission partner installation or any government owned/sponsored office/working location covered under this contract. A list of PEDs includes, but is not limited to cell phones, cameras, two-way pagers, laptops, recorders (digital, tape, etc.), flash drives, or any other kind of removable media, without prior approval and approval paperwork from NGA. See NGA instructions/regulations/policy for a full list of prohibited and unauthorized items. Disciplinary action will be determined based on the severity of the violation.

Classified Work Performance Security Requirements

(U) Contractor personnel performing classified work on the GEOINT Service Data Services contract are required to have active TS/SCI clearances for access to NGA and OGA facilities. Clearances are required for performing duties within classified environments, and for access to classified NGA and OGA computer systems. Contractors are subject to a Counterintelligence Polygraph as requested by the Government. NGA will sponsor security clearances, NGA Badge, Common Access Cards (CAC), and other required items (Example: hangtag) for required program personnel.

(U) Contractors must abide by the DD Form 254 - Contract Security Classification Specification, and applicable security policies and regulations.

(U) The Contractor must follow all applicable NGA, IC, DoD and foreign mission partner information security, operational security, and cybersecurity policies and guidance when accessing and transmitting data over networks during performance of contractual requirements.

(U) The Contractor must inform the Government when its employees no longer support the contract (see DD254). The Government desires notification prior to the day the individual no longer supports the contract, but requires notification no later than the day support ends. If contract personnel will no longer be supporting NGA via an NGA contract, all Government-issued items must be turned into the NGA NCE Workforce Support Center, NGA Site Security Office, or the COR. If contract personnel are unable to turn these items into the NCE Workforce Support Center, NGA Site Security Office, or COR then it is the contractor’s security office responsibility to collect the items from the individual to include completing any debriefing paperwork needed and notify and seek further direction from the COR or Industrial Security. If the Contractor debriefs the employee, the Contractor must send a copy of the debriefing statement, plus any Government items (IE: NGA Badge, CAC, Courier Card, parking hangtags, etc.) within four (4) business days (timeline may be extended with authorized documented exceptions by NGA Security) to an NGA Site Security Office or the NCE Workforce Support Center.

(U) All government furnished information released to the contractor or created in the performance of this contract will be destroyed by the contractor or returned to the NGA upon termination of the contract; or when no longer required in the performance of the contract as directed by the COR.

(U) Any SCI work performed at contract sites must be performed in either an NGA accredited Sensitive Compartmented Information Facility (SCIF) for this effort or an OGA SCIF that has either a Memorandum of Agreement (MOA), Memorandum of Understanding (MOU), Joint Use Agreement or Co-Use Agreement with NGA for this effort.

(U) Other than the locations listed in the paragraph above, any classified work performed at a location that is not an NGA facility or listed in the signed/approved contractor/sub-contractor cleared facility, must be approved by the CO.

Information Handling

(U) The Contractor will comply with the NGA, DoD, IC, and local policies and regulations (to include, but not limited to, the Consolidated NGA Security Classification Guide (CoNGA) to properly mark (to include portion marking) classified, unclassified, and CUI information, documentation, media, etc.

(U) Markings will be in accordance with the lowest security classification possible to ensure the confidentiality and integrity for greatest release to partners in accordance with NGA marking guides for classified information.

(U) Information handling will be in accordance with applicable security policy and regulations, and NGA compliance documents.

Non-Disclosure Agreements

(U) The contractor must require all employees, prime and subcontractors, sign the attached non-disclosure agreement (NDA) prior to starting work. The purpose of the NDA is to prevent disclosure of sensitive Government information the contractor may be exposed to through performance of this contract. Copies of signed NDAs must be submitted to the CO and the COR.

Period of Performance

(U) The period of performance (PoP) for this requirement is one (1), 12-month Base Period, and four (4), 12-month option periods.

Place of Performance

(U) The primary place of performance will be the contractor facility, preferably within 15 miles of NGA East (National Capital Region) or NGA West (St Louis). The specific location will be agreed upon at contract award as there is no space on-site for contractors.

Foreign Travel Requirements Theatre/Country Clearances

(U) The contractor must obtain special theatre and/or country clearances and comply with theatre/country specific requirements for applicable OCONUS work. The DoD 4500.54-E and DoD Foreign Clearance Guide states the requirements for travel to specific countries.

Passports, Visas, Licenses, and Permits

(U) The contractor must be responsible for timely and complete submittal of the necessary information and forms directly to the appropriate Government Agency for the required passports, visas, licenses, and permits. The contractor must be responsible for the sponsorship of its employees and must process said permits directly through the appropriate Government Agency.

Export Compliance

(U) The National Geospatial-Intelligence College (NGC) workforce (civilian, contractor, and military) provides GEOINT training and education to the US National Security and civilian communities, as well as to America's global allies. As such, NGC must be able to maintain compliance with US export laws and regulations. The contractor must document compliance with the Arms Export Control Act and the International Traffic in Arms Regulations (22 C.F.R. Parts 120-130) as required by the government.

Associate contractor Agreements (ACA)

(U) Throughout the course of the contract, the contractor may be required to work with, or within proximity to, other contractors within the Software Environment or at other Contractor facilities.

(U) The contractor must enter into Associate Contractor Agreements (ACA) with applicable third party contractors and other stakeholders after contract award for any portion of the contract requiring joint participation in the accomplishment of the requirement. The agreements must include the basis for sharing information, data, technical knowledge, expertise and/or resources essential to this effort, which must ensure the greatest degree of cooperation to meet the terms of the contract. The Government will provide specific names of contractors to the contractor as needed.

(U) ACAs must include, but not limited to, the following general information:

(U) Identify the associate contractors and their relationships. Identify the program involved and the relevant Government contracts of the associate contractors.

(U) Describe the associate contractor interfaces by general subject matter. Specify the categories of information to be exchanged or support to be provided. Include the expiration date (or event) of the ACA. Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

(U) The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor. Liability for the improper disclosure of any proprietary data contained in or referenced by any ACA must rest with the parties to the ACA and not the Government. All costs associated with the ACAs are included in the negotiated cost of this contract. ACAs may be amended as required by the Government during the performance of this contract. The contractor must submit copies of all ACAs to the Contracting Officer.

Information Assurance Contractor Training and Certification CDRL 011

(U) The contractor must comply with the Information Assurance Contractor Training and Certification requirements as outlined in DFARS clause 252.239-7001 for all applicable labor categories under this contract.

(U) Contractor is responsible for all training costs for new or existing personnel, except for mandatory NGA training.

Contract Transition Off Plan CDRL 012 The Contractor must provide a Contract Transition Off Plan for transitioning work to the Government’s follow-on provider for operation and maintenance of the system. In accordance with the Government-approved plan, the Contractor must assist the Government in planning and implementing a complete transition from this contract vehicle to the follow-on providers. This must include formal and informal coordination with Government staff and follow-on provider personnel. The Contract Transition Off Plan should provide for the return of all GFE and GFI, and the delivery to the Government of all software, documentation, data, and test software developed under this contract. The plan should provide for all activities (e.g., training) necessary to enable the Government (or Government providers) to conduct the operations and maintenance of the delivered capabilities and completion of any outstanding work. The Contract Transition Off Plan must be delivered to the Government NLT 60 calendar days before the end of the contract PoP for Government approval and concurrence.

Table 1 NGA-SF Products for Ingest into Source Content Dissemination Services Products

SMR

Table 2 Glossary

UNCLASSIFIED

image1.jpeg image2.png