diff --git a/docs-kits/kits/Resiliency/MP_Kit.md b/docs-kits/kits/Resiliency/MP_Kit.md deleted file mode 100644 index e0d527185b6..00000000000 --- a/docs-kits/kits/Resiliency/MP_Kit.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -id: mp kit -title: MP Kit -sidebar_position: 6 ---- - - -## Increase production flexibility and leverage existing business potential for lot size one - -### Automate the orchestration of production resources and planning processes - - -The Modular Production (MP) Kit defines services, interfaces and data models based on industry standards with the goal to increase flexibility and reliability of industrial production. Furthermore services that provide information about production status and planning that is required by other use cases will be provided. - -Modular Production has the goal to support individual production (batch size 1) at the price of series production. In particular, this is to be achieved by automating the orchestration of production resources and planning of production processes as much as possible, thus significantly reducing effort and planning times. - -See [Status Quo](#status-quo) below for more details on Modular Production. - -The Modular Production Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -#### Connect and access to shopfloor information for further value creation - -Due dates, machines used etc. for specific individual produced product are made available through standardized service to the Catena-X network honoring access and data sovereignty rules. - - -### Status Quo - -Higher-level, external influencing factors from the supply chain, such as delays in the logistics chain for supplier parts or short-term order changes, may invalidate a production plan that has already been drawn up. Today, such short-term changes in the general conditions of the production process can often only be taken into consideration indirectly and made through manual corrections. - -### Benefits for OEM, SME and Solution Provider - -A growth in efficiency in the sense of the OEE is achieved in that production can be reconfigured in the event of faults to continue operating as well as possible. The increased flexibility creates the space for new business models, such as the interposition of highly prioritized, lucrative orders. - -Further benefits and value can be generated through additional services or apps that connect to the shopfloor information service via the Catena-X platform. diff --git a/docs-kits/kits/Resiliency/MaaS.md b/docs-kits/kits/Resiliency/MaaS.md deleted file mode 100644 index b0f46b5a791..00000000000 --- a/docs-kits/kits/Resiliency/MaaS.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -id: maas -title: MaaS Kit -sidebar_position: 3 ---- - - -## Enable on-demand manufacturing in an interoperable, federated network of manufacturing networks by linking demand with capacities and capabilities - - -The Manufacturing-as-a-Service (MaaS) Kit defines the mechanisms and services needed for an interoperable, federated network of networks, where manufacturing demand meets manufacturing capacities and capabilities. - -See [Status Quo](#status-quo) below for more details on Manufacturing-as-a-Service. - -The MaaS Kit provides a comprehensive reference architecture with standardized interfaces and data models, including first implemented services to show the operating network of networks with a single-entry point into the world of on-demand manufacturing (ODM) independent of domain. The main focus is on facilitating the intermediation of manufacturing supply as a service and manufacturing demand. In addition, IT services enable the connectivity and process automation for being part of this digital marketplace. - -The MAAS Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -### Minimize risk of operations - -The available reference architecture supports operators of networks and services to minimize risk while operating Manufacturing-as-a-Service applications. - -### Reduce development time - -The time to develop integrations of additional solutions or stakeholders (e.g. consumers or suppliers of on-demand manufacturing) to existing networks are drastically cut through well-defined, standardised interfaces and data models. - -### Low threshold entry to marketplace - -Existing examples of implemented services enable quick entry for consumers and suppliers of on-demand manufacturing to the marketplace that facilitates the intermediation of manufacturing supply as a service and manufacturing demand. - -### Cut leadtime for manufacturing transactions - -IT services to enable connectivity and process automation to further streamline the interaction between consumer and supplier of on-demand manufacturing. - - -## Status Quo - -Manufacturing-as-a-Service is the practice of connecting consumers and providers of on-demand manufacturing capabilities in a Catena-X context both directly and through integration of other on-demand platforms. The overall aim is to increase resilience against fluctuating demand through one single-entry point for different manufacturing domains. - -By requesting components over a graphical user interface, the MaaS portal, component buyers primarily have the value of finding alternative suppliers at short notice, that are definitely able to manufacture the required components. - -Manufacturers and ODM platforms primarily gain value in the MaaS portal by offering manufacturing capabilities as suppliers. In this way, suppliers can compensate for fluctuations in demand from their conventional customers by being able to get orders from an alternative sales channel without having to invest great effort in sales activities. -Both sides also benefit from the security and data sovereignty advantages of the Catena-X environment. diff --git a/docs-kits/kits/Resiliency/PURIS_Kit.md b/docs-kits/kits/Resiliency/PURIS_Kit.md deleted file mode 100644 index 456f45189a2..00000000000 --- a/docs-kits/kits/Resiliency/PURIS_Kit.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -id: PURIS -title: PURIS Kit -sidebar_position: 5 ---- - - -## Mitigate the bullwhip effect in your supply chain by identifying potential shortages earlier - -### Verify the demands and capacities of actual production plan from today up to a few weeks - - -The Predictive Unit Real-Time Information System (PURIS) KIT provides the capabilities to exchange the production related information within a given relationship between two business partners such as the already available stock of the supplier, the updating stock of the customer, the customer's demand and the supplier's fulfillment status of an order. The aim is to help mitigate potential and actual shortage scenarios. - -PURIS is the second of two components of the Demand and Capacity Management as approached by the Resiliency Kit: - -1. A planning component forecasting its demands and capacities for the next months up to multiple years. -2. An operationalization component verifying the demands and capacities of its actual production plan from today up to multiple weeks. - -See [Status Quo](#status-quo) below for more details on Demand and Capacity Management. - -The PURIS Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -#### Connect once to interact with all your partners - -By leveraging the standardized APIs you avoid point-to-point integrations. - -#### Increase flexibility with easy access and exchange of up-to-date information - -Low effort to exchange the latest updated information with your partners through formalized approach. - -#### Leverage Catena-X built-in data sovereignty - -Decide the access and usage conditions for the exchanged data in a compliant way - -### Status Quo - -Within the Business Domain Resiliency, the Demand and Capacity Management (DCM) represents the planning and the PURIS represents the operationalization component. Considering a shorter time period in PURIS based on the production plan, results in more reliable information. - -Generally, the Demand and Capacity Management needs a close cooperation between a company and its partners with the supply chain. - -Within the value chain, each partner needs to plan his own production and relies on his customers' demand forecasts. The bullwhip effect describes the rising amplified deviation between orders to suppliers and sales to buyers along the value chain. The fluctuation rises from tier to tier. Using the latest production related information, you can mitigate the bullwhip effect for you and your partners within the value chain. - -- As a customer, you can verify the production related information of your partner so that you can identify potential shortages earlier with less effort and mitigate or resolve them spending less resources. -- As a supplier, you can increase your production efficiency, e.g. by optimizing your batch size based on your customers' latest demands. diff --git a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MP_Kit.md b/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MP_Kit.md deleted file mode 100644 index e0d527185b6..00000000000 --- a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MP_Kit.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -id: mp kit -title: MP Kit -sidebar_position: 6 ---- - - -## Increase production flexibility and leverage existing business potential for lot size one - -### Automate the orchestration of production resources and planning processes - - -The Modular Production (MP) Kit defines services, interfaces and data models based on industry standards with the goal to increase flexibility and reliability of industrial production. Furthermore services that provide information about production status and planning that is required by other use cases will be provided. - -Modular Production has the goal to support individual production (batch size 1) at the price of series production. In particular, this is to be achieved by automating the orchestration of production resources and planning of production processes as much as possible, thus significantly reducing effort and planning times. - -See [Status Quo](#status-quo) below for more details on Modular Production. - -The Modular Production Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -#### Connect and access to shopfloor information for further value creation - -Due dates, machines used etc. for specific individual produced product are made available through standardized service to the Catena-X network honoring access and data sovereignty rules. - - -### Status Quo - -Higher-level, external influencing factors from the supply chain, such as delays in the logistics chain for supplier parts or short-term order changes, may invalidate a production plan that has already been drawn up. Today, such short-term changes in the general conditions of the production process can often only be taken into consideration indirectly and made through manual corrections. - -### Benefits for OEM, SME and Solution Provider - -A growth in efficiency in the sense of the OEE is achieved in that production can be reconfigured in the event of faults to continue operating as well as possible. The increased flexibility creates the space for new business models, such as the interposition of highly prioritized, lucrative orders. - -Further benefits and value can be generated through additional services or apps that connect to the shopfloor information service via the Catena-X platform. diff --git a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MaaS.md b/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MaaS.md deleted file mode 100644 index b0f46b5a791..00000000000 --- a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/MaaS.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -id: maas -title: MaaS Kit -sidebar_position: 3 ---- - - -## Enable on-demand manufacturing in an interoperable, federated network of manufacturing networks by linking demand with capacities and capabilities - - -The Manufacturing-as-a-Service (MaaS) Kit defines the mechanisms and services needed for an interoperable, federated network of networks, where manufacturing demand meets manufacturing capacities and capabilities. - -See [Status Quo](#status-quo) below for more details on Manufacturing-as-a-Service. - -The MaaS Kit provides a comprehensive reference architecture with standardized interfaces and data models, including first implemented services to show the operating network of networks with a single-entry point into the world of on-demand manufacturing (ODM) independent of domain. The main focus is on facilitating the intermediation of manufacturing supply as a service and manufacturing demand. In addition, IT services enable the connectivity and process automation for being part of this digital marketplace. - -The MAAS Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -### Minimize risk of operations - -The available reference architecture supports operators of networks and services to minimize risk while operating Manufacturing-as-a-Service applications. - -### Reduce development time - -The time to develop integrations of additional solutions or stakeholders (e.g. consumers or suppliers of on-demand manufacturing) to existing networks are drastically cut through well-defined, standardised interfaces and data models. - -### Low threshold entry to marketplace - -Existing examples of implemented services enable quick entry for consumers and suppliers of on-demand manufacturing to the marketplace that facilitates the intermediation of manufacturing supply as a service and manufacturing demand. - -### Cut leadtime for manufacturing transactions - -IT services to enable connectivity and process automation to further streamline the interaction between consumer and supplier of on-demand manufacturing. - - -## Status Quo - -Manufacturing-as-a-Service is the practice of connecting consumers and providers of on-demand manufacturing capabilities in a Catena-X context both directly and through integration of other on-demand platforms. The overall aim is to increase resilience against fluctuating demand through one single-entry point for different manufacturing domains. - -By requesting components over a graphical user interface, the MaaS portal, component buyers primarily have the value of finding alternative suppliers at short notice, that are definitely able to manufacture the required components. - -Manufacturers and ODM platforms primarily gain value in the MaaS portal by offering manufacturing capabilities as suppliers. In this way, suppliers can compensate for fluctuations in demand from their conventional customers by being able to get orders from an alternative sales channel without having to invest great effort in sales activities. -Both sides also benefit from the security and data sovereignty advantages of the Catena-X environment. diff --git a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/PURIS_Kit.md b/docs-kits_versioned_docs/version-24.05/kits/Resiliency/PURIS_Kit.md deleted file mode 100644 index 456f45189a2..00000000000 --- a/docs-kits_versioned_docs/version-24.05/kits/Resiliency/PURIS_Kit.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -id: PURIS -title: PURIS Kit -sidebar_position: 5 ---- - - -## Mitigate the bullwhip effect in your supply chain by identifying potential shortages earlier - -### Verify the demands and capacities of actual production plan from today up to a few weeks - - -The Predictive Unit Real-Time Information System (PURIS) KIT provides the capabilities to exchange the production related information within a given relationship between two business partners such as the already available stock of the supplier, the updating stock of the customer, the customer's demand and the supplier's fulfillment status of an order. The aim is to help mitigate potential and actual shortage scenarios. - -PURIS is the second of two components of the Demand and Capacity Management as approached by the Resiliency Kit: - -1. A planning component forecasting its demands and capacities for the next months up to multiple years. -2. An operationalization component verifying the demands and capacities of its actual production plan from today up to multiple weeks. - -See [Status Quo](#status-quo) below for more details on Demand and Capacity Management. - -The PURIS Kit is continuously under development and future extensions and improvements will help you to adopt or extend functionality even faster. - - -#### Connect once to interact with all your partners - -By leveraging the standardized APIs you avoid point-to-point integrations. - -#### Increase flexibility with easy access and exchange of up-to-date information - -Low effort to exchange the latest updated information with your partners through formalized approach. - -#### Leverage Catena-X built-in data sovereignty - -Decide the access and usage conditions for the exchanged data in a compliant way - -### Status Quo - -Within the Business Domain Resiliency, the Demand and Capacity Management (DCM) represents the planning and the PURIS represents the operationalization component. Considering a shorter time period in PURIS based on the production plan, results in more reliable information. - -Generally, the Demand and Capacity Management needs a close cooperation between a company and its partners with the supply chain. - -Within the value chain, each partner needs to plan his own production and relies on his customers' demand forecasts. The bullwhip effect describes the rising amplified deviation between orders to suppliers and sales to buyers along the value chain. The fluctuation rises from tier to tier. Using the latest production related information, you can mitigate the bullwhip effect for you and your partners within the value chain. - -- As a customer, you can verify the production related information of your partner so that you can identify potential shortages earlier with less effort and mitigate or resolve them spending less resources. -- As a supplier, you can increase your production efficiency, e.g. by optimizing your batch size based on your customers' latest demands. diff --git a/docs-kits_versioned_sidebars/version-24.05-sidebars.json b/docs-kits_versioned_sidebars/version-24.05-sidebars.json index 95d43606fe9..bc9799ce7f9 100644 --- a/docs-kits_versioned_sidebars/version-24.05-sidebars.json +++ b/docs-kits_versioned_sidebars/version-24.05-sidebars.json @@ -1059,10 +1059,7 @@ "type": "doc", "id": "kits/Resiliency/resiliency" }, - "items": [ - "kits/Resiliency/maas", - "kits/Resiliency/PURIS" - ] + "items": [] } ] } diff --git a/openApi/dt/discovery-finder-openapi.yaml b/openApi/dt/discovery-finder-openapi.yaml deleted file mode 100644 index c392d4d5d26..00000000000 --- a/openApi/dt/discovery-finder-openapi.yaml +++ /dev/null @@ -1,264 +0,0 @@ -############################################################### -# Copyright (c) 2021 Robert Bosch Manufacturing Solutions GmbH -# Copyright (c) 2021 Contributors to the Eclipse Foundation -# -# See the NOTICE file(s) distributed with this work for additional -# information regarding copyright ownership. -# -# This program and the accompanying materials are made available under the -# terms of the Apache License, Version 2.0 which is available at -# https://www.apache.org/licenses/LICENSE-2.0. -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT -# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the -# License for the specific language governing permissions and limitations -# under the License. -# -# SPDX-License-Identifier: Apache-2.0 -############################################################### - -openapi: 3.0.3 -info: - title: Discovery Finder - description: Discovery Finder to find endpoint of the BPN/EDC Discovery. - contact: - name: SLDT Team - version: 0.0.1 - -security: - - CatenaXOpenId: - - profile -servers: - - url: "{protocol}://{host_name}:{port}/api/{version_prefix}" - variables: - protocol: - description: Allows access through http and https (recommended) - default: http - enum: - - http - - https - host_name: - description: Hostname of server hosting the api - default: localhost - port: - description: "80 is default for http, 443 for https" - default: "443" - enum: - - "80" - - "443" - - "4243" - version_prefix: - default: v1.0 - enum: - - v1.0 -paths: - /administration/connectors/discovery: - post: - tags: - - Finder - summary: Define the endpoint to BPN discovery services and the EDC discovery service. - operationId: PostDiscoveryEndpoint - requestBody: - description: Create new endpoint for bpn discovery service / edc discovery service. The type is uniqued. This service is allowed to administrators only - content: - application/json: - schema: - $ref: '#/components/schemas/DiscoveryEndpoint' - examples: - complete: - $ref: '#/components/examples/discovery-endpoint' - required: true - responses: - "201": - description: Discovery Endpoint created successfully - content: - application/json: - schema: - $ref: '#/components/schemas/DiscoveryEndpoint' - examples: - complete: - $ref: '#/components/examples/discovery-endpoint-result' - /administration/connectors/discovery/search: - post: - tags: - - Finder - summary: Find the endpoints to BPN discovery services and the EDC discovery service. - operationId: GetDiscoveryEndpoints - requestBody: - description: The request body is expecting a list of types ( e.g. oen, bpid, etc.) to return available discovery endpoints. - content: - application/json: - schema: - $ref: '#/components/schemas/SearchRequest' - examples: - complete: - $ref: '#/components/examples/discovey-endpoint-search' - required: true - responses: - "200": - description: Returns discovery endpoints based on search filter. - content: - application/json: - schema: - $ref: '#/components/schemas/DiscoveryEndpointCollection' - examples: - complete: - $ref: '#/components/examples/discovery-endpoint-search-result' - /administration/connectors/discovery/{resourceId}: - delete: - tags: - - Finder - summary: Delete the endpoint to BPN discovery services and the EDC discovery service. - operationId: DeleteDiscoveryEndpointByResourceId - parameters: - - name: resourceId - in: path - description: The IdentifierKeyValue unique id (BASE64-URL-encoded) - required: true - style: simple - explode: false - schema: - type: string - responses: - "204": - description: Discovery Endpoint deleted successfully -components: - schemas: - DiscoveryEndpoint: - title: DiscoveryEndpoint - type: object - required: - - type - - description - - endpointAddress - - timeToLive - properties: - type: - type: string - minLength: 1 - maxLength: 200 - description: - type: string - minLength: 1 - maxLength: 500 - endpointAddress: - type: string - minLength: 1 - maxLength: 300 - documentation: - type: string - minLength: 1 - maxLength: 500 - resourceId: - type: string - timeToLive: - type: integer - minimum: 1 - maximum: 31536000 - SearchRequest: - title: SearchRequest - required: - - types - properties: - types: - title: types - type: array - maxItems: 10000 - items: - type: string - DiscoveryEndpointCollection: - title: DiscoveryEndpointCollection - properties: - endpoints: - title: endpoints - type: array - maxItems: 10000 - items: - $ref: '#/components/schemas/DiscoveryEndpoint' - type: object - ErrorResponse: - type: object - required: - - error - properties: - error: - $ref: '#/components/schemas/Error' - Error: - type: object - required: - - details - properties: - message: - type: string - example: size must be between {min} and {max} - description: The detailed error message for the exception which occurred. - minLength: 1 - path: - type: string - description: The requested path. - minLength: 1 - details: - type: object - additionalProperties: - type: object - description: An object with key/value pairs containing additional information about the error - securitySchemes: - CatenaXOpenId: - type: openIdConnect - openIdConnectUrl: ../.well-known/openid-configuration - examples: - discovery-endpoint: - value: - { - "type": "oen", - "description": "Service to discover BPN to a particular OEN", - "endpointAddress": "http://...", - "documentation": "http://.../swagger/index.html", - "timeToLive": 31536000 - } - discovery-endpoint-result: - value: - { - "type": "oen", - "description": "Service to discover BPN to a particular OEN", - "endpointAddress": "http://...", - "documentation": "http://.../swagger/index.html", - "resourceId": "ec6f407b-4296-418c-9e4e-fb739fe72a67", - "timeToLive": 31536000 - } - discovey-endpoint-search: - value: - { - "types": [ "oen", "bpid", "bpn" ] - } - discovery-endpoint-search-result: - value: - { - "endpoints": [ - { - "type": "oen", - "description": "Service to discover BPN to a particular OEN", - "endpointAddress": "http://...", - "documentation": "http://.../swagger/index.html", - "resourceId": "ec6f407b-4296-418c-9e4e-fb739fe72a67", - "timeToLive": 31536000 - }, - { - "type": "bpid", - "description": "Service to discover BPN to a particular Battery Pass ID", - "endpointAddress": "http://...", - "documentation": "http://.../swagger/index.html", - "resourceId": "08702529-3714-4c4f-b022-346b9b4fbbe2", - "timeToLive": 31536000 - }, - { - "type": "bpn", - "description": "Service to discover EDC to a particular BPN", - "endpointAddress": "http://...", - "documentation": "http://.../swagger/index.html", - "resourceId": "316417cd-0fb5-4daf-8dfa-8f68125923f1", - "timeToLive": 31536000 - } - ] - } \ No newline at end of file diff --git a/sidebarsDocsKits.js b/sidebarsDocsKits.js index da3e0797666..6a9db5c4e3a 100644 --- a/sidebarsDocsKits.js +++ b/sidebarsDocsKits.js @@ -632,10 +632,7 @@ const sidebars = { type: 'doc', id: 'kits/Resiliency/resiliency' }, - items: [ - 'kits/Resiliency/maas', - 'kits/Resiliency/PURIS' - ] + items: [] }, ] }; diff --git a/utils/resiliencyItems.js b/utils/resiliencyItems.js index 732fa3b5a03..7b98015b16c 100644 --- a/utils/resiliencyItems.js +++ b/utils/resiliencyItems.js @@ -8,26 +8,26 @@ export const resiliencyItems = [ { id: 1, img: DCM_Kit, - pageRoute: "/docs-kits/kits/Resiliency/DCM%20Kit" + pageRoute: "/docs-kits/category/dcm-kit" }, { id: 2, img: Maas_Kit, - pageRoute: "/docs-kits/kits/Resiliency/maas" + pageRoute: "/docs-kits/category/manufacturing-as-a-service-kit" }, { id: 3, img: OSim_Kit, - pageRoute: "/docs-kits/next/kits/OSim%20Kit/Adoption%20View%20OSim%20Kit" + pageRoute: "/docs-kits/category/osim-kit" }, { id: 4, img: PURIS_Kit, - pageRoute: "/docs-kits/next/kits/PURIS%20Kit/Adoption%20View%20PURIS%20Kit" + pageRoute: "/docs-kits/category/puris-kit" }, { id: 5, img: MP_Kit, - pageRoute: "/docs-kits/kits/Resiliency/mp%20kit" + pageRoute: "/docs-kits/category/modular-production-kit" }, ]