DAF CSDR Support and Data Curation —PWS

Performance Work Statement (PWS)

DAF Cost and Software Data Reporting (CSDR) Support and Data Curation for

Air Force Cost Analysis Agency (AFCAA)

Period of Performance: One (1) Year — Start Date TBD

Funding: Operations and Maintenance (O&M)

1. INTRODUCTION AND PURPOSE

The Department of War (DoW) requires accurate and reliable cost reporting to inform life cycle cost estimates and programming and acquisition decisions. The data collected from DoW cost reporting forms the basis of these estimates, as mandated by statute and DoW and Department of the Air Force (DAF) policies.

This Performance Work Statement (PWS) defines a focused, one-year level of support to the Air

Force Cost Analysis Agency (AFCAA) covering two related areas of work: (1) Cost and Software

Data Reporting (CSDR) planning, verification and validation (V&V), and compliance support; and

(2) CSDR submission data curation, metadata tagging, and quality preparation activities in support of the downstream CSDR data ingestion environment maintained by the Government.

Both tasks are performed in support of the CSDR process under DoD Instruction (DoDI) 5000.73, Cost Analysis Guidance & Procedures, and Air Force Instruction (AFI) 65-508.

Use of automated validation, data analytics, and Artificial Intelligence (AI) tooling to improve the efficiency and quality of the work described herein is highly encouraged, subject to the limitations described in Section 7.

2. TASKS AND TASK REQUIREMENTS

The contractor shall provide the necessary labor, supervision, and management to fulfill the tasks described below. The contractor shall adhere to all scheduled timelines, milestones, delivery schedules, and administrative requirements, including scheduled on-time delivery of reports, data products, status reports, billing invoices, staffing of personnel, and action item completion.

Meetings shall include a kickoff meeting within ten (10) business days after contract start;

recurring working meetings between the contractor's task leads and the AFCAA technical lead(s);

and quarterly formal reviews with the AFCAA Program Manager and technical leads, to include a final review approximately thirty (30) calendar days before the end of the period of performance.

Task 1 (Enabling Task) — Obtaining Permissions to Access Data Sources

Successful performance of this requirement depends on the contractor working proactively with the Government to obtain permissions to access Government-held data. Much of the data in the

Cost Assessment Data Enterprise (CADE) repository is from defense contractors and major subcontractors. Each considers its data as business sensitive and subsequently has marked it, or considered it, as proprietary. This requires protecting this information from public disclosure.

Since the contractor team while providing these services will be provided or have access to nonpublic information, each person on the contractor and subcontractor team working this effort shall sign a non-disclosure agreement (NDA) with AFCAA and an NDA with OSW Cost

Assessment Program Evaluation (CAPE) for access to CADE. The contractor and subcontractor team shall work proactively and sign, as required, NDAs with other Government organizations to support and fulfill data collection and task requirements.

The contractor will work proactively with AFCAA to identify NDA requirements for all Original

Equipment Manufacturer (OEM) and major subcontractor data the contractor will access in support of CSDR planning, verification and validation, and curation activities under this PWS.

Should an OEM or major subcontractor require an NDA with the contractor, then the contractor shall develop and complete this before AFCAA facilitates access to that OEM's or major subcontractor's Government-held data. These NDAs must carry through the entire contract period of performance, including any option periods. Furthermore, the NDAs shall flow equally across the contractor and its subcontractors. These NDAs shall be coordinated directly between the contractor and the OEMs within thirty (30) days of identified need. If the contractor shows a diligent effort to complete the NDA process with consistent follow up with OEMs and is still unsuccessful, the Government will reassess and replan accordingly. Subcontractors may or may not be required to sign separate NDAs, dependent on the negotiated OEM agreements.

As part of its proposal and throughout the duration of this contract, the contractor shall identify and notify the Contracting Officer (CO) of any Organizational Conflict of Interest (OCI) it or any of its subcontractors has, or could have, with any OEM or major subcontractor who has submitted reports held in CADE. Moreover, the contractor shall notify the CO and the AFCAA Program

Manager of any acquisition or merger involving itself or its subcontractors and explain whether that action will create an OCI. Similarly, the contractor will identify any other emerging event or action that would create an OCI.

Task 2 (Enabling Task) — Plan of Action and Milestones (POA&M)

The contractor shall develop and submit, for Government review and approval, a POA&M describing the contractor's approach to satisfy all tasks and elements under this PWS within thirty

(30) calendar days of contract award. The POA&M shall be a living document and shall be updated quarterly, or as directed by the AFCAA technical lead. The POA&M shall include, at minimum:

• A detailed description of the approach to completing each task and subtask, including interim and final milestones.

• Task activity and milestone schedule, including any go/no-go decision points requiring

Government concurrence.

• Sufficient lead time for the delivery of all task products to allow Government review and feedback; the contractor shall resolve all Government comments before any deliverable is considered final.

• A management plan covering staffing, schedule, business management, and reporting, with specific identification of the Task 3 and Task 4 Key Personnel and their respective responsibilities.

• Plans to format and share work products such that finalized products are uploaded to

AFCAA's designated platform(s) and, where applicable, to CADE.

Task 3 (Core Task) — CSDR Planning, Verification and Validation, and Compliance Support

Task Objective

The contractor shall provide support to AFCAA and the DAF Cost Centers in administering the

CSDR process for ACAT I-level DAF programs and all programs delegated to AFCAA for CSDR plan approval, in accordance with DoDI 5000.73. The contractor shall assist AFCAA, Center Cost

Staffs, and PMOs across the full CSDR submission set, including the Contractor Cost Data Report

(FlexFile and DD Form 1921-series and successor reporting structures), the Quantity Data

Report, the Technical Data Report (form, fit, and function data), the Software Resources Data

Report (SRDR), the Maintenance and Repair Parts Data Report (M&R), and the Contractor

Business Data Report (CBDR).

Scope of Work

The contractor shall perform the following subtasks as required by AFCAA and as reflected in the approved POA&M:

CSDR Planning and Plan Tailoring

• Support AFCAA, Center Cost Staffs, and PMOs in the development and tailoring of CSDR

Plans (DD Form 2794) for ACAT I-level DAF programs, all programs delegated to AFCAA and any other DAF non-ACAT I programs of interest to the DAF, ensuring that approved plans represent the broader cost community's data needs for future cost estimating.

• Lead the Cost Working-Group Integrated Product Team (CWIPT) through the CSDR planning process. This includes proactively identifying upcoming RFPs and Industry Days to ensure timely kickoffs, scheduling kickoff meetings, and briefing a condensed version of the DAF CSDR Training to baseline the team.

• Provide the first CSDR plan draft based on initial introductions to the program and the contract Statement of Work (SOW), ensuring plans adequately capture quantity reporting structures and form, fit, and function parameters for the Software Resource Data Report

(SRDR) and Technical Data Report (TDR), which typically carry greater complexity than the cost-data submissions. This draft shall stem from the most appropriate CSDR

Standard plan.

• Review and provide recommendations on contractor-submitted CSDR Plans (DD 2794) prior to AFCAA approval, with attention to consistency with the approved Work Breakdown

Structure (WBS), CADE Standard WBS templates, MIL-STD-881 mapping, and the cost estimating community's data requirements.

• Track upcoming solicitations and Request for Proposal (RFP) releases to ensure timely

CSDR Plan development are approved; track current CSDR planning activities against established RFP and contract award dates.

• Provide Subject Matter Expert (SME) guidance in the implementation of FF, QDR, TDR, SRDR, M&R, and organic data collection, as well as examine/document/discuss discoveries, and results in Lesson Learned/Best Practices paper.

• Lead and facilitate the CSDR Readiness Review (including preparation materials) within 60 days of contract award.

CSDR Verification, Validation, and Compliance

• Verify that submissions from defense contractors, major subcontractors, and government entities conform to the final approved CSDR Plan by comparing submissions to the plan and to prior submissions on the same program.

• Validate the completeness, internal consistency, and reasonableness of the full submission set: the Cost Data Report (Flexfile and 1921 series), the Quantity Data Report, the Technical Data Report, the SRDR, M&R, and CBDR.

• For the SRDR and TDR specifically, the contractor shall perform a more detailed validation review reflecting the higher complexity of these submissions, including review of quantity-time phasing consistency, technical parameter completeness across the reportable WBS elements, and traceability of form, fit, and function characteristics to the approved CSDR

Plan.

• Document discrepancies identified during V&V, coordinated resolution with the submitting contractor through the appropriate Government channels, and recommend disposition

(acceptance, conditional acceptance with comments, or rejection). All received submissions events regardless of resubmission shall have an overall average processing time of 60 days. Otherwise, the submission event is flagged for AFCAA/CWIPT awareness and contractor must provide support for resolution in a consistent and timely fashion.

• Support the AFCAA CSDR Process Manager in management of the end-to-end CSDR planning, V&V, and compliance process for DAF programs. All actual report approvals shall be made by Government personnel; the contractor's role is strictly support.

CSDR Compliance

• Track compliance and provide resolution support scaled to the expected volume of program CSDR compliance actions required each month.

• Resolve CSDR compliance issues for DAF programs by proactively coordinating with

PMO and PMO contracting officer and CWIPT.

• Track DAF programs with CSDR compliance issues and document get-well resolution within three months or less. Actively track timelines, and if program fails to achieve resolution within the three-month threshold, the contractor shall escalate the issue by alerting the Cost Data Support Group (CDSG) and AFCAA.

Cost Working Integrated Product Team (CWIPT) Support

• Support CWIPTs for ACAT I-level and ACAT II–III level DAF programs, assisting in development of a final recommended CSDR Plan for Government approval.

Cost Reporting Standards Board (CRSB) Support

• Identify candidate issues for CRSB consideration and work with the AFCAA CSDR

Process Manager on CRSB recommendations.

DCARC and DAFCARC Coordination

• Coordinate with the Office of the Secretary of War (OSW) Defense Cost and Resource

Center (DCARC) for DAF ACAT I-level programs, and with the DAF Cost and Resource

Center (DAFCARC) for ACAT II–III programs.

Task 4 (Core Task) — CSDR Submission Data Curation, Metadata Tagging, and Quality Preparation

Task Objective

The contractor shall perform data curation, metadata tagging, and data quality preparation activities on CSDR submission data in support of the CSDR data ingestion environment maintained by the Government. The objective is to ensure that CSDR submissions — the Cost

Data Report (Flexfile and 1921 series), the Quantity Data Report, the Technical Data Report, the

SRDR, and the M&R, and the CBDR — are properly tagged, normalized, and quality-checked as they move from the submission state into the downstream cost estimating analytical environment.

This task is performed as recurring data stewardship in support of the CSDR mission and is not pipeline development.

The Quantity Data Report, Software Resource and Data Report, and Technical Data Report receive specific emphasis under this task. These reports represent a known gap in the readily available data holdings of the cost estimating community and warrant focused curation effort during this period of performance. Improving the discoverability, tagging, and usability of these submissions is a primary intended outcome of Task 4.

Scope of Work

CSDR Submission Data Cleansing and Standardization

• Review CSDR submissions for data quality issues including missing values, internal inconsistencies, mis-aligned WBS elements, inflation/escalation treatment, and other issues that would impede downstream analytical use.

• Apply normalization treatments as directed by the AFCAA technical lead, including WBS alignment to the CADE Standard WBS, Cost Element Structure (CES) standardization, and inflation/price-escalation adjustments.

• Document each cleansing and normalization action taken on each submission such that the original-submitted data and the curated data remain distinguishable and traceable.

Metadata Tagging and Programmatic Tagging

• Apply metadata tags to CSDR submissions consistent with the AFCAA-approved metadata schema, including programmatic identifiers (program, contract, contractor, contract line item, reporting period, submission type, ACAT level, commodity area, and other approved tags).

• Where new tags are required to support emerging cost estimating analytical needs, the contractor shall recommend additions or modifications to the metadata schema to the

AFCAA technical lead for Government concurrence prior to implementation. The contractor shall not unilaterally modify the approved schema.

• Apply technical parameter tagging to Technical Data Report submissions to support discoverability and traceability of form, fit, and function parameters across the program portfolio.

Quantity Data Report and Technical Data Report Focused Curation

• Perform focused curation of Quantity Data Report submissions, including standardization of quantity-time phasing representations, reconciliation of quantity reporting against contract and program quantities, and tagging of quantity data to support downstream cost-per-unit and learning-curve analysis.

• Perform focused curation of Technical Data Report submissions, including extraction and structured tagging of form, fit, and function parameters; mapping to the approved CSDR

Plan technical parameter list; and identification of parameter gaps relative to the cost estimating community's known analytical needs.

• Provide recommendations to the AFCAA technical lead on improvements to the Quantity

Data Report and Technical Data Report planning templates and tagging conventions based on patterns observed during curation.

Upstream Data Preparation Activities

• Perform upstream data preparation activities required for CSDR submissions to be ingested by Government-maintained data infrastructure. These activities are limited to data preparation, tagging, normalization, and quality-check actions performed on the

CSDR submission data itself. Configuration, modification, or development of Government data infrastructure is not in scope for this PWS.

• Coordinate with Government data engineers on data format, tagging, and quality issues that affect downstream ingestion.

Automated Validation and AI/Analytic Tool Use

The use of automated validation routines, analytic tooling, and AI capabilities to improve the efficiency and quality of the work in this task is highly encouraged, subject to the proprietary-data restrictions in Section 7. The contractor is encouraged to use such tooling for non-proprietary portions of CSDR data and metadata at all times, and for proprietary portions only as authorized in Section 7.

Documentation

• Maintain documentation of curation rules, tagging conventions applied, normalization procedures, and data quality findings sufficient for Government personnel to understand, audit, and reproduce the curation work performed.

• Deliver curation and tagging documentation as described in Section 6.

3. KEY PERSONNEL

The Government has identified two (2) Key Personnel positions under this PWS, one per core task. Where this PWS is awarded as a Basic Ordering Agreement (BOA) or similar vehicle with the potential for separate task-order awards to different contractors for Task 3 and Task 4, each task-order awardee is responsible for the Key Personnel position associated with its task. The

Key Personnel for each task shall not be substituted without written approval from the CO.

Task 3 Key Personnel — CSDR Subject Matter Expert (Lead)

Highly experienced individual to lead the CSDR planning, V&V, and compliance support work in

Task 3. Must have at least ten (10) years of progressively responsible experience in weapon systems acquisition and cost estimating, specifically on major DoW or Air Force ACAT I/II/III threshold-level programs. Expertise shall include a strong understanding of CSDR policy, planning, validation, compliance, and the CADE application.

Key Skills and Experience:

• CSDR Policy & Guidance: Expert knowledge of DoDI 5000.73, DoD 5000.04-M-1, and

MIL-STD-881 work breakdown structures and mapping.

• DoW Cost Data: Familiarity with various DoW cost data sources.

• CADE Standard WBS: Proven experience mapping 1921-series and FlexFile cost data to the CADE Standard WBS templates for the planning and validation process to ensure accurate cost reporting.

• Contractor Cost Data Reporting (CCDR): Expertise with 1921 series and FlexFile cost reports and applying them to the CSDR planning and validation process.

• Quantity Data Report (QDR): Experience reviewing, validating, and tailoring CSDR

Quantity Data Reports, including quantity-time phasing and reconciliation to contract and program quantities.

• Technical Data Report (TDR): Strong understanding and experience utilizing CADE

Technical Data parameter lists for CSDR planning and validation, including extraction and review of form, fit, and function parameters.

• Software Resources Data Reporting (SRDR): Expertise with SRDR submissions and applying them to the CSDR planning and validation process.

• Maintenance and Repair Parts Data Report (M&R): Expertise with M&R submissions and applying them to the CSDR planning and validation process.

• Contractor Business Data Report (CBDR): Expertise with CBDR submissions and applying them to the CSDR planning and validation process

• Tools Proficiency: Working knowledge of CADE, DACIMS, cPet, PPM, and CSDR-SR systems, and any other tools the government identified as necessary.

• Communication: Ability to present and effectively communicate complex information clearly and concisely with senior leaders.

Task 4 Key Personnel — Data Curation Lead

Highly experienced individual to lead the CSDR submission data curation, metadata tagging, and quality preparation work in Task 4. Must have at least ten (10) years of progressively responsible experience in data engineering, data curation, or data science with substantial experience working with DoW cost data, CSDR submissions, or comparable structured technical/financial reporting data.

Key Skills and Experience:

• Data Curation and Stewardship: Demonstrated experience curating large, structured datasets, including data quality assessment, normalization, and traceable documentation of curation actions.

• Metadata and Tagging: Demonstrated experience designing and applying metadata schemas and programmatic tags to structured data, with familiarity with cost-data tagging conventions (program identifier, contract identifier, WBS, CES, ACAT level, commodity).

• CSDR Submission Familiarity: Working familiarity with the CSDR submission set, including the Cost Data Report (FlexFile and 1921-series), the Quantity Data Report, the

Technical Data Report, the SRDR, and the M&R.

• Programming and Data Manipulation: Proficiency in Python and SQL, with practical experience using data-manipulation libraries (Pandas, NumPy, or equivalent) for cleansing and transformation of structured data.

• Data Pipeline Familiarity: Familiarity with data pipeline concepts (ETL/ELT, staging, quality checks) sufficient to support upstream data preparation work. The Key Personnel is not expected to design or develop Government pipelines under this PWS but shall coordinate effectively with the Government pipeline owners.

• Tools Proficiency: Working knowledge of CADE, DACIMS, cPet, PPM, and CSDR-SR submission systems; working familiarity with DAF Data Fabric platforms including VAULT and Envision.

• Documentation and Communication: Strong written documentation skills; ability to communicate data curation findings and tagging recommendations clearly to both cost analyst and data engineering audiences.

4. PLACE OF PERFORMANCE, DUTY HOURS, AND GOVERNMENT-

FURNISHED SYSTEMS

Duty Hours

Normal duty hours are 0800 – 1630, Monday through Friday. Federal holidays shall be observed in accordance with Office of Personnel Management policy. Hours may be flexible at the discretion of the COR and the Government technical lead. Contractor personnel are expected to be available during AFCAA's normal operating hours for coordination.

Place of Performance

For contractual purposes, work is expected to be performed at the contractor's own facilities;

however, the contractor may be requested to work on-site at Government locations in the National

Capital Region (NCR) in cases where on-site presence is more efficient or effective for a particular activity (for example, CWIPT meetings, CRSB sessions, or sensitive coordination). Remote and telework arrangements are permissible for unclassified work, consistent with AFCAA policy and the contractor's own personnel-management practices.

Government-Furnished Equipment, Systems, and Access

The Government will provide Government laptop computers as required to perform contract tasks, with software licenses for applications used by AFCAA. The Government will initiate provisioning of accounts and credentials promptly upon contract start; however, provisioning timelines are subject to Government IT and security processing. Contractors should anticipate an average of ten (10) to fifteen (15) business days for full provisioning, though individual timelines may vary.

Provisioning delays shall not constitute an excusable delay for work that can be performed without access to Government systems. During the provisioning period, the contractor shall execute all work that can reasonably be performed using contractor-owned devices and systems, including

POA&M development, project planning, methodology development, documentation, and coordination with AFCAA technical leads. The contractor shall not charge idle time awaiting

Government system access when productive work is available on other contract tasks.

The following Government systems are required access for this effort:

• CADE (Cost Assessment Data Enterprise): required for both Task 3 and Task 4 personnel.

• DACIMS, cPet, PPM, and CSDR-SR: required for Task 3 and Task 4 personnel performing

CSDR planning, V&V, and submission curation work, as needed.

• DAF Data Fabric platforms (VAULT and Envision): required for Task 4 personnel performing data curation and tagging work, as required by the AFCAA technical lead.

Clearance: All contractor personnel performing under this PWS shall hold, at a minimum, a Secret security clearance. Access to CSDR submissions may include proprietary contractor data and, on a program-by-program basis, classified data; the contractor shall ensure all

5. GENERAL LABOR REQUIREMENTS

In addition to the Key Personnel identified in Section 3, the contractor shall provide a complement of supporting personnel sufficient to perform the work outlined in this PWS during the one-year period of performance. Supporting personnel are expected to include cost estimators/analysts with CSDR experience supporting Task 3, and data analysts/data stewards supporting Task 4.

The contractor shall propose its labor mix based on the work content described in Tasks 3 and 4 and shall identify substitutes for non-Key personnel in accordance with the contract's substitution provisions.

Replacement or substitute personnel for vacancies shall be filled with qualified personnel within fourteen (14) calendar days of vacancy unless otherwise approved in writing by the CO.

6. DELIVERABLES

The contractor shall provide the deliverables identified below. All deliverables are subject to

Government review and acceptance.

# Deliverable Description Due

1 Signed NDAs Signed AFCAA, OSW CAPE, and

OEM/subcontractor NDAs for all contractor and subcontractor personnel performing under this PWS.

NLT 5 business days after contract start;

updates as new personnel are added.

2 POA&M

Plan of Action and Milestones covering Tasks 3 and 4, with milestone schedule, risk areas, staffing plan, and Key Personnel identification.

Draft NLT 30 calendar days after award; final NLT 60 calendar days after award; quarterly updates.

# Deliverable Description Due

Monthly Status

Report

Brief monthly report covering work accomplished, work planned, issues/risks, and personnel/staffing changes.

Monthly, by the 10th calendar day of the following month.

Quarterly Review

Materials Briefing materials and agenda for each quarterly formal review and the final review.

NLT 5 business days before each quarterly review.

Task 3 CSDR Work Products

CSDR Plan review notes and tailoring recommendations; V&V findings and disposition recommendations; CWIPT, CSDR RR, and CRSB meeting minutes and updated action item trackers;

and other Task 3 work products as directed by the

AFCAA technical lead.

As generated;

logged in the

POA&M.

Task 4 Curation and Tagging Documentation

Documentation of curation rules applied, metadata tags applied, normalization actions, quality findings, and recommendations on schema or tagging conventions. Includes specific attention to Quantity Data Report and Technical Data Report curation outcomes.

Quarterly, aligned to formal reviews; interim deliveries as directed.

End-of-Contract Data Transfer

Transfer to the COR of all passwords, data collected, processes used, curation logs, tagging records, and any other information obtained throughout the contract's period of performance.

NLT 5 business days before end of period of performance.

7. AUTOMATED VALIDATION AND AI / ANALYTIC TOOL USE

The use of automated validation routines, data analytics tooling, and Artificial Intelligence (AI) capabilities to improve the efficiency and quality of the work described in this PWS is highly encouraged. This includes, but is not limited to, automated rule-based validation of CSDR submissions, anomaly detection on submitted cost and quantity data, automated metadata tagging assistance, and AI-assisted review of Technical Data Report content.

The contractor shall not, however, process proprietary CSDR data through AI tools (including but not limited to GenAI.mil capabilities) unless and until: (1) the Government has provided explicit written authorization to process proprietary CSDR data on the specific platform or tool in question;

and (2) the contractor has documented and is operating under a Standard Operating Procedure

(SOP) that establishes the data-protection controls applicable to that platform or tool. This restriction reflects current Government direction pending legal review and confirmation of data-protection adequacy on AI platforms.

The contractor may use AI and analytic tooling on non-proprietary portions of CSDR data and on metadata, tagging schemas, and documentation at any time, consistent with applicable security and information-protection requirements.

This PWS makes allowance for evolving Government authorities and platform accreditations during the period of performance. As additional AI platforms or capabilities are authorized for use with proprietary CSDR data, the AFCAA technical lead will notify the contractor in writing, and the contractor may expand its use of those capabilities consistent with the authorization terms and applicable SOPs.

8. QUALITY CONTROL

The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS, applicable laws and regulations, and best commercial practices. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Quality Control Plan (QCP) shall be delivered via electronic mail within thirty (30) days of contract award. The contractor shall deliver amendments or changes to the QCP within three (3) business days following any change, to the COR and the CO.

9. CONTRACTOR MANPOWER REPORTING (CMRA)

The contractor shall report all labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure Contractor Manpower

Reporting Application (CMRA) data collection site. The contractor is required to completely fill in all required data fields. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each fiscal year.

Prime contractors are responsible for ensuring all subcontractor data is reported. Subcontractor data shall be reported through the prime contractor in accordance with applicable AF CMRA helpdesk procedures.

10. ASSOCIATE CONTRACTOR INTERFACE

During performance of this contract, the contractor may be required to interface with other contractors supporting AFCAA and OSW CAPE. All such interactions will be governed by the terms of the Associate Contractor Agreement (ACA) clause, AFFARS 5352.217-9010.

To mitigate the risk of inappropriate information sharing, the contractor shall not independently share information with associate contractors. All exchanges of methods, applications, program history, or other data shall occur only at the express direction of the COR, who shall act as the central conduit for managing communications and information sharing between associate contractors.

Under no circumstances shall the contractor represent AFCAA in policy discussions, decision-making forums, or in communications with external entities. The contractor's role is strictly limited to providing the technical and analytical services defined in this PWS.

11. TRAVEL AND OTHER DIRECT COSTS

Travel, as well as Other Direct Costs (ODC), shall be on a cost-reimbursable basis under a separately assigned CLIN. The contractor may be required to travel to attend meetings or coordinate data review activities to fulfill the requirements of this PWS. The actual number of trips and their timing are subject to change based on Government requirements. All travel must be conducted in accordance with FAR 31.205-46, Travel Costs, and the Joint Travel Regulations

(JTR). The contractor shall submit a written request for travel to the COR for approval prior to incurring travel costs.

12. DATA AND DELIVERABLE RIGHTS

Government rights in data and deliverables produced under this contract shall be determined in accordance with the applicable Federal Acquisition Regulation (FAR) and Defense FAR

Supplement (DFARS) clauses incorporated into the contract. Given that this is an O&M-funded contract for recurring CSDR support and data stewardship services, the contractor shall deliver to the Government all work products generated in performance of this PWS — including CSDR plan review notes, V&V findings, curation logs, metadata tagging records, documentation, and

SOPs — in editable form sufficient for the Government to use, maintain, and update those products without further reliance on the contractor.

The contractor shall not assert restrictive markings on work products generated under this contract using Government funds. Any pre-existing privately-funded tools, methods, or software that the contractor proposes to use in performance shall be identified to the CO at the time of proposal, and the rights in any such pre-existing items shall be determined by the CO.

13. MISCELLANEOUS

The contractor shall be responsible for the accuracy, timeliness, and completion of all tasks under this effort. The contractor shall provide the COR with all passwords, data collected, processes used, and any other information obtained throughout the contract's period of performance. The

COR will meet with the contractor within seven (7) business days prior to the end of the contract to ensure all information is received.