Project Dossier

Led the architectural evolution of the Periodic Technical Inspection (PTI) platform for the Saudi Standards, Metrology and Quality Organization (SASO). The system was designed to accommodate the population of the Kingdom of Saudi Arabia, providing access for citizens and foreign nationals across varying educational backgrounds and language fluencies.

//System Architecture & Evolution

• ->Monolithic to Headless Migration: The portal, originally built on Drupal, was refactored over a multi-year development cycle into a decoupled, headless system to optimize performance, isolate frontend execution threads, and scale service components.
• ->System Integration: Engineered integration bridges to communicate with internal government databases, enabling dynamic inventory lookups to confirm inspection slot availability based on car types and vehicle license parameters.

//Technical & Operational Solutions

• ->Infrastructural Resilience: Designed state-preservation and transaction-queuing mechanisms to ensure that user registration states, booked slots, and billing records remained synchronous without corrupting database integrity during external payment gateway timeouts.
• ->Operational Logic Adaptations: Modified system workflow logic to handle operational deviations, such as corporate or private drivers acting on behalf of owners, while preserving security and verification parameters.
• ->Accessibility Integration: The interface was designed around clean, semantic iconography and imagery to guide users through the reservation pipeline, reducing textual dependencies to support varying literacy levels in English and Arabic.

//Engineering Notes / Edge Cases

Managed through iSoft; served as the core architect driving the system optimization, API stability, and structural database improvements.

Use Case Case Study: SASO Platform Architectural Evolution

//1. Phase I: Architecture & Inception

• ->The Strategy: Set up the foundational portal infrastructure, designing a secure enterprise configuration.
• ->The Implementation: Selected and tuned the environment to act as an accessible Content Management System (CMS) that met initial requirements while serving as a baseline capable of scaling into transactional operations.

//2. Phase II: Workflow Orchestration & Intelligent Forms

• ->The Strategy: Developed state transitions and workflow logic within the orchestration layer.
• ->The Implementation: Constructed dynamic, data-driven forms that rendered attributes from backend services. Defined the structural API specifications required to support multi-step data ingestion.

//3. Phase III: Two-Way State Synchronization

• ->The Strategy: Configured the integration layer into a two-way state machine to support contactless government services.
• ->The Implementation: Synchronized frontend interaction loops with backend operational workflows. Used unique process identifiers to maintain transaction tracking across application boundaries, ensuring data consistency without client-side session state dependencies.

//4. Phase IV: Frontend Decoupling

• ->The Strategy: Isolated the user interface from backend systems to streamline design and developer iteration.
• ->The Implementation: Decoupled the frontend architecture entirely. This separation insulated the visual presentation layer, allowing for user experience improvements without disrupting core backend integrations.

//5. Phase V: Distributed Server Infrastructure & DevOps

• ->The Strategy: Scaled the physical and cloud infrastructure to handle growing traffic volumes and established environment isolation controls.
• ->The Implementation: Split the single server topology into dedicated, decoupled Database and Web Portal nodes. Established isolated lanes for Staging, Testing, and Preproduction environments. Configured test hosts and automated web deployment scripts.

//6. Phase VI: Technical Governance & Project Orchestration

• ->The Strategy: Streamlined team communication and project management tooling to reflect technical workflow states.
• ->The Implementation: Standardized project terminology, mapped Jira workflows to operational phases, and enforced a release engineering calendar to protect production deployments.