Attachment G_RFP Proposal Worksheetv3.xlsx
XLSX spreadsheet 19 KB Posted
- Attached to
- Remote Health Readiness Program 4 (RHRP-4) Federal contract opportunity
- Solicitation number
- HT001125R0020
- Issued by
- Defense Health Agency
About this file
This document is an RFP Proposal Worksheet for the Remote Health Readiness Program 4 (RHRP-4) solicitation, detailing technical proposal requirements across four key subfactors. The worksheet instructs offerors to provide comprehensive plans for: 1) Provider Network Implementation, including network sizing models, provider ratios, and coverage in specific markets like Guam, Alaska, San Antonio, and the National Capital Region; 2) Scheduling Capability, outlining electronic and telephonic scheduling approaches for medical readiness services across mobile, web, and telephonic platforms; 3) NIST/CMMC Compliance, requiring detailed descriptions of security requirement implementations, including DFARS clause compliance and a plan for achieving CMMC Level-2 Certification; and 4) Transition-In Plan, describing a detailed schedule and approach for ramping up capabilities within 9 months of contract award. The solicitation is issued by the Defense Health Agency to provide medical and dental readiness services to military Reserve and Active Components, TRICARE Prime Remote enrollees, DoD Service Civilians, and Department of Homeland Security members.
View the file
Other files for this federal contract opportunity
Show all 50
Remote Health Readiness Program 4 (RHRP-4) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| THIS IS FOR THE TECHNICAL FACTOR/VOLUME III ONLY. |
| On the Tech Subfactor Crosswalk Tab: |
| 1. The Offeror shall input their company name in Yellow Higlighted Cell D1. |
| 2. The Offeror shall provide the Section(s), Paragraph(s) and Page number(s) where the requested subfactor is addressed in the Yellow Highlighted cell in Column A only. |
| 3. This Crosswalk does not count against page limits for the Technical Factor. |
Tech Subfactor Crosswalk Offeror Name
| Volume III Technical (Factor 3) | ||||
| Section, Paragraph, and Page Number | ||||
| Subfactor 1: Provider Network | ||||
| The Offeror’s proposal shall provide a comprehensive Provider Network Implementation Plan describing the Offeror’s approach for establishing, implementing, and maintaining robust medical and dental provider networks capable of delivering the full range of required readiness services via the three identified modalities to Service Members (SMs) described in PWS paragraphs 5.1, 5.2, and 5.7. The Offeror shall disclose in its proposal the percentage of its proposed network that already exists (however constituted), explain the arrangements it has to use (and how it will use) the already existing network, and attach any letters of commitment from network owners indicating that the network(s) identified in the proposal will participate in or join the Offeror’s network. Specifically, the Offeror’s proposal shall address the following: | ||||
| a. The Offeror’s proposed Provider Network Sizing Model (PWS paragraph 5.1.1) including formulas and methods used to derive network sizing targets by provider practice area to meet the contract’s in-clinic requirement. The Offeror’s proposal shall clearly demonstrate how its network model: | ||||
| i. Incorporates the SM population (Exhibit F1); | ||||
| ii. Calculates the number of providers needed and minimum provider ratios; | ||||
| iii. Determines types of providers required; | ||||
| iv. Accounts for the travel distance and access standards described in PWS paragraph 5.1.2. The Offeror shall also describe the mapping tools/programs it proposes to use for determining the driving distance between a SM’s or civilian employee’s home of record, place of duty, or place of civilian employment and the provider’s location; and | ||||
| v. Includes an approach to monitor and address network shortages. | ||||
| b. The Offeror’s process/timeline for establishing agreements with providers, and obtaining appointments with such providers, in areas known for having limited network/provider coverage. | ||||
| c. The Offeror shall apply each element of its sizing model, and show the results of applying the model to reflect the types and numbers of providers necessary for an adequate network (considering the travel distance and access standards described in PWS paragraph 5.1.2), to the following markets as a representative sample of the contract requirements: | ||||
| i. Guam | ||||
| ii. State of Alaska | ||||
| iii. San Antonio, TX | ||||
| iv. National Capital Region, i.e. the metropolitan area that includes Washington, D.C. and the surrounding Maryland and Virginia counties |
| Subfactor 2: Scheduling Capability | ||
| The Offeror’s proposal shall provide a comprehensive plan describing the Offeror’s approach to creating, operating, and maintaining a secure readiness scheduling capability, as described in the PWS, that allows SMs, SCs, and SC designees to access required medical readiness services using mobile, web, and telephonic means for each of the three modalities: in-clinic, virtual, and group events. (PWS paragraphs 5.2, 5.3, 5.5, 5.7) | ||
| a. The Offeror’s proposal shall describe its approach to creating, operating, and maintaining both electronic and telephonic scheduling capabilities for all modalities. The proposed approach shall include a detailed description of how the capabilities will provide all functionality described in the PWS paragraphs 5.2, 5.3, 5.5, 5.7, and 5.10 accessible via web and mobile platforms, including customizable user roles (see Exhibit G) with ability to schedule, edit, view, modify, and cancel readiness appointments. | ||
| b. The Offeror’s proposal shall describe its approach for creating and maintaining the Status Dashboard Common Operating Picture for displaying financial reporting, scheduling, and forecasting services (PWS paragraph 5.10). The proposed approach shall include a detailed description of how the Status Dashboard will provide all functionality as described in PWS Paragraph 5.10 and its subparagraphs. |
| Subfactor 3: NIST/CMMC Compliance (PWS paragraphs 5.2.7.5.1, 6.4, 6.5) | |
| a. The Offeror’s proposal shall describe how it will implement and comply with the security requirements prescribed in DFARS clause 252.204-7012. | |
| b. The Offeror’s proposal shall describe its approach to implementing each of the 110 security requirements of NIST SP 800-171 for the processing, storage, and transmission of any DoD controlled unclassified information. | |
| c. The Offeror’s proposal shall describe its approach to track and assess compliance of its subcontractors with the NIST SP 800-171 requirements in accordance with DFARS clause 252.204-7020 and 252.204-7021. | |
| d. The Offeror shall have a current (i.e., not more than 3 years old) basic assessment summary-level score posted in the Supplier Performance Risk System (SPRS) and shall include its summary-level score in its proposal. | |
| e. The Offeror shall include in its proposal a Plan of Action that will apply if its summary-level score is below 110, identifying security tasks remaining to be accomplished and describing how it will accomplish those remaining tasks. | |
| f. The Offeror’s proposal shall describe how it will achieve a CMMC Level-2 Certification through a CMMC third party assessor organization (C3PAO) following the four-phase DOD implementation plan. |
| Subfactor 4: Transition-In Plan | |
| The Offeror’s proposal shall provide a detailed Transition-In Plan and schedule (with detailed milestones and interim steps), addressing all activities required from contract award through commencement of services, to satisfy the transition-in requirements, as described in PWS para 1.6.1. The Offeror’s plan shall explain its approach for meeting each of the milestones and associated requirements identified in the Performance Based Milestone Payment Schedule Transition_In, Attachment A and otherwise for ensuring a smooth ramp up of all required capabilities (e.g., information technology (IT) capabilities, IT connections, staffing, training, provider networks, logistics capabilities, etc.) necessary to deliver all services and support described in the PWS paragraph 1.6.1 by the full performance start date (not later than 9 months from contract award). |
File details come from the government source that posted it. Updated .