How we work?

Our processes are based on a provisioning engine. The Primary Service Provider (see what we do) needs to get inexpensive high quality resources. In order to ensure that SIS is using a high-sophisticated provisioning engine. The use cases below illustrate some of its processes. The heart is the Provisioning Engine, which automatically assignes the task to the right SIS engineer, which is illustrated in a video here.

High Security Patches need to be applied at 3 a.m. CET
1. The Primary Service Provider requests SIS to patch a specific systems.
2. The request is accepted and analyzed by provisioning engine.    
3. The provisioning engine chooses from the available SIS engineers the right skilled and tasks the request. In this case one SIS Senior engineer is needed.

  

  

High volumes of data needs to be restored 
1. The Primary Service Provider requests SIS to restore many files in a very short time-frame.
2. The request is accepted and analyzed by provisioning engine.
3. The provisioning engine chooses from the available SIS engineers the right skilled and tasks the request. In this case many Junior SIS engineers are needed.

                                                

A software needs to be scripted and a SIS engineer needs 7h and 20m to do that
1. The Primary Service Provider requests SIS to create a Microsoft script in order to be distributed via SCCM later on.
2. The request is accepted and analyzed by provisioning engine.
3. The provisioning engine chooses from the available SIS engineers the right skilled and tasks the request. In this case one Senior SIS engineers is needed.
4. Her/his time is billed back exactly based on the minutes she/he work on the task. This is also the case in all use-cases, however it is illustrated here.