# Maryland Workday Deployments: How to Pick the Right SPS

Paige Thornton · August 4, 2026

> Maryland agencies are picking supplier performance systems (SPS) by comparing feature lists—and most are getting it wrong.

## Start With Three Diagnostic Questions

| Takeaway | Detail |
| --- | --- |
| Workday | As of August 2026, native SPS covers 80% of public-sector needs at half the TCO of JAGGAER/Ivalua for 500–2,000 active suppliers, provided you configure custom weighted fields and a certification-expiry check \| If you skip advanced collaboration portals and predictive risk scoring, native scorecards handle the rest—without bolt-on licensing. |
| Normalize supplier IDs to Workday | s Supplier_ID field before go-live to avoid RSTARS integration failures \| Mismatched vendor ID formats are the #1 pitfall; a data mapping exercise pre-migration prevents audit and payment delays. |
| Configure custom weighted fields for scorecards | 40% on-time delivery, 30% quality, 30% compliance \| Workday lacks native weighted scoring, but calculated fields deliver the same result without third-party spend. |
| Phase in scorecards by spend tier, starting with top 20% of suppliers | Enabling all suppliers at once overwhelms staff; tiered rollout keeps completion rates high and errors low. |
| Pilot success requires >80% scorecard completion and

Canonical: https://zdnetinside.com/blog/maryland_workday_deployments_how_to_pick_the_right_sps.php
Markdown: https://zdnetinside.com/blog/maryland_workday_deployments_how_to_pick_the_right_sps.php/index.md