adpa-digital-twin

Guide ADPA Digital Twin architectures for event-driven state changes and asset management.

1|1|Updated Jul 20, 2025
One-click install
npx skills add https://github.com/mdresch/adpa --skill adpa-digital-twin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adpa-digital-twin
Source: https://github.com/mdresch/adpa/tree/main/adpa-digital-twin
Command: npx skills add https://github.com/mdresch/adpa --skill adpa-digital-twin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture and implementation guidance for the ADPA Digital Twin POC. Use when modifying physical assets, event-driven state changes, or trigger rules.

Core Features & Use Cases

  • Clear architectural guidance for event-driven digital twin processing, including asset registration, state snapshots, and trigger evaluation.
  • Defined data schemas and service components to support scalable digital twin implementations.
  • Real-world use cases include monitoring physical assets, reacting to state changes, and generating documents based on triggers.

Quick Start

Configure a digital twin project by defining asset types, event sources, and trigger rules, then deploy the event-driven processing flow.

Frequently Asked Questions about adpa-digital-twin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement event-driven state changes for a digital twin?

Event-driven state changes for a digital twin are implemented by processing external events to update asset state snapshots, evaluating trigger rules, and generating documents without directly writing to the asset state table.

What is the best way to enforce row-level security on digital twin asset tables?

Row-level security on digital twin asset tables is enforced by applying access constraints across all data schemas, ensuring that event-driven state changes and asset management operations adhere to strict platform security boundaries.

Can I use AzureDT and iTwin platforms for digital twin asset management?

AzureDT and iTwin are fully supported platform types for digital twin asset management, alongside a Generic option, allowing you to register physical assets and process state changes across diverse enterprise environments.

How do trigger rules work for document generation in a digital twin architecture?

Trigger rules in a digital twin architecture evaluate event-driven state changes against defined conditions, automatically initiating document generation workflows when specific asset state criteria are met.

Why should I avoid direct writes to the digital twin asset states table?

Direct writes to the digital twin asset states table are prohibited to maintain data integrity, ensuring all state snapshots are captured exclusively through the controlled event-driven processing flow.

What is needed to configure an event-driven digital twin processing flow?

Configuring an event-driven digital twin processing flow requires defining asset types, identifying event sources, and establishing trigger rules to deploy scalable physical asset monitoring and state evaluation.