| Access Code | A named object used to apply record-level security to individual job records, restricting which roles can view or modify specific jobs. |
| Department | A named object used to apply function-level security to individual job records. A single department can secure as many jobs as necessary. |
| Frequency | A named rule that specifies the recurring days on which a schedule or job runs. OpCon uses frequencies during the schedule build process. |
| Job | The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. |
| Master Schedule | The template definition of a schedule stored in OpCon's master tables. Changes to the master affect all future builds but not already-built daily schedules. |
| Role | A named collection of privileges that can be assigned to one or more user accounts. Users in a role inherit all of that role's privileges. |
| Schedule | A named group of jobs in OpCon that represents a business process. Schedules are built each day based on their defined frequencies and calendars. |
| Schedule Build | The process by which OpCon creates daily schedule instances from master schedule definitions, applying frequencies, calendars, and properties. |
| Solution Manager | The browser-based web interface for OpCon. Provides access to operations, self-service, vision dashboards, and configuration. |