Overview

  • Overview of ReadyWorks for New Users

    Introduction to ReadyWorks


    Welcome to ReadyWorks! This guide is designed to help you understand how to use ReadyWorks effectively, especially if you're new to the platform. We'll walk you through the key concepts, explain the steps you'll take, and most importantly, help you understand how data flows through the system.

     

    What is ReadyWorks?


    ReadyWorks is a powerful platform designed to help organizations manage their assets efficiently. It acts as a Digital Platform Conductor, integrating various systems and providing a unified view of your asset estate, supporting processes, and corresponding data. Whether you're upgrading to Windows 11, migrating VM hypervisors, or orchestrating complex operational processes, ReadyWorks helps you streamline operations by connecting to different data sources, consolidating information, and automating workflows.

     

    Key Features and Capabilities

    1. Enterprise-Grade Automation:
    ReadyWorks offers a robust automation platform that integrates with a wide range of enterprise systems through its ETL (Extract, Transform, Load) capabilities. This allows it to ingest and normalize data from disparate sources, such as device management systems, ticketing tools, and business applications, offering a consolidated view for better decision-making. The platform excels in handling data migration, device refresh projects, and IT operations at scale.
    2. Centralized Data Management and Insights:
    Once data is ingested, ReadyWorks maps it into structured asset tables through SQL-driven processes, ensuring consistent and rationalized records. It offers custom reporting and dashboards that provide clear insights into key metrics, such as asset utilization and compliance, which can be tailored to business needs.
    3. Self-Service and Workflow Automation:
    ReadyWorks includes a Self-Service Portal that allows end-users to engage directly with their assigned assets, triggering workflows like device refreshes or updates through TCOMMs (Triggered Communications). These communications are critical for ensuring user participation in large-scale initiatives such as system upgrades or migrations.
    4. Waves for Bulk Operations:
    The platform is built to handle large-scale operations through the use of “Waves,” where related assets can be grouped and processed together. This feature is particularly useful in migration and refresh scenarios, allowing IT teams to efficiently manage thousands of assets simultaneously.
    5. Governance and Compliance:
    ReadyWorks ensures that governance and compliance are maintained across workflows by offering detailed audit trails, real-time monitoring, and the ability to enforce policies across all users. This is critical for organizations managing sensitive corporate data and seeking to ensure security and data integrity throughout their operations.
    6. Integrations and Extensibility:
    ReadyWorks integrates seamlessly with external systems through its ETL connectors, supporting both cloud and on-premises environments. The platform also offers REST API support, allowing organizations to extend its capabilities or connect to systems not natively supported by ReadyWorks, without requiring complex custom development.
    7. ReadyWorks for IT and Business Users:
    The platform is designed to be usable by both technical IT staff and business users, providing powerful tools for automation that don’t require extensive coding knowledge. This citizen integrator approach ensures that both groups can benefit from the same productivity enhancements.
    In summary, ReadyWorks provides a comprehensive solution for automating workflows, managing assets, and integrating data across your organization, helping businesses achieve operational efficiency and improved governance.
    See more
  • The ReadyWorks User Interface
    A screenshot of a computer

Description automatically generated

    Navigation Menu

    Located on the left side of the User Interface, the Navigation Menu is divided into sections for PROJECT, ASSETS and ADMIN

    Display Area

    Located to the right of the Navigation Menu, this area displays the pages for each ReadyWorks module

    User Menu

    Located on the top blue bar, the User Menu is divided into sections for FavoritesUser GuideOnline UsersPending Tasks and Logged On User

    Settings

    Located at the top right of the User Interface, the Settings menu is divided into sections for Options and About

    Search

    Located on the top left of the User Interface and above the Navigation Menu, the global Search box is available to search the Name field and Text fields (with Global Search enabled) of entries stored in ReadyWorks (e.g. assets, list items, waves, tasks, etc.)

    See more
  • Understanding the Data Flow in ReadyWorks

    Before diving into the steps, it's crucial to understand how data moves through ReadyWorks. Here's an overview:

    1. Data Sources (Connectors): ReadyWorks connects to various external systems (like SCCM, Active Directory, etc.) using Connectors to extract data.
    2. ETL Module (Extract, Transform, Load): The data extracted from these systems is brought into ReadyWorks through the ETL Module, where it is temporarily stored in Staging Tables.
    3. Data Mapping: The data from the staging tables is then transformed and mapped into the appropriate Asset Types within ReadyWorks using Data Mappings.
    4. Asset Types: Asset Types represent the categories of items you're managing (e.g., Computers, Users, Printers). They store the structured data ready for use.
    5. Reports and Dashboards: Finally, the data within Asset Types can be used to create Reports and Dashboards, providing insights and enabling decision-making.

    Understanding this flow is essential because each step builds upon the previous one. By the end of this guide, you'll see how data moves from external sources into meaningful information within ReadyWorks.

    See more
  • Key Data Flow Concepts and Terms

    Asset Types


    Why are Asset Types important?

    Asset Types are the backbone of ReadyWorks. They define how data is organized and presented within the platform. By properly setting up Asset Types, you ensure that the data is structured in a way that reflects your organization's needs.

    Assets vs. Lists:

    • Assets: Represent primary items (e.g., Computers, Users) and appear prominently in the navigation menu.
    • Lists: Serve as lookup tables or control lists (e.g., Locations, Models) and help maintain data consistency.

    Example:

    If you're managing printers, creating a "Printer" Asset Type allows you to store all relevant printer data in one place. You might also create a "Printer Model" list to standardize model names.

     

    ETL Module (Extract, Transform, Load)


    Why use the ETL Module?

    The ETL Module is essential for bringing data from external systems into ReadyWorks. It ensures that data is extracted accurately, transformed as needed, and loaded into the platform for use.

    • Connectors: Pre-built integrations that know how to communicate with external systems.
    • Jobs: Specific tasks within connectors that define what data to extract.
    • Staging Tables: Temporary storage where the raw data is held before mapping.

    Data Flow Insight:

    Data moves from the external system into ReadyWorks through Connectors and is stored in Staging Tables. Understanding the structure of this data is crucial for the next step—Data Mapping.

     

    Data Mapping


    Why is Data Mapping crucial?

    Data Mapping is where you transform and organize the raw data into meaningful information that fits your Asset Types. This step is vital because it allows you to clean, combine, and structure data before it becomes part of your main dataset.

    • SQL Queries: Used to manipulate and combine data from staging tables.
    • Mapping to Asset Types: Assigns the transformed data to the correct fields in your Asset Types.

    Data Flow Insight:

    Data from the Staging Tables is transformed through SQL queries and mapped to the Asset Types. This is where raw data becomes structured, actionable information.

     

    Reports and Dashboards


    Why build Reports and Dashboards?

    Reports and Dashboards help you visualize and analyze the data within your Asset Types. They provide insights that can drive decision-making and reveal trends or issues that need attention.

    • Report Builder: A tool to create custom reports using data from Asset Types.
    • Visualization: Charts, graphs, and tables that present data in an understandable format.

    Data Flow Insight:

    Data within Asset Types is used to generate reports and dashboards, providing the end-users with meaningful insights derived from the data flow starting from the external sources.

     

    See more
  • Accessing the ReadyWorks Platform

    Objective: Familiarize yourself with the ReadyWorks interface. Contact your local ReadyWorks Administrator or contact to obtain the URL for your unique instance. Your ReadyWorks environment may be hosted either on-premises or in the cloud.

    • Login: Use your credentials to access ReadyWorks. If your environment has been configured, no additional credentials are needed. For 'native' ReadyWorks accounts not tied to SSO, your ReadyWorks Administrator can provide credentials and reset your password.
    • Navigation Menu: Located on the left side, it includes sections like Assets, Reports, and Admin options.

    Why this step is important:

    Understanding the layout of the platform will make it easier to navigate through the next steps. Familiarity with the interface reduces the learning curve and helps you locate features quickly.

     

    See more
  • Glossary of ReadyWorks Terms
    Term Definition
    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.
    See more
  • Platform Wide Buttons

    Icons are placed on the toolbar to assist with common ReadyWorks actions. Some icons become active when an item (row) is selected in the associated table on the page or the appropriate conditions are met. The following table outlines each toolbar icon:

    Icon

    Description

    Download (action buttons, asset types, attachments, connectors, forms, mappings, reports)

    Delete, Remove (portal access)

    Unlink, Unassign (action buttons, users)

    Assign to Task (waves), Assign to Wave (assets, lists)

    Edit (action buttons, assets, charts, cron jobs, dashboards, job schedules, lists, portal access, reports, search, task priorities, task types, wave groups, wave types)

    Bulk Edit (assets, lists, tasks, waves)

    View (published reports)

    Assign (tasks)

    Start (tasks)

    Start All (tasks)

    Complete (actions, tasks)

    Cancel (tasks)

    Fail (tasks)

    Pause (tasks)

    Undo (actions)

    Copy (action templates, asset types, assets, connectors, forms, security groups, task chain templates, T-Comm templates)

    T-Comm On Demand

    Preview (charts)

    Clear Cache (charts)

    Run Cron Job (cron jobs)

    A blue and white logo

Description automatically generated

    Share (search)

    A white circle on a blue background

Description automatically generated

    Apply (search)

     

     

    See more