Indiana Department of Administration On On Behalf Of Of Indiana Department of Child Services, Child Support Bureau Request for Services 19-081 Design, Development, and Implementation of the INvest Child Support Automated System Pre-Proposal Conference April 25th, 2019 1:00 PM John E. Helmer IV IDOA Procurement 1
Agenda • General Information • Purpose of RFS • DDI Overview • Scope of Work • Term of the Contract • Key Dates • Business Proposal, Technical Proposal, Cost Proposal • Proposal Preparation & Evaluation • Minority and Women’s Business Enterprises (M/WBE) • Additional Information • Question and Answer Session 2
General Information • Sign-In Sheet for Attendees • Sign-In Sheet and PowerPoint will be posted on IDOA’s Solicitation Website • Hold questions until the end of the presentation – Attendees via the Webex or phone will need to submit all questions via the Question/Inquiry process outlined in Section 1.7 of the RFS. – Any verbal response is not considered binding; respondents are encouraged to submit any question formally in writing if it affects the proposal that will be submitted to the state. 3
General Information (cont.) • No questions will be taken today regarding the scope of work for this project. Today’s session is meant to cover process-related topics (i.e. how to fill out IDOA forms) • Any questions asked today along with any scope of work related questions should be submitted in writing per section 1.7 of the RFS to receive a formal response. 4
Purpose of the RFS • The overall purpose of this RFS is to ultimately select and contract with a qualified vendor that can satisfy CSB’s need for DDI services for the INvest Project. 5
DDI Overview It is the intent of CSB to contract with a vendor that can CSB requirements for the INvest Project are detailed in prove their abilities and experience in the following key the following chapters: areas: • • Title IV-D Program INvest Organizational Structure (Chapter 5) • • Technical knowledge and development of INvest Project Management (Chapter 6) • statewide child support enforcement systems INvest Core Functional Requirements (Chapter • Project management and systems development 7) • life cycle (SDLC) INvest Non-Core Functional Requirements • Enterprise solution architecture (Chapter 8) • • Hardware and software build out and integration INvest Technical Solution Requirements (Chapter • Data conversion 9) • • Implementation INvest Training and On-Site Support (Chapter 10) • • Training and on-site support INvest Implementation (Chapter 11) • • Supporting a State-led change management INvest Post Implementation (Chapter 12) • effort INvest Performance Standards (Chapter 13) • INvest Optional Service (Chapter 14) • Collaborating to work as “one team” throughout the life of a project 6
Scope of Work INvest should utilize API’s built and managed in the Mulesoft Anypoint Platform, be in a FedRAMP cloud environment, and meet all the technical, core and non-core requirements. 7
Term of the Contract • Contract Term – The term of the contract shall be for a period of three (3) years from the date of contract execution. There may be two (2) one-year renewals for a total of five (5) years at the State’s option. 8
Key Dates Activity Date Issue of RFS April 15, 2019 Pre-Proposal Conference April 25, 2019 Deadline to Submit Written Questions – Round One May 01, 2019 Response to Written Questions/RFS Amendments – Round One May 10, 2019 Deadline to Submit Written Questions – Round Two May 22, 2019 Response to Written Questions/RFS Amendments – Round Two May 31, 2019 Letter of Intent June 07, 2019 Submission of Proposals June 19, 2019 The d dates f for t the following a activities are t target dates o only. T These a activities m may b be c completed earlier or later t than the date s sho hown. n. Proposal Evaluation June through September Proposal Discussions/Clarifications (if necessary) TBD Oral Presentations (if necessary) August 2019 Best and Final Offers (if necessary) September 2019 RFS Award Recommendation September 2019 9
Business Proposal (Attachment E) • Company Financial Information (Section 2.3.3) – Confidential information must be kept separate from the proposal in the electronic copies. IDOA recommends sending a “public” file that has the confidential information redacted (may be in PDF format) and a “final” file that includes all required information (must be in format provided). • Contract Terms (Section 2.3.5) – Respondent should review the sample State contract (Attachment C) and note exceptions to State non-mandatory clauses in Business Proposal. The Respondent should accept the mandatory clauses in the Business Proposal and Transmittal Letter. • References (2.3.6) – The Respondent must include a list of at least three (3) clients for whom they have provided products and/or services that are the same or similar to those requested in this RFS. – The Subcontractors utilized must also include at least three (3) clients for whom they have provided services that are the same or similar to those services the Subcontractor will provide for this RFS. 10
Technical Proposal Response Template (Attachment F-1) • Please answer all questions we have provided for you in the Technical Proposal Response Template. • Your response should follow the structure outlined in the instructions. • If a question requests an example and the file is too large to insert within the response area, please attach the file and clearly indicate the requirement it belongs to and the file name of the example. • Respondents are discouraged from simply repeating language from the RFS as evidence of an understanding or capability. 11
Cost Proposal (Attachment D) • Cost Proposal Composition – Table of Contents – Total Cost Summary – Milestones – Software & Hardware – Rate Card – Optional Services – Cost Proposal Narrative – Cost Assumptions – Cost Savings Opportunities • Please complete the template provided for the Cost Proposal by populating ONLY the yellow shaded cells. 12
Recommend
More recommend
