We recommend going through a few cycles of several of the activities needed to integrate DataEye.
This cyclical approach has several advantages:

• At the end of each cycle, you  have a working integration (between DataEye and whatever existing IT systems the KPIs are coming from). So you will:

• have real KPI information early in the project
• be able to modify your view on KPIs and displays soon after they are created
• be able to get buy-in from operational staff early in the project

• You can modify your view on what you want, in the light of what you learn as the integration progresses. This can be very helpful because we all can change our perception of what is possible once the introduction of a new system is under way. In the alternative situation where there is single “sign-off” of requirements, this opportunity for change is often denied and this can lead to frustration.

• In the long run, because you will have an integration that suits
  your needs better, you will need less effort and expense in the future
  to discuss and amend the DataEye operation and views.

The cyclical approach does also mean, however, that it is important to get the appropriate contributions from your people when needed, particularly in planning the next cycle and in reviewing a completed cycle.

• Login or register to post comments
• Back to top