City of Seattle Request for Proposal # DIT-160063
Addendum
Dated: 03/30/2016
The following is additional information regarding Request for Proposal # DIT-160063, titled “IT Services Management (ITSM) Project Consultant Services for HEAT SaaS Tool Implementation” released on03/15/2016. Thedue date and time for responses will remain as04/08/2016 @ 2:00PM(Pacific). This addendum includes both questions from prospective proposers and the City’s answers, and revisions to the RFP. This addendum is hereby made part of the RFP and therefore, the information contained herein shall be taken into consideration when preparing and submitting a proposal.
Item # / Date Received / Date Answered / Vendor’s Question / City’s Answer / RFP Revisions1 / 3/24/16 / 3/30/16 / 8.2.1, What is meant by the Consultant "warranting and certifying that the installation has not degraded use of other Seattle ITs’ networks or computer systems"? We are not clear how "degraded" is defined in that context,nor sure that the Consultant would be able to assess Seattle's other networks or systems? / The spirit of this requirement is that the implementation of the HEAT SaaS tool does not negatively impact network performance and that the integrator will work with the City network team to resolve any network performance issues causes by the implementation of the HEAT SaaS tool. / None.
2 / 3/24/16 / 3/30/16 / 9.4, The RFP at 9.4 refers to a 'saas implementation certification'. Can you please confirm which issuing agency the City of Seattle is referring to? / We understand HEAT Software has certified HEAT SaaS partners that have been certified by HEAT to implement HEAT SaaS solutions. We expect HEAT to know who the qualified partners are. / None.
3 / 3/24/16 / 3/30/16 / Page 25 (Last Page), the RFP has an image that says "Insurance Requirements" and "City terms and conditions", but they are just an image. Please provide a copy of what City of Seattle meant to attach. /
/ None.
4 / 3/24/16 / 3/30/16 / Can the city delineate between the various phases of the project? What would be included in a first phase, second phase, e.t.c.? / Phase I (go live by 31-DEC-2016)
• Service Catalog and Self Service Portal
• Service Asset & Configuration Management (as needed to support incident and request management and including personal devices (i.e. desktops, laptops, phones))
• Request Fulfilment
• Incident Management
Phase II (go live by 31-DEC-2017)
• Change Management (Citywide – Q1 2017)
• Access Management
• Asset Management (for non-shared services, i.e., laptops)
• Change Management (departmental)
• Service Asset & Configuration Management (full implementation)
• Knowledge Management
• Problem Management
• Release and Deployment Management
• Service Level Management / None.
5 / 3/24/16 / 3/30/16 / Which integrations will be included with HEAT SM 2016? Can you please go into detail: which applications, one-way v. bi-directional data, forms, fields, e.t.c.? / We want all of the modules listed to be integrated in HEAT SM 2016 by the end of 2017. If some of the modules can be initially implemented in HEAT SM 2015 then migrated to HEAT SM 2016, that would be fine and the call of the Integrator. We expect the data for each of the modules to reside in the HEAT SM tool with integration with the modules listed in the RFP. As part of the integration, the data, forms and fields will be identified during the engineering and configuration of the tool. / None.
6 / 3/24/16 / 3/30/16 / 11.5 Proposed Project Methodology and Plan: does the project plan need to be in MS Project? / No, any format is fine. / None.
7 / Vendors that attended the mandatory pre-proposal conference and are eligible to respond to this RFP? / HEAT Software
PricewaterhouseCoopers / None.
Page 1 of 3