20250221_U_SABER_III_BPA_SOW_DRAFT.pdf

UNCLASSIFIED

STATEMENT OF WORK (SOW)

For the

Software Aqua Badge Engineering Resources III (SABER III)

Blanket Purchase Agreement (BPA)

Version 1.0

21 February 2025

Document Change History

Date

Sections

Changed Reason for Change Author

Revision

Number

Table of Contents

1 (U) Introduction

2 (U) Background

3 (U) Scope

3.1 (U) The DevCorps Aqua Construct for SABER III

3.2 (U) Development and Software Engineering Capability

3.3 (U) Software Developer Capability:

4 (U) Period and Place of Performance (PoP)

4.1 (U) Period of Performance

4.2 (U) Place of Performance

4.3 (U) Telework

5 (U) Capability Requirements

5.1 (U) Assessments and Evaluations

5.2 (U) Designing and Engineering

5.3 (U) Agile Development

5.4 (U) Continuous Integration (CI)/Continuous Delivery (CD)/pipeline configuration and utilization

5.5 (U) Application Development

5.5.1 (U) Front End Development

5.5.2 (U) Server-Side Development

5.5.3 (U) API Development

5.5.4 (U) Testing/TDD (unit, integration, functional, etc.)

5.5.5 (U) Security and Accreditation

5.6 (U) System Integration

5.7 (U) Operations and Sustainment

5.7.1 (U) O&S Support

5.7.2 (U) O&S Test and Evaluation

5.7.3 (U) O&S Security and Accreditation

5.7.4 (U) Data Sustainment and Format

5.8 (U) Documentation/Template development and maintenance

6 (U) General Requirements and Guidance

6.1 (U) Staffing

6.1.1 (U) Labor Category (LCAT) Requirements

6.1.2 Key Personnel

6.2 (U) Invoice Billing Break-Out Reporting Requirement

6.3 (U) Security

6.3.1 (U) Association and Security Requirements

6.3.2 (U) Classified Work Performance Security Requirements

6.3.3 (U) Physical Security

6.3.4 (U) Information Handling

6.4 (U) Data Rights

6.5 (U) Government Furnished/Contractor Acquired Property Management

6.6 (U) Compliance and Reference Documents

6.7 (U) Travel

6.8 (U) Recognized Federal Holidays

6.9 (U) Hours of Operation

6.10 (U) Deliverables

6.10.1 (U) Deliverables Matrix

6.10.2 (U) General Deliverable Requirements

6.10.3 (U) Format of Deliverables

7 (U) ORDER PROCESS

7.1 (U) General

7.2 (U) Competitive Ordering Process

7.3 (U) Unauthorized Work

7.3.1 (U) Order Funding Restrictions

8 (U) ACRONYMS

1 (U) Introduction

(U) The overall objective of Software Aqua Badge Engineering Resources (SABER) is to provide software development capacity in support of the many NGA existing and emerging capabilities.

This additional capacity will provide support to various activities across the agency from design, development and modernization of applications and services to operations and sustainment (O&S) of existing or newly deployed applications. The SABER requirement is comprised of a set of software development labor categories capable of solving software development and engineering problem sets within the scope of this document. These software labor resources will be expected to deliver software and services in accordance with the principles and methodologies described within this document.

2 (U) Background

(U) NGA is both a Combat Support Agency (CSA) of the Department of Defense (DoD) and a member of the United States Intelligence Community (IC). As a CSA, NGA provides critical support to the national decision-making process and the operational readiness of America’s military forces. As a member of the IC, the NGA mission is to provide timely, relevant, and accurate GEOINT in support of national security objectives. As such, NGA is primarily responsible for the associated Planning, Collection, Processing, Analysis, Dissemination (PCPAD) of GEOINT data and information on behalf of the national level decision makers, IC and DoD customers. To remain operationally effective within a fluid, unconventional domain, NGA must advance in capability and analytic methodology.

(U) The GEOINT Services organization resides within NGA’s Directorate of Chief Information

Office and Technology (CIO-T). GEOINT Services is tasked with designing, developing and delivering geospatial capabilities of common concern on behalf of our National System for

Geospatial-Intelligence (NSG) mission partners. These missions enabling capabilities deliver critical functionality to include geospatial applications and data services across a multitude of operational domains.

(U) DevCorps, one of the Divisions within GEOINT Services, delivers accessible, intuitive, and interoperable GEOINT software capabilities and services to our NSG mission partners. To accomplish this, DevCorps employs agile methodology principles and persistent customers engagement, utilizing a cadre of in-house government software development experts, to deliver user-focused and mission-oriented software solutions. This approach underscores DevCorps’ position as the foremost standard in NGA’s a digital maker culture.

3 (U) Scope

(U) The SABER III Contractor-provided software developers shall develop, modify, integrate, test, deploy and/or maintain government-owned software and applications exclusively utilizing the published NGA software way and DevCorps standards, as applicable. Paragraph 3.1 discusses the development team composition within DevCorps, commonly referred to as “the aqua construct.”

To meet agency requirements the scope is addressed in paragraphs 3.2 and 3.3 below.

3.1 (U) The DevCorps Aqua Construct for SABER III

(U) The following drawing (Figure 1) depicts a small example of the make-up of potential government and contractor (Aqua) software developer teams, to include the government technical management and oversight. In the SABER III construct, it is intended that Contractor-provided software development staff can fully support the governments development objectives.

Additionally, at the Senior and Principal levels, it is expected that the Contractor-provided staff may provide mentorship, problem-solving, and/or team leadership, when necessary. However, at no time will Contractor-provided software development staff conduct management or oversight of government personnel.

(U) In this Aqua construct, the government technical leads provide all technical direction and guidance to development teams, while the government contract PM, COR, and CO provide administrative and performance evaluation, direction, and guidance. It is intended that teams are a mix of government and Contractor developers as much as feasible. However, on occasion, a team may consist of all government developers, or even all Contractor-provided staff developers.

Additionally, it is expected that within this construct there is an evolving development CONOPS as described in Table 6.3, Reference 1 of this document, such as:

• General guidelines for development

• Integration with existing DevOps tools and deployment platforms

• General development recommendations

• Source code deliveries

Figure 1: DevCorps AQUA Construct – Technical Management

3.2 (U) Development and Software Engineering Capability

(U) All development and software engineering activities require applying the NGA “Software

Way” standards and DevCorps software methodologies in accordance with the task(s) identified in this SOW. The overarching goal is to provide geospatial capabilities that support the technologies required to advance NGA mission-related efforts. During the period of performance within a specified purchase order, the Contractor-provided software development staff shall:

• (U) Provide software development and engineering, technical assessment, software operations, maintenance and sustainment, and other required software activities, as deemed necessary by the Government. Contract staff shall leverage Commercial Off the Shelf

(COTS), Government Off-the-Shelf (GOTS), Free and Open Source (FOSS), NGA’s

DevOps toolkit, the NGA Platform as a Service (PaaS), and/or other technologies to complete all the tasks associated with software deliverables within individual DevCorps project backlogs. SABER III will focus on, but not be limited to, the following areas of need within NGA:

o (U) Software development support of current and emerging needs in GEOINT Analytic capabilities.

o (U) Software development support of current and emerging needs in GEOINT Collection.

o (U) Software development support of current and emerging needs in GEOINT Foundation data systems.

o (U) Software development support of current and emerging needs in GEOINT Enterprise data capabilities.

o (U) Software development support of current and emerging needs for automation of security compliance, security acceptance testing, and authorization for operation deployment. Tasks must include the construction and modification of automated software tests for applicable National Institute for Standards and Technology (NIST) and ICD requirements, the integration into multi-level security DevOps pipelines in support of continuous integration and continuous deployment, and the development of tools for monitoring said pipeline.

o (U) Software development and engineering tasks in support of improving geospatial data dissemination mechanisms.

o (U) Configuring and deploying GPU-enabled inferencing engines to support use cases such as hosting Large Language Models (LLMs).

o (U) Developing custom code integrations with deployed inferencing engine APIs.

o (U) Perform software development and engineering tasks in support of the following purposes:

▪ (U) Data management

▪ (U) Data ingest

▪ (U) Data cataloging

▪ (U) Analytic processing

▪ (U) Data transformation

▪ (U) Data storage methods

▪ (U) Data dissemination

3.3 (U) Software Developer Capability:

(U) The Contractor shall provide qualified personnel to the SABER III vehicle that are capable of supporting the completion of software development and engineering tasks associated with

GEOINT functions and capabilities of the DevCorps backlog. In addition, the Contractor-provided software development staff shall ensure the DevCorps developed software demonstrates its applicability to the Authorization to Operate (ATO) initiative by advancing the capabilities needed by the Enterprise Capability Document. The following three software developer labor categories (and further defined in Section 6.1.1) have been identified to achieve these effects:

• (U) Software Engineer (Principal – Software Engineer V): Individual must have exceptional domain knowledge and substantial hands-on experience in developing, implementing and leading software applications and teams. As a Principal Software

Engineer, this labor competency is responsible for creating, maintaining and/or improving the software code, with duties to design and update software databases under contract and direction from the assigned Government Lead. The Principal Software Engineer maintains broad awareness of the functions, responsibilities and demands levied on the DevCorps and is capable of providing input to and communicating strategic direction in concurrence with Government leaders. The Principal Software Engineer has a demonstrated understanding of the full lifecycle of software development and is able to communicate it effectively to others. Clear communication skills are required such that highly technical and complex concepts and methods can be effectively transmitted to a non-technical and/or junior officer audience. Astute ability in writing test scripts, test-driven development, in an

Agile software development environment, where built in automated test procedures are paramount and continuous integration of software and continuous delivery of software, to the Government is the culture.

• (U) Software Engineer (Senior – Software Engineer IV): Individual must have broad domain knowledge and extensive hands-on experience in developing, implementing and leading software programs. As a senior developer, this labor competency is responsible for creating, maintaining and/or improving the performance of existing software code, with duties to design and update software databases under contract and direction from the assigned Government Lead. Astute ability in writing test scripts, and test-driven development in an agile software development environment, where built-in automated test procedures are paramount and continuous integration of software and continuous delivery of software.

• (U) Software Engineer (Mid – Software Engineer III): Individual must have moderate domain knowledge and ample hands-on experience in developing, implementing software programs. As a mid-level developer, this labor competency is responsible for creating, maintaining and/or improving the performance of existing software code, with duties to write and update software code and databases under contract and direction from the assigned Government Lead. Clear communication skills are required. Proven ability writing test scripts, test driven development, in an agile software development environment, where building in automated test procedures in addition to functional code are paramount to continuous integration and continuous delivery of software.

• (U) Software Engineer (Junior – Software Engineer II): Individual must have a basic understanding of domain knowledge with some hands-on experience in developing, implementing software programs. As a Junior-level developer, this labor competency is responsible for supporting the creation, maintenance and/or improvement of the performance of existing software code, with duties to write and update software code and databases under contract and direction from the assigned Government Lead. Clear communication skills are required. Some experience writing test scripts, test driven development, in an agile software development environment, where building in automated test procedures in addition to functional code are paramount to continuous integration and continuous delivery of software.

4 (U) Period and Place of Performance (PoP)

4.1 (U) Period of Performance

(U) The base ordering period shall be 60 months from BPA award. The Period of Performance will be specified in the individual orders. No order shall extend past 12 months from the end of the ordering period.

4.2 (U) Place of Performance

(U) All work will be performed within the United States with no anticipated travel. Development work will primarily take place in/around the NGA Saint Louis facilities, in St. Louis, MO.

However, a potential exists for some development work to occur in/around the NGA Washington facilities in Springfield, VA or within Contractor-provided facilities. Actual location of work will be further defined in individual orders.

(U) Any Government-provided on-site facility requirements, including Government Furnished

Equipment (GFE), will be defined in the individual orders. If necessary, the requirement for

Contractor facility (i.e. SCIF) use will be identified in individual orders.

4.3 (U) Telework

(U) Telework development opportunities will be defined in individual orders when authorized by the Government PM, COR, or CO.

• (U) In the event that telework is authorized in an individual order, it will be done so with the assumption development will be delivered via an unclassified environment and then further transferred into secure networks in accordance with Government-provided pre-established processes and standards.

• (U) Unclassified telework, although generally allowable in accordance with Federal

Acquisition Regulations (FAR) Part 7.108, will only be authorized on a case-by-case basis.

All work should be considered on-site, unless otherwise specified in the individual order or approved through the PM, COR, or CO.

• (U) Regardless of telework authorization, the vendor’s personnel must be capable and responsible for performing all classified requirements of the contract in an appropriate facility.

• (U) Telework is only allowed at the locations (local commuting area) identified in the individual order for each position approved for telework. Teleworking from a different location shall not be authorized.

• (U) Contractor-provided software development staff are able to be recalled to the duty site from authorized telework locations at any time, as determined by the PM, COR, or CO.

• (U) A Government-approved telework plan shall be in place prior to telework that shows direct traceability to the work statements duties and tasking. The Contractor must submit a telework plan ten (10) business days prior to the requested telework start date (Table 6.4, CDRL B006). Any telework that takes place without written approval from the PM, COR, or CO will be considered unallowable and thus, unbillable.

• (U) All telework hours shall be billed at the negotiated rate for the position. Premium rates will not be allowed.

• (U) The Contractor-provided software development staff must maintain adherence to rules and standards associated with the protection of sensitive information (i.e. CUI, FOUO, etc.)

while operating in a telework environment.

• (U) The Government will not reimburse the Contractor for telework equipment or facility costs including, but not limited to, internet service, telephone service, or hardware.

• (U) Contractor telecommuting policy and labor timekeeping policies and procedures are subject to government audit.

5 (U) Capability Requirements

(U) This section describes software development, support, operations and sustainment requirements for SABER III. The ability to develop and maintain application software that meets both standard and non-standard software development practices while integrating with enterprise systems for NSG/ASG continuity remains an Agency imperative. Contractor-provided software development staff shall support the Government in all technical coordination supporting designing, developing, deploying, and sustaining software, as required. Contract personnel in Principal

Developer or Lead positions may also be required to provide status updates on all capability activities, timelines, issues, and interactions with stakeholders at regularly scheduled coordination meetings, as established by the Government.

5.1 (U) Assessments and Evaluations

(U) Contractor-provided software development staff, working with identified Government stakeholders, shall conduct assessments and evaluations of newly proposed software and/or requested application projects to identify and document requirements, make recommendations on feasibility for development, and, if reasonable, determine development options. The assessment and evaluation shall include the definition of baseline requirements, formulation of platforms for testing and operations, recommended list of viable coding language(s), cloud cost estimations, and identify rough schedule and resource requirements.

(U) As required by the Government, and in concert with the assigned Product Managers (PdMs) and government Technical Leadership, the Contractor may be required to conduct assessments and/or evaluations of existing software and/or applications to identify requirements associated with Government reporting, Discrepancy Reports (DR), Common Vulnerability Exposures

(CVE), Information Assurance Vulnerability Assessments (IAVA), and Requests for Change

(RFC). Assessment and Evaluation shall identify impacts to the applications or systems, develop implementation effort(s), plan development schedule estimates, and identify and document critical and major undocumented functional and non-functional capabilities impacted.

(U) All assessment and evaluation data shall be included in appropriate documentation such as the Software Requirements Specification (SRS) document (see Section 5.8). Government

Technical Leadership may require a separate report to complete this requirement.

5.2 (U) Designing and Engineering

(U) In close coordination with the assigned PdM and Government Technical leadership, the

Contractor-provided software development staff shall conduct design analysis, using Agile

Development Methodologies, in support of software/application development or software operations and sustainment decisions. When possible, design analysis should target the use of

CORE infrastructure and containerized solutions. Development languages, development sprints/schedules, open-source software availability, sustainment cost, identifying opportunities for elimination of proprietary software, security risks and proposed mitigation plans should also be taken into consideration when conducting design analysis.

5.3 (U) Agile Development

(U) The Contractor-provided software development staff shall employ Agile Methodologies, as defined by DevCorps documentation and direction, from assessment through completion of development activities, utilizing appropriate compliance and/or reference documents from

Tables 6.2 & 6.3 of Section 8.2 Compliance and Reference Documents. Agile software development refers to software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between cross-functional teams.

(U) The Contractor-provided software development staff shall, in conjunction with the assigned product manager and development team, contribute to the development and maintenance of a user story backlog, conduct story pointing activities, participate in Agile development meetings

(Sprint Planning, Backlog Grooming, Retrospectives, etc.) and other Agile activities as defined in DevCorps Agile Methodology (Table 6.3, Reference 2 of this document).

5.4 (U) Continuous Integration (CI)/Continuous Delivery (CD)/pipeline configuration and utilization

(U) The Contractor-provided software development staff shall practice the fundamental DevOps

CI/CD best practices of frequently merging code changes into a central code repository, as defined by the Government, and utilize automated build tools, as defined by the Government to conduct various automated code reviews (quality assurance, linting, testing, vulnerability, etc.)

prior to the automated deployment into the required software environments (development, stage, pre-production, production). The Contractor-provided software development staff shall use the

DevCorps Application Pipeline to adhere to CI/CD standards, unless directed otherwise by

Government Technical Leadership. The Contractor-provided software development staff shall follow the specific processes for CI/CD as defined in the DevCorps Standards Guide (Table 6.3, Reference 5 of this document).

5.5 (U) Application Development

(U) The Contractor-provided software development staff shall develop new software/applications that supports newly established or defined Agency Missions as well being able to modify or develop software/applications that enhance, support or sustain current Agency operational systems. The Government will prioritize development projects for the Contractor-provided staff, dependent on Agency needs and available resources.

5.5.1 (U) Front End Development

(U) The Contractor-provided software development staff shall conduct development using the appropriate coding language(s) (i.e. HTML, CSS, JavaScript) in conjunction with applicable frameworks (i.e. Angular, React, vue.js,) for front-end development when directed by the

Government.

5.5.2 (U) Server-Side Development

(U) The Contractor-provided software development staff shall conduct development using the appropriate coding language(s) (i.e. Java, Python, JavaScript) in conjunction with applicable frameworks (etc. Spring Boot, FastAPI, Express.js) for server-side development when directed by the Government.

5.5.3 (U) API Development

(U) The Contractor-provided software development staff shall develop Application

Programming Interfaces (API) to connect different applications, services, or systems and document appropriately when directed by the Government.

5.5.4 (U) Testing/TDD (unit, integration, functional, etc.)

(U) The Contractor-provided software development staff shall conduct the necessary test and evaluation activities for each software release. Test(s) shall demonstrate that software changes satisfy the requirements of the new application’s Technical Specification or correct identified defects of existing applications, and do not introduce unintended detrimental consequences.

(U) The Contractor-provided software development staff shall use Test Driven Development

(TDD) as directed. The Contractor-provided software development staff shall conform to the

DevCorps established guidelines on required code coverage for application development. The

Contractor-provided staff shall create, procure, or obtain Government furnished Test Data

(Government Furnished Information – GFI) and Test Software for the purposes of formal test and evaluation. The Contractor-provided staff shall document, maintain, manage and deliver the test and evaluation Test Data and Test Software. As applicable, the Contractor-provided staff shall generate or create integration tests for applications utilizing microservices architecture or integrating with multiple services.

(U) For purposes of this Blanket Purchase Agreement (BPA) “Test Software” includes software used in regression testing, User Acceptance Test (UAT) and Independent Verification and Validation (IV&V) to configure the test environment and test article(s), and software necessary to conduct the test(s) (e.g., test scripts, test drivers, simulators, and post processors).

Test Software also includes documentation sufficient to enable a third party to use the Test

Software and reproduce the results of a previous tests (regression, UAT and IV&V).

(U) As applicable, the Contractor-provided software development staff shall generate Test

Plans, Test Procedures, and Test Data to support the Government-conducted IV&V process.

The Contractor-provided staff shall provide required information, which may include source code, testing harness, test data, test results, algorithm description documents and other documents that attest to the validity of the exit criteria of the IV&V specifications for SABER

III efforts.

(U) For thick client software releases, the GPMO will direct the IV&V test (Self-Test) and document the results in test reports. The Contractor-provided software development staff shall participate in TEMs, assist in software installation, review test results, assist in anomaly resolution, and work off any DRs written during the IV&V process.

5.5.5 (U) Security and Accreditation

(U) As applicable, the Contractor-provided software development staff shall provide support for the security Assessment and Authorization of new and sustained applications on

Government networks and computers. The Contractor-provided staff shall support the resolution of issues related to system/application configuration and active software development as it pertains to DevCorps operated and sustained software from a cybersecurity perspective.

(U) The Contractor-provided software development staff shall complete government directed

DEVELOPER IAVA and NOC-directed InfoSec protection actions within directed time (to include POA&M negotiation/implementation, as directed by the COR).

5.6 (U) System Integration

(U) The Contractor-provided software development staff shall facilitate coordination of activities and related efforts between DevCorps, Users and other NGA programs initiatives.

(U) For each SABER III application software release the Contractor-provided software development staff must support deployment of SABER III software products for operations and/or user evaluation (Beta Test) using the DevCorps methodologies referenced in Table 3.

When directed by technical leadership, the Contractor-provided staff shall move software into

Government environments to allow for user evaluation and feedback. The Contractor-provided staff shall support the user evaluation process for the deployed software and collect user comments and feedback for analysis and provide the results to the Government, as requested as indicated in the DevCorps Product Management (PdM) and Customer Engagement Standard

Operating Procedures (SOP) (Table 6.3, Reference 11).

(U) The Contractor-provided software development staff shall coordinate with DevCorps government subject matter experts as necessary to schedule updates, installations, refreshes, Common Vulnerability Exposures (CVE) updates, Information Assurance Vulnerability Alert

(IAVA) updates, or other critical system/application maintenance as directed by the Government

Point of Contact (CO, COR, SABER III PM or Government Technical Leadership).

5.7 (U) Operations and Sustainment

(U) The Contractor-provided software development staff shall perform Operations defined as the execution of support to meet the performance and other defined requirements of the system, application, data repository or service in a cost-effective manner1.

(U) The Contractor-provided software development staff shall perform all elements of

Sustainment as defined below:

• (U) Corrective Maintenance: Identify, isolate and rectify a fault or problem to restore the application, system, or data repository to an operational state2.

• (U) Perfective Maintenance: Modification to improve performance or maintainability2.

1 Defense Acquisition Guidebook 2 DAU Acquisition Community Connection IT Maintenance Definitions

• (U) Adaptive Maintenance: Modification to keep an application, system, or data repository usable in a changed or changing environment, to include evolving security needs3.

• (U) Technology Insertion: Incorporating new or improved technology in an evolving technical environment2.

• (U) Technology Refreshment: Replacement of existing hardware or software for continued supportability throughout the lifecycle4.

• (U) Evolutionary Acquisition: Incremental delivery of enhancements initially deferred5.

5.7.1 (U) O&S Support

(U) The Contractor-provided software development staff shall employ Agile Methodologies, as defined by DevCorps documentation and direction, from assessment through completion of

O&S development activities, utilizing appropriate O&S compliance and/or reference documents from Table 6.2 & 6.3 of Section 6.6 Compliance and Reference Documents.

5.7.2 (U) O&S Test and Evaluation

(U) The Contractor-provided software development staff shall conduct the necessary O&S test and evaluation activities for each software release. Test shall demonstrate that software changes satisfy the requirements of the application’s Technical Specification, correct identified defects, and do not introduce unintended detrimental consequences.

(U) The Contractor-provided software development staff shall use Test Driven Development

(TDD) as directed. The Contractor-provided staff shall conform to the DevCorps established guidelines on required O&S code coverage for application development. The Contractor-provided staff shall create, procure, or obtain Government furnished Test Data (Government

Furnished Information – GFI) and Test Software for the purposes of formal test and evaluation.

The Contractor-provided staff shall document, maintain, manage and deliver the test and evaluation Test Data and Test Software. As applicable, the Contractor-provided staff shall generate or create integration tests for applications utilizing microservices architecture or integrating with multiple services.

(U) For purposes of this BPA “Test Software” includes software used in regression testing, User Acceptance Test (UAT) and Independent Verification and Validation (IV&V) to configure the test environment and test article(s), and software necessary to conduct the test(s)

(e.g., test scripts, test drivers, simulators, and post processors). Test Software also includes documentation sufficient to enable a third party to use the Test Software and reproduce the results of previous test(s) (regression, UAT and IV&V).

(U) As applicable, the Contractor-provided software development staff shall generate Test

Plans, Test Procedures, and Test Data to support the Government-conducted IV&V process.

The Contractor-provided staff shall provide required information, which may include source

3 International Software Benchmark Standards Group, Software Development and Enhancement Glossary 4 Managers Guide to Technology Transition v1.0, OSD AT&L 5 DAU Glossary of Defense Acquisition Acronyms and Terms code, testing harness, test data, test results, algorithm description documents and other documents that attest to the validity of the exit criteria of the IV&V specifications for SABER

III efforts.

(U) For thick client software releases, the GPMO will direct the IV&V test (Self-Test) and document the results in test reports. The Contractor-provided software development staff shall participate in TEMs, assist in software installation, review test results, assist in anomaly resolution, and work off any DRs written during the IV&V process.

5.7.3 (U) O&S Security and Accreditation

(U) As applicable, the Contractor-provided software development staff shall provide support for the security Assessment and Authorization of new and sustained applications on

Government networks and computers. The Contractor-provided staff shall support the resolution of issues related to system/application configuration and active software development as it pertains to DevCorps operated and sustained software from a cybersecurity perspective.

(U) The Contractor-provided software development staff shall complete government directed

DEVELOPER CVE, IAVA and NOC-directed InfoSec protection actions within directed time

(to include POA&M negotiation/implementation, as directed by the Government COR/PM).

5.7.4 (U) Data Sustainment and Format

(U) The Contractor-provided software development staff shall sustain existing mission application databases and datasets in support of DevCorps capabilities and services. The

Contractor-provided staff shall provide all levels of monitoring, logging, and alerting for applications and services for developed or sustained capabilities using NGA’s DevSecOps environment, notifying the government of abnormal activity, as directed. The Contractor-provided staff shall implement procedures to ensure that operational data and metadata is current and consistent, to ensure the proper data is available to users, to ensure the fidelity of the data and to record its pedigree. When applicable, the Contractor shall ensure that the ingested metadata is compliant to its applicable Military Specification or de-facto specification for existing and emerging datatypes.

• (U) The Contractor-provided staff shall condition data to comply with the NSG

Application Schema (NAS) data standard when applicable to mission.

• (U) The Contractor-provided staff shall provide data in Department of Defense

Discovery Metadata Specification when applicable to mission.

• (U) The Contractor-provided staff shall adapt existing and emerging NGA raster and vector datasets and metadata and processed imagery to comply with applicable Open

Geospatial Consortium (OGC) standards web services when applicable to mission.

Example OGC standards include but are not limited to Web Map Service (WMS) and

Web Feature Service (WFS).

• (U) The Contractor-provided staff shall adapt datasets to Representation State Transfer

(REST) compliant services when applicable to mission.

• (U) The Contractor-provided staff shall adapt datasets to the NSG Metadata Format

(NMF) when applicable to mission.

• (U) The Contractor-provided staff shall adapt datasets to the applicable Intelligence

Community Publication (IC PUBS) standard when applicable to mission.

5.8 (U) Documentation/Template development and maintenance

(U) Project Charter. The Contractor-provided staff designated as Team Leads shall assist the

SABER III PMO in creation of the Project Charter, as required, to capture any known requirements, risks, assumptions, and known outcomes. The Project Charter may include data captured during assessment and evaluation phase and the initial Project Request.

(U) Project Closeout and Transition Report. The Contractor-provided staff designated as Team

Leads shall assist the SABER III PMO in completion of the Project Closeout and Transition

Report and metric collections, as required, to document any information required to assist in transition of the project from DevCorps to the Customer.

(U) Systems Requirements Documents. The Contractor-provided software development staff shall assist in creation or update of System Requirements Documents, which include (but is not limited to, Software Requirements Specification Document and technical drawings, to incorporate results of assessments, evaluations, development and iterative or adaptive maintenance. Document creation or updates may result from (but is not limited to): 1) new development of software or applications, 2) maintenance fixes, 3) identified critical (previously) undocumented functional and non-functional capabilities, and 4) maintenance needs resulting from user engagement.

(U) User/Training Manuals. When software development actions create new or modify user interfaces the Contractor-provided software development staff shall create or update existing

User/Training Materials and/or prepare new User/Training Materials to be delivered with each software delivery as directed by the Government, so the materials always reflect the latest software modifications.

(U) Framework Template Maintenance. The Contractor-provided software development staff shall provide maintenance for existing or new DevCorps software development templates, as required, to ensure templates receive required security, functionality, and feasibility updates.

(U) DevCorps Development Documentation. The Contractor-provided software development staff shall provide maintenance for existing or new DevCorps development documentation throughout the life of the project within DevCorps, as required, to ensure the development documentation receives required and relevant updates pertaining to security, best practices, framework, developer, and/or user input and feedback.

6 (U) General Requirements and Guidance

(U) The following requirements are to provide the necessary resources and non-personal services needed to perform the SABER III mission identified in this SOW.

6.1 (U) Staffing

(U) The Contractor must provide FTEs at the prescribed labor categories (Table 6.1) with fully qualified personnel to satisfy the conditions of this SOW. The Contractor is responsible for ensuring all personnel performing work under this contract possess and maintain current certifications during the execution of this contract. The Contractor will not be reimbursed for earning or maintaining qualifications or certifications.

(U) The Contractor must provide a staffing plan within five (5) business days after purchase order award (Table 6.4, CDRL B001). Specific numbers and personnel requirements will be noted in each individual purchase order. All Contractor-provided software development staff are expected to be professional, and able to work in a fast-paced team.

(U) All personnel performing work on this contract are required to possess and maintain an active

Top Secret (TS) clearance with the ability to be nominated and then adjudicated by NGA for sensitive compartmentalized information (SCI).

(U) The Contractor shall provide the government notification ten (10) business days prior to personnel leaving the contract.

(U) The Contractor shall nominate a replacement within ten (10) business days of the departure of the previous employee. Nominations will be made by submitting a resume of the nominee to the PM/COR for approval. The Contractor is responsible for ensuring the individual nominated to the COR meets or exceeds the qualifications identified in the SOW and Table 6.1 below.

Resumes must address the individual’s technical background, education, work experience, and accomplishments related to the activities described in this SOW and the requirements addressed in Table 6.1.

(U) The Contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible and accountable for subcontractor performance.

6.1.1 (U) Labor Category (LCAT) Requirements

(U) Contractor proposed staff must meet the SABER III requirements in accordance with the required skills and knowledge identified in Table 6.1 below:

Table 6.1: Software Engineer Labor Categories (LCATs) and Requirements

Table is Unclassified

LCAT Required Qualifications Desired Qualifications

Software Developer, Principal

• Education o A Master of Science or equivalent degree in Computer Science, Engineering, Mathematics, Information Systems. Cybersecurity, or equivalent technical degree and a minimum of 13 years of experience in full stack development to include Java, Web services, Database, and micro-service development software, engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work.

o Or, a Bachelor of Science or equivalent degree in

Computer Science, Engineering, Mathematics, Information Systems or equivalent technical degree and a minimum of 15 years of experience in full stack development to include Java, Web services, Database, and micro-service

• Possesses at least one of the following Agile

Development Certifications o Certified Scrum Master o Agile Certified Practitioner (PMI-ACP) o Certified Scrum Professional

• Demonstrated experience working independently with clients or stakeholders to develop user-stories in support of full-service consumer and business applications.

• Demonstrated experience in development of customized code, scripts, modules, macro procedures, or libraries to implement specialized spatial analysis functions using languages such as Python, Java, JavaScript, PHP, C, Perl, or similar scripting and development languages.

• Demonstrated experience in integration and tailoring of geospatial Commercial Off-The-Shelf (COTS)

Table 6.1: Software Engineer Labor Categories (LCATs) and Requirements

Table is Unclassified

LCAT Required Qualifications Desired Qualifications development software, engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work.

o Or, a minimum, as equivalent to education, of 17 years of experience in software engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work may be substituted for a technical degree.

• Experience o Demonstrated firsthand experience in at least four of the following:

▪ Java, JavaScript or Python enterprise application development

▪ Web services architecture, design, and development

▪ Relational database design

▪ Spatial database design

▪ NoSQL database design

▪ Micro-service architecture, design and development

▪ Containerization and/or Orchestration

▪ API Development

▪ Cloud Native Development, AWS, Azure, Google Cloud or similar Cloud

Service providers o Demonstrated experience with relational database development.

o Must have minimum of 5 years or more experience with agile and lean philosophies, with at least 2 years serving as scrum or team lead.

o Demonstrated experience with Continuous

Integration and Continuous Delivery (CI/CD) techniques, test-driven development, or automated testing practices.

software applications; specialized software and database development and maintenance; integration of related specialized hardware; engineering studies to identify and remedy geodata processing bottlenecks.

• Demonstrated experience with government and/or commercial imagery products, to include SAR or related RADAR imaging technologies.

• Demonstrated experience working with and developing geospatial information systems (GIS) to include open-source and proprietary geospatial formats

• Demonstrated experience in use and development with common geospatial tools, data, and operating platforms. These may include, but are not limited to:

o Tools - Boundless Spatial suite, Remote View, PostGRES/PostGIS, Oracle Spatial and/or other geospatial databases, ArcGIS

Desktop, ArcGIS Server, Image Server, and File Geodatabases.

o Data formats including KML, KMZ, NITF, TIFF, JPEG, GeoPDF, and similar geo-related formats and data structures.

o Operating Platforms – ESRI, OpenGeo Suite, or similar.

• Demonstrated in-depth experience abstracting new or legacy systems via standards-based API’s to include web services. Including but not limited to Open

Geospatial Consortium standards.

• Demonstrated experience in at least one of the following:

o Developing terrain analysis visualization and algorithms.

o Developing automated detection algorithms.

Software Developer, Senior o Education

▪ A Master of Science or equivalent degree in Computer Science, Engineering, Mathematics, Information Systems. Cybersecurity, or equivalent technical degree and a minimum of 8 years of experience in full stack development to include Java, Web services, Database, and micro-service development software, engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work.

▪ Or, a Bachelor of Science or equivalent degree in Computer Science, Engineering, Mathematics, Information Systems or equivalent technical degree and a minimum of 10 years of experience in full stack development to include Java, Web services, Database, and micro-service development software, engineering/development, or a related o Possesses at least one of the Agile

Development Certifications

▪ Certified Scrum Master

▪ Agile Certified Practitioner

(PMI-ACP)

▪ Certified Scrum Professional o Demonstrated experience in development of customized code, scripts, modules, macro procedures, or libraries to implement specialized spatial analysis functions using languages such as Python, Java, JavaScript, PHP, C, Perl, or similar scripting and development languages.

o Demonstrated experience working independently with clients or stakeholders to develop user-stories in support of full-service consumer and business applications.

o Demonstrated experience in integration and tailoring of geospatial Commercial Off- The-Shelf (COTS) software applications;

specialized software and database development and maintenance; integration of related specialized hardware; engineering

Table is Unclassified

LCAT Required Qualifications Desired Qualifications area that demonstrates the ability to successfully perform the duties associated with this work.

▪ Or, a minimum, as equivalent to education, of 12 years of experience in software engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work may be substituted for a technical degree.

o Experience o Demonstrated firsthand experience in at least three of the following:

▪ Java, JavaScript or Python enterprise application development

▪ Web services architecture, design, and development

▪ Relational database design

▪ Spatial database design

▪ NoSQL database design

▪ Micro-service architecture, design and development

▪ Containerization and/or Orchestration

▪ API Development

▪ Cloud Native Development, AWS, Azure, Google Cloud or similar Cloud

Service providers o Demonstrated experience with relational database development.

o Must have minimum of 3 years or more experience with agile and lean philosophies, with experience serving as scrum or team lead a plus.

o Demonstrated experience with Continuous

Integration and Continuous Delivery (CI/CD) techniques, test-driven development, or automated testing practices studies to identify and remedy geodata processing bottlenecks.

o Demonstrated experience with government and/or commercial imagery products, to include SAR or related RADAR imaging technologies.

o Demonstrated experience working with and developing geospatial information systems (GIS) to include open-source and proprietary geospatial formatsDemonstrated experience in use and development with common geospatial tools, data, and operating platforms. These may include, but are not limited to:

▪ Tools - Boundless Spatial suite, Remote View, PostGRES/PostGIS, Oracle Spatial and/or other geospatial databases, ArcGIS Desktop, ArcGIS Server, Image Server, and File Geodatabases.

▪ Data formats including KML, KMZ, NITF, TIFF, JPEG, GeoPDF, and similar geo-related formats and data structures.

▪ Operating Platforms – ESRI, OpenGeo Suite, or similar o In-depth experience abstracting new or legacy systems via standards-based API’s to include web services. Including but not limited to Open Geospatial Consortium standards.

o Demonstrated experience in at least one of the following:

▪ Developing terrain analysis visualization and algorithms.

Developing automated detection algorithms.

Software Developer, Mid • Education o A Master of Science or equivalent degree in

Computer Science, Engineering, Mathematics, Information Systems. Cybersecurity, or equivalent technical degree and a minimum of 3 years of experience in full stack development to include Java, Web services, Database, and micro-service development software, engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work.

o Or, a Bachelor of Science or equivalent degree in Computer Science, Engineering, Mathematics, Information Systems or equivalent technical degree and a minimum of 5 years of experience in full stack development to include Java, Web services, Database, and micro-service development software, engineering/development, or a related area that demonstrates the ability to successfully perform the duties associated with this work.

• Demonstrated experience in the development of customized code, scripts, modules, macro procedures, or libraries to implement specialized spatial analysis functions using languages such as Python, Java, JavaScript, PHP, C, Perl, or similar scripting and development languages.

• Demonstrated experience in integration and tailoring of geospatial Commercial Off-The-Shelf (COTS) software applications; specialized software and database development and maintenance; integration of related specialized hardware; engineering studies to identify and remedy geodata processing bottlenecks.

• Demonstrated experience with government and/or commercial imagery products, to include SAR or related RADAR imaging technologies.

• Demonstrated experience working with and developing geospatial information systems (GIS) to include open-source and proprietary geospatial formats

• Demonstrated experience in use and development…