Costpoint Enterprise GCCM Environments
The table in this topic details the Environments and Systems (databases) that are included in the GCCM offering.
In the table below, CompanyName is equal to the System Name that was provided, by your company, to Deltek prior to your cloud activation.
Environment | System Name(s) | Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Production | REGENT (PROD) | Purpose
Your company's live production database is deployed and maintained in this environment. Access Only the Deltek Cloud Operations team has access to the database residing in the Production Environment. Direct access (using a database tool) to the database in the Production Environment is not permitted. Deltek does provide ODBC access to your Production database. Application Version The applications running in the Production Environment run the latest version of the application software. Attention: For more information on when updates are made to the applications running in the Production Environment, refer to the
Application Lifecycle topic.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Non Production | REGENTCONFIG
REGENTTEST REGENTSBOX |
Purpose
The CONFIG & TEST databases are intended to be used when implementing Costpoint. The SBOX database can be used for multiple purposes. It can be used to support your company's implementation of Costpoint, training users and/or to test your configuration changes before these changes are applied to your Production database. Companies should implement Costpoint using their CONFIG, TEST and Production database. Companies should plan to be live in their Production database when they complete their implementation. The Non Production databases are also used to support a customer's testing efforts as part of the software development lifecycle in the cloud. Testing of Extensibility Packages, Web Services, Stored Procedures and Custom Database Objects is performed in the Non Production Environment. Once testing is complete you can schedule the Promote to Production service request to deploy your development project to your Production Environment. Please review the Promote to Production Service Request thoroughly as there are restrictions as to when you can promote development projects to the Production Environment. Additional Systems (databases) Customers can purchase additional Systems (databases) in the Non Production Environment. SQL Access Users have elevated rights to their databases in the Non Production Environment. This allows users to perform implementation services, data migration and testing. Users have access to database tools in the Non Production Environment allowing them to connect directly to the databases in the Non Production Environment. The SaaS Customer Administrator must submit the Request SQL Access to Non Production Databases service request to grant a user with rights to the database tool. You can grant a user either read only or read/write SQL rights. Citrix is required to access the database tools. SQL Rights Granted
The SaaS Admin must also add the user's Cloud AD Account to the following Group Memberships in the Cloud Active Directory:
Important: Users do not have database tool access to the databases in the Production Environment. Application Version (Costpoint Updates) When applying major or minor updates to the cloud, these updates will be applied to the Non Production Environment prior to applying these updates to the Production Environment. Maintenance Releases, referred to as MR's, are applied to all Environments at the same time. Attention: For more information on when updates are made to the applications running in the Production Environment, refer to the
Application Lifecycle topic.
Database Refresh Up to a maximum of 12 times per year, customers can request their Costpoint database (CONFIG, SBOX) to be refreshed. A Database Refresh service request must be submitted in order for Deltek to process a database refresh. At certain times Database refreshes are not permitted. Attention: Please refer to the
Application Lifecycle topic as well as the detailed instructions for the Database Refresh service request in order to understand these blackout periods.
IMPORTANT: Deltek reserves the right to reset your Sandbox database back to a blank database at anytime. Typically resetting your Sandbox database is only done when a major upgrade is scheduled. If Deltek plans to reset your Sandbox database to a blank database, this will be communicated to you prior to any action taking place. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Development | REGENTDEV
Customers can purchase additional Systems (databases). |
Purpose
The Development Environment is available for developing Extensibility Packages, Web Services, Stored Procedures and Custom Database Objects. SQL Access The SaaS Customer Administrator must submit the SQL Access to Non Production Databases service request to provide the SaaS Developer with database tool access. SQL Rights Granted
The SaaS Admin must also add the user's Cloud AD Account to the following Group Memberships in the Cloud Active Directory:
You can access the Costpoint Data Dictionary by navigating to the Print Data Dictionary Report in Costpoint located in the .Application Version (Costpoint Updates) The Development Environment is updated to the next Costpoint version at or around the same time the Non-Production Environment is updated. Database Refresh Up to a maximum of 12 times per year, you can request that your company’s Development database be refreshed. To do so, submit a Database Refresh service request. Additional Systems (databases) Customers can purchase additional Systems (databases) in the Development Environment. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Validation Program (RVP) | CompanyNameRVP | Purpose
The Release Validation Program’s (RVP) main goal is to allow clients to thoroughly conduct end-to-end testing on the latest software release, prior to upgrade. The goals of the RVP are as follows:
Enrollment & Participation Requirements Costpoint Enterprise customers are invited to enroll in the Release Validation Program (RVP). Your SaaS Administrator will be provided with instructions on how to enroll in the program. As a member of the RVP program, your team will be asked to perform the following tasks on a quarterly basis. Your RVP system will have the latest Quarterly Release installed.
It’s important that customers who have enrolled in the RVP participate fully in the program. Customers that do not participate may be asked to exit the program to make room for another customer to participate. SQL Access The SaaS Customer Administrator must submit the SQL Access to Non Production Databases service request to provide the SaaS Developer with database tool access. SQL Rights Granted
The SaaS Admin must also add the user's Cloud AD Account to the following Group Memberships in the Cloud Active Directory:
You can access the Costpoint Data Dictionary by navigating to the Print Data Dictionary Report in Costpoint located in the Administration > System Administration > System Administration Reports/Inquiries. Application Version The RVP Environment will receive the Quarterly Release as soon as it is available, this environment will have the new features before your Development, Non-Production or Production environments. Database Refresh Your data will automatically be refreshed from Production within 2 weeks prior to the next Quarterly Release. |