Archirodon Procurement Inventory Control System

Behind the Build: Developing the Archirodon Procurement Inventory Control System

In 2010, I had the opportunity to be part of a pivotal project within the EDP (Electronic Data Processing) department of Archirodon, a leading international construction company known for large-scale marine and infrastructure projects. Our goal was to modernize and centralize procurement and inventory operations across multiple project sites—resulting in the development of the Archirodon Procurement Inventory Control System (PICS).

The Need for a Centralized Solution

At the time, Archirodon was facing growing operational complexity as projects expanded across various regions. Procurement processes were semi-manual, inventory tracking was fragmented, and timely data access across departments was challenging. The company needed a tailored, web-based system that could streamline workflows, track materials in real time, and ensure accountability across departments.

My Role in the Project

As a PHP developer, I was part of a small but focused team within the EDP department. Working closely with system analysts and end-users from procurement and warehouse departments, I helped design and develop key modules of the application. Our tech stack included:

  • Frontend and Backend: PHP (custom-built, no frameworks)
  • Database: Microsoft SQL Server (MsSQL)
  • Server Environment: Windows Server (IIS)

My responsibilities covered:

  • Designing and coding core features such as Purchase Requisition, Purchase Order Management, Inventory Tracking, and User Role Management
  • Building dynamic forms and reports with advanced filtering, sorting, and export capabilities
  • Writing SQL queries, stored procedures, and optimizing database calls for better performance
  • Collaborating on user testing, feedback sessions, and iterative updates

Challenges We Overcame

One of the main challenges was ensuring system responsiveness and data integrity across geographically distributed sites with varying internet reliability. We addressed this by:

  • Implementing transaction-based logic to ensure critical data wasn’t lost or duplicated
  • Adding offline-ready features for remote warehouse encoding
  • Designing a modular structure so that future enhancements or regional customizations could be handled efficiently

The Impact of the System

The Archirodon Procurement Inventory Control System greatly improved the company’s ability to manage resources and control costs. Among the tangible outcomes:

  • Reduced procurement processing time by over 30%
  • Improved transparency and accountability across site warehouses
  • Centralized data access enabled real-time reporting and audit trails
  • Enhanced communication between procurement, finance, and logistics teams

Reflections and Lessons Learned

Looking back, this project was more than just a software development task—it was an exercise in understanding operational pain points and solving real-world business problems. Being part of such a critical internal system build early in my career taught me:

  • The value of working closely with end users to understand workflow nuances
  • How to write scalable code even without modern frameworks
  • The importance of documentation, especially when building long-term enterprise systems

Final Thoughts

I’m proud to have contributed to a system that supported a global construction leader like Archirodon. While technology has evolved since then, the core principles—building with purpose, communicating with users, and writing maintainable code—continue to guide my development work today.

If you’ve worked on legacy enterprise systems or are curious how large-scale organizations approach internal software builds, feel free to connect—I’d love to share insights!