Liftmaster Pro: Functionality
To enable an automatized configuration process the object dependencies between the single lift components (shorter: the product logic) must be stored within Liftmaster Pro. For this the product which has to be configured is divided into component groups according to its list of part structure. Following that usage lists (= lists of parts which can be used in the single component groups) are defined. The interconnections between these components groups are configured with assistance of formulary based rule tables. The individual selection possibilities result out of this system of rules – completed by component characteristics without interconnections. The required article master data are normally supplied via interfaces of enterprise resource planning systems. After configuring an installation the results can be resend to these systems via its interfaces again.
Configuration process
After entering the basic data concerning shaft and cabin dimensions the shaft and frame parts are identified. Parts depending on lengths - as guard rail, clamps and suspension ropes - are determined fully automated. Following that Liftmaster Pro evaluates the appropriate cylinders and proposes the smallest suitable one. The chosen cylinder is displayed according to standard delivery options – these may be changed later if required. Fit able aggregates are detected accordingly to the cylinder and the most favourable is preselected. Now the system assembles all devices needed according to the cylinder and adds them to the list of parts. Components belonging straight to the lift, such as doors, cabin and safety installations are identified during the next step. Equal processes apply for additional devices like oil cooler or bleed oil sets.
- Master data and parameters have to be entered only once for the whole construction.
- Standard configuration is displayed by the system according to this data.
- Standard configuration can be customized afterwards.
The product logic to be followed can be defined freely. Complex calculations can be integrated within the configuration process. The total product costs are permanently actualised during the whole construction process. Production costs as well as sales prices can be determined. Individual customer discounts may be taken into account during sales price calculation.
Supported lift components
Liftmaster Pro is able to construct all main lift components - cylinders, aggregate, lift cage, cabin, doors and control systems. A device construction module enables the determination of all parts needed for fitting and fixture within the lift shaft. Cantilever or borehole type as well as pulling system installations may be configured. Further more the configuration of the following lift components is supported:
- Oil cooler
- Pipe rupture device
- Wall anchor
- Bleed oil sets
- cable
Assembly set configuration
In large part parameters for the construction of the complete installation will be determined already during assembly set configuration. This includes for example shaft and cabin dimensions or weights to be moved. After entering all parameters the shaft and frame parts and other components containing straight to the lift, such as doors, cabin and safety installations are determined. During this process safety clearance and geometry of the components to be installed are considered to ensure that the configured installation can be fitted in any case and collisions of any single parts are impossible. Parts depending on lengths as guard rail, clamps and suspension ropes are determined fully automated.
Cylinder configuration
Direct (1:1) or indirect (1:2) driven installations may be configured. Constructions of parted cylinders are supported as well as double piston installations. A large part of parameters needed for cylinder configuration are taken over from the assembly set configuration. Only information only relevant for the cylinder choice has to be entered at this process step.
Aggregate configuration
For choosing appropriate aggregates all parameters of the cylinder configuration, such as lift cage pace, flow rate, pressures a. s. o., are used. So no aggregate can be chosen which does not meet the power rating resulting from the cylinder configuration. Further more all connecting elements like pipes and tubes may be detected by the system as well.
Configuration of further lift components
For all further lift components normally none or only a few parameters are to be collected, as these generally result out of the configuration of the other components.
Create documents
After completion of the configuration process an offer may be generated according to the determined scope of supply. Different list of parts positions can be combined to sales positions and their prices may be calculated. Individual customer and product discounts may be stored for price calculation. Further more additional information is offered for each position (descriptions, assembly instructions, drawings, diagrams a. s. o.). In addition to the configuration data overview (scope of supply, performance data, dimensions a. s. o.) all required documentations needed e.g. for TÜV acceptance or lift implementation can be drawn up. This includes for example calculation of the cylinder buckling safety, the suspension ropes safety or the bending load for the guide rails. A shaft description may also be drawn, containing all dimensions relevant for implementation within the lift shaft. Documents produced can be displayed on the screen, printed or exported in a variety of formats (e.g. pdf).
Master data import
Master data as customer and stock lists, price information or terms of payment and delivery may be imported by the ERP interface.
Order data export
Order data including all information concerning configuration and characteristics may be exported by the ERP interface.
User group orientation
With regard to the different requirements of the single user groups of a Liftmaster Pro-Installation the system offers a variety of adequate customization possibilities concerning the user interface. Usage by a final customer for example requires massive function and data reductions in comparison with usage by a technical office employee.
