At a glance
- 15
- step end-to-end workflow, intake to closeout
- 9
- procurement paths with written playbooks
- 87
- page comprehensive operating guide
- PIID
- numbering: every action traceable, request to closeout
The problem
Rhode Island Airport Corporation procurement ran as a transactional, email-based function. Five-phase written procedures ended when the executed contract went back to the vendor. Intake, department approval, notice to proceed, and closeout were undocumented. Status visibility depended on individual inboxes: to know where a contract action stood, you asked the person who had it.
What was delivered
- Led the OpenGov procurement platform buildout, moving RIAC to a centralized 15-step end-to-end workflow with exception paths for sole source and emergency actions.
- Designed and implemented a full Procurement Instrument Identifier (PIID) numbering system, assigned at initiation and converted at award, giving every action a traceable record from request through closeout.
- Authored an 87-page Comprehensive Guide with procedure playbooks for all nine procurement paths (its own case study).
- Produced a legacy-to-OpenGov process comparison, threshold and Board-approval rules, and a crosswalk of every legacy procedure to its OpenGov equivalent for Legal review.
- Built bonding and liquidated damages frameworks, vendor open house materials, Power BI reporting, and automation workflows.
- Integrated DocuSign routing through OpenGov for reviewer signatures while preserving CEO wet-signature requirements.
The operating layer
Status now lives in the system instead of in inboxes. Every action carries an identifier from the day it is requested. Every path, including sole source and emergency, has a written procedure that Legal has reviewed. And the signature routing is instructive: reviewers sign electronically, and the CEO still signs on paper, because the workflow bends to the agency’s authority structure, not the other way around.
Why it matters for Munivera
This is the exact pre-work an AI procurement agent needs. Clean procedures, a numbering system, defined thresholds, and a documented workflow are what make automation safe. An agent dropped into email-based procurement automates chaos; an agent dropped onto this operating layer automates a procedure. RIAC is the reference site and the first candidate for a Procurement Intake Agent pilot on top of OpenGov.
Measured before/after figures (intake cycle time, closeout completeness, staff hours reclaimed) are captured in engagement and published only with client approval. Call if you want to walk through the method.