Sprint will implement Oracle's PeopleSoft Interaction Hub by May 2016 to provide a self-service portal for employees. The implementation will include a branded portal with minimal customizations on PeopleTools 8.54. Sprint aims to have requirements gathering completed by May 28 and the overall project completed by May 2016 to provide benefits like seamless integration of PeopleSoft applications and enhanced user experiences through collaboration and web 2.0 features.

1. May 2015
ORACLE PEOPLESOFT INTERACTION HUB
KICK-OFF
1
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

2. Agenda
Next Steps
Portal Overview and Features
Portal Release Strategy and Roadmap
Portal Demo
Interaction Hub Overview
Project Timeline
Project Objectives and Scope
Resources
Planned Work Sessions
Content Management Strategy
UI/ Branding Design
Wire Frame Portal Layouts
Security Design/SSO Appr
Navigation/Taxonomy Approach
Integration Strategy
Tab Layout
Pagelet Design
Maintenance
Architecture & Sizing
Governance
Roles and Responsibilities
1
2
3
4
5
6
1
2
3
4
5
6
7
8
9
10
7
8
9
10
11
2
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

3. It serves as the gateway to your enterprise or the rest of the world.
IH is a world-class portal solution with many robust content and
collaborative features.
is part of Oracle's PeopleSoft Enterprise applications, and is part of the
Applications Unlimited program.
ideal for customers wishing to deploy an unlimited number of
communities for their enterprise,
it is especially well suited for unifying the PeopleSoft Enterprise
Application user experience and business processes.
What is Oracle’s PeopleSoft Interaction Hub?
Interaction Hub Overview
3
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

4. Sprint will implement the Interaction Hub with a focus on self-service transactions (i.e a self-service portal)
Sprint with deploy a branded Portal with minimal customizations
Sprint with implement Unified Navigation as part of the Self Service Delivery for Sprint’s Portal
Sprint’s IH implementation with be close to vanilla; with IH’s 9.1 application version (Revision 3) and
People Tools 8.54.10
Implement Oracle’s PeopleSoft Interaction Hub by May 2016
Implement PeopleSoft IH on PeopleTools 8.54 by May 2016
Scope and Assumptions
Project Objectives and Benefits
4
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

5. • Seamless and simple integration of PeopleSoft applications content
• Content management
• Web 2.0 and collaboration--at all levels from small groups to the entire Enterprise
There are three main benefits that PeopleSoft IH provides, all of which contribute to an
enhanced experience for your user communities:
Benefits
Interaction Hub Benefits
5
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

6. Timeline | Overview | Resources | Process Flow | Deep Dive
Analyze Phase
6
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

7. Object Mapping: Completed by Friday, April 10
Requirements Gathering: Completed by Friday, May 28
Business Review and Sign Off
Peer Review, Fit/Gap Analysis
Timeline – Complete Phase
May 2015 June 2015 July 2015
5/2 5/9 5/16 5/23 5/30 4/6 4/13 4/20 4/27 5/4 5/11 5/18 5/25
WUT Requirements Gathering and Sign Off
100% Complete by May 2016
Object Mapping
Object Mapping
Review
IUP Upgrade Tasks
May 2015
7
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

8. Object Mapping: Completed by Friday, April 10
Requirements Gathering: Completed by Friday, May 28
Business Review and Sign Off
Peer Review, Fit/Gap Analysis
Timeline - Analyze
March 2015 April 2015 May 2015
3/2 3/9 3/16 3/23 3/30 4/6 4/13 4/20 4/27 5/4 5/11 5/18 5/25
WUT Requirements Gathering and Sign Off
100% Complete by July 30
Object Mapping
Object Mapping
Review
IUP Upgrade Tasks
8
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

9. Plan and complete:
Plan Analyze Design Build Test Deploy
Overview
Develop Workplan
Object Mapping Design business
processes
Build and unit test
application
Prepare
Production
environment
Perform training
Complete
application roll-
out plan
Implement
support
organization
model changes
Payroll Parallel
Test
User acceptance
test
Performance
testing
System Test
Assembly /
Integration test
Refine
customization,
integration and data
conversion design
until complete
Plan testing
Design systems
/ application
components
Design reports,
conversions,
enhancements,
extensions and
forms
Understand
business
requirements
Assess business
processes
Perform a fit/gap
analysis
Create conceptual
design
Refine scope,
timeline and
Workplan
Define high
level requirements
Define scope
Establish team
9
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

10. The Requirements Traceability Matrix (RTM) is a list of detailed
requirements defining how the system needs to work to match
business needs/processes; Each requirement will be classified as a fit or gap
Overview
10
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

11. IH
PS Module
David Adesokan
Resources
Resources
11
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

12. Complete List of Sprint
Modified & Added Objects
Compare
8.9 Sprint
to Vanilla
Online
Application Designer
Objects (Records,
Pages, PeopleCode
App Engine,
etc.)
Batch,
Interfaces,
Reports,
Integrations
Group objects
in work units &
object level
mapping to
customizations
Categorize
work units in 4
dispositions
RETIRE
No FDD/TDD updates
Assess conversion
impacts
Apply disposition at
object level
Update upgrade
scripts
Retrofit
MTP
Source
Create tech design
& build code
Only update FDD/TDD
for conversion
& configuration impacts
No FDD updates; May
require TDD updates
Create/Update FDD, TDD,
and define conversion or
configuration impacts
REPLACE
RETAIN
RE-ENGINEER
Shell
Scripts &
Other
Evaluate
Process Flow
Technical and Development Teams
Step 1 Step 2 Step 3 Step 4 Step 5
Tech Team,Functional Team,
Process owners
Functional &
Technical
Team
Technical and
Development Teams
Collecting inventory of Sprint custom batch and file system objects
Documentation maybe needed for existing customizations that do not have an FDD/TDD
12
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

13. Governance
Wire Frame Portal Layouts
Integration Strategy
Content Management Strategy
Architecture & Sizing
Pagelet Design
Navigation/Taxonomy Approach
Maintenance
Security Design/SSO Appr
UI/ Branding Design
Tab Layout
Planned Work Sessions
13
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

14. Outcome of Sessions
Each work session will drive towards the following outputs
Inputs Analyze Outputs
Re-engineer
Gather requirements
Perform fit/gap analysis
Confirm no dependencies exist
Identify conversion impacts
Validate requirements
Perform fit/gap analysis
Identify conversion impacts
Validate requirements
Replace
Retain
Retire
Customization final
dispositions (MosCow
list)
Existing 8.9 functional
designs
Requirements
Traceability Matrix
(RTM) Template
Knowledge from Sprint
stakeholders and
business users
Updated RTM
Fit/Gap analysis results
RICEFW Inventory
Identify configuration
and conversion impacts
14
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

15. Outcome of Work Sessions
New customizations may require a disposition (re-engineer, replace, retain, retire)
Inputs Analyze Outputs
Define work units
Existing 8.9 functional
designs
Knowledge from Sprint
stakeholders and business
users
Determine if work unit aligns with existing work unit and
confirm disposition is the same
If new work unit, analyze and determine preliminary
recommendation Customization final
disposition
Workshops to review customization and recommendation
with the business to reach final disposition, if necessary
15
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

16. RTM Deep Dive
v9.2 Requirement ID
PeopleSoft Module
Delivered / Custom
Requirement
Requirement Type
Priority
Sprint ID
Business / Process Area
Business Process Owner
Change Mgmt Impacts (Training / Job Aids)
Cross Module Impact
Column Description
Unique identifier (Sprint ID + Number)
PeopleSoft Module
Requirement is for delivered functionality or customization
Business requirement
Application, Business Process, Interface, or Report
Low, Medium, High, Critical
Reference to the Sprint ID used during PWC’s Customization Review in 2014
Business function within a module
Sprint resource responsible for sign off
Describe potential impacts to existing documentation (May apply for Replace or Retains)
Describe potential dependencies with other modules
16
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

17. Step 1: Confirm Analyze Disposition
For any lines where the Disposition does not equal the BDD Disposition, research the
discrepancy and add comments to Disposition Decision
Discrepancies are highlighted in yellow
Put n/a if not applicable
For new work units, Analyze Disposition needs to be determined
Enter the final disposition into Analyze Disposition
Re-engineer
ReplaceRetain
Retire
Updating Guidelines
Analyze
Disposition
17
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

18. Requirements
Gathering Has Begun
10%
15-65% requirement gathering/documentati
70% requirements are ready for peer review
80% requirements ready to be reviewed by business
90% requirements pending approval from business
100% requirements have been approved by business
Updating Guidelines
Step 8: Update the Requirement Status and % Complete
In Progress
Pending Business Approval
Complete
18
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

19. n in progress
Useful Links
SharePoint
19
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

20. http://sprintcommunities.corp.sprint.com/sites/COPS2/espmo/PeopleS
oft%20Project/Forms/AllItems.aspx?View={65186983-146C-412F-
A756-31ED225AF600}
http://sprintcommunities.corp.sprint.com/sites/COPS2/espmo/PeopleS
oft%20Project/Forms/AllItems.aspx?RootFolder=%2Fsites%2FCOPS2
%2Fespmo%2FPeopleSoft%20Project%2FFSCM%209%2E2%20Upg
rade%2F01%2DAnalyze%2F02%2D%20Func%20Team%2F01%2DIn
%20progress
Useful Links
PS Upgrade Home:
RTM:
20
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

21. FAQs
21
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

22. FAQs
No, there is no need to save a new copy after making updates because SharePoint automatically
tracks versions under the same filename.
Should I save a new file every time I make changes?
No, batch timing and scheduling will be updated in existing job docs.
Should batch timing and scheduling requirements be included on the RTM?
Batch processing will be tested as part of Integration Testing.
How will we test batch processing/timing?
22
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

23. Questions
23
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.

24. 24
©2014 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.