Exhibit F QASP H2F.docx

Quality Assurance Surveillance Plan

For

U.S. Army Reserve Holistic Health and Fitness (H2F) Pilot Program Re Compete

Contract # W81K0422R0026

18 APR 2022

QASP H2F

TABLE OF CONTENTS

Subject Page Number

1.0 Overview 3

2.0 Description of Services 3

3.0 Roles and Responsibilities 4

4.0 Contract Quality Requirements 6

5.0 Government Surveillance 7

6.0 Non-Conforming Performance 9

7.0 Deduct Plan 10

8.0 Data Analysis 10

9.0 Acceptance of Services 10

10.0 COR Status Report 10

11.0 Contractor Manpower Reporting Application 10

12.0 Contractor Performance Assessment Reporting System 11

13.0 Combating Trafficking In Persons 11

14.0 COR/Quality Assurance Surveillance Files 12

15.0 QASP Changes 12

1.0 Overview.

1.1 Purpose. The purpose of this Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures the Government will use to ensure that it receives the services under this contract as identified in the Performance Work Statement (PWS). The objective of this firm fixed price contract is to acquire Holistic Health and Fitness (H2F) education and training services for the U.S. Army Reserve H2F Pilot Program. Government-furnished property and services for those items are specified in the PWS. The Contractor shall perform to the standards specified in U.S. Army Reserve Holistic Health and Fitness (H2F) Pilot Program PWS.

1.2 Intent. The intent of this QASP is to:

1) Ensure Contractor performance meets or exceeds contract terms, conditions and specifications

2) Hold the Contractor accountable for quality control

3) Encourage the Contractor to take appropriate steps to control and improve quality

4) Ensure all sections of FAR 46 are applied as required and applicable

Accordingly, the Government will perform surveillance on the contract in accordance with this QASP, but reserves the right to monitor the contract in any manner necessary, at any time necessary, and at all places necessary to ensure that the services rendered conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level, and at the contractor's place of business. Sub-contract service providers shall be accountable to the Contractor who, in turn is responsible to the Government. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor. The Government will not exercise any supervisory controls over the contract service providers performing the services herein.

2.0 Description of Services.

2.1 Scope of Work. The contractor shall provide all personnel, transportation, supervision, and non-personal services necessary to perform H2F education and training services as defined in this PWS. This is the second year of the Pilot program of Pilot tests in the 81 Readiness Division (RD) region, Pilot A and Pilot B (1,200 pax each), with different levels of resourcing. The Contractor shall provide in-person education by an H2F Team (5 pax) during the unit Battle Assemblies (BA) 9x/year to Pilot A units, education stored on a mobile accessible website, and a full-time Human Performance Advisor (HPA) for reach back support, technical expertise as the lead strength and conditioning specialist, and to oversee the execution of all services. Pilot B units receive web based information and reach back expertise for unit Master Fitness Trainers (MFT) and Master Resilience Trainers (MRT).

2.2 Type of Contract. The contract will be firm fixed price.

3.0 Roles and Responsibilities. The following provides a synopsis for the roles and their respective authority during the performance of the contract:

3.1 Government.

· Assure that the Contractor performs the technical requirements of the contract

· Perform inspections necessary in connection with contract performance

· Maintain written and oral communications with the Contractor concerning technical and performance aspects of the contract

· Issue written interpretations of technical requirements, including Government drawings, designs, and specifications

· Monitor Contractor's performance and documents and notifies both the Contracting Officer and Contractor of all deficiencies

· Coordinate availability of Government furnished property

· Provide site entry of Contractor

ACC and MICC do not use other acronyms to refer to and describe a COR. Terms such as the “COTR, “Onsite COR”, “TM”, etc. will not be used. Some personnel may be assigned as Alternate CORs, but other than a statement to that effect and what actions the KO expects that ACOR to take in the absence of the primary COR, there is no difference between a COR an Alternate COR, or other government surveillance personnel assigned to conduct contract oversight. Throughout the remainder of this QASP, The term “COR’ will be used to refer to all government surveillance personnel assigned to monitor the contractor’s performance on this contract.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost, price, or delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

The Contracting Officer shall use the Joint Appointment Module (JAM) and the Surveillance and Performance Monitoring (SPM) Module in Procurement Integrated Enterprise Environment (PIEE) to electronically track COR nominations, appointments, terminations, and training certifications for each COR appointed to conduct oversight on this contract. The COR will upload their surveillance documents, such as Monthly Status Reports (MSR), COR trip reports, correspondence with the contractor, and other miscellaneous documents into the Surveillance and Performance Monitoring (SPM) Module for this contract. The Joint Appointment Module (JAM) and the Surveillance and Performance Monitoring (SPM) is available within the (PIEE) at: https://wawf.eb.mil/.

3.1.2.1 Alternate Contracting Officer’s Representative (ACOR). N/A

3.2 Contractor.

3.2.1 Contract Manager. N/A

3.2.2 Program Manager. N/A

3.2.3 Quality Manager. The Contractor responsible for promoting quality achievement and performance improvement throughout the organization. Develops, implements, communicates and maintains a quality plan to bring the Contractor’s Quality Systems and Policies into compliance with quality system requirements. Directs the activities of contractor quality personnel to measure key quality characteristics of services delivered and processes from inception to completion. Establishes the standards of service for customers expected by the Requiring Activity.

For quick access, the contact information for the performance of this QASP is provided:

Government Personnel:

Table 1: Key Positions for Contract Administration

Contracting Officer

Contractor Personnel:

Quality Manager

4.0 Contract Quality Requirements.

4.1 Contractor’s Quality Control Plan/Program (QCP). The Government will evaluate the adequacy of the Contractor’s QCP performance under this contract in accordance with this QASP. The Contractor’s quality control program is the means by which he assures himself that all work complies with the requirement of the contract PWS. It is essential that Government Surveillance Personnel understand that Quality Control (QC) is the responsibility of the contractor, and not the government.

As such, the Government will focus their efforts on validating if the Contractor is maintaining an adequate quality control inspection system that ensures the Contractor maintains evidence that services provided conform to contract quality requirements. The Contractor shall provide inspection data to the Government on request for validation. The Contractor’s QCP shall include a process that can identify, prevent, and ensure non-recurrence of defective services. See Attachment 7, List of Contractor Requirements.

4.2 Government Quality Assurance. This QASP describes what the Government will do to ensure that the Contractor has performed in accordance with the performance standards within the PWS.

This QASP describes:

· How the performance standards will be applied:

· The Performance Standard for each requirement in the PWS will be applied as prescribed in the PWS. Ensure that each Performance requirement within the PWS includes a Measurable performance standard in terms of quality, timeliness, or quantity.

· Ensure the method of assessing contractor performance against performance standards is included in this QASP.

· Ensure each Performance Requirement includes an acceptable quality limit (AQL). AQL is the worst tolerable performance that is still considered acceptable.

For example; if “the contractor shall provide personnel support within 2 hours”, the AQL may be:

+ Or - (+/-) 15 minutes. See Attachment 8, QASP Surveillance Item Requirements

· Which performance elements will be surveilled (Attachment 4, Surveillance Checklist)

· All performance activities will be surveilled through-out the Period of Performance, using a risk based approach to selecting Checklist items from Attachment 7, List of Contractor Requirements. The selected items will be populated on the Monthly Checklist and placed on the Surveillance Schedule for each period surveilled.

· When the surveillance will be scheduled (Attachment 3, Surveillance Schedule)

· A sample of Checklist items will be selected from Attachment 7, List of Contractor Requirements. These selected items for each month will be placed on the Surveillance Checklist and scheduled surveillance on the Monthly Schedule. Surveillance may be scheduled on a daily, weekly or monthly frequency. However, each contractor requirement must be audited for compliance prior to invoice payment being made.

· The Acceptable Quality Limit (AQL)

· The AQL will be determined by the Requiring Activity, i.e., the COR, and referenced in Attachment 8, QASP Surveillance Item Requirements for each Performance requirement.

· The nature of Government contract quality assurance actions that include the number of observations made and the number and type of defects (defect rate).

· Personnel conducting contractor performance surveillance will use Attachment 4, Surveillance Checklist, or equivalent to answer the Performance question asked, and provide comments in the area provided on the checklist. These comments and metrics from the Checklist will be included on each MSR submitted during the Period of Performance.

5.0 Government Surveillance.

5.1 Methods of Surveillance. The following Methods of Surveillance may be utilized in monitoring the Contractors’ performance

1. 100% Inspection will be reserved for the highest risk areas where consequence of failure may affect life or limb, or there is likelihood of mission failure

1. Periodic Inspection Will be used when planned sampling of a service is at a specific predetermined date and time. This is most appropriate for tasks that occur infrequently, yet on a scheduled basis.

1. Customer Feedback. Attachment 2, Customer Complaint Record, DA Form 5477, will be placed at convenient locations for the end user of these services, and made available to document/record all complaints. The COR will collect the Customer Complaints each surveillance cycle and investigate for validity ASAP.

The following procedures will be followed when a complaint is received.

1. The COR will investigate to determine the validity of the complaint

2. If the complaint is determined to be invalid, the COR will inform the person who submitted the complaint of the reason(s) as soon as practical

3. For validated complaints that are true contractual non-conformances, the procedures in paragraph 6 below will be applied

4. A Customer Complaint Log will be used to document each validated customer complaint and uploaded monthly surveillance report in the Surveillance and Performance Monitoring (SPM) Module in PIEE.

5.1.1 Surveillance Procedure.

5.1.1.2.2 The COR will review the Contractor supplied In-person Education Evaluation Reports that are to include Soldier satisfaction feedback and recommendations to improve education delivery. The COR will review these reports within one week after each In-person Education training iteration. These reports will be signed by the COR, verifying review and concurrence with the validity of the information. These reports will be included with the COR monthly report in the CORT tool.

5.1.1.3 The COR will perform 100% inspection of Contractor developed periodized physical readiness training programs for use by Soldiers on a Smart phone-based mobile application (supplied by the government) after 30 days of contract award then quarterly during the contract period of performance (PoP). If the COR discovers a deficiency(s), the COR will immediately notify the contractor’s QM for re-performance of the service to ensure compliance. If the standards are not met or if the contractor’s QM refuses to correct an identified deficiency, the COR will notify the contracting officer for appropriate action in accordance with the appropriate inspection of services clause. The COR will utilize the attached checklist(s) to track and document surveillance.

5.1.1.4 The COR will perform period inspection of the in-person education iterations either by on-site observation at the Pilot units or by observing the education iterations via the Microsoft Teams communication platform to ensure compliance with education topics provided by the government and to ensure quality and coordination of the education iteration. The COR will document the unit/date/instructor/education topic sampled and any deficiency on an excel spreadsheet. If the COR discovers a deficiency(s), the COR will immediately notify the contractor’s QM for re-performance of the service to ensure compliance. If the standards are not met or if the contractor’s QM refuses to correct an identified deficiency, the COR will notify the contracting officer for appropriate action in accordance with the appropriate inspection of services clause.

5.1.1.5 The COR will perform an analysis of Customer feedback either by email or phone solicitation of unit commanders, unit MFT, unit MRTs, and unit H2F coordinators in order to assess training support and access for the Smart phone-based mobile application, and timeliness of the reach back support to the participating units from the Contractor. The COR will document responses on an Excel spreadsheet to be included with the COR monthly report in the CORT tool.

5.2. Surveillance Schedule. Attachment 3, Surveillance Schedule will be created each month utilizing the DA 5475, COR Surveillance Schedule, or locally generated equivalent. The schedule is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Schedule will be completed at the beginning of each month during the Period of Performance (PoP) to schedule the upcoming month surveillance activity. Completed Surveillance Schedules will be filed in the Surveillance and Performance Monitoring (SPM) Module in PIEE (https://wawf.eb.mil) file for this contract.

5.3 Surveillance Checklists. Attachment 4, Surveillance Checklist will be created each month utilizing the DA 5476, COR Surveillance Checklist, or locally generated equivalent. The Checklist is “FOR OFFICIAL USE ONLY” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Checklist will be completed with the Surveillance Schedule. Completed Surveillance Checklist will be filed in the Surveillance and Performance Monitoring (SPM) Module at (https://wawf.eb.mil) file for this contract.

5.4 Surveillance Documentation. Each months’ Completed Surveillance Documentation, to include the MSR must be filed in the Surveillance and Performance Monitoring (SPM) Module in PIEE at (https://wawf.eb.mil) for this contract.

6.0 Non-Conforming Performance. A Non-conformance occurs when the Contractor fails to meet the terms, conditions and/or specifications of the Contract/Task Order. All instances of non-conformance must be documented by the COR. The COR will provide the details of the non-conformance using Attachment 5, Contract Discrepancy Report (CDR), DA Form 5479, to the KO, who will notify the Contractor of each nonconformance occurrence, unless the KO has authorized the COR to submit directly to the contractor, and copy the KO. Resolution of any non-conformance discovered at the Subcontractor level will be addressed with the prime Contractor. Non-conformances are classified as either: Level I (Minor); Level II (Major); or Level III (Critical).

6.1 Level I (Minor). Level I non-conformance is not likely to materially reduce the usability of services for their intended purpose or is a departure from established standards having little bearing on completing the contract requirement. Minor non-conformances can usually be corrected on the spot and can be issued to the Contractor through either a verbal or written Contract Discrepancy Report (CDR). However, the Government is required to document verbal Level I CDRs. The COR may issue verbal Level I CDRs directly to the appropriate level of Contractor management. The COR will notify the KO as soon as practical when a verbal Level I CDR is issued and document them in their Monthly Reports. If the non-conformance cannot be corrected on the spot, the Contractor shall be given a suspense date to correct the deficiency. The KO will issue and sign written Level I CDRs, Attachment 5.

6.2 Level II (Major). Level II non-conformance is likely to result in failure of the services to meet contract requirements. Also, repeated discrepancies, a large number of documented Level I CDRs and trends indicating failure of the Contractor’s quality control program can be classified as Level II CDRs. The KO issues all Level II CDRs in writing, Attachment 5. The COR will notify the KO as soon as practical when a major non-conformance is identified.

6.3 Level III (Critical). Level III non-conformances result in hazardous or unsafe conditions due to the manner in which the services are performed; prevent or impact a vital agency mission as a result of performance; or are for repeated or uncorrected Level II CDRs. The Contracting Office Director or Deputy Director issues written Level III CDRs. The COR is responsible for notifying the KO immediately upon discovery of a critical non-conformance.

6.4 Documenting NCRs. The COR will provide the details of the non-conformance using Attachment 5, Contract Discrepancy Report, DA Form 5479. If the Requiring activity prefers to issue a locally developed CDR, documentation must include as a minimum: the Contract or Task Order number; reference to the specific contract requirement; the specific discrepancy to the requirement; where it was discovered; the date and time it was discovered; Contractor representative who was notified; and the suspense date for Contractor response/corrective action.

6.5 Tracking and Resolving NCRs. All CDRs, verbal and written, regardless of issuer will be included in the COR’s Monthly Report. The COR and KO shall track CDRs to ensure the Contractor identifies and takes appropriate corrective action to the root cause and the specific non-conformance is corrected within the required timeline. The KO will make a final written determination of the Government’s remedies if the non-conformance is not corrected by the Contractor after receiving notice and a reasonable opportunity to correct the work.

7.0 Deduct Plan. This acquisition does not include a Deduct Plan.

8.0 Data Analysis. Data Analysis will be performed to identify trends in cost, schedule and/or performance risks. The results of Data Analysis will be documented in COR MSR and may be used to make adjustments to surveillance schedules and/or checklist items to increase or decrease surveillance, based on performance trends. Negative trends noted using Government data/observations could result in issuing the Contractor a Contract Discrepancy Report. Trends noted using Contractor data will not result in a CDR unless the Contractor has not addressed the negative trend. QASP changes based on Data Analysis will be coordinated with the Contracting Officer for approval.

9.0 Acceptance of Services. When all services have been deemed acceptable and there is documented, objective, quality evidence to support acceptable performance, the COR will accept the services provided and authorize payment to the Contractor. Acceptance and payment will be made by approving the Contractor’s Receiving Reports in Wide Area Workflow at https://wawf.eb.mil/ as an iRAPT Inspector, and/or Acceptor.

10.0 COR Status Report. COR Status Reports, or MSR will be submitted on a monthly basis to the Contracting Officer via the Surveillance and Performance Monitoring (SPM) Module in PIEE CORT Tool. MSR reports must be uploaded into the CORT Tool, using the “Smart Form” monthly surveillance report. Monthly status reports will be due no later than (NLT) the 10th day of the month following the month of surveillance. COR Status Reports will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis must contain a summary of surveillances performed, Customer Feedback if any, CDRs if any, an analysis of the Contractors performance, recommended adjustments to surveillance schedules, and any other pertinent contract information IAW FAR 46.104, and the COR Appointment Letter. Completed Surveillance Checklists and CDRs, if any, will be included as attachments to COR Status Reports, or referenced in the MSR for that month and uploaded separately in the Miscellaneous Documents Section of the CORs’ Surveillance and Performance Monitoring (SPM) Module file for this contract. See para 4.2.

11.0 Contractor Manpower Reporting Application (CMRA). Reporting Labor Hours. The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report all Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address: https://www.ecmra.mil.

The required information includes the following:

a. Contracting Officer (KO), Contracting Officer’s Representative (COR) name;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data;

e. Estimated direct labor hours (including sub-Contractors);

f. Estimated direct labor dollars paid this reporting period (including sub-Contractors);

g. Total payments (including sub-Contractors);

h. Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different);

i. Estimated data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information);

k. Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment or contingency contract language; and Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country).

While inputs may be reported any time during the FY, The COR shall ensure the contractor submits all data shall no later than October 31 of each calendar year. The COR shall verify that the Contactor has complied with the required contractor manpower reporting annually and document the results in the Surveillance and Performance Monitoring (SPM) Module in PIEE CMRA section. Contracting officers shall ensure that the requirement to report contractor manpower is included in all contracts, task/delivery orders and modifications.

12.0 Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (COR Status Reports, Completed Surveillance Checklists, Customer Feedback and CDRs, if any) will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information.

13.0 Trafficking In Persons (CTIP). In accordance with DFARS PGI 222.17 and FAR 52.222-50, the KO will be notified immediately of any information from any source that alleges a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

14.0 COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance File will be maintained in the Surveillance and Performance Monitoring (SPM) Module in PIEE, IAW DODI 5000.72, and DFARS PGI 201.602-2.

15.0 QASP Changes. This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications by the KO, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

CANDACE N. LEWIS

1LT, MS

CONTRACTING OFFICER REPRESENTATIVE Date

KIRK HEYEN

Health Readiness Contracting Officer Contracting Officer’s Signature Block Date

Attachments:

1. Performance Requirements Summary (PRS), DA Form 5473

2. Customer Complaint Record, DA Form 5477

3. Surveillance Schedule, DA Form 5475

4. Surveillance Checklist(s)

5. Contract Discrepancy Report, DA Form 5479

6. Contract Discrepancy Log

7. List of Contractor Requirements

8. QASP Surveillance Item Requirements

DOCUMENT REVISION HISTORY

This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

1.0

Attachment 1 Performance Requirements Summary

Contractor shall provide properly trained, qualified, and certified personnel.

inspection

Contractor shall maintain key personnel.

inspection

Contractor shall participate in leadership meetings.

Contractor shall provide timely support to unit Master Fitness Trainers (MFT) and Master Resilience Trainers (MRT)

Contractor shall conduct in-person education for Pilot A units.

100% inspection

Contractor shall provide H2F web based training materials.

Contractor shall provide periodized physical readiness training programs that align with FM 7-22.

inspection

Contractor shall abide by all HIPPA requirements.

Attachment 2 Customer Complaint Record, DA Form 5477

Attachment 3 Surveillance Schedule, DA Form 5475

You will need to develop a monthly schedule for conducting surveillance. You can use this form. The date you are going to conduct surveillance would go in the far left column. You would list the PWS, paragraph number for the task you are going to surveil on the top line.

Attachment 4 Surveillance Checklist(s)

H2F COR SURVEILLANCE CHECKLIST

COR Name:

1. Did the contractor provide all personnel, transportation, and supervision to perform H2F education, services, and training as defined in this Performance Work Statement?

PWS 1.1

Comments:

2. Did the contractor shall perform to the standards in this contract?

PWS 1.1

Comments:

3. Did the contractor develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS?

PWS 1.6.1

Comments:

4. Did the contractor develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services?

Comments:

5. Did the Contractor provide their final written Quality Control Plan QCP no later than (NLT) thirty (30) days after contract award?

Comments:

6. Did the Contractor submit QCP changes within five (5) days to the KO and Contracting Officer’s Representative (COR) for review and approval prior to implementation?

Comments:

7. Did the Contractor provide Human Performance Advisor (HPA) services Monday through Friday, normally between the hours of 8:00 AM to 5:00 PM, except federal holidays or when the government facility is closed for administrative reasons? During in-person education days, was the Contractor available between the hours of 7:00 AM to 5:00 PM?

PWS 1.10

Comments:

8. Did the Contractor personnel performing work under this contract have the appropriate clearance/training at time of the proposal submission, and maintain the level of security required for the life of the contract? PWS 1.16

Comments:

9. Did the Contractor safeguard all government equipment, information and property provided for contractor use?

PWS 1.13

Comments:

10. Did the Contractor establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government were not lost or misplaced and were not used by unauthorized persons? In the event keys, other than master keys, are lost or duplicated, did the Contractor upon direction of the Contracting Officer, re-key or replace the affected lock or locks?

PWS 1.14, 1.14.1

Comments:

11. Did the Contractor prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees?

PWS 1.14.2

Comments:

12. Did the Contractor establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons?

PWS 1.15

Comments:

13. Did the Contractor employees complete Level I OPSEC Awareness training? New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

PWS 1.16

Comments:

14. Are All Contractor employees US Citizens or legal US residents and did all Contractor personnel , at a minimum, have an Interim SECRET Security Clearance upon start of performance, and have a finalized SECRET Security Clearance within 120 days of the start of full performance from the Defense Industrial Security Clearance Office? Contractor must maintain the level of security required for the life of the contract. PWS 1.17

Comments:

15. Did the Contractor ensure all employees possess and maintain a current Information Assurance Technician (IAT) Level I or Level II or Level III professional certification, depending on their duties as defined in DoDI 8570.01 and other DoDI guidance as required during the execution of this contract?

PWS 1.19

Comments:

16. Did all Contractor employees and associated Sub-Contractor employees complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter?

PWS 1.19

Comments:

17. Did the Contractor ensure all personnel performing work under this contract possess and maintain specified qualifications during the execution of this contract?

PWS 1.18

Comments:

18. Did the Contractor attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5?

PWS 1.35

Comments:

19. Did the Contractor obtain written permission from the Contracting Officer to add or remove key personnel?

PWS 1.14

Comments:

20. Did the Contractor submit a list of individuals(s) identified as key personnel to the KO and COR within fifteen (15) days of contract award? Any changes to the working status of these key personnel shall be transmitted (in writing) to the KO and COR within ten (10) work days of the proposed change.

PWS 1.29

Comments:

21. Did the Contractor replace key personnel in a timely manner and with qualifications equal to or better than that of the original employee?

Comments:

22. Did the Contractor ensure all key personnel terminated or released from employment under this contract are replaced within ten (10) work days of their removal?

Comments:

23. Did the HPA take responsibility for the performance of the work under this contract?

PWS 1.30

Comments:

24. Did all contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials?

PWS 1.31

Comments:

25. Are all Contractor personnel capable of travel?

PWS 1.32

Comments:

26. Did the Contractor obtain written pre-approval from the COR prior to travel that incurred actual expenses resulting from long distance travel?

Comments:

27. Did the Contractor produce a long distance travel request template, local travel log template, and a long distance trip report template? The templates shall be submitted to the COR within ten (10) days after contract award for approval.

PWS 1.32.1

Comments:

28. Did the Local Travel Log template include, at a minimum: Name, duty position, reason for travel, key personnel assisted (name, position, and phone number), significant activities accomplished during visit, follow-up requirements, recommendations/comments and signature block?

PWS 1.32.2

Comments:

29. Were Long Distance Trip Reports provided to COR within five (5) work days after travel has been completed? This report shall be submitted on the approved template and provide a synopsis of accomplishments performed during the travel period.

PWS 1.32.3

Comments:

30. Did the Contractor submit monthly invoices for reimbursement citing the appropriate Contract Line Item Number (CLIN)? Each individual travel instance must be captured; copies of receipts, travel vouchers, etc. shall be attached to the invoice to support charges.

Comments:

31. Did the Contractor maintain original receipts and make available to Government auditors upon request? PWS 1.32.3

Comments:

32. Did he long distance trip report include at a minimum: Travelers name, position, reason for travel, mode of travel, duration of travel, destinations, purpose / scope, organization visited, key personnel assisted (name, position, and phone number), significant activities accomplished, discussion background, concerns / issues, follow- up requirements, recommendations / comments, conclusion, and signature block?

Comments:

33. Did the Contractor provide all data and materials produced under the performance of this contract to US Government as provided for in the relevant contract clauses?

Comments:

34. Did the Contractor obtain express written permission from the KO to use any information generated through actions in support of the USAR H2F Pilot Program in forums outside of the requirements of this PWS and subsequent TOs?

Comments:

35. Did the Contractor shall provide written justification to the KO requesting the release of information outside of the USAR H2F Program not less than 30 days prior to expected release date? The request shall include type of information to be released, intended audience, and methods to be used in safeguarding Government and protected personal information.

Comments:

36 Did the Contractor notify the Contracting Officer immediately whenever it become aware that an organizational conflict of interest existed and promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI?

PWS 1.21

Comments:

37. The Contractor shall have personnel on board, during the thirty (30) phase in-period to minimize any decreases in productivity and to prevent possible negative impacts on additional services.

PWS 1.38

Comments:

38. Did the Contractor obtain their CAC or other forms of government identifications, any specific government training, conducting inventory and transfer of GFP/GFE during the phase-in period?

PWS 1.38

Comments:

39. Are the Contractor personnel performing work under this contract able to read, write, speak, and understand the English language to effectively carry out all contract requirements?

PWS 1.29.1

Comments:

40. Did the Contractor furnish all services required to perform work under this contract that are not listed under Section 3 of this PWS?

PWS 4.1

Comments:

41. Did Contract personnel engage with Soldiers within two target populations, Pilot A and Pilot B, in order to improve physical / mental readiness outcomes?

PWS 5.1

Comments:

42. Did the contractor provide one full-time HPA, in-person education delivered by a part-time H2F Team to include a physical therapist, occupational therapist, dietitian, strength and conditioning coach, and mental performance expert during UTA, and access to a Smart phone-based mobile application strength and conditioning platform?

PWS 5.1.2

Comments:

43. Did the contractor conduct 9 session (90 mintues each) of in-person education (i.e., 9x/year) for all Pilot A units?

PWS 5.1.2.1

Comments:

44. Were the in-person education dates agreed upon by USARC H2F Program Manager and the contractor at a minimum of 45 days in advance?

Comments:

45. Did the contractor synchronize with unit leaders in order to maintain a student to trainer ratio of 50:1 for in-person education?

Comments:

46. In-person education shall be delivered using a rotational model for module instruction by each H2F Team member in accordance with an outline of topics provided by the Government.

Comments:

47. Did the contractor coordinate with unit leaders and unit MFT and MRT in order to schedule break-out sessions for physical training and resilience training on BA weekend when the in-person education was delivered?

Comments:

48. Did the HPA and USARC H2F Program Manager conduct a face to face meeting at least 14 days prior to the execution of In-person Education to finalize all coordination requirements and to ensure all portions of the program meet requirements?

PWS 5.1.2.2

Comments:

49. Did Pilot B units receive web based information and reach back support for unit MFT and MRT from the HPA?

PWS 5.1.3

Comments:

50. Did the HPA implement, document, and provide oversight of all H2F services and provide ongoing, objective feedback to the USAR H2F Program Manager and chain of command in accordance with the Performance Requirements Summary (PRS) and Deliverables Schedule (DS)?

PWS 5.2.1

Comments:

51. Did the HPA coordinate with 81 RD staff, unit leaders, and contracted personnel to schedule and conduct H2F in-person education for Pilot A units?

PWS 5.2.2

Comments:

52. Did the HPA coordinate with unit leaders, staff, MFT and MRT in order to schedule and facilitate on-site physical readiness training and resilience training in unison with in-person education by contracted H2F Team? PWS 5.2.3

Comments:

53. Did the HPA plan, create, and administer scientific-based, periodized physical training programs/protocols for unit Soldiers designed to maximize physical performance and reduce the risk of musculoskeletal injuries for use and dissemination on a Smart phone-based mobile application and website? Training program(s) will include quantified training loads (total and for the following individual components of fitness: strength, power, agility, cardiovascular endurance, and muscular endurance.

PWS 5.2.4

Comments:

54. Did the HPA provide appropriate training protocols for Soldiers in garrison, on TDY status, and deployed?

PWS 5.2.5

Comments:

55. Did the HPA demonstrate and provide instruction and guidance on physical training, exercises, movements, and injury avoidance?

PWS 5.2.6

Comments:

56. Did the HPA coordinate with Troop Program Unit (TPU) H2F Team to develop, coordinate, and execute approved training programs for Soldiers with physical limitations that are medically cleared for strength and conditioning training/reconditioning?

PWS 5.2.7

Comments:

57. Did the HPA provide reach back capability for unit MFT and MRT to seek out advice and assistance in accordance with the PRS?

PWS 5.2.9

Comments:

58. Did the HPA initiate, organize, and participate in periodic virtual meetings with unit MFT to review and evaluate physical training programs and identify opportunities for improvement?

PWS 5.2.10

Comments:

59. Did the HPA develop and promulgate monthly training materials to include hand-outs, Power Point presentations, templates, and video for storage on a government H2F All Partners Access Network (APAN)? PWS 5.2.11

Comments:

60. Did the HPA coordinate with USARC H2F Program Manager, TPU H2F Team, Camp Parks R2 Performance Center Site Manager, and unit MFT and MRT to develop and store web based information on APAN site?

PWS 5.2.12

Comments:

61. Did the HPA collect and report all data in accordance with the DS?

PWS 5.2.13

Comments:

62. Did the HPA produce information papers, reports, or presentations in accordance with the DS?

PWS 5.2.14

Comments:

63. Did the HPA attend and participate in meetings with unit staff, 81 RD leadership, and USARC H2F Program Manager?

PWS 5.2.15

Comments:

64. Did the HPA maintain knowledge of current Army standards and regulations related to the Army Combat Fitness Test, FM 7-22 Holistic Health and Fitness, Resiliency Training and Comprehensive Soldier and Fitness (CSF2), and Total Force Fitness (TFF) Policy?

PWS 5.2.16

Comments:

65. Did the HPA communicate with the U.S. Army Research Institute of Environmental Medicine (USARIEM), and U.S. Army Public Health Center (APHC) in order to facilitate external evaluations related to outcome measures and scalability as requested?

PWS 5.2.17

Comments:

66. Did the Contractor report ALL Service Contract Reporting (including subcontractor manpower) required for performance of this contract?

PWS 5.3

Comments:

67. Did the Contractor attend any post award conference convened by the KO in accordance with FAR Subpart 42.503?

PWS 1.35

Comments:

68. Did the Contractor abide by all applicable regulations, publications, manuals, and local policies and procedures?

PWS 6.1

Comments:

The COR will develop a monthly Checklist for conducting surveillance. The COR may use either of the forms attached. The COR will list the PWS requirements that ARE NOT listed as PRS requirements in the PWS as a pool of surveillance items for each month of surveillance activity you conduct. See Attachment 7, List of Contractor Requirements. Each month, select the performance requirements you will evaluate from that list.

Attachment 5 Contract Discrepancy Report, DA Form 5479

Attachment 6 Contract Discrepancy Log

Attachment 7 List of Contractor Requirements

Attachment 8 QASP Surveillance Item Requirements image1.emf image2.emf

DA 5473 PRS .pdf

PERFORMANCE REQUIREMENTS SUMMARY

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

REQUIRED

SERVICE

PARAGRAPH

NUMBER STANDARD

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM REQUIREMENT (AQL)

METHOD OF

SURVEILLANCE

THE PROPORTION

OF REQUIRED

SERVICE TO TOTAL

CONTRACT PRICE

DA FORM 5473, MAR 2008 APD LC v1.00PREVIOUS EDITIONS ARE OBSOLETE.

PERFORMANCE REQUIREMENTS SUMMARY

REQUIRED

SERVICE

PARAGRAPH

NUMBER

STANDARD

MAXIMUM ALLOWABLE

DEGREE OF DEVIATION

FROM REQUIREMENT (AQL)

METHOD OF

SURVEILLANCE

THE PROPORTION

OF REQUIRED

SERVICE TO TOTAL

CONTRACT PRICE

DA FORM 5473, MAR 2008

APD LC v1.00

PREVIOUS EDITIONS ARE OBSOLETE.

1.00

DA FORM 5473-R, NOV 1985

PERFORMANCE REQUIREMENTS SUMMARY

APD

REQ_SERV:

REQ_SERV_1:

REQ_SERV_2:

REQ_SERV_3:

REQ_SERV_4:

REQ_SERV_5:

REQ_SERV_6:

REQ_SERV_7:

REQ_SERV_8:

REQ_SERV_9:

REQ_SERV_10:

PARAGRAF:

PARAGRAF_1:

PARAGRAF_2:

PARAGRAF_3:

PARAGRAF_4:

PARAGRAF_5:

PARAGRAF_6:

PARAGRAF_7:

PARAGRAF_8:

PARAGRAF_9:

PARAGRAF_10:

STANDARD:

STANDARD_1:

STANDARD_2:

STANDARD_3:

STANDARD_4:

STANDARD_5:

STANDARD_6:

STANDARD_7:

STANDARD_8:

STANDARD_9:

STANDARD_10:

AQL:

AQL_1:

AQL_2:

AQL_3:

AQL_4:

AQL_5:

AQL_6:

AQL_7:

AQL_8:

AQL_9:

AQL_10:

METHOD:

METHOD_1:

METHOD_2:

METHOD_3:

METHOD_4:

METHOD_5:

METHOD_6:

METHOD_7:

METHOD_8:

METHOD_9:

METHOD_10:

PROPORTN:

PROPORTN_1:

PROPORTN_2:

PROPORTN_3:

PROPORTN_4:

PROPORTN_5:

PROPORTN_6:

PROPORTN_7:

PROPORTN_8:

PROPORTN_9:

PROPORTN_10:

image3.emf

DATE OF COMPLAINT TIME OF COMPLAINT

NATURE OF COMPLAINT

CONTRACT REFERENCE

VALIDATION

DATE CONTRACTOR INFORMED COMPLAINT TIME CONTRACTOR INFORMED OF COMPLAINT

ACTION TAKEN BY CONTRACTOR (Responsible officer)

RECEIVED AND VALIDATED BY

ORGANIZATION

INDIVIDUAL

NOTE: ( ) Used for in-house operation.

CUSTOMER COMPLAINT RECORD

SOURCE OF COMPLAINT

(Responsible officer) (Responsible officer)

DA FORM 5477, MAR 2008 PREVIOUS EDITIONS ARE OBSOLETE. APD PE v1.01ES initiator:ralph.gaines@us.army.mil;wfState:distributed;wfType:email;workflowId:b71742b09d8a4c49a6eb59ab36d6e236

DATE OF COMPLAINT:

TIME OF COMPLAINT:

ORGANIZATION INDIVIDUAL SOURCE OF COMPLAINT:

NATURE OF COMPLAINT:

CONTRACT REFERENCE:

VALIDATION:

DATE CONTRACTOR INFORMED COMPLAINT Responsible officer:

TIME CONTRACTOR INFORMED OF COMPLAINT Responsible officer:

ACTION TAKEN BY CONTRACTOR Responsible officer:

RECEIVED AND VALIDATED BY:

NOTE Used for inhouse operation:

undefined: Off

Text2:

SubmitButton1:

image4.emf

DA FORM 5477

DATE OF COMPLAINT TIME OF COMPLAINT

NATURE OF COMPLAINT

CONTRACT REFERENCE

VALIDATION

DATE CONTRACTOR INFORMED COMPLAINT TIME CONTRACTOR INFORMED OF COMPLAINT

ACTION TAKEN BY CONTRACTOR (Responsible officer)

RECEIVED AND VALIDATED BY

ORGANIZATION

INDIVIDUAL

NOTE: ( ) Used for in-house operation.

CUSTOMER COMPLAINT RECORD

SOURCE OF COMPLAINT

(Responsible officer) (Responsible officer)

DA FORM 5477, MAR 2008 PREVIOUS EDITIONS ARE OBSOLETE. APD PE v1.01ES initiator:ralph.gaines@us.army.mil;wfState:distributed;wfType:email;workflowId:b71742b09d8a4c49a6eb59ab36d6e236

DATE OF COMPLAINT:

TIME OF COMPLAINT:

ORGANIZATION INDIVIDUAL SOURCE OF COMPLAINT:

NATURE OF COMPLAINT:

CONTRACT REFERENCE:

VALIDATION:

DATE CONTRACTOR INFORMED COMPLAINT Responsible officer:

TIME CONTRACTOR INFORMED OF COMPLAINT Responsible officer:

ACTION TAKEN BY CONTRACTOR Responsible officer:

RECEIVED AND VALIDATED BY:

NOTE Used for inhouse operation:

undefined: Off

Text2:

SubmitButton1:

image5.emf

DATE

COR/QAE SURVEILLANCE SCHEDULE

When completed stamp "FOR OFFICIAL USE ONLY"

DA FORM 5475, MAR 2008 APD PE v1.00

PREVIOUS EDITIONS ARE OBSOLETE.

image6.emf

DA FORM 5475

COR/QAE SURVEILLANCE SCHEDULE

When completed stamp "FOR OFFICIAL USE ONLY"

DA FORM 5475, MAR 2008 APD PE v1.00 image7.emf

DA 5476 Surv Checklist.pdf

CONTRACT

REQUIREMENT

PARAGRAPH

NUMBER

METHOD OF

SURVEILLANCE

ACCOMPLISHED

WHERE

ACCOMPLISHED

COMPLIANCE

SURVEILLANCE ACTIVITY CHECKLIST

DA FORM 5476, MAR 2008 APD LC v1.00PREVIOUS EDITIONS ARE OBSOLETE.

REQUIREMENT

CONTRACT

PARAGRAPH

NUMBER

METHOD OF

SURVEILLANCE

DATE

ACCOMPLISHED

WHERE

ACCOMPLISHED

COMPLIANCE

SURVEILLANCE ACTIVITY CHECKLIST

For use of this form, see DA PAM 5-20; the proponent agency is ACSIM.

DA FORM 5476, MAR 2008

APD LC v1.00

PREVIOUS EDITIONS ARE OBSOLETE.

1.00

DA FORM 5476-R,…