Enterprise Security
Audit Logs: Design History Tracking
In precision engineering, understanding the evolution of a design ensures accountability and safety. Edelweis implements Audit Logs as an immutable digital ledger where every modification and approval is timestamped and attributed, satisfying stringent regulatory audits.
1. Anatomy of a Design Audit Trail
We capture a multi-dimensional stream of data tracking interactions between roles and the PDM Vault:
Geometric Mutations
Logging when features are added or modified, linked directly to specific Lead Engineer identities.
Parameter Changes
Tracking shifts in material assignments or Master Modeling variables (e.g., wall thickness).
State Transitions
Permanent record of lifecycle movements (In-Work to Released) with Reviewer digital signatures.
2. Regulatory Compliance & Forensic Utility
| Log Category | Data Captured | Engineering Purpose |
|---|---|---|
| Access Logs | IP, SSO ID, Timestamp. | Detecting unauthorized attempts to view TDP assets. |
| Modification | Pre vs. Post-change values. | Reverting to "Known-Good" states after V&V failures. |
| Approval Logs | Reviewer digital signatures. | Proving Chain of Command during safety audits. |
| Transfer Logs | Encrypted handshake records. | Verifying Vendor receipt of correct revisions. |
3. Integrated Decision Logging
-
•
ECO Linking: Major revisions are linked to unique Engineering Change Orders (ECO) containing technical justification.
-
•
Sim-Driven Changes: Automated tagging linking geometric changes to specific FEA or CFD reports.
-
•
Markup Archiving: Saving all 3D annotations and "Redlines" from live review sessions as part of permanent history.
4. Searchable History & Reporting
-
•
Timeline Visualization: Graphical representation of evolution, showing bursts of activity or design freezes.
-
•
Conflict Reconstruction: Tracing prototype errors back to specific tolerance stack-up or modeling revisions.
-
•
Exportable Audit Reports: Generating Design History Files (DHF) for inclusion in final handover workflows.
Technical Directives
| Directive | Protocol |
|---|---|
| Immutability | Logs are "Append-Only"; no user has permission to edit or delete log entries. |
| Granularity | Logs must capture unique SSO identities; shared "Admin" accounts are prohibited. |
| Retention Policy | Logs are archived with project vaults and maintained for a minimum of 10 years. |