1- PWS - Water Management Program SATOC.pdf

Performance Work Statement for the

WATER MANAGEMENT PROGRAM ENHANCEMENT SERVICES

Replacement for Contract No. W9127N-21-D-0002

PANNWD-26-P-0000 029287

Project in Portland, Oregon

07 MAY 2026

WATER MANAGEMENT PROGRAM ENHANCEMENT SERVICES

1.0 General Statement

This is a non-personal commercial services contract for Water Management Program Enhancement Services in support of the U.S. Army Corps of Engineers (USACE), Portland District (CENWP). The Contractor shall provide all labor, equipment and materials necessary to perform required services under this contract and comply with all local, state, and federal regulations during the services performed. This is a Firm-Fixed-Price (FFP) Indefinite Delivery Indefinite Quantity (IDIQ) contract with a base 5-year period. The Government will not exercise any supervision or control over the contract service providers performing the services.

2.0 Definitions

Throughout this statement of work these terms are defined as follows:

A2W: Access to Water. The USACE Access to Water (A2W) refers to the U.S. Army Corps of Engineers' initiative and online system for providing public access to real-time water resources data, primarily through their Corps Water Management System (CWMS) Data Dissemination tools, offering maps, charts, and reports for navigation, flood control, and water supply management, supporting stakeholders with vital information on reservoir levels, flows, and project statuses nationwide.

Acceptable Quality Level (AQL): Acceptable Quality Level equals the performance standards listed in 5.0, Performance Standards and Requirements, and as summarized in 6.0, Performance Requirements Summary. The Contractor must re-perform all unsatisfactory work unless excused by the Quality Assurance Evaluator.

API: Application Programming Interface. This is a set of functions or commands that allow an application to interact with a particular database, application, software libraries, or system.

Aquarius: Analytics software developed by Aquatic Informatics to monitor flooding, water quality, stormwater, and more.

CBT: Columbia Basin Teletype. CBT includes a CBT Messenger for sending, receiving, and displaying data and communication associated with operating the dams on and around the Columbia River Basin.

CCP: Corps Computational Processor. A module included in the OpenDCS government software that provides the means to perform computations and transformations on data coming into a specified database.

CDA: CWMS Data API. An application programming interface that provides access to the USACE Water Management CWMS data.

Contract Discrepancy Report (CDR): A written record of unsatisfactory performance by the Contractor as observed by the Quality Assurance Evaluator.

Contracting Officer (KO): The Government employee who is authorized to enter into, administer, and/or terminate contracts, and make related determinations and findings. Only a warranted Contracting Officer, acting within their delegated limits, has the authority to issue modifications or otherwise change the terms and conditions of this contract. If an individual other than the Contracting Officer attempts to make changes to the terms and conditions of this contract the Contractor shall not proceed with the change and shall immediately notify the Contracting Officer.

Contracting Officers Representative (COR): The Government employee who has been authorized in writing as the KO’s representative, acting within the limits of their authority. The COR may not make changes to the terms and conditions of this contract.

Contrail: A product by OneRain/AEM that provides a means to acquire and monitor data collection systems. The software product is transitioning from Contrail to Elements 360.

COR: Contracting Officer Representative.

Corps: United States Army Corps of Engineers (USACE).

CWBI: Civil Works Business Intelligence is a USACE initiative transitioning toward a Cloud-based platform that integrates data from multiple USACE business lines into a single framework.

CWMS: Corps Water Management System. This system has been developed by the United States Army Corps of Engineers (USACE) Hydrologic Engineering Center in Davis, CA. The system consists of hydrologic models, processes, database schema, API, procedures, and a system architecture that supports the USACE water management mission.

DECODES: Device Conversion and Delivery System. DECODES is the module within OpenDCS (Open Data Collection System) that takes data from a variety of recording devices and converts the data into standard engineering units, suitable for entry into a database.

DoD: The Department of Defense.

DSS: Data Storage System. A set of data file formats used by the USACE Hydrologic Engineering Center (HEC) for storing data.

Elements 360: A product by OneRain/AEM that provides a means to acquire and monitor data collection systems. The software product is the next generation of software package Contrail.

ENG: Engineering.

G6: USACE Information Technology group. USACE-IT maintains the computer and information systems of the United States Army Corps of Engineers.

GDACS: Generic Data Acquisition and Control System used by the USACE for automatically monitoring and controlling facilities across the United States.

GOES: Geostationary Operational Environmental Satellite. Operated by the United States National Environmental Satellite, Data, and Information Service (NESDIS) under NOAA, these satellites provide the means to acquire environmental data. The data from these satellites support weather forecasting, severe storm tracking, and meteorologic and hydrologic operations and research.

HEC: The USACE Hydrologic Engineering Center in Davis, CA.

HRIT: High Rate Information Transmission. The HRIT is an evolution of two existing data platforms, the legacy Low Rate Information Transmission (LRIT) and the Emergency Managers Weather Information Network (EMWIN) that is currently two separate transponders onboard GOES-NOP series satellites. The HRIT messages are received via GOES satellite by a dish and a HRIT receiver.

HydroDCS: HydroDCS is a network appliance that acquires data via the government owned OpenDCS software and provides methods for visualizing the data. The HydroDCS appliance was developed by OLAV & Co., Inc. under contract with USACE.

Hydromet: Hydromet refers to the collection of hydro-meteorological data by USACE Water Management. This includes the data collection platforms (DCPs), sensors, power systems, and transmission methods for acquiring the hydro-meteorological data.

KO: Contracting Officer.

KTR: Contractor.

LRGS: Local Readout Ground Station. A module included in the OpenDCS government software that is used to receive data from GOES satellite and other data sources. Data received through the LRGS is usually processed through the DECODES module of the OpenDCS software.

NTP: Notice to proceed. When the Contractor receives this message from the KO then the Contractor can commence work related to the contract/task order.

OpenDCS: Open Data Collection System. Government software package that contains modules for receiving, decoding, performing computations and transformations on the data and posting the data into a database. The modules contained in OpenDCS include LRGS, DECODES, and the Corps Computational Processor (CCP).

POC: Point of contact.

PRS: Performance Requirements Summary. The summary is used to determine if the Contractor meets the performance standards of the contract, as well as provides guidelines for how and when surveillance will be performed.

QASP: Quality Control Surveillance Plan. The Contractor uses the QASP to guide and document the implementation of the required management and quality control actions to achieve the specified results.

QCP: Quality Control Plan. A management plan for producing a quality product or service, on schedule and within budget.

Quality Assurance Evaluator (QAE): The Government employees responsible for checking Contractor performance.

RWCDS: Regional Water Control Data System. This is the Northwestern Division Portland management team encompassing supervisory and technical staff. This team maintains the data systems in support of the water management mission of the Northwestern Division Portland to include the Portland Division and Portland, Seattle, and Walla Walla districts.

U.S.: United States, referring to the nation United States of America.

USACE: United States Army Corps of Engineers.

WM: USACE Water Management.

3.0 Description of Services

3.1 Project Background

The USACE has been tasked by Congress to construct and operate facilities to provide flood control and utilize water resources for the benefit of the public interest. Facilities constructed by the USACE serve recreation, emergency management, power generation, water supply, fish recovery, and other purposes. The USACE is mandated to be a steward of water as a resource. As an environmental steward, the USACE collects and manages data about all aspects of the environment relating to water, which includes hydro-meteorological, water quality, fish, and other biological considerations that are utilized in near real-time, emergency or long-term decision making.

Every aspect of water stewardship has the need to collect and manage data. Each aspect may either have their own data system or may need a data system to operate efficiently and share the data collected with various interest groups to include water management. The USACE Water Management data systems collect mission critical data from the field and make it available to operators, regulators, and managers of the USACE projects. The data is also used in models to produce scenarios that could have occurred or may occur in the future. Managers and partner agencies also use this data and the products produced from the system to make decisions.

The USACE Northwestern Division (CENWD) in Portland, OR has a Regional Water Control Data System (RWCDS) encompassing four offices in three different cities. This system consists of three nodes with the same equipment and configuration at each of the nodes. The nodes are located in Portland, Seattle, and Walla Walla. The three nodes mainly service four USACE Water Management offices that include Division Water Management in Portland, Portland District (CENWP), Seattle District (CENWS), and Walla Walla District (CENWW). The three nodes system files are kept in sync with operating system resources and database industry standard replication methods. Each office manages their data collection, acquisition, posting, and dissemination processes and products within a regionally defined framework.

One component of the data system is the Corps Water Management System (CWMS) software suite and database schema. A Sun server hosts the software in Solaris Zones. The CWMS software, database and local applications are hosted in these zones. During the performance period of this contract the Sun servers may be replaced with Linux servers with different virtual machine configurations. The servers are currently hosted on premises with the potential to migrate these resources to a Cloud environment.

A substantial amount of data is shared between the USACE and various agencies. Linux Cloud servers host data exchange and public web services with various agencies. The RWCDS maintains these instances to ensure a robust architecture.

The RWCDS develops code that is platform-independent and modular in nature. Work may include research on existing state-of-the-art technologies, technical recommendations, strengths and weaknesses of proposed options, deployment recommendations and plans, solution implementation, prototyping, deployment, on-going maintenance and support plans.

3.2 Services to Be Provided

The work required for the contract will include typical computer and programming skills such as software analysis, database development, web development, hardware and system development, user interface development and systems integration. For this IDIQ, USACE expects the work to involve publicly releasable Water Management datasets. While the contractor may have access to system architecture information, the Government will provide and control the environment in which any such architecture details are viewed, discussed, and stored. The Government will not require the contractor to process, store, or transmit Controlled Unclassified Information (CUI) or Federal Contract Information (FCI) on contractor-managed systems. So, no CMMC is required. Any architecture or security artifacts will remain within Government-provided systems. Any higher CMMC requirements should only be applied at the task order level if a future task order requires CUI or FCI to be handled on contractor-managed systems.

The Contractor shall have the capabilities to address the following aspects of the Water Management data system with the appropriate skills.

3.2.1 Data Collection

Data collection is work that relates to capabilities, equipment and systems in the field. Work efforts would focus on hardware solutions that may include physical components as well as human-machine interfaces, transmissions capabilities, and other related efforts. Tasks may include field and office installation.

Example tasks for data collection include the development of programming protocols on data collection platforms, integration of communications devices with data collection platforms, or the development of an interface for controlling a communication device or a data collection platform. In defining and performing these tasks, the following relative effort is anticipated.

Expertise Percent IT Hardware and System Development

55 %

IT Systems Integration

Knowledge of USACE Data Systems 5 % Programming 30 % User Interface Development 10 % Web Development Databases

3.2.2 Data Exchange

Data exchange is the processes and systems which get, put and modify data and products. Data can be acquired via webservices, sftp, html or other means. Data is transformed using relational tables, computations, and translations. Processes occur between various systems utilizing different operating systems, application programming interfaces, scheduling programs and programming languages.

Solutions will support the integration of processes across systems. Examples of software utilized include CWMS, CCP, GDACs, Aquarius, Contrail, and other software that utilizes XML and JSON. Languages currently used include Bash, Python, R, JavaScript, and HTML5. Current resources are on premises on the USACE network and Cloud based. Example tasks for data exchange include developing methods for retrieving data from web services, transforming data from the retrieved format to an ingestible format for the system, and writing the transformed data to the appropriate location for ingesting into the system. In defining and performing these tasks, the following relative effort is anticipated.

Development

IT Systems Integration 40 % Knowledge of USACE Data Systems 5 % Programming 30 % User Interface Development 10 % Web Development 10 % Databases 5 %

3.2.3 Data Management

Data management is the storage of data and information. The CWMS database API, CDA, is the standard method for interacting with the CWMS schema. The CWMS database is utilized to support the water management mission, and support processes used to carry out that mission. Data to be stored includes meteorological, hydrological, meta-data, agency documents, industry documents, measurement locations, dams, and reference information about river systems. Aspects of business processes may be stored and managed for continuity and availability. Information will be managed and made available using current industry standard technologies as appropriate. Common storage platforms may include Oracle, Postgres, MongoDB, CWMS, PLSQL, SQLite, and portals. Example tasks for data management include developing schemas to store additional hydro-meteorological meta-data and building out information sharing structures. In defining and performing these tasks, the following relative effort is anticipated.

Programming 20 % User Interface Development 10 % Web Development 10 % Databases 55 %

3.2.4 Data Visualization

Data visualization is the representation of data which conveys the content in a context appropriate manner. Visualization can be static or dynamic products, dashboards, portals, webpages, and other user interfaces. Data can be displayed in tabular, graphical, or GIS forms. Technologies used to provide visualization may include NodeJS, HTML5, JavaScript, CGI, PHP, Apache, NGINX, and Tomcat among others. Example tasks for data visualization include building dashboards to display the status of project operations and building a series of webpages to organize supporting content for the water management mission. In defining and performing these tasks, the following relative effort is anticipated.

Programming 10 % User Interface Development 30 % Web Development 55 % Databases

3.2.5 System Design

System design is the architecture utilized to support the integration of technologies necessary for the water management mission. Design elements include researching current technologies and methodologies, gathering use-case requirements, defining roles and responsibilities, and proposing solutions with pros and cons. Criteria used to evaluate proposed solutions would include implementation considerations, management, the USACE IT environment, and maintenance requirements. System design also includes the implementation and deployment of selected proposals. System design may include Water Management systems, hydrologic systems, Cloud based solutions, other USACE or commercial systems, processes, and integration with existing systems. Example tasks for system design include development of recommendations for architecture to support the use of WaterML or HydroJSON for ingestion of data into CWMS and architecture to retrieve and process data from partner agencies (USGS, USBR, NRCS, and others) into CWMS. In defining and performing these tasks, the following relative effort is anticipated.

IT Systems Integration 40 % Knowledge of USACE Data Systems 35% Programming 20% User Interface Development Web Development Databases 5%

4.0 Government Will Furnish

4.1 System Architecture and Processes Information

The Government will provide information for each task order regarding the applicable architecture and processes of the Water Management data systems so methods and procedures will be developed according to the framework in existence.

4.2 Equipment And Supplies

The Government may provide a government computer and workspace for accessing the USACE network.

Equipment to be provided and location of services will be defined at the task order level.

4.3 Dependent Work

Where there are dependencies regarding other IT systems and software products, the Government will coordinate with the appropriate entity. This includes, but is not limited to, the USACE Hydrologic Engineering Center, ACE-IT, OneRain/AEM, and Aquatic Informatics. The Government will provide the resources necessary to establish environments and products that will facilitate a successful solution. If an environment or product cannot be established or altered to accommodate a particular solution, then modifications to the implementation of that solution will be discussed and implemented.

4.4 System Knowledge

The Government will provide details of system architecture pertaining to each task, however, will not provide training on commercially available software products.

5.0 Contractor Shall Furnish

The Contractor shall furnish all labor, equipment and materials necessary to perform required services under this contract and comply with all local, state, and federal regulations during the performance of services.

6.0 Performance Standards and Requirements

6.1 Issuance of Task Orders

The Contracting Officer will issue a Request for Proposal (RFP) when contractor services are required. After receiving an RFP, the Contractor shall provide a proposal within five business days.

6.2 Location of Services

The location of work performed under this Contract shall be stated in the individual task orders. The Government expects the bulk of the task orders to be issued by CENWP; however, the Contracting Officer may issue written authorization to any USACE activity to issue task orders under this Contract.

6.3 Task Order Management

The Contractor shall provide product management and coordination for work tasks during production of all task orders. The Contractor shall assign a Project Manager (PM) to act as a primary point of contact (POC).

The PM shall be responsible for the coordination of work developed under each task order. Within three calendar days of an issued task order, the Contractor shall advise the CENWP Contracting Officer’s Representative (COR) in writing of the individual so designated.

6.4 Domain Knowledge

Domain knowledge in surface water and meteorology is critical for work effort success due to the nature of the USACE Water Management mission. The USACE Water Management mission has life and safety consequences. Therefore, when creating products for use by USACE Water Management it is imperative that the vendor’s personnel have experience working with surface water and meteorological information. The Offeror shall detail, in a page or less, a listing of knowledge, skills, and abilities relevant to their experience working with surface water and meteorological information.

6.5 Required Personnel

The Contractor shall provide personnel to fulfill the following responsibilities, and, where stated, with the following minimum education and experience:

6.5.1 Labor Category: Principal

Description: Handle client and business relationships and develop the mission and strategic vision for the firm. The major responsibility is managing relationships and acting as a representative of company interests.

6.5.2 Labor Category: Project Manager

Description: Responsible for the planning, procurement, and execution of a project. First point of contact for any issues or discrepancies arising from within the project. Responsible for maintaining progress, mutual interaction, and tasks of various parties in such a way that reduces the risk of overall failure, maximizes benefits, and minimizes costs.

6.5.3 Labor Category: Software Analyst/Programmer (Key Personnel)

Description: Responsible for knowing the software application domain, preparing software requirements, and specification documents. Conveys the demands of software users into programming tasks.

Responsibilities as a programmer include writing computer software as a software developer. The development environment should encompass both on premises and Cloud environments.

Minimum Education and Experience:

• Bachelor’s degree in a field such as Computer Science, Software Engineering, Computer Engineering or related computer science or engineering field; and 5 years of experience performing as a software analyst/programmer.

• OR

• 10 years of experience performing as a software analyst/programmer

6.5.4 Labor Category: Database Developer (Key Personnel)

Description: Practitioner of data architecture concerned with designing, creating, deploying, and managing data architectures. Responsible for how data will be stored, consumed, integrated, and managed by different data entities and IT systems, as well as any applications using or processing that data in some way.

Minimum Education and Experience:

• Bachelor’s degree in a field such as Computer Science, Software Engineering, Computer Engineering or related computer science or engineering field; and 5 years of experience developing databases and storage solutions

• 10 years of experience developing databases and storage solutions

6.5.5 Labor Category: Web Developer (Key Personnel)

Description: Practitioner of World Wide Web application development and user interfaces.

Responsible for how data is made available in a web environment and the look and feel of web pages that provide the user with a simple understandable way to view and obtain information. Practitioner in the development and deployment of static and dynamic web pages. The development environment should encompass both on premises and Cloud environments.

Computer Engineering, or related field of engineering, science or water resources; and 3 years working in the field of web development.

• 6 years working in the field of web development

6.5.6 Labor Category: Hardware and System Developer (Key Personnel)

Description: Practitioner in designing, testing, and updating computer hardware. Responsible for recommending and overseeing the production and assembly of prototypes. Perform modifications to hardware components for computers and evaluate existing computers. Use of complex problem-solving skills to improve systems.

• Bachelor's degree in Computer Science, Electrical Engineering, Software Engineering, Computer Engineering, or Mechanical Engineering; and 3 years of experience working in the area of hardware and system development.

• 5 years of experience working in the field of hardware and system development

6.5.7 Labor Category: User Interface Developer (Key Personnel)

Description: Practitioner in the design, development, and implementing of visual and interactive elements that users engage with to control, use, or otherwise interact with an application. Responsible for creating application front ends and integrating them with the business layer while following best practices and standards applicable to the application.

• Bachelor’s degree in a field such as Computer Science, Software Engineering, Computer

Engineering, or related field of engineering, science, or water resources; and 4 years of experience in user-interface development.

• 8 years of experience in user interface development

6.5.8 Labor Category: Systems Integration (Key Personnel)

Description: Practitioner specializing in bringing together components of a system into a fully functional system ensuring the components function together efficiently and effectively. Responsible for diagnosing and troubleshooting components and their interaction as well as researching and understanding existing products and software components. Responsible for designing and developing processes that bring together the components resulting in a functioning system. The development environment should encompass both on premises and Cloud environments.

Computer Engineering, or related field of engineering, science, or water resources;

and 7 years of experience involving system integration

• 10 years of experience involving system integration.

6.5.9 Labor Category: Clerical Support (Office Tech)

Description: Manage the routine administration tasks within an organization.

6.6 Required Expertise

The Contractor shall provide personnel with the following skills:

6.6.1 IT Hardware and System Development

Planning, developing, and providing advice on best design and standard practices for components of hardware and data systems. Examples of hardware include data collection platforms (DCPs), routers, switches, servers, transmitters, receivers, and Open-Source hardware.

6.6.2 IT Systems Integration

Integrating new development that adds or enhances functionality of the system with current system frameworks. Integrating various data collection methods and processes into an effective robust system.

Integrating networks so information, processes, and procedures can effectively and efficiently function as a complete system. Some of the systems that require integration and inter-connections include CWMS, OpenDCS, Hydromet, Aquarius, Contrail, GDACS, CBT Messenger, HydroDCS appliance, HRIT, various federal agency web services (such as USGS, USBR, National Weather Service, and NRCS), and state agencies web services (such as the Oregon Water Resources Department web service).

6.6.3 Knowledge of Data Systems

Knowledge of and experience working on data systems used by USACE. Some of the USACE data systems include CWMS, CWBI, OpenDCS, Hydromet, the Northwest Region RWCDS data system framework, Aquarius, Contrail, GDACS, CBT Messenger, and the HydroDCS appliance. Contractor employees must be able to meet USACE security requirements to obtain access to USACE computers that reside in all network segments (Production, Controlled Internet Accessible, Internet Accessible, and Cloud instances).

6.6.4 Programming

Programming for Sun Servers, virtual servers using VMware, Solaris, Linux, Windows environments, Cloud-based solutions, and platform independent programming. Programming and scripting languages might include: Bourne shell (sh), Bash shell (bash), C shell (csh), Korn shell (ksh), Perl, Unison, Java, JavaScript, REACT, AJAX, Apache, NodeJS, Jython, Python, R, VBA, Visual Basic, PL/SQL, HTML5 and/or CDA.

6.6.5 User Interface Development

Facilitating dialogue with users/customers to capture the design requirements stated and implied. Use of data flow diagrams, use cases, storyboards, or similar method for effective and efficient design of applications that require a user interface.

6.6.6 Web Development

Use of standard web protocols and development of hybrid client applications, web services, web-based tools, user friendly and configurable pages, and visually appealing web design. Understanding of the USACE Water Management national web page architecture that utilizes resources such as GitHub, REACT, CDA, and CWBI.

6.6.7 Databases

Familiarity and use of databases such as Oracle, PostgreSQL, the USACE Water Management database CWMS, SQLite, the USACE Hydrologic Engineering Center Data Storage System (HEC-DSS or DSS for short), MongoDB, XML, WaterML, and JSON. Management and configuration of relational database schema replication applications such as Oracle Streams and GoldenGate. Development of database schemas and effective organization of JSON and XML formatting. Testing, diagnostics, query building and testing, management, and administering of databases.

6.7 Personnel Replacement

The Contractor shall be responsible for the professional and technical competence of the personnel it assigns to perform the obligations under each task order. Changes to personnel assigned to each task order shall not occur without prior notification to the Government and approval of the Contracting Officer. Notification shall be submitted to the COR and the KO. The notification shall include documentation that supports how the employee meets the minimum education and experience requirements for their labor category as defined in Section 6.5 above, and that they have completed the security training requirements found in Section 7.2 below.

Replacement of personnel shall be carried out as quickly as possible, and in a manner that shall not adversely affect the performance obligations under the task order.

6.8 Metadata

Any data, database(s) and/or geospatial data produced for task orders must be documented through the preparation of standard metadata (data about data) descriptions. The Contractor shall ensure that the metadata delivered is compliant with the International Organization for Standardization (ISO) 19115-1:2014 and 19115- 2:2019, North American Profile (NAP). The Standard is available for purchase at:

https://www.iso.org/standards.html.

6.9 Codes and Standards

Work under all task orders shall comply with the latest codes, standards, and regulations applicable to the work requested including USACE Engineering Regulations and Manuals, and Industry Codes and Standards.

6.10 Correction of Unsatisfactory Work

The Government maintains the right to reject any work that is found to be in error, incomplete, illegible, or in any way not conforming to the specifications outlined in each task order. The Contractor shall be liable for all costs in connection with correcting such errors. Corrective work may be performed by the Government or by Contractor at the discretion of the KO.

6.11 Computer Virus Checking

Prior to submitting an electronic file or electronic media to the Government, the Contractor shall check it for viruses utilizing an anti-virus software package. The product utilized shall be current. The Contractor shall maintain a subscription or utilize a software product vendor who provides updates at least quarterly.

6.12 Geographic Information System (GIS)

The Contractor must be able to produce GIS data that meets USACE mandated Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE). A free copy of this software is available at the USACE CADD/GIS Technology Center website. These GIS files must be fully compatible with CENWP Enterprise GIS (EGIS) System which utilizes Environmental System Research Institute (ESRI) Geodatabase format. All geospatial data must also be documented through the preparation of standard metadata (data about data) descriptions. The Contractor shall ensure that the metadata delivered is compliant with the Federal Geographic Data Committee (FGDC) Standard “Content Standard for Digital Geospatial Metadata”, FGDC-STP-001-1998.

A free copy of this standard is available at the following website:

https://www.fgdc.gov/standards/standards_publications/index_html. Geospatial data must also conform to FGDC ESRI ArcCatalog Metadata Form, filling in at a minimum all required fields identified in the FGDC ESRI Stylesheet.

6.13 Quality Monitoring and Measurement

The Government will perform quality monitoring and measurement of services performed under each task order through a Quality Assurance Surveillance Plan (QASP).

https://www.iso.org/standards.html https://www.fgdc.gov/standards/standards_publications/index_html.

7.0 Security Requirements

7.1 Physical Security

The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

7.2 Anti-Terrorism/Operations Security (AT/OPSEC)

The Contractor shall submit the documents required to support AT/OPSEC requirements to the COR. This shall include:

• Foreign Born Employee Submittals.

• Naturalized Citizen Submittals.

• Candidates E-Verify Program Pre-screen Submittals.

7.2.1 AT Level I Training

All contractor employees, including subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website:

http://jko.jten.mil/courses/atl1/launch.html; or it can be provided by the RA ATO in presentation form which will be documented via memorandum.

7.2.2 Access and General Protection/Security Policy and Procedures

All Contractor and all associated sub-contractors’ employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The Contractor shall also provide all information required for background checks or background investigation and to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

7.2.3 For Contractors Requiring Common Access Card (CAC)

The Contractor and all sub-contractors employees will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an interim CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

7.2.4 Suspicious Activity Reporting Training (e.g. iWATCH, CorpsWatch, or See Something, Say Something)

The Contractor and all associated subcontractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the project manager, security representative or law enforcement entity. This training shall be completed http://jko.jten.mil/courses/atl1/launch.html%3B within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.

7.2.5 Contractor Employees Who Require Access to Government Information Systems

All Contractor employees with access to a government info system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the information systems and then annually thereafter in accordance with personnel security standards listed in AR 25-2 (Information Assurance), an appropriate background investigation will be conducted prior to accessing the government information systems.

7.2.6 For Contracts that Require OPSEC Training

All new Contractor employees will complete Level I OPSEC Training within 30 calendar days of their reporting for duty. Additionally, all Contractor employees must complete annual OPSEC awareness training. The Contractor shall submit certificates of completion for each affected Contractor and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training. OPSEC awareness training is available at the following websites:

https://www.iad.gov/ ioss/ or http://www.cdse.edu/catalog/operations-security.html; or it can be provided by the RA OPSEC Officer in presentation form which will be documented via memorandum.

7.2.7 For Information Assurance (IA)/Information Technology (IT) Training

All Contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All Contractor employees working in IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01- M and AR 25-2 within six months of employment.

7.2.8 For Information Assurance (IA)/Information Technology (IT) Certification

All Contractor employees supporting IA/IT functions shall be appropriately certified upon contract IAW DoD 8570.01-M, DFARS 252.239-7001 and AR 25-2. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

7.2.9 Pre-screen Candidates Using E-Verify Program

The Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award.

8.0 Other Considerations

8.1 Walsh-Healey Public Contracts Act or the McNamara-O'Hara Service Contract Act

Every employer performing work covered by the Walsh-Healey Public Contracts Act or the McNamara-O'Hara Service Contract Act (SCA) is required to post a notice of the compensation required (including, for service contracts, any applicable wage determination) in a prominent and accessible location at the worksite where it may be seen by all employees performing on the contract. A copy of the poster is available in two versions at the following DOL website: http://www.dol.gov/whd/regs/compliance/posters/sca.htm.

8.2 Veterans Employment Emphasis for U.S. Army Corps of Engineers Contracts

In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS 222.13 and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S. veterans while performing under a USACE contract. While no set-aside, evaluation http://www.iad.gov/ http://www.iad.gov/ http://www.cdse.edu/catalog/operations-security.html%3B http://www.uscis.gov/e-verify) http://www.uscis.gov/e-verify) http://www.dol.gov/whd/regs/compliance/posters/sca.htm preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:

• Federal Veteran employment information at http://www.fedshirevets.gov/index.aspx

• Department of Labor Veterans Employment Assistance at http://www.dol.gov/vets/

• Department of Veterans Affairs-VOW to Hire Heroes Act at http://benefits.va.gov/vow

• Army Wounded Warrior Program at http://wtc.army.mil/modules/employers/index.html

• U.S. Chamber of Commerce Foundation – Hiring Our Heroes at http://www.hiringourheroes.org/

Guide to Hiring Veterans – Reference Material http://www.fedshirevets.gov/index.aspx http://www.dol.gov/vets/ http://benefits.va.gov/vow http://wtc.army.mil/modules/employers/index.html http://www.hiringourheroes.org/ http://www.hiringourheroes.org/