Attachment 1- Performance Work Statement (PWS).docx

Confidential Unclassified Information (CUI) Curvo-BroadJump Performance Work Statement The Defense Logistics Agency (DLA) Troop Support - Philadelphia Medical Customer Operations and Supplier Operations combine to perform world-wide medical supply chain management for DoD medical materiel and supplies directly supporting warfighters in theatre and their families at home. The Defense Medical Logistics Enterprise System (DMLES) - DLA is the suite of information technology (IT) applications that enables all dimensions of Defense Medical Logistics operations and support.

1.1 Requirement Description: The Defense Logistics Agency - Troop (DLA-TS) Support Medical Directorate has a requirement to obtain a subscription agreement for Curvo-BroadJump Data License and PharmaChecker license. This license is required to provide pharmaceutical databases that include descriptive drug information and pricing transparency in support of pharmacy procurement and analysis, which promises to lower healthcare costs and improve patient care. The database is required to provide critical classification data for DLA Troop Support on a weekly basis to enable cross references of products or equivalent products such as therapeutically equivalent products, pharmaceutically equivalent products, etc. Curvo-BroadJump product information is also required in numerous DLA Troop Support Medical system applications as well as in downstream service customer systems and catalogs.

Period of Performance:

2.0 SCOPE

The government requires a neutral, unbiased pharmaceutical benchmarking and market-intelligence data service. The contractor shall provide a subscription service consisting of a pharmaceutical market data feed and a web-based analytics application. The service shall provide actionable intelligence to drive long-term, measurable cost savings and efficiency improvements to the healthcare supply chain.

The contractor’s data must be GPO-agnostic and track a significant portion of the U.S. healthcare market’s non-labor spend to create a trusted source of market intelligence for transparent pricing across pharmaceutical spend.

2.1 Services Provided

The contractor shall provide the following services and applications as part of the subscription.

2.1.1 Pharmacy Data Licensing and Market Intelligence Feed: The government requires a comprehensive flat data file containing market intelligence for pharmaceutical products. This data feed will serve as a trusted source for transparent pricing.

· The contractor shall work collaboratively with the DLA to establish a secure and efficient data transfer method.

· The data feed shall contain pricing benchmarks including, but not limited to: Minimum Price, Average Price, Maximum Price, and pricing at the 10th, 25th, 50th, 75th, and 90th percentiles.

· The data feed shall include the following data fields for each record provided:

· Class: Highest level of classification for the transaction.

· Subclass: Secondary level of classification grouping products.

· Category: Tertiary level of classification grouping products by attributes.

· ManufacturerID: Contractor’s internal ID for the manufacturer.

· Manufacturer: Name of the product manufacturer.

· ProductID: Contractor’s internal ID for the distinct product.

· NDC: The National Drug Code for the product.

· Item_Description: Description of the identified product with all relevant attributes.

· Total_Units_Purchased: Total units purchased across all facilities during the benchmark period.

· Facility_Count: Distinct count of all facilities that purchased the product.

· Account Type: The pharmacy account type (e.g., WAC, 340B, GPO, Retail).

· Class_Of_Trade: The type of facility that purchased the product.

· DSH_Eligible: Indicator for whether the purchasing hospital is DSH eligible as defined by HRSA.

· Minimum_Price: The minimum price observed in the market.

· Average_Price: The average price observed in the market.

· Maximum_Price: The maximum price observed in the market.

· Percentile_10: 10th percentile price observed.

· Percentile_25: 25th percentile price observed.

· Percentile_50: 50th percentile price (Median) observed.

· Percentile_75: 75th percentile price observed.

· Percentile_90: 90th percentile price observed.

2.1.2 PharmaChecker™ Web Application: The government requires access to a web-based user interface for custom, on-demand analyses of pharmaceutical spend. This application shall provide pricing transparency and contextual market insights.

· The contractor shall provide a site license for up to nineteen (19) .mil government users.

· The application shall provide NDC-level benchmarking and trend analysis, allowing users to visualize market dynamics for a single NDC or a basket of pharmaceuticals.

· The application must provide the ability to create comparative cohorts based on Account Type, Class of Trade, and DSH Eligibility Status.

· The application shall provide additional contextual information, such as facility spend, purchase quantity, and other relevant factors, to help users understand pricing rationale.

3.0 Invoice Instructions

For invoicing purposes, to allow for incremental invoicing, the quantity and unit price have been flipped. When invoicing in WAWF, please put the required dollar amount in WAWF’s quantity field and a unit price of $1.00.

The contractor shall submit a proper invoice by the 10th day of each month for services delivered the previous month through Wide Area Workflow (WAWF). All invoices shall be submitted in accordance with clauses DFARS 252.232-7003 and 252.232-7006 included in the RFP and award.

The invoice shall contain:

The contract number A unique invoice number The month services were delivered Name and address of the contractor A separate entry for each call order with a description of the service A separate entry for mileage for each call order The date of each call order Duration of each call order The rate of payment for each entry A total amount invoiced for each call order and mileage entry A total amount invoiced for all services, including mileage, for the invoice A description of the service provided for each call order Name of government contact person Name of government customer Notation indicating cancelled call order Payment will be made by Defense Finance Accounting Service (DFAS) as listed in box 18a of the SF1449.

The invoice shall comply with the requirements identified below: The Government intends to be done electronically in accordance with DFARS clause 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports. The Government will utilize the Department of Defense Wide Area Workflow (WAWF) Receipt and Acceptance (RA) System to accept supplies/services delivered under this task order. This web-based system is located at https://wawf.eb.mil and provides technology for DOD vendors and authorized DOD personnel to generate, capture, and process receipt and payment related documentation in a paperless environment. Invoices for supplies/services rendered under this IDIQ shall be submitted electronically through WAWF.

The requirements for invoicing are subject to FAR 52.232-25 Prompt Payment. Invoices for goods received or services rendered under this Task Order(s) shall be submitted electronically through WAWF. Hard copy invoices cannot be accepted. The vendor’s failure to include the necessary information will result in invoices being rejected. Back up documentation can be included and attached to the invoice in WAWF. Attachments created in any Microsoft Office product are attachable to the invoice in WAWF. The Maximum size limit of each attachment is 2 Megabytes (MB). Total size limit for all files is 5MB.

The vendor is required to utilize the system when processing invoices and receiving reports under this contract/order. Unless the provisions at DFARS 252.232-7003(c) applies, the vendor shall (1) ensure an Electronic Business Point of contact is designated in the System for Award Management (SAM) at https://www.sam.gov and (II) register to use WAWF-RA at the https://wawf.eb.mil site within ten (10) calendar days after award on this contract/order or modification. Step by step procedures to register are available at the https://wawf.eb.mil site. The vendor will submit invoices and performance reports as required by the PWS electronically in accordance with the requirements specified for WAWF. All invoices will clearly identify the period of performance. The approval of invoices will be based on the performance standards included in the requirements of the PWS. All discrepancies from Task Order requirements will be highlighted and raised to the attention of the Contracting Officer within 15 business days from date of submission to the COR.

The Invoice POC will approve invoices which demonstrate that the vendor has met the deliverables for the period. The vendor is directed to use the “2-In-1” format when processing invoices and receiving reports. For those vendors who are unfamiliar with WAWF, contents for this information can be located on the Defense Finance and Accounting Services (DFAS) Website at: http://www.dfas.mil/Contractororpay/electroniccommerc/ETToolBox.html http://www.dfas.mil/contractorpay/ electronic commerce/ETToolBox.html After clicking the “submit” button, a Notice of Successful/Unsuccessful Submission will appear. This screen contains a “Send More E-Mail Notifications” button. Click on this button and add the email addresses for the COR, and others as desired. Notification shall be provided for each invoice submitted.

In some situations, the WAWF-RA system will pre-populate the “Issue By DoDAAC,” “Admin By DoDAAC,” and “Pay DoDAAC.” Vendors shall verify those DoDAACs automatically entered by the WAWF-RA system match the above information. If these DODAACs do not match, then the vendor shall correct the field(s) and notify the Contracting officer of the discrepancy (ies). On the vendor Interface page click on “WAWF-RA” header at the top of the page. Under downloads on the WAWF-RA page that appears, click the appropriate documents either “Combo”, “2-in-1,” or “Cost Voucher” to download the instructions.

Note to Vendor:

Before closing out an invoice session in WAWF-RA, but after submitting the document(s), the vendor will be prompted to send additional email notifications. Vendors shall click on “Send More Email Notification” on the page that appears. Add the acceptor’s/receiver’s email address (Note this address is their work address and not their WAWF-RA organizational email address) in the first email address block and add any other additional email addresses desired in the following blocks. This additional notification to the Government is important to ensure the acceptor/receiver is aware that the invoice document(s) have been submitted into the WAWF-RA system.

The POC’s identified above are for WAWF-RA issues only. Any other contracting questions/problems should be addressed to the Contracting Officer or other person identified in the contract/order to whom questions are to be addressed.

WAWF Tools and Help

(a) The vendor may have their CAGE code activated (required only first time) in WAWF by calling 866-618-5988. Once activated, the vendor should self-register at the web site https://wawf.eb.mil .

(b) Vendor training is available at: http://www.wawftraining.com . Additional support can be obtained by calling the DISA Ogden Help Desk at 1-866-618-5988 or e-mailing to cscassig@ogden.disa.mil .

(c) WAWF Vendor “Quick Reference” Guides are located at: https://acquisition.navy.mil/rda/home/acquisition_one_source/ ebusiness/don_ebusiness_solutions/wawf_overview/vendor_information Payment information can be accessed from the Defense Finance and Accounting Service (DFAS) website at http://www.dfas. mil. The contract/order number and invoice number is required when inquiring about the status of a payment. Questions concerning payment should be directed to the DFAS at 1-800-756-4571.

3.1 Deliverables

The contractor shall provide the following deliverables:

· Pharmacy Data Feed (Weekly, or at a mutually agreed-upon cadence)

· PharmaChecker™ Application Access (Continuous)

3.2 Performance Requirements Summary

The tasks the Vendor shall perform are defined in Section 2.1. All deliverables will be submitted to the COR for acceptance unless otherwise agreed upon. The Government will make objective and subjective assessments of the vendor’s performance to determine whether contract performance is acceptable. The vendor is expected to perform all functions in a professional manner and prepare accurate and timely documentation. Progress will normally be tracked based on the milestone event when the vendor receives a specific tasking. Performance may vary with the complexity of the acquisition and/or technical document. It is expected that the documentation and procedures will comply with all major regulatory and process requirements and agency policies and procedures.

3.2.1 Method of Surveillance

The Government will ensure quality assurance and timeliness of all tasks via COR Inspections and Customer Feedback. The Government will inspect and evaluate performance of each completed task or deliverable required in the task order SOW.

3.2.2 Inspection and Acceptance Criteria

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR. All deliverables will be inspected for content, completeness, accuracy, legibility and conformance to contract requirements by the COR. At the discretion of the Government, inspection may include validation of information or software through the use of automated tools and/or testing of the deliverables, as specified in the SOW.

If the Government finds that a draft or final deliverable contains spelling errors, grammatical errors, improper format, or otherwise does not conform to the requirements stated within the task order SOW, the document may be immediately rejected without further review and returned to the Vendor for correction and re-submission. If the Vendor requires additional Government guidance to produce an acceptable draft, the Vendor shall arrange a meeting with the COR.

The basis for acceptance shall be compliance with the requirements set forth in this task order PWS, the Vendor's proposal and other terms and conditions of the contract. Deliverable items rejected shall be corrected in accordance with the applicable clauses. Reports and document deliverables will be accepted when all discrepancies, errors or other deficiencies identified in writing by the COR have been corrected to the Government’s satisfaction.

The Vendor shall provide electronic copies of deliverables. Electronic copies shall be delivered via email attachment or other media by mutual agreement of the parties. The electronic copies shall be compatible with the current DLA Microsoft (MS) Office products or other applications as appropriate and mutually agreed to by the parties. The Vendor shall use best commercial practices for formatting deliverables under this contract. If the draft deliverable is adequate, the Government may accept the draft and provide comments for incorporation into the final version. All of the Government's comments to deliverables must either be incorporated in the succeeding version or the Vendor must demonstrate to the Government's satisfaction why such comments should not be incorporated.

3.2.3 General Acceptance Criteria

General quality measures, as set forth below, will be applied to each work product received from the vendor under the resultant task order. These performance measurements are defined as:

Quality:

Accuracy – Work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

Clarity – Work products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.

Consistency to Requirements – All work products must satisfy the requirements of this Performance Work Statement.

Format – Work products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals. All text and diagrammatic files shall be editable by the Government.

Timeliness Work products shall be submitted on or before the due dates determined/specified between the task order COR and vendor or submitted in accordance with a later scheduled date determined by the Government.

3.2.4 Fixed Price Performance Based Service Contract Payments The following procedures apply:

The vendor shall submit a monthly invoice for 100% monthly amount for each SOW task. As part of the COR’s monthly certification process, the COR will indicate on the invoice submitted the amounts authorized for payment for each task based on the performance measures described herein. The determination for payment will be made in accordance with the procedures set forth below. The COR or his/her designated representative will advise the vendor of what the Contracting Officer’s (KO’s) authorized amount of payment will be for each month. The vendor may direct questions on any withholding of a payment to the Contracting Officer.

3.2.5 Performance Review and Payments

Below are the Performance Standards that will be used in evaluating performance in determining the amount of the payment owed to the vendor. These Performance Standards apply to the deliverables listed in Section 2.5 and to all performance under this task order SOW.

Overall Performance Ratings

Satisfactory – Performance meets or exceeds contractual requirements. The contractual performance reflects some minor problem(s) for which corrective actions taken by the vendor appear or were satisfactory. The COR recommends and the Contracting Officer will make a determination to pay the vendor 100% of the invoice amount.

Fair – Performance does not meet some contractual requirements. The contractual performance reflects a minor problem(s) for which the vendor has not yet identified corrective actions. The vendor’s proposed actions appear only marginally effective or were not fully implemented. The minor performance problem(s) do not adversely impact the mission of the Agency. The COR recommends and the Contracting Officer will make a determination to pay the vendor 90% of the invoice amount.

Marginal – Performance does not meet some contractual requirements. The contractual performance reflects a serious problem(s) for which the vendor has not yet identified corrective actions. The vendor’s proposed actions appear only marginally effective or were not fully implemented. The COR recommends and the Contracting Officer will make a determination to pay the vendor 80% of the invoice amount.

Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains a serious problem(s) for which the vendor’s corrective actions appear or were ineffective.

Payment will be withheld pending resolution of cure notice(s). Termination for default or cause may result.

Timeliness

Satisfactory Meets or exceeds contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects some minor problem(s) for which corrective actions taken by the contractor appear or were satisfactory.

Fair Does not meet some contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects a minor timeliness problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented. The minor timeliness problem(s) do not adversely impact the mission of the Agency.

Marginal Does not meet some contractual requirements in terms of timeliness of delivery. The timeliness of contractual performance reflects a serious problem(s) for which the contractor’s proposed actions appear only marginally effective or were not fully implemented.

Unsatisfactory Does not meet most contractual requirements in terms of timeliness of delivery and recovery is not likely in a timely manner. The timeliness of contractual performance contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

Quality

Satisfactory Meets or exceeds contractual requirements in terms of quality of work performed. The quality of contractual performance reflects some minor problem(s) for which corrective actions taken by the contractor appear or were satisfactory.

Fair Does not meet some contractual requirements in terms of quality of work performed. The quality of contractual performance reflects a minor quality problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally quality of work performed. The quality of contractual effective or were not fully implemented. The minor quality problem(s) do not adversely impact the mission of the Agency

Marginal Does not meet some contractual requirements in terms of quality. The quality of contractual performance reflects a serious problem(s) for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.

Unsatisfactory Does not meet most contractual requirements in terms of quality and recovery is not likely in a timely manner. The quality of contractual performance contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

Disincentives are applied for ratings of “Fair”, “Marginal”, and “Unsatisfactory” as follows:

Satisfactory = 100% payment

Fair = -10% disincentive

Marginal = -20% disincentive

Unsatisfactory = Payment will be withheld pending resolution of cure notice(s). Termination for default or cause may result.

End of Statement of Work

CUI - SOURCE SELECTION INFORMATION – SEE 2.101 AND 3.104