First, give conclusions that can be used for decision-making
The starting point for informationization should be business issues, not software names. Sales trails are lost in such a way that customers can be treated and followed up; orders, inventories and deliveries are often inconsistent and priority should be given to breaking orders to performance; business data are not available in a timely manner, and master data and key indicators are harmonized.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
Interviews with front-line and managers to map current status processes and data flows.
Validation Key Dependence
Select a business closed circle to establish a baseline for processing volume, time and error.
Development of assessable outcomes
Compare process optimization, product purchase, system integration and custom development.
Make sure you decide the next step with the real results.
Piloting in one sector or region, stabilization and replication.
How do you understand it in the actual business?
Trade enterprises want to be on the CRM, ERP, and BI at the same time, but the biggest problem is that sales orders cannot be synchronized with inventories. First, by harmonizing the calibre of customers, commodities, and orders, connecting the inventory and the inventory, management will have reliable performance data; then by expanding marketing and business analysis, it will be easier to succeed than if three systems are online.
The easiest pit to step on.
Increased efficiency of the system
Designing processes by management only, without first-line users
If basic data and responsibilities are not being managed, complex statements are first made
How should we end up receiving and confirming?
The first phase should check whether the process is truly closed, whether the data is clearly defined as the system’s primary responsibility, whether users are continuously using it, whether anomalies are processed, and whether baseline indicators are improved. The system is only on line and must be operational in a long-term manner.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.