Technical specification for enterprise informatization
Part 1: enterprise resource planning system (ERP) specification
order
At present, the series standards of enterprise informatization technical specifications are composed of the following parts:
-Part 1: enterprise resource planning system specifications;
-Part 2: Product Data Management System (PDM) specification;
-Part 3: Customer Relationship Management System (CRM) specification;
-Part 4: Collaborative Product Business System (CPC) specification;
-Part 5: Supply Chain Management System (SCM) specification;
-Part 6: Office Automation System (OA) specification;
-part 7: enterprise information supervision norms;
…………
This part is divided into 1 part.
Technical specification for enterprise informatization
Part 1: enterprise resource planning system (ERP) specification
1 range
This part gives the software functions, basic requirements and methods related to the development management and implementation management of enterprise resource planning system (ERP).
This part is applicable to the selection of ERP products and services by enterprises.
2 Terms and definitions
The following definitions apply to this part.
2. 1
Accept acceptance
An activity of the authorized representative of the buyer, through which the buyer accepts the ownership of part or all of the software products that perform the contract.
2.2
Demander and acquirer
Organizations that purchase software products for themselves or other organizations.
2.3
Approve
A written document signed by the authorized representative of the buyer that is satisfied with the developer's project plan, design or other aspects can be used as the basis for the next stage of work. The approval does not exempt the developer from the responsibility of meeting the contract requirements.
2.4
Architectural architecture
The organizational structure of a system or CSCI, indicating its components, the interfaces of these components and the operational concepts between them.
2.5
Build in the development phase
1) A software version that meets a specific subset of all the requirements that a complete software needs to meet.
2) Time taken to develop a software version that meets a specific subset of requirements.
Note: The relationship between the terms "development phase" and "version" depends on the developer; For example, a development stage can be realized by several versions, and a development stage can also publish several parallel versions (such as in different places) or be used as synonyms.
2.6
Computer database
See database.
2.7
Computer hardware computer hardware
A device that can receive and store computer data, perform a series of system operations on computer data or generate control output.
This device can realize basic interpretation, calculation, communication, control or other logical functions.
3 General rules
ERP product design follows the following principles:
-The underlying design is highly integrated, and all kinds of data, calculations and * * * are highly unified, which is different from the simple connection of a single type of application;
-The products adopt an advanced and stable IT development platform, and the system is stable, safe, flexible and extensible;
-There are abundant practical cases in various industries;
-Software providers maintain sustained and healthy development of their own businesses to ensure the sustainable development of products and services;
—— Conforming to relevant systems and regulations, and suitable for enterprise management and humanistic and cultural characteristics.
In order to realize the above principles, relevant standard working methods and contents should be established in product research and development, implementation, service and product function.
4 technical requirements for ERP product development
Product research and development should be rigorous and scientific, the whole system should be complete, flexible, rigorous and efficient, and strict management control should be carried out to ensure the quality of products and the speed of market reaction, the continuity of work, the traceability of various problems of products, and the preservation of various process control documents and records. The following is the framework description of the most basic process of product research and development, and the template of documents in the process is not provided, which can be designed and determined by each enterprise according to its own needs. The following will explain the main working process in the form of flow chart, and explain it in tables respectively.
4. General process of1R&D cycle
The general process of R&D cycle is shown in figure 1.
Figure 1
……
5 ERP product service technical requirements
5. 1 Basic organizational structure
At least an independent "ERP service department" should be established, which is different from the product research and development department.
5.2 Basic personnel composition
Engineers, management consultants, customer support personnel, system analysts, programmers.
5.3 Overview of each job
See Table 6 for all work contents.
Table 6
Describe the service content, the purpose of the service provider and the service object at the applicable stage of the service name.
In the implementation stage of management consulting, management consulting consultants investigate customers' business processes and provide management consulting reports for customers' business process optimization.
system integration
In the stage of installation and implementation, engineers of ERP service department and technical engineers of user information department install ERP into the user's server and debug the network and peripheral equipment to ensure that the software can be implemented smoothly in the user's overall environment.
Education and training implementation stage, maintenance stage, ERP service department and consultant user department &; Through the pre-designed teaching materials and processes, the personnel of the Information Department let students know the standard functions and operation modes of ERP, so that students can operate the system smoothly after learning and help the implementation of the system.
The ERP service department consults the user department in the system implementation stage &; With the help of pre-designed implementation counseling process and information tools, information department personnel can scientifically and systematically enable users to successfully introduce ERP into enterprises as planned.
Hotline service maintenance service stage ERP service department service personnel user use department &; Through well-trained service personnel, the personnel of the Information Department accept all kinds of inquiries from users about the use of software, answer questions for users, provide guidance, and ensure users to use ERP smoothly.
……
6 ERP product functional technical requirements
As a real ERP product, it should be able to meet all aspects related to the most important management and operation behavior of the enterprise in terms of basic functions, and at the same time, take into account the constant changes of the actual situation, so as to lay a good foundation for adapting to the changes of management. The framework specifications and evaluation methods provided below can quickly evaluate the basic functions of an ERP system and explain them in detail in tabular form.
6. 1 general description
Description of evaluation method
A) Table 7 is a summary of the score percentage and distribution points of evaluation indicators of each module *100;
Table 7
Total score of functional category
Environment and user interface
system integration
systems management
Basic information
stock
buy
marketing
Early month (abbreviation of beginning of month)
Workshop task management
craftsmanship
Material requirements planning (MRP)
expense
human resources
quality management
business decision
general account
Automatic input
acceptable
deal with
fixed assets
total
B) The column description of each evaluation index is as follows:
1) Category: functional classification of this module;
2) Grade: refers to the importance of this function to users;
3) Distribution: refers to the distribution ratio of this function in the whole module;
4) Function description: description of the function;
5) Evaluation criteria: the evaluation index of the exquisiteness and achievement level of this function;
6) Yes or No: refers to whether this function of management software meets this evaluation standard;
7) Weight: refers to the importance of this appraisal standard in this function;
8) Score: refers to the score of this function after the weight of evaluation standard is assigned.
Note: The above assessment indicators are for reference only.
6.2 Environment and User Interface
……
6.3 system integration
……
6.4 system management
……
6.5 Basic information
……
6.6 inventory
See table 12 for inventory.
Table 12
The category grade distribution function describes whether the assessment standard has a weight score.
Whether the basic data C 5 inventory system setting query determines the permission 2
Automatically print file 2 after saving
Define the warehouse and accounting period of warehouse 1.
B 10 warehouse basic information management definition warehouse type 3
Defines whether virtual warehouse 2
Define Inventory Operation Reason 3
Does C 5 user warehouse authorization support setting the user's operation authority for warehouse 3?
C 5 inventory initialization inventory initialization 2
Inventory initialization de-confirmation 3
Material Inventory Definition A 15 Inventory management of non-inventory accounts can manage the entrusted processing materials of other enterprises 1.
You can manage other non-inventory items, such as service items or expense items 1.
A 15 Control and management of inventory items can define warehousing and warehousing rules of inventory items. For non-standard business, you can issue a warning message or force not to handle 1.
You can select some warehouse items to participate in MRP operation 1.
Customizable Available Quantity Business Rule 2
You can define whether to allow zero outbound 2.
You can define whether the available quantity of outbound 2 is allowed to be exceeded.
You can customize the expected issue quantity rule 1.
User-defined rules for expected receipt quantity 1
Inventory backlog management, shelf life management and early warning tips II
Users can define the age of warehouse category to analyze the age of inventory item 3.
A 15 management of the same material storage location The same enterprise can store materials in multiple factories.
The same factory can store two in multiple warehouses.
The same warehouse can store 1 in multiple locations.
1 can be stored in multiple batches in the same location.
……
refer to
GB/T 1526- 1989 information processing data flow chart, program flow chart, system flow chart, program network diagram and system resource diagram.
Symbols and conventions for document preparation are based on
GB/T 8566-200 1 information technology software life cycle process
Gb/t11457-1995 software engineering terminology.
Gb/t 1 8491-2001information technology software measurement function scale measurement part1:concept definition.
GB/T 18492-200 1 information technology system and software integrity level
GB/Z 18493-200 1 information technology software life cycle process guide
SJ 20778-2000 Software Development and Documentation
Accounting System for Enterprises Accounting (2000) No.25