CN115271294B - Standardized management system for enterprises - Google Patents
Standardized management system for enterprises Download PDFInfo
- Publication number
- CN115271294B CN115271294B CN202210374424.9A CN202210374424A CN115271294B CN 115271294 B CN115271294 B CN 115271294B CN 202210374424 A CN202210374424 A CN 202210374424A CN 115271294 B CN115271294 B CN 115271294B
- Authority
- CN
- China
- Prior art keywords
- standardized
- department
- module
- new
- departments
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0637—Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The application discloses an enterprise standardized management system, which comprises: loading a standardized organization architecture tree according to a standardized module, wherein organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through parent-level IDs; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department; loading a corporate organization architecture tree in an original organization architecture module, wherein organization architectures in the corporate organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level; and corresponding the nodes in the standardized module to the nodes in the original organization architecture module, and realizing standardized system operation through the standardized module.
Description
Technical Field
The application relates to an information management system, in particular to an enterprise standardized management system.
Background
In some companies, as the development of the companies grows, more and more company projects and more staff are on duty. In the daily management process, various problems such as non-uniform project architecture, inflexible authority setting, irregular approval process setting and the like often exist, so that information in each hierarchy of a company is misplaced and complicated, and related information processing cannot be unified.
Disclosure of Invention
The application provides an enterprise standardized management system, which can lead companies to carry out standardized carding on each hierarchy organization architecture and personnel posts, and solve the problems in the aspects of system management uniformity, flexibility and standardization after carrying out standardization on system basic information. The specific technical scheme is as follows.
According to one aspect of the present application, there is provided an enterprise standardization management system comprising:
s1, loading a standardized organization architecture tree according to a standardized module, wherein organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through a parent level ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department;
s2, loading a company organization architecture tree in an original organization architecture module, wherein organization architectures in the company organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level;
s3, corresponding the nodes in the standardized module to the nodes in the original organization architecture module, and realizing standardized system operation through the standardized module.
Further, the standardized organization architecture tree is loaded according to the standardized module, and organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through parent-level IDs; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department includes:
when the standardized department is created, setting the ID of the selected hierarchy as the parent level ID of the newly created standardized department, and carrying out upper and lower hierarchy association; when the standardized post is created, setting the standardized department ID as the department ID of the newly created standardized post, and carrying out home department association;
wherein the hierarchy comprises: company, department, and post layers.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
the departments in the original organization architecture module are associated with standardized departments corresponding to standardized department IDs in the standard modules, and positions under the departments in the original organization architecture module are associated with standardized positions through corresponding to standardized position IDs in the standard modules.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
when a new standardization department is created by selecting the company level in the standardization module, a corresponding new department is created under the company organization in the original organization architecture module, and the standardization ID of the new department is set to be associated with the corresponding new standardization department.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
when a new standardization department is created at the division level in the standardization module, a new department is created at all division levels under a company organization in the original organization architecture module, a standardization department ID is set for the new department, and the standardization department ID of the new department is associated with the new standardization department.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
when a new standardized department is created at the project level in the standardized module, a new department is created at the project level under the corporate organization in the original organizational structure module, standardized department IDs are set for the new departments, and the standardized department IDs of the new departments are associated with the new standardized departments, respectively.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
when a new standardized post is created under the standardized department in the standardized module, a new post is created under the department associated with the standardized department in the original organization architecture module, a standardized post ID is set for the new post, and the new post set standardized post ID is associated with the new standardized post.
Further, the step of enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, and the step of implementing the standardized system operation through the standardized module includes:
and through the association relation between the standardized module and the original organization architecture module, the association operation in the processes of authorization, approval, modification and review in each hierarchy is realized.
According to another aspect of the present application, a storage medium has stored thereon a computer program which, when executed by a processor, implements the management system of any of the above.
According to another aspect of the application, a computer device comprises a storage medium, a processor and a computer program stored on the storage medium and executable on the processor, the processor implementing the management system of any of the above when executing the computer program.
In summary, the beneficial technical effects of the application are as follows: according to the application, a standardized organization architecture tree is loaded according to a standardized module, and organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through a father-level ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department; loading a corporate organization architecture tree in an original organization architecture module, wherein organization architectures in the corporate organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level; the nodes in the standardized module are corresponding to the nodes in the original organization architecture module, and standardized system operation is realized through the standardized module, so that the operation modes of automatically updating to the original organization architecture module according to new projects of templates and changes in standardized templates are unified through basic information standardization, and the consistency of departments and positions under each project is satisfied; when authorizing the system service, all the personnel of the same type can be authorized directly in a standardized post mode, and compared with the mode that character members need to be updated in time when new projects exist in the original scheme through character configuration, convenience is improved, and configuration is more flexible; when the flow is approved and configured, the standardized posts can be directly and uniformly configured, the system can automatically grasp the personnel matching the post of the project according to the project of the initiator, and the approval personnel are not required to be manually selected, so that the requirement of standardized management is met.
Drawings
The accompanying drawings are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate the application and together with the embodiments of the application, serve to explain the application. In the drawings:
fig. 1 shows a flow chart of an enterprise standardized management system according to an embodiment of the present application.
Detailed Description
In the description of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings are merely for convenience in describing the present application and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and thus should not be construed as limiting the present application.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
In the present application, unless explicitly specified and limited otherwise, the terms "mounted," "connected," "secured," and the like are to be construed broadly and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art according to the specific circumstances.
The application will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.
As shown in fig. 1, in some implementable embodiments of the present application, there is provided an enterprise standardization management system comprising:
s1, loading a standardized organization architecture tree according to a standardized module, wherein organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through a parent level ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department;
s2, loading a company organization architecture tree in an original organization architecture module, wherein organization architectures in the company organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level;
s3, corresponding the nodes in the standardized module to the nodes in the original organization architecture module, and realizing standardized system operation through the standardized module.
In some implementable embodiments provided by the present application, the loading of the standardized organization architecture tree according to the standardized module, the organization architecture in the standardized organization architecture tree being associated in an upper-lower hierarchy by a parent ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department includes:
when the standardized department is created, setting the ID of the selected hierarchy as the parent level ID of the newly created standardized department, and carrying out upper and lower hierarchy association; when the standardized post is created, setting the standardized department ID as the department ID of the newly created standardized post, and carrying out home department association;
wherein the hierarchy comprises: company, department, and post layers.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
the departments in the original organization architecture module are associated with standardized departments corresponding to standardized department IDs in the standard modules, and positions under the departments in the original organization architecture module are associated with standardized positions through corresponding to standardized position IDs in the standard modules.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
when a new standardization department is created by selecting the company level in the standardization module, a corresponding new department is created under the company organization in the original organization architecture module, and the standardization ID of the new department is set to be associated with the corresponding new standardization department.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
when a new standardization department is created at the division level in the standardization module, a new department is created at all division levels under a company organization in the original organization architecture module, a standardization department ID is set for the new department, and the standardization department ID of the new department is associated with the new standardization department.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
when a new standardized department is created at the project level in the standardized module, a new department is created at the project level under the corporate organization in the original organizational structure module, standardized department IDs are set for the new departments, and the standardized department IDs of the new departments are associated with the new standardized departments, respectively.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
when a new standardized post is created under the standardized department in the standardized module, a new post is created under the department associated with the standardized department in the original organization architecture module, a standardized post ID is set for the new post, and the new post set standardized post ID is associated with the new standardized post.
In some possible embodiments of the present application, the step of mapping the node in the standardized module to the node in the original organization architecture module, the step of implementing the standardized system operation by the standardized module includes:
and through the association relation between the standardized module and the original organization architecture module, the association operation in the processes of authorization, approval, modification and review in each hierarchy is realized.
In some embodiments of the present application, an enterprise standardized management system is provided, which may include:
s1, logging in an entry standardization module, loading a standardization organization architecture tree according to a system configuration item, carrying out upper and lower level association through a father level ID, and creating a standardization department after selecting a level or creating a standardization post after selecting the standardization department;
when a standardized department is created, setting the ID of the selected level as the parent level ID of the newly created standardized department, and carrying out upper-lower level association;
setting the selected standardized department ID as the belonging department ID of the newly created standardized post when the standardized post is created, and carrying out the association of the belonging departments;
the original organization architecture module department of the system is associated with a standardized department through a standardized department ID thereof, and the post under the department is associated with a standardized post through a standardized post ID thereof;
if a company hierarchy is selected to create a standardized department, automatically creating a department under a company organization and setting a standardized ID to be associated with the standardized department;
if a division level is selected to create a standardized department, all division companies under a company organization are automatically searched, departments are created under each division company, and standardized department IDs are respectively set for the departments and are associated with the standardized department;
if the item level is selected to create a standardized department, all items under the organization of the company are automatically searched, departments are created under each item, and standardized department IDs are respectively set for the departments and are associated with the standardized department;
if a standardized post is created under the standardized department, all departments associated with the standardized department under the organization architecture of the company are automatically searched, posts are created under the departments, and standardized post IDs are respectively set for the posts and are associated with the standardized post;
s2, logging in an organization architecture module, loading a company organization architecture tree, and performing upper and lower hierarchical association on the organization architecture through a parent level ID. After selecting a company or a division level, a new organization architecture node can be created, and lower-level departments and post data are automatically added according to a standardized module preset node;
if a company hierarchy is selected, a newly created branch office or project may be selected;
if the division is created, after information such as the name of the division is filled, the division is created under the organization architecture company level when the information is stored, the system searches all standardized departments belonging to the division level and standardized posts under the standardized departments according to the type numbers, and the actual departments and department posts are automatically regenerated under the newly created division to be associated with the standardized departments and the standardized posts;
if the project is created, after the information such as the project name is filled, the project is created under the organizational structure company level when the project is stored, the system searches all standardized departments belonging to the project level and standardized posts under the standardized departments according to the type numbers, and the actual departments and department posts are automatically regenerated under the newly created project to be associated with the standardized departments and the standardized posts.
If the division level is selected, after information such as the project name is filled, the project is created under the selected division, the system searches all standardized departments belonging to the project level and standardized posts under the standardized departments according to the type number, and the actual departments and department posts are automatically regenerated under the newly created project to be associated with the standardized departments and the standardized posts.
S3, when system authorization or flow approval is carried out, the system can be managed more conveniently by using standardized settings. If the menu authorization is performed and the standardization process is not performed, the system needs to authorize the lead of each branch company, and the position or personnel of the lead of each branch company needs to be selected. After the standardized posts are available, a certain branch company can be directly selected and set to lead the standardized posts, the system inquires all actual posts with association relations according to the standardized post IDs, and then all personnel on the standardized posts can be automatically matched through the association inquiry of the personnel and the posts. When the process approver is set, the standardized posts can be set as well as the authorization, all the personnel under the standardized posts can be automatically matched, if the current project of the processor is required to be automatically identified, the department IDs related to the posts and the department IDs of the processor can be compared, and further fine screening is performed, so that the aim of automatic matching through standardized configuration is fulfilled.
According to the application, a standardized organization architecture tree is loaded according to a standardized module, and organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through a father-level ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department; loading a corporate organization architecture tree in an original organization architecture module, wherein organization architectures in the corporate organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level; the nodes in the standardized module are corresponding to the nodes in the original organization architecture module, and standardized system operation is realized through the standardized module, so that the operation modes of automatically updating to the original organization architecture module according to new projects of templates and changes in standardized templates are unified through basic information standardization, and the consistency of departments and positions under each project is satisfied; when authorizing the system service, all the personnel of the same type can be authorized directly in a standardized post mode, and compared with the mode that character members need to be updated in time when new projects exist in the original scheme through character configuration, convenience is improved, and configuration is more flexible; when the flow is approved and configured, the standardized posts can be directly and uniformly configured, the system can automatically grasp the personnel matching the post of the project according to the project of the initiator, and the approval personnel are not required to be manually selected, so that the requirement of standardized management is met.
Based on the method shown in fig. 1, correspondingly, the embodiment of the application also provides a storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the enterprise standardized management system shown in the figure.
Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.), and includes several instructions for causing a computer device (may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective implementation scenario of the present application.
In an embodiment of the present application, there is provided a computer device including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, where the processor implements the enterprise standardized management system described in any one of the above when executing the computer program.
Based on the method shown in fig. 1, in order to achieve the above objective, an embodiment of the present application further provides a computer device, which may be specifically a personal computer, a server, a network device, etc., where the computer device includes a storage medium and a processor; a storage medium storing a computer program; a processor for executing a computer program to implement the enterprise standardized management system described above and illustrated in fig. 1.
Optionally, the computer device may also include a user interface, a network interface, a camera, radio Frequency (RF) circuitry, sensors, audio circuitry, WI-FI modules, and the like. The user interface may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (e.g., bluetooth interface, WI-FI interface), etc.
It will be appreciated by those skilled in the art that the architecture of a computer device provided in the present embodiment is not limited to the computer device, and may include more or fewer components, or may combine certain components, or may be arranged in different components.
The storage medium may also include an operating system, a network communication module. An operating system is a program that manages and saves computer device hardware and software resources, supporting the execution of information handling programs and other software and/or programs. The network communication module is used for realizing communication among all components in the storage medium and communication with other hardware and software in the entity equipment.
From the description of the embodiments above, it will be apparent to those skilled in the art that the present application may be implemented by means of software plus necessary general hardware platforms.
Those skilled in the art will appreciate that the drawing is merely a schematic illustration of a preferred implementation scenario and that the modules or flows in the drawing are not necessarily required to practice the application. Those skilled in the art will appreciate that modules in an apparatus in an implementation scenario may be distributed in an apparatus in an implementation scenario according to an implementation scenario description, or that corresponding changes may be located in one or more apparatuses different from the implementation scenario. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.
The above-mentioned inventive sequence numbers are merely for description and do not represent advantages or disadvantages of the implementation scenario. The foregoing disclosure is merely illustrative of some embodiments of the application, and the application is not limited thereto, as modifications may be made by those skilled in the art without departing from the scope of the application.
Claims (7)
1. An enterprise standardization management system, comprising:
s1, loading a standardized organization architecture tree according to a standardized module, wherein organization architectures in the standardized organization architecture tree are associated in an upper-lower hierarchy through a parent level ID; creating a standardized department after selecting the hierarchy and/or creating a standardized post after selecting the standardized department; comprising the following steps: when the standardized department is created, setting the ID of the selected hierarchy as the parent level ID of the newly created standardized department, and carrying out upper and lower hierarchy association; setting a standardized department ID as a department ID of the newly created standardized post when the standardized post is created, and carrying out home department association; the hierarchy includes: a company layer, a department layer and a post layer;
s2, loading a company organization architecture tree in an original organization architecture module, wherein organization architectures in the company organization architecture tree are associated in an upper-lower hierarchy through the father-level ID; adding lower-level departments and post data according to preset nodes in the standardized module when a new organization architecture node is created by selecting a company level or a hierarchy of the companies in the level;
s3, enabling the nodes in the standardized module to correspond to the nodes in the original organization architecture module, realizing standardized system operation through the standardized module, associating the departments in the original organization architecture module with standardized departments corresponding to standardized department IDs in the standardized module, and associating positions under the departments in the original organization architecture module with standardized positions through corresponding to the standardized position IDs in the standardized module;
when a new standardized department is created by selecting the company level in the standardized module, a corresponding new department is created under a company organization in the original organization architecture module, and a standardized ID of the new department is set to be associated with the corresponding new standardized department;
when a new standardized department is selected to be created at the division level in the standardized module, a new department is created at all division levels under a company organization in the original organization architecture module, standardized department IDs are respectively set for the new department, and the standardized department IDs of the new department are associated with the new standardized department;
when a new standardized department is created by selecting an item level in the standardized module, creating a new department under the item level under a company organization in the original organization architecture module, setting standardized department IDs for the new departments respectively, and associating the standardized department IDs of the new departments with the new standardized departments;
when a new standardized post is created under the standardized department in the standardized module, creating a new post under the department associated with the standardized department in the original organization architecture module, setting a standardized post ID for the new post and associating the new post set standardized post ID with the new standardized post;
s4, when system authorization or flow approval is carried out, the standardized setting is used for management: directly selecting and setting a certain branch company to lead a standardized post, inquiring all actual posts with association relations according to the standardized post ID by the system, and automatically matching all personnel on the standardized post through the association inquiry of the personnel and the post; when the process approver is set, a standardized post is set as well as the authority, all the personnel under the standardized post are automatically matched, and if the current project of the processor is required to be automatically identified, the department IDs related to the posts and the department IDs of the processor are compared, and further fine screening is performed, so that the automatic matching is achieved.
2. The management system according to claim 1, wherein in the step S2:
when a company hierarchy is selected, then a newly created branch or project is selected; after the name information of the division is filled, the division is created under the organization architecture company level during storage, the system searches all standardized departments belonging to the division level and standardized posts under the standardized departments according to the type numbers, and the actual departments and department posts are automatically regenerated under the newly created division to be associated with the standardized departments and standardized posts.
3. The management system according to claim 1, wherein in the step S2:
if a branch level is selected, after project name information is filled, a project is created under the selected branch, the system searches all standardized departments belonging to the project level and standardized posts under the standardized departments according to type numbers, and the actual departments and department posts are automatically regenerated under the newly created project to be associated with the standardized departments and standardized posts.
4. The management system according to claim 1, wherein in step S2, when the project is selected to be created, the project is created under the organizational structure company level when the project name information is filled, the system searches all standardized departments belonging to the project level and standardized posts under the standardized departments according to the type numbers, and automatically regenerates the actual departments and department posts associated with the standardized departments and standardized posts under the newly created project.
5. The management system of claim 1, wherein said mapping the nodes in the standardized module to the nodes in the original organizational structure module, implementing standardized system operations by the standardized module comprises:
and through the association relation between the standardized module and the original organization architecture module, the association operation in the processes of authorization, approval, modification and review in each hierarchy is realized.
6. A storage medium having stored thereon a computer program, which when executed by a processor implements the management system of any of claims 1 to 5.
7. A computer device comprising a storage medium, a processor and a computer program stored on the storage medium and executable on the processor, characterized in that the processor implements the management system of any of claims 1 to 5 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210374424.9A CN115271294B (en) | 2022-04-11 | 2022-04-11 | Standardized management system for enterprises |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210374424.9A CN115271294B (en) | 2022-04-11 | 2022-04-11 | Standardized management system for enterprises |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115271294A CN115271294A (en) | 2022-11-01 |
| CN115271294B true CN115271294B (en) | 2023-10-20 |
Family
ID=83758422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210374424.9A Active CN115271294B (en) | 2022-04-11 | 2022-04-11 | Standardized management system for enterprises |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115271294B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102087723A (en) * | 2009-12-03 | 2011-06-08 | 中国移动通信集团公司 | Method, system and device for sharing enterprise address book |
| CN109242420A (en) * | 2018-08-22 | 2019-01-18 | 中国平安人寿保险股份有限公司 | Authority control method, device, electronic equipment and storage medium |
| US10346444B1 (en) * | 2012-01-12 | 2019-07-09 | OpsDog, Inc. | Management of standardized organizational data |
| CN112905966A (en) * | 2021-02-22 | 2021-06-04 | 梧州学院 | Enterprise standardized information management system |
| CN113269459A (en) * | 2021-06-08 | 2021-08-17 | 深圳市育联网大数据有限公司 | Method for constructing sports network organization system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10229185B2 (en) * | 2015-06-30 | 2019-03-12 | Veritas Technologies Llc | Method and system for configuration management of hierarchically-organized unstructured data using associative templates |
-
2022
- 2022-04-11 CN CN202210374424.9A patent/CN115271294B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102087723A (en) * | 2009-12-03 | 2011-06-08 | 中国移动通信集团公司 | Method, system and device for sharing enterprise address book |
| US10346444B1 (en) * | 2012-01-12 | 2019-07-09 | OpsDog, Inc. | Management of standardized organizational data |
| CN109242420A (en) * | 2018-08-22 | 2019-01-18 | 中国平安人寿保险股份有限公司 | Authority control method, device, electronic equipment and storage medium |
| CN112905966A (en) * | 2021-02-22 | 2021-06-04 | 梧州学院 | Enterprise standardized information management system |
| CN113269459A (en) * | 2021-06-08 | 2021-08-17 | 深圳市育联网大数据有限公司 | Method for constructing sports network organization system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115271294A (en) | 2022-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10021580B2 (en) | Mobile device validation | |
| CN109710236B (en) | Service development and implementation method, device, platform and medium based on shared service | |
| EP2510473B1 (en) | Unified user login for co-location facilities | |
| US20140250183A1 (en) | Home appliance information management apparatus, home appliance information sharing method, and home appliance information sharing system | |
| US20130103816A1 (en) | Multiplatform management system and method for mobile devices | |
| US8984191B2 (en) | Automated data center network patching system | |
| US20110093367A1 (en) | Method, apparatus, and computer product for centralized account provisioning | |
| CN109670612A (en) | Assets management method and device, storage medium, computer equipment | |
| CN113987541A (en) | Data access control method and device and electronic equipment | |
| US10929279B2 (en) | Systems and method for automated testing framework for service portal catalog | |
| CN114726632B (en) | Login method, login equipment and storage medium | |
| CN115271294B (en) | Standardized management system for enterprises | |
| CN105701605A (en) | Waveform list management module applied to integrated communication navigation identification system | |
| Mohamed et al. | SaaS dynamic evolution based on model-driven software product lines | |
| US8341530B1 (en) | Customer service center database management | |
| CN108536447B (en) | Operation and maintenance management method | |
| US20050108324A1 (en) | Serialized inventory control system and method | |
| CN102456023A (en) | Method and system for searching user information | |
| CN101729281B (en) | Method, equipment and system for developing and installing network management properties of businesses | |
| JP5064337B2 (en) | Software development management system | |
| CN114116679A (en) | Multi-database environment operation and maintenance method and system | |
| US20100064171A1 (en) | Tariff management deployment automation | |
| US20090037871A1 (en) | Community-centric management of composite applications | |
| US7231448B1 (en) | System and method for automated network element database population | |
| CN111831262A (en) | Mobile terminal portal construction method for government affair service platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |