| Access Control List (ACL) | A list of permissions attached to an object that specifies which users or system processes are entitled with access. |
| Active Directory | Active Directory (AD) is the on-premises directory service that serves as the golden source for user data. |
| Asset Disposition | The process of disposing, recycling, or repurposing assets that are no longer needed. |
| Asset Refresh | The process of replacing aging or outdated assets, such as computers or devices, with newer models. |
| Asset Rule | Asset Rules are a ReadyWorks module that allows for cascading activities based on pre-defined conditions of an asset. |
| Asset Table | A table for post Data Mapping data aligned with a specific type of entity or device, such as computers, users, or locations. It defines the schema and fields, allowing data to be stored, managed, and reported on within the Management Interface. |
| Asset Tag | A unique identifier assigned to an asset for tracking purposes. |
| Bulk Edit | A ReadyWorks feature that allows Users to make changes to multiple records simultaneously. |
| CMDB | Configuration Management Database, a repository that acts as a data warehouse for IT assets and services. |
| Connector | The ReadyWorks component that supports authentication in order to run data pulls into ReadyWorks Staging Tables |
| CRON (Jobs) | Time-based job scheduling tool that allows scheduled commands or scripts to run automatically at specified times or intervals. |
| CSV file | Comma-Separated Values file; a plain text file that contains a formatted list of data ready for ingestion into ReadyWorks. |
| Data Mapping | The ReadyWorks module that supports defining SQL rules and transformations to map Staging Table fields to corresponding fields into the Asset Table schemas for Analysis and Orchestration. |
| End User | The community that exclusively users ReadyWorks through the Self-Service Portal and possess no entitlements to access the Management Inteface. |
| ETL Engine | The Extract, Transform, Load engine in ReadyWorks houses Connectors to your source data systems and runs jobs on a scheduled basis using CRONs; the result of a successful ETL pull are Staging Tables. |
| ETL Pull | The call for data from a source system by the ETL Engine, when using a REST API this is a GET request. The pulls resulting Staging Tables. |
| Front End | See’ Management Interface’ |
| ICS file | A file format used for exchanging calendar and scheduling information between different applications. |
| Identity Provider (IdP) | Acts as a centralized authority responsible for verifying user credentials and issuing security assertions that confirm the user's identity. These assertions are then used by other applications like ReadyWorks to grant differentiated access to authenticated users without requiring separate logins. |
| Lifecycle Status | A field used to track the state of an asset, such as deployed, in stock, at capacity, etc. |
| Management Interface | The ReadyWorks Graphical User Interface; a visual way for users to interact with the platform. Requires a logon to ReadyWorks. |
| Orchestration | Involves setting up and managing sequences of actions within ReadyWorks that are triggered based on specific conditions or schedules, enabling ReadyWorks to efficiently orchestrate complex workflows. |
| ReadyWorks | A software platform that automates and streamlines IT asset management processes, including asset refreshes. |
| REST API | Representational State Transfer Application Programming Interface: a type of API that uses HTTP requests to GET, PUT, POST, and DELETE data. |
| Self-Service Portal | A web-based interface that enables End Users to interact with entitled data to facilitate processes via a personalized webpage. Users can view and edit data about their assigned assets, and self-schedule activities, End-Users do not have full login entitlements. |
| Single-Sign On (SSO) | Authentication method that allows for users to access multiple applications or services with a single set of credentials managed by an single Identify Provider across the organization. |
| Staging Tables | Temporary tables used to store raw (or lightly processed) source system data before it is transformed and loaded into the final linked Asset Tables via Data Mapping. |
| T-Day | Refers to the start date of a wave and is used as the reference point for scheduling triggered communications (TCOMMs) and other orchestrated activities. For example, a TCOMM might be scheduled to be sent out at T-Day minus 2 (T-2), meaning two days before the start of the wave. This allows for automated communication and reminders to be sent to end users at predetermined intervals leading up to their scheduled activity date. By using T-Day as a central reference point, ReadyWorks can help ensure a consistent and organized refresh process across multiple waves and user |
| TCOMM Template | A predefined HTML layout used to format emails used at specific stages or trigger points in the refresh process. All messages are logged to ensure no duplicate messaging. Templates contain structure, layout, graphics, field value placeholders for the email to be sent to an end-user. Templates typically include: - Subject line: A customizable subject line for the email communication. - Message body: The main content of the email, which can include text, images, and placeholders for dynamic information (e.g., end-user's name, asset details, refresh appointment information). - Branding/Graphics: Customizable to match corporate logo, color, and font standards to support the organization's visual identity. - Dynamic Value Placeholders: Automatically populates the email with specific information about the end-user's name, asset details, or refresh appointment date and time. - Call-to-action: Clear instructions or links guiding the user to take specific actions, such as confirming their refresh appointment or accessing the Self-Service Portal. |
| Triggered Communication (TCOMM) | Automated messages based off TCOMM Templates that are sent to end-users by ReadyWorks to provide a notification or request information from the end-user by the Self-Service portal. |
| User | In ReadyWorks terminology this refers to an individual who has a credentials and is entitled to access based on their role as defined by Security Groups. Not to be confused with End User. |
| WAMP Application | Web, Apache, MariaDB (database), PHP; components of the ReadyWorks software stack. |
| Wave (Project Wave) | A group of assets or users that are scheduled together for a purpose (survey, schedule, satisfaction) based on predefined criteria such as number of end-users, campus location, department, security posture, or asset type, such that natural, logical groupings can be created and managed. |