Purpose = having a complete, comprehensible, up-to-date set of instructions for activating the Space Management application for new and existing tenants.
Activation scenarios
We have 5 activation scenarios:
Activation scenario A – new Spacewell tenant
In this scenario, we are dealing with a 100% new customer. No data migrations from MCS or Asset.
When activating a new tenant, all Locations must always be created in Space Management.
Through the integrations, they will automatically appear in all Workplace touchpoints and in Asset.
This scenario doesn’t cause any downtime or end user impact, because we are starting from scratch.
For details, go to this playbook: A - new Spacewell tenant
Activation scenarios B1/B2 – existing Asset tenant
In these scenario, we are dealing with an existing customer who already has location master data in Asset (Axxerion FMB, with or without Cobundu).
Use these scenario when
- Migrating a pure Asset tenant
who is using Workplace already: B1
- who is not using Workplace yet: B2
- Migrating a tenant from MCS
when locations were already migrated to Asset prior to the space management activation
- Alternatively, consider scenarios C1/C2
Scenario B1 causes downtime and end user impact, because we are migrating all location master data, which is the backbone of all our touchpoints. Depending on what a tenant is using, there will be visible impact on various ‘satellite’ touchpoints:
- Meeting room displays
- Kiosks
- Mobile Workplace app
- GO Portal
- Dashboards in GO Portal
This scenario also requires careful preparation of the location master data in Asset, especially when dealing with a pure Asset customers that was not converted from MCS in the past.
For details, go to this playbook: B1 - existing Asset + Workplace tenant
Scenario B2 doesn’t cause any downtime or end user impact, because we are starting from scratch for Workplace.
This scenario also requires careful preparation of the location master data in Asset, especially when dealing with a pure Asset customers that was not converted from MCS in the past.
For details, go to this playbook: B2 - existing Asset tenant (without Workplace)
Activation scenarios C1/C2 – existing MCS tenant
In these scenarios, we are dealing with an existing MCS tenant for which no migrations to Asset have taken place yet.
Use these scenarios when
- Migrating a pure Asset tenant
who is using Workplace already: B1
- who is not using Workplace yet: B2
- Additionally, both scenarios will migrate:
UDI fields to space management, because the UDI cannot be migrated to Asset automatically!
- Lands and Outside Locations from MCS
Scenario C1 causes downtime and end user impact, because we are migrating all location master data, which is the backbone of all our touchpoints. Depending on what a tenant is using, there will be visible impact on various ‘satellite’ touchpoints:
- Meeting room displays
- Kiosks
- Mobile Workplace app
- GO Portal
- Dashboards in GO Portal
For details, go to this playbook: C1 - existing MCS + Workplace tenant
Scenario C2 doesn’t cause any downtime or end user impact, because we are starting from scratch for Workplace.
For details, go to this playbook: C2 - existing MCS tenant (without Workplace)