Enterprise resource planning
Connecting business processes and ERP information with operations and assets.
SARAS / TECHNOLOGY IN PRACTICE
From a project schedule to an AI workflow. These are the tools I’ve worked with, the systems I’ve connected, and the things I build with them.
Explore my toolkit ↓I work across scheduling, project controls and reporting, connecting the planning process with the information people need to act.
How the tools relate in my practice01 / THE TOOLKIT
Open a tool for its role and an example. System ownership, hands-on use and training are shown separately.
Build and maintain project schedules, connect dependencies and find the critical path.
Planning and scheduling across industrial project lifecycles.
CV: system ownership and project-controls practice.
Bring schedule and portfolio decisions into a shared planning environment.
Schedule and portfolio management.
CV: system ownership; Oracle training, 2025.
Turn scope into a working schedule with dependencies, milestones and progress.
Project planning and delivery coordination.
CV: named system ownership.
Connect the project pipeline with resource capacity and portfolio priorities.
Portfolio and resource planning.
CV: named system ownership.
Schedule analysis and project-controls work.
Listed in my planning toolkit; a project-specific example is still to be added.
CV: tools and methods.
Resource scheduling and capacity visibility.
Listed in my planning toolkit; a project-specific example is still to be added.
CV: tools and methods.
Connected planning and scenario modelling.
Listed in my planning toolkit; a project-specific example is still to be added.
CV: tools and methods.
Own requirements, setup, governance and training so the team can operate the system independently.
Migrated from Omega PIMS at Quantafuel and trained more than 50 users.
CV: Quantafuel migration and adoption.
Understand the source data and workflows before moving them into Omega365.
The starting system in the Quantafuel migration.
CV and portfolio: PIMS → Omega365.
Connect recurring steps across business applications.
Part of my Power Platform practice and training context.
CV: Power Platform training; tools and methods.
Build business interfaces around a team’s process and data.
Part of my Power Platform practice and training context.
CV: Power Platform training; tools and methods.
Make planning and operational information usable for reporting and executive decisions.
Reporting practice, system ownership and PL-300 certification.
CV: Power BI system owner and certified data analyst.
Work through data, models and recurring reporting tasks, using AI to help with spreadsheet work.
An early step from AI-assisted writing into practical data work.
Portfolio: AI journey, 2022–23.
Give projects a shared place for information, structure and coordination.
Built the BI Startup Hub’s Notion project-management system.
CV: BI Startup Hub; Notion administration.
Structure tasks, ownership and delivery workflows.
Administration training; a project-specific example is still to be added.
CV: Asana admin.
Organise work, project views and team coordination.
Administration training; a project-specific example is still to be added.
CV: ClickUp admin.
Work with issues and team delivery workflows.
Foundational training; a project-specific example is still to be added.
CV: Jira Fundamentals.
Draft reports and text, work through models and explore organisational frameworks.
Started during Digital Business studies in Oslo in 2022.
Portfolio: documented AI journey.
Orchestrate work in VEV, with explicit dependencies and inspectable handoffs.
The orchestrator role in my multi-agent system.
Systems portfolio: VEV.
Research a bounded part of a mission and return findings for the next handoff.
The researcher role in VEV.
Systems portfolio: VEV.
Turn a brief into code, inspect a codebase and verify what was built.
The engineering role in VEV and the environment used to develop this portfolio.
Systems portfolio and this portfolio workspace.
Compose reusable, interactive interfaces from components.
Portfolio interfaces and interactive system explanations.
Portfolio source: React components.
Describe component inputs and data shapes explicitly while building interfaces.
The portfolio’s application source.
Portfolio source: TSX and TypeScript.
Build spatial illustrations that can assemble, unfold and respond to interaction.
The four-world gateway and mechanical experiments in the lab.
Gateway source: sculpture engine and local Three.js modules.
Publish and verify the portfolio, including domain routing and release preservation.
The public portfolio and Systems domain.
Deployment records: September 2026.
Build, preview and publish standalone web experiences.
The four-world gateway and the Works collection.
Site manifests and domain deployment records.
Try a different word or reset the filters.
An evolving record of my practice. Some tools have a documented project story; others are part of my toolkit or training.
02 / THE ENTERPRISE CONTEXT
At the organisation level, the work is about how information moves between systems—and who can use it to make a decision.
Explore my experience ↗Connecting business processes and ERP information with operations and assets.
Bringing asset information into the wider operational picture.
Part of the cross-platform integration work connecting business and plant information.
Coordinating integration between operational technology, business systems and executive reporting.
03 / THE SYSTEMS I’VE BUILT
My own systems give design, agent coordination, learning and delivery a repeatable structure.
I use it to frame the problem, explore a direction and review the experience.
02 / MY SYSTEMSI coordinate specialist agents through dependencies, evidence and human decisions.
03 / MY SYSTEMSI turn outcomes and corrections into bounded, evaluated improvements.
04 / MY SYSTEMSI move from discovery and definition through assembly, review and delivery.
Earlier in this practice: Kontor, a supervised build workshop with separate making, review and acceptance roles.
04 / TAKE IT APART
Unfold a mechanical assembly. Change a shared data model. Explore how evidence affects confidence.
Open the interactive lab ↗