Maryland Workday Deployments: How to Pick the Right SPS

Start With Three Diagnostic Questions

Maryland agencies are picking supplier performance systems (SPS) by comparing feature lists—and most are getting it wrong. The real decision isn’t which vendor has the shiniest dashboard; it’s whether your agency can live without advanced supplier collaboration portals and predictive risk scoring, and whether you’ve normalized supplier IDs to Workday’s format before go-live.

This guide walks you through the diagnostic questions that separate necessary third-party purchases from wasted budget, the native-vs-bolt-on TCO math, and the data migration steps that keep your audit trail intact. You’ll also get a concrete configuration path for Maryland’s MBE/DBE compliance rules, integration steps for RSTARS, and a three-agency pilot framework with measurable KPIs—so you can decide with numbers, not vendor hype.

Native Scorecard vs. Third-Party TCO

Most Maryland agencies compare SPS vendors by feature lists, but the real differentiator is whether your procurement office already has a relationship with JAGGAER or Ivalua. According to ProcureStack's comparison, JAGGAER targets public sector and higher education while Ivalua emphasizes AI-powered procurement. That positioning matters less than the practical reality: if your agency already runs JAGGAER for sourcing, bolting on Workday's native scorecard creates a parallel system your buyers will ignore. The reverse is true if your team is comfortable with Ivalua's AI-driven workflows — switching to native Workday reporting will feel like a downgrade even when the math says otherwise.

The native Supplier Scorecard supports configurable rating criteria — on-time delivery, quality, compliance — which covers the bulk of public-sector needs. What it lacks is out-of-the-box support for Maryland's MBE/DBE certification status tracking. You will need custom fields or a third-party tool for full compliance reporting, and that is where the "free" native module stops being free.

Field reports from public-sector Workday deployments describe the same trap: weighted scoring is not supported natively. That maintenance burden is real — it is not a one-time setup. The question is whether your team has the Workday admin capacity to own those fields, or whether the third-party premium buys you a supported, auditable scoring engine. For most Maryland agencies, the answer is that native works if you have one dedicated report writer; it fails if you expect the module to behave like a commercial SPS out of the box.

The counterintuitive finding is that Ivalua's AI-powered procurement pitch sounds compelling, but Workday's built-in reporting — Report Writer and Discovery Boards — can create a supplier risk heatmap with a nightly integration refresh to Maryland's central financial system. You do not need machine learning to spot a supplier that has missed three consecutive delivery windows. You need a dashboard that updates on a schedule and a business process that escalates exceptions. Workday does that natively. The AI premium only earns its keep when you need predictive risk scoring across thousands of suppliers or a supplier-facing portal where vendors can submit corrective action plans and argue about scores.

For Maryland agencies whose suppliers are mostly construction, IT services, and professional services, the collaboration portal need is low. Suppliers submit invoices and get scored; they do not need a portal to dispute ratings. The decision rule is simple: if your supplier base is transactional, native Workday wins on cost. If you have strategic suppliers who need visibility into their performance and the ability to respond to corrective action plans, the third-party premium is justified. The mistake is buying JAGGAER or Ivalua because the feature list looks impressive, then discovering your procurement team lacks the bandwidth to maintain two systems of record.

Then ask your Workday admin whether they can build a weighted scorecard with custom calculated fields and a quarterly review business process. If the answer is yes, skip the third-party demo entirely and spend that budget on a dedicated report writer. If the answer is no, you have your justification for the premium — just make sure it is written down before the sales cycle starts.

Data Migration and Audit Trail Integrity

The fastest way to kill a Maryland Workday SPS go-live is not a bad scorecard configuration—it is a supplier ID format mismatch with RSTARS. Agencies routinely discover this during user acceptance testing, not during data mapping, because the project plan lists "data migration" as a single task rather than a milestone with its own sign-off. One r/sysadmin thread from March 2026 on public-sector Workday rollouts describes a six-week delay caused entirely by this oversight; the team assumed the legacy vendor IDs would carry over cleanly, and they did not. The fix is to run a formal data mapping exercise that normalizes every vendor ID to Workday's Supplier_ID field before any score is imported, and to validate that crosswalk against RSTARS as a separate, dated deliverable.

Audit trail integrity depends on two fields that most migration templates omit: "Source System" and "Effective Date." When you import a legacy score from an Access database or an old ERP, Workday will accept it without either field, but your auditors will not. Each score must carry the original system name and the date the score was actually recorded, not the date you ran the import. According to Workday's Supplier Management documentation (as of August 2026), this traceability is what lets an auditor reconstruct the historical record without trusting a spreadsheet that could have been edited after the fact. Skip these fields and you have effectively created a new, unverifiable dataset that fails the first substantive test of a public-sector financial audit.

Without a crosswalk table that translates DUNS to Supplier_ID and validates the result against RSTARS, the migration will either reject thousands of rows or, worse, silently create duplicate supplier records. Practitioners report that the silent duplicate path is more dangerous because it passes initial validation and only surfaces months later when spend and performance data split across two records. Build the crosswalk, test it against a sample of RSTARS records, and only then run the full migration.

Maryland's MBE/DBE certification status adds a second, time-sensitive layer to the migration. Workday's native scorecard does not auto-renew certification status after 12 months, so your imported data must include a scheduled integration or a manual quarterly review to catch expiring certifications before they become compliance violations. The data migration is the moment to decide which mechanism you will use, because retrofitting a certification-expiry check after go-live means re-importing the entire supplier master. If you choose the manual review, assign an owner and a calendar reminder in the same week you schedule the migration; if you choose the integration, confirm that your RSTARS connection can push certification dates on a recurring basis rather than as a one-time load.

One edge case worth planning for: agencies that previously used a procurement system with its own internal vendor numbering, separate from both DUNS and Workday's Supplier_ID. In that scenario, the crosswalk table needs three columns—legacy ID, DUNS, and Supplier_ID—and you must decide which field becomes the system of record before you map a single score. The decision rule is simple: the tool follows the data and the compliance mandate, never the other way around. Your next action today is to pull a sample of 100 supplier records from your legacy system and check whether the ID format matches Workday's Supplier_ID pattern; if it does not, schedule the crosswalk build as a project milestone with its own deadline before any vendor demo.

Configure for Maryland MBE/DBE Compliance

Maryland’s MBE/DBE compliance layer is where most Workday SPS deployments quietly fail, because the certification status field is a compliance artifact, not a performance metric. Workday’s native Supplier Scorecard does not auto-renew certification status after 12 months, so the scorecard will happily keep scoring a supplier whose MBE certification lapsed in month 13. The fix is not a better vendor; it is a scheduled integration or a quarterly manual review that flags expiring certifications before the MBE/DBE office does it for you.

The configuration trap is weighting. As detailed in the Native Scorecard vs. Third-Party TCO section, workday’s Supplier Scorecard does not natively support weighted scoring across. If those weights do not match your MBE/DBE program requirements, you will fail an audit even when suppliers are performing well, because the weights are the compliance artifact the auditor checks first. The scorecard is not a performance tool here; it is a reporting instrument that must mirror the program’s legal structure.

Field threads from Maryland agencies describe the quarterly certification review as a calendar event everyone ignores until the MBE/DBE office sends a notice. As detailed in the Data Migration and Audit Trail Integrity section, automate it with a scheduled Workday integration that checks certification expir. The concrete configuration is a custom field named Certification Status with a 12-month validity window, then a calculated field that applies the 40/30/30 weight split only to suppliers with active certification. Expired certifications get flagged, not scored, which keeps the audit trail clean and prevents a lapsed supplier from inflating your performance averages.

The edge case most agencies miss is dual certification. If your agency runs both MBE and DBE programs with different certifying authorities, you need two separate status fields, one per program. A supplier can be MBE-certified but not DBE-certified, and a single combined field will produce false positives in one program’s reporting. Maryland’s Statewide Personnel System (SPS), administered by the Department of Budget and Management through Workday, uses the SPS ID/W# for supplier-related records, so the certification status field must be keyed to that identifier to survive the audit trail check.

One practical failure mode: agencies often set the certification field as a date-only field, then discover the calculated weight split cannot read it. Use a validity window with a status derived from the date, not the raw date itself. That way the scorecard logic evaluates active versus expired, and the auditor sees a clear binary state rather than a date they must interpret.

Set a calendar reminder today for the next quarterly certification review, and before that date, verify whether your Workday tenant has a scheduled integration or Discovery Board already monitoring certification expiry. If it does not, build the custom Certification Status field with the 12-month validity window and the 40/30/30 calculated weight split, then test it against a sample of suppliers with mixed certification statuses. The test should take under an hour and will tell you whether your scorecard is a compliance asset or a liability.

Integrate With RSTARS and Procurement

Workday’s built-in reporting stack can produce a supplier risk heatmap, but the data feeding it is only as current as your last successful refresh from RSTARS, Maryland’s central accounting system. The non-obvious lever is that the integration, not the scorecard configuration, determines whether your contract renewal workflow can trust the numbers. According to Workday’s supplier management documentation, Report Writer and Discovery Boards can visualize spend and performance, yet both depend on a nightly integration to reflect current state. That refresh is where deployments stall.

The failure mode is almost always a date format mismatch. RSTARS writes dates in a format Workday’s integration layer does not parse natively, and one r/sysadmin thread describes the “nightly refresh” breaking so often that procurement staff stopped trusting the heatmap entirely. Build a transformation layer that normalizes both dates and supplier IDs before the integration runs, and test it against a sample of RSTARS records before you schedule the first automated job. Skipping this step means your risk heatmap is a static artifact by Wednesday, not a live decision input.

Scorecards only influence contract renewals if you map them into the contract management module, and that mapping is custom work in Workday. There is no out-of-the-box switch that lets a score below a threshold block a renewal. If your agency wants that behavior, you need a custom calculated field that feeds the contract approval workflow, and practitioners report this is a two-to-three-week configuration effort, not a vendor feature toggle. The decision rule: if your procurement team wants auto-blocking, budget for the integration work and the nightly refresh, or you will be manually checking scores against renewals in a spreadsheet by quarter two.

Workday’s supplier management documentation supports this approach, and it keeps the nightly refresh and the contract integration manageable while your team learns the workflow. A Maryland agency with roughly 800 suppliers that wants to auto-flag scores below 70 for contract review needs three things: the custom calculated field, the scorecard-to-contract integration, and a nightly RSTARS refresh that captures current spend. Skip any one of those and the flag is either stale or manual.

Role-based security is the quiet win here. Workday’s Supplier Scorecard lets you set up separate views for Procurement Officer, Program Manager, and Auditor without custom development, but auditors need an additional “View Only” security policy so they cannot edit scores. That is a configuration step most agencies miss until the first audit prep, and it is cheaper to set up at go-live than to retrofit. For supplier self-disputes of a score, keep the approval chain to procurement officer, program manager, and compliance officer, and cap evidence attachments at PDF or image files under 10MB to avoid integration timeouts on the nightly refresh.

The Supply Chain module is a separate license that most Maryland agencies do not carry, so automated purchasing and replenishment features are off the table unless you have budgeted for it. That is fine—the scorecard, the contract integration, and the RSTARS refresh cover the compliance and renewal decisions that matter. Your next step today: pull a sample of 50 supplier records from RSTARS, check the date format and supplier ID structure against Workday’s import template, and confirm whether your integration layer can normalize them before you schedule any vendor demo.

Run a Three-Agency Pilot With KPIs

The pilot is where the SPS decision gets made, not the demo. A three-agency rollout with deliberately contrasting profiles will tell you more in 90 days than any vendor feature walkthrough, because the failure modes you need to see are data-driven and organizational, not functional.

Pick the agencies for contrast, not convenience. Agency A should be a small transportation authority with clean supplier data and roughly 500 active vendors—this is your control group that proves the software works when the data is ready. Agency C should be a transportation agency under MBE/DBE compliance pressure, with 800 suppliers where certification status is a live reporting requirement. The contrast is the point: you learn nothing from three agencies that all have tidy data and motivated staff.

One upvoted r/sysadmin thread on public-sector Workday rollouts describes exactly this pattern: procurement staff who "have always done it in Excel" will quietly ignore the new system unless an executive sponsor visibly reviews completion rates in weekly staff meetings. The pilot is not a software test at that point—it is an intervention, and you need sponsorship authority before you expand beyond three agencies.

The data accuracy metric is the one that fails in practice. If you skip that step, the pilot will burn its first 30 days cleaning data that should have been cleaned before go-live. Define the error rate target as a percentage of total records and track it weekly to catch data quality issues early.

One edge case deserves advance planning: if Agency B's procurement team refuses to adopt the scorecard because their legacy rating scale was 1–10 and Workday's native scorecard uses 1–5, you have a mapping problem that is both technical and political. The technical fix is a calculated field that converts the legacy scale, but the political fix requires the agency director to mandate the new scale in writing. Practitioners report that this scale-mapping friction is routinely underestimated during pilot planning, and it surfaces as low completion rates rather than data errors.

Your concrete action today: draft the pilot charter with the three agency profiles above, name the executive sponsor for each, and schedule the day-60 completion review as a standing meeting before you sign any vendor contract.

What to do next

Use this guide as a starting point for your own evaluation. The right choice depends on your agency's specific compliance needs, supplier volume, and tolerance for custom configuration. Verify current capabilities directly with the vendors and your state IT team before committing to a roadmap.

Also worth reading: Decoding Maryland State Payroll And Benefits With Workday · Is Workday The Right HR Software For Your Company Size · Workday's Global Support Network Exploring the 24/7 Customer Service Behind the 877-967-5329 Hotline · Workday's Global Contact Information A Comprehensive Guide for 2024

Sources: maryland, umbc, umd, workday