Attachment 0002-JAIC T and E BPA PWS 11Feb21.pdf

Joint Artificial Intelligence Center

Test and Evaluation Services

Blanket Purchase Agreement

Performance Work Statement

Released 11 February 2021

Contents1.0 Introduction

2.0 Description of Services/Work Product Overview

3.0 General Information:

4.0 Tasks

5.0 Post Award

6.0 Data Rights and Intellectual Property

7.0 Appendix

1.0 Introduction

1.1 Background

The Department of Defense (DoD) Joint Artificial Intelligence Center (JAIC) was established in 2018 to be the focal point of the DoD Artificial Intelligence (AI) Strategy to accelerate scaling AI and its impact across the Department. Working closely with the Services, Combatant Commands, and other Components, JAIC identifies appropriate use cases for AI across DoD, rapidly pilots solutions, and scales impact across its enterprise.

The mission of the JAIC, as specified in the DoD AI Strategy, is “to accelerate the delivery of AI-enabled capabilities, scale the Department-wide impact of AI, and synchronize DoD AI activities to expand Joint Force advantages.” The purpose of this requirement is to acquire new and innovative AI test tools, capabilities, and services that can enable the DoD to rapidly test and validate AI capabilities developed for DoD operations and missions.

1.2 Scope

The PWS includes the acquisition of commercial AI tools and services, the development of new AI tools and services, the integration of AI tools and services into environments, the operation and support of AI tools and services, and the use of AI tools and services to conduct AI testing on AI models and software applications. The scope includes the work, performance, processes, and accountabilities in support of the DoD and US Government’s AI test and evaluation objectives in the following areas:

1.2.1. Test and Evaluation (T&E) Technology and Tools:

The DoD and US Government require test technology and tools for a variety of AI, automation, and autonomy applications. The anticipated AI T&E focus areas may include development of T&E capabilities to support the Government’s full spectrum of emerging AI technologies, to include, Machine Learning (ML), Deep Learning (DL), and Neural Networks (NN) with focus on the following:

Conversational interface applications using voice to text.

Speech-enabled products and services for Government applications and systems.

Image analysis, testing deep learning based visual search and image classifier.

Natural Language Processing (NLP)-enabled products and services.

Humans augmented by machines (to include human-machine interfaces) and improved methods to measure warfighter cognitive and physical workloads (to include Augmented Reality (AR) and Virtual Reality (VR) test services).

Autonomous systems.

1.2.2. T&E Services:

Agencies and organizations within the DoD and US Government require T&E services.

The JAIC T&E office provides T&E services to the Mission Initiatives (MIs) in the JAIC and DoD as a whole. Specific T&E services will be identified at the Call Order level by the requirement owner. Required T&E services could include, but are not limited to, the following:

Data Set Development/Curation/Documentation: Each MI or Government AI project has unique data that must be acquired and curated such that it can be used to test modern AI software systems. Efforts include, but are not limited to, data provenance, integrity, security, quality assessment, image annotation, and data coverage analysis as applied to T&E in addition to data documentation and corresponding review.

Test Harness Development: Creation of automated, containerized, cloud-enabled test harnesses that facilitate automatic ingestion of data into a containerized AI model and aggregates the results.

Model Output Analysis: Analysis expertise/software is needed to assess the quality of results from the AI models developed by the MIs. This effort involves both development of containerized, cloud-based, analysis software and creation of context specific and operationally relevant performance metrics.

Test Planning, Documentation, and Reporting: Testing expertise to create the required documentation for an AI algorithm undergoing the testing lifecycle (algorithm test, system test, and operational test). This effort includes, but is not limited to, the creation of Test and Evaluation Master Plans (TEMPs), Test Plans, and Test Reports, and management of a test schedule.

Testing Services: This effort involves the services and expertise to plan, document, and conduct T&E of AI, automated, and autonomous products. This includes, but is not limited to, performing testing on AI algorithms and/or AI enabled systems across all T&E areas (algorithm test, system test, developmental test, and operational test).

Identifying new technologies, products, or development efforts: AI is a new and rapidly developing field. The JAIC T&E Division is tasked with finding those technologies not covered within the scope of the previous focus areas that may be beneficial to AI T&E efforts at the JAIC. The JAIC T&E Division identifies the impact of the new technologies and incorporates the effort to improve T&E of AI.

All proposed solutions must align with JCF and Mission Initiative infrastructure needs, i.e., cloud-based test tools that are containerized and should be designed and developed in a responsible manner such as outlined in the Department of Defense AI Ethical Principles, adopted February 2020 (“DoD AI Ethical Principles”; See Attachment 0005 Appendix B Department of Defense AI Ethical Principles).

1.3. Alignment/Integration of AI T&E Tools and Services with the JCF:

Many of the AI T&E products acquired or developed under this PWS will be required to align and interoperate with the Joint Common Foundation (JCF). The JCF is the DoD’s AI platform that will provide a common set of AI tools, services, workspaces, and processes for developing, testing, certifying, deploying, and operating AI capabilities for the DoD. The JCF will initially be built and operated in the DoD enterprise cloud, but will expand to interconnect with DoD bases, facilities, test ranges, training centers, tactical sites, and weapons and sensor platforms into a distributed DoD AI ecosystem. An important aspect of the JCF is the incorporation of modern, agile, automated, DevSecOps tools and processes for AI data science, AI model development and validation, and AI software development, testing, and certification.

In most cases, the T&E tools, capabilities, and services acquired, developed, or operated under this BPA will be required to conform to JCF published standards and practices. In many cases, the T&E tools, capabilities, and services acquired, developed, or operated under this BPA will be required to be integrated into the JCF and operated as part of the evolving JCF baseline.

The types of activities anticipated for aligning and/or integrating AI T&E products and services into the JCF include, but are not limited to, the following:

Locking down AI T&E tools and software in accordance with DoD and JCF specified security standards to ensure they meet security standards for integration into the JCF.

Packaging and delivering AI T&E tools and software as hardened containers in accordance with DoD and JCF specified standards.

Packaging AI T&E tools and services in accordance with DoD and JCF defined standards to ensure that they can be successfully integrated into the JCF.

Aligning AI T&E tools and software with JCF specified Application Programming Interfaces (APIs) for interoperating with the JCF DevSecOps process.

Providing AI T&E tools with JCF specified APIs for exporting testing data and test results so that they may be easily shared across the JCF.

Integrating AI T&E tools and services into the JCF platform, and in some cases, enabling them to become part of the JCF baseline.

Registering AI T&E tools and services in the JCF provided AI service marketplace.

Providing technical and system administration support for operating AI T&E tools and services as part of the operational JCF baseline – in support of third party users.

Conducting T&E activities on specific AI models and AI software applications within the JCF platform.

The JCF is a new capability that is continually growing and evolving. The requirements and technical standards for JCF alignment and integration are not currently finalized, and will continue to evolve over time. Therefore, specific requirements for JCF alignment and integration will not be specified as part of this overarching BPA vehicle, but will be provided at the time of individual Call Order publication.

1.4 Type of Contract

This is a BPA. Type of contract(s) allowed under this agreement are Firm Fixed Price (FFP), Time and Materials (T&M), and FFP – T&M hybrid. The type of contract(s) will be established by the Ordering Contracting Officer (OCO) at the individual Call Order level.

1.5 Authorized BPA Users

The BPA is open for ordering to the U.S. Government in support of AI T&E. This vehicle is established for decentralized ordering. The OCO is responsible for reviewing the Ordering Guide in its entirety and following all pertinent rules and regulations for awarding a BPA Call Order against this BPA.

1.6 Lengths of Agreements

The T&E BPA is available for ordering for a period of five years. The BPA will be reviewed annually, and, if necessary, updated as needed. The Government will consider off boarding contractors during this time, if it is determined that it is in the best interest of the Government. As needed, the Government will also explore onboarding new contractors. During the final year, the BPA will be reviewed to determine if it will be renewed.

1.7 Non – Personal Services

The Government shall neither supervise Contractor employees nor control the methods by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work scheduled 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 constitutes, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the Contracting Officer.

1.8 Thresholds

Individual Call Orders shall not exceed the dollar threshold listed in FAR 13.5(c).

1.9 Organizational Conflict of Interest (OCI)

A contractor shall not perform any T&E for their own data requirements, including AI capability delivery or machine learning algorithm development without appropriate reporting, screening, and approval in accordance with FAR 9.5

Additionally, personnel performing work under any subsequent agreements made from this BPA may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services, which may create a current or subsequent Organizational Conflict of Interests (OCI). The Contractor shall notify the Contracting Officer immediately that such access or participation may result in any actual or potential OCI and promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contracting Officer has sole discretion to decide whether the Contractor’s mitigation plan is acceptable. If the Contractor cannot satisfactorily avoid or mitigate any OCIs, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which the OCI may affect.

In order to prevent a future OCI resulting from potential bias, unfair competitive advantage, or impaired objectivity, the Contractor (to include subcontractors) shall be subject to the following restrictions.

The Contractor shall be excluded from competition for or award of any agreement/call order to which, in the course of performance of this PWS, the Contractor has received advance procurement information before such information has been made generally available to other persons or firms.

The Contractor shall be excluded from competition for, or award of any agreement/call order for which the Contractor provide the development of specifications or statements of work. Additionally, the Contractor shall be excluded from future procurements to which they have drafted evaluation criteria.

The Contractor shall be excluded from any procurement where the Government determines there is an unmitigated Organizational Conflict of Interest.

2.0 Description of Services/Work Product Overview

2.1 Key Personnel

A T&E BPA Manager must be identified by all Contractors who are part of the T&E BPA.

Qualifications for the T&E BPA Manager are listed below:

T&E BPA Manager: The Contractor shall identify a T&E BPA Manager by name who shall provide management, direction, administration, quality management, and leadership of the execution of the BPA. The T&E BPA Manager shall act as the initial interface between the OCO, Government agencies, and Contractor. The T&E BPA Manager shall be responsible for regularly briefing the OCO and JAIC on BPA status, milestones, and provide feedback to the Government. The T&E BPA Manager shall have the authority to respond to requirements issued through this agreement and bind the company.

It is required that the T&E BPA Manager has the following qualifications:

Must be an employee of the prime Contractor or have an offer of employment from the prime Contractor that the individual intends to accept in the event of an award being made to the Contractor.

Possess a minimum of ten years of Project Management experience managing complex projects in an IT engineering or big data environment.

Demonstrate ability to lead, manage or participate as a member of a cross-functional team.

All Call Orders executed under this BPA must contain a Key Personnel clause for a Program Manager. The qualifications for the PM will be determined at the Call Order level by the OCO. Additional Key Personnel may be specified as part of the Call Order at the discretion of the OCO.

2.2 Labor Categories

See attachment labeled, “Attachment 0004 Appendix A T&E LCAT Table” for more information.

3.0 General Information:

3.1 Security Requirements

The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this agreement. At the end of each work day, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.

The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government Contracting Officer Representative (COR). Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.

Call Orders outside of the DoD will need to determine specific security requirements at the Call Order level.

3.2 Other Security Requirements

A DD Form 254, Contract Security Classification Specification, applies to this BPA. Call Orders issued under this BPA can support up to a Top Secret (SCI/SAP) level classification. However, specific classification/clearance requirements (Unclassified, Secret, Top Secret, etc.) will be established at the Call Order level. Unclassified Call Orders may not have a DD254 or require a facility clearance. When responding to a requirement, proposed personnel shall possess at least the minimum security clearance required for that call order prior to proposal submission or being issued a Common Access Card (CAC). There is one exception that pertains to Contractor personnel with an interim security clearance for contractors providing support in the NCR. Fingerprints must be complete, favorable and on file for validation by 11th Wing Information Protection office (this is only applicable for contractors providing support in the NCR; all other locations shall follow local procedures). Contractor personnel must have a SECRET security clearance prior to performance on a Call Order if they require a Pentagon-sponsored Government e-mail. All Contractor personnel must maintain the level of security required for their contracted duties for the life of the Call Order

The security requirements are in accordance with the attached DD Form 254 template which will be tailored by the OCO at the call order level. Any extracts or use of such data shall require the Contractor to apply derivative classifications and markings consistent with the source from which the extracts were made in accordance with DoDM

5200.1 Volumes 1-4, Information Security Program, a manual for safeguarding classified information; and Executive order 12356, Classified National Security Information. Pursuant to DoD 5220.22M; Chapter 6, Visits and Meetings; the contractor shall submit visit requests to applicable security managers (see Call Order CORs for security manager POCs). Contractor shall complete necessary documentation for sub-contractor(s) associated with each BPA holder.

The Contractor’s facility identified in Block 6 in the DD Form 254 shall be cleared with the appropriate facility clearance (i.e. Top Secret facility) at the time of call order proposal submission. Contractor facility verification is through the Industrial Security Facilities Database (ISFD) using the company commercial and Government entity (CAGE) code submitted with its proposal. In the event that a company has more than one CAGE Code assigned, the CAGE Code submitted with its proposal shall be for the facility where the actual work that is performed in support of this BPA. “Personnel” clearance is different from “Facility” clearance.

3.3 Government Furnished Property

Government furnished items or services will be specified by the OCO in the individual Call Orders.

3.4 Service Contract Reporting (SCR)

The Office of the Secretary of Defense (OSD) mandates reporting of manpower data with regard to the performance of DoD services contracts consistent with the requirements of title 10, U.S.C., section 235 and 2330a, as amended. Contractors are to report manpower data relating to the performance of services contracts into SAM, consistent with existing Service Contract Reporting (SCR) requirements under the FAR Subpart 4.17 - Service Contracts Inventory (SCI). When reporting on Call Orders issued under an indefinite-delivery contract or agreement, reports are completed at the order level. No reports are collected at the contract or agreement level. Contractors are required to report data in SAM on an annual basis when awarded a DoD contract or Call Order valued in excess of $3 million in obligations. The Contractor shall completely fill in all the information in the format using the following web address: http://sam.gov. SCI reporters are required to report the following information: Total Amount Invoiced, Prime Contractor Hours Expended, and, if applicable, Tier 1 subcontractor information. The reporting period for Contractors in SAM is open from mid-October through mid- December for reporting against the prior Government fiscal year. Contractors shall complete the SCR before the reporting period closes against the prior Government fiscal year.

3.4.1 COR

No COR will be established at the base BPA level. Each Call Order will have a separately identified COR and designation letter that specifies their specific authorities and responsibilities. The COR will be identified by the designation letter issued by the Contracting Officer. A copy of the letter will be sent to the Contractor and the Contractor will acknowledge each COR’s designation letter. Under no circumstances does a COR have the authority to authorize substantive changes to any terms and conditions of the resulting order with respect to cost/price, and delivery dates.

3.4.2 Quality Control/Assurance

All Call Orders under this BPA shall include a Quality Assurance Surveillance Plan (QASP) and a Quality Control Plan (QCP) outlining the Government’s surveillance methodology and assessment of the Contractor’s performance in terms of an acceptable level of quality. Contractors performing under this BPA shall ensure that they have an approved Quality Management System. The QASP and QCP should both include evaluation methods for Responsible AI and/or adherence to the DoD’s AI Ethical Principles.

3.4.4 Size Standards

Contractors must certify size standard for each Call Order. All size standards will be confirmed by the OCO at the Call Order level for eligibility to compete.

3.4.5 Subcontracting Plans

The Small Business Subcontracting Plan requirement is required for Contractors with a business size designation of “other than small” in accordance with FAR Clause 52.219- 9, Small Business Subcontracting Plan, Alt II and DFARS clause 252.219-7003, Small, Disadvantaged, and Women-Owned Small Business Subcontracting Plans (Government Contracts). Unrestricted Call Orders shall include Small Business Subcontracting Plan requirements. The Small Business Subcontracting Plan shall be defined by the OCO at the Call Order level.

3.4.6 Small Business Participation

The Small Business Participation Plan shall be defined by the OCO at the Call Order level.

3.5 Recognized Holidays

Work at a Government site shall not take place on Federal holidays or weekends (but may require off-hour work due to network loading or other disruptions that could occur) unless direct by the OCO on individual Call Orders.

3.6 Work Location

The work location for each requirement will be specified in each Call Order but may include CONUS and OCONUS locations.

4.0 Tasks

This is not an all-encompassing list, as technology changes, additional tasks could be required.

4.1 BPA and Call Order Management:

The Contractor shall propose a plan to manage the BPA and subsequent individual Call Orders. This includes management and oversight of all activities performed by the Contractor personnel including subcontractors to satisfy the requirements identified in this Performance Work Statement (PWS) and subsequent Call Order work statements.

Each individual Call Order is expected to have a project management team, associated documentation, and reporting requirements in support of Purchasing Organization processes.

4.2. Task #1: AI T&E Solutions:

The Contractor shall propose, design, build, and operationalize techniques, tools, or process solutions at the direction of the Purchasing Organization to conduct T&E of AI, automated, and autonomous products. Solutions developed under this task should follow system engineering and software development best practices including risk management. This includes, but is not limited to, requirements creation, user story development, Concept of Operations (CONOPS) ideation, architecture diagrams, System View (SV) diagrams, network diagrams, system workflows, unit testing, code traceability, software containerization, Continuous Integration/Continuous Development (CI/CD) development, User Guides, Interface Control Documents (ICD), and API.

Test solutions shall address how the development and anticipated deployment/use of the product under evaluation considers and instantiates the DoD’s AI Ethical Principles and aids in mitigating ethical risks.

4.3. Task #2: T&E and Independent Verification and Validation (IV&V) Services:

The Contractor shall conduct T&E of capabilities directed by a Government Test Engineer assigned by the Purchasing Organization for capabilities developed from requirements and perform its T&E and V&V efforts on a day-to-day basis throughout the project lifecycle. The Contractor shall provide feedback, audit results, and test results on an ongoing basis.

The Contractor shall provide T&E services of AI models, AI enabled systems, automated products, and autonomous systems against metrics determined prior to model development and provide testing of the final integrated product. Where possible, the T&E activities shall be answered within the Agile development framework for system development in conjunction with the Purchasing Organization.

For AI models, T&E will occur on selected models to ensure the model meets all defined metrics and addresses/satisfies the DoD’s AI Ethical Principles.

The Contractor shall provide engineering support required to review, assess, and analyze all levels of system documentation to identify and define test requirements.

Requirements and design specifications, test plans and procedures, test results, logistics training documentation, and change proposals shall be reviewed. The Contractor shall provide Requirements Traceability and Change Impact Assessments in close coordination with the Purchasing Organization. The Contractor shall conduct unit and integration testing prior to delivery, but T&E will be conducted through the Purchasing Organization with outside support if necessary.

The Contractor shall evaluate test coverage with respect to test type, test validity, test scenarios, test conduct, test results, and problem report content. The goal is to reduce the number of defects or problems reported at integrated combat systems with AI capabilities by continually improving software verification level test methods. Testing should be traceable to system requirements and faults identified by testing can be traced back to higher level system specifications.

The Contractor shall plan, conduct, participate, and execute T&E activities including but not limited to:

1. Developing, revising, and maintaining Test Plans in coordination with the Purchasing Organization.

2. Updating the test plans to reflect changes to existing tests due to enhancements or deficiency corrections.

3. Setting up the test environment including the setup and breakdown of test equipment and systems.

4. Executing tests according to the test plans and test procedures and collecting test data.

5. Documenting deficiencies via problem reports and providing a Final Test Report.

The Contractor shall analyze T&E data and perform the following:

1. Provide Deficiencies Assessments of deficiencies uncovered during testing including support of root cause analysis and solution recommendations.

2. Provide Test Procedure Improvements Recommendations to facilitate improved deficiency detection.

3. Assess the impact to other system components of deficiencies uncovered during testing.

4. Perform and document Trade-off and Analysis of Alternatives Assessments.

5. Provide test artifacts, objective quality evidence, and detailed analysis results.

The Contractor shall conduct, participate, or provide witness in system T&E, certification, and training events to be held at Government or non-Government venues as needed. Events may include but are not limited to, the following:

1. Developer/Capability Test.

2. Integrated Software/System Level Test.

3. Formal Qualification Test (FQT).

4. Verification and Validation (V&V) Test.

5. Software Build FQT.

6. Segment/System Test.

It is expected that test solutions will address how the development and anticipated deployment/use of the product under evaluation considers and instantiates the DoD AI Ethical Principles and aids in mitigating ethical risks.

4.4. Task #3: Other Technologies:

The Contractor shall identify other new or relevant technologies that were not previously mentioned above to the Purchasing Organization. The Contractor shall design, build, acquire, or operationalize the new technologies at the Government’s direction to improve T&E of AI, automated, and autonomous systems as well as support instantiation of the DoD AI Ethical Principals.

4.4. Task #4: Alignment/Integration with the JCF:

The Contractor shall modify and enhance AI T&E tools, capabilities, and services to align with JCF architectures, technical standards, and security standards. The Contractor shall package AI T&E capabilities as containers in accordance with JCF specified standards, implement JCF specified security mechanisms and security patterns, and implement JCF specified APIs for integrating T&E capabilities into the JCF ecosystem.

The Contractor shall align AI T&E tools, capabilities, and services to operate in accordance with JCF DevSecOps processes and workflows. The Contractor shall provide mechanisms to enable AI T&E capabilities to be orchestrated into and managed as part of JCF managed DevSecOps workflows. The Contractor shall also integrate AI T&E capabilities with JCF DevSecOps information reporting and sharing mechanisms.

The Contractor shall integrate AI T&E tools, capabilities, and services into the JCF so they become part of the JCF baseline. The Contractor shall work with the JCF Platform team to align, integrate, test, and certify the integration of new AI T&E capabilities into the JCF platform. The contractor will exercise the JCF platform’s DevSecOp process to incorporate AI T&E capabilities into the JCF platform baseline. The Contractor shall register AI T&E capabilities in the JCF AI service marketplace and provide basic instructions and training guides to assist third party users that seek to utilize the new AI T&E capabilities.

The Contractor shall provide operations, maintenance, and systems administration support to the JCF platform operations team for operating and maintaining AI T&E capabilities as part of the JCF service baseline.

The Contractor shall provide AI test and evaluation services as part of JCF executed AI model and software development DevSecOps workflows. Within JCF DevSecOps workflows the Contractor shall define and develop automated test scripts, monitor and review test results from AI T&E automated test tools running in JCF, consolidate and review test and evaluation results generated as part of JCF DevSecOps workflows, and provide input for AI model and software release and deployment decisions within the JCF DevSecOps process.

5.0 Post Award

5.1 Conferences

The Government will hold post-award conferences as needed. The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5.

The Contracting Officer, PM, COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the Contracting Officer will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of any issues. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

5.2 Transition In/Transition Out

Transition in and out for contractors on this BPA will be specified for each Call Order.

5.2.1 Transition-Out Plan. The Contractor shall provide a Transition-Out Plan NLT than 30 calendar days prior to expiration of the call order. The plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming Contractor (if applicable). In addition, the Contractor will continue to accomplish all tasks as outlined in the call order during this period. The current Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs and issues

5.2.2 Communication. The Contractor shall establish and maintain effective communication with the Government personnel for the period of the transition via weekly status meetings per the COR’s direction.

6.0 Data Rights and Intellectual Property

Data Rights and Intellectual Property will be addressed at the Call Order level.

7.0 Appendix

Attachment 0004 Appendix A. T&E LCAT Table

Attachment 0005 Appendix B. Department of Defense AI Ethical Principles