The file's text, extracted by GovTribe without its formatting.
ATTACHMENT C
To the RFR
BIDDER’S RESPONSE CHECKLIST
| Item Number |
| Name |
| Section of RFR in which referenced |
| Included in Bid? |
| 2 |
| General Response Narrative; Response to General Requirements of section 2, specifically: |
| 4.2.2 |
| 1) Category of submission |
| 2.1.1 |
| 2) Approach; Table 3 Bidder’s Approach |
| 2.1.1 |
| 3) Key Deliverables; Table 4 Bidder Key Deliverables |
| 2.1.1 |
| 5) Qualifications; Table 5 Bidder Qualifications |
| 2.1.1 |
| 8) Demonstration included in Bid. FOR WORKSTREAM #2 BIDDERS ONLY. Workstream #2, Bidders must include in their bid a link to a short video, slideshow or other visual presentation of the features, workflow and operations of their Third-Party ENS App or Third-Party Companion App. |
| 2.1.1 |
| 9) Miscellaneous. Details of any material governmental investigation pending against your firm, or any material ongoing or open audit or investigation by the Health Connector or any regulatory agency. |
| 2.1.1 |
| 3 |
| Bidder Background Submission Requirements |
| 4.2.3 |
| 4 |
| Project Experience |
| 4.2.4 |
| 5 |
| Business References, using Business References Form available at https://www.mass.gov/lists/osd-forms. |
| 4.2.5 |
| 6 |
| Proposed Strategy |
| 4.2.6 |
| 7 |
| Project Management |
| 4.2.7 |
| 8 |
| Initial Project Plan |
| 4.2.8 |
| 9 |
| Proposed MSA and SOW |
| 4.2.9 |
| 10 |
| Additional documentation. FOR WORKSTREAM #2 ONLY |
1. Data Privacy and Security standards met by the App;
2. Performance requirements and service levels, which should include service levels and the method by which the levels are measured;
3. Details of back up, data loss prevention, and disaster recovery;
4. A description of the process or mechanism and protocols used to securely transfer data files;
5. A Voluntary Product Accessibility Template (VPAT) for their proposed Third-Party ENS App.
6. Methodology and test results for prior tests conducted to assess the performance, privacy and security of the App.
7. Degree to which their App is “backwards compatible” with earlier versions of smartphones than the most current version.
8. Any performance standards (time lapse for key data access, etc.) that the Bidder has documented.
9. Whether or not the App has open APIs that will enable it to interoperate with a wide range of Commonwealth systems.
4.2.10
| 12 |
| Bidder’s Cost Response |
| 4.2.12 |
| 13 |
| Bidder’s Existing Agreements and Other Documentation |
| 4.2.13 |
| 14 |
| Bidder’s response checklist; check off documents included in the Bid in the “Included in Bid”’ column |
| 4.2.14 |
| 15 |
| Assumptions, Qualifiers and Constraints |
| 4.2.15 |
| 16 |
| Commonwealth Standard Forms |
1. Commonwealth Standard Contract Form
2. Commonwealth Terms and Conditions for Information Technology Contracts
3. Contractor Authorized Signatory Listing 4.2.16; 11, Appendix 4