ESBD_File_318813_HHS0012857 HeRMOSS - PCS 134 Attachment 1 of Addendum 1.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

C:\Users\Fnesbitt01\Pictures\images.png

PCS 134

Form Revision Date 05/10/2021 Release Date 06/26/2015 Vendor Questions and Answers +/- Rows Reference Vendor Question HHS Response 9.0.0.2.20101008.1.734229 Refer to Section 3.4.2, Page Limit and Supporting Documentation of the RFO.

Refer to Section 3.4.2, Page Limit and Supporting Documentation of the RFO.

No, it is not permissible. Refer to Section 3.4.2, Page Limit and Supporting Documentation of the RFO.

Refer to Section 3.4.2, Page Limit and Supporting Documentation of the RFO.

No, refer to Section 6.6.2, Financial Statements and Financial Solvency and Section 3.5.2, Submission Options.

Refer to Exhibit L, HHS Online Bid Room Instructions, for a link to our resources page for a tutorial, guidebook, and other resources to help you use the HHS Online Bid Room.

The maximum file size for each attachment is 250 MB, or megabytes. For responses that include larger attachments, bidder must use other options such as mail or personal delivery, refer to Section 3.5.2, Submission Options.

Refer to Section 3.4.4, Exceptions and Exhibit E, Exceptions Form, of the RFO.

Refer to Section 3.4.4, Exceptions and Exhibit E, Exceptions Form, of the RFO.

Refer to Section 3.4.4, Exceptions and Exhibit E, Exceptions Form, of the RFO.

Refer to Section 3.4.4, Exceptions, Exhibit E, Exceptions Form, and Section 2.3.1, Contract Award and Execution, of the RFO.

Refer to Section 3.4.4, Exceptions, Exhibit E, Exceptions Form, and Section 8.1.2, Offer Period, of the RFO.

Refer to Section 3.4.4, Exceptions, Exhibit E, Exceptions Form, and Section 2.3.1, Contract Award and Execution, of the RFO.

Refer to Section 3.5.5, Modifications and Withdrawals and Section 2.3.1, Contract Award and Execution, of the RFO.

Refer to Section 3.4.4, Exceptions and Exhibit E, Exceptions Form, of the RFO.

Refer to Section 3.4.4, Exceptions and Exhibit E, Exceptions Form, of the RFO.

Yes, the System Agency will provision parallel environments in the Austin Data Center (ADC) as per identified requirement(s) in the RFO.

Yes. However, direct or indirect integration with System Agency’s DCS environment is not permitted.

The System Agency will apply necessary patching upgrade packages and maintain all servers within the DCS environment.

The System Agency does not require the vendor to have the ability to place the archived data back into the Maven platform. However, the archived data will be accessible by the System Agency upon request, as per RFO data archival need for Transition/Turnover Phases.

Non-approved data is data that is both ingested by the Maven platform and does not meet DSHS schema standards (i.e., syntax, format, errored content) and will be sent back to the provider for correction or resubmittal.

This requirement is focused upon existing interfaces identified within the RFO. No new interfaces are determined at this point.

The System Agency currently leverages various extraction and analysis tools; examples include SAS, Tableau, and Dynatrace.

Current implementation of the Maven platform does not support a data warehouse approach. The System Agency requires Respondents to propose pricing for data warehousing support and maintenance within the Solicitation Response. Refer to Section 7.1.2, Supplemental Services, of the RFO.

Refer to Section 2.2.2, Contract Phases, Domains, and Subdomains per Phase, of the RFO.

3.4.2 Page Limit and Supporting Documentation

Formatting Cell3: Page 67

3.4.2 Page Limit and Supporting Documentation

Formatting Cell3: Page 67

3.4.2 Page Limit and Supporting Documentation

Formatting Cell3: Page 67

3.4.2 Page Limit and Supporting Documentation

Formatting Cell3: Page 79

6.6.2 Financial Statements and Financial Solvency

Formatting Cell3: Page 69

3.1 Solicitation Response Submission And Delivery

Proposal Submission Cell3: N/A (Proposed New Clause) Limitation of Liability Cell3: N/A (Proposed New Clause) Disclaimer Cell3: Throughout, including without limitation Pages 16-18, Article X of Exhibit B of the RFO (Indemnity) Indemnification Cell3: Throughout, including without limitation Pages 10-12, Article V of Exhibit B (Intellectual Property) Intellectual Property Cell3: Page 68, Section 3.4.6 of the RFO (Binding Offer) Binding Offer Cell3: Page 68, Section 3.4.6 of the RFO (Binding Offer) Negotiations Cell3: Page 67-68, Section 3.4.4 of the RFO (Exceptions) Exceptions Cell3: Page 19

CAA-CPA-06

Contractor shall consult with the System Agency regarding unacceptable Contractor Personnel, remove and replace any personnel deemed unacceptable by the System Agency, at its sole discretion, within fourteen (14) Calendar Days of notification. Replacement personnel must have equal to, or greater qualifications relative to personnel being replaced - as determined by the System Agency at its sole discretion. Replacement personnel are subject to System Agency approval prior to any assignment.

Cell3: Page 20

CAA-CPA-010

Contractor shall provide résumés and references for the System Agency’s review and approval within fourteen (14) Calendar Days of notification of resignation for replacement of any Contractor Personnel during Design, Development, and Implementation (DDI) and Technical Management Services (TMS) projects.

Cell3: Page 22

CAA-DDI-02

Design, Development, and Implementation (DDI) Subdomain Contractor shall provide integration and release management approach to Transition releases and updates from the Contractor’s DEV, TEST, STAGING, and PROD environments to the System Agency’s electronic environment, DEV, TEST, STAGING and PROD environment. Refer to Exhibit M, Health Registries Process Guide V.4.0.

Cell3: Page 24

CAA-DDI-010

Contractor shall establish and maintain a Development (DEV) environment that mirrors the Austin Data Center (ADC) State Development environment. Refer to Exhibit M, Health Registries Process Guide V.4.0 for details.

Cell3: Page 31

CAA-TMS-056

Application Management/ Design

Contractor, to the fullest extent possible, shall comply with the Exhibit N, SERVICE MANAGEMENT MANUAL Enterprise Policies DCS RFO Language for the Maven platform that must be hosted and maintained within the DCS platform.

Cell3: Page 25

CAA-TMS-03

Application Data Management RFO TEXT: Contractor shall be able to archive historical data separately from active data sets due to storage constraints. This data shall be kept in accordance with HHSC data retention policy and human readable interpretation standards.

Cell3: Page 25

CAA-TMS-04

Application Data Management Cell3: Page 26

CAA-TMS-012

Application Data Management Contractor shall provide interfaces for data exchange to and from the Maven platform (e.g., Application Programming Interface (API), web services).

Cell3: Page 27

CAA-TMS-019

Application Data Management-Contractor shall have data extraction tools to support multi-dimensional analysis (using criteria from multiple data tables and multiple fields) for external analysis of the data within the Maven platform. The tool must accommodate the System Agency’s application development team.

Cell3: Page 29

CAA-TMS-033

Application Data Reporting Contractor shall facilitate the Maven platform data warehouse functionality (i.e., analysis, data manipulation, analytics, and trend reporting).

Cell3: Page 76

5.2.1 Domain & 5.2.2. Subdomain

Project Domains

a) headers and footers

b) requirement text

c) exhibits/figures/graphics

d) tables

a) section dividers

b) title page

c) table of contents

d) resumes

e) GANTT Chart

f) D&B report

g) Financial statements and supporting documents

h) All forms