HomeMy WebLinkAbout20. Telecom Board Agenda Packet - November 8, 2023 - Special Session
BOARD
MEMBERS
Andrew
Van Fleet
Board Chair
Theodore
Batemon
Ritch
Kurtenbach
Mike
Young
Amy
Wienands
City Council
Liaison:
Rob
Nichols
November 8, 2023
City Clerk’s Office
11:30 a.m.
1. Roll call.
2. Approval of the agenda, as presented.
3. Motion approving appointment of Erin Langenberg to the Strategic
Communications Manager position, effective December 18, 2023, subject to
the approval of an employment agreement.
4. Motion approving appointment of Julie Eastman to the Accounting Manager
position, effective November 20, 2023, subject to the approval of an
employment agreement.
5. Resolution approving a request for proposal for the FY2024 Billing System,
Operational Support System, and Flow-Through Provisioning, Contract No.
1097.
6. General comments from staff, consultants, and board members.
7. Adjourn.
Kelley Felchle
Board Secretary
WATERLOO
Telecommunications Utility Board of Trustees
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
REQUEST FOR PROPOSAL
F.Y. 2024 BILLING SYSTEM, OPERATIONAL SUPPORT SYSTEM, FLOW-THROUGH
PROVISIONING
Waterloo Fiber
City of Waterloo, IA
November 2023
CONTRACT NO. 1097
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
Table of Contents
1. INTRODUCTION
2. ADMINISTRATIVE INFORMATION
3. FORM AND CONTENT OF PROPOSALS
4. SCOPE OF WORK
5. SPECIFICATIONS
6. EVALUATION AND SELECTION
7. CONTRACTUAL TERMS AND CONDITIONS
8. FORM OF BID BOND
9. FORM OF PERFORMANCE, PAYMENT, AND MAINTENANCE BOND
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 1 INTRODUCTION
1.1 Purpose
The Municipal Telecommunications Utility of the City of Waterloo d/b/a Waterloo Fiber (WF) is
soliciting proposals for the purchase of Operating Support System (OSS) / Billing Support System
(BSS) software and seeks sealed proposals for a billing, operational support, and flow-through
provisioning system. This request is detailed in writing in Attachment A. The Proposed Solution
must integrate the City of Waterloo Water Work’s current billing system, Cogsdale, into the
proposed OSS / BSS system.
The Owner has begun implementation of its Broadband Business Plan, which provides for
construction of a carrier-class passive optical network (PON) passing approximately 26,367
commercial and residential premises. The Owner is seeking a turnkey go-live ready system including
all required software, installation materials, and professional services to implement the Operating
and Billing systems described in this RFP. The Owner reserves the right to reject any or all proposals,
re-advertise for new proposals, and to waive informalities in the proposals submitted. Proposals
may be held by Waterloo Fiber, for a period not to exceed thirty (30) days from the day of the
opening of proposals for the purpose of evaluating the proposals, prior to awarding the contract.
The Owner desires to establish, where possible, a direct relationship with all equipment and
software manufacturers in the Proposed Solution. Therefore, any components in the Proposed
Solution that are available for direct purchase by the Owner from the manufacturer must be quoted
to allow for direct purchase. All manufacturer lead times for equipment must be included in the
Proposed Solution.
Scope of work service requirements are more particularly identified in Section 4 of this RFP.
Specifications and compatibility requirements are more particularly identified in Section 5 of this
RFP.
The City of Waterloo, IA has contracted the services of Magellan to manage the selection,
procurement, and integration of their new network. All references to “WF”, “Waterloo Fiber”, and
“Waterloo Fiber personnel” include City and Magellan staff by extension. The Bidder is solely
responsible for ensuring all equipment, software, and services required to fully commission the
network as described by this RFP and its supporting documents are included in their Proposed
Solution.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
1.2 Definitions
The City of Waterloo, IA has made every effort to use industry standard terminology throughout
this RFP and to provide clear definitions unique to the context. If the prospective Bidder has
questions on terminology or context, it is the responsibility of the Bidder to request clarification in
writing. Likewise, the Bidder should define terms that may be unclear in their proposal. The
following definitions and clarifications are provided:
Term Definition
CSP (Communication Service Provider) A commercial telecommunications provider
offering some combination of information,
entertainment, and/or application services to retail
and/or wholesale customers over a network by
leveraging the infrastructure as a rich, functional
platform.
MTU (Municipal Telecommunications
Utility)
The new retail CSP created by the City of Waterloo,
IA.
WF (Waterloo Fiber) The marketing brand of the broadband system
operated by the MTU (MTU dba/WF).
RFP (Request for Proposal) Consists of this requirements document with all its
exhibits and attachments.
Proposed Solution Defined as all materials, software, licensing, and
labor necessary to implement the turn-key system
described and required by this RFP.
Shall Designates a requirement of the Proposed
Solution.
Owner The Waterloo MTU d/b/a WF to include their
designated project managers, staff, and
consultants.
Bidder A Bidder submitting a Proposed Solution
purported to satisfy the requirements of the RFP.
Contract The contract(s) entered into with the successful
Bidder(s) as described in Section 7.1.
Qualified Bidder A Bidder that has the capability in all material
respects to perform the scope of work and
specifications of the Contract. In determining
whether a Bidder is a Qualified Bidder, the Owner
may consider various factors including, but not
limited to, the Bidder’s competence and
qualifications to provide the goods or services
requested, the Bidder’s integrity and reliability, the
past performance of the Bidder and the best
interest of the Owner.
Qualified Proposal A Proposal that complies with the material
provisions of this RFP.
CPE (Customer Premise Equipment) Provider edge equipment located on a subscriber
premise to deliver CSP services.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
ISP (Inside Plant infrastructure) All racks, cable management, power, cooling,
electronics, and installation components located
inside an environmentally controlled structure.
OSP (Outside Plant Infrastructure) Fiber optic cable, vaults, cabinets, pedestals, splice
enclosures, and installation components located
underground and/or aerially on poles.
Project Completion Defined as the time when the Bidder has:
delivered, installed, configured, and
successfully tested the proposed network, and
provided all required documentation and
training, and
received final acceptance from the Owner
General Terms and Conditions The General Terms and Conditions for Services
Contracts.
1.3 Overview of the RFP Process
This RFP is designed to provide Bidders with the information necessary to develop a Proposed
Solution. The RFP process is for the Owner’s benefit and is intended to provide the Owner with
competitive information to assist in the selection process. It is not intended to be comprehensive.
Each Bidder is solely responsible for determining all factors affecting the design, configuration, and
implementation of a comprehensive proposal that will accomplish the technical and business goals
described by this RFP.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
1.4 RFP Schedule
The Owner will make every effort to adhere to the following schedule leading to the award of a
contract; however, this schedule is subject to change. Bidders will be notified of significant schedule
changes:
Project Calendar Anticipated Event Dates:
Issuance of the RFP November 9, 2023
Non-Mandatory Pre-Bid Meeting November 15, 2023
Final Submission of Bidders’ Questions November 17, 2023
Response to Bidders’ Questions November 28, 2023
Proposals Due December 5, 2023
Utility consideration of proposals & approval of award of contract December 20, 2023
Contract Signed December 27, 2023
Commence Installation January 8, 2024
Complete Installation No Later Than August 1, 2024
1.5 Proposal Submission
On behalf of the Municipal Telecommunications Utility of the City of Waterloo, notice is hereby
given that sealed proposals will be received by the City Clerk of the City of Waterloo, Iowa, at her
office in the City Hall of the said City on the 5th day of December, 2023 before 1:00 p.m. for the
construction of the F.Y. 2024 BILLING SYSTEM, OPERATIONAL SUPPORT SYSTEM, FLOW-THROUGH
PROVISIONING, Contract No. 1097. Proposals received after the deadline for submission of bids as
stated herein shall not be considered and shall be returned to the late bidder unopened.
1.6 Project Acceptance
The Bidder must demonstrate to the Owner full and complete compliance with all requirements in
the RFP and successfully complete an Acceptance Test Plan (ATP) to validate the operational
performance of the Proposed Solution to receive final acceptance for Project Completion. The
Owner reserves the right to withhold final payment until the Bidder meets all requirements in this
RFP to the Owner’s satisfaction.
The Bidder shall provide as part of their proposal a list of acceptance tests in addition to those in
Section 4 that they believe best demonstrate the operation and performance of the Proposed
Solution as described in this RFP. The specific ATP tests and procedures to perform them will be
developed jointly by the Owner and Bidder during implementation of the Proposed Solution.
After completion of the network implementation, the Owner will review the scope of work in
Section 4 to determine if the Proposed Solution as installed satisfies the RFP requirements. The
Owner will document in writing any deficiencies discovered, and upon the Bidder’s completion or
correction of these items, the Owner shall authorize final payment to the Bidder.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
1.7 Deployment Strategy and Schedule
The Bidder shall work with the Owner to ensure that the necessary site preparations are made to
support the January 8, 2024 Commencement Installation Date and that the necessary equipment
and services are shipped/delivered in a timely manner. The Bidder shall provide in their Proposal
an estimated timeline relative to the contract award date with projected milestones including
equipment delivery, high level design, equipment installation, acceptance testing, and Project
Completion.
If applicable, no equipment shall be shipped or invoiced without prior written approval from the
Owner.
1.8 Project Contract Requirements
A contract will be awarded to the most qualified, responsible bidder.
The Owner reserves the right to reject any or all proposals, re-advertise for new proposals, and to
waive informalities in the proposals submitted.
Proposals may be held by the Owner for a period not to exceed thirty (30) days from the day of the
opening of proposals for the purpose of reviewing the proposals and investigating the responsibility
of bidders, prior to awarding the contract.
The Owner desires to establish, where possible, a direct relationship with all software
manufacturers in the Proposed Solution. Therefore, any components in the Proposed Solution that
are available for direct purchase by the Owner from the manufacturer must be quoted to allow for
direct purchase.
1.9 Bid Bond Requirements
All bids must be accompanied in a separate envelope by a certified or cashier's check drawn on an
Iowa bank, or a bank chartered under the laws of the United States, a certified share draft drawn
on a credit union in Iowa or chartered under the laws of the United States, or bid bond, (on the form
furnished by the Owner) payable to the Municipal Telecommunications Utility (MTU) in the sum of
not less than five percent (5%) of the bid submitted, which certified check, certified share draft or
bid bond will be held as security that the Bidder will enter into a Contract for the construction of
the work and will furnish the required bonds, and in case the successful Bidder shall fail or refuse
to enter into the Contract and furnish the required bonds, his bid security may be retained by said
Owner as agreed upon liquidated damages. If bid bond is used, it must be signed by both the Bidder
and the surety or surety's agent. Signature of surety's agent must be supported by accompanying
Power of Attorney.
1.10 Performance Bond Requirements
The successful Bidder will be required to furnish a “Performance Bond” and a “Payment Bond”
within ten (10) days after forms are presented to Bidder in an amount equal to one hundred
percent (100%) of the contract price, said bond to be issued by a responsible surety approved by
the Board of Trustees and shall guarantee the faithful performance of the contract and the terms
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
and conditions therein contained, and shall guarantee the prompt payment of all materials and
labor and protect and save harmless the Owner from claims of any kind caused by the operations
of the Bidder.
1.11 RFP Attachments and Exhibits
The Proposed Solution should be developed to incorporate the network architecture, subscriber
counts, service integrations, and traffic capacities described and required by this RFP. A list of
Attachments accompanying this RFP to assist the Bidder include:
Attachment A – BSS OSS RFP Questions
Attachment B – BSS OSS RFP Pricing
Some sections of this RFP require a description of the Proposed Solution and a point-by-point
response to the specifications. The Bidder shall describe their Proposed Solution for each section
and identify its level of compliance with each specification with a brief explanation if applicable in
Attachment A – BSS OSS RFP Questions. Compliance, exceptions, and clarifications to the RFP shall
all be clearly identified and summarized. Compliance shall be indicated with a score between 0%
and 100% compliant. The terms “Understood” and “Read and Understood” are unacceptable.
The point-by-point response provided by the Bidder shall be for the system as proposed and shall
reflect the costs included in Attachment B – BSS OSS RFP Pricing.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 2 ADMINISTRATIVE INFORMATION
2.1 Restriction on Communication
From the issue date of this RFP until a Notice of Intent to Award the Contract is issued, Bidders may
contact only the Issuing Officer, Michael Regan (mregan@entrustsol.com). The Issuing Officer will
respond only to written questions regarding the procurement process. Questions related to the
interpretation of this RFP must be submitted as provided in Section 2. Oral questions related to the
interpretation of this RFP will not be accepted. Bidders may be disqualified if they contact any City of
Waterloo employee or official other than the Issuing Officer about the RFP.
This section shall not be construed as restricting communications related to the administration of any
contract currently in effect between a Bidder and the City of Waterloo.
2.2 Downloading the RFP from the Internet
The RFP document and any addenda to the RFP will be posted at the Waterloo municipal government
bids website. The Bidder is advised to check the website periodically for Addenda to this RFP, particularly
if the Bidder downloaded the RFP from the Internet as the Bidder may not automatically receive addenda.
It is the Bidder’s sole responsibility to check daily for addenda to posted documents.
2.3 Procurement Timetable
The dates provided in the procurement schedule within this RFP are provided for informational and
planning purposes. The Owner reserves the right to change the dates. If the Owner changes any of the
deadlines for Bidder submissions, the Owner will issue an addendum to the RFP.
2.4 Non-Mandatory Pre-Proposal Conference
On behalf of the Municipal Telecommunications Utility of the City of Waterloo, notice is hereby given that
sealed proposals will be received by the City Clerk of the City of Waterloo, Iowa, at her office in the City
Hall of the said City on the 5th day of December, 2023 before 1:00 p.m. for the F.Y. 2024 BILLING SYSTEM,
OPERATIONAL SUPPORT SYSTEM, FLOW-THROUGH PROVISIONING, Contract No. 1097. Proposals
received after the deadline for submission of bids as stated herein shall not be considered and shall be
returned to the late bidder unopened. A Non-Mandatory Pre-Bid Meeting will be held at 10:00 am local
time on November 8, 2023 join via Microsoft Teams video conference, Meeting ID: 258 033 608 081 ,
Passcode: iumJAw, https://www.microsoft.com/microsoft-teams/join-a-meeting
Inquiries Should Be Directed to: Michael Regan, via email only at: mregan@entrustsol.com. All questions
must be submitted via e-mail before 5:00 pm, Friday, November 17, 2023. RFP documents may be
examined at the City Clerk’s Office. Electronic copies of RFP documents in PDF format are available for
download on the the Waterloo municipal government bids website.
It shall be the responsibility of the Bidder to monitor the City’s website and above noted e-procurement
websites for published addenda. All fully executed addendum must be returned to Owner with proposal
submission. Owner will not accept faxed or emailed addenda.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
In Compliance with this RFP and to All the Conditions Imposed Therein and Hereby Incorporated by
Reference, the Undersigned Offers, And Agrees to Furnish Services requested in the solicitation.
The pre-bid conference may be recorded. Questions asked at the conference that cannot be adequately
answered during the conference may be deferred. A copy of the questions and answers will be sent to
Bidders who submit a letter of intent to propose and will be posted in the form of an addendum at: the
Waterloo municipal government bids website.
2.5 Questions, Requests for Clarification, and Suggested Changes
Bidders are invited to submit written questions and requests for clarifications regarding the RFP. Bidders
may also submit suggestions for changes to the specifications of this RFP. The questions, requests for
clarifications, or suggestions must be in writing and received by Michael Regan, Issuing Officer, on or
before the date and time listed within the RFP. Oral questions will not be permitted. If the questions,
requests for clarifications, or suggestions pertain to a specific section of the RFP, Bidder shall reference
the page and section number(s). The Owner will send written responses to questions, requests for
clarifications, or suggestions received from Bidders before the date listed within the RFP. Owner’s written
responses will become an addendum to the RFP. If the Owner decides to adopt a suggestion that modifies
the RFP, the Owner will issue an addendum to the RFP.
The Owner assumes no responsibility for oral representations made by its officers or employees unless
such representations are confirmed in writing and incorporated into the RFP through an addendum.
2.6 Amendment to the RFP
The Owner reserves the right to amend the RFP at any time using an addendum. The Bidder shall
acknowledge receipt of all addenda in its Proposal.
2.7 Amendment and Withdrawal of Proposal
The Bidder may amend or withdraw and resubmit its Proposal at any time before the Proposals are due.
The amendment must be in writing, signed by the Bidder and received by the time set for the receipt of
Proposals. Electronic mail and faxed amendments will not be accepted. Bidders must notify Michael
Regan, Issuing Officer, in writing prior to the due date for Proposals if they wish to completely withdraw
their Proposals.
2.8 Proposal Opening
The Owner will open Proposals after the deadline for submission of Proposals has passed. The Proposals
will remain confidential until the Owner has issued a Notice of Intent to Award a Contract. However, the
names of Bidders who submitted timely Proposals will be publicly available after the Proposal opening.
The announcement of Bidders who timely submitted Proposals does not mean that an individual Proposal
has been deemed technically compliant or accepted for evaluation.
Proposals will be considered by the Board of Trustees of the Municipal Telecommunications Utility at its
meeting at 4:00 pm on December 20, 2023, in the Harold E. Getty Council Chambers in City Hall, 715
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
Mulberry Street, Waterloo, Iowa. The Board may approve awarding a Contract at said meeting, or at such
other time and place as shall then be announced.
2.9 Costs of Preparing the Proposal
The costs of preparation and delivery of the Proposal are solely the responsibility of the Bidder.
2.10 No Commitment to Contract
The Owner reserves the right to reject any or all Proposals received in response to this RFP at any time
prior to the execution of the Contract. Issuance of this RFP in no way constitutes a commitment by the
Owner to award a contract.
2.11 Rejection of Proposals
The Owner may reject outright and not evaluate a Proposal for reasons including, without limitation:
2.11.1 The Bidder fails to deliver a complete Proposal.
2.11.2 The Bidder acknowledges that a mandatory specification of the RFP cannot be met.
2.11.3 The Bidder’s Proposal changes a material specification of the RFP or the Proposal is not
compliant with the mandatory specifications of the RFP.
2.11.4 The Bidder’s Proposal limits the rights of the Owner.
2.11.5 The Bidder fails to include information necessary to substantiate that it will be able to meet
a specification of the RFP as provided in Section 5 of this RFP.
2.11.6 The Bidder fails to timely respond to the Owner’s request for information, documents, or
references.
2.11.7 The Bidder presents the information requested by this RFP in a format inconsistent with
the instructions of the RFP or otherwise fails to comply with the specifications of this RFP.
2.11.8 The Bidder initiates unauthorized contact regarding the RFP with a City employee or official
other than, Michael Regan, Issuing Officer.
2.11.9 The Bidder provides misleading or inaccurate responses.
2.11.10 The Bidder’s Proposal is materially unbalanced.
2.11.11 There is insufficient evidence (including evidence submitted by the Bidder and evidence
obtained by the Owner from other sources) to satisfy the Owner that the Bidder is a
Qualified Bidder.
2.12 Reference Checks
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
The Owner reserves the right to contact any reference to assist in the evaluation of the Proposal, to verify
information contained in the Proposal and to discuss the Bidder’s qualifications and the qualifications of
any subcontractor identified in the Proposal.
2.13 Information from Other Sources
The Owner reserves the right to obtain and consider information from other sources concerning a Bidder,
such as the Bidder’s capability and performance under other contracts, the qualifications of any
subcontractor identified in the Proposal, the Bidder’s financial stability, past or pending litigation, and
other publicly available information.
2.14 Verification of Proposal Contents
The content of a Proposal submitted by a Bidder is subject to verification. If the Owner determines in its
sole discretion that the content is in any way misleading or inaccurate, the Owner may reject the Proposal.
2.15 Proposal Clarification Process
The Owner reserves the right to contact a Bidder after the submission of Proposals for the purpose of
clarifying a Proposal. This contact may include written questions, interviews, site visits, a review of past
performance if the Bidder has provided goods and/or services to the City of Waterloo or any other political
subdivision wherever located, or requests for corrective pages in the Bidder’s Proposal. The Owner will
not consider information received from or through Bidder if the information materially alters the content
of the Proposal or the type of goods and/or services the Bidder is offering to the Owner. An individual
authorized to legally bind the Bidder shall sign responses to any request for clarification. Responses shall
be submitted to the Owner within the time specified in the Owner’s request. Failure to comply with
requests for additional information may result in rejection of the Proposal.
2.16 Disposition of Proposals
All Proposals become the property of the Owner and shall not be returned to the Bidder. Once the Owner
issues a Notice of Intent to Award the Contract, the contents of all Proposals will be public records
available for inspection by interested parties.
2.17 Copyright Permission
By submitting a Proposal, the Bidder agrees that the Owner may copy the Proposal for purposes of
facilitating the evaluation of the Proposal or to respond to requests for public records. By submitting a
Proposal, the Bidder consents to such copying and warrants that such copying will not violate the rights
of any third party. The Owner shall have the right to use ideas or adaptations of ideas that are presented
in Proposals.
2.18 Release of Claims
By submitting a Proposal, the Bidder agrees that it will not bring any claim or cause of action against the
Owner based on any misunderstanding concerning the information provided in the RFP or concerning
the Owner ’s failure, negligent or otherwise, to provide the Bidder with pertinent information in this RFP.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
2.19 Evaluation of Proposals Submitted
Proposals that are timely submitted and are not rejected will be reviewed and evaluated in accordance
with Section 6 of the RFP. The Owner will not necessarily award a Contract resulting from this RFP to the
Bidder offering the lowest cost. Instead, the Owner will award the Contract(s) to the Qualified Bidder(s)
whose Qualified Proposal the Owner believes will provide the best value to the Owner.
2.20 Award Notice and Acceptance Period
Notice of Intent to Award the Contract(s) will be sent to all Bidders submitting a timely Proposal and may
be posted at the website listed within the RFP. Negotiation and execution of the Contract(s) shall be
completed no later than thirty (30) days from the date of the Notice of Intent to Award or such other time
as designated by the Owner. The Bidder’s form of contract may be utilized and the MTU reserves the
right to negotiate the terms of the agreement. If the successful Bidder fails to negotiate and deliver an
executed Contract by that date, the Owner, in its sole discretion, may cancel the award and award the
Contract to the remaining Bidder the Owner believes will provide the best value to the Owner.
2.21 No Contract Rights until Execution
No Bidder shall acquire any legal or equitable rights regarding the Contract unless and until the Contract
has been fully executed by the successful Bidder and the Owner.
2.22 Choice of Law and Forum
This RFP and the Contract shall be governed by the laws of the State of Iowa. Changes in applicable laws
and rules may affect the award process or the Contract. Bidders are responsible for ascertaining pertinent
legal requirements and restrictions. Any and all litigation or actions commenced in connection with this
RFP shall be brought in the appropriate Iowa forum.
2.23 No Minimum Guaranteed
The Owner does not guarantee any minimum level of purchases under the Contract.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 3 FORM AND CONTENT OF PROPOSALS
3.1 Explanation to Bidders
Any explanation desired by a bidder regarding the meaning or interpretation of the RFP must be
requested in writing on or before November 17, 2023. Any interpretation made will be in the form
of an addendum to the RFP and will be furnished to all prospective bidders. Its receipt by the bidder
must be acknowledged in the space provided on the Proposal Form. Oral explanations or
instructions given before the award of the Contract will not be binding.
3.2 Submission of Proposals
The Bidder shall submit an electronic copy of their proposal that includes:
• an executive summary of the Proposed Solution
• a diagram of the Proposed Solution network showing the components and
connectivity
• Component diagram of the proposed equipment configuration
• a completed copy of Attachment A – BSS OSS RFP Questions
• a completed copy of Attachment B – BSS OSS RFP Pricing
• any other pertinent documentation such as data sheets, diagrams, and training
catalogs
• references and contact information
Digital copies of the proposal shall be submitted through a file drop service with notification to the
Owner via e-mail (eric.lage@waterloofiber.com) and include the most appropriate format of each
item including MS Word, MS Excel, MS Visio, and/or Adobe Acrobat formats. Bidders submitting
incomplete or materially deficient proposals may be disqualified.
3.3 References and Contact Information
The Owner requires sufficient corporate, financial, and reference information to adequately assess
the qualifications of the Bidder to sell, install, and support the Proposed Solution. The reference
information will be used by the Owner to differentiate between Bidders with similar Proposed
Solutions, and shall be provided in a separate document including the following information:
Corporate Information
The Bidder shall provide an overview of their corporate structure. The overview should address the
following specific items:
Name, address, and contact information of the Company and representative
Company History and Formation
Ownership (Public or Privately Held)
Number of Employees
Organizational chart of the management and implementation teams for the project
A detailed history of all mergers or acquisitions (if applicable).
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
Bidder’s financial condition and supporting documentation (i.e. audited annual reports, etc.)
Implementation Experience
WF will operate in a competitive marketplace with experienced incumbent CSP’s, therefore the
Bidder’s experience implementing and supporting CSP networks will be crucial to the successful
launch and ongoing operation of WF. To this end, the Bidder shall provide a brief summary of their
experience implementing and supporting carrier-class networks for CSP customers. The summary
should address the following specific experience:
Implementations of municipal and/or commercial CSP networks
Implementations of similar network implementation
List of certifications relative to the Proposed Solution held by the implementation team
List of partner certifications relative to the Proposed Solution held by the Bidder
Bidders with specialization in the proposed software manufacturers’ service provider architecture
are preferred. Copies of formal manufacturer-conferred certifications including the certification
name, description, requirements, and date of award/renewal should be provided in the Bidder’s
response.
The Bidder shall submit a list of three (3) CSP references who have deployed similar
implementations within the last five (5) years. The reference information shall include the company
name with dates of implementation along with the name, address, and phone number of the
individual(s) that may be contacted at the company. Bidder shall omit all homogenous enterprise
IT deployments (i.e., private corporate-centric networks) from their response and references.
3.4 Termination, Litigation, Debarment
3.4.1 Termination, Litigation, Debarment the Bidder must provide the following information for
the past five (5) years
3.4.2 Has the Bidder had a Contract for goods and/or services terminated for any reason? If so,
provide full details regarding the termination.
3.4.3 Describe any damages or penalties assessed against or dispute resolution settlements
entered into by Bidder under any existing or past Contracts for goods and/or services.
Provide full details regarding the circumstances, including dollar amount of damages,
penalties and settlement payments.
3.4.4 Describe any order, judgment or decree of any Federal or State authority barring,
suspending or otherwise limiting the right of the Bidder to engage in any business, practice
or activity.
3.4.5 A list and summary of all litigation or threatened litigation, administrative or regulatory
proceedings, or similar matters to which the Bidder or its officers have been a party.
3.4.6 Any irregularities discovered in any of the accounts maintained by the Bidder on behalf of
others. Describe the circumstances and disposition of the irregularities.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
3.4.7 Failure to disclose these matters may result in rejection of the Proposal or termination of
any subsequent Contract. The above disclosures are a continuing requirement of the
Bidder. Bidder shall provide written notification to the Owner of any such matter
commencing or occurring after submission of a Proposal, and with respect to the successful
Bidder, following execution of the Contract.
3.5 Bidder shall indicate in its Proposal that it agrees to submit monthly invoices and accept
payment in the form of check or ACH.
3.6 Acceptance of Terms and Conditions
By submitting a Proposal, Bidder acknowledges its acceptance of the terms and conditions of the
RFP and the General Terms and Conditions without change except as otherwise expressly stated in
its Proposal. If the Bidder takes exception to a provision, it must identify it by page and section
number, state the reason for the exception, and set forth in its Proposal the specific RFP or General
Terms and Conditions language it proposes to include in place of the provision. If Bidder's
exceptions or responses materially alter the RFP, or if the Bidder submits its own terms and
conditions or otherwise fails to follow the process described herein, the Owner may reject the
Proposal, in its sole discretion.
3.7 Firm Proposal Terms
The Bidder shall guarantee in writing the goods and/or services offered in the Proposal are currently
available and that all Proposal terms, including price, will remain firm for the number days indicated
on the RFP cover sheet 90 days following the deadline for submitting Proposals.
3.8 Proposal Shall Include Only Generally Available Equipment and Software
a) All Bidder supplied programs and software must be field operational before the date the
proposal is submitted.
b) Demonstrations must utilize the proposed equipment, programs or software precisely as
proposed.
c) Unless otherwise specified in the specifications, all items on which a Bidder submits a proposal
must be new, of the latest model or manufacture, and be at least equal in quality to that
specified in the bidding documents.
3.9 Bidder Required to Identify Patented Items, and Copyrighted Text, Information, Data, or
Software Included in Its Proposal; Bidder Required to Include with Its Proposal any Licenses that
Owner Will be Expected to Execute.
Bidders shall identify any patented equipment, processes, materials, or hardware, or any
copyrighted text, information, data, or software that it proposes to supply as part of the goods or
services it is required to provide under the RFP. Every Bidder shall likewise identify the licensing
agent for the patented or copyrighted items, and shall provide with its proposal a copy of any
licensing or user agreement that the Owner will be expected to execute for the use of patented
equipment, processes, materials, or hardware, or copyrighted text, information, data, or software
included in a proposal, as well as the anticipated cost to the Owner, if any, for use under a license
or agreement. The Bidder to whom the Contract is awarded warrants that the intellectual property
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
rights of third parties (e.g. copyright, trademark, or patent) will not be violated by the Bidder's or
the Owner's use of any equipment, process or service provided in response to the RFP.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 4 SCOPE OF WORK
The Municipal Telecommunications Utility of the City of Waterloo d/b/a Waterloo Fiber (WF) is soliciting
proposals for the purchase of Operating Support System (OSS) / Billing Support System (BSS) software
and seeks sealed proposals for a billing, operational support, and flow-through provisioning system.
This request is detailed in writing in Attachment A.
The Bidder shall indicate its compliance with each of the requirements in Attachment A – BSS OSS RFP
Questions. Pricing to perform this SoW shall be entered into Attachment B – BSS OSS RFP Pricing. All
planning and tasks required in Attachment A – BSS OSS RFP Questions shall begin upon award of a
Contract to the Bidder. Bidders shall submit a copy of Attachment A and Attachment B as part of their
Proposal. A requirement for this proposal will be a solution to integrate the City of Waterloo Water
Work’s current billing system, Cogsdale, into the proposed OSS / BSS system.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 5 SPECIFICATIONS
5.1 Overview
The Proposed Solution must include all the equipment, software, and services necessary for the
Bidder to provide to the Owner a turnkey, tested, operational-ready network complete with
documentation and staff training. The successful Bidder shall provide the goods and services to
the Owner in accordance with the specifications as provided in this RFP. Proposals must identify
any deviations from the specifications of this RFP or specifications the Bidder cannot satisfy. If
the Bidder deviates from or cannot satisfy the specification(s) of this RFP, the Owner may reject
the Proposal.
The Bidder shall be solely responsible for validating the Proposed Solution is sufficiently
configured with the components and capacity required to serve the subscriber growth and service
mix described in this RFP. The Bidder shall be responsible for engineering all link capacities and
hardware configurations to ensure acceptable service performance and subscriber experience on
the WF network.
5.2 Warranty, Maintenance, and Technical Support
For all critical components, WF shall require 24x7x365 next business day (NBD) hardware
maintenance, access to technical support center services, and software updates for patches and
feature releases. Maintenance and support services shall be quoted for a 3-year term.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 6 EVALUATION AND SELECTION
6.1 Introduction
This section describes the evaluation process that will be used to determine which Proposal(s)
provides the greatest benefit to the Owner. The Owner will not necessarily award the Contract
to the Bidder offering the lowest cost to the Owner. Instead, the Owner will award to the Bidder
whose Qualified Proposal the Owner believes will provide the best value to the Owner.
6.2 Evaluation Committee
The Owner will conduct a comprehensive, fair, and impartial evaluation of Proposals received in
response to this RFP. The Owner will use an evaluation committee to review and evaluate the
Technical Proposals. The evaluation committee will recommend an award based on the results
of their evaluation to the Owner or to such other person or entity who must approve the
recommendation.
6.3 Proposal Evaluation and Scoring
The evaluation of the proposals and any requested oral presentations will be based on the
following criteria:
1. Overall Price (lowest cost / proposal cost) 0-30
points
2. Attachment A – BSS OSS RFP Questions Compliance Score
(0% to 100%)
0-30
points
3. Section 1 response thoroughness (-1 point for each unfulfilled
requirement)
0-20
points
4. Section 3 response thoroughness (-1 point for each unfulfilled
requirement)
0-20
points
TOTAL POINTS AWARDED 0-100
points
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SECTION 7 CONTRACT TERMS AND CONDITIONS
7.1 Contract Terms and Conditions
The Contract that the Owner expects to award as a result of this RFP shall comprise all of the
specifications, terms and conditions of the RFP, written clarifications or changes made by the
Owner to the RFP through an addendum to the RFP in accordance with the provisions of the RFP,
the General Terms and Conditions, the offer of the successful Bidder contained in its Proposal,
and any other terms deemed necessary by the Owner. No objection or amendment by a Bidder
to the provisions or terms and conditions of the RFP or the General Terms and Conditions shall
be incorporated into the Contract unless the Owner has explicitly accepted the Bidder’s objection
or amendment in writing.
The Owner reserves the right to either award a Contract(s) without further negotiation with the
successful Bidder or to negotiate Contract terms with the successful Bidder if the best interests
of the Owner would be served.
7.2 Contract Length
The term of the Contract will be for three (3) years. The Owner shall have the sole option to renew
the Contract upon the same or more favorable terms and conditions.
7.3 Insurance
The Contract will require the successful Bidder to maintain insurance coverage(s) in the minimum
amounts set forth below, unless otherwise required by the Owner.
Type of Insurance LIMIT AMOUNT
General Liability (including
contractual liability) written on an occurrence basis
General Aggregate
Products –
Comp/Op Aggregate
Personal injury
Each Occurrence
$2 million
$1 Million
$1 Million
$1 Million
Automobile Liability (including vehicles owned,
hired, and non-owned), including contractual
liability, written on an occurrence basis
Combined single limit $1 Million
Excess Liability, Umbrella Form Each Occurrence
Aggregate
$1 Million
$1 Million
Errors and Omissions Insurance Each Occurrence $1 Million
Property Damage Each Occurrence
Aggregate
$1 Million
$1 Million
Workers Compensation and Employers Liability As Required by Iowa
law
Employers Liability
$500,000
Cyber Liability (including Privacy/Security,
Business Interruption, Cyber Extortion, Financial
Fraud
Each Occurrence
Aggregate
$1 Million
$1 Million
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
Acceptance of the insurance certificates by the Owner shall not act to relieve Bidder of any
obligation under this Contract. It shall be the responsibility of Bidder to keep the respective
insurance policies and coverages current and in force during the life of this Contract. Bidder shall
be responsible for all premiums, deductibles and for any inadequacy, absence or limitation of
coverage, and the Bidder shall have no claim or other recourse against the Owner for any costs
or loss attributable to any of the foregoing, all of which shall be borne solely by the
Bidder. Notwithstanding any other provision of this Contract, Bidder shall be fully responsible
and liable for meeting and fulfilling all of its obligations under this section of the Contract.
Bidder’s insurance shall name Owner as an additional insured on a primary and non-contributory
basis including a waiver of subrogation in favor of Owner.
Bidder shall provide certificates of insurance to Owner prior to contractual work, annually
thereafter, and upon request by Owner.
7.4 Termination and Adjustment
A. If Bidder fails to fulfill its obligations under this Contract, the Owner may terminate this
Contract after giving the Bidder ten days written notice to cure such failure. The ten-day cure
period will begin on the date shown on the written notification from the Owner. If within the
10-day period Bidder fails to cure to the reasonable satisfaction of the Owner, then the Owner
may give notice that it is terminating this Contract and Bidder shall cease all activity associated
with this Contract at such time as the notification is received. The Owner has the right to set off
the cost of procuring another contractor to perform or complete the Scope of Work in the event
Bidder fails to perform the Work satisfactorily.
B. At any time prior to completion of the Work, the Owner may, in its sole discretion, terminate
the Contract by providing the Bidder written notice of its intention to terminate. Unless the
notification provides otherwise, Bidder shall cease all activity associated with this Contract at
the time the notification is received. If the termination is without fault of the Bidder, the Owner
shall pay for Work satisfactorily performed to the date of termination and reimburse Bidder for
reasonable unrecoverable expenses Bidder incurred prior to receiving the notification.
7.5 Indemnification Requirements
For purposes of this section 7.5, the term “Owner” means the City of Waterloo and its elected
and appointed officials, agents, employees, volunteers, and others working on its behalf. To the
fullest extent permitted by law, Bidder agrees to defend, pay on behalf of, indemnify, and hold
harmless the Owner against any and all claims, demands, suits, damages or losses, together
with any and all outlay and expense connected therewith including, but not limited to,
attorneys’ fees and court costs that may be asserted or claimed against, recovered from or
suffered by the Owner by reason of any injury or loss including, but not limited to, personal
injury, bodily injury including death, property damage, including loss of use thereof, and
economic damages that arise out of or are in any way connected or associated with Bidder’s
work or services under this Contract, including that of its officers, agents, employees,
subcontractors and others under the control of Bidder, except to the extent caused by or
resulting from the sole negligence of the Owner.
Bidder’s obligation to indemnify the Owner contained in this Contract is not limited by the
amount or type of damages, compensation or benefits payable under any workers’
compensation acts, disability benefit acts, or other employee benefits acts.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
The Owner shall not be liable or in any way responsible for any injury, damage, liability, claim,
loss or expense incurred by Bidder arising out of or in any way connected or associated with
Bidder’s work or services under this Contract, including that of its officers, agents, employees,
subcontractors and others under control of Bidder, except to the extent caused by or resulting
from the sole negligence of the Owner.
Bidder expressly assumes responsibility for any and all damage caused to Owner property
arising out of or in any way connected or associated with Bidder’s work or services under this
Contract, including its officers, agents, employees, subcontractors and others under the control
of Bidder.
7.6 Ownership of Documents
The Bidder agrees that the Owner is the sole and exclusive owner of all designs, design plans,
images, drawings, models, survey notes, reports, specifications, studies, records and other data
and documents, in whatever form, prepared under this Contract (the "Design Documents"). The
Bidder hereby irrevocably assigns, transfers and conveys to the Owner all right, title and interest
in and to the Design Documents and all intellectual property rights and proprietary rights arising
out of the Design Documents, including copyrights, patents, trademarks, and derivative works
and interests. The Bidder warrants to the Owner that the Design Documents will be free from
any claims or encumbrances of intellectual property or proprietary rights of the Bidder and any
third party, including any employee, agent, contractor, sub-Contractor, subcontractor,
subsidiary or affiliate of Bidder. Upon completion or termination of this Contract, the Bidder
shall immediately turn over to the Owner all Design Documents not previously delivered to the
Owner.
To the extent any of the Bidder’s rights in the Design Documents are not subject to assignment
or transfer, including any moral rights and any rights of attribution and integrity, the Bidder
hereby irrevocably and unconditionally waives such rights, and the enforcement of them, and
agrees not to challenge the Owner's rights in and to the Design Documents.
7.7 Ownership of Data
Any and all Owner data stored on the Bidder’s servers or within the Bidder’s custody is the sole
property of the Owner. The Bidder, subcontractor(s), officers, agents, and assigns shall not
make use of, disclose, sell, copy or reproduce the Owner’s data in any manner, or provide to any
entity or person outside of the Owner without the express written authorization of the Owner.
In the event resulting Contract is terminated for any reason, or upon expiration, and in addition
to all other rights to property set forth, the Selected Bidder shall make available to the Owner,
at no cost, all Owner data stored within the system, stored on the Bidder’s servers, or within the
Bidder’s custody, within fifteen (15) days of termination or Bidder request.
In the event resulting Contract is terminated for any reason, or upon expiration, and in addition
to all other rights to property set forth, the Owner shall retain ownership of all data, work
products, and documentation, created pursuant to the resulting Contract.
7.8 Data Privacy and Security
Bidder shall comply with all relevant federal, state, and local laws and regulations on security
and privacy. Bidder shall have and follow a disaster recovery plan. Bidder shall only store and
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
process Owner data within the continental United States. A requirement to the Contract, the
Bidder shall back up all Owner data daily to an offsite hardened facility.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
BID BOND
Sample Bid Bond Form
KNOW ALL BY THESE PRESENTS:
That we, , as Principal, and
, as Surety, are held and
firmly bound unto the Municipal Telecommunications Utility of the City of Waterloo, Iowa, as Obligee,
(hereinafter referred to as “the Jurisdiction”), in the penal sum of
dollars ($ ), or _______ percent of the
amount bid in lawful money of the United States, for which payment said Principal and Surety bind
themselves, their heirs, executors, administrators, successors, and assigns jointly and severally, firmly by
these presents.
The condition of the above obligation is such that whereas the Principal has submitted to the Jurisdiction a
certain proposal, in a separate envelope, and hereby made a part hereof, to enter into a contract in writing,
for the following described improvements;
F.Y. 2024 BILLING SYSTEM, OPERATIONAL SUPPORT SYSTEM, FLOW-THROUGH PROVISIONING
Contract NO. 1097
The improvement includes the installation and maintenance for an Operating Support System (OSS) /
Billing Support System (BSS) software for a billing, operational support, and flow-through provisioning
system that integrates with the City of Waterloo Water Work’s current billing system, Cogsdale, in support
of the launch of Waterloo Fiber, the City’s broadband Internet utility. Waterloo Fiber provides data, video,
and telephony services to businesses, homes, and community institutions within the City of Waterloo
(“Service Area”).
The City is in the process of building a feeder/distribution network for a Fiber-to-the-Premise (FTTP)
network initially capable of offering a 10 Gbps infrastructure to support wholesale and retail broadband
data services. Current design encompasses approximately 30,000 residential, commercial, and
community anchor passings.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
(CONT. BID BOND) Project Name
The Surety hereby stipulates and agrees that the obligations of said Surety and its bond shall be in no way
impaired or affected by any extension of the time within which the Jurisdiction may accept such bid or
execute such Contract; and said Surety does hereby waive notice of any such extension.
In the event that any actions or proceedings are initiated with respect to this Bond, the parties agree that
the venue thereof shall be Black Hawk County, State of Iowa. If legal action is required by the Jurisdiction
against the Surety or Principal to enforce the provisions of the bond or to collect the monetary obligation
incurring to the benefit of the Jurisdiction, the Surety or Principal agrees to pay the Jurisdiction all damages,
costs, and attorney fees incurred by enforcing any of the provisions of this Bond. All rights, powers, and
remedies of the Jurisdiction hereunder shall be cumulative and not alternative and shall be in addition to all
rights, powers and remedies given to the Jurisdiction, by law. The Jurisdiction may proceed against Surety
for any amount guaranteed hereunder whether action is brought against Principal or whether Principal is
joined in any such action or actions or not.
NOW, THEREFORE, if said proposal by the Principal be accepted, and the Principal shall enter into a contract
with Jurisdiction in accordance with the terms of such proposal, including the provision of insurance and of
a bond as may be specified in the contract documents, with good and sufficient surety for the faithful
performance of such contract, for the prompt payment of labor and material furnished in the prosecution
thereof, and for the maintenance of said improvements as may be required therein, then
this obligation shall become null and void; otherwise, the Principal shall pay to the Jurisdiction the full
amount of the bid bond, together with court costs, attorney’s fees, and any other expense of recovery.
Signed and sealed this day of , 20 .
SURETY: PRINCIPAL:
Surety Company Bidder
By By
Signature Attorney-in-Fact/Officer Signature
Printed Name of Attorney-in-
Fact/Officer
Printed Name
Company Name Title
Company Address Address
City, State, Zip Code City, State, Zip Code
Company Telephone Number Telephone Number
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
(CONT. BID BOND) Project Name
NOTE: All signatures on this bid bond must be original signatures in ink; copies, facsimile, or electronic
signatures will not be accepted. This bond must be sealed with the Surety’s raised, embossing seal. The
Certificate or Power of Attorney accompanying this bond must be valid on its face and sealed with the
Surety’s raised, embossing seal.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
SURETY BOND NO.
PERFORMANCE, PAYMENT, AND MAINTENANCE BOND
KNOW ALL BY THESE PRESENTS:
That we, __________________________________________________________________, as Principal
(hereinafter the “Contractor” or “Principal” and ____________________________________________, as
Surety are held and firmly bound unto the Municipal Telecommunications Utility of the City of Waterloo,
Iowa , as Obligee (hereinafter referred to as “the Jurisdiction”), and to all persons who may be injured by
any breach of any of the conditions of this Bond in the penal sum of
____________________________________________________________________________________
dollars ($____________________), lawful money of the United States, for the payment of which sum, well
and truly to be made, we bind ourselves, our heirs, legal representatives and assigns, jointly or severally,
firmly by these presents.
The conditions of the above obligations are such that whereas said Contractor entered into a contract with
the Jurisdiction, bearing date the _______ day of ___________________, _________, hereinafter the
“Contract”) wherein said Contractor undertakes and agrees to construct the following described
improvements:
F.Y. 2024 BILLING SYSTEM, OPERATIONAL SUPPORT SYSTEM, FLOW-THROUGH PROVISIONING, CONTRACT NO. 1097
The improvement includes the installation and maintenance for a Operating Support System (OSS) /
Billing Support System (BSS) software for a billing, operational support, and flow-through provisioning
system that integrates with the City of Waterloo Water Work’s current billing system, Cogsdale, in
support of the launch of Waterloo Fiber, the City’s broadband Internet utility. Waterloo Fiber provides
data, video, and telephony services to businesses, homes, and community institutions within the City of
Waterloo (“Service Area”).
The City is in the process of building a feeder/distribution network for a Fiber-to-the-Premise (FTTP)
network initially capable of offering a 10 Gbps infrastructure to support wholesale and retail broadband
data services. Current design encompasses approximately 30,000 residential, commercial, and
community anchor passings.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
(CON’T – PERFORMANCE, PAYMENT, AND MAINTENANCE BOND)
and to faithfully perform all the terms and requirements of said Contract within the time therein specified,
in a good and workmanlike manner, and in accordance with the Contract Documents.
It is expressly understood and agreed by the Contractor and Surety in this bond that the following provisions
are a part of this Bond and are binding upon said Contractor and Surety, to-wit:
1. PERFORMANCE: The Contractor shall well and faithfully observe, perform, fulfill, and abide by each
and every covenant, condition, and part of said Contract and Contract Documents, by reference
made a part hereof, for the above referenced improvements, and shall indemnify and save harmless
the Jurisdiction from all outlay and expense incurred by the Jurisdiction by reason of the Contractor’s
default of failure to perform as required. The Contractor shall also be responsible for the default or
failure to perform as required under the Contract and Contract Documents by all its subcontractors,
suppliers, agents, or employees furnishing materials or providing labor in the performance of the
Contract.
2. PAYMENT: The Contractor and the Surety on this Bond hereby agreed to pay all just claims submitted
by persons, firms, subcontractors, and corporations furnishing materials for or performing labor in
the performance of the Contract on account of which this Bond is given, including but not limited to
claims for all amounts due for labor, materials, lubricants, oil, gasoline, repairs on machinery,
equipment, and tools, consumed or used by the Contractor or any subcontractor, wherein the same
are not satisfied out of the portion of the contract price the Jurisdiction is required to retain until
completion of the improvement, but the Contractor and Surety shall not be liable to said persons,
firms, or corporations unless the claims of said claimants against said portion of the contract price
shall have been established as provided by law. The Contractor and Surety hereby bind themselves
to the obligations and conditions set forth in Chapter 573 of the Iowa Code, which by this reference
is made a part hereof as though fully set out herein.
3. MAINTENANCE: The Contractor and the Surety on this Bond hereby agree, at their own expense:
A. To remedy any and all defects that may develop in or result from all work except new paving to
be performed under the Contract within the period of two year (s) from the date of acceptance
of the work under the Contract, by reason of defects in workmanship or materials used in
construction of said work; and
B. To keep all work in continuous good repair; and
C. To pay the Jurisdiction’s reasonable costs of monitoring and inspection to assure that any
defects are remedied, and to repay the Jurisdiction all outlay and expense incurred as a result
of Contractor’s and Surety’s failure to remedy any defect as required by this section.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
(CON’T – PERFORMANCE, PAYMENT, AND MAINTENANCE BOND)
4. GENERAL: Every Surety on this Bond shall be deemed and held bound, any contract to the contrary
notwithstanding, to the following provisions:
A. To consent without notice to any extension of time to the Contractor in which to perform the
Contract;
B. To consent without notice to any change in the Contract or Contract Documents, which thereby
increases the total contract price and the penal sum of this bond, provided that all such changes
do not, in the aggregate, involve an increase of more than 20% of the total contract price, and
that this bond shall then be released as to such excess increase; and
C. To consent without notice that this Bond shall remain in full force and effect until the Contract
is completed, whether completed within the specified contract period, within an extension
thereof, or within a period of time after the contract period has elapsed and the liquidated
damage penalty is being charged against the Contractor.
D. That no provision of this Bond or of any other contract shall be valid that limits to less that
five years after the acceptance of the work under the Contract the right to sue on this Bond.
E. That as used herein, the phrase “all outlay and expense” is not to be limited in any way, but
shall include the actual and reasonable costs and expenses incurred by the Jurisdiction
including interest, benefits, and overhead where applicable. Accordingly, “all outlay and
expense” would include but not be limited to all contract or employee expense, all equipment
usage or rental, materials, testing, outside experts, attorneys fees (including overhead expenses
of the Jurisdiction’s staff attorneys), and all costs and expenses of litigation as they are incurred
by the Jurisdiction. It is intended the Contractor and Surety will defend and indemnify the
Jurisdiction on all claims made against the Jurisdiction on account of Contractor’s failure to
perform as required in the Contract and Contract Documents, that all agreements and promises
set forth in the Contract and Contract Documents, in approved change orders, and in this Bond
will be fulfilled, and that the Jurisdiction will be fully indemnified so that it will be put into the
position it would have been in had the Contract been performed in the first instance as required.
In the event the Jurisdiction incurs any “outlay and expense” in defending itself against any claim as to
which the Contractor or Surety should have provided the defense, or in the enforcement of the
promises given by the Contractor in the Contract, Contract Documents, or approved change orders, or
in the enforcement of the promises given by the Contractor and Surety in this Bond, the Contractor and
Surety agree that they will make the Jurisdiction whole for all such outlay and expense, provided that
the Surety’s obligation under this bond shall not exceed 125% of the penal sum of this bond.
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
(CON’T – PERFORMANCE, PAYMENT AND MAINTENANCE BOND)
In the event that any actions or proceedings are initiated regarding this Bond, the parties agree that the
venue thereof shall be Black Hawk County, State of Iowa. If legal action is required by the Jurisdiction to
enforce the provisions of this Bond or to collect the monetary obligation incurring to the benefit of the
Jurisdiction, the Contractor and the Surety agree, jointly, and severally, to pay the Jurisdiction all outlay and
expense incurred therefor by the Jurisdiction. All rights, powers, and remedies of the Jurisdiction hereunder
shall be cumulative and not alternative and shall be in addition to all rights, powers, and remedies given to
the Jurisdiction, by law. The Jurisdiction may proceed against surety for any amount guaranteed hereunder
whether action is brought against the Contractor or whether Contractor is joined in any such action(s) or
not.
NOW THEREFORE, the condition of this obligation is such that if said Principal shall faithfully perform all the
promises of the Principal, as set forth and provided in the Contract, in the Contract Documents, and in this
Bond, then this obligation shall be null and void, otherwise it shall remain in full force and effect.
When a word, term, or phrase is used in this Bond, it shall be interpreted or construed first as defined in this
Bond, the Contract, or the Contract Documents; second, if not defined in the Bond, Contract, or Contract
Documents, it shall be interpreted or construed as defined in applicable provisions of the Iowa Code; third,
if not defined in the Iowa Code, it shall be interpreted or construed according to its generally accepted
meaning in the construction industry; and fourth, if it has no generally accepted meaning in the construction
industry, it shall be interpreted or construed according to its common or customary usage.
Failure to specify or particularize shall not exclude terms or provisions not mentioned and shall not limit
liability hereunder. The Contract and Contract Documents are hereby made a part of this Bond
Contract No. 1097 F.Y. 2024 Billing System, Operational Support System, Flow-Through Provisioning
Project No. _______________
(CON’T – PERFORMANCE, PAYMENT, AND MAINTENANCE BOND)
PRINCIPAL: SURETY:
Contractor Surety Company
By By
Signature Signature Attorney-in-Fact Officer
Title Printed Name of Attorney-in-Fact Officer
FORM APPROVED BY:
Company Name
Attorney for Jurisdiction Company Address
City, State, Zip Code
Company Telephone Number
NOTE:
1. All signatures on this performance, payment, and maintenance bond must be original signatures
in ink; copies, facsimile, or electronic signatures will not be accepted.
2. This bond must be sealed with the Surety’s raised, embossing seal.
3. The Certificate or Power of Attorney accompanying this bond must be valid on its face and sealed
with the Surety’s raised, embossing seal.
4. The name and signature of the Surety’s Attorney-in-Fact/Officer entered on this bond must be
exactly as listed on the Certificate or Power of Attorney accompanying this bond.
Section #Area Compliancy Notes
1 System Architecture
1.1 Platform
1.1.1
Applications shall utilize an industry standard relational database technology as their data repository strategy.
Please note supported databases. 0% compliant
1.1.2 Utilizes data redundancy techniques (e.g. RAID, mirroring). Please describe redundancy schema.0% compliant
1.2 System Basic Functions
1.2.1
Solution has remote access (e.g. VPN, Web) for administration of system, users, security, etc. Please
describe.0% compliant
1.2.2 User interfaces have:
1.2.2.1 • industry standard keyboard and mouse capabilities.0% compliant
1.2.2.2 • are browser neutral.0% compliant
1.2.3
Applications support simultaneous users residing in multiple on-site and off-site locations. Describe
topology/networking needed for support.0% compliant
1.2.4 System shall automatically backup system data based on user specified schedule. Please describe 0% compliant
1.2.5 System provides logs of the following for all user and system activity
1.2.5.1 • Date/time 0% compliant
1.2.5.2 • User id 0% compliant
1.2.5.3 • Terminal ID / IP address 0% compliant
1.2.5.4 • System function / application 0% compliant
1.2.5.5 • Combination of the above.0% compliant
1.2.6
System utilizes scheduler for automatic initiation of user specified processes (e.g. provisioning, billing). Please
describe.0% compliant
1.2.7
All external reference information is automatically updated / refreshed according to defined schedules (e.g.
MSAG, LERG, TPM, etc.). Please describe.0% compliant
1.2.8 Software is escrowed for each release/patch in a formal offsite location. Please describe.0% compliant
1.2.9
System shall continue daily operations (ordering, trouble tickets, reports, etc.) when retail or wholesale billing
and/or invoicing in process.0% compliant
1.3 Scalability
1.3.1
Will support a minimum of 150 users (75 concurrent), local and remote, while maintaining sub 2 second
response times for user screens 0% compliant
1.3.1.1 • Please describe licensing structure for growth of additional capacity.NA-Use Notes Field
1.3.2
Will support 30K customer accounts initially with growth up to 100K customers without having to upgrade
software.0% compliant
1.4 Security
1.4.1 Setup of security is real-time, on-line 0% compliant
1.4.2 System access is controlled through user id / password 0% compliant
1.4.3 Security setup only available through a specialized security administrator user 0% compliant
1.4.4 System shall provide collection of users into groups 0% compliant
1.4.5 System shall provide user access based on following profiles:
1.4.5.1 • Administration (full access to all applications)0% compliant
1.4.5.2 • System (access based on system; e.g. Telephone, CATV, etc.)0% compliant
1.4.5.3 • Module (access based on module)0% compliant
1.4.5.4 • Group (access based on user group)0% compliant
1.4.6 Shall provide setup of the following user rights for above profiles:
1.4.6.1 • Full Access (read, add, change, delete, execute)0% compliant
1.4.6.2 • Data Entry (add only)0% compliant
1.4.7 Shall provide logging unauthorized access attempts 0% compliant
1.5 Application Basic Functionality
1.5.1
System shall provide at least a triple play product strategy of wire line or VOIP voice services (Local/Long
Distance), data services (internet/wholesale), and video services.0% compliant
1.5.2
All applications fields with limited number of values are selected through dropdown boxes and are driven
through control tables.0% compliant
1.5.3
Application control tables are user maintainable and subject to security levels (e.g. only system admin can
update billing tables)0% compliant
1.5.4
Applications support a minimum of six levels of billing hierarchy (e.g. Company, Sub-company, Division,
Group, Master, Detail)0% compliant
1.5.5 All customer related screens can access customer records through a minimum of:
1.5.5.1 • account number 0% compliant
1.5.5.2 • name 0% compliant
1.5.5.3 • telephone number 0% compliant
1.5.5.4 • billing address (street, city, state, and/or zip)0% compliant
1.5.5.5 • service address (street, city, state, and/or zip)0% compliant
1.5.5.6 • email address 0% compliant
1.5.5.7 • SSN 0% compliant
1.5.5.8 • Drivers License 0% compliant
1.5.6
Displays list of customers for selection from drop down box if more than one customer matches above
criteria 0% compliant
1.5.7
Shall enter partial criteria, have system display list of possible customers and then make selection from drop
down box 0% compliant
1.5.8 Applications confirm updates before committing 0% compliant
This tab contains what the Municipal Telecommunication Utlity of Waterloo considers to be the minimum functional requirements for selection of an OSS/BSS solution.
If using hard copy version: Fill out level of compliancy in the Compliancy field for associated question or request. Use only the following percent values: 100% for fully compliant, 80%,
If using electronic version: Use the drop down selections in the Compliancy field to indicate level of compliance to associated question or request. Please add any additional comments
Scoring: 100%-5 pts; 80%-4 pts; 60%-3pts; 40%-2 pts; 20%-1 pt; 0%-0pts
For any features/interfaces that would need to be developed, City of Waterloo and Municipal Telecommunication Utlity of Waterloo requests that a firm fixed bid and time line be
1.5.8.1
• Shall apply mass changes to customer data through on line interface (e.g. change all product codes from
one value to another)0% compliant
2 Web Capability
2.0.1 System contains Web portals for:
2.0.1.1 • customer self care 0% compliant
2.0.1.2 • Bill review and payment
2.0.1.2.1 – Shall provide method for clients to review mirror image of current and past bills 0% compliant
2.0.1.2.2 – Shall provide method to download bill to client computer as a pdf, Excel, or Word document 0% compliant
2.0.1.2.3 – Shall provide method to download LD detail to client computer as an Excel or .csv file 0% compliant
2.0.1.2.4 – Shall provide method for clients to make payments online through credit/debit card or EFT.0% compliant
3 Products
3.1 General:
3.1.1 Product matrix is table driven and maintainable by users 0% compliant
3.1.2 User defined product elements, at a minimum:
3.1.2.1 • Code 0% compliant
3.1.2.2 • Product type (e.g. telephone, CATV, Data, etc.)0% compliant
3.1.2.3 • Sector (e.g. business, residential, government, etc.)0% compliant
3.1.2.4 • Geographic indicator where product offered 0% compliant
3.1.2.5 • Descriptions (2) (Order entry and invoice)0% compliant
3.1.2.6 • Product rates (2) Normal and Promo rate 0% compliant
3.1.2.7
• Effective date range or Shall provide method to assign what billing periods product or promotion should be
activated 0% compliant
3.1.3 Unlimited number of elements/codes 0% compliant
3.1.4 Shall provide price rates with a minimum significance of 4 decimal places (e.g. 0.0001)0% compliant
3.1.5 Shall provide both positive and negative price rates up to +- 999,999,999.9999 0% compliant
3.1.6
Shall provide method to group product elements/codes into packages (e.g. CATV 150 channels plus 3
premium channels)0% compliant
3.1.7
Shall provide method to group packages into product sets or bundles (e.g. group a data package, CATV
package, and telephone package into one orderable product)0% compliant
3.1.8
Shall provide method to select x out of y components under same package and price (e.g. CATV Gold
package supports user to select any 3 premium channels)0% compliant
3.1.9
Shall provide method to set elements, packages, product, etc. sets to be defaulted and/or filtered (i.e. only
elements applicable to client are visible for selection) to customers meeting following criteria:
3.1.9.1 • Shall provide calculation of charges based on:
3.1.9.1.1 – Flat amount 0% compliant
3.1.9.1.2 – Unit charge * number of units 0% compliant
3.1.9.1.3 – Customer specified charge (e.g. labor cost)0% compliant
3.1.9.1.4 – Combo of the above 0% compliant
3.1.9.2
• Shall provide the following non-transactional product types: (note: transactional product types described
within each service section below)
3.1.9.2.1 – 1 time installation charge/credit 0% compliant
3.1.9.2.2 – 1 time deactivation / cancellation charge 0% compliant
3.1.9.2.3 – 1 time order charge/credit 0% compliant
3.1.9.2.4 – 1 time labor charge/credit 0% compliant
3.1.9.2.5 – 1 time miscellaneous charge/credit 0% compliant
3.1.9.2.6 – monthly recurring charge/credit 0% compliant
3.1.9.2.7 – client specific pricing/credit 0% compliant
3.1.9.2.8 – Combination of above 0% compliant
3.1.9.3
• Shall provide method to set effective and discontinue dates for elements, packages, product sets (e.g.
feature will no longer be available for ordering, but still a billable element)0% compliant
3.1.9.4 • Shall provide method to apply discount methods to:
3.1.9.4.1 – individual product codes 0% compliant
3.1.9.4.2 – packages 0% compliant
3.1.9.4.3 – product sets 0% compliant
3.1.9.4.4 – specific hierarchical account levels 0% compliant
3.1.9.4.5 – MDU owner and/or residents 0% compliant
3.1.9.4.6 – overall invoice total 0% compliant
3.1.9.4.7 – combination of the above 0% compliant
3.1.9.5 • Shall provide calculation of discounts methods on:
3.1.9.5.1 – Flat amount 0% compliant
3.1.9.5.2 – Percentage of associated charge 0% compliant
3.1.9.5.3 – Tiered flat amount based on associated charge(s)0% compliant
3.1.9.5.4 – Tiered percentage based on associated charge(s)0% compliant
3.1.9.5.5 – Threshold flat amount based on associated charge(s)0% compliant
3.1.9.5.6 – Threshold percentage based on associated charge(s)0% compliant
3.1.9.5.6.1 + Combination of above 0% compliant
3.2 Transaction types - Wire line Voice/LD:
3.2.1 Shall provide the following transaction based product revenue elements:
3.2.1.1 • Local measured service 0% compliant
3.2.1.2 • Peg Count (cost per transaction)0% compliant
3.2.1.3 • Mileage (distance sensitive)0% compliant
3.2.1.4 • Duration (length of transaction)0% compliant
3.2.1.5 • Type of transaction (DA, OPH, etc.)0% compliant
3.2.1.6 • Jurisdiction (intra/interLATA; intra/interstate; international)0% compliant
3.2.1.7 • Zone (Mileage based)0% compliant
3.2.1.8 • Zone (Geographic based - e.g. NPA-NXX, country code, country and city code)0% compliant
3.2.1.9 • Time of Day 0% compliant
3.2.1.9.1 – Combination of above 0% compliant
3.3 Transaction types - Video:
3.3.1 Shall provide the following transaction based product revenue elements:
3.3.1.1 • Pay per view 0% compliant
3.3.1.2 • On-line purchases 0% compliant
3.3.1.3 • Video on demand 0% compliant
3.4 Transaction types - Internet/Data:
3.4.1 Static IP addresses 0% compliant
3.4.2 Bandwidth (MB/s)0% compliant
3.4.3 Data transmitted (packet count)0% compliant
3.4.4 Disk space used or requested (Mb)0% compliant
3.4.5 Email addresses 0% compliant
3.4.6 Web hosting site/pages 0% compliant
3.4.7 End-point connection 0% compliant
3.4.8 Combination of above 0% compliant
4 Mandatory Data Elements
4.1 Fields:
4.1.1 Alphanumeric customer account number (min. 25 chars)0% compliant
4.1.2 Separate service and billing addresses (MSAG compliant fields)
4.1.2.1 • All addresses are edited for CASS certification 0% compliant
4.1.2.2 • Street prefix 0% compliant
4.1.2.3 • House/Building Number 0% compliant
4.1.2.4 • Street 0% compliant
4.1.2.5 • Street Suffix (e.g. lane, drive)0% compliant
4.1.2.6 • Street Line 2 0% compliant
4.1.2.7 • City 0% compliant
4.1.2.8 • County/Parish 0% compliant
4.1.2.9 • State 0% compliant
4.1.2.9.1 – Zip 0% compliant
4.1.2.9.2 – Zip+4 0% compliant
4.1.2.9.3 – Apartment 0% compliant
4.1.2.9.4 – Lot 0% compliant
4.1.2.9.5 – Suite 0% compliant
4.1.2.9.6 – Box 0% compliant
4.1.2.9.7 – Direction (e.g. NW)0% compliant
4.1.3 MDU Indicator/Code on address records 0% compliant
4.1.4 Customer status (user definable or at a minimum)
4.1.4.1 • Home passed 0% compliant
4.1.4.2 • New/Pending 0% compliant
4.1.4.3 • Active 0% compliant
4.1.4.4 • Suspend / Temp disconnect 0% compliant
4.1.4.5 • Disconnect 0% compliant
4.1.4.6 • Cancelled 0% compliant
4.1.4.7 • Medical certificate 0% compliant
4.1.4.8 • Cannot disconnect 0% compliant
4.1.5 Personal identification information
4.1.5.1 • Title (e.g. Mr., Ms.)0% compliant
4.1.5.2 • First name 0% compliant
4.1.5.3 • Last name 0% compliant
4.1.5.4 • Middle name 0% compliant
4.1.5.5 • Suffix (e.g. Sr., Jr., III)0% compliant
4.1.5.6 • Business name 0% compliant
4.1.5.7 • Business tax id 0% compliant
4.1.5.8 • Social security number 0% compliant
4.1.5.9 • Driver's license 0% compliant
4.1.6 Contact information
4.1.6.1 • Contact name 0% compliant
4.1.6.2 • Contact phone number 1 0% compliant
4.1.6.3 • Contact e-mail 0% compliant
4.1.7 Credit class 0% compliant
4.1.8 Directory publish code
4.1.8.1 • Publish 0% compliant
4.1.8.2 • Non-publish, not available to directory assistance 0% compliant
4.1.8.3 • Non-publish, available to directory assistance 0% compliant
4.1.8.4 • Unlisted 0% compliant
4.1.8.5 • Unlisted, not available to 911 0% compliant
4.1.8.6 • Directory copies 0% compliant
4.1.8.7 • Directory listing 1 0% compliant
4.1.8.8 • Directory listing 2 0% compliant
4.1.9 Calling Card Toll Free Access Number 0% compliant
4.1.10 Calling Card PIN number 0% compliant
4.1.10.1 • Blocking codes
4.1.10.1.1 – 500/900 numbers 0% compliant
4.1.10.1.2 – International numbers 0% compliant
4.1.10.1.3 – Collect / 3rd number 0% compliant
4.1.10.1.4 – Adult content (video)0% compliant
4.1.10.1.5 – Bad debt status flag 0% compliant
4.1.10.2 • Disconnect reason 0% compliant
4.1.10.3 • Original account start date 0% compliant
4.1.10.4 • Bill method
4.1.10.4.1 – Hard copy 0% compliant
4.1.10.4.2 – Electronic copy 0% compliant
4.1.10.4.3 – Web access 0% compliant
4.1.10.4.4 – Email 0% compliant
4.1.10.4.5 – Physical media (e.g. CD)0% compliant
4.1.10.5 • Pay method
4.1.10.5.1 – Cash 0% compliant
4.1.10.5.2 – Checks 0% compliant
4.1.10.5.3 – Prepay 0% compliant
4.1.10.5.4 – Bill pay (list available agents)0% compliant
4.1.10.5.5 – Web payment portal 0% compliant
4.1.10.5.6 – EFT 0% compliant
4.1.10.5.7 – Credit card 0% compliant
4.1.10.5.8 – Debit card 0% compliant
4.1.10.5.9 – Gift certificates/card 0% compliant
4.1.10.5.10 – Recurring payment 0% compliant
4.1.10.6 • Pay method information
4.1.10.6.1 – EFT account name / card name 0% compliant
4.1.10.6.2 – EFT account number / card number 0% compliant
4.1.10.6.3 – EFT bank routing number / card id 0% compliant
4.1.10.6.4 – Card expiration date 0% compliant
4.1.10.6.5 – Security code 0% compliant
4.1.10.7 • Business classification code 0% compliant
4.1.10.8 • Tax exempt status by jurisdiction 0% compliant
4.1.10.9 • Deposit 0% compliant
4.1.10.10 • Deposit interest 0% compliant
4.1.10.11 • Previous occupant information
4.1.10.11.1 – Name 0% compliant
4.1.10.12 • Original service order number 0% compliant
4.1.10.13 • Last service order number 0% compliant
4.1.10.14 • Customer role (e.g. responsible party, co-responsible party)0% compliant
4.1.10.15 • Bill cycle 0% compliant
4.1.10.16 • Statement invoice format code 0% compliant
4.1.10.17 • Main bill to account levels
4.1.10.17.1 – Level 1 bill to account 0% compliant
4.1.10.17.2 – Level 2 bill to account 0% compliant
4.1.10.17.3 – Level 3 bill to account 0% compliant
4.1.10.17.4 – Level 4 bill to account 0% compliant
4.1.10.17.5 – Level 5 bill to account 0% compliant
4.1.10.17.6 – Level 6 bill to account 0% compliant
4.1.10.18 • Produce statement flag 0% compliant
4.1.10.19 • Bill Handle Sort Code 0% compliant
4.1.10.20 • Last Statement Date 0% compliant
4.1.10.21 • Statement Due Date 0% compliant
4.1.10.22 • Bill Language Code 0% compliant
4.1.10.23 • Community/Affinity code 0% compliant
4.1.10.24 • Shall provide method to add unlimited notes to account
4.1.10.24.1 – User id of person adding note 0% compliant
4.1.10.24.2 – Date / time of note 0% compliant
4.1.10.24.3 – Note code / category 0% compliant
4.1.10.24.4 – At least 1000 character note field 0% compliant
4.1.10.24.5 – Ability to search note fields across all accounts 0% compliant
4.1.10.24.6 – Ability to search note fields across filtered list of accounts 0% compliant
4.1.10.25 • Services (multiple services per account)
4.1.10.25.1 – Service type
4.1.10.25.1.1 + Wire line/voice 0% compliant
4.1.10.25.1.2 + Voice Over IP 0% compliant
4.1.10.25.1.3 + Video 0% compliant
4.1.10.25.1.4 + Data/Internet 0% compliant
4.1.10.25.1.5 + Transport 0% compliant
4.1.10.25.1.6 + Special Circuit 0% compliant
4.1.10.25.1.7 + Special Circuit ID (user definable range or list)0% compliant
4.1.10.25.2 – Service start date 0% compliant
4.1.10.25.3 – Service suspend date 0% compliant
4.1.10.25.4 – Service deactivation date 0% compliant
4.1.10.25.5 – Service statement code (needed if services are billed on different invoices)0% compliant
4.1.10.25.6 – Tax / surcharge codes
4.1.10.25.6.1 + Federal 0% compliant
4.1.10.25.6.2 + State 0% compliant
4.1.10.25.6.3 + Sales 0% compliant
4.1.10.25.6.4 + Minimum 10 local 0% compliant
4.1.10.25.6.5 + Minimum 10 surcharges 0% compliant
4.1.10.25.7 – Tax exempt flag 0% compliant
4.1.10.25.8
– Service Balances and Aging (charges, credits, adjustments, taxes/surcharges, penalties stored separately
for each aging level)
4.1.10.25.8.1 + Overall account balance 0% compliant
4.1.10.25.8.2 + Current balance elements 0% compliant
4.1.10.25.8.3 + 30 day past due 0% compliant
4.1.10.25.8.4 + 60 day past due 0% compliant
4.1.10.25.8.5 + 90 day past due 0% compliant
4.1.10.25.8.6 + 120 day past due 0% compliant
4.1.10.25.8.7 + 150 day past due 0% compliant
4.1.10.25.8.8 + 180 day past due 0% compliant
4.1.10.26 • Specific service fields
4.1.10.26.1 – Wire line specific
4.1.10.26.1.1 + Key = telephone number 0% compliant
4.1.10.26.1.2 + Ported number indicator 0% compliant
4.1.10.26.1.3 + DID number 0% compliant
4.1.10.26.1.4 + PRI number 0% compliant
4.1.10.26.1.5 + PBX group 0% compliant
4.1.10.26.1.6 + EAS area 0% compliant
4.1.10.26.1.7 + IntraLATA PIC 0% compliant
4.1.10.26.1.8 + InterLATA PIC 0% compliant
4.1.10.26.1.9 + International PIC 0% compliant
4.1.10.26.1.9.1 · Service limits
4.1.10.26.1.9.1.1 › Billing period overall toll maximum 0% compliant
4.1.10.26.1.9.1.2 › Billing period domestic toll maximum 0% compliant
4.1.10.26.1.9.1.3 › Billing period international toll maximum 0% compliant
4.1.10.26.1.9.1.4 › Billing period DA maximum 0% compliant
4.1.10.26.1.9.1.5 › Billing period Local Measured Service monthly maximum 0% compliant
4.1.10.26.1.9.2 · Toll Free 0% compliant
4.1.10.26.2 – Video specific
4.1.10.26.2.1 + Key = user defined 0% compliant
4.1.10.26.2.2 + Number of set top boxes 0% compliant
4.1.10.26.2.3 + Content restriction 0% compliant
4.1.10.26.2.4 + EAS area/alert 0% compliant
4.1.10.26.2.5 + Service limits 0% compliant
4.1.10.26.2.5.1 · Billing period overall content monthly maximum 0% compliant
4.1.10.26.2.5.2 · Billing period pay-per-view monthly maximum 0% compliant
4.1.10.26.2.5.3 · Billing period video on demand monthly maximum 0% compliant
4.1.10.26.3 – Data/internet specific
4.1.10.26.3.1 + Key = email address / static IP address / user defined 0% compliant
4.1.10.26.3.2 + Encrypted password (with complexity limits for security)0% compliant
4.1.10.26.3.3 + Alternate marketing email address 0% compliant
4.1.10.26.3.4 + Forwarding email address 0% compliant
4.1.10.26.3.5 + Domain name 0% compliant
5 Customer Relations Management (CRM)
5.0.1 Shall provide method to setup and maintain customer information listed in Mandatory Data section above.0% compliant
5.0.2 Shall provide method to access the following customer information on-line:
5.0.2.1 • Existing and previously purchased product(s)0% compliant
5.0.2.2 • Current and historical billing details (e.g. services, costs, taxes, etc.)0% compliant
5.0.2.3 • Current and historical account balances 0% compliant
5.0.2.4 • Current and historical ordering information 0% compliant
5.0.2.5 • Current trouble and historical trouble tickets 0% compliant
5.0.2.6 • Shall provide method for user defined CRM reports based on any of the accessible data.0% compliant
6 Work Flow Management
6.0.1 Shall provide method to setup and maintain workflow stop points (e.g. departments)0% compliant
6.0.2
Shall provide method to set up different work order flows based on type of order (e.g. single line vs. multi-
line, video, data/internet, etc.)0% compliant
6.0.3
Shall provide method to setup work flows based on multiple order components (e.g. phone, LD, and internet,
but not video)0% compliant
6.0.4
Shall provide method to set up different work order flows based on combination of order type and
components 0% compliant
6.0.5 Shall provide method to generate multiple work orders from one service order 0% compliant
6.0.6
Shall provide method to set up different work order flows based on service location and facility assignment /
availability 0% compliant
6.0.7
Shall provide method for work order system to track order across applications (e.g. CRM->Order Entry-
>Engineering->Billing)0% compliant
6.0.8
Prevents orders from leaving stop point without signoff (i.e. user id of person completing order section/date
of completion).0% compliant
6.0.8.1 • Shall have system provide signoff for automated steps (e.g. real-time provisioning)0% compliant
6.0.8.2 • Shall provide method to apply notes to order at each stop point 0% compliant
6.0.8.3 • Shall provide method to list/report outstanding orders by:
6.0.8.3.1 – order type 0% compliant
6.0.8.3.2 – stop point 0% compliant
6.0.8.3.3 – length of time in stop point 0% compliant
6.0.8.3.4 – overall length of time order has been in system 0% compliant
6.1 Order Processing
6.1.1 Shall provide method to set up and maintain the following order types
6.1.1.1 • New install or order of service (e.g. voice, video, PPV, VOD, etc.)0% compliant
6.1.1.2 • Change of service 0% compliant
6.1.1.3 • Change of account information 0% compliant
6.1.1.4 • Add features 0% compliant
6.1.1.5 • Transfer account 0% compliant
6.1.1.6 • Discontinue features 0% compliant
6.1.1.7 • Discontinue service 0% compliant
6.1.1.8 • Close account 0% compliant
6.1.1.9 • Customer change of service address (must handle CPE equipment)0% compliant
6.1.2 Shall provide method to set up and maintain order status codes
6.1.2.1 • New/Pending 0% compliant
6.1.2.2 • Active 0% compliant
6.1.2.3 • Change/Pending 0% compliant
6.1.2.4 • Hold 0% compliant
6.1.2.5 • Suspend / Temporary disconnect 0% compliant
6.1.2.6 • Reconnect 0% compliant
6.1.2.7 • Completed 0% compliant
6.1.2.8 • Cancelled 0% compliant
6.1.2.9 • Erred/Void 0% compliant
6.1.3 Shall provide method to hold, suspend or cancel an order in any status prior to completion in real-time.0% compliant
6.1.4 Shall provide method to track a service order in real-time until archived from the system.0% compliant
6.1.5 Shall provide method to set up and maintain order screen flow based on order type 0% compliant
6.1.6 Shall provide method to set up and maintain CSR scripting/marketing messages per:
6.1.6.1 • System edits service order information for completeness and reasonableness 0% compliant
6.1.6.2 • Shall provide method to confirm addresses against MSAG for validity 0% compliant
6.1.6.3 • Shall provide method to convert address to CASS certification format 0% compliant
6.1.6.4 • Shall provide method to support service types:
6.1.6.4.1 – Business 0% compliant
6.1.6.4.2 – Residential 0% compliant
6.1.6.4.3 – Government 0% compliant
6.1.6.4.4 – Wholesale 0% compliant
6.1.6.4.5 – Transport 0% compliant
6.1.6.4.6 – Resale 0% compliant
6.1.6.4.7 – Internal 0% compliant
6.1.6.4.8 – Other 0% compliant
6.1.6.5 • Shall provide method to set priority for order:
6.1.6.5.1 – Emergency 0% compliant
6.1.6.5.2 – High 0% compliant
6.1.6.5.3 – Normal 0% compliant
6.1.6.5.4 – Low 0% compliant
6.1.6.6
• Shall provide method to calculate Firm Order Commit date based on work order flow timelines PRIOR to
committing order 0% compliant
6.1.6.7 • Shall provide method to generate disconnect orders automatically based on disconnect methodology 0% compliant
6.1.6.8 • Shall provide method to set up and maintain disconnect criteria:
6.1.6.8.1 – maximum balance not subject to disconnect (e.g. $5.00)0% compliant
6.1.6.8.2 – Number of days past due 0% compliant
6.1.6.8.3 – Business type not subject to disconnect (e.g. hospital)0% compliant
6.1.6.9
• Shall provide method for a specific user type to inquire in real-time all orders by user defined criteria.
(order type, service type, status, due date, department, customer, etc.)0% compliant
6.1.6.10 • Shall provide method to retrieve order in real-time by:
6.1.6.10.1 – Order type 0% compliant
6.1.6.10.2 – Service type 0% compliant
6.1.6.10.3 – Service order number 0% compliant
6.1.6.10.4 – Account number 0% compliant
6.1.6.10.5 – Account name 0% compliant
6.1.6.10.6 – Order status 0% compliant
6.1.6.10.7 – Due date 0% compliant
6.1.6.10.8 – Work flow point 0% compliant
6.1.6.11 • Shall provide method to add notes to account or service order during order process
6.1.6.11.1 – User id of person adding note 0% compliant
6.1.6.11.2 – Date / time of note 0% compliant
6.1.6.11.3 – Note code / category 0% compliant
6.1.6.11.4 – At least 1000 character note field 0% compliant
6.1.6.12 • Shall provide method to automatically close order to billing when one or all components provisioned 0% compliant
6.1.6.13 • Shall provide method to attach Subscriber line ID to order 0% compliant
6.2 Number Portability (Voice Orders)
6.2.1
Shall provide method to initiate a number porting request to the number portability database administrator
triggered by a service order.0% compliant
6.2.2
Shall provide method to receive and process a number port request from the number portability database
administrator. This includes validation of the customer account, customer's account change restriction
indicator, port request data element validation and where appropriate, to generate the appropriate service
order.0% compliant
6.2.3
Shall provide method to generate a port request rejection response to the number portability database
administrator.0% compliant
6.2.4 Shall provide method to track the status of a number porting request in real-time.0% compliant
6.2.5 Shall provide method to store relevant number port requests as part of bill cycle history.0% compliant
7 Flow Through Provisioning
7.1 General
7.1.1
Shall provide method to identify service order information and translate it in real-time/near real-time into
electronic transactions submitted to the appropriate provisioning system as part of automated provisioning of
services.0% compliant
7.1.2
Interface shall provide method to provision all order types (install, change, disconnect, etc.) and services
supported by product table as long as functions supported by provisioning system 0% compliant
7.1.3
Interface shall provide method to provision multiples services simultaneously (e.g. voice, video, and data
services).0% compliant
7.1.4
Shall provide method to receive completion/error codes real-time from provisioning system to track issues or
problems during order process.0% compliant
7.2 Voice
7.2.1
Shall provide method to seamlessly interface to selected soft switch and unified messaging system.
7.2.1.1 • Metaswitch 0% compliant
7.2.1.2 • Alcatel-Lucent 0% compliant
7.2.2
If system does not have current interface to above soft switch platforms, please indicate expected time and
cost to create interface for each switch not currently supported.
0% compliant
7.2.3 Shall provide method to exchange electronic LIDB information with a third party vendor.0% compliant
7.2.4 Shall provide method to exchange electronic Emergency Services (911) information with a third party vendor.0% compliant
7.3 Video/ONT/Set top boxes
7.3.1
Shall provide method to seamlessly interface to Alcatel AMS system to provision and monitor the set top
boxes, ONT and the XGS-PON system.
7.3.1.1
• Shall provide capability for installation orders to generate and store an SLID# (Subscriber Location ID) to
be used to as an activation key for the ONT 0% compliant
7.3.1.2
• Shall provide capability to send authorization codes (hits) to set top boxes to a defined customer range
(e.g. customer number range, number of customers, all customers) on demand, or on schedule.0% compliant
7.3.1.3
• Shall provide a method to send authorization codes (hits) to set top boxes to allow or disallow PPV
purchase, VOD purchase.0% compliant
7.3.1.4
• Shall provide a method to send authorization codes (hits) to set top boxes to set them in 1-way and 2-way
communication mode. (return path)0% compliant
7.3.1.5 • Shall provide capability to automatically hold orders if ONT not active 0% compliant
7.3.1.6
• Shall provide capability to capture and store OLT/SLOT/Port/Serial Number returned by the AMS system,
through the AMS alert function, when an ONT becomes active, but is not provisioned.0% compliant
7.3.1.7
• Shall provide capability to automatically complete held order's profiles (e.g. OLT, Slot ,Port, Serial #)
associated with a newly activated ONT's and release order for provisioning.0% compliant
7.3.1.8 • Shall provide capability to monitor AMS system for alerts 0% compliant
7.3.1.9
• Shall provide ability to activate/deactivate individual service ports on the ONT (i.e. POTS, RF, Ethernet
ports).0% compliant
7.3.1.10 • Shall provide ability to activate/update/deactivate QoS profiles on the XGS-PON system through the AMS 0% compliant
7.3.1.11
• Shall have the capability to store unused VLAN assignments and make VLAN Assignments in the OLT and
the Routers at the time of ONT Turn-up.0% compliant
7.3.1.12
• Shall have the capability to assign QOS and IP filter templates based upon the customer profiles and assign
these template identifications to the appropriate customer VLAN within the routers using the Alcatel's 5620
Service Aware Mgr 0% compliant
7.3.2
Shall provide method to seamlessly interface to ([to be selected interface]) middleware for IPTV STB
registration assignments and customer video subscription services.
0% compliant
7.3.3
Shall provide method to seamlessly interface to Tandberg OpenStream VOD system (VOD purchase limit,
authorization, reporting)0% compliant
7.3.4
If system does not have current interface to above platforms, please indicate expected time and cost to
create interface.0% compliant
7.4 Data/Internet
7.4.1 Shall provide method to seamlessly interface to ISP. 0% compliant
7.4.2
If system does not have current interfaces to above, please indicate expected time and cost to create
interface.0% compliant
8 Retail Billing
8.1 General
8.1.1 Shall provide up to 999 billing cycles 0% compliant
8.1.2 Shall provide method to designate cycle periods to be:
8.1.2.1 • Daily 0% compliant
8.1.2.2 • Weekly 0% compliant
8.1.2.3 • Monthly 0% compliant
8.1.2.4 • Quarterly 0% compliant
8.1.2.5 • Yearly 0% compliant
8.1.2.6 • ad-hoc where bill period is calculated from Last bill date to current date for disconnecting clients 0% compliant
8.1.3 Shall provide method to generate bills when either:
8.1.3.1 • Individual components are closed within service order 0% compliant
8.1.3.2 • All components are closed within service order 0% compliant
8.1.4 Shall provide method to prorate charges based on:
8.1.4.1 • Effective or discontinue dates for price elements, products, packages, etc.0% compliant
8.1.4.2 • Effective or discontinue dates for account or sub-account(s)0% compliant
8.1.4.3 • Actual days in month or standard 30 day month 0% compliant
8.1.4.4 • Back billing of price elements 0% compliant
8.1.4.5 • Back billing of customer account or sub-accounts 0% compliant
8.1.5 Shall provide method to support and bill for all supported elements in product database 0% compliant
8.2 Usage/Transaction Collection/Mediation/Billing
8.2.1
Shall provide method to collect/poll/mediate usage/transaction records from external and internal providers
depicted in Provisioning section in accordance to the following:
8.2.1.1 • Voice
8.2.1.1.1 – LD 0% compliant
8.2.1.1.2 – Collect calls 0% compliant
8.2.1.1.3 – 3rd party billed 0% compliant
8.2.1.1.4 – Shall provide method to perform file and record gap detection.0% compliant
8.2.1.1.5 – Shall provide method to perform file and record duplicate detection.0% compliant
8.2.1.1.6
– Shall provide method for user to perform real-time, date/time effective modifications to tables for usage
identification and guiding. (NPA-NXXs, LRN, LERG, TPM, CIC, trunks, etc.)0% compliant
8.2.1.1.7 – Shall provide method to disposition records without defined criteria to an error recycle process.0% compliant
8.2.1.1.8
– Shall provide method to disposition Local/IntraLATA records with no applicable specific access like or
revenue settlement information to be discarded or to an error recycle process.0% compliant
8.2.1.1.8.1
+ Shall provide method to perform error threshold checking at file, pack or internal file header/trailer and
record levels.0% compliant
8.2.1.1.8.2
+ Shall provide method to validate usage record fields for proper format and content per company business
rules and industry guidelines.0% compliant
8.2.1.1.8.3
+ Shall provide method to perform record assembly/creation when a source record is used to generate one
or multiple resulting records for down stream processing.0% compliant
8.2.1.1.8.4 + Shall provide method to process recycle usage only.0% compliant
8.2.1.1.8.5 + Shall provide method to identify and populate rejects/returns with user defined error codes.0% compliant
8.2.1.1.8.6 + Shall provide method to reset all files to reprocess an entire usage stream.0% compliant
8.2.1.1.8.7 + Shall provide method to verify originating and terminating locations, when needed.0% compliant
8.2.1.1.8.8 + Shall provide method to identify and validate the usage owner. (ACNA. CIC, OCN, etc.)0% compliant
8.2.1.1.8.9
+ Shall provide method to populate usage record derived fields. (EMI compliant, geography specific,
exceptions, etc.)0% compliant
8.2.1.1.8.10
+ Shall provide method to perform account verification and guiding of usage to appropriate cycle and/or
pricing plan.0% compliant
8.2.1.1.8.11 + Shall provide method to perform number portability guiding.0% compliant
8.2.1.1.8.12 + Shall provide method to identify and combine long duration calls for pricing.0% compliant
8.2.1.1.8.13
+ Shall provide method for an authorized user to define multiple output records for each type of input
record.0% compliant
8.2.1.1.8.14 + Shall provide method to guide records to internal (downstream) and external (Outbound) sources.0% compliant
8.2.1.2 • Video
8.2.1.2.1 – PPV 0% compliant
8.2.1.2.2 – VOD 0% compliant
8.2.1.3 • Data/Internet
8.2.1.3.1 – Bandwidth used 0% compliant
8.2.1.3.2 – Storage used 0% compliant
8.2.1.3.3 – Email accounts used 0% compliant
8.2.2
Shall provide method to perform on demand, event initiated and scheduled capture and/or receipt of usage
information from multiple locations.0% compliant
8.2.3 Shall provide method to mediate packet based usage.0% compliant
8.2.4 Shall provide method to translate raw usage records into the desired format(s) for downstream processing.0% compliant
8.2.5 Shall provide method to manually input usage records.0% compliant
8.2.6 Shall provide method to monitor collection devices real-time 0% compliant
8.2.7 Shall provide method for user to perform ad hoc reporting.0% compliant
8.2.7.1 • Shall provide method to validate all files for proper identification/naming, format and completeness.0% compliant
8.2.7.2
• Shall provide method to perform multiple level editing when ever possible. (i.e. will identify every error
condition that exists in each record)0% compliant
8.2.7.3 • Shall provide method for user to define error codes and message phrases for erred usage.0% compliant
8.2.7.4
• Shall provide method to perform on demand and scheduled recycling error cap. Shall provide method to
reprocess erred usage.0% compliant
8.2.7.5 • Shall provide method for user to define mass change for error correction.0% compliant
8.2.7.6 • Shall provide method to provide statistical information to Revenue Assurance.0% compliant
8.2.7.7 • Shall provide method for user to define error codes and message phrases for erred usage.0% compliant
8.2.7.8 • Shall provide method to review unbilled transactions 0% compliant
8.2.7.9 • Fraud Detection in real-time.0% compliant
8.3 Outbound File Processing and Delivery
8.3.1 Shall provide method to accept outbound usage files from usage processing and billing systems.0% compliant
8.3.2
Shall provide method to guide and package (internal labels, formatting, sequencing, etc.) based upon user
defined processing indicators and parameters. (rejects/returns, reprocessed, normal, etc.)0% compliant
8.3.3
Shall provide method to suspend and/or hold outbound files prior to packaging and notifies user when
required guiding information is not provided.0% compliant
8.3.4 Shall provide method to perform record packing in accordance with EMI guidelines.0% compliant
8.3.5
Shall provide method to perform record packaging for local/IntraLATA specific access like or revenue
settlement processing in accordance with geographic guideline.0% compliant
8.3.6 Shall provide method to provide file transmittal information for each file.0% compliant
8.3.7 Shall provide method to provide statistical information to Revenue Assurance.0% compliant
8.4 Transaction Pricing
8.4.1
Shall provide method to price voiced switched circuit and packet based usage products by carrier and
company parameters.0% compliant
8.4.2 Shall provide method to price for all jurisdictions 0% compliant
8.4.3
Shall provide method to price for distance/mileage based, band/zone based and point-to-point for occurrence
and usage sensitive records.0% compliant
8.4.4 Shall provide method to price date/time effective and discontinued.0% compliant
8.4.5
Shall provide method to price voice calls for one or multiple rate periods (rate period specific billing) for the
same call / record.0% compliant
8.4.6
Shall provide method to price voice calls by rate class and message type (of call) including operator handled
surcharges.0% compliant
8.4.7 Shall provide method to price voice calls by account code and/or authorization code.0% compliant
8.4.8 Shall provide pricing of transactional (usage) elements based on:
8.4.8.1 • Peg Count (cost per transaction)0% compliant
8.4.8.2 • On demand services such as Pay Per View and Video on Demand.0% compliant
8.4.8.3 • Mileage (distance sensitive)0% compliant
8.4.8.4 • Duration (length of transaction)0% compliant
8.4.8.5 • Type of transaction (DA, OPH, etc.)0% compliant
8.4.8.6 • Jurisdiction (intra/inter LATA and state)0% compliant
8.4.8.7 • Zone (Mileage based)0% compliant
8.4.8.8 • Zone (Geographic based - e.g. NPA-NXX, country code, country and city code)0% compliant
8.4.8.9 • Time of Day 0% compliant
8.4.8.9.1 – Bandwidth (packet count)0% compliant
8.4.9 Shall provide method to price combinations listed above.0% compliant
8.4.9.1 • Shall provide method to reprice individual transactions based on product parameters 0% compliant
8.4.9.2 • Shall provide method to price local and long distance usage.0% compliant
8.4.9.3
• Shall provide method to identify and store local/IntraLATA specific access like or revenue settlement
information.0% compliant
8.4.9.4
• Shall provide method for user to access and modify local/IntraLATA specific access like or revenue
settlement information in real-time.0% compliant
8.4.9.5 • Shall provide method to access taxes information in real-time.0% compliant
8.5 Taxing
8.5.1 Shall provide method to tax price elements based on jurisdictions 0% compliant
8.5.2 Shall provide method to calculate and store at least 10 tax jurisdictions per customer 0% compliant
8.5.3 Shall provide method to determine tax jurisdictions from address 0% compliant
8.5.4 Shall provide method to determine if price element is regulated or unregulated 0% compliant
8.5.5
Shall provide method to determine if customer or service is tax exempt, provide report listing all tax exempt
customers 0% compliant
8.5.6 Tax tables and methodology shall be kept current 0% compliant
8.5.7 Shall provide method to tax domestic and international charges 0% compliant
8.6 Invoicing
8.6.1 Account Hierarchy Billing
8.6.1.1
• Shall provide a minimum of six levels of billing hierarchy. (e.g. Company, Sub-company, Division, Group,
Master, Detail)0% compliant
8.6.1.2
• Shall provide roll-up and invoicing at all hierarchical levels (can invoice at a detail number or roll up charges
and invoice at a company level)0% compliant
8.6.1.3
• Shall provide multi-level invoicing (can invoice sub-companies 1, 2,and 3 individually; all other sub
companies invoiced at the company level)0% compliant
8.6.2 General
8.6.2.1 • Shall provide method to interface with the Pitney Bowes Series 8 inserter 0% compliant
8.6.2.2 • Shall provide method to build invoice format on-line with following sections:
8.6.2.2.1 – Summary page with:
8.6.2.2.1.1 + −Overall charges / balances by product within company, sub company, etc.0% compliant
8.6.2.2.1.2 + Taxes and surcharges 0% compliant
8.6.2.2.1.3 + Client information (address, contact info)0% compliant
8.6.2.2.1.4 + Bill cycle information (dates encompassed, remittance date, etc.)0% compliant
8.6.2.2.1.5 + Free form message section (min. 250 chars)0% compliant
8.6.2.3 • Remittance section 0% compliant
8.6.2.4 • Shall provide method to indicate if invoice is payable or only for record purposes 0% compliant
8.6.2.5 • Index to remaining pages 0% compliant
8.6.2.6 • Detailed page(s) based on product details (charges, discounts, waives, usage, etc. associated with product)0% compliant
8.6.2.7 • Shall provide method to put user logos on pages 0% compliant
8.6.2.8 • Shall provide method to print invoices in duplex mode 0% compliant
8.6.2.9
• Shall provide method to select if products elements are printed in detail or summarized (e.g. usage may be
summarized for a plan)0% compliant
8.6.2.9.1 – Shall provide method to publish invoice to web page for review 0% compliant
8.6.2.9.2
– Shall provide method to omit invoices from printing file for customers that wish to only receive electronic
bills.0% compliant
8.6.3 Billing Operations
8.6.3.1 • Shall provide automatic scheduling of billing cycles 0% compliant
8.6.3.2 • Shall provide automatic backup of data throughout process 0% compliant
8.6.3.3 • Shall provide rollback and restart throughout billing run.0% compliant
8.6.3.4 • Processes shall support user defined stop points during core processing for manual review 0% compliant
8.6.3.5 • Shall provide user to set error thresholds.0% compliant
8.6.3.6
• Shall provide method to segregate accounts with errors for later processing while continuing to process
remaining data 0% compliant
8.6.3.7 • Event notification and tracking shall be available real-time, on-line.0% compliant
8.6.3.8 • Shall provide method to run billing cycles without closing order entry system 0% compliant
8.6.3.9 • Shall provide method to produce operational reports detailing process statistics (e.g. bill register)0% compliant
8.7 Delinquent and Disconnect Processing
8.7.1 General
8.7.1.1
• Shall provide method to generate late notices (dunning letters) automatically based on late notice
methodology with at least the following user definable parameters.
8.7.1.1.1 – maximum balance not subject to disconnect (e.g. $5.00)0% compliant
8.7.1.1.2
– Shall provide a method to set up different maximum balance not subject to disconnect based on service
type, location, etc.0% compliant
8.7.1.1.3 – Number of days past due 0% compliant
8.7.1.2 • Shall provide method to create up to 3 separate notices 0% compliant
8.7.1.3 • Shall provide method to create disconnect list based on user defined disconnect criteria
8.7.1.4 • Shall provide method to automatically generate disconnect orders from delinquent list 0% compliant
8.7.1.5 • Shall provide method to allow review of disconnect list prior to generating disconnect orders 0% compliant
8.7.1.6 • Shall provide method to remove account from disconnect list manually 0% compliant
8.8 Revenue Assurance
8.8.1 General
8.8.1.1
• Shall provide method to auto-balance each billing run to the previous billing run. (e.g. tracks adds,
changes, deletes and previous balances and verifies that all revenue is accountable)0% compliant
8.8.1.2 • Shall provide method to report out of balance situation with supporting detail to facilitate resolution.0% compliant
8.8.1.3
• Shall provide method to report detail of charges that fell out of bill cycle by reason and by point of entry
(source).0% compliant
8.8.1.4 • Shall provide method to provide an audit trail of all charges by point of entry (source) for each bill cycle.0% compliant
8.8.1.5 • Shall provide method to create user definable ad-hoc reports 0% compliant
8.8.2 Deposit management
8.8.2.1 • Shall provide method to house deposit for services 0% compliant
8.8.2.2 • Shall provide method to calculate interest on deposit 0% compliant
8.8.2.3 • Shall provide method to apply deposits and interest to payments 0% compliant
8.8.3 Payments
8.8.3.1 • Shall provide method to apply partial payments:
8.8.3.1.1 – Equally between billable elements 0% compliant
8.8.3.1.2 – Based on user defined percentages 0% compliant
8.8.3.1.3 – Based on type of element/priority (e.g. local charges are paid off before long distance)0% compliant
8.8.3.2 • Shall provide method to setup promise-to-pay schedules 0% compliant
8.8.3.3 • Shall provide method to manually apply credits or debits to accounts 0% compliant
8.8.3.4 • Shall provide method to accept remittances through:
8.8.3.4.1 – Bill pay 0% compliant
8.8.3.4.2 – Cash 0% compliant
8.8.3.4.3 – Check 0% compliant
8.8.3.4.4 – Coupon 0% compliant
8.8.3.4.5 – Credit/Debit card 0% compliant
8.8.3.4.6 – EFT 0% compliant
8.8.3.4.7 – Gift certificates/cards 0% compliant
8.8.3.4.8 – Money orders 0% compliant
8.8.3.4.9 – Pre-pay 0% compliant
8.8.3.4.9.1 + Pre-pay calling cards 0% compliant
8.8.3.5 • Shall provide method to accept and process prepay amounts applicable to:
8.8.3.5.1 – overall invoice 0% compliant
8.8.3.5.2 – specific service, package, or product 0% compliant
8.8.3.5.3 – flat amount over specified time period 0% compliant
8.8.3.6 • Ability to enter payments to a batch file during billing process and post after billing is complete.0% compliant
8.8.4 Credits / Refunds
8.8.4.1 • Shall provide method to apply credits to account balances:
8.8.4.1.1 – Automatically update balance when credit is applied 0% compliant
8.8.4.1.2 – Automatically update balance due amount to reflect credit amount immediately when credit is applied 0% compliant
8.8.5 Long Distance Processing
8.8.5.1 • Segregate and report unbillable CDRs - MOU, messages, revenue - by line 0% compliant
8.8.5.2 • Ability to post unbillables as errors are corrected 0% compliant
8.8.5.3 • Ability to delete unbillable CDRs after designated number of attempts to post 0% compliant
8.8.5.4
• Ability to define and bill long distance calling plans, (e.g. 200 minutes @ $12.95, unlimited minutes @
$29.50)0% compliant
8.8.5.5 • Ability to automatically save processed files in designated folder 0% compliant
8.8.5.6 • Ability to automatically drop duplicate CDRs 0% compliant
8.9 Reporting
8.9.1 General
8.9.1.1 • Shall provide standard reports on demand. List standard reports.0% compliant
8.9.1.2
• Shall provide method to interface with third-party reporting packages (e.g. Crystal reports, other ODBC
compliant connections)0% compliant
8.9.1.3
• Shall provide method to create reports at defined hierarchical levels or allow for rollup of sub-levels for
account level reports 0% compliant
8.1 History
8.10.1 General
8.10.1.1 • Shall provide historical retrieval of customer information 0% compliant
8.10.1.2 • Shall provide historical retrieval of all billing data 0% compliant
8.10.1.3 • Shall provide historical retrieval of all ordering information for an account 0% compliant
8.10.1.4 • Shall provide on-line retrieval of historical invoices 0% compliant
8.10.1.5 • Shall provide user defined ad-hoc reporting of historical data 0% compliant
8.11 Plant Records
8.11.1 General
8.11.1.1 • Shall provide method to interfaces with account information.0% compliant
8.11.1.2 • Shall provide method to interfaces with Ordering systems 0% compliant
8.11.1.3 • Shall provide method to interfaces with Product information 0% compliant
8.11.1.4 • Shall provide method to interface with financial/inventory systems 0% compliant
8.11.2 Plant information
8.11.2.1 • Shall provide method to store plant information for voice, video and data services.
8.11.2.1.1 – Inside Plant
8.11.2.1.1.1 + Line cards 0% compliant
8.11.2.1.1.2 + Distribution Frame and/or Node 0% compliant
8.11.2.1.2 – Outside Plant
8.11.2.1.2.1 + Optical ring Facilities to Nodes on the ring and Trunks to Remotes 0% compliant
8.11.2.1.2.2 + Nodes on the ring and Remotes 0% compliant
8.11.2.1.2.3 + Amplifies and Repeaters 0% compliant
8.11.2.1.2.4 + Optical Facilities, Trunks and drops to building entrance facilities, concentrators, pedestals and NIDs.0% compliant
8.11.2.1.2.5 + Building entrance facilities, concentrators, pedestal and NIDs.0% compliant
8.11.2.2 • ONT 0% compliant
8.11.2.2.1 – Serial number 0% compliant
8.11.2.2.2 – Subscriber Line ID for ONT recognition 0% compliant
8.11.2.2.3 – OLT Shelf 0% compliant
8.11.2.2.4 – Slot 0% compliant
8.11.2.2.5 – PON Port 0% compliant
8.11.2.2.6 – Pon ID 0% compliant
8.11.2.2.7 – VLAN ID 0% compliant
8.11.2.2.8 – Router ID 0% compliant
8.11.2.2.9 – QoS and IP Filter template ID 0% compliant
8.11.2.3 • Shall provide method to create a new local facility record in real-time.0% compliant
8.11.2.4 • Shall provide method to change an existing local facilities records in real-time.0% compliant
8.11.2.5 • Shall provide method to suspend an existing local facility record in real-time.0% compliant
8.11.2.6
• Shall provide method to edit service order information for completeness and provide feedback to Ordering
system.0% compliant
8.11.2.7
• Shall provide method to identify when an order requires engineering to build new facilities to fulfill request
for service.0% compliant
8.11.2.8
• Shall provide method to provide the Ordering system an existing service area inventory representation.
(graphical map, street address facility locator, building riser capacity, etc.)
NOTE: Could be combine with a Community Property Records function/system.0% compliant
8.11.2.9 • Shall provide method to provide FOC to Ordering system.0% compliant
8.11.2.9.1
– Shall provide method to perform mass record updates to implement company level changes and industry
level changes. (CLLIs, NPA splits, etc.)0% compliant
8.11.3 Inventory - if internal to proposed solution
8.11.3.1 • Shall provide method to support telephone business and residential equipment.0% compliant
8.11.3.2 • Shall provide method to support video business and residential equipment.0% compliant
8.11.3.3 • Shall provide method to support data business and residential equipment.0% compliant
8.11.3.4 • Shall provide method to support local and interconnection FTTH/B network equipment.0% compliant
8.11.3.5 • Shall provide method to update inventory levels through order/disconnect processes 0% compliant
8.11.3.6 • Shall provide method to support auto reordering of equipment based on reorder levels 0% compliant
8.11.3.7 • Shall provide method to support bar code or electronic labeling of in-store, truck and warehouse items.0% compliant
8.11.3.8 • Shall provide method to track inventory based on location (store, truck, warehouse, repair, etc.)0% compliant
8.11.3.9 • Shall provide method to update Financial information to reflect status of inventory 0% compliant
8.12 Trouble Ticket
8.12.1 General
8.12.1.1 • Shall provide method for authorized users to enter and track trouble tickets.0% compliant
8.12.1.2 • Shall provide method for authorized users to define trouble tickets codes, severity codes, priority codes 0% compliant
8.12.1.2.1
– Shall provide method for authorized users to define multi-level problem description codes (e.g. Cable -->
Fuzzy Picture --> On one channel) - Hierarchy tree 0% compliant
8.12.1.3 • Shall provide method for authorized customer support and engineering personnel to view tickets by:
8.12.1.3.1 – Ticket Number 0% compliant
8.12.1.3.2 – Date 0% compliant
8.12.1.3.3 – Client 0% compliant
8.12.1.3.4 – Assigned technician 0% compliant
8.12.1.3.5 – Client address/location 0% compliant
8.12.1.3.6 – Network component / access point 0% compliant
8.12.1.3.7 – Trouble Ticket code 0% compliant
8.12.1.3.8 – Severity Category 0% compliant
8.12.1.3.9 – Automatic escalation of ticket based on
8.12.1.3.9.1 + Priority/severity 0% compliant
8.12.1.3.9.2 + Time in system 0% compliant
8.12.1.4
• Shall provide method for authorized users to create and display outage information on all trouble ticket
interfaces.0% compliant
8.12.1.4.1
– Shall provide method for automatic generation and activation of outage notification to all trouble ticket
interfaces based on number of tickets open in specified geographic location, plant facility, or other criteria.0% compliant
8.12.1.4.2
– Shall provide method for automatic notification via text messaging or email alert of outages or other
threshold items (e.g. pre-defined number of open tickets in certain area, etc.)0% compliant
8.12.1.5
• Shall provide a method to pause a trouble ticket. (for purposes of reporting open trouble ticket length
when a customer requests that a ticket be delayed or put on hold)0% compliant
8.12.1.6 • Shall provide a method to view trouble ticket lists by the following criteria:
8.12.1.6.1 – Geographic location 0% compliant
8.12.1.6.2 – Plant facility information grouping (e.g. node, line segment)0% compliant
8.12.1.6.3 – Network facility information (e.g. service group, line card)0% compliant
8.12.1.6.4 – Problem type 0% compliant
8.12.1.6.5 – Problem severity 0% compliant
8.12.1.6.6 – Length of time open 0% compliant
8.12.1.6.7 – City, State 0% compliant
8.12.1.6.8 – Customer number / ID range 0% compliant
8.12.1.6.9 – Customer type (Business, Residential, Government, etc.)0% compliant
8.12.1.7 • Shall provide a method to create and enforce scheduling limits based on trouble ticket assignee 0% compliant
8.12.1.8
• Shall provide a method to assign trouble tickets to technicians based on availability, geographic location,
and skill 0% compliant
8.12.1.9 • Shall provide method to see pending service orders such as non-payment disconnect 0% compliant
8.12.1.10 • Shall provide method to see account status (active, disconnect, etc.)0% compliant
8.12.1.11 • Shall provide method to see CPNI information from trouble ticket interface.0% compliant
8.12.1.12
• Shall provide method to show special account notes or information (e.g. "call before going onsite",
"dangerous animal onsite", etc.)0% compliant
8.12.1.13
• Shall provide method for system to automatically generate credits requests based on trouble ticket
disposition.0% compliant
8.12.1.14 • Shall provide method to report trouble ticket activity using the same view criteria. (see above)0% compliant
8.12.1.15 • Shall provide method to report trouble ticket trends.0% compliant
8.12.1.16 • Shall provide method to provide users diagnostic aids on the systems.0% compliant
8.12.1.17 • Shall provide method to bring up plant and maps associated with trouble account/location.0% compliant
8.12.1.18 • Shall provide method to interfaces with CRM for account information.0% compliant
8.12.1.18.1
– Shall provide method to interfaces with Billing Systems for Accounts Receivable (if part of billing) and Billed
History.0% compliant
8.12.1.18.2 – Shall provide method to interfaces with Accounting Systems if Accounts Receivable not part of billing.0% compliant
8.12.1.18.3 – Shall provide method to interfaces with Plant information.0% compliant
8.12.1.18.4 – Shall provide method to interfaces with Product information.0% compliant
8.12.1.18.5 – Shall provide method to interfaces with Work Management system (see item 18.1)0% compliant
8.13 Wholesale Billing
8.13.1 General
8.13.1.1 • Shall provide method to support multiple billing cycles with different billing dates.0% compliant
8.13.1.2 • Shall provide method for user to perform ad hoc reporting.0% compliant
8.13.1.3 • Shall provide method for user to define flexible controls to process and view wholesale billing information.0% compliant
8.13.1.4 • System is compliant with the BOS and/or SECAB guidelines.0% compliant
8.13.1.5
• Shall provide method to interface with external and internal usage data source providers. (Call
Collection/Call Mediation, Inbound, Outbound)0% compliant
8.13.1.6
• Shall provide method to interface with Accounting Systems (Accounts Receivable- if not part of billing,
General Ledger, Margin Analysis)0% compliant
8.13.1.7 • Shall provide method to interface with CRM.0% compliant
8.13.1.8 • Shall provide method to interface with Industry Reference information.0% compliant
8.13.1.9 • Shall provide method to interface with Product information.0% compliant
8.13.1.9.1 – Shall provide method to interface with Revenue Assurance.0% compliant
8.13.1.9.2
– Shall provide method to interface with third party tax information or provides a user maintainable
alternative.0% compliant
8.13.2 File and Record Acceptance
8.13.2.1 • Shall provide method to input manual MOU. (can be used to correct processing errors)0% compliant
8.13.2.2 • Shall provide method to accept and process EMI files and packs of category 11 AURs.0% compliant
8.13.2.3 • Shall provide method to accept and process EMI files and packs of category 11 SURs.0% compliant
8.13.2.4 • Shall provide method to accept and process packet based usage.0% compliant
8.13.2.5 • Shall provide method to perform file and record gap detection.0% compliant
8.13.2.6 • Shall provide method to perform file and record duplicate detection.0% compliant
8.13.2.7
• Shall provide method to translate non-standard usage records into the desired format(s) for downstream
processing.0% compliant
8.13.3 Usage Error Management
8.13.3.1 • Shall provide method to validate all files for proper identification/naming, format and completeness.0% compliant
8.13.3.2
• Shall provide method to perform error threshold checking at file, pack or internal file header/trailer and
record levels.0% compliant
8.13.3.3
• Shall provide method to validate usage record fields for proper format and content per company business
rules and industry guidelines.0% compliant
8.13.3.4 • Shall provide method to disposition incomplete or incorrect records to an error recycle process.0% compliant
8.13.3.5
• Shall provide method to perform multiple level editing when ever possible. (i.e. will identify every error
condition that exists in each record)0% compliant
8.13.3.6
• Shall provide method to identify usage with an invalid or unknown Account or CIC by naming the source
file, traffic direction, the record count, MOUs and the date/time range.0% compliant
8.13.3.7
• Shall provide method to perform on demand and scheduled recycling error cap Shall provide method to
reprocess erred usage.0% compliant
8.13.3.8 • Shall provide method for user to define error codes and message phrases for erred usage.0% compliant
8.13.3.9 • Shall provide method for user to define and perform mass changes for usage error correction.0% compliant
8.13.3.9.1 – Shall provide method to provide statistical information to Revenue Assurance.0% compliant
8.13.4 Control and Reference Information
8.13.4.1 • Product catalog file/data structure shall provide multiple rate elements per product.0% compliant
8.13.4.2
• Shall provide method to perform on-line, date/time effective modifications to the tariff for product, pricing
and discount changes.0% compliant
8.13.4.3
• Shall provide method to perform on-line, date/time effective modifications to the MPB information, BP
and/or ownership percentages and mileage information.0% compliant
8.13.4.4
• Shall provide method to perform on-line, date/time effective modifications to tables for usage identification.
(NPA-NXXs, CLLI, LRN, etc.)0% compliant
8.13.4.5 • Shall provide method to perform on-line, date/time effective modifications to factors. (PIU, PIL, PLU, PCL)0% compliant
8.13.4.6 • Shall provide method to query on-line all control and reference information.0% compliant
8.13.4.7
• Shall provide method to perform on-line modification to industry reference information, if needed. (LERG,
NECA tariff #4, TPM, etc.)0% compliant
8.13.4.8
• Shall provide method to perform third party tax information updates and/or provides on-line, date/time
effective modification to tax information.0% compliant
8.13.4.9
• Shall provide method to interface with original data sources, whenever possible, for automated reference
information updates.0% compliant
8.13.5 Factors Application
8.13.5.1
• Shall provide method to apply date/time sensitive factors at multiple control levels. (customer/account, CIC,
product, jurisdiction, etc.)0% compliant
8.13.6 Summary Usage Record Generation
8.13.6.1
• Shall provide method to summarize AURs into daily and/or monthly SURs based upon user defined
parameters.0% compliant
8.13.6.2
• Shall provide method to create industry compliant EMI category/group 1150 MPB SURs for SBCs based
upon user-defined parameters.0% compliant
8.13.6.3
• Shall provide method to process industry compliant EMI category/group 1150 MPB SURs from an IBC based
upon user defined parameters.0% compliant
8.13.7 Facility Billing Preparation
8.13.7.1 • Shall provide method to back out a complete billing cycle. (reset to pre-bill status)0% compliant
8.13.7.2 • Shall provide method for user to define the bill date, start date, through date and due date for each cycle.0% compliant
8.13.7.3
• Shall provide method to define billing cycle options that are time (weekly, monthly, quarter, on-demand)
and/or circumstance (revenue threshold, circuit count threshold, first bill, etc.) driven.0% compliant
8.13.7.4 • Shall provide method to perform circuit’s accuracy and verification prior to billing.0% compliant
8.13.8 Facility Billing Process
8.13.8.1 • Shall provide method to apply recurring and non-recurring charges.0% compliant
8.13.8.2
• Shall provide method to perform back-billed calculations for recurring and non-recurring charges based
upon effective date.0% compliant
8.13.8.3 • Shall provide method to bill for special construction.0% compliant
8.13.8.4 • Shall provide method to apply adjustments and provides the detail of adjustments applied.0% compliant
8.13.8.5 • Shall provide method to calculate and apply OC&Cs as well as providing the detail of OC&Cs applied 0% compliant
8.13.8.6 • Shall provide method to calculate and apply surcharges where applicable.0% compliant
8.13.8.7
• Shall provide method to calculate and/or apply pricing discount plans, time of day discounting, promotions
and waivers.0% compliant
8.13.8.8 • Shall provide method to apply past and future effective dates for discounts and promotions.0% compliant
8.13.8.9 • Shall provide method to bill High Capacity facilities.0% compliant
8.13.8.9.1 – Shall provide method to calculate and apply mileage for rating.0% compliant
8.13.8.9.2
– Shall provide method to create one or multiple invoices for a customer by geographic location associated
with the account and/or CIC.0% compliant
8.13.8.9.3
– Shall provide method to perform on-demand billing at any time during the month for one or multiple
customers based upon user-defined criteria.0% compliant
8.13.8.9.4 – Shall provide method for re-running a billing cycle using only archived data and product information.0% compliant
8.13.8.9.5 – Shall provide method for re-running a billing cycle using current data and product information.0% compliant
8.13.9 Usage Billing Preparation
8.13.9.1 • Shall provide method to back out a complete billing cycle. (reset to pre-bill status)0% compliant
8.13.9.2 • Shall provide method for user to define the bill date, start date, through date and due date for each cycle.0% compliant
8.13.9.3
• Shall provide method to define billing cycle options that a time (weekly, monthly, quarter, on-demand)
and/or circumstance (revenue threshold, MOU amount threshold, first bill, etc.) driven.0% compliant
8.13.9.4 • Shall provide method to perform usage accuracy and verification prior to billing.0% compliant
8.13.9.5 • Shall provide method for Usage Billing Processing 0% compliant
8.13.9.6 • Shall provide method to define a charge type and the calculation(s) needed to apply the charges.0% compliant
8.13.9.7 • Shall provide method to apply LIDB charges.0% compliant
8.13.9.8 • Shall provide method to apply CCL charges, where still applicable.0% compliant
8.13.9.9 • Shall provide method to apply end office element charges.0% compliant
8.13.9.9.1 – Shall provide method to apply 800 database query charges.0% compliant
8.13.9.9.2 – Shall provide method to apply Local Transport charges.0% compliant
8.13.9.9.3 – Shall provide method to apply Operator Transfer charges.0% compliant
8.13.9.9.4 – Shall provide method to apply recurring and non-recurring charges.0% compliant
8.13.9.9.5
– Shall provide method to perform back-billed calculations for recurring and non-recurring charges based
upon effective date.0% compliant
8.13.9.9.6 – Shall provide method to apply adjustments and provide the detail of adjustments applied.0% compliant
8.13.9.9.7 – Shall provide method to calculate and apply OC&Cs as well as providing the detail of OC&Cs applied 0% compliant
8.13.9.9.8 – Shall provide method to calculate and apply surcharges where applicable.0% compliant
8.13.9.9.9
– Shall provide method to calculate and/or apply pricing discount plans, time of day discounting, promotions
and waivers.0% compliant
8.13.9.9.10 – Shall provide method to apply future and past effective dates for discounts and promotions.0% compliant
8.13.9.9.11 – Shall provide method to rate access for wireless usage.0% compliant
8.13.9.9.12 – Shall provide method to perform MPB calculations, where still applicable.0% compliant
8.13.9.9.13
– Shall provide method to perform MOU access rating by rate schedule, rate period, mileage, mileage band,
jurisdiction, feature group, routing, call type and V&H coordinates.0% compliant
8.13.9.9.14 – Shall provide method to summarize and displays carrier usage by originating and terminating categories.0% compliant
8.13.9.9.15
– Shall provide method to summarize and display carrier usage by jurisdiction and rate category. (e.g.
transport, end office, CCL charges)0% compliant
8.13.9.9.16
– Shall provide method to create one or multiple invoices for a customer by geographic location associated
with the account and/or CIC.0% compliant
8.13.9.9.17
– Shall provide method to perform on-demand billing at any time during the month for one or multiple
customers based upon user-defined criteria.0% compliant
8.13.9.9.18 – Shall provide method for re-running a billing cycle using only archived data and product information 0% compliant
8.13.9.9.19 – Shall provide method for re-running a billing cycle using current data and product information.0% compliant
8.13.9.10 • Invoice Preparation
8.13.9.10.1
– Shall provide method to validate charges automatically and identify questionable or erroneous invoice
charges.0% compliant
8.13.9.10.2 – Shall provide method to apply prompt payment discount.0% compliant
8.13.9.10.3 – Shall provide method to calculate late fees and/or penalties.0% compliant
8.13.9.10.4 – Shall provide method to provide a convergent invoice with other products.0% compliant
8.13.9.11 • Invoice Processing and Taxing
8.13.9.11.1
– Shall provide method to provide financial information to an Accounting System(s) by company and/or cycle
and jurisdiction.0% compliant
8.13.9.11.2 – Shall provide method to calculate and apply taxes to charges for multiple jurisdictions.0% compliant
8.13.9.11.3 – Shall provide method to exempt customers with proper certification from taxation.0% compliant
8.13.9.11.4
– Shall provide method to invoice in multiple formats such as electronic (BOS, EDI, SECAB, web based,
email) and paper.0% compliant
8.13.9.11.5
– Shall provide method to create an invoice capable of a minimum of supporting more than two levels of
billing hierarchy. (e.g. Company, Sub-company, Division, Group, Master, Detail)0% compliant
8.13.9.11.6 – Shall provide method for user to define held bills and bill intercept criteria for Customer Service review.0% compliant
8.13.9.11.7 – Shall provide method to calculate subtotals at the state level.0% compliant
8.13.9.11.8
– Shall provide method to calculate a total balance due including current and past due amounts for the new
balance due date.0% compliant
8.13.9.11.9
– Shall provide method to calculate and reports tax information by jurisdiction, taxing authority and by tax
area.0% compliant
8.13.9.11.9.1 + Shall provide for payment Processing, A/R and Disputes 0% compliant
8.13.9.11.9.2
+ Shall provide method to receive and apply advanced, current and past due payments using a GUI and/or a
batch process.0% compliant
8.13.9.11.9.3 + Shall provide method to age accounts receivables and provide treatment support.0% compliant
8.13.9.11.9.4
+ Shall provide method to enter deposits and calculates interest on deposits in accordance with state
requirements.0% compliant
8.13.9.11.9.5 + Shall provide method to maintain credit class/score, payment history and treatment history.0% compliant
8.13.9.11.9.6
+ Shall provide method to maintain management defined approval levels for adjustments and refund
requests.0% compliant
8.13.9.11.9.7 + Shall provide method to on-line inquire customer account and service and equipment information.0% compliant
8.13.9.11.9.8
+ Shall provide method to on-line inquire billing data, including invoices, payment advanced payments,
deposits and adjustments.0% compliant
8.13.9.11.9.9 + Shall provide method to on-line inquire credit information, payment history, treatment history and status.0% compliant
8.13.9.11.9.10 + Shall provide method to enter and notate disputes and other credits and debits.0% compliant
8.13.9.11.9.11 + Shall provide method to suspend impact of dispute on balance due while dispute is under investigation.0% compliant
8.13.9.11.9.12 + Shall provide method to process refund requests.0% compliant
8.13.9.11.9.13 + Shall provide method to apply settlements at line item level.0% compliant
8.13.9.11.9.14 + Shall provide method to perform mass adjustments.0% compliant
8.13.9.12 • Revenue Assurance
8.13.9.12.1
– Shall provide method to provide automated balancing and controls; controls release of batched
transactions.0% compliant
8.13.9.12.2 – Archive, Retention and Retrieval 0% compliant
8.13.9.12.3 – Shall provide method to automatically or on-demand archive billing data.0% compliant
8.13.9.12.4
– Shall provide method to retain the details of the invoice on-line for a user defined period (min. 6 months)
for review, historical reporting, trending and analysis.0% compliant
8.13.9.12.5 – Shall provide method to comply with Federal and State statutes of limitation for invoice retention.0% compliant
8.13.9.12.6
– Shall provide method to support multiple mediums for efficient operations, flexible storage and retrieval
procedures.0% compliant
8.14 Solution Modules and Pricing
8.14.0.1
• Modules - Please submit a module by module list for proposed solution with associated pricing. Please
signify what pricing is based on (e.g. module price, seat licenses, combination, etc.). Please indicate if
module is part of base proposal or optional.0% compliant
8.14.0.2 • Installation - Please submit expected installation costs including needed hardware, labor, etc.0% compliant
8.14.0.3
• Yearly maintenance costs - Please submit a module by module list for proposed solution with associated
pricing, as well as, any hardware maintenance costs 0% compliant
8.15 Warranty
8.15.0.1
• Solution shall be covered by a minimum of a one year warranty commencing on the acceptance date. This
warranty shall also include unlimited 24x7 technical support.0% compliant
8.16 Training and Support
8.16.0.1 • Complete training of all necessary personnel for all proposed applications.0% compliant
8.16.0.2 • Shall provide method to revert back to prev. version if problems with current version 0% compliant
9 System Architecture
9.1 System Basic Functions
9.1.1 System provides logs of the following for all user and system activity
9.1.1.1 • Location 0% compliant
9.1.1.2 • Application function (e.g. add, change, delete, etc.)0% compliant
9.1.1.3
• Shall provide method to review in process screens by supervisor and/or Shall provide method to update
user screen remotely while user at screen 0% compliant
9.2 Security
9.2.1 System shall provide user access based on following profiles:
9.2.1.1 • Screen (access based on screen within modules)0% compliant
9.2.1.2 • Field (access based on field within screen)0% compliant
9.2.2 Shall provide setup of the following user rights for above profiles:
9.2.2.1 • Update (read, change only)0% compliant
9.2.2.2 • Delete (read, delete only)0% compliant
9.2.2.3 • Operation (execute only)0% compliant
9.2.2.4 • Read Only 0% compliant
9.2.2.5 • Any combination of the above 0% compliant
9.2.3 Shall provide real-time monitoring of users logged onto the system by user id, system, module, screen 0% compliant
9.2.4 Clients shall set/update client user ids/passwords through IVR and Web portals.0% compliant
9.3 Application Basic Functionality
9.3.1
System shall provide wireless products if a quad play strategy of wire line voice services, wireless, data
services, and video services is desired at a later time.0% compliant
9.3.2
Shall provide a method to customize the GUI interface per user to allow for increased efficiency when
navigating the menus and screens. (For example: allow for a "Favorites" menu/navigation bar of common
screens to be customized by each user)0% compliant
9.3.3
Shall provide a method to view multiple customer accounts at the same time for comparison operations while
maintaining distinction between the accounts (customer name, address, account number visible).0% compliant
9.3.4 All customer related screens can access customer records through a minimum of:
9.3.4.1 • Contact number 0% compliant
9.3.4.1.1 – Passport number 0% compliant
9.3.4.1.2 – Tax ID (for businesses)0% compliant
9.3.4.1.3 – activation date 0% compliant
9.3.4.1.4 – deactivation date 0% compliant
9.3.4.1.5 – features/options 0% compliant
9.3.4.1.6 – A/R balance 0% compliant
9.3.4.1.7 – order date 0% compliant
9.3.4.1.8 – ordering agent 0% compliant
9.3.4.1.9 – equipment id (set top box, IP address, etc.)0% compliant
9.3.4.2 • Shall provide method to generate customer alerts based on, a minimum:
9.3.4.2.1 – Balance amount 0% compliant
9.3.4.2.2 – Account status 0% compliant
9.3.4.2.3 – Marketing messages 0% compliant
9.3.4.2.4 – Assigned products 0% compliant
9.3.4.2.5 – Outstanding trouble tickets 0% compliant
9.3.4.2.6 – Geographic location 0% compliant
9.4 Documentation / Help System
9.4.1 On-line real-time access to user documentation.0% compliant
9.4.2 Shall provide method to search help using keywords, topics, etc.0% compliant
9.4.3
Integration from help system to applications to allow user to quick link to affected modules, screens, and
fields 0% compliant
9.4.4 Each application has on-line help access at
9.4.4.1 • module 0% compliant
9.4.4.2 • screen level 0% compliant
9.4.4.3 • field level 0% compliant
10 Web Capability
10.0.1 System contains Web portals for:
10.0.1.1 • customer self care
10.0.1.1.1 – Shall provide method for clients to order any web selected service or package, user id/passwords, etc.0% compliant
10.0.1.1.2
– Shall provide method to indicate what services, packages, features, order types etc. can be accessed
through web 0% compliant
10.0.1.1.3
– Shall provide method to direct customers to customer service for packages or services offered by company
but cannot be ordered through web (e.g. account disconnects, T-1 service)0% compliant
10.0.1.1.4 – Shall provide method for clients to make changes to current services 0% compliant
10.0.1.1.5
– Shall provide method for clients to make changes to profile information (e.g. contact phone, payment
method, etc.)0% compliant
10.0.1.2 • Bill review and payment
10.0.1.2.1
– Shall provide method to dispute charges by selecting charge(s) online and have dispute sent to customer
support for review and follow-up 0% compliant
10.0.1.2.2
– Shall provide method for users of the web portal to make payment on accounts via electronic check, credit
card.0% compliant
10.0.1.2.3 – Shall provide method for users to make payment on the deposit as well as balance of the account 0% compliant
10.0.1.2.4
– Shall provide method for clients to apply gift certificates and promotional codes towards payment. System
would verify validity of certificates and codes prior to acceptance.0% compliant
10.0.1.3 • Shall provide method to put in links to other Web sites if desired 0% compliant
10.0.1.4 • Reporting
10.0.1.4.1
– Shall provide method for clients to generate and download reports from current and past invoices based on
data contained in invoices (e.g. products, taxes, LD, etc.)0% compliant
10.0.2 Other
10.0.2.1
• Shall provide a method to automatically generate flow-through provisioning process for predefined list of
services when changed via web portal 0% compliant
10.0.2.2
• Shall provide a method to indicate on all orders and actions generated in the system that it originated from
the web portal 0% compliant
10.0.2.3 • Shall provide a method for a customer to sign up for new service via the web portal 0% compliant
10.0.2.3.1 – Shall provide a method for automatically checking the customer's credit as part of the order process 0% compliant
10.0.2.3.2
– Shall provide a method to calculate all appropriate sign-up charges and deposits based on credit and
business practices 0% compliant
10.0.2.4 • Shall provide a method to link special promotions to the web portal to encourage conversion rates 0% compliant
10.0.2.5 • Shall provide a method to disallow downgrade of service if configured to do so.0% compliant
10.0.2.6
• Shall provide a method to allow the user to access call detail records such as long distance, as well as pay
per view purchases 0% compliant
10.0.2.7
• Shall provide a method for the customer to interact with CSR and or help desk agents via web based chat
session (feature should be configurable to allow or disallow this feature based on availability of agents, time,
date)0% compliant
11 Products
11.1 General:
11.1.1
Shall provide method to set elements, packages, product, etc. sets to be defaulted and/or filtered (i.e. only
elements applicable to client are visible for selection) to customers meeting following criteria:
11.1.1.1 • Company 0% compliant
11.1.1.2 • Customer class (residential, business, MDU, etc.)0% compliant
11.1.1.3 • Community (location code)0% compliant
11.1.1.4 • City 0% compliant
11.1.1.5 • State 0% compliant
11.1.1.6 • Zip code 0% compliant
11.1.1.7 • Affinity code 0% compliant
11.1.1.8 • Product Class (adult, family, etc.)0% compliant
11.1.1.9 • Credit class 0% compliant
11.1.1.9.1 – Combination of above 0% compliant
11.1.1.10
• Shall provide the following non-transactional product types: (note: transactional product types described
within each service section below)
11.1.1.10.1 – daily recurring charge/credit 0% compliant
11.1.1.10.2 – quarterly recurring charge/credit 0% compliant
11.1.1.10.3 – yearly recurring charge/credit 0% compliant
11.1.1.10.3.1 + seasonal recurring charge/credit 0% compliant
11.1.1.10.3.2 + vacation recurring charge/credit 0% compliant
11.1.1.11 • Shall provide method to spread 1-time charges over user specified number of billing periods 0% compliant
11.1.1.12
• Shall provide method to recalculate product element pricing based on package components (e.g. receive
call waiting free if user selects caller id and call waiting also, else call waiting is $3.00)0% compliant
11.1.1.13 • Shall provide calculation of discounts methods on:
11.1.1.13.1
– Eligible versus non-eligible amounts defined as incorporation of non-qualified elements for discount
calculation (e.g. discount applied to all local measured traffic, however, discount calculated on overall usage
including LD, DA, etc.)0% compliant
11.1.1.13.2 – Time schedule (e.g. first 3 months of service, holidays, etc.)0% compliant
11.1.1.13.3 – Sliding scale (first month at 15%, month 2 at 10%, month 3 at 5%)0% compliant
11.1.1.13.3.1 + Length of time client stays with company 0% compliant
11.1.1.13.3.2 + Service Anniversary 0% compliant
11.1.1.13.3.3 + Geographic location (e.g. street, city, county/parish, state)0% compliant
11.1.1.13.3.4 + User defined based on client information (e.g. Birthday, Anniversary, etc.)0% compliant
12 Additional Data Elements
12.1 Fields:
12.1.1 Personal identification information
12.1.1.0.1 – Passport id 0% compliant
12.1.2 Contact information
12.1.2.1 • Contact phone number 2 0% compliant
12.1.2.2 • Contact fax 0% compliant
12.1.3 Minimum of 5 user definable demographic fields (e.g. age, male/female, etc.)0% compliant
12.1.3.1 • Directory listing 3 0% compliant
12.1.3.2 • Bill method
12.1.3.2.1 – FTP 0% compliant
12.1.3.3 • Account pop-up message (used to display account critical information)0% compliant
12.1.3.4 • Previous occupant information
12.1.3.4.1 – Contact phone number 1 0% compliant
12.1.3.4.2 – Contact e-mail 0% compliant
12.1.3.5 • Minimum of 10 user defined number and text fields 0% compliant
12.1.3.6
• Service Balances and Aging (charges, credits, adjustments, taxes/surcharges, penalties stored separately
for each aging level)0% compliant
12.1.3.7 • Driving instructions 0% compliant
13 Customer Relations Management (CRM)
13.0.1 Shall provide method to access the following customer information on-line:
13.0.2
Shall provide method to import data containing customer name, address, contact information from outside
research firms.0% compliant
13.0.3
Shall provide method to interface with Product information to list potential products for customer according
to customer parameters (e.g. business type, location, etc.)0% compliant
13.0.4 Shall provide method to track and report on sales campaigns including products of interest.0% compliant
13.0.5 Shall provide method to track sales contacts.0% compliant
13.0.6 Shall provide method for product quotes in real-time, including taxes.0% compliant
13.0.7 Shall provide method for revenue projections as part of sales forecasts.0% compliant
13.0.8 Shall provide method for territory management.0% compliant
13.0.8.1 • Shall provide method to notify sales personnel of changes to key customer.0% compliant
13.0.8.2 • Shall provide method to track and report user activity for target marketing.0% compliant
13.0.8.3 • Shall provide method for analysis of usage to suggest up-selling and cross-selling opportunities 0% compliant
13.0.8.4 • Shall provide method to track referrals and activation for referral bonuses.0% compliant
13.0.8.5 • Shall provide method for customer retention analysis.0% compliant
14 Work Flow Management
14.0.1 Shall provide method to setup and maintain workflow process through graphical interface 0% compliant
14.0.2 Shall provide method to allow stop points to be set up in sequence or in parallel 0% compliant
14.0.2.1 • Shall provide method to set up work order stop points to have time limits to work order 0% compliant
14.0.2.2 • Shall provide method to have different time limits based on order priority (e.g. emergency, high, normal)0% compliant
14.0.2.3 • Shall provide method to monitor stop points and list/report orders exceeding desired time limits 0% compliant
14.0.2.4
• Shall provide method to report, real-time, orders exceeding time parameters through pop-up windows or
email.0% compliant
14.0.2.5 • Shall provide method to interface with PDA type devices for communication with field technicians 0% compliant
14.0.2.6 • Shall provide method to interfaces with Work Management system 0% compliant
15 Order Entry
15.1 Point of Sale - integration
15.1.1
Shall provide method to seamlessly interface with OSS financial and ordering components contained in this
matrix, in real-time, with POS system component. (see other interfaces section below)0% compliant
15.2 Point of Sale - if included in proposed solution
15.2.1 Shall provide method to facilitate cash drawer functions:
15.2.1.1 • Open / close drawer 0% compliant
15.2.1.2 • User id / password protected 0% compliant
15.2.1.3 • Shall provide method to track all transactions by user id / date / time / order type / payment type 0% compliant
15.2.1.4 • Shall provide method to reverse transactions 0% compliant
15.2.1.5 • Auto balance of drawer at closing 0% compliant
15.2.1.6 • Shall provide method to report / email out-of-balance drawer reports automatically 0% compliant
15.2.1.7 • Shall provide method to report drawers not closed at scheduled time intervals (e.g. close of business)0% compliant
15.2.2 Shall provide method to enter payment types:
15.2.2.1 • Cash 0% compliant
15.2.2.2 • Check 0% compliant
15.2.2.3 • Credit Card 0% compliant
15.2.2.4 • Debit Card 0% compliant
15.2.2.5 • Money orders 0% compliant
15.2.2.6 • Promotional Coupons 0% compliant
15.2.2.7 • Gift certificates 0% compliant
15.2.2.8 • Government certificates 0% compliant
15.2.2.9 • Credits 0% compliant
15.2.3 Shall provide method to initiate new, change, and disconnect orders through interface to Order Entry portal 0% compliant
15.2.4 Shall provide method to access customer information real-time for support of customer 0% compliant
15.2.5
Shall provide method to setup and maintain security levels allowing supervisors access to individual cash
drawers 0% compliant
15.2.6 Shall provide method to interface to multiple billing systems.0% compliant
15.2.7 Shall provide method to access CRM, Product and Order entry information for price quotes 0% compliant
15.2.8 Shall provide method to update inventory for any retail sale of equipment 0% compliant
15.3 Order Processing
15.3.1
Shall provide method to attach orders to a super order (i.e. Shall provide method to have multiple orders
tracked as a single order)0% compliant
15.3.2 Shall provide method to open and maintain multiple service and multiple work orders for each account.0% compliant
15.3.3 Shall provide method to set up and maintain order status codes 0% compliant
15.3.4
Shall provide method to have order status code set automatically based on work order point (see Workflow
section)0% compliant
15.3.5 Shall provide method to set up and maintain CSR scripting/marketing messages per:
15.3.5.1 • Order type 0% compliant
15.3.5.2 • Screen 0% compliant
15.3.6 Shall provide method to set up field defaults based on order type.0% compliant
15.3.6.1 • Shall provide method for screens to hide or display fields based on order type 0% compliant
15.3.6.2 • Shall provide method to do credit check through credit services or internal scoring method 0% compliant
15.3.6.3 • Shall provide method to assign orders to individual CSR's or groups of CSR's 0% compliant
15.3.6.4
• Shall provide method to perform mass changes to multiple accounts through one order (e.g. add new
promotion to all CA clients)0% compliant
15.3.6.5 • Shall provide method to retrieve order in real-time by:
15.3.6.5.1 – Assigned CSR 0% compliant
15.3.6.6 • Shall provide method to calculate deposit level based on services 0% compliant
15.3.6.7 • Shall provide method to calculate deposit level based on customer credit score 0% compliant
15.4 CARE Processing (Voice Orders)
15.4.1
Shall provide method to generate electronic CARE compliant records triggered by a new, change or
disconnect order and exchange those records and files with other impacted carriers.0% compliant
15.4.2
Shall provide method to receive and process electronic CARE compliant records and files from other carriers.
This includes validation of the customer account, customer's account change restriction indicator, CARE data
element validation and where appropriate, to generate the appropriate new or change order.0% compliant
15.4.3 Shall provide method to generate electronic rejection CARE compliant records and files to source carrier.0% compliant
15.4.4 Shall provide method to report status of CARE record initiated orders by source carrier.0% compliant
15.4.5 Shall provide method to store relevant CARE records as part of bill cycle history.0% compliant
15.5 Outside/Local Service (OSR/LSR) Requests Processing
15.5.1
Shall provide method to generate electronic records triggered by a new, change, disconnect or port order and
exchange those records and files with other impacted service providers.0% compliant
15.5.2
Shall provide method to generate, receive and process electronic LSR compliant records and files from other
carriers. This includes validation of the customer account, customer's account change restriction indicator,
LSR data element validation and where appropriate, to generate the appropriate new, change, disconnect or
port order.0% compliant
15.5.3 Shall provide method to generate electronic rejection LSR compliant records and files to source carrier.0% compliant
15.5.4 Shall provide method to report status of OSR/LSR initiated orders by source carrier.0% compliant
15.5.5 Shall provide method to store relevant OSR/LSR records as part of bill cycle history.0% compliant
16 Flow Through Provisioning
16.1 General
16.1.1
Shall provide method to initiate a customers request to purchase content from a third party's system (e.g.
security systems)0% compliant
16.1.2 Shall provide method to initiate provisioning of resale service to underlying carrier through gateway interface.0% compliant
16.2 Voice
16.2.1 Shall provide method to exchange Directory information with third party vendor.0% compliant
16.2.2 Shall provide method to exchange Operator Service information with third party vendor.0% compliant
17 Retail Billing
17.1 General
17.1.1 Shall provide method to designate cycle periods to be:
17.1.1.1 • Seasonally where season is defined be starting and ending dates 0% compliant
17.1.2 Shall provide method to change dates of bill cycles and automatic proration of outstanding charges 0% compliant
17.2 Usage/Transaction Collection/Mediation/Billing
17.2.1
Shall provide method to collect/poll/mediate usage/transaction records from external and internal providers
depicted in Provisioning section in accordance to the following:
17.2.1.1 • Voice
17.2.1.1.1
– Shall provide method for user in real-time to define file and record exception identification, guiding and
reject/return control information by company.0% compliant
17.2.2 Shall provide method for a user to define input and output record formats 0% compliant
17.2.3 Shall provide method to segregate test usage from production usage at point of capture.0% compliant
17.3 Convergent Bill Capability
17.3.1 Shall provide method to accept charge elements from other systems for billing purposes 0% compliant
17.3.2 Shall provide cross discounting of one or more products 0% compliant
17.4 Revenue Assurance
17.4.1 General
17.4.1.1 • Shall provide method to report trends by product type and geographic location for each bill cycle.0% compliant
17.5 Reporting
17.5.1 General
17.5.1.1 • Shall provide method to email reports 0% compliant
17.5.1.2 • Shall provide method to publish reports to the web 0% compliant
17.5.1.3 • Shall provide method to publish reports to Adobe PDF's 0% compliant
17.5.1.4 • Shall provide method to export to MS Excel 0% compliant
17.5.1.5 • Shall provide method to schedule creation of reports 0% compliant
17.5.1.6 • Shall provide method to format reports with logos and notes sections 0% compliant
17.5.2 Sales Commissioning
17.5.2.1 • Shall provide method to capture billing information for commissioning 0% compliant
17.5.2.2 • Shall provide commissions calculations on gross and net revenues 0% compliant
17.5.2.3 • Shall provide commission calculation on specified products only 0% compliant
17.5.2.4 • Shall provide commission calculation on only amounts over minimum 0% compliant
17.5.2.5 • Shall provide tiered and threshold commission structures 0% compliant
17.5.2.6 • Shall provide recurring commissions 0% compliant
17.5.2.7 • Shall provide one-time commissions 0% compliant
17.5.2.8 • Shall provide interface to finance application 0% compliant
18 Other Interfaces and Modules
18.1 Plant Records
18.1.1 General
18.1.1.1 • Shall provide method to create user defined fields at all levels of plant records.0% compliant
18.1.1.2 • Shall provide method to interface with third party CAD/GIS mapping system.0% compliant
18.1.1.3 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
18.1.2 Inventory - integration: ([Cogsdale])
18.1.2.1 • Shall provide method to seamlessly interface, in real-time, with inventory vendor 0% compliant
18.1.2.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
18.2 Service Order Screens
18.2.1
Shall provide a method to indicate to the user when entering a service order for a new customer on a
location with a preexisting active customer present.0% compliant
18.2.2
Shall provide a method to indicate to the user when entering an order if there is a pending order on the
same account or location.0% compliant
18.2.3 Shall provide a method to ensure that service and work orders can only be entered on serviceable locations.0% compliant
18.2.4
Shall provide a method for the service order system to interface with the plant records, network records, and
location records systems.0% compliant
18.2.5
Shall provide a method for the system to suggest or correct service order type and services based on
facilities and services available to the location.0% compliant
18.2.6
Shall provide a method to indicate and rout the service order process based on plant records such as flags
for underground or overhead plant facilities 0% compliant
18.2.7
Shall provide a method to limit the type of services applied to service orders based on marketing,
geographic, or other defined groups of service.0% compliant
18.2.8
Shall provide a method to indicate to the user special promotions, up-sell information, or other messages
based on individual customer criteria, marketing group, geographic location, or service area.0% compliant
18.2.9
Shall provide a method to directly access credit score information for the customer at the time of service
order creation. (if yes, please describe)0% compliant
18.2.9.1 • If answer is yes to above credit score question; is the credit score stored in the system for later retrieval?0% compliant
18.2.10
Shall provide a method to indicate to the user the required deposit amount based on services and equipment
ordered.0% compliant
18.2.11 Shall provide a method to force the user to complete pre-defined fields (e.g. SSN, Name, Address, etc.)0% compliant
18.2.12
Shall provide a method to select service bundles that will automatically fill in prerequisite information about
the services without additional key-strokes.0% compliant
18.2.13
Shall provide a method to change services or other data within an open service order without having to start
a new order.0% compliant
18.2.14
Shall provide a method to indicate to the user what the estimated bill amount will be after the order is
processed.0% compliant
18.2.14.1 • If yes, does this estimate include tax amount?NA-Use Notes Field
18.2.15
Shall provide a method for the system to recommend bundles or other services if that bundle or service
meets the same requirements as that selected but has a lower cost.0% compliant
18.2.16
Shall provide a method to have a survey pop-up when orders of certain type are created (e.g. disconnection
order survey)0% compliant
18.2.17 Shall provide a method to automatically flag an order when the customer is in a bad-dept, or non-pay status.0% compliant
18.2.18 Shall provide a method for the user to flag an order for high priority or rush.0% compliant
18.2.19
Shall provide a method to indicate to the user if a new service order is created for duplicate customer
information such as social security number.0% compliant
18.2.20
Shall provide a method for the service order system to interface with the work force management system to
automatically rout the order based on service type, geographic location, network or plant facility information.0% compliant
18.2.20.1 • Please describe how business logic is handled in this process.NA-Use Notes Field
18.2.21
Shall provide method to configure printed words on service orders for purposes of providing customer
agreement forms including signature area. (privacy policy, equipment issuing forms, etc.)0% compliant
18.3 Work Force Management
18.3.1 Shall provide method to easily schedule service, work, and trouble orders from respective entry points.0% compliant
18.3.2 Shall provide method to electronically transmit orders via wireless network to laptops or PDAs 0% compliant
18.3.3 Shall provide method for users to update and close orders via wireless network on laptops or PDAs 0% compliant
18.3.4
Shall provide method for laptop or PDAs to store information about orders so that it can be retrieved when
wireless network is unavailable 0% compliant
18.3.5
Shall provide method to interface with GPS data system to track and collect information regarding users in
the field as it relates to orders.0% compliant
18.3.5.1 • If answer is yes to above GPS question, please describe this communication NA-Use Notes Field
18.3.6 Shall provide an overview list of orders assigned to each user and provide most efficient route to each 0% compliant
18.3.7
Shall provide a method to change order schedule date and time via GUI interface that allows drag-and-drop
functionality. (e.g. a scheduled order can be selected then dragged to another slot in the schedule with the
mouse)0% compliant
18.3.8 Shall provide a method to schedule orders based on field user availability, skill, and equipment requirements 0% compliant
18.3.8.1
• Ability to allow / disallow scheduling of work / service orders to technician based on work load (e.g. point
system or similar).0% compliant
18.3.8.2 • Shall provide reports that show work history by field technician, date range, order type, etc.0% compliant
18.3.9
Shall provide method to provide single printed page work order summary for disconnection / reconnection
work orders 0% compliant
18.4 Marketing and Promotions
18.4.1 Shall provide a method to set up marketing and promotion plans 0% compliant
18.4.1.1 • Promotions should be configurable by the following:
18.4.1.1.1 – Geographic location 0% compliant
18.4.1.1.2 – Service availability 0% compliant
18.4.1.1.3 – Plant and network availability 0% compliant
18.4.1.1.4 – Calculated penetration rates 0% compliant
18.4.1.1.5 – Custom inquiry or query from reporting interface 0% compliant
18.4.2 Shall provide reporting functions for marketing and promotion plans 0% compliant
18.4.2.1 • Reporting should be capable of at least the following criteria:
18.4.2.1.1 – Take rate / conversion rate 0% compliant
18.4.2.1.2 – Take rate / conversion rate divided by service type 0% compliant
18.4.2.1.3 – Demographic data (if available)0% compliant
18.4.2.1.4 – Geographic locations 0% compliant
18.4.2.1.5 – Start / Stop date of promotion 0% compliant
18.4.2.1.6 – Conversion rate based on CSR or user of system to track performance 0% compliant
18.4.2.1.7 – List of takers or successful conversions by individual customer (report)0% compliant
18.4.3
Shall provide a method to exclude customers in promotional communications based on CPNI settings (mail,
email, phone call)0% compliant
18.4.4
Shall provide a method to cause a pop-up or other message to display on the included customers accounts
when accessed based on the availability of the promotion 0% compliant
18.4.5 Shall provide a method to create a promotion or campaign based on a start and stop date / time.0% compliant
18.4.6
Shall provide a method to automatically reset billing charges on customer accounts after promotional plans
expire to non-promotional rates 0% compliant
18.4.7
Shall provide a method to create a promotion for existing services or bundles without having to create special
services or bundles.0% compliant
18.4.8
Shall provide a method to set up the promotion to apply penalties to accounts that cancel the service before
the predefined required time frame.0% compliant
18.5 Non-Payment Disconnection Interface
18.5.1 Shall provide a method for the system to automatically generate late fees on past due customer accounts.0% compliant
18.5.2
Shall provide a method for authorized users to exempt customer accounts from non-pay disconnection
process 0% compliant
18.5.3
Shall provide a method for the system to apply a late fee to the account's current balance and not the
previous balance to ensure an amount can only be penalized once. (please describe method if the same task
is accomplished in a different way)0% compliant
18.5.4
Shall provide a method to generate a report of non-payment customer accounts that includes when the
customer was sent late notices.0% compliant
18.5.5
Shall provide a method for the disconnection notice to line-item the basic phone rate per regulatory
requirements.0% compliant
18.5.6
Shall provide a method for the system to apply payment to the basic phone line first to ensure that the
phone line is not disconnected if minimum payment is received.0% compliant
18.5.7
Shall provide a method to disconnect all other services except for basic phone line when minimum payment
is received. (cost of basic phone line)0% compliant
18.5.8
Shall provide a method for the system to automatically interface and initiate disconnection process though
flow-through provisioning systems 0% compliant
18.5.9
Shall provide a method for the non-pay system to mark the account as being suspended and that indicator
be visible to all other parts of the system.0% compliant
18.5.10
Shall provide a method to handle secondary disconnection procedures if all services are not able to be
disconnected automatically through flow-through systems. (e.g. follow up process / order to create a service
order for physical disconnection in the field).0% compliant
18.5.11
Shall provide a method to automatically reconnect the account when sufficient payment is received and
initiate service order process to send to the flow-through provisioning systems.0% compliant
18.5.12
Shall provide a method to handle secondary reconnection procedures if all services are not able to be
reconnected automatically through the flow-through systems. (e.g. follow up process / order to create a
service order for physical reconnection in the field).0% compliant
18.5.13
Shall provide a method to update the disconnection indicator on the account so that all other systems reflect
the reconnection status and the date and time of disconnection and reconnection.0% compliant
18.5.14
Shall provide a method to store the disconnection and reconnection actions (with date and time stamp) in the
account history.0% compliant
18.5.15
Shall provide a method to generate a report of customers that were suspended for non-payment in a defined
date range.0% compliant
18.5.16
Shall provide a method to generate service orders to finalize or close accounts based on how long the
account has been in a non-payment status.0% compliant
18.5.17 Shall provide a method to automatically apply charges for un-returned equipment.0% compliant
18.5.18 Shall provide a method to generate a report of all un-returned equipment for the non-payment customer list 0% compliant
18.5.19
Shall provide a method to update the internal credit score / payment history information based on non-
payment suspension activity.0% compliant
18.5.20
Shall provide a method to provide a payment extension or arrangement plan to accounts on the non-pay list
and prevent them from being disconnected based on this arrangement.0% compliant
18.5.20.1
• Shall provide a method to resume non-pay flow if payment arrangements are broken the system should
resume the disconnection process.0% compliant
18.5.21
Shall provide a method to create a non interest or interest loan to spread a past due or bad debt amount
over time.0% compliant
18.6 Bad-Debt Interface
18.6.1 Shall provide a method to search and review all bad-debt accounts 0% compliant
18.6.1.1 • Shall provide a method to complete "charge-off" process in mass for selected accounts.0% compliant
18.6.1.2 • Shall provide a report that shows basic customer information for purposes of collection agencies.0% compliant
18.6.1.3 • Shall provide a method to flag a bad debt for bankruptcy protection.0% compliant
18.6.1.4 • Shall provide a method to easily reinstate a debt to an account to reactivate that account.0% compliant
18.6.1.5 • Shall provide a method to apply collection notices to the bad debt account.0% compliant
18.6.1.6 • Shall provide a method to include equipment charges (for unreturned equipment) to the bad-debt balance 0% compliant
18.7 Executive Dashboard
18.7.1 Is there an executive dashboard available? (high level overview of key items)0% compliant
18.7.1.1
• Does it show trouble ticket statistics including total number open, average time of resolution, and current
outages?0% compliant
18.7.1.2
• Does it show order status statistics including total number of orders open, average time of completion,
status totals, and late items based on schedule?0% compliant
18.7.1.3
• Does it show penetration statistics based on account type, service type, geographic location, promotion, tax
district, or other custom marketing group?0% compliant
18.7.1.4 • Does it show average revenue per service or customer type?0% compliant
18.7.1.5 • Does it show customer growth / decline by time range (week, month, year, etc.)0% compliant
18.8 Customer Dashboard (internal employee use)
18.8.1
Is there a customer dashboard (a single view / screen that shows the most important customer / account
information)?0% compliant
18.8.1.1 • Does it show the current balance due and the due date? Total balance due?0% compliant
18.8.1.2 • Does it show the previous balance and previous balance due date?0% compliant
18.8.1.3 • Does it indicate if the customer is nearing or is in a status of non-pay disconnection?0% compliant
18.8.1.3.1
– Does it show what amount must be paid to avoid disconnection for non-payment or get reconnected after
disconnection?0% compliant
18.8.1.4
• Does it have a direct link to the current and past bills? (if yes, is this a reproduction of the bill or an actual
scan of the bill as printed?)0% compliant
18.8.1.5 • Does it show the billable services and their active dates?0% compliant
18.8.1.6 • If the customer has an open trouble ticket is that indicated?0% compliant
18.8.1.7
• If the customer is considered part of an outage area as defined by the ticketing or operational system is it
indicated?0% compliant
18.8.1.8 • If the customer has an open service or work order is that indicated?0% compliant
18.8.1.9 • Does the CPNI information or question show on this dashboard?0% compliant
18.8.1.10 • Does the basic payment history show on this dashboard?0% compliant
18.8.1.11 • Do payment arrangements, contracts, or bill extensions show on this dashboard?0% compliant
18.8.1.12
• Can special account or location information (notes) be shown or pop-up based on account type, account
number, marketing campaign, or other customizable data?0% compliant
18.8.1.13
• Can special account specific notes be displayed on this dashboard such as warnings, theft of service notes,
bankruptcy, court orders, etc? Can these notes be displayed based on a time range (notes expire after a
certain time)0% compliant
18.8.1.14 • Can caller ID information via inbound phone call trigger a pop up or opening of the customer dashboard?0% compliant
18.8.1.14.1 – If yes, please describe this process.NA-Use Notes Field
18.8.1.15
• Can the dashboard be accessed by searching customer number, name, location ID, phone number, social
security number?0% compliant
18.8.1.16
• Can other parts of the system be accessed directly after the specific account is open in the dashboard?
(trouble ticket, service order, etc.)0% compliant
18.9 CABs Billing
18.9.1 Do you provide a client access billing module?0% compliant
18.9.1.1 • ability to update rates / derive rates from a configurable table 0% compliant
18.9.1.2 • ability to include circuit IDs on bill 0% compliant
18.9.1.3 • ability to bill switched access and special access 0% compliant
19 List of Interface Requirements
19.0.1 Point of Sale System:
19.0.1.1 • Shall provide method to seamlessly interface, in real-time, with functions supported by [PoS Vendor]:0% compliant
19.0.1.1.1 – Transmit to the PoS system information including:0% compliant
19.0.1.1.2 – Open order status 0% compliant
19.0.1.1.3 – Accept No Checks 0% compliant
19.0.1.1.4 – Account Status 0% compliant
19.0.1.1.5 – Suspended for Non-Payment 0% compliant
19.0.1.1.6 – Current and previous balance 0% compliant
19.0.1.2 • Provide method to accept payments in advance when new service is created via order 0% compliant
19.0.1.3 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.2 Interactive Voice Response System:
19.0.2.1 • Shall provide method to seamlessly interface, in real-time, to process functions supported by [IVR Vendor]:0% compliant
19.0.2.1.1 – Account balance 0% compliant
19.0.2.1.2 – Payments 0% compliant
19.0.2.1.3
– Outage management including ticket creation, update, close. Status updates via IVR generated from ticket
system.0% compliant
19.0.2.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.3 Caller ID on Screen System:
19.0.3.1 • Provide method to generate proper list of customer to provision based on product / package combination 0% compliant
19.0.3.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.4 Digital Set Top Box Control System
19.0.4.1 • add, delete, update set top box account information including package authorization 0% compliant
19.0.4.1.1 – setting of set top box mode (1-way, 2-way, PPV authorization, PPV buy limit)0% compliant
19.0.4.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.5
Digital CATV Management System (not necessary if function can be replicated directly through provided
interfaces)
19.0.5.1 • add, delete, update set top box account information including package authorization 0% compliant
19.0.5.1.1 – setting of set top box mode (1-way, 2-way, PPV authorization, PPV buy limit)0% compliant
19.0.5.1.2 – add, delete, update of user account details including location information, customer number, name, etc.0% compliant
19.0.5.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.6 ISP Server Systems ([Standard Linux Distribution])
19.0.6.1 • add, modify, delete user accounts (Unix based authentication through passwd file)0% compliant
19.0.6.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.7 FTTU Provisioning System
19.0.7.1
• add, modify, delete provisioning records related to FTTU deployment of Passive Optical Network systems
(XGS-PON). Register new equipment with defined service profiles for CATV, Data, and Phone services.0% compliant
19.0.7.2
• configure end devises (ONT) for service availability. (e.g. set services on or off). Interface between
disconnection / reconnection system and FTTU provisioning system to automatically perform service
activation or deactivation 0% compliant
19.0.7.3 • perform auditing functions to reconcile billing records / services with actual provisioned services 0% compliant
19.0.7.4 • receive and report on alarm generation by AMS system 0% compliant
19.0.7.5 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.8 FTTU Provisioning System - Calix ([Calix XGS-PON])
19.0.8.1
• add, modify, delete provisioning records related to FTTU deployment of Passive Optical Network systems
(XGS-PON). Register new equipment with defined service profiles for CATV, Data, and Phone services.0% compliant
19.0.8.2
• configure end devises (ONT) for service availability. (e.g. set services on or off). Interface between
disconnection / reconnection system and FTTU provisioning system to automatically perform service
activation or deactivation 0% compliant
19.0.8.3 • perform auditing functions to reconcile billing records / services with actual provisioned services 0% compliant
19.0.8.4 • receive and report on alarm generation by EMS system 0% compliant
19.0.8.5 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.9 Phone Switch ([MetaSwitch Class 5 Soft switch])
19.0.9.1 • provision telephony services including access line, feature set (e.g. voice mail, caller ID, etc.).0% compliant
19.0.9.2 • collect call detail records for rating engine (LD)0% compliant
19.0.9.3 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.10 Phone Switch ([Alcatel 4760 PCX])
19.0.10.1 • provision telephony services including access line, feature set (e.g. voice mail, caller ID, etc.).0% compliant
19.0.10.2 • collect call detail records for rating engine (LD)0% compliant
19.0.10.3 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.11 Voice Gateway ([Calix XGS-PON])
19.0.11.1 • provision telephony services including access lines 0% compliant
19.0.11.2 • add, delete, update subscriber information and port configuration.0% compliant
19.0.11.3 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.12 Cable MODEM and MTA Management System ([Incognito Software])
19.0.12.1 • provision data services for DOCSIS network elements including MODEMs, BSRs (multi-vendor)0% compliant
19.0.12.2 • add, delete, update subscriber information and port configuration.0% compliant
19.0.12.3
• configure end devises (MODEMs) for service availability. (e.g. set services on or off). Interface between
disconnection / reconnection system and provisioning system to automatically perform service activation or
deactivation 0% compliant
19.0.12.4 • perform auditing functions to reconcile billing records / services with actual provisioned services 0% compliant
19.0.12.5
• provision voice services on end devices (MTAs) including line activation / deactivation and subscriber
information 0% compliant
19.0.12.6 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.13 VOD System
19.0.13.1 • Account authorization, purchase limit, billing reporting, rating, log files 0% compliant
19.0.13.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.14 General Ledger and Accounts Payable System ([CSA Financial - Lawson Software, CSA MWIS])
19.0.14.1 • Interface to general ledger, accounts payable, and inventory system.0% compliant
19.0.14.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.15 Phone porting and management interface ([Level 3])
19.0.15.1
• Interface to assign, update, and remove subscriber phone line provisioning information, including 911, and
directory listing 0% compliant
19.0.15.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
19.0.16 Bill Printing
19.0.16.1 • Interface to bill printing vendor to upload and download invoice information for purposes of printing.0% compliant
19.0.16.2 • If development is needed to support interface, please give firm time and cost estimates.NA-Use Notes Field
***THIS SECTION NOT TO BE SUBMITTED ELECTRONICALLY***
Pricing $Notes
1 Costs to meet minimal requirements as listed in "Required" Form
Please list cost of individual components, any needed development and overall total. Please note
time, rate, and expected delivery in Notes field for any needed development.
1.1 Existing applications (Name and function(s) of component and cost)
Subtotal
1.2 Hardware (List all hardware components and cost)
Subtotal
1.3
Needed Development (List the section # and description from the Required or Info
Required tab and cost)
x hours @ $xx/hour; delivery within xx days of approval
Subtotal
1.4 Yearly Maintenance/Licensing (List ea. Base/Developed Component and cost)
Subtotal
1.5 Installation (List ea. Item installed and associated cost)
Subtotal
1.6 Training (List all training)
Instructions:
Existing applications section - Please list all components (applications/modules) and associated costs required to meet the functions outlined in the “Required” and "Desirable" forms accordingly.
Hardware section - Please list all hardware costs, by component, needed for solution.
Needed Development section - Please list all needed development to meet the functions outlined in the “Required” and "Desirable" form accordingly. List the section # and description from the Required/Desirable
form, the total cost, and the cost breakdown (# hours @ rate per hour), and time for delivery.
Please subtotal each section and calculate overall Proposed Cost Total
Yearly Maintenance/Licensing section - Please list all annual maintenance and licensing fees for the proposed solution by component; software and hardware
Installation section - Please list all one-time costs to install proposed solution.
Training section - Please list all training costs for the proposed solution by component. Please note if the training is on-site or off-site.
Other section - Please list any other costs associated with solution not covered in previous sections.
Subtotal
1.7 Other Items
Subtotal
1.8 Proposal Total:
2 Costs to meet requirements as listed in "Desirable" Form
Please list cost of individual components, any needed development and overall total. Please note
time, rate, and expected delivery in Notes field for any needed development. These costs will not
be evaluated as part of the Proposed Cost but will be considered in other areas of the evaluation.
2.1 Existing applications (Name and function(s) of component and associated cost)
Subtotal
2.2 Hardware (List ea. Hardware item and associated cost)
Subtotal
2.3
Needed Development (List the section # and description from the Required or Info
Required tab and cost)
x hours @ $xx/hour; delivery within xx days of approval
Subtotal
2.4 Yearly Maintenance/Licensing (List ea. Base/Developed Component and cost)
Subtotal
2.5 Installation (List ea. Item installed and associated cost)
Subtotal
2.6 Training (List all training and associated cost)
Subtotal
2.7 Other Items and associated costs
Subtotal
2.8 Total Desired Components:
3 Additional Requested Costs
These costs will not be evaluated as part of the Proposed Cost but will be considered in other
areas of the evaluation.
3.1 Year 2 Maintenance/Licensing (List ea. Base/Developed Component and cost)
Subtotal
3.2 Year 3 Maintenance/Licensing (List ea. Base/Developed Component and cost)
Subtotal
3.3
Ongoing Support (Provide a three year schedule for hourly rates of support staff (or
by task) that Waterloo Fiber may require or request in the future, ie. Programmer,
Software Development, etc.)
$xx/hour per staff title or task
3.4 Total Additional Requested Costs: