Ser­vice requests can occur in very dif­fe­rent and com­plex forms. Smart­Se­arch ana­ly­zes the pro­blem on the basis of the respec­ti­ve ser­vice case. Based on this, an initi­al search result is pro­vi­ded — drawn from all ser­vice-rele­vant sources such as ope­ra­ting manu­als, spa­re parts cata­logs, or ser­vice reports. Using seman­tic search and con­text-depen­dent fil­te­ring, the­se initi­al results can be suc­ces­si­ve­ly nar­ro­wed down until the desi­red solu­ti­on is found.

In princip­le, all ser­vice-rele­vant infor­ma­ti­on can be used as data sources. This can be the tickets stored in Inno­soft, assign­ments or ser­vice reports on cases that have alrea­dy been pro­ces­sed. But exter­nal sources can also pro­vi­de valu­able addi­ti­ons. All data is pro­ces­sed using AI-sup­por­ted, auto­ma­ted pro­ces­ses and repre­sen­ted in the form of a digi­tal twin. This digi­tal repre­sen­ta­ti­on of your machi­nes and sys­tems, as well as their inter­nal struc­tu­ring and func­tio­n­a­li­ties, is made direct­ly acces­si­ble in Inno­soft by Smart­Se­arch. Smart­Se­arch thus acts as a sin­gle source of truth and can pro­vi­de cen­tral access to all data rele­vant to the service.

In addi­ti­on to the ticket sys­tem, Smart­Se­arch is also avail­ab­le in Innosoft’s deploy­ment plan­ning and mobi­le field ser­vice solu­ti­on. This means that your dis­patchers can alrea­dy iden­ti­fy rele­vant docu­ments when plan­ning the assign­ment and pro­vi­de them to the tech­ni­ci­an on his mobi­le device. This way, an initi­al solu­ti­on pro­po­sal is avail­ab­le to him befo­re he arri­ves, which he can imple­ment direct­ly at the customer’s site. Track the resul­ting incre­a­se in first-time fix rate and reduc­tion in mean time to repair using various sta­tis­tics in Inno­soft. Redu­ce your ser­vice cos­ts and incre­a­se cus­to­mer satisfaction.