HomeMy WebLinkAbout661511 ADVANCED CONTROL SYSTEMS INC - CONTRACT - RFP - 8790 ADVANCED DISTRIBUTION MANAGEMENT SYSTEMTASK ORDER
PURSUANT TO A MASTER AGREEMENT BETWEEN
THE CITY OF FORT COLLINS
AND
ADVANCED CONTROL SYSTEMS, INC.
TASK ORDER NUMBER: 1
PROJECT TITLE: ADMS BRII
ORIGINAL BID/RFP NUMBER & NAME: 8790 Advanced Distribution Management
System
MASTER AGREEMENT EFFECTIVE DATE: April 29, 2019
OWNER’S REPRESENTATIVE: Mike Margenau
TASK ORDER COMMENCEMENT DATE: May 8, 2019
TASK ORDER COMPLETION DATE: April 20, 2020
MAXIMUM FEE: (time and reimbursable direct costs): $649,300
PROJECT DESCRIPTION/SCOPE OF SERVICES: The City of Fort Collins Utilities (FCU),
Light and Power Operations (LPO) division is seeking to add an Advanced
Distribution Management System (ADMS) to manage its electric distribution
network. With this RFP, FCU seeks a state-of-the-art ADMS to improve the
management and control of the electric distribution system, outage
management, enhance distribution planning functions, optimize the
distribution system, and improve forecasting accuracy, among other
capabilities.
Service Provider agrees to perform the services identified above and on the attached forms in
accordance with the terms and conditions contained herein and in the Master Agreement between
the parties. In the event of a conflict between or ambiguity in the terms of the Master Agreement
and this Task Order (including the attached forms) the Master Agreement shall control.
The attached forms consisting of fifty-four (54) pages are hereby accepted and incorporated
herein, by this reference, and Notice to Proceed is hereby given after all parties have signed this
document.
SERVICE PROVIDER: ADVANCED CONTROL SYSTEMS, INC.
By: Date:
Name: Title:
Task Order 1 - 8790 Advanced Distribution Management System Page 1 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Dave Kuriger CFO
5/10/2019
OWNER’S ACCEPTANCE & EXECUTION:
This Task Order and the attached Contract Documents are hereby accepted and incorporated
herein by this reference.
ACCEPTANCE: Date:
Mike Margenau, Project Manager
REVIEWED: Date:
Pat Johnson, Senior Buyer
APPROVED AS TO FORM: Date:
Cyril Vidergar, Assistant City Attorney II
(if greater than $1,000,000)
ACCEPTANCE: Date:
Adam Bromley, Sr Manager, Electric Engineering
ACCEPTANCE: Date:
Tim McCullough, Deputy Director, Utilities
ACCEPTANCE: Date:
Kevin Gertig, Utilities Executive Director
(if greater than $1,000,000)
ACCEPTANCE: Date:
Gerry Paul, Purchasing Director
(if greater than $60,000)
ACCEPTANCE: Date:
Darin Atteberry, City Manager
(if greater than $1,000,000)
ATTEST: Date:
City Clerk
(if greater than $1,000,000)
Task Order 1 - 8790 Advanced Distribution Management System Page 2 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
5/10/2019
5/10/2019
5/13/2019
5/13/2019
5/13/2019
ATTACHMENT A
TASK ORDER SCOPE OF SERVICES
1. Description of the Services
The specific approach to deploying the ADMS and business processes will be determined
during the Design Release of the Project. To the extent that this approach is changed
(such that the scope of work changes), the parties will process a Change Order (in
accordance with the procedures described in the Master Services Agreement) to
document the impact on the Project and any adjustment to the project schedule due to the
revised approach to deploying the System. The Services will be performed, and
Deliverables will be provided in accordance with the specifications described herein, and
other specifications delivered by Fort Collins from time to time and agreed to by ACS.
The scope of work for the ADMS Project includes all planning, execution, implementation,
and training for an ADMS for Fort Collins. Each stage of the Project will require approval
from the Fort Collins Project Manager before moving on to the next stage. Specific
Deliverables and milestones are set out in the Project Schedule.
PRISM supports various interfaces to Enterprise wide systems. This capability includes the
ability to consume the payload from the ESB data service for various purposes.
All interfaces will be deployed as a standard Multispeak interface from ACS to the ESB,
with the exception of GIS. The PRISM interface to the Graphical Information System will
be a direct connection and not via the ESB data service.
The ACS ADMS will interface to the current/existing Fort Collins SCADA system via OPC
for exchange of status points.
The interface servers to allow the integration of the external systems with the PRISM
ADMS will be located in the demilitarized zone server (DMZ).
As part of the ADMS Project, ACS is responsible for providing Services throughout various
stages of the Project. The following is a high-level list of Deliverables/Services required for
the successful completion of the Project:
1.1 Kick Off Meeting
1.2 Project Scope of Work definition
1.3 Project work plan (minimum contents):
1.4 Project Scope
1.5 Project RACI chart
1.6 Project Requirement Traceability Matrix
1.7 Project Schedule
1.8 Project Approach
1.9 Test Plan
1.10 Communications Plan
1.11 Training
1.12 Project Conclusion
1.13 Submittal and maintenance of Project Schedule
1.14 Tracking of all project correspondence
1.15 Regular touchpoint conference calls with ACS Project Manager, frequency to be
determined
1.16 Submittal and tracking of all required project documentation
1.17 Project meetings and weekly progress reports, in a format that is mutually agreed
1.18 Coordination of all ACS testing activities
1.19 Coordination of all ACS commissioning activities
Task Order 1 - 8790 Advanced Distribution Management System Page 3 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
1.20 Define all requirements for external interfaces to the PRISM system, including but
not limited to:
• CIS – Customer Information System
• GIS – Geographic Information System
• AMI – Automatic Metering Infrastructure System
• Call Net after hours call taking (IVR interface)
• SCADA interface (OPC)
1.21 System Design Services
1.22 System Architectural Drawings
1.23 ACS Project Management Services
1.24 System Integration and Configuration Services
1.25 Redundant Configuration of the PRISM ADMS solution
1.26 Pre-Factory Acceptance Test (pre-FAT) performed in Norcross, GA by ACS
personnel in preparation of Factory Acceptance Testing
1.27 The ACS Project Manager will provide Fort Collins with a copy of the Factory
Acceptance Test procedures one month prior to the scheduled test for approval.
Fort Collins will need to provide approval of, or requested modifications to, the FAT
procedures two weeks prior to the scheduled test. This will allow time for changes
to be made, and the approved procedures to be executed during the system pre-
FAT.
1.28 Customer-Witnessed Factory Acceptance Testing (FAT)
1.29 ACS system engineering review of GIS data (prior to import)
1.30 Model building labor for Distribution Stations and Feeders (Qty. to be determined)
1.31 Reports Design (for all Feeders)
1.32 Onsite workshops (OMS, Business Process, Interfaces, Model Building)
1.33 Onsite installation/commissioning
1.34 Site Acceptance Testing (SAT)
1.35 The SAT will be performed by Fort Collins with ACS providing supervision during
the test.
1.36 The SAT will be conducted using the procedures outlined in the Factory
Acceptance Test and can include additional tests if needed.
1.37 System Go Live
1.38 Post Go Live Support
1.39 On-Site training for Fort Collins designated personnel. There is no limit to the
number of student attendees so long as the number does not require ACS to
provide additional classes that would increase the required man weeks of work
planned in the project schedule
1.40 DASmap GIS import training using the installed system on-Site.
1.41 Call-taker training using the installed system on-Site.
1.42 ADMS system operator training using the installed system on-Site.
1.43 ADMS system administrator and reports training
Task Order 1 - 8790 Advanced Distribution Management System Page 4 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
1.44 ACS will provide printed training materials for each training course provided and
will customize on-site training for each application based on Fort Collins specific
needs. The ACS Project Manager will meet with Fort Collins to review the
proposed training and refine it as needed based on Fort Collins specific needs.
1.45 Send training documentation prior to training (electronic and hard copies)
1.46 ADMS project closure
1.47 Project closeout document
Configuration of Fort Collins networking devices, such as firewalls and other peripherals
as required, is out of scope for ACS. ACS can provide recommendations on best practice
configurations.
2. System Hardware and Software
2.1 System Hardware
The following hardware specifications are provided for information only.
Item Qty. Description
1
4
Fort Collins
Supplied
PRISM SCADA Master
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
2
4
Fort Collins
Supplied
Application Server
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
3
4
Fort Collins
Supplied
Historian/DASdb
128 GB (4 x 32GB) RDIMM DDR4-2666 Memory
3.6 TB (6 x 600GB) 12G 15K SAS SFF SC DS HDD
4
4
Fort Collins
Supplied
OMS GUI
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
5
4
Fort Collins
Supplied
IdM
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
6
1
Fort Collins
Supplied
Training Simulator Server
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
7
1
Fort Collins
Supplied
Item Qty. Description
Fort Collins
Supplied
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
10
1
Fort Collins
Supplied
FSFO Monitor Workstation
32GB (4 x 8GB) DDR4-2666 Memory
1.2 TB (2 x 600GB) 15k SAS SFF disk drives
11
1
Fort Collins
Supplied
DASmap PC
32GB (4 x 8GB) DDR4-2666 Memory
2TB 6G SATA HDD
12
3
1
4
ACS
Supplied
Network Equipment
ACS VPN Diagnostic Router
Cisco ASA 5506 Firewall Router
HP Aruba 2920-24G Network Switch
2.2 System Software
2.2.1 Business Release II – ADMS I (OMS)
The following software will be supplied with Business Release II:
2.2.1.1 Production Environment
Item Qty. Description
13
1
1
2
1
2
2
1
1
1
1
1
1
1
2
1
1
PRISM Software
PRISM Master Server-based License
PRISM Master Redundant System License
DNPnet Network Communication Protocol
Distributed Database/OI Architecture – System
License
Distributed Database/OI Architecture – Client
License
Single Sign-On Authentication
RTDB Tools/Java-based GUI
Item Qty. Description
1
10
10
1
40
1
40
1
40
GridVu Network Server Base License
GridVu Network – Annual User License
GridVu Network – Disaster User License
POWR Mobile Base License
POWR Mobile – Annual User License
POWR Survey Base License
POWR Survey – Annual User License
POWR Switch Base License
POWR Switch – Annual User License
15
1
1
1
1
1
1
1
OMS Software
PRISM OMS Electrical Base with Trouble Call
Analysis
Base OMS Reports for 10 Users
PRISM OMS Work Order Management
PRISM OMS Enhanced IVR
PRIMS OMS AVL
PRISM OMS Crew Call Out
PRISM OMS System Alerts
16
1
1
1
1
1
DMS Software
3-Phase Unbalanced Distribution Power Flow
SwitchPlan
Short Circuit Analysis
Outage Scheduler
Load Estimator
17
1
14
1
3rd Party Software
VMware Virtualization Software
Red Hat Enterprise Linux Version 7
Windows OS Server Edition
2.2.1.2 Development Environment
Item Qty. Description
18
1
Item Qty. Description
19
1
1
1
1
Visual Software
ReShape
Redline
Topology Processor
DASdb
20
1
1
1
1
1
1
1
OMS Software
PRISM OMS Electrical Base with Trouble Call Analysis
Base OMS Reports for 10 Users
PRISM OMS Work Order Management
PRISM OMS Enhanced IVR
PRIMS OMS AVL
PRISM OMS Crew Call Out
PRISM OMS System Alerts
21
1
1
1
1
1
DMS Software
3-Phase Unbalanced Distribution Power Flow
SwitchPlan
Short Circuit Analysis
Outage Scheduler
Load Estimator
22 1
5
3rd Party Software
VMware Virtualization Software
Red Hat Enterprise Linux Version 7
2.2.1.3 Quality Assurance Environment
Item Qty. Description
23
1
1
1
1
1
1
1
1
1
1
1
1
1
Item Qty. Description
1
1
PRISM OMS Crew Call Out
PRISM OMS System Alerts
26
1
1
1
1
1
DMS Software
3-Phase Unbalanced Distribution Power Flow
SwitchPlan
Short Circuit Analysis
Outage Scheduler
Load Estimator
27 1
5
3rd Party Software
VMware Virtualization Software
Red Hat Enterprise Linux Version 7
2.2.1.4 Training Environment
Item Qty. Description
28 1
1
PRISM Software
XpertSim Training Simulator
PRISM Base Historian
29
1
3rd Party Software
Red Hat Enterprise Linux Version 7
2.3 Equipment Hardware and Configuration
Reference the System Deliverables by Release as described in Tables 2.2.1.1
through 2.2.1.4, above, required for ADMS Business Release II SOW.
Additionally, ACS may provide the following equipment, to be determined during
the course of Task Order 1.
• VPN Routers
Fort Collins is responsible for supplying the following equipment, unless otherwise
specified:
• All networking hardware including any necessary firewalls
• All computer hardware including the Blade server environment and
operator/dispatcher workstations
By no later than the completion of this Task Order, or at the earlier request of the
Fort Collins, ACS will return all personal property of Fort Collins in its possession
including, without limitation, any Fort Collins-owned equipment, and all originals and
any copies of all disks, tapes, files, correspondence, notes and other documents (the
“Fort Collins Property”). The Fort Collins Property will be in substantially the same
condition as when provided to ACS, reasonable wear and tear excluded.
2.4 Additional Specifications
ACS and ACS Personnel will adhere to all specifications provided to ACS by Fort
Collins from time-to-time and all specifications prepared by ACS and approved by
Fort Collins.
Task Order 1 - 8790 Advanced Distribution Management System Page 9 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
2.5 Assumptions
The following are general assumptions and exclusions that have been incorporated
into this Statement of Work:
2.5.1 All Documentation Deliverables will be provided in electronic form, unless
otherwise expressly agreed by the parties.
2.5.2 ACS is responsible for any Deliverable that fails during implementation.
2.5.3 ACS must ensure that all necessary permits, authorizations and approvals
have been secured in order that Services as set forth in this Statement of
Work can proceed.
2.5.4 ACS Personnel attending on-site will adhere to all Fort Collins internal
practices and procedures and will comply with Fort Collins’ information
security policies then in effect.
3. ROLES & RESPONSIBILITIES
3.1 Fort Collins Roles and Responsibilities
The following are the general roles and responsibilities for Fort Collins during the
project and encompass what is expected during Business Release II:
o Participate in all planned meetings and ensure that proper personnel are in
attendance dependent on the topic(s) to be discussed;
o Provide information and data as required for ACS to perform its
responsibilities;
o Respond to ACS requests for assistance and/or clarification on Fort Collins
supplied documentation in the time frame agreed;
o Provide a knowledgeable GIS staff that can quickly answer questions and
make corrections to the source GIS database when needed;
o Take training as may be specified and/or offered by ACS, including
participating in workshops, and providing instructions to ACS to enable
proper configuration of baseline system functionality;
o Provide office and other workspace, including phone and high-speed internet
connectivity for ACS personnel while at Fort Collins;
o Provide other assistance as may be reasonably requested by ACS during any
on-site work;
o Provide any hardware, third-party software and other materials as may be
defined as provided by Fort Collins;
o Provide any configuration or programming of Fort Collins supplied equipment
such as Firewalls, Routers or other networking equipment;
o Participate in factory testing as defined in the project;
o Receive and locate the various system hardware when shipped from ACS;
o Assist ACS in installing the systems at Fort Collins;
o Provide communications via VPN connection from ACS to the systems at
each physical location, including connectivity through any firewall or security
device required and installed by Fort Collins for such connections;
o Conduct Site Acceptance Testing with ACS assistance as defined in the
project;
o Provide the necessary technical and analytical resources to support the
various project tasks and activities;
Task Order 1 - 8790 Advanced Distribution Management System Page 10 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
o Perform point-to-point verification of the accuracy of the SCADA database to
the extent deemed appropriate by Fort Collins, and certify to ACS that the
database is accurate and complete;
o Provide other services as may reasonably be requested by the ACS project
manager.
3.2 ACS Roles and Responsibilities
The following are the roles and responsibilities of ACS for the Project.
o Schedule, host and minute all project meetings, including any necessary
design meetings;
o Participate in all planned meetings and ensure that proper personnel are in
attendance dependent on the topic(s) to be discussed;
o Provide information and data as required for Fort Collins to perform its
responsibilities;
o Respond to Fort Collins requests for assistance and/or clarification on ACS
supplied documentation in the time frame agreed;
o Provide training as specified in the project;
o Provide office and other workspace, including phone and high-speed
internet connectivity for Fort Collins personnel while at ACS;
o Provide other assistance as may be reasonably requested by Fort Collins
during any on-site work;
o Provide hardware, third-party software and other materials as may be
defined as provided by ACS;
o Develop additional functionality as may be required to meet the agreed upon
requirements per the attached Attachment C;
o Install all interconnecting cabling between hardware provided by ACS as
part of the scope of this contract;
o Stage the hardware in the ACS factory and provide all necessary
interconnections for power and communications;
o Test the various systems and prepare them for FAT;
o Provide Fort Collins with assistance during FAT;
o Pack, ship and install the systems at Fort Collins;
o Perform testing to verify proper operation of the systems after installation;
o Assist Fort Collins in Site Acceptance Tests;
o Provide the necessary technical and analytical resources to support the
various project tasks and activities;
o Perform other services as may reasonably be requested by the Fort Collins
project manager.
4. Project Schedule:
ACS shall complete the Services in accordance with the project schedule mutually agreed to
by the parties (“Project Schedule”). A preliminary detailed project schedule is provided below.
Task Order 1 - 8790 Advanced Distribution Management System Page 11 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Task Name Duration Start Finish
ADMS Project Schedule 236 days Wed 5/8/19 Wed 5/8/19
ADMS {Release 2} 236 days Wed 5/8/19 Mon 4/20/20
Project Initiation 4 days Wed 5/8/19 Mon 5/13/19
Project Award/Receipt of PO from Fort Collins 1 day Wed 5/8/19 Wed 5/8/19
Order Processing 2 days Thu 5/9/19 Fri 5/10/19
Assignment to PM 1 day Mon 5/13/19 Mon 5/13/19
Project Planning 79 days Thu 5/9/19 Tue 8/27/19
ACS Internal Kickoff Meeting 1 day Tue 5/14/19 Tue 5/14/19
ACS Review of DSOW Detailed Scope of Work 2 days Wed 5/15/19 Thu 5/16/19
ACS-Fort Collins Kickoff Meeting (Remote) 1 day Fri 5/17/19 Fri 5/17/19
ACS Procurement Activities for System Equipment 9 days Wed 5/15/19 Mon 5/27/19
Place order for VPN Router 1 day Wed 5/15/19 Wed 5/15/19
Place order for all hardware in ACS scope 1 day Wed 5/15/19 Wed 5/15/19
Receive VPN Router at ACS Factory 1 day Mon 5/27/19 Mon 5/27/19
Secure Red Hat Enterprise Linux licenses 1 day Wed 5/15/19 Wed 5/15/19
Secure Microsoft Windows licenses 7 days Wed 5/15/19 Thu 5/23/19
Fort Collins Procurement Activities 65 days Thu 5/9/19 Wed 8/7/19
Fort Collins finalizes environment locations 1 day Thu 5/9/19 Thu 5/9/19
Fort Collins finalizes hardware architecture 1 day Fri 5/31/19 Fri 5/31/19
Fort Collins procures system server and workstation
equipment
40 days Mon 6/10/19 Fri 8/2/19
Fort Collins procures additional networking
equipment
20 days Mon 6/10/19 Fri 7/5/19
Fort Collins procures mobile devices for POWR
application
40 days Thu 6/13/19 Wed 8/7/19
Define CIS Configuration Details 47 days Wed 5/22/19 Thu 7/25/19
Remote CIS Interface Meeting 1 day Wed 5/22/19 Wed 5/22/19
Provide CIS configuration details document for
completion
1 day Thu 5/23/19 Thu 5/23/19
Return CIS configuration details document 15 days Fri 5/24/19 Thu 6/13/19
Task Order 1 - 8790 Advanced Distribution Management System Page 12 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
ACS Compiles CIS Design Documentation 10 days Fri 6/14/19 Thu 6/27/19
Fort Collins reviews CIS Design Documentation 10 days Fri 6/28/19 Thu 7/11/19
ACS incorporate Fort Collins feedback and resubmits
CIS Design Documentation
5 days Fri 7/12/19 Fri 7/12/19
Fort Collins approves CIS Design Documentation 5 days Fri 7/19/19 Thu 7/25/19
Define OMS Configuration Details 61 days Tue 6/4/19 Tue 8/27/19
Send eAlarm Requirements Document 1 day Mon 6/17/19 Mon 6/17/19
Send POWR Requirements Document 1 day Mon 6/17/19 Mon 6/17/19
Project Execution 151 days Mon 5/20/19 Thu 1/2/20
Receive scoped hardware at ACS Factory 1 day Mon 6/17/19 Mon 6/17/19
ACS provides detailed system architecture drawings
per CC location
3 days Mon 6/3/19 Wed 6/5/19
Fort Collins reviews and approves architecture
drawings
1 day Thu 6/20/19 Thu 6/20/19
Fort Collins Equipment Staging 20 days Mon 8/5/19 Fri 8/30/19
Fort Collins installs, racks and powers server
equipment
3 wks Mon 8/5/19 Fri 8/23/19
Fort Collins provides link for remote ACS access 1 wk Mon 8/5/19 Fri 8/9/19
Fort Collins installs and powers workstations 1 wk Mon 8/26/19 Fri 8/30/19
Baseload PRISM, Historian, Workstations (per
environment)
10 days Mon 8/26/19 Fri 9/6/19
PRISM OMS RT Platform 1 wk Mon 8/26/19 Fri 8/30/19
Historian (Oracle) 1 wk Mon 8/26/19 Fri 8/30/19
Workstations 1 wk Mon 9/2/19 Fri 9/6/19
Baseload OMS Servers 15 days Mon 9/9/19 Fri 9/27/19
OMS Production 15 days Mon 9/9/19 Fri 9/27/19
OMS Backup 15 days Mon 9/9/19 Fri 9/27/19
Baseload Portal and Interface Servers (per
environment)
18 days Mon 9/30/19 Wed 10/23/19
Reporter (PORTAL) 5 days Mon 9/30/19 Fri 10/4/19
Interface Server 5 days Mon 10/7/19 Fri 10/11/19
Authentication Server 8 days Mon 10/14/19 Wed 10/23/19
Task Order 1 - 8790 Advanced Distribution Management System Page 13 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Validate Baseload Configuration 10 days Thu 10/24/19 Wed 11/6/19
Load RT-OMS Software applications 10 days Thu 11/7/19 Wed 11/20/19
ESRI Interface/DASmap Model Building 129 days Mon 5/20/19 Thu 11/14/19
Build views in GIS data per provided information 61 days Mon 5/20/19 Mon 8/12/19
Provide symbology and sizing desired from GIS 1 day Mon 5/20/19 Mon 5/20/19
ACS reviews and finalizes GIS items 10 days Tue 5/21/19 Mon 6/3/19
Provide a list of GIS items needed (symbols,
background items, etc..)
1 day Tue 6/4/19 Tue 6/4/19
Fort Collins reviews and finalizes symbology 10 days Wed 6/5/19 Tue 6/18/19
Build the symbology in PRISM DB 7 days Wed 6/19/19 Thu 6/27/19
Provide DAS to RTDB spreadsheet for completion 1 day Fri 6/28/19 Fri 6/28/19
Fort Collins reviews, updates and finalizes RTDB
spreadsheet
5 days Tue 7/2/19 Mon 7/8/19
Provide 1st GIS export file for analysis 1 day Mon 7/1/19 Mon 7/1/19
1st Iteration: GIS data analysis. Provide Report of
Geometry/Connectivity issues (Provided by ACS)
15 days Tue 7/2/19 Mon 7/22/19
1st Iteration: Resolve the reported items from the
issue list to be provided as a result of the GIS data
analysis, and provide new GIS data
15 days Tue 7/23/19 Mon 8/12/19
Configure Import Tool (2nd Iteration) 27 days Tue 8/27/19 Wed 10/2/19
Provide 2nd GIS Export file for analysis 1 day Tue 8/27/19 Tue 8/27/19
2nd Iteration: GIS data analysis. Provide Report of
Geometry/Connectivity issues (Provided by ACS)
10 days Wed 8/28/19 Tue 9/10/19
2nd Iteration: Resolve the reported items from the
issue list to be provided as a result of the GIS data
analysis, and provide new GIS data
10 days Wed 9/11/19 Tue 9/24/19
Install preliminary topology model on OMS system 4 days Wed 9/25/19 Mon 9/30/19
Onsite Trip to present working DASmap/PRISM
model
2 days Tue 10/1/19 Wed 10/2/19
Configure Import Tool (3rd Iteration) 21 days Thu 10/17/19 Thu 11/14/19
Provide 3rd GIS Export file for analysis 1 day Thu 10/17/19 Thu 10/17/19
Task Order 1 - 8790 Advanced Distribution Management System Page 14 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
3rd Iteration: GIS data analysis. Provide Report of
Geometry/Connectivity issues (Provided by ACS)
5 days Fri 10/18/19 Thu 10/24/19
Make the changes as result of onsite modeling
workshop
5 days Fri 10/25/19 Thu 10/31/19
3rd Iteration: Resolve the reported items from the
issue list to be provided as a result of the GIS data
analysis, and provide new GIS data
5 days Fri 11/1/19 Thu 11/7/19
Finalize ESRI import tool and import DB into
DASMAP
5 days Fri 11/8/19 Thu 11/14/19
Freeze DASmap Model for FAT 0 days Thu 11/14/19 Thu 11/14/19
GridVu Design & Configuration 16 days Wed 8/28/19 Wed 9/18/19
Send Request for Gridvu Configuration Details 1 day Wed 8/28/19 Wed 8/28/19
Fort Collins provides banner and disclaimer wording
for Gridvu
1 day Thu 8/29/19 Thu 8/29/19
Determine hosting platform (internal vs. AWS) 3 days Thu 8/29/19 Mon 9/2/19
Fort Collins returns configuration details 10 days Thu 8/29/19 Wed 9/11/19
ACS completes configuration per specs 5 days Thu 9/12/19 Wed 9/18/19
CIS Interface - Configuration 23 days Wed 8/7/19 Fri 9/6/19
Fort Collins to provide full CIS data 5 days Wed 8/7/19 Tue 8/13/19
ACS to verify full CIS DB 10 days Wed 8/14/19 Tue 8/27/19
CIS DB import complete 0 days Tue 8/27/19 Tue 8/27/19
CIS-OMS Interface Development 8 days Wed 8/28/19 Fri 9/6/19
Fort Collins configures internal network 20 days Mon 7/8/19 Fri 8/2/19c
OPC - SCADA Interface Design 42 days Wed 6/12/19 Thu 8/8/19
OCP Interface Design 26 days Wed 6/12/19 Wed 7/17/19
Initial OCP Solution Meeting 1 day Wed 6/12/19 Wed 6/12/19
Provide OCP Point List 5 days Thu 6/13/19 Wed 6/19/19
Provide OCP Solution Design Documentation 1 wk Thu 6/20/19 Wed 6/26/19
Approve OCP Design Documentation 1 wk Thu 6/27/19 Wed 7/3/19
PRISM DB Pseudo-point creation 2 wks Thu 7/4/19 Wed 7/17/19
OCP - SCADA Interface Conceptual Test 6 days Thu 7/18/19 Thu 7/25/19
Task Order 1 - 8790 Advanced Distribution Management System Page 15 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Configure Vendor-ACS OCP Link 1 wk Thu 7/18/19 Wed 7/24/19
Fort Collins to provide OCP remote connection
information
1 day Thu 7/25/19 Thu 7/25/19
OCP - SCADA Interface - Configuration 10 days Fri 7/26/19 Thu 8/8/19
OCP Installation and Configuration 2 wks Fri 7/26/19 Thu 8/8/19
CallNet - OMS Interface 47 days Mon 6/3/19 Tue 8/6/19
CallNet Interface Design 47 days Mon 6/3/19 Tue 8/6/19
Remote CallNet Interface Meeting 1 day Mon 6/3/19 Mon 6/3/19
Provide CallNet configuration details document for
completion
1 day Tue 6/4/19 Tue 6/4/19
Return CallNet configuration details document 15 days Wed 6/5/19 Tue 6/25/19
ACS Compiles CallNet Design Documentation 10 days Wed 6/26/19 Tue 7/9/19
Fort Collins reviews CallNet Design Documentation 10 days Wed 7/10/19 Tue 7/23/19
ACS incorporate Fort Collins feedback and
resubmits CallNet Design Documentation
5 days Wed 7/24/19 Tue 7/30/19
Fort Collins approves CallNet Design
Documentation
5 days Wed 7/31/19 Tue 8/6/19
Integrate OMS 18 days Thu 11/21/19 Thu 1/2/20
Integrate the DASmap model into the system 5 days Thu 11/21/19 Wed 12/4/19
Import CIS data dump and integrate into the OMS
system
8 days Thu 12/5/19 Mon 12/16/19
Configure OMS per Fort Collins requirements 5 days Tue 12/17/19 Thu 1/2/20
POWR Mobile 31 days Tue 6/18/19 Tue 7/30/19
ACS request Fort Collins' crew makeup 1 day Tue 6/18/19 Tue 6/18/19
Fort Collins Supplies crew makeup (for auto
population)
15 days Wed 6/19/19 Tue 7/9/19
ACS application configuration 10 days Wed 7/10/19 Tue 7/23/19
ACS application installation 5 days Wed 7/24/19 Tue 7/30/19
Upload Fort Collins DASdb from GIS model and load
DASmap Applications
20 days Fri 11/15/19 Thu 12/19/19
Switch Order Management 2.5 days Fri 11/15/19 Tue 11/19/19
Task Order 1 - 8790 Advanced Distribution Management System Page 16 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
GridVu Public 2.5 days Tue 11/19/19 Thu 11/21/19
GridVu Network 2.5 days Fri 11/22/19 Tue 12/3/19
RedLine (cuts) 2.5 days Tue 12/3/19 Thu 12/5/19
ReShape (schematic diagram) 2.5 days Fri 12/6/19 Tue 12/10/19
Set up GOI users 2.5 days Tue 12/10/19 Thu 12/12/19
ePRISM 2.5 days Fri 12/13/19 Tue 12/17/19
eAlarm 2.5 days Tue 12/17/19 Thu 12/19/19
Project Testing 171 days Mon 6/17/19 Thu 2/27/20
Prepare FAT Documents for System Testing (OMS,
GridVu, POWR)
36 days Mon 6/17/19 Mon 8/5/19
Create test scenarios for FAT 2 wks Mon 6/17/19 Fri 6/28/19
Submit FAT procedures to Fort Collins for review and
approval
1 day Mon 7/1/19 Mon 7/1/19
Fort Collins to review and approve FAT procedures 20 days Tue 7/2/19 Mon 7/29/19
ACS finalizes FAT procedures 5 days Tue 7/30/19 Mon 8/5/19
Perform ACS Internal Pre-FAT 15 days Tue 12/17/19 Thu 1/16/20
Integrated Testing of SCADA/OMS System 5 days Tue 12/17/19 Thu 1/2/20
Pre-FAT 5 days Fri 1/3/20 Thu 1/9/20
Pre-FAT variance cleanup 5 days Fri 1/10/20 Thu 1/16/20
Perform FAT 20 days Fri 1/17/20 Thu 2/13/20
FAT 10 days Fri 1/17/20 Thu 1/30/20
Post FAT Variance Cleanup and ACS System
Checkout
10 days Fri 1/31/20 Thu 2/13/20
Prepare System for Onsite SAT 20 days Fri 1/31/20 Thu 2/27/20
ACS provides SAT procedure 1 day Fri 1/31/20 Fri 1/31/20
Fort Collins to provide feedback on modifications
needed for SAT procedures if needed no later than
3 weeks prior to SAT
1 wk Mon 2/3/20 Fri 2/7/20
ACS duplicates tested production environment to
Disaster, QA, Test and Training
2 wks Fri 2/14/20 Thu 2/27/20
System Training 14 days Tue 3/3/20 Thu 3/19/20
Task Order 1 - 8790 Advanced Distribution Management System Page 17 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Linux PRISM Fundamentals Training 3 days Tue 3/3/20 Thu 3/5/20
OMS Call Taker Training 3 days Tue 3/3/20 Thu 3/5/20
OMS Operator Training Shift 1 4 days Tue 3/10/20 Fri 3/13/20
OMS Operator Training Shift 2 4 days Mon 3/16/20 Thu 3/19/20
OMS Admin Training 3 days Tue 3/17/20 Thu 3/19/20
DASMap Training 4 days Tue 3/10/20 Fri 3/13/20
Perform Onsite SAT and System Commissioning 5 days Fri 3/20/20 Thu 3/26/20
Onsite OMS SAT 5 days Fri 3/20/20 Thu 3/26/20
OMS & POWR Mobile GO LIVE 9 days Fri 3/27/20 Wed 4/8/20
System Go-Live 1 day Fri 3/27/20 Fri 3/27/20
Onsite Go-Live Support 5 days Mon 3/30/20 Fri 4/3/20
Go-Live System Training 3 days Mon 4/6/20 Wed 4/8/20
PORTAL Enterprise Reporting Training 3 days Mon 4/6/20 Wed 4/8/20
Business Release 2 Closeout 8 days Thu 4/9/20 Mon 4/20/20
ACS sends Project Customer Acceptance Form 1 day Thu 4/9/20 Thu 4/9/20
Fort Collins returns signed Project Customer
Acceptance Form
2 days Fri 4/17/20 Mon 4/20/20
Task Order 1 - 8790 Advanced Distribution Management System Page 18 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
5. TASK ORDER COST DETAIL
5.1 Base Pricing
Pricing based on Table of Compliance Attachment A
Pricing Total
Software Services BR Total
BR II $266,216 $383,084 $649,300
5.2 Software Pricing
SOFTWARE PRICING BREAKOUT
Software Module Pricing
PRISM Base $55,450
Inter-Control Center
Communications Protocol
(ICCP)
$15,000
Outage Management System
(OMS)
$75,000
Distribution Management
System (DMS)
$75,000
PRISM OMS Workforce
Resource (POWR - mobile
platform for PRISM)
$25,000
3rd Party software licenses $20,766
Total $266,216
The ACS offer is based on lump sum pricing the following estimated services breakout is
provided for reference only.
All payments are based on the milestones set forth below.
5.3 Services Pricing
SERVICES PRICING BREAKOUT
Project Management $16,800
GIS Integration $69,400
Data Modeling $69,800
Design, Build & Configuration $98,734
Testing $64,175
On-Site Services $44,923
Training $19,252
$383,084
Task Order 1 - 8790 Advanced Distribution Management System Page 19 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
5.4 Optional Development Adder
Per discussion with City of Fort Collins, ACS can develop the ability for field crews to identify
power flow up and downstream from any point in the network as described in Out_144 in
Attachment A. Example graphic of example of this capability shown in graphic below:
Additional cost for this development would be $24,000 (Twenty-Four Thousand USD)
All pricing is based on standard ACS configuration and is defined under the following
conditions:
• Firm, in USD, for the validity of the Offer
• All taxes and import duties are excluded from price
• Prices quoted are F.O.B Norcross, GA
• Limited to the Scope of Supply
If needed, on-site services will be charged at our hourly rate of $225/Hour. Customer will be
billed for travel time, plus all travel and living expenses at cost, plus an additional 15%.
5.5 Payment Schedule
Fort Collins shall pay ACS for Services rendered in accordance with the payment schedule
set forth below.
Each payment milestone shall be considered complete and payable upon completion of the
stated list of deliverables. The Project Milestone Acceptance Form shall be completed and
submitted per the Master Services Agreement. Alternatively, each milestone shall be
considered complete if a period of 30 days has elapsed since the completion of stated list of
deliverables.
Task Order 1 - 8790 Advanced Distribution Management System Page 20 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Payment Milestones
Milestone Services Software Payment
1 Contract Award 100% $ 266,216.00
2
Design/Interface Documents
Complete
30% 0% $ 114,925.20
3 GIS Modeling Complete 20% 0% $ 76,616.80
4 Factory Acceptance Test 10% 0% $ 38,308.40
5
Completion of Site Acceptance
Testing
20% 0% $ 76,616.80
6 Project Complete 20% 0% $ 76,616.80
Total $ 649,300.00
7 Project Support Go Live
Milestone 1 (100% of Software) – Contract Award
This milestone shall be considered complete and payable when Fort Collins and ACS
have completed the Task Order.
Milestone 2 (30% of Services) – Design/Interface Documents Complete
This milestone shall be considered complete and payable when all Interface Design
Documents have been completed and approved by Fort Collins. The objective criteria for
the completion of this milestone shall be the submission of all approved interface design
documents to Fort Collins.
Milestone 3 (20% of Services) – GIS Modeling Complete
This milestone shall be considered complete and payable when ACS finishes the 3rd
iteration of the GIS modeling effort. The objective criteria for the completion of this
milestone shall be the submission of the 3rd and final GIS modeling report to Fort
Collins. The requirement of additional iterations of the model will not cause this milestone
to be delayed or remain unpaid.
Milestone 4 (10% of Services) – Completion of FAT
This milestone shall be considered complete and payable upon completion of the FAT for
the PRISM system. The objective criteria for this milestone shall be the completion of the
FAT requirements including the submittal of the Test Report for the testing by ACS and the
acceptance of the report by Fort Collins.
Milestone 5 (20% of Services) – Completion of Site Acceptance Testing
This milestone shall be complete and payable upon completion of the site testing for the
system. The objective criteria for this milestone shall be a report by ACS that all testing at
site has been completed and the acceptance of this report by Fort Collins.
Task Order 1 - 8790 Advanced Distribution Management System Page 21 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Milestone 6 (20% of Services) – Project Complete
This milestone shall be considered complete and payable upon completion of the project.
The objective criteria for this milestone shall be the use of the ACS PRISM system by Fort
Collins as the production system for a period of two (2) consecutive weeks with no
Severity 1 or Severity 2 defects to the system. Alternatively, this milestone shall be
considered complete if a period of three (3) months has elapsed since the completion of
Milestone 5.
5.6 Expenses
In accordance with the Agreement, Fort Collins will reimburse ACS for travel expenses at
cost. Below is an estimate of the expenses with no mark-up.
Travel and Living Expenses Estimate
Assumed Rates
Flights ATL to DEN $350 Per Flight (economy)
Hotel Ft. Collins - Hampton $100
Per Night including
taxes
Per Diem $50
Rental Car $100
Daily Meals $100
GIS Workshop
1 ppl, 1 trip for 5 days
each
Flights 1 $350 $350
Hotel 5 $100 $500
Rental Car 5 $100 $500
Per Diem 5 $50 $250
Daily Meals 5 $100 $500
$2,100
OMS Workshop 1 ppl, 1 trip for 5 days
Flights 1 $350 $350
Hotel 5 $100 $500
Rental Car 5 $100 $500
Per Diem 5 $50 $250
Daily Meals 5 $100 $500
$2,100
Task Order 1 - 8790 Advanced Distribution Management System Page 22 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
SCADA
Implementation
Phase
1 ppl, 1 trips for 5 days
each
Flights 1 $350 $350
Hotel 5 $100 $500
Rental Car 5 $100 $500
Per Diem 5 $50 $250
Daily Meals 5 $100 $500
$2,100
OMS & Testing
Phase
2 ppl, 1 trips for 19 days
each 7+7+5
Flights 4 $350 $1,400
Hotel 38 $100 $3,800
Rental Car 19 $100 $1,900
Per Diem 38 $50 $1,900
Daily Meals 38 $100 $3,800
$12,800
Training
1 ppl, 1 trips for 10 days
each
Flights 1 $350 $350
Hotel 10 $100 $1,000
Rental Car 10 $100 $1,000
Per Diem 10 $50 $500
Daily Meals 10 $100 $1,000
$3,850
Total $22,950
Task Order 1 - 8790 Advanced Distribution Management System Page 23 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
RFP No.: 8752 Rev2
ADMS
February 22, 2019 City of Fort Collins Page | 13
8 BUSINESS RELEASE II- ADMS I (OMS) TABLE OF
COMPLIANCE
ATTACHMENT B
Task Order 1 - 8790 Advanced Distribution Management System Page 24 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Requirement Response Comments
Receive Outage Notification
Receive
Outage
Notification
Out_079 Ability to receive outage event notifications from SCADA system for use in managing outage events SF
Receive
Outage
Notification
Out_080 Ability to display real time information on Substation and Transmission devices from SCADA. SF
Receive
Outage
Notification
Out_081
Ability to display SCADA information at Distribution Substation locations (such as loading on Circuit Breaker,
Transformer, Operational State of Switches).
SF
Receive
Outage
Notification
Out_082
Outage lifecycle shall include the following stages - predicted, verified, assigned, dispatched, working, closed and
completed. Changes in stage shall be recorded along with a date and timestamp
SF
Receive
Outage
Notification
Out_083 Comments/notes shall be allowed to be recorded against an Outage event SF
Display Outage
Display Outage Out_013
Outage and Fault locations can be graphically identified and displayed on a map during outage events (including
configurable symbology based on status)
SF
Display Outage Out_014 Ability to display a visible indication of Normal Open points (via Arrow, Highlight, other) SF
Display Outage Out_016 Provide the ability to display all current outages/trouble calls for internal and external use/communication SF
Display Outage Out_017 Ability to allow key customers (Commercial) to be identified and prioritized SF
Display Outage Out_020 Ability to store how long a customer was out for entire outage event history SF
Display Outage Out_023
Ability to provide a spatial display of current Outage and Service Interruption related events in real-time or near-real
time
SF
Display Outage Out_024
Ability to provide a spatial display of current customers affected by an Outage or Service Interruption event, by
individual location, and aggregated counts by Spatial representation (such as Counts per Feeder, Counts per Zip
Code)
RQ
Display Outage Out_025
Ability to select an Outage (planned and unplanned) and provide both a spatial and list display of all current
customers affected by that outage
SF
Display Outage Out_026 Ability to provide a spatial display of current damage (Pole / Line Down and other Damaged Facilities) numbers SF
Display Outage Out_027 Ability to display Customers impacted by an Outage. SF
Display Outage Out_028 Provide the ability to display current and historic outages by type RQ
Display Outage Out_029 Ability to display Outage Schedules for Substations. RQ
Display Outage Out_031 Ability to display Planned Outage locations. SF
Display Outage Out_032 Ability to display Customers impacted by an Outage. SF
Display Outage Out_033 Ability to display Customers that will be impacted by a Planned Outage. SF
OMS - Outage Management Requirements
Task Order 1 - 8790 Advanced Distribution Management System Page 25 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Display Outage Out_034 Ability to display Customers impacted by multiple Outages. SF
# of Customer impacted by multiple outage are displayed in Dashboard.
Customer names are listed in Ticket details
Display Outage Out_039 Outage events shall be associated with Trouble Calls. The list of Trouble Calls for an outage shall be viewable SF
Display Outage Out_114
Ability to provide a spatial display for Outage events who have exceeded, or are about to exceed (within a specified
criteria) the Estimated Restore Time (ERT) that has been communicated to Customers
SF
ERT is shown on-screen. This counts down and then blinks red when the
ERT is overrun.
Display Outage Out_132 Ability to symbolize outage and non-outage related trouble calls. SF
Display Outage Out_138 Ability to filter outage calls for non-payment customers RQ
Display Outage Load_015
Ability to display Customer Counts by type and phase for a Substation, Feeder, Protective Device, any switchable
device location in the electrical model.
SF
View Basemap
View Basemap Load_048
Ability to launch a Google Earth and Google street view from a selected location on the map to show underlying
satellite imagery basemap with facilities draped on top
SF GridVu network
View Electric Assets
View Electric
Assets
Out_118
Be able to display internal views (schematics, photos, specifications, settings, etc.) of Substations, Vaults, etc. in
relation to the feeder network
SF
View Electric
Assets
Out_119 Provide the ability to search for network devices and display them with a larger symbology for ease of viewing. SF
Device is not made larger, but a yellow circle is drawn and the device is
centerd in the display wondwo and the cursor points to identify the search
device.
View Electric
Assets
Out_120 Provide the ability to display Open Tie Switch locations. SF
View Electric
Assets
Out_122
Provide the ability to list all facilities or electrical equipment on a selected feeder and downstream of any point in the
electrical model.
SF
This capability is accomplished in several ways graphically and by using the
model viewer
View Electric
Assets
Out_123 Support ability to set and enforce user access permissions to Control Zones/Areas SF
View Current Electric Configuration
View Current
Electric
Configuration
Out_078 Ability to provide a spatial display of Energized and De-energized Devices and line Segments SF
View Current
Electric
Configuration
Out_110
The electric network can be viewed dynamically in ADMS showing switching changes and temporary network
modifications and update the default GIS view in real time
SF
Access Meter
Data
Out_001
Provide the ability to trace from an Outage point to find the closest meters either side of the Outage and perform a
meter ping through the AMI system to aid in the outage/restoration analysis process.
SF
Access Meter
Data
Out_002 The LPO Solution shall be able to receive outage/restoration/momentary event details published from AMI/MDMS SF
Access Meter
Data
Out_003
Provide ability to support integration with AMI to ping meters in order to track the progression of outage restoration
from start to power restored
SF
Access Meter
Data
Out_022 Ability to ingest AMI Outage or Event status from an AMI or MDMS Platform SF
Identify Outage History
Identify Outage
History
Out_040 Allow outages/trouble calls to be archived SF
Identify Outage
History
Out_041 Allow archived outages/trouble calls to be viewed and found by address SF
Identify Outage
History
Out_042 Allow a history of work and outage/trouble call to be displayed for a specific customer or location SF
Identify Outage
History
Out_043
Provide a configurable list of outage/trouble call identified issues (Outage, No Problem Found, Billing Question, Limb
on Line, etc.)
RQ
Identify Outage
History
Out_044 Ability to capture and store Historical Data on the number of customers identified by (or connected to) a feeder SF
Identify Outage
History
Out_046 Ability to produce ad-hoc reports against historical outage data SF
Trace Network
Trace Network Out_097
Allow a feeder to display connected customers/service delivery points in the same color as a displayed/traced feeder
and by phase
SF
Trace Network Out_098
Ability to trace upline from any point on the system to identify protective devices, wire sizes and span lengths, feeder
identification, abnormal system conditions, and substations. Trace results must be highlighted
SF
Tracing is a visual function, highlighting the circuit and connected elements
on the operator map display. A list of facilities/devices is not generated.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Out_099 Identify/display first, second, x devices to check upstream of an outage as part of the outage resolution analysis SF
The TCA function (prediction engine) in OMS indicates the predicted device
and provides operators with ability to roll upstream/downstream to next or
selected device.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Out_100
Trace Network Out_105
Provide the ability to list and display by phase customer and transformer count, customer classification and
connected kVA for devices in a Feeder trace.
SF
This information is available in the model but is not displayed as part of a
feeder trace. Customer-to-transformer connectivity can be displayed in the
map. Ability to display downstream customer count and connected kVA for
devices on the map is under development for a future release.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired
Trace Network Out_144
Ability to provide field crews with up to the minute map switching status including the ability to trace up and down
stream from any point in the network in under 5 seconds.
SF
Trace Network Load_037 Provide the ability to trace to Distributed Generation (DG) Locations SF
If DGs are modeled in GIS and imported to ADMS, then they will be shown
in a trace. There is no ability to define a trace to a DG location specifically.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Load_038 Allow electric system to be traced downstream and display/report the connected Distributed Generation Locations SF
DG locations can be viewed within the model and on the map, but a
specific trace functionality does not currently exist to display a list/report of
these locations as part of the results.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Load_039 Provide the ability to display relationships between Distributed Generation locations and Transformer locations. SF
Trace Network Load_040
Provide the ability to display relationships between Electric Vehicle Charging Station locations and Transformer
locations.
SF
If EV charging stations are included in the load model, then the relationship
between them and the connected load transformers will be displayed.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Load_041 Provide the ability to trace the connected network and view; KVA by Phase, Customer Count, and Aggregated KVA. SF
Create Switch Order
Create Switch
Order
Out_004 Provide the ability to display de-energized subdivision prior to the switching that is done to energize. SF
Create Switch
Order
Out_008 Provide the ability to display Switching Procedures and SOP's associated with certain Devices. SF
Create Switch
Order
Out_009 Support the manual creation of switching orders SF
Create Switch
Order
Out_011 Support the catalog/history capture of switching orders SF
Perform Switching
Perform
Switching
Out_066
Provide the ability to perform open/close switching activities in real-time and have that information available to
Utilities personnel including field crews in real-time
SF
Perform
Switching
Out_067 Provide the ability to display graphical evidence of switching activities (for example via graphical flags) SF
Perform
Switching
Perform
Switching
Out_069
Offeror shall describe the solutions functionality supporting the following Planned Switching requirements:
• Generate customer list
• Generate critical customer list
• Device-based graphical switching
• Keep track of partial restorations
• Use templates of existing switch plans to generate new plan
• Use power flow analysis to perform what-if analysis for specific switch plan
• Use suggested switching to generate future switch plan
• Use switch management module to see other planned switching events
• Use switch management module to simulate switching plans
• Integrated requests for switching plans for all jobs from WMS
SF
Perform
Switching
Out_070
Offeror shall describe the solutions functionality supporting the following Unplanned Switching requirements:
• Generate customer list
• Generate critical customer list
• Device-based graphical switching
• View downstream related conditions/tags
• Device-based graphical tagging
• Device-based graphical addition of notes
• Complete auditing of switching operations
• Keeps track of partial restorations
• View SCADA outages
• Use power flow analysis to perform what-if analysis for specific switch plan
• Use multiple views: georeferenced, circuit/feeder view, backbone view
SF
Perform
Switching
Out_071
Ability to add and remove temporary switches
SF
Perform
Switching
Out_072
Ability to correlate distribution system model to allow prediction of outage cause and upstream protective device
based upon affected meters/customers and fault current information to identify probable cause/area indicating the
source/areas of trouble on the system
SF
Perform
Switching
Out_074
Reflect real time switching/sectionalizing or other changes on distribution system and automatically alter its
prediction engine accordingly
SF
Perform
Switching
Out_075
Ability to provide a real time interactive map that can show switching operations as they are performed rather than
waiting and sending as a system refresh (i.e. zero latency)
SF
Perform
Switching
Out_134 Dispatchers must have ability to easily alter timestamps associated to switching events SF
Perform
Switching
Restore
Outage
Out_089
Provide an incident summary screen which displays current outages and associated information including Outage
number, Outage Status, Device(s), number of trouble calls per outage #, number of affected customers per outage
scenario, start time, assigned crew(s) and operating area
SF
Notify Customer
Notify Customer Out_059 Able to identify customers that need follow up in outage situations SF
Notify Customer Out_061 Provide automated mechanisms for customers to confirm outages and restorations SF
Notify
Customer
Out_063
Ability to provide a spatial display of the destinations and/or associated outages that crews are responding to,
associated with a crew
SF
Notify
Customer
Out_064 Ability to provide a spatial display for Outage ETR (Estimated Time to Restore) events, by Event SF
ETR for outages is not displayed spatially. Outage area polygons can be
displayed in the map, and the ETR viewed on the GridVu map or by viewing
the outage detail screen.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Notify
Customer
Out_065 Ability to send text, phone call, E-mail messages to Customers when their Meter is scheduled for Install/Exchange. SF
Notify
Customer
Out_139
Ability to show a version of planned and unplanned outages on a web map for external customer use showing
Outage groupings, outage state e.g. planned, meter reported outage, Oms verified outage, restored.
SF
Only existing (confirmed) outages are displayed on the map (whether
planned or unplanned). The type of outage may be displayed in the outage
info under the cause code.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
View Analytics
View Analytics Out_106 Support calculation and configuration of all key performance metrics (ASAI, SAIDI, SAIFI, CAIFI, MAIFI) SF
View Analytics Out_107 Support the ability to view SAIDI and SAIFI by Feeder and protective device by phase spatially. NR
The capability of calculating SAIDI/SAIFI by circuit is available in the latest
release of OMS. The information is available via report and is not viewable
spatially.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
View Analytics Out_108 Ability to display aggregated load by Substation, Bus, Feeder, and any other point in the distribution model. SF
View Analytics Out_109
Support the ability to Calculate and store System Average Interruption Duration/Frequency Index(s) (ASAI, SAIDI,
SAIFI, CAIFI, MAIFI) and other related indices including statistics for each customer.
SF
View Analytics Out_131 Ability to easily edit outage step/start/restoration time stamps and outage statistics SF
View Analytics Out_136 Support a dashboard showing total outages, customers affected, length of outages, ERTs, crew dispatch status SF
View Analytics Out_137 Support a separate historical dashboard showing outage statistics NR
Historical dashboard capability is currently available in the Enterprise Portal
included as part of the proposed system.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Predictive Outage Analysis
Predictive
Predictive
Outage
Analysis
Out_128
Ability to predict, for underground sections, protective devices immediately if two customers on the same feeder
report outages.
SF
Predictive
Outage
Analysis
Out_129
The LPO solution shall provide no delay or filtering on the percentage of customers reporting outages. For instance if
one meter is out fed from one distribution transformer and another meter is out fed from a different transformer but
both are on the same circuit, the upstream fuse should be immediately identified as the common protective device.
Two different outages should not be predicted on different transformers.
SF
Predictive
Outage
Analysis
Out_038
Outage events created by the outage prediction process shall have a status of “predicted” (where the outage cannot
be verified from SCADA, AMI, or field) or “verified”
SF
Terminology: Unconfirmed outagess are called "Incidents" Verified or
predicted status are "confirmed" outages in PRISM
Predictive
Outage
Analysis
Out_149
Ability to show planned and unplanned outages on a web map for internal use showing Outage groupings, outage
state e.g. planned, meter reported outage, Oms verified outage, restored.
SF
Only existing (confirmed) outages are displayed on the map (whether
planned or unplanned). The type of outage may displayed in the outage
info under the cause code.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Switching Study Mode
Switching
Study Mode
Out_096
The LPO solution can support a switching study mode to support simulations and training
SF
Create Reports
Create Report Load_051 Offeror shall describe the standard and custom reporting capabilities available in the solution SF
PRISM SCADA/ADMS/OMS includes PRISM Reporter, a robust enterprise
tool for management, customer and employee information. You can work
from pre–designed reports (Reporter allows full customization of sources,
format and clearances) or create ad–hoc queries. Results can be delivered
over the internet as HTML, DHTML, PDF or Microsoft Excel documents,
and are easily integrated with scheduling and web applications, with
complete security. Charts (in 2–D and 3–D), columnar, cross–tab and
summary reports are supported. Although Reporter works easily with
JDBC, ODBC, XML and Access sources, as well as object/array data, the
Reporter interface is designed to simplify organization and publication.
Create Report Load_016
Ability to support report creation for Conductor Summary (including secondaries) for System with contents similar to
legacy report
RQ
What is legacy reporting system? Will sample reports be supplied to
Create Report Load_022 Ability to support report creation for Spotload Summary with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
GIS/ADMS Field Tool Functional
ADMS
Navigation
ADMS_074
Mobile map shall provide the ability to search by, Switch Point number, transformer number, switch number, service
address, general addresses, intersections, substation, feeder. All searches are able to be performed in disconnected
and connected communication states.
SF
The user can search in the mobile map using device identifiers
(transformers, switches/switchable points) that come from GIS in the
import to the control center map. This would include additional layers that
would contain vault identifiers, for example. Transformers and feeders are
selectable by identifier directly from the tree view on the left side of the
map.
When internet connection is lost, the system map/device information for the
areas being viewed may still be searched. The ability to view and search
Google map information would be lost, as this information cannot be
cached locally.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Display Outage Out_036
Support the ability to display a web based and mobile Outage map (including a geographical view of the location of
outages, outage status, and the number of customers impacted, and the location of Critical Care customers) with
both internal (City of Fort Collins) and external views
SF
Trace Network Out_144
Ability to provide field crews with up to the minute map switching status including the ability to trace up and down
stream from any point in the network in under 5 seconds.
MD
Tracing is not supported on the mobile (GridVu Network) map. FCU would
like the ability to be able to determine upstream/downstream for elements
on the mobile display.
ACS confirms that a method of displaying upstream/downstream for a
circuit element on the GridVu mobile map is possible, however requires
additional development. Pricing to add this functionality is included in
Section 3.2
Perform
Switching
Out_147
Ability to provide field crews with up to the minute map switching status including the ability to show switching plans
created by dispatchers in under 5 seconds.
SF
Perform
Switching
Out_148
Ability to provide field crews with up to the minute map switching status including the ability to test switch plans
prior to actual switching in under 5 seconds.
SF
View Current
Electric
Configuration
Out_145
Mobile map viewer shall show up to the minute status when connected to WiFi. When disconnected, map shall still
be fully functional. All mobile changes and changes made in dispatch office shall be transmitted immediately and
automatically when WiFi is reestablished.
Requirement Response Comments
ADMS
Navigation
ADMS_089
Offeror shall describe their solutions ability to turn on/off layers
based on zoom level and user profiles; change symbology based on
zoom level
SF Manual operator layer turn on/off is supported. Auto layer control based on zoom level is supported
ADMS
Navigation
ADMS_090
Offeror shall describe their solutions ability to "highlight" feeders or
affected equipment based on selected feeder or equipment
SF
PRISM supports various dynamically colorized views of the feeder network. Each view supports distribution operations with full SCADA functionality. Each view
supports dynamic colorization visualization using topology processor from the network model, three-phase flow direction indicators, remote control, switching,
tagging, linkages to other displays. The three types of views are:
1)Geographic view
2)Schematic view
3)Feeder view
Geographic and schematic views are created from a GIS or CAD application of the feeder map using PRISM DASmap model/map editor.
The feeder view is created in real-time by the operator who is able to select the network feeder in which to provide a simplified focused view for better situational
awareness.
PRISM’s real-time dynamic schematic generator, ReShape, will dynamically generate a schematic switching diagram from the current real-time feeder topology by
clicking on the feeder in the geographic view. The Reshape display pops up in a separate window.
The advantage of Reshape over the geographic or the schematic is as follows:
1.The feeder, including the feeder’s open ties to backup feeders, is presented in a simplified view for improved switching situational awareness.
2.Backup feeders tied to the primary feeder can also be created in a pop-up window and presented with a cursor click at the tie point.
3.The feeder topology matches the same real-time topology as displayed in the full network view.
4.ReShape view matches the same feeder color used for the feeder in the geographic or schematic view.
5.Synchronized ‘search and locate’ of devices in any view (such as a geographic map) will identify the same device in ReShape view and vice versa.
6.ReShape is a full function SCADA display with full device control, and tag placement capability
7.SwitchPlan icons in the ReShape view shows full sequenced switching icons from SwitchPlan.
8.Reshape view can be pan/zoomed to adjust size and location.
9.ReShape view does not require any maintenance
10.Next version additions will add DERMS related devices to ReShape.
ADMS
Navigation
ADMS_091
Offeror shall describe their solutions ability to display raster data,
e.g., aerial photos under vector data
SF PRISM supports a product called GridVu which displays the network over a Google map. Google supports the raster (aerial) image or vector background image,
Conduct
Online
PowerFlow
ADMS_005
Offeror shall describe solution ability to integrate with SCADA to
carry out Voltage Reduction and with AMI to detect bellweather
meters
SF PRISM support Integrtaed Volt VAr contorl (IVVC) with AMI integration. AMI can include the ull populatino or Bellweather metwrs.
Conduct
Online
PowerFlow
ADMS_006
Offeror shall describe solution ability to support interactive Online
PowerFlow Results in real time at all points in the distribution model
SF
The load flow results are displayed in a pop-up box using the cursor/tool tip hovering over the feeder network map. The load flow results are displayed for the
feeder node over which the cursor hovers. The displayed results show three-phase Voltage, current, real and reactive power, etc.
Conduct
Facility
Information
ADMS_073
Offeror shall describe the solutions ability to display the distribution
system models in the following view: Schematic, Geo-referenced,
Substation One-Line, Single Feeder, Backbone of System
SF See response to ADMS_090
Facility
Information
ADMS_080
Offeror shall describe their solutions approach to making operating
area jurisdiction visible by device/symbology
SF See response to ADMS_080
Load Models
and Estimate
Load
ADMS_029
Offeror shall describe their solutions ability to perform real-time load
flow analysis taking into account electrical storage, electric vehicles,
reverse energy flows
SF
The new version of DASdb includes support for DERMS composing of energy storage types and DG injection types. IVVC handles storage strategy in charge and
discharge mode adjusting the asset from load to source under the realtime optimization control of the DERMS suite. More information regarding the PRISM
DERMS suite operating ability is available in the published 2018 EPIC DERMS study inlcuded in this proposal..
Load Models
and Estimate
Load
ADMS_030
Offeror shall describe the ability of the solution to provide a standard
set of historic load models and how those are utilized by On Line
Power Flow (OLPF)
SF See response to ADMS_030
Load Models
and Estimate
Load
ADMS_031
Offeror shall describe the ability of the solution to provide a load
estimation function or functions and how those are utilized by On
Line Power Flow (OLPF)
SF See response to ADMS_031
Load Models
and Estimate
Load
ADMS_076
Offeror shall describe their solutions approach to support "As-
operating" and "As-proposed" distribution system models including
appropriate symbology to distinguish between the states
SF
PRISM supports "As-operating" and "As-proposed" (It is not clear what As-Proposed means. ACS assumes the definition is as described in RFP section
OBJECTIVE, GOALS, AND BACKGROUND as “As-constructed". The as-constructed state is imported from ESRI arc-info onto DASmap which is converted to a
SCADA display and database in PRISM. The real-time telemetry in PRISM updates the position of the switches which is calculated by Topology Processor to
produce the topology view called "as-operated". Changes in ESRI to the "as-constructed" network does not change the topology driven view of the "as-operated"
network the operator uses. i.e. the normally open switches are changed based on as-operated telemetry.
In addition PRISM supports a feature called ‘Redline’ which enables the operator to make changes to the "as-constructed" state through temporary cuts and
jumpers.
Load Models
and Estimate
Load
ADMS_077
Offeror shall describe their solutions approach to provide a customer
On-line
Incremental
GIS Updates
ADMS_096
Offeror shall describe their solutions ability to perform incremental
updates from GIS to ADMS shall be in real-time
SF
Please read response to ADMS_078. The GIS update is not realtime. However it is incremental. The time to import and commit changes from the GIS to the
PRISM ADMS may take 1 hour. However most of the time is unattended writing to Oracle. This time does not affect the operations of the ADMS. The change-
over to the new validated data (model and display map) is bumpless with respect to operations.
On-line
Incremental
GIS Updates
ADMS_097
Offeror should explain solutions ability to import the electric system
network and assets without losing current switch status. This must
be done for all switch points (over 10,000 locations). Ability to export
from ADMS to GIS including switch point status.
SF
Please read response to ADMS_078. The GIS update is not realtime. But it never affects operations. The as-constructed source in GIS is different from the as-
operated source in ADMS. ADMS continues to collect reatliem switch changes. As for the number of points, PRISM operates ADMS on a 3000 feeder system with
5,000,000 points.
Operate
Tagging
Devices
ADMS_036
Offeror shall describe their solutions approach to request,
management, and planning of outage requests (including
geographically)
SF
Planned outages are supported in PRISM OMS. A planned outage is created with a start time and duration and is recorded as an incident until the beginning of
the outage at which point the operator confirms the planned event.
Operate
Tagging
Devices
ADMS_037
Offeror shall describe their solutions approach to the creation and
monitoring of safety protection guarantees (i.e. tags and grounds)
SF
The SCADA platform supports placement of tags and ground. The system supports an an application called SwithcPlan which is an electronic switch order
planning with crew asignment sent to their mobile.The SwitchPlans can be manually build using the PRISM GUI, or created by an optimization
application.SwitchPlan also supports a template to control the process for any work or switching procedure includng the correct placement of tags and grounds
Operate
Tagging
Devices
ADMS_038
Offeror shall describe the impact tagging devices can have on
network tracing
SF
Device tagging is not affected by graphical network tracing. However tracing is a graphical fucntion and a application fucntion, Within the application such as
Intelligent switching the intellgent switch plan is affetced by raggig in order to preserve the control restriction.
Operate
Tagging
Devices
ADMS_039
Offeror shall describe their solutions ability to provide a geographical
view of tagging notes
SF
Tags are visible on the PRISM graphic displays in schmatic view, geogrpahic view and reShape view. The mbile view is a geographc overlay on Google maps
which should near reatiem network switching updates as well as any point tag which is visible as an icon on the map. If the mobile user taps the tag, the
Support
Intelligent
Alarming
ADMS_068
Offeror shall describe their solutions ability to integrate with LPO
SCADA (Iconix) system for alarm processing and view of SCADA
status and analog values
SF
ACS has interfaced to legacy centralized SCADA systems for the installation of OMS and DMS applications. The legacy SCADA system will interface to PRISM
via a number of different methods:
1.PRISM has supported legacy SCADA systems which runs software to make the legacy SCADA system simulate if it were a RTU/data concentrator. The
central ADMS will therefore issue a polling sequence using DNP3.0. serial or a report by exception scheme using DNP3.0/IP. In summary the legacy SCADA
system functions as a data concentrator with the added benefit of providing the operators with the legacy user interface to control points. In addition, the ADMS
can likewise support displays to control points through the legacy SCADA system.
2.Some systems use a standard ICCP intercontrol center interface to pass data including block five which supports controlled points.
3.If the legacy system does not support either of these interface methods, a custom IP network interface is available from PRISM to share data and commands
with the legacy SCADA system.
4.If the RTUs are dual ported each system can receive data from the RTU’s independently.
In each case the solution is a centralized architecture. The transition to remove the legacy SCADA is simplified using solution 1 and 2 above since only a
communication server (or communication serial interface unit for serial RTUS) is needed to take over polling the RTUs with no further changes.
PRISM also supports a distributed automation platform which is totally transparent to the legacy SCADA system. This approach has been implemented at Georgia
Power to automate 1.3M meters on up to 800 feeders in Georgia without changes to the SCADA.
Support
Intelligent
Alarming
ADMS_069
Offeror shall describe their solutions ability to support analysis of
network topology to generate meaningful alarms at the highest level
SF
There are at least three interpretations and responses to this question: 1. Modeling cascading topology across multiple Voltage levels 2. Using real-time topology
changes to generate load flow-based alarms and violations 3. Standard SCADA functionality to generate meaningful alarms
Concerning:
1. Modeling cascading topology across multiple Voltage levels, PRISM has been deployed in situations where all voltage levels including HV, Subs transmission,
MV and LV network elements are modelled in a single model. ACS has delivered network analysis for each network type. If a HV failure occurs on a HV/subT
meshed network, PRISM topology processor will evaluate the potential impact of loss of service, etc., at lower Voltage levels on the radial network.
2. Using real-time topology changes to generate load flow-based alarms and violations, the PRISM ADMS distribution management and distribution automation
functions / applications rely on an accurate model of the real-time state of the network. Rather than each application determining the network state or network
topology the DMS Topology Processor calculates the current real-time state to be used by all the applications as well as by the user interface to colorize the
network maps.
Topology processor begins with the static model ‘as built’ connectivity of the network imported from the GIS. The update from the GIS is the source definition of
the connectivity and serves to define the network structure. TP dynamically updates the connectivity by adding the telemetered and manually updated state of the
switching devices in the network in order to calculate the ‘topology’. Other applications such as Real-time Redline enable the operator to apply cuts and jumpers
which represent temporary of emergency network changes that affect connectivity and therefore topology.
Every DMS/DA, automation, optimization and analysis application dynamically adapts to the topology changes in real-time. Switching order creation applications
which generate switching steps in order to meet various objective functions will likewise dynamically adapt to the real-time topology changes.
Based on the real-time network topology the load estimator will recalculate the load profile across all feeder nodes. The Load flow analysis will then generate
alarms to determine violations. The violations based on the real-time topology will produce the following information, some of which can be colorized on the
network map. The analysis will solve:
•Solve the full-sized radial (open-loop) or non-radial (closed-loop) distribution system. The feeder line sections and transformers can be three-phase, two-phase or
single-phase units in either a radial or non-radial configuration. In the non-radial configuration, three-phase and non-three phase feeder sections is supported to
function in a looped or parallel configuration.
•Solve selected zones, substations, and feeders without solving the entire distribution system model
*Compute voltages and currents for each phase for every node, feeder section and other devices.
*Compute three-phase or phase-by-phase active and reactive loads and losses for the distribution system as a whole or for individual substations, transformers,
capacitors, reactors and feeders.
*Handle feeders with unbalanced loads and line impedance.
*Scale all or selected loads with a dispatcher entered scaling factor.
*Re-scale selected loads with selected power factor.
*Automatically Adjust LTC taps and associated capacitor banks to maintain specified RPDC.
*Set all or selected LTCs, associated capacitor banks and reactors in fixed or automatic control mode.
Category Requirement Response Comments
TR_ARCH Architecture
TR_ARCH-1
For the ADMS solution provide an Architecture diagram and/or table which shows all components (modules/servers)
of the solution in a Logical and Physical View, required to support City of Fort Collins Requirements. The system shall
be readily scalable to accommodate 5% annual growth. Include Server Size (i.e. RAM, Processor Speed/Spec Rating),
for each of the following environments: Production / QA / Development and Disaster Recovery.
SF See attached System Diagram. Server sizes will be listed in the quote document
TR_ARCH-2
For the ADMS solution provide an Architecture Table which shows all components of the solution and lists which
server type that component is resident on, and also includes a) Purpose of the Component b) Required O/S and
Version No. c) Required third-party software (i.e. RDBMS Technology, Java, .NET Framework, etc.) and version d)
Whether this component is provided as part of the Implementation, or is a dependency on City of Fort Collins IT to
provide.
SF
All components of the ACS ADMS will run on Red Hat Linux Enterprise v 7.x. Servers
and their OS will be listed on the list of Deliverables in the quote document. All
software needed for the system will be provided by ACS
TR_ARCH-3
For the ADMS solution propose an Architecture view which supports a High Available (HA) server configuration,
including any dependent server configurations required to support failover and/or server redundancy. Describe how
the solution supports failover for any critical components, and any situations that may result in data loss in
restarting or recovering from a failover event.
SF
The ACS ADMS Solution will be designed as a high availability system. It will consist
of a main system and hot standby in the Production environment and another hot
standby system in the DR environment. Our system will support a failover of less than
1 min with no data loss
TR_ARCH-4
For the ADMS solution propose an Architecture View and description which supports a Disaster Recovery (DR) /
Failover Site, for any critical components, located in a physically separate location Include any expected
dependencies and expected recovery time, based on scenarios where an expected restoration of service to the DR
site is within 1 hour, 4 hours, or 24 hours.
SF
If the DR system is running as a hot-standby, the cutover will be <1min with no data
loss. Otherwise, it will be approx. 10 minutes for the server to spool up.
TR_ARCH-5
For the ADMS solution provide a list of required routine maintenance procedures to be carried out on the Enterprise
GIS solution, and the impact of this maintenance on the Solution availability.
SF Responses
TR_ARCH-6
For the ADMS solution provide a description of the Software Platform used as part of the core development of the
Platform (i.e., .Net, Java, etc.), and any software development tools typically required to integrate with the solution,
if any. Describe any software testing tools that may support integration testing for your solution. Provide a
comparison review to the City's and Utilities technology standard or reference model in comparison to
recommended designs.
SF The basic software development platform is based on ReHat Linux 7.5.
TR_ARCH-7
For the ADMS solution provide a description of the support for server Virtualization. Include description of
Virtualization software required/supported, and any customers/locations which have implemented the solution in a
Virtualized Production Environment.
SF
Virtualization is supported. Normally ACS will supply the .OVA file and the customer
would supply the appropriately sized server and the Hypervisor. ACS can supply the
virtual host server and Hypervisor - if needed.
TR_ARCH-8
For the ADMS solution provide a description of how your Solution employs an RDBMS (i.e. Oracle/SQL Server specific
versions such as "Enterprise" or "Standard") and SAN storage as means of storage, data redundancy, and recovery
during service interruption, both within a Primary Data Center and between a Primary and an Alternate/DR Data
Center. What is the expected DBA FTE support time required for the solution, based on City of Fort Collins
TR_ARCH-12
Provide Diagram and/or Table describing the various core Integration methods (i.e. Web services/SOAP/REST/Batch
file) supported by the ADMS solution for the integrations listed above. For each method, describe the means of
securing this integration (i.e. HTTPS/SSH/SFTP).
SF See response to TR_ARCH-12
TR_ARCH-13
Describe the various ESB/SOA/EAI/Messaging Technologies that the proposed solution has been integrated with in a
Production environment.
SF
PRISM has supported vrious ESB mesaging technologies including TIBCO, Oracle,
Proprietary and now PRISM is being integrated with iSpeed messaging technology
TR_ARCH-14
Offeror shall adhere to all of City of Fort Collins IT standards, policies and procedures in the delivery, configuration
and maintenance of the proposed ADMS solution.
SF
TR_ARCH-15
Offeror shall indicate if any aspect of its solution for ADMS is a hosted solution. If it is hosted, explain in detail the
connectivity with the solution and how data transfer is securely managed.
SF
The mobile functionality is recommended to be hosted, particulalry the GridVu public
facing services. PRISM uses AWS.
TR_INT Integration
TR_INT-1
Offeror shall describe how their solution caters for 1. a centrally located data repository and 2. multiple, distributed,
repositories in regard to sharing of data between departments within City of Fort Collins and also other, external,
City departments.
SF See response to TR_INT-1
TR_INT-8
Offeror shall describe available integration adaptors available for CIS (Banner), EAM (Maximo), GIS (Esri), System
Planning (Milsoft EA-Windmil), and SCADA (Iconix)
SF
ACS has interfaced with Banner, Maximo and others proprietary CISs. GIS interfaces
have included ESGI, AutoDesk Map3D, Integraph Gtech, Siemens, SmallWorld GE,
Orego, etc. System planning modules to which PRISM (DASmap) has interfaced is
SynerGEE, Windmill, Siemens, Cyme, PSS/e, PSS/ODMS.
TR_INT-9
Offeror shall describe support for integration standards like the Inter-Control Center Communications Protocol
(ICCP), Common Information Model (CIM), and the service oriented architecture to support the exchange of real
time and historical power system information. SF
See response to TR_ARCH-11
TR_INT-10
Offeror shall describe how their ADMS solution functions together with an Esri based geometric network model
representation of a GIS electric utility network. SF
See response to TR_INT-10
TR_INT-11
Offeror shall describe how their ADMS solution functions together with an Esri based utility network model
representation of a GIS electric utility network. SF
See response to TR_INT-10
TR_INT-12
Offeror shall describe how FCU can maintain a GIS-based "high fidelity" electrical network model that supports
OMS/ADMS functionality SF
See response to TR_INT-10
TR_INT-13
Offeror shall describe how ADMS will or will not leverage FCU GIS and Work/Asset/Materials Management System
(Maximo) for asset model sources SF
See response to TR_INT-13 and ADMS_095
TR_INT-14
Offeror shall describe the data requirements and integrations required to support ADMS Switch Order Management
in their solution SF
See response to TR_INT-14
TR_PERF-05
Structural facility edits and switching operations to the electric network made by system control
operators/dispatchers must be available to field crews in (near) real time
SF
Structural facility edits through the geographical map display using ‘Redline’ and
SCADA switching operations to the electric network made by system control
operators/dispatchers is available to field crews in (near) real time.
TR_PERF-06 The system shall retain information such as zoom scale and the layers users had last turned on between sessions. SF
Zoom scale is variable using the mouse wheel. Layers are automatically
cluttered/decluttered, however they can be manually toggled on. Window configuration
can be saved on a user basis.
TR_MBLE Mobile
TR_MBLE-01 Offeror shall describe mobile display ability to provide a browser and device agnostic display (i.e. responsive design) SF
The mobile display utilizes responsive design and will automatically adjust display
content to best match the screen orientation.
TR_MBLE-02 Offeror shall describe the features and functionality of the mobile platform that ensures ease of use. SF Please see Brochure for POWR and GridVu
TR_MBLE-03 Offeror shall describe how the mobile platform maximizes system/wireless connectivity. SF See Response to TR_MBLE-03
TR_MBLE-04 Offeror shall describe how the mobile platform manages disconnects and re-connects from wireless connections. SF See Response to TR_MBLE-03
TR_MBLE-05
Offeror shall describe how the mobile platform simplifies and streamlines the process of mobile data viewing and
editing (including redlining tools).
NR
GridVu network is used for view only at this time. Redline changes are shown in
GridVu. Future product releases will enable editing
TR_MBLE-06
Offeror shall describe how the mobile platform synchronizes data to and from the mobile devices and back to the
office systems (including tabular, vector, reference drawings and documents).
SF See Response to TR_MBLE-03
TR_MBLE-07 Offeror shall describe the solutions ability to provide “Speech to Text” functionality on the mobile device. NR
IVR supports Text-to-speech. Mobile products will inlcude Text-to-speech in future
versions.
TR_MBLE-10 Offeror shall describe the solutions ability to display real time traffic conditions. NA
TR_MBLE-11
Offeror shall describe the solutions ability to provide simple tools for turning on and off individual layers and groups
of layers.
SF
Model layers are listed with checkboxes availabe to chose the layers that are shown
on the map.
INT Interfaces
INT_004
GIS to ADMS - Esri GIS to ADMS sending network model information (either high fidelity based on Esri utility
network model or integration enhancing the model during ETL) for nominal state and proposed facilities
SF
ACS Response: Understood. ACS would prefer to receive the .MDB file from the
ESRI GIS. This would ensure that the connectivity and geospatial data is relatively
correct and accurate. The model import from the ESRI system is fairly simple and
straightforward using our DASmap import tool. This will minimize FCU’s time and
ACS’ time in troubleshooting similar issues with ESRI import of the EDAR data.
Using the GIS data supplied by the utility, ACS will perform an initial import and will
advise the utility of the errors and adjustments necessary to be made to the GIS in
order for DASmap to perform an import and to convert to a connectivity model and
map for PRISM. In the event that there are data or connectivity errors in the GIS
source, ACS will identify the correction(s) to be made. The utility will adjust/correct the
GIS data as necessary in order for DASmap to perform the import and conversion.
Methodologies to build the distribution power flow model varies from customer to
customer. Typically, ACS will provide a spreadsheet to collect the device parameters.
This information is used in DASmap to populate the model imported from ESRI.
However, in the case of Ft. Collins the specification mentions that a Milsoft Windmill
Engineering Analysis tool is used which contains the power flow information that ACS
will need. ACS will only need to perform a one-time import of the data from Windmill to
INT_007 SCADA to ADMS - providing fault distance/magnitude IED data SF See Response to INT_007
INT_008 SCADA to ADMS - events/messaging from field devices SF Events/messaging from field devices is a standard SCADA function
INT_009
ADMS to MDMS - for device control transactions (meter Ping/Power Status Verification, and On Demand
Read)
SF
PRISM OMS supports meter Ping/Power Status Verification, and On Demand Read
and restoration confrmation using MultiSPeak messages with MDM or the head end.
INT_010 MDMS to ADMS - delivery of latest interval/register reads and Outage/Restore/Momentary events SF Similar to INT-009 PRISM complies using MultiSpeak
INT_011 Weather Service to ADMS - 3rd party Weather service data to ADMS for use in Outage Management
activities
SF
Weather service data is supported by PRISM from third parties. Weather data is used
for load forecast and PV forecasts.
INT_012
ADMS to Access Fort Collins external web site - and to Customers via various media for delivery of outage
and restoration information
SF See Response to INT_012
INT_013 Banner CIS to Esri GIS and ADMS for delivery of customer information SF See Response to ADMS_095
INT_014 Banner CIS to Esri GIS and ADMS for delivery of customer information SF See Response to ADMS_095
INT_015 Banner CIS to ADMS for delivery of customer load information SF The operational interface to Banner CIS is through a Batch File - .CSV or a variant
INT_016 LPO mobile Field Tool to ADMS for delivery of Crew Status and Locations SF See Response to TR_MBLE-002
INT_017 Call Net to ADMS - After Hours/Call Net to ADMS for update of after hour calls handled by the 3rd party into
ADMS
SF PRISM has interfaced to 3rd party call centers to OMS Call
Task Order 1 - 8790 Advanced Distribution Management System Page 40 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
ADMS Maintenance & Support
Category Requirement Response Comments
MS-1 Technical Support
MS-1.1
Describe the technical support to be provided to customer during deployment and post deployment.
Technical support shall include but not be limited to phone support, email support, on-site support, 24/7
support. Technical support shall address any element of the Vendor’s solution.
SF
MS-1.2
Technical support hours of operation and escalation policies and procedures for problem
resolution
SF
Our support team is normally available 8:00 am to 7:00 PM
Eastern time. Optional 24hr support is available as part of our
Platinum Level support.
Issues are divided into 4 levels of severity:
1. Critical - System Down.
2. Urgent - Operations Crippled.
3. High - Operations Coping
4. Medium - Minor impact to operations
Response times time and case-closed times are closely
monitored and escalated according to our escalation tree. See
attached Customer Care Services 2018 Guide for more
information
MS-1.3
Technical support standard certification procedures for support personnel and average years
of service in the support organization.
SF
All support personnel are degreed engineers trained by ACS.
7yr Background checks are performed in line with NERC/CIP
guidelines
MS-1.4 Support metrics to demonstrate support performance and resolution capabilities. SF
MS-1.5
Are emergency response services available independent of any maintenance contract so as
to handle critical or catastrophic situations? Please describe.
SF
Yes. ACS takes its partnership with its customers seriously. In
the event of a catastrophic situation ACS will make that
customer's system restoration (or at least stabilization) its
highest priority. Ad-hoc cross-silo teams are created to
minimize bureaucracy and maximize productivity to acheive that
goal.
MS-1.6
Are there differences in support services based on the type of deployment (owned/hosted by
customer, hosted by vendor, managed services provided by vendor)? Please describe.
SF
No. ACS will support 100% of its delivered solution. The only
difference in levels of support are the Bronze/Gold/Platinum
packages
MS-2 Services Support
MS-2.1
Vendor shall provide options for post-implementation support. Describe the post-acceptance support to
be provided, including all elements of the system so that customer can successfully operate the system
over its expected operating life.
SF
ACS offers several options of post-acceptance support
including patch-management, Diagnostic Services, Security
Audits, Onsite consulting, onsite training, upgrade planning…
see attached Customer Care Services 2018 Guide for more
information. All of this will allow Fort Collins to grow their
DOC-1.1
Customer shall be provided with all installation guides, testing, maintenance, operating and other
manuals and guidelines deemed appropriate to oversee successful installation and sustained
operation, monitoring, maintenance and troubleshooting of the system, including software
specifications and operating manuals. Including all necessary materials and installation guides.
Describe the online/portal documentation access/capabilities that the vendor provides.
SF
A softcopy of Full Documentation is provided with the system.
As well, manuals can be downloaded from our customer portal.
This portal provides the latest in security information, patches,
and documentation and is free to all customers. Videos are
available on a variety of issues to help re-familiarize the
operator/Administrator on almost any application.
DOC-1.2
Vendor shall supply or ensure web-based access all necessary up-to-date and accurate documentation
for installation, testing, quality assurance, equipment tracking, security, and operation of the system.
Customer requires that all software and associated release documentation must be provided
electronically in common Microsoft Office and Acrobat Reader PDF formats. The associated
documentation includes release notes, application notes, configuration documentation, installation
details, etc. No hardcopies with this information are to be provided to Customer.
SF
All updates and patches are applied before shipping. Softcopy
of documentation is provided and available for download via the
customer portal.
DOC-1.3
Vendor shall provide training and user documentation. All training materials shall be provided in
electronic format to FCU for unlimited use by FCU.
SF This is provided as part of the normal training process
DOC-1.4
Customer shall have the right to make and distribute as many paper and digital copies of all
documentations as it deems necessary for internal Customer use.
SF
DOC-1.5 Vendor shall provide Customer new or updates to the manuals when they become available. SF
DOC-2 Documentation List
DOC-2.1
Vendor shall provide, with RFP, a complete list of all system documentation that shall be made
available to Customer including a Table of Contents and Index for each document. Customer requires
that this list of documents will include, at a minimum, the following areas:
SF
DOC-2.2
Vendor shall provide, with RFP, System Architecture Documents, including system architecture
overviews, logical and technical architectures, and physical architectures of Customer
implementation.
SF See attached System Diagram
DOC-2.3 Vendor shall provide, upon award, User Manuals, describing the functions of the system. SF
DOC-2.4
Vendor shall provide, upon award, System Administration Manuals, including user account
management, levels of authority, backup and restore procedures, troubleshooting procedures,
etc.
SF
DOC-2.5
Vendor shall provide, upon award, Database Management System Manuals, including data
load, incremental update, data errors and troubleshooting guide, data backup and restore
procedures for the system and the Disaster Recovery system.
SF
DOC-2.6 Vendor shall provide, upon award, Configuration Manuals for the system. SF
DOC-2.7
Vendor shall provide, upon award, Maintenance and/or Troubleshooting manuals for the
system.
SF
SA-5.1
All system components shall have the capability for remote firmware and software upgradeability.
Describe in detail the mechanisms and processes used to update the system and all necessary
components including, but not limited to meters/modules, network equipment, communication modules,
etc. without system service interruption. Software/firmware updates shall be processed remotely and
run automatically once initiated.
SF
A 2-Factor VPN router is supplied with the system to allow ACS
to download updates, Patches, or new software to your system.
The router also allows our support team to diagnose any issues
in real time. If patch management is accepted, then a patch for
your system is uploaded to your patch server through the 2-
factor VPN Router. From there the patch is applied to all nodes
on your system.
SA-5.2
Describe in detail the process to recover from a corrupted software/firmware update to any device on
the system including, but not limited to meters, communication modules, network equipment, etc.
SF
The system is a redundant system, so that the fix or patch is
applied to the redundant node and service is rolled over to it.
The system is monitored and if an issue is found, then the
patch can be rolled back with no interruption of service. If no
issue is found, then the update/ patch/ fix is applied to the other
node.
SA-5.3
The ADMS shall support patching with standard recommended patches, OR the vendor must supply
patch information and testing within 30 days of patch releases from vendors. Please describe who is
responsible for patches and/or patch compliance and recommended patch procedures.
SF
Frank Hester is our Director of Customer Engagement.
Ultimately - he is responsible for your patching.
SA-5.4
The ADMS should be easily upgraded. Please describe the process for release and implementation of
software upgrades and tools included in the proposed ADMS solution to facilitate the upgrade process.
SF
SA-5.5
Describe the testing processes prior to each software release and what information is provided with
each upgrade (Attach the most recent software release notes and instructions provided with the most
current release).
SF See attached Release Notes Document
SA-5.6
Describe the tools included in the proposed ADMS Solution and recommended practice for validating
and migrating configurations and data from a Test environment to a Production environment. Please
include, as an attachment, your standard template for recording and change management for the
ADMS head-end configuration.
SF
Task Order 1 - 8790 Advanced Distribution Management System Page 43 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
SA-5.7
The ADMS should not require frequent upgrades. Describe when the utility must upgrade to the most
recent release and any impacts to operating without upgrades. Include a list of the upgrades, service
packs and head-end released for general availability over the last 36 months.
SF
PRISM 11 was rolled out in 2016. PRISM 11.2 will be out in
October as the first release of our "Blueprint" Methodology.
The BluePrint is a new ACS methodology in which software for
ACS applications will already reside on each system that is
delivered. This step allows ACS and its customers to be
confident that the correct software is installed on each system
in a standard way. From here each customer will have their
software configured appropriately for the needs of their system
and consumers. For customers who may have custom
applications or customs changes that differentiate it from a
standard delivery, these customizations will be implemented
under specific Custom folders already located in the standard
delivery model. Also included in the BluePrint methodology is
the ever-current system, which means that ACS will be
releasing application updates for Red Hat and PRISM
applications on a periodic basis to be sure each customer is
running the latest and greatest of our software. Advanced
Control Systems aims to identify and resolved problems and
bugs in software before a customer is even aware there may be
a bug or problem in the software. ACS is excited to deliver a top
of the line product in a standard and consistent manner, yet still
allow each customer the ability for customization.
Moving forward, we plan to introduce a minor upgrade every
quarter. This upgrade will be pushed out to all existing
customer as part of our BluePrint methodology. The next major
upgrade is planned around 2020.
Task Order 1 - 8790 Advanced Distribution Management System Page 44 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
ADMS Solution Roadmap and Future Enhancements
Category Requirement
RM-1 Product Roadmap, Lifecycle and Enhancements
RM-1.1 How long has the vendor been offering an ADMS solution?
RM-1.2
How many ADMS implementations does the vendor currently have in service?
In service is defined as the ADMSI solution is in production, operated on a 24x7
basis.
RM-1.3
Please provide the product roadmap for the next 24 months in the section to
the right. Alternatively, a separate attachment can be provided
RM-1.4
Describe the Software Development Lifecycle, including but not limited to
Vendor's unique methodology, tools, best practices, quality gates and example
artifacts.
RM-1.5
For the Vendor's proposed system: a) define the planned major releases of the
product over the next 3 years. Provide an overview of the significant features
and capabilities planned or anticipated to be provided.
RM-1.6 Provide a history of major releases for the product over the past 24 months.
RM-1.7
Describe Vendor's process to solicit and incorporate customer feedback on
features, functions, enhancements, etc. that the customer would like to see
Vendor incorporate into future releases.
Comments
ACS always encourages our clients to provide feedback for product enhancements,
alternate solutions, or ideas to streamline certain processes. These are generally
given to the sales representative during a call/meeting or submitted to the helpdesk
as a product enhancement by phone/email. Both are gathered on a periodic basis
and vetted by our Business Solutions team, Research & Development, and Qaulity
Test & Release team to determine if it can be standardize and make business sense
to move forward with said recomendation.
ACS has 32 cstomer system that utilize a distribution model, of which 15 have ADMS
applications deployed. There are 13 PRISM OMS systems deployed.
ACS first delivered advanced DMS applications on the system we deployed to Tawian
Power Company (TPC) in 2000, which is still in operation today. The OMS
functionallity was added to bring full ADMS capability to the PRISM platform in 2007
with delivery to the City of Anaheim, CA.
Please refer to the Roadmap document attached separately.
The Sofware Development Cycle is comprised of several parts, in which each part
helps to set/enforce standards to produce a quality product. This cycle begins with a
collaboration to create the requirements for the new development. After
requirements are set then brainstorming is done to identify a standard (if possible)
and effective way to solve the issue based on the establised requirements. Once a
best practice decision has been made the development of the software will begin.
After completeing the intial development the programming engineer will check the
product once again against the given requirements. When approved the new
product, its requirements and any testing results are passed to the QTR (Quality Test,
& Release) department in which testing is completed and tracked via the HP Qaulity
Center. After passing all tests in the Quality Center ocassionally we may implement
beta testing at this point. After completing this thorough testing process a document
is circulated confirming everyone is away of the new software development before
the general release.
Please refer to the Roadmap document attached separately.
In decending order BluePrint 11.3 (software suite), BluePrint 11.2, Prism 11.0.1, Prism
Task Order 1 - 8790 Advanced Distribution Management System Page 45 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
RM-1.8
Describe Vendor's support of its system upgrades and service patch releases.
Specifically address the process and timeframe to regression test Vendor's
system with each service patch release and major operating system revision
release. Describe Vendor's schedule for major releases.
RM-1.9
Vendor shall indicate compliance and provide the definition of on-going
software updates and upgrades in relationship to base License and annual
Maintenance Fees or any additional required cost anticipated.
RM-1.10
a) “Updates” and "Upgrades" mean product or other maintenance releases of
the Software that correct processing errors and other faults and defects found in
the previous minor or major releases of the Software. This includes all
modifications, revisions, additions, alterations, error corrections of the Software
that represent minor or major releases of new versions of the Software. All
updates would be provided under the maintenance and service agreement at no
additional cost. Vendor shall indicate compliance with this requirement.
RM-1.11
b) New Software modules which create new functionality and would not be
enhancements. Enhancements to existing functionality would be considered
Updates. Will these be considered amendments to the base license and
amended to the master license agreement?
RM-1.12
Vendor shall describe the communications, license term, support services and
process that would be offered to support a future core product change that
would effectively render the currently licensed version into a future state of "un-
supported" or retired version.
RM-1.13
Vendor shall provide or describe the Change Management Plan in support of
software Updates. This plan should address a minimum of basic elements
including: Communications; Change Risk; Priority; Customer Impact;
Description of Change; Systems affected; Programs Impacted; Implementation
Procedure; Back-out Procedure; Testing Procedure; Post Change Success
Criteria; Post Change Review Notes. Vendor shall include a sample Release
Notes document.
See attached Release Notes Document
Major operating system upgrades are determined by Red Hat Enterprise Linux
release dates. All updates are tested in house first for 45 to 60 days to verify
program compatibility with all new software changes. All system patches or minor
upgrades are gathered from Red Hat at the end of the month and tested for a week
All software updates are released on a monthly or quarterly basis. Each release is
tested and stamped with a version for tracking purposes. All minor releases do not
require a license update while major releases may require the license to upgrading
Comply
Enhancements/Updates will not be considered an amendment to the the base or
master license. New software may require an license addition or amendment.
ACS will periodically send out EOL notifications if software support will be
discontinued at least 1 year prior to the end of support. There will also be multiple
notifications as the EOL date approaches. After support ends ACS is committed to
help every customer as much as we can though no software updates are created
after EOL date has passed
Task Order 1 - 8790 Advanced Distribution Management System Page 46 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
ADMS Testing and Training
Requirement Response Comments
TT-2 Functionality Acceptance Test (FAT)
TT-2.1
The Vendor shall execute, with Customer oversight, a functionality acceptance test of the
solution. The purpose of the FAT is to verify that the technical, functional, performance,
information, and commercial specifications proposed by Vendor to Customer can be realized
as expected. Successful completion of the FAT by Vendor, and acceptance of the results by
Customer, shall be a pre-requisite for continuance of solution deployment. Vendor shall
acknowledge its compliance with this requirement.
SF
ACS Response: Comply
The FAT will be available for Customer oversight at our facility in
Norcross, GA.
TT-8 Training
TT-8.2
Vendor shall provide functional training to Customer personnel as necessary to install, test,
troubleshoot, operate, and maintain the system through its operating life.
SF
Functional training classes are offered on a rotating basis from our
offices in Norcross, GA. Custom, or individualized, classes can be
developed as needed.
TT-8.3
Vendor shall provide system integrator/administrator training for personnel assigned to
configure, integrate, operate, and maintain the software, including training on the design and
use of all Vendor supplied administration and configuration tools.
SF
Adminstration training classes are offered on a rotating basis from
our offices in Norcross, GA. Custom, or individualized, classes can
be developed as needed.
TT-8.5
Vendor shall provide, with RFP, a syllabus of its training courses that encompass all aspects of
the system from installation through sustaining operation. Vendor shall provide its
recommended schedule for such training, including recommended attendees by organization.
SF See attached Training Directory
Task Order 1 - 8790 Advanced Distribution Management System Page 47 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
ADMS Security
Category Requirement
SC-1 Access Domain
SC-1.1
Describe your policies and processes to ensure that default account configurations including
names, passwords, etc. are changed across all systems and assets
SC-1.2
Describe your established Access Management policies and processes for employee and
customer accounts including requests, approvals, provisioning, password assignment
requirements, access controls, de-provisioning, etc.
SC-1.3
Describe your process and timing requirements for revoking access for employees and other
actors which leave the organization or assume new roles
SC-1.4
Describe your policies and controls to enforce unique userIDs and restrict account sharing
among multiple people/actors
SC-1.5
Describe additional compensating controls in place to ensure user accountability for shared
user accounts
SC-1.6
Describe how systems and other assets enforce account lockout after a configurable number
of failed authentication attempts, including constraints/limitations
SC-1.7
Describe all controls in place to protect files, scripts or other assets that may have user,
system or other passwords/credentials stored within them.
SC-1.8
Describe how systems and other assets provide protection (e.g., encryption, hashing, jailed
files, etc.) for stored credentials
SC-1.9
Describe how all systems and assets that store or process customer information implement
and enforce access controls based on "deny by default" and "least-privileged" methodologies
SC-1.10
Describe any use of Multi-Factor Authentication for systems and assets including scope,
implementation, tools, and scenarios (e.g., always, remote access, etc.) and specifically for
privileged users such as Administrators
SC-1.11
Describe your established Password Management and Requirements policies and processes
including but not limited to password length, complexity, strength, entropy, aging, retries,
reuse, limitations on userID or account names in passwords, as well as assuring that there are
no master/default passwords embedded in firmware, etc.
SC-1.12
Describe how your systems and assets support and enforce Role-Based Access Control for all
users/actors, with Roles and Permissions assigned to those Roles
SC-1.13
Describe your established Access Review process including scope, frequency,
roles/permissions, approach, approvals, evidence, audits, etc.
Comments
The operating system uses salted hashes to store credentials.
The OS is configured to respect users and groups. If your username is not in a specific group
you will not be allowed access by default. Our PRISM application runs under the "acs" group
and users must be assigned to that group in order to use that application. Other users are
denied access.
We always use multifactor access throug a dedicated virtual machine for remote access. We
are designing a mechanism for multifactor access for operators.
We don't have passwords embedded in firmware. VPN password management is to change
passwords every 15 months. Passwords for VPN keys are 8 characters with a Cap, letter,
number and special character. VPN key passwords are set by the VPN Administrator.
The operating system contains users and groups. Roles are related to groups and the OS
enforces group permissions. PRISM SCADA contans roles such as Operator, Distribution
Coordinator, etc.These roles are assigned to certain areas and Areas of Assignment/Areas of
SC-1.14
Describe how your assets (servers, workstations, mobile devices, etc.) implement authorized
use banners and provide examples of typical verbiage
SC-2 Application Domain
SC-2.1
Describe how your application protects against common inbound attacks such as SQL
Injection, XSS, etc.) in both the client-side and server-side areas of concern.
SC-2.2
Describe how your application protects data at-rest (e.g., encryption, etc.) and in-transit (e.g.,
TLS, etc.) including specific technologies and versions.
SC-2.3 Describe how your Application protects sensitive data (e.g., passwords, PII, etc.).
SC-2.4
Describe how your Application protects outbound data to ensure that sensitive information
(e.g. username or password) is not presented back to the end-user following data validation,
authentication or other errors.
SC-2.5
Describe how your Application implements Directory services (e.g., Active Directory, LDAP,
etc.) for Authentication, Authorization. For a Managed Services solution describe if and/or
how your system would integrate with Customer's Active Directory.
SC-2.6
Describe all Application capabilities for logging and auditing user transactions including data
elements and linking specific users to specific transactions.
SC-2.7
Describe your approach and infrastructure for deploying, updating and utilizing anti-virus, anti-
malware, anti-spyware tools on all Application assets including servers, desktops, laptops,
mobile devices and other assets regardless of platform including but not limited to tools,
update frequency, scan scope (on-access, quick, full-system, etc.), scan frequency, etc.
SC-2.8
Describe all password and authentication rules/requirements/policies enforced by your
application including but not limited to minimum length, complexity, aging/expiration, reuse,
retries, etc.
SC-2.9
Describe how your Application supports and enforces Role-Based Access Control for all
users/actors, with Roles and Permissions assigned to those Roles
For data in transit we use TLS. For data at rest backups are encrypted.using AES 256.
The OS salts and hashes passwords. PII is not present in SCADA but only in advanced
applications like OMS. That information is stored in a database on a secured network.
Passwords are not echoed back during authentication.
We use Red Hat Identity Management (IdM) as a Linux directory server for single sign on.
IdM has the ability to integrate with the customer's Active Directory.
In the operating system auditing is turned on. Within PRISM SCADA users are assigned to
displays and devices each of which log important associated actions to an event log.
We deploy antivirus in two modes. Updates are collected here at ACS and deployed at the
customer site or updates are collected at the customer site and deployed locally. When
hosted here, updates are collected monthly, tested within our test environment and those
updates are deployed with the OS updates. Signatures are first deployed in the development
environment, tested and then deployed to production. If the AV console is deployed at the
customer site, the customer can determine when to deploy. We use Trend Micro for AV and
on-access scanning is enabled. On critical systems, deep scans are done by the customer
when there is no dander of impacting operations. For non-critical systems, update frequency
is approximately every 3 hours and the client scans at regular intervals.
In the operating system password rules are configurable to include: 1) history, 2) size, 3)# of
digits, 4) # upper case, 5) # lower case, 6) # other characters, 7) # of required character
classes, 8) # consecutive repeated chars, 8) # of chars repeated from old password, 9)
whether password complexity rules apply to the root/admin user
PRISM SCADA contans roles such as Operator, Distribution Coordinator, etc.These roles are
assigned to certain areas and Areas of Assignment/Areas of Responsibility are enforced by
SCADA PRISM
Customer servers contain authorized use banners on request of the customer. Typical
verbiage is:Warning: This Information System is actively monitored.
SC-2.10
Describe all formal Secure Development Lifecycle (SDL) and Software Development Lifecycle
(SDLC) methodologies in use by your organization
SC-2.11
Describe all mechanisms used by your Application to implement user session functionality
(e.g., cookies, etc.).
SC-2.12
Describe any capabilities and configurability for your Application to impose session time-out
and/or lockout triggered by user inactivity or other conditions.
SC-2.13 Describe how your Application implements or integrates with SSO solutions (e.g., SAML, etc.)
SC-2.14
Describe how your Application implements authorized use banners, all methods of
configuration and provide examples of typical verbiage
SC-2.15
Describe your process for communicating application vulnerability information to your
customers and performing vulnerability remediation
SC-3 Cloud Domain
SC-3.1
Describe your backup approaches, procedures and infrastructure including:
Approach (3-2-1 or similar)?
Storage location, format and protections/controls for backup media?
Length of time to retrieve backups to start of restore?
Personnel access to backup media?
Backup and restore testing approaches and frequency?
Approach for securely providing backup data and media to customers at service end *OR*
end-of-life disposal?
SC-3.2
Describe your BCP and DR approaches, procedures and infrastructure including:
Formalized BCP & DR plans?
Frequency of updates for these plans?
Are current copies of these plans stored off-site from the production facilities to which they
apply?
Specific facilities and assets included in the plan?
Testing methodology (e.g., tabletop, walk-through, failover/failback, etc.), frequency,
documentation, results?
Formalized RPOs and RTOs?
SC-3.3
Describe all controls employed for data segregation from ALL other shared environments,
resources
SC-3.4
Describe all components which are deployed in Virtual environments (e.g., servers, storage,
network, etc.) and the virtualization approach and components in use (e.g., VMWare, Hyper-
V, Xen, etc.)
Authorized use banners are available when logging into critical servers and can be added to
other servers as required using the MOTD functionality of Linux.Typical verbiage is:
"Warning: This Information System is actively monitored.
This System may be accessed by authorized users only!
Unauthorized actions on this System will be prosecuted."
We communicate serious vulnerability information through email to the primary support
contacts. OS remediation is done via our patch management process
We would use disk snapshots to perform backups. Those would be done at specific times
using scripting. There would be no backup media as the snapshots would remain in the cloud.
Restores involve deletion of the existing VM and the building of another with the disk from the
backup. Testing backups would involve creating another VM and verifying its functionality. At
service end we would have to export data from the Google Cloud.
We don't yet have these procedures for a cloud environment. However, for Business
Continuity and Disaster Recovery we would make your account multiregional within the United
states. RPO and RTO would be unnecessary as Google would move your environment to a
data center within another region.
We would host your environment either within a separate account or within a separate project.
SC-3.5
Describe all components which use proprietary approaches or components for segregation or
virtualization including developer and previous security testing performed
SC-3.6
Describe requirements and procedures for document control and destruction of physical
documents (e.g., shredding, incineration, etc.)
SC-3.7
Describe requirements and procedures for media control and destruction of digital
information (e.g., degauss, physical destruction, secure wipe, etc.)
SC-3.9
If to be included as part of proposed ADMS solution, describe explicit details for:
Hosting Provider?
Hosting facilities' location(s)?
Hosting models proposed (e.g., SaaS, PaaS, IaaS, NaaS, etc.)?
SC-3.10
Describe all internal and external/3rd party compliance and vulnerability audits performed by
provider including auditors, frequency, results
SC-3.11
Provide a copy of ALL audit results for the last 3 years including attestations of finding
remediation
SC-3.12
Describe any use of third parties for providing services in your cloud model including details
for:
Names and roles?
Contractual and security requirements in force for each third party?
Security assessments and results performed for each third party?
SC-4 Data Domain
SC-4.1
Describe data backup policies and processes including but not limited to scope, schedules,
frequency, encryption, archival, disposal, completeness reviews, restoration verification,
on/off-site storage, adherence to 3-2-1 methodology, etc.
SC-4.2
Can you ensure hard drive encryption consistent with validated cryptography standards as
referenced in FIPS 140-2, Security Requirements for Cryptographic Modules for all personal
data?
SC-4.3 Describe any Data-Loss Prevention (DLP) controls/solutions that you utilize
SC-4.4
Describe all data masking capabilities for data repositories, applications and other assets that
will obfuscate/replace/protect sensitive data elements
SC-4.5
Describe all policies and procedures for ensuring and monitoring the security of customer
data
SC-4.6
Describe all approaches for securing customer data AT-REST including but not limited to
encryption (e.g., type, key standards, key management, key administration, etc.) and other
approaches/controls
We use Storix as our backup product. We work with the customer to determine a backup
schedule and format such as a 3-2-1 approach. Backup media is either removable disk or
tape. Backup data is encrypted. Backup servers can be placed on a separate DMZ. Storage
locations are at the customer site with offsite backup arranged by the customer. Restore
testing is under the customer's control. We normally do not maintain customer backups at our
site.
Internally our systems are loaded on virtual servers and we use Veeam to backup our servers
We can insure this for removable media sent/received from the customer.
We use Tripwire Enterprise for DLP in customer systems
The Oracle database that we deliver has data masking capabilities
We store customer information at our site in a safe. For customer passwords we store those
in LastPass which is accessed via multifactor authentitcation. For staged customer systems
those are behind a firewall/NAT router
Customer data at rest is stored in LastPass which is accessed with multifactor authentication
SC-4.7
Describe all approaches for securing customer data IN-TRANSIT including but not limited to
encryption (e.g., type, key standards, key management, key administration, etc.), SFTP+PGP,
VPN and other approaches/controls
SC-4.8
Describe all additional security controls that protects data that contains PII, CIP-constrained
or other highly sensitive data
SC-4.9
Will our data be co-mingled or co-located with data from other clients? Describe the logical
and physical controls and partitioning in-place to protect data confidentiality, integrity and
access
SC-5 Network Domain
SC-5.1
Describe any access you require to our network resources, and if so your
approaches/requirements
SC-5.2
Describe your approach to monitor, identify and prevent unauthorized network connections
or connection points (e.g., rogue access points, etc.)
SC-5.3
Describe your approach to host/network-based integrity checking for endpoints that allows
only endpoints with sufficient OS, patching, malware protection, etc. to access networks and
other assets
SC-5.4
Describe your approach to email traffic monitoring and protection including scope, tools,
spam filtering, malware monitoring, support for email encryption (SMTP/TLS, S/MIME, other),
etc.
SC-5.5
Describe your approach to establishing, deploying and managing Network Enclaves that will
protect the our systems and assets, including but not limited to network segmentation (logical
and/or physical), firewalls, NAC, IDS/IPS, malicious traffic monitoring, etc.
SC-5.6
Describe all security controls implemented for any wireless networks within your corporate,
hosting and data processing facilities
SC-6 Personnel Domain
We use multifactor IPSEC VPN with 2048-bit keys using AES 256 encryption for our VPN
access. We connect using windows 10 VMs that are used only for connecting to customer
networks.Within the SCADA netowrk we use SSH to securely transfer data between machine.
It is possible to have the Red Hat IdM server handle the key management process to make it
more convenient.
We follow our customers CIP data management requirements when connecting to their
system
We need remote access to the delivered system and to any ACS existing system. We provide
a Cisco 1921 SEC/k9 with Advanced IP Services device configured for remote VPN. You
would provide a public IP address and place this device on your WAN or behind your firewall.
We would connect via our VPN client with your permission. You have the ability to turn the
device off when not in use or use firewall rules to prevent our access.
In delivered systems, we can send logging information from network devices to the provided
logging server from which notifications can be generated if any but the identified devices are
present on the network.
On our corporate network we are in the process of implementing a Network Access Control
solution.
We have not delivered a NAC system to customers. We will install the Tripwire agent on all
servers/workstations in delivered systems.
We are implementing NAC at our corporate office.
We have applications that send specific emails from the SCADA system. The SCADA system
itself does not receive email. We use SMTP/TLS when the far end requires it. Our email
server will have antivirus to deal with any malware sent out of the system.
We deliver firewalls that segment networks and only allow the defined traffic to flow with deny-
by-default rules.We have not delivered NAC to customers, but we can use hardware IPS/IDS
as a separate network device and host-based IDS
SC-6.1
Describe all established elements, binding scope and conditions of any confidentiality and non-
disclosure agreements for all employees, contractors and partners engaged with your
organization
SC-6.2
Describe all established elements and binding scope of a formal, documented Security
Awareness Program for all employees, contractors and partners engaged in your organization
including but not limited to: training scope and frequency, drills/tests, etc.
SC-6.3
Describe your established policies and procedures for conducting background checks for all
employees, contractors and other personnel including but not limited to criminal, drug, credit,
employment history, etc.
SC-6.4
Describe all current or planned use of offshore (outside of USA) resources as part of your
customer delivery strategy
SC-6.5
Describe all physical security controls protecting all data processing assets and facilities
including but not limited to access card systems/doors/gates, security guards, CCTV, sensors,
mantraps, etc.
SC-7 Security Management Domain
SC-7.1
Describe all elements of your established Business Continuity Plan (BCP) including priorities
based on risk and impact analysis to your organization and your customers' organizations
SC-7.2
Describe all elements of your established Disaster Recovery Plan (DRP) including priorities
based on risk and impact analysis to your organization and your customers' organizations
SC-7.3
Describe all policies, procedures and timing o ensure that your BCP and DRP elements are
tested for effectiveness including approach (e.g., tabletop, walk-through, partial/full failover-
failback, etc.)
SC-7.4
Describe your established policies and processes for ensuring compliance relative to internal
and/or external security policies and requirements
SC-7.5
Describe your established policies and processes to ensure independent assessment and
validation of your controls
SC-7.6
Describe how you identify, monitor and enforce segregation of duties relative to assets,
information, functions and services
SC-7.7
Describe how you extend, monitor and enforce your security management policies and
procedures to all contractors and third-party partners including agreements, risk assessments
and notification to customers of changes
Each person who requres access to customer sites must receive approval from the Director of
Customer Care. This includes any contractors. We notify customers of any changes in status
within 24 hours of the change.
Financial Business processes require either dual authorization/review (cash disbursements,
cash receipts, payroll, capital expenditures). Segregation of Duties is enforced via Company
policy and ERP/Network system access. Controls are reviewed and updated periodically or
as change occurs.
We are ISO-9001 compliant and have an audit each year.
Our confidientiality agreement with covers: ACS’s Intellectual Property, Computer processes,
Computer programs and codes, Customer lists and potential customer targets, Customer
preferences, ACS, customer or vendor financial information, Marketing strategies and
materials, including price lists, New materials research, Research and development
strategies, and developmental materials, Pending projects and proposals, Proprietary
production processes, Technological data, including without limitation transformer drawings,
Our security awareness program for employees connecting to customer sites is to have each
person trained using the 13 hour Information Security Basics (AWR-173-65) course. We then
have a NERC CIP-based refresher course each year. We participate in our customers' NERC
SC-7.8
Describe all formal and documented Security policies and processes published and available
to all employees, contractors and partners as well as their basis (e.g., NIST, COBIT, ISO/IEC,
etc.)
SC-7.9
Describe your established process for regular review and update of all security policies and
procedures, including provisions to address any changes in laws or regulatory guidance
SC-7.10
Describe how employees, contractors and partners are required to accept security policies
and procedures upon joining your organization and when these policies and procedures are
updated
SC-7.11
Identify and describe in detail your compliance with and all certifications and relevant dates
for any industry-accepted control standards (e.g., NERC-CIP, NIST Cybersecurity Framework,
NIST 800-53, SSAE-16, SOX, SAS-70, PCI-DSS, ISO/IEC 27000, etc.)
SC-7.12
FCU may use BitSight (like a credit report for cyber security) to assess Vendor internet-facing
security. Do you subscribe to BitSight or a similar service, and if so are you willing to provide a
sanitized report?
SC-8 System Domain
SC-8.1
Describe your controls and restrictions relative to administrative access on all servers,
desktops, laptops and mobile devices
SC-8.2
Describe your organization's formal and documented Asset Management policies and
procedures
SC-8.3
Describe your organization's established Change & Configuration Management policies and
procedures including enforcing appropriate testing, review, approval, promotion to
operations and back-out plans, etc.
We do not subscribe to that plan or a similar one.
We meet NERC CIP standards for a third party provider. We have recurring seven year
background checks for employees. We participate in the security awareness programs of our
customers
Administrative access to servers is restricted to network administrators. Most employees do
not have administrative access to their desktops/laptops unless they are engineers. Some
have separate admin accounts others have admin as a part of their account. We are
migrating to separate admin accounts for all employees who need administrative access.
Employees have administrative acces to phones.
ACS primary assets are internally developed software . See attached capitalized software
procedure. All other asset purchases require approval by the CFO and/or CEO.
All changes before implemented in production are first tested against the current standardized
release. Once a change has been implemented and tested it must be approved by and
signed off on by Research & Development Department, Customer Care Department, and
Quality, Test & Release Department. The changes are also published in a common place for
tracking purposes. In emergency cases where a change must be made immediately to
address an urgent issue, once the urgent issue has been addressed this change is then sent
through this same process to confirm standardization and long term usability. When
implementing changes ACS prefers to makes changes first in a customers test environment
or QA system (a requirement for patching services) to first confirm system performance. If a
QA system is not available changes will be made on a backup or standy node first to confirm
system performance. If any issue occurs during this confirmation process all changes can be
rolled back from other common nodes to return system to original state.
Employees are required to accept the policies and procedures of the organization, including
the Handbook, upon hire by signing an Employee Acknowledgement. For contractors, their
signature on the contract attests to their adherence to our policies. Policies are updated as
employment laws and applicable regulatory requirements are changed and updated.
The employee handbook contains information on the individual's need to meet security
standards. We also have a Security Vulnerabilty Policy available to all employees. It was
required for NERC CIP compliance. Some policies are based on NIST.SP.800
SC-8.4
Describe your formal and documented policies, processes and approach to defining,
deploying, modifying, managing, enforcing and reviewing standard security configurations
(e.g., policies, hardening standards, etc.) for all systems and assets.
SC-8.5 Describe any host-based IDS/IPS solutions that you utilize
SC-8.6
Describe how all systems and assets are configured to capture and log successful and
unsuccessful user authentication and authorization attempts, and how long system log files
are retained to support access control monitoring, security investigations, forensics and other
relevant activities
SC-8.7
Describe your approach and infrastructure for deploying, updating and utilizing anti-virus, anti-
malware, anti-spyware tools on all assets including servers, desktops, laptops, mobile devices
and other assets regardless of platform including but not limited to tools, update frequency,
scan scope (on-access, quick, full-system, etc.), scan frequency, etc.
SC-8.8
Describe your organization's established Patch Management policies and procedures
including enforcing appropriate timing and processes for testing, review, approval, promotion
to operations and back-out plans, etc.
SC-8.9
Describe the logical and physical isolation/separation of your Development, Testing, QA
facilities/environments from customer Production environments
SC-9 Logging Domain
SC-9.1
Describe the auditing and logging mechanisms implemented for all systems components (e.g.,
applications, middleware, databases, operating systems, hypervisors, network devices, etc.)
SC-9.2
Describe the data elements of all logged events (e.g., date, time, event type, userID,
username, hostname, IP address, key event details, etc.)
SC-9.3
Describe logging extent (e.g., number of transactions, number of days, etc.) and retention
(e.g., by days, number of files, etc.)
SC-9.4
Describe ability to capture logs and alerts relative to sensitive files/assets, users with elevated
privileges, etc.
ACS software is designed to comply with NERC/CIP policies that fit within the scope of 3rd
Party software. ACS will also give recommendations to enhance customer security and
increase system stability/functionality. Each system is checked and all high vulnerability
threats addressed before shipment, and confirmed by Quality, Test and Release Department.
Any software security threats are addressed and documented during the standard patching
process which also notifies customer of threats that may have been addressed.
We deploy Tripwire and/or Trend Micro Antivirus which includes a host-based IDS.
Successful and unsuccessful logins are sent to the Tripwire Log Center and can be kept for a
configurable amount of time.
We deploy antivirus in two modes. Updates are collected here at ACS and deployed at the
customer site or updates are collected at the customer site and deployed locally. When
hosted here, updates are collected monthly, tested within our test environment and those
updates are deployed with the OS updates. Signatures are first deployed in the development
environment, tested and then deployed to production. If the AV console is deployed at the
customer site, the customer can determine when to deploy. We use Trend Micro for AV and
on-access scanning is enabled. On critical systems, deep scans are done by the customer
when When there we patch is no RHEL dander each of impacting month we operations. create a repository For non-critical on our systems, Red Hat Network update frequency Satellite
server containing all patches we will deploy for the month. We then patch our test
environment and validate the patches do not interfere with its operations. We then use that
repository to patch customer systems. The cusotmer is required to backup his system before
we patch as restore from backup is the only means by which we recover from a failed patch.
Then we patch the customer's development environment and allow the customer to test
operations to ensure that there are no issues. Once approved, we then patch the production
Internally we have customer physical systems behind firewalls/routers as we simulate the
customer network during deployment. After customer systems are in production, we access
SC-9.5
Describe your approach for time synchronization for servers and other assets (e.g., common
source, etc.)
SC-9.6
Describe policies, processes and procedures for regular logging and audit reviews as well as
reviews in response to security events
SC-9.7
Describe your implementation of Security Information and Event Management (SIEM)
technology for security log retention long-term, as well as event monitoring and correlation,
and event alerting
SC-9.8
Describe how you will support conducting vulnerability assessments and penetration testing
for assets that will house or process our information
SC-9.9
Describe all implementations of file versioning supported by all relevant assets (e.g., systems,
applications, etc.) and how many versions are configurable
SC-9.10
Describe all storage types and approaches for data housing (e.g., SAN, NAS, hybrid cloud,
storage management, etc.) and associated file systems
SC-9.11
Describe how our data is protected if law enforcement access or seizes hardware or other
assets on which our data is housed in colocation with other data
SC-9.12
Describe all relevant SLAs, disclosure agreements, policies, processes and procedures for
notifying us in the event of security incidents, breaches or investigations; also describe timing,
points of contact for these activities
SC-9.13
Describe your support for our security team to access relevant data and artifacts in response
to forensic investigation
SC-10 Threat Management
SC-10.1
Describe your approach to regular Vulnerability Assessment and Scanning, both internally-
performed and externally-performed, including frequency, scope, tools and communication of
findings to your security resources
SC-10.2
Describe your formal Threat and Vulnerability Management policies and processes including
threat identification (e.g.,, alerts, scans, etc.), risk assignment and remediation management
with required timeframes.
SC-10.3
Describe your established Incident Response policies and procedures for addressing security
incidents including responsibilities, evidence preservation, chain of custody, customer
notification, etc.
We will assist a customer in resolving a security event at the customer site.
We deploy Tripwire Enterprise and Tripwire Log Center to perform this function. Tripwire also
automates many of the reports required by NERC.
We will consult with your vulnerability tester and penetration tester as necessary
We use a document management system which automatically manages file versioning.
Our security consultant has placed us on a schedule to create these policies see 01 ACS
Security Review Final for Fort Collins.pdf (attached)
We generally use DAS (Direct Attached Storate) using ext4 for Linux and ASM for Oracle. We
can also use gfs2 for shared Linux file systems.
Your data will not be protected in this case. However, we will not normally have any of your
operational data in our systems as we will remove any virtuals after delivery.
We have created system access agreements with individual customers
Since we will connect to your system using virtual machines. We can provide access to that
virtual. We would use our outside consultant to interface to your forensic team.
We use Nessus to scan devices on the network. Our network admin does the scan will inform
our director of IT.
We don't have formal policies but should there be a serious issue we have an external
security consultant who has assisted us in risk assignment and remediation.
We install one or more GPS clocks in each site. All critical servers point to the GPS clock as
their primary time source. The primary servers are also configured to synchronize with one
another and be backup time servers in the case of a failure of the GPS.
Task Order 1 - 8790 Advanced Distribution Management System Page 56 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
those systems through an IPSEC VPN client installed on a separate virtual machine used only
for accessing customer systems
We deploy Tripwire Enterprise and Tripwire Log Center to allow the collection of logging and
audit information. We allow all devices on the critical network to log intformation.
The data elements of logged events depends somewhat on the system. The date and time are
critical for logged data. Other information would depend on the device.
Logging extend and retention would depend on the configuration of the server. Normal
requirements are to maintain logs for 90 days.
We can audit and log user login/logout and audit access to files.
Task Order 1 - 8790 Advanced Distribution Management System Page 55 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
We have an ISO 9001 audit each year and our policies are reviewed as a part of that process.
Task Order 1 - 8790 Advanced Distribution Management System Page 54 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
CIP quarterly information security awareness programs.
We perform a seven-year background check for all employees that connect to or visit
customer systems. That check includes criminal, credit, employment, education history. Drug
screening is done before hiring.
We have an office in Taiwan that works on mapping projects. We have an office in India but
that office should not work on this project.
We have HID access cards for all entrances, each employee has assigned hours during
which he/she can enter the buiding. We have a CC camera system. Our security system is
integrated into our fire system.
The business continuity plan is centered around High Availability of critical resources. The
Company’s ERP(Infor CloudSuite), CRM(Salesforce), Email(Office 365), Critical Network
shares(Flexential), and Telephone system(Comcast Business Voice Edge) are all hosted or
backed up in the cloud. The cloud is also used to back-up the user local drives via
OneDrive(Office 365). In addition, there is primary(Comcast) and secondary(Flexential-
bundled with several providers) internet service. ACS has the unique position of being next
door to our hosted data center, Flexential, accessed by two direct fiber lines. The Flexential
facility is highly secure with certified compliances in AICPA SOC1-3, ISO27001,
HIPAA/HITECH, PCI DSS, and NIST 800-53 standards. Tthe Flexential hosted files are
Effective 10/15/2018, ACS will utilize a third party (Flexential) to provide Disaster Recovery As
A Service. The critical Network files are hosted in Atlanta, GA Data Center(next door to ACS)
and replicated in 7 minute intervals to the Louisville, KY data center. The failover process is
expected to have minimal impact internally and externally.
Effective 10/15/2018, The DRP will be tested twice annually. This will include a fail over from
all systems that are hosted locally to cloud based. This drill will also utilize the backup
internet service.
See attached.
Task Order 1 - 8790 Advanced Distribution Management System Page 53 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
The ACS corporate Wireless Network requires Network Authentication. In addition, the admin
console blocks non approved devices. The Guest wifi requires a password and is blocked
from all internal network resources; the guest network accesses the internet only.
Your data will be located at our factory. It will be separated from other customers data
physically by being loaded onto customer hardware or logically by being loaded only in virtual
machines that will be delivered to the customer.
Task Order 1 - 8790 Advanced Distribution Management System Page 52 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
or on a drive in a safe or on a staged system behind a firewall
This would be the Google virtualization environment.
Physical documents that that need to be controlled should be marked confidential. These
documents will be shredded when they are no longer needed.
We engage an external company to destroy digital media. Information is stored securely until
it can be destroyed.
We expect to be using the Google Cloud to host if we should host an ADMS in the cloud. We
would provide you with access to the system.
We don't have this for the Google Cloud
We don't have this for the Google Cloud
To be determined for the Google Cloud.
Task Order 1 - 8790 Advanced Distribution Management System Page 51 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
We would use the virtualization provided by Google.
We are aware of CIP-013-1 and are planning to be compliant in the future.
Some user sessions are managed through J-session ID which re-writes the URL for individual
sessions. Some applications store usernames are stored using webstorage and other
applications use cookies.
For the OS, user timeout and is configurable. For web-based applications, configurations are
based on the application.
We use Red Hat Identity Management (IdM) for Single Sign On. RHEL IdM can integrate with
RADIUS, LDAP. Integrating with SAML requires additional software.
Task Order 1 - 8790 Advanced Distribution Management System Page 50 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
This System may be accessed by authorized users only!
Unauthorized actions on this System will be prosecuted.
For web-based applications on the we scan with Nessus to validate the configuration.
Subsequent scans maintain this compliance. For publicly accessible sites, a third party should
be hired to maintain the security of the site.
Task Order 1 - 8790 Advanced Distribution Management System Page 49 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Responsibility are enforced by SCADA PRISM
When engineers access customer sites emails are sent to the user himself/herself, the ACS
adminsitrators and to the customer. Permission is received from each customer before a
connection is made. Should there be any issue, access records are kept for 3 years and
provided to customers on request.
We work with the customer after delivery to configure all default account passwords
The document SOP 30CC 14 Rev9 Compliance for ACS Employees (ID 236659).pdf
describes our internal procedures. Requests are made to the director of Customer Care, who
approves remote access. Users are then provided with a virtual environment from which they
access customer systems. VPN key passwords are assigned and changed every 15 months.
They must contain a capital, special, number, and lower case. Customers are notified of
change in status within 24 hours. A checklist is completed concerning the revoked VPN
Within 24 hours of a change in role, customers are notified via email and the processes above
are followed.
Each user is provided with a remote access token which uniquely identifies him and is not
shared.
For remote access, we use multifactor authentication and the customer is notified who is
connected to his system. Shared account usage can then be traced to the VPN.
We work with the customer to configure these for delivered systems. For VPN keys, there is
key lockout after 3 failed attempts.
We store customer information at our site in a safe. For customer passwords we store those
in LastPass which is accessed via multifactor authentitcation.
Task Order 1 - 8790 Advanced Distribution Management System Page 48 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
DOC-2.8
Upon System Acceptance, Vendor shall fully document the As-Built system and provide to
Customer this documentation.
SF
DOC-2.9
Vendor shall provide, upon award, system integration and standard interface specifications.
Systems integration requirements and designs specific to the Customer implementation shall
be supplied to Customer as part of the vendor's implementation services.
SF
SA-5 Maintainability
Task Order 1 - 8790 Advanced Distribution Management System Page 42 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
system to meet their ever-changing needs
MS-2.2
Vendor shall provide system installation, configuration, and support for user acceptance testing, as
required to implement the functional requirements of this specification.
SF
MS-3 Alternative Service Offering (Optional)
MS-3.1
Vendors are welcome to propose any other optional service offerings. If proposing an alternative
service offering, provide details such that customer sufficiently understands your offering and its value
to customer. SF
DOC-1 General Documentation Requirements
Task Order 1 - 8790 Advanced Distribution Management System Page 41 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
build the network model. This is a one-time requirement, since future changes to the
model will be incrementally updated in DASmap without the need for future imports
from Milsoft Windmill Engineering Analysis
INT_005
ADMS to GIS Portal - Publication from ADMS to GIS Enterprise Portal for display of ADMS outages and
restorations, switching, and operational state temporary edits
MD OMS data can be sent to the GIS as a process.
Task Order 1 - 8790 Advanced Distribution Management System Page 39 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
TR_INT-15
Offeror shall describe the solutions ability to integrate with IVR and prior experience with specific IVR systems that
have been integrated with/to SF
See response to TR_INT-15
TR_INT-16
Offeror shall describe their solutions approach to SCADA integration/data supported to at least the substation
devices SF
See response to TR_INT-15
TR_PERF Performance
TR_PERF-01 The system shall be able to render all of the electric distribution network within 120 seconds. SF
The electric distribution network call up time is very fast. The first callup will be
approximately a few seconds and after that search and location, pan/zoom
manipulation is instantaneous. Typcical SCADA one-line callup is less than 1 second.
TR_PERF-02 The system shall be able to render a single electric feeder within 5 seconds. SF
A single electric feeder is automatically generated dynamically from the model
(reshape), rendered and displayed in less than 5 seconds (typically 1 second)
TR_PERF-03 The system shall be able to trace a single electric feeder within 5 seconds. SF Trace function is performed instantly (less than 1 second)
TR_PERF-04 The system shall be able to render aerial photography within 10 seconds SF
Aerial photography, is performed in a browser call GridVu Network which is available
in the col=troll center and on a crew mobile device. It accurately shows the network
state, topology colorization, over a Google aerial map. The time to render the first call
up and to update real-time changes is less than 10 seconds from the time of the event
change recorded in SCADA.
Task Order 1 - 8790 Advanced Distribution Management System Page 38 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
requirements?
SF See response to TR_ARCH-8
TR_ARCH-9
For the ADMS solution provide a description of how your Solution, and processes that operate within your solution,
can be integrated with third-party monitoring and logging tools. Include a list of third-party monitoring tools your
solutions has been integrated with.
SF
3rd party Software includes monitoring and virus protection tools provided by
- RHEL – 7.5
- -Oracle – 12c Version 1 – (soon to be Version 2)
- -Web Browser – Firefox Quantum 60.1esr (64 Bit) – Mozilla Firefox for RHEL redhat
1.0
- Security software – Sophos Anti-Virus for Linux Version 9.15.0
- AutoCad – Map 2016 (for advanced DMS using DASdb7 we use MAP 2018*)
TR_ARCH-10
For the ADMS solution describe how and where configuration, and operation parameters are managed and stored
(within the relational database, XML files, etc.).
SF
Configuration and operational parameters are stored in the Relational Database, .ini
files, and property files.
TR_ARCH-11
For the ADMS solution describe the standard interfaces that will be used (MultiSpeak, CIM, IEC 61968, etc.). Provide
a description of how each integration maps to any standards.
SF See response to TR_ARCH-11
ADMS System & Non-Functional Requirements
Task Order 1 - 8790 Advanced Distribution Management System Page 37 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
*Automatically switch line capacitors to maintain CBC objectives (for automatic mode).
*Set all line capacitors in fixed or automatic mode.
Support
Intelligent
Alarming
ADMS_070
Offeror shall describe their solutions ability to provision for software
generated alarms
SF
The PRISM advanced software applications generate alarms to provide the operator information as to the state of automation and any problems the automation
may encounter that will affect its successful completion. The application generated alarms comply with the systems general alarms handling as described in the
response to ADMS_066, ADMS_067 and ADMS_069.
Switching
Study Mode
ADMS_079
Offeror shall describe their solutions approach using different
symbology to view distribution model between abnormal vs. nominal
state vs. operating states
SF See response to ADMS_079
Switching
Study Mode
ADMS_087
Offeror shall describe their solutions ability to switch between
production and training environments
SF
The training system should be configured as a separate system. Training scenarios create situations and alarm loading that should be separated from the mission
critical network and the actual operational environment. That is why aircraft simulators don’t have wings.
Task Order 1 - 8790 Advanced Distribution Management System Page 36 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
infomraiton is revealed.
Operate
Tagging
Devices
ADMS_040
Offeror shall describe their solutions ability to single query all
abnormal devices
SF
There are several methodologies provided to query abnormal device states. A dynamically built abnormal report can be requested and displayed. Also associated
with the graphical display, a list of all abnormal devices is listed and can be located on the graphical map by clicking on the abnormal device in the list.
The next version of the map network display can be colorized to show the abnormal elements in the configuration.
Operate
Tagging
Devices
ADMS_041
Offeror shall describe if their solutions offers wizards/other driven
approach to tagging based on type of tag
SF
The PRISM GOI user interface to set a tag is displayed when the device is selected and a Tag is to be set. A list of the tags available and the existing tags are
displayed. Multi level tags can be placed on a device. Also the user can customize the tags types and capabilities for each system implementation to match
existing tag processes and standard known usages.
Operate
Tagging
Devices
ADMS_098
Offeror shall describe their solutions approach to be able to read OPC
tags and data from SQL SCADA historical database.
MD
Excergy: Renumbered to ADMS_098 to avoid duplication with already numbered ADMS_085
OPC interface has been delevered in the past, however, this implmentation of OPC tags from historical data will rqeuire development
Perform Short
Circuit Analysis
ADMS_044
Offeror shall describe their solutions ability to support Fault
Magnitude, Fault Type (phase), and Protective Relay Targets from
Relay IED
SF
Fault magnitude and fault type (i.e. the phase) from relays and recloser controllers are supported. PRISM supports a variety of controller types from many
manufacturers in our device profile library which self-defines the DNP profile for the devices which are to be potentially used for self-healing and other automation
functions.
The library enables PRISM to communicate with a wide range of relays and controller/ IED types from different manufacturers. New profiles are being added
frequently upon customer request, and made available to the general customer population from our website.
Perform Short
Circuit Analysis
ADMS_045
Offeror shall describe their solutions ability to Provide Short Circuit
Analysis tools to determine possible fault locations based on pre-
fault loading data from SCADA, OLPF, distribution feeder model
SF See response to ADMS_045 Short Circuit Analysis with Fault Locatation
Perform
Switching
ADMS_046
Offeror shall describe their solutions ability to support a map view
that is capable of changing to match what happens when either
manual or automated switches open/close, including loadbreak and
switch operations
SF
The PRISM Map view provides realtime map changes when any event affecting topology(switch changes, ticket confirmation, etc) occurrs.
Excergy: added "open/close"
Perform
Switching
ADMS_092
Offeror should explain solutions ability to identify "normal open"
switch points (flag or indicator) in addition to the current switch
status. This is different from maintaining a "designed" state map.
SF
Normally open and designed states are supported. Designed state is typically a static field defined in the connectivity source (ESRI map), whereas the normally
open is an operating state that can change from season to season, or for any other reason. The ‘Normally Open’ (also normally closed) is flagged as ‘normal’ and
the abnormal report (see response to ADMS_040).
Restore
Outage
ADMS_050
Offeror shall describe their solutions ability to control distributed
assets for fault identification, switching, control of smart inverters,
and energy storage
SF See response to ADMS_050
Support
Intelligent
Alarming
ADMS_066
Offeror shall describe their solutions ability to compare
measurements against operating limits and alert operators to
abnormal conditions
SF See response to ADMS_066
Support
Intelligent
Alarming
ADMS_067
Offeror shall describe their solutions ability to support of the
following: Conditional alarms, Alarm prioritization, Alarm filtering,
Routing
SF See response to ADMS_067
Task Order 1 - 8790 Advanced Distribution Management System Page 35 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
(Load) distribution system model
SF
Methodologies to build the distribution power flow model varies from customer to customer. Typically, ACS will provide a spreadsheet to collect the device
parameters. This information is used in DASmap to populate the model imported from ESRI. However, in the case of Ft. Collins the specification mentions that a
Milsoft Windmill Engineering Analysis tool is used which contains the power flow information that ACS will need. ACS will only need to perform a one-time import
of the data from Windmill to build the network model. This is a one-time requirement, since future changes to the model will be incrementally updated in DASmap
without the need for future imports from Milsoft Windmill Engineering Analysis
Load Models
and Estimate
Load
ADMS_095
Offeror shall describe how proposed facilities replacing existing
facilities are used in OMS/ADMS for functions such as On Line Power
Flow (OLPF).
SF See response to ADMS_095
On-line
Incremental
GIS Updates
ADMS_052
Offeror shall describe their approach for consuming GIS data for low
fidelity (GIS has single point feature for Transformer "Bank" with
related/tabular transformer information and expands to high fidelity
model needed for OMS/ADMS operations) vs. high fidelity (GIS has
similar hierarchical/spatial model as required by OMS/ADMS) models
SF
The new model editor DASmap consumes the high fidelity data for connectivty model creation, coupled with singel point asset data and /or Milsoft model data it
build the Power flow model. Single point asset data is available for
operator on-line query to display asset information in the SCADA displays, similar to the Hanssen CIS query.
On-line
Incremental
GIS Updates
ADMS_057
Offeror shall describe the tools and integrations in place to make
edits to the electric model in ADMS and push required changes back
to the GIS model.
NA
Philisophically ADMS does not push data to the GIS. The GIS network connectivity data is defined only in GIS as a as-constructed/as-built source for all
connectivity related users and applications. The PRISM realtime model is the operational source for all users of the as operated network.
On-line
Incremental
GIS Updates
ADMS_078
Offeror shall describe their solutions ability to provide a zero latency
update of the distribution system model from GIS without losing
switch position status
SF
The update happens without ever losing switch position. The update at present is manual since the GIS points that are remote must be linked to the RTU in
DASmap. Other changes may be to add analog values to the display, or poke points etc, all of which are not in the GIS. The changes should be made
(recommended) first to a qualty assurance system as per NERC CIP criteria:(CIP-003: Cyber Security Requirements governs security management. In part the
requirements state: “The Responsible Entity shall establish and document a process of change control and configuration management for adding, modifying,
replacing, or removing Critical Cyber Asset hardware or software, and implement supporting configuration management activities to identify, control and
document all entity or vendor related changes to hardware and software components of Critical Cyber Assets pursuant to the change control process.”
CIP-006: Cyber Security – Governs the Physical Security of Critical Cyber Assets and includes physical security protection
CIP-007 Systems Security Management: - governs security measures related to processes such as patch management and system access controls. It requires a
network administrator or a responsible entity to ensure that any changes which might occur during a software update or installation of a security patch doesn't
affect the overall operations and performance of the critical cyber assets.)
Then changes are applied to the product system. However many distribution utilites apply changes to the production but there should be some eyes validating the
checkout, since it is possible that automatin functions are operating. The concept for zero latency update was valid in OMS only system where not much can
impact operations. Functions such as IVVC and FIDR (FLISR) changes a lot of considerations.
On-line
Incremental
GIS Updates
ADMS_081
Offeror shall describe their solutions approach to synchronize
common GIS facility information including the following: Size, Make,
Kind, Construction Standard, Designed Operating Voltage, Circuit,
Line, Fuse Sizing
SF
Common GIS facility data is defined only once in the object model feature class and future instances of the object inherits all paramters associated with the
model. DASmap takes care of this behind the scenes.
Task Order 1 - 8790 Advanced Distribution Management System Page 34 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Online
PowerFlow
ADMS_007
Offeror shall describe solutions ability to provide Engineering
PowerFlow analysis/peak load analysis including the ability to handle
3-phase unbalanced, radial and weekly meshed distribution feeders,
closed loops
SF See ADMS_007 in Attachment: "ADMS I Responses"
Conduct
Online
PowerFlow
ADMS_009
Offeror shall describe solutions ability to provide indicators of where
no measurements exist and alert dispatchers to trouble spots based
on the absence of such measurements
SF See #2 of ADMS_069 in attachment: "ADMS Responses"
Conduct
Online
PowerFlow
ADMS_010
Offeror shall describe their solutions ability to support On-Line
PowerFlow study mode
SF
The On-line power flow described in response to ADMS_7 will run in any of the configured study modes as well as the realtime mode and the simultion mode
(DTS). Once in study mode, the operator is able to perform changes network and mode changes, save a case for simulation mode initialization and to perfom the
load flow analysis of the changes.
Conduct
Online
PowerFlow
ADMS_011
Offeror shall describe the data requirements and integrations
required to support ADMS On-Line PowerFlow in their solution
(systems to consider are the Esri GIS, SCADA, Elster EAMS Smart Grid
& Sys. Ops.., Maximo Asset Management and/or legacy Access
databases, CIS)
SF
Operator Power Flow parameters are built into the DASdb model created by PRISM DASmap. The connectivity model is imported from ESRI GIS (or many other
GIS's are supported). Some GIS implemntations use the GIS to store the powr flow parameters. If so they are also imported into DASmap with the connectivity
and exported to PRISM as DASdb. If the data is not saved n ESRI, the model can be imported from planning tools such as CYME SynerGEE, Siemens, etc. into
DASmap and merge into the PRISM has also integrated data from Elster and Maximo. and different CIS systems. ACS is now an INDRA company and the
INGRID product suite includes work force management, GIS and CIS along with analytics modules. The iSPeed DDS message bus will be the common
integrtaion bus for all moduels and layers between IT / OT.
Facility
Information
ADMS_053
Offeror shall describe their approach to rollout of ADMS solution
from a software and hardware (field devices) perspective (substation
by substation, etc.).
SF A layered approach is recommended where each layer is an available product. …..
Facility
Information
ADMS_055
Offeror shall describe the use of reporting and analytics in their
solution. Please also describe experience of publishing/using
centralized analytics outside of ADMS for presentation and reporting
on ADMS data/results.
SF See response to ADMS_055
ADMS I - Business Release II
Task Order 1 - 8790 Advanced Distribution Management System Page 33 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
SF
Perform
Switching
Out_150
Provide the ability to perform open/close switching activities in real-time and to send these switch orders to field
crews in real-time when connected
SF
Facility
Information
ADMS_082
Mobile map shall provide the ability for crews to easily turn on/off various layers of: secondary, primary, water,
wastewater, stormwater, fiber, street addressing, street names, lot lines, edge of street, all proposed electric
construction areas, surrounding Utility providers and various basemaps including aerial photos provided by ESRI and
City Of Fort Collins owned sets.
NA
? What is the "750"? Remove it?
Excergy - removed "750"
Task Order 1 - 8790 Advanced Distribution Management System Page 32 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Create Report Load_017 Ability to support report creation for Conductor Summary by Feeder with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Create Report Load_018 Ability to support report creation for Conductor Summary by Phase with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Create Report Load_019 Ability to support report creation for Current Feeder Loads with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Create Report Load_020 Ability to support report creation for Transformer Count by Phase with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Create Report Load_021 Ability to support report creation for Conductor graphs with contents similar to legacy report RQ
What is legacy reporting system? Will sample reports be supplied to
vendors?
Excergy: assumption is yes, we provide a sample EDAR report on the
share drive for reference.
Task Order 1 - 8790 Advanced Distribution Management System Page 31 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Outage
Analysis
Out_037
Support an outage prediction process that uses the current state of the distribution system model and trouble calls
and real- time system events. The outage prediction process will determine the most probable point of interruption
on a distribution circuit and create an outage record associated with the predicted device
SF
Predictive
Outage
Analysis
Out_127 Ability to predict all common protective devices upstream from reported service points up to the substation breaker. SF
Task Order 1 - 8790 Advanced Distribution Management System Page 30 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Out_135 Ability to "undo" executed switching steps, including outage statistics SF
Perform
Switching
Out_141
Ability for dispatchers to quickly change switch status at any point in the system (single and 3 phase) and provide
immediate feedback of load warnings, loop creation and feeder tie creation. Symbology shall indicate each of these
three conditions.
SF
Perform
Switching
Out_142
Ability to place and show lockout tags and ground placement locations and symbolize circuits with Hot Line Order
tags.
SF
Restore Outage
Restore
Outage
Out_045 Support the ability to calculate and store the Estimated Time of Restoration (ETOR) for Outages. SF
Restore
Outage
Out_073
Ability to collect damage information or other text/image assessments and assign to distribution system model
devices
SF
Restore
Outage
Out_086
Entry of partial and complete restoration details by specifying the points on the distribution system model that have
been energized. Restoration times and the customers restored by the restoration steps will be recorded. Generate
outage stats for each group of customers restored during a restoration process
SF
Restore
Outage
Out_087
Update outage related information including outage cause, restoration steps and restoration time and type of
equipment affected. Enforce the entry of certain fields such as restoration time, outage cause code prior to allowing
a user to close an outage
SF
Task Order 1 - 8790 Advanced Distribution Management System Page 29 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Out_068
Provide ability to switch with different optimizations - Hold for hours/days/weeks, Minimize number of device
operations, Weighting toward automated vs. manual devices
SF
Task Order 1 - 8790 Advanced Distribution Management System Page 28 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
Ability to determine if a single or multiple transformers are out below a switch/protective device as part of
identifying outage spread
SF
Trace Network Out_101
Ability to view and trace the connected model of the Distribution networks from the High side circuit switchers
and/or breakers at the Distribution Substation downstream including primary metered customers switchgear.
SF
Trace Network Out_102
Ability to trace the connected model through the Electric Distribution network from a selected point and highlight
and display (in tabular format) all connected downstream devices, segments, faults/potential faults, and available
fault currents.
RQ
Trace Network Out_103 Provide the ability to list and display facilities and devices in a Feeder trace. SF
Tracing is a visual function, highlighting the circuit and connected elements
on the operator map display. A list of facilities/devices is not generated.
Agreed with Fort Collins that current functionality is acceptable, and no
modifications are desired.
Trace Network Out_104 Provide the ability to list and display customers (including primary metered customers) connected in a Feeder trace. SF
Task Order 1 - 8790 Advanced Distribution Management System Page 27 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
The ADMS displays the temporary network mods as specified. However
the requirement is not clear: it does not send network changes back to the
GIS. ADMS obtains all network connectivity from GIS. Network topology is
received in ADMS / SCADA.
View Current
Electric
Configuration
Out_111
Ability to display and change Operational State information for devices in real time. The status change capability must
be phase specific with the ability, for example, to operate any combination of single or multiple phases on a three
phase device in a single step
SF
View Current
Electric
Configuration
Out_115
Provide a spatial display of current Protective Device states (i.e. Open and Close states, including where those states
are abnormal) - where those states are managed by the OMS/DMS and/or SCADA
SF
View Current
Electric
Configuration
Out_116
Provide a Schematic view of selected Electric Distribution network data (i.e. substation, feeder, protective device
levels).
SF
View Current
Electric
Configuration
Out_146 Ability to symbolize a switch by its ability to open one phase at a time or if it opens all three phases ganged together. SF
View Current
Electric
Configuration
Load_053 Provide the ability to identify normal operating state (GIS) while displaying currently switched state (OMS/DMS) SF
Access Meter Data
Task Order 1 - 8790 Advanced Distribution Management System Page 26 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
PRISM Software
PRISM Master Server-based License
DNPnet Network Communication Protocol
Distributed Database/OI Architecture – System License
Distributed Database/OI Architecture – Client License
Single Sign On Authentication
RTDB Tools/Java-based GUI
eAlarm Event Notification and Summary
Post Disturbance Analysis
PRISM Playback
PRISM SoftRTU
PRISM ICCP Non-Redundant License
PRISM ICCP Redundant License
PRISM Enterprise Historian
24
1
1
1
1
Visual Software
ReShape
Redline
Topology Processor
DASdb
25
1
1
1
1
1
OMS Software
PRISM OMS Electrical Base with Trouble Call Analysis
Base OMS Reports for 10 Users
PRISM OMS Work Order Management
PRISM OMS Enhanced IVR
PRIMS OMS AVL
Task Order 1 - 8790 Advanced Distribution Management System Page 8 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
1
1
1
1
1
1
1
1
1
1
1
1
PRISM Software
PRISM Master Server-based License
DNPnet Network Communication Protocol
Distributed Database/OI Architecture – System
License
Distributed Database/OI Architecture – Client
License
Single Sign On Authentication
RTDB Tools/Java-based GUI
eAlarm Event Notification and Summary
Post Disturbance Analysis
PRISM Playback
PRISM SoftRTU
PRISM ICCP Non-Redundant License
PRISM ICCP Redundant License
PRISM Enterprise Historian
Task Order 1 - 8790 Advanced Distribution Management System Page 7 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
eAlarm Event Notification and Summary
Post Disturbance Analysis
PRISM Playback
PRISM SoftRTU
PRISM ICCP Non-Redundant License
PRISM ICCP Redundant License
PRISM Enterprise Historian
PRISM Reporter – Special Link to OMS Schema
PRISM RT Dashboard 1-User
14
1
1
1
1
1
1
Visual Software
DASmap – Single User License
ReShape
Redline
Topology Processor
DASdb
GridVu Public – Server Base License
Task Order 1 - 8790 Advanced Distribution Management System Page 6 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49
OMS Interface
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
8
1
Fort Collins
Supplied
PRISM Portal Reporting Server
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
1.2 TB (2 x 600GB) 12G 15K SAS SFF SC DS HDD
9
1
GridVu Public Server
64 GB (4 x 16GB) RDIMM DDR4-2666 Memory
Task Order 1 - 8790 Advanced Distribution Management System Page 5 of 56
DocuSign Envelope ID: B0B8B257-A4F7-46DC-A8D9-C94CE5489A49