Product structure of the production scheduler Asprova

*Asprova MS – Short term scheduling. Using finite-capacity scheduling, creates detailed production schedules at high speed based on master and order data. Main body of the production scheduler.

*Asprova LS – Long term scheduling. Enables creation of a schedule with finite-capacity ‘rough’ scheduling, useful in longer projections for factory management.

*Asprova MRP – Material requirement planning. Although not as accurate, this module allows creation of a schedule with the minimum of master data, if there is no need to create detailed schedules for factory resources.

*Asprova APS – Advanced scheduling. This license includes Asprova MS, LS along with the Sales and Purchase options. This allows performing long, mid, and short term scheduling across sales, manufacturing and purchasing in a single module.

*Asprova BOM – Bill of materials. This license allows editing of the master data, and some limited scheduling capability. This module is useful to have more than one person managing the master data, without purchasing another full MS license.

*Asprova MES – Manufacturing execution. Enables viewing of the schedule, and entry of results data. Typically this module is used by the shop floor staff to report the actual progress of the scheduled operations. Sales divisions can also use this module to check due dates and schedules for specific orders. (One license of Asprova MS is required in order for this license to be meaningful.)

*Asprova NLS / Asprova DS – Networked licensing. Typically Asprova licenses are enabled via a USB dongle. In order to avoid the need to physically carry dongles to other PCs to use Asprova, the network licensing system allows remote PCs to connect to a server which holds the licensing information, and obtain a license via the network. This opens up the possibility of sharing licenses across factories in multiple countries.
Asprova DS allows storing the project data itself at a common location as well, and enables ‘transactions’, which for example allow users of the MES modules to submit results data while the main MS/APS module is running. (Normally, a project would need to be saved and given to the other user, meaning only one user can edit a project at a time.)