TIMETOWEB Content Management - PowerPoint PPT Presentation

1 / 33
About This Presentation
Title:

TIMETOWEB Content Management

Description:

TIMETOWEB Content Management TIMETOACT Group Im Mediapark 2, D-50670 Cologne Seite * Seite * – PowerPoint PPT presentation

Number of Views:108
Avg rating:3.0/5.0
Slides: 34
Provided by: EFA51
Category:

less

Transcript and Presenter's Notes

Title: TIMETOWEB Content Management


1
TIMETOWEB Content Management
TIMETOACT Group Im Mediapark 2, D-50670
Cologne
Seite 1
2
CMS or Portal ?
TIMETOWEB Content Management System
  • What kind of portal do you need?
  • Application-Portal
  • Application-Integration Portal
  • Information-Portal

3
Application-Portal
TIMETOWEB Content Management System
  • Application that comes with (free) portal
  • optimized for its own application
  • e.g. SAP HR employee self-services
  • e.g. Facility Management portal
  • usage beyond its own application is limited
  • relatively low cost
  • should most often be implemented
  • TIMETOACT has no experience with application
    portals

Seite 3
4
Application-Integration-Portal I
TIMETOWEB Content Management System
  • Typical strength
  • Application integration in a heterogeneous
    infrastructure (e.g. integrate Siebel CRM with
    custom ERP and SAP financial information system,
    click on a customer name in Siebel-portlet, see
    his backlog in ERP-portlet and his credit line in
    SAP-portlet)
  • Transaction support(e.g. Increase credit line)
  • Single sign-on(e.g. Sign on to CRM and ERP
    simultaneously)
  • Manager Level Users(Managers use many
    applications superficially, i.e. as portlets,
    administrators and clerks use fewer applications
    as fullscreen apps)

Seite 4
5
Application-Integration-Portal II
TIMETOWEB Content Management System
  • Best Application-Integration-Portal is the
    WebSphere-Portal
  • Supports important standards, e.g. JSR-168
    (contrary to SAP)
  • Is clear market leader
  • Comes with usefull add-ons
  • Supported by rapid development tools like portlet
    factory
  • Should be implemented if typical strength is
    required
  • TIMETOACT has good experience with WebSphere
    Portal

Seite 5
6
White Paper Portal-Implemantation I
TIMETOWEB Content Management System
  • InfrastructureOrganization of the portal
    infrastructure, integration of the portal into
    the enterprise infrastructure.
  • UI-Customization Adjustment of the portals user
    interface to the own corporatelayout.
  • WebSphere Portal 6 Features Decision about the
    usage and implementation of WebSphere add-on
    features and alternative products.

7
White Paper Portal-Implemantation II
TIMETOWEB Content Management System
  • OperationImplementation of requirements for the
    production.
  • Application migration Development of a strategy
    and/or several scenarios for the migration and
    integration of existing applications.
  • Pilot-applications Development of criteria and
    identification of applications for the early
    integration into the portal.
  • Portlet-application development Development of a
    strategy and a concept for the development of
    portlets.
  • Shaping of business processes Decision over the
    introduction of IBM WebSphere Process server
    and/or alternative products.

Seite 7
8
White Paper Portet-Development
TIMETOWEB Content Management System
  • The portal selection
  • Portlet development
  • The spring-framework
  • Generic portlet develpment with the JSR168
    portlet API
  • Spring portlet MVC
  • Java Server Faces (JSF)
  • Spring portlet MVC vs. JSF pro and contra
  • Conclusion

9
Information Portal Requirements I
TIMETOWEB Content Management System
  • 100 Corporate Identity
  • Multilingualism
  • Simple content maintenance (inline editing with
    web browser)
  • Performance (sub-second)
  • Management tools
  • Reorganization
  • Monitoring
  • Data integration
  • Lotus Notes, RDBMS, RSS, SAP etc.

10
Information Portal Requirements II
TIMETOWEB Content Management System
  • Content Live Cycle Management, among others
  • Change notifications
  • Check in, check out
  • Approval workflow
  • Follow-up
  • Version management
  • Scheduling (approval, follow-up, revision,
    archiving etc.)

11
Information Portal Requirements III
TIMETOWEB Content Management System
  • Personalization
  • active, passive, hybrid
  • Knowledge management
  • uniform indexing, taxonomy, tagging
  • Feasibility information architecture
  • Effective navigation
  • Corporate structure visualization
  • Creating an overview over existing information

12
Platform Choice
TIMETOWEB Content Management System
Lotus Notes / Domino Portal
Hard- software is available No platform implementation required Established distribution-mechanism (replication) Established user management Usage of existing access rights management Usage of existing administration-skills Usage of existing databases Usage of established processes End-user skills New Hard- software required New platform implementation required ? ? ?
13
Platform Choice Lotus Domino
TIMETOWEB Content Management System
  • Established, proven and mature platform
  • High integration e.g. user administration,
    authorization management, clustering, mail,
    monitoring, replication, scheduling, search, etc.
  • Open platform LEI, LSX, SAP, RDBMS, RSS,
    WebServices, XML etc.
  • Domino 8.5 delivers DXL, DoJo, X-Pages (JSF)
  • High performance, high availability
  • Fast projects, low costs

14
TIMETOWEB CMS Architecture
TIMETOWEB Content Management System
  • Content Modules
  • Collaborative / Web 2.0 Modules
  • Flexible
  • Easily adaptable
  • Very configurable
  • Serves also as a framework for individual web
    applications
  • Optimal integration of existing Notes databases

15
TIMETOWEB Datasource Technology
TIMETOWEB Content Management System
  • Central TIMETOWEB technology
  • Simple integration of legacy data using
    configuration

Seite 15
16
TIMETOWEB Web User Interface
TIMETOWEB Content Management System
  • Intuitive interface
  • Real WYSIWYG
  • Inline editing
  • Fast
  • Uses latest JavaScript framework technology
  • Can be restricted to paragraph styles

17
Information-Portal with CMS
TIMETOWEB Content Management System
18
Information-Portal with CMS
TIMETOWEB Content Management System
  • Personalized widgets
  • Links
  • My favorites
  • My news
  • My location
  • My weather
  • RSS-Feeds
  • Tag clouds
  • etc.

19
Information-Portal with CMS
TIMETOWEB Content Management System
  • Personalization of information and layout

20
Web 2.0 Social Software with CMS
TIMETOWEB Content Management System
  • Blogs
  • Chatrooms
  • Bulletin board
  • Forms, mails
  • Integrated project-rooms
  • Annotation of content
  • Newsletter
  • Tagging
  • RSS-Feeds
  • etc.

21
Information Architecture with CMS
TIMETOWEB Content Management System
  • Extension of the sitemap by tagging, tag clouds,
    related documents, etc.
  • Cost advantage by optimized search for information

22
EmployeePages extension
TIMETOWEB Content Management System
  • Visualization of the organisational structure
  • Master data import
  • Employee profiles
  • Profile search
  • Phonebook
  • much more

23
EmployeePages extension
TIMETOWEB Content Management System
  • Sametime integration
  • Export VCF, mail-distributor, phone-listings
  • etc.

24
Chances for cost savings
TIMETOWEB Content Management System
  • Less editorial expenses
  • by an easy to use application
  • by fast and easy deposition of information
  • Less developing expenses by a fast integration of
    different applications
  • Lower access times for the users
  • by personalization
  • by information architecture
  • by knowlege and skill management

25
Practical Example Welcome Page
TIMETOWEB Content Management System
The welcome page is divided in fixed components
predetermined by the enterprise and moveable
widgets with partial personalizable content. The
arrangements and settings are filed persistent in
each person document. Thereby the personal
welcome page is available from every computer.
Fixed components whose content e.g. could be
evaluated by rights or localization.
By the user moveable and partial personalizable
widgets.
26
Infocenter
TIMETOWEB Content Management System
Chronological sorting of information. Simple
detection of information by an intuitive
navigation through years and months.
Organisatonal or logical classification.
The extern and intern enterprise news could be
displayed classified by category, division or
rights and sorted by publishing date.
27
Shared Documents
TIMETOWEB Content Management System
Documents like best practices or guidelines can
be displayed in overviews. For authorized persons
the inserting of new documents is also possible
simple an fast in the web interface.
Content fields can be edited at any time by
Inline Editing.
Simple upload and removal of files.
28
Community
TIMETOWEB Content Management System
The employees coulds create, edit and manage the
information in their profile. The basic data
could be imported and regulary updated from other
data sources (e.g. SAP, domino directory) to keep
the maintenace effort small. By a categorisation
by groups or tags an effective search for skills
or assignments is possible.
Search within the pool of employees by different
categorisations.
Overview of the contact information of each
employee .
29
Employee Profiles
TIMETOWEB Content Management System
In the detailed employee profiles could be stored
most diverse information about the single
employees.
Contact information
Information about e.g. skills, expertise,
languages, tags, groups, hobbies, history,
supervisors and so on could be edited fast and
simple by the employee through Inline Editing.
30
TIMETOWEB references (summary)
TIMETOWEB Content Management System
  • Aliseca (intranet)
  • Bayer AG (intranet)
  • Bayer CropScience AG (intra-, extra- internet)
  • Bayer HealthCare AG (approx. 190 intranet
    websites)
  • Bayer MaterialScience AG (intra-, extra-
    internet)
  • BDEW (extra- internet)
  • Berliner Volksbank (intranet)
  • Coca Cola Erfischungsgetränke AG (intranet in
    preparation)
  • GdP (Extra- Internet)
  • Geberit AG (intranet in preparation)
  • Gesamtmetall (internet)
  • LANXESS AG (global intranet)
  • LBS (Intranet)
  • Vinnolit (internet)

31
TIMETOACT references
TIMETOWEB Content Management System
32
Conclusion CMS vs. Portal
TIMETOWEB Content Management System
  • CMS (TIMETOWEB) based websites offer a wide range
    of personalization options.
  • CMS based websites use widgets and look more like
    portals.
  • CMS based websites offer better content
    management than portals.
  • CMS based websites are good in aggregating
    information.
  • Portals are the right choice for application
    integration.
  • Portals are more complex and more expensive than
    a CMS.
  • TIMETOACT has know-how, methodology and deep
    skills in CMS and WebSphere Portal

33
How can we help you?
TIMETOWEB Content Management System
Write a Comment
User Comments (0)
About PowerShow.com