Client discussion aid
PoC-to-production approach
PoC Data
Seeded
fake records only
Production Source
ADP WFM
time and activity detail
Middleware
Boomi
orchestration and monitoring
Payroll Target
ADP WFN
gross-to-net remains there
Auth
TBD
SSO / role-based access
Persistence
TBD
production database and audit trail
What this PoC proves
Line-level capture
Supervisors can model availability, uptime, downtime, standard, and quantity instead of working backward later.
Gross pay math
Earned hours, efficiency, incentive hours, and gross earning lines are calculated consistently from source detail.
Seeded reports
Leadership can see line utilization, downtime, efficiency, incentive mix, payroll readiness, and gross pay controls.
Integration visibility
Mock Boomi run history shows where exceptions and payload controls would be monitored.
What production would add
Persistent database
Cards, calculations, approvals, comments, exports, and audit history.
Role-based access
Employee, supervisor, HR/payroll, admin, and reporting permissions.
Payroll controls
Period locks, tie-outs, error handling, retry logic, and export approvals.
Boomi process
Scheduled imports, validated payloads, ADP WFM source mapping, and ADP WFN output mapping.
| Phase | Planning Duration | Client Outcome |
|---|---|---|
| 1. Discovery and rules confirmation | 1-2 weeks | Confirm line-level capture, standards, downtime codes, employee populations, and payroll earning-code mapping. |
| 2. Production build | 3-6 weeks | Persist cards, approvals, calculations, audit trail, reporting, and Boomi-ready APIs. |
| 3. Integration and parallel testing | 2-4 weeks | Boomi moves ADP WFM source data in and ADP WFN gross-pay outputs out; payroll validates parallel runs. |
| 4. Go-live and hypercare | 1-2 pay cycles | Monitor exceptions, payroll controls, supervisor usage, and report accuracy after production launch. |
| Estimate Driver | Why It Matters |
|---|---|
| ADP WFM source readiness | Available APIs/files, approval timing, card detail, and whether standards/activities are extractable. |
| Calculation complexity | Overtime premium treatment, multiple plants, alternate standards, group incentives, and retro corrections. |
| Approval workflow | Whether employee signoff, supervisor approval, HR/payroll review, and audit comments are required. |
| Security model | Employee/supervisor/payroll access, SSO, role rules, and whether external hosting/security review is needed. |
| Reporting depth | Operational KPIs, payroll controls, standard performance, exception trends, and scheduled exports. |
| Parallel payroll testing | Number of pay cycles, plant coverage, exception scenarios, and signoff requirements. |