Brightly Assetic Environment Policy
Objective: Gain an understanding of the Brightly Assetic Environment Policy and how often data is refreshed in different environment types.
Brightly Assetic provides a range of environment types to meet the needs of our customers. Below is an overview of the different environment types and what they offer in terms of functionality and data refresh options.
Production
The Production environment is where the day-to-day operations occur. As part of any data migration and system configuration by Assetic, it is the environment that is initially populated. It will never be over-written by another environment. Availability, back-up and disaster recovery are all detailed in the Technical FAQ documentation.
Sandbox
Sandboxes are multi-purpose environments. They can be used for testing of new processes (including integrations) and data, and the delivery of training.
As part of a standard deployment this environment is made available during the implementation phase and up to three months after go live.
The utilization of the Sandbox environment can be extended at the client’s request for a nominal annual fee.
This environment can be over-written (usually by Production) with permission from the client. Assetic will aim to complete this process within 24 hours. Clients can request this environment to be refreshed up to six times per year.
Preview
Assetic can make a Pre-production environment available for specific users to test and review software before deployment to Production. As Assetic operates on a release schedule of once every two weeks, this environment is only available in the week before release, after the issuing of the Preliminary Release Notes.
Due to the nature of this environment the resources assigned and available to assist users are significantly less than the Production or Sandbox environments. This environment is initially configured with a copy of the data in Production, however it will only be updated from Production once every six months at the most.
It is a requirement of clients that wish to access a Preview environment that they supply Assetic with details of their testing methodology and resources prior to being given access.
All issues logged from a Preview environment may only be related to items detailed within the published Preliminary Release Notes. Any new or previously undocumented issues should be logged from the Production or Sandbox environments.
This environment is not part of a standard deployment and must be specifically requested. It will then be made available at an additional annual cost.
Note: Assetic has developed a separate Preview Access Agreement to provide more detail on both client and Assetic's obligations around the use of these environments.
Additional Environments
Should clients require environments other than those listed above e.g. a specific Training and/or Testing environment, then these can be made available at an additional annual cost.
As per the Sandbox environment clients can request these environment be refreshed up to a maximum of six times per year.
Utilization
Assetic periodically reviews the utilization of all environments. Should the review reveal low or no usage of non-production environments Assetic will contact the client to determine if these additional environments are still required.
