Configurations

Optimize My Day uses the concept of configurations. A configuration is a private container of planning and optimization data. Customers of OMD, as one legal entity, will usually require one configuration only. However, OMD users may have access to various configurations. This is often the case for large organizations using several OMD configurations concurrently. Also, consultants may be involved in setting up various specific configurations for a particular customer or they can be involved in different customer projects at the same time.

Configuration Identifier

Each configuration is identified by a configuration identifier. This identifier is determined automatically by OMD at the moment the configuration is created. The configuration identifier is a unique number and is used to protect one configuration from another. Optimize My Day users can only see and update configurations they have access to. If a OMD user has created his own configuration, that user is initially the only user who has access to this configuration. The user may grant access to other OMD users by providing their name in the menu option Planning -> Share Configuration screen.

The identifier of a configuration can be found in the browser's address field when opening the configuration. For example, the URL

https://sandbox.optimizemyday.com/omd/?configuration=596658

points to the configuration with identifier 596658 on the OMD Go instance sandbox.

Sandboxes

Changes to the configuration of a customer should be handled with care. It is advised to first test changes in a Sandbox environment, specifically setup for the purpose of testing and acceptance.

Usually, we distinguish between two types of Sandboxes:

A configuration that has identical settings to the production environment. The configuration is automatically filled with test data derived from the customer’s Test ERP system. Processed items within OMD are sent back to the test system. This type of configuration requires test data from the customer’s Test ERP system to be available in order to test processes within OMD.

A configuration that has identical settings to the production environment. The configuration is filled with production data. Processed items within OMD are not sent back to the production system. This configuration always has accurate production data available. However, the amount of data is identical to the production environment. Hence, this type of configuration should only be considered within a relatively small environment.

In both types of sandboxes, the preferences effecting sensible data to be sent out to customers, such as customer reports or servicesheets, must be turned off.

Production Domain

When moving into production, all described functionality will have to point to the domain https://www.optimizemyday.com (instead of https://sandbox.optimizemyday.com), which is a High Availability environment with Failover and Disaster Recovery procedures in place. During development it is important to take this change of domain into account.

Structure

Each document uploaded to OMD must contain an initial Configuration element. Other configuration-specific data is specified within the Configuration element.