Self-attested diversity to SAP + eSourcing: NMSDC/WBENC-validated, filterable firms

Overview

A national construction firm lacked reliable supplier diversity data beyond self-attestations collected during onboarding. Project teams and buyers could not filter for certified firms, reporting to owners was inconsistent, and compliance reviews required manual document hunts. Intelligex implemented a data enrichment and governance layer that pulled third-party certification data into the vendor master, added approval workflows for new or changed designations, and delivered dashboards for sourcing and reporting. Buyers gained trustworthy filters at bid time, certifications and expirations were visible in one place, and diversity reporting used a consistent, auditable set of facts.

Client Profile

• Industry: Commercial construction and infrastructure
• Company size (range): Multi-region general contractor with self-perform and subcontracted trades
• Stage: Established preconstruction, e-sourcing, and vendor onboarding processes
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Estimating and preconstruction, Project management, Legal and compliance, DEI/supplier diversity office, Accounts Payable and Treasury, IT applications

The Challenge

Supplier diversity information lived in scattered forms and spreadsheets. Subcontractors self-attested as diverse during onboarding, but there was no systematic way to verify designations or track expiration dates. Each region kept its own lists, and buyers often relied on informal networks to find certified firms for bids. When public owners or primes requested diversity reports, teams assembled evidence from inboxes and shared drives with varying quality and completeness.

The firm already ran an Enterprise Resource Planning (ERP) platform for vendor master, purchase orders, and payments, along with an e-procurement tool for sourcing events and contract records. Replacing these systems was not an option. What was missing was an authoritative layer for diversity attributes, consistent validation against recognized certifiers, and a simple approval path for new designations or changes. The goal was practical: enrich vendor records with trustworthy data, make it easy for buyers to use, and give compliance teams confidence at audit time.

Why It Was Happening

Self-attestation filled a gap left by fragmented processes. Onboarding forms varied by region and trade, and there was no canonical model for diversity classifications, certification numbers, or expiration dates. Once created, vendor records were rarely updated, and spreadsheets drifted from the truth. When a designation changed, it was reported in an email without a clear owner to verify and publish the update across systems.

Technical constraints reinforced the problem. The ERP allowed diversity fields but they were optional and free-text, the e-procurement tool had its own taxonomy, and neither synchronized with external certifier data. Without a shared state and cadence for validation, data decayed. Buyers had no reliable filters, so sourcing teams did extra work to vet firms late in the process, and reporting often lagged behind actual certifications.

The Solution

Intelligex delivered a supplier diversity enrichment hub that sat on top of the existing ERP and e-procurement tools. The hub normalized diversity classifications, matched suppliers to third-party certification sources, and synchronized validated designations and expirations back to the vendor master. A stewardship workflow handled new or changed designations with document capture and human-in-the-loop approval. Dashboards surfaced certified firms by trade, region, and status so buyers could filter during sourcing, and compliance could produce consistent reports with traceable evidence.

• Integrations: Bi-directional sync with ERP (for example, SAP S/4HANA) for vendor master updates; connectors to the e-procurement platform to expose filters in sourcing; data pulls and reference checks against certifying bodies such as NMSDC, WBENC, and the U.S. Small Business Administration’s HUBZone Program, with optional mapping to transportation projects aligned to the DOT DBE program.
• Canonical diversity model: Standardized classifications (e.g., MBE, WBE, DBE, SBE, SDVOSB, HUBZone) with fields for certifying agency, certification ID, effective and expiration dates, jurisdiction, and document links.
• Matching and enrichment: Supplier identity matched using legal name, tax identifier where permitted, address, and trade; enrichment logic prioritized verified sources and recent certifications.
• Stewardship and approvals: Human-in-the-loop reviews for new or changed designations; required evidence upload; dual review when designations impact public reporting; reason codes and comments captured.
• Workflow and validations: Guardrails to prevent publishing expired certifications; alerts for upcoming expirations; checks for conflicting designations across jurisdictions; soft blocks prompting suppliers to refresh documentation.
• Buyer-facing features: Sourcing filters by certification type, region, and trade; saved lists for project pursuits; exportable vendor packets with current certificates and dates.
• Dashboards: Portfolio view of certified spend pool by trade and region, expiring certifications, newly approved designations, and coverage against project goals.
• Permissions and audit: Role-based access for buyers, compliance, and DEI; immutable logs of evidence, approvals, and publication events; read-only access for auditors and project owners.

Implementation

• Discovery: Mapped vendor onboarding and maintenance flows; inventoried diversity fields in ERP and e-procurement; cataloged current certification types and jurisdictions relevant to the firm’s projects; reviewed reporting obligations for public owners and primes.
• Design: Defined the canonical diversity schema and status glossary; specified matching rules and evidence requirements; designed the approval workflow with escalation for high-visibility projects; established update cadences and event schemas for create, change, and expiration.
• Build: Implemented the enrichment hub and ERP connectors; configured data sources for certifier checks; created buyer-facing filters in the sourcing tool; built dashboards for compliance and DEI; added document capture and secure storage for certificates.
• Testing/QA: Ran enrichment on a sampled vendor set; validated matches with regional teams; exercised expiration alerts and conflict checks; used human-in-the-loop reviews to fine-tune rules and reason codes before publishing to production.
• Rollout: Piloted with a subset of regions and trades; kept existing spreadsheet trackers as a temporary reference; enabled read-only dashboards first, then activated publication back to ERP and sourcing once stakeholders confirmed data quality.
• Training/hand-off: Scenario-based sessions for buyers and compliance analysts; quick guides for evidence review and approvals; supplier communications explaining what designations are accepted and how to refresh documentation; transitioned operations to the DEI and procurement teams with IT support on call.

Results

Buyers could filter reliably for certified firms during preconstruction and sourcing. Diversity designations, certification IDs, and expiration dates appeared consistently in the vendor master and sourcing screens, eliminating guesswork and reducing last-minute scrambles to verify status. Project teams assembled bid lists and vendor packets using current information without toggling between spreadsheets and emails.

Reporting to owners and primes became straightforward. Compliance dashboards reflected the same underlying data that buyers used, with supporting certificates attached and approval history visible. Expirations were monitored centrally, so renewals were requested before status lapsed. Disputes over designation validity dropped because the evidence and decision trail were clear, and auditors could review complete records in a single place.

What Changed for the Team

• Before: Self-attestations lived in forms and shared folders; After: Certifications were validated against trusted sources and stored with evidence in the vendor record.
• Before: Buyers searched ad hoc lists for certified firms; After: Sourcing filters surfaced eligible suppliers by trade, region, and designation.
• Before: Expiration dates were unknown until an issue arose; After: Alerts flagged upcoming expirations and blocked publication of lapsed designations.
• Before: Reporting required manual reconciliation; After: Dashboards pulled from a single, governed data set with attached certificates and approvals.
• Before: Changes arrived via email with unclear ownership; After: A stewardship workflow routed designation updates with reason codes and review.

Key Takeaways

• Treat supplier diversity data as master data: standardize classifications, validate against recognized certifiers, and publish from a single source.
• Make diversity attributes usable by buyers through filters in existing sourcing tools, not stand-alone lists.
• Embed a lightweight approval workflow with evidence capture so designations are trustworthy and auditable.
• Track expirations centrally and alert early to prevent lapses that disrupt sourcing and reporting.
• Roll out in phases by region and trade to build confidence, then expand once enrichment and approvals stabilize.

FAQ

What tools did this integrate with?
The enrichment hub synchronized with the ERP for vendor master attributes and payments and connected to the e-procurement platform to expose diversity filters in sourcing events and contracts. It referenced third-party certification data from organizations such as NMSDC, WBENC, and the SBA HUBZone Program, with optional alignment to DOT DBE requirements for transportation projects.

How did you handle quality control and governance?
We enforced a canonical schema and required evidence for new or changed designations. Human-in-the-loop reviews verified documents, and dual review applied to sensitive changes tied to public reporting. Validations blocked expired or conflicting designations, and every decision carried a reason code with attached evidence and a timestamped audit entry.

How did you roll this out without disruption?
We piloted in select regions and trades while keeping existing trackers as a reference. Dashboards launched first in read-only mode so stakeholders could compare results to known lists. Once data quality met expectations, publication back to ERP and sourcing was enabled, and the spreadsheet path was retired.

Which certifications were supported?
The model supported common classifications such as Minority Business Enterprise (MBE), Women’s Business Enterprise (WBE), Disadvantaged Business Enterprise (DBE), Small Business Enterprise (SBE), Service-Disabled Veteran-Owned Small Business (SDVOSB), and HUBZone. Each designation stored certifying agency, certification ID, jurisdiction, and effective and expiration dates, with links to supporting documents.

How were expirations and renewals managed?
The hub tracked expiration dates and generated alerts to suppliers and internal stewards ahead of lapse. Soft blocks warned buyers when a designation was approaching expiration, and publication of lapsed designations was prevented until renewed documentation was reviewed and approved. Renewals reused prior evidence and routing to minimize cycle time while maintaining governance.