CORE & MAIN LP (#2027021) - Laserfiche WebLink

RFP-2 – Scope of Work RFP# PWD 25.604 City of Pleasanton, CA RFP-2 | Page 2 Internal Use Only •Files shall be retained on the SFTP server for a minimum of 30 calendar days after successful retrieval by the receiving party, after which they may be purged. 2.3 SFTP Server Hosting and Management •CUS shall provision and manage the SFTP server. The server shall be hosted within the United States. •CUS shall provide the City with dedicated SFTP credentials and connection parameters (hostname, port, public key fingerprint) no later than 30 days prior to the start of data exchange testing. •CUS shall provide separate directory structures for City-to-CUS uploads and CUS-to-City downloads to prevent cross-contamination of file flows. 2.4 Availability •The SFTP server shall maintain 99.5% uptime availability, measured monthly. •CUS shall notify the City a minimum of 48 hours in advance of any planned maintenance that may affect SFTP availability. 3. CUS-to-City Daily Data Exchange Ref: CUS Exception 5 — CUS will post daily upload files to an SFTP site, allowing the Utility to use automation/scripting to retrieve required files and any other relevant files that need to be posted. 3.1 Posting Schedule •CUS shall post all daily files no later than 6:00 AM Pacific Time each business day, or as mutually agreed upon during project kick-off. •CUS shall confirm the daily posting schedule in writing during the project kick-off phase. 3.2 File Types CUS shall post the following daily files at a minimum (additional file types may be defined during kick-off): a.Work Order Status File: Current status of all open and completed work orders, including meter installation confirmations, field exceptions, and rescheduled appointments. b.Meter Inventory File: Updated meter serial numbers, endpoint IDs, and installation locations for all meters deployed or swapped during the prior day. c.Exception Report File: All field exceptions, access issues, customer refusals, and other non-standard conditions encountered during the prior day. d.Photo/Documentation Index: Index file referencing photos and field documentation captured, with linkage to work order numbers. 3.3 File Naming Convention All files shall follow a consistent naming convention to be defined by CUS and approved by the City. The naming convention shall include at a minimum: •File type identifier (e.g., WO_STATUS, METER_INV, EXCEPTION) •Date stamp in YYYYMMDD format •Sequence number for multiple files of the same type posted on the same day Example: PLEASANTON_WO_STATUS_20260501_001.csv 3.4 Monitoring and Alerting •CUS shall implement automated monitoring to detect failures in the daily file posting process. •If daily files are not posted by the scheduled time, CUS shall send an automated notification to City- designated contacts within one (1) hour of the missed posting window. Docusign Envelope ID: 6AD75F50-8A33-85A5-8039-9E3E1257A838Docusign Envelope ID: 177582DA-4F1C-8834-813C-BC4FD03AA45E