Supply Chain Management

From MIKE2 Methodology

This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.

Nothing can break a well-engineered supply chain like for poor quality information. Issues due to data accuracy or integrity can often stop the automated supply chain as information fails to load in systems. Using an Information Development approach, organisations should aim to improve data quality over time in an ongoing fashion. Data Latency is also a major issue. Minimising this 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 that allows reuse of much of the existing technology

Contents 1 An Overview on the Business Solution 1.1 Definition of the Solution Area 1.2 Impacted Industries 1.3 Why this Solution Requires an Information Development Approach 2 Typical High Level Business Requirements 3 Project Delivery using MIKE2.0 3.1 Key Components Required from SAFE Architecture 3.2 Applicable Activities from the MIKE2.0 Methodology 4 Best Practices for Implementation 5 Areas of Complexity 6 Applicable Software Solutions

An Overview on the Business Solution

Definition of the Solution Area

Impacted Industries

Why this Solution Requires an Information Development Approach

Typical High Level Business Requirements

Project Delivery using MIKE2.0

Key Components Required from SAFE Architecture

Applicable Activities from the MIKE2.0 Methodology

Best Practices for Implementation

Areas of Complexity

Applicable Software Solutions