Amusement Park Design

The Challenge

When describing the needs of each department for a company such as major theme park you begin to see how truly sophisticated the various enterprises and needs of each environment can be. It then becomes easier to think of each different department within the company as its own, entirely, separate business/subcompany.

For our department / “sub-company” role, we specifically represent the Parks side of major theme park (Design and Engineering) and primarily focus on updating and sustaining the various rides and attractions of their parks. On occasion, we will work with other departments (such as the attraction and rides department) to help with the design and build of new rides and attractions as well.

Because we are looking at each department as its own “sub-company” it becomes increasingly complicated to track:

• Which person
• At which company
• Is using which license
• From which vendors
• To work on which projects
• On what days or at what times.

The addition of trying to track and create chargebacks to these other “sub-companies” for their usage proved difficult when trying to track their specific usage for reporting.

Multiple Feature History

Goal: In our case, we need to reduce our design from 2D and increase our design into 3D. For our departments, individual project tracking and goal setting a feature of LAMUM that we have found specifically helpful is the Multiple Feature History. Using this feature, we are able to report the comparison on the rate at which this transition is actually happening to meet our individual department goals and growth.

Usage / Utilization Rates

Currently, our department is moving towards a licensing platform from AutoDesk that utilizes Token Flex, which is a “consumption-based” model.

Although it is technically still possible to monitor consumption rates generated from the platform (after putting the data through a separate formula after gathering it), LAMUM provides a function to show monthly comparisons to track if the actual utilization of the licensing has increased or decreased a significant enough amount that would justify a change in our licensing.

At the end of the utilization year, we are then able to compare the actual burn rate of the token between LAMUM and AutoDesk for more accurate annual
reporting of usage.

Chargeback Reports

When working with the various other departments we are also able to use LAMUM to monitor the usage of our other software tools across any of those other departments or users.

This allows us to create the chargeback reports needed for those departments accessing our specific tools during collaborations.

Just this one feature of LAMUM has already offset the cost of some of those tools; such as Ansys, Matlab, and Design X.