At least 4 weeks before the date of the planned go-live, the Customer contacts the Manager of Product support (“Manager“ in the next text) by sending an email to: firstname.lastname@example.org and informs him about the intention.
Manager checks the resources for a specific weekend. If there is a resource bottleneck, he offers another suitable date with the Customer.
At least one week before the date of go-live, the Customer opens an OSS incident with low priority (follow https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/2035056704 ), with the connectivity to all affected systems and valid logon data (please check required https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/2097086478). The expiry date of connectivity/logon data exceeds the go-live date.
Together with opening an OSS incident, the Customer delivers to the Manager a dry-run report signed by the authorized officer for a GO with dry-run hardware and software configuration and settings, results, and a statement that go-live will take place under the same conditions. If anything changes, it has to be recorded in the statement.
Prior to the go-live date, the Datavard consultant assigned for GO support (“Consultant” in text) will check the accessibility of the system, authorizations, the conformity with the dry-run report. In case of any discrepancies, the Consultant informs the Customer and asks for corrections to be applied latest one day before the go-live date.
In case of any issues during go-live, the Customer opens an OSS incident with high or very high priority (following https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/2035056704) and – based on the urgency – contacts Consultant by phone. Customer’s and Consultant’s activities related to the issue are being recorded to an OSS incident.