HomeMy WebLinkAboutStaff Report 14173
City of Palo Alto (ID # 14173)
City Council Staff Report
Meeting Date: 9/27/2022 Report Type: Consent Calendar
City of Palo Alto Page 1
Title: Approval of Outage Management System (OMS) Contract C23184285
With Milsoft Solutions Inc. in the Amount Not to Exceed $625,994 Over a 5-
Year Term
From: City Manager
Lead Department: Utilities
Recommendation
Staff recommends that Council approve and authorize the City Manager or their designee:
1. To execute the attached Contract C23184285 with Milsoft Solutions, Inc. (Milsoft) to
purchase an electric outage management system (OMS) with a standalone Interactive Voice
Response (IVR) capability and texting through TextPower. The purchase cost of the system
is a one-time $71,947 with an annual maintenance fee of $108,651 for 5 years.
2. To negotiate and execute one or more change orders to the contract with Milsoft for
related additional but unforeseen work, which may develop during the project, the total
value of which shall not exceed $10,792 or 15% of the implementation cost, for a total
contract amount not to exceed $625,994
Executive Summary
The City’s existing electric outage management system (OMS), iVue solution from National
Information Solutions Cooperative, Inc. (NISC), was purchased in 2011. The OMS has not been
upgraded due to system incompatibility and vendor constraints. As of 2021, the Electric
Operations Division has determined that, due to general enhancements and unification to the
City’s Geographic Information System strategy, as well as the upcoming deployment of a Sensus
FlexNet Advanced Metering Infrastructure, it is now preferable to upgrade or replace the
current OMS to better suit the utility’s current operational environment and growing needs in
better service to its community at-large.
Since the beginning of calendar year 2022, there have been 19 unplanned power outages in
Palo Alto, with eight considered major based on total customer impact (500 customers or
greater). The last several outages underscore the importance of communicating during an
outage and the Utilities Department is committing to increased community notifications.
Specifically, Utilities is increasing public communication at the beginning of a major power
City of Palo Alto Page 2
outage, providing updates during an outage as they become available, and alerting the
community when restoration of power has taken place, with cause of power outage when
known.
The new OMS is expected to substantially improve City of Palo Alto Utilities’ (CPAU) ability to
notify customers and mobilize resources in response to electric outages and emergencies. As
published in the recent blog “Recent Power Outage Details & Utilities Follow-Up Actions
Planned”, the OMS will allow customers to stay informed on outage and restoration
information to subscribed customers through email and text alerts. Confirmed outages will be
posted directly to the outage map and available to all customers. The new system includes an
internal distribution to key personnel via emails and text messages to keep staff informed of
outage details and receive information in a more timely and effective manner.
Background
In order to coordinate activities and disseminate information during a planned or unplanned
electric outage, the City purchased the NISC outage management system in 2011. The intent of
the NISC system was to provide staff with the capability to monitor the electric system on a
real-time basis from the Utility Control Center during an outage, and to improve the accuracy
and timeliness of information for reporting purposes. Originally, it was envisioned that the NISC
system would be able to provide information to customers about outages, both by making
direct phone calls to customers in the affected areas and by responding to incoming customer
inquiries. However, the NISC system did not integrate successfully with the Utilities billing
system (SAP) and as a result, it never functioned as expected. The new OMS will be able to
integrate information in the SAP Customer Information System, meter statuses in the Meter
Data Management System, and circuitry from the GIS, which will aid in identifying the location
and extent of an outage.
Discussion
When a planned or unplanned electric outage occurs, CPAU needs a system that will provide
information for staff to identify the root cause and location of the problem, perform repairs
quickly, as well as provide customers and management with up-to-date information on the
outage and its repair status. An effective OMS system also improves reliability in the
distribution system by providing historical data that can be mined to find common causes for
failures and damages. By identifying common factors in electrical system failures, improvement
programs can be prioritized to provide the greatest increases in reliability at the lowest cost.
On March 2, 2022, a Request for Proposal (RFP) Number 184285 for “Outage Management
System and Interactive Voice Response” was issued. Staff received only two proposals. Below
is a table with proposed upfront and annual operating costs, excluding texting charges. Since
both proposals met the comprehensive technical (i.e. architecture, security, performance) and
functional (i.e. usability, integration, reporting, notification, dispatching, external map, IVR)
requirements as described in the RFP to provide a complete outage management system with a
City of Palo Alto Page 3
standalone IVR Unit, staff decided to evaluate the two proposals instead of canceling and
reissuing the RFP.
Summary of Solicitation Process
Proposal Title RFP 184285
Proposed Length of project 12 months
Number of Proposal packages downloaded 16
Total days to Respond 25 days
Number of Proposal Received 2
Bid Range $527,452 to $887,569
Company Name Amount
Milsoft Solutions, Inc. $527,452
The proposals were evaluated based on the following criteria. It was also specified that the
weights associated with the criteria would be different for the five components of the RFP.
1. Quality and completeness of Proposal
2. Quality, performance, and effectiveness of the solution
3. Proposer’s experience
4. Cost to the City
5. Proposer’s financial condition and stability
6. Proposer’s ability to perform the requirements within the time specified
7. Proposer’s prior record of performance with City or other agencies
8. Proposer’s ability to provide future maintenance, repairs, parts and/or services
9. Proposer’s compliance with applicable laws, regulations, policies
10. Proposer’s integration experience
Milsoft scored the highest overall points for the OMS evaluation including lowest
implementation and total cost. Milsoft is a proven utility solution provider of over 30 years of
experience, with more than 900 software systems across the United States. Milsoft also has a
long and established successful deployment and integration track record with their business
partners and customers while exceling in customer service and support.
Electric outage information in the Milsoft Solutions, Inc. will be integrated with both the GIS
database and the SAP Customer Information System and will enable the identification of outage
location and extent, will aid in situation analysis of crew requirements at the outage location,
and can be used to set parameters for customer notifications of outages and repair schedules
by phone, email, and text. Information on the outage will also be published to the Utilities web
page automatically once it is accepted as an outage by the System Operator. After the
completion of repairs, information saved in the system will assist in analyzing the cause of an
outage.
The OMS is designed to:
City of Palo Alto Page 4
• Coordinate the dispatch of crews;
• Generate management and reporting tools that can be used internally to share
dashboard views of various key performance indicators;
• Verify restoration efforts by re-checking Advanced Metering Infrastructure information
to confirm the power has been restored to all customers; and
• Record and review outage events to determine ‘weak spots’ in the system and plan for
remediation.
• Power Outage Communication
One of the key features of an OMS is its ability to communicate power outage information for
use by both customers and internal staff. The system will also have a variety of other
communication options that can be enabled as desired, including the ability to send updates by
email and text. This will allow CPAU to communicate outages to customers based on their
communication preferences. Internal staff will also benefit from the OMS by having a shared
interface and dashboard to input trouble calls and track progress. CPAU staff can see new
trouble calls as they come in and receive outage status updates in real-time.
Timeline
It will take between six to nine months to implement the new Milsoft OMS and IVR systems
depending on availability of staff and third parties for data conversion, interface development,
system integration, and testing.
Resource Impact
The Milsoft Solutions, Inc. contract will cost $71,974 for the purchase of the OMS, Call Capture
(IVR), and texting through TextPower, an annual maintenance cost of $108,651 for five years.
The City opted in for the texting features with an annual cost of $10,308 which includes a
maximum of 15,000 texts per month. A contingency amount of $10,792 is also requested for
additional unforeseen work that may develop during the first year of the project. The total
contract amount is not to exceed $625,994 at the end of the five-year term. Funding for the
implementation and first year subscription of this contract is available in the FY 2023 Adopted
Operating Budget of the Electric Fund. Funding in future years is subject to City Council
approval through the annual budget process.
Policy Implications
The approval of the contract is consistent with the Council priority to improve emergency
responsiveness and with the Council-approved Utilities Strategic Plan Item Numbers C1,
“Receive Safe and Reliable Service,” and BP4, “Serve Customers Promptly and Completely.”
Environmental Review
Council action on this item is not a project as defined by CEQA because the purchase of OMS
software is an organizational or administrative activity that will not result in direct or indirect
physical changes in the environment. CEQA Guidelines section 15378(b)(5).
Attachments:
City of Palo Alto Page 5
• Attachment A: Milsoft Contract, C23184285
1
C23184285 - Milsoft Contract for Software License and Support, with OMS, IVR & TextPower® Subscriptions
This Contract for Software License, Support, and Subscription (hereinafter referred to as “Contract”) is by and between CITY OF PALO ALTO UTILITIES, Palo Alto, CA (hereinafter referred to as “Customer”) and Milsoft Utility Solutions, Inc., a Texas corporation (hereinafter referred to as “Milsoft”), and is effective on the date signed by the latter of Customer and Milsoft (“Effective Date”). Whereas, Customer has the desire and capacity to procure from Milsoft the authorized use of its proprietary software known as OMS Subscription: DisSPatch® and Tester, FieldSyte™ powered by RC Engine, Milsoft Analytics™, Milsoft Customer Outage Alerts™, and Milsoft Personnel Notification™; Communications Subscription: Milsoft Hosted IVR™ as quoted, with Texting powered by TextPower®; also Texting & Integration Configurations and Database Conversion w/migration, supportable (altogether, the “System”), more particularly identified in Section 1 below; and Whereas, Milsoft has the desire and capability to furnish and support the System for Customer as quoted and in accordance with the terms and conditions of this Contract; Now, therefore, in consideration of the premises, the Contract Price and the respective covenants contained herein, the Customer and Milsoft (the “parties”) hereby agree as follows: 1. SYSTEM. The System (or “System Components”) shall consist of the licensed System software (the “Software”) and subscription services described in Milsoft Quote # 51199, constituting “Schedule A” for purposes of this Contract and incorporated herein by reference as if fully set forth, as well as any other software and/or services that may be added by future
quote and acceptance as addenda hereto. 2. CONTRACT PRICE; TERMS OF PAYMENT. The itemized and/or aggregate pricing for the System Components, basic installation, training if included, and software license (collectively the base “Contract Price”) is set forth in Schedule A, together with the terms of payment. 3. STATEMENT OF WORK. If and to the extent deemed necessary by Milsoft, the Parties shall in good faith mutually develop and agree upon a Statement of Work (“SOW”) to describe and set forth with particularity the essential scope of work, technical specifics, period of performance, schedules/milestones, acceptance criteria, change orders and other requirements unique to the project. Should the Parties be unable to agree upon the SOW within [ 30 ] calendar days after entering into this Contract, either Party may elect to terminate this Contract by giving written notice to the other, without necessity of default, whereupon the termination shall be effective in one week (7 calendar days after notice) if no agreement as to the SOW be reached. 4. DELIVERY, INSTALLATION AND TURNOVER. For the Contract Price and in accordance with the SOW (if applicable), Milsoft shall deliver the System Components to the Customer’s location identified in Schedule A and, subject to
Customer’s preparatory compliance as described in Section 7, shall install the System on site, or by remote electronic delivery, or combination thereof as appropriate. The Turnover Date shall be the date, after completion of installation and testing, upon which Milsoft turns over the System to Customer for fully operational use. 5. TRAINING. Milsoft shall provide basic System administration and user training to Customer’s designated employees, if and as may be described in more detail in the Statement of Work or Schedule A. 6. SUPPORT SERVICES. Support is included at no additional cost for the products and services provided hereunder by Subscription. For the components of Software not covered by subscription hereunder, Customer will be eligible to participate in Milsoft’s annually renewable support program (the “Support Program”) for technical and user support, Software fixes/patches, and upgrades to future Software editions. The Support Program is offered at an initial annual rate of 20% of the Retail Price of the Software, excluding any discounts, plus any applicable sales taxes. Renewal pricing is subject to change in view of software complexity and market conditions, not to exceed 20% variance from one year to the next. If payment is not received when due,
Milsoft may withhold services until paid. In the event Customer declines or discontinues its participation in the Support Program, in order to again be eligible to receive support Customer may be required to upgrade and/or agree to pay an increased rate based upon the extent of maintenance missed and appropriate to the circumstances.
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
2
For purposes of this Contract, support of the Software means:
• support related to System applications;
• delivery of Software fixes/patches;
• delivery of upgrades to the latest Software versions made available by Milsoft. Hours of support availability will be 24 hours/day, 7 days/week, year-round for outage management and Milsoft communications systems; and no less than 7:00 a.m. to 7:00 p.m. Central Time, Monday through Friday, excepting normal business holidays observed by Milsoft, for all other support issues. With prior notice and as reasonably requested, Customer shall allow online access to the System and sufficient access to Customer’s premises as needed for Milsoft to provide its support services.
The services to be provided under the Support Program do not cover damages or claims due to misuse, negligence, accidents, thefts, unexplained data loss, loss of data due to Hardware failure, lack of daily backups, abuse, electrical outages, fire, flood, wind, acts of God or public enemy, or improper wiring, installation, repair or alteration by anyone other than Milsoft approved technicians. Repairs necessitated by any one or more of the above-excepted causes may be performed by Milsoft upon request, provided the Customer agrees to pay for such extra work at Milsoft’s current hourly rates. Such work would not represent or imply any additional warranty or representation regarding the System, the System Components or the functionality of the System. 7. CUSTOMER’S OBLIGATIONS, PREP AND SPECS; INTEGRATION WITH 3rd-PARTY SOFTWARE. 7.1 Customer assumes responsibility for care and risk of loss of the System Components upon delivery to its location. Customer is responsible for meeting the data requirements, purchasing and providing any other hardware and/or third party software, and preparing its location for installation consistent with the specifications, requirements and recommendations per
SOW, Schedule A, RFP/Response or applicable terms and conditions, at its expense. Any Customer data required for installation shall be timely delivered to Milsoft pursuant to its instructions. Customer shall also secure any permits, licenses or other governmental approvals for its installation site as may be required by applicable law or regulation, at its expense. Once a Milsoft technician is on-site as reasonably scheduled, if the installation is delayed due to failure of the Customer to have met the preparatory requirements, there may be a charge of $1,000 per day assessed until ready to proceed. 7.2 Milsoft products are generally amenable to integration with a variety of products from third-party vendors known by Milsoft to be certifiably interoperable (including but not limited to many MultiSpeak® integrations, when applicable), subject to verification, and with a range of other third-party products that may require more extensive customization. The development or provision by Milsoft of any and all interface between its products and third-party software (whether deemed necessary at the time of Milsoft product installation or as needed in the future due to change of circumstances) can only be undertaken pursuant to specific evaluation and may, at the discretion of Milsoft, require reasonable adjustment of time and/or cost. Every interface to be developed and provided for integration with third-party products must be testable by Milsoft with consent
and cooperation of the third-party vendor (whose consent and cooperation shall be provided by Customer, as Customer’s responsibility) and will be specific only to the version or iteration of the third-party product in use at the time of the interface development. Customer shall be responsible for alerting Milsoft to future additions, updates or new versions of all third-party product and for providing renewed consent and cooperation of each third-party for testing, as any such changes could render the Milsoft interface less functional unless addressed. In such event, Milsoft offers no warranty for the previously provided interface, and assumes no responsibility to develop or provide additional interface without further agreement and compensation, if at all. No other representation, warranty or promise regarding interfaces or integration between Milsoft products and third-party software is expressed or implied. 8. SOFTWARE LICENSE. 8.1 Upon successful installation and as of the Turnover Date, Milsoft grants to Customer, and Customer accepts, a non-exclusive and non-transferable license to use the Software furnished hereunder (including modifications and enhancements furnished under the terms of this Contract, and modifications and enhancements furnished under the terms of the Support Program described in Section 6) strictly upon the terms and conditions contained herein. Title to and ownership of all Software shall remain with Milsoft or its licensors. Customer shall have no right to sell, sublicense, publish, disclose, display, assign, duplicate, alter, lease, or otherwise make available the Software to any third party. Customer shall take appropriate action with its employees, agents, contractors, consultants and other representatives or end users to ensure compliance with these terms and conditions. Customer may make copies of the Software only for backup purposes and/or archival purposes, and any such copy must contain the same copyright notice and proprietary markings that the original Software contains. Customer acknowledges the Software represent a very large-scale investment in the development of an intangible asset by Milsoft and must be strictly protected hereunder. In the event of a breach under the provisions of this Software license by Customer, upon written notice which may be given at the election of Milsoft, Customer shall forfeit all rights as licensee
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
3
under this Contract and shall immediately return the Software to Milsoft along with all documentation and source media associated therewith. Customer assumes full liability to Milsoft for any damages (including consequential damages), whether or not foreseen by the parties hereto, resulting directly or indirectly from any compromise of any rights owned by Milsoft and not expressly conferred under this Contract, if such damages are the result of the willful act or omission of Customer (including any employee, agent, contractor, consultant or other representative of Customer). CUSTOMER ACKNOWLEDGES THAT THE SOFTWARE IN EXECUTABLE LINE CODE FORM REMAINS A CONFIDENTIAL TRADE SECRET AND CUSTOMER AGREES NOT TO ATTEMPT TO REVERSE-ENGINEER, TRANSLATE, DECIPHER, DECOMPILE, MODIFY OR DISASSEMBLE THE SOFTWARE, NOR INCORPORATE THE SOFTWARE IN WHOLE OR IN PART INTO ANY OTHER SOFTWARE OR PRODUCT OR DEVELOP DERIVATIVE WORKS THEREFROM OR ALLOW ANY OTHER THIRD PARTY TO DO SO, WITHOUT THE EXPRESS WRITTEN CONSENT OF MILSOFT. 8.2 Unless otherwise agreed on a case-by-case basis, any other work resulting from the joint effort or collaboration of the Parties shall be jointly owned, free of restriction, and without any right or obligation of either Party to consent to or share profits or proceeds from the use or exploitation thereof. Customer agrees to take such further action, and to obtain or sign such further agreements or acknowledgments, as Milsoft may reasonably request to give effect to this paragraph. Notwithstanding the foregoing, Milsoft shall not have ownership of, and may not license or otherwise provide to others, elements or portions of its work product that represent descriptions of, or means for executing, business functions or processes of Customer that are particular to Customer or its individual business and that are provided to Milsoft by Customer to enable Milsoft to support Customer’s business environment. Before filing patent applications for any inventions that disclose any such functions or processes, Milsoft agrees to obtain Customer’s consent for such disclosure. This exclusion is not intended to apply to generic programming and technology per se, but instead to business applications that can be readily recognized as unique, proprietary, or competitively sensitive in Customer’s business. 9. CONFIDENTIALITY. 9.1 During performance of this Contract or in the contemplation thereof, and subject to and in conformity with Section 8, employees, agents and authorized contractors or consultants of each party to this Contract may have access to private or confidential information owned by the other party, including, but not limited to, the Software, and information concerning costs, charges, operating procedures and methods of doing business, which may be owned or controlled by the other party. With respect to any such information so accessed or acquired, each party agrees as follows: (a) all such information shall be and shall remain the exclusive property of the party which owns the information; (b) each party shall limit access to such information of the other party to their respective employees, agents and authorized contractors or consultants who have a need to know consistent with the receiving party’s authorized use of such information; (c) the receiving party shall keep, and have its employees, agents and authorized contractors or consultants having access keep, all such information confidential; (d) the receiving party shall not copy, publish or disclose to others, or permit its employees, agents and authorized contractors, consultants or anyone else to copy, publish or disclose to others, any such information without the owning party’s prior written consent; (e) the receiving party shall return such information to the owning party at its request; and (f) the receiving party shall use such information only for the purpose of performing its obligations hereunder. 9.2 Each party shall secure and protect the other party’s confidential information in a manner consistent with the protection it provides to its own confidential information, but in any case using no less than reasonable degree of care. Each party’s duties of confidentiality as regards the confidential information shall survive any cancellation, expiration or termination of this Contract. Notwithstanding the foregoing, receiving party may disclose Confidential Information as required by applicable law or by proper legal or governmental authority; in such event, receiving party shall give the owning party prompt notice of any such legal or governmental demand and reasonably cooperate with such owner in any effort to seek a protective order or otherwise to contest such required disclosure, at owner’s expense. The Parties acknowledge that Customer is a local agency subject to the requirements of the California Public Records Act. 9.3 Each party at all times shall maintain appropriate internal policies and procedures reasonably sufficient to satisfy its obligations under this Section 9. Should either party or its employees, agents and authorized contractors or consultants use, disclose or attempt to use or disclose any such information in a manner contrary to this Contract, the owning party shall have the right to seek injunctive relief against such breach or threatened breach (without posting a bond or other security), in addition to any other remedies that may be available at law or in equity. 10. PRODUCT CHANGES. Milsoft reserves the right to make modifications and distribute enhancements to existing Software. In addition, upon notice to Customer of no less than one hundred eighty (180) days, Milsoft reserves the right to discontinue offering the Support Program associated with the System in place, and may require that specified upgrades to the System Components be made as a condition for continued Customer participation in the Support Program.
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
4
11. LIMITED WARRANTIES. 11.1 Software. Upon delivery and continuing through the first thirty (30) calendar days following the Turnover Date, Milsoft warrants exclusively that the Software shall substantially conform to, and perform in substantial accordance with, all applicable Software specifications. Milsoft represents and warrants generally that it owns the Software or that it has the right to license Customer’s use of the Software in accordance with the provisions of this Contract. In event of breach or failure, Customer’s exclusive remedies shall be, at the option and expense of Milsoft, either (i) to have Milsoft promptly correct any discrepancy in performance that materially impairs the appropriate functionality of the Software; or (ii) to have Milsoft refund the price paid for the licensed use of the Software, provided that Customer must allow Milsoft to de-install the Software within 30 days of Customer’s timely notification to Milsoft of the discrepancy. ALL CLAIMS AND REMEDIES ARE LIMITED TO THOSE EXPRESSLY PROVIDED IN THIS CONTRACT. 11.2 Support Services. With respect to services provided under the Support Program or other work, Milsoft warrants exclusively that such services shall be performed in a good and workmanlike fashion. In event of breach or failure, Customer’s exclusive remedies shall be, at the option and expense of Milsoft, either (i) to have Milsoft promptly correct such services, or (ii) to have Milsoft refund the price paid for the applicable portion of the services. 12. DISCLAIMER OF OTHER WARRANTIES. THERE ARE NO OTHER WARRANTIES EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 13. GENERAL LIMITATION OF LIABILITY. THE LIABILITY OF MILSOFT, ITS LICENSORS AND ITS AFFILIATES, IF ANY, AND CUSTOMER’S SOLE AND EXCLUSIVE REMEDY FOR DAMAGES FOR ANY CLAIM OF ANY KIND WHATSOEVER WITH RESPECT TO THE PRODUCTS AND SERVICES PROVIDED BY MILSOFT, REGARDLESS OF THE LEGAL THEORY OR THE DELIVERY OR NON-DELIVERY OR ALLEGED FAILURE OF ANY PRODUCTS OR SERVICES, SHALL NOT BE GREATER THAN THE FEES ACTUALLY PAID BY CUSTOMER TO MILSOFT HEREUNDER IN CONNECTION WITH THE PRODUCTS OR SERVICES AT ISSUE DURING THE TWENTY-FOUR (24) MONTH PERIOD IMMEDIATELY PRECEDING THE DATE UPON WHICH SUCH CLAIM ACCRUED, OR, IF THERE ARE MULTIPLE CLAIMS GIVING RISE TO SUCH LIABILITY, THE MAXIMUM CUMULATIVE AMOUNT PAID BY CUSTOMER TO MILSOFT UNDER THIS AGREEMENT IN ANY CONSECUTIVE PERIOD OF THREE (3) YEARS, EXCLUDING ONLY (A) CLAIMS FOR MISAPPROPRIATION OF EITHER PARTY’S INTELLECTUAL PROPERTY RIGHTS OR NON-COMPLIANCE WITH CONFIDENTIALITY AND PRIVACY-RELATED OBLIGATIONS, (B) ENFORCEMENT OF INDEMNIFICATION OBLIGATIONS, OR (C) WILLFUL MISCONDUCT. UNDER NO CIRCUMSTANCES WILL MILSOFT, ITS LICENSORS OR ANY AFFILIATE BE LIABLE TO CUSTOMER FOR ANY SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, COMPENSATION, REIMBURSEMENT OR DAMAGES ON ACCOUNT OF THE LOSS OF PRESENT OR PROSPECTIVE PROFITS, EXPENDITURES, INVESTMENTS, COMMITMENTS, BUSINESS REPUTATION OR GOODWILL, FOR LOSS OF DATA, COST OF SUBSTITUTE SOFTWARE, COST OF CAPITAL, AND THE CLAIMS OF ANY THIRD PARTY, OR FOR ANY OTHER REASON WHATSOEVER, REGARDLESS OF WHETHER SUCH CLAIM HAS ITS BASIS IN ANY THEORY OF CONTRACT, EQUITY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHER LEGAL THEORY, EVEN IF EITHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF ANY SUCH DAMAGES. 14. PAYMENT. Timely payment by Customer to Milsoft at its principal place of business of all sums due hereunder is a material element of this Contract. Unless otherwise specified in Schedule A or by a subsequent agreement of the parties in writing, payment shall be due upon billing and paid within thirty (30) days of invoice. Without limiting Milsoft’s other rights and remedies for any failure of Customer to make payment, Milsoft may charge interest on all unpaid sums at the lesser of the rate of 1.5% per month or the maximum contract rate allowed by law. Milsoft has no desire to exceed the maximum amount of interest that may be contracted for, charged or received under applicable law, and any interest paid in excess of said maximum amount shall be credited toward any past due payment or refunded to Customer. Milsoft shall handle all invoicing and collections for TextPower services as well, as provided in Schedule B. 15. TAXES. Unless specified as such, the prices set forth herein do not include any sales, use, excise, ad valorem, property or other taxes applicable to the sale, use, license or delivery of the System Components and any related services supplied hereunder. It is understood that as a governmental entity, Customer is not subject to or liable for taxation. 16. FORCE MAJEURE. Neither party shall be deemed in default of any provision of this Contract, or responsible for failures in performance, resulting from any cause beyond its reasonable control, which include, without limitation, acts of God, civil or military authority, civil disturbances, war, fires, or other catastrophes. In the event of any failure or delay resulting from such causes, an equitable adjustment of schedule and any other appropriate terms and conditions shall be agreed upon by the parties.
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
5
17. NON-WAIVER. No waiver of any breach or default shall constitute waiver of subsequent breach or default. No failure or delay to exercise any right, power, or privilege under this Contract shall operate as a waiver of such right, power, or privilege; nor shall any single or partial exercise of any right, power, or privilege preclude further exercise of such right, power, or privilege. 18. TERM and TERMINATION. The initial term of Subscription(s) hereunder shall be five (5) years unless otherwise stated in Schedule A and may continue in renewal or extension thereof in the time and manner stated therein; in the absence of further written agreement or notice of cancellation or termination, agreement to extend on a month-to-month basis may be inferred so long as Customer continues to pay and Milsoft continues to accept monthly subscription payments. If at any time either party fails to perform a material obligation and does not remedy such failure within thirty (30) days following notice from the non-defaulting party, the non-defaulting party may elect to terminate this Contract by giving notice of termination to the party in default. Termination for default shall in no way prejudice the rights or remedies available to the non-defaulting party as a result of the default nor relieve Customer of its obligation to pay Milsoft for all compliant product provided and services actually rendered up to the date of termination. In the event either party breaches or defaults hereunder to the detriment of the other, in addition to other rights and remedies the party wronged shall be entitled to recover its reasonable attorney’s fees and related expenses incurred, including but not limited to court costs incurred at both trial and appellate levels, in the enforcement of this Contract. 19. DISPUTE RESOLUTION. The parties will attempt in good faith to promptly resolve any dispute arising out of this Contract without resorting to litigation. Before any suit for damages may proceed, the parties shall submit to non-binding mediation by an impartial mediator, at a mutually convenient location, with each party bearing its own attorney’s fees and expenses. Any dispute not so resolved by negotiation or mediation may then be submitted to a court of competent jurisdiction. Nothing contained herein, however, shall preclude the parties from first seeking temporary injunctive or other equitable relief in preservation of its rights. 20. GOVERNING LAW; CHOICE OF FORUM. The validity, performance and construction of this Contract shall be governed by the laws of the State of California (without giving effect to principles of conflicts of law). The parties agree that the Uniform Computer Information Transaction Act and the UN Convention on International Sale of Goods do not apply. Any legal claim or action shall be filed in the state or federal venue in which Customer maintains its principal municipal offices, e.g. Superior Court of California, County of Santa Clara or U.S. District Court, Northern District of California, unless otherwise agreed. 21. SUCCESSORS AND ASSIGNS. This Contract shall inure to the benefit of and be binding upon successors and assigns of the parties; however, Customer may not assign without the consent of Milsoft, which shall not be unreasonably withheld.
22. CONSTRUCTION AND CAPTIONS; PARTIAL INVALIDITY. Captions are for convenience only and shall not be
construed to expand or limit any provision hereunder. Should any provision of this Contract be held invalid, illegal, or unenforceable in any respect, such invalidity, illegality or unenforceability shall not affect any other provision of this Contract.
23. CONTROLLING TERMS, ORDER OF PRECEDENCE. Any terms or conditions appearing on the face or reverse side of any purchase order, preliminary quote, acknowledgment or confirmation that are different from or in addition to those required hereunder shall not be binding upon the parties, even if signed and returned, unless both parties expressly agree in writing to be bound by such. In event of any conflict or inconsistency between the main body of this Contract and the provisions of any schedule or other attachment, the provisions of this Contract shall prevail, except as to the job-specific details of Schedule A, Schedule B or applicable SOW. 24. NOTICE. All notices given under this Contract must be in writing and shall be deemed duly given only upon (a) personal hand delivery; (b) the fourth day following deposit in the United States Mail, postage paid, certified/return receipt requested; (c) delivery by a nationally recognized overnight courier service that obtains signed acknowledgment of receipt; or (d) confirmation of electronic transmission via facsimile or email; using the addresses or numbers shown below or any other address or numbers as either party may designate by ten days prior written notice given in accordance with this provision. If to Customer: If to Milsoft:
(City of) Palo Alto Utilities Milsoft Utility Solutions, Inc.
Attention: Anna Vuong Attn: Adam Turner, CEO of Business Operations
250 Hamilton Ave P.O. Box 5726
Palo Alto, CA 94301 Abilene, Texas 79608
Telephone: (650)329-2528 Facsimile: (325) 690-0338
Email: anna.vuong@cityofpaloalto.org Email: adam.turner@milsoft.com
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
6
25. ENTIRE AGREEMENT; AMENDMENTS; SIGNATURES. The SOW (if any) and all referenced schedules and addenda are integral parts of this Contract as if written verbatim herein. Collectively, this Contract sets forth all authorized and material representations, constitutes the parties’ entire agreement and understandings with respect to the subject matter, and supersedes any and all other agreements, proposals and/or representations, subject to Milsoft’s Response to Request for Proposal as Accepted (if applicable) which is incorporated herein by reference. No addendum, amendment or modification shall be effective unless in writing and duly executed by authorized representatives of both parties. Signatures may be made and/or delivered by electronic means, and any true, correct and complete copy of this fully signed instrument shall be as enforceable as the original. IN WITNESS WHEREOF, the parties have signed by their duly authorized representatives as of the dates entered below. CITY OF PALO ALTO UTILITIES, MILSOFT UTILITY SOLUTIONS, INC. City of Palo Alto, California
By: By:
(Signature) Adam Turner, CEO of Business Operations
______________________________________
(Name & Title, typed or printed)
Date: Date:
APPROVED AS TO FORM: __________________________
City Attorney or designee
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
8/25/2022
Schedule A
Quote Number: 51199
Date Created: 03-25-2022
Account Manager: Josh Wolf
E-mail:josh.wolf@milsoft.com
Phone:(800)344-5647
Valid Until:06-25-2022
Bill To
Anna Vuong
Palo Alto Utilities
10250, MS3C
Palo Alto, CA, 94303
USA
Milsoft Communications
Quantity Quoted Line Item Retail Price Ext. Price
1.00 $15,000.00 $0.00
1.00
IVR Hosted System
A dedicated hosted IVR system to include Caller ID, Second Language, Text-to-Speech, Voice
Recognition, Milsoft Outage Call Handling and Milsoft TeleLink Suite.
Training included.
Hosted IVR Monthly Subscription
Monthly supported Subscription for dedicated IVR system. Contract term is five (5) years. Call charges
billed at $0.05 per minute.
$2,800.00 $2,800.00
Subtotal:$2,800.00
Total:$2,800.00
Outage Management
Quantity Quoted Line Item Retail Price Ext. Price
1.00 $2,750.00 $2,750.00
1.00 $1,250.00
1.00 $834.00 $834.00
1.00 $325.00 $325.00
1.00
OMS Subscription w/ OMS Test System
Monthly subscription of Milsoft DisSPatch® OMS & Test System. 5-year contract Milsoft Support
included.
FieldSyte Monthly
Milsoft Analytics
Five (5) seat addition to Milsoft Analytics (only sold in bundles of 5).
Milsoft Customer Outage Alerts Subscription
Milsoft's Customer Outage Alerts Subscription provides email, text* and voice** notifications to external
customers based on parameters set by the Milsoft customer. Notifications can be configured to send
automatically or manually, based on outage criteria from Milsoft DisSPatch®. Two (2) hours Web
training included, with add'l training available for $250/hour. Requires Milsoft Texting integration. The
monthly price of $225 includes Milsoft Support - see Terms and Conditions.
*Texting requires a 3rd party gateway (i.e., TextPower) provider to ensure compliance with all FCC,
FTC, CTIA, and MMA regulations (sold separately)**Voice notifications require Milsoft IVR (hosted or
on-site).
Milsoft Personnel Notification Subscription $236.25 $236.25
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 1 / 6
$1,250.00
A monthly subscription of Milsoft Personnel Notification. Milsoft Support included.
Subtotal:$5,395.25
Total:$5,395.25
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
Services - One time cost
Quantity Quoted Line Item Retail Price Ext. Price
1.00 Integration Configuration
A Milsoft integration configured for MultiSpeak compatible products. Milsoft Support applicable.
$12,000.00 $12,000.00
1.00 Database Conversion
A database conversion process. Includes a customer migration application. Milsoft Support applicable.
$27,500.00 $27,500.00
Subtotal:$39,500.00
Total:$39,500.00
Training - One time cost
Quantity Quoted Line Item Retail Price Ext. Price
1.00 Initial OMS Setup / Training
Includes: three (3) days of initial on-site OMS training, software installation and configuration, and all
travel-related expenses.
Recommended, but not included: two (2) days of follow-up training, 90-180 days after implementation.
Milsoft Support not applicable.
$15,000.00 $15,000.00
1.00 Training OMS w/System 2 Day On-site: Follow Up
Two (2) days of onsite OMS training and all related travel expenses. Curriculum chosen by Customer.
Milsoft Support not applicable.
A DisSPatch Test System will be included for six months at no charge. The Test system includes: A
single, stand-alone license of DisSPatch® for Training, Modeling, and Simulation of the outage system.
$8,000.00 $8,000.00
Subtotal:$23,000.00
Total:$23,000.00
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 2 / 6
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
Additional setup charges may apply as services are selected, e.g.:
-- One-time registration and verification- $399
-- Interface with Client’s email server - $499
-- AlertDispatcher ProTM for 2-way field crew Communication (5 group threads incl. with 10k text mthly
bundle) - $750
-- Additional 5-group thread bundles - $59/mo
-- Automated List Processing (ALP) allows daily FTP upload from raw CIS file setup/mapping - $799
Subtotal:$10,306.00
Total:$10,306.00
Grand Total
Subtotal:$81,001.25
Total:$81,001.25
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 3 / 6
Milsoft Communications - Texting
Quantity Quoted Line Item Retail Price Ext. Price
1.00 $7,000.00 $7,000.00
1.00 $859.00 $859.00
1.00
Texting Configuration
The configuration of two-way texting functionality for Milsoft IVR and/or DisSPatch OMS provided
through TextPower. Price includes (2) hours phone or web training. Additional telephone or web
training is available for $250 per hour. Milsoft Support applicable - see Terms and Conditions.
Texting Subscription
Monthly Texting Subscription that includes up to 15,000 texts, billed monthly. Additional texts billed
separately at $0.05 per text.
Communications Assurance Program (lookup of all phone numbers and loading mobiles into your
"opt-in" database) billed at $0.025 per number
Opt-In Processing subsequent to initial upload is billed at $0.045 per opt-in number
Contract term of five (5) years.
TextPower Set-up Charges
TextPower Set-up Charges: Local Number text-enablement (10DLC)
$2,447.00 $2,447.00
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
Terms and Conditions - Interactive Voice Response - Hosted System
Payment Terms
•Payment due upon receipt of invoice
•100% of Hosted System Setup invoiced upon quote acceptancePrice Inclusion
•Support ProgramPrice Exclusion
•Fee ($10,000) to audit and gain compliance for a non-approved payment gatewaySubscription Terms
•Five (5) year initial term, invoiced monthly
•Automatic (1) year renewals after initial term, unless/until canceled in writing by notice given before the nextcontract year, renewal pricing may be subject to change
•Call Charges billed monthly at $0.05 per minute
Quote Acceptance:
This Quote comprises all material representations and constitutes the entire understanding between the parties to date with respect to the subject matter hereof and supersedes any and all prior representations, offers or agreements either oral or written between the parties with respect to such subject matter. This Quote shall serve
as Schedule A to the Customer’s contract for procurement of the Product, Training, Service and Support Program as described when applicable, or as an Addendum to Customer/Client’s current contract(s) with Milsoft..
•Payment due upon receipt of invoice
•Subscription invoiced monthly•Payment must be in USDSubscription Term
•Subscription invoiced upon installation
•Five (5) year initial term
•Automatic (5) year renewals after initial term, unless/until canceled in writing by notice given before the nextcontract year; renewal pricing may be subject to change
Terms & Conditions – DisSPatch OMS Subscription with Test System
Payment Terms
•Payment due upon receipt of invoice
•100% invoiced upon quote acceptance
•Payment must be in USD
Price Exclusion
•Gateway Provider sold separately (by 3rd Party)
•Milsoft IVR and/or DisSPatch sold separately (by Milsoft)
•Support ProgramoAnnual support at the rate of 20% of the retail priceoAnnual support invoiced separately upon install
Terms & Conditions –Milsoft Customer Outage Alerts™, Personnel Notifications
Payment Terms
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 4 / 6
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
•Payment due upon receipt of invoice
•Subscription invoiced monthly•Payment must be made in USD
Subscription Terms
•Five (5) licenses of Milsoft Analytics Dashboards powered by Tableau
•Includes all Milsoft system-created dashboards available for the Customers existing Milsoft application(s)
now in use. Additional dashboards development will be available under separate quotation, SOW required.
•Subscription begins upon installation
•Five (5) year initial term
•Automatic (1) year renewals after initial term, unless/until canceled in writing by notice given 60 days prior tolicense expiration
•Support included.
Terms & Conditions - Milsoft Analytics – Subscription
Payment Terms
•Payment due upon receipt of invoice
•75% invoiced after quote acceptance
•25% invoiced upon delivery of final conversion
•Payment must be in USD
Price Exclusions
•Hardware
•Support ProgramoAnnual support at the rate of 20% of the full list price
o Support invoiced separately upon completed installation
Terms & Conditions - Integration Configuration
Payment Terms
•Payment due upon receipt of invoice•75% invoiced after quote acceptance
•25% invoiced upon delivery of final conversion•Payment must be in USDPrice Exclusions
•Hardware
•Microsoft® SQL Server™
•Support ProgramoAnnual support at the rate of 20% of the full retail priceoSupport invoiced separately upon install
Terms & Conditions - Database Conversion
Payment Terms
•Payment due upon receipt of invoice
•Payment must be made in USD•75% invoiced upon quote acceptance
•25% invoiced upon training completion or one year from signed quotePrice Exclusion
•Costs incurred as a result of Customer requested changes
Terms & Conditions - Training (Initial, Follow-Up)
Payment Terms:
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 5 / 6
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
Terms & Conditions – FieldSyte™ System, powered by RC MapEngine™ - Subscription
Subscription Term
•Five (5) year initial term, unless otherwise specified on the face of this Quote; commencing upon installation.
•Automatic (1) year renewals after initial term, unless/until canceled in writing by notice given before the nextcontract year; renewal pricing may be subject to change.
Payment Terms
•Payment due in USD upon receipt of invoice.
•Configuration & Setup and first month covered by initial invoice.
•Subscription fees invoiced monthly at quoted rates, in advance.
Price Inclusion
•Initial Setup and Testing.
•Subscription includes Support Program.
Price Exclusion
•Underlying Milsoft® system required; sold or subscribed separately.
IMPORTANT! Customer’s Hardware and Operating System (OS) Requirements
Customer, before signing below, please check online to ensure that you have current compatibility and the latest recommendations for optimum functionality of this and all Milsoft® software with your computers and devices, through the following link to our sharefile: https://www.mymilsoft.com/resources/hardware-requirements
Account Name: ___________________________________________
Accepted By: _____________________________________________
Printed Name: ____________________________________________
Date: ____________________________________________________
PO# (if applicable): ________________________________________
Terms & Conditions – Texting Subscription - Powered by TextPower®
Subscription Term
•Five (5) year initial term, unless otherwise specified on the face of this Quote; commencing upon installation.
•Automatic (1) year renewals after initial term, unless/until canceled in writing by notice given before the nextcontract year; renewal pricing may be subject to change.
Payment Terms
•Payment due in USD upon receipt of invoice.
•Configuration & Setup fee and first month covered by initial invoice.•Subscription fee invoiced monthly at quoted rate, in advance.•Text fees apply as incurred (in excess of bundled monthly max), at quoted rate, in next monthly
invoice.
•Communications Assurance Program (lookup of all phone numbers and loading mobiles into your
"opt-in" database) billed at $0.025 per number. Opt-In Processing subsequent to initial upload is billedat $0.045 per opt-in number.
Price Inclusion
•Initial Setup and Testing.
•Number of texts per month as quoted, up to monthly max, within subscription fee.
•Subscription includes Support Program.
Price Exclusion
•Underlying Milsoft or Daffron system required; sold or subscribed separately.
•Carrier surcharges, if any.
Quote 51199 | Submission Options: quotes@milsoft.com | P.O. Box 5726 Abilene, TX 79608 | Fax: 325-690-0338 6 / 6
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
1
ATTACHMENT J – OMS-IVR REQUIREMENTS
RFP184285 – Outage Management System Requirements
Module Capability
ID
Prior
ity
Description Response
Architec
ture
OMS.AR.00
1
Critic
al
The solution will include two environments (Production and
Test/Training) for all solution components.
Current Base
Architecture OMS.AR.002 Critical The OMS has desktop clients that are compatible with Windows and Chrome. Chrome is used by most staff, but
there is no City standard. List all supported browsers as a comment, as well as any plug-ins required.
Current Base
Architec
ture
OMS.AR.00
3
Critic
al
The OMS server(s) can operate on Windows Server 2016 or
later. Describe compatible Windows OS versions and patch levels in the comments.
Current Base
Architecture OMS.AR.004 Critical The OMS server(s) can be deployed in a virtual machine environment (preferably VMware). Describe the supported
virtualization technologies and vendors in the comments.
Current Base
Architec
ture
OMS.AR.00
5
Critic
al
The OMS has an architecture that provides capabilities for
the archiving, reporting and storage of historical information in such a manner that operational performance is not
impacted when historical reports are generated.
Current Base
Architecture OMS.AR.006 Critical The OMS has a mechanism for establishing redundancy (with auto fail-over) and availability greater than what can be
achieved by a single server environment. Describe the mechanism used. Indicate the amount of down time that
occurs during a typical hardware failure.
Partially Comply
Architec
ture
OMS.AR.00
7
Critic
al
The OMS shall support high availability architecture and be
designed for 24x7 uptime.
Current Base
Architecture OMS.AR.008 Critical The OMS provides the ability to restore all performance indices data (e.g. SAIDI, MAIFI, etc.) to a backup point in
the event of a computer storage failure or other catastrophic failure.
Current Base
Architec
ture
OMS.AR.00
9
Critic
al
The OMS shall support an open SQL database that meets the
ANSI-SQL 2016 standard. Describe any database licensing requirements (for example, whether vendor-provided or
CPAU-provided).
Current Base
Architecture OMS.AR.010 Critical The system should be designed to be used with tablets and mobile devices, in addition to PCs. Current Base
Architec
ture
OMS.AR.01
1
Critic
al
The OMS system must be available during maintenance
activities.
Current Base
Security OMS.SEC.001 Critical The OMS modules includes an audit trail of all user actions, including user credentials, date/time and action taken. Current Base
Security OMS.SEC.0
02
Critic
al
The OMS modules support usernames and passwords.
Explain password management functionality in the comments.
Current Base
Security OMS.SEC.0
03
Optio
nal
The OMS modules support Active Directory. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
2
Security OMS.SEC.0
04
Critic
al
The OMS user sessions have session timeouts that
automatically log out a user after a certain amount of user inactivity, and this period is configurable and may be turned off for certain users.
Not
Provided
Security OMS.SEC.005 Critical The OMS supports WSS. Current Base
Security OMS.SEC.006 Critical The OMS supports transport layer security via TLS/SSL. Current Base
Security OMS.SEC.007 Optional The OMS supports multifactor authentication. Please describe the technologies and standards supported in the
comments.
Current Base
Security OMS.SEC.008 Critical The OMS application supports industry standard authentication mechanisms I,nstead of proprietary authentication methods.
Current Base
Security OMS.SEC.009 Critical The vendor must comply with City's VISA, Vendor Cybersecurity Terms and Conditions (to be included in the final contract as an exhibit), and Information Privacy Policy (to be included in the final contract as an exhibit).
Current Base
Security OMS.SEC.0
10
Critic
al
For systems hosted using third-party cloud services, such as
AWS, the system must offer a secured, logically separated IT environment in cloud consistent with the AWS_Security_Compute_Services_Whitepaper document (https://d1.awsstatic.com/whitepapers/Security/Security_Compute_Services_Whitepaper.pdf).
Current Base
User Categori
es
OMS.UC.001 Critical The OMS should support role-based security permissions. Partially Comply
User Categories
OMS.UC.002 Critical The OMS has the ability to restrict functionality by user categories, and each user has the ability to be assigned to one or more user category.
Partially Comply
User
Categories
OMS.UC.00
3
Critic
al
The OMS supports user categories that can be restricted to
have the ability to view information and not modify any data in the OMS.
Partially
Comply
User Categori
es
OMS.UC.004 Critical The OMS supports a user group that is restricted to edit functions that do not impact the electrical model (i.e. can do
everything except for open and close devices, cut or insert jumpers, etc.).
Partially Comply
User Categories
OMS.UC.005 Critical The OMS supports user categories that can only edit crew related information.. Partially Comply
User Categories
OMS.UC.006 Critical The OMS supports user categories that can only edit outage details. Partially Comply
User
Categories
OMS.UC.00
7
Critic
al
The OMS supports a user categories that can perform all
actions (e.g. Administrator).
Partially
Comply
User Categories
OMS.UC.008 Critical The OMS shall support a total of 6 concurrent users. This limit does not include users of the call taking application. Current Base
Availability & OMS.NFR.001 Critical The OMS system shall be available 99.99% of the time, not including disaster recovery and/or planned maintenance. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
3
Perform
ance
Availability & Performance
OMS.NFR.002 Critical The OMS shall support appropriate tooling, test, version control, and governance facilities to expedite testing, deployment, rollback and applying code patches to application software without downtime.
Current Base
Availability & Perform
ance
OMS.NFR.003 Critical The OMS shall support performance logging and alerts to evaluate/notify support staff of performance issues and the performance levels.
Current Base
Availability & Performance
OMS.NFR.004 Critical The OMS shall be capable of holding at least 365 days worth of outage data, after which it may be moved to another system for archival. The number of days may be reduced based on the ease or ability to import data from the archival system.
Current Base
Availability &
Performance
OMS.NFR.005 Critical End user response time to queries (or actions) shall be sub second for heavy user, less than 5 seconds for web client and
less than 8 seconds for a mobile client under normal and event load conditions
Current Base
Availability & Performance
OMS.NFR.006 Critical An outage shall be created within 1 second of receipt of inbound call from IVR, under blue sky or storm load, without loss of calls.
Current Base
Operator Displays OMS.OD.001 Critical A geographic map display window that shows all of the distribution circuits. The source data for the view is from the
ESRI ArcGIS Utiliy Network Model.
Current Base
Operator Displays OMS.OD.002 Critical The OMS has decluttering ability to turn off displayed items (text annotations, poles, secondary roads etc.) as the user zooms out and zooms in. It has the ability to display specific
map layers based on the zoom perspective, e.g. If the user is viewing a large area then only display primary conductors and major street centerlines. This capability should be configurable by the user or administrator and applicable to a user or group of users. The users should be able to select this option from a menu.
Current Base
Operator Displays OMS.OD.003 Critical The map viewer has the ability to load raster background data such as satellite, search light, or drive-by photo images and Google map backgrounds or equivalent. The display must include an accurate geographic representation of
distribution circuits and the underlying of the land base information, e.g. street centerlines, aerial or satellite imagery. Please explain the technology used in comments.
Current Base
Operator
Displays
OMS.OD.00
4
Critic
al
The map viewer has the ability to load dynamic background
data from a weather data source. List the weather data sources supported in the comments.
Current Base
Operator Displays OMS.OD.005 Critical The ability to manually turn on and off the display of layers or groups of objects. Current Base
Operator
Displays
OMS.OD.00
6
Critic
al
The map viewer automatically loads all visible areas of the
distribution system without user intervention when the user is panning and zooming around.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
4
Operator
Displays
OMS.OD.00
7
Critic
al
The map viewer has the ability to zoom and pan to enable
easy searching of components on the distribution system.
Current Base
Operator Displays OMS.OD.008 Critical The ability to search for devices by name, locations by address, customer by address. Current Base
Operator Displays OMS.OD.009 Critical The map viewer has the ability to generate simplified views of feeders by generating an on-the-fly orthogonal schematic of a selected feeder. This function includes the ability to generate a schematic representation of one or more distribution circuits.
Current Base
Operator Displays OMS.OD.010 Critical The map viewer has the ability to view only selected feeders and substations Current Base
Operator Displays OMS.OD.011 Critical The system provides the Admin configurable symbology for device representation on maps. Current Base
Operator Displays OMS.OD.012 Critical The ability to search must support the use of wildcards and return multiple matching results for the users selection. Current Base
Operator
Displays
OMS.OD.01
3
Critic
al
The ability to open a separate magnification window to show
details while keeping the main map view open and zoomed out.
Current Base
Operator Displays OMS.OD.014 Critical The ability to have an overview window that shows outage locations on top of regional polygons or other geographical
layer showing physical features.
Current Base
Operator Displays OMS.OD.015 Critical The user should be able to be perform a trace from a selected point upstream, downstream or both and perform a query against attributes in the model for all of the equipment
touched by the trace. The trace should be by selected phase or for all phases present.
Current Base
Operator Displays OMS.OD.016 Critical The symbols for all switchable devices have the ability to change automatic and manually when they are open or closed
and have the ability to have unique symbols for individual phases being open or closed.
Current Base
Operator Displays OMS.OD.017 Critical The map viewer has the ability to dynamically color the conductors based upon the source feeder and change as the feeder extend changes due to switching.
Current Base
Operator Displays OMS.OD.018 Critical The map viewer represents de-energized segments with a unique color to graphically differentiate energized and de-energized sections of circuits.
Current Base
Operator
Displays
OMS.OD.01
9
Critic
al
The map viewer represents the conductor segments
predicted de-energized by the OMS with another unique color.
Current Base
Operator Displays OMS.OD.021 Critical The map viewer represents the customers predicted de-energized by the OMS with another unique color. Current Base
Operator Displays OMS.OD.024 Critical The map viewer can display the locations of crews based upon their assigned work. Current Base
Operator Displays OMS.OD.025 Critical The map viewer has an option to display the locations of crews based upon GPS coordinates provided by a mobile or AVL system.
Current Base
Operator Displays OMS.OD.026 Critical Authenticated user (with correct security permissions) has the ability to open and close at any point in the system. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
5
Operator
Displays
OMS.OD.02
7
Critic
al
When I device opened or closed, the system must provide
immediate feedback of load warnings, loop creation and feeder tie creation. Symbology shall indicate each of these three conditions.
Current Base
Operator Displays OMS.OD.028 Critical The user has the ability to display all opened and closed conductors to represent cut or downed wires. Current Base
Operator Displays OMS.OD.029 Critical The map viewer has the ability to display a visible indication of Normal Open points (via Arrow, Highlight, other). Current Base
Operator Displays OMS.OD.030 Critical The user has the ability to insert and remove jumpers, conductors and temporary switches. Current Base
Operator
Displays
OMS.OD.03
1
Critic
al
The jumpers can be by specific phase or for all phases and be
able to cross phases, i.e. connect a phase A conductor to a nominally fed phase B conductor.
Current Base
Operator Displays OMS.OD.032 Critical The system provides the ability to confirm outage from device on map. Current Base
Operator
Displays
OMS.OD.03
3
Critic
al
The Systems provides the ability to change incident location
from one device to a different device (to actual trouble location).
Current Base
Operator Displays OMS.OD.034 Critical Provide the functionality to make changes to the operational electrical network, and have the changes persist through any
refreshes from the GIS system.
Current Base
Operator Displays OMS.OD.035 Critical Graphically display safety and clearance tags in the electrical network. Current Base
Operator Displays OMS.OD.036 Critical Interface with tag generation programs. Partially Comply
Operator
Displays
OMS.OD.03
7
Critic
al
Display a symbol indicating the location of customers who
have initiated trouble calls.
Current Base
Operator Displays OMS.OD.038 Critical The system should provide the functionality to display nested outages. Current Base
Operator Displays OMS.OD.039 Critical The ability to add and remove notes associated with a specific device. A device note symbol must be created and displayed adjacent to the device.
Current Base
Operator Displays OMS.OD.040 Critical The ability to center in the graphic window displays the location of an outage record or crew location. The centering of the outage or crew symbols is triggered by a request from the outage summary or crew summary windows.
Current Base
Operator Displays OMS.OD.041 Critical Provide a map display function that provides the capability to select an outage and center the outage location in the graphic display window.
Current Base
Operator Displays OMS.OD.042 Critical Provide a configurable OMS operator log book function which is designed to replace existing manual log book system of record keeping.
Partially Comply
Operator Displays OMS.OD.043 Critical The operator has the ability to ping individual AMI meters in order to verify the outage and restoration from the operator displays.
Current Base
Operator Displays OMS.OD.044 Critical The OMS shall display the results of the ping in the operator displays. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
6
Operator
Displays
OMS.OD.04
5
Critic
al
Provide functionality to display either the operational
electrical network or the as-designed electrical network for an area, and highlight graphically any devices that are in a non-standard configuration.
Current Base
Reporting OMS.RPT.001 Critical The OMS includes standard reports using a report writing package (Crystal Reports). List any other supported report writing packages.
Current Base
Reporting OMS.RPT.002 Critical The OMS reports includes a report that calculates standard IEEE reliability metrics (e.g., SAIDI, CAIDI, SAIFI, and CAIFI) for a user defined time frame (past 5 years, last year, current year to date, last month, current month to date, last week and the previous day). Provide details in comments.
Current Base
Reporting OMS.RPT.003 Critical Standard IEEE reliability metrics should be available based on equipment, customer, circuit, cause or system wide for user defined time frames. Provide details in comments.
Current Base
Reporting OMS.RPT.004 Critical The OMS reports include the above report for system, regions, substations and feeders for the same periods. Current Base
Reporting OMS.RPT.005 Critical The OMS reports calculate the IEEE indices with and without the inclusion of outages for major event days, as defined in IEEE 1366-2012.
Current Base
Reporting OMS.RPT.006 Critical The OMS tracks and reports customer calls or AMI notifications that cannot be associated to a known customer location.
Current Base
Reporting OMS.RPT.007 Critical The OMS includes a report that lists all outages that occurred within a range of user defined dates and may be filtered by outage cause and condition. Provide details in comments.
Current Base
Reportin
g
OMS.RPT.0
08
Critic
al
The OMS reports are provided in a format that supports the
ability for reports to be customized without having to re-define the reports from scratch.
Current Base
Reporting OMS.RPT.009 Critical The OMS includes documentation and a data dictionary of all of the tables and columns used by the standard reports. Current Base
Reportin
g
OMS.RPT.0
10
Critic
al
The OMS includes documentation of all additional tables that
contain operational data so that reports can be extended and defined.
Current Base
Reporting OMS.RPT.011 Critical The OMS includes configurable dashboards or portals that can reflect current outage and system operating conditions
that can be made available to a large user base internally. Describe the dashboard or portal technology and available functionality.
Current Base
Reportin
g
OMS.RPT.0
12
Critic
al
The OMS dashboard/portals are able to be updated so that
information displayed on the portals is no older than 5 minutes.
Current Base
Reporting OMS.RPT.013 Critical The OMS provides an outage dashboard with related map which is configurable to display current outages and
associated information.
Current Base
Reporting OMS.RPT.014 Critical The system should provide the ability to perform analysis and produce ad-hoc reports against historical outage data (e.g., outage cause, number of outages on a given fuse,
feeder, transformer, etc. over a user defined period of time).
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
7
Reportin
g
OMS.RPT.0
15
Critic
al
The system should allow tracking of outage information on a
per-customer basis, at least for important customers, so that outage durations and frequency of outages may be recorded for CEMI (Customers Experiencing Multiple Interruptions) purposes, for instance.
Current Base
Reporting OMS.RPT.016 Critical The system should have the ability to report historical ETR vs. actual restorations by different categories, crew, different timeframes, equipment.
Current Base
Reportin
g
OMS.RPT.0
17
Critic
al
The system should have the ability to edit completed outages
with a logbook feature.
Current Base
Reporting OMS.RPT.018 Critical The system should have the ability to display dashboard on mobile platform. Current Base
Tabular Lists OMS.TD.001 Critical All OMS tabular lists are dynamically updated without any operator interaction (that is, there is a configurable dynamic refresh rate).
Current Base
Tabular Lists OMS.TD.002 Critical The OMS has a dynamic list of grouped calls (not individual calls). Current Base
Tabular Lists OMS.TD.003 Critical The OMS has a dynamic list of all calls by feeder and substation (not grouped outages). Current Base
Tabular Lists OMS.TD.004 Critical The OMS has a dynamic summary list of outages and counts of outages by user defined region. Current Base
Tabular Lists OMS.TD.005 Critical The OMS dynamic list of grouped calls supports a dynamic status to reflect current status of event including: acknowledge, crew on site, ETA, and restored.
Current Base
Tabular Lists OMS.TD.006 Critical The OMS has an outage list summary screen which displays current outages and associated information including outage number, outage status, device(s), number of trouble calls per outage number, number of affected customers per outage
scenario, reported hazards, start time, assigned crew(s) and operating area.
Current Base
Tabular Lists OMS.TD.007 Critical All dynamic lists have sorting capability on any column, including the capability to have multiple nested sorts. Current Base
Tabular Lists OMS.TD.008 Critical All dynamic lists support easy (1-click) navigation to the map viewer. Current Base
Tabular Lists OMS.TD.009 Critical The OMS has a dynamic summary of reliability indices by substation and by feeder. Current Base
Tabular Lists OMS.TD.010 Critical All dynamic lists have filtering capability, with the ability to filter on multiple fields. Current Base
Tabular
Lists
OMS.TD.01
1
Critic
al
All dynamic lists have the ability to save sorts and filters by
user or user category.
Current Base
Tabular Lists OMS.TD.012 Critical Data from all tabular displays may be manually exported to Microsoft Excel and emailed to a specific user. Current Base
Tabular Lists OMS.TD.013 Critical Allow for the entry of partial and complete restoration details by specifying the points on the distribution network that have been energized. Restoration times and the customers restored by the restoration steps should be recorded.
Current Base
Integration OMS.INT.001 Critical The OMS shall support integration to other utility applications via standard Web Services, File Exchange, and
APIs, etc.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
8
Integrati
on
OMS.INT.00
2
Critic
al
The OMS shares a common electrical operations model that
represents the electrical substations and circuits in the same format as the ESRI GIS (e.g. Web API, ArcGIS Feature Services, etc.)
Current Base
Integration OMS.INT.003 Critical The OMS model is based upon the ESRI distribution electrical GIS definitions. Identify in the comments the version supported.
Current Base
Integration OMS.INT.004 Critical The system must support integration with ESRI GIS and have tools within the OMS model for reviewing the electrical model updates before they are applied to the production OMS model.
Current Base
Integration OMS.INT.005 Critical The OMS supports integration with an AMI and MDM systems. Current Base
Integrati
on
OMS.INT.00
6
Critic
al
The OMS supports integration with an AMI and MDM
system using MultiSpeak. Identify supported versions of MultiSpeak.
Current Base
Integration OMS.INT.007 Critical The OMS can use the AMI and MDM outage detection and last gasp messages to drive the outage prediction engine. Partially Comply
Integration OMS.INT.008 Critical The AMI and MDM integration supports outage restoration messages (power on) to confirm and validate outage restorations.
Current Base
Integration OMS.INT.009 Critical The OMS can filter out AMI and MDM calls based upon factors that drive false indications, including meter pulls and non-pay disconnects.
Current Base
Integration OMS.INT.011 Critical The OMS supports integration with an IVR system for the purposes of taking automated trouble calls. Current Base
Integration OMS.INT.012 Critical The OMS supports integration with an IVR system for the purposes of allowing callers to request outage status. Current Base
Integration OMS.INT.013 Critical The OMS supports integration with an IVR system for the purposes of notifying callers they are included in a known outage.
Current Base
Integration OMS.INT.014 Critical The OMS supports integration with an IVR system for the purposes of notifying callers of the estimated time of restoration.
Current Base
Integration OMS.INT.015 Critical The OMS supports integration with an IVR system for the purposes of calling customers with changes in status, updates to estimated time of restoration, and call back.
Current Base
Integrati
on
OMS.INT.01
6
Critic
al
The OMS must support integration with SAP CIS for
Customer Information.
Current Base
Integration OMS.INT.017 Critical The OMS supports the integration with Advanced Control Systems (ACS) SCADA system for the purposes of obtaining breaker and switch status for all SCADA controlled devices. ACS SCADA controlled devices must be non-operable in the OMS system.
Current Base
Integration OMS.INT.018 Critical The OMS-ACS SCADA interface is compliant with MultiSpeak standard. Identify supported versions of MultiSpeak.
Current Base
Integration OMS.INT.020 Critical The system should support integration with an AVL solution. CPAU uses Verizon Connect Fleet GPS. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
9
Integrati
on
OMS.INT.02
1
Critic
al
Provide the ability to integrate with ArcGIS base maps or
similar service for public mapping of outages.
Current Base
Integration OMS.INT.022 Critical The OMS should support integration to the Utilities Department’s customer self-service portal, MyCPAU. Utilities has contracted with third party service provider, Smart Energy Water (SEW), for use (and hosting) of SEW’s Smart Customer Mobile (SCM) portal. Integration will be for the purpose of sending outbound outage notifications, alerts,
and updates to customers via text and email which will be triggered by the OMS but delivered to customers via the MyCPAU customer portal.
Current Base
Call
Taking
OMS.CT.00
1
Critic
al
The OMS includes a call-taking module for internal and
external users.
Current Base
Call Taking OMS.CT.002 Critical The OMS call-taking module has the ability to search for an account by entering in the caller's phone number. A caller may have one or more numbers (work, home, cell, for example).
Current Base
Call Taking OMS.CT.003 Critical The OMS call-taking module supports the ability to search by the caller account number. Current Base
Call Taking OMS.CT.004 Critical The OMS call-taking module supports the ability to search by the caller number. Current Base
Call
Taking
OMS.CT.00
5
Critic
al
The OMS call-taking module supports the ability to search
by the caller first and last name.
Current Base
Call Taking OMS.CT.006 Critical The OMS call-taking module supports the ability to search by the outage location address. Current Base
Call Taking OMS.CT.007 Critical The OMS call-taking module has the ability for all searches listed above to include wildcards in the search. Current Base
Call Taking OMS.CT.008 Critical The OMS call-taking module displays for the matched customers account the current outage status. Current Base
Call Taking OMS.CT.009 Critical The OMS call-taking module displays if the customer is disconnected for non-payment. Current Base
Call Taking OMS.CT.010 Critical The OMS call-taking module displays for the matched customers account the Estimated Time of Restoration Time
(ETR).
Current Base
Call Taking OMS.CT.011 Critical The OMS call-taking module displays for the matched customers the current outage case notes. Current Base
Call Taking OMS.CT.012 Critical The OMS call-taking module displays for the matched customers the current outage crew status. Current Base
Call
Taking
OMS.CT.01
3
Critic
al
The OMS call-taking module has the ability to retrieve for
the matched customers the history of all outage calls taken.
Current Base
Call Taking OMS.CT.014 Critical The OMS call-taking module has the ability to retrieve for the matched customers the history of all outages for that account.
Current Base
Grouping OMS.GRP.001 Critical The OMS includes an outage call grouping function that automatically groups all calls to a common open point based upon a dynamic electrical connectivity model.
Current Base
Grouping OMS.GRP.003 Critical The OMS outage call grouping function is configurable with an outage prediction rules engine. Describe your rules engine.
Partially Comply
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
10
Groupin
g
OMS.GRP.0
04
Critic
al
The call grouping function is performed as new calls come
into the OMS in real time.
Current Base
Grouping OMS.GRP.005 Critical The OMS supports a mechanism for the user to manually change, override and create new groups. Current Base
Grouping OMS.GRP.007 Critical The OMS grouping function uses the phases of the connectivity model and the phase location of the calls to make predictions by phase.
Current Base
Grouping OMS.GRP.008 Critical The OMS prediction engine does not change an outage prediction location for any outage that is confirmed by the user.
Current Base
Groupin
g
OMS.GRP.0
09
Critic
al
The outage prediction grouping is based upon all changes to
model, including open and close of devices (by phase).
Current Base
Grouping OMS.GRP.010 Critical The outage prediction is based upon all changes to model including cuts and jumpers (by phase). Current Base
Grouping OMS.GRP.011 Critical The OMS has the ability to separate one or multiple calls/locations from an incident for additional repair work (e.g., fixed fuse, individual customer still out).
Current Base
Grouping OMS.GRP.012 Critical The OMS user has the ability to confirm an outage's predicted location or device on the user's main screen and through the graphical interface.
Current Base
Groupin
g
OMS.GRP.0
13
Critic
al
The OMS user has the ability to identify both an outage's
damaged location and its affected device.
Current Base
Grouping OMS.GRP.014 Critical The OMS user has the ability to associate a non-connected outage to a device. Current Base
Grouping OMS.GRP.015 Critical Ability to create and view high-level incidents comprised of several individual incidents (nested incidents). Current Base
Grouping OMS.GRP.016 Critical The OMS can accept and manage calls not related to a customer (e.g., intersection). Current Base
Grouping OMS.GRP.017 Critical The OMS can accept and manage calls for customers without electrical connectivity. Current Base
Grouping OMS.GRP.018 Critical The OMS has the ability to identify outages containing ranked priority customers (e.g., hospitals) on the user's main
screen and on the graphical interface.
Current Base
Grouping OMS.GRP.019 Critical The OMS administrative users have the ability to configure outage priority (including customer profile, key account, cause, problem code, etc.).
Current Base
Grouping OMS.GRP.020 Critical The OMS administrative user has the ability to configure incident to prevent grouping based on a later event (e.g., working on wire down, then a fuse blows).
Current Base
Grouping OMS.GRP.021 Critical The OMS will automatically predict customers "out" that have not called in to report the outage. Current Base
Grouping OMS.GRP.023 Critical The OMS has the capability to manually split existing outages into separate outages, and to merge multiple outages into a single outage.
Current Base
Grouping OMS.GRP.024 Critical The system must allow a dispatcher to move an outage out of an open state to an intermediate state without providing all of the info required to final close an outage.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
11
Groupin
g
OMS.GRP.0
25
Critic
al
The ability to indicate the predicted device associated with an
outage is confirmed closed. The prediction engine should take the device’s new status into consideration in subsequent outage prediction analysis.
Current Base
Dispatching OMS.DSP.001 Critical The OMS allows the user to define crews. The crew definitions must be configurable and include, but not be limited to, the following fields: number of crew members, the type of the crew, equipment information, type of vehicle
associated with the crew and assign individuals to a crew.
Current Base
Dispatching OMS.DSP.002 Critical The crew functionality reflects when a crew goes on and off shift and make the off shift crews unavailable for assignment. Current Base
Dispatching OMS.DSP.003 Critical The ability to change the working status of a crew (e.g., from unavailable to available). Current Base
Dispatch
ing
OMS.DSP.0
04
Critic
al
The OMS has a function to manage calling crews in for
work, it tracks contact information and their history of all previous calls and whether they were reached, and came in or declined when called.
Current Base
Dispatching OMS.DSP.005 Critical The OMS includes the ability to configure attributes and relationships on employee and crew records. Current Base
Dispatching OMS.DSP.006 Critical Crews can be defined as permanent or temporary (contractor, mutual aid). Newly created crews are immediately available for work in the system.
Current Base
Dispatching OMS.DSP.007 Critical THE OMS supports the ability to associate a resource (person) to multiple crews. Current Base
Dispatching OMS.DSP.008 Critical The OMS supports the ability to assign (or "un-assign") outages to one or more crews at the same time or sequentially. It also provides the ability to assign or “un-
assign” one or more crews to an outage.
Current Base
Dispatching OMS.DSP.009 Critical The OMS supports the ability to create a queue of work for a crew. Current Base
Dispatching OMS.DSP.010 Critical A “Crew Summary” window indicating available crews and number of incidents that are assigned or working is provided. Current Base
Dispatching OMS.DSP.011 Critical The OMS supports the ability to progress an outage through specific stages including, assigned, dispatched, working, closed and completed. Each change in status should be recorded and time stamped in an outage log.
Current Base
Dispatch
ing
OMS.DSP.0
12
Critic
al
The OMS provides the ability for the user to indicate that a
crew is at the work site.
Current Base
Dispatching OMS.DSP.013 Critical Allow a dispatcher to add comments or notes associated with an outage and record the comments in an outage log. Current Base
Dispatching OMS.DSP.014 Critical The ability to update outage related information including outage cause, restoration steps and restoration time and type of equipment affected. The system should enforce the entry of certain fields such as restoration time, outage cause code prior to allowing a user to close an outage.
Current Base
Dispatching OMS.DSP.015 Critical The system should have the ability to identify additional equipment that failed as part of an outage. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
12
Dispatch
ing
OMS.DSP.0
16
Critic
al
The OMS crew functionality has the ability to be integrated
with a mobile data system, but support manual management of non-mobile enabled crews in addition to the mobile enabled crews.
Current Base
Callbacks OMS.CB.001 Critical The OMS has a module for the purposes of managing callbacks to customers who have been restored. It must contain a dynamic list of customers restored who requested a callback.
Current Base
Callback
s
OMS.CB.00
2
Critic
al
The OMS callback module has the ability to initiate callbacks
to only customers who request callbacks when restored (or those registered for notifications).
Current Base
Callbacks OMS.CB.003 Critical The OMS callback module also has the ability to be able to callback customers whose ETR was changed greater than a
configurable amount or have a new ETR available.
Current Base
Callbacks OMS.CB.004 Critical The OMS callbacks module has the ability to be integrated with an IVR system for performing automatic callbacks. Current Base
Callbacks OMS.CB.005 Critical The OMS callbacks module has the ability to phone via IVR, send text and/or email (configurable) messages to customers
updating them at various stages of the outage restoration process (e.g., change of ETR, time when restored etc.)
Current Base
Notificiations OMS.NFY.001 Critical The OMS includes a configurable automatic notification capability that notifies internal users via email and text message when outages are reported, predicted, revised, or restored.
Current Base
Notificiations OMS.NFY.002 Critical The OMS notification function has the ability to notify internal users via configurable selections--email or text---
when outages are confirmed.
Current Base
Notificiations OMS.NFY.003 Critical The OMS notifications have configurable triggers for notification of each internal user based upon: size of outage, inclusion of a specific customer, or the inclusion of any
critical customer.
Current Base
Notificiations OMS.NFY.004 Critical The OMS notification function generates a notification when an ETR for an outage previously notified is created or revised. The notification message must contain a configurable set of parameters including: number of customers affected, type of customer, customer location, and affected feeders/devices.
Current Base
Notificia
tions
OMS.NFY.0
05
Critic
al
The OMS generates a notification when an ETR (for a
previously notified outage) exceeds the time by some configurable amount of time.
Current Base
Notificiations OMS.NFY.006 Critical The OMS generates a notification for internal users when an outage is restored to service. The notification may be
configured by a set of parameters as defined in OMS.NFY.004.
Current Base
Notificiations OMS.NFY.007 Critical The OMS notification system is capable of generating notification to customers when outage is predicted, confirmed, or when ETR is created or updated.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
13
Notificia
tions
OMS.NFY.0
08
Critic
al
The OMS notification of customers includes the capability to
notify those customers who desired to be notified when they are restored.
Current Base
Notificiations OMS.NFY.009 Critical Provide capability to automatically contact a customer electronically with outage status updates using IVR. Current Base
Notificia
tions
OMS.NFY.0
10
Critic
al
Provide capability to automatically contact a customer
electronically with outage status updates using email.
Current Base
Notificiations OMS.NFY.011 Critical Provide capability to automatically contact a customer electronically with outage status updates using text message. Current Base
Notificiations OMS.NFY.012 Critical Support integration with corporate social media sites such as Twitter and Facebook, and CPAU's customer portal, which is Smart Energy Water (SEW).
Partially Comply
Notificiations OMS.NFY.013 Critical All external notification functionality must also apply to internal users--supervisors, managers, customer service representatives, etc.--on a configurable basis.
Current Base
Notificia
tions
OMS.NFY.0
14
Critic
al
Audible notification can be configured to play when an
outage event or trouble call occurs.
Current Base
Notificiations OMS.NFY.015 Critical Notification list for known outages for customers who enroll must have an option for time of day. Current Base
Estimated Restoration Time
OMS.ETR.001 Critical The OMS includes functionality to automatically generate Estimated Time of Restoration (ETR) for each outage. Provide details on how ETRs are calculated.
Current Base
Estimate
d Restoration Time
OMS.ETR.0
12
Critic
al
The OMS has the ability to override ETR on individual
incident manually.
Current Base
Estimated Restorat
ion Time
OMS.ETR.013 Critical The OMS has the ability to override ETR on a group of incidents manually. Current Base
Estimated Restoration Time
OMS.ETR.014 Critical The OMS has the ability to configure ETR expiration alerts. Current Base
Estimate
d Restoration Time
OMS.ETR.0
15
Critic
al
The OMS has the ability to disable all ETR functionality. Current Base
Switching OMS.SW.001 Critical The OMS must include a tool to manually prepare switching plans that contain a sequential record of all steps taken to perform a switching job.
Current Base
Switching OMS.SW.002 Critical The user is able records/create switch order steps ahead of time. Current Base
Switching OMS.SW.003 Critical The user is able to identify a switch order for planned outages. Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
14
Switchin
g
OMS.SW.00
4
Critic
al
The OMS switching module has the ability to track one or
more approvals of the switching plan.
Current Base
Switching OMS.SW.005 Critical The OMS switching module allows users to record switching plan header information. The header information is configurable to include multiple pre-defined fields but be able to include at a minimum the following fields: description, location, project number, planned start date/time and planned end date/time.
Partially Comply
Switchin
g
OMS.SW.00
6
Critic
al
The OMS switching module has the ability to support the
creation of non-switching steps such as check load, place grounds, or any other non-switching action.
Current Base
Switching OMS.SW.007 Critical The OMS switching module allows switching plans to be played back against the real time model as each step is
executed.
Current Base
Switching OMS.SW.008 Critical The OMS switching module supports the creation of steps for the placing and removing of tags, safety documents and notes.
Current Base
Switchin
g
OMS.SW.00
9
Critic
al
The OMS switching module validates for the correct
application of tags and safety documents to ensure proper isolation for safety.
Current Base
Switching OMS.SW.010 Critical The OMS switching module includes a function for the user to select a sequence of steps in a switching plan that is being
prepared and generate the reverse sequence of steps (i.e., for each open it writes a close, etc.).
Current Base
Switching OMS.SW.011 Critical The OMS switching module generates a list of customers impacted by a planned outage. The lists can be exported in CSV format.
Current Base
Switching OMS.SW.012 Critical The OMS switching module stores and catalogs historical switching orders. Current Base
Switching OMS.SW.013 Critical The user can search historical switching orders using the fields in OMS.SW.005. Current Base
Switching OMS.SW.014 Critical The user can edit historical switching orders and save as new. Current Base
External Map OMS.EXTMAP.001 Critical Provide an outage map that can be integrated into the CPAU website, which is mobile-responsive and can be scaled dynamically to accommodate a customer's smartphone
resolution.
Current Base
External Map OMS.EXTMAP.002 Optional Provide an outage map through a native mobile app. Current Base
External Map OMS.EXTMAP.003 Critical The outage map possesses GIS features, such as pan and zoom. Current Base
External Map OMS.EXTMAP.004 Critical Displays outages by zip code boundaries. Current Base
External Map OMS.EXTMAP.005 Critical Prevent the user from zooming in on the map to sufficiently identify the exact service location. Current Base
External Map OMS.EXTMAP.006 Critical The outage map provides the ability to display the number of outages Current Base
External
Map
OMS.EXTM
AP.007
Critic
al
The outage map provides the ability to display the number of
affected customers.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
15
External
Map
OMS.EXTM
AP.008
Critic
al
The outage map provides the ability to display ETR for each
outage.
Current Base
External Map OMS.EXTMAP.009 Optional The outage map provides the ability to add dispatcher created notes or annotations to map. Current Base
External Map OMS.EXTMAP.010 Critical The outage map provides the ability to dynamically updates based on new, dispatched, crew onsite, confirmed, or restored outages.
Current Base
External Map OMS.EXTMAP.011 Critical Depending on the zoom level, the outage map provides the ability to automatically display or hide different map features.
Current Base
External
Map
OMS.EXTM
AP.012
Critic
al
The outage map provides the ability refresh automatically.
Describe the recommended refresh rate.
Current Base
External Map OMS.EXTMAP.014 Optional The outage map provides the ability for customers to report outages from the map. Current Base
External Map OMS.EXTMAP.015 Critical Includes usage statistics, such as Google Analytics. Current Base
Damage Assessment
OMS.DA.001 Optional The OMS has screens for collecting damage assessment information. Provide details. Current Base
Damage Assessm
ent
OMS.DA.002 Optional The OMS damage assessment function allows damage to be recorded at specific locations in the model. Current Base
Damage Assessment
OMS.DA.003 Optional Damage assessment information must include the ability to identify damage associated with poles, lines, cable and structures.
Current Base
Damage
Assessment
OMS.DA.00
4
Optio
nal
The damage assessment screens should show the user all
current locations of predicted and confirmed outages from the OMS so that the damage assessment may be correlated with the known outages in the system.
Current Base
Damage Assessment
OMS.DA.005 Optional The user should be able to record the counts of all types of damage. Current Base
Damage Assessm
ent
OMS.DA.006 Optional The user should be able to indicate whether the damage is accessible by vehicle. Current Base
Damage Assessment
OMS.DA.007 Optional One damage incident must include the ability to record one or more types of damage at that location. Current Base
Damage Assessment
OMS.DA.008 Optional Damage assessments can be related to outages by the user in the OMS or placed at a location where there is no current predicted outage.
Current Base
Damage Assessment
OMS.DA.009 Optional Damage assessment information must be able to be entered by a non-dispatch user type. Current Base
Damage Assessment
OMS.DA.012 Optional Damage assessment information must also be enterable and updatable by an external application through well documented APIs or integration methods.
Future Base Release
Damage Assessment
OMS.DA.013 Optional The damage assessment tool must have the capability to summarize damage assessment information to quantify restoration duration.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
16
Damage
Assessment
OMS.DA.01
4
Optio
nal
In addition to the ability to enter damage assessment in the
OMS, a separate integrated damage assessment application that can run on a mobile device (phone, tablet, etc.) in a disconnected state.
Future Base
Release
Damage Assessment
OMS.DA.015 Optional The damage assessment tool must allow assessors to receive and update work in the field. Future Base Release
Damage Assessm
ent
OMS.DA.016 Optional The damage assessment tool should allow assessors to view assignments not assigned to them, and review any updates or
notes that are attached.
Future Base Release
Damage Assessment
OMS.DA.017 Optional The damage assessment tool must allow assessors to report damage information in near real time. Future Base Release
Interacti
ve Voice Response
OMS.IVR.00
1
Critic
al
The IVR system simultaneously is able to support at least
1,000 concurrent calls with the ability of expanding during major storms.
Current Base
Interactive Voice Response
OMS.IVR.002 Critical The IVR system directs callers through various options by using a menu of choices. Current Base
Interacti
ve Voice Response
OMS.IVR.00
3
Critic
al
The IVR system permits callers to respond using voice
recognition.
Current Base
Interactive Voice Response
OMS.IVR.004 Critical The IVR system permits callers to respond using touch tones. Current Base
Interacti
ve Voice Response
OMS.IVR.00
5
Critic
al
The IVR system has the capability to identify caller by caller
ID or caller-entered, telephone number.
Current Base
Interactive Voice Response
OMS.IVR.006 Critical The IVR system is able to associate the number called to a physical customer address . Current Base
Interacti
ve Voice Response
OMS.IVR.00
7
Critic
al
Further identify caller locations using text-to-speech. Current Base
Interactive Voice Response
OMS.IVR.008 Critical The IVR system has the ability to quickly locate a customer record using various search criteria including account number, street address and/or customer name.
Current Base
Interacti
ve Voice Response
OMS.IVR.00
9
Critic
al
The IVR system has the ability of verifying outage location
address and other information using text-to-speech technology.
Current Base
Interactive Voice Response
OMS.IVR.010 Critical The IVR system has the ability to recognize calls from customers with multiple accounts or meters and distinguish which location is calling in the problem.
Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
17
Interacti
ve Voice Response
OMS.IVR.01
1
Critic
al
The IVR system provides a means for tracking all customer-
recorded messages.
Current Base
Interactive Voice Response
OMS.IVR.012 Critical The IVR system has the ability to create a record of a trouble call that includes at a minimum: customer name and address, the type of trouble, the time the trouble is reported, the transformer and feeder number that feeds the customer and
customer comments.
Current Base
Interactive Voice Respons
e
OMS.IVR.013 Critical The IVR system has the ability to determine if a calling customer is associated with an existing outage and to display the status of the outage.
Current Base
Interactive Voice Response
OMS.IVR.014 Critical The IVR system has the ability to recognize calls from priority customers as defined by utility. Current Base
Interactive Voice Respons
e
OMS.IVR.015 Critical The IVR system has the ability to call back customers who called in using a touchtone telephone, in order to verify restoration of power and accept input from the customer
indicating whether power is on or off.
Current Base
Interactive Voice Response
OMS.IVR.016 Critical The IVR system has the ability of creating a call list of customers to notify them of any planned service interruptions.
Current Base
Interactive Voice Respons
e
OMS.IVR.017 Critical The IVR system has a web-based interface available to the user for monitoring and administration of the whole system. Current Base
Interactive Voice Response
OMS.IVR.018 Critical The IVR system supports multiple applications (inbound/outbound) to be run on separate lines simultaneously without having to dedicate circuits to either inbound or outbound.
Current Base
Interactive Voice Respons
e
OMS.IVR.019 Critical The IVR system has a user-friendly “flexible rules engine” to update/customize configurations for IVR options applications.
Current Base
Interactive Voice Response
OMS.IVR.020 Critical The IVR system has a fault tolerance features/redundancy. Current Base
Interactive Voice Respons
e
OMS.IVR.021 Critical Support for open standards, such as CCXML, VoiceXML, W3C, XML, H.323, etc.
Interactive Voice Response
OMS.IVR.022 Critical Multichannel Support: Email Current Base
Interactive Voice Respons
e
OMS.IVR.023 Critical Multichannel Support: SMS-Texting Current Base
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
18
Interacti
ve Voice Response
OMS.IVR.02
4
Critic
al
Provide customizable reports for analysis of calls using
metadata.
Current Base
Interactive Voice Response
OMS.IVR.026 Critical Provide online monitoring dashboards, Current Base
Interacti
ve Voice Response
OMS.IVR.02
7
Critic
al
Provide call volumes statistics: by transaction, by time of
day, and by successful completion.
Current Base
Interactive Voice Response
OMS.IVR.028 Critical Producing special reports in the event of outages caused by massive storm/hurricane (e.g. to track dropped calls, abandoned calls, average call time, number of people that "hit 0" - talks to a dispatcher, success rate, etc.)
Current Base
Interacti
ve Voice Response
OMS.IVR.02
9
Critic
al
Interface using Session Initiation Protocol (SIP) - Aura
Session Manager version 6.2 or later.
Partially
Comply
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
C23184285 – OMS Cost
Milsoft C23184285, Quote #51199
One-
Time Monthly Annual
Milsoft Communications (IVR) $2,800 $33,600
IVR Hosted
IVR Hosted Monthly Subscription $2,800 $33,600
Outage Management $5,395 $64,743
OMS - Subscription with Test System $2,750 $33,000
FieldSyte Monthly $1,250 $15,000
Milsoft Analytics $834 $10,008
Milsoft Outage alerts subscription $325 $3,900
Milsoft Personnel Subscription $236 $2,835
One-time costs $62,500
Integration Services $12,000
Database Conversion $27,500
Initial OMS Setup & Training $15,000
Training Follow up $8,000
TextPower $9,447 $859 $10,308
Configuration $7,000
Subscription $859 $10,308
Setup charges $2,447
Total Costs $71,947 $9,054 $108,651
DocuSign Envelope ID: F76E1D1A-23D2-44DB-B7A8-1CED9D74E1D9
Certificate Of Completion
Envelope Id: F76E1D1A23D244DBB7A81CED9D74E1D9 Status: Completed
Subject: Please DocuSign: C23184285 Milsoft Contract final.pdf
Source Envelope:
Document Pages: 31 Signatures: 1 Envelope Originator:
Certificate Pages: 2 Initials: 0 Annmarie Romero
AutoNav: Enabled
EnvelopeId Stamping: Enabled
Time Zone: (UTC-08:00) Pacific Time (US & Canada)
250 Hamilton Ave
Palo Alto , CA 94301
annmarie.romero@cityofpaloalto.org
IP Address: 199.33.32.254
Record Tracking
Status: Original
8/25/2022 11:14:59 AM
Holder: Annmarie Romero
annmarie.romero@cityofpaloalto.org
Location: DocuSign
Security Appliance Status: Connected Pool: StateLocal
Storage Appliance Status: Connected Pool: City of Palo Alto Location: DocuSign
Signer Events Signature Timestamp
Adam Turner
adam.turner@milsoft.com
CEO of Business Operations
Milsoft Utility Solutions, Inc.
Security Level: Email, Account Authentication
(None)
Signature Adoption: Drawn on Device
Using IP Address: 141.126.92.160
Sent: 8/25/2022 11:17:35 AM
Viewed: 8/25/2022 12:49:32 PM
Signed: 8/25/2022 3:04:16 PM
Electronic Record and Signature Disclosure:
Not Offered via DocuSign
In Person Signer Events Signature Timestamp
Editor Delivery Events Status Timestamp
Agent Delivery Events Status Timestamp
Intermediary Delivery Events Status Timestamp
Certified Delivery Events Status Timestamp
Carbon Copy Events Status Timestamp
Tabatha Boatwright
Tabatha.Boatwright@CityofPaloAlto.org
Utilities Administrative Assistant
City of Palo Alto
Security Level: Email, Account Authentication
(None)
Sent: 8/25/2022 3:04:17 PM
Viewed: 8/25/2022 3:13:12 PM
Electronic Record and Signature Disclosure:
Not Offered via DocuSign
Anna Vuong
anna.vuong@cityofpaloalto.org
Sr. Business Analyst - Utilities
City of Palo Alto Utilities
Security Level: Email, Account Authentication
(None)
Sent: 8/25/2022 3:04:18 PM
Electronic Record and Signature Disclosure:
Not Offered via DocuSign
Witness Events Signature Timestamp
Notary Events Signature Timestamp
Envelope Summary Events Status Timestamps
Envelope Sent Hashed/Encrypted 8/25/2022 11:17:35 AM
Certified Delivered Security Checked 8/25/2022 12:49:32 PM
Signing Complete Security Checked 8/25/2022 3:04:16 PM
Completed Security Checked 8/25/2022 3:04:18 PM
Payment Events Status Timestamps