Demand and capacity management system and procedures

Abstract

Demand and capacity management system (1), configured as a web-based data service (200) in an automotive network for communication between supplier and customer, comprising: - at least one data management system (2) configured as a cloud-based or central server, - at least one customer device (3) comprising an associated demand and capacity management application (3.3), - at least one supplier device (4) comprising an associated demand and capacity management application (4.3), - at least one first data room connector (3.1) which can be detachably connected or linked to the customer device (3) as a communication interface, - at least one second data room connector (4.1) that can be detachably connected to or is connected to the supplier device (4) as a communication interface, wherein the first data room connector (3.1) is configured to communicate with the data management system (2) via an associated connection and with the supplier device (4) directly via communication channels (6.1, 6.2), and the second data room connector (4.1) is configured to communicate with the data management system (2) via an associated connection and with the customer device (3) directly via the communication channels (6.1, 6.2), wherein the web-based data service (200) is configured to: a) Entering a coupling of at least one of the data room connectors (3.1, 4.1) and receiving a data room connector identifier or network identifier (108) and writing the data room connector identifier or network identifier (108) to the data management system (2), b) Creating a data space connector asset (112) for expected data on this coupled data space connector (3.1, 4.1), c) Receiving an initial request (101) of the expected data directly via the communication channels (6.1, 6.2) between the data space connectors (3.1, 4.1), d) Comparing the expected data with relevant internal data, e) based on the matching results, creating a second requirement, f) optionally retrieve from the data management system (2) a network identifier (108) of the receiving data room connector (3.1, 4.1), g) Transmitting the second request (103) and the associated network identifier (108) of the receiving data space connector (3.1, 4.1) to the coupled data space connector (4.1, 3.1) directly via the communication channels (6.1, 6.2) between the data space connectors (3.1, 4.1), h) Establishing one of the communication channels (6.1, 6.2) between the coupled data space connector (3.1, 4.1) and the receiving data space connector (3.1, 4.1) and i) Sending the second request (103) to the receiving data room connector (3.1, 4.1).

Description

[0001] The present invention relates to a demand and capacity management system and method. STATE OF THE ART

[0002] Exchange data management systems are well-known, for example, from DE 10 2015 120 093 A1, DE 102 30 895 A1 and DE 10 2016 103 771 A1. With the increasing complexity of supply chains and a rising number of global and local crises, small and medium-sized enterprises (SMEs) as well as large corporations are exposed to an increased risk of disruptions in their supply chains, which often lead to bottlenecks and ultimately to production stoppages.

[0003] DE 102 46 302 A1 discloses a central unit and a method for the electronic generation and management of supplier data, wherein decentralized supplier terminals access the central unit. SUMMARY OF THE REVELATION

[0004] One of the purposes of this disclosure is to provide a demand and capacity management system. Furthermore, one of the purposes of this disclosure is to provide a demand and capacity management procedure.

[0005] According to the demand and capacity management system, the task is fulfilled by the features claimed in claim 1. According to the demand and capacity management method, the task is fulfilled by the features claimed in claim 9.

[0006] According to the disclosure, a (particularly computer-implemented) demand and capacity management system (especially for linking a customer demand request with the available supplier capacity) is provided, wherein the system is configured as a web-based data service, e.g., an automotive network. The computer-implemented demand and capacity management system (referred to as DCM system) may have at least one cloud-based server processing structure. The system may include at least the following: - at least one data management system (e.g., an automotive data management system, a federated operating system or environment, an OEM operating system or environment, or a cloud-based server) that can be configured as a cloud-based server or as a central server with internal data and / or information, e.g., a central address database of the system, - at least one customer device, comprising an associated demand and capacity management application (also called customer demand and capacity management application, or DCM app or customer DCM app for short), - at least one supplier device comprising an associated demand and capacity management application (also called supplier demand and capacity management application, or DCM app or supplier DCM app for short), - at least one initial data space connector that can be connected to the customer device as a communication interface, e.g. an Eclipse data space connector (called EDC or EDC endpoint or customer EDC for short), - at least one second data room connector that can be connected to the supplier device as a communication interface (called EDC or EDC endpoint or supplier EDC for short), wherein the first data room connector is configured to communicate with both the data management system and the supplier device, and wherein the second data room connector is configured to communicate with both the data management system and the customer device, the web-based data service can be configured to: a) Entering a coupling of at least one of the data room connectors and receiving a data room connector identifier (also called ID or account or EDC endpoint address) and writing the data room connector identifier to the data management system, b) Creating a data space connector asset for expected data on this coupled data space connector, c) Receiving an initial request for the expected data (also called a data request), in particular a POST request, e.g. an HTTP-based request or a WWW-based request, e.g. from a coupled data room connector, d) Matching the expected data with the associated internal data (e.g., on the coupled customer device), e) based on the matching results, in particular identifying a receiving data room connector, creating a second request (also called a communication request), f) optionally retrieving from the data management system a network address (e.g. an IP address or similar) of the receiving data room connector, g) Transmitting the second request and the associated network address of the receiving data space connector to the coupled data space connector, h) Setting up or activating a communication channel between the coupled data room connector and the receiving data room connector, and i) Sending the second request to the receiving data space connector, in particular as a response to the first request.

[0007] According to another aspect, the web-based data service can be configured to: a) Entering a coupling of at least one of the data room connectors and receiving a data room connector identifier (also called ID or account or EDC endpoint address) and writing the data room connector identifier to the data management system, b) Creating a data space connector asset for expected data on this coupled data space connector, c) Creating an initial request for the expected data (also called a data request), in particular a POST request, e.g. an HTTP-based request or a WWW-based request, e.g. from a coupled data room connector, d) Retrieving from the data management system a network address (e.g. an IP address or similar) of the receiving data room connector, e) Transmitting the first request and the associated network address of the receiving data space connector to the coupled data space connector, f) Setting up or activating a communication channel between the coupled data room connector and the receiving data room connector, and g) Sending the first request to the receiving data room connector.

[0008] According to another aspect, the web-based data service can be configured to: a) Receiving an initial request for expected data (also called a data request), in particular a POST request, e.g. an HTTP-based request or a WWW-based request, e.g. from a coupled data space connector, b) Matching the expected data with the associated internal data (e.g., on the coupled customer device), c) based on the matching results, in particular identifying a receiving data room connector, creating a second request (also called a communication request), d) optionally retrieving from the data management system a network address (e.g. an IP address or similar) of the receiving data room connector, e) Transmitting the second request and the associated network address of the receiving data space connector to the coupled data space connector, f) Setting up or activating a communication channel between the coupled data room connector and the receiving data room connector, and g) Sending the second request to the receiving data room connector.

[0009] According to another aspect, the web-based data service can be configured to: either a) Entering a coupling of at least one of the data room connectors and receiving a data room connector identifier (also called ID or account or EDC endpoint address) and writing the data room connector identifier to the data management system, b) Creating a data space connector asset for expected data on this coupled data space connector, c) Creating an initial request for the expected data (also called a data request), in particular a POST request, e.g. an HTTP-based request or a WWW-based request, e.g. from a coupled data room connector, d) Retrieving from the data management system a network address (e.g. an IP address or similar) of the receiving data room connector, e) Transmitting the first request and the associated network address of the receiving data space connector to the coupled data space connector, f) Setting up or activating a communication channel between the coupled data room connector and the receiving data room connector, and g) Sending the first request to the receiving data room connector. or a) Receiving an initial request for expected data (also called a data request), in particular a POST request, e.g. an HTTP-based request or a WWW-based request, e.g. from a coupled data space connector, b) Matching the expected data with the associated internal data (e.g., on the coupled customer device), c) based on the matching results, in particular identifying a receiving data room connector, creating a second request (also called a communication request), d) optionally retrieving from the data management system a network address (e.g. an IP address or similar) of the receiving data room connector, e) Transmitting the second request and the associated network address of the receiving data space connector to the coupled data space connector, f) Setting up or activating a communication channel between the coupled data room connector and the receiving data room connector, and g) Sending the second request to the receiving data room connector.

[0010] The web-based data service comprises a method, a device, and computer instructions within a data processing system for enabling direct data interactions between customer and supplier, rather than via a central server. Specifically, the data processing system is currently a demand and capacity management system. Within this system, customers and suppliers are directly connected through their linked data space connectors and communication channels using simple coupling requests—that is, the first request and / or the second request. A request can be sent from the customer to the supplier, and the supplier can then send their capacity back to the customer.

[0011] The invention enables various parties, such as companies, customers, and suppliers, to exchange data in a sovereign manner and to utilize a shared understanding of processes. Furthermore, the invention ensures interoperability and enables the parties involved to identify potential bottlenecks and overcapacities at an early stage, to better monitor and control resources and facilities, to facilitate collaboration and decision-making between suppliers and customers to resolve bottlenecks or overcapacities, to automate processes, and / or to improve efficiency and accuracy. The system also enables a smooth data flow between applications with different interfaces and an efficient comparison of the data originating from these applications.

[0012] The system and method according to the invention define common demand and capacity management applications for each party, e.g., suppliers, customers, companies, and a common web-based data service method (also referred to as web-based data service or web-based method) and the interpretation of the data among all participants in an automotive network, e.g., in the so-called Catena-X network. This enables data exchange between all parties, e.g., customers, suppliers, companies, whereby the standard is implemented without the need for individual definitions. This enables fully automated data exchange across all parties. No central database is required. The common demand and capacity management applications for each party define how the data is exchanged between the various parties, e.g., suppliers, customers, companies, and the various applications.

[0013] The web-based data service includes, in particular, two data models: An initial data model can be configured as a requirements data structure model, specifically as a material requirements data structure model. This model is configured to determine, and in particular automatically determine, at least one material requirement associated with customer items and / or company items. The material requirements data structure model can include, for example, data and / or information on supplier(s), customer(s), customer material number(s), customer material description(s), unit(s), requirement series, requirement categories, customer location, and requirement time series.

[0014] A second data model can be configured as a capacity group data structure model. This model is configured to identify, and in particular to identify automatically, at least one capacity group associated with supplier items and / or company items. The capacity group data structure model can include, for example, data and / or information about the supplier(s), customer(s), capacity group ID(s), capacity group name(s), unit of measure, capacity line series, calendar week, actual capacity, maximum capacity, quantity, quality, associated demand series, customer material number(s), demand category, and customer location.

[0015] In another embodiment, at least two types of demand and capacity management applications are provided.

[0016] An initial demand and capacity management application is intended for communicating the demand from the customer to the supplier.

[0017] The customer device may include the following: the associated primary demand and capacity management application; at least one associated application programming interface (API demand) for at least one of the requirements, e.g., for all incoming requirements from other devices and / or for the requirements / demand to be communicated by the customer device to the supplier device. The requirements / demands communicated by the customer device to the supplier device may be referred to as "Week-Based Material Demand," "Month-Based Material Demand," or "Year-Based Material Demand," depending on the basis, e.g., weekly, monthly, annually.

[0018] A second demand and capacity management application is provided for communicating capacity from the supplier to the customer and / or from the customer to the supplier and / or between them.

[0019] Furthermore, the supplier equipment may include the following: the associated second demand and capacity management application; at least one associated application programming interface (API capacity) for at least one of the requirements, e.g., for all incoming requirements from other equipment and / or requirements / demands for the capacity to be communicated from the supplier equipment to the customer equipment. The requirements / demands communicated from the supplier equipment to the customer equipment may be referred to as "Week-Based Material Demand," "Month-Based Material Demand," or "Year-Based Material Demand," depending on the basis, e.g., weekly, monthly, annually.

[0020] According to a further embodiment, the customer device may include at least one associated comparison unit for comparing the expected data with associated internal data and / or an associated customer storage device for storing associated internal data.

[0021] The supplier device may also include at least one associated reconciliation unit for reconciling the expected data with associated internal data and / or a supplier reconciliation unit for storing associated internal data.

[0022] According to another embodiment, each of the at least two associated application programming interfaces (API requirements) is coupled to one of the associated data room connectors. For example, the application programming interface assigned to the supplier can be coupled to the supplier data room connector, and the application programming interface assigned to the customer can be coupled to the customer data room connector.

[0023] In particular, the associated demand and capacity management application can be configured to match the expected data with the associated internal data and to receive all data that is correctly addressed and / or addressed to the respective coupled data room connectors.

[0024] The computer-implemented demand and capacity management process, e.g., for linking customer demand with available supplier capacity, is configured as the web-based data service described above, e.g., in the automotive network described above (with at least one cloud-based server processing structure), of the computer-implemented demand and capacity management system described above, whereby the web-based data service can be configured as described above for: - Entering a coupling of at least one of a number of data room connectors and receiving the data room connector identifier and writing the data room connector identifier to the data management system of the demand and capacity management system, - Create the data space connector asset for expected data on this coupled data space connector, - Receiving the first request for the expected data, especially a POST request, e.g. from the coupled data space connector, - Comparing the expected data with relevant internal data, e.g. in the automotive data management system, - based on the matching results, identifying the receiving data room connector and / or creating the second request for a receiving data room connector, - optionally retrieve from the data management system a network address (e.g. IP address) of the receiving data room connector, - Transmitting the second request and the associated network address of the receiving data space connector to the coupled data space connector, - Setting up or activating a communication channel between the paired data room connector and the receiving data room connector, and - Sending the second request to the receiving data room connector.

[0025] Alternatively, the web-based data service can include the following steps: - Entering a coupling of at least one of a number of data room connectors as coupled data room connector(s) and receiving the data room connector identifier and writing the data room connector identifier to the data management system of the demand and capacity management system, - Creating the first request for the expected data, in particular a POST request, e.g. from the coupled data room connector, - Retrieving from the data management system a network address (e.g. IP address) of the receiving data room connector, - Transmitting the first request and the associated network address of the receiving data space connector to the coupled data space connector, - Setting up or activating a communication channel between the paired data room connector and the receiving data room connector, and - Sending the first request to the receiving data room connector.

[0026] In addition, the web-based data service may include the following steps: - Receiving the first request for expected data, especially a POST request, e.g. from the coupled data space connector, - Comparing the expected data with relevant internal data, e.g. in the automotive data management system, - based on the matching results, identifying the receiving data room connector and / or creating the second request for a receiving data room connector, Optionally, retrieve from the data management system a network address (e.g., IP address) of the receiving data room connector, - Transmitting the second request and the associated network address of the receiving data space connector to the coupled data space connector, - Setting up or activating a communication channel between the paired data room connector and the receiving data room connector, and - Sending the second request to the receiving data room connector.

[0027] The web-based data service can also be configured to determine the requested material requirement and / or capacity requirement based on the initial request received and to send the determined material requirement and / or capacity requirement to the coupled data room connector.

[0028] The web-based data service can also be configured to determine and output at least one service parameter, e.g., current service parameter, bottleneck status and / or surplus status, and / or future service parameter, e.g., status of cooperation between supplier and customer, based on the determined material requirements and / or the determined capacity requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The present disclosure will be better understood with reference to the detailed description below and the accompanying drawings, which are for illustrative purposes only and thus do not limit the present disclosure, wherein: Fig. 1 A block diagram of a computer-implemented demand and capacity management system shows, in particular for linking customer demand with available supplier capacity, Fig. 2 illustrates an exemplary process of a computer-implemented demand and capacity management procedure, in particular for linking customer demand with available supplier capacity, Fig. 3 illustrates an exemplary first data model configured as a material requirements data structure model, Fig. 4 illustrates an exemplary second data model configured as a capacity group data structure model, and Fig. 5 illustrates an exemplary process of an exchange and comparison procedure.

[0030] Corresponding parts are marked with the same reference symbols in all figures.

[0031] Fig. Figure 1 shows a block diagram of a demand and capacity management system 1, hereinafter referred to as DCM system 1. The DCM system 1 can be computer-implemented. The DCM system 1 can be configured, for example, to link a customer demand requirement 100 as the first requirement 101 or a demand with a requirement regarding available supplier capacity 102 as the second requirement.

[0032] The DCM system 1 can be configured as a web-based data service, e.g., an automotive network. The DCM system 1 can have at least one cloud-based server processing structure or network, in particular a standardized data flow and information access network, e.g., a Catena-X automotive network.

[0033] The DCM system 1 comprises at least one data management system 2 (also called business partner data management system, business partner data management discovery service system, or EDC discovery service system (EDC = Eclipse Database Connector)). Data management system 2 stores and enters the address data of all business partners into the DCM system 1.

[0034] The BPDM system 2 can be configured, for example, as an automotive data management system, a federated operating system or environment system, an OEM operating system or environment, or as a cloud-based server.

[0035] The BPDM system 2 can also be configured as a cloud-based server 5 with stored central data 104 and / or central information 105, e.g. a central address book of the DCM system 1 of all (especially registered) customers 3 and all (especially registered) suppliers 4 and their associated data room connectors 3.1, 4.1.

[0036] The BPDM system 2 is a central address book in which the network identifier 108 (also called ID or identifier or IP address) of all customers 3, all suppliers 4 and / or their associated data room connectors 3.1, 4.1, which are entered in the DCM system 1, is stored.

[0037] The BPDM system 2 can also be configured to support the registration of new customers 3, new suppliers 4, and / or their associated data room connectors 3.1 and 4.1. Furthermore, the BPDM system 2 can be configured to assign a unique identifier 109 (also called connector identifier or unique connector ID) to each associated data room connector 3.1 and 4.1.

[0038] For example, in order to participate in the standardized procedure of the DCM system 1, in particular to enable a smooth flow of data between the various customers 3 and / or suppliers 4 with different interfaces, all customers 3 and all suppliers 4 must register in the DCM system 1 with their associated central customer data 106 and / or central supplier data 107.

[0039] The DCM system 1 further comprises at least one customer device 3.2. The customer device 3.2 comprises at least one associated demand and capacity management application 3.3 and an associated storage device 3.4.

[0040] The demand and capacity management application 3.3 assigned to customer 3 is also referred to as Customer DCM App 3.3. Customer DCM App 3.3 stores and processes customer information 110 about customer demand requirements 100 (also called customer demand). Customer DCM App 3.3 is a specific customer demand and capacity management software for storing and processing this data.

[0041] The DCM system 1 further comprises at least one supplier device 4.2. The supplier device 4.2 comprises an associated demand and capacity management application 4.3 and an associated storage device 4.4.

[0042] The demand and capacity management application 4.3 assigned to supplier 4 is also referred to as Supplier DCM App 4.3. Supplier DCM App 4.3 stores and processes supplier information 111 about the supplier capacity requirement 101. Supplier DCM App 4.3 is a specific customer demand and capacity management software.

[0043] Customer 3 and supplier 4 may have different applications (software applications) for demand and capacity management, e.g., SAP, custom solutions, and therefore have completely different interfaces. Multiple customers and suppliers with their different applications can be present in DCM system 1.

[0044] The invention enables customers 3 and suppliers 4 to exchange data in a simple and direct manner and to utilize a common process and a smooth data flow between them, through the use of at least the two associated DCM apps 3.3, 4.3, i.e., one for each customer 3 and one for each supplier 4, of two associated data room connectors 3.1, 4.1, i.e., one for each customer 3 and one for each supplier 4, and of two data models, i.e., one for customer demand (hereinafter referred to as customer demand data structure model 3.5) and one for supplier capacity (hereinafter referred to as supplier capacity group data structure model 4.5), as described below: The data room connector 3.1 is connected and coupled to the customer DCM app 3.3, e.g. via a detachable connection, such as a plug connection, and serves as a communication interface, in particular as an Eclipse data room connector (called EDC or EDC endpoint or customer EDC for short) in the automotive network, e.g. in the Catena-X network.

[0045] The additional data room connector 4.1 is connected and coupled with the supplier DCM app 4.3, e.g. via a detachable connection, such as a plug connection, and serves as a communication interface, e.g. also an Eclipse data room connector.

[0046] Each DCM app, specifically each customer DCM app 3.3 and each supplier DCM app 4.3, has only one data room connector 3.1, 4.1. Each data room connector 3.1, 4.1 processes all incoming requests from other DCM apps, e.g., customer demand requests 100, initial requests 101 from customer DCM apps 3.3, and supplier capacity requests 102, secondary requests 103 from supplier DCM apps 4.3.

[0047] Data room connectors 3.1 and 4.1 are configured to send POST requests (100, 101, and 103). POST requests are a request method supported by HTTP and used by the World Wide Web. The POST request is configured so that the web-based server accepts the data contained in the request message. The POST request and the subsequent data exchange serve to transmit data between registered and linked components, such as supplier devices 3 and customer devices 4, which are registered in the BDPM system 2 and linked to the DCM system 2 via data room connectors 3.1 and 4.1.

[0048] Before sending requests 100, 101, and 103, an address exchange procedure, specifically an exchange procedure for unique identifiers, is provided in the web-based data service 200 of the DCM system 1 to determine which device, e.g., the supplier device 4 and / or the customer device 3, wishes to send data. For example, each data room connector 3.1 or 4.1 receives an IP address of the recipient's data room connector 4.1 or 3.1 from the paired supplier DC app 4.3 or customer DC app 3.3. The respective supplier DC app 4.3 or customer DC app 3.3 retrieves this IP address from the BPDM system 2.

[0049] Each of the data room connectors 3.1, 4.1 is configured to communicate with both the DCM system 1, in particular the BPDM system 2, and with other supplier devices 3 and other customer devices 4.

[0050] The web-based data service 200 of the DCM system 1 can be configured to: a) Entering a coupling of at least one of the data room connectors 3.1 and / or 4.1 into the corresponding device, e.g. the customer device 3.2 and / or the supplier device 4.2, and receiving a data room connector identifier (also called ID or account or EDC endpoint address), e.g. the network identifier 108 and / or the unique identifier 109, and writing this data room connector identifier to the BPDM system 2, b) Creating a data space connector asset 112 for expected data on this coupled data space connector 3.1 and / or 4.1, c) Receiving an initial request 101 of the expected data, in particular a POST request (also called a data request), e.g. a customer requirements request 100 or a supplier capacity request 102, from the coupled data room connector 3.1 and / or 4.1 in the respective device, e.g. the customer device 3.2 and / or the supplier device 4.2, d) Comparison of the expected data with associated internal data, in particular by means of an associated comparison unit 3.3.1 or 4.3.1 in the coupled device, e.g. in the coupled customer device 3.2 or the coupled supplier device 4.2, e) based on the matching results, in particular the identification of a receiving data room connector 3.1 or 4.1, the creation of a second requirement 103, in particular a communication setup requirement, f) Optionally, retrieve from DCM system 2 the network identifier 108 and / or the unique identifier 109 (e.g., a network address or an IP address or similar) of the receiving data space connector 3.1 or 4.1, g) Transmitting the second request 103 and the associated network address of the receiving data space connector, e.g. the network identifier 108 and / or the unique identifier 109, to the coupled data space connector 4.1 or 3.1, h) Setting up or activating a communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and i) Sending the second request 103 to the receiving data room connector 4.1 or 3.1, e.g. in response to the first request 101.

[0051] According to one alternative, the web-based data service 200 can be configured to: a) Entering a coupling of at least one of the data room connectors 3.1 and / or 4.1 into the corresponding device, e.g. the customer device 3.2 and / or the supplier device 4.2, and receiving a data room connector identifier (also called ID or account or EDC endpoint address), e.g. the network identifier 108 and / or the unique identifier 109, and writing this data room connector identifier to the BPDM system 2, b) Creating a data space connector asset 112 for expected data on this coupled data space connector 3.1 and / or 4.1, c) Creating an initial request 101 of the expected data, in particular a POST request (also called a data request), e.g. a customer requirements request 100 or a supplier capacity request 102, from the coupled data room connector 3.1 and / or 4.1 in the respective device, e.g. the customer device 3.2 and / or the supplier device 4.2, d) Retrieving from the DCM system 2 the network identifier 108 and / or the unique identifier 109 (e.g. a network address or an IP address or similar) of the receiving data space connector 3.1 or 4.1, e) Transmitting the first request 103 and the associated network address of the receiving data space connector, e.g. the network identifier 108 and / or the unique identifier 109, to the coupled data space connector 4.1 or 3.1, f) Setting up or activating a communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and g) Sending the first request 103 to the receiving data room connector 4.1 or 3.1.

[0052] According to a second alternative, the web-based data service 200 can be configured to: a) Receiving an initial request 101 of the expected data, in particular a POST request (also called a data request), e.g. a customer requirements request 100 or a supplier capacity request 102, from the coupled data room connector 3.1 and / or 4.1 in the respective device, e.g. the customer device 3.2 and / or the supplier device 4.2, b) Comparison of the expected data with associated internal data, in particular by means of an associated comparison unit 3.3.1 or 4.3.1 in the coupled device, e.g. in the coupled customer device 3.2 or the coupled supplier device 4.2, c) based on the matching results, in particular the identification of a receiving data room connector 3.1 or 4.1, the creation of a second requirement 103, in particular a communication setup requirement, d) optionally retrieve from the DCM system 2 the network identifier 108 and / or the unique identifier 109 (e.g. a network address or an IP address or similar) of the receiving data room connector 3.1 or 4.1, e) Transmitting the second request 103 and the associated network address of the receiving data space connector, e.g. the network identifier 108 and / or the unique identifier 109, to the coupled data space connector 4.1 or 3.1, f) Setting up or activating a communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and g) Sending the second request 103 to the receiving data room connector 4.1 or 3.1, e.g. in response to the first request 101.

[0053] According to a third alternative, the web-based data service 200 can be configured to: either a) Entering a coupling of at least one of the data room connectors 3.1 and / or 4.1 into the corresponding device, e.g. the customer device 3.2 and / or the supplier device 4.2, and receiving a data room connector identifier (also called ID or account or EDC endpoint address), e.g. the network identifier 108 and / or the unique identifier 109, and writing this data room connector identifier to the BPDM system 2, b) Creating a data space connector asset 112 for expected data on this coupled data space connector 3.1 and / or 4.1, c) Creating an initial request 101 of the expected data, in particular a POST request (also called a data request), e.g. a customer requirements request 100 or a supplier capacity request 102, from the coupled data room connector 3.1 and / or 4.1 in the respective device, e.g. the customer device 3.2 and / or the supplier device 4.2, d) Retrieving from the DCM system 2 the network identifier 108 and / or the unique identifier 109 (e.g. a network address or an IP address or similar) of the receiving data space connector 3.1 or 4.1, e) Transmitting the first request 103 and the associated network address of the receiving data space connector, e.g. the network identifier 108 and / or the unique identifier 109, to the coupled data space connector 4.1 or 3.1, f) Setting up or activating a communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and g) Sending the first request 103 to the receiving data room connector 4.1 or 3.1. or a) Receiving an initial request 101 of the expected data, in particular a POST request (also called a data request), e.g. a customer requirements request 100 or a supplier capacity request 102, from the coupled data room connector 3.1 and / or 4.1 in the respective device, e.g. the customer device 3.2 and / or the supplier device 4.2, b) Comparison of the expected data with associated internal data, in particular by means of an associated comparison unit 3.3.1 or 4.3.1 in the coupled device, e.g. in the coupled customer device 3.2 or the coupled supplier device 4.2, c) based on the matching results, in particular the identification of a receiving data room connector 3.1 or 4.1, the creation of a second requirement 103, in particular a communication setup requirement, d) optionally retrieve from the DCM system 2 the network identifier 108 and / or the unique identifier 109 (e.g. a network address or an IP address or similar) of the receiving data room connector 3.1 or 4.1, e) Transmitting the second request 103 and the associated network address of the receiving data space connector, e.g. the network identifier 108 and / or the unique identifier 109, to the coupled data space connector 4.1 or 3.1, f) Setting up or activating a communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and g) Sending the second request 103 to the receiving data room connector 4.1 or 3.1, e.g. in response to the first request 101.

[0054] The described web-based data service 200, in particular the web-based demand and capacity service, is provided to a large number of customers 3 and suppliers 4 in the DCM system 1. Data exchange, especially the exchange of demand and capacity data between customers 3 and suppliers 4, takes place decentrally. Specifically, each DCM app, e.g., customer DCM app 3.3 and supplier DCM app 4.3, with its matching units 3.3.1 and 4.3.1, operates and stores the data, e.g., demand data and capacity data, locally and in direct exchange via the direct communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1. There is no central communication or platform that stores or processes the data, demand data and / or capacity data, originating from the DCM apps. B. Customer DCM app 3.3 and supplier DCM app 4.3.

[0055] The BPDM system 2 is used exclusively for direct data exchange between two DCM apps, e.g., between one of the customer DCM apps 3.3 and one of the supplier DCM apps 4.3 via their associated data room connectors 3.1 and 4.1.

[0056] The customer DCM app 3.3 is used to transmit demand, in particular customer demand request 100, e.g., a "Week-Based Material Demand," a "Day-Based Material Demand," a "Month-Based Material Demand," or similar, from customer 3 to supplier 4. The supplier DCM app 4.3 is used to communicate capacity, in particular supplier capacity request 102, e.g., a "Week-Based Capacity Group," a "Day-Based Capacity Group," or a "Month-Based Capacity Group," from supplier 4 back to customer 3.

[0057] To support the exchange of data such as customer demand requirement 100, e.g., "Week-Based Material Demand" data, or supplier capacity requirement 102, e.g., "Week-Based Capacity Group" data, the respective DCM application—that is, the customer DCM app 3.3 or the supplier DCM app 4.3—must define a single endpoint that supports the first requirement 100, a POST request, e.g., via an HTTP or WWW-based POST request procedure. The structure of the endpoint is arbitrary. The address of the respective DCM app, e.g., the customer DCM app 3.3 or the supplier DCM app 4.3, should be provided as part of the associated data room connector asset 112 (also called the EDC data asset). The respective data room connector asset 112 defines the directory into which the received data is stored by the respective receiving DCM app, e.g., the receiving customer DCM app 3.3 or Supplier DCM App 4.3, will be written.

[0058] The data room connectors 3.1 and 4.1 can include multiple asset sets used for different applications, one of which is used for the described DCM apps, the customer DCM app 3.3 and the supplier DCM app 4.3.

[0059] In another embodiment, the first requirement 101, which is provided as a POST request, e.g., an HTTP-based POST request, may not be directly called by a partner, e.g., a supplier 4 (also called a supply chain partner). Preferably, the first requirement 101 is provided via the communication channels 6.1, 6.2, and thus via EDC communication, a so-called Eclipse data communication. To enable such EDC communication, each data room connector 3.1, 4.1 includes the corresponding data room connector assets 112 (also called EDC data assets).

[0060] The data room connector assets 112 are used, for example, to identify the asset when searching in the asset catalog of a supplier 4. Since the data room connector assets 112 reflect the contractual relationship between supplier 4 and its customers 3, only one asset with the property "asset:prop:dcm" with the value "weekbasedmaterialdemand-endpoint" ("weekly material demand endpoint") is visible to customer 3 at any given time, in order to avoid ambiguities.

[0061] The following is an example of a data room connector asset 112 with corresponding access and usage policies and contract definition in a first table 1 (where expressions in double curly brackets {{}} must be replaced by a corresponding value):

[0062] / / Definition of access and usage guidelines

[0063] / / Contract definition

[0064] Data exchange via communication channels 6.1 and 6.2 can be provided in a standard format, such as a JSON string or JavaScript Object Notation (JO) file. The JSON string can be generated from the respective data space connector asset 112. Specifically, data space connector asset 112 can include an RDF turtle that uses standardized tooling, such as the well-known Eclipse ESMF tooling. Data space connector asset 112 can be specified to use a pure asset management shell payload.

[0065] For example, the data to be exchanged, in particular the "Week-Based Material Demand" and the "Week-Based Capacity Group," can be generated as JSON strings that are sent via communication channels 6.1 and 6.2, e.g., an EDC communication channel. The respective JSON string is standardized and contains both the "Week-Based Material Demand" and the "Week-Based Capacity Group."

[0066] In another embodiment, multiple customer requirement requests 100 or multiple supplier capacity requests 102, e.g., multiple "Week-Based Material Demand" strings, can be sent in a single transmission as a JSON list. If only one customer requirement request 100, e.g., a "Week-Based Material Demand" string, is transmitted, it is sent as a list with one entry or string.

[0067] If customer requirement 100 changes for any week, the entire data set should be sent to supplier 4. Transmitting only the changes, e.g., delta / incremental updates, is not currently implemented but can be. Such an exchange of the entire data set prevents inconsistent or incomplete records. A data transfer must include at least one "Week-Based Material Demand" record.

[0068] Fig. Figure 2 shows an exemplary process of a computer-implemented demand and capacity management procedure, in particular for linking customer demand with available supplier capacity through the web-based data service 200 of the DCM system 1.

[0069] The web-based data service 200 of the DCM system 1 can include at least the following steps: 201. Entering a connection of at least one of the data room connectors 3.1 and / or 4.1 and receiving the data room connector identifier, e.g. network identifier 108 and / or unique identifier 109, and writing this data room connector identifier to the BPDM system 2, 202. Create the data space connector asset 112 for expected data on this coupled data space connector 3.1 and / or 4.1, 203. Receiving the first request 101 of the expected data, in particular a POST request, via the coupled data room connector 3.1 and / or 4.1 from the respective customer DCM app 3.3 and / or the supplier DCM app 4.3, 204. Comparing the expected data with related internal data, 205. Based on the comparison results, create a second requirement 103, in particular a communication setup requirement, 206. Optionally, retrieve from DCM system 2 the network address, e.g., the network identifier 108 and / or the unique identifier 109 (IP address), of the receiving data room connector 3.1 or 4.1, 207. Transmitting the second request 103 and the associated network address of the receiving data room connector 3.1 or 4.1 to the coupled data room connector 4.1 or 3.1, 208. Setting up or activating the communication channel 6.1 or 6.2 between the coupled data room connector 3.1 or 4.1 and the receiving data room connector 4.1 or 3.1, and 209. Sending the second request 103 to the receiving data room connector 4.1 or 3.1.

[0070] The number and order of the steps can vary, e.g. in accordance with the described alternatives one to three.

[0071] Fig. Figure 3 shows an exemplary first data model configured as a material requirements data structure model 3.5.

[0072] The material requirements data structure model 3.5 can be configured to determine, and in particular automatically determine, at least one material requirement 7 associated with customer items and / or company items. The material requirements data structure model 3.5 can, for example, include data and / or information on supplier(s) 3, customer(s) 4, customer material number(s) 8, customer material description(s) 9, unit(s) of measure 10, requirement series 11, requirement categories 12, customer location 13, requirement time series 14, and others.

[0073] Table 2 shows an example of a “WeekBasedMaterialDemand” data model, which was generated as a JSON string as described above.

[0074] Fig. Figure 4 shows an exemplary second data model configured as a capacity group data structure model 4.5.

[0075] The capacity group data structure model 4.5 is configured to identify, and in particular to identify automatically, at least one capacity group 15 associated with supplier items and / or company items. The capacity group data structure model 4.5 can, for example, include data and / or information on supplier(s) 3, customer(s) 4, capacity group identifier(s) 16, capacity group name(s) 17, unit of measure 18, capacity line series 19, calendar week 20, actual capacity 21, maximum capacity 22, quantity 23, quality 24, associated demand series 25, customer material number(s) 26, demand category 27, and customer location 28.

[0076] Table 3 shows an example of a “WeekBasedCapacity” data model, which was generated as a JSON string as described above.

[0077] Fig.Figure 5 shows an exemplary process of an exchange and reconciliation procedure 210 and 211, which is provided by the respective DCM apps, e.g. the customer DCM app 3.3 for customer 3 or the supplier DCM app 4.3 for supplier 4.

[0078] Each exchange and reconciliation procedure 210 and 211 performed by the respective customer DCM app 3.3 and supplier DCM app 4.3 is carried out for all incoming data, e.g., incoming requirements / demands, such as a customer demand request 100 and / or a supplier capacity request 102, received by and addressed to the respective customer DCM app 3.3 and supplier DCM app 4.3. One of the DCM apps 3.3 or 4.3 does not perform the exchange and reconciliation procedure 210 and 211 for other DCM apps 3.3 or 4.3.

[0079] Each exchange and matching procedure 210 and 211 is designed to identify bottlenecks and surpluses in the DCM system 1.

[0080] Each exchange and matching procedure 210 and 211 can be subdivided into sub-procedures, in particular into an input 210.1 and / or 211.1, a demand exchange sub-procedure 210.2 and / or 211.2, a matching and comparison sub-procedure 210.3 and / or 211.3, a sub-procedure for resolving bottlenecks and surpluses 210.4 and / or 211.4, a loop 210.5 and / or 211.5, and an output 210.6 and / or 216.6.

[0081] Each exchange and matching procedure 210 and 211 is performed in response to each customer demand request 100 (also referred to as demand) or supplier capacity request 102 (also referred to as capacity), each provided as a POST request and submitted via input 210.1 or 211.1, respectively. The POST request can be repeated as often as necessary when new POST requests are received to process the demand and capacity requests.

[0082] Furthermore, the POST requirements, e.g. customer demand requirements 100, supplier capacity requirements 102, can be exchanged between the DCM apps 3.3, 4.3 through the demand exchange sub-procedures 210.2, 211.2 (see dashed lines).

[0083] In the reconciliation and comparison sub-process 210.3 or 211.3, the data from supplier capacity request 102, e.g., "Week-Based Capacity Group" demand / requirement, and the data from customer demand request 100, e.g., "Week-Based Material Demand" demand / requirement, are reconciled and compared. Specifically, the reconciliation and comparison sub-process 210.3 or 211.3 determines which entities / partners, e.g., Customer 3 / Supplier 4, need to be compared by identifying and using a linked Material Demand attribute in the capacity group data of supplier capacity request 102.

[0084] “Multiple-Week Capacity Groups” can refer to the same “Week-Based Material Demand.” All “Week-Based Capacity Groups” can contain one or more “Week-Based Material Demand” entities. During the reconciliation and comparison sub-process 210.3 or 211.3, all registered and linked partners, such as Suppliers 4 and Customers 3, can be evaluated and compared. The comparison can be performed on a weekly basis. Subsequently, the bottleneck and surplus resolution sub-process 210.4 and / or 211.4 is configured to identify a bottleneck or surplus that might occur in the near future, for example, to pinpoint a specific week in which a bottleneck or surplus might occur.

[0085] If a bottleneck or surplus is identified, a message, information, signal or other can be generated and sent via output 210.6 and / or 211.6 to the supplier 4, the customer 3 and / or a central server, e.g. at the OEMs, and / or to the BPDM system 2.

[0086] This approach allows Supplier 3 to present its production bottlenecks in detail and with a high degree of flexibility. In this way, the parties involved gain an overview of potential bottlenecks, e.g., for the next 18-24 months, which increases the ability to react promptly and resolve problems before they impact production.

[0087] Based on the results of the exchange and reconciliation procedures 210 and 211, the respective DCM app 3.3, 4.3 is configured to decide how to handle the situation. This can be done by adjusting (and thus triggering a new POST request) the demand at customer 3 (customer demand request 100) or the capacity at supplier 4 (supplier capacity request). In many cases, supplier 4 and customer 3 will agree on a joint approach to manage the situation.

[0088] Each POST request (at least the first request 101) can be further signed with a universally unique identifier 109 and a specific network identifier 108 for each customer 3 and / or each supplier 4, e.g., a customer ID and / or a supplier ID. The universally unique identifier 109 can be generated according to a standard rule, e.g., the standard RFC 4122 (Request for Comments, RFC). For technical reasons, the unique identifier 109 must be treated as unique. To reduce the probability of collisions and eliminate certain attack vectors, it must be treated as unique within the supplier-customer relationship; therefore, an additional customer or supplier ID may also be included in the signature.

[0089] The unique identifier 109 is not required for the matching process. It is needed, for example, to update material requirements and capacity groups. When a data record needs to be updated, the object is resent with the same unique identifier 109, but with different content. This informs the receiving data room connector 3.1, 4.1, and the associated customer DCM app 3.3 and supplier DCM app 4.3 that the previously sent data has now been changed.

[0090] In summary, the DCM system 1 provides a web-based data service 200 that is configured to determine a requested material requirement and / or a requested capacity requirement based on the received initial request 100 and to send the determined material requirement and / or the determined capacity requirement to the coupled data room connector 3.1, 4.1 and the respective customer DCM app 3.3 and supplier DCM app 4.3.

[0091] The web-based data service 200 can also be configured to determine and output at least one service parameter, e.g., the current service parameter, the bottleneck status and / or the surplus status, and / or one future service parameter, e.g., the status of cooperation between supplier and customer, based on the determined material requirements and / or the determined capacity requirements. Reference list 1 Demand and Capacity Management System (DCM System) 2 Data Management System (BPDM System) 3 customers 3.1 associated data room connector 3.2 Customer device 3.3 Associated demand and capacity management application (customer DCM app) 3.3.1 associated adjustment unit 3.4 associated storage device 3.5 Customer Demand Data Structure Model 4 supplier 4.1 associated data room connector 4.2 Supplier device 4.3 Associated demand and capacity management application (supplier DCM app) 4.3.1 associated adjustment unit 4.4 associated storage device 4.5 Capacity Group Data Structure Model 5 cloud-based servers 6.1 Communication channel 6.2 Communication channel 7 Material requirements 8 Customer material number 9 Customer Material Description 10 units of measure 11 demand series 12 categories of needs 13 customer locations 14 demand time series 15 Capacity Group 16 Capacity group identifier 17 Capacity group name 18 units of measure 19 Capacity Line Series 20th calendar week 21 actual capacity 22 maximum capacity 23 Quantity 24 Quality 25 linked demand series 26 Customer material number 27 Needs category 28 customer locations 100 Customer Requirements 101 first requirement 102 Supplier capacity requirement 103 second requirement 104 key data 105 key pieces of information 106 key customer data 107 key supplier data 108 Network identifier (IP address) 109 unique identifier (unique connector ID) 110 customer information 111 Supplier Information 112 Data Room Connector Asset 200 web-based data service 201-209 Procedural steps 210 Exchange and matching procedures 210.1 Input procedure 210.2 Demand Exchange Sub-Procedure 210.3 Matching and comparison sub-procedure 210.4 Sub-procedures for resolving bottlenecks and surpluses 210.5 loop 210.6 Output unit 211 Exchange and matching procedures 211.1 Input procedure 211.2 Demand Exchange - Sub-procedure 211.3 Matching and comparison sub-procedure 211.4 Sub-procedures for resolving bottlenecks and surpluses 211.5 Loop 211.6 Output unit

Claims

[1] Demand and capacity management system (1), configured as a web-based data service (200) in an automotive network for communication between supplier and customer, comprising: - at least one data management system (2) configured as a cloud-based or central server, - at least one customer device (3) comprising an associated demand and capacity management application (3.3), - at least one supplier device (4) comprising an associated demand and capacity management application (4.3), - at least one first data room connector (3.1) which can be detachably connected or linked to the customer device (3) as a communication interface, - at least one second data room connector (4.1) that can be detachably connected to or is connected to the supplier device (4) as a communication interface, wherein the first data room connector (3.1) is configured to communicate with the data management system (2) via an associated connection and with the supplier device (4) directly via communication channels (6.1, 6.2), and the second data room connector (4.1) is configured to communicate with the data management system (2) via an associated connection and with the customer device (3) directly via the communication channels (6.1, 6.2), wherein the web-based data service (200) is configured to: a) Entering a coupling of at least one of the data room connectors (3.1, 4.1) and receiving a data room connector identifier or network identifier (108) and writing the data room connector identifier or network identifier (108) to the data management system (2), b) Creating a data space connector asset (112) for expected data on this coupled data space connector (3.1, 4.1), c) Receiving an initial request (101) of the expected data directly via the communication channels (6.1, 6.2) between the data space connectors (3.1, 4.1), d) Comparing the expected data with related internal data, e) based on the matching results, creating a second requirement, f) optionally retrieve from the data management system (2) a network identifier (108) of the receiving data room connector (3.1, 4.1), g) Transmitting the second request (103) and the associated network identifier (108) of the receiving data space connector (3.1, 4.1) to the coupled data space connector (4.1, 3.1) directly via the communication channels (6.1, 6.2) between the data space connectors (3.1, 4.1), h) Establishing one of the communication channels (6.1, 6.2) between the coupled data space connector (3.1, 4.1) and the receiving data space connector (3.1, 4.1) and i) Sending the second request (103) to the receiving data room connector (3.1, 4.1). [2] System (1) according to claim 1, wherein the web-based data service (200) comprises at least two data models, wherein a first data model is configured as a customer requirements data structure model (3.5), in particular a material requirements data structure model, and a second data model is configured as a capacity group data structure model (4.5). [3] System (1) according to claim 1, wherein the customer device (3.2) as an associated demand and capacity management application (3.3) comprises at least one associated application programming interface for processing at least one of the requirements and / or demands to be communicated by the customer device (3.2) to the supplier device (4.2). [4] System (1) according to claim 1 or 2, wherein the supplier device (4.2) as an associated demand and capacity management application (4.3) comprises at least one associated application programming interface for processing at least one of the requirements and / or capacities to be communicated by the supplier device (4) to the customer device (3). [5] System (1) according to any of the preceding claims, wherein the customer device (3) comprises at least one associated matching unit (3.3.1) for matching the expected data with associated internal data and / or an associated customer storage device (3.4) for storing associated internal data. [6] System (1) according to one of the preceding claims, wherein the supplier device (4.2) comprises at least one associated matching unit (4.3.1) for matching the expected data with associated internal data and / or a supplier matching unit for storing associated internal data. [7] System (1) according to one of the preceding claims, wherein each of the at least two associated application programming interfaces is coupled to the associated data space connectors (3.1, 4.1). [8] System (1) according to any of the preceding claims, wherein the associated demand and capacity management application (3.3, 4.3) is configured to match the expected data with associated internal data and to receive all data that is correctly addressed and / or that is addressed to the respective coupled data room connectors (3.1, 4.1). [9] Demand and capacity management method, in particular for linking a customer demand requirement (101) or a customer demand with an available supplier capacity, wherein the method is configured as a web-based data service (200) of a demand and capacity management system (1) according to one of the preceding claims, wherein the web-based data service (200) is configured to: a) Entering a coupling of at least one of a number of data room connectors (3.1, 4.1) and receiving a data room connector identifier and writing the data room connector identifier to a data management system (2) of the demand and capacity management system (1), b) Creating a data space connector asset (112) for expected data on this coupled data space connector (3.1, 4.1), c) Receiving an initial data request (100) of the expected data directly via communication channels (6.1, 6.2) between the data room connectors (3.1, 4.1), d) Comparing the expected data with related internal data, e) based on the matching results, creating a second requirement (103), f) optionally Retrieve from the data management system (2) of at least one network address or network identifier (108) of the receiving data space connector (3.1, 4.1), g) Transmitting the second request (103) and the associated network identifier (108) or the network address of the receiving data space connector (3.1, 4.1) to the coupled data space connector (4.1, 3.1) directly via the communication channels (6.1, 6.2) between the data space connectors (3.1, 4.1), h) Setting up or activating one of the communication channels (6.1 or 6.2) between the coupled data space connector (3.1, 4.1) and the receiving data space connector (3.1, 4.1), and i) Sending the second request (103) to the receiving data room connector (3.1, 4.1). [10] Method according to claim 9, wherein the web-based data service (200) is further configured to: - based on the received initial request (101), determining a requested material requirement and / or a requested capacity requirement and sending the determined material requirement and / or the determined capacity requirement to the coupled data room connector (3.1, 4.1). [11] Method according to claim 9 or 10, wherein the web-based data service (200) is further configured to: - Based on the determined material requirements and / or the determined capacity requirements, determine and output at least one service parameter.

Images