pmai · May 22, 2026 · May 1, 2026 · May 1, 2026 · May 1, 2026 · May 1, 2026
diff --git a/docs/1___overview.adoc b/docs/1___overview.adoc
@@ -25,7 +25,7 @@ It must be possible to answer questions such as:
 
 * Were the simulation objectives and credibility requirements fulfilled?
 
-While the MIC Core specification provides metadata for simulation models, it does not describe the simulation tasks in which those models are used.
+While the MIC Core specification provides metadata for simulation models, it does not support and describe the simulation tasks in which those models are used (see figure 1).
 
 This specification addresses this gap.
 
@@ -94,7 +94,12 @@ The goal of this specification is therefore not to prescribe a fixed metadata im
 
 === Simulation Process Context
 
-The metadata structure defined in this specification follows a simulation process aligned with the *Credible Simulation Process Framework.*
+The metadata structure defined in this specification follows a simulation process aligned with the https://modelica.github.io/ssp-ls-traceability/1.0.0/#sec-crediblesimulationprocessframework[*Credible Simulation Process Framework*], as defined in <<CSP>>, as referenced in the SSP Layered Standard Traceability 1.0.0 specification (see <<SSPLST>>):
+
+[#im-csp]
+.Credible Simulation Process with attached metadata to the process phases
+image::CSP.png[]
+
 
 This process distinguishes the following phases:
 
@@ -143,6 +148,15 @@ This approach allows organizations to implement the standard incrementally and a
 
 Additionally, the specification is designed to be technology-agnostic, meaning that it does not prescribe specific data formats or technologies for metadata representation, or mapping of metadata items to specific attribute names in a specific format.
 
+=== Sub-Attributes
+
+For a number of attributes, for example for <<Simulation Task,Simulation Task>>, the specification allows the use of sub-attributes to describe the attribute in more detail, e.g. by providing both machine-readable and human-readable variants of a name, version information, or URIs.
+
+The use of sub-attributes is per-se optional, however standards implementing this specification can make the use of sub-attributes, and the use of certain sub-attributes mandatory.
+
+The list of allowed sub-attributes is listed in the definition of an attribute.
+Since they are shared between attribute definitions, the definition of common sub-attributes is placed in <<common-sub-attributes>>.
+
 === Obligation Levels and Use-Case Dependency
 
 The attributes defined in this specification are categorized into three obligation levels: Mandatory, Recommended, and Optional.

diff --git a/docs/2___core_attributes.adoc b/docs/2___core_attributes.adoc
diff --git a/docs/3___conformance.adoc b/docs/3___conformance.adoc
@@ -1,4 +1,4 @@
-[[sic-core-conformance]]
+[#sic-core-conformance]
 == Conformance
 
 This specification provides a set of standardized attributes, which other standards that define meta-data and meta-data formats can adopt by claiming conformance.

diff --git a/docs/4___literature.adoc b/docs/4___literature.adoc
@@ -4,3 +4,5 @@
 - [[[PW13]]] Preston-Werner, T. (2013): **Semantic Versioning 2.0.0**.  https://semver.org/spec/v2.0.0.html
 - [[[RFC2119]]] Bradner, S. (1997): **Key words for use in RFCs to Indicate Requirement Levels**. IETF RFC 2119.  https://www.rfc-editor.org/rfc/rfc2119
 - [[[MIC]]] IRT SystemX (2020): **Model Identity Card - Toward a standard to characterize simulation models**. https://mic.irt-systemx.fr
+- [[[CSP]]] prostep ivip (2025): **Credible Simulation Process Framework** in prostep ivip SmartSE Recommendation 2025 PSI 11 V4.0 Part H: https://www.prostep.org/en/medialibrary/detail?ai%5Baction%5D=detail&ai%5Bcontroller%5D=Catalog&ai%5Bd_name%5D=prostep-ivip-smartse-recommendation-2025-psi-11-v-4-0-part-h-credible-simulation-process&ai%5Bd_pos%5D=2
+- [[[SSPLST]]] Modelica Association Project SSP (2025): **SSP Layered Standard Traceability 1.0.0**. https://ssp-standard.org/ssp-ls-traceability/1.0.0/
diff --git a/docs/A___mapping_srmd.adoc b/docs/A___mapping_srmd.adoc
diff --git a/docs/B___basic_subset.adoc b/docs/B___basic_subset.adoc
@@ -0,0 +1,34 @@
+[appendix#basic-subset]
+== Subset of SIC Core for basic usecases (Basic Subset)
+
+The full set of metadata attributes defined in this specification is designed to support a wide range of use cases and functionalities related to simulation activities, including search, analysis, reuse, and traceability.
+However, not all of these attributes may be necessary or relevant for every use case or implementation.
+The information and metadata required depend on the use case.
+Furthermore, the availability of information and metadata may vary across different environments and organizations, especially in early stages of implementation.
+
+To support incremental adoption and implementation, this appendix defines a *basic subset* of the full SIC Core metadata that enables basic functionality for search, analysis, reuse, and traceability.
+
+The basic subset contains sufficient metadata to identify and understand the simulation task, the models and parameters used, and the fulfillment of simulation objectives and quality criteria.
+A key factor for user acceptance is that most of this information can be provided by the used IT systems, or is readily available to users, and does not require significant additional effort to be collected and documented.
+
+This basic subset of SIC core can be used as a starting point in the implementation of metadata for simulation, while allowing easy growth into a more fuller use of the SIC Core metadata as needed and as information becomes available.
+
+See <<sic-core-attributes>> for the actual definition of the attributes in the basic subset, as listed below.
+
+[cols="1>m,2^e,7<",width="100%",align="center",frame="topbot",options="header"]
+|===
+| Attribute Name| Category | Obligation | Description | Typical Source
+| <<Ordering Project,Ordering Project>> | Administrative |  Recommended | Unique name of the ordering project | Project management tool
+| <<Specific Product,Specific Product>> | Administrative |  Recommended | Unique name of the specific product | Project management tool
+| <<Simulation Request,Simulation Request>> | Administrative |  Recommended | Unique name of the Simulation Request | Project management tool
+| <<Simulation Task,Simulation Task>> | Administrative | Mandatory | Unique name of the simulation task | Project management tool
+| <<Item under Test,Item under Test>> | Analysis | Mandatory | System, component, or product being analyzed | Tool / system
+| <<Simulation Objective,Simulation Objective>> | Analysis |  Mandatory | Objective or purpose of the simulation | User
+| <<Quality Criterion,Quality Criterion>> |  Analysis | Recommended | Criteria used to evaluate simulation success | User
+| <<Used Model,Used Model>> | Execution | Mandatory | Model used for the simulation | Tool / system
+| <<Used Parameter,Used Parameter>> | Execution | Mandatory | Parameter used for the simulation | user (selection)
+| <<Used Tool,Used Tool>> | Execution | Mandatory | Tool used for the simulation | Tool / system
+| <<Task Status,Task Status>> | Fulfillment | Mandatory | Is the task still in progress abortet, finished | User
+| <<Quality Fulfilled,Quality Fulfilled>> | Fulfillment | Recommended | Documentation of the quality fulfillment decision | User
+| <<Objectives Fulfilled,Objectives Fulfilled>> | Fulfillment |  Recommended | Documentation of the objectives fulfillment decision  | User
+|===
diff --git a/docs/images/CSP.png b/docs/images/CSP.png
diff --git a/docs/index.adoc b/docs/index.adoc
@@ -25,3 +25,5 @@ include::3___conformance.adoc[]
 include::4___literature.adoc[]
 
 include::A___mapping_srmd.adoc[]
+
+include::B___basic_subset.adoc[]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -25,3 +25,5 @@ include::3___conformance.adoc[]
		include::4___literature.adoc[]

		include::A___mapping_srmd.adoc[]

		include::B___basic_subset.adoc[]