Implementation Approach: Direct Setup in Production Environment

During a new implementation, all configurations such as statuses, master data, milestones, and other process-supporting elements are made directly in the Production (PROD) environment. This approach differs from traditional implementations where initial setup and testing occur in a separate WISH environment.

Why Configure Directly in PROD?

Avoid Sync Issues Between WISH and PROD

Maintaining full synchronization between WISH and PROD is difficult in practice. Even small configuration differences can result in unexpected issues at go-live. Repeating every change in both environments is not only inefficient but also introduces the risk of human error. By working directly in PROD, this challenge is eliminated.

Use the Correct Endpoints from Day One

All external integrations such as handheld scanners, customer portals, EDI connections, and board computers must point to the correct production environment. Setting up these components directly in PROD ensures the correct endpoints are used from the beginning, preventing rework or misrouted data.

Benefit from Best Performance

The production environment is optimized for performance. During implementation, this is especially valuable when configuring time-sensitive processes and integrations, as test environments may not provide the same responsiveness.

Clean Data with Transactional Cleanup Jobs

To ensure a clean go-live, Boltrics includes a standard job that deletes transactional data. This job is executed multiple times during the implementation and once more right before go-live. The result is a production environment that’s ready to run with only finalized configuration and master data.

Tracking and Monitoring Changes

Each record in 3PL Dynamics automatically includes a timestamp showing when and by whom it was created or modified. This built-in traceability is usually sufficient for auditing and troubleshooting purposes.

For more detailed change tracking, Change Log Monitoring can be enabled for specific tables. This logs every change to field values and allows for full review of modifications during the implementation process.

Using the RAPP Environment for Testing

Customers may also use the RAPP environment, a nightly copy of PROD, to test changes before applying them in the live system. RAPP is ideal for validating adjustments without risking disruptions to daily operations.

Once changes have been tested successfully in RAPP, they must be manually replicated in the PROD environment. This encourages deliberate application of updates and helps ensure stability in production.

Note

For an overview of all available environments and their purposes, visit Environment Types.