Business base data management method, device and equipment and readable storage medium

Abstract

This application discloses a method, apparatus, device, and readable storage medium for managing basic business data. The method includes: constructing a hierarchical system for basic business data; the hierarchical system includes multiple levels; constructing corresponding dedicated data resource libraries based on the levels included in the hierarchical system; acquiring the basic business data corresponding to each level; and storing the basic business data corresponding to each level in the corresponding dedicated data resource library. The technical solution disclosed in this application establishes hierarchical relationships between basic business data through a hierarchical architecture, enabling the reuse of basic business data at different levels across projects. This reduces repetitive data entry workload, lowers data management costs, and improves data reuse rate. Furthermore, by storing the basic business data corresponding to each level in the corresponding dedicated data resource library, it achieves categorized management of basic business data, thereby reducing the time cost of data retrieval and improving data management efficiency.

Description

Technical Field

[0001] This application relates to the field of real estate development technology, and in particular to a business basic data management method, apparatus, equipment and readable storage medium. Background Technology

[0002] In real estate development, basic business data lacks correlation, is scattered across different media, resulting in low data reuse rate, low search and retrieval efficiency, and the need for repeated entry of similar data, leading to high data management costs.

[0003] In summary, improving the reuse rate and management efficiency of basic business data is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a business basic data management method, apparatus, device and readable storage medium to improve the reuse rate and management efficiency of business basic data.

[0005] To achieve the above objectives, this application provides the following technical solution: A business infrastructure data management method, comprising: Construct a hierarchical system for basic business data; the hierarchical system for basic business data includes multiple levels; Based on the levels included in the aforementioned business basic data hierarchy, construct corresponding dedicated data resource libraries; Obtain the basic business data corresponding to the level, and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

[0006] Optionally, the business basic data hierarchy includes a component level, a subsystem level, a product platform level, and a product level. Based on the hierarchical structure of the business foundation data, a corresponding dedicated data resource library is constructed, including: Construct a component library corresponding to the component level, construct a module library corresponding to the component level, the subsystem level, and the product platform level, and construct an instance library corresponding to the product level.

[0007] Optionally, acquiring the business basic data corresponding to the level and storing the business basic data corresponding to the level in the corresponding dedicated data resource library includes: Obtain the standard attribute definition and entry review information of the component, determine the target component that has passed the review based on the entry review information, and store the standard attribute definition and entry review information of the target component in the component library.

[0008] Optionally, acquiring the business basic data corresponding to the level and storing the business basic data corresponding to the level in the corresponding dedicated data resource library includes: Obtain the standard attributes of each component, subsystem, and product platform, and obtain the encapsulation and warehousing information of each component, subsystem, and product platform, as well as the encapsulation process management information of each component, subsystem, and product platform; The standard attributes, packaging and warehousing information, and packaging process management information of each component, subsystem, and product platform are stored in the module library.

[0009] Optionally, acquiring the business basic data corresponding to the level and storing the business basic data corresponding to the level in the corresponding dedicated data resource library includes: Acquire project-level business data; the project-level business data includes project instance models and project business data. The project-level business data is stored in the instance library.

[0010] Optionally, it also includes: Obtain the updated business basic data corresponding to the level, and update the business basic data stored in the corresponding dedicated data resource library based on the updated business basic data.

[0011] Optionally, it also includes: The basic business data of each level shall be managed using a unified standard.

[0012] A business basic data management device, comprising: The first construction module is used to build a hierarchical system of business basic data; the hierarchical system of business basic data includes multiple levels. The second construction module is used to construct a corresponding dedicated data resource library based on the levels included in the business basic data hierarchy system. The data storage module is used to acquire the basic business data corresponding to the level and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

[0013] An electronic device, comprising: Memory, used to store computer programs; A processor, configured to implement the steps of the business infrastructure data management method as described in any of the preceding claims when executing the computer program.

[0014] A readable storage medium storing a computer program that, when executed by a processor, implements the steps of the business infrastructure data management method as described in any of the preceding claims.

[0015] This application provides a business basic data management method, apparatus, device, and readable storage medium. The method includes: constructing a business basic data hierarchy; the business basic data hierarchy includes multiple levels; constructing a corresponding dedicated data resource library based on the levels included in the business basic data hierarchy; obtaining the business basic data corresponding to each level; and storing the business basic data corresponding to each level in the corresponding dedicated data resource library.

[0016] The technical solution disclosed in this application constructs a hierarchical system of business basic data, comprising multiple levels. Based on the levels of this system, corresponding dedicated data resource libraries are built, and the acquired business basic data corresponding to each level is stored in the respective dedicated data resource libraries. Thus, this application establishes hierarchical relationships between business basic data through a hierarchical architecture. This hierarchical architecture allows business basic data at different levels to be reused across projects, reducing repetitive data entry, lowering data management costs, and improving data reuse rates. Furthermore, by storing the business basic data corresponding to each level in the corresponding dedicated data resource libraries, it achieves categorized and classified management of business basic data, clearly defining the storage carrier for each type of data, significantly reducing the time cost of data retrieval and improving data management efficiency.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] Figure 1 A flowchart illustrating a business infrastructure data management method provided for some embodiments of this application; Figure 2 A schematic diagram of the structure of a business basic data management device provided in some embodiments of this application; Figure 3 This is a schematic diagram of the structure of an electronic device provided in some embodiments of this application. Detailed Implementation

[0019] Traditional real estate development companies face the following problems in managing their basic business data: 1. Disorganized data architecture: Basic business data lacks a clear hierarchical relationship, is scattered across different media, has an extremely low data reuse rate, and requires repeated entry of similar data; 2. Disorganized storage management: Data such as components, modules, and project instances are not stored in a categorized manner, resulting in low efficiency in searching and retrieving data. Furthermore, the lack of standardized data makes it prone to attribute discrepancies.

[0020] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0021] See Figure 1 The flowchart of a business infrastructure data management method provided in some embodiments of this application may include: S11: Construct a hierarchical system for basic business data; the hierarchical system for basic business data may include multiple levels.

[0022] In some embodiments of this application, a business basic data hierarchy system is constructed from the bottom to the top, which may include multiple levels.

[0023] For example, the constructed business foundation data hierarchy can include a component level, a subsystem level, a product platform level, and a product level. The component level consists of basic data units, representing the smallest, most fundamental, and indivisible basic functional units in real estate development. These are the "atoms" that constitute higher-level business data. For example, they can correspond to 25% of the business foundation data; for instance, steel bars, cement, bricks, faucets, and insulated glass all belong to the component level. The component level is formed by the aggregation of components. It consists of multiple components integrated according to specific design logic and functions, forming intermediate products with independent functions. Examples include: integrated kitchen cabinets (including boards, hinges, handles, etc.), integrated bathrooms (integrating sanitary ware, tiles, waterproofing, pipes, etc.), standardized window units (including window frames, glass, and hardware), complete electrical distribution boxes (including circuit breakers, terminals, instruments, etc.), and fresh air system fan box modules all belong to the component level. Subsystems are formed by the aggregation of components. For example, corresponding to 50% of the hierarchical data, a subsystem is a functional collection composed of multiple components and elements to achieve a complete system function. It is the next higher level of integration of components. Examples include: integrated external wall insulation and decoration system (including insulation board, decorative panel, anchors and other components), roof waterproofing and drainage system, central air conditioning system (including compressor, fan coil unit, air duct and other components), intelligent security system (including camera, access control, alarm host and other components), community garbage classification and treatment system, charging pile power supply system, smart home system, and fire sprinkler system. The product platform level is formed by the integration of subsystems. For example, corresponding to 75% of the platform data, the product platform level is the highest level. It refers to a shared architecture, technical system, standard module library and design rules that can support the development of multiple final products (buildings / projects). Based on this platform, multiple different specific real estate projects (products) can be efficiently developed. For example, Longfor's "R&D platform" covers a complete set of design guidelines, cost limits and supplier libraries for different product types such as "high-rise residential", "villa", and "commercial". The product level is the final business carrier formed by the product platform. The product level is a specific residential product or project series that can be sold to end customers. It is the final business carrier that is encapsulated by the product platform and personalized for specific market needs. The above business basic data level system can be adapted to two data organization modes: (1) Component mode: with components as the core, it aggregates upwards layer by layer to form component, subsystem, product platform and other level data; (2) Encapsulation mode: encapsulates downwards from the product platform to form standardized product-level data.

[0024] By constructing a hierarchical system of business basic data with multiple levels, the hierarchical relationship between business basic data can be clearly defined. The hierarchical architecture enables basic data such as components and parts to be reused across projects, reducing the workload of repeated data entry, lowering data management costs, and improving data reuse rate.

[0025] It should be noted that, in addition to constructing a hierarchical business data system encompassing the aforementioned multiple levels based on functional integration, it is also possible to construct such a system based on other dimensions. For example, the lifecycle levels of data can be divided based on the development process nodes of a real estate project, adapting to the full-stage management needs from the initial planning phase to operation and maintenance. In this case, the constructed hierarchical business data system could include a preliminary planning data layer, a design phase data layer, a procurement and construction data layer, and a delivery and operation and maintenance data layer. Alternatively, the professional attribute levels of data can be divided based on the professional field of real estate development, adapting to cross-professional collaborative management needs. In this case, the constructed hierarchical business data system could include a structural professional data layer, an electromechanical professional data layer, a decoration professional data layer, and a cost professional data layer, etc.

[0026] S12: Based on the levels included in the business basic data hierarchy, construct the corresponding dedicated data resource library.

[0027] Based on the established hierarchical system of basic business data, dedicated data resource libraries can be constructed according to the levels contained in the system. This allows for the storage of basic business data corresponding to each level into the respective dedicated data resource libraries. The dedicated data resource libraries enable the separate management of basic business data in real estate development, thereby achieving classified storage of basic business data, avoiding mixed storage management, improving the efficiency of searching and retrieving basic business data, significantly reducing the time cost of data searching and scheduling, and improving data management efficiency.

[0028] S13: Obtain the basic business data corresponding to the level and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

[0029] Based on the construction of a hierarchical system of basic business data and the corresponding dedicated data resource library, the basic business data corresponding to each level can be obtained and stored in the dedicated data resource library corresponding to that level. This enables the classification and management of basic business data by database, thereby clarifying the storage carrier of each type of data, achieving orderly and standardized storage management, reducing the time cost of searching and scheduling basic business data, improving the efficiency of searching and retrieving basic business data, and improving data management efficiency.

[0030] In addition, in some embodiments of this application, after receiving a data management instruction sent by a user, the user's role can be obtained, and it can be determined whether the user has the data management permission corresponding to the data management instruction based on the user's role. If so, the corresponding target business basic data can be managed according to the data management instruction (e.g., adding, deleting, modifying, viewing, etc. of the target business basic data). Otherwise, a prompt can be output that the user does not have the corresponding data management permission to perform the data management, so that the user can be informed of the feedback response in a timely manner and perform subsequent processing based on the prompt.

[0031] The technical solution disclosed in this application constructs a multi-level business basic data hierarchy. Based on the constructed business basic data hierarchy, a corresponding dedicated data resource library is built, and the acquired business basic data corresponding to each level is stored in the corresponding dedicated data resource library. Thus, this application establishes a hierarchical relationship between business basic data through a hierarchical architecture. This hierarchical architecture allows business basic data at different levels to be reused across projects, reducing repetitive data entry, lowering data management costs, and improving data reuse rate. Furthermore, by storing the business basic data corresponding to each level in the corresponding dedicated data resource library, it achieves categorized management of business basic data, clearly defining the storage carrier for each type of data, significantly reducing the time cost of data retrieval and improving data management efficiency.

[0032] This application provides a business basic data management method in some embodiments. The business basic data hierarchy may include a component level, a component level, a subsystem level, a product platform level, and a product level. Based on the hierarchical structure of the business foundation data, construct corresponding dedicated data resource libraries, which may include: Build a component library corresponding to the component level, a module library corresponding to the component level, subsystem level and product platform level, and an instance library corresponding to the product level.

[0033] In some embodiments of this application, a business foundation data hierarchy can be constructed according to the degree of functional integration. This hierarchy, from bottom to top, can sequentially include a component level, a subsystem level, a product platform level, and a product level. Components are basic data units; components are formed by the aggregation of components; subsystems are formed by the aggregation of components; product platforms are formed by the integration of subsystems; and products are the final business carrier encapsulated by the product platform. For detailed descriptions of this part, please refer to the corresponding sections above; further elaboration is omitted here.

[0034] Based on the above, the corresponding dedicated data resource libraries can be constructed according to the hierarchical structure of the business foundation data. Specifically, this can be done by constructing a component library corresponding to the component level, a module library corresponding to the component level, subsystem level, and product platform level, and an instance library corresponding to the product level. That is, a corresponding component library can be constructed for basic functional units; for functional units formed by aggregation at the next lower level (since they are all encapsulated at lower levels), a corresponding module library can be constructed to store the corresponding business foundation data; and for products encapsulated by the product platform, a corresponding instance library can be constructed to store the corresponding project-level business data. Based on this, a one-to-one correspondence between the business foundation data corresponding to each level and the dedicated data resource library can be achieved. Specifically, data at the component level can be transferred to the component library for storage; data at the component, subsystem, and product platform levels can be transferred to the module library for storage; and product-level data can be transferred to the instance library for storage, forming the business data corresponding to the project instance.

[0035] Of course, a dedicated data resource library can also be built for each level. Specifically, a component library corresponding to the component level, a component library corresponding to the component level, a subsystem library corresponding to the subsystem level, a product platform library corresponding to the product platform level, and an instance library corresponding to the product level can be built. In this case, the business basic data corresponding to the level can be transferred one-to-one with the dedicated data resource library.

[0036] Compared to traditional methods that lack a full-link data flow mechanism from basic components to product instances, and where the same type of data cannot be transferred in a standardized manner across different projects, resulting in insufficient consistency of project business data, this application can achieve full-link data flow, storage, and standardized management from basic components to product instances through the above process. This ensures that the attributes and standards of the same type of basic business data are consistent across different projects, reduces project data deviation, guarantees data consistency, and improves data reuse rate and data management efficiency.

[0037] This application provides a business basic data management method in some embodiments, which obtains business basic data corresponding to a certain level and stores the business basic data corresponding to that level in a corresponding dedicated data resource library, and may include: Obtain the standard attribute definition and entry review information of the component. Based on the entry review information, determine the target component that has passed the review and store the standard attribute definition and entry review information of the target component in the component library.

[0038] In some embodiments of this application, the component library can be responsible for the standardized management of components, including defining standard component attributes, reviewing and storing components upon entry into the library, etc. Standardized management of components is a core element in ensuring uniform component specifications, controllable quality, and efficient circulation throughout the entire product standardization process.

[0039] Specifically, it can obtain the standard attribute definitions of components and their warehousing audit information. The standard attribute definitions refer to establishing unified, quantifiable, and verifiable attribute dimensions and indicators for each component. For example, the standard attribute definitions can include basic identity attributes (also known as basic identification attributes, such as component code, name / description, model, specifications, etc.), technical performance attributes (such as fire / water / corrosion resistance rating, sound insulation performance, material composition, dimensional tolerances, etc.), cost accounting attributes (such as unit, unit price, supplier, procurement cycle, minimum purchase quantity, etc.), quality acceptance attributes (such as implementation standards, test report requirements, pass / fail criteria, etc.), and application adaptation attributes (such as subsystem, applicable scenarios, associated drawings / technical parameter files, etc.). The warehousing audit information is the audit information obtained before the component is put into storage, verifying its quality, quantity, and compliance. For example, it can be used to check whether the physical item meets the standards by comparing it with the standard attributes, generating corresponding warehousing audit information. This audit information can also include the auditing department, audit dimensions (also known as audit indicators, audit scope), and audit opinions.

[0040] Based on the above, the target components that have passed the review can be identified according to the entry review information. The standard attribute definitions of the target components and the entry review information are stored in the component library to achieve standardized management of components. This facilitates the reuse of component data across projects, improves data reuse rate, and ensures that the attributes and standards of the same type of component data are consistent across different projects, thereby reducing project data deviation.

[0041] This application provides a business basic data management method in some embodiments, which obtains business basic data corresponding to a certain level and stores the business basic data corresponding to that level in a corresponding dedicated data resource library, and may include: Obtain the standard attributes of each component, subsystem, and product platform, as well as the encapsulation and library information of each component, subsystem, and product platform, and the encapsulation process management information of each component, subsystem, and product platform. The standard attributes, packaging and warehousing information, and packaging process management information of each component, subsystem, and product platform are stored in the module library.

[0042] In some embodiments of this application, the module library can be responsible for the management of component, subsystem and product platform data, specifically covering standard attribute implantation (associating unified standards with modules), product encapsulation and storage (encapsulating and storing product platform and other data), and encapsulation process management (managing and controlling all nodes of the encapsulation process).

[0043] Specifically, it can acquire the standard attributes of each component, subsystem, and product platform, as well as their encapsulation and warehousing information, and their encapsulation process management information. The standard attributes of components, subsystems, and product platforms can be used to clarify the attributes carried by each module (e.g., product series, applicable floor area ratio, cost indicators, technical parameters, related regulatory clauses, BIM (Building Information Modeling) model files, renderings, supplier information, etc.), and associate each module with relevant attributes and standards, giving each module a clear standard attribute label. The encapsulation and warehousing information of components, subsystems, and product platforms can be used to determine the encapsulation structure of each module (e.g., basic information, hierarchical structure data, etc.). The encapsulation process management information of components, subsystems, and product platforms can include the nodes, responsible persons, acceptance criteria, and time requirements of the encapsulation process. This allows for process control over the product encapsulation process of the module library, ensuring compliance and consistency in results.

[0044] Based on the above, the standard attributes, encapsulation information, and encapsulation process management information of each component, subsystem, and product platform can be transferred to the module library to store this information. This enables standardized management of components, subsystems, and product platforms, facilitates cross-project data reuse, improves data reuse rate, and ensures that the attributes and standards of the same type of module data are consistent across different projects, reducing project data deviation. Furthermore, the encapsulation process control through the module library can improve the compliance and efficiency of product-level data encapsulation, avoid disorder in the encapsulation process, and achieve a standardized data encapsulation process.

[0045] This application provides a business basic data management method in some embodiments, which obtains business basic data corresponding to a certain level and stores the business basic data corresponding to that level in a corresponding dedicated data resource library, and may include: Acquire project-level business data; project-level business data may include project instance models and project business data. Store project-level business data in the instance library.

[0046] In some embodiments of this application, the instance library can be used to store project-level business data. Specifically, project-level business data can be acquired, which may include project instance models (project implementation models corresponding to the product) and project business data (business information actually executed by the project). The acquired project-level business data is then stored in the instance library, thereby utilizing a dedicated instance library to store project-level business data, reducing the time cost of searching and scheduling project-level business data, improving the efficiency of searching and retrieving project-level business data, and ultimately enhancing data management efficiency.

[0047] A business infrastructure data management method provided in some embodiments of this application may further include: Obtain the updated business basic data corresponding to the level, and update the business basic data stored in the corresponding dedicated data resource library based on the updated business basic data.

[0048] In some embodiments of this application, the updated business basic data corresponding to the level can be obtained in real time or periodically, and the business basic data stored in the corresponding dedicated data resource library can be updated according to the updated business basic data, so as to improve the reliability, effectiveness and accuracy of the business basic data stored in the dedicated data resource library, thereby improving the accuracy of data management.

[0049] A business infrastructure data management method provided in some embodiments of this application may further include: The basic business data at all levels are managed using a unified standard.

[0050] In some embodiments of this application, business foundation data at each level can be managed using a unified standard, clearly defining the attribute specifications of components and modules. That is, a standardized system covering components, subsystems, and product platforms can be established, clarifying the attribute specifications, association rules, and control requirements of data at each level. This achieves data unification, traceability, and reusability, eliminating data silos (i.e., breaking down data ambiguities between design, procurement, construction, and cost departments, establishing a unified enterprise-level data language), enabling data interoperability and integration, supporting modular development (specifically, allowing data at each level to be quickly combined and adapted, improving the reusability efficiency of the product platform), and ensuring controllable quality and cost.

[0051] In some embodiments of this application, efficient management of basic business data can be achieved through multi-module collaboration: (1) Hierarchical data construction module, whose function is to construct a hierarchical data system of components → subsystems → product platforms → products, and adapt to component mode and encapsulation mode; components: hierarchical definition unit, mode adaptation unit. (2) Sub-database management module, whose function is to manage various types of data in component library, module library, and instance library; components: component library management unit (standard attribute management, inbound management), module library management unit (attribute implantation, encapsulation inbound, process management), instance library management unit (instance model storage, business data management). (3) Data flow module, whose function is to realize the flow and association of hierarchical data with corresponding resource libraries; components: hierarchical-library mapping unit, data flow execution unit. (4) Standardization and process control module, whose function is to unify data standards and control module encapsulation processes; components: standard attribute definition unit, encapsulation process control unit.

[0052] Some embodiments of this application also provide a business infrastructure data management device, see [link to relevant documentation]. Figure 2 This is a schematic diagram of the structure of a business basic data management device provided in some embodiments of this application, which may include: The first construction module 21 is used to construct the business basic data hierarchy system; the business basic data hierarchy system may include multiple levels. The second construction module 22 is used to construct a corresponding dedicated data resource library based on the levels included in the business basic data hierarchy system; The data storage module 23 is used to obtain the basic business data corresponding to the level and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

[0053] This application provides a business basic data management device in some embodiments, wherein the business basic data hierarchy may include a component level, a component level, a subsystem level, a product platform level, and a product level; The second building module 22 may include: The first construction submodule is used to build a component library corresponding to the component level, a module library corresponding to the component level, subsystem level and product platform level, and an instance library corresponding to the product level.

[0054] Some embodiments of this application provide a business basic data management device, wherein the data storage module 23 may include: The first data storage submodule is used to obtain the standard attribute definition and entry review information of the components, determine the target components that have passed the review based on the entry review information, and store the standard attribute definition and entry review information of the target components in the component library.

[0055] Some embodiments of this application provide a business basic data management device, wherein the data storage module 23 may include: The first acquisition submodule is used to acquire the standard attributes of each component, each subsystem and each product platform, acquire the encapsulation and library information of each component, each subsystem and each product platform, and acquire the encapsulation process management information of each component, each subsystem and each product platform. The second data storage submodule is used to store the standard attributes, packaging and storage information, and packaging process management information of each component, subsystem, and product platform into the module library.

[0056] Some embodiments of this application provide a business basic data management device, wherein the data storage module 23 may include: The second acquisition submodule is used to acquire project-level business data; project-level business data may include project instance models and project business data. The third data storage submodule is used to store project-level business data in the instance library.

[0057] A business infrastructure data management device provided in some embodiments of this application may further include: The update acquisition module is used to acquire the updated business basic data corresponding to the level, and update the business basic data stored in the corresponding dedicated data resource library based on the updated business basic data.

[0058] A business infrastructure data management device provided in some embodiments of this application may further include: The management module is used to manage basic business data at all levels using a unified standard.

[0059] Some embodiments of this application also provide an electronic device, see [link to relevant documentation] Figure 3 This is a schematic diagram of the structure of an electronic device provided in some embodiments of this application, which may include: Memory 31 is used to store computer programs; When the processor 32 executes the computer program stored in the memory 31, it can implement the steps of any of the above-described business basic data management methods.

[0060] Some embodiments of this application also provide a readable storage medium storing a computer program, which, when executed by a processor, can implement the steps of any of the above-described business basic data management methods.

[0061] For a description of the relevant parts of the business basic data management device, electronic device and readable storage medium provided in the embodiments of this application, please refer to the detailed description of the corresponding parts of the business basic data management method provided in the embodiments of this application, and will not be repeated here.

[0062] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0063] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0064] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0065] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0066] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0067] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for managing basic business data, characterized in that, include: Build a hierarchical system for basic business data; The business basic data hierarchy includes multiple levels; Based on the levels included in the aforementioned business basic data hierarchy, construct corresponding dedicated data resource libraries; Obtain the basic business data corresponding to the level, and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

2. The business basic data management method according to claim 1, characterized in that, The business foundation data hierarchy includes component level, component level, subsystem level, product platform level, and product level. Based on the hierarchical structure of the business foundation data, a corresponding dedicated data resource library is constructed, including: Construct a component library corresponding to the component level, construct a module library corresponding to the component level, the subsystem level, and the product platform level, and construct an instance library corresponding to the product level.

3. The business basic data management method according to claim 2, characterized in that, Obtaining the basic business data corresponding to the level, and storing the basic business data corresponding to the level into the corresponding dedicated data resource library, including: Obtain the standard attribute definition and entry review information of the component, determine the target component that has passed the review based on the entry review information, and store the standard attribute definition and entry review information of the target component in the component library.

4. The business basic data management method according to claim 2, characterized in that, Obtaining the basic business data corresponding to the level, and storing the basic business data corresponding to the level into the corresponding dedicated data resource library, including: Obtain the standard attributes of each component, subsystem, and product platform, and obtain the encapsulation and warehousing information of each component, subsystem, and product platform, as well as the encapsulation process management information of each component, subsystem, and product platform; The standard attributes, packaging and warehousing information, and packaging process management information of each component, subsystem, and product platform are stored in the module library.

5. The business basic data management method according to claim 2, characterized in that, Obtaining the basic business data corresponding to the level, and storing the basic business data corresponding to the level into the corresponding dedicated data resource library, including: Acquire project-level business data; the project-level business data includes project instance models and project business data. The project-level business data is stored in the instance library.

6. The business basic data management method according to any one of claims 1 to 5, characterized in that, Also includes: Obtain the updated business basic data corresponding to the level, and update the business basic data stored in the corresponding dedicated data resource library based on the updated business basic data.

7. The business basic data management method according to claim 6, characterized in that, Also includes: The basic business data of each level shall be managed using a unified standard.

8. A business basic data management device, characterized in that, include: The first construction module is used to build the business basic data hierarchy system; The business basic data hierarchy includes multiple levels; The second construction module is used to construct a corresponding dedicated data resource library based on the levels included in the business basic data hierarchy system. The data storage module is used to acquire the basic business data corresponding to the level and store the basic business data corresponding to the level into the corresponding dedicated data resource library.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the business infrastructure data management method as described in any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the business basic data management method as described in any one of claims 1 to 7.

Images