AI-Powered Fuel Station Auditing POC
A proof-of-concept for a digital solution intended to support fuel-station auditing and compliance monitoring across Saudi Arabia, combining concepts such as AI-assisted inspection and digital-twin-based monitoring within a centralized experience.
My contribution focused on taking the requirements gathered by the team and translating them into an interactive, role-based prototype that made the proposed solution easier to understand, discuss, and validate with stakeholders before moving into implementation.
The Challenge
Making an early technology concept concrete enough to validate.
At the POC stage, the challenge was not simply to document what the system might contain.
The proposed solution combined several operational concepts, including inspection campaigns, stations, criteria, recorded evidence, reporting, claims, and role-based access, within a technology concept involving AI and digital twins.
Before committing to the actual implementation, stakeholders needed a way to see how these pieces would come together as one usable system.
The prototype therefore needed to translate early requirements into something concrete enough to explore, challenge, and refine.
POC Journey
From written requirements to a shared validation reference.
- 01Requirements
- 02Interpretation
- 03Product Structure
- 04Role-Based Journeys
- 05Prototype
- 06Validation
My Contribution
Making the proposed solution visible before it was built.
Interpreted the Requirements as a Connected Product
I reviewed the requirements gathered by the team and translated them from individual features into a connected understanding of the proposed solution.
This meant considering how entities such as inspections, stations, criteria, sessions, reports, and claims relate to each other, rather than designing each screen in isolation.
Structured Role-Based Journeys
Mapped the experience around different user responsibilities and permissions, defining how users would access and interact with the relevant parts of the system.
This helped make the proposed access model and workflows more visible before implementation.
Turned the Concept into an Interactive POC
Designed an interactive prototype that represented key workflows across the proposed platform.
The prototype covered experiences such as creating and managing inspections, organizing inspection sessions, reviewing inspection activity, accessing reports and results, and presenting detailed inspection outcomes and supporting evidence.
The goal was not to simulate the underlying AI or digital-twin technology, but to show how users would experience the solution built around it.
Used the Prototype as a Validation Tool
The prototype was presented to the client to validate the proposed experience before moving forward with implementation.
Having a tangible experience made it easier to discuss workflows, permissions, information structure, and expected system behavior than relying on written requirements alone.
At this stage, the prototype became less of a design artifact and more of a shared decision-making reference.
- Written Requirements
- Interactive Experience
- Stakeholder Discussion
- Validation
Key Deliverables
A POC built to clarify decisions before implementation.
Interactive POC Prototype
Translated early requirements into a navigable representation of the proposed product.
Role-Based User Journeys
Represented how different users would interact with the platform according to their responsibilities and permissions.
Workflow Visualization
Connected inspections, sessions, stations, criteria, reports, and other core concepts into coherent user flows.
Stakeholder Validation Material
Provided a concrete reference for reviewing the proposed solution with the client before implementation.
Skills in Practice
What this POC required from an analysis perspective.
- Requirements Interpretation
- Requirements Analysis
- Solution Modeling
- User Flows
- Role & Permission Analysis
- Information Architecture
- Interactive Prototyping
- Stakeholder Communication
- Requirements Validation
Takeaway
A POC is valuable when it turns assumptions into something people can question.
This project reinforced the value of prototyping early, especially when a solution combines unfamiliar technologies with complex operational workflows.
At that stage, the most useful prototype is not the one that tries to imitate the technology behind the scenes. It is the one that helps stakeholders understand what the system will allow people to do, how information will move, and whether the proposed experience actually makes sense.
For this project, the prototype created that shared reference before implementation began.