Integrated Telecommunications Business Support System and Operating Support System Solution

The vendor is required to provide integrated telecommunications business support system and operating support system solution for voice, video, security and cyber, data services and managed services to government, healthcare, public safety and education entities in the state.
- Billable elements and items related to elements or requests
•    Must have the ability to bill multiple types of circuits: physical, virtual, and logical.
•    The system must be able to manage different circuit types and associate them to customers, locations, and other groupings typical for telecom billing. 
•    The system must have the ability to present multiple billable items under a single service and circuit. (i.e., port charges, third party billing, recurring, non-recurring charges)
•    The system must be able to track the following per billable item: 
o    Object code (4 digits, sent via xml to state accounting system i/3) 
o    General ledger code (5 digit)
•    The system must allow for prorated, partial, and one-time charges.
•    The system must allow the ability to split a charge by percentage or specific dollar amounts between accounts or sub-accounts. 
•    The system must allow the ability to bill one time and non-recurring charges and monthly recurring charges to a different accounts or cost centers.
•    The system must be able to apply discounts and fees at the account, sub-account, service, or charge. 
•    These discounts and fees may be automatic or variable (example USF contribution fees, 911 county location fees)
•    The system must capture or pull and display key circuit information shown below in an efficient and streamlined process for the customer and support staff throughout the lifecycle of a circuit
o    A and Z location
o    Service (internet, data, voice, etc.)
o    Bandwidth
o    Description
o    Status (currently in-service, reserved, disconnected)
o    correlate vendor and LEC circuit id to network circuit id
o    Correlate vendor contract
o    Correlate customer contract
•    The system must allow for documents to be attached to the billing order and request. 
•    The system must be able to create, upload, store, add or remove documents (invoices, forms, inventory lists, account usage, etc.). 
•    These should be able to be associated with vendors, customers, or one and multiple services and charges.
•    The system must be able to have a customer and service specific rate sheet that can override any standard rate sheets that can be added and applied by the user.
- Invoicing and billing account management
•    The system must be able to automatically send invoices, reports, or similar documents to customers or a link to the documents. 
•    The documents must be able to be recreated or reprinted as necessary. 
•    The system must reasonably enable the network to efficiently send correspondence to select or all customers (e.g., rate changes to applicable groups, all customer notifications, etc.)
•    The system must be able to track key billing information by customer, including locations, cost center, account, sub account, and GL code. 
•    The system must allow billing accounts to be managed efficiently and effectively - accounts and organizations merge, changes should not need to be made multiple times and places, etc. 
•    Where appropriate, field changes should be able to be pushed globally across the system. 
•    The system must allow the ability to designate account coding for each hierarchical level of billing accounts.
•    The system must allow for efficient management of data, typically through bulk and batch import, export and validation processes. 
•    It must include more options than single field, point and click, data entry user interfaces.
•    The system must have the ability to tie a service to a customer location (network uses an 11 alphanumeric character code to denote a location specific to the account).
•    Unique service identifiers (circuit ids, telephone numbers, etc.) must be able to be displayed on invoices and bills. 
•    The system must be able to reasonably efficiently handle moving services between locations, customers, accounts, etc. and the charges should not need to be recreated. 
•    The proposal must explain how charge history is maintained. 
•    The system must be able to efficiently rebill customers for services network is billed by a vendor. 
•    Network is charged $0.015 and minute by the vendor and needs to automatically charge the customer $0.020 and minute for the service. 
•    The system must allow network to mark expenses (hours billed by contractors, equipment and materials purchased, leased circuits, etc.) as overhead or billable to a customer. 
•    This should be allowed to be overridden by select personnel. 
•    The system must include features designed to prevent common human errors or omissions typical to a mid-size telecom agency. for example, the system should not allow expense items to be entered but not associated with any billable order. 
•    Customers must be able to view billing and payment information in an effective and efficient portal, web app, or streamlined experience. 
•    They should be able to navigate from billing information to operating support information like incidents, service requests, maintenance and changes, etc. 
•    The system must allow staff to manage and maintain rates in a streamlined process and apply and update charges in an efficient manner.
•    The system must be able to store information useful in the administration or use of the service (auth codes, pins, etc.), and be able to show or hide the information based on roles and security.
•    The system must provide efficient and modern consolidated billing invoice options for all products and services in a single bill, such as:
o    Presenting all recurring charges, usage-based charges, service charges, support charges, one time charges, financial charges, labor, and other charges in a single bill.
o    Invoice presentation options based on different services.
o    Grouping and subtotaling by service
o    Bills and invoices should be concise and not include duplicate information, mostly or entirely blank pages, services not applicable to the customer, etc.
•    The system must allow network to run trial billing cycles at any time between closing billing cycles
•    The system must allow network to run trial invoices for customers from trial billing cycle close information
•    The system must be able to export .xml file to upload for payment state financial system
•    The system must be able to create summary reports and documents about exported data
•    The system must allow network to run final billing cycle close at any time during the month to accommodate for timing of closes for fiscal year end
•    The system must provide views of services associated with a customer account
•    The system must allow the creation of additional and custom fields to track specific attributes and ability to add these fields to views and forms and screens, and search and report on them (e.g., network customer type, class, category, association, i/3 accounting string, aba routing number, banking information)
•    The system must allow network to efficiently manage billing for customers that are hierarchical. 
•    We serve a state department, and we also serve specific facilities and regions of that department, and then further multiple divisions or teams within that facility and region. 
•    Accounts should be set up in a parent-child relationship or some similar mechanism to be able to manage and report and display accounts which are nested in this way. 

- Questions/Inquires Deadline: September 5, 2025