Conformance
Standards conformance evidence trail. Each claim below is self-attested with citation; items requiring formal third-party attestation are listed separately under "In progress."
Conformance statement (PDF)
Single-page summary of every claim on this page, formatted for procurement. Generated from this page's source.
AAS metamodel
Self-attestedAsset Administration Shell metamodel and serialisation conformance. Updated to V3.1 across the editor, AASX exporter, JSON/XML output, and SDK shapes.
AAS V3.1 metamodel — file-level conformance
Output of /api/v1/extract emits assetIdShort starting with a letter (V3.1 idShort rule, BNF [a-zA-Z][a-zA-Z0-9_-]*; we permit the hyphen at the trailing positions because real-world OEM SKUs depend on it — see Scope notes), AssetInformation.globalAssetId as a simple string (not a Reference), key elements with type+value as child elements (not attributes per V3.1), ConceptDescription with embeddedDataSpecifications (not the deprecated dataSpecifications). All three AssetKind values are supported (Type, Instance, NotApplicable). AAS editor's Fix tool upgrades V3.0 input to V3.1 on import. Note this claim is about the FILE OUTPUT — the create-wizard UI exposes IDTA-template-driven submodels rather than every metamodel knob; deeper SubmodelElement variants (Range, Blob, Entity, Capability, Operation, Event, Relationship, AnnotatedRelationship) are reachable via the editor's right-click context menu, not via the wizard.
AAS V3.1 validation — XSD + AASd-* + official IDTA engine
Output passes THREE gates, not one. (1) The official AAS V3.1 XSD (structure: elements, types, namespace). (2) The AASd-* metamodel constraints the schema cannot express — 33 rule codes enforced in lib/api/aas-constraints.ts (idShort uniqueness + pattern, langString text, reference key types, AssetInformation, value-type conformance, range order, and more). The /api/v1/validate endpoint runs BOTH. (3) In CI, every push to main also runs the official IDTA aas-test-engines against representative fixtures, so 'valid' means valid by the standard owner's reference engine, not only our own checks.
AASX package format
AAS Studio exports AASX zip files containing the AAS as XML inside aasx/ + an OPC origin manifest + relationships file + bundled source PDFs (for AI-extracted AASs) referenced as File submodelElements. Round-trip with AASX Package Explorer is verified for the shipped submodel templates.
IDTA submodel templates
Self-attestedAAS Studio ships 17 IDTA-aligned submodel templates with semantic IDs at the submodel level + ECLASS / IEC-CDD IRDIs at the element level (where catalogued). The four most-used are detailed below; also shipped: Battery Passport (IDTA-02035 series), EU Machinery, CATENA-X (SerialPart / PCF / Traceability), Generic DPP (ESPR), ContactInformation, HierarchicalStructures (BoM), TimeSeries, AssetInterfacesDescription, MaintenanceInstructions, RecyclingAndEndOfLife, and FunctionalSafety.
IDTA-02006 — Digital Nameplate
Submodel emitted with semanticId https://admin-shell.io/idta/nameplate/3/0/Nameplate (IDTA-02006-3-0-1). Core nameplate properties (ManufacturerName, ManufacturerProductDesignation, SerialNumber, YearOfConstruction, DateOfManufacture, hardware/firmware/software versions, CountryOfOrigin, ContactInformation, Markings) carry IEC-CDD primary + ECLASS supplemental semanticIds.
IDTA-02003 — Technical Data
Submodel emitted with semanticId https://admin-shell.io/ZVEI/TechnicalData/Submodel/1/2. GeneralInformation block (Manufacturer, ProductDesignation, ArticleNumber, OrderCode) carries ECLASS IRDIs. TechnicalProperties block carries ECLASS IRDIs auto-attached via the catalog (64+ well-known properties: Payload, Reach, NumberOfAxes, IPRating, Voltage, PerformanceLevel, OPCUASupport, CECertification, etc.)
IDTA-02023 — Carbon Footprint
Submodel emitted with semanticId https://admin-shell.io/idta/CarbonFootprint/CarbonFootprint/1/0 (v1.0). All 4 elements (PCFCO2eq, PCFReferenceValue, PCFQuantityOfMeasure, PCFLifeCyclePhase) carry ECLASS IRDIs.
IDTA-02004 — Handover Documentation
Submodel emitted with semanticId https://admin-shell.io/vdi/2770/1/0/Documentation. 4 elements (Title, Summary, Language, DocumentVersionId) all carry ECLASS IRDIs. Source PDFs are bundled in the AASX zip as File submodelElements.
IEC 63278
Self-attestedConformance to IEC 63278 (AAS for industrial applications) at the metamodel + submodel-template + integration-pattern level.
IEC 63278-1 — AAS metamodel
AAS Studio's metamodel maps to IEC 63278-1 (AAS metamodel and serialisation) via the IDTA AAS V3.1 specification. The two are co-developed; satisfying IDTA AAS V3.1 satisfies IEC 63278-1 by transitive reference.
IEC 63278-2 — Information modelling
Submodel templates use IEC 63278-2-aligned semantic identifiers (eCl@ss IRDIs in 0173-1#02-AAxxx#nnn form for properties, IDTA URIs for submodels). The IRDI catalog (lib/ai/irdi-catalog.ts) covers 64+ properties spanning identity, geometry, electrical, robotics, and lifecycle domains.
IEC 63278-3 — Integration patterns
AAS Studio integrates with IEC 63278-3 patterns via three surfaces: (1) AASX file export — interchange format. (2) Server-side REST API at /api/v1/* with Bearer auth + OpenAPI 3.0 schema — direct integration. (3) Eclipse BaSyx integration guide at /docs/integrations/eclipse-basyx documenting the AAS server pattern.
EU regulatory mappings
Self-attestedPre-built submodel mappings for EU regulations with hard 2027 deadlines.
EU Reg. 2023/1542 — Battery Regulation
Battery Passport AAS template with required carrier elements + the per-regulation TypeScript predicate isBatteryAas() + Python predicate is_battery_aas() in the SDKs. Per-regulation landing page at /battery-passport documents the field mapping.
EU Reg. 2023/1230 — Machinery Regulation
Digital technical file template covering Nameplate + TechnicalData + HandoverDocumentation. SDK predicate isMachineryAas() / is_machinery_aas(). Landing at /eu-machinery-2027 with deadline countdown (2027-01-20).
EU Reg. 2024/1781 — ESPR / Digital Product Passport
Generic DPP template aligned with the ESPR draft delegated acts. Auto-tagged ECLASS IRDIs ensure category-specific delegated acts can layer on top without re-extracting. Predicate isDppAas() / is_dpp_aas() in SDKs.
CATENA-X CX-0006 — SerialPart aspect
SerialPart aspect compatible with CATENA-X dataspace ingestion. ECLASS IRDIs satisfy the CX semantic-ID requirement. Predicate isCatenaXAas() / is_catena_x_aas().
Audit trail + cryptographic evidence
Self-attestedAAS Studio embeds audit-trail evidence inside every extracted AAS — required for regulator-facing scenarios where the question is 'where did this data come from'.
SHA-256 source anchor
Every AI-extracted AAS embeds the SHA-256 of the source PDF as a Property submodel element. The hash matches the bytes the engineer reviewed at certify time, proving the AAS data corresponds to a specific source document.
Engineer certification
The wizard's certify step captures engineer name + initials + UTC timestamp; these are embedded in submodel descriptions. Audit-replay at /studio/library/[id] re-renders the original Review pane with consensus weights, source provenance, and weight-tuner replay — no new LLM calls.
Multi-source provenance
When extraction draws from multiple sources, each field's consensus block records the per-source URLs/files + their authority weight + their value. Disagreements are flagged as needsReview rather than silently merged. Per-regulation auditors can replay the merge with adjusted weights.
Verifiable credentials + signing
Self-attestedBeyond signing the file, AAS Studio can issue the AAS as an EUDI-aligned verifiable credential a third party verifies offline and the issuer can revoke. The combination conformant + signed + EUDI-credential-native is the differentiating trust story for regulator-facing DPP.
Content signing (ES256, non-repudiation)
Extracted AAS content is signed with the tenant's ES256 (ECDSA P-256) key (lib/pki/org-signing-key.ts + aas-signature.ts). A verifier confirms the issuer and that the bytes have not drifted — offline, without the issuer's API key. Algorithm substitution (alg:none) is rejected.
W3C Verifiable Credential (EUDI-aligned)
GET /api/v1/extractions/{id}/credential issues the AAS as a W3C VCDM 2.0 JWT-VC, or an SD-JWT-VC for selective disclosure. POST /api/v1/credentials/verify verifies either, resolving the trust anchor by kid against the public JWKS — the same credential family the EU Digital Identity wallet uses. EUDI trust-list anchoring is an external follow-up.
Credential revocation (Token Status List)
Issue a revocable credential with ?revocable=1; revoke it via POST /api/v1/credentials/status/{id}; a verifier then rejects it (reason: revoked). A 1-bit-per-credential packed status list (IETF oauth-status-list profile) is served publicly for offline checks.
Audit / certification status
In progressItems where we self-attest today and plan to obtain third-party attestation when business case justifies the spend.
IDTA Certified status
Not yet pursued. Estimated cost €20k + 3 months audit cycle. Tracked for Q3 2026 once 3+ enterprise leads request it explicitly.
SOC 2 / FedRAMP attestation
Not yet pursued. Combined cost €40-80k + 4-6 months audit. Tracked for Q4 2026 / 2027 once enterprise pipeline justifies. Self-hosted Docker deployment available today as the alternative for data-residency-constrained customers (see /docs/integrations).
Found a gap? If your procurement requires a claim not on this page, email contact@aas-studio.com — we'll either add it or flag it as out-of-scope. We don't claim attestations we don't have.