Glossary of Terms

Workday stores your data as business objects—organizations, workers, positions, and so on—which can be thought of as database tables or worksheets in Excel. Just as a database table or worksheet has columns and rows, a Workday business object has fields and instances. A business object is composed of a set of related fields, similar to how a table or spreadsheet is composed of a set of related columns. Instances of a business object in Workday are like rows in a table or spreadsheet, with each instance representing a unique occurrence of that type of object such as an organization or worker. A business object can have no instances, one instance, or many instances. Workday automatically links related business objects together. For example, purchase order lines are linked to a purchase order header, the purchase order header is linked to a supplier, the supplier is linked to a company, and so on.

A tool to transform business data into meaningful and useful information.

The five (5) major business areas that will be supported by the ERP solution (i.e., Finance, Procurement, H/R, Payroll, and Budget).

A fund whose expenditures are subject to appropriation if held in the state treasury or subject to allotment if held outside the state treasury.

Accounts that are subject to the appropriation and/or allotment process.

The establishment of budgets and the continuous comparison between actual and budgeted results.

Criteria for building budget or forecast budgets. Types of budget structures include financial, staffing and position. Budget structures can be configured to require approval, organized by dimension type (such as cost center or region), and updated with amendments.

A legislative fiscal staff publication that summarizes the budget passed by the state Legislature. This publication is usually distributed a few months after the end of the legislative session. Budget notes provide guidance but are not legally binding.

Review of a project’s predesign study by an independent qualified multi-disciplined team using the value engineering methodology.

Caseload, economic, or demographic factors that have a significant effect on the state budget. Examples include inflation rate changes and state population changes in certain age groups.

An enterprise application developed as a tool to assist agencies in building all components of the decision package and submitting operating and transportation budget requests online. The new Agency Budget System (ABS) replaced BDS in June of 2018.

The ability to define an agency’s plan of estimated expenditures, revenues, cash disbursements, and cash receipts for each month of the biennium.

A plan of financial operation embodying an estimate of proposed expenditures for a given period of time or purpose and the proposed means of financing them.

Any additional cost (or savings) that occurs in the future because a budget item in the current biennium is not fully funded or is onetime.

A sequence of one or more tasks related to defining, targeting, and awarding a bonus to employees. In this process, a compensation administrator creates the bonus plan definition. The administrator or manager assigns the bonus plan to employees through one of various means. Assignment of the plan determines eligibility for the bonus event. The administrator sets up the bonus process, which funds the bonus pool, and then launches the process on the specified event date. Workday creates bonus events for employees based on their organization. Managers review the target bonus for their employees and submit bonus proposals for review. Once approved, the employees receive their bonus.

A debt instrument issued through a formal legal procedure and secured either by the pledge of specific properties or revenues or by the general credit of the state. Examples include bid bond, performance and payment bond. See: Form C-100 (2014) Section G.

A two-year fiscal period. The Washington state biennium runs from July 1 of an odd-numbered year to June 30 of the next oddnumbered year

Converting expenditures that occurred for only part of a biennium into the amount needed for a full biennium of implementation.

An entity who submits a bid in response to a solicitation issued for goods or services by an agency of Washington state government

An offer, proposal, or quote for goods or services in response to a solicitation issued for goods or services by an agency.

Restricts the coverage options available to workers under a specific benefit plan. For example, you can restrict the maximum age of dependents covered under a plan or the maximum and minimum coverage amounts.

Defines the following: • The coverage levels or amounts available to employees enrolling in an insurance, health care, defined contribution, or spending account plan. • The target populations for a plan (for example, employee, employee + spouse, or employee + children). • Eligibility for benefits, including which benefit groups are eligible for the plan. • Restrictions on the age of covered dependents. • Plan rates and costs.

Identifies workers who qualify for similar benefit plans and elections. Workday builds benefit groups dynamically based on eligibility rules that control group membership; all workers who meet the criteria specified in a group's eligibility rules are automatically assigned to that group. For example, you can create benefit groups by defining eligibility rules that assign executive management staff to one group, salaried employees to a second group, and hourly employees to a third group.

Identifies the events that trigger benefit enrollment, for example, open enrollment, new hires, or the birth of a child. It also identify the coverage types to make available to employees for when an event of this type occurs.

These rules specify coverage increase limits, EOI requirements, waiting periods, and other rules and conditions of enrollment for benefits enrollment events.

An event in the employee's life that gives the employee the opportunity to change benefit elections. These include staffing changes (for example, getting hired or promoted) but also "life events," for example, getting married or having a new child.

Identifies the benefit plans, coverage targets, and coverage amounts that employees receive by default when they do not complete an enrollment event.

A type of benefits coverage. For example, you can define Medical, Dental, Vision, Group Term Life, Long Term Disability, and Short Term Disability benefit coverage types. Each type can contain one or more specific benefit plans. You can set rules for benefit elections at the benefit coverage type level. For example, you can restrict an employee to selecting only one plan of a specific coverage type. You can also specify which coverage types are available for employee election during which benefit events.

Architectural/Engineering (A/E) Basic Design Services consist of those services described in the Guidelines for Determining Architect/Engineer Fees for Public Works Building Projects in Washington State. These design services include normal architectural, structural, mechanical, electrical and civil engineering services for the project. See: Form C-100 (2014) Section B2.

Speaking broadly, the Workday design being ‘done’ refers to the functional baseline model of design complete and ready for a hand-off to other areas of the program to inform and complete their work before validating the baseline with state agencies. This as a framework or a foundation – we must have these baseline designs complete first.   

‘Done’ when referring to this functional baseline model, does not mean the following:  

• That the design is complete – this is an iterative process, and getting to a ‘done’ functional baseline model is a crucial step in that process  

• That state agencies will not have opportunities to provide feedback or identify custom needs to build upon this function baseline model  

‘Done’ criteria are:  

• SAAM manual audit crosswalk is complete  

• Configuration workbooks are updated, signed off by approved business owners and/or functional leads  

• Baseline user stories and test scenarios are complete  

• To-be processes and documentation are complete