CWDS Glossary
The CWDS Glossary includes a List of Acronyms and defined terms captured from various models, reports, and other artifacts pertaining to the Child Welfare System – California Automated Response and Engagement System (CWS-CARES) Project. The Glossary standardizes terms used across the various project disciplines; each term is defined with its meaning specific to the project domain.
The State may update the CWDS Glossary at any time. Any questions please contact CWDS Communications.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Office of Systems Integration (OSI)
The trusted leader in the management and delivery of large, complex technology projects, enabling improved service delivery to the people of California.
OSI's mission is to procure, manage and deliver technology systems that support the delivery of health and human services to Californians.
OSI's mission is to procure, manage and deliver technology systems that support the delivery of health and human services to Californians.
Office of Technology and Solutions Integration (OTSI)
The Office of Technology and Solutions Integration (OTSI) is a California state agency that manages large, complex technology projects for California Health and Human Services. It focuses on procuring, managing, and delivering technology systems that support the delivery of these services to Californians. OTSI fosters a collaborative learning environment and emphasizes professional growth.
Office of the Agency Information Officer (OAIO)
Supports CHHS's efforts to enhance their programs through their successful delivery of data and technology solutions. Through Portfolio Support, Enterprise Architecture, Information Security, Agency Governance and Horizontal Integration activities, the OAIO provides both operational and strategic services to increase the probability of successful projects while promoting a person-centered culture and a corresponding portfolio of interoperable systems that can share and use data effectively to provide wholistic services to Californians in need.
Omnibus Budget Reconciliation Act of 1993
The Omnibus Budget Reconciliation Act of 1993 encourages and enables each state to develop and establish, or expand, and to operate a program of family preservation services, community-based family support services, time-limited family reunification services, and adoption promotion and support services.
Ongoing Support
Time after Go-Live Support where Orgs can access Implementation materials in the Implementation Portal and submit questions and inquiries to Implementation and Customer Relations. During this time the CWS-CARES Service Desk provides technical support.
Online Analytical Processing (OLAP)
The technology behind many Business Intelligence applications. OLAP is a powerful technology for data discovery, including capabilities for limitless report viewing, complex analytical calculations, and predictive “what if” scenario (budget, forecast) planning.
Online Transition Processing (OLTP)
A class of information systems that facilitate and manage transaction-oriented Applications, typically for data entry and retrieval transaction processing.
Operating System (OS)
The software that supports a computer's basic functions, such as scheduling tasks, executing applications, and controlling peripherals.
Operations Architecture
Facilitates the ongoing support and management of information technology (IT) services infrastructure of an enterprise. The IT infrastructure of an enterprise will typically comprise many different systems and platforms, often in different geographic locations. Operations architecture ensures that these systems perform as expected by centrally unifying the control of operational procedures and automating the execution of operational tasks. It also reports the performance of the IT infrastructure. The implementation of operations architecture consists of a dedicated set of tools and processes that are designed to provide centralization and automation.
Optimistic Concurrency Control (OCC)
A method applied to transactional systems that allows more than one user to access the same record at one time. OCC assumes that multiple transactions can frequently complete without interfering with each other. While running, transactions use data resources without acquiring locks on those resources. Before committing, each transaction verifies that no other transaction has modified the data it has read. If the check reveals conflicting modifications, the transaction attempting to commit rolls back and must be restarted. OCC is generally used in environments with low data contention, which leads to higher overall throughput than other concurrency control methods.