20240424 ARM SOW.docx

UNCLASSIFIED

National Geospatial-Intelligence Agency (NGA)

Statement of Work For GEOINT Services Office (TEG) Automated Raster Modernization (ARM) Contract

April 24, 2024

1. BACKGROUND

As identified in the recent NSG Directive 1501 process, Compressed ARC Digitized Raster Graphic (CADRG) and Enhanced Compressed Raster Graphics (ECRG) will continue to be created and disseminated until no system requires the data. As such, this long-standing product will continue to be a highly visible, mission requirement for years to come. Additionally, CADRG and ECRG will continue to be the primary foundation map background format for NGA digital maps for the foreseeable future, due to the widespread implementation of these formats in DoD systems, and the formats’ use of the Arc Raster Chart (ARC) projection system, which allows seamlessly moving map displays at any scale. NGA has proudly supported this effort since its inception in the mid 1990’s and will continue its efforts to modernize the source and software used to create these important and widely disseminated products.

The Automated Raster Modernization (ARM) initiative was started in 2017 as a replacement for the legacy Common Mapping Production System (CMPS) and today the system consists of two modules, GeoDec (Georeferencing and Decollaring) and Accord (Automated Cataloging and Compression of Raster Data). Both modules are Cloud based Web solutions using primarily open source software tools.

GeoDec can semi-automatically and/or manually geo-reference and de-collar source PDF or TIFF’s to produce several Georeferenced Maps and Charts (GRMC) outputs including GeoTiff and GeoPDF. GeoDec also provides the input to Accord; a final GeoTiff with an accompanying JSN metadata file.

Accord imports the GeoDec final GeoTiff and accompanying JSN metadata to create CDRG and ECRG source repositories that can be processed into frame files and then ultimately into product deliverables. Each CADRG and ECRG title is composed of hundreds of frame files that are given version numbers as part of the file name and that are often superseded by newer frames on an individual basis. The required Accord product output types are:

· 28/56 day AIRAC cycle

· Monthly NavPlan, EuropeSAC, Sectional, and TLM updates (and associated files)

· Yearly NavPlan CDRG/ECRG updates (Big Bang/Little Bang)

· As needed Country Rom distribution, tests, and specials.

ARM production must be integrated with a standardized cataloging service on ingest, and the Source Content Dissemination Service (SCDS) on export. Additionally, ARM data and metadata must be synchronized with the NGA Product Dissemination file server and database (aka Gateway). The ARM effort envisions an efficient, technologically advanced production, archiving, and dissemination system for NGA raster maps and charts.

2. OBJECTIVE AND SCOPE

The purpose of this contract is to acquire a software development(s) team or teams to provide NGA with the technical expertise and support required to maintain and enhance the ARM system: GeoDec and Accord. This effort is a continuation of the ARM effort (awarded under the original title “GEOINT Services Development – Data Transformation, Enterprise Print”). The selected contractor will provide development, enhancement, deployment, operational sustainment and maintenance in accordance with the capabilities listed in Table 1.

Table 1: Key Capabilities

· Administrator Functions

· GeoDec

· Georeferencing software creating Accord inputs and Georeferenced Maps and Chart (GRMC, formally FBG) output.

· Accord

· Cataloging

· Reformatting

· Shapefile capability

· Colortable capability

· Legend File capability

· Supplementary file inclusion (ex. chartlists, indexes, graphics, geo-tiffs, read-me)

· Edit/Create Media (including Country Roms, Specials, and Expurgations)

· Edit/Update Media (including Big Bang, Little Bang, CSD/ESD, TLMUPD, Sectional and ESAC)

· Client Versions of Accord and GeoDec

· Metadata user access and loading

· SCDS Integration

· ASG Containerized Solution and Support

Contractor will provide all necessary support to the ARM project to ensure complete development, deployment and sustainment to meet all mission requirements during the period of performance.

At a minimum, the following map/chart formats per product from topographic, aeronautical and toponymic source data will required:

GeoDec Output

· Low res GeoPDF (400 dpi RGB or CMYK)

· Other formats: GEOTIFF, JPEG, Mr Sidd

· Metadata Accord Output

· Frames, metadata, databases, and deliverable packages of:

· Compressed Arc Digitized Rater Graphic (CADRG)

· Enhanced Compressed Raster Graphic (ECRG) ASG Support The contractor will remotely support the software at all CADRG/ECRG production sites, including those at ASG partner sites (UK, CAN, AUD, and NZL) whether it is the client versions or containerized. Contractor will supply the software, instructions, training and troubleshooting.

3. PERFORMANCE REQUIREMENTS

The government intends the continued use of agile development methodologies and tools to manage the execution of the work on this contract. The contractor must support the utilization of agile methodologies and tools including user stories and backlogs.

In addition to the Key Capabilities in Table 1, the user stories will fulfill the remaining performance objectives of the contract and may be refined with each sprint to continue meeting user needs. In agreement with the product owner, user stories can be modified, added, retracted, or reprioritized.

· The contractor shall participate in sprint review meetings with government PM’s and customer organizations and document their activities in a scrum planning tool such as JIRA or Redmine.

OPERATING CONSTRAINTS (NON-FUNCTIONAL REQUIREMENTS)

The following non-functional requirements shall be satisfied during performance, in agreement with the product owner. These non-functional requirements can be modified, added, retracted or reprioritized from the requirements backlog for these features:

· The digital products must adhere to industry encoding standards, to NGA standards, and to product specifications found at https://nsgreg.nga.mil/registers.jsp or http://quicksearch.dla.mil/ASSIST

· NGA’s DevOps environment and/or Government-approved techniques or methodologies, such as SAFE Agile/Lean. DevOps tool such as cloud foundry and mesosphere, more information available on: https://home.geointservices.io/

· The teams must use Software techniques/methodology elements aligning with the 12-factor application such as the ones described in https://12factor.net

3.1 Operations and Sustainment

The contractor shall maintain the entire, cumulative ARM software baseline to include all new capabilities developed, tested, and released from the backlog in accordance with NGA standards. Specific examples are provided below however they are not all inclusive of O&S activities that will be included in the vendor’s agile backlog.

· The Contractor shall provide Corrective, Adaptive, Preventative, and Optimization Services in accordance with the approved Operations and Sustainment Plan (CDRL 2407).

· The software maintenance process shall include activities from recording an issue, technical investigation of the issue, designing a modification or fix, and testing before implementing the fix to a software release, consistent with existing maintenance processes.

· The map/chart formats in “Section 3 Scope” shall continue to be supported in order to fulfill the Key Capabilities (Table 1) and any current or future user stories.

· Contractor will continue to support both cloud-based enterprise version of ARM and a stand-alone offline Client version.

· To expedite the georeferencing and de-collaring of any non-referenced products received by NGA for archiving, continued use of computer vision algorithms able to detect grid intersections and toponymic features is required.

· Bounding rectangle vectors (footprints), index files, and standardized xml metadata shall continue to be generated for each product and series to enable web-based discovery and support data management.

· The Contractor shall continue to provide integration for software and hardware to ensure compatibility with NGA’s cross-domain solutions.

· The frame registry shall continue to be maintained in support of Replication on Demand, so that currency can be managed at the frame level and the most recent frame editions will always be available for automatic generation of CADRG/ECRG titles.

· The contractor shall continue to respond to the results of software and data testing performed by NGA and other DoD test organizations and end users.

· The contractor shall revise as necessary product specifications and associated data standards regarding CADRG and ECRG for all NSG-approved changes.

· The contractor shall continue to adhere to NGA standards for Image Quality testing, Unit Testing, and Functional Testing before code deployment. NGA CORE development tools shall be used when deemed appropriate by the government PM.

3.2 Software Development

The contractor shall develop, test, stage and deploy new software supporting the FOC capability of the ARM system and downstream systems, in accordance with the backlog as prioritized by the Government officers managing the program. Specific examples are provided below however they are not all inclusive of new software development activities that will be included in the vendor’s agile backlog.

· Source Baseline – All feasible ADRG source used in the Common Mapping Production System (CMPS) will need to be converted to GeoTiff with associated metadata and ingested into the Accord system, where it will be cataloged and reformatted. Accord databases will be wiped with the exception of USGS, Aero, and ESAC RPF codes before the baseline reset. NGA will be responsible for the quality control of the source baseline reset and filling gaps where the conversion from ADRG to GeoTiff was not possible. This effort is required so that NGA can pick up where the CMPS left off (approximately 77,000 charts) and start integrating charts produced since NGA took CADRG/ECRG production in house.

· Standard Media – Users must have the ability to create standard media, essentially all products, other than those in update media status. Standard media will pull chosen frames (modified in Edit Media) for a selected title, NSN and NRN will already be populated.

· Edit Media – User must have a way to choose which frames belong on each title saved in the system. Users must have the ability modify titles by adding and deleting frames. Frame removal can be done visually via frames displayed on the map or textually in a table. Edit media should accommodate ECRG and or CDRG and well as multiple map types. A description box, frame counts, and file size should be viewable by the user. Metadata fields should include, frame name, series, at a minimum.

· TLM Update with Index – System shall be able to create a quarterly TLM Update disk for CDRG and ECRG with associated index files. TLM Update disks include all 50K, 100K, and 25K frames that, at the time of production, do not have a home on an already published title. CDRG TLM Update requires a TLMindex.ntf which will include a production date, frame counts from TLM 100, 50 and 25K (200K, 50K Other, and 24K will be listed as 0 frames), and a list of all TLM 100, 50 and 25 K frames and their last known title association (including current months TLMUPDATE). The ECRG TLM Update requires a currency.xml file. The currency.xml file is created for all the update cycle titles and is not unique to the ECRG TLMUPDATE.

· CSD/ESD with Index – System shall be able to create a monthly CSD and ESD disk for CDRG and ECRG with associated index files. CSD/ESD disk contain any new or updated NavPlan frames (JOG, ONC, TPC, GNC, and JNC) created since the last Big Bang or Little Bang. CSD and ESD disks are cumulative starting with the first issue after the Big Bang and Little Bang and are reset to blank when new Big Bang/Little Bangs are cut. CSD titles include an index.ntf file that includes a production date, frame counts for GNC, JOG-A, JNC, LFC, LNC, ONC, TFC, and TPC. A list of all frames are included with their last known title association (including current months CSD and ESAC titles). CSD also includes the last OCF file. ESD disk will include the currency.xml that is created for all the update cycle titles and is not unique to the ECRG ESD.

· New Media – System will have the ability to set up a new title. NSN, NRN, Edition, Media Type, Description and Notes are the minimum requirements for inputs. User will need the ability to add frames to the media, at least, graphically. Frame listing will have, at minimum, the frame number, series, and status. Newly added media will be added to the list of titles available through Standard Media.

· Big Bang – System will have the ability to manage and create yearly CDRG worldwide titles (48 preset AOI’s) of all Nav Plan frames (JOG, ONC, TPC, GNC, and JNC). These titles will not have special add-on files but their frames will need to be accounted for and included in the following month’s CSD Index files.

· Little Bang – System will have the ability to manage and create yearly ECRG worldwide titles (13 preset AOI’s) of all Nav Plan frames (JOG, ONC, TPC, GNC, and JNC). These titles will not have special add-on files but their frames will need to be accounted for and included in the following month’s Currency.xml files.

· Bridge CSD – System will need to have functionality to allow for the creation of the Bridge CSD. The Bridge CSD/ESD is delivered in place of the standard CSD/ESD with the monthly cycle right after the Big Bang and Little Bang are cut. This disk can contain two volumes. Volume A should be all frames from the last CSD until the Big Bang. Volume B should be only new brand new (revision 1) frames born after the last Big Bang until the current Big Bang. It is possible that one or more of these disks may not need to be cut (no frames). This requirement can be a process outside Accord if necessary.

· Viewing Frame Metadata – Users of Accord need the ability to view frame metadata. With millions of frames maintained by the system, the user will need a way to select a frame or frames and view the associated metadata for that frame or frames. Minimally, Series, Item, Edition, Sig Date, and Currency Date should be displayed.

· Bulk Loading of Metadata – Users of Accord should have the ability to load the required metadata to Accord in bulk via a spreadsheet to accommodate large quantities of charts at one time. This is a necessity so that the system can accommodate large quantities of data, much like what we have received so far from the automated program.

· Superseding Solutions – With the volumes of data Accord will produce in its lifetime a system for identifying superseded charts and removing them from the system is required. Having duplicate charts has a negative impact on the work that the Gateway does and makes tracking data via databases problematic.

· Legends/Legend Files – System will have the ability to collect legends from GeoDec inputs and disseminate legends on required disks. Minimally, Sectionals, ICMs, ESACS, and City Graphics will be the map types that require legends ability. Legend folders on titles will follow the legacy (CMPS) file structures for CDRG and ECRG. Legends.csv is required for CDRG products and the format will follow the legacy (CMPS) file structure.

· User Access to Database – Users of Accord need a way to access the Accord database. With upwards of 80,000 records users will need the ability to select a subset of data based on, at least, map type and/or series, as well as a complete download in a format readable by Excel.

· OpenCV Replacement – Replace the OpenCV library with another Computer Vision library. OpenCV has Foreign Ownership, Control or Influence issues and has required additional work to strip out unneeded libraries for software approval.

· SCDS Integration – Integrate with the SCDS database and services for dissemination of CADRG/ECRG data. Ensure data and metadata are available for dissemination and web services.

· Swapped Containers – I think this is almost complete for the ATO and future work would be included in accreditation.

· Containerized Solution – Containerize the GeoDec and ACCORD applications to allow for hosting at remote sites or on other classification domains. The applications should be operational without the need to reach back to NGA systems.

4. STAFFING

The Contractor is responsible for proposing the team composition best suited to meet the ARM requirements, however the government estimates that this work can be performed by no more than two scrum teams. The Contractor shall provide 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 maintaining qualifications. All contractors are expected to be professional, and able to work in a fast-paced team.

Because of the complexity of the contract, all contractor personnel are expected to perform for a minimum of 6 months under the resulting contract. The contractor shall provide the government notification 10 business days prior to personnel leaving the effort and backfill their positions within 10 business days by submitting a resume for the Contracting Officer’s Representative (COR)’s approval with an individual with qualifications that meet or exceed the qualifications of the person to be replaced.

Resumes should include a brief description of the experience and capability for all contract employees on the proposed team. Resumes should also address the individual’s technical background, education, work experience, and accomplishments related to the activities described in this requirement.

The Government has identified the following key personnel positions: Scrum Master / Program Manager (CPM), Geospatial Database Architect, and Geospatial Software Developer. The CPM must be the single point of contact for any programmatic issues that may arise under this task order. The Contractor shall also designate an individual to be the backup for the CPM, to ensure the customer has uninterrupted access to the Contractor. All key personnel performing work on this contract are required to have active Top Secret/Sensitive Compartmented Information (TS/SCI) clearances.

4.1 Key Personnel

Scrum Master / Program Manager The contractor must provide an overarching contract Program Manager (PM) to ensure total program integration and support during all phases of the contract. The PM must provide program health status in the areas of schedule, cost, and performance. The PM must manage and administer the programmatic and technical efforts associated with this PWS to include, but may not be limited to, contract administration, cost, schedule, security administration, configuration control, and property control.

The PM must attend requested meetings and technical exchange meetings to discuss a myriad of topics that may include, but may not be limited to, staffing, resource allocation, schedule, performance, cost, capability integration and/or interoperability, workflow and/or process optimization, etc.

The Contractor PM must continuously assess progress and forecasts in achieving program goals, objectives and schedule milestones.

Required: Experience with Scrum Agile and Project/Program Management Desired: Experience designing and developing cartographic software, Experience leading teams of developers Geospatial Database Architect Required: Experience creating and maintaining Oracle and PostGIS spatial databases Desired: Experience with Geographic Information Systems and Automated Mapping Systems Geospatial Software Developer Required: Demonstrate Experience with computer vision/OCR development using open source software such as OpenCV. Experience building cartographic software in a PaaS environment.

Desired: Experience designing cloud native microservices, REST API’s, familiarity with automated testing practices, Swagger documentation, and DevOps pipeline. Experience creating workflows with open source technology such as NiFi.

4.2 Team Structure/Composition

Required Skills and Knowledge for the Team UX designer capability with experience developing geospatially enabled web applications Demonstrates experience with developing software using cartographic processing of raster maps and charts using tools such as GDAL, Tesseract, and implementing solutions into PaaS environment Demonstrates experience with Continuous Delivery and Continuous Integration (CI/CD) techniques, test-driven development, and automated testing practices.

Demonstrates experience developing and managing a micro-service architecture At least one team member is required to hold and maintain ICD 503 Level II compliance certification.

Demonstrates experience writing conversion/ingest software between geospatial formats Demonstrates experience with Geoserver or similar software to create OGC services SAFe Agile and Scrum methodology Open-source login/authentication services

4.3 Program Review and Meetings

The Contractor must provide their slide deck for Program Management Reviews along with written Reports/Minutes of all significant coordination activities. (CDRL 2401) The Contractor will report program progress at Monthly and Quarterly Program Management Reviews (PMR) to include cost, schedule, performance, staffing, and deliverables

4. 4 Helpdesk and documentation The contractor shall create a knowledge article to explain basic troubleshooting techniques for the ARM suite, to be used by the DTE helpdesk (CDRL 2402).

In circumstances when the DTE helpdesk escalates the technical problem, the contractor shall provide advanced troubleshooting support at minimum during NGA Core hours (10:00 AM to 2:00 PM EST).

4. 5 Risk Management Plan The contractor must develop a Risk Management Plan which identifies any risks to successful, timely completion of its contracted effort, to include likelihood of occurrence, impact to overall schedule and performance, and recommended/planned risk mitigation (CDRL 2403). The contractor will present a risk review with the government at the quarterly PMR to discuss and adjudicate program risks.

4.6 Transition

4.6.1 Phase-In. The Contractor shall lead a contract kickoff meeting within 10 business days after contract award. At a minimum, the contractor shall introduce team members and staff, and discuss organizational structure and administrative operations pertinent to this requirement. The Kickoff Meeting Agenda is due within 5 business days after contract award (CDRL 2404). The Contractor shall provide a Phase-In transition plan 10 business days after contract award (CDRL 2405). To minimize any decreases in productivity and to prevent possible negative impact on additional services, the Contractor shall have all key personnel on board during the thirty (30) day phase-in period commencing with the date of contract award. During the phase-in period, the Contractor shall become familiar with performance requirements, obtain their IC badge, CAC, and all other forms of government identifications, complete any specific government required training, and conduct inventory and transfer of Government Furnished Property/ Government Furnished Equipment (GFP/GFE) to include transfer of all source code, documentation, and SOPs developed and maintained by the incumbent contractor.

4.6.2 Phase-Out. Prior to the completion of this contract, an observation period may occur, at which time team management personnel of the incoming Contractor may observe operations. This will allow for orderly turnover of facilities, equipment, and records and will help to ensure continuity of services. The outgoing Contractor is ultimately responsible for performing full services IAW the contract during the phase-out period, and shall not defer any requirements for the purpose of avoiding responsibility or of transferring such responsibility to the succeeding Contractor. The outgoing Contractor shall fully cooperate with the succeeding Contractor and the Government, so as not to interfere with their work or duties.

The outgoing Contractor shall be prepared to transition the workload to the newly selected Contractor during the thirty (30) day phase-out period, which will occur at the end of the period of performance of the contractual effort. Upon expiration of this Task Order, the Contractor shall provide to the Government the names of personnel who worked on the task order and written confirmation that they have been read off in accordance with NGA security policy.

4.6.3 Transition Report. The contractor shall submit a Task Order Closeout and Transition Report.

At the end of the task order base year or option year, if an option year is not awarded or as directed by the CO, the Contractor shall provide a close-out report at the timeline directed by the Government.

The Closeout and Transition Report (CDRL 2406) shall include all up-to-date critical information needed to sustain operations after this task order expires. The report shall include all Government owned property, inventories, Government owned software, work center standard operating procedures, existing network drawings, status of deliverables and any other applicable documentation. As applicable, the report shall include at a minimum:

· Confirmation that all code developed on this contract has been version controlled and stored in the appropriate repository as directed by the PM or COR

· Confirmation that all code developed on this contract will have a read me document per application that describes the process of how to deploy/run/modify/add to the codebase & how to perform unit testing

· Documentation on how to automatically deploy code in the DevOps pipeline will be finalized, safeguarded and transferred to the successor contractor

· Confirmation that all API’s have Swagger documentation to cover all current functionality

· Confirmation that a complete set of instructions to run any non-standard, offline, or locally deployed non-cloud versions of the application has been included

5. GENERAL INFORMATION

5.1 Period of Performance

Period of Performance: The period of performance will be for a one (1) Base Year period of 12 months and one (1) 12-month option period from time of contract award.

5.2 Place of Performance

The work shall be performed primarily at the contractor’s site, with any NGA SCIF required testing and integration to be performed at NGA’s Arnold facility. Meetings and project planning activities will be virtual, performed at NGA facilities, or contractor’s site, at NGA’s discretion.

5.3 Travel

The Contractor may be required to travel CONUS or OCONUS in support of NGA’s mission to achieve FOC for the ARM program while connecting and/or training foreign partners.

Travel team size, destination, and trip duration will be determined by the Government in support of ARM contract objectives.

The Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR), FAR 31.205-46, subject to the limitation of funds specified in this contract.

All travel requires advanced approval in writing by the COR prior to requested travel date. Contractor shall provide travel request to the COR 30 days prior to request travel date.

The contractor will not be reimbursed for any local travel. Local travel is defined in the contract as travel conducted on official business within a 50-mile radius of official duty station.

The Contractor shall submit monthly invoices for reimbursement citing the appropriate travel CLIN. Each individual travel instance shall be captured; copies of receipts, travel vouchers, etc. shall be attached to the invoice to support charges. Original receipts shall be maintained by the Contractor and made available to Government auditors upon request.

5.4 Quality

The Government intends to utilize a Quality Assurance Surveillance Plan (QASP) to monitor the quality of the contractor’s performance. The oversight provided for this task order via the QASP will help to ensure that service levels reach and maintain the required levels throughout the task order’s period of performance. The QASP provides the COR with a proactive method to avoid unacceptable or deficient performance, and provides verifiable input for the required Past Performance Assessments before any Option Periods are exercised. The QASP will be finalized immediately following award and a copy will be provided to the contractor. The QASP is a living document and may be updated by the Government as necessary.

6 SECURITY

6.1 Unclassified Work Performance Security Requirements:

6.1.1 Uncleared personnel are authorized to perform work up to the UNCLASSIFED level on this contract with access to DoD Controlled Unclassified Information (CUI) information as determined by the Government. Only United States personnel (foreign nationals are prohibited from working on this contract) are authorized to perform work or have access to the information on this contract.

6.1.2 Contractors must abide by the DD Form 254 - Contract Security Classification Specification, and applicable security policies and regulations. The Contractor shall follow all applicable NGA, IC, and DoD information security and operational security policies and guidance when accessing and transmitting data over networks during performance of contractual requirements.

6.1.3 In the performance of this contract, the contractor will have access to and be exposed to DoD CUI, to include but not limited to: For Official Use Only (FOUO). The contractor shall 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 shall be “all release and disclosure request shall be submitted through the prime contractor to NGA”.

6.1.4 The Contractor shall comply with the NGA, DoD, and IC policy and regulations, to include but not limited to the Consolidated NGA Security Classification Guide (CoNGA) to properly portion mark all information associated with this effort appropriately. Information handling will be in accordance with applicable security policy and regulations and NGA compliance documents.

6.1.5 The Contractor shall inform the Government when their employees no longer support the contract the same day. If the contract personnel will no longer be supporting NGA, via an NGA contract, all government issued items shall 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 and notify and seek further direction from the COR or NGA Industrial Security. The Contractor shall send any Government items (IE: NGA Badge, parking hangtags, etc.) within 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.

6.1.6 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.

6.1.7 Contractors with a favorable HSPD-12 Tier 1 adjudication are eligible to receive a T-9 visitor badge that does not require an escort in unclassified areas of the facility, however they must be escorted in classified areas of the facility. Contractor personnel without a favorable HSPD-12 Tier 1 adjudication will receive a red visitor badge (escort required) for visits to NGA facilities and will be escorted at all times while in NGA facilities. The visitor badge must be returned at the end of each visit day. Contractors are required to undergo a HSPD-12 Tier 1 background investigation with the possibility of a Single Scope Background Investigation (SSBI) before gaining access to NGA development environments. NGA will sponsor the HSPD-12 Tier 1 background investigation for required program personnel.

6.1.8 Contractor personnel are prohibited from bringing any computer-related equipment or accessories of any kind onto federal facilities, including but not limited to cameras, two-way pagers, laptops, CDs, DVDs, flash drives, or any other kind of removable media, without prior approval and approval paperwork from NGA. A full list of prohibited items will be provided to the Contractor upon award.

6.2 Classified Work Performance Security Requirements:

6.2.1 Contractor personnel performing classified work on this contract are required to have active TS/SCI clearances for access to classified NGA facilities, when performing duties within classified environments, and for access to classified NGA computer systems. Contractors are subject to a Counterintelligence 4.2.2 Polygraph as requested by the Government. NGA will sponsor security clearances, NGA Badge and Common Access Cards (CAC) for required program personnel.

6.2.2 Contractors must abide by the DD Form 254 - Contract Security Classification Specification, and applicable security policies and regulations. The Contractor shall follow all applicable NGA, IC, and DoD information security and operational security policies and guidance when accessing and transmitting data over networks during performance of contractual requirements.

6.2.3 The Contractor shall comply with the NGA, DoD, and IC policy and regulations, to include but not limited to the Consolidated NGA Security Classification Guide (CoNGA) to properly portion mark all classified documentation appropriately. Information handling will be in accordance with applicable security policy and regulations and NGA compliance documents

6.2.4 The Contractor shall inform the Government when their employees no longer support the contract the same day (see DD254 - Government Furnished Property and Information). If the contract personnel will no longer be supporting NGA, via an NGA contract, the items shall 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 shall send a copy of the debriefing statement, plus any Government items (IE: NGA Badge, CAC, Courier Card, parking hangtags, etc.) within 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.

6.2.5 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.

7.0 REFERENCE DOCUMENTS

· Properly Styled Code - 18F Front End Guide - https://frontend.18f.gov/#js-style

· Web Content Accessibility Guidelines 2.0 AA (WCAG 2.0 AA) standards http://squizlabs.github.io/HTML_CodeSniffer/or https://github.com/pa11y/pa11y

· Code documented per NGA Dev Corps standards available Gitlab https://gitlab.gs.mil/DevCorps/Documentation

· The digital products must adhere to industry encoding standards, to NGA standards, and to product specifications found at https://nsgreg.nga.mil/registers.jsp or http://quicksearch.dla.mil/ASSIST

· NGA’s DevOps environment and/or Government-approved techniques or methodologies, such as SAFE Agile/Lean. DevOps tool such as cloud foundry and mesosphere , more information available on: https://home.geointservices.io/

· The teams must use Software techniques/methodology elements aligning with the 12 factor application such as the ones described in https://12factor.net

8.0 DELIVERABLES

The Contractor shall provide the following deliverables.

(sec 4.3)

(sec 4.5)

(sec 4.6)

(Section 4.6)

(Section 4.6)

(sec 3.1)

image1.jpeg