Business Hive-ups and Hive-Downs

The Plot 60 Way

Many group companies consist of trading and non-trading businesses and often assets will get left behind in non-trading businesses or businesses that only exist to cross charge their services.

Hive-up and Hive-down refer to the transfer of a business or assets within a group company, either “up” to the parent company or “down” to a subsidiary.

In an Acturis context both hive-up and hive-down are achieved by means of a data migration within the platform itself, modifying the data structures and system configuration to align to the desired business organisation.

With this in mind, we at Plot 60 adopt many of the disciplines of data migration to ensure that hive-ups and hive-downs are implemented seamlessly.

Definition

The first phase of a hive-up or hive-down is to identify and describe the business structure sought and compare this to the existing structures in order to very clearly define the existing and target models and describe the movement of data assets within those structures.

Hive build

As we are dealing with an intra-platform change existing routines will be adopted in order to effect the changes.

Testing the hive-up or hive-down solution is usually an iterative approach and generally involves running the routines in a dedicated testing environment.

Output from this phase results in a fully tested hive-up or hive-down process that is reliable and can deliver the business structures sought within the allocated time.

Hive Execution

After comprehensive testing, the time comes to run the hive-up or hive-down routine. In the majority of cases this is likely to occur overnight, over a weekend or public holiday.

Transition

During the execution phase, audit trails and logs will be created to ensure that all data has been correctly assigned. Finally, after reviewing the audit trails and logs, you will be prepared to make an informed decision to transition users to the new hived-up or hived-down Acturis platform.