JPI: Sandbox org for What-If Planning and Testing Environment

Feature Request: Sandbox Org for What-If Planning and testing JPI settings

Summary

We are requesting a sandbox environment for Just Plan It (JPI) where customers can safely test changes — from settings and configuration to job schedules and what-if quoting analysis — without any risk to the live production plan or today's operator assignments.

Business Need

We use JPI as our source of truth for operator assignments and daily scheduling. You can see below the JPI Dashboard we are implementing on a TV display in our shop, useful for both Planners and Operators.

Meanwhile, any change we want to evaluate — a new setting, a router reconfiguration, a prospective job for quoting, or a feature we haven't used before — currently has to be made directly against live data.

This creates two problems:

1. Quoting new work: Our Estimating team cannot model the impact of adding a prospective job to the schedule without disrupting the active plan, so lead-time quotes are either guesses or come at the cost of plan integrity.
2. Continuous improvement: As an existing customer trying to deepen our JPI implementation, we regularly want to test new JPI features, or features we haven't used yet, against a realistic copy of our shop state. Today, every such experiment is a live-fire exercise.

Proposed Solution

Extend to customers the sandbox-and-clone capability JPI already maintains internally for Sales and Support purposes. Specifically:

• Full sandbox environment that mirrors the customer's production JPI org and supports the same range of edits — settings, configuration, routers, resources, job schedules, what-if quoting — but is fully isolated from production.
• "Refresh from Production" action that overwrites the entire sandbox with a fresh clone of the production org in one click. One-way only (Prod → Sandbox). No merge logic, no partial syncs.
• Zero impact on production: nothing done in the sandbox can touch live operator assignments, sequence priorities, or schedules.

Why This Benefits JPI (Not Just Customers)

JPI's Sales and Support teams already use clone environments to help customers. Exposing that same capability to customers directly lets customers self-serve experiments and validation work that today generate support tickets ("what happens if I change X?", "can we test Y before rolling it out?"). Fewer support escalations, faster customer-led adoption of new features, and more confident power users.

Proposed Commercial Arrangement 

My recommendation is that the sandbox be positioned as a perk of the Enterprise – Unlimited plan: included at no additional cost for Enterprise-Unlimited customers, and offered as a paid add-on for customers on lower tiers. That makes the sandbox a genuine upgrade incentive to Enterprise – Unlimited, while rewarding customers already committed at the top tier without nickel-and-diming them on a capability that is core to responsible use of a production scheduling tool. Lower-tier customers still get access if they want it — they simply pay for the additional infrastructure — so JPI captures revenue where the willingness to pay exists and absorbs the cost where the strategic value of the relationship justifies it.

-------
Note: I submitted this request as a "ticket" through my profile, but posting it here for any public comment by the "community". 

Thank you.