Reference
API Documentation: Custom Automation
Automation is the force multiplier of modern engineering. Edelweis standardizes its automation layer through scripts that interface with PDM Vaults and CAD environments, ensuring custom tools are as robust and traceable as the designs they create.
1. Automation Architecture & Environment
We utilize a multi-language approach for deep system integration and high-speed execution:
Primary Languages
C# (.NET) for heavy system integration; Python for rapid data processing; VBA for legacy support.
Execution Context
Categorized as Client-Side (UI/geometry) or Server-Side (batch PDF/automated Audit Logs).
Object Model Access
Strict adherence to CAD software Object Models ensures forward compatibility with new versions.
2. Custom Macro Categories
| Module | Purpose | Impact |
|---|---|---|
| Batch TDP Generator | Automates Unified TDP creation from assemblies. | Reduces export time by 90%; eliminates naming errors. |
| BOM Sync Engine | Pushes CAD properties to BOM and ERP systems. | Ensures 100% data fidelity between model and procurement. |
| Compliance Auditor | Scans drawings for missing GD&T or title block data. | Acts as automated first-pass review for Engineers. |
| Mass Validator | Cross-references material density with model data. | Prevents mass calculation errors before FEA/CFD runs. |
3. Development & Deployment Workflow
-
•
Sandbox Testing: Developed in isolated environments using cloned Private Servers to prevent data corruption.
-
•
Versioned Codebase: Scripts managed in Git with full history tracking, allowing rollbacks and peer reviews.
-
•
The "Silent" Standard: Processes run without human input, supporting high-throughput background automation.
-
•
Error Handling: Robust Try-Catch logic writing directly to project Audit Logs in case of failures.
4. API Security & Access Control
-
•
Token Rotation: Using encrypted, time-limited tokens rather than hardcoded credentials for Cloud API access.
-
•
Execution Logging: Audit Logs distinguish "System Changes" from "User Changes" for automated file modifications.
-
•
Audit Requirement: No macro is deployed to production without formal code audit by a Senior Systems Engineer.
Technical Directives
| Directive | Protocol |
|---|---|
| Hardcoding Ban | Paths, material names, and addresses must be pulled from central config files. |
| Self-Documentation | Every function must include header comments defining Inputs, Outputs, and Dependencies. |
| API Version Lock | Scripts must verify CAD/PDM versions at runtime to prevent execution on unsupported updates. |