REQUEST FOR PROPOSALS

PROFESSIONAL SERVICES FOR

IMPLEMENTATION OF ORACLE HUMAN
CAPITAL MANAGEMENT (HCM) CLOUD
SOLUTION

RELEASE DATE: SEPTEMBER 10, 2020

DUE DATE: OCTOBER 8, 2020 AT 5:00PM

1. INTRODUCTION
The Fayetteville Public Works Commission (hereafter referred to as PWC) is seeking
qualified firms to submit proposals to provide Professional Services for Implementation
of an Oracle Human Capital Management (HCM) Cloud solution.

PWC desires to engage with an experienced vendor that will provide Oracle HCM Cloud
product expertise, project management, system configuration, reporting, integration
development and support to implement a complete solution.

2. BACKGROUND
PWC was created on March 4, 1905, through an act of the state legislature to manage,
operate, and supervise the three utilities – electric, water, and sanitary sewer services.
PWC operates as a public authority owned by the City of Fayetteville and is governed by
four Commissioners appointed by the Fayetteville City Council. PWC serves more than
112,000 customers daily.

PWC has approximately 650 employees across multiple divisions and numerous
departments. The Appendix includes several documents that provide more detail about
the current versions, environments, infrastructure, and integrations between all the HR
relevant applications at PWC.

Between 2014 and 2016, PWC implemented a suite of Oracle applications and updated
several supporting applications, to include E-Business Suite (EBS). The purpose of this
RFP is to transfer the HR related functions from EBS to HCM Cloud.

An enterprise-wide business intelligence application (Sisense) has also been purchased;

however, the design and development has been limited due to ongoing planning efforts
for a full-scale data and analytics program which is currently underway.

3. TERMS AND CONDITIONS

3.1 This document provides general and specific information for use by Vendor(s) in
submitting a proposal to supply PWC with information technology, goods and
services as listed in this RFP in accordance with N.C.G.S. 1436.129.8. We will
select a qualified Vendor with whom we will develop a mutually beneficial
contractual relationship. Our decision to award will be based on our determination
of the proposal that offers the best overall benefit to PWC, considering pricing,
maintenance and support, and any value-added services and other factors
specified herein. PWC reserves the right to reject any or all proposals. Prior to
award of contract, the recommended Vendor shall enter into a Service Agreement
with PWC. A sample Service Agreement is attached.

PAGE 1
3.2 ACCURACY OF RFP AND RELATED DOCUMENTS
PWC assumes no responsibility for conclusions or interpretations derived from
technical and background information presented in the RFP, or otherwise
distributed or made available during the procurement process. In addition, PWC
will not be bound by or be responsible for any explanation, interpretation or
conclusions of this RFP or any documents provided by PWC other than those
given in writing by PWC through the issuance of addenda. In no event may a
Vendor rely on any oral statement by PWC or its agents, advisors or consultants.

3.3 PWC RIGHTS AND OPTIONS

PWC, at its sole discretion, reserves the following rights:
A. To supplement, amend, substitute or otherwise modify the RFP at any
time;
B. To cancel this RFP with or without the substitution of another RFP;
C. To reject any or all proposals produced in response to the RFP; to take
any action affecting this RFP, this RFP process, or the Services or facilities
subject to the RFP that would be in the best interests of PWC;
D. To issue additional requests for information, and/or;
E. To require one or more Vendor(s) to supplement, clarify or provide
additional information for PWC to evaluate the responses submitted.

3.4 EXPENSE OF SUBMITTAL PREPARATION

PWC accepts no liability for the cost and expenses incurred by the Vendor in
response to this RFP, including preparing requests for clarification. Each Vendor
that prepares a Response shall do so at its own expense and with the express
understanding that they cannot make any claims whatsoever for reimbursement
from PWC for the costs and expenses associated with the Response.

3.5 TRADE SECRETS/CONFIDENTIALITY

Upon receipt at PWC, your Response is considered a public record, except for
material which qualifies as “Trade Secret” information under N.C.G.S. 66-152(3).
Your Response will be reviewed by PWC staff and members of the general
public who submit public records request.

THE RESPONDER IS REQUIRED TO IDENTIFY ALL CONTENT DESIGNATED

AS A TRADE SECRET AS DEVINED PURSUANT TO N.C.G.S. 66-152(3) AND
WHICH MEETS THE CRITERIA FOR CONFIDENTIALITY PURSUANT TO
N.C.G.S. 132.1.2(1). ALL NOTED TRADE SECRETS MUST FOLLOW
PROCEDURES NOTED BELOW AND REQUIRE ATTACHED
DOCUMENTATION SPECIFYING HOW THE CONTRENT QUALIFIES AS A
TRADE SECRET UNDER NORTH CAROLINA LAW. IF AN ENTIRE RESPONSE
IS MARKED CONFIDENTIAL OR TRADE SECRET, IT WILL BE DISQUALIFIED
FROM CONSIDERATION.

To properly designate material as “trade secret” under these circumstances,

each Vendor must take the following precautions.

A. Any trade secrets submitted by Vendor should be submitted separately

in a sealed enveloped marked “Trade Secret – Confidential and

PAGE 2
 Proprietary Information – Do Not Disclose Except for the Purpose of
Evaluation this Response”,
B. Offer documentation specifying how the content qualifies as a trade
secret under North Carolina law and
C. The “trade secret” should be stamped on each page of the trade secret
materials contained in the envelope.

4. SCHEDULE AND PROCESS

The following chart shows the schedule of events to prepare your organization’s response.
The key events and deadlines for this process are as follows:

DATE EVENT
9/10/2020 Advertisement of RFP
9/24/2020 Cut-off for Submitted Questions
10/08/2020 Response Submission due by 5:00 p.m. on this date.
10/30/2020 Short list of bidders will present to review team
11/30/2020 PWC anticipates awarding contracts on or before this date
1/11/2021 Vendors are expected to start on or before this date
6/15/2021 Completion date (estimated)

Requests for information or clarification of this RFP must be made in writing and addressed
to Nikole Subject at: nikole.subject@faypwc.com. Questions should reference the topic
number. Vendor shall plainly mark the outside of the sealed envelope with the following
information: SEALED BID: ORACLE HCM CLOUD RFP, Vendor’s name, address,
proposal due date, and time. Communication regarding this RFP via any medium other
than the designated fax number or e-mail address, including phone, personal visits, etc.,
is prohibited.

Vendors shall provide seven (7) copies of the proposal and include a flash drive containing
a PDF version of their complete proposal. PWC will accept sealed proposals until 5:00
PM, October 8, 2020, in the PWC Procurement Office, 1st floor, PWC Administration
Building, 955 Old Wilmington Road, Fayetteville, NC 28301. Proposals received after the
stated date and time will not be considered and will be returned to the Vendor unopened.
Electronic (fax or e-mail) proposals will not be accepted.

5. PROPOSAL CONDITIONS
5.1.1 Cover Letter signed by an authorized individual who commits to the terms and
conditions of the company’s proposal.

5.1.2 Executive Summary, not to exceed two (2) pages. Include a description and
history of the company, services provided and experience specific to requirements
outlined in this RFP.

5.1.3 Statement of Qualifications to demonstrate ability to meet RFP requirements:

PAGE 3
 A. Include a description of office location(s), organizational structure, number
of years in business, and annual revenue.
B. Demonstrate capacity to fully perform all scope requirements, including
experience, reliability, capacity, facilities, equipment, competent
subcontractors, and financial stability.
C. Demonstrate understanding and experience of executing best practices
related to Oracle HCM Cloud implementations.
D. Provide names, qualifications, and percentage of time commitment for staff
or other resources that will be assigned to PWC for this project. PWC
reserves the right to accept or reject any proposed assigned staff or
subcontractor.
E. Provide resumes of project team members, to include subcontractors.
Include time/experience with the Vendor.
F. Provide an organizational chart to demonstrate how the project team fits
within the larger organization.
G. Disclose any litigation you are currently involved in, or have been, within the
past five (5) years in which the Vendor or your partners/subcontractors were
a party.
H. Provide details of how and why your company will best serve the needs of
PWC.

5.1.4 References shall include contact information and project information for three (3)
clients. References should include clients/projects similar in size and scope as
described in this RFP that Vendor has served within the past three (3) years.

5.1.5 Scope of Work that includes a detailed account of how the Vendor will meet the
requirements outlined in the RFP.

5.1.6 Bid Summary Form that includes cost details for the proposed services. Vendor
must also attach a detailed cost explanation for each Bid Summary Form, include
line item detail for all expenses. Provide information on any options not included
in the base fees and expenses.

6. SCOPE OF WORK
The purpose of this project is to implement Oracle’s HCM solution. The overall goal of the
project is to implement Out of the Box functionality as much as possible and take
advantage of new/enhanced functionality that will bring PWC to utility best practice. PWC
intends for this work to be a multi-year, multi-phased project with a stabilization period
between each phase. Listed below are the cloud services of interest to PWC. Vendors
should propose a phased approach and detail how and when the modules should be
implemented to help reach the PWC strategic goal to “attract, retain and engage a top
quality workforce.”

PAGE 4
 Global Human Resources
• Core Human Resources
• Benefits
• Workforce Modeling and Predictions
• Strategic Workforce Planning
• Human Resources Help Desk
• Digital Assistant

Talent Management
• Recruiting
• Onboarding
• Performance Management
• Career Development
• Compensation
• Learning
• Talent Review and Succession Management

Workforce Management
• Absence Management
• Time and Labor
• Workforce Health and Safety

Payroll
• Payroll Cloud Service
• Cash Management (restricted use)
• Fusion Payroll Interface

At minimum, the proposed scope for implementation of each phase must include the following
components:

Project Details
Fit Gap Analysis Conduct fit gap analysis to determine readiness for
implementation of industry best practice; use data to map out
implementation that fits PWC needs (people, process,
technology).
Functional Develop the requirements to implement HCM and leverage the
Implementation enhanced functionality, as well as, influence industry best
practice for PWC business units.
Technical Identify any possible conflicts/enhancements required for the
upgrade and to set benchmarks for post-upgrade performance
targets. Review and determine compatibility of interfaces,
customizations, extensions, and databases.
Integration Review all integrations between systems and identify all changes
required for the implementation.
Environment Review existing environments, to include licensed users,
hardware, operating systems, memory, processors and storage

PAGE 5
 to ensure compatibility with HCM requirements. Review existing
supporting environments required for development, testing, and
training and provide recommendations/requirements.
Deployment
Design, Installation, & Define detailed requirements for the new solution along with the
Configuration initial configuration. Provide on-site solution design and
installation, including leading design meetings. For all design
decisions, the vendor should take advantage of the characteristics
and features within the application framework to minimize
customization. Where possible, move current customizations to
out of the box solution.

Data Migration
1. Analyze existing data and develop recommendation for
data conversion/migration.
2. Develop data Quality Plan.
3. Develop Data Migration Plan.

Custom Code Evaluation

1. Analyze existing code.
2. Determine what code can be eliminated due to out of box
functionality.
3. Determine what code can be eliminated based on
changes to the business process.
4. Migrate all existing code to Oracle Groovy. Provide details
on the data migration strategy and any outsourced
resources and qualifications.

Custom Report Evaluation

1. Review existing reports
2. Determine which reports can be eliminated due to out of
the box functionality or transferred to the enterprise
business intelligence system (Sisense).

Integration Review & Provide technical services related to configuration and interface
Design integration, to include those with third parties. Review all
integration points with the current version & determine if any
require redesign or updates.
Development Working with PWC’s Oracle Development team develop all
required new interfaces or modifications of existing interfaces.
Testing Provide a detailed testing plan for all phases of testing (unit,
system, integration, performance, UAT). Vendor should identify
test environments required to be provided by PWC. Test
scenarios to include, but not be limited to, all impacted
applications, reports, processes and interfaces. Analyze
systemwide impacts of test scenarios on all applications,
processes, and interfaces. Vendor is to work closely with the

PAGE 6
 PWC QA team when developing and executing the plan. Test
scripts must be shared with PWC.

NOTE- Automation is preferred, using OUTA.

User Acceptance Testing Provide test cases/scripts and help facilitate end user testing.
Monitor and track testing statistics. Explain approach to address
failed tests.
Training/ Knowledge Create comprehensive training plan(s). Provide knowledge
Transfer transfer for IT and application support staff which should include
hands on sessions and be staged throughout the project. Provide
training using the train the trainer approach. Provide all training
materials required for end user training to ensure seamless
transition.
Documentation Documentation must cover, at minimum, all installations,
configurations, processes, integrations, testing, training, design
diagrams, and any other material related to the overall project.
Deployment Plan All testing, to include conference room pilots and/or mock go-lives
must be completed and documented. Document any lessons
learned and incorporate all required changes to the Production
Go Live cutover strategy, which should include detailed schedule,
roles/ responsibilities, data capture/entry plan, and rollback
options.
Production Go Live Prior to the Production Go Live cutover, the vendor should
conduct an assessment to ensure infrastructure, environments,
network, desktop, data/database, application, and staff are ready
to transition to production cutover. Migrate to the new solution.
Post Implementation Ensure effective operations of both business and technical
Support solutions. Validate any data exceptions and ensure system errors
are addressed in a timely manner. All defects are to be resolved,
including the coordination of resolutions with third parties. Go
Live deployment warranty period shall be no less than 90 days,
with clearly defined SLAs.

Warranty/Ongoing Support
Warranty Describe any operational services, warranty options, and/or ongoing
technical support options available after the initial warranty period expires
(phone support, remote diagnostics, conferences, etc.).

7. PROJECT REQUIREMENTS
7.1 Within the proposed Statement of Work (SOW), the vendor must provide a full
description of the methodology and approach for meeting scope requirements.

PAGE 7
 A. Detail your implementation plan and timeline to meet scope
requirements as defined in this RFP.
B. Include details on the project approach, including analysis methods and
any input/artifacts required from PWC.
C. The plan should include an assessment/fit gap analysis for each phase
to determine readiness for implementation and use of industry best
practice. This data should include a focus on technical and process-
related tasks to ensure the organizational change management plan is
specific to PWC needs.

7.2 Provide detail on how the project will be managed, to include tasks/responsibilities
of the vendor project manager. At minimum, the vendor project manager will:
A. serve as a single point of contact for project, including the management
of any subcontractor(s)
B. coordinate all activities required to successfully implement the solution
within approved scope, schedule and budget
C. facilitate weekly status meetings to provide updates and share
information
D. maintain detailed work plan, budget, and schedule (changes must be
reviewed and approved by PWC team)
E. provide status reports that will track milestones, schedule, expenses,
and issues

7.3 Define the proposed project implementation team, to include working hours,
location, role, qualifications, and experience. Include staffing, resources, and any
other requirements to be met by PWC. (PWC will provide a Project Manager.)
Planned changes in key vendor resources, such as Project Manager and analysts
must be approved by PWC.

7.4 Describe deliverables provided for each phase of the project.

7.5 Describe change order and issue escalation processes.

7.6 Describe how a comprehensive organizational change management plan will be

developed and implemented to ensure a smooth transition to the new platform.

7.7 Identify issues and challenges PWC should anticipate and indicate how they are
resolved using your approach and services.

8. EVALUATIONS OF PROPOSALS
8.1 All qualified proposals will be reviewed and evaluated. At any time during the
review, PWC may request additional information from the Vendor. Such information
request and Vendor’s response must be in writing. Information may be requested
from sources other than the submitted proposal to evaluate the Vendor.

8.2 Evaluation criteria will include, but will not be limited to:
A. Strength and stability of the Vendor to provide the requested
services
PAGE 8
 B. Experience and success with similar projects of comparable size
and scope
C. Ability to meet the project timeline
D. Overall responsiveness, viability and completeness of the proposal
E. Demonstrated understanding of and ability to meet or exceed
PWC’s specifications
F. Scope of goods/services being proposed
G. Personnel/subcontractor qualifications
H. Cost of proposed goods/services
I. Any other facts considered relevant by the PWC

8.3 PWC reserves the right to select and negotiate with the successful Vendor any
combination of bid line items and options.

PAGE 9
 APPENDIX A – Bid Proposal Summary Notes

1. PWC anticipates awarding contracts by November 2020 with an expected start date no later
than January 2021 for the selected Vendor(s).

2. Prices are firm fixed prices unless otherwise stated and shall be valid for acceptance by PWC
for a period of 120 days from the RFP deadline date.

3. PWC reserves the right to select and negotiate with the successful Vendor(s) any combination
of phases, bid line items, and options. Specifically, PWC may choose to award phases
individually, at different times, and/or different vendors.

4. Vendor must attach a Bid Summary Form, Bid Detail Forms, and Detailed Cost Explanation,
to include cost per module, how price was derived and whether costs are included as base
price or option price.

5. If various service delivery options and/or pricing structures are available, multiple Bid
Summary Forms are allowed. Each should be clearly marked and include all supporting
details/forms.

6. The Vendor shall be subject to PWC travel policies. Travel expenses will be paid on a
reimbursement or per diem basis.

7. PWC will purchase software/licenses based on vendor recommendation. The price does not
need to be indicated on Bid Summary form, but the recommendation must be included on the
Detailed Cost Explanation.

PAGE 10
 APPENDIX B – Bid Summary Form
List expenses for each module by phase – Add lines as needed

Expenses by Phase/Module Base Price Option Total

Phase 1

Subtotal for Phase 1

Phase 2

Subtotal for Phase 2

Phase 3

Subtotal for Phase 3

TOTAL for all Phases

PAGE 11
 APPENDIX C – Bid Detail Form – Phase 1
Detailed Cost Explanation Must be Attached

PHASE 1

List all modules included:

List expenses for each phase by expense category

Expenses Base Price Option Total

IMPLEMENTATION
Software/License Fees NA NA NA
Fit Gap Analysis
Project Planning & Management
Organizational Change Management
Design, Installation & Configuration
Data Conversion/Migration
Integration Review & Design
Development
Testing
Go Live (deployment, cutover plan)
Documentation
Training/Knowledge Transfer
Travel
Other (please define)

POST IMPLEMENTATION
Project Management
Technical Support
Training/Knowledge Transfer
Travel
Warranty
Other (please define)

SUBTOTAL

PAGE 12
 APPENDIX D – Bid Detail Form – Phase 2
Detailed Cost Explanation Must be Attached

PHASE 2

List all modules included:

List expenses for each phase by expense category

Expenses Base Price Option Total

IMPLEMENTATION
Fit Gap Analysis
Project Planning & Management
Organizational Change Management
Design, Installation & Configuration
Data Conversion/Migration
Integration Review & Design
Development
Testing
Go Live (deployment, cutover plan)
Documentation
Training/Knowledge Transfer
Travel
Other (please define)

POST IMPLEMENTATION
Project Management
Technical Support
Training/Knowledge Transfer
Travel
Warranty
Other (please define)

SUBTOTAL

PAGE 13
 APPENDIX E – Bid Detail Form – Phase 3
Detailed Cost Explanation Must be Attached

PHASE 3

List all modules included:

List expenses for each phase by expense category

Expenses Base Price Option Total

IMPLEMENTATION
Fit Gap Analysis
Project Planning & Management
Organizational Change Management
Design, Installation & Configuration
Data Conversion/Migration
Integration Review & Design
Development
Testing
Go Live (deployment, cutover plan)
Documentation
Training/Knowledge Transfer
Travel
Other (please define)

POST IMPLEMENTATION
Project Management
Technical Support
Training/Knowledge Transfer
Travel
Warranty
Other (please define)

SUBTOTAL

PAGE 14
 APPENDIX F – HR Information

Category Detail
Number of Regular Full-time Employees 649
Number of Temporary Employees 11
Number of Positions 659
Number of Grades 35
Number of Departments 61
Number of Supervisory Positions 23
Approximate # of new hires per year 80
Approximate # of transitions each year 53
(promotion, transfer, etc.)
Approximate # of exits each year (retirement, 13 retirements, 38 separations
separations, etc.)
Performance Review Process Performance reviews are conducted
annually based on hire date; three (3) and
six (6) month appraisals are conducted for
new employees
Time entry Employees and/or supervisors enter time in
WAM on daily/weekly basis (customized
integration to EBS for payroll)
Benefits Employees sign up annually; managed
through third party site
Onboarding Manual process
Recruiting Manual process; third party sites used for
job postings
Hiring Internal candidates apply through
iRecruitment; external applicants apply
through PWC website
Payroll Bi-weekly; managed by internal staff

PAGE 15
 APPENDIX G – Oracle E-Business Suite (EBS) Application
Overview

Application Information
Current versions EBS - 12.1.3
DB version – Oracle 12.1.0.2.x
OS version – OL 6.9
# End Users (Approximate) • Employee Self Service – 626 (all active employees)
• iRecruitment Employee Candidate (used for internal
applications only) – 626 (all active employees
• OLM – NA (not used)
• Manager Self Service - 112
Interfaces • WAM/EBS – Supply Chain Interfaces
• WAM/EBS – Finance Interfaces
• WAM/EBS – HR Interfaces
• EBS/CC&B – Finance Interfaces
• Hyperion/EBS – Finance Interfaces
• SOA used for WAM/EBS/CC&B Interfaces
• ODI used for Hyperion/EBS Interfaces
• OBIEE (BI and BIP)
Reports • BI and BIP Reports
• Oracle out of the box reports
• Custom Reports: Up to 15 (HR only)
• Sisense (attendance and hours dashboard)
Active modules in EBS • Human Resources
• iRecruitment (internal applications only)
• Learning Management (active, not used)
• Payroll
• Accounts Receivable
• Accounts Payable
• Fixed Assets
• General Ledger
• iSupplier
• iExpense
• Procurement
• Inventory
Customizations • Opening and closing of work orders in WAM is 100%
customized in regards to meeting financial accounting
entries and reporting
• Customization of SLA in all eBS Finance Modules

PAGE 16
 • Customization of Payroll Costing Process
Physical servers/operating • Production
systems • UAT
Virtual servers/operating • Development
systems • Testing
Load balancing • Yes (clustered environment) Cisco ACE 4710
Current environments • Production
• User Acceptance Testing
• Development
Databases/operating systems • Production-Oracle 11.2.0.3/Oracle Linux 5.8
• Development-Oracle 11.2.0.3/Oracle Linux 5.8
Backup schedule • RMAN every night at 11:45 PM; OS Full 10 PM Friday
Incremental M-S 10 PM File System
# Batches processed daily • Approx. 20 real time interfaces

PAGE 17
APPENDIX H – Oracle E-Business Suite (EBS) Application
Integrations Overview

PAGE 18
 APPENDIX I – Oracle E-Business Suite (EBS) Application
Integrations Detail

Integra Trigger Source Destina Workflow/Functional First/Intitial SOA Composit (or on

tion ID Event tion Destination SOA protocol name)
7 FTPTransf CCB EBS Write-off and build of write-off
er
transactions for AP
23 NA WAM EBS G/L Cost Adjustments(122) NA

26 Not SOA EBS Hyperion Budget

27 Not SOA EBS Hyperion G/L Balance

80 SOA EBS WAM Direct Charge financials from FPWC_EBS_AP_WAM_FMW_46_D

EBS to WAM(PO, invoice, fica) IRECT_CHARGES{3.1}

82 SOA EBS WAM Item Master/Catalog- sends FPWC_EBS_GEN_WAM_FMW_41_

newly created items to WAM ITEM_MASTER_INTERFACE

83 SOA EBS WAM Item On Hand Quantity-synchs FPWC_EBS_GEN_WAM_FMW_42_

on hand quantity ITEM-
ONHAND_QUANTITY_INTERFACE

84 SOA EBS WAM Payroll Actuals FPWC_EBS_GEN_WAM_FMW_83_

PAYROOLL_ACTUALS
85 SOA EBS WAM Creates new employee records FPWC_EBS_HR_WAM_FMW_47_E
in WAM MPLOYEE_DATA_INTERFACE

86 SOA EBS WAM Creates new job title/Crew Rates FPWC_HR_WAM_FMW_48_Crew_

in WAM Craft_INTERFACE
87 SOA EBS WAM Creates timekeeping entries for FPWC_EBS_HR_WAM_FMW_85_L
leave/vacation/sick enties & EAVEDATA_INTERFACE
cancellations
88 SOA EBS WAM Item Org/Storeroom and FPWC_EBS_INV_WAM_FMW_34_I
Average Cost temOrgAndAvgCost
90 SOA EBS WAM Sends new vendors to WAM FPWC_EBS_INV_WAM_FMW_87_
VENDOR_MASTER_INTERFACE

91 SOA EBS CCB Payments taken in EBS EBStoCCBAPDRequestScheduler

transferred to CCB-non utility calls …
billing
92 SOA WAM EBS WO Material Request(Checkout FPWC_WAM_EBS_INV_FMW_43_
Request) MATERIALCHECKOUT_INTERFACE

93 SOA WAM EBS Fixed asset interface-Creates FA FPWC_WAM_FA_EBS_FMW_38_FI

entries in EBS XED)ASSETS_INTERFACE

PAGE 19
Integra Trigger Source Destina Workflow/Functional First/Intitial SOA Composit (or on
tion ID Event tion Destination SOA protocol name)
97 SOA WAM EBS Creates/activates work orders in FPWC_WAM_GEN_FMW_52_WO
the EBS GL string RK_ORDER_SEGEMENT_INTERFAC
E
98 SOA WAM EBS Creates GL entries in EBS- FPWC_WAM_GEN_EBS_FMW_86_
Custom GL OVERHEAD_ALLOCATION_COST_I
interface(LOs,MOs,etc-GL86) NTERFACE

99 SOA WAM EBS creates new Timesheets in WAM FPWC_WAM_HR_EBS_FMW_88_E

MPLOYEE_TIMESHEET_INTERFACE

100 SOA WAM EBS Sends purchase requisition to FPWC_WAM_PO_EBS_FM_44_SER

EBS VICE_REQUISTION_INTERFACE

104 FTPTransf EBS External 401(K) contributions to

er
Prudential
105 FTPTransf EBS External 457 contributions to Nationwide
er

121 FTPTransf EBS External College Savings

er
122 CCB EBS Customer Payment
Settlement(requirement doc
INT_32)
123 SOA EBS CCB Customer Refunds EBStoCCBAPDRequestScheduler
Acknowledgement-check calls
number (NOT coming back) to
CCB from EBS AP(INT 39)
124 SOA EBS CCB Customer Refunds EBStoCCBAPDRequestScheduler
Cancellation(INT_39) calls
127 SOA CCB EBS G/L Entries(requirement doc CCBtoEBSGLRequestScheduler call
INT_31) CCB toEBSGLBPELprocess
134 FTPTransf EBS External Purchasing Power
er
135 FTPTransf EBS External Retirement Contributions to CCBtoEBSAPRRequestScheduler
er
ORBIT calls CCBtoEBSAPBELprocess

136 Manual EBS Hyperion Salary Details file upload

170 SOA CCB EBS Customer refund

PAGE 20
APPENDIX J – Sample Service Agreement

PAGE 21
PAGE 22
PAGE 23
PAGE 24
PAGE 25
PAGE 26
PAGE 27
 APPENDIX K – Vendor Information

Name of Company

Address

Phone No. Fax No.

E-Mail Address

Federal I.D. No.

SDBE, Minority or Woman Owned Business Enterprise Yes No

Bid Submitted By:

(Name Printed)

(Signature)

Title:

Date:

PAGE 28