Detailed Description
The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.
The present application will be described in further detail below with reference to the accompanying drawings, in order to make the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, but all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.
In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict, the term "first\second" being referred to merely as distinguishing between similar objects and not representing a particular ordering for the objects. The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements that are expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or modules that may not be expressly listed or inherent to such process, method, article, or apparatus, and unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for the purpose of describing embodiments of the application only.
The embodiment of the application provides a management method for externally cooperated purchasing parts, as shown in fig. 1, the method comprises the following steps:
step S100, connecting an ERP system of an enterprise, synchronously screening BOM information and supplier information of purchased parts in real time, and inputting repair data, receiving data and returning data, wherein the input mode comprises code scanning input and pc popup window selection input.
Preferably, the ERP system (enterprise resource planning system) is a central center of enterprise management core data, stores key information such as purchasing plans, production bill of materials (BOM), supplier files, inventory data and the like, is connected with the enterprise ERP system, can enable an outsourcing purchasing management module to be communicated with data of links such as enterprise internal production, inventory, finance and the like in real time, avoids manual repeated input or data splitting, extracts source data related to outsourcing purchasing from the enterprise ERP system, namely, synchronously screens BOM information and supplier information of purchasing parts in real time, and ensures accuracy and timeliness of a management flow. The BOM information is used for recording all parts, raw materials and quantity ratios of the parts and raw materials required by producing a certain product in detail, and determining which parts are required to be purchased by enterprises to an export-cooperative provider, wherein the provider information comprises the basic information, the production capacity, the supply history, the quality rating and the like of the provider. The real-time synchronous screening shows that whether BOM information in the enterprise ERP system is updated due to product design change or supplier information is modified due to cooperation condition change, the management system can immediately acquire the latest data, so that the information according to the enterprise in the purchasing management process is always accurate and timely, and purchasing errors or decision errors caused by information lag are avoided.
Preferably, in the part outsourcing purchasing process, the repair data, the receiving data and the returning data are key information reflecting the actual use condition and the quality condition of the parts, specifically, in the part receiving, repairing or returning link, the unique identification (such as a two-dimensional code and a bar code) on the part is scanned by using a code scanning device (such as a code scanning gun), the basic information (such as a model number and a batch number) of the part is identified and is related to a corresponding purchasing order, and a worker can quickly complete data input by only supplementing a small amount of other information (such as the quantity of received goods, the reason of repairing, the quantity of returned goods and the like). When the staff operates at the computer end, the system pops up corresponding windows according to different data input scenes (such as receiving, repairing and returning), preset options and input boxes related to the current operation are listed in the windows, for example, when receiving and recording, the windows can display synchronous purchase order information, the staff only needs to select the actual receiving quantity, receiving states (such as passing and failing) and the like in a pull-down menu, and the input boxes can be supplemented with instructions for special cases. Through combining the code scanning input mode and the PC popup window selection input mode, enterprises can comprehensively, efficiently and accurately collect various data of parts in the purchasing whole process.
Step S200, performing a full-process tracking analysis according to the BOM information, the supplier information, the repair data, the receiving data and the returning data, and determining an order state of the purchased part.
Preferably, transparent tracking of the whole purchasing process is achieved through integrated analysis of BOM information, supplier information, repair data, receiving data and returning data, specifically, from the generation stage of purchasing orders, the BOM information clearly confirms the specific specification, quantity and other requirements of purchasing parts required by enterprises, the enterprises place purchasing orders to suppliers based on the BOM information, the supplier information can help the enterprises to know the production scheduling capacity, historical supply period and the like of the suppliers, and the enterprises can preliminarily estimate order delivery time and judge whether the suppliers have the capacity of completing orders on time by combining the part demand time in the BOM information. In the production and transportation stages of the parts, the production progress can be indirectly estimated through the production capacity evaluation and the historical delivery record of the suppliers in the supplier information, for example, if the historical delivery time rate of a certain supplier is high and the production capacity is strong, the average time length of the production period of the order can be used for judging which stage of the order is in production in a period of time after the order is placed, and meanwhile, if the conditions of logistics delay and the like occur, the expected arrival time and the actual non-arrival condition in the receiving data are combined, and the abnormality of the transportation link can be timely found.
Preferably, when the parts reach the enterprise and enter the receiving link, the receiving data becomes a core focus point, the information such as the actual receiving quantity, the quality inspection result (qualified or unqualified) and the like is recorded by a code scanning input or PC popup window selection input mode, the system compares the data with the purchasing quantity requirement in BOM information and the quality standard agreed in supplier information, if the actual receiving quantity is not in accordance with the BOM required quantity or the quality inspection fails, the abnormal condition of the order state is immediately judged, such as partial delivery, delivery failure and the like, and corresponding processing flows such as communication with suppliers for replenishment or return are triggered.
Preferably, after the parts are put into use, the repair data and the return data reflect the subsequent quality condition of the products, when the parts are in fault and need to be repaired, the scan code is used for inputting the repair data, the purchase order and the supplier to which the parts belong are tracked, whether the repair reasons are related to factors such as the production process of the supplier, the quality of raw materials and the like is analyzed, if the repair rate is higher, the system quality problem exists in the parts delivered by the order, the order state is adjusted to be in need of negotiating a solution with the supplier, the return data directly reflect the final processing result of the enterprises on the quality or the delivery condition of the parts, and the return reasons (such as the quality is not up to standard, the delivery delay leads to production schedule change and the like) are combined with other data, so that the enterprises can be helped to comprehensively evaluate the purchase order execution condition, and the final order state such as the order completion but the quality problem, the order termination and the like are determined.
Preferably, through carrying out association analysis on BOM information, supplier information, repair data, receiving data and returning data in each link of purchasing, enterprises can accurately grasp the whole flow state of purchasing part orders from delivery, production, transportation and receiving to after-sale in real time, discover problems in time and take targeted measures, so that the smooth progress of purchasing flows and the stability of supply chains are ensured.
Further, step S200 further includes that the order status includes at least BOM basic information, supplier processing information, working section completion status, receiving status, returning status and component repair status of the purchased component.
Preferably, the BOM basic information comprises part identifiers such as model numbers, specifications, drawing numbers, technical parameters (such as size, material and performance indexes), required quantity, purchasing quantity required by a production plan, associated products, parts used for producing which final product, and change records, and if the BOM is changed due to design adjustment (such as part upgrading or replacement), the BOM is synchronously updated to an order state, so that purchasing errors are avoided. The supplier processing information reflects the execution capacity and progress of the suppliers to the purchase orders and comprises basic information of the suppliers, such as names, numbers, capacity levels (such as A/B/C grade suppliers), historical cooperation evaluation (delivery timing rate and quality qualification rate), processing plans, part production scheduling (such as start-up date and expected finishing date), production line distribution, key process nodes (such as time nodes for casting, machining and surface treatment), raw material sources, if key raw materials (such as special steels and electronic chips) are involved, the purchase channel and inventory condition of the suppliers need to be recorded, supply chain risks (such as delay of the exchange period caused by raw material shortage) are prejudged, abnormal early warning is performed, if the suppliers possibly delay production due to equipment failure, manpower shortage and the like, and the system automatically marks the order state as 'processing abnormal' and pushes reminding.
Preferably, the working section completion state refers to a specific link of the production and processing of parts and components and comprises a sectioning node, a state identifier, a quality record and a working section inspection result (such as whether a first part is inspected to be qualified or not and the process sampling inspection defective rate) and an order state is marked as a quality risk and a correction flow is triggered if the defective rate of a certain working section exceeds the standard, wherein each working section is marked with "not started", "in progress", "completed", "reworked" and the deviation between the actual completion time and the planned time is recorded. The receipt status is a "check result record" after the component arrives at the enterprise, and includes the arrival information, the actual arrival time, the transportation mode (such as the logistics carrier, the transportation time), the package integrity (broken/intact), the check result such as the quantity check, the quality check and the reject cause, and the status classification such as the normal receipt, the partial receipt and the reject. The return status refers to a status record of the return process of the received parts due to quality problems, delivery delays, demand changes, etc., and includes return reasons such as quality disqualification (highest duty), specification disqualification, delivery timeout, overstock (excessive purchasing caused by demand changes), return flow and processing results (such as refund/receipt, dispute status). The repair state of the part refers to a state record of the part which is put into use and needs to be returned to a factory for maintenance or replacement due to quality problems, and comprises repair triggering, information tracking and state updating (such as repair, repair completion and repair failure).
Further, step S200 further includes monitoring the status of the order by using a workflow, and if the order of the purchased component has a delivery deadline/overdue, automatically triggering an early warning mechanism to perform early warning.
Preferably, the workflow is an automatic process management tool with preset rules, and can automatically drive the process to flow according to preset conditions (such as time nodes and data changes) and trigger corresponding operations, specifically, the workflow continuously acquires BOM information of orders, processing progress of suppliers, receiving status and other data, automatically identifies the orders needing intervention according to early warning rules (such as delivery deadlines and overdue) set by enterprises, and immediately starts an early warning mechanism and executes notification and processing processes once abnormality is determined. When the difference between the 'required delivery date' and the current time of an order reaches a threshold of a clinic period set by an enterprise (such as 3 days and 5 days before delivery), the system automatically triggers early warning, pushes early warning information to a purchasing responsible person and a supplier interfacing person, wherein the content comprises an order number, a part name, the number of remaining days, the expected delivery time, a risk reason (such as 'delay of a finishing working section by 1 day') and a recommended operation, when the actual delivery time exceeds the delivery date required by a BOM and no effective delay approval exists, the system triggers early warning to inform the purchasing department of the overdue early warning, informs the responsible person and the supplier high-level of the supplier, has an influence description (such as 'has caused the stop of an assembly line for 12 hours'), automatically synchronizes to an enterprise management layer (such as the production general supervision) if the system does not respond for 24 hours, starts an emergency scheme (such as calling a safety stock, enables a standby supplier), gathers whole flow data of the order (such as a working section delay record and communication mail), analyzes the root cause (such as the supplier productivity shortage and logistics accident), and generates an early warning report.
Further, step S200 further includes, upon querying the rework record, providing a plurality of data export options including exporting all data and exporting filter data.
Preferably, when inquiring the repair records, the user can flexibly select the range and the content of the exported data according to the actual requirements, specifically, all the repair records under the current inquiry condition are exported at one time, all the field information (such as part numbers, repair time, repair reasons, processing personnel, belonging orders and the like) stored in the module are contained, the records meeting the specific requirements are filtered through screening functions (such as conditions of time range, part types, suppliers, repair states and the like) provided by the system, and then the screened subset data are exported, so that redundant data are prevented from being exported, and the manual screening cost is reduced.
And step S300, configuring a right management strategy, and performing control management of accessible data and executable operations on the order state.
Preferably, a permission management policy is configured, namely, the risk of data leakage is solved through the rule setting of layering, role division and scene division, sensitive information (such as vendor base price and core BOM parameters) is prevented from being acquired by unauthorized personnel, misoperation risk is avoided, basic staff is prevented from touching key processes (such as unauthorized order state modification and return record deletion) by mistake, responsibility tracing is fuzzy, responsibility of each role is clarified through operation trace, and the problem that the responsibility is unclear is avoided. The authority management comprises objects, contents and operations, wherein an authority role group is preset according to different post functions in an enterprise, the authority management and control of ' field level ' and ' record level ' of order state data are carried out, different roles see different information ' are realized, specific operations are forbidden or allowed according to role responsibilities, and flow confusion caused by ' override execution ' is avoided. And further, control management of accessible data and executable operation on order states is realized, the data safety and the management efficiency of external cooperation parts are improved, and efficient cooperation and standardized operation of purchasing flows are realized.
Further, the step S300 comprises the step S310 of constructing a role access control (RBAC) model, wherein a, a service scene is acquired, a plurality of system roles are determined through analysis, b, a role hierarchy is defined according to the plurality of system roles, a role tree is generated, c, a role access control (RBAC) model is generated based on the role tree, d, the plurality of system roles comprise a system super manager, a purchasing manager, a quality manager, a provider operator and a provider mechanical designer.
Preferably, the business scenario is obtained, including the enterprise side (purchase management, quality inspection, system operation and maintenance) and the provider side (order execution, production data feedback, technical document submission analysis), and multiple system roles are determined according to the business function division, including a system super manager, a purchase manager, a quality manager, a provider operator and a provider machinery designer, as shown in table 1:
table 1 System role function mapping table
Preferably, then defining role tiers, automatically having all rights of low-tier roles with overlapping exclusive rights, not crossing different role rights of the tiers to avoid confusion of responsibilities, generating role trees, reconstructing role access control (RBAC) models, wherein a system super manager is used for creating/deleting roles, configuring role rights, managing user account numbers, monitoring system logs, deriving full-volume data, modifying system basic parameters (such as threshold values, right rules), a purchase manager is used for creating/modifying purchase orders, associating BOM information, selecting suppliers, deriving purchase related data (such as order status, supplier quotation), a quality manager is used for entering a receipt inspection result (qualification/disqualification), initiating a repair flow, recording quality problem description, generating quality reports (such as disqualification reason distribution, supplier quality ranking), deriving quality related data, a supplier manager is used for checking all orders allocated to the suppliers, examining production plans, logistics arrangement, summarizing production section completion status, abnormal events (such as equipment failure) and giving the manager, a supplier operator is used for creating/modifying purchase order status (such as "rough-order completed", actual demand for designing in-order quality report, quality report requirements (such as actual demand for the supplier is updated), a raw material quality report is used for the raw material is required to be analyzed, submitting technical improvement schemes (such as optimizing processing technology and reducing cracks).
Further, the step S300 includes a step S320 of configuring authority fine granularity by utilizing the role access control (RBAC) model, wherein the authority is used for function control and the data authority is used for resource control, a step S330 of configuring the authority comprises disassembling a system function into an operation unit and distributing the operation unit according to the system roles, a step S340 of configuring the data authority comprises dividing system resources according to a data range and binding by utilizing the system roles, and a step S350 of managing the authority further comprises a system page, buttons in the page and fields of a system list.
Preferably, a role access control (RBAC) model realizes full-link management and control from a function entry to data content through three-dimensional binding of role-operation-data, wherein operation authority controls what a user can do, such as whether an order deleting button can be clicked, data authority controls what the user can see, such as whether a provider contact way field in an order can be checked, and page element level management and control sinks authority to system pages, buttons and list fields, so that pixel level accurate control is realized. The complex functions are decomposed into minimum executable units (such as button clicking and form submitting), then an operation unit is allocated according to the system role, if the role does not have certain operation authority, the corresponding button is hidden or gray in the page (such as a provider operator cannot see the button for deleting an order), and the button clicking event automatically triggers log record, including 'role + time + operation content'. According to the binding of the roles of the resource scope, the configuration of the data authority is carried out, for example, the field level control page list or the visibility and editing authority of the fields in the form (such as hiding the 'unit price' field), the record level control user can access the order record scope (such as only displaying the order of the department or the provider) and the business object level control whether to allow access to certain types of data (such as prohibiting the provider from viewing the core technical parameters of the enterprise BOM), the unauthorized role cannot access a specific page (such as the provider operator does not have permission to enter the 'provider admission audit' page), and the content seen by different roles in the same page is different (such as the purchasing administrator sees the complete order operation column and the provider administrator sees only the 'production progress feedback' button).
Further, step S320 further includes encrypting the interactive data between the enterprise ERP system and the external provider by using a data encryption and secure transmission technology, and restricting the access rights of the sensitive data by an identity authentication and authorization mechanism.
Preferably, TLS1.3 (transport layer security protocol) is used to encrypt the data transmission channel, so as to ensure that the data cannot be decrypted even if intercepted in the internet transmission process, and all sensitive information transmitted between the enterprise ERP system and the external provider is covered, including but not limited to purchasing data, BOM details (such as core technical parameters), purchasing unit price, order arrangement, provider data, production process files, raw material sources, capacity bottleneck information, quality data, inspection reports, repair rate statistics, unqualified product processing schemes, system interaction data, user account numbers, operation logs and authority configuration information. Meanwhile, the access authority of sensitive data is limited through an identity authentication and authorization mechanism, namely, a user is required to additionally provide an identity certificate besides inputting an account password, unauthorized access caused by account password leakage is prevented, dynamic properties such as environment, time and data sensitivity are increased on the basis of RBAC role authority, finer-granularity access control is realized, the safety and the integrity of the data are further ensured, and the trust of a provider on the data safety is enhanced.
Further, the step S300 also includes a step S360 of supporting multi-terminal access, including data query, entry and approval by the mobile terminal application, and real-time synchronization of the mobile terminal application data and the Web terminal data, a step S370 of constructing a visual drag and configuration interface for personalized setting according to operation habits, including custom layout and list field display, and a step S380 of automatically storing and applying personalized setting by the system according to user configuration.
Preferably, the system supports access through mobile equipment such as a mobile phone, a tablet and the like to perform data query, data input and approval, namely, order states (such as delivery deadline reminding and repair records), supplier performance, quality data and the like are checked at any time and any place, a scanning code inputs goods receiving information (such as part batch numbers and quantity) and repair reasons (photographing and uploading fault pictures), a notification to be approved (such as return goods application and BOM change) is received, and approval (signature confirmation and filling opinion) is directly completed at a mobile terminal. The user can freely adjust the system page layout through the dragging component (such as cards, tables, charts), and in the data list (such as order list, supplier list), the user can select the display/hidden field independently and adjust the field sequence. The method comprises the steps of storing the layout, field display and other settings of each user, supporting setting of 'role default configuration' (such as displaying a temporary order reminding card by default of all purchase administrators), enabling a new user to enter an automatic application template, reducing repeated configuration cost, automatically loading the same configuration when the mobile terminal logs in next time after the user adjusts the layout at a Web terminal, and further improving system management efficiency, optimizing experience and flexibility and expansibility.
In the above, a method for managing outsourced purchase parts according to an embodiment of the present invention is described in detail with reference to fig. 1. Next, a management system for outsourcing parts according to an embodiment of the present invention will be described with reference to fig. 2.
According to the management system for the outsourcing purchasing parts, which is disclosed by the embodiment of the invention, the technical problems that information transfer is lagged and inaccurate, data input efficiency is low and is easy to make mistakes, purchasing flows cannot be tracked in a full flow, and data security risks are high due to rights management deficiency in the prior art are solved, and the technical effects of improving information processing efficiency and accuracy, realizing transparency and traceability of purchasing flows and improving the collaborative efficiency of an enterprise supply chain are achieved. As shown in FIG. 2, the management system for the outsourced purchasing of the parts comprises an information synchronization module 10, a tracking analysis module 20 and a control management module 30.
The system comprises an information synchronization module 10, a tracking analysis module 20 and a control management module 30, wherein the information synchronization module is used for connecting an ERP system of an enterprise, synchronously screening BOM information and supplier information of purchased parts in real time, inputting repair data, receiving data and returning data, wherein the inputting mode comprises code scanning inputting and pc popup window selecting inputting, the tracking analysis module 20 is used for carrying out full-flow tracking analysis according to the BOM information, the supplier information, the repair data, the receiving data and the returning data to determine the order state of the purchased parts, and the control management module 30 is used for configuring an authority management strategy and carrying out control management of accessible data and executable operation on the order state.
Next, the specific configuration of the trace analysis module 20 will be described in detail. The tracking analysis module 20 may further include at least the BOM base information, the supplier process information, the station completion status, the receiving status, the return status, and the component repair status for the purchased component.
Next, the specific configuration of the trace analysis module 20 will be described in further detail. The tracking analysis module 20 further includes monitoring the status of the order by using a workflow, and automatically triggering an early warning mechanism to early warn if the order of the purchased component has a delivery deadline or overdue.
Next, the specific configuration of the control management module 30 will be described in detail. The control management module 30 further includes constructing a role access control (RBAC) model a. Acquiring a business scenario, analyzing and determining a plurality of system roles b. Defining a role hierarchy from the plurality of system roles, generating a role tree c. Generating a role access control (RBAC) model based on the role tree d. Wherein the plurality of system roles include a system super manager, a procurement manager, a quality manager, a vendor operator and a vendor mechanical designer.
Next, the specific configuration of the control management module 30 will be described in further detail. The control management module 30 still further includes performing authority fine-grained configuration by using the role access control (RBAC) model, including configuring operation authorities and configuring data authorities, wherein the operation authorities are used for function control, the data authorities are used for resource control, the configuring operation authorities include disassembling system functions into operation units and distributing the operation units according to the multiple system roles, the configuring data authorities include dividing system resources according to a data range and binding by using the multiple system roles, and the authority control further includes a system page, buttons in the page and fields of a system list.
Next, a detailed description will be continued of a specific configuration of a management system for outsourcing purchase of parts. The system comprises a mobile terminal application, a Web terminal application, a visual drag and configuration interface, a user-defined layout and list field display, a system and a user-defined configuration, wherein the mobile terminal application is used for carrying out data query, recording and approval through the mobile terminal application, and the mobile terminal application data is synchronous with the Web terminal data in real time.
Next, the specific configuration of the control management module 30 will be described in further detail. The control management module 30 further includes encrypting the interactive data between the enterprise ERP system and the external provider by using data encryption and secure transmission technology, and limiting the access rights of the sensitive data by an identity authentication and authorization mechanism.
Next, the specific configuration of the trace analysis module 20 will be described in further detail. The trace analysis module 20 still further includes providing a variety of data export options including exporting all data and exporting filter data when querying a rework record.
The management system for the outsourced purchased parts provided by the embodiment of the invention can execute the management method for the outsourced purchased parts provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Although the present application makes various references to certain modules in a system according to an embodiment of the present application, any number of different modules may be used and run on a user terminal and/or a server, and each unit and module included are merely divided according to functional logic, but are not limited to the above-described division, so long as the corresponding functions can be implemented, and in addition, specific names of each functional unit are only for convenience of distinguishing from each other, and are not intended to limit the scope of protection of the present application.
The above embodiments do not limit the scope of the present application. It will be apparent to those skilled in the art that various modifications, combinations, and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of the present application.