Unified Data improves business decision making by aggregating data and analytics from diverse business applications on multiple systems and allowing relevant data to be presented on a customized GUI (based on user preference) so that information can be easily viewed, monitored and controlled from a desktop dashboard.
This is not a new application. Unifying data has been widespread and has been used for more than a decade in the financial markets. It is an easy application to cost justify. In financial services speed and better decision making quickly translates into profits. These markets are technically challenging. The data streams there are extremely large, numerous and complex; and the systems need to be very fast, highly reliable and meet rigorous requirements. The good news is that that Unified Data systems sector can easily adapt to the relatively simpler demands in enterprise market.
In general, these market place needs center on solving problems where there is a need to retrieve and display data from several different data streams where accessing each individual system is either slow and cumbersome or impractical.
Examples include:
- Technical help desk where access to accounting and other systems saves valuable time and keystrokes
- Need for a combined work order/trouble ticket system for telcom and computing technology needs
- Multiple systems used because of a merger or acquisition and data migration needs are complex
- A less expensive way to leverage the power of an ERP system for a small group
- Health care where new and legacy systems are being used
Let’s examine the typical process that takes place with a technical help desk to how it can be optimized. Typical steps include:
- Once there is an inbound inquiry for assistance, the first step needed is to establish the identity of the caller. Sometimes this information may be screen popped by the telephone ACD phone system for the help desk agent, if not, records need to be accessed to determine who the caller is.
- Next, it must be determined if the organization is authorized to receive services, has paid or contracted to pay and to determine what level of services they are. This information is usually contained in an accounting system database.
- There may be an additional step at this stage to see if the caller is certified and or has the technical proficiency to access the help desk. This may require another database to be accessed.
- Next, a support ticket needs to be created and entered into the trouble ticket system. This system may be able to tell whether someone else is already working on this trouble case. If not, another database may need to be checked.
- Presumably the trouble ticketing system contains the customer records with the details of the deployment, relevant software release and the system configuration. If not, other applications need to be checked for more information.
How Do I Get Started?
Once you engage us, we start by scheduling a needs assessment to understand the project scope. This includes a series of in-depth interviews with you and relevant project stakeholders to understand your data flows and how your users need to use the data and the relevant format to present it. Next, we build a prototype to show what the solution could look like. Once this agreed upon we prepare a detailed work scope that outlines roles and responsibilities. Upon agreement of all parties we prepare and deliver the finished solution. The entire process typically takes 30 days or less to complete.
If you have a problem that you would like to discuss with us, please call or write.