Value above all-enterprise software development

One of our Deputy Directors was in charge of finance. The first sentence we asked the software department was:

How much value can this system bring to enterprises?

The second sentence is:

What kind of exception reports does it provide?

What managers often like to say is that it is normal not to show it to me. I want to see reports with problems.
That is, what kind of analysis report do you provide when a problem occurs during enterprise operation.

For example:
What should a supplier management system do?
I think it is probably about managing our suppliers,
Record the following content:
Contact person, address, phone number, supply of materials, price, delivery cycle, and credit ..

Error!

These items are made in an Excel table. What should I do ??

Management and management is to help me manage and analyze the system.
What is the value of supplier management?

We can't look up from the data, but from the business perspective.

Therefore, we try,
This system helps the management personnel understand the suppliers with high supply volume and good supply quality.
Details:
Find the top ten suppliers:
Comparison of requirements: Price, delivery cycle, credit, and quality.
The material selector can select suppliers based on their proportions.

The person who provides the material selection personnel did not report the exception of supplier selection according to the system suggestion rules.

This is the value

Then, we will push from the business what data we need and what data is not in the system (determine the application domain), and ensure that the system can be integrated into the existing enterprise information system.

Three factors to consider for system implementation:

In China, many companies are striving to launch ERP, MRP, mrp2, SCM, and other systems first. Even some securities companies say they are going to ERP.

According to my personal experience and understanding, many companies fail to implement the program.
I analyzed the following reasons:
1. The company lacks it information.Unified and coherent wholeConstruction Objectives
2. Internal CompanyLack of strong IT supportDepartment, CTO, and CIO.
3. CompanyCannot guarantee the provision of IT information construction resources(Including manpower)
4. CompanyExisting culture and valuesCannot work with the purchased system.

The first reason is very important. Most companies do not have a unified and consistent overall IT construction goal.
As a result, the online system cannot move towards a unified goal, resulting in a waste of manpower and material resources.

The second reason is second only to the first one,
Because I once met a boss who talked to me like this,
"Why cannot our system go to Oracle ?"
My manager said that the current system will not be applied when purchasing Oracle, and many of our systems are already running on MSSQL.
"Can't we afford such a large company? MSSQL security is so bad, you can change it if you have the opportunity ."

I believe that many CIOs and ctos in China are either absent or served by the Vice President. These Vice Presidents may be unable to take into account the IT information system construction due to other problems, the company's IT construction is usually unable to obtain corresponding strong support, resulting in IT construction failure.

The third reason is that I am too lazy to say,

Gu yuyun: I want my horse to run fast, and I want my horse to eat grass.
-- Common Faults of most Chinese companies.

The fourth reason is a problem of enterprise management. An enterprise (a year ago) will have its own corporate culture. Therefore, people who wish to change the culture of the enterprise through a system, in the end, we will find that corporate culture determines the value of this software. Companies that launch sap do not think they are big companies or large enterprises,Ultimately, the value of this software will be determined by your corporate culture..

After talking about so many illusory things, let's talk about the actual things,
The following content is a summary of IT practitioners.

What it personnel should do and shouldn't do in an Enterprise
If you have been in this industry for more than a few years, skip this article or share your experience.

1.Enter an EnterpriseShouldn'tWhat you do is to get involved in big projects. If you write code, the first three months of writing are definitely spam. If you don't believe it, please read what you wrote in a year later. (If you are still in that company)

ShouldLookCompany System ProcessFigure: Let's see the actual running process of the company,
Deal with the relevant departments of the system to see the company's organizational structure. (because software is operated by people after all, you don't know the basic information about these users, something made will certainly not be liked. At the same time, you can know who is the contact person of the system and who is the final decision of the system's success through understanding of the personnel of the relevant departments of the system. This will help you understand the customer's needs in the future, obtain resources to lay the foundation)

These seem unrelated to it work, but they actually work fine.

I think every technical staff member thinks that these things should not be handed over to me. I only need to do technical work. However, as it personnel, you must goParticipate in company ProcessTo consider the problem from the perspective of the business logic of the station, (in addition to the idea, it must also promote participation in the work of the Department, of course, usually in Chinese enterprises, what should I do if it personnel cannot obtain work support? Give up or continue pushing?Do not think what people think, do not do what people do (what is creative work, what is value, how can we get more work experience in a short time? What is growth ?),In this way, my personal abilities have been greatly improved as my work has been promoted .).

2.Do not complain about the work done by a colleague at work.
Because first, you don't know under which circumstances the decision is made (it may be due to abnormal customer requirements, or it may not be enough time, you may not be able to get the corresponding support). Second, your complaints may cause tension between you and your existing colleagues.

What can be done isReconstructionAfter learning about it, we need to perform local reconstruction, further understand it, And then perform a larger reconstruction.
And mustExercise cautionBecause your changes may make other systems unable to run properly before you have a complete understanding of the entire enterprise system.

3.Do not blindly launch new systems or design new systems

In turn, the task isReconstruction of existing systems.
The above refactoring refers to code-level refactoring, which usually occurs in a system, and here refers to restructuring between systems.

For example:
Are there any duplicate functions between systems? Duplicate data?
Can the system be merged?
Is there a problem with data exchange between systems?
Is the corresponding interface between systems reasonable?
Can our processes form a unified planning chart between systems?
In which system can the latest requirements be met?
And so on.

4.Communicate Frequently within the department
If an enterprise's IT department is well-established, this problem can be easily solved.
If a single IT department is responsible for a part of the system, there may be poor communication.
AI,Simple textMa, Chinese culture has been like this for thousands of years.
Therefore, you must take the initiative to communicate with each other. Some people may say that you are a little confused.
At this time, you have to give yourself some courage to say,Let people talk about it in their own crab Road..

In fact,High team value, high personal value. The so-called, the skin is not saved, Mao will be attached.

You are welcome to share your views and experiences and make common progress.