Module 3: Key concepts
The hierarchical structure | Everything about optimization | The architecture of the solution | Appointment trajectory3 stages make up each module : course, summary and quiz. You are currently on the course section.
The Summary section shows, with key images, the keywords to remember.
The Quiz section is aimed to assess your knowledge and thanks to your success to move forward to the next module.
The hierarchical structure
Welcome to the first sequence in this module devoted to learning about key concepts for Opti-Time’s hierarchical structure.
We are going to look at the structure Opti-Time provides for handling and structuring the people and places that play such a pivotal role in your business enterprise.
Structural elements such as:
– resources;
– work sites;
– regions;
– teams.
These will be key components in the optimizations you run to streamline your daily business operation.
Let’s find out now what this hierarchical structure looks like…
Everything about optimization
This second sequence in the module puts the spotlight on the optimization process that is central to the Opti-Time application. We will show you how routes and interventions can be optimized through a series of calculations performed by two engines: the real time engine, and the batch engine. We will also see how an optimization proposed by Opti-Time is the combined result of an interplay between numerous variables, the most important of which are the optimization constraints, and the parameter settings.
We will examine how business constraints in time and space affect your optimization, and the significance of judicious handling of your Optimization parameters.
Once your first optimization has been run, we will look at the notions of journal and results and explain how to interpret the optimization proposed by Opti-Time.
Finally, we look at how to be realistic when setting constraints: realistic working hours, achievable journeys or routes, breaks and rhythm of working, how long each intervention lasts. Assessment of how apt your constraints are is vital for a successful optimization… for your teams, your routes, and your enterprise.
Optimization requires diligence and attention to detail!
The architecture of the solution
In this third sequence of this module, we look at the architecture of the Opti-Time solution, so you can see how it is constructed.
So here we are going to look at areas such as applications, servers, databases, webservices, geoservices, optional add-ons that can be bolted on to the solution, synchronous and asynchronous services.
The path of an appOINTMENT
This last sequence of the module of key concepts explores the life cycle of an intervention (or appointment) from the time the customer calls, for example to report a repair that is needed, or request a maintenance visit, through to its fulfilment when a technician calls and solves the problem, or delivers the service to the end customer.
Let’s follow the trajectory for this ‘workflow’ step by step, from the request recorded in the call centre through to a service being fully delivered.
This workflow trajectory is adapted, evidently, to predefined processes in your organisation, through customization of Opti-Time as described in earlier sequences.
Click on the right down button and then on the Opti-Time course to continue 