Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
200 changes: 200 additions & 0 deletions docs/data.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,200 @@
{
"contributors": [
{
"name": "Abhishek Verma",
"github": "https://github.com/abhishekverma2323",
"skills": [
"python",
"machine learning",
"C/C++",
"sql",
"data analysis"
],
"interests": [
"ai agents",
"nlp",
"real-world ai systems",
"automation"
],
"track": "A: Agent Builders",
"level": 1
},
{
"name": "Amaan Khan",
"github": "amaankhan6828",
"skills": [
"c++",
"python",
"numpy",
"machine learning"
],
"interests": [
"ai agents",
"automation",
"data science",
"real world problem solving"
],
"track": "",
"level": 1
},
{
"name": "Anupaul Saikia",
"github": "Saikia05",
"skills": [
"python",
"SQL",
"C/C++",
"javascript",
"blender",
"fusion 360",
"inventor"
],
"interests": [
"agents",
"3D",
"large-scale machines",
"manufacturing",
"generative design",
"robotics",
"agrotechnology"
],
"track": "",
"level": 1
},
{
"name": "Bassel Mazhar",
"github": "basselmazhar1",
"skills": [
"python",
"javascript"
],
"interests": [
"AI agents",
"LLMs"
],
"track": "",
"level": 1
},
{
"name": "John Ringbert",
"github": "laserkavaj1",
"skills": [
"Networking",
"Cybersecurity",
"Troubleshooting"
],
"interests": [
"F1",
"Soccer",
"Fishing",
"Skiing"
],
"track": "E: QA & Security",
"level": 1
},
{
"name": "Kailash Narayana Prasad",
"github": "KailashNp",
"skills": [
"C++",
"Python",
"Java",
"SQL",
"Cybersecurity (Network Security, Web Security, OWASP Top 10, Vulnerability Assessment, Penetration Testing basics)",
"Cryptography (Encryption/Decryption, Hashing, Digital Signatures, Public Key Infrastructure)",
"Blockchain (Decentralization, Consensus Mechanisms, Smart Contracts basics)",
"Secure Data Storage",
"HTML/CSS",
"Android Development (Kotlin, Jetpack Compose)",
"Git & GitHub",
"Problem Solving",
"Analytical Thinking",
"Technical Troubleshooting",
"Team Collaboration"
],
"interests": [
"AI Agents & Autonomous Systems",
"Agent Security & Adversarial Attacks",
"Cybersecurity & Ethical Hacking",
"Network & Web Security",
"Cryptography & Secure Communication",
"Blockchain & Decentralized Systems",
"Natural Language Processing (NLP)",
"Intelligent Systems & Automation"
],
"track": "E: QA & Security",
"level": 1
},
{
"name": "Vineet Sharma",
"github": "vineetsharma18",
"skills": [
"javascript",
"react",
"MySQL",
"PostgreSQL",
"Next.js",
"C",
"C++",
"html",
"css"
],
"interests": [
"ai",
"agents",
"web dev",
"NLP",
"3D",
"security"
],
"track": "",
"level": 1
},
{
"name": "Yash Maheshwari",
"github": "yashm0910",
"skills": [
"Python",
"FastAPI",
"RAG",
"LLMs",
"Langchain",
"LangGraph",
"Machine Learning",
"NLP",
"SQL",
"Streamlit"
],
"interests": [
"AI systems",
"agent workflows",
"retrieval-augmented generation",
"backend engineering",
"system reliability",
"evaluation and feedback loops"
],
"track": "A: Agent Builders",
"level": 1
},
{
"name": "bhavesh",
"github": "bhavesh4323",
"skills": [
"c++",
"python",
"numpy",
"machine learning",
"mongodb"
],
"interests": [
"ai agents",
"blockchain",
"cryptocurrencies",
"real world problem solving"
],
"track": "A: Agent Builders",
"level": 1
}
],
"generated": true
}
12 changes: 12 additions & 0 deletions submissions/vansh-singhal/HOW_I_DID_IT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
How I Did It – Level 2

What I did, step by step
I cloned the project and opened it in VS Code. Then I ran npm install to install all dependencies, followed by npm run build to compile the project. After that, I executed npm run test-client to verify everything was working, and it ran successfully.

For the LLM setup, I installed Ollama and initially tried running a model, but faced issues. To avoid those problems, I switched to a lightweight model (TinyLlama), which ran smoothly. I tested it with a simple prompt to confirm it was working properly.

What problems I hit and how I solved them
The main issue I faced was while using Ollama. The model I initially tried didn’t run properly on my system, likely due to resource constraints. After identifying this, I switched to a smaller, lightweight model (TinyLlama), which resolved the issue and worked without any errors.

What I learned that I didn’t know before
This task helped me understand the complete project setup workflow—from installing dependencies to building and testing.
107 changes: 107 additions & 0 deletions submissions/vansh-singhal/HOW_I_DID_IT_level3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@

# HOW_I_DID_IT.md => level3

## What I Did, Step by Step

Identified real-world digital twin implementations outside LPI knowledge base

Reviewed the existing LPI case studies to avoid duplication across domains such as aerospace, manufacturing, and generic smart city examples. Focused on selecting implementations that are not commonly cited in standard digital twin literature.

Selected 3 domains with distinct characteristics: urban governance (Chennai), transport infrastructure (Aachen), and renewable energy optimization (GE Wind Farm). This ensured diversity in system scale, data complexity, and application outcomes.

Researched Chennai Smart City Digital Twin

Source: Public reports and news coverage on Chennai’s AI-based urban digital twin initiative
Focused on flood prediction and traffic congestion as core use cases
Identified challenge (fragmented urban data and reactive disaster management), approach (integration of IoT, GIS, and simulation models), and outcome (predictive flood management and improved coordination)
Mapped to SMILE phases: System Understanding (urban modeling), Measurement (sensor data), Intervention (scenario simulation), Learning (feedback loops), Evolution (urban data observatory)

Researched Aachen City Digital Twin

Source: European urban mobility case study documentation
Focus: transport network optimization and cross-department coordination
Identified challenge (lack of shared infrastructure visibility), approach (city-scale simulation of road networks and traffic), and outcome (improved planning efficiency and congestion reduction)
Mapped to SMILE phases: System Understanding (road network modeling), Measurement (traffic data), Intervention (simulation-based planning), Learning (AI-based congestion prediction), Evolution (institutional integration)

Researched GE Digital Wind Farm

Source: Industry analysis and documented case examples of GE digital twin deployment
Focus: energy output optimization and predictive maintenance
Identified challenge (variability in turbine performance), approach (integration of IoT data with machine learning models), and outcome (increased efficiency and reduced downtime)
Mapped to SMILE phases: System Understanding (turbine modeling), Measurement (telemetry data), Intervention (dynamic configuration), Learning (ML-based prediction), Evolution (continuous optimization)

Analyzed SMILE phase alignment

Created a comparison across all three implementations to identify phase coverage and maturity
Observed that all implementations follow a consistent progression from system modeling to continuous improvement
Identified that none of the systems skip simulation (Intervention phase), confirming its importance in real-world deployments

Cited all sources formally

Used publicly available reports, case studies, and credible publications
Ensured all information used is non-confidential and verifiable
Maintained consistency in describing outcomes and approaches

---

## Problems I Faced and How I Solved Them

Problem 1: Distinguishing digital twin from general smart systems

Many systems labeled as “digital twins” are actually dashboards or IoT monitoring platforms without simulation capability
Solution: Applied strict filtering criteria — system must include (a) virtual model, (b) real-time synchronization, (c) simulation capability, and (d) measurable outcomes
This eliminated several smart city projects that lacked predictive or simulation components

Problem 2: Limited availability of measurable outcomes

Urban and infrastructure projects often report qualitative benefits instead of quantified results
Solution: Prioritized implementations with reported improvements such as congestion reduction, efficiency gains, or predictive accuracy
Where exact metrics were limited, inferred outcomes were validated through multiple sources

Problem 3: Avoiding overlap with common digital twin examples

Many widely cited examples (e.g., aerospace and manufacturing leaders) are already part of standard knowledge bases
Solution: Selected less commonly analyzed but still real and deployed systems such as Chennai and Aachen
This ensured originality while maintaining credibility

Problem 4: Mapping real-world systems to SMILE framework

These implementations were not originally designed using SMILE methodology
Solution: Performed retrospective mapping by analyzing system architecture and lifecycle behavior
Demonstrated that these systems naturally align with SMILE phases despite independent development

---

## What I Learned

Simulation (Intervention phase) is a non-negotiable component

All three implementations rely on simulation before real-world execution
Chennai simulates flood scenarios, Aachen simulates traffic flow, and GE simulates turbine performance
Implication: Digital twins without simulation are incomplete systems

Data integration is the primary bottleneck

Chennai required integration across multiple government departments
Aachen required coordination between infrastructure stakeholders
GE required combining environmental and operational data
Implication: The challenge is organizational and data-related, not purely technical

Continuous learning drives long-term value

Short-term benefits come from modeling and simulation
Long-term value comes from systems that learn and improve over time
GE’s system shows the strongest example of continuous optimization

Explainability is critical for adoption

Decision-makers rely on systems they can interpret and trust
Urban systems require transparency for governance decisions
Industrial systems require explainable outputs for operational reliability
Implication: Explainability must be embedded in decision-support layers

Digital twins follow a consistent lifecycle pattern

All three implementations independently follow a progression similar to SMILE
This suggests that SMILE represents a generalized structure of successful digital twin systems rather than a theoretical framework

70 changes: 70 additions & 0 deletions submissions/vansh-singhal/level2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
# Level 2 Submission - Vansh Singhal

## Tracks Selected
**Track A:** Agent Builders

## LPI Sandbox Execution
```
> npm run build && node dist/test-client.js


> lpi-developer-kit@1.0.0 build
> tsc

=== LPI Sandbox Test Client ===

[LPI Sandbox] Server started — 7 read-only tools available
Connected to LPI Sandbox

Available tools (7):
- smile_overview: Get an overview of the S.M.I.L.E. methodology (Sustainable Methodology for Impac...
- smile_phase_detail: Deep dive into a specific SMILE phase. Returns activities, deliverables, key que...
- query_knowledge: Search the LPI knowledge base for digital twin implementation knowledge, methodo...
- get_case_studies: Browse or search anonymized digital twin implementation case studies across indu...
- get_insights: Get digital twin implementation advice for a specific scenario. Provides scenari...
- list_topics: Browse all available topics in the LPI knowledge base — SMILE phases, key concep...
- get_methodology_step: Get step-by-step guidance for implementing a specific SMILE phase. Returns pract...

[PASS] smile_overview({})
# S.M.I.L.E. — Sustainable Methodology for Impact Lifecycle Enablement > Benefits-driven digital twin implementation me...

[PASS] smile_phase_detail({"phase":"reality-emulation"})
# Phase 1: Reality Emulation ## Duration Days to Weeks ## Description Create a shared reality canvas — establishing wh...

[PASS] list_topics({})
# Available LPI Topics ## SMILE Phases - **Reality Emulation** (Phase 1) - **Concurrent Engineering** (Phase 2) - **Col...

[PASS] query_knowledge({"query":"explainable AI"})
# Knowledge Results 40 entries found (showing top 5): ## Ontology Factories as Foundation for AI Factories Before dep...

[PASS] get_case_studies({})
# Case Studies 10 available: - **Smart Heating for Municipal Schools — Self-Learning Digital Twins** (Smart Buildings ...

[PASS] get_case_studies({"query":"smart buildings"})
# Case Study Results ## Smart Heating for Municipal Schools — Self-Learning Digital Twins **Industry**: Smart Building...

[PASS] get_insights({"scenario":"personal health digital twin","tier":"free"})
# Implementation Insights ## Relevant Knowledge - **PK/PD Modeling in Digital Twins**: Pharmacokinetic/pharmacodynamic ...

[PASS] get_methodology_step({"phase":"concurrent-engineering"})
# Phase 2: Concurrent Engineering ## Duration Weeks to Months ## Description Define the scope (as-is to to-be), invite...

=== Results ===
Passed: 8/8
Failed: 0/8

All tools working. Your LPI Sandbox is ready.

```

### Local LLM Output (Ollama - gemma4)
Prompt:
What is a digital twin?

Response:
At its simplest, a digital twin is a virtual representation of a physical object, process, or system.

It is not just a 3D model (like a drawing in CAD software); it is a dynamic, living model that is connected to the real-world object via data. As the physical object changes, the digital twin updates in real-time to reflect those changes.

### Reflection on SMILE
What stood out to me about SMILE is its emphasis on converting personal data into meaningful, actionable insights rather than simply collecting or tracking it. I also found it interesting that it prioritizes understanding the system and its context before diving into data collection. Overall, it comes across as a practical approach to designing systems that not only reflect reality but also contribute to improving it.
Loading
Loading