Attachment 1-PWS Medical Courier Final FY25..pdf
PDF 465 KB Posted
- Attached to
- Medical Courier Services-Andersen AFB, Guam
- Solicitation number
- HT941025Q2006
- Issued by
-
Defense Health Agency
About this file
This file is a Performance Work Statement (PWS) for medical courier services at the 36th Medical Group, Andersen Air Force Base in Guam. The contractor will provide daily transportation of medical samples, supplies, pharmaceuticals, and optical items between the 36th Medical Group clinic and the US Naval Hospital Guam.
The period of performance is April 1, 2025 to March 31, 2026 with four 12-month options. Key service requirements include daily pickups from 36th MDG no later than 0830 hours, delivery to USNH Guam by 1200 hours, and return deliveries to 36th MDG by 1330 hours, with additional Friday evening pickups required. The contractor must comply with HIPAA requirements, provide proper training for handling medical/biological samples, maintain proper temperature controls during transport, and assume liability for all items during transit. The contractor is required to operate Monday through Friday except federal holidays, following the medical facilities' standard hours of operation, and must submit a Quality Control Plan within 30 days of contract award.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Questions and Answers.docx | DOCX document | |
| Attachment 2 - Past Performance Questionnaire.docx | DOCX document | |
| Combined Synopsis Solicitation - HT941025Q2006..pdf | ||
| Attachment 3 - Quote Sheet.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Department of Defense Defense Health Agency
Performance Work Statement
Medical Courier Services
36th Medical Group, Andersen AFB, Guam
[Division, Branch, or Program Executive Office Title]
Solicitation Number:
Version:
Date: 4/1/2024
NOTE TO OUR CUSTOMERS: THIS TEMPLATE MUST BE TAILORED BY
INCLUDING YOUR UNIQUE REQUIREMENTS (SEE PART 5), QUANTITIES FOR
WORKLOAD, SPECIFIC SURVEILLANCE TECHNIQUES, ETC. ANY QUESTIONS
REGARDING THIS TEMPLATE SHOULD BE ADDRESSED WITH YOUR ASSIGNED
ACQUISITION TEAM. GENERAL INFORMATION IS PRESENTED IN BLUE
ITALICS WITH PARENTHESIS BORDERS, WHILE FILL-IN GUIDANCE IS
PRESENTED IN BLUE WITH BLACK BRACKET BORDERS. PLEASE DELETE ALL
BLUE ITALICS AND BLUE NON-ITALICS WHEN FINALIZING THE PWS.
TEMPLATE PWS WILL BE USED FOR DEFENSE HEALTH AGENCY (DHA) D AND
R SERVICE REQUIREMENTS WHEN EXECUTED BY DHA CONTRACTING
OFFICERS (CO).
THIS INSTRUCTIONAL BLOCK SHOULD BE DELETED PRIOR TO FINALIZING
YOUR PWS.
PART 1
1.0 GENERAL INFORMATION
1.1 This is a non-personal services contract to provide Medical Courier Services.
1.2 Description of services/introduction: The 36th Medical Group (MDG) is located at Andersen AFB, the northern most point of Guam. The 36th MDG primary mission is to provide top quality care to our active-duty military and their families while maintaining combat ready medics, a fit force, and healthy families. We strive to maximize readiness, strengthen, and build partnerships, develop Airmen, prepare today for the fight tomorrow, and promote a healthy population. The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Medical Courier services as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services. The contractor shall perform to the standards in this PWS.
1.3 Background: The contractor will be required to provided transportation services to and from 36 MDG clinic to naval hospital on a daily basis providing professional and too quality service by ensuring medical items are in proper compliance with the regulations and meet the standards of temperature/ climate, and environment conditions to and from 36 MDG and vise versa.
1.4 Objectives: To procure medical courier services under the DHA strategic sourcing program.
1.5 Scope: The Contactor shall provide medical courier services at 36th Medical Group (MDG) Andersen AFB. Services consist of delivery of medical samples, supplies, pharmaceuticals, optics (prescription glasses, etc.) to and from 36th MDG Andersen AFB to US Naval Hospital (USNH) Guam on a daily basis unless otherwise set forth in this PWS. The contractor shall supply all necessary equipment and labor required to perform services for military treatment facilities (MTFs). Additionally, the contractor monitors, manages and reports on services for higher management and develops plans to improve timeliness and accuracy rates, service availability, and overall MTF performance and compliance.
1.6 Period of Performance (PoP): This period of performance for this task order is from 01 APR 2025 – 31 MAR 2026 with four 12-month options; the contractor has 30 calendar days from task order award to initially fill the positions. Workers performing on this task order shall start on 15 May 2025 to avoid any break in service. An earlier worker start date is possible if a mutual agreement between the Government and awarded contractor can be established at no additional cost to the Government.
Base Period: 01 April 2025 – 30 March 2026
1.6.1 Transition: Transition-in/transition-out period N/A
1.6.1.1 Transition-in period: Full performance start date is, 01April 2025. Transition-in performance is defined as contractor is fully operational and able to perform the services detail in the PWS. During the transition-in period, the contractor shall prepare to meet all contract requirements and ensure incoming personnel are functionally trained and qualified on the full performance start date except cybersecurity requirements, which must be fully adhered during transition and full performance periods. The remaining incoming personnel shall be trained and qualified within 30 days after contract award.
1.6.1.1.1 The contractor shall comply with transition-in requirements of the DHA, as listed in paragraph 1.11.1, for contractors needing to be issued Common Access Card (CAC) identification, including Department of Defense (DoD) and DHA-directed training and forms submission, prior to network access.
1.6.1.2 Transition-out period: The transition-out plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming contractor/Government personnel at the expiration of the contract. See Part 7, Technical Exhibit 1.
1.6.1.2.1 The contractor shall comply with transition-out requirements of the DHA for contractors who have been issued a CAC or who generate “records”, as defined by DoD (records manual), including DoD-directed disposition of records, and others displayed on the In/Out (I/O) Processing Portal.
1.7 Administrative specifications
1.7.1 Place of performance: The work shall be performed at 36th Medical Group, Building 26012, Carolines Avenue, Andersen AFB Guam.
1.7.2 Recognized Federal holidays: The Contractor is NOT required to perform services on the following recognized federal holidays:
New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Juneteenth Day Christmas Day Independence Day
1.7.3 Hours of operation: The contractor is responsible for conducting business Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.
Hours of operation Hospital Clinics: Monday-Thursday 8 a.m. to 4 p.m.
Training every 2nd Wednesday of each month 7:30 a.m. to 4:30 p.m. – Clinic Closed
Main Outpatient Pharmacy: Monday-Friday 7:30 a.m. to 4:30 p.m. – Closed Holidays Laboratory: Monday-Thursday 7 a.m. to 5:30 p.m.; Fridays 7 a.m. to 5 p.m. – Closed Holidays
1.7.4 Emergency Services:. On occasion, services may be required to support an activation or exercise of contingency plans outside the normal duty hours.
1.8 Contractor travel: Reserved – N/A
1.9 Other Direct Costs (ODC): Reserved – N/A.
1.10 Quality
1.10.1 Quality Control (QC): (If applicable) The contractor shall develop and maintain an effective QC program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure nonrecurrence of defective services. The contractor’s QC program is the means by which the work complies with stated requirements. The contractor shall submit Quality Control Plan (QCP) within 30 days after contract award, a comprehensive written via microsoft word or adobe pdf QCP shall be submitted to the CO and COR; if changes are made to the QCP, the contractor has 5 working days to submit the revised plan to the CO and COR. After acceptance of the Quality Control Plan (QCP) the contractor shall receive the CO’s acceptance in writing of any proposed change to his QC system. See Part 7, Technical Exhibit 1 - CDRL A001.
1.10.2 Quality assurance (QA): The government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan provides a systematic method for the Government to evaluate performance and to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).
1.11 Contractor personnel
1.11.1 CAC requirements: For all contractors who will work in Government facilities, the Facilities Security Officer (FSO)/Company's Security point of contact (POC) will provide the Government all the required information per the DHA CAC request process current version 2.1, January 2018, or more recent when updated. See process attached at Part 7 Section 7.1.1 of the PWS. A CAC is the standard identification for eligible DoD contractor personnel.
1.11.1.1 The contractor shall return all CACs to the COR upon the departure of the contractor(s).
1.11.2 Contractor onboarding and training. The contractor shall complete all requirements, training, and forms as prescribed in the following requirements:
1.11.2.1 The DHA’s “Onboarding Checklist for Contractor Employees” is located at the DHA Onboarding and Offboarding Portal at https://info.health.mil/cos/admin/hr/IO/SitePages/Home.aspx
1.11.2.2 The DHA’s contractor training instructions embedded at Part 7 Section 7.1.2.
1.11.2.3 The contractor shall comply with onboarding requirements of the DHA for contractors needing to be issued CAC identification, including DoD- and DHA-directed training and forms submission, prior to network access, as displayed in the In/Out-Processing Portal at:
https://info.health.mil/cos/admin/hr/IO/SitePages/home.aspx (note: Public Key Infrastructure (PKI)-restricted, printed versions available).
1.11.2.4 Contractor shall comply with all federal and local guidelines to transport medical items, included but not limited to medical records, biological specimens, and pharmaceuticals.
1.11.2.5 Contractor shall ensure employee adherence to the Health Insurance Portability and Accountability Act (HIPAA).
1.11.2.6 Contractor shall provide all necessary training for employees concerning transport of medical/biological samples and supplies.
1.11.2.7 Contractor shall provide training to all employees concerning proper biohazard spill clean-up in the event of a specimen leakage. NOTE: specimens are prepared for transport by facility medical technicians to minimize spill occurrence.
1.11.2.8 Liability: The contractor shall be liable for any damages resulting from any carelessness or failure to follow proper safety, installation, engineering, or maintenance procedures and standards. The contractor shall provide point of contact (POC) for all contractual matters during all hours of operation. The POC shall respond on-site within 1 hour during normal duty hours of operation and within 2 hours during non-duty hours to discuss concerns with government personnel designated by the CO to discuss problem areas.
1.11.3 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.
1.11.4 Reserved – N/A
1.11.5 Lock combinations: Reserved – N/A
1.12 Key personnel (Contractor): Reserved - N/A
1.13 Data rights: Reserved – N/A.
1.14 Reporting Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified/unclassified defense information. Employees shall be briefed by their immediate supervisor upon initial on-base assignment.
https://info.health.mil/cos/admin/hr/IO/SitePages/Home.aspx https://info.health.mil/cos/admin/hr/IO/SitePages/home.aspx
1.14.1 Contractor Manpower Reporting (CMR): RESERVED.
1.14.2 Non-Disclosure Agreement (NDA): (If applicable) All contractor personnel who will obtain access to proprietary, classified, or confidential information or any information release of which is protected or governed by law or regulation associated with DHA acquisitions shall be required to complete and sign a DHA contractor NDA (DHA Form 49) prior to beginning work on the subject contract. The contractor shall execute an NDA on behalf of the company and shall ensure that all staff assigned to, including all subcontractors and consultants, or other personnel performing on contract/Task order execute an NDA protecting the procurement sensitive information of the Government and the proprietary information of other contractors. The NDA shall be executed not later than first day of employment and to be renewed upon exercising a contract option period. Assignment of staff who has not executed this statement or failure to adhere to this statement shall constitute default on the part of the contractor. The contractor shall maintain originally signed NDAs of individual employees and provide copy to the COR.
1.14.3 Government’s COR: The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: 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 aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor contractor's performance and notifies both the CO and contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of contractor personnel. 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 or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.
1.14.4
1.15 Contractor Identification
1.15.1 Contractor personnel performing services in a contractor capacity in a Government facility are required to possess and wear an identification badge that displays his or her name and the name of their company. All contractor personnel shall identify themselves as contractor support personnel in all forms of communication with all entities with whom DHA/Deputy Assistant Director for Acquisition (DAD-A)/Head of the Contracting Activity (HCA) has business dealings. The contractor shall: Answer all telephone calls and have a personalized voice message with an introductory statement that includes the fact that the person is contractor support personnel. Ensure all those with whom the person interacts in any face-to-face dealings while supporting the DAD-A understands that the person is contractor support personnel.
Include a title block in all emails that states the fact that the person is contractor support personnel. Ensure all those with whom the person interacts in any face-to-face dealings while supporting DHA/DAD-A/HCA understands that the person is contractor support personnel.
1.15.2 Contractor personnel will be required to attend meetings or otherwise communicate with Government and/or other contract representatives to meet the requirements of this order.
Contractor personnel shall make their contractor status known during introductions.
1.15.3 Contractor personnel, while performing in a contractor capacity, are prohibited from using their retired or reserve component military rank or title in any written or verbal communications associated with the contracts in which they provide services.
1.16 Contractor Access to Health Affairs (HA)/DHA Network(s)
1.16.1 FSO/Company's Security POC shall notify the DHA Personnel Security Office after being awarded a contract that requires access to a DoD system (If applicable, if not delete 1.16.1 and 1.16.2 and replace to 1.16 Reserved). Contractor personnel requiring access to the HA/DHA networks for performance of their tasks require a background investigation and the security awareness training. The contractor shall be prepared for this process as it could take two (2) or more weeks. The FSO/Security POC shall submit a Standard Form (SF) 85/86 to DHA's Personnel Security Office for a background investigation.
1.16.2 Company's FSO/Security POC must notify the Personnel Security Office when the contractor has submitted the SF-85/86. The FSO/Security POC, or the COR must notify the DHA Personnel Security Office in writing of a contractor's termination from the contract, including the termination date.
1.17 Personnel Security
1.17.1 The contractor shall comply with DoD 8570.01-M, “Information Assurance Workforce Improvement Program, CH4” November 10, 2015 as amended; 8500.01, “Cybersecurity”, dated March 14, 2014; DoD Manual (DoDM) 6025.18, “Implementation of the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule Compliance in DoD Health Care Programs” dated March 3, 2019, Department of Defense Instruction (DoDI) 6025.18 “HIPAA Privacy Rule Compliance in DoD Health Care Programs”, dated March 13, 2019; and DoDM
5200.02 “Procedures for the DoD Personnel Security Program (PSP),” incorporation change 3, effective September 24, 2020. Contractor responsibilities for ensuring personnel security include, but are not limited to, meeting the following requirements:
1.17.1.1 Follow the DHA Personnel Security Office guidelines for submittal of security clearances. Contact the DHA Personnel Security Office for guidance on the appropriate background investigation required for personnel on the contract. The DHA Personnel Security Office can be reached at (703) 275-6038.
1.17.1.2 Initiate, maintain, and document personnel security investigations appropriate to the individual’s responsibilities and required access to Controlled Unclassified Information (CUI).
1.17.1.3 DHA Personnel Security Office does not deny any access to any automated information system (AIS), network, or Controlled Unclassified Information (CUI). If a contractor receives an unfavorable background investigation, the request for access will be sent back to the FSO for further action. Any unfavorable adjudication will result in DHA Personnel Security Office not signing off on any access request.
SECURITY
1.17.1.4 Pass and Identification Items: The contractor shall ensure the pass and identification items required for contract performance are obtained for employees.
1.17.1.5 Retrieving Identification Media: The contractor shall return all identification media and/or visitor passes from employees who depart for any reason before the contract expires; i.e.
terminated for cause, reassignment, retirement, etc.
1.17.1.6 Traffic Laws: The contractor and its employees shall comply with base traffic regulations. Traffic regulations include, but are not limited to:
1.17.1.6.1 Employees shall wear seatbelts when operating or riding in any vehicle (military, company or private owned) while on installation.
1.17.1.6.2 Speed limits on Andersen AFB are 25 MPH unless otherwise posted. Be aware of reduced speed limits and exercise caution when driving in base housing and school zones.
1.17.1.6.3 All vehicle operators on the installation shall not use cell phones unless the vehicle is safely parked or they are using a 100% hands free device. The wearing of any other portable headphones, earphones or other listening devices while operating a motor vehicle is prohibited.
1.17.1.7 Weapons, Firearms, and Ammunition: Employees are prohibited from possessing weapons, firearms, or ammunition on themselves or within vehicles (military, contractor-owned, or privately owned) while on Andersen AFB.
1.17.1.8 For Officail Use Only (FOUO): The contractor shall comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.
1.17.1.9 Military Exercises: No compensation shall be claimed for any delays resulting from re-entry procedures due to exercises.
PART 2
2.0 DEFINITIONS, ACRONYMS, AND APPLICABLE
PUBLICATIONS/INSTRUCTIONS
2.1 Definitions:
2.1.1 Category D: Information Technology (IT) and Telecommunications Services (called D- Services)
2.1.2 Category R: Support (Professional/Administrative/Management) Services (called R- Services)
2.1.3 Contracting Officer (CO): A person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings.
2.1.4 Contracting Officer’s Representative (COR): An individual, including a contracting officer’s technical representative (COTR), designated and authorized in writing by the CO to perform specific technical or administrative functions. This individual does NOT have authority to change the terms and conditions of the contract.
2.1.5 Nonpersonal services contract: a contract under which the personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the Government and its employees.
2.1.6 Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance. The Government may either prepare the QASP or require the offerors to submit a proposed quality assurance surveillance plan for the Government’s consideration in development of the Government’s plan.
2.2 Acronyms: (List all acronyms used in the PWS and what they represent. At a minimum, insert the acronyms provided below).
AIS Automated Information System APL Approved Products List APL AQL Acceptable Quality Level ARRT Acquisition Requirements Roadmap Tool ATO Authority to Operate B2B Business-2-Business CAC Common Access Card CAP Cloud Access Point CCEVS Common Criteria Cybersecurity Evaluation and Validation Scheme CDI Covered Defense Information
CE Computer Environment CDRL Contract Data Requirement List CIO Chief Information Officer CJCSM Chairman of the Joint Chiefs of Staff Manual CMMC Cybersecurity Maturity Model Certification CMR Contractor Manpower Reporting CNSSI Committee on National Security Systems Instruction CO Contracting Officer(s) CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative CSP Cloud Service Provider CSSP Cyber Security Service Provider CUI Controlled Unclassified Information DAD-A Deputy Assistant Director for Acquisition DC3 DoD Cyber Crime Center DD Form 254 Department of Defense Contract Security Requirement List (if applicable) DB Design-Build DBB Design-Bid-Build DFARS Defense Federal Acquisition Regulation Supplement DHA Defense Health Agency DISA Defense Information System Agency DoD Department of Defense DoDD Department of Defense Directive DoDI Department of Defense Instruction DSAs Data Sharing Agreements DSAA Data Sharing Agreement Application DMZ Demilitarized Zone DoDM Department of Defense Manual DPCLO DHA Privacy and Civil Liberties Office DUA Data Use Agreement eMSM Enhanced Multi-Service Markets EULA End User License Agreement EVM Earned Value Management FAR Federal Acquisition Regulation FCI Federal contract information FE Facilities Enterprise FedRAMP Federal Risk Authorization and Management Program FISMA Federal Information Security Modernization Act FRCS Facility Related Control Systems FSO Facilities Security Officer HA Health Affairs HIPAA Health Insurance Portability and Accountability Act HCA Head of the Contracting Activity HIT Health Information Technology IGCE Independent Government Cost Estimate
IA Information Assurance IO Initial Outfitting I/O In/Out Processing Portal IPv Internet Protocol Version IS Information System ISP Internet Service Provider IT Information Technology ISCM Information Security Continuous Monitoring IV&V Independent Verification & Validation MedCOI Medical Community of Interest MHS Military Health System MIL-STD Military Standard MTFs Military Treatment Facilities NCR National Capitol Region NDA Non-Disclosure Agreement NIAP National Information Assurance Partnership NIST National Institute of Standards and Technology OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs OPM Office of Personal Management OSD Office of the Secretary of Defense P-ATO Personal Authorization to Operate P&R Personnel and Readiness PGI Procedures, Guidance and Information PDT Project Delivery Team PHI Protected Health Information PII Personally Identifiable Information PIT Platform Information Technology PK Public Key PKI Public Key Infrastructure POA&M Plan of Action and Milestones POC Point of Contact PMO Program Management Office PoP Period of Performance PP Personal Property PPSM Ports, Protocols, and Services Management PRS Performance Requirements Summary PSP Personnel Security Program PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Plan RFP Request for Proposal RFQ Request for Quotation
RMF Risk Management Framework SP Special Publication SPRS Supplier Performance Risk System SRM Sustainment, Restoration and Modernization SRG Security Requirements Guides STIG Security Technical Implementation Guides TOS Terms of Service US United States UFC Unified Facilities Criteria VPN Virtual Private Network XML Extensible Markup Language
2.3 Applicable Publications, DHA Administrative Instructions (AI), etc.
DHA AI 4140.01 – Medical Logistics Temperature Sensitive Medical Products Management.
PART 3
3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES
The Requiring Activity Authority has assessed the need for Government Furnished Property, Equipment, and Services and determined:
3.1 Services: The Government:
☐ Will NOT provide Government Furnished Services in support of this contract/task order. As a result, this paragraph is Not Applicable.
☒ WILL provide Government Furnished Services required in support of this contract/task orders. These Services are described below: The government shall provide emergency medical transportation and treatment if required. The contractor shall reimburse the Government for the cost of these medical services at current rates.
3.2 Facilities: The Government:
☒ Will NOT provide Facilities in support of this contract/task order. As a result, this paragraph is Not Applicable.
☐ WILL provide Facilities in support of this contract/task orders. The Government provided Facilities are described below: [Insert in the blank lines below what facilities (i.e. physical address/location of the building/suite/room/cubicle numbers) will be provided, the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment.]
3.3 Utilities: The Government:
☒ Will NOT provide Utilities in support of this contract/task order. As a result, this paragraph is Not Applicable.
☐ WILL provide Utilities in support of this contract/task orders. The Government provided Utilities are described below: [Insert in the blank lines shown below what utilities will be provided, i.e., all utilities in the facility will be available for the contractor’s use in performance of tasks outlined in this PWS.]
3.4 Equipment: The Government:
☒ Will NOT provide Equipment in support of this contract/task order. As a result, this paragraph is Not Applicable.
☐ WILL provide Equipment in support of this contract/task orders. The Government provided Equipment is described below:
3.4.1 Procurement Integrated Enterprise (PIEE), GFP Module Application RESERVED The contractor shall be responsible for obtaining and maintaining access, training and successful operation of the PIEE/GFP Module application for the entirety of the contract/task order PoP.
The PIEE GFP Module application is located at the following website: https://wawf.eb.mil/piee-landing/. Access to PIEE/GFP Module application training materials and in-depth information applicable to the contractor’s responsibilities regarding GFP can be found at the following website: https://dodprocurementtoolbox.com/.
Contracting Office Responsibilities:
The Contracting Office shall ensure close coordination and validation of the GFP items with the COR and DHA Accountable Property Officer prior to uploading the GFP Attachment into the PIEE/GFP Module. At the time GFP is anticipated and identified, the Government will upload the GFP Attachment into the PIEE/GFP Module. It is the Contracting Office’s responsibility to prepare, upload and maintain the GFP Attachment in the PIEE/GFP Module in accordance with the GFP Attachment instructions provided at the DoD Procurement Toolbox. The CO and COR shall manage and keep an inventory of any GFP associated with contract/task orders awarded through DHA, in accordance with applicable FAR Part 45, DoD FAR Supplement (DFARS) 245 with respective clauses, DHA AI 095 and PD 45-01 following the change in disposition of items listed on that PIEE/GFP Module Attachment.
The contracting office will also review, acknowledge, reject and/or approve shipment orders provided by the contractor as appropriate. Functional roles can be determined within the Contracting Office, and requested within the PIEE/GFP Module system.
Contractor Responsibilities:
A key contractor responsibility is to work with the CO and COR to ensure the PIEE/GFP Module data, to include the PIEE/GFP Attachment, provides a timely, complete and accurate accounting of the GFP applicable to the contract/task order. Contractors are required to report the receipt of any GFP shipped to them, regardless of whether it is listed on the GFP Attachment for their contract. Similarly, contractors are required to utilize the GFP Module application in conjunction with the shipment of GFP to the Government, or in reporting Property Loss of GFP issued (such as destruction or loss). Discrepancies or disputes regarding property shipped to or shipped from the contractor must be reported via the GFP Module application, with the CO having authority over final designation of status.
https://wawf.eb.mil/piee-landing/ https://wawf.eb.mil/piee-landing/ https://dodprocurementtoolbox.com/
The contractor shall report semi-annually 100% inventories, reconciliations, and final disposition of GFP provided by the government. Final invoices will not be paid pending GFP reconciliation.
Contractors shall be aware of and ensure compliance with applicable FAR Part 45, DFARS 245 and 252.245, Defense Pricing and Contracting Policies, Procurement Integrated Enterprise Environment Standards, DHA Administrative Instruction 094 and DHA Guidance.
3.5 Materials: The Government:
☒ Will NOT provide Materials in support of this contract/task order. As a result, this paragraph is Not Applicable.
☐ IS providing Materials in support of this contract/task orders. The Government-provided Materials are described below:
PART 4
4.0 CONTRACTOR FURNISHED ITEMS AND SERVICES
(This section is used to identify the materials and equipment that the contractor must provide.
Examples provided below.)
4.1 Services: The Contractor:
☒ Will NOT provide Contractor Furnished Services in support of this contract/task order. As a result, this paragraph is Not Applicable.
☐ WILL provide Contractor Furnished Services required in support of this contract/task orders.
These Services are described below: provide [Insert within the blank lines shown below what Services the Government will provide for the contractor staff to provide the support outlined in the PWS.]
4.2 General:
4.3 Secret Facility Clearance: N/A
4.4 Materials: N/A
4.5 Equipment: N/A
4.6 Facilities: N/A \
PART 5
5.0 SPECIFIC TASKS
5.1 Performance Objectives: The contractor shall be responsible for providing all personnel, equipment, tools, materials, supervision, training, liscening, transportation and all other items and services necessary to accomplish the pick-up and delivery service of medical items from 36 MDG Andersen AFB to USNH Guam. The contractor shall follow and meet all requirements in the delivery schedule 5.1.1 as stated below. During transport Courier assumes liability of sensitive information and samples to include but not limited to: medically sensitive/ pretected health minformation, temperature sensitive samples and pharmaceuticals, diagnostic radiography reports, prescription glasses, etc.
5.1.1 Serivce Delivery Schedule: Services shall be provided daily based on clinic schedule (usually Mon-Fri but subject to change to meet military mission needs). The contractor shall utilize the check in and out form for every delivery performed. Please see attached 7 for check in and out form template. The Service Delivery Schedule is as follows:
5.1.1.1 Pick-up items daily at 36 MDG NLT 0830 hrs.
5.1.1.2 Deliver items/pick-up new items daily at USNH Guam NLT 1200 hrs.
5.1.1.3 Return items to 36 MDG daily NLT 1330 hrs.
5.1.1.4 On the last duty day of every week pick-up from 36 MDG Laboratory NLT 1730 and deliver to USNH Guam NLT 1830
5.2 Special Qualifications:
5.2.1The contractor shall comply with all federal and local guidelines to transport medical items but not limited to medical records, biological, specimen and pharmaceuticals.
5.2.2 Contractor shall ensure employee adherence ti Health Insurance Portability and Accountablity Act (HIPAA)
5.2.3 Contractor will provide all necessary training for employees conncering transport of medical/biological samples and supplies.
5.2.4 Contractor will provide training to all employees concerning proper biohazard spill clean-up in the event of specimen leakage. Note: Specimens are prepared for shipment by facility medical technicians to minimize spills.
5.2.1 When using education/certification in conjunction with labor categories, the COR in coordination with the CO must establish a review process of contractor personnel to ensure labor category requirements are met.
PART 6
6.0 INFORMATION TECHNOLOGY & SECURITY
6.1 All work under this contract is unclassified
6.2 The TIER 1 or TIER 2 levels and position sensitivity designation for positions under this contract is: (Requirement must be checked in order to be a requirement for this PWS.)
6.3 Personally Identifiable Information (PII)/Protected Health Information (PHI), Procurement, and Federal information requirements:
6.3.1. Data Sharing Agreements (DSAs): Contractors requiring access to PII, which includes PHI, or access to de-identified data, are subject to the DHA Privacy and Civil Liberties Office (DPCLO) (Privacy Office) Data Sharing Program. This program requires DHA to enter into DSAs with parties outside the MHS who use or create MHS data. A DHA contract may use the term Data Use Agreement (DUA) rather than DSA. DSAs assure that outside parties protect MHS data in accordance with the Privacy Act and the HIPAA Rules. To apply for a DSA, the contractor submits a Data Sharing Agreement Application (DSAA) to the DHA DPCLO. The contractor submits the DSAA even if a subcontractor will be the party accessing MHS data.
After review and approval of the DSAA, the Privacy Office provides a DSA to the contractor for execution.
6.3.2. Processing Procurement Sensitive Information: All individuals shall seek guidance from the CO regarding the coordination of documents, dissemination, and transmission of procurement sensitive information. Procurement sensitive information shall not be transmitted electronically unless encryption is utilized. Depending on a particular procurement, other restrictions may apply.
6.4 Training
6.4.1 Contractor employees performing cybersecurity/cyberspace functions shall comply with the following requirements: (If applicable)
6.4.1.1 Training: All contractor and associated subcontractor employees working Cybersecurity Information Assurance (IA)/Cyberspace functions must comply with DoD training requirements in Department of Defense Directive (DoDD) 8140.01 and DoD 8570.01-M. Contractors shall identify, document, track, and report qualifications of contract support personnel who perform cyberspace work roles.
6.4.1.2 Certification: The contractor shall ensure that personnel accessing IS have the proper and current IA certification to perform IA functions at contract award in accordance with DoD
8570.01–M, IA Workforce Improvement Program. The contractor shall meet the applicable IA certification requirements as outlined in DFARS 252.239-2001, including:
6.4.1.2.1 DoD-approved IA workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01–M; and
6.4.1.2.2 Appropriate operating system certification for IA technical positions as required by DoD 8570.01–M.
6.4.1.2.2.1 Upon request by the Government, the contractor shall provide documentation supporting the IA certification status of personnel performing IA functions.
6.4.1.2.2.2 Contractor personnel who do not have proper and current certifications shall be denied access to DoD IS for the purpose of performing IA functions.
6.4.2 User requirements: All contractor employees that require access to DHA IT must comply with the requirements of DHA-Procedural Instruction 8140.01, Acceptable Use of DHA IT, to include those contract employees with privileged access.
6.5 Cybersecurity Requirements for Non-DoD IT or Covered Contractor IS: RESERVED
6.5.1 The contractor shall, at time of award, have implemented the security requirements prescribed in the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800- 171), in accordance with DFARS clause 252.204-7012.
6.5.2 NIST SP 800-171 DoD Assessment Methodology. The DFARS provision 252.204-7019 introduces the “NIST SP 800-171 DoD Assessment Methodology” requirement. This requirement enables a strategic assessment of a contractor’s implementation of the NIST SP 800- 171 requirements as required in DFARS clause 252.204-7012. The DoD Assessment Methodology requirement flows down to subcontractors.
6.5.2.1 Basic Assessment: The contractor shall obtain and maintain access to the Supplier Performance Risk System (SPRS) via the PIEE, (available via the internet at https://www.sprs.csd.disa.mil/)
6.5.2.1.1 The contractor shall perform a Basic Assessment, using the NIST SP 800-171 DoD Assessment Scoring Template, and enter the results electronically in SPRS for each covered contractor information system that is relevant to an offer, contract, task order, or delivery order.
See Attachment 2, Deliverable Schedule Table.
6.5.2.1.2 The contractor shall ensure that applicable subcontractors also have their results of a current assessment posted in SPRS prior to awarding a subcontract or other contractual instrument in accordance with DFARS clause 252.204-7020.
https://www.sprs.csd.disa.mil/
6.5.3 The contractor shall provide the government with access to its facilities, systems, and personnel when necessary to conduct or renew a higher-level (i.e., Medium or High) assessment in accordance with DFARS clause 252.204-7020.
6.5.4 Cybersecurity Maturity Model Certification (CMMC) (When applicable): The CMMC (DFARS clause 252.204-7021) builds upon the NIST SP 800-171 DoD Assessment Methodology by adding a comprehensive and scalable certification element to verify the implementation of processes and practices associated with the achievement of a cybersecurity maturity level. The CMMC is designed to increase assurance to the DoD that federal contract information (FCI) and DoD Controlled Unclassified Information (CUI) is protected at a level commensurate with the risk. The CMMC requirement flows down to subcontractors.
6.5.4.1 The contractor shall have a current (i.e., not more than three years old) CMMC certificate in SPRS issued by an accredited CMMC Third Party Assessment Organization (3PAO) at the required CMMC level. The description of CMMC levels is available at https://www.cmmcab.org/.
6.5.5 The contractor shall submit requests to vary from NIST SP 800-171 in writing to the CO or COR, for consideration by the DoD Chief Information Officer (CIO). The contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be non-applicable or to have an alternative, but equally effective, security measure that may be implemented in its place.
6.5.6 If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the CO or COR when requesting its recognition under this contract.
6.5.7 Cloud Computing: If the contractor intends to use an external cloud service provider, on their behalf, to store, process, or transmit any DoD CUI in performance of this contract, the contractor shall require the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/) and that the cloud service provider complies with requirements in paragraphs 6.5.8 through 6.5.14 for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.
6.5.7.1 If the information is DoD CUI-specific (e.g., PII/PHI), then the contractor shall ensure the external cloud service provider meet the security requirements equivalent to FedRAMP High baseline.
6.5.8 Cyber Incident Reporting Requirement
6.5.8.1 When the contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the https://www.cmmcab.org/ https://www.fedramp.gov/ contractor’s ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the contractor shall:
6.5.8.1.1 Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other IS on the contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the contractor’s ability to provide operationally critical support; and
6.5.8.1.2 In accordance with DFARS clause 252.204-7012, rapidly report (within 72 hours) cyber incidents involving DoD CUI to DoD Cyber Crime Center (DC3) via https://dibnet.dod.mil/portal/intranet/. In the event of a cybersecurity incident involving a CUI- Specific breach (i.e., PII/PHI), the contractor, in addition to reporting to the DC3, shall follow the incident reporting guidance prescribed in the TRICARE Operations Manual, Chapter 1, Section 5, “Compliance with Federal Statutes” at https://manuals.health.mil/
6.5.8.2 Cyber incident report: The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements as prescribed at the https://dibnet.dod.mil/portal/intranet/.
6.5.8.3 Medium assurance certificate requirement: In order to report cyber incidents in accordance with this clause, the contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/
6.5.9 Malicious software: When the contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DC3 in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.
6.5.10 Media preservation and protection: When a contractor discovers a cyber incident has occurred, the contractor shall preserve and protect images of all known affected IS and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.
6.5.11 Access to additional information or equipment necessary for forensic analysis: Upon request by DoD, the contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.
6.5.12 Cyber incident damage assessment activities: If DoD elects to conduct a damage assessment, the CO will request that the contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of DFARS clause 252.204-7012.
6.5.13 Apply other IS security measures when the contractor reasonably determines that IS security measures may be required to provide adequate security in a dynamic environment or to https://dibnet.dod.mil/portal/intranet/ https://manuals.health.mil/ https://public.cyber.mil/ accommodate special circumstances (e.g., HIPAA) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.
6.5.14 The contractor shall maintain within the US or US territories all Government data that is not physically located on DoD premises, unless the contractor receives written notification from the CO to use another location, in accordance with DFARS 239.7602-2(a).
6.5.15. The contractor shall mitigate supply chain risk to the government by complying with DFARS 252.239-7018 and only utilizing unified capability equipment identified on the DODIN Unified Capabilities Approved Products List (https://aplits.disa.mil/processAPList), unless granted a waiver in accordance with DODI 8100.04, DOD Unified Capabilities (UC).
6.6 Risk Management Framework (RMF) for DoD IT: RESERVED
All IS, Platform Information Technology (PIT) and IT Services or Products under this requirement, that receive, transmit, store, or process nonpublic government data must be accredited in accordance with DoDI 8510.01, Risk Management Framework (RMF) for DoD IT and comply with annual Federal Information Security Modernization Act (FISMA) security control testing. IS and PIT systems must be categorized in accordance with Committee on National Security Systems Instruction (CNSSI) 1253, implement a corresponding set of security controls from the NIST SP 800-53, and use assessment procedures from NIST SP 800-53A with additional DoD-specific assignment values, overlays, implementation guidance, and assessment procedures as required.
6.6.1 All systems subject to RMF must present evidence of authorization in the System Security Plan, Security Assessment Report) a Plan of Action and Milestones (POA&M) and authorization decision document or show that the system has a DoD RMF or equivalent DoD Component PIT system accreditation decision that is current within 3 years within 5 business days of CO request.
Evidence of FISMA compliance must be presented in the form of a POA&M. Systems must have and maintain an Authority to Operate (ATO) or Authority to Operate with Conditions (ATO-C) by contract award.
6.6.2 The contractor shall implement security controls in accordance with NIST implementation and validation requirements specified in the NIST SP 800-37 Risk Management Framework (RMF) and DoDI 8510.01, Risk Management Framework (RMF).
6.6.3 The contractor shall configure the information system in accordance with Defense Information Agency (DISA) Security Requirements Guides (SRGs) and security technical implementation guides (STIGs).
6.6.4 The contractor shall ensure that the information system conforms to the requirements of DoDI 8551.01 “Ports, Protocols, and Services Management (PPSM)”.
6.6.5 The contractor shall ensure that the information system shall authenticate all entities as specified in DoDI 8520.03 “Identity Authentication for Information Systems” prior to granting access.
https://aplits.disa.mil/processAPList
6.6.6 The contractor shall Public Key (PK) enable the information system, implementing digital signature and encryption requirements specified in DoDI 8520.02, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling”.
6.6.7 The contractor will be responsible for compliance with the Joint Force Head Quarters – Department of Defense Information Network issuances and IA Vulnerability Management (IAVM) issuances by ensuring that the issuances are assessed, implemented and maintained throughout development and sustainment in accordance with specified timelines.
6.6.8 The contractor shall support reciprocity, by providing all directed information in NIST security documents to the government.
6.6.9 The contractor shall implement system level protection and detection capabilities that are consistent with their contract for NIST Security requirements that meet DoD and DHA Cybersecurity Architectures.
6.6.10 Cyber Incident Reporting Requirement: The contractor shall comply with the incident management requirements of Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6510.01B, “Cyber Incident Handling Program”.
6.6.11 Information security continuous monitoring (ISCM): ISCM is defined as maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions. ISCM is a critical part of the risk management process to ensure that IS and PIT operations remain within an acceptable level of risk despite any changes that occur. The Contractor shall maintain ongoing monitoring, analysis and incident response procedures for all ARRT and PIT systems under this requirement in accordance with NIST SP 800-137.
6.6.12 The contractor shall mitigate supply chain risk to the government by complying with DFARS 252.239-7018 and only utilizing unified capability equipment…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .