I just want to ask a general question. Is there anyone out here who's using APM (more info at www.alignability.com)?
At the moment I'm figuring out if it's usefull to make the step to APM. Now we use hp OpenView Service Desk 4.5 with Service Pack 17. But there is the posibility my company wants to introduce and use the APM model. Now we must do some tests.
If there is someone, or if there is someone who knows APM but didn't migrate to APM, please let me know for what reasons, thanks a lot.
Hi We are used more then 3 y. APM. Why - because all docs is ready and not need to write :). At principal, you can start deploy own processes and procedure , but how time you spend? but if you get APM, to implementation(installation) you spend some minutes. The other time need to study your peoples use SD by this documentations. All docs did as word doc and as interactive web docs, so people every time can read if not remember or like to study new process.
Hi Yes , disadv. exist and we add and modefy the docum. for this addons. Example: Calssification in SR(service call) was disabled, we activated and add this to docs. Workflow - doc. about workflow not exist, we activate and modefy the doc.
At princiapl SD as was, so at a be SD after update to APM, APM that just process documentation and all.:)
I wouldn't say that there are disadvantages per SP. There are the usual requirements of any process that is you must keep it up to date and relevant. From my experience I would say that after it is implemented you look to re-evaluate the whole process again and see where you business benefits from having used it and where the process model does not benefit the business. Identify these areas and you can then update the process and OVSD to support the process. I think that this is important to keep tailoring the APM model to fit the ever changing business (and IT needs) of your company. APM is good to get you a process integrated with OVSD quickly and to get working - but in my mind it needs to be reviewed and kept relevant and up to date just like and other process.
One disadvantage for someone that has used the default OVSD application is that the name changes of items and attributes can take a while to get used to / figure out.
e.g. Service Calls become Support requests Incidents becomes Alarms Workgroup becomes Group
HI Alarm,Support Request , etc. At the first time I thin that as Mark, but how it change from any Localization? Example: in Russian Work order -> Narjad(but in russian transcription), Service call - > Zapros. That the same. Believe in Belgian too.