Scope
The following environments are considered within the scope of this Hardware Recommendations document.
| Environment type | Description |
|---|---|
| Production | The environment used for day-to-day operational services. |
| Test | A standby environment that replicates the production environment and is used for evaluating production functionality without impacting the production environment. |
| Project | A temporary environment used for reconfiguration and validation of key business processes for the duration of project activities. |
Project Environment Summary
Trapeze requires all customers provision a separate stand-alone environment in advance of any planned project activity. This environment will be utilized by the project team for the duration of the project schedule.
The project team will use this environment to perform the following activities:
- Implement new configurations of the product
- Implement new versions of the product
- Provide user training
This environment isolation approach ensures that Trapeze can continue to provide Customer Care support in the event of production issues without impacting existing project activities or schedules, which ensures that the operational needs of customers can be upheld in line with Trapeze's maintenance obligations without impacting project or maintenance work streams.
Once the project has been transitioned successfully to production, the project environment can be decommissioned in line with preexisting environment promotion practices.
Non-Compliance Risks
In the event that this guidance is not followed, the Environment Owner accepts the following business continuity risks:
- Trapeze Customer Care will be unable to proceed with troubleshooting or remediation of any production issue for the duration of the Trapeze Professional Services project.
OR
- Trapeze Professional Services resources will be directly impacted as a result of any remediation required by Trapeze Customer Care to address production issues.
In the event of any delay as a result of environment reuse, the customer will be responsible for any additional project time/effort required to restore the environment into its previously known good state.
In order to eliminate these risks, Trapeze highly recommends that a stand-alone project environment be provisioned in time for project go-live activities.
If the Environment Owner is unable to provision a project environment, they should inform Trapeze directly so that we can work collaboratively towards reducing possible risks for both organizations.