- Introduction to WaTech Allocations (Allocated Rates)
- The Allocation Process
- Customer Base, Methodology & Invoicing Structure
- Do Agencies Receive Funding to Pay Allocation Charges?
- Enterprise System Rates Allocation
- State Data Network Allocation
- Security Gateway Allocation
- Security Infrastructure Allocation
- State Data Center (Debt) Allocation
- State Data Center (Operations) Allocation
- State Data Center (Debt Services) Allocation
- Location Based Services Allocation (GIS/WAMAS)
- Office of Cybersecurity (OCS) Allocation
- Small Agency IT Allocation
Page updated 10/09/2019
Customer Base and Methodology
The customer base and methodology may differ for each allocation.
- The customer base is selected based on existing (or hoped-for) state agencies using the services bundled within a specific allocation.
- The methodology for spreading the total cost of the allocation across the customer base will be noted in the allocation sections below.
- OFM publishes the Central Service Model Allocation Methodologies and Data Sources on its public website. This includes all allocations from central service agencies, including those that WaTech bills for.
Invoicing (Billing) of Allocations
Central service providing agencies are responsible for setting up a particular invoicing structure that relates to their funding structure.
Determining Granularity and Frequency
OFM provides the breakdown to the service-providing agency who then incorporates this into their billing/invoicing system. The agency has some discretion in terms of how they elect to bill agencies included in that allocation in terms of frequency or granularity of detail. Regardless of agency choices in these areas, the yearly amount billed must total the total amount of that allocation. (The exception is for OAH, AGO, and SAO, which bill based on actual use of the service.)
- Granularity Example: WaTech requested additional revenue and expenditure authority to improve Disaster Recovery services at the Quincy Data Center. This was a request largely to fund a project with several one-time costs but also resulted in a need for the ongoing cost to maintain the connectivity to the new data center. Upon approval, the Enterprise Security Infrastructure allocation amount was increased by the additional revenue needed. Internally at WaTech, a decision was made to bill this allocation using two (2) separate invoice lines (one suffixed with ‘– Other’, and the other with ‘- Disaster Recovery’.
- Frequency Example: The Washington Master Addressing Services (WAMAS) allocation is NOT part of the OFM Central Services Model. As a result, OFM did not allocate additional expenditure authority to agencies, who were expected to absorb this cost from savings related to using this service. Because the total amount was fairly small, WaTech elected to bill agencies once yearly for their portion of this allocation rather than billing very small amounts monthly.
Changes During Supplemental Years
As noted above, sometimes changes are made during a supplemental budget year. When an allocation is adjusted retroactively, the provider agency must adjust the rate for the remaining months of that (and possibly future) fiscal years and then bill or credit allocation customers to receive the appropriate revenue.