Asprova FAQ

Stage content		Support
	Understanding the current situation, and setting of goals Fill out the 'Profit increase diagnosis' sheet with information about the current situation and goals to be achieved. The goal should be somewhere between the current situation and the ideal state. Goals should be set with the intention of not changing them during the implementation process.	Web seminar [Free] Profit increase diagnosis [Free]
	Learning about Asprova Install the free trial version of Asprova. Use the introductory manual to become familiar with the examples, and the various operations available in Asprova.	Asprova trial version [Free] Introductory manual [Free]
	Prototype creation and system consideration Make a prototype using data from your factory. Evaluate the prototype, determine the scope of the system to be implemented and whether any interfacing/assisting systems will need to be developed. Divide the problem points into: A：Issues which can be handled by Asprova standard features B：Issues which can be worked around by altering the way scheduling is carried out C：Issues which can be solved by peripheral systems or Asprova plugins Before making an official decision to use Asprova, a prototype should always be made and thoroughly evaluated, to give a clearer picture of what profit increase will be achievable.	Hands-on training [For a fee] Trial license (temporary dongle) [For a fee] Prototype creation support [For a fee]
	Contract and project team founding Sign a contract for the necessary Asprova license(s) and development/consultation support. A team to work on the implementation of the 'profit increase' project should be decided on. Typically this is a 3 person team consisting of an overall leader, one production managment staff, and a system management staff.	Usage contract [For a fee]
	Data preparation The actual data is prepared. The preparation of the necessary master data requires a lot of effort. Typically, it can take one person more than a month to complete. It should be made possible for the person in charge to set aside time for the data preparation. It is a difficult task to gather large amounts of accurate data, and sometimes this job seems to have no clear end in sight. In those cases, we recommend starting the running of Asprova with the data mostly complete/accurate, and fine tuning the data as the implementation is run.	Consultation [For a fee] Program development [For a fee]
	Additional program development In many cases, Asprova is connected with other existing systems, to make the overall running smoother. It is possible to use Microsoft Access, Visual Basic etc to develop interfaces to existing systems beforehand.
	Usage manual creation Explains the new way of handling work instructions, result gathering, order processing.
	System explanation meeting The 'profit increase project' can bring revolutionary changes in the workplace. Habits for work instruction issuing and result gathering may change significantly. It is well recommended to hold a meeting where these changes and the purpose behind them can be explained to those who will be involved.
	Test running Test running begins. The test period is usually 1 or 2 months, after which the implementation is put into full use.
	Maintenance Most factories will likely have items and resources changing as time goes by. In order to gain the full benefits of long term use of Asprova, such as future upgrades and new versions, a maintenance contract is entered.	Maintenance contract [For a fee]

Implementation timeline