BusinessTime

From MIKE2 Methodology

MIKE2 recommends use of a BusinessTime model when defining requirements. This simple model classifies when synchronization of business events are required by different systems to meet their information needs.

BusinessTime events can generally be defined in 3 categories:

• Transactional events such as web page requests or queries against OLTP applications.

• Events that mandate near real-time processing or that which must be done on at least an hourly basis (such as Order Processing or Updates of Customer Details). Whereby in the past nightly batch processes were used support synchronization of this data, the actual business requirements mandate it be propagated when the event occurs.

• Areas where significant delays are acceptable. These involve supporting business requirements such as trending, analytics and summary reporting for DSS and MIS applications.

Moving to a BusinessTime model often involves progressively automate integration processes between systems through Services-Oriented Architecture. Minimising latency mandates the need to remove manual processes that require an operator.

Successful Information Integration often follows a progressive process whereby processes go from manual, to batch, and then finally to real-time synchronization. The transition from batch, to real-time, through to Services-Oriented Architecture allows reuse of much of the existing technology.