The URL can be used to link to this page

Home My WebLink AboutAddendum 1 - RFP - 9973 Data Sharing and Consent ManagementAddendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 1 of 10 ADDENDUM NO. 1 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of RFP 9973 DATA SHARING AND CONSENT MANAGEMENT OPENING DATE: 3:00 PM (Our Clock) May 22, 2024 To all prospective bidders under the specifications and contract documents described above, the following changes/additions are hereby made and detailed in the following sections of this addendum: Exhibit 1 – Questions and Answers Please contact Dennis Ralph, Sr. Buyer, at (970) 221-6281 or dralph@fcgov.com with any questions regarding this addendum. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. Financial Services Purchasing Division 215 N. Mason St. 2nd Floor PO Box 580 Fort Collins, CO 80522 970.221.6775 970.221.6707 fcgov.com/purchasing Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 2 of 10 EXHIBIT 1 QUESTIONS AND ANSWERS 1. Can the city detail the format and cadence as well as how the service provider will receive utility data from the city? a. Will this be a monthly flat file transfer or direct API access? i. At present the City uses a daily flat file transfer for usage and a bimonthly flat file of customer data but may move to a daily direct access transfer in 2025 or thereafter. b. Can you provide a list of the data fields that will be provided to the service provider (i.e. account #, service address, meter #, consumption, demand, cost, etc.)? i. Current data fields are attached, although there may be updates possible in 2025 or thereafter. c. Is the utility data standardized to set time periods (i.e. monthly) or will the service provider be required to provide logic calculations to average consumption data over irregular time periods (i.e. irregular billing periods, quarterly, longer than standard 30-day monthly periods, etc.). i. 15-minute Utility interval usage is provided in a daily file containing the previous day’s usage. 2. Does the city have a target setup and annual budget for this scope of services? a. The City acknowledges that the transfer of existing data requests represents a one-time body of work that may be additional to the set up and annual budgets. The City will consider pricing as a part of the evaluation criteria. 3. What level of support does the city envision being provided to building owners by the service provider? Should we assume 9:00-5:00, Monday-Friday phone and email customer support? Does the city have a preferred response time target (i.e. 48hrs)? a. The City does not foresee a need for robust customer support, however requests proposed pathways to address technical queries associated with the solution itself (e.g., unexpected error messages). The City would review all solutions that provide a pathway to address technical errors or queries that customers might encounter (e.g., allowing customers to submit tickets on the public portal, etc.). The City’s expectation is a response to queries within 48 hours but does not have preferences regarding hours staffed by vendor. Standard communications associated with the status of data requests should be provided. 4. Can the city provide an estimate of the number of buildings or accounts that will be accessing the system? a. The City benchmarking ordinance requires transparency of building use for over 1400 commercial properties. In addition, contractors utilize the solution to request customer data; at present ~1100 residential customers have shared data. This number is anticipated to increase over time. Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 3 of 10 5. Is access only provided to business customers or will this include residential customer account access and support as well? a. Both residential and business customers will have access to the portal. At present we typically see business customers utilizing the solution for the purposes of our existing benchmarking ordinance and residential customer data shared with solar contractors. Residential customers have requested access to the portal for exporting their own data, and this utilization is anticipated to increase as it becomes available. 6. Who is the firm that currently provides the MyData portal? a. UtilityAPI 7. Of the features listed in the RFP Deliverables/Milestones section B, are any not currently available in the Portal that the City uses, and if so, can you please list them. a. Transfer of existing ongoing data shares to the new solution b. Summary of all third parties showing count of data access over timeframe, distinguishing subtotals by year or month in a long-duration period, distinguishing subtotals by type of 3rd party (ESPM, Solar Contractor, Solar Contractor that is Active in Participating Solar Contractor Network) c. Data errors and escalations/ support tickets d. Ability to change the presentation order on public-facing site e. Ability for residential customers to download their own data f. Ability for staff to edit or remove third party registrations g. Ability for any approved staff to access and aggregate multiple accounts when selecting sites to be included in the data request h. Ability to sort and filter all 3rd parties registered, and to retire / archive or delete inactive records of service providers or individual users within those organizations. 8. Will you consider a subcontractor to a Prime to provide the helpdesk services in 2e - “Provides user support by phone and/or online to aid customers in the use of the solution when needed.” a. The City currently provides Help Desk services in support of our existing benchmarking program. The City is open to considering proposals using subcontractors offering further customer support subject to Section II, F Subcontractors/Subconsultants in the RFP. The City does not foresee the need for a full Help Desk to aid in the use of the solution. The City would like to understand escalation pathways for customers who require technical troubleshooting in the use of the solution (see response to Question 3). 9. How many inquiries per year have been addressed by the current help desk for the platform? a. The current platform does not offer a full help desk. MyData vendor staff respond to customer queries directly related to the use of the solution via email. The City does not have a number of previous inquiries responded to by the vendor. Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 4 of 10 10. Do you have any preferences for diverse businesses as subcontractors or Service Providers? a. This RFP does not have a specific goal for participation by small and minority businesses, women’s business enterprises, or labor surplus area firms. However, the City encourages qualified small and minority businesses and women’s business enterprises to participate in the competitive process. The proposals will be evaluated based on the assessment criteria stated in Section IV of the RFP. Although there is not a specific goal for diverse businesses, the assessment criteria include consideration to a firm’s programs, initiatives, and hiring practices in support of equity, diversity, and inclusion. Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 5 of 10 Exhibit 1, b, i Data Fields Service Extract Field Index Data Element Description Valid Values/Format Sample Data 1 SDP_ID Service Delivery Point (SDP) business key reference 012345_678 2 SDP_Service Type of utility service provided at the Service Delivery Point (SDP) Electric Water Wastewater Stormwater Irrigation Internet NON-SERVICE CHARGES ELECTRIC 3 SDP_Latitude Latitude for Service Delivery Point (SDP), with a precision of 6 past the decimal ##.###### 38.840544 4 SDP_Longitude Longitude for Service Delivery Point (SDP), with a precision of 6 past the decimal ###.###### -105.0444233 5 SDP_InstallationDate Date Service first started at Service Delivery Point (SDP) Local MOUNTAIN time, with daylight savings observed YYYY-MM-DD 2020-02-28 6 SDP_ActivationDate Latest Service activation date at Service Delivery Point (SDP) for the current customer/account Local MOUNTAIN time, with daylight savings observed YYYY-MM-DD 2020-02-28 7 SDP_DeactivationDate Date that the service was deactivated for this associated customer/account. Local MOUNTAIN time, with daylight savings observed YYYY-MM-DD 2020-02-28 8 SDP_OccupantType Occupant type, left NULL if required fields missing for conditional OWNER RENTER VACANT NULL OWNER 9 SDP_MeterReadMethod Method for meter data use collection NULL would indicate the service is not metered MANUAL AUTO NULL AUTO 10 SDP_WaterAllotment Annual water allotment of water Service. Aligned with billing unit of measure (gallon). Null if a non-water service. 100000 11 SDP_TurnedOffNoPaymentD ate Date service turned off, if currently turned off for non-payment Local MOUNTAIN time, with daylight savings observed YYYY-MM-DD 2020-02-28 12 SDP_RemoteTurnOffFlag Flag to indicate if service has the capability to be turned-off/deactivated remotely N Y Y 13 SDP_NetMeteringFlag Flag to indicate if the service currently has net metering (i.e. solar PV) N Y Y Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 6 of 10 14 SDP_IrrigationOnlyFlag Flag to indicate if service is only used for outdoor landscape irrigation N Y Y 15 SDP_ChargeCode If available. Indicator of multiple billing factors or components. Currently based on Banner CIS, but could be adapted to utilize other future formats. E100 16 SDP_Flags Field for addition of entity flags Positi on Flag 1 Reserved for future Use 2 Reserved for future Use NULL 17 DEVICE_ID Device Reference, I.E. Meter/Inventory/Equipment Number - NULL permitted if non-metered service NULL 987654321 18 DEVICE_Type Meter type, used to flag differing meter capabilities (zigbee, etc.) The list of values is not finite, but rather possibilities/examples. NULL 25 35 120 170 A3_ILN AXRS4 D4SM REX REX 19 DEVICE_TypeDetail Meter size for water service, meter capacity for electric, not sure if equivalent data available for other services. The list of values is not finite, but rather possibilities/examples. 1 1/2" 1" 10" 2" Water - Flat 1" Water - Flat 3/4" 1-Phase-200 AMP 120/240V single-phase - 3 wire 3-Phase-200 AMP 3-Phase-Over 200 AMP 1 1/2" 20 DEVICE_Flags Field for addition of entity flags Positi on Flag 1 Reserved for future Use 2 Reserved for future Use NULL 21 PREMISE_ID Premise reference, group of one or more Service Delivery Point (SDP) by location (building, etc.) 01234 22 PREMISE_Type Indicate the type of service (and therefore customer receiving the service) RS = residential, CM = commercial, IN = Industrial RS CM IN CM Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 7 of 10 23 PREMISE_Subtype Further delineation of the PREMISE_Type, currently empty/blank for all. Previously planned detail: The values to the right generally align with Banner rate class (R, GS, GS50, etc.), but were modeled after the values from OSF. Some modifications were done from the base OSF values (removed “city own”, “primary”, etc.) SINGLE-FAMILY DUPLEX MULTI-FAMILY COMMERCIAL SMALL COMMERCIAL MEDIUM COMMERCIAL LARGE INDUSTRIAL SUBSTATION RENEWABLE FLOOD LIGHTING TRAFFIC LIGHTING ELECTRIC VEHICLE STATION SINGLE-FAMILY 24 PREMISE_Latitude Latitude for Premise, with a precision of 6 past the decimal ##.###### 38.840544 25 PREMISE_Longitude Longitude for Premise, with a precision of 6 past the decimal ###.###### -105.0444233 26 PREMISE_GISAddressID City GIS’s Address ID assigned to the premise 79740000 27 PREMISE_AddressStreet Full Premise Street Address 1600 PENNSYLVANIA AVE. 28 PREMISE_AddressCity Premise City FORT COLLINS 29 PREMISE_AddressState Premise State XX CO 30 PREMISE_AddressZip Premise Zip (5+4) when available, otherwise only first 5 ##### #####-#### 80525-1234 31 PREMISE_AddressCountry 2 Digit Code ISO 3166-1 Standard Alpha- 2 in which the Premise is located, assumed to be US but may not always be true US 32 PREMISE_ElectricHeatFlag Indicates if the premise has electric heat N Y Y 33 PREMISE_MedicalAssistanceF lag Identifies a premise as receiving medical assistance – those that receive support or billing discounts based on various medical factors, which may indicate either medical equipment or related needs that result in high consumption N Y Y 34 PREMISE_Flags Field for addition of entity flags Positi on Flag 1 Reserved for future Use 2 Reserved for future Use NULL 35 BILLINGACCOUNT_ID The Account identifier to which this Service Delivery Point (SDP) is billed. 098765-43210 36 BILLINGACCOUNT_AddressPr intName Billing address customer full name This will be a concatenation of the FIRST and LAST name JOHN ANDERSON Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 8 of 10 37 BILLINGACCOUNT_AddressLi neOne Billing address line 1 1600 PENNSYLVANIA AVE. 38 BILLINGACCOUNT_AddressLi neTwo Billing address line 2 NULL 39 BILLINGACCOUNT_AddressLi neThree Billing address line 3 NULL 40 BILLINGACCOUNT_AddressSt reet Billing street 41 BILLINGACCOUNT_AddressCi ty Billing city OCEANVIEW 42 BILLINGACCOUNT_AddressSt ate Billing state XX KS 43 BILLINGACCOUNT_AddressZi p Premise postal code (5+4) when available, otherwise only first 5 ##### #####-#### 12345-9876 44 BILLINGACCOUNT_AddressCo untry Billing Country (2 Digit Code using Iso 3166-1 Standard Alpha-2) US 45 BILLINGACCOUNT_DeliveryTy pe Method for bill delivery PAPER DIGITAL EBILL PAPER 46 BILLINGACCOUNT_Delinquen cyDate The date the Billing Account became delinquent, if currently delinquent for non-payment, according to billing’s standard definition for delinquency. Local MOUNTAIN time, with Daylight Savings Observed YYYY-MM-DD 2020-02-28 47 BILLINGACCOUNT_Flags Field for addition of entity flags Positi on Flag 1 Reserved for future Use 2 Reserved for future Use NULL 48 CUSTOMER_ID Customer associated with primary/billing/mailing Account 012345 49 CUSTOMER_BusinessName Name of the business, if the customer is a business Widgets Inc. 50 CUSTOMER_BusinessType Categorization of the customer’s business/functional type, defined by Utilities Customer Accounts – this field is a unique selection, only used if the customer is a business, currently empty/blank for all. FOOD SERVICE FOOD SALES HEALTHCARE INDUSTRIAL LODGING NURSERY/GREE NHOUSE OFFICE PUBLIC ASSEMBLY RELIGIOUS RETAIL RETAIL AUTO SERVICES STORAGE TRANSPORTATI ON UTILITY OTHER FOOD SERVICE Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 9 of 10 51 CUSTOMER_Name Full customer name - Concatenation of FIRST and LAST name JOHN ANDERSON 52 CUSTOMER_NameFirst Customer’s first name or the name of the commercial customer. JOHN 53 CUSTOMER_NameMiddle Customer middle initial. If commercial customer or middle initial is not known, this will be null. C 54 CUSTOMER_NameLast Customer’s last name. If commercial customer, this will be null. ANDERSON 55 CUSTOMER_PrimaryLanguag e Customer's primary language in ISO 639-1. EN is assumed if unknown. Field will not be null. ENG 56 CUSTOMER_PhoneNumberPr imary Three-digit area code for the primary phone number, with standard 3-4 US phone number, prioritizing either primary designated numbers if available, or most current - Prioritizing mobile numbers first ###-###-#### 512-555-1212 57 CUSTOMER_PhoneNumberPr imaryExtension Phone extension if known, otherwise NULL NULL 58 CUSTOMER_PhoneNumberSe condary Three-digit area code for the primary phone number, with standard 3-4 US phone number, if an additional number is available - Nullable ###-###-#### 512-555-1212 59 CUSTOMER_PhoneNumberSe condaryExtension Phone extension if known, otherwise NULL 1234 60 CUSTOMER_EmailVerified Billing email, OSF portal email, or other verified email for PII Prioritizing billing email, then billing portal email, then other verified email john.anderson@m yisp.com 61 CUSTOMER_EmailSecondary Additional, typically unverified email, for use in communications that exclude PII – Prioritizing most recent email first lynn.anderson@m yisp.com 62 CUSTOMER_KeyCustomerFla g Identifies a customer as critical to the Utility - defined by the Customer Accounts division of the Customer Connections service unit – whenever connecting with these customers, Customer Accounts should be notified/involved – these are typically customers with larger or multiple services N Y Y 63 CUSTOMER_IncomeQualified Flag Identifies a customer as being income qualified – those that receive support or billing discounts based on various income factors N Y Y 64 CUSTOMER_Flags Reserved for future use Positi on Flag 1 Future Use 2 Future Use NULL 65 BUILDING_ID Building identifier associated to the SDP, related using the GIS Address ID – FC#### FC5106 Addendum # 1 RFP 9973 DATA SHARING AND CONSENT MANAGEMENT Page 10 of 10 based on building footprint, maintained by City GIS 66 BUILDING_IDGroup Building Campus identifier associated to the Building – similar to BUILDING_ID, but groups multiple buildings – used for multi-family, universities, etc. – useful when parcel improvements and/or SDPs can’t be tied to a specific building, but instead a set of buildings FC#### FC1066 67 PROPERTY_ID The County Assessor parcel code that the SDP falls within – this may be different than the parcel(s) served by the SDP (rarely, an SDP serves multiple parcels) ########## 9725245101 Interval Usage Extract Field Index Data Element Description Valid Values/Format Sample Data 1 SDP_ID Service Delivery Point (SDP) business key reference 987654_321 2 PREMISE_ID Premise reference, group of one or more Service Delivery Point (SDP) by location (building, etc.) 110002 3 BILLINGACCOUNT_ID The Account identifier to which this Service Delivery Point (SDP) is billed. 987654321 4 METER_ID Reference for the specific meter 987654321 5 USAGE_ReadValidation Type of read, if valid or estimated A = Valid E = Estimate A E A 6 USAGE_ReadDateTime_UTC The date and time of the read, based on UTC This is interval ending, so 2:15am would contain the consumption from 2:00am to 2:15am. YYYY-MM-DD 24hh:mm:ss 2020-02-28 15:34:12 7 USAGE_ReadDateTime_Local The date and time of the read, based on GMT This is interval ending, so 2:15am would contain the consumption from 2:00am to 2:15am. YYYY-MM-DD 24hh:mm:ss 2020-02-28 15:34:12 8 USAGE_Consumption Metered consumption for the read date/time #####.#### 2.0425 9 USAGE_ConsumptionDirection Direction of metered consumption, either supplied to the customer (delivered), or received from the customer (received) D = Delivered R = Received D R D 10 USAGE_ConsumptionUnits Unit of measure associated with the consumption (kWh for electricity, gal for water, etc.) kWh gal kWh 11 USAGE_Flags Field for addition of entity flags Position Flag 1 Reserved for future Use 2 Reserved for future Use NULL