ABCD Payroll Interface

Business Requirements Document

Version <1.0>
ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

Revision History
Date Version Description Author
8/6/2000 1.0 First Draft
 ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

Table of Contents
1. Introduction
1.1 References
1.2 Business Requirements Index

2. Positioning
2.1 Problem Statement

3. Stakeholder and User Descriptions

3.1 Stakeholder and User Summary
3.2 User Environment
3.3 Summary of Key Stakeholder or User Needs
3.4 Alternatives and Competition

4. Product Overview
4.1 Product Perspective
4.2 Assumptions and Dependencies

5. Product Features

6. Other Requirements
 ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

Business Requirements Document

1. Introduction
The purpose of this document is to collect, analyze, and define high-level needs and features of the ABCD Payroll
Interface. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist.
The details of how the ABCD Payroll Interface fulfills these needs are detailed in the use-case and software
requirements specifications.
1.1 References
Type Name Source

1.2 Business Requirements Index

ID Short Description

BRD001 Interface to compute pay

BRD002 Populate ancillary pay grid

BRD003 Capture manual changes for audit purposes

BRD004 Settlement sheet report

BRD005 Means of backing into totaled hours

BRD006 BR for hours computation type

BRD007 BR for hours computation breaks

BRD008 BR for hours pre\post

BRD009 BR for hours OT

BRD010 BR for hours premium

BRD011 Cutoff point and notification

BRD012 Exception- shifts are over 24 hours

BRD013 Exception- shifts are under 2 hours

BRD014 Revenue vs Expense reporting

BRD015 Manual process

2. Positioning
2.1 Problem Statement
The problem of getting ABCD hours into ADP or TMW affects payroll, the terminals, and the drivers at a portion of
our KAGW subsidiary namely those drivers in the PNW the impact of which is efficiency for the terminal and
payroll as well as driver satisfaction to give the legacy Harris drivers and the PNW drivers information based on
 ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

what they require for ensuring their pay is correct. A successful solution would allow the ABCD hours to be
populated based on specific driver\terminal criteria into a format that will allow it to be uploaded into ADP for
payroll processing whether that be via TMW or other means.
3. Stakeholder and User Descriptions
3.1 Stakeholder and User Summary
Name Description Responsibilities Stakeholder

Vice President & Stakeholder

General Manager, PCT
Operations Director Stakeholder

Payroll Manager Stakeholder

Terminal Clerk Terminal clerk at Captures or verifies and manipulates Operations Director
individual terminal hours
responsible for
Turns hours into payroll clerk
payroll hours
reporting to payroll
Payroll Clerk Corporate office Puts hours into ADP Payroll Manager
payroll clerk
working with ADP

3.2 User Environment

Name As-is State Future State

Terminal Clerk PNW- collects manually filled out driver One process- ABCD hours feed ancillary
daily hour sheets and enters this information pay grid based on driver type; this pay
into ancillary pay grid. Adds supplementary grid once populated is static and saved;
pay on approved time sheets from terminal user makes manipulations to the pay grid
manager for Non-driving time, driver based on paper exceptions and finalizes;
meetings, etc. Adds supplementary pay exceptions between first and final pay grid
from separate PTO request form for PTO are approved by Terminal manager and
hours. Turns ancillary pay grid into Payroll turned into payroll clerk
clerk
Harris Legacy- ABCD hours feed TMW;
user launches collect process which pulls in
hours accumulated daily and assigns the
daily hours to the last order number of the
shift; user manually manipulates hours based
on driver submitted, terminal manager
approved exception forms for non-driving
time, holiday, trainee\er, truck transport,
PTO, per diem, etc; hours populate pay audit
report which is then transferred to ancillary
pay grid; user turns ancillary pay grid into
Payroll clerk
Payroll Clerk Uploads ancillary pay grid into ADP Uploads ancillary pay grid into ADP- no
change
 ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

ABCD Collects data from driver\tractor information Collects data from driver\tractor
information- no change
Interface PNW- none Calculates hours by shift based on
subsidiary terminal requirements, add
Harris Legacy- Calculates hours by shift
pre/post based on terminal requirements;
from login/logout time, adds 10 min post
clearly handle multiple login\logout
trip; if driver logs in\out multiple times in a
events during the same shift.
shift driver is paid for hours twice and paid
for post trip twice.

3.3 Summary of Key Stakeholder or User Needs

ABCD start and end times should total hours for the day/shift for each driver taking into account subsidiary/terminal
requirements. These hours need to get from this final state into ADP either direct or indirectly. A portion of the
drivers who will fall under this umbrella are accustomed to receiving settlement sheets documenting their pay by
shift.
ID Business Requirement
BR001 Need interface to use ABCD data to compute pay
BR006 Hours can compute based on the driver’s type 2 and 3. The combinations of these types would define
whether hours are based on login/logout time or driveway to driveway time.
BR007 Driver’s type 2 and 3 would define whether breaks are paid or unpaid. If paid breaks they need to be
broken out of normal hours and captured separately.
BR008 Driver’s type 2 and 3 would define the amount time to be automatically added to the beginning for pre-
trip and to the ending for post-trip.
BR009 Driver’s type 2 and 3 would define whether a driver is paid OT and if so over how many hours.
BR010 If a driver is not paid OT driver’s type 2 and 3 would define whether he get a premium type pay for
hours over 40 (or some other value) top populate a different field in the ancillary pay grid
BR002 ABCD hours will populate an initial ancillary pay grid
BR004 Creation of settlement sheet type report for Legacy Harris drivers to compare their pay\hours to.
BR003 Initial ancillary pay grid created from ABCD hours needs audit controls around the final pay grid sent to
payroll. Pay grid once populated is static and saved, pay grid manipulated by user, exceptions between
first and final pay grid are populated to a report for approval.
BR005 Terminal clerk needs means of backtracking the final hours to ABCD information for the shift.
BR015 Need alternative manual process for use when ABCD outage or issues

3.4 Alternatives and Competition

Workforce payroll solution could use ABCD information to populate their product and feed ADP. This solution is
not yet approved and once approved will not be in Production use for 6-9 months.

Manual hours capture like current PNW terminals could take the place of automation. This would require the
drivers to each fill out a time sheet and get it approved and turned into PNW terminal for collection.
 ABCD Payroll Interface Version: <1.0>
Business Requirements Document Date: 8/6/2000
BRD

4. Product Overview
4.1 Product Perspective
This interface will allow PNW to gain efficiencies in pay capture but still allow them the ability to manually collect
timesheets and compare, adjust hours as deemed necessary. It will alleviate the Harris TMW application and easily
allow Harris to compare, adjust hours as deemed necessary. The addition of an audit control piece will show who
made adjustments to pay outside of ABCD hours. This interface could easily incorporate integration of other
acquisitions using ABCD hours for payroll hours calculations.
4.2 Assumptions and Dependencies
Type Description

Assumption ABCD Data collected

Dependency

5. Product Features
ID Business Requirement
BR011 Terminal clerk can initiate initial pay grid calculations via a report in KAG Reports or a IU whichever is
deemed best by IT. A clear cutoff time will need to be established or notification sent when ready.

6. Other Requirements
ID Requirement
BR014 Revenue vs Expense reporting
BR012 Exception handling- to highlight a field on the ancillary pay grid if shifts are over 24 hours
BR013 Exception handling- to highlight a field on the ancillary pay grid if shifts are under 2 hours