This FAQ section is intended solely as a small sample for this exemplary Reference Architecture (RA). In a formal RA document, a FAQ section is typically not included; its presence here is a strategic (mis)use of the format to better illustrate the core ideas and logic of the system.
1. What is CDM?
The Vortex CDM (Cannonical Data Model) represents a standard architectural approach to data modeling through the creation of interim (bridge) objects. These objects serve the integration and conversion between legacy formats and modern systems. While technical data (B2MML) describes the technical state, the CDM provides business context (e.g., Order_ID, SLA_Level), ensuring immediate data readability for financial and strategic systems.
2. Why is CDM necessary for telemetry?
A Point-in-Time Context is ensured through the CDM. Data becomes "self-describing," which allows for stateless processing at the Refinement Gate and achieves independence from constant real-time queries to central databases.
3. How is standard telemetry sent and who packs the UDS packet?
All telemetry is encapsulated into a UDS (Unified Data Structure) envelope. This process is executed at the Vortex Edge level, where raw data is intercepted, translated into B2MML format, supplemented with a Header, and sent to the Site Hub (L4).
4. How is the CDM populated within the UDS packet?
Vortex Edge acts as a contextual orchestrator. Data from the MES (L3) is cached locally and automatically attached to the telemetry at the moment of its generation, forming an unbreakable link between the technical event and the business context.
5. What is "Forked Delivery" and how does it function?
After a command is approved via the DPI Lite mechanism, a delivery fork is performed: the native command is sent directly to L1 for minimal latency, while the B2MML/CDM packet is sent to the UNS as a post-processing record for auditing and analytics.
6. What is the difference between DPI Lite and Full DPI (Vortex Proxy)?
DPI Lite is executed at the Edge level and focuses on verifying the structure and validity of the schema. Full DPI is conducted at the Vortex Proxy and involves deep semantic inspection of the command content along with authorization checks before access to the device is granted.
7. What happens to random JSON data without UDS envelopes?
Such data is treated as noise. Rejection is performed at the source via DPI Lite verification, while the Refinement Gate at the entrance to the corporate L5 acts as a secondary barrier.
8. What if writing is performed directly to the Site Hub (L4), bypassing the Edge?
Access is secured through X.509 certificates and ACL lists on the broker. Should data be successfully written, it is discarded at the Refinement Gate as it cannot pass Master Schema validation.
9. Can a UDS packet exist without B2MML or CDM payload?
Yes. The UDS envelope is modular. In scenarios such as Heartbeat signals or purely business events, a packet may contain only the Header and CDM. The validity of such a packet is determined solely based on the schema version; if the schema defines a payload as optional, the system accepts it as valid.
10. Why is XSD mentioned if JSON is used?
The B2MML XSD represents the industrial source of truth (ISA-95). It is transpiled into a JSON Schema which serves as the execution mechanism for real-time validation, merging standards with modern network performance.
11. How are B2MML and CDM payloads validated by a single schema?
A Master JSON Schema is utilized, which validates the UDS Header, B2MML technical payload, and CDM business payload as a single, coherent entity through a system of references.
12. How is payload content identified without manual mapping?
Programmatic introspection is applied. The schema independently declares its own content, allowing applications to dynamically recognize data types as soon as the schema is loaded from the Registry.
13. Does a vendor need to modify software to assemble UDS packets?
No. The use of the native protocol continues. Communication is transparently intercepted at the Vortex Edge level and encapsulated into the UDS format during "upstream" transmission, while commands arrive at the gateway in their original format.
14. What if the system does not support the B2MML standard?
In such cases, data is mapped into a CDM interim object. This achieves interoperability of specific formats with the Aero-Factory ecosystem without requiring changes to the source code of the vendor's system.