When an organization identifies the need for a new incident management software application, a common question is, “Should we build it ourselves, or should we source an off-the-shelf product?”
You have to start by assessing how complex your requirements are and the level of resources that will be required to meet them. Simple data capture is often seen as acceptable, and it may well be… until a past incident needs to be reviewed or an investigation must be launched. Without the broad search and investigation functionality of a comprehensive (and proven) incident management solution, an organization exposes itself to potential litigation and financial impact.
So, accepting that powerful, robust and scalable incident management software is preferred, what’s the best way to acquire it?
[click to continue…]
As stated in my previous post, Service-Oriented Architectures have changed the way we make software here at PPM 2000. With this change came new opportunities, our largest being systems integration. Let’s start with a definition:
“In information technology, systems integration is the process of linking together different computing systems and software applications physically or functionally, to act as a coordinated whole.”
At PPM, this means that our software gets to be a part of the software eco-system running in the ‘cloud’ or at our customer’s sites.
[click to continue…]
For my first post, I want to talk about something I have found to be both challenging and rewarding, Service-Oriented Architecture or… SOA. I am sure many of you have read the recent blog post from Google engineer, Steve Yegge where he takes a shot at both Google+ and Amazon. Hidden in this article are some real ‘gems’ related to Service-Oriented Architectures and how pivotal they can be when it comes to a company’s communication and collaboration.
The similarities I have drawn from this article are staggering when compared to the challenges we face here at PPM 2000:
[click to continue…]
