diff --git a/process/general_concepts/_assets/score_building_blocks_meta_model.drawio.svg b/process/general_concepts/_assets/score_building_blocks_meta_model.drawio.svg
index 6655290a55..48b596a666 100644
--- a/process/general_concepts/_assets/score_building_blocks_meta_model.drawio.svg
+++ b/process/general_concepts/_assets/score_building_blocks_meta_model.drawio.svg
@@ -1,4 +1,2292 @@
-
-
-
-
+
diff --git a/process/general_concepts/_assets/score_building_blocks_meta_model_deployment_example.drawio.svg b/process/general_concepts/_assets/score_building_blocks_meta_model_deployment_example.drawio.svg
index 3dbdbc450b..cf1cb1a3b3 100644
--- a/process/general_concepts/_assets/score_building_blocks_meta_model_deployment_example.drawio.svg
+++ b/process/general_concepts/_assets/score_building_blocks_meta_model_deployment_example.drawio.svg
@@ -1,4 +1,2532 @@
-
-
-
-
\ No newline at end of file
+
diff --git a/process/process_areas/architecture_design/architecture_workflow.rst b/process/process_areas/architecture_design/architecture_workflow.rst
index d14ec92e4c..0ef1844fe4 100644
--- a/process/process_areas/architecture_design/architecture_workflow.rst
+++ b/process/process_areas/architecture_design/architecture_workflow.rst
@@ -19,6 +19,20 @@ Architecture Workflows
For a detailed explanation of workflows and their role within the process model, please refer to the :ref:`processes_introduction`.
+.. workflow:: Create/Maintain Platform architecture
+ :id: wf__cr_mt_platarch
+ :status: valid
+ :tags: architecture_design
+ :responsible: rl__contributor
+ :approved_by: rl__committer
+ :supported_by: rl__safety_manager, rl__security_manager
+ :input: wp__requirements_stkh, wp__issue_track_system
+ :output: wp__platform_arch
+ :contains: gd_guidl__arch_design
+ :has: doc_concept__arch_process, doc_getstrt__arch_process
+
+ The platform architecture is created and maintained.
+
.. workflow:: Create/Maintain Feature architecture
:id: wf__cr_mt_featarch
:status: valid
diff --git a/process/process_areas/architecture_design/architecture_workproducts.rst b/process/process_areas/architecture_design/architecture_workproducts.rst
index d60ecb12c0..ee14278885 100644
--- a/process/process_areas/architecture_design/architecture_workproducts.rst
+++ b/process/process_areas/architecture_design/architecture_workproducts.rst
@@ -17,6 +17,16 @@
Architecture Work Products
##########################
+.. workproduct:: Platform Architecture
+ :id: wp__platform_arch
+ :status: valid
+ :complies: std_wp__iso26262__software_751, std_wp__isosae21434__development_1051, std_req__aspice_40__iic-04-04
+ :tags: doc_lifecycle_model_3
+
+ Platform Architecture describes the overall software structure with the belonging features, modules and their logical interfaces, i.e. top-level decomposition of the platform into features and their interactions
+
+ * Static view - Overview of features, SW modules and their relationships within the platform
+
.. workproduct:: Feature Architecture
:id: wp__feature_arch
:status: valid
diff --git a/process/process_areas/architecture_design/guidance/architecture_guideline.rst b/process/process_areas/architecture_design/guidance/architecture_guideline.rst
index c698da8b75..23cd0702d7 100644
--- a/process/process_areas/architecture_design/guidance/architecture_guideline.rst
+++ b/process/process_areas/architecture_design/guidance/architecture_guideline.rst
@@ -66,34 +66,108 @@ Those steps are:
- Description
- Responsible
* - 1.
- - :ref:`Create feature architecture (Concept) `
+ - :ref:`Create platform architecture (Concept) `
- :need:`[[title]] `
* - 2.
- - :ref:`Model feature architecture `
+ - :ref:`Model platform architecture `
- :need:`[[title]] `
* - 3.
- - :ref:`Allocate feature requirements to architectural elements `
+ - :ref:`Allocate stakeholder requirements to architectural elements `
- :need:`[[title]] `
* - 4.
- - :ref:`Review architectural design `
+ - :ref:`Review platform architecture `
- :need:`[[title]] `
* - 5.
- - Merge architectural design into score delivery container
+ - Merge platform architecture into score delivery container
- :need:`[[title]] `
* - 6.
+ - :ref:`Create feature architecture (Concept) `
+ - :need:`[[title]] `
+ * - 7.
+ - :ref:`Model feature architecture `
+ - :need:`[[title]] `
+ * - 8.
+ - :ref:`Allocate feature requirements to architectural elements `
+ - :need:`[[title]] `
+ * - 9.
+ - :ref:`Review feature architecture `
+ - :need:`[[title]] `
+ * - 10.
+ - Merge feature architecture into score delivery container
+ - :need:`[[title]] `
+ * - 11.
- | :ref:`Create component architecture (Concept) `
| :ref:`Allocate component requirements to architectural elements `
- :need:`[[title]] `
- * - 7.
+ * - 12.
- :ref:`Model component architecture `
- :need:`[[title]] `
- * - 8.
+ * - 13.
- :ref:`Review component architecture `
- :need:`[[title]] `
- * - 9.
+ * - 14.
- Merge component architectural design into module's delivery container
- :need:`[[title]] `
+.. _create_platform_architecture:
+
+Create platform architecture (Concept)
+----------------------------------------
+
+The platform architecture (= top-level architecture) shall be created in the platform delivery container. It provides the overall decomposition of the platform into features and defines the logical interfaces at the platform boundary.
+
+The platform architecture shall describe the concept of the platform, including supporting figures and drawings. If multiple solutions are possible, these should be documented here with the rationale for the final decision. A design decision template is provided in :need:`Decision Record Template `.
+
+Additionally, you should consult your project's specific guidelines, e.g., for using the version management tooling or architecture element naming conventions, which should be defined (or linked) in the :need:`Project SW development Plan `.
+
+.. _model_platform_architecture:
+
+Model platform architecture
+---------------------------
+
+Based on the concept description, a model of the platform architecture shall be designed. It shall provide an overview of the features within the platform and their logical interfaces at the platform boundary. Therefore, the following elements shall be used:
+
+.. list-table:: Architectural Elements of the Platform Architecture
+ :header-rows: 1
+ :widths: 10,30
+
+ * - Element
+ - Sphinx directive
+ * - Feature
+ - feat
+ * - Logical Interface
+ - logic_arc_int
+ * - Logical Interface Operation
+ - logic_arc_int_op
+
+The relations of the static elements are described in :ref:`metamodel_architectural_design`.
+
+.. _allocate_stakeholder_requirements:
+
+Allocate stakeholder requirements to architectural elements
+-----------------------------------------------------------
+
+In this step, the stakeholder requirements shall be allocated to the platform architectural elements depending on their content. These links shall be established from architectural elements to stakeholder requirements via the attribute *fulfils*.
+
+If needed, additional feature requirements derived from architectural decisions should be created and allocated to the respective feature.
+
+.. _review_platform_architecture:
+
+Review platform architecture
+-----------------------------
+
+As soon as the design is in a mature state, it can be reviewed according to :need:`doc_concept__wp_inspections`
+and merged into the main branch of the platform delivery container. See also the document life-cycle guideline :need:`gd_guidl__documentation` for more information about the documentation for the platform architecture :need:`wp__platform_arch`.
+
+For the review process, a checklist template is available: :need:`Architecture Inspection Checklist Template `.
+
+The following roles should be included in the review:
+
+* :need:`[[title]] `
+* :need:`[[title]] `
+* :need:`[[title]] `
+* :need:`[[title]] `
+
.. _create_feature_architecture:
Create feature architecture (Concept)
diff --git a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst b/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst
index 12e641b34c..f5fafeb4aa 100644
--- a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst
+++ b/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst
@@ -103,7 +103,7 @@ Architectural Views
* Sequence Diagram (feat_arc_dyn, comp_arc_dyn)
* Interface View (logic_arc_int, real_arc_int)
- Only an additional view shall be created on module level.
+ At the module level, only one additional static view (mod_view_sta) shall be created.
Attributes of Architectural Elements
------------------------------------