Implementing GRAVITY is swift and with minimal installation (on your end). Theoretically an application could be up and running with GRAVITY in a matter of minutes. However, the success of GRAVITY depends on the speed of business and IT change in the customer’s organisation. The below steps and timelines are meant to provide an indication or starting basis for individual project planning. Drawio
...
Steps & Milestones
Step | Name | Description | Duration |
1 | Decision on SaaS vs OnPrem reached | An offer has been negotiated and accepted by both parties including implementation type, i.e. SaaS vs OnPrem. This decision is crucial and has an impact on the technical implementation. All relevant security reviews have been conducted and NDAs signed. | N/A |
2 | Deal closed | All contracts have been signed by both parties. | N/A |
3 | Kick-Off Workshop (WS1) | All relevant stakeholders hold a kick-off session to validate high-level requirements, basic setup (e.g., validating SaaS vs OnPrem, extension vs code injection, user identification, DNS settings,…) and timeline. | 30 Minutes |
4 | Technical Integration see implementation steps below: | Depending on outcome of Kick-Off Workshops, the individual tasks are addressed to get GRAVITY up and running and integrated for the first users. A separate tech workshop might be required to address additional configuration questions. | N/A |
5 | Impulse Workshop (WS2) | This workshop is for the business owners and content editors of GRAVITY. The goal is to understand how users are onboarded, engaged, and trained with GRAVITY. Real-world examples inspired from computer games are discussed in the workshop. A small handout is shared with all participants. | 60 Minutes |
6 | Use Case Preparation | Content editors prepare use cases showing what and where in the application they would like to add content. | |
7 | Application Configuration and first Content (WS3) | Use Cases are created and the GRAVITY support team configures application and gives first feedback. | 90 Minutes |
8 | Content preparation | Content editors now prepare content and add it to the application. Issues are raised with GRAVITY support team and dealt with. | N/A |
9 | Content Review and advanced topics. (WS4) | Together with GRAVITY team the first wave of content is reviewed. Advanced topics such as Audiences, Goals, Administration, Deployment and Staging are discussed with content editors. | 90 Minutes |
10 | Go-Live | Business as usual. | N/A |
11 | Ongoing Support | Depending on contract |
...
Step | Name | Description | Who |
|---|---|---|---|
1 | Setup GRAVITY tenant | Setup the Kubernetes instance for running the customer’s GRAVITY tenant. | Gravity |
2 | Configure Firewall | Configure HTTPS access to the GRAVITY tenant URL. | Customer |
3 | Rollout GRAVITY Plugins | Prepare and distribute the GRAVITY browser plugins for Edge and/or Chrome. More information about the browser plugins. Alternatively use inject script. More information about the inject scripts. | Customer |
4 | GRAVITY configuration | Based on the business information the GRAVITY server will be configured through the admin site. | Gravity & Customer |
...
Step | Name | Description | Who |
|---|---|---|---|
1 | Setup GRAVITY server | Setup a Java Runtime Server (Server requirements) or any technology which can run any of the available GRAVITY docker containers (available Docker containers). | Customer |
2 | Configure Firewall | Configure HTTPS access to the GRAVITY server URL. | Customer |
3 | Rollout GRAVITY Plugins | Prepare and distribute the GRAVITY browser plugins for Edge and/or Chrome. More information about the browser plugins. Alternatively use inject script. More information about the inject scripts. | Customer |
4 | GRAVITY configuration | Based on the business information the GRAVITY server will be configured through the admin site. | Gravity & Customer |
...