Paybase Kick Off 2019aug02

Paybase Replacement with PeopleSoft
Kick-off meeting
08/02/2019
© 2013 Robert Half International Inc. An Equal Opportunity Employer. All rights reserved. This material is the
confidential property of Robert Half International Inc. Copying or reproducing this material is strictly prohibited.
Last Updated 10/22/2017
Agenda
 Project Charge Code
 Project Delivery
 Overview and Scope
 Detailed Scope
 High Level Project Schedule
 Project Success Criteria
 Scrum Team
 Definition of “Done”
 Sprint Ceremonies
 Next Steps
2 confidential property of Robert Half International Inc. Copying or reproducing this material is strictly prohibited.
Project Code
P - FS Paybase Replacement 2019 • 0004210
Project delivery - Agile & Scrum
 Agile project delivery for ITFS FHCM

 Scrum Team
 Internal Product Owner
 Internal Scrum Master
 Multiple Sprints with 4 weeks each
High Level Scope
 Print Paychecks & Advices directly from PeopleSoft without going through Paybase
 Enable self-service for FSC / Print center to do reprints without IT help
 Maintain/enhance existing audits and reports *
 Give ability for print center users to do their job using PeopleSoft instead of Paybase
 Retire Paybase Application, Terminal Servers, Work Stations
 Retire FTP, Scripts and monitoring of Paybase servers
 Convert old Paybase check & Advice files to be used on new templates for legal
purposes/reprints/audits *
 Testing Advices and Paychecks with Banks
 Archive Advice & Paycheck PDFs to S3 (TBD)
 EIS Scanning/SOX Audit (project statement TBD)
 UAT support
 User Guide
 Training
© 2016 Robert Half International Inc. An Equal Opportunity Employer M/F/Disability/Veteran. All rights reserved.
5 This material is the confidential property of Robert Half International Inc. Copying or reproducing this material is strictly prohibited.
High Level Scope
Program Online
UAT
Changes Changes
EIS Scan
Audits & Conversio
Reports n
Training
Sprint 1 (Pay Check and Advice Changes)
 Program Changes
– Modify Pay and Advice programs to suppress Paybase
data file
– Modify PAYxxx and DDPxxx programs XML to incorporate
Bank Microcode (MICR Line) on checks and advices
– Modify PAYxxx and DDPxxx programs XML to incorporate
Electronic Signature on checks and advices
Design Decision: Are we going to take out-of-the-box

Paycheck or Advice or current RH Paycheck or Advice?
Sprint 2 (Bursting & Printing)
 Bursting
– Validate the PDF created by PeopleSoft delivered processes
(PY_SSP_PRINT) for Pay and Advice files and do necessary
modifications if necessary.
– Create config driven file split to mimic Parse-Split program to create
multiple files based on print center and FSC*
– Create archive process to load batch PDF files to S3 for Audit. Ability
to search during audit and control.
– Autosys and schedule changes
 Printing
– Configure and code to print PDF from PeopleSoft to Print Center
Printers (Proto Type)
Assumption: Individual PDF files for future TCAST in SF is out of scope
Sprint 3 (Usability & Working with Banks)
 Online Pages
– Print Center users to release Pay and Advice files for printing.
Additional information for the user on the file’s value, counts and
overflow.
– Working with Banks
– Work with Banks on the new Paycheck formats and MICR fonts,
Signature etc.
 Conversion
– Create Ad-hoc program to convert Paybase data file to XML so that it can be
used to reprint checks & advices. This includes overflow.
Assumption: No conversion beyond 2010 or manual process to process file from
NAS drive?
Sprint 4 (Reprints and Approval Workflow)
– Print Center Self-Service to re-print Checks and Advices with
approval workflow from FSC leadership (Single or multiple full
file) *
– Audit Controls and approval workflow
– Emails and Email Templates
– FSC Self-Service to re-print Checks and Advices to local printer
for legal purposes
– *** NEEDS TO BE DESIGNED WITH FSC
Sprint 5
(Security, Reports, and Audit)
 Security, Reports & Audits
– Security for IT, FSC and Print Center users
– Remove PayCheck/Advice release role for users if inactive for certain
number of days*?
– Print Center Reports (Employee, Check#, $ Value, Totals by file)
– FSC reports (Parse-Split Report)
– Audit reports on usage, re-prints, file release
– Audit logs to EIS
– *** NEEDS TO BE DESIGNED WITH FSC
UAT & Deployment
 UAT support for X weeks
 Production deployment workplan
 Production deployment
 Retirement of Paybase Servers and related
programs
 Update production support guides
Timeline Updated as of 7/8
FTDD for Sprints 1, 2 and 3
(8/22)
Complete Complete
User User
Story for Story for Warranty,
Sprint 4 Sprint 5 KTLO
UAT &
We are by 9/1 by 9/30 transition
Training
here System starting
Testing of 11/6
Sprint 5 Last 2
(10/01 – Sprints
Sprint 4 10/15) (10/15
(09/16 – -11/5
Sprint 3 Security,
10/15) Onwards)
Sprint 2 (08/16- Reports &
Re-Print
09/15) Audit (SIT, EIS
(07/01- Approval
Sprint 1 Print Checks and Print SCAN)
08/15)
(05/01 – and advices Mechanism
Parse Split via PIA
07/01)
and Burst Conversion
Program with Future
Changes Check View
and Printer Date
Setup Go-Live
Ju
June July August September October November
Project Success Criteria
 Build all the functionality in PeopleSoft to replace Paybase within the budget
 Use of agile concepts to complete the development
 Business is prepared and trained before rollout
 IT support plan is in place before rollout
 Go live with no risky vulnerabilities
Project Team
elle
Mich y
Hue a th
Sain
KK
vas
Srini 1
-
B SA
-2
BSA
Giri e
ipall
Lank
“Done”
The user story is considered “Done” if the

proposed solution for the user story has
been designed, documented, coded, unit
tested and ready for System Testing.
Sprint Ceremonies
o
em
w/D
ng
Pla rint
Re rint
nni
vie
Sp
Sp
Re Bac duct
spe print
me g
um
e
fine klo
nt
ctiv
Sc r
Pro
S
ily
tro
Da
Re
Next Steps
• Create JIRA Project

• Create Scrum Dashboard
• Sprint Planning meeting (3 hours)
• Product Backlog Refinement meeting for Sprint -1 (3 hours)
• Bi-weekly Scrum meetings 15 minutes (Tue- Thur)
• Create a Project Plan
• Weekly Status Report (Hours, Budget etc)
Appendix
Proposed Check & Advice Print Process
Paybase Replacement with delivered PeopleSoft
High Level Benefits:
1. No dependency on external vendor
Current New 2. No licensing and maintenance costs
RTF & XML 3. Ease of usage and support
Checkdraw
Publisher 4. Web-based application and can retire
Terminal Servers
2-Tier application Web based 5. We can use PS delivered workflow to
get approvals (If required)
Custom Reports PS Custom Reports 6. Form changes will not affect the
previous paycheck/advices as they are
Same as stored in XML files
MS 2003 Servers
TCAST/HCM
Option 1 Key Points
XML/PDF Based  5 months implementation & 2 month testing
 Need to get Bank MICR Line
 Electronic Signature is additional effort
Overflow checks  PDF split (based on custom config) before
sending to printers is an additional effort
 If PS online check functionality is utilized, the
Changing Inbuilt PDF checks file will be sent to printer through XML/PDF
(not currently in PRD)
 High Complexity project
Data Format- Ability to expose for  For legal purposes – we should find a way to
XML/PDF self-service print old checks/advices Vs keeping Paybase
for next 6 years
PAY003/DDP003 Effective Dated  Working with Banks to confirm the changes in
check/advice design.
Forms
Printers
Wishlist
- VOID watermark on all re-print checks for legal

Paybase Kick Off 2019aug02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Paybase Kick Off 2019aug02

Uploaded by

Copyright:

Available Formats

Paybase Replacement with PeopleSoft

P - FS Paybase Replacement 2019 • 0004210

 Agile project delivery for ITFS FHCM

Design Decision: Are we going to take out-of-the-box

Assumption: Individual PDF files for future TCAST in SF is out of scope

– *** NEEDS TO BE DESIGNED WITH FSC

– *** NEEDS TO BE DESIGNED WITH FSC

June July August September October November

The user story is considered “Done” if the

• Create JIRA Project

- VOID watermark on all re-print checks for legal

You might also like