uPerform implementation roadmap

1. uPerform
Implementation
Architecture?
Authoring
Screen Sensitive
Help
Administration
uPerform
Client
VM
Technical
Design
Linking
Portals
Linking SAP
GUI
Website
Content Copy
User Provisioning
Website Context
Screen
Tab
Custom Transaction
Workflow
setting?
multiple languages?
Individual website
per instance/country/
region?
per language?
SMTP settings?
Per instance?
Author's access? (test
id or user name)
Authored content stored where?
Translation? (occurs
where?)
QA
Staging
Production
Desktop VMs for authoring
Provision authoring VM or clients for all countries?
Client
Installer?
Certified installer
Client Installer delivery to authors
workstations
Configure for multiple
countries in one
instance
linking by SAP Transaction
code
Configure for multiple
countries in one instance?
Folder Structure
Copy content
republish after copy?
incremental content
copy?
Golden copy for
system
Local Content?
Translated Content?
Per instance
How many uPerform instances?
One big beefed up system to support all
system instances?
3 uP instances one per each system
instance?
Bandwidth optimization is not built into
the uPerform application or the
content
uPerform doesn’t have the ability to
cluster the DB or Search servers
eLearning content is not cached
Glossary
First time import
Utilize workflow and/or collaboration with a
N-Region implementation plan?
uPerform Authoring do not work in Windows 2003/Windows
2008 Virtual Machines or Terminal Servers
Publishing
Authors should be able to publish
content by selecting a specific
output from a single template
User ID uPerform authoring is linked to an user ID and it won’t
recognize the IE Sessions if we logged in the system
application with a different login ID
Considerations
Glossary Management
uPerfrom® Implementation Roadmap
Methodology
ANCILE uPerform™, ANCILE uBenchmark™, ANCILE Info Pak™, and ANCILE uLearn™ are trademarks of ANCILESolutions
Operations
Content Management
User Management