1) Section C - PM MAV LFSS 24SEP25 SAM.pdf

PM MAV Logistic Fielding Support Services Scope

C.1 General

C.1.1

The contractor, as an independent contractor and not as an agent of the United States Government (Government or USG), shall provide on a term or completion basis, and as specified by Work Directive (WD), Logistic Fielding Support Services and Sustainment Services for Project Manager Mounted Armored Vehicles (PM MAV) Vehicle Portfolio that includes the Bradley Fighting Vehicle (BFV) Family of Vehicles (FoVs), Armored Multi-Purpose Vehicle (AMPV) FoV, MLRS, M113, and M88 Combat Recovery Vehicle FoV and Foreign Military Sales (FMS) Countries. All work performed under Section C shall be accomplished under Task Order(s) (TO) and detailed scope will be further defined by WDs signed by the Procuring Contracting Officer (PCO) and incorporated into the contract via contract modification. The contractor shall receive, respond to, and track Government requests for information, requests for proposals, and investigation and analysis, as specified further in Section C of this contract. The USG reserves the right to modify or cancel WDs in whole or in part and change the order of priority assigned to WDs. The contractor shall not perform an effort unless authorized by a contract modification. Throughout the life of the contract for each work directive and work directive proposal, the contractor must submit a complete Assertion of Restrictions in accordance with (IAW) DFARS.

C.1.4 Vehicle Platforms:

The PM MAV Vehicle Portfolio includes: The Bradley Fighting Vehicle System (BFVS) Family of Vehicles (FoV), Multiple Launch Rocket Systems (MLRS), M88 Combat Recovery Vehicle (M88) FoV, Armored Multi-Purpose Vehicle (AMPV) FoV, and M113 FoV.

C.1.5 Scope:

This Statement of Work (SOW) describes contractor-required services related to maintenance, repair and overhaul, equipment modification, installation of equipment and technical representative services to keep machines, systems, and vehicles functioning and in working order.

Services that shall be provided to FMS, U.S. Army Active Duty, Reserves, and National Guard units under this contract include Materiel Fielding and De-processing, Field Service Representative, Maintenance Teams, Modification Work Order (MWO), Total Package Fielding (TPF) and New Equipment Training (NET) in support of the Bradley, MLRS, AMPV and M88 FoV programs. These services shall be provided at sites located in both Continental United States (CONUS) and Outside Continental United States (OCONUS) locations. The contractor’s responsibilities shall include maintaining control of subcontractor’s efforts to ensure Government requirements are met.

As used herein, the phrase “contractor personnel” includes both prime and subcontractor personnel and the contractor shall ensure that these requirements are included in all subcontracts.

C.1.8 General Requirements

C.1.8.1 Work Authorization

All work awarded hereunder shall be performed to the extent authorized and individually funded under specific WD(s) incorporated into the contract via a TO or modification to a TO.

C.1.8.2 Limitations

Contractor personnel shall not perform inherently Governmental services under this contract, nor shall any work described herein be considered inherently Governmental services.

C.1.8.3 Contractor Personnel

Contractor personnel providing services hereunder are employees of the contractor and subcontractor(s) and are under their sole administrative control and supervision. The contractor shall select, assign, and provide directions to its employees performing services under all TOs and WDs awarded hereunder. The Government will not exercise any supervision or control over the contractor's employees in their performance of services. If the Government determines the schedule, contractor employees are required to work changes from initial planning, the contractor shall identify any change to the Contracting Officer’s Representative (COR) within two business days to address impacts to include changes in hours, cost and material. The contractor is not authorized to execute any changes in schedule without COR approval prior to execution.

C.1.8.3.1 Replacement Personnel

In the event a contractor employee is deemed not capable of supporting the effort or incurs disciplinary action while supporting an effort, the contractor or subcontractor shall remove that person at contractor expense from the support location. Upon learning that a contractor employee needs to leave the location, the contractor shall notify the PCO and COR, via email, within 48 hours. Notifications shall include a summary of the reason why the employee is leaving, the support location, as well as the time when a replacement will be on site to continue support. At the time of this written notification, the Government will determine, within five business days, if a replacement is still required to meet the mission. This determination will be provided to the contractor by the PCO and COR via email. If a replacement is

O'Connell, Joseph - Business Law This sentence isn’t making sense for me.

required, the contractor shall have a replacement on site no later than eight business days after the USG’s determination for CONUS and OCONUC locations.

C.1.8.4 Contractor Personnel Qualifications

The contractor shall utilize employees IAW the minimum qualifications called out in Section H and as specified at the TO level. All contractor personnel assigned to perform work hereunder shall meet the minimum qualifications specified in the TO; to include the proper licenses and ability to operate the required machinery or equipment in fulfillment of the mission. If there are concerns regarding the qualifications of a contractor employee, final determination will be made by the Government.

C.1.8.5 Period of Performance

Each individual TO and WD awarded hereunder will specify a period of performance. Specific schedules will be outlined in the associated WD.

C.1.8.6 Performance Locations

Services performed under this contract may be performed at either an on-site or off-site location. On-site locations may be any U.S. Government base or installation or other contractor facility within the CONUS or OCONUS. Off-site locations may be a contractor's home office, branch office, or any facility/location utilized by the contractor which is not under the control of a Government agency. Each individual WD awarded hereunder will specify the specific location(s) for the performance of the service(s). The contractor shall comply with the work and holiday schedules at each location.

C.1.8.7 Travel

Individual WDs awarded hereunder may require contractor personnel to travel to CONUS and/or OCONUS locations and provide support IAW the schedules and manning levels outlined in the applicable WD. OCONUS travel locations is defined as any location outside the continental United States. Specific locations will be called out in the WD.

The contractor shall be responsible for all travel arrangements for personnel supporting a WD that requires travel. The contractor shall notify the COR of early departures or late arrivals. The contractor will be authorized to make travel arrangements prior to the commencement of work. Travel related activities will be detailed in a Program Management WD.

C.1.8.8 Deploying Personnel

WDs requiring contractors to deploy to OCONUS locations will include pertinent details and requirements for contractors to deploy. Deployable personnel shall meet the requirements specified in Army Regulation (AR) 715- 9.

Depending on the Status of Forces Agreement (SOFA) or other international agreements, contractor employees may be subject to the customs, processing procedures, laws, agreements and duties of the country in which they are deploying to and the procedures, laws and duties of the United States upon re-entry. The contractor shall verify and comply with all requirements.

Upon arrival in the host country, contractor personnel may be required to obtain locally required identification cards.

C.1.8.8.1 Documentation of Deploying Personnel

In support of OCONUS deployment of contractor personnel, the contractor shall identify to the Government all documentation requirements needed No Later Than (NLT) 90 calendar days prior to deployment. If the contractor receives notification less than 90 calendar days prior to OCONUS deployment, they shall identify documentation requirements to the COR within 3 business days of receipt of notification.

The contractor is responsible and authorized for obtaining (i) all passports, visas, and other documents necessary for contractor personnel to transverse through and within the Area of Operation and (ii) the customs, immigration, or similar liabilities of its contractor personnel. Contractor shall be responsible for completing the Synchronized Pre-deployment and Operational Tracker-Enterprise Suite (SPOT-ES) documentation required for deployment and shall request assistance from the Government at least 10 business days in advance, if required.

C.1.8.9 COR

Work Directives will be incorporated into their respective task orders. Each TO will have an appointed COR. The contractor shall direct communications on WD technical matters to the appointed COR.

C.1.8.10 Contractor Management Focal Point

The contractor shall establish a single management focal point and maintain a supporting program management system tailored to accomplish the administrative, management, security, quality control, technical, and financial requirements associated with individual TOs awarded hereunder.

These efforts shall be done IAW Program Management TOs and WDs awarded under this contract.

C.1.8.12 Quality Assurance Program

The contractor shall establish and maintain a quality assurance program governing performance of all TOs and WDs awarded hereunder for identifying and correcting deficiencies in the quality of services. The contractor shall ensure that it has an auditable quality assurance process commensurate with the scope and content of the requirements of each WD. The contractor shall be required to establish a certified quality management system (ISO 9000 or ISO 9001:2015) to the extent the system applies.

Product Quality Deficiency Report (PQDR). The contractor shall investigate and provide failure analysis and corrective action for all PQDRs (Standard Form 368) generated against supplies produced and/or services performed under this contract. USG will provide the contractor with reasonable access to solve problems where exhibits are found to be non-conforming or fail to operate. Should an exhibit of the item in question be required, the contractor shall submit an exhibit request electronically to the Government PQDR Action Officer. All corrective actions taken by the contractor shall be at no additional cost to the Government. PQDR corrective actions which require a configuration change must be approved by the Government PCO. All PQDR investigation reports and associated corrective actions shall be approved by the PQDR Action Officer before the Government considers a PQDR closed. PQDRs will not be closed in Product Data Reporting and Evaluation Program (PDREP) until the corrective action(s) delivered by the contractor or its suppliers are officially approved by the Government IAW CDRL A020 – QDR..

Inspection and Test Equipment. The contractor shall be responsible for their supply and maintenance of all measuring, monitoring, inspection, and test equipment necessary to assure conformance to contract requirements. The contractor shall notify the Government if any inspection and test equipment used, or suspected of being used, is found to be out of calibration or if any changes are made to the inspection and test equipment. The contractor shall make inspection equipment available to the Government during Government in-process or end item inspection.

Inspection Records. The Government reserves the right to review inspection records and process documents upon request.

C.1.8.13 Non-Disclosure Agreements (NDA)

Contractor employees may be required to sign NDAs on a per-Task Order basis, at the Government's discretion.

C.1.8.14 Contractor Field Support Status

The contractor shall submit a Contractor Field Services (CFS) Support Status Report IAW CDRL A008.

C.2 Contract Data Requirement List (CDRL) Deliverables

The contractor shall submit CDRL deliverables IAW the awarded contract hereunder. The delivery, schedule, and format required for those deliverables will be called out in associated CDRLs.

CDRL requirements will be established in individual WDs and shall be uploaded by the contractor via the Government CDRL tool. However, a WD, or the COR, may direct an alternative submission method or place, or dual submission. If the CDRL Tool is the appropriate submission method, and file size limit is exceeded or the Tool rejects the file, the contractor shall upload a notification of delivery instead, and shall notify COR and shall take additional steps as directed by the COR.

Within 10 calendar days after contract award, the contractor shall provide the PCO, Contract Specialist, and COR with a list of personnel requiring access to the CDRL tool. Personnel will be required to have either a Government issued Common Access Card (CAC) or Government-approved External Certificate Authority (ECA) in order to be provided access to the CDRL Tool.

CDRL Tool user instructions and training will be provided at the Start of Work Meeting (SOWM). The contractor shall deliver CDRLs without any security protection features which would prevent the Government from opening, editing, sorting, merging, or otherwise manipulating the data for Government purposes.

C.3 Meeting and Minutes

C.3.1 The contractor shall participate in joint Government-contractor meetings, as specified in the WDs, to monitor the status of integrated logistics services. The meetings shall provide a means for coordination, monitoring schedules and contract performance, and ensuring Government and contractor compliance with established regulatory guidance and contractual requirements. Joint meetings shall be held at the contractor’s facility or via teleconference, web conference, or video conference, as determined by the Government. Requirements for CDRL deliverables for CDRLs A001 and A002, if applicable, will be outlined in the WD.

C.3.7 Meeting Attendance

Any contractor employee attending meetings with Government employees shall, at the beginning of the meeting, announce that they are a contractor employee. The contractor employee must state the contractor's name and state the name of all other companies or persons that (a) currently employ them, or

(b) that they currently represent.

C.3.9 Audio and Network Accessibility for Briefings

The contractor shall provide audio and network meeting capabilities in a Government compatible format when the meeting location is not at a Government facility.

C.3.4 Contract Post-Award Start of Work Meeting (SOWM)

C.3.4.1 The contractor shall schedule and host a Post-Award SOWM at its facility, unless otherwise directed in the WD, within 30 calendar days after contract award. This SOWM is to achieve a clear and mutual understanding of all contract requirements between the Government and the contractor and identify and resolve potential problems to ensure successful contract performance. The contractor shall, at a minimum, invite the COR identified in

Section G or by appointment, the PCO and Contract Specialist identified on the face page of this document, and the Administrative Contracting Officer

(ACO).

C.3.4.2 The COR, PCO, Contract Specialist, and ACO shall be given at least 14 calendar days advance notification, via electronic mail, of the time, date, and location of the SOWM. The contractor shall collaborate with the Government to draft the SOWM agenda prior to the meeting. The contractor shall discuss the determined schedule, cost, and performance goals. The contractor shall deliver a Record of Agenda, Meeting Minutes, and Action Items IAW CDRL A001 and Briefing Material IAW A002 The Government will provide CDRL Tool user instructions and training at the SOWM.

C.3.5 WD Post-Award Start of Work Meeting

The contractor shall host a post-award start of work meeting at its facility, unless some other location is agreed to by the parties, within 7 calendar days after work directive award, or as required by each individual WD. The contractor shall, at a minimum, invite the COR, PCO, and ACO. The contractor shall give the COR, PCO, and ACO at least 3 calendar days advance notification, via electronic email, of the time, date, and location of the SOWM. The contractor shall discuss or present cost, schedule, performance, risks, risk mitigation, issues, and resolution strategies and goals. The contractor shall deliver a Record of Agenda, Meeting Minutes, and Action Items IAW CDRL A001 and Briefing Material IAW A002, if applicable per individual WD.

C.3.6 Other Meetings

The contractor shall conduct or participate in joint meetings with the Government, as specified in the list below. The contractor shall provide the COR with a minimum 5 business day notice prior to the scheduled meeting date.

The requirements of the contractor and frequency for these meetings will be called out in each WD.

a. MWO IPT

b. Government Fielding Branch

c. Logistic Field Support Services Status Reviews

d. COR Field Support Services Review

e. Program Management Reviews (PMR)

f. Field Problem Review Board (FPRB)

g. Environmental, Safety, and Occupational Health (ESOH)

h. Ad Hoc Meetings

i. Fielding Synchronization

The contractor shall prepare, and issue meeting invites via Microsoft Outlook Calendar or Teams calendar invites. To the extent possible, the contractor shall attend the meetings in person with appropriate personnel to present or answer questions as required. If it’s not possible to attend in person, the contractor shall ensure the appropriate personnel are available to attend the meetings virtually. The contractor shall deliver a Record of Agenda, Meeting Minutes, and Action Items IAW CDRL A001 and Briefing Material IAW A002, if applicable per individual WD.

C.3.7 MWO IPT

The contractor shall attend MWO IPT meetings led by the Government, as requested by the USG. The contractor shall participate in discussions relating to specific MWO efforts, schedule, personnel, shipping and inventory assistance, and any known issues with any of the MWO missions covered under a

WD.

C.3.8 Government Fielding Branch

The contractor shall attend the Government led Fielding Branch meeting held on a weekly basis. The contractor shall be prepared to discuss all aspects of their Integrated Logistics Field Support Services efforts currently under a WD and answer questions as required. If required, the contractor shall prepare briefing materials IAW CDRL A002, Presentation Materials.

C.3.9 Logistics Field Support Services Status Review

The contractor shall support status review meetings as requested by the USG and be prepared to discuss any ongoing efforts. The contractor shall provide the status on existing WD’s with any issues that require administrative changes. The contractor shall be prepared to discuss all facets of the Sustainment Services program at these meetings to include cost, schedule, performance, and risk.

C.3.10 COR Field Support Services Review

The contractor shall conduct, on a quarterly basis, Field Support Services reviews of all efforts under the WDs. Briefings shall contain, by WD, efforts previously performed; upcoming efforts; any known issues or problems;

description of hours authorized, hours expended, material dollars expended, and material dollars committed; and any variances from planned efforts and reasons for the variances. Following each meeting, contractor shall provide meeting minutes IAW CDRL A001, Record of Meeting Minutes Report, Meeting Minutes and Action Items.

C.3.11 PMR

The contractor shall host and prepare materials to support a PMR on an annual basis. The contractor shall present cost, schedule, performance, and any risks for each active TO performed under this contract and be prepared for detailed discussion with the Government. The contractor shall prepare briefing materials IAW CDRL A002, Presentation Material.

C.3.12 FPRB

The contractor shall participate in the Government hosted bi-annual FPRB and as requested for each individual PM MAV vehicle platform regarding field problems with a wide range of participants from working-group level personnel to leadership. The contractor shall be prepared to propose resolutions and risks with risk mitigation(s) at each FPRB meeting and be prepared to engage in discussions.

C.3.13 Environmental Safety and Occupational Health Meetings

The contractor shall participate in the Government hosted bi-annual discussions regarding safety issues with a wide range of participants from working-group level personnel to leadership. The contractor shall identify potential risks, propose resolutions and mitigation plans at each meeting as necessary.

C.3.14 Ad Hoc Meetings

As required, the contractor shall attend, virtually or in person, ad hoc meetings required to manage the various efforts performed under this contract. Government will provide notice of meetings in as much advance as possible. For ad hoc meetings, the contractor shall support discussion of the issues and take any actions out of the meetings delegated to them. These meetings will be required to facilitate the management of the Field Support Services efforts as they operate in a changing environment.

C.3.15 Fielding Synchronization Meetings

The contractor shall discuss analysis, schedules, milestones, accomplishments, future planning, corrective action planning, risks, risk mitigation strategies and issues regarding worldwide fielding synchronizations. These meetings will be attended by the contractor and Government fielding teams worldwide. These meetings will be chaired by the Chief, Materiel Fielding Team. The contractor shall make no changes to fielding schedule(s) or change the make-up of any TPF package without approval of the Chief, Materiel Fielding Team.

C.3.16 Materiel Requirements List (MRL) Coordination Meetings

The contractor shall conduct quarterly MRL Coordination meetings with the Fielding and/or Gaining Commands, Materiel Fielding Team (MFT), and Integrated Logistics Support Managers. The contractor shall answer questions related to discrepancies identified in the MRL and obtain results of recent configuration changes to be incorporated into a final MRL using the Basis of Issue Plan (BOIP), Modified Table of Organization and Equipment (MTOE), Table of Distribution and Allowance (TDA) for Training & Doctrine Command (TRADOC) Units, and System Architecture (SA). The contractor shall deliver Fielding Hand-Off Documentation/DA Form 5682 Submittal report IAW CDRL A004. The report shall include the final MRL (documented on DA Form 5682 or other approved format from DA PAM 770-2) IAW the configurations within the BOIP/MTOE/SA authorization document(s) provided by the Government. Meetings shall be conducted at a Government facility or through teleconference calls.

During the meeting, the Government will provide a Mission Support Plan (MSP) that shall be used by the Material Fielding Team (MFT) during its development of the initial issue.

C.3 Task Orders and Work Directives

C.3.1 Task Order Requirements. All work under this contract shall be performed under individual Task Orders. Each Task Order will incorporate Work Directive(s), which will further detail the scope of work to be completed.

C.3.2 Work Directive Requirements. Work Directives will be identified in Section B of the Task Order, by Contract Line-Item Number. Work Directive(s) may take one of two basic forms - completion or term. Each Work Directive will specify which form applies to the individual effort. Work Directive(s) shall be within the general scope of the basic contract and will be incorporated as an attachment to Section J of its respective Task Order. The contractor shall notify the Government immediately of any Work Directive or portion of a Work Directive that duplicates or appears to duplicate work previously performed under Government contracts. The contractor shall provide all necessary labor, materials, supplies, services, facilities, and equipment to perform the specific services required by the Work Directives

C.3.3 The contractor shall notify the COR and the PCO immediately by email if any scheduled requirement will not be met as defined, detailing the reason(s) why the requirements will not be met and proposing corrective action. The COR may, in writing, provide alternative notification procedures.

C.3.4 WDs will outline Government Furnished Material (GFM), Government Furnished Equipment (GFE), or Government Furnished Information (GFI) to be provided via Attachment 0001 of the Task Order.

C.3.5 Conflicts of interest. The contractor shall notify the PCO of any potential or suspected conflict of interest and provide the plan to mitigate or eliminate the conflict to the satisfaction of the Government.

C.3.6 Work Directive Close-out. The contractor agrees to perform those internal functions necessary to support this process in a timely manner. Work Directive closeout will occur 60-90 calendar days after Work Directive performance has concluded.

C.4 Program Management

The contractor shall manage and control its resources to ensure contractual requirements are met efficiently and economically, including management and control of subcontractor performance. The contractor shall provide all resources necessary to perform the services defined in this contract, except for those items otherwise noted in the WD. The contractor shall be responsible for the administration, operation, and conduct of all personnel providing services under each WD.

C.4.4 Desktop Metrics. If a WD requires desktop metrics (also known as project schedule), the contractor shall develop, maintain, and submit a contractor developed, logic driven Desktop Metrics schedule IAW CDRL A0044 Desktop Metrics – Project Schedule.

C.4.4.1 Desktop Metrics shall be delivered IAW CDRL A044 and shall provide the following data: contractual milestones, major decision points, planned events, summary-level activities, intermediate activities, and detailed tasks and planning packages from contract award through completion of its performance. It should provide sufficient detail to facilitate Government assessment of schedule realism. The Desktop Metrics shall be integrated, logical networked-based schedule and shall include activities from other contracts that impact the project. The contractor shall apply predecessor and successor relationships at the lowest level of tasks, and those tasks shall contain projected start and finish dates and baseline start and finish dates.

The Desktop Metrics shall identify critical paths and clearly provide for slack time to accommodate unexpected program events.

The desktop metrics shall include fields and data that enable the user to access the information by product, process, function, or organizational lines. The desktop metrics shall have a numbering system that provides traceability to the WBS. Progress-to-date status shall include, at a minimum, estimated start and finish dates, actual start and finish dates, estimated percent complete of activities and tasks, remaining duration, and revised forecasts.

C.4.5 Cost and Software Data Reports (CSDRs)

C.4.5.1 CSDRs are the primary means by which the Department of Defense (DoD) collects data on the costs that contractors incur on DoD programs. Reliable and comprehensive cost data is essential to produce credible cost estimates as required in both statute and regulation. The Governments goals and use of CSDR data is to improve the quality of cost estimates, ensure proper resource allocation occurs within the DoD, and enable data driven decision making by program and department leadership.

The contractor shall systematically collect, report, and deliver actual contract costs by work directive in the following reports:

Report Title CDRL:

-Resource Distribution Table (RDT) A005

-Cost and Hour Report / Flexfile (DD Form 1423-1) A006

-Maintenance and Repair Parts Data Report A007

The contractor shall prepare CSDR reports IAW the above listed CDRLs, CSDR Plan (Attachment 0001).

C.4.5.2 Application to Subcontractors

The contractor shall flow-down CSDR requirements to subcontractors (regardless of subcontractor tier) when the subcontract value is expected to exceed $50 million using the most likely contractor quantities, hours, or options (as applicable), as required by Department of Defense (DoD) Manual

5000.04 (CSDR Manual). The contractor shall require subcontractors to electronically submit CSDRs deliverables directly to the Defense Cost and Resource Center (DCARC) IAW CDRLs A005-A007. The contractor shall ensure that subcontractors subject to CSDR reporting thresholds collect data in sufficient detail to meet Attachment 0001 – CSDR Plan requirements. The contractor shall collect and deliver data on all subcontractors to comply with Attachment 0002 RDT and CDRL A005 – RDT and Attachment 0001 – CSDR Plan requirements. A subcontract is any agreement, purchase order, or instrument other than a prime contract calling for work or for the material required for the performance of one or more prime contracts.

C.4.5.3 Resource Distribution Table.

In accordance with the work directive, the contractor shall develop, maintain, and deliver the data item IAW Attachment 0002 RDT and submit it under CDRL A005. The RDT identifies the value of work assigned to the contractor and its subcontractors by each WBS element listed in Attachment 0001 CSDR Plan, and is the primary means of identifying which subcontractors qualify for CSDR flow down reporting.

C.4.5.4 Cost and Hour Report (Flexfile)

The contractor shall prepare and submit the “Cost and Hour Report (Flexfile)” IAW CDRL A006. The “Cost and Hour Report (Flexfile)” reports incurred and forecasted costs and hours related business data in order to perform this contract. The contractor shall utilize the Contract Work Breakdown Structure (WBS) identified in Attachment A001 – CSDR Plan, as the primary framework for contract budgeting and reporting of costs and hours to perform the contract.

The contractor shall extend the WBS to provide adequate internal management, surveillance, and performance measurement of the contract. The contractor shall ensure all WBS oriented reporting is compliant with at least the levels identified in Attachment 0001 – CSDR Plan.

C.4.5.5 Maintenance and Repair Data Report

The contractor shall prepare and submit the Maintenance and Repair Parts Data Report IAW CDRL A007. This report captures maintenance event data related to each maintenance event.

C.4.5.7 Cost and Software Data Reporting (CSDR) Readiness Reviews

The contractor shall host a CSDR Readiness Review at the contractor’s facility or virtually using a screen sharing platform where CSDRs are prepared with the Government’s Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD Manual 5000.04 (CSDR Manual). The purpose of the CSDR Readiness Review formally known as the Post Award Conference (PAC) is to review the contracts CSDR requirements and assess how the Contractor’s accounting system satisfies the CSDR requirements found in DoD 5000.04 (CSDR Manual) and the CSDR Plan (Attachment 0001). In a briefing presented by the contractor in its own format, the contractor shall:

- Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.

- Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.

- Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by the CSDR Plan (Attachment 0001) and associated CDRLs.

- Present the methodologies used for mapping internal cost accounts to the WBS, specifically showing how individual WBS elements and functional element codes will be populated.

- Propose any changes to the CSDR Plan (Attachment 0001) in order to tailor the plan to the contractor’s accounting system, to include any Contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct reporting subcontractor performing against a different delivery schedule than the associated prime Contractor.

The contractor and CWIPT will also review the initial submission of the Resource Distribution Table (RDT) (CDRL A005), in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the Defense Cost and Resource Center (DCARC) and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.

The Readiness Review shall be held within 60 calendar days after work directive award or the SOWM on a date mutually agreed to by the CWIPT and the Contractor. The duration of the Readiness Review will depend on level of complexity of the program, the contract, and reporting entity’s prior experience with the requirement and/or specific issues that may require in-depth discussion. The meeting is typically 1-4 hours but actions with more complex CSDR Plan or less experienced reporting entities should reserve a full working day. For additional planning guidance for the CSDR-Readiness Review meeting reference the CSDR Readiness Review guide on the CADE website (https://cade.osd.mil/).

C.4.6 The contractor shall deliver a Project Status Report (PSR) IAW CDRL A009. This report shall provide a description of the work performed against the WD during the Period of Performance of the WD. The PSR report shall include descriptions of WD progress and contributions during the Period of Performance to document achievements against established objectives and plans. Material to be covered may also include a brief description of tasks performed in the reporting period, accomplishments highlighted, technical issues/resolution, and recommendations. The report shall be limited to contractor and subcontractor efforts in performance of the Work Directive being reported.

C.4.7 Performance Management

C.4.7.1 The contractor shall establish, maintain and use an Integrated Performance Management System in the performance of WDs.

C.4.7.2 The contractor shall deliver a Performance and Cost Report (PCR), IAW CDRL A010. The PCR shall include monthly and cumulative-to-date Budget, Performance, and Expenditures by WD. This report shall be in contractor format.

https://cade.osd.mil/

C.4.7.3 The WD corresponding to each WBS shall be indicated on the PCR report. The contractor shall break out labor hours, labor dollars, material, Other Direct Costs (ODCs), and total costs by WBS. The Government reserves the right to request the contractor to decompose subcontractor ODCs to include subcontract labor cost, subcontract material cost, and subcontract ODC cost. Cost variances shall be reported in the differences between Budgeted Cost of Work Performed (BCWP) and Actual Cost of Work Performed (ACWP). Schedule variances shall be reported as the differences between BCWP and Budgeted Cost of Work Scheduled (BCWS). The contractor report shall also include the Budget at Completion and a Latest Revised Estimate (LRE) including estimated overrun/underrun for all authorized work. The PCR shall include the Period of Performance for each TO and WD. The contractor shall comply with notification requirements outlined in FAR 52.232-20, Limitation of Cost, per TO and WD.

C.4.9 The contractor is not authorized to incur hours that exceed the estimate on each executed WD and the hours awarded in each CLIN. Any hours in excess of those awarded are unallowable unless a Pre-Contract Cost Authorization is signed.

C.4.10 Contract Funds Status Report (CFSR)

C.4.10.1 The contractor shall provide the CFSR IAW CDRL A011. The contractor shall reconcile reporting elements in the CFSR with the PCR as an addendum to the PCR.

C.4.10.2 Every CLIN or subCLIN that is directly billed by the contractor for payment will be reported on a separate CFSR page. The contractor may aggregate multiple related subCLINs on a single CFSR page only if those subCLINs are billed at the CLIN level. The general intent is for data in the CFSR to be segregated in such a way that is one-to-one with how the contractor submits billings to the Government for payment.

C.4.11 The contractor shall deliver CDRL A012, Reachback Report, which documents systems and parts exhibiting excessive malfunctioning or wear, manual passages that are incorrect, software that exhibits excessive malfunction, and other items that materially differ from their intended design or function, and are mission critical. The WD will provide guidance and the method and timing of documentation and reporting.

C.4.12 Short Duration Efforts (SDEs) are up to 200 hours and consist of efforts related to any Vehicle Platform or Project Management Office issues, problems, document review, meetings, logistics support, or studies that are not yet determined. SDEs will be executed the same as other WDs and will be funded under Program Management. The contractor shall deliver a Short Duration Efforts Report, IAW CDRL A013. This report shall provide a list of SDEs by month and the status of each SDE.

C.4.13 Rough Order of Magnitude (ROM)

The Government may request a ROM, to obtain an estimated budget in support of a WD. The contractor shall submit the ROM within five business days of the request for a ROM. ROMs shall be prepared IAW CDRL A003.

The Government’s request for a ROM in no way infringes on its unilateral right to issue work directives

C.4.13.2 Request for Proposal (RFP)

C.4.14 The Government may issue an RFP in response to any ROM submission. The Government may award a WD to provide funding for the contractor to review and provide input on proposed future WDs.

C.4.14.1 The contractor’s proposal shall be inclusive of labor hours, labor cost, material, travel, and other direct costs with support and rationale.

The contractor shall provide comments, concerns, technical expertise, best practices, and lessons learned in support work directive proposal development and ROM estimates.

C.4.15 Excess funding on cost-based CLINs will be de-obligated by the Government once contract performance is 100 percent complete. De-obligation of excess funding does not impact the contractor’s right to subsequently submit a voucher reflecting settled amounts and rates IAW FAR 42.705(b), unless otherwise indicated in the contract modification which de-obligated the funding.

C.4.17 Government Furnished Property (GFP) and Government Furnished Information (GFI)

C.4.17.1 All GFP to include GFM, Government Furnished Equipment (GFE), and GFI will be listed in Attachment 0003, Government Furnished Information, Material, and Property List, which will be incorporated by Task Order.

C.4.17.2 The contractor shall prepare and deliver a Government Property Inventory Report in accordance with CDRL A014. The CDRL report shall include for each GFM/GFE/GFI item: current quantity on hand, current usage rate, current condition of items, forecasted usage schedule, and status summary of PQDR submitted on the item (if any). The contractor is authorized to utilize GFP across any TOs issued under this contract, unless otherwise directed by the USG. Government assets accountable to other contracts shall not be redirected or used for activities on this contract without written concurrence from the cognizant PCO.

C.4.17.3 The contractor shall not use vehicles for any purpose outside the scope of work for this contract without prior written approval from the PCO.

C.4.19 Transportation Account Codes

The Government will provide a Transportation Account Code for transportation of Government owned parts, materials, and tools to all locations.

C.4.20 The contractor shall complete a PQDR and deliver a Quality Deficiency Report, IAW CDRL A020. The Government will provide the contractor with disposition instructions for the non-conforming product.

C.5 Government Furnished Property and Incidental Property

GFP will be provided by the Government on a TO basis, based on WD requirements, IAW Attachment 0001.

C.6 Fielding & Support

The contractor shall provide planning, coordination, technical, and management support of all fielding aspects of identified assets.

C.6.1 The contractor shall provide a list of the facilities, logistical, and administrative requirements needed to set up and conduct fielding preparation.

C.6.2 Total Package Fielding

The Government will issue vehicles IAW AR 770-2 and DA PAM 770-2 with Basic Issue Items (BII), Components of the End Item (COEI), and if needed Special Tools & Test Equipment (STTE), Authorized Stockage List (ASL) items, Technical Manuals (including Interactive Electronic Technical Manuals).

Additional Authorized List (AAL), and Associated Support Items of Equipment

(ASIOE).

TPF activities include supply requisitioning, staging, inventorying, providing caretaker stockage, equipment shipment & hand-off using property book automation systems, precise documenting and closing out of records, and conducting New Materiel Introductory Briefings (NMIB), unit level In Process reviews (IPR), and Materiel Requirements List (MRL) reviews. Specific contractor requirements and the scope of work required to support overall TPF activities will be defined in each WD.

C.6.2.1 Regarding TPF services actions, the contractor shall:

a) Participate and support the Government lead in NMIBs.

b) Assist Government personnel in preparing the fielding site.

c) Assist Government personnel in conducting joint inventory of BII, COEI, applying Operations/Modifications kit (Op/Mods), and if required, ASL, AAL and STTE.

d) Assist Government personnel in preparing documentation for unit signature.

e) Assist Government personnel in hand-off of vehicle and all TPF materiel.

f) Assist Government personnel in documenting vehicle serial number and item unique identification (IUID) to the unit receiving it, so that the Global Combat Support System – Army (GCSS – Army) database can be loaded.

g) Track shipment of Vehicles, BII and COEI.

h) Provide a status of TPF events in accordance with CDRL A009, FSR Report.

fi) Receive, load, unload, tie down (shackle), unshackle, transport, de-process, and prepare vehicles for issue during fielding events.

j) Update, kit, maintain, and deliver the Basic Issue Items (BII), Additional Authorized List (AAL) items, and Components of the End Item (COEI) required for vehicle fielding. The contractor shall provide a Fielding Hand-Off Documentation Report IAW CDRL A016. The contractor shall enter information from fielded vehicles onto DA Form 3161 and information and information from fielded vehicle BII, COEI, AAL, ASL, and STTE onto DA Form 2062.

k) Provide and physically attach, mount, or otherwise install all common and unique repair parts necessary to operate and maintain vehicles in -10/-20 standard condition during fielding and training events.

l) Perform a functional check on all Mission Equipment Packages associated with the vehicles. This includes interoperability and connectivity of all vehicle computer/ communication systems. The contractor shall report deficiencies in accordance with CDRL A017, Deficiency Report.

C.6.2.2 New Materiel Introductory Brief

The contractor shall be prepared to assist with NMIB activities for the gaining unit and be present at all NMIB sessions as directed or requested by the Government. The contractor shall provide personnel to offer assistance and support as needed.

C.6.2.3 Fielding and Site Preparation

C.6.2.3.1 The contractor shall have personnel present at fielding sites to perform 100% inventories and to prepare vehicles to include BII, COEI, applying Operations/Modifications kit (Op/Mods), and if required, ASL, AAL, and STTE for hand off and/or training. The contractor shall document all major items for each fielding as authorized by the units Modified Table of Organization and Equipment (MTOE) or Tables of Distribution and Allowances (TDA) to determine the proper vehicle configuration prior to hand off to the unit.

C.6.2.3.2 The contractor shall provide serial number and IUID to the Government fielding team, upon request. This documentation is essential for the proper property book transactions to take place in GCSS-Army, Defense Property Accountability System (DPAS), or Logistics Modernization Program (LMP). The contractor shall record the serial numbers of all major assemblies and components and install all Components of End Item (COEI).

C.6.2.3.3 The contractor shall track and record all vehicle shipments, BII, COEI, STTE, ASL, and AAL and deliver this data IAW CDRL A018, Record Vehicle Shipments. This report shall include vehicle arrivals, vehicle inventory report, and shipping discrepancy.

C.6.2.4 TPF Materials

The contractor shall receive, inventory, kit, store, maintain, and consolidate TPF materials received from the Government, as required by a WD.

The contractor shall provide a Maintenance and Repair Parts Data Report IAW CDRL A0043. This report shall list all parts requisitioned due to required repairs, shortages, or missing items.

C.6.2.5 The contractor shall provide FSR technical support during vehicle fielding and training events. In addition, the contractor shall provide one FSR for each Armor Brigade Combat Team for one year after completion of NET as specified in the individual WD.

C.6.2.5.2 The contractor shall manage all repair parts including receiving GFM supplies from the Government, storing parts until needed, and the turn in or disposal of unserviceable parts and equipment.

C.6.2.5.3 The contractor shall document all non-mission essential items not available at the time of initial handoff or re-issue. The contractor shall document this information in an After Action Report (AAR) to be delivered

IAW CDRL A019. The contractor deliver status and document issues (i.e.

overages, shortages, damaged material, past due contract delivery schedule dates) IAW CDRL A019.

C.6.2.6 Vehicle Handoff

The contractor shall load, offload, and move end items, perform inventory of vehicles and equipment, perform quality assurance inspection of the vehicles, perform maintenance functions adjust, align, service, repair, clean, inspect, and perform road test of end items. The contractor shall provide logistics management support by assisting the Government in preparing DA Form 2062 and DA Form 3161 for unit signature.

C.7 TPF AND DE-PROCESSING, MAINTENANCE & POST FIELDING INSPECTION (PFI)

C.7.1 Reception

C.7.1.1 Contractor personnel, as required by individual WDs, shall be at the location specified in the schedule to download vehicles from the rail head or ship when vehicles arrive. Personnel shall assist the Government with loading/off-loading, and if necessary, chaining/unchaining vehicles from rail cars or ships. Vehicles arriving by ship will be moved to Rail Head or commercial truck. Vehicles arriving by commercial truck will be off loaded at the Deprocessing and or PFI locations. Vehicles arriving by rail, will be moved by the contractor with Government assistance from the Rail Head to the Deprocessing and or PFI Location. As directed by individual WDs, FSRs shall either drive the vehicles themselves, or assist the Government team with transporting the vehicles from the download site to where they will be de-processed.

C.7.1.2 The contractor shall inspect vehicles IAW the Preventive Maintenance, Checks and Services (PMCS) section of the Technical Manuals (TM) and identify all deficiencies and shortcomings, with electronic faults isolated to the circuit card or Shop Replaceable Unit (SRU) level through troubleshooting.

The contractor shall document deficiencies and shortcomings on the DA FORM 2404 or 5988-E.

C.7.2 Vehicle Deprocessing

Deprocessing is the checkout of vehicles at the deprocessing or handoff site(s) upon arrival from production facilities. The contractor shall de-process all equipment after delivery to the deprocessing site. The contractor shall ensure vehicles are ready to operate prior to issue to the receiving unit.

C.7.2.2 IAW platform specific de-processing checklists, Attachments 0004- 0006, the contractor shall remove all preservative coatings, grease, tape, and packing materials from vehicles and inspect vehicles for any damage incurred during shipment. The contractor shall ensure that all aspects of vehicle operation are checked and verified prior to issuing the vehicle. The contractor shall troubleshoot and repair Government Line Replaceable Units (LRUs) with electronic faults and isolate to the circuit card or Shop Replaceable Unit (SRU) level. The contractor shall ensure that all aspects of vehicle operation are checked and verified prior to issuing the vehicle. The contractor shall troubleshoot and repair Government Line Replaceable Units

(LRUs) with electronic faults and isolate to the circuit card or Shop Replaceable Unit (SRU) level.

C.7.2.3 Deprocessing actions shall be performed IAW specific WD requirements and include the following:

(a) review of vehicle operations,

(b) pull oil analysis samples and take corrective actions as determined by the Army Oil Analysis Program (AOAP) and provide to the gaining unit for submittal,

(c) road testing (if applicable),

(d) replacement of failed or discrepant components.

C.7.2.5 During vehicle de-processing and inventory, the contractor shall identify all repair parts, components and major assemblies found to be defective, missing or damaged that render a vehicle platform (inclusive of end items and major assemblies) not fully mission capable (NFMC) as defined in Army Regulation 700-138, “Army Logistics Readiness and Sustainability,” - 10/20 Technical Manuals, and Deprocessing Checklists, Attachment 0004-0006.

The contractor shall generate the following documentation…