Response companion · RFI 6HQOIG-26-A-000X
The map is a database.
The RFI is explicit that these HR workflows do not sit inside the HR directorate. So before writing a response, we modeled them: 46 steps across five Mission Support directorates, scored for friction, every step resolved against the Workday Core HCM business process framework, and running now as a working platform, not a slide.
| Boundary | Crossings | Cost | Status |
|---|---|---|---|
| HR⇄T&TD | 6 | Thrash | |
| B&A⇄HR | 7 | Thrash | |
| B&A⇄T&TD | 4 | Normal | |
| B&A⇄CON | 1 | Normal | |
| CON⇄HR | 2 | Normal |
Live data from the platform’s illustrative model, the same tables an engagement runs on, populated with constructed data.
Why this shape
Three positions most process work does not take
Each is a working feature of the platform, not a methodology slide.
Map by boundary, not by org chart
The unit of analysis is every point where work leaves one directorate and enters another, where cycle time, rework and visibility are actually lost. The platform's home view is the boundary register, ranked by annualized cost.
Boundary registerObserved, not guessed
Every duration carries its evidence: n, range, source, confidence. Practitioner walk-throughs and log exports replace 'about two days.' Where the number is still an estimate, the platform says so and queues the capture.
Capture & evidenceThe model emits the documents
Workday BP worksheets, RACI, SOPs, UAT scripts and the traceability matrix are generated from the same typed model as the maps. Configuration-ready is a file, not a claim.
Generation centerFriction analytics
Six bottleneck signatures, counted
Named, detectable patterns rather than adjectives. Counts computed live from the model.
| Signature | Detection rule | Instances |
|---|---|---|
| Boundary thrash | A single case crosses the same directorate boundary more than twice. Almost always an artifact routed before it was complete. | 9 |
| Serial approval chain | Approvals executed in sequence that carry no dependency on one another. Candidates for parallel routing or outright elimination. | 5 |
| Re-keying | The same data element captured by hand in more than one system. The clearest predictor of data-quality defects in a new HCM tenant. | 12 |
| Shadow step | Work performed in email, spreadsheets or personal trackers with no system of record. Invisible to system-side analysis, and the most common source of surprise at cutover. | 18 |
| Wait-state dominance | Elapsed time exceeds touch time by more than roughly ten to one. The process is not slow because the work is hard, it is slow because it is queued. | 12 |
| Exception as norm | An exception path used in more than about one case in five. The documented process has quietly stopped being the real process. | 10 |
For the contracting officer
Everything the RFI asked for, in one place
The five-page response answers Questions 1 through 9 within the format constraints. The platform carries the working evidence behind it, with a crosswalk from each question to where it is answered.