Method and system for managing technical files related to iron and steel enterprises

By functional and maturity classification of technical documents of steel enterprises, the problem of inefficient production efficiency caused by improper document management is solved, and the efficient management of technical documents and shortening of production cycles is achieved.

CN120371786APending Publication Date: 2025-07-25SHOUGANG JINGTANG IRON & STEEL CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510330763.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-03-20
Publication Date
2025-07-25

AI Technical Summary

Technical Problem

Existing steel companies have duplicate content and unclear classification in technical document management, resulting in low production efficiency and extended production cycles.

Method used

Technical documents are classified step by step according to the usage objects and the usage period, including knowledge reserve files and job guidance files, and call the corresponding files to perform operations based on the target operation request, setting permissions and management processes to ensure the scientificity and confidentiality of the files.

Benefits of technology

It reduces the type and content duplication rate of technical documents, improves production efficiency, shortens production cycle, and improves management costs and user-side quality experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120371786A_ABST
    Figure CN120371786A_ABST
Patent Text Reader

Abstract

The invention discloses an iron and steel enterprise related technical file management method and system, and the method comprises the steps: carrying out the primary classification of technical files according to a use object, and obtaining a primary classification file; the use objects comprise technicians and operators; the primary classification file comprises a knowledge reserve type file and an operation guidance type file; the knowledge reserve file is used by the technician; the operation instruction file is used by the operator; carrying out secondary classification on the operation guidance file according to the service life to obtain a secondary classification file; wherein the secondary classification file comprises a short-term execution file and a long-term execution file; based on a target operation request, calling the knowledge reserve file and / or the secondary classification file to execute corresponding operation; wherein the target operation request comprises one or more of a retrieval request, a lookup request, a downloading request, a version comparison request, a secrecy request, an analysis request and a question and answer request.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the technical field of steel management, and particularly to a technical document management method and system related to steel enterprises. Background Art

[0002] Technical documents, as an important carrier for ensuring the product quality of steel enterprises, play a significant role. The rigor of the content, the scientific nature of management, the accuracy of distribution, the convenience of retrieval, and the confidentiality of technical documents directly affect the product quality.

[0003] With the continuous development of steel product varieties, the continuous segmentation of the customer market, and the increasing differentiation of customer demands, the differences in alloys, mold fluxes, process technologies, and inspection judgments of different products are gradually increasing, and the differences in automotive sheet products are more significant. Therefore, when producing an order, various types of technical documents will be derived, such as procedure documents (product process procedures, technical procedures, job procedures), operation guides (for key and difficult varieties), control plans (for automotive sheet products), quality plans (for non-automotive sheet products), technical notices, and so on.

[0004] However, in existing steel enterprises, the management of technical documents is insufficient. All the above-mentioned technical documents are distinguished by operators themselves. The technical documents that operators need to use include multiple types of technical documents such as technical procedures, job procedures, operation guides, control plans, and technical notices. The content of various technical documents is large but mostly repetitive. For example, the job procedure is usually forty or fifty pages, and the repetitive content between the operation guide for key and difficult varieties and the general job procedure is nearly 80%. As a result, when producing key and difficult varieties, it is impossible to identify the change points that are different from conventional varieties, which affects the operation efficiency of products and prolongs the production cycle of products. Summary of the Invention

[0005] In order to solve or partially solve the technical problems that the management of technical documents in existing steel enterprises is insufficient, which affects the operation efficiency of products and prolongs the production cycle of products, the present invention provides a technical document management method and system related to steel enterprises.

[0006] To solve the above technical problems, in the first aspect of the present invention, a technical document management method related to steel enterprises is disclosed. The method includes:

[0007] Classify technical documents once according to the users, and obtain the first-classified documents; among them, the technical documents include: product process specifications, technical specifications, job specifications, potential failure mode and effects analysis, control plans, technical standards, process change orders, technical notices, and trial production plans; the users include technicians and operators; the first-classified documents include: knowledge reserve documents and operation instruction documents; the knowledge reserve documents are used by the technicians and include: the product process specifications, the technical specifications, and the potential failure mode and effects analysis; the operation instruction documents are used by the operators and include: the job specifications, the control plans, the technical standards, the process change orders, the technical notices, and the trial production plans;

[0008] Classify the operation instruction documents a second time according to the usage period, and obtain the second-classified documents; among them, the second-classified documents include: short-term execution documents and long-term execution documents; the short-term execution documents include: the trial production plans, the process change orders, and the technical notices; the long-term execution documents include: the control plans, the technical standards, and the job specifications; among them, the execution priority of the short-term execution documents is higher than that of the long-term execution documents;

[0009] Based on the target operation request, call the knowledge reserve documents and / or the second-classified documents to perform corresponding operations; among them, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, and Q&A request.

[0010] Optionally, after classifying the technical documents once according to the users and obtaining the first-classified documents, the method further includes:

[0011] Classify the operation instruction documents into the second-classified documents according to generality; among them, the second-classified documents include: general documents and personalized documents; the general documents include: the job specifications and the technical standards; the personalized documents include: the control plans, the trial production plans, the process change orders, and the technical notices.

[0012] Optionally, after classifying the operation instruction documents a second time according to the usage period and obtaining the second-classified documents, the method further includes:

[0013] Real-time monitor whether any one of the control plans, the trial production plans, the process change orders, and the technical notices needs to be issued;

[0014] If necessary, determine the corresponding associated units, product categories, sales varieties, product specifications, quality end-users, sales end-users, end-uses, tapping marks, and steel grade codes, and send them to the production execution system so that the production execution system has the function of viewing the technical documents applicable to the current production materials with one key.

[0015] Optionally, after the operation instruction type files are secondarily classified according to the expiration date to obtain the secondarily classified files, the method further includes:

[0016] Monitor the execution deadline of the short-term execution files in real time;

[0017] If the execution deadline of the short-term execution files expires, solidify them to the long-term execution files according to the preset solidification logic; wherein, the preset solidification logic includes: solidifying the trial production plan to the control plan or the post regulations; solidifying the process change order to the control plan; solidifying the technical notice to the technical standard.

[0018] Optionally, after the operation instruction type files are secondarily classified according to the expiration date to obtain the secondarily classified files, the method further includes:

[0019] Obtain newly created technical documents;

[0020] Review the newly created technical documents, and after passing the review, stamp them with a controlled seal and send them out;

[0021] Regularly review the newly created technical documents; the review results include one of the following: revision, continued applicability, invalidation;

[0022] When the review result is invalidation, stamp the newly created technical documents with an invalidation seal.

[0023] Optionally, before the method calls the knowledge reserve type files and / or the secondarily classified files to perform corresponding operations based on the target operation request, the method further includes:

[0024] Set the viewing permissions for the knowledge reserve type files and / or the secondarily classified files;

[0025] The calling of the knowledge reserve type files and / or the secondarily classified files to perform corresponding operations based on the target operation request specifically includes:

[0026] Based on the viewing level corresponding to the access request and the viewing permissions for the knowledge reserve type files and / or the secondarily classified files, display the technical documents that meet the viewing level from the knowledge reserve type files and / or the secondarily classified files.

[0027] Optionally, setting the viewing permissions for the knowledge reserve files and / or the secondary classification files specifically includes:

[0028] Referring to the classification types, setting department-level viewing permissions and company-level viewing permissions for the knowledge reserve files and / or the secondary classification files; wherein, the department-level viewing permissions are open to department-level administrators, and the company-level viewing permissions are open to company-level administrators; and / or

[0029] Controlled by the permission setting request of the preparer, setting user-level viewing permissions for the knowledge reserve files and / or the secondary classification files; wherein, the user-level viewing permissions are open to the users designated by the preparer.

[0030] Optionally, based on the target operation request, invoking the knowledge reserve files and / or the secondary classification files to perform corresponding operations specifically includes:

[0031] If a viewing request or a download request for the technical document is detected, a watermark of the user information of the logged-in account is automatically generated on the browsing interface corresponding to the technical document or inside the downloaded file.

[0032] Optionally, if a viewing request or a download request for the technical document is detected, the method further includes:

[0033] If the source of the viewing request or the download request is a mobile terminal, perform one or more of the following operations: prohibit viewing, prohibit downloading, prohibit screenshotting.

[0034] In a second aspect of the present invention, a technical document management system related to an iron and steel enterprise is disclosed. The system includes:

[0035] A first classification module for performing a first classification of technical documents according to the users of use to obtain first classification documents; wherein, the technical documents include: product process specifications, technical specifications, post specifications, potential failure mode and effects analysis, control plans, technical standards, process change orders, technical notices, trial production plans; the users of use include technical personnel and operators; the first classification documents include: knowledge reserve files and operation guide files; the knowledge reserve files are used by the technical personnel and include: the product process specifications, the technical specifications, the potential failure mode and effects analysis; the operation guide files are used by the operators and include: the post specifications, the control plans, the technical standards, the process change orders, the technical notices, the trial production plans;

[0036] The second classification module is used to classify the job instruction files according to the expiration date to obtain the second-classified files. Among them, the second-classified files include: short-term execution files and long-term execution files. The short-term execution files include: trial production plan, process change order, technical notice. The long-term execution files include: control plan, technical standard, post regulation. Among them, the execution priority of the short-term execution files is higher than that of the long-term execution files.

[0037] The execution module is used to call the knowledge reserve files and / or the second-classified files to perform corresponding operations based on the target operation request. Among them, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, Q&A request.

[0038] Through one or more technical solutions of the present invention, the present invention has the following beneficial effects or advantages:

[0039] The technical solution of the present invention re-determines technical documents, including: product process regulations, technical regulations, post regulations, control plans, technical standards, process change orders, technical notices, trial production plans. Classify technical documents step by step according to the usage object and expiration date. On this basis, call the knowledge reserve files and / or the second-classified files to perform corresponding operations based on the target operation request. By redefining and classifying technical documents, the present invention can reduce the number of file types, and the content of various technical documents has no repetition. For example, the job instruction book is cancelled, and the post regulation is only restricted to be used as a job file for standardizing the post operation process to avoid the repetition of the content between the job instruction book and the post regulation, reduce the content repetition rate, improve the operation efficiency of the product, shorten the production cycle and management cost of the product, and improve the quality experience of the user side.

[0040] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable, the following specifically illustrates the specific embodiments of the present invention. Description of the Drawings

[0041] By reading the detailed description of the preferred embodiments below, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of showing the preferred embodiments and are not considered to be a limitation of the present invention. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0042] Figure 1 Shows a flowchart of a technical document management method related to an iron and steel enterprise according to an embodiment of the present invention;

[0043] Figure 2 A schematic diagram showing a technical file architecture according to an embodiment of the present invention;

[0044] Figure 3 A logical schematic diagram showing the solidification of a short-term execution file into a long-term execution file according to an embodiment of the present invention is shown;

[0045] Figure 4 A schematic diagram of a technical document management system related to a steel enterprise according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0046] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0047] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0048] First, as Figure 1 As shown, the method for managing technical documents related to a steel enterprise provided by an embodiment of the present invention comprises at least the following steps:

[0049] S101, classifying the technical documents according to the use objects to obtain a classified document.

[0050] In the prior art, the production of an order will generate various technical documents, such as procedural documents (product process regulations, technical regulations, job regulations), operating instructions (difficult and key varieties), control plans (automotive sheet products), quality plans (non-automotive sheet products), technical notifications, etc. Most of the contents of these classified documents are repeated. For example, the repetition rate of job regulations and operating instructions is more than 80%, which is not suitable for use by operators. For another example, various types of temporary documents are issued in the form of technical notifications, including production organization requirements for new products, process changes for mass-produced products, temporary inspection requirements, material standards, process parameter changes in control plans, etc., which are all issued to operators in the form of technical notifications. The differences between different versions of technical documents cannot be displayed, which is inconvenient for compilers, reviewers, and executors to understand the changes. The classification of technical documents in the prior art is relatively messy, which easily causes confusion in the implementation of process standards.

[0051] Therefore, in order to avoid problems such as content duplication of technical documents and unclear classification of various types of technical documents leading to production defects in products, in this embodiment, the types of technical documents are classified according to functions, and one function corresponds to one type of technical document. For example, the quality plan is cancelled, and the control plan is uniformly used for all products; the operation instruction is cancelled, and according to the job classification, the job regulations are uniformly used; the technical document used in the new product development stage is called the trial production plan, which is only used for short-term implementation and transferred to the job regulations after being solidified. In the trial production plan, in view of the characteristics of steel products, in addition to marking the process technical requirements of the new product, special requirements such as production preparation, roll preparation requirements, roll period, and materials are also marked to supplement the content outside the control plan, so as to assist the control plan to cover management requirements. For product process changes after mass production, a process change order is used to show the comparison of content before and after the change and the reason for the change, so that the key process change points can be concisely and directly passed to the operators, reducing the search time and search errors. For requirements such as new material inspection standards, production organization of key and difficult products in mass production, temporary tests, temporary judgment standards, and temporary inspections, a technical notice is used to reduce the phenomenon of flying technical notices everywhere and facilitate on-site use by operators.

[0052] On this basis, the technical documents determined in this embodiment mainly include the following categories: product process regulations, technical regulations, job regulations, FMEA (Failure Mode and Effects Analysis), control plan, technical standards, process change orders, technical notices, and trial production plans.

[0053] Product process regulations: It is a technical document that stipulates the characteristic parameters and quality benchmarks of product production processes in combination with factors such as meeting product order requirements, ensuring product physical quality, production efficiency, economic benefits, environmental protection, energy conservation and consumption reduction, production safety, process rationality, and continuous improvement. The product process regulations are divided into a manufacturing management section and a quality design section.

[0054] Job regulations: It is an operation document formulated to standardize the job operation process and implement professional requirements such as safety, production, equipment, technology, and environmental protection. The job regulations include operating procedures, equipment regulations, safety regulations, and handover systems.

[0055] Technical regulations: It is a technical management document compiled to implement product process regulations and related technical requirements. The technical regulations are compiled according to production processes and are guiding documents for formulating job regulations.

[0056] FMEA: It is the core of the entire R & D process and a preventive quality control tool based on risk thinking. It includes DFMEA (Design Failure Mode and Effects Analysis) and PFMEA (Process Failure Mode and Effects Analysis).

[0057] Control Plan: The control plan is a dynamic document formed during the product quality planning process, which is used to describe the control measures required at each stage of the process and provides process monitoring and control methods for controlling characteristics. A single control plan can apply to a group or family of products produced from the same process and the same raw materials.

[0058] Technical Standard: It refers to the standards formulated by the company internally for matters that need to be coordinated and unified in the production and manufacturing fields. It includes: production scheduling standards, quality judgment standards, procurement acceptance standards, packaging inspection standards, raw material and fuel technical standards, process auxiliary material technical standards, sampling and sending standards, etc. Among them, the technical standard carries a source number. For example, it extends its source in the way of document number + Z + sequential number, but it does not form a limitation. For example, a total of 14 technical standards related to sampling and product surface judgment are brought out after the "Steel Product Inspection Control Procedure", which are SJTJSM013Z001, SJTJSM013Z002, etc. The "Production Operation Arrangement and Production Organization Control Procedure" brings out 4 technical standards related to production scheduling, and the technical standard numbers are SJTSCM004Z001, SJTSCM004Z002, etc. According to the above method, the source of the technical standard can be traced, the hierarchical management of technical documents can be realized, and the implementation scope is clearer.

[0059] Process Change Order: It is applicable to changes such as chemical composition, performance, process parameters, process route, raw and auxiliary materials, and process control after mass production. It includes changes in system parameters and control plans.

[0060] Technical Notice: It is a temporary and short-term operation document. The manufacturing department is only limited to the use of iron front ratio notice, new material inspection standards, production organization of key and difficult products, temporary tests, temporary judgment standards, and temporary inspection requirements. The operation department is only limited to the use of material concession acceptance, temporary measures for production equipment failures, temporary tests, and temporary inspection requirements.

[0061] Pilot Production Plan: During the new product development process, content supplemented as needed outside the control plan (a one-time planning for production preparation of man, machine, material, and environment) adopts the pilot production plan.

[0062] The types of technical documents classified in this embodiment are relatively few, and the content is basically non-repetitive, which can reduce the problem of non-conformity between the document content and types.

[0063] Furthermore, the above technical documents are divided according to one or more principles of whether the function is general, time period, user object, and separation of management and technology. Each type of technical document does not cross or repeat in terms of content and time limit.

[0064] Specifically, the above technical documents are classified according to the users to obtain the first-level classification documents. Among them, the users include technicians and operators. Among them, the first-level classification documents include: knowledge reserve documents and operation guide documents. The technical documents used by technicians are called knowledge reserve documents, including: product process specifications, technical specifications, and FMEA. The technical documents used by operators are called operation guide documents, including: post specifications, control plans, technical standards, process change orders, technical notices, and trial production plans.

[0065] In this embodiment, the technical documents are classified into knowledge reserve documents and operation guide documents with reference to the users, making the audience scope of the technical documents clearer and facilitating on-site operators to consult.

[0066] S102, the operation guide documents are classified secondarily according to the service life to obtain the second-level classification documents.

[0067] Among them, the second-level classification documents include: short-term execution documents and long-term execution documents; the short-term execution documents include: trial production plans related to new products, process change orders related to mass production, and technical notices related to temporary operations; the long-term execution documents include: control plans related to products, technical standards related to technologies, and post specifications related to operations; among them, short-term execution is applicable to various temporary changes and tests, and the validity period does not exceed 1 year. The execution priority of the short-term execution documents is higher than that of the long-term execution documents. When there is a conflict between the two, the former is executed.

[0068] After classification according to the above principles, the classification framework of the technical documents in this embodiment can be obtained. See Figure 2 , which is a schematic diagram of the technical document framework.

[0069] In an alternative embodiment, since the prior art does not form a closed-loop management for technical documents, technical knowledge is not accumulated and continued, and cannot provide reference for the subsequent compilation of technical documents, resulting in the need to start from scratch when compiling new technical documents in the later stage, with low development efficiency and repeated quality problems. Therefore, in this embodiment, after the operation guide documents are classified secondarily according to the service life to obtain the second-level classification documents, the execution period of the short-term execution documents is monitored in real time; if the execution period of the short-term execution documents expires, they are solidified into long-term execution documents according to the preset solidification logic.

[0070] See Figure 3 , which is a schematic diagram of the logic for solidifying short-term execution documents into long-term execution documents. Among them, the preset solidification logic includes: solidifying the trial production plan into the control plan or post specification; solidifying the process change order into the control plan; solidifying the technical notice into the technical standard.

[0071] In this embodiment, a closed-loop management is implemented for short-term execution documents. The execution period of the short-term execution documents is 1 year. After expiration or the set expiration time (such as being abolished 1 month later), they automatically enter the solidification process. According to the preset solidification logic, the short-term execution documents are automatically solidified into the corresponding long-term execution documents, so that knowledge and experience can be accumulated and inherited, thereby shortening the product and process development cycle and improving the stability and consistency of product quality.

[0072] In an alternative embodiment, the operation instruction documents are divided into secondary classification documents according to generality; among them, the secondary classification documents include: general documents and personalized documents; the general documents include: post regulations, technical standards; the personalized documents include: control plans, trial production plans, process change orders, technical notice needles. Further, in accordance with the concept of consistency in product personalization, the personalized documents related to the product can be integrated into the control plan, so that one control document covers all the technical requirements of the product, which is convenient for the operators to consult during on-site production, reduces the search time and search errors, and improves product quality. In this embodiment, through classification design based on functional generality and the users, it is convenient for technicians and operators to edit, retrieve, read and other management and use.

[0073] In an alternative embodiment, considering that the regular review of technical documents is not timely, some technical documents are not revised for a long time, the requirements of regular review and revision stipulated in management are not implemented in place, new changes are not identified, resulting in the requirements of technical documents not meeting the actual needs, and there is no unified management of the controlled seal and invalid seal of technical documents, and each department engraves them by itself, resulting in management chaos.

[0074] In an alternative embodiment, the management process of newly created technical documents is also optimized. Specifically, after the operation instruction documents are classified into secondary classification documents according to the service life and the secondary classification documents are obtained, the newly created technical documents are acquired; the newly created technical documents are reviewed, and after the review is passed, the controlled seal is stamped and distributed; the newly created technical documents are regularly reviewed to ensure the applicability of the technical documents; the review results include one of the following: revision, continue to be applicable, invalidation. For example, one year after the release date of the technical document, the technical document is automatically pushed to the compiler for the annual review task, and review results such as revision, continue to be applicable, invalidation, etc. are selected for the technical document. The technical document performs corresponding operations according to the review results. When the review result is invalidation, the invalidation seal is stamped on the newly created technical document. Further, for the annual regular review of all technical documents, the to-be-reviewed tasks are automatically generated according to the set advance period (such as 30 days) and the compiler is reminded.

[0075] Optionally, if the newly created technical document belongs to the short-term execution document, it is solidified into the long-term execution document according to the preset solidification logic after expiration.

[0076] Optionally, perform version difference comparison on the newly created technical documents after review to determine the difference information of each version. For example, after the review of technical documents, compare different functional attributes, such as the modified content of different versions, to facilitate personnel in various links such as document compilation, review, learning, and dissemination to understand the change points. Of course, it is also possible to compare the modified content at various stages before, during, and after the release of technical documents to obtain difference information.

[0077] Through the above solution, it is possible to achieve the full life cycle management of the creation / revision, review, countersignature, approval, stamping with a controlled seal, distribution, dissemination, regular review, short-term document solidification, and invalidation of technical documents.

[0078] In an optional implementation manner, since the permissions of different types of technical documents in the prior art cannot be vertically subdivided level by level, in order to prevent the situation of incomplete distribution, it can only be distributed to all departments, resulting in operators being able to see many documents not executed by their own positions, which is likely to cause the risk of leakage.

[0079] Based on this, in this embodiment, before calling the knowledge reserve type files and / or secondary classification files to perform corresponding operations based on the target operation request, set the viewing permissions of the knowledge reserve type files and / or secondary classification files.

[0080] In the specific operation process of setting the viewing permissions, refer to the classification type, and set department-level viewing permissions and company-level viewing permissions for the knowledge reserve type files and / or secondary classification files; among them, the department-level viewing permissions are open to department-level administrators, and the company-level viewing permissions are open to company-level administrators. For example, company-level administrators can view all technical documents, and department-level administrators can only view all technical documents of their own departments. And / or, controlled by the permission setting request of the preparer, set user-level viewing permissions for the knowledge reserve type files and / or secondary classification files; among them, the user-level viewing permissions are open to the users designated by the preparer. When setting the viewing permissions, determine the viewers and downloaders of the knowledge reserve type files and / or secondary classification files, and only the selected people can view or download, so as to determine the distribution scope of various technical documents. Further, refine the permissions to departments, work areas, and positions level by level according to the permission requirements to obtain the gradually subdivided viewing permissions, and personnel outside the permissions have no right to view and download this technical document.

[0081] After setting the viewing permissions, in an optional implementation manner, distribute the knowledge reserve type files and / or secondary classification files without distinction, and display the corresponding technical documents according to the viewing permissions during subsequent viewing; or directly distribute them to departments, or work areas, or positions according to the viewing permissions of the knowledge reserve type files and / or secondary classification files, and view the technical documents according to the viewing permissions.

[0082] If there is a request to access knowledge reserve files and / or secondary classification files, technical files that meet the viewing level shall be displayed from the knowledge reserve files and / or secondary classification files based on the viewing level corresponding to the access request and the viewing permissions of the knowledge reserve files and / or secondary classification files. For example, compare the viewing permissions of the knowledge reserve files and / or secondary classification files with the viewing level corresponding to the requester of the access request. If the permission comparison is consistent, display it to the requester of the access request. If not, prohibit the display.

[0083] The above operations can enhance the confidentiality of technical files and prevent the risk of leakage.

[0084] It should be noted that the confidentiality of knowledge reserve files is lower than that of secondary classification files, so the confidentiality levels of the two can be set differently. For example, set the viewing permission of knowledge reserve files to the company level and the confidentiality of secondary classification files to the user level.

[0085] In an optional implementation manner, unify the system login address to the collaborative office system - file management system. When distributing technical files, distribute them to the file management system corresponding to each account according to the viewing permissions of the technical files. The files that the operator sees are the files that need to be executed by the position, which is beneficial for the operator to execute without the need to switch systems again.

[0086] In an optional implementation manner, technical files are generally distributed to relevant positions through the file management system. The operator needs to log in to the file management system in the office computer and search for them. The operator mainly uses the production execution system during daily production. The production execution system and the file management system are two independent systems. Therefore, the operator needs to frequently switch computers when producing different varieties, which is inconvenient to operate. For this reason, in this embodiment, the file management system and the production execution system have a data transmission interface. In the file management system, it is monitored in real time whether any one of the control plan, trial production plan, process change order, and technical notice needs to be issued; if so, determine the corresponding associated unit, product category, sales variety, product specification, quality end user, sales end user, end use, tapping mark, and steel grade code, and issue them to the production execution system through the data transmission interface, so that the production execution system has the function of viewing at one key the technical files applicable to the current production materials, facilitating the operator to view at one key all the technical files applicable to the current production variety, thus ensuring the smooth progress of production.

[0087] S103, based on the target operation request, call the knowledge reserve files and / or secondary classification files to perform corresponding operations.

[0088] Among them, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, and Q&A request.

[0089] After the expiration of the set period (such as one year) for the release of technical documents, the review operation for knowledge reserve documents and / or secondary classification documents is automatically triggered. Specifically, the technical documents are automatically pushed to the preparers for the annual review task, and review results such as revision, continued application, and invalidation are selected for the technical documents. The technical documents perform corresponding operations according to the review results. When the review result is invalidation, an invalidation stamp is affixed to the newly created technical document. Further, for the annual regular review of all technical documents, a to-be-reviewed task is automatically generated according to the set advance period (such as 30 days) and the preparers are reminded.

[0090] In an optional implementation manner, considering that the technical document is a confidential document, there are no encryption measures for online viewing and downloading of the technical document, there is a risk of confidentiality leakage through taking pictures or downloading, and the operators do not have private accounts, and there is only one public account for each operation console, and it is impossible to trace when a technician leaks the secret. In this embodiment, each operator is configured with its own login account, and the password is set by the operator himself. If a viewing request or download request for the technical document is detected, a watermark of the user information belonging to the login account is automatically generated inside the viewing interface corresponding to the technical document or the downloaded file. The watermark is used as an integrity verification to strengthen the ownership protection and facilitate the identification of authenticity and traceability.

[0091] Further, in order to prevent leakage of secrets, after detecting a viewing request or download request for the technical document, if the source of the viewing request or download request is a mobile terminal, one or more of the following operations are performed: prohibit viewing, prohibit downloading, and prohibit screenshotting. By setting the viewing, downloading, and screenshotting permissions according to the type of the operation terminal, the leakage of technical documents is prevented, and the confidentiality of technical documents is improved.

[0092] In an optional implementation manner, question information is received; among them, the question information carries the account, user information, etc.; the question information is fed back to the working interface of the main responsible department. The Q&A information of the main responsible department is fed back to the interface corresponding to the account according to the account information. Through the above solution, it supports employees to ask questions at any time, and the main responsible department answers and interprets them. By absorbing the opinions and suggestions from bottom to top of employees, the continuous improvement of the rigor of technical documents is promoted.

[0093] In an optional implementation manner, a search request is received, and a fuzzy search is performed across the whole station and the search results are displayed to achieve multi-condition fuzzy search.

[0094] In an alternative embodiment, attribute data of technical documents is collected in real time for big data analysis. The attribute data includes: the number of unread people, reading time, search frequency, click volume, etc., so as to facilitate the statistics of the reception and absorption of technical documents.

[0095] In an alternative embodiment, a process modification request is received, and the management process of technical documents is modified according to the process modification request; wherein, a separate management process can be set for each type of technical document, including formulation / revision, approval, release, viewing, downloading, invalidation, etc.

[0096] Through the above operations, the full life cycle management of the creation / revision, review, countersignature, approval, stamping with a controlled seal, distribution, publicity, regular review, short-term document solidification, and invalidation of technical documents can be realized. At the same time, the usage functions such as retrieval, viewing, downloading, version comparison, confidentiality, analysis, Q&A, mobile APP approval and access of technical documents can be realized.

[0097] In a second aspect, based on the same inventive concept as the technical document management method related to steel enterprises provided in the foregoing first aspect embodiments, the embodiments of the present invention further provide a technical document management system related to steel enterprises. Refer to Figure 4 , the system includes:

[0098] A first classification module 401, configured to classify technical documents once according to the usage object to obtain first-classified documents; wherein, the technical documents include: product process specifications, technical specifications, post specifications, potential failure mode and effects analysis, control plans, technical standards, process change orders, technical notices, trial production plans; the usage objects include technical personnel and operators; the first-classified documents include: knowledge reserve documents and operation guidance documents; the knowledge reserve documents are used by the technical personnel and include: the product process specifications, the technical specifications, the potential failure mode and effects analysis; the operation guidance documents are used by the operators and include: the post specifications, the control plans, the technical standards, the process change orders, the technical notices, the trial production plans;

[0099] A second classification module 402, configured to classify the operation guidance documents a second time according to the usage period to obtain second-classified documents; wherein, the second-classified documents include: short-term execution documents and long-term execution documents; the short-term execution documents include: trial production plans, process change orders, technical notices; the long-term execution documents include: control plans, technical standards, post specifications; wherein, the execution priority of the short-term execution documents is higher than that of the long-term execution documents;

[0100] The execution module 403 is configured to call the knowledge reserve file and / or the secondary classification file to perform corresponding operations based on the target operation request; wherein, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, and question-and-answer request.

[0101] It should be noted that for the technical document management system related to iron and steel enterprises provided in the embodiments of the present invention, the specific manners in which each module performs operations have been described in detail in the method embodiments provided in the above first aspect. The specific implementation process can refer to the method embodiments provided in the above first aspect, and will not be elaborated here in detail.

[0102] Through one or more embodiments of the present invention, the present invention has the following beneficial effects or advantages:

[0103] The technical solution of the present invention re-determines technical documents, including: product process specifications, technical specifications, job specifications, control plans, technical standards, process change orders, technical notices, and trial production plans. The technical documents are classified step by step according to the usage objects and usage periods. On this basis, the knowledge reserve file and / or the secondary classification file are called to perform corresponding operations based on the target operation request. By redefining and classifying technical documents, the present invention can reduce the number of file types, and there is no duplication in the content of various technical documents. For example, operation manuals are cancelled, and job specifications are restricted to be only operation documents for standardizing the job operation process to avoid content duplication between operation manuals and job specifications, reducing the content duplication rate, ensuring the production cycle of products, reducing management costs, and enhancing the quality experience of the user side.

[0104] Although the preferred embodiments of the present application have been described, those of ordinary skill in the art can make additional changes and modifications once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0105] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. A technical document management method related to iron and steel enterprises, characterized in that, The method includes: Classifying technical documents once according to the users, to obtain the first-classified documents; wherein, the technical documents include: product process specifications, technical specifications, job specifications, potential failure mode and effects analysis, control plans, technical standards, process change orders, technical notices, trial production plans; the users include technical personnel and operators; the first-classified documents include: knowledge reserve documents and operation instruction documents; the knowledge reserve documents are used by the technical personnel and include: the product process specifications, the technical specifications, the potential failure mode and effects analysis; the operation instruction documents are used by the operators and include: the job specifications, the control plans, the technical standards, the process change orders, the technical notices, the trial production plans; Classifying the operation instruction documents a second time according to the usage period, to obtain the second-classified documents; wherein, the second-classified documents include: short-term execution documents and long-term execution documents; the short-term execution documents include: the trial production plans, the process change orders, the technical notices; the long-term execution documents include: the control plans, the technical standards, the job specifications; wherein, the execution priority of the short-term execution documents is higher than that of the long-term execution documents; Based on a target operation request, calling the knowledge reserve documents and / or the second-classified documents to perform corresponding operations; wherein, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, Q&A request.

2. The method according to claim 1, wherein After classifying the technical documents once according to the users to obtain the first-classified documents, the method further includes: Dividing the operation instruction documents into the second-classified documents according to generality; wherein, the second-classified documents include: general documents and personalized documents; the general documents include: the job specifications, the technical standards; the personalized documents include: the control plans, the trial production plans, the process change orders, the technical notices.

3. The method according to claim 1 or 2, characterized in that, After classifying the operation instruction documents a second time according to the usage period to obtain the second-classified documents, the method further includes: Real-time monitoring whether any one of the control plans, the trial production plans, the process change orders, the technical notices needs to be issued; If so, determining the corresponding associated units, product categories, sales varieties, product specifications, quality end-users, sales end-users, end-uses, tapping marks, steel grade codes, and issuing them to the production execution system, so that the production execution system has the function of viewing at one key the technical documents applicable to the current production materials.

4. The method according to claim 1, wherein After classifying the operation instruction documents a second time according to the usage period to obtain the second-classified documents, the method further includes: Real-time monitoring the execution period of the short-term execution documents; If the execution period of the short-term execution file expires, it is solidified to the long-term execution file according to the preset solidification logic; wherein, the preset solidification logic includes: solidifying the trial production plan to the control plan or the post regulations; solidifying the process change order to the control plan; solidifying the technical notice to the technical standard.

5. The method according to claim 1, characterized in that, After the operation instruction type files are secondarily classified according to the usage period to obtain the secondarily classified files, the method further includes: Obtaining a newly created technical file. Reviewing the newly created technical file, and affixing a controlled seal and distributing it after the review is passed. Regularly reviewing the newly created technical file; the review result includes one of the following: revision, continued applicability, invalidation. When the review result is invalidation, affix an invalidation seal to the newly created technical file.

6. The method according to claim 1, characterized in that Before the method based on the target operation request calls the knowledge reserve type files and / or the secondarily classified files to perform corresponding operations, the method further includes: Setting the viewing permissions for the knowledge reserve type files and / or the secondarily classified files. The method based on the target operation request calls the knowledge reserve type files and / or the secondarily classified files to perform corresponding operations, specifically including: Based on the viewing level corresponding to the access request and the viewing permissions for the knowledge reserve type files and / or the secondarily classified files, display the technical files that meet the viewing level from the knowledge reserve type files and / or the secondarily classified files.

7. The method according to claim 6, wherein The setting of the viewing permissions for the knowledge reserve type files and / or the secondarily classified files specifically includes: Referring to the classification type, setting department-level viewing permissions and company-level viewing permissions for the knowledge reserve type files and / or the secondarily classified files; wherein, the department-level viewing permissions are open to department-level administrators, and the company-level viewing permissions are open to company-level administrators; and / or Controlled by the permission setting request of the compiling personnel, setting user-level viewing permissions for the knowledge reserve type files and / or the secondarily classified files; wherein, the user-level viewing permissions are open to the users designated by the compiling personnel.

8. The method according to claim 1, characterized in that The method based on the target operation request calls the knowledge reserve type files and / or the secondarily classified files to perform corresponding operations, specifically including: If a viewing request or a download request for the technical file is detected, automatically generate a watermark of the user information of the logged-in account on the browsing interface corresponding to the technical file or inside the downloaded file.

9. The method according to claim 8, wherein If a viewing request or a download request for the technical file is detected, the method further includes: If the source of the viewing request or the download request is a mobile terminal, perform one or more of the following operations: prohibit viewing, prohibit downloading, prohibit screenshotting.

10. A technical document management system related to iron and steel enterprises, characterized in that, The system includes: The first classification module is used to classify technical documents once according to the users, and obtain the once-classified documents; wherein, the technical documents include: product process specifications, technical specifications, job specifications, potential failure mode and effects analysis, control plans, technical standards, process change orders, technical notices, trial production plans; the users include technical personnel and operators; the once-classified documents include: knowledge reserve documents and operation instruction documents; the knowledge reserve documents are used by the technical personnel and include: the product process specifications, the technical specifications, the potential failure mode and effects analysis; the operation instruction documents are used by the operators and include: the job specifications, the control plans, the technical standards, the process change orders, the technical notices, the trial production plans; The second classification module is used to classify the operation instruction documents twice according to the service life, and obtain the twice-classified documents; wherein, the twice-classified documents include: short-term execution documents and long-term execution documents; the short-term execution documents include: trial production plans, process change orders, technical notices; the long-term execution documents include: control plans, technical standards, job specifications; wherein, the execution priority of the short-term execution documents is higher than that of the long-term execution documents; The execution module is used to call the knowledge reserve documents and / or the twice-classified documents to perform corresponding operations based on the target operation request; wherein, the target operation request includes one or more of the following: retrieval request, access request, download request, version comparison request, confidentiality request, analysis request, Q&A request.