Opus Glossary
- Updated on May 28th, 2024
- 98 Minute to read
- Share
-
Dark
This is a auto-generated Article of all your definitions within the glossary.
Glossary
This is a auto-generated Article of all your definitions within the glossary.
-
Alert
A notification triggered by the response to a question, associated with an alert priority level of critical, high, medium, or low. Alerts typically require a corrective action to address the issue identified. They are used to indicate the urgency of an issue and ensure timely action based on the priority assigned.
-
Analytics
Business Intelligence (BI) analytics involving the systematic computational analysis of data or statistics captured. In the context of OPUS, these are powerful dashboards that interpret, visualize, and derive insights from information recorded during various operations. Analytics enable users to monitor performance, identify trends, and make data-driven decisions.
-
Business Intelligence
Business Intelligence (BI) analytics involving the systematic computational analysis of data or statistics captured. In the context of OPUS, these are powerful dashboards that interpret, visualize, and derive insights from information recorded during various operations. Analytics enable users to monitor performance, identify trends, and make data-driven decisions.
-
Categories
Methods for defining and organizing items, reports, dashboards, and other elements within OPUS. Categories help classify and group related information for easier management, retrieval, and analysis.
-
Category
A method of defining and organizing items, reports, dashboards, and other elements within OPUS. Categories help in classifying and grouping related information for easier management, retrieval, and analysis.
-
Checklist
A list of capture questions to be completed in a job in OPUS. Used to ensure that all necessary steps or actions are taken in a specific order and no important details are overlooked.
-
Checklists
A collection of multiple checklists within OPUS. Each checklist comprises a list of items, tasks, or questions designed to ensure that specific procedures are followed and completed accurately.
-
Clone
A copy of a job used to create a new job based on the current job. Cloning can be utilized to duplicate jobs, workflows, or checklists for the same site, item, or context user, ensuring consistency and saving time in job setup.
-
Comment
A note or remark made against a question, job or transaction in OPUS. Comments can be optional or mandatory and may depend on the answer provided. They are used to provide additional context, explanations, or feedback related to the specific question or job.
-
Context User
A user in OPUS who is linked to a checklist, such as an employee on whom the job or checklist is being performed. The context user is typically the subject or recipient of the checklist's tasks and actions.
-
Destination Site
The site where a job is performed or where an item is destined. The destination site is the final location for a job's execution or where an item will be delivered or used.
-
Document
A document in OPUSmedia that can be filled in from a job in OPUS and used to send to an operator for review and signature. Documents can be used for contracts, policies, procedures, and other formal documents. They can be complemented with audio, allowing the recipient to choose the audio and document language for better accessibility and understanding.
-
External Customer
An entity, either internal or external to the organization, that has multiple sites linked to it within OPUS. External customers can be clients, partners, or other companies that require management and tracking of their associated sites.
-
External Reference
An identifier used to link items in OPUS with corresponding references in an external system. This ensures consistency and alignment between OPUS and other systems, facilitating seamless data integration and management.
-
Item
An asset, staff member, personal protective equipment (PPE), equipment, or stock associated with a job in OPUS. Items are essential components that are tracked and managed to ensure the successful completion of a job.
-
Item Classification
A method for defining items within OPUS as one of the following categories: Asset, Stock, Vehicle, Staff, PPE, or Lists. Item classification helps in organizing and managing items based on their type and function.
-
Job
A job is a task or job that an operator performs on the mobile or WebGL platform. Jobs can be a Standard Operating Procedure, Checklist, Scorecard, Task, Capture form.
-
Job Reference
A unique reference number assigned to a job, used to identify and track the job within OPUS. This reference can be user-generated or auto-incremented with special prefixes for better organization and identification.
-
Jobs
Collection of tasks or sets of tasks assigned to users or teams within OPUS. Jobs encompass specific activities that need to be completed and are tracked and managed through the platform.
-
Notification
Alerts sent to users via push notifications on the OPUS4business mobile app, email, or SMS. Notifications inform users of important updates, job assignments, alerts, or other critical information, ensuring timely communication and action.
-
ODMS
Operational Digital Management System (ODMS) enables Franchise Owners to monitor both high-level and detailed aspects of their operations simultaneously. By leveraging ODMS, Franchise Owners can streamline their processes, identify inefficiencies, and implement improvements, leading to optimized operational efficiencies across their restaurants.
-
Offline
The ability to perform tasks and capture information on a mobile device without requiring an active internet connection. This feature ensures that operators can continue their work seamlessly in areas with limited or no connectivity, with data syncing once a connection is reestablished.
-
Operator
The individual responsible for capturing and recording information in an OPUS job or checklist. Operators follow specific checklists to ensure accurate and consistent data entry.
-
OPUS
OPUS is a comprehensive digital operating platform designed to streamline data collection and management for teams in the field. It enables real-time feedback of work-related information through a mobile app, which supports both online and offline data capture, including GPS, text, and photos. The platform offers customizable forms for checklists, assessments, and audits, ensuring that businesses can standardize their data collection processes. With secure cloud storage, OPUS ensures enterprise grade security for all data. It provides robust job scheduling and management features, allowing for efficient monitoring and reporting of job completion and data quality. Advanced analytics tools offer tailored visualizations for enhanced business insights. Additionally, OPUS supports powerful workflows to automate functions based on custom triggers, ensuring a seamless operational management experience across staff, tasks, stock, and resources.
-
OPUS4business
A mobile app designed to capture jobs on mobile devices such as phones or tablets. There is also a WebGL version available for operators who operate off desktop computers. OPUS4business enables efficient job management and data capture across various devices, ensuring flexibility and accessibility for operators.
-
OPUS4managers
A mobile app designed for managers to track, manage, and extract data from OPUS on a mobile platform. OPUS4managers provides managers with the tools they need to oversee operations, monitor progress, and analyze data in real-time, all from their mobile devices.
-
OPUSmedia
A next-generation app for creating, distributing, and signing documents, built specifically for digital devices using the OPUS digital operating platform. OPUSmedia leverages advanced technologies to streamline document management and electronic signatures. It is designed to facilitate efficient digital document workflows, from creation to distribution and signing.
-
OPUSstudio
A customization portal for administrators to manage checklists and tailor OPUS to meet a company's specific needs. OPUSstudio allows for the creation, modification, and organization of checklists, workflows, as well as the customization of various features and settings to align with organizational workflows and requirements.
-
Org Unit
An organizational unit such as a department, region, or division within a company. Org Units help structure the organization by grouping related functions and areas for more efficient management and operations. They are commonly used in the HR structure to organize employees and their roles within the company.
-
Overview Page
The first page that appears in OPUS, outlining all pertinent actions, jobs, and operational activities for your company. The Overview Page provides a centralized dashboard for users to quickly access and manage essential tasks and information.
-
Position
A specific role or job held by an employee within an organization, typically within an Org Unit. Employees join a company in a designated position and perform the responsibilities, tasks, and authority associated with that role.
-
Priority
A designation used to define the urgency or importance of tasks, questions answered, or actions required. Priority levels such as Critical, High, Medium, Low, and None help in prioritizing responses and ensuring that urgent issues are addressed promptly.
-
Project
An organized initiative within OPUS that can be a project, campaign, or promotion. Projects encompass a set of tasks or objectives aimed at achieving specific goals within a defined timeframe.
-
Question
A data field within a checklist that requires input or response from an operator. Questions are designed to gather specific information, verify completion of tasks, or ensure adherence to procedures. There are many types of questions to enable checklists to be put together very quickly, such as text, numbers, images, barcode scanner, calculations, dates, times, item transactions, lists, options, scores, and many more.
-
Reference
A unique identifier used in OPUS to distinguish and manage various elements such as Job, User, Site, Position, Org Unit, Project, Question, Item Category. References ensure accurate and retrieval of information within the platform.
-
Report
System-generated and customizable documents that extract and present data from a specific job or across the entire OPUS platform. Reports provide detailed insights and summaries of operational activities, helping users analyze performance and outcomes.
-
Section
Splits the checklist into logical units, allowing the operator to navigate to different sections or menus in mobile checklists quickly. Sections help organize the checklist, making it easier for operators to find and complete tasks efficiently.
-
Site
A location such as a store, warehouse, customer site, restaurant, or workplace where a job will be performed and information will be captured by an operator. Sites are specific places where operational tasks and activities take place.
-
Site Classification
The categorization of a site within the organization, such as a store, workplace, warehouse, boot stock, customer location, supplier, or cost centre. Site classification helps in organizing and managing sites based on their specific functions and characteristics.
-
Site Role
A role associated with a site and a user that defines the function the user performs at the site or in any job related to the site. Site roles help clarify responsibilities and are used in workflows to assign jobs to users and operators based on their designated functions at a specific site.
-
Sites
Locations where various operational activities take place within OPUS. Sites can include stores, workplaces, warehouses, boot stock, customer locations, and other relevant places where jobs are performed and items are managed.
-
Source Site
The site from which an item originates or is sourced. The source site is the original location associated with the item before it is moved, transferred, or utilized in other operations.
-
Sub Company
A company under a parent company that inherits certain checklists and configurations from the parent company, commonly used in franchise operations. This structure allows for consistent processes and standards across all sub companies while enabling localized management.
-
Sub Section
A division within a section that allows for multiple subsections, represented as pages in a mobile checklist. Subsections provide further organization within a section, enabling operators to navigate and complete tasks efficiently on mobile devices.
-
Tag
A label used to categorize and organize various elements within OPUS, such as a Job, Checklist, Team, Site, Item, Project Group, Site Branch, Site Region, User, Site Division, Site Brand, or Site Area. Tags help in identifying and grouping related items for easier management and retrieval.
-
Team
A grouping of users and operators within OPUS that can be tracked and managed collectively for job assignments and performance. All Operators is a special team in which all users belong to.
-
Transaction
A record of an event against an item in OPUS, such as verification, count, recount, movement, transfer, repair, warranty claim, intake, use, or return. Transactions document the status and history of an item, ensuring accurate tracking and management.
-
User
An individual who uses the OPUS system. Users can have different roles such as web user, guest user, administrator, or mobile operator, each with specific permissions and access levels within the platform.
-
User Role
A set of roles that define what a user can do and which features are accessible to them in OPUS. User roles help manage permissions and ensure that users have the appropriate access to perform their tasks effectively within the platform.
-
Users
A collection of Individuals who use the OPUS system. Users can have different roles such as web user, guest user, administrator, or mobile operator, each with specific permissions and access levels within the platform.
-
Workflow
Powerful processes within OPUS that automate functions based on customized triggers and events. Workflows streamline operations by automatically initiating tasks, creating new jobs, reminders, sending notifications, and updating records when specific conditions are met.
-
Workflows
A set or list of Powerful processes within OPUS that automate functions based on customized triggers and events. Workflows streamline operations by automatically initiating tasks, creating new jobs, reminders, sending notifications, and updating records when specific conditions are met.