Component production preparation approval method and electronic equipment

Abstract

The invention discloses a part production preparation approval method and electronic equipment, and the method comprises the steps: obtaining a task notification corresponding to a part in response to a part production preparation approval request, and determining the access authority of the task notification, the task notice is at least used for notifying a target object to execute production preparation of the part; under the condition that the access permission belongs to a target permission department, the adoption level of the task notification is determined, the release state of the task notification is determined according to the adoption level, the adoption level comprises whole vehicle adoption and local adoption, and the release state comprises release confirmation and release refusal. Accurate management and control of task notification permissions are achieved, intelligent matching of levels and release states is adopted, and efficient and compliant execution of production preparation is guaranteed.

Description

Technical Field

[0001] This invention relates to the field of information processing technology, and in particular to a method for approving the production preparation of components and an electronic device. Background Technology

[0002] In the automotive or complex equipment manufacturing industries, component production preparation is a critical step in product development and mass production, typically requiring collaboration among multiple departments (such as R&D, procurement, production, and quality). To ensure the standardization and consistency of production preparation, companies formally notify relevant parties to perform tasks such as component process design, material procurement, and tooling preparation through task notifications (such as engineering instructions and production preparation notices). These documents often involve sensitive information (such as technical parameters and supplier data), and their scope of application may vary depending on the vehicle configuration (used in the entire vehicle) or a specific module (used in a specific area). Therefore, strict control over document access permissions (e.g., viewing is restricted to the target department) and publication status (effective upon confirmation of publication, and temporarily suspended if publication is refused) is necessary.

[0003] In related technologies, static permission settings and manual review are relied upon: access permissions for task notifications are assigned through fixed roles (such as department heads) or simple rules (such as sharing within the project team), and the release status is determined subjectively by the approver based on experience (such as "adopted for the whole vehicle" or "partially adopted" being merely noted, without any automated association logic). For example, a company might upload task notifications through an OA system, manually select "departments allowed to access," and have the approving leader directly mark "released" or "rejected." The solution has significant drawbacks: First, the granularity of access control is insufficient—access rights are only divided by department, which cannot dynamically adapt to specific parts or task scenarios (e.g., only some positions in the same department need to view sensitive parameters), which can easily lead to unauthorized access or information redundancy. Second, the decision on release status lacks a basis—the association between adoption level (whole vehicle / partial) and release status relies on human experience and no standardized rules have been established (e.g., "whole vehicle adoption" must be approved by senior management, while "partial adoption" can be confirmed by the department level), which can easily lead to misjudgments (e.g., parts that should be implemented globally are only partially released, affecting production collaboration). Third, the process is inefficient—manually verifying permissions and status is time-consuming and prone to errors, especially when multiple parts are approved in parallel, which delays the production preparation schedule. Summary of the Invention

[0004] This invention provides a method for approving the production preparation of components and an electronic device to solve the problems of inefficient management of task notifications caused by static permission allocation and manual review, which are prone to unauthorized access or misjudgment.

[0005] According to one aspect of the present invention, a method for approving the production preparation of a component is provided, comprising:

[0006] In response to a production preparation approval request for a component, a task notification corresponding to the component is obtained, and the access permissions of the task notification are determined. The task notification is used at least to notify the target object to perform the production preparation of the component.

[0007] If the access permission belongs to the target authorized department, the adoption level of the task notification is determined, and the release status of the task notification is determined according to the adoption level. The adoption level includes whole vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release.

[0008] According to another aspect of the present invention, a method for approving the production preparation of a component is provided, comprising:

[0009] The access permission determination module is used to respond to the production preparation approval request of the component, obtain the task notification corresponding to the component, and determine the access permission of the task notification, wherein the task notification is at least used to notify the target object to perform the production preparation of the component.

[0010] The release status determination module is used to determine the adoption level of the task notification when the access permission belongs to the target permission department, and to determine the release status of the task notification based on the adoption level. The adoption level includes whole vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release.

[0011] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0012] At least one processor; and

[0013] A memory communicatively connected to the at least one processor; wherein,

[0014] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the production preparation approval method for components according to any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the production preparation approval method for components according to any embodiment of the present invention.

[0016] The technical solution of this invention, in response to a production preparation approval request for a component, obtains the corresponding task notification for the component and determines the access permissions of the task notification. Since the task notification is at least used to notify the target object to execute the production preparation of the component, precise control over the access permissions of the task notification ensures the targeted transmission and secure execution of production preparation information. If the access permissions belong to the target authorized department, the adoption level of the task notification is determined, and the release status of the task notification is determined based on the adoption level. Since the adoption level includes whole-vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release, the release status can be accurately determined by distinguishing the adoption level. This solves the problem of inefficient task notification management caused by static permission allocation and manual review, which is prone to unauthorized access or misjudgment. It achieves precise control over task notification permissions, intelligent matching of adoption level and release status, and ensures efficient and compliant execution of production preparation.

[0017] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart of a production preparation approval method for a component according to Embodiment 1 of the present invention;

[0020] Figure 2 This is a flowchart of a production preparation approval method for a component according to Embodiment 2 of the present invention;

[0021] Figure 3 This is a schematic diagram of the structure of a component production preparation approval device provided according to Embodiment 3 of the present invention;

[0022] Figure 4 This is a schematic diagram of the production preparation approval for a task notification corresponding to a component of a Hongqi vehicle model, provided according to an embodiment of the present invention.

[0023] Figure 5 This is a schematic diagram of the approval result of the CDP system with part number 5407305-QU51 according to an embodiment of the present invention;

[0024] Figure 6This is a schematic diagram of the approval result for PDM system part number 5407305-HA51 provided according to an embodiment of the present invention;

[0025] Figure 7 This is a schematic diagram of the structure of an electronic device that implements the component production preparation approval method of the present invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0029] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0030] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0031] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0032] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0033] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0034] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0035] Example 1

[0036] Figure 1 The flowchart of a component production preparation approval method is provided in Embodiment 1 of the present invention. This embodiment is applicable to component production preparation approval in the automotive and other manufacturing industries. It requires fine control over the authority and release status of task notifications. This method can be executed by a component production preparation approval device, which can be implemented in hardware and / or software. Optionally, it can be implemented through an electronic device, such as a mobile terminal, a PC, or a server.

[0037] like Figure 1 As shown, the method may specifically include:

[0038] S110. In response to the production preparation approval request for the component, obtain the task notification corresponding to the component, and determine the access permission of the task notification, wherein the task notification is at least used to notify the target object to perform the production preparation of the component.

[0039] The term "components" can be understood as various independent or combined parts, assemblies, modules, etc., that make up a complete vehicle. They are the basic building blocks of a product (such as a car) and the core object of the production preparation approval process. All approvals, task notifications, and adoption judgments revolve around a specific component to ensure it can be correctly and compliantly put into production. A production preparation approval request can be understood as a need or application for approval of production preparation matters for a specific component before it is formally put into production. It is the trigger point of the process, indicating that various pre-production preparations for a certain component need to begin, after which the generation and approval of the task notification will occur. The task notification can be understood as a formal notification document or system record used to notify the target object (such as relevant departments / personnel) to perform the production preparation work for a certain component. The task notification also includes the production preparation information for the component. The target object may include, but is not limited to, R&D engineers, process engineers, and purchasing specialists. Access permissions can be understood as whether a user, role, or department has the authority to view, operate, or obtain a task notification. They are usually set based on organizational structure, division of responsibilities, or security policies to control the scope of information distribution and operational boundaries, ensuring that only relevant responsible departments or personnel can access specific production preparation tasks. This is a prerequisite for entering subsequent logical judgments (such as adoption level or release status).

[0040] S120. If the access permission belongs to the target authority department, determine the adoption level of the task notification, and determine the release status of the task notification based on the adoption level. The adoption level includes whole vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release.

[0041] The target authorized department can be understood as a pre-defined specific department or role group authorized to access or process a task notification. This is related to the component category, adoption level, or business affiliation, serving as a reference standard for authorization judgment. Only when the access permission of the task notification matches the target authorized department is further processing of the notification permitted. The target authorized department can be the design space, or a product library such as "Sedan," "Hongqi L Platform," "Power Motor," "Power Battery," "Electric Vehicle," "Passenger Vehicle Engine," "Passenger Vehicle Transmission," or "Passenger Vehicle Drive Axle." Different target authorized departments use different systems, including the CDP system and the PDM system. The collaborative area stored in the CDP system is the "Design Space." The PDM system stores the categories "Sedan," "Hongqi L Platform," "Power Motor," "Power Battery," "Electric Vehicle," "Passenger Vehicle Engine," "Passenger Vehicle Transmission," and "Passenger Vehicle Drive Axle." The adoption level can be understood as the application scope of the component identified in the task notification during production preparation, divided into "whole vehicle adoption" and "partial adoption." This is a crucial basis for determining the subsequent release status, approval process complexity, and resource allocation scope. The term "vehicle adoption" can be understood as the component being included in the configuration list of the officially mass-produced vehicle, belonging to the vehicle-level BOM (Bill of Materials). This indicates that the component has high priority and high compliance requirements, triggering the "confirmed release" status and driving comprehensive production preparation. "Partial adoption" can be understood as the component being used only in specific scenarios (such as prototype vehicles, partial modifications, non-mainstream platforms, verification samples, etc.), not yet included in the main mass-production BOM, requiring further assessment before the release status can be confirmed. The release status can be understood as the current approval result status of the task notification, indicating whether it is effective and executable. It is the final output of the process, determining whether production preparation has officially started. Only task notifications in the "confirmed release" status can trigger downstream business actions (such as process route generation, purchase order creation, etc.). "Confirmed release" can be understood as indicating that the task notification has been approved, has executable effect, and can serve as the formal basis for production preparation. It is the "green light" signal of the process, allowing the system or manual intervention to start subsequent production preparation work. The refusal to issue a task notification can be understood as indicating that the task notification has not been approved, lacks execution validity, and cannot be used for formal production preparation. It serves as a "red light" signal in the process, used to intercept non-compliant, unnecessary, or premature production preparation requests, ensuring reasonable resource allocation and project quality. Refused task notifications can be returned to the original functional department for redesign.

[0042] Optionally, based on the above scheme, the method further includes: if the access permission does not belong to the target access department, determining the publishing status as a refusal to publish.

[0043] Understandably, if the person (or department) currently handling the task notification does not have permission to access it (that is, the task notification does not belong to the target department that is allowed to view the task notification), then the system will automatically set the release status of the task notification to "reject release".

[0044] By adopting this technical solution, precise control of permissions can be achieved, preventing unauthorized departments from making mistakes or issuing tasks in violation of regulations, ensuring that the production preparation process is only executed by authorized departments, and improving management security and process standardization.

[0045] The technical solution of this invention, in response to a production preparation approval request for a component, obtains the corresponding task notification for the component and determines the access permissions of the task notification. Since the task notification is at least used to notify the target object to execute the production preparation of the component, precise control over the access permissions of the task notification ensures the targeted transmission and secure execution of production preparation information. If the access permissions belong to the target authorized department, the adoption level of the task notification is determined, and the release status of the task notification is determined based on the adoption level. Since the adoption level includes whole-vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release, the release status can be accurately determined by distinguishing the adoption level. This solves the problem of inefficient task notification management caused by static permission allocation and manual review, which is prone to unauthorized access or misjudgment. It achieves precise control over task notification permissions, intelligent matching of adoption level and release status, and ensures efficient and compliant execution of production preparation.

[0046] Example 2

[0047] Figure 2 This is a flowchart of a component production preparation approval method provided in Embodiment 2 of the present invention. This embodiment further refines the determination of the release status of the task notification based on the adoption level, building upon the relationships between the above embodiments. Optionally, determining the release status of the task notification based on the adoption level includes: determining the release status as confirmed release when the adoption level is whole vehicle adoption; and / or, when the adoption level is partial adoption, detecting whether the component manufacturing includes route information, and determining the release status of the task notification based on a first detection result. Detailed implementation can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here.

[0048] like Figure 2 As shown, the method may specifically include:

[0049] S210. In response to the production preparation approval request for the component, obtain the task notification corresponding to the component, and determine the access permission of the task notification, wherein the task notification is at least used to notify the target object to perform the production preparation of the component.

[0050] S220. If the access permission belongs to the target authority department, determine the adoption level of the task notification. If the adoption level is vehicle-wide adoption, determine the release status as confirmed release.

[0051] Understandably, when the target authorized department has access to the task notification, it will read the adoption level associated with the task notification. If the adoption level is determined to be "vehicle adoption", it means that the component has been included in the formal configuration of the vehicle and has high priority and complete compliance. At this time, the release status of the task notification should be automatically set to "confirmed release" to authorize the full commencement of subsequent production preparation work.

[0052] S230. In the case of partial adoption, detect whether the manufacturing of the component includes route information, and determine the release status of the task notification based on the first detection result.

[0053] In this context, component manufacturing can be understood as the production and manufacturing process, technological flow, required resources, and information related to the component; in this embodiment, it refers to its manufacturing route information. If component manufacturing includes valid manufacturing route information, it indicates that the processing, assembly, and procurement processes of the component have been planned, and it is more likely to be allowed to be released. The route information can be understood as structured data describing all manufacturing processes, technological routes, factory / workshop allocations, equipment requirements, etc., required for the component from raw materials to finished products. This directly affects whether the process department needs to arrange in-house process routes or whether the procurement department should initiate outsourcing processes. The route information serves as an entry threshold in the "partial adoption" scenario. If there is no route information, it indicates that the component is not yet manufacturable in the current department. The first detection result can be understood as the result of the detection operation on "whether component manufacturing includes manufacturing route information," that is, if it includes (has route information), the detection result is "yes," and if it does not include (no route information), the detection result is "no."

[0054] It should be noted that, in this embodiment of the invention, if the adoption level is vehicle-wide adoption, and / or if the adoption level is partial adoption, S220 is executed, provided that the access permission belongs to the target authority; and S230 is executed.

[0055] Based on the above scheme, optionally, detecting whether the component manufacturing includes route information includes: obtaining project information, factory identification information and component identification information from the task notification, and querying the component manufacturing route information from a preset database based on the project information, factory identification information and component identification information.

[0056] The project information can be understood as project identifiers or project context information associated with the current component production preparation, including but not limited to project number, project name, etc., used to define the scope of application of the manufacturing route. The same component may correspond to different process routes in different projects. The factory identifier information can be understood as information used to uniquely identify a certain manufacturing plant or workshop, which may be a factory code, name, ID, etc., used to clarify which specific factory / workshop the component is planned to be produced in; it is one of the indispensable query conditions when querying "manufacturing route information", because the production path of the same component may be completely different in different factories. The component identifier information can be understood as information used to uniquely identify a specific component, including but not limited to component number, component name, and material code, etc., and is the unique key identifier for querying and identifying the component. The preset database can be understood as a pre-established and maintained structured database (such as the process database in PLM, MPM, or MES) that stores process master data such as manufacturing routes, and is the data source for all data queries, by querying this database to obtain "component manufacturing route information".

[0057] By adopting this technical solution, the manufacturing route can be efficiently queried from a pre-set database by accurately linking project, factory and component information, ensuring that the production path is clear and traceable, effectively avoiding blind production, and improving the compliance and feasibility of production preparation.

[0058] Based on the above scheme, optionally, determining the release status of the task notification based on the first detection result includes: if the first detection result includes route information but the route information does not include the completed design task book, determining the release status as rejection.

[0059] The design task book can be understood as a detailed design guidance document or task list prepared for a specific component or production task, including but not limited to design requirements, technical parameters, and design schedule, and is a key indicator of the closed loop of the design phase. If route information exists but a completed design task book is lacking, it indicates that the manufacturing basis may be incomplete, unstable, or not formally confirmed, and there is a risk of engineering changes. Therefore, the issuance of a task notification should not be permitted.

[0060] By adopting this technical solution, the design task book is ensured to be completed before production preparation, avoiding production deviations due to design deficiencies, effectively reducing the risk of rework, and ensuring sufficient production basis and standardized and controllable processes.

[0061] Based on the above scheme, optionally, determining the release status of the task notification based on the first detection result includes: if the first detection result includes route information and the route information includes a completed design task book, determining the release status as confirmed release; and / or, if the first detection result does not include route information, detecting whether the component is an external part, and determining the release status of the task notification based on the second detection result.

[0062] The term "outsourced parts" can be understood as components whose manufacturing process relies on external resources such as external procurement, outsourced processing, and mold making. These components can be identified by markings such as "procurement" or "mold" in their manufacturing route information, or by being explicitly provided by a supplier. This is a key classification for determining whether components need to be obtained from external sources.

[0063] By adopting this technical solution, we can ensure sufficient production basis by verifying route information and design task book, classify and manage outsourced parts without route information, achieve precise release control, reduce production risks, and ensure process compliance and execution efficiency.

[0064] Based on the above scheme, optionally, determining the release status of the task notification based on the second detection result includes: if the second detection result is an external component and the external component is used independently, determining the release status as a rejection to release; and / or, if the second detection result is an external component and the external component is not used independently, detecting whether the component meets a preset type, and determining the release status of the task notification based on the third detection result.

[0065] The term "independent adoption" can be understood as the adoption of a component as an independent, complete unit (rather than as part of a larger assembly or system), with its own adoption level and approval process. It is understood that if an externally manufactured component is "independently adopted," even if it is purchased externally, its task notification will be refused due to control requirements, risk control, or process specifications. The term "preset type" can be understood as a predefined set of component types used to classify and manage components of different natures, uses, or management requirements. It is used to determine whether a component belongs to a type that can be specially handled or allowed for release when certain detection conditions are not met (such as lack of route information or non-independent adoption), serving as a supplementary screening condition for determining the subsequent release status (such as whether release is allowed). The preset types include, but are not limited to, logical assemblies, devices, and technical conditions. The term "logical assembly" can be understood as a functional component or module composed of multiple components combined according to certain logical relationships, but not a physically fully integrated assembly; it emphasizes logical combination relationships and functional synergy. The term "device" can be understood as a component with a specific function or purpose; it refers to equipment, mechanisms, or modules with independent functions that can be installed or used independently, such as sensor devices. The term "technical specifications" can be understood as technical specifications for certain specific processes, surface treatments, or connection methods of components, rather than referring to specific physical parts. These technical specifications include coating and solder joints. The term "coating" can be understood as surface treatment process requirements related to appearance, corrosion resistance, and color. The term "solder joints" can be understood as technical specifications related to welding processes, connection strength, and quality control.

[0066] By adopting this technical solution, high-risk independent external components are strictly controlled by distinguishing whether they are used independently. At the same time, non-independent external components are managed in a refined manner according to preset types, which effectively reduces production risks and ensures compliant release and reasonable resource allocation.

[0067] Based on the above scheme, optionally, determining the release status of the task notification based on the second detection result includes: if the second detection result is not an external component, determining the release status as confirmed release.

[0068] Understandably, if the inspection reveals that the component is not an outsourced part (i.e., it is a self-manufactured part), the release status of its task notification will be directly set to "confirmed release". This is because self-manufactured parts usually have internal manufacturing capabilities to ensure their reliability, do not rely on external suppliers, have manageable risks, and can confidently proceed with production preparation.

[0069] By adopting this technical solution, we can ensure a clear process and well-defined responsibilities for self-made parts, reduce approval risks, ensure efficient production preparation, and improve the standardization and reliability of internal production task management.

[0070] Based on the above scheme, optionally, determining the release status of the task notification based on the third detection result includes: determining the release status as confirmed release when the component is of a preset type; and / or determining the release status as rejected release when the component is not of a preset type.

[0071] Understandably, it's necessary to check whether components belong to pre-approved special types, such as "logic assemblies," "devices," or "technical specifications" (e.g., painting requirements, solder joint specifications). If so, a task notification can be issued to initiate subsequent work; otherwise, issuance is rejected. This is because these pre-approved component types typically don't rely on traditional manufacturing routes or exist in the form of technical specifications. Even without detailed process routes or being outsourced, they can safely and compliantly guide production or procurement. Other non-pre-approved component types, lacking manufacturing routes and not falling into these exception categories, mean their production feasibility is unverified. Issuing them prematurely could lead to resource waste, process chaos, or quality risks. Therefore, strict control is necessary to ensure that only qualified components can enter the production preparation stage.

[0072] By adopting this technical solution, the compliant release of components that meet specific technical or management requirements is ensured through the accurate identification of preset types of components (such as logic assemblies, device components, and other special types), while unqualified components are blocked, thus effectively controlling production risks and ensuring process standardization and product quality.

[0073] like Figure 4 The diagram shows the production preparation approval process for task notifications corresponding to parts for the target vehicle model Hongqi. Table 1 below shows examples of some externally manufactured parts under the CDP system. Table 2 below shows examples of some externally manufactured parts under the PDM system. For example... Figure 5 The image shows the approval result for CDP system part number 5407305-QU51. Figure 6 This refers to the approval result for PDM system part number 5407305-HA51.

[0074] .

[0075] .

[0076] The technical solution of this invention implements hierarchical and precise control over the issuance of task notifications. When the entire vehicle is adopted, the notification is confirmed to ensure overall compliance. When the vehicle is adopted, the status is flexibly determined through route information detection. This not only ensures that the entire process of parts is under control, but also improves the efficiency of parts approval and balances the safety and flexibility of production preparation.

[0077] Example 3

[0078] Figure 3 This is a schematic diagram of a component production preparation approval device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: an access permission determination module 310 and a release status determination module 320.

[0079] Access permission determination module 310 is used to respond to a production preparation approval request for a component, obtain a task notification corresponding to the component, and determine the access permission of the task notification, wherein the task notification is at least used to notify the target object to perform the production preparation of the component.

[0080] The release status determination module 320 is used to determine the adoption level of the task notification when the access permission belongs to the target permission department, and determine the release status of the task notification according to the adoption level, wherein the adoption level includes whole vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release.

[0081] The technical solution of this invention addresses the problem of inefficient task notification management caused by static permission allocation and manual review, which can lead to unauthorized access or misjudgments. This allows for precise control of task notification permissions and ensures the safe and targeted transmission of production preparation information, as the task notification is used to at least notify the target object to perform the production preparation of the component. Furthermore, the release status determination module, when the access permission belongs to the target department, determines the adoption level of the task notification and its release status based on the adoption level. Since the adoption level includes whole-vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release, the release status can be accurately determined by distinguishing the adoption level. This solves the problem of inefficient task notification management and the risk of unauthorized access or misjudgments caused by static permission allocation and manual review. It achieves precise control of task notification permissions and intelligent matching of adoption level and release status, ensuring efficient and compliant execution of production preparation.

[0082] Based on the above scheme, the release status determination module includes a release status determination submodule. Specifically, the release status determination submodule is used to determine the release status as confirmed release when the adoption level is whole vehicle adoption; and / or, when the adoption level is partial adoption, to detect whether the component manufacturing includes route information, and determine the release status of the task notification based on a first detection result.

[0083] Based on the above scheme, the release status determination submodule includes a release status determination unit. The release status determination unit is configured to determine the release status as confirmed release if the first detection result includes route information and the route information includes a completed design task book; and / or, if the first detection result does not include route information, to detect whether the component is an externally manufactured part, and to determine the release status of the task notification based on the second detection result.

[0084] Based on the above scheme, the release status determination submodule is further configured to determine the release status as rejection release when the first detection result includes route information but the route information does not include the completed design task book.

[0085] Based on the above scheme, the release status determination unit includes a release status determination subunit. The release status determination subunit is configured to determine the release status as "reject release" when the second detection result indicates an external component and the external component is used independently; and / or, when the second detection result indicates an external component and the external component is not used independently, to detect whether the component meets a preset type, and determine the release status of the task notification based on a third detection result, wherein the preset type includes at least logic assembly, device component, and technical conditions.

[0086] Based on the above scheme, the release status determination unit includes a release status determination subunit. The release status determination subunit is further configured to determine the release status as confirmed release if the second detection result is not an external component.

[0087] Based on the above scheme, the release status determination subunit is further configured to determine the release status as confirmed release when the component is of a preset type; and / or, to determine the release status as rejected release when the component is not of a preset type.

[0088] Based on the above scheme, the release status determination submodule is also used to obtain the project information, factory identification information and component identification information in the task notification, and query the component manufacturing route information from a preset database according to the project information, factory identification information and component identification information.

[0089] Based on the above scheme, the publishing status determination module is further configured to determine the publishing status as "reject publishing" when the access permission does not belong to the target access department.

[0090] The component production preparation approval device provided in the embodiments of the present invention can execute the component production preparation approval method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0091] Example 4

[0092] Figure 7 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0093] like Figure 7 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0094] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0095] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a component production preparation approval method.

[0096] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from ROM 12. When the computer program is executed by processor 11, it performs the functions defined in the methods of the embodiments of the present invention.

[0097] In some embodiments, a component production preparation approval method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the component production preparation approval method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a component production preparation approval method by any other suitable means (e.g., by means of firmware).

[0098] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0099] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0100] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0102] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0103] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0104] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0105] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for approving the production preparation of a component, characterized in that, include: In response to a production preparation approval request for a component, a task notification corresponding to the component is obtained, and the access permissions of the task notification are determined. The task notification is used at least to notify the target object to perform the production preparation of the component. If the access permission belongs to the target authorized department, the adoption level of the task notification is determined, and the release status of the task notification is determined according to the adoption level. The adoption level includes whole vehicle adoption and partial adoption, and the release status includes confirmed release and rejected release.

2. The method according to claim 1, characterized in that, Determining the release status of the task notification based on the adoption level includes: If the adoption level is vehicle-wide adoption, the release status is determined to be confirmed release; and / or, When the adoption level is partial adoption, it is detected whether the manufacturing of the component includes route information, and the release status of the task notification is determined based on the first detection result.

3. The method according to claim 2, characterized in that, Determining the release status of the task notification based on the first detection result includes: If the first detection result includes route information and the route information includes a completed design task book, the release status is determined to be confirmed release; and / or, If the first detection result does not include route information, the system detects whether the component is an externally manufactured part and determines the release status of the task notification based on the second detection result.

4. The method according to claim 2, characterized in that, Determining the release status of the task notification based on the first detection result includes: If the first detection result includes route information but the route information does not include the completed design task book, the release status is determined to be "reject release".

5. The method according to claim 3, characterized in that, Determining the release status of the task notification based on the second detection result includes: If the second detection result indicates an external component and the external component is used independently, the release status is determined to be "reject release"; and / or, If the second detection result indicates that the component is an external part and the external part is not used independently, the component is checked to see if it meets the preset type. The release status of the task notification is determined based on the third detection result. The preset type includes at least logic assembly, device, and technical conditions.

6. The method according to claim 3, characterized in that, Determining the release status of the task notification based on the second detection result includes: If the second detection result is not an external component, the release status is determined to be confirmed release.

7. The method according to claim 5, characterized in that, Determining the release status of the task notification based on the third detection result includes: Under the condition that the component is of a preset type, the release status is determined to be confirmed release; and / or, If the component is not of a preset type, the release status is determined to be "reject release".

8. The method according to claim 2, characterized in that, Detecting whether the manufacturing of the component includes route information includes: Obtain the project information, factory identification information, and component identification information from the task notification, and query the component manufacturing route information from a preset database based on the project information, factory identification information, and component identification information.

9. The method according to claim 1, characterized in that, The method further includes: If the access permission does not belong to the target authority, the publishing status is determined to be "publishing refused".

10. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the production preparation approval method for the component according to any one of claims 1-9.

Images