A02.12 PWS NDC MATOC dated 2024.04.01.docx

Performance Work Statement

Navigation and Civil Works Data Analysis and System Support Professional Services Multiple Award Task Order Contract (MATOC)

Contents

Performance Work Statement (PWS)

1. Introduction U.S. Army Engineer Institute for Water Resources (IWR) is a Field Operating Activity (FOA) under the Commanding General, USACE, and the staff supervision of the USACE Headquarters (HQUSACE) Directorate of Civil Works under the direction of the Deputy Commanding General for Civil and Emergency Operations (DCG-CEO) and the Director of Civil Works (DCW). The IWR was established in 1969 to provide the U.S. Army Corps of Engineers (USACE) Civil Works (CW) Program with the capability to analyze and anticipate emerging water resources trends and issues facing our nation. From its beginning, responding to the continuing changes in water resources development policies, IWR has been tackling the complex water resources challenges stemming from an increasing public demand for water projects and the policy and technological challenges of the 21st Century. Analytical and professional support to USACE is required to pursue innovative approaches to solving these new problems.

IWR occupies a unique position within the USACE CW program. IWR’s challenging mission remains integral to shaping the evolution of Federal water resources policy as decision-makers at all levels within USACE look to IWR for insights into a host of complex and rapidly changing economic, environmental, climate and social issues.

2. Mission This MATOC will obtain technical and analytical support services for IWR that is generally not readily available within the USACE. These support services will be used by IWR in accomplishing its missions and supporting reimbursable work units for navigation and water resources work to include but not limited to the following:

· IWR data systems and applications support, including cyber security compliance, operation, maintenance, upkeep, and development support for all the centers within IWR, with an emphasis on the work performed by the Navigation and Civil Works Decision Support Center (NDC) in Alexandria, Virginia; and New Orleans Louisiana.

· Analysis of emerging trends and issues in anticipation of changing water resources management conditions to inform the strategic direction of CW missions and the corporate development of policies, programs and investment decision-support strategies, with emphasis on the Navigation mission.

· Systems-based planning methodologies, tools and training across CW business areas, analysis, economic and socio-economic assessments, enterprise capacity development, national economic analysis, multi-criteria and risk-informed analysis. Development of results-oriented CW Program through the management of national data systems, and application for investment decision support to USACE CW on an enterprise level.

3. Scope Among the broader purposes stated in Section 2, this MATOC will support NDC’s operation, maintenance, upkeep, enhancement, and development of Automated Information Systems (AIS) and applications operated and/or otherwise managed by IWR and its various centers. Delivered services will require consideration of data and analytical requirements of the USACE’s CW water resources missions to include the areas of study and expertise that IWR provides to its customers through its research, analysis, technical assistance and training activities to include but not limited to Navigation, Flood and Storm Damage Reduction, Aquatic Ecosystem Restoration, Emergency Management, Water Supply, Hydropower and Recreation.

The incorporation of CW water resources mission support functions may include, but are not limited to the following:

· Server, Software, and Data System Maintenance

· Research and Development of Software, including Models and Data Management and Analytical Applications

· Modernization and Migration of Software for Operation from On-premise and/or Cloud Environments

· Cyber Security Risk Management Framework (RMF) and Information System Security Officer (ISSO)Services

· Data Management and Analysis

· Documentation and Training Support

· Special Studies and Investigations

· Decision Support Analysis & Assessments

· Economic Analysis Among the AISs and applications for which NDC support will be sought are those operated and/or otherwise managed by the NDC, including the: Lock Performance Monitoring System; Dredging Information System; Notices to Navigation Interest Information System; Transportation Operations and Waterborne Statistics System; and their government-internal and public-facing applications. This contract will also allow for delivery of similar services for other yet-to-be named systems operated, managed, or supported by the IWR and its Centers. The four specific AISs referenced above are described below:

3.1 Lock Performance Monitoring System (LPMS) – a cloud-based (Amazon Web Services) integrated data system designed to manage information and data associated with characteristics, disposition, operation, status, utilization, and overall performance of the Nation’s navigation locks.

3.2 Dredging Information System (DIS) – a cloud-based (Amazon Web Services) integrated data system designed to manage information and data associated with scope, characteristics, costs, planning, scheduling, awarding, and execution of USACE dredging programs and projects.

3.3 Notices to Navigation Interests Information System (NTNI) – a cloud-based (Amazon Web Services) integrated data system designed to manage information and data associated with scope, characteristics, scheduling, duration, and anticipated effects of USACE actions that have the potential to affect navigation of/in the nation’s navigable waters.

3.4 Transportation Operations and Waterborne Statistics (TOWS) System – a suite of databases and applications that support ingest, review, management, retrieval, reporting, and digital publication of waterborne commerce statistics (e.g., vessel operations and movements, commodity movements) and related data (e.g., dock and navigation infrastructure characteristics, port and statistical boundaries, waterway networks, commercial navigation routes), that are being transitioned from an on-premise environment into a cloud-based (Amazon Web Services) integrated data system.

Each of the referenced data systems includes government-internal user interfaces and data services designed to support:

· Data entry, retrieval, and management; data quality assurance and control; data processing, analyses, aggregation, and visualization; reporting and publication; and cross-AIS data integration (including exchange of data with other USACE AISs).

Each of the referenced data systems also includes public-facing user interfaces and data services designed to support:

· Data aggregation and obfuscation required to ensure compliance with relevant laws and policies, data and information retrieval; visualization; reporting; and cross-AIS data integration.

3.5 Automated Information Systems Service (AIS’s)

AIS capabilities will require understanding of the following:

a) Relational and geospatial database schemas, API, and user interface development and support requirements for AISs including but not limited to LPMS, DIS, NTNI, and TOWS.

b) Web services and related software.

c) Database modernization, integration, and innovation, including awareness of such activities occurring with LPMS, DIS, NTNI, and TOWS systems, and broader industry and technological trends and advancements.

d) Cloud development and migration (familiarity with multiple cloud providers).

e) Support for AISs including enabling and facilitation of interoperability with other database, web services, and scripting and automated processes. Deep familiarity and experience with relational and geospatial database and system functions and use cases, database structure, code, and relationships among data systems operated and/or otherwise managed by the IWR and its Centers, including those operated and/or otherwise managed by the NDC and its Waterborne Commerce Statistics Center (WCSC).

f) Timely deployment of AISs maintenance patches, updates, new feature development, and troubleshooting

g) Authentication and privilege management – components such as those associated with LPMS, DIS, NTNI, and TOWS database access and management controls, web services, and login servers.

h) Provide RMF and ISSO Support.

i) User interface maintenance updates, new feature development, and troubleshooting.

j) Data Quality Control (QC), analysis, and reporting support to USACE Headquarters, Divisions, and Districts.

k) Software Quality Assurance (QA)/QC processes.

l) Techniques to dynamically aggregate and disaggregate data for purposes of disabling ability to attribute or deconstruct analyses of data to identify individual sources, to include techniques applied to LPMS, DIS, NTNI, and TOWS pursuant to requirements of the Trade Secret Act and related laws and regulations.

m) Miscellaneous improvements to other related LPMS, DIS, NTNI, and TOWS efforts.

n) Data Management Efforts.

o) In addition, the scope of this contract is intended to cover the areas of study and the kinds of expertise that IWR provides to its customers through its research, analysis, technical assistance and training activities to include but not limited to other relevant USACE work such as Climate Change; Hydrologic and Hydraulic Analysis and Engineering; Integrated Water Resources Management; Sediment Management; and Asset Management/USACE Infrastructure Strategy/Public Private Partnerships/Financing.

4. Performance Requirements

The following section specifies the Performance Objectives and Performance Elements for the contract. The scope of this effort focuses primarily on support for the Civil Works Navigation Data Center, mission but also encompass aspects of other mission areas that connect with Navigation (including Flood Risk Management, Aquatic Ecosystem Restoration, Hydropower, Regulatory, Recreation, and Water Supply, Emergency Management, etc.) and support the overall USACE mission. Within the broad range of activities identified within this scope and performed by USACE, tasks may be required within any of the missions, business or program areas described in Sections 2 and 3, either domestically or internationally. It is anticipated that in many cases, extensive subject matter expertise and cutting-edge technologies and strategies will be required to perform the complex analysis and development of state-of-the-art solutions and deliverables associated with the tasks described below.

4.1 Data Management and Decision-Support Systems and Tools

4.1.1 Develop, enhance, and maintain automated information management and decision support systems and affiliated tools to support management, analysis, integration and delivery/publication of navigation and civil works data and information. Examples of systems that might be supported under subsequent task orders include but are not necessarily limited to: Lock Performance Monitoring System, Master Docks Plus (MDP or MD+), Waterborne Commerce Statistics DB (TOWS), Notice to Navigation Interests (NTNI), Dredging Information System (DIS), and Civil Works Business Intelligence (CWBI) which may link to other USACE and Federal systems.

4.1.2 Provide data management support services including, but not limited to maintenance of metadata consistent with USACE and nationally/intentionally recognized metadata standards.

4.1.3 Develop and deliver user support, training, and system help documentation for navigation, other civil works data and associated information management systems and tools/models.

4.1.4 Integrate relevant elements of emerging research and technological advances to assist IWR with developing future data management, processing, analytical, and decision-support applications and systems, and support development of relevant guidance and policy recommendations.

4.2 Data, Collection and Analytical Methodologies, Tools, and Models

4.2.1 Develop analytical methods, tools/models to support analyses, survey designs, and survey instruments for use in support of USACE navigation and other civil works missions.

4.2.2 Provide end-user support on deployed and/or supported systems, methods, tools, and models for use in support of USACE navigation and other civil works missions.

4.2.3 Develop and test software and models for use in support of USACE navigation and other civil works missions.

4.2.4 Conduct research and analysis (includes data collection as appropriate) in support of developing methods and analytical tools relevant to navigation and other civil works mission data collection, management, and decision-support needs.

4.2.5 Integrate findings and products of leading-edge research in support of developing state-of the art methodologies and analytical tools for navigation and other civil works mission data collection, management, and decision-support needs.

4.3 Training and Multi-Media Support

4.3.1 Develop, modify, and/or present materials for training courses on topics including (but not limited to) data collection and management, data analysis, economic analysis, and decision analysis and decision making.

4.3.2 Develop associated multi-media products and/or exhibits for professional conferences, exhibitions, training environments, and USACE or IWR-NDC internet and intranet.

4.4 Decision Support, Analyses, Assessments

4.4.1 Perform strategic analyses or assessments on emerging and potential needs for navigation and waterborne transportation in addition to emerging issues that may arise for other USACE missions and business lines.

4.5 Navigation and CW Studies and Analysis

4.5.1 Conduct studies, assessments, and evaluations to examine the relevancy and effectiveness of current navigation and CW policies and guidance, the need for new policies and guidance, programs, operating procedures, rulemaking and approaches, and options available to USACE in resolving current issues.

4.5.2 Conduct studies and provide study support for USACE CW policy, programs, research, and related investment issues, needs, and requirements.

5. General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

5.1 Non-Personal Services

The government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (KO) immediately.

5.2 Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute the requirement. The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

5.3 Contract Administration and Management

This section describes the contract administration and management for this effort. The following sub-sections provide details of various considerations on this effort.

5.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor must maintain continuity between the support operations at the location specified in individual Task Orders and the contractor's corporate offices.

5.3.2 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively administer the requirement. The contractor shall respond to Government requests for contractual actions in a timely fashion. The contractor shall have a single point of contact between the government and contractor personnel assigned to support contracts or task orders. The contractor shall assign work effort and maintaining proper and accurate time keeping records of personnel assigned to work on the requirement.

5.3.3 Personnel Administration

The contractor shall provide the following management and support as required. The contractor shall provide for employees during designated government non-work days or other periods where government offices are closed due to weather or security conditions. The contractor shall maintain the technical competency of their employees by providing initial and refresher training as required to meet the task order PWS requirements. The contractor shall make necessary travel arrangements for employees. The contractor shall provide necessary infrastructure to support contract tasks.

The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs). If the capability, knowledge, and expertise is no longer available, the contractor is responsible for providing individuals with comparable qualifications in a timely manner to maintain the schedule of service or deliverables required by current task orders.

5.3.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The contractor shall also be responsible for insuring timely payment to subcontractors. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add or subtract subcontractors to their team after notification to the KO or COR.

5.3.5 Contractor Personnel, Disciplines, and Specialties

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The contractor shall match personnel skills to the work or task with a minimum of under/over employment of resources. The contractor shall ensure the labor categories as defined in the Labor Categories document (Appendix A), labor rates, and man-hours utilized in the performance of each task order issued hereunder will be the minimum necessary to accomplish the task. The contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

5.3.6 Location and Hours of Work

Unless specified at the individual task order level, the work required on this solicitation is expected to be carried out at the contractor’s location. If work is required at government facilities, normal workdays are Monday through Friday except US Federal Holidays. Federal workers typically work eight (8) hours per day, 40 hours per week. Contractors will adhere to their respective employer’s labor agreements for what Federal holidays they are eligible to have leave granted.

5.3.7 Travel / Temporary Duty (TDY)

Travel to other government facilities or other contractor facilities may be required and will be specified in the PWS. Costs for travel shall be billed in accordance with the individual delivery order and regulatory implementation of Public Law 99-234 and FAR 31.205-46 Travel Costs (subject to local policy & procedures; may reference FAR).

6. Security and Safety Requirements This section describes the Security and Safety special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

6.1 Security

Overarching security requirements and Contractor access to classified information shall be as specified in the basic DD Form 254, which will be further identified in the DD Form 254 for each TO, as required. Note, while IWR may at some point, be involved in classified work, it is a rare occurrence. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum, a favorable National Agency Check (NAC).

6.1.2 Visitor Group Security Agreement

The contractor shall sign a Contractor Visitor Group Security Agreement to protect classified information involved in work performed under this contract or Task Order. The Agreement will outline responsibilities in the following areas: Contractor security supervision; Standard Practice Procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection; protection of government resources; DD Forms 254; periodic security reviews; and other responsibilities, as required.

6.1.3 Other Security Requirements

General security requirements and guidance: The security requirements described below apply to all contract personnel (including employees of the prime contractor and all subcontractor employees) supporting the performance requirements of this contract. The contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated government representative (e.g., COR, TPOC, or other representative identified in an individual task order, or KO (if a COR, TPOC, or other representative is not appointed)).

The Department of Defense (DoD) and Army/USACE-specific security requirements specified below, if applicable, are performance requirements. All contract personnel shall complete applicable initial training within 30 days of contract award, or the date new contract personnel begin performance on the contract. The contractor shall maintain security training records in accordance with applicable Requiring Activity (RA) policies. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as “RAMs”), and Health Protection Condition (HPCON) measures.

The contractor is responsible for meeting performance requirements during elevated security in accordance with applicable RA plans and procedures - this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the government may implement security changes that affect contract personnel. The contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.

6.1.4 Information Assurance (IA)/Information Technology (IT) requirements All contract personnel performing IA/IT services must comply with DoD training and certification requirements specified in DoD 8570.01-M, Information Assurance Workforce Improvement Program, and maintain required background investigations specified in RA policy. Contract personnel shall provide the Government representative with documentation of certification(s) prior to performing on the contract. In accordance with applicable DoD, Army, and USACE regulations, the Contractor shall ensure that all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract comply with cybersecurity and architectural requirements, including, but not limited to: security technical implementation guides (STIG)(e.g., the current version of the Application Security and Development STIG, and the internet access point (IAP) demilitarized zone (DMZ) STIG), and the use of security controls developed under the risk management framework documentation for the system or platform. The Contractor shall address questions regarding these provisions to the Government representative, who will coordinate between the Contractor and the USACE Chief Information Officer (CIO).

6.1.5 Antiterrorism (AT) Level I Training

All contract personnel requiring routine access to Army installations, facilities, and controlled access areas, or requiring network access shall complete initial and annual refresher AT Level I awareness training. Online AT Level I awareness training is available at https://jko.jten.mil/ (website subject to change).

a) Physical security and access control requirements: All contract personnel requiring physical access to a federal installation or facility shall comply with the access control procedures of that location. Contract personnel requiring unescorted access to meet contract performance requirements on a DoD installation in the US shall be vetted by the installation/facility Provost Marshal/Directorate of Emergency Services/Security Office using the National Crime Information Center-Interstate Identification Index (commonly referred to as “NCIC-III”) and Terrorist Screening Database (commonly referred to as “TSDB”). Contract personnel shall comply with all personal identity verification requirements specified in installation/facility policies and procedures. Contract personnel who do not meet requirements for unescorted access to USACE facilities shall coordinate escorted access with the government representative, as needed. Contract personnel who receive keys, access cards, or lock combinations that provide access to government-owned property shall comply with key and lock control procedures of the RA.

b) Contract personnel requiring a common access card (CAC): contract personnel will be issued a common access card (CAC) only if duties involve one of the following: (1) both physical access to a DoD facility and access to DoD information systems or networks; (2) remote access to a DoD information system or 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. Before CAC issuance, contract personnel must have, at a minimum, a favorably adjudicated Tier 1 investigation or an equivalent or higher investigation in accordance with applicable Army regulations and Homeland Security Presidential Directive-12 (HSPD-12). At the discretion of the RA, an initial CAC may be issued based on a favorable review of a fingerprint check and a successfully scheduled Tier 1 investigation with the National Background Investigations Bureau. The RA provides contract personnel with additional information and forms to initiate the CAC issuance process, and/or to initiate background investigations, when required. Contract personnel shall complete these processes within established timelines to avoid delays.

c) Suspicious Activity Reporting Training (e.g. IWATCH, Corps Watch, or See Something, Say Something). All contract personnel shall receive initial and annual refresher training from the RA representative on the local suspicious activity reporting program. This locally developed training provides contract personnel with general information on suspicious behavior, and guidance on reporting suspicious activity to the project manager, security representative or law enforcement entity.

d) Contractor employees who require access to government information systems. All contract personnel with access to a government information system (including USACE business systems and CAC-enabled websites) shall comply with applicable DoD and Army regulations and shall use the organization's User ID-Password Administration and Security System (U-PASS) at commencement of services to request network user accounts. Contract personnel shall complete DoD Information Assurance Awareness training prior to accessing information systems, and annually thereafter.

e) Contracts requiring a formal Operations Security (OPSEC) program: The contractor shall develop an OPSEC SOP/Plan within 90 days of contract award. The OPSEC SOP/Plan shall be reviewed and accepted by the RA OPSEC Officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it, and why it needs to be protected. In accordance with Army and DoD regulations, the contractor shall have a certified Level II OPSEC coordinator, who shall ensure OPSEC compliance during contract performance.

f) Training requirements for the protection of sensitive information: All contract personnel with access to critical information (as identified in the RA's OPSEC Program) shall complete initial and annual refresher OPSEC Level I Awareness training, which is available at the following website http://www.cdse.edu/catalog/operations-security.html (websites subject to change). All contract personnel with access to Controlled Unclassified Information (CUI) shall complete initial and annual refresher CUI training in accordance with applicable Army policy.

g) Contracts requiring handling or access to classified information: The prime contractor shall have a Facility Clearance (FCL) at the appropriate level prior to performance on the contract; the RA will sponsor the prime contract company in obtaining the FCL. All cleared contract personnel shall comply with the FCL requirements, as well as applicable laws and regulations regarding contractor access to national security information. For classified contracts, the RA will generate the DD Form 254, which will be attached to the contract.

h) Threat Awareness Reporting Program: All contract personnel who maintain an active security clearance shall receive initial and annual refresher training on the Threat Awareness and Reporting Program (commonly referred to as “TARP”), provided by a Counterintelligence Agent. As determined by the servicing Counterintelligence Agent for the RA, contract personnel may complete web-based TARP training.

i) Escorting in classified and/or sensitive areas: In accordance with applicable regulations, all contract personnel who do not possess the appropriate security clearance or access privileges will be escorted in areas where they may be exposed to classified information or operations, sensitive information or activities, or restricted areas.

j) Pre-screen candidates using E-Verify Program: contractors shall comply with the requirements set forth in FAR clause 52.222-54 Employment Eligibility Verification and FAR Subpart 22.18 in using the E-Verify Program at (https://www.e-verify.gov/) (website subject to change) to meet the contract employment eligibility requirements. Contractors are encouraged to cooperate with Federal and State agencies responsible for enforcing labor requirements to include eligibility for employment under United States immigration laws in accordance with FAR 22.102-1(i). An initial list of verified/eligible candidates shall be provided to the COR within 2-weeks following initial contract award. When contracts are with individuals, the individuals will be required to complete Form I-9, Employment Eligibility Verification, and submit it to the KO for inclusion in the official contract file.

6.1.6 Local Security Policy

a) All contractor employees who require physical access to government-controlled facilities or logical access to government information and or information systems are subject to a fitness determination and appropriate vetting. The Humphreys Engineer Center Support Activity (HECSA) utilizes the same OPM guidelines for fitness determinations that are used to determine suitability for federal employment under 5 CFR part 731.

b) To assist in the vetting process, the contractor must submit information through the government COR or TPOC who will deliver the information to the security office. All notice of visits must be received no later than twenty-four business days in advance of the contractor reporting for work unless an exception is requested by the COR and approved by the security office.

c) The COR or TPOC for each contract is the liaison between the security office and the contractor. Contractor employees who are not sponsored by a government employee will not be granted access to any facilities under HECSA control nor will HECSA security approve access to information systems if the COR does not provide the notice of visit containing appropriate contractor information.

d) The type of investigation a contracted employee is subject to depends on the type of work being performed and the duration of access required. The minimum requirement for vetting personnel who do not require a common access card is the NCIC III. Contractors who need a common access card must have the minimum of a current favorably adjudicated NACI on file. If no investigation is on file the CAC will not be issued until a favorable FBI fingerprints check is received by the security office and the NACI has been initiated in PSIP.

e) If an employee has been the subject of a previous favorably adjudicated investigation, it may be reciprocally accepted if there has not been a two-year break in service and there is no presence of new and potentially unfavorable information that casts doubt about the subject’s suitability. When a background check is reciprocally accepted but is more than 5 years old, the security office may initiate an NCIC III check to ensure no new unfavorable information exists.

f) Contractor employees whose access to classified information has been suspended or revoked will not be authorized logical access to information systems IAW AR 25-2 paragraph 4-14 b (2) until that investigation is favorably adjudicated. These personnel will also not be allowed unescorted access to government facilities until the investigation has been favorably adjudicated by the Command Security Manager. The contractor must provide employees who can be cleared to perform work and must immediately provide replacement employees for those who cannot be cleared.

6.2 Safety

6.2.1 Contractor Compliance

The contractor and its subcontractors shall comply with Public Law 91-596 (Occupational Safety and Health Act (OSHA)) and the Environmental, Safety, and Occupational Health (ESOH) (DODD 4715.1E). These requirements shall be incorporated into the contractors’ safety and health program. The Department of Defense (DoD) participates in the OSHA Voluntary Protection Program (VPP). Contractor personnel performing services on a DoD installation shall participate in the local VPP. Information on the VPP is available at https://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=1&p_keyvalue=1910 ) and EM 385-1-1 USACE Safety Regulation http://www.publications.usace.army.mil/Portals/76/Publications/EngineerManuals/EM_385-1-1.pdf

6.2.2 Mishap Notification and Investigation

The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving government property damage or injury to Government personnel and to cooperate in any resulting safety investigation. The contractor shall notify (via telephone) the cognizant KO, the COR, and/or other applicable members within four (4) hours of all mishaps or incidents. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post. If requested by the cognizant KO, the COR, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the government personnel until the investigation is completed.

7.0 Special Requirements

7.1 Government Furnished Materials

It is not anticipated that the contractor will be working at government facilities. In cases where the government provides equipment or materials, it will be specified in the individual task order PWS. It is common for IWR to provide government furnished equipment to contractors who are working on AIS tools and programs. Each task order that requires government laptop(s) to perform work, shall require that an inventory of the government laptops shall be maintained for the duration of the task order. Each inventory shall include the following information: laptop(s) identified by barcode(s), the task order number that the laptop is required to support, and the name of the staff member assigned to each laptop. The inventory of laptop(s) shall be provided upon request by IWR Contracting Staff.

7.2 Quality

This section describes the Quality Control components for this effort. The following sub-sections provide details of various considerations on this effort.

7.2.1 Quality Control

The contractor shall develop a Task/Delivery Order Quality Control Plan (QCP) and maintain an effective quality control program to ensure all services are performed in accordance with this MATOC and all subsequent task orders. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractors QCP is the means by which he assures himself that his work complies with the requirement of the contract.

The finalized QCP will be accepted by the government at the time of the award of the Task/Delivery Order. The KO may notify the contractor of required modifications to the plan during the period of performance. The contractor then shall coordinate suggested modifications and obtain acceptance of the plan by the KO. Any modifications to the program during the period of performance shall be provided to the KO for review no later than 10 working days prior to effective date of the change. The QCP shall be subject to the government’s review and approval. The government may find the QCP "unacceptable" whenever the contractor’s procedures do not accomplish quality control objective(s). The contractor shall revise the QCP within 10 working days from receipt of notice that QCP is found "unacceptable."

7.3 Disclosure of Artificial Intelligence

The contractor shall fully disclose all uses (including proposed used of AI) of chat bots, large language models, neural networks, deep learning models, and/or other artificial intelligence code, applications, or services (collectively referred to as “artificial intelligence”), including integrated artificial intelligence features in commercial products, used during development, testing, and/or delivery of any proposals, services, or products developed in response to this contract and affiliated task orders.

Such disclosures shall include: complete identification information of the artificial intelligence used, including name, version, and release information; a description of the specific service or product on which the artificial intelligence was used; and a description of the specific role(s) and purpose(s) served by the artificial intelligence during development, testing, and delivery of services and products, and phase(s) and component(s) thereof. Any service or product delivered to the government shall be free of any constraints, conditions, and limitations on uses unless otherwise specified in subsequent task orders.

7.4 Authorities / Technical Direction

The contractor shall take no direction from any government employee or any other person other than the government KO for changes to the terms and conditions of this MATOC or any subsequent task orders for cost, schedule or terms of the stated work after award. Any direction given by any government employee or any other person outside their authority must be reported to the KO. CORs are limited to the authorities stated in the COR appointment letters. COR appointment letters from previous contracts at this installation are not valid for this contract.

7.5 Review and Comment Protocols

All draft work items produced by the contractor under any task order shall be submitted to the appropriate TPOC for review and comment. All final versions must also be reviewed and approved by the appropriate TPOC. Should the contractor not concur with a specific comment on any version of a document, the contractor shall bring this to the attention of the appropriate TPOC.6.8 Contract Data Requirements List The contractor shall provide deliverables as described in DD Form 1423, CDRL and subsequent task orders. Unless specified otherwise in the task order PWS, the contractor shall provide reports and other print deliverables in publication quality format and provide web publishable versions of such deliverables. All deliverables, including software, shall be provided to the government with unlimited rights. Format and delivery schedule for deliverables shall be outlined in individual task orders under the Contract Data Requirements List and/or other means to be determined. The table below identifies a set of deliverables that may be required under this contract. It should be noted that the table is NOT all inclusive of the types of deliverables that may be required.

CDRL #Deliverable Type

7.6 Quality Assurance Surveillance Plan (QASP)

The Government shall monitor the Contractors performance under each task order in accordance with the government’s QASP (Appendix B).

7.7 Maintenance of Data

The contractor must physically maintain all data solely on equipment located within the legal jurisdiction of the United States IAW DFARS 239.7602-2(b) . All data, including but not limited to documents, administrative data, support data, and billing data, transmitted via the system or maintained in the system shall always reside in data processing and storage equipment located in the United States or in data processing and storage equipment of which the operation and maintenance are subject only to the laws of the United States. Data transmitted must only be subject to disclosure pursuant to U.S. Federal law and not the laws of any other jurisdiction or foreign nation. All DoD information/data placed or created by DoD users in a Cloud Service Provider’s (CSP) Cloud Service Offering (CSO) is owned by the DoD, the Mission Owner, and/or their Information Owner. The CSP has no rights to the DoD’s information/data. For more information on data storage, data rights, and data ownership requirements refer to Section 5.2, Legal Considerations, in the DoD Cloud Computing Security Reference Guide (SRG).

The government shall retain unlimited rights to all development and automation performed and all data, Infrastructure-as-Code (IaC) or Configuration as Code (CaC) or processes created under this contract. This would not include code, processes, or automation that USACE might subscribe to that are commercially available under Commercial Use Rights and/or Government Purpose Rights.

The government shall retain unlimited rights of all user data/information/knowledge provided to, created/developed in, loaded/transitioned to, or hosted in/by the contractor, CSP, tenant, multiple CSP, multiple tenant, CSO, vendor IT infrastructure, hosting environment, system(s). This includes rights to logs, scans, analytics, and other data, conducted by the contractor, CSP, or tenant, on their IT infrastructure, hosting environment, system(s), or prototype process. The government retains the right to request full copies of this data at any time.

Contractors supporting scopes of work requiring access to the CWBI cloud environment must complete a DA7789 PAA and meet IL4 security training requirements as specified by Defense Information Systems Agency. All work performed in support of systems and applications CWBI residing in or planned for operation from within the CWBI cloud environment is to be performed from within the CWBI’s DevSecOps environment and perform all work in accordance with requirements of Federal Acquisition Regulation Supplement (AFARS) Part 5139 Appendix HH.

8.0 Deliverables

The contractor shall provide deliverables as described in subsequent task orders. Unless specified otherwise in the task order PWS, the contractor shall provide reports and other print deliverables in publication quality format and provide web publishable versions of such deliverables.

Reports, print deliverables and all documents published must comply with Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended in 1998, requires federal agencies to provide individuals with disabilities equal access to electronic information and data comparable to those who do not have disabilities, unless an undue burden would be imposed on the agency. The Section 508 standards are the technical requirements and criteria that are used to measure conformance within this law.

All deliverables, including software, shall be provided to the government with unlimited rights. Format and delivery schedule for deliverables shall be outlined in each subsequent task order under the Contract Data Requirements List and/or other means to be determined. The table below identifies a set of deliverables that may be required under this contract. It should be noted that the table is NOT all inclusive of the types of deliverables that may be required.

Deliverable Type Frequency

PERFORMANCE REQUIREMENT SUMMARY

Performance Standards: performance standards will be specified with each PWS solicitation. As a point of reference, the following is a table of potential performance standards.

Standard Acceptable Quality Level

Deliverables completed in accordance with schedule 100% of the time

9.0 Invoicing

9.1 General

Unless otherwise specified in task orders placed under this MATOC, invoices for each payment shall be submitted upon 100% completion of services/tasks and shall include all necessary information and supporting documentation. Payment and invoicing instructions will also be included in the Performance Work Statement with each order.

The Government shall pay the Contractor as full compensation for all work required, performed, and accepted under this contract, inclusive of all costs and expenses, the firm-fixed price stated in this contract.

The Contractor shall provide invoices in accordance with FAR 32.905(b). Electronic invoice submissions must be created in black and white and in Adobe’s Portable Document Format (PDF) and comply with the requirements specified within this contract. At a minimum, invoices must contain the following elements:

a) Name and address of the contractor (Note: Differences between the Contractor name and remittance address on the invoice and the data shown in the System for Award Management (SAM) record can potentially cause delays in payment.