Instances Section Overview
Theme: Overview | Who is it for? Automation engineers who run multiple concurrent instances of the same schedule or connect to remote OpCon environments
What Is It?
OpCon supports running the same schedule multiple times simultaneously using named instances or multi-instance definitions. Remote instances allow a local OpCon system to reference and interact with schedules on a separate, remote OpCon server.
When Would You Use It?
- OpCon supports running the same schedule multiple times simultaneously using named instances or multi-instance definitions
Why Would You Use It?
- Operational value: Allow a local OpCon system to reference and interact with schedules on a separate, rem
When would you use this section?
- Running the same schedule once per store location, machine, or customer simultaneously
- Passing different parameters into each instance of a schedule
- Configuring a connection to a remote OpCon server
- Using Vision to monitor cards that pull data from remote OpCon environments
What is in this section?
| Page | Description |
|---|---|
| Named Schedule Instances | Defining and running named instances of a schedule with unique properties |
| Remote Instances | Connecting to and referencing remote OpCon server instances |
Glossary
| Term | Definition |
|---|---|
| Machine (Machine (Agent)) | An execution target for OpCon jobs. Each machine runs an agent that communicates with the OpCon server and runs submitted jobs. |
| 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. |
| Vision | A Solution Manager dashboard module that provides real-time status views of OpCon jobs and schedules, organized by business area or SLA. |
FAQs
Q: What does the Instances Section Overview cover?
OpCon supports running the same schedule multiple times simultaneously using named instances or multi-instance definitions. Remote instances allow a local OpCon system to reference and interact with schedules on a separate, remote OpCon server.
Q: Who manages Automation Concepts in OpCon?
Automation engineers and administrators manage Automation Concepts, including configuration, user access, and monitoring.
Q: Where should I start in the Automation Concepts section?
Begin with the overview pages in the sidebar. If you are new to this area, review access and role requirements with your OpCon system administrator before making configuration changes.