SAP SOW MDAISUP_REDACT.pdf

All tasks and activities under this SOW shall be performed in accordance with the highest standards of quality, security, and integrity, ensuring that all outputs align with requirements and compliance standards.

3.1 Production and Delivery

The Contractor shall provide a phased AI delivery program built around the following :

3.1.1 Initial model Development

3.1.1.1 The Contractor shall further develop an initial AI model tailored to meet the specific objectives of the project. This shall include data collection, model training, and preliminary validation steps to ensure the model's foundational performance is aligned with the requirements

3.1.1.2 The Contractor shall produce and deliver a comprehensive performance report for Model performance. This report shall highlight quality assurance processes, confidence thresholds, and strategies for handling edge cases. The report shall also detail the specifics of the model's performance metrics and provide actionable insights for further improvements. (CDRL A001)

3.1.1.3 The Contractor shall perform further initial model development that adheres to state-of-the-art methodologies . This process includes:

Developing and training baseline models using initial datasets. These models shall utilize state-of-the-art machine learning techniques tailored to the designated use case.

Performing hyperparameter tuning and optimization to refine model performance.

Implementing rigorous testing protocols to validate the performance and scalability of initial models, ensuring they meet predefined criteria for accuracy, reliability, and robustness.

Providing training and support.

3.1.2 Initial Model Evaluation Score

The Contractor shall establish a metric for evaluating the initial model's performance. This score shall be calculated based on defined benchmarks and criteria The evaluation process shall include a comprehensive testing phase where the model's outputs are compared against expected outcomes to ensure accuracy and reliability.

At the end of the Contract, the Contractor shall provide the datasets developed for future use and further development. (CDRL A002)

3.2 Progress Reporting (CDRL A003)

The Contractor shall provide a monthly status report that identifies work accomplished, percent completion, funds expended, hours expended, problem areas, recommendations, and work planned for the next period.

The monthly status report shall include the following topics:

Narrative summary of the work performed and results obtained;

Anticipated activities for the following month;

An explanation of deviations from the last month’s projections;

Current or projected problems and issues being worked by the Contractor;

Current or projected problems and issues requiring government attention;

Trip Reports for travel performed including highlights/summary of technical discussion(s), action items and a list of attendees.

4.0 GOVERNMENT FURNISHED PROPERTY

4.1 Government Furnished Information (GFI)

The Government will provide the Contractor with documentation as required. All Government furnished information (GFI) shall be returned within 10 days after completion of the task order, unless otherwise directed in writing by the Contracting Officer.

4.2 Government Furnished Property (GFP)

The Government will provide the Contractor with relevant GFP, to be determined later and issued as required to complete the task order. All GFP shall be returned within 10 days after completion of the task order, unless otherwise directed in writing by the Contracting Officer.

5.0 SECURITY

The Contractor shall require access to classified information up to the SECRET level. All documents prepared under the Task Order will be UNCLASSIFIED. The Contractor will not be required to generate or store classified data to meet the requirements of this Task Order.

Provisions of the attached DD Form 254 for this task order apply.

5.1 Release of Information

(a) Release of information shall be in accordance with Section I, DFARS Clause 252.204-7000, Disclosure of Information.

(b) All technical data provided to the contractor by the Government will be protected from public disclosure in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the appropriate NSWC PCD authority. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising;

or any other proposed public release. The contractor shall provide adequate physical protection to such information to preclude access by any person or entity not authorized such access by the Government.

5.2 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

5.3 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Prior to access, Contractor personnel requiring access to Department of the Navy (DoN) controlled unclassified information (CUI) or "user level access to DoN or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DoN Central Adjudication Facility.

5.4 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides and unclassified limited documents (e.g., For Official Use Only (FOUO), Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

5.5 CUI

CUI is a document designation, not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause foreseeable harm to an interest protected by one or more provisions of the Freedom of Information Act (FOIA). This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. CUI must be marked, controlled and safeguarded in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI)

5.6 Security of Unclassified DoD Information on Non-DoD Information Systems (DoDI 8582.01) DoD Policy

Adequate security shall be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.

Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.

Information Safeguards

Unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

a. Non-public information provided to a Contractor (e.g., with a request for proposal).

b. Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

c. Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non- DoD entities on non-DoD information systems shall minimally be safeguarded as follows:

a. Do not process unclassified DoD information on publicly available computers (e.g., those available for use by the general public in kiosks or hotel business centers).

b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

c. At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the Contractor or teaming partner.

e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

f. Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security.

g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

i. Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of transport layer security or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).

j. Provide protection against computer network intrusions and data exfiltration, minimally including:

i. Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

ii. Monitoring and control of both inbound and outbound network traffic (e.g., at the external boundary, sub-networks, individual hosts), including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. Prompt application of security-relevant software patches, service packs, and hot fixes.

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, Critical Program Information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

m. Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

5.7 Operations Security

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.

Critical information includes information regarding:

Operations, missions, and exercises, test schedules or locations;

Location/movement of sensitive information, equipment, or facilities;

Force structure and readiness (e.g., recall rosters);

Capabilities, vulnerabilities, limitations, security weaknesses;

Intrusions/attacks of DoD networks or information systems;

Network (and system) user identifications and passwords;

Movements of key personnel or visitors (itineraries, agendas, etc.); and Security classification of equipment, systems, operations, etc.

The Contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

Practice OPSEC and facilitate OPSEC awareness;

Immediately retrieve documents from printers assessable by the public;

Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

Protect information from personnel without a need-to-know;

When promulgating information, limit details to that essential for legitimacy;

During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

6.0 DISTRIBUTION LIMITATION STATEMENT

Documentation generated under this task order shall have the following Distribution Limitation Statement and Destruction Notice affixed to the front cover and title page (if any):

DISTROBUTION STATEMENT F: FURTHER DISTRIBUTION ONLY AS DIRECTED

BY [CONTROLLING DOD OFFICE] [DATE OF DETERMINATION] OR HIGHER DOD

AUTHORITY.

DESTRUCTION NOTICE - FOR CLASSIFIED DOCUMENTS, FOLLOW

PROCEDURES IN DOD 5220.22-M, NATIONAL INDUSTRIAL SECURITY PROGRAM

OPERATING MANUAL, CHAPTER 5, SECTION 7 OR DOD 5200.1-R, INFORMATION

SECURITY PROGRAM REGULATION. FOR UNCLASSIFIED, LIMITED

DOCUMENTS, DESTROY BY ANY METHOD THAT WILL PREVENT DISCLOSURE

OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT.