Skip to main content

Getting started

OpCon Deploy is a separate application working on a central repository that contains the schedule definitions, transformation rules, and all the required configuration information to deploy the schedule definitions between OpCon environments in a controlled and consistent manner.

The current version is 23.0.


General Overview

When implementing OpCon Deploy, the schedule definitions must be imported into the central repository before they can be deployed to OpCon systems within the environment. When a schedule definition is imported into the central repository and an entry for the schedule definition already exists, a new version of the schedule definition is created. This means that it is possible to deploy older versions of the schedule definition as a definition is never updated in the repository.

The objective is never to update the schedule definitions directly on production OpCon systems, but rather to deploy the schedule definition to a development system, make and test the changes, then import a new schedule definition to create a new version and then deploy the new version to the running OpCon system.

To communicate with OpCon systems, user and server definitions are required. Each OpCon Deploy user is mapped to an OpCon user and the OpCon Deploy server is mapped to an OpCon system. User roles define the capabilities of the user within OpCon Deploy and Server roles define the capabilities of the OpCon systems.

All actions performed within the OpCon Deploy system are audited so it is possible to determine who did what and when by examining the audit records.


The OpCon Deploy system provides the following processes:


The import process consists of extracting a schedule definition from the source OpCon environment and storing it in the central repository for future deployment.

If the schedule definition exists in the central repository, a new version is created.


The Deploy process consists of selecting a schedule definition from the central repository and inserting it into the selected target OpCon environment.

During the deployment process, it is possible to transform the schedule definition by using Transformation Rules. This allows a single schedule definition to be deployed to multiple OpCon systems instead of creating a schedule definition for each target OpCon system.

During the deployment process if the target system is defined as a Production system, a check is performed to determine if the definition on the system matches the definition that was deployed. For other systems, a check is made to see if the schedule definition exists on the target system.

It is also possible to deploy a package which consists of a set of schedules that are deployed and managed in a consistent manner.


The simulation process performs a deployment check without updating the schedule definition on the target OpCon system.


The rollback process performs a restore of a schedule definition from the backup taken during the deploy process.


The batch process provides the capability to deploy or simulate deployments of schedules or packages at specific times or perform individual or mass imports of schedule definitions.


The delete process removes a package or schedule from the selected OpCon system.

Release Management Process