Expensive models and experiments
PIML can reduce repeated simulation or experimental cost while retaining the governing knowledge used in Computer Science and Business Systems.
Physics-Informed Machine Learning Society
FDP: 25 September 2026
Annual Meeting: 08–09 July 2027
Andhra Pradesh, India
pimlsociety@gmail.com
Computer Science and Business Systems combines software, data engineering, AI and enterprise architecture with operations, finance, supply chains, product management and organizational decision-making. Its distinctive PIML opportunity lies in enterprises whose value is created through physical assets, manufacturing, energy, transport, buildings or infrastructure.
The physical layer and the business layer must remain explicit. Thermodynamics, degradation and material flows are physical; capacity, inventory, service levels, prices and policy are operational or economic constraints. A rigorous system links them without relabelling every business rule as physics.
This page presents ten focused research areas, degree-level project pathways, selected publications and direct support through the PIMLS biweekly members meeting.
This Computer Science and Business Systems guide covers Physics-Informed Neural Networks (PINNs), physics-guided machine learning, scientific machine learning, neural operators, hybrid models and engineering digital twins. Explore the research and project pathways below, then join the Physics-Informed Machine Learning Society to connect with the international PIMLS community.
Use available scientific knowledge to make limited data more useful, transparent and testable.
PIML can reduce repeated simulation or experimental cost while retaining the governing knowledge used in Computer Science and Business Systems.
Learn uncertain parameters, closures or discrepancies around an inspectable mechanistic foundation.
Test whether structured models generalize across geometries, materials, assets, operating regimes or sites.
Use physical residuals, independent measurements, uncertainty and conventional engineering baselines before deployment.
Each card connects a meaningful Computer Science and Business Systems question with suitable scientific knowledge, modelling choices and evidence needed to test it.
Enterprise decisions depend on the state of physical assets. PIML opportunities: Connect validated asset models, telemetry, work orders and decision provenance.
Maintenance timing trades risk, cost and availability. PIML opportunities: Learn degradation residuals and optimize policies under uncertainty.
Tariffs and production plans interact with process physics. PIML opportunities: Co-optimize physical feasibility, emissions, cost and service constraints.
Schedules change thermal, wear and quality states. PIML opportunities: Embed surrogate process models inside robust planning.
Physical disruption propagates through enterprise networks. PIML opportunities: Couple hazard/transport models with inventory and service dynamics.
Design and maintenance choices affect long-term value. PIML opportunities: Propagate physical degradation uncertainty into lifecycle economics.
Claims require traceable material and energy flows. PIML opportunities: Reconcile sensor and enterprise records with mass/energy balances.
Defects emerge from process states and measurement. PIML opportunities: Use process physics with lot, machine and inspection metadata.
Replacement must compare heterogeneous equipment. PIML opportunities: Use calibrated health models and decision-specific uncertainty.
Comfort, energy and occupancy affect operations. PIML opportunities: Use thermal twins with tariffs and facility constraints.
Start with a scope that matches your time, mathematical background, experimental access and expected research contribution.
Learn the foundations with a bounded, measurable system.
A reproducible implementation, clear baselines, a manageable dataset and physically meaningful validation.
Combine an engineering model, substantial data and rigorous comparison.
A thesis-quality study with held-out regimes, mechanistic and data-only baselines, ablation and uncertainty.
Address a publishable methodological, multiscale or deployment research gap.
New methodology or validated engineering insight, multi-regime evidence, reproducible software and journal publications.
Choose one Computer Science and Business Systems question and a measurable engineering output.
State the governing relationships, constraints or validated domain knowledge you will retain.
Build mechanistic and data-only baselines before the hybrid model.
Hold out experiments, conditions, assets, sites or regimes at the deployment level.
Report uncertainty, ablation, limitations, data lineage and reproducible code.
Use this focused reading list to understand the general PIML framework, direct Computer Science and Business Systems evidence and suitable hybrid modelling methods.
Do not list papers only. Compare the engineering question, incorporated knowledge, data, split strategy, baselines, uncertainty and evidence level.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
This source is included in the Computer Science and Business Systems literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
Scientific ML, optimization, trustworthy AI and reproducible research software.
Differential equations, numerical methods, inverse problems and uncertainty.
Instrumentation, data acquisition, state estimation and responsible deployment.
Experiments, calibration, validation evidence and practical expertise for Computer Science and Business Systems.
These answers help students avoid common scope, terminology and validation mistakes.
Use the biweekly meeting form for research guidance.
Request accessNo. Computer Science and Business Systems projects may use physics-guided features, hybrid residual models, differentiable simulators, neural operators, constrained architectures or data assimilation. State exactly what knowledge is incorporated.
Choose one engineering question, a measurable output and a defensible mechanistic baseline. Add learning only where data can identify an uncertainty or discrepancy.
A meaningful question, justified prior knowledge, deployment-level holdouts, strong baselines, ablation, uncertainty, reproducibility and honest limitations.
Simulation can broaden coverage, but simulation-only evidence cannot establish real-system accuracy. Use calibrated experiments, field measurements or trusted independent references appropriate to the claim.
Submit the biweekly members meeting form to discuss your project level, branch, data, model, validation plan and possible collaborators.
Join the biweekly members meeting for project guidance, collaboration and publication planning—or contact the Society directly.
Meeting participation is requested through the Google form. Complete it carefully so the Society can understand your research interest.