Planning and system selection

Company Size Informationization Priorities

The information focus of enterprises of different sizes is not on the number of systems, but on the steps that have been taken to increase the complexity of management. Twenty-person teams first resolve the client, order and financial base records, 50 people focus on the cross-post process, and 100 people on the harmonization of master data, competencies and business analysis.

ZhiHua Tech Original Course2 minutes 51 secondsFAQs and solutions in enterprise informatization

This video is used for enterprise-infomatic knowledge learning and internal discussions.

DIRECT ANSWER

Let's see what we can do.

The information focus of enterprises of different sizes is not on the number of systems, but on the steps that have been taken to increase the complexity of management. Twenty-person teams first resolve the client, order and financial base records, 50 people focus on the cross-post process, and 100 people on the harmonization of master data, competencies and business analysis.

VIDEO NOTES

The video content of this issue is read

The following are structured textual interpretations of the video for the current period, which allow for rapid reading, internal discussion and search; it is not verbatim subtitles. Around “20, 50, 100 people in the information focus of the enterprise”, it is suggested that a distinction be made between the appearances, business causes and system improvements before deciding whether process adjustments, data governance, system integration, automation or customization development are required.

1. Processes that were out of control first after the increase in the number of people

The focus of information for enterprises of different sizes is not on the number of systems, but on the extent to which the complexity of management has grown. Twenty-person teams first resolve the client, order and financial base records, 50 focus on the cross-post process, and 100 on the harmonization of master data, authority and business analysis.

2. System capacity to be built at different stages as a matter of priority

The focus of information for enterprises of different sizes is not on the number of systems, but on the extent to which the complexity of management has grown. Twenty-person teams first resolve the client, order and financial base records, 50 focus on the cross-post process, and 100 on the harmonization of master data, authority and business analysis.

3. Ways to avoid system over-front or long-outstanding accounts

The focus of information for enterprises of different sizes is not on the number of systems, but on the extent to which the complexity of management has grown. Twenty-person teams first resolve the client, order and financial base records, 50 focus on the cross-post process, and 100 on the harmonization of master data, authority and business analysis.

WORKFLOW DESIGN

What should we do with this scene?

The first step in the project is to determine what information is to be done by the size of the enterprise, the route of construction, the product selection and the entry point for AI. The first step is to define what is to be done about the “different focus of information for enterprises with 20, 50, 100 people” and to define real inputs, expected output, tool privileges, manual clearance, unusual handling and operational acceptance indicators, before deciding whether to use rules, scripts, API, Codex or other AIAgents.

01The first process to lose control after the increase in numbers

The verification of conditions, liability, data sources and exceptions is done using real samples, and the presentation is not used as a substitute for production evidence.

02System capacity that should be built at different stages as a matter of priority

The verification of conditions, liability, data sources and exceptions is done using real samples, and the presentation is not used as a substitute for production evidence.

03Ways to avoid system over-front or long-outstanding accounts

The verification of conditions, liability, data sources and exceptions is done using real samples, and the presentation is not used as a substitute for production evidence.

IMPLEMENTATION PATH

Suggested paths for improvement

  1. 1
    Recovery status process and cost baseline

    Selecting recent and representative tasks and anomalies, identifying participants, input outputs, time and current costs.

  2. 2
    Prioritization by value, risk and conditions of implementation

    Distinction between actions that are self-executing, that require manual confirmation and that prohibit automatic processing.

  3. 3
    First, try a quantitative closed ring.

    Start with the draft, a copy or a limited scene, and keep the abnormal transferer and retreat.

  4. 4
    Extension or re-routing of routes through data decisions

    Continuous observation of accuracy, adoption, processing cycle, error and real business results.

ACCEPTANCE

How to automate the receipt and inspection is really effective.

The acceptance cannot be based solely on whether a single demonstration runs. The following results should be observed continuously using independent samples and real anomalies, and pre-modification baselines of the same calibre should be maintained:

  • Whether core processes are really shortened
  • Whether key data form a uniform calibre
  • Continued use of staff
  • Reconciling input, operating cost and business value

The authorization, approval, audit and manual takeover must also be verified when it comes to the amount, customer commitment, privacy, compliance, production change or deletion operations.

RELATED RESOURCES

Continue to learn about the programmes