With expectations rising over how alerting and warning systems perform, need also rises to think "out of the box". Consider "the box" a notification product, a solution that performs alerts, warnings, and notifications through one or more communications modes - say telephones, texting, sirens, broadcast, social media, internal networks, digital signage, or whatever. These products normally do a fine job of their intended purpose. However, that's often not enough these days to make sure the right people get the right information at the right time.
What if you think out of the box and link these systems to other systems? No genius required to figure out how these products would work better if they are connected to other products, say, an incident management tool. If you've operated an alerting product, particularly while a critical event was unfolding, you've likely thought, "Wouldn't it be nice if...?" While it's pretty easy to see how these links would make a big difference, there are challenges to making the connections really happen.
Enter the systems integrator. This is a company that knows how to take disparate systems and make them work together. There are special skills involved, and particular processes to follow. The process begins by developing a real understanding of the problems to be solved. Then, technical expertise comes into play for design. Design includes a number of elements including architecture, functionality, speed, usability, data management, and evolving technology. Then, the systems integrator starts building the box outside the box.
Beyond the technical challenge, there's the ever-present cost challenge. The cost of systems integration can range from being ridiculously inexpensive for value returned to being ridiculously expensive. Among contributing factors is whether the product ("the box") was built to accommodate links. Before buying, it's a good idea to ask a vendor if their product has an API. That's an "application program interface", a fancy name for saying the vendor has made the keys available to gettting data into and out of their product. A good systems integrator can work around a product that has no API, but having one helps.
The key is to think out of the box. Don't think it can't be done because it hasn't been done...even if the vendor who sold it to you doesn't know how to do it. Making and selling products is one discipline. Integrating products is another. We've not seen a lot of examples of companies doing both well.
So, don't complain about the limitations and think, "Wouldn't it be nice...?". Get someone who can help you. Find out what the real cost and return will be. Qualified systems integrators are out there, and if you can't find them, we know some good ones.
You may be surprised at how easy it is to make a strong business case and receive funding for a systems integration project.
All the best,
Rick
(You can request a copy of our guidance for writing good business cases at info@galainsolutions.com.)
Top
What if you think out of the box and link these systems to other systems? No genius required to figure out how these products would work better if they are connected to other products, say, an incident management tool. If you've operated an alerting product, particularly while a critical event was unfolding, you've likely thought, "Wouldn't it be nice if...?" While it's pretty easy to see how these links would make a big difference, there are challenges to making the connections really happen.
Enter the systems integrator. This is a company that knows how to take disparate systems and make them work together. There are special skills involved, and particular processes to follow. The process begins by developing a real understanding of the problems to be solved. Then, technical expertise comes into play for design. Design includes a number of elements including architecture, functionality, speed, usability, data management, and evolving technology. Then, the systems integrator starts building the box outside the box.
Beyond the technical challenge, there's the ever-present cost challenge. The cost of systems integration can range from being ridiculously inexpensive for value returned to being ridiculously expensive. Among contributing factors is whether the product ("the box") was built to accommodate links. Before buying, it's a good idea to ask a vendor if their product has an API. That's an "application program interface", a fancy name for saying the vendor has made the keys available to gettting data into and out of their product. A good systems integrator can work around a product that has no API, but having one helps.
The key is to think out of the box. Don't think it can't be done because it hasn't been done...even if the vendor who sold it to you doesn't know how to do it. Making and selling products is one discipline. Integrating products is another. We've not seen a lot of examples of companies doing both well.
So, don't complain about the limitations and think, "Wouldn't it be nice...?". Get someone who can help you. Find out what the real cost and return will be. Qualified systems integrators are out there, and if you can't find them, we know some good ones.
You may be surprised at how easy it is to make a strong business case and receive funding for a systems integration project.
All the best,
Rick
(You can request a copy of our guidance for writing good business cases at info@galainsolutions.com.)
