Less talking, more doing. Let’s build something.
I don’t know a better way to test an idea than building it and see how it performs in the real world.
This project is focused on building a digital twin of a power transformer and make it available to anyone interested in poking at it and giving feedback.
I know it will be a bumpy road but a fun one too.
The PTDT is a project focused on creating a digital model describing the electrical, mechanical, thermal and chemical behaviour of a power transformer.
As much as possible, the algorithms in this model are based in international standards and guidelines from IEEE, IEC, and CIGRE.
This digital twin is fully open source distributed under the MIT license and implemented using the e-lang engineering programming language.
F𝗈𝗋 𝗍𝗁𝗈𝗌𝖾 𝗂𝗇𝗍𝖾𝗋𝖾𝗌𝗍𝖾𝖽 𝗂𝗇 𝖿𝗈𝗅𝗅𝗈𝗐𝗂𝗇𝗀 𝗂𝗍𝗌 𝖼𝗋𝖾𝖺𝗍𝗂𝗈𝗇 𝖺𝗌 𝗂𝗍 𝗁𝖺𝗉𝗉𝖾𝗇𝗌, you can find all the source code on GitHub.
EngineersTools/ptdt: The Power Transformer Digital Twin (github.com)
The best way to visualise, interact and experiment with this digital twin is using a code editor, we suggest using VSCode and installing the e-lang extension.
A digital twin like this has many use cases in asset management, for example:
- failure mode identification
- condition assessment
- root cause analysis
- operational decision-making
All these files are located in the src folder of this repository.
Architecture
𝖲𝗈 … 𝗐𝗁𝖺𝗍 𝖾𝗅𝖾𝗆𝖾𝗇𝗍𝗌 𝗌𝗁𝗈𝗎𝗅𝖽 𝖼𝗈𝗆𝗉𝗋𝗂𝗌𝖾 𝖺 𝖯𝗈𝗐𝖾𝗋 𝖳𝗋𝖺𝗇𝗌𝖿𝗈𝗋𝗆𝖾𝗋 𝖣𝗂𝗀𝗂𝗍𝖺𝗅 𝖳𝗐𝗂𝗇?
𝖳𝗁𝖾𝗋𝖾 𝗂𝗌 𝖺𝗅𝗐𝖺𝗒𝗌 𝗆𝗈𝗋𝖾 𝗍𝗁𝖺𝗇 𝗈𝗇𝖾 𝗐𝖺𝗒 𝗍𝗈 𝖺𝖼𝖼𝗈𝗆𝗉𝗅𝗂𝗌𝗁 𝖺 𝗀𝗈𝖺𝗅, 𝗌𝗈 𝗁𝖾𝗋𝖾 𝗂𝗌 the architecture I am planning to implement for this project.
𝖠𝗍 𝖺 𝗁𝗂𝗀𝗁 𝗅𝖾𝗏𝖾𝗅, 𝖨 𝗍𝗁𝗂𝗇𝗄 𝗐𝖾 𝗇𝖾𝖾𝖽 𝖺𝗍 𝗅𝖾𝖺𝗌𝗍 𝖿𝗈𝗎𝗋 𝗅𝖺𝗒𝖾𝗋𝗌 𝗍𝗈 𝗆𝖺𝗄𝖾 𝗈𝗎𝗋 𝗍𝗐𝗂𝗇 𝗂𝗇𝗍𝖾𝗋𝖺𝖼𝗍 𝗐𝗂𝗍𝗁 𝗍𝗁𝖾 𝖾𝗑𝗍𝖾𝗋𝗇𝖺𝗅 𝗐𝗈𝗋𝗅𝖽:
📝𝖨𝗇𝗀𝖾𝗌𝗍𝗂𝗈𝗇
⚙️𝖬𝗈𝖽𝖾𝗅𝗌
🧮𝖠𝗅𝗀𝗈𝗋𝗂𝗍𝗁𝗆𝗌
📈𝖱𝖾𝗌𝗎𝗅𝗍𝗌
𝖠 𝖻𝗋𝗂𝖾𝖿 𝗌𝗎𝗆𝗆𝖺𝗋𝗒 𝗈𝖿 𝗍𝗁𝖾 𝗋𝖾𝗌𝗉𝗈𝗇𝗌𝗂𝖻𝗂𝗅𝗂𝗍𝗂𝖾𝗌 𝗈𝖿 𝖾𝖺𝖼𝗁 𝗆𝗈𝖽𝗎𝗅𝖾 𝗂𝗌 𝖺𝗌 𝖿𝗈𝗅𝗅𝗈𝗐𝗌.
• 𝖳𝗁𝖾 𝐢𝐧𝐠𝐞𝐬𝐭𝐢𝐨𝐧 𝗅𝖺𝗒𝖾𝗋 𝗁𝖾𝗅𝗉𝗌 𝗎𝗌 𝖺𝖼𝗊𝗎𝗂𝗋𝖾 𝗋𝖺𝗐 𝖽𝖺𝗍𝖺, 𝖼𝗅𝖾𝖺𝗇 𝗂𝗍 𝗎𝗉, 𝗍𝗋𝖺𝗇𝗌𝖿𝗈𝗋𝗆 𝗂𝗍 𝖺𝗌 𝗇𝖾𝖼𝖾𝗌𝗌𝖺𝗋𝗒 𝖺𝗇𝖽 𝗏𝖺𝗅𝗂𝖽𝖺𝗍𝖾 𝗋𝖾𝖺𝖽𝗒 𝗍𝗈 𝖻𝖾 𝖺𝗌𝗌𝗂𝗀𝗇𝖾𝖽 𝗍𝗈 𝗈𝗎𝗋 𝗆𝗈𝖽𝖾𝗅𝗌.
• 𝖳𝗁𝖾 𝐦𝐨𝐝𝐞𝐥𝐬 𝗅𝖺𝗒𝖾𝗋 𝗂𝗌 𝗂𝗇 𝖼𝗁𝖺𝗋𝗀𝖾 𝗈𝖿 𝗉𝗋𝗈𝗏𝗂𝖽𝗂𝗇𝗀 𝖽𝖺𝗍𝖺 𝗌𝗍𝗋𝗎𝖼𝗍𝗎𝗋𝖾𝗌 𝗈𝗋 𝗌𝖼𝗁𝖾𝗆𝖺𝗌 𝖿𝗈𝗋 𝖺𝗅𝗅 𝗍𝗁𝖾 𝖼𝗈𝗆𝗉𝗈𝗇𝖾𝗇𝗍𝗌 𝖺𝗇𝖽 𝗈𝗍𝗁𝖾𝗋 𝗆𝗈𝗋𝖾 𝖺𝖻𝗌𝗍𝗋𝖺𝖼𝗍 𝖼𝗈𝗇𝖼𝖾𝗉𝗍𝗌. 𝖨𝗇𝗌𝗍𝖺𝗇𝖼𝖾𝗌 𝗈𝖿 𝗍𝗁𝖾𝗌𝖾 𝗆𝗈𝖽𝖾𝗅𝗌 𝗐𝗂𝗅𝗅 𝖼𝗈𝗇𝗍𝖺𝗂𝗇 𝗍𝗁𝖾 𝖽𝖺𝗍𝖺 𝗋𝖾𝗉𝗋𝖾𝗌𝖾𝗇𝗍𝗂𝗇𝗀 𝗍𝗁𝖾 𝖼𝗎𝗋𝗋𝖾𝗇𝗍 𝗌𝗍𝖺𝗍𝖾 𝗈𝖿 𝗍𝗁𝖾 𝖺𝗌𝗌𝖾𝗍.
• 𝖳𝗁𝖾 𝐚𝐥𝐠𝐨𝐫𝐢𝐭𝐡𝐦𝐬 𝗅𝖺𝗒𝖾𝗋 𝖼𝗈𝗇𝗍𝖺𝗂𝗇𝗌 𝖺𝗅𝗅 𝗍𝗁𝖾 𝖼𝖺𝗅𝖼𝗎𝗅𝖺𝗍𝗂𝗈𝗇𝗌, 𝖿𝗈𝗋𝗆𝗎𝗅𝖺𝗌, 𝖿𝗎𝗇𝖼𝗍𝗂𝗈𝗇𝗌, 𝗋𝗎𝗅𝖾𝗌 𝖺𝗇𝖽 𝗉𝗋𝗈𝖼𝖾𝖽𝗎𝗋𝖾𝗌 𝗍𝗁𝖺𝗍 𝖽𝖾𝗌𝖼𝗋𝗂𝖻𝖾 𝗍𝗁𝖾 𝖻𝖾𝗁𝖺𝗏𝗂𝗈𝗎𝗋 𝗈𝖿 𝖺 𝗉𝖺𝗋𝗍𝗂𝖼𝗎𝗅𝖺𝗋 𝗎𝗇𝗂𝗍.
• 𝖳𝗁𝖾 𝐫𝐞𝐬𝐮𝐥𝐭𝐬 𝗅𝖺𝗒𝖾𝗋 𝗉𝗋𝖾𝗉𝖺𝗋𝖾𝗌 𝗈𝗎𝗍𝗉𝗎𝗍𝗌 𝗍𝗁𝖺𝗍 𝖼𝖺𝗇 𝖻𝖾 𝖼𝗈𝗇𝗌𝗎𝗆𝖾𝖽 𝖻𝗒 𝖾𝗑𝗍𝖾𝗋𝗇𝖺𝗅 𝗌𝗒𝗌𝗍𝖾𝗆𝗌, 𝗐𝗁𝖾𝗍𝗁𝖾𝗋 𝗂𝗍 𝖻𝖾 𝖺 𝗋𝖾𝗉𝗈𝗋𝗍, 𝖺 𝗏𝗂𝗌𝗎𝖺𝗅𝗂𝗌𝖺𝗍𝗂𝗈𝗇 𝗈𝗋 𝗈𝗍𝗁𝖾𝗋 𝗌𝗈𝖿𝗍𝗐𝖺𝗋𝖾 𝗌𝗒𝗌𝗍𝖾𝗆.
