Cinram on How we wen.. - Lansa

wispxylopolistInternet and Web Development

Aug 7, 2012 (5 years and 2 months ago)

587 views

How we went SAP
-
like without
'sapping' the System
i

Tony Collins

European Systems Development Manager

Cinram International Inc.


World's largest provider of pre
-
recorded
multimedia products and logistics services


Founded 1969, staff of 17,000, revenues of $2bn


Facilities in North America and Europe


2.1 billion DVDs and 800 million CDs per year


Clients include motion picture studios, music
labels, publishers and software companies


Warner Home Video, Warner Music Group,
Twentieth Century Fox, Metro
-
Goldwyn
-
Mayer
and EMI Group plc (EMI)


About
Cinram Logistics UK


Largest media distribution company in Europe


14 acre site in Aylesbury with over 400 people


Order processing, warehousing, shipping,
invoicing and returns processing


From 20 clients to 18,000 outlets in UK & Eire


DVDs, CDs, vinyl records, mini discs and
UMDs

Systems Environment


IBM System
i

servers


700 users in multiple countries


All core apps have 5250 terminal user interface


Global Distribution System (GDS)


Bespoke system written originally for Sony Music
with the JDE technical structure


PRMS ERP Package


Warehouse Management System from CA


Staff have primarily RPG and JDE skills


Limited exposure to Windows and Web stuff


Modernisation Challenge


Must urgently satisfy important new customer


Cannot disrupt day
-
to
-
day operations


Must develop in
-
house with existing resources


Do not have access to original source code


Heavily customised so annexed from JDE


Prior negative experience with screen
-
scraping


Modest budget but high end
-
user expectations!


Customer: I want my SAP back!

The Evolution of a User Interface

SAP R/2 (IBM Mainframe)

The Evolution of a User Interface

SAP R/3 version 1.0 (
OSF/
Motif and OS/2)

The Evolution of a User Interface

SAP R/3 version 2.0 (Windows 3.1)

The Evolution of a User Interface

SAP R/3 version 3.0 (Windows 95)

The Evolution of a User Interface

SAP R/3 version 4.0 (Windows 98)

The Evolution of a User Interface

SAP R/3 version 4.6 (today)

The Evolution of a User Interface

mySAP.com

What Did We Offer the Customer?

Their reaction?

Options


Refacing


Had evaluated Seagull product 5 years earlier


Invited back for a demo


Looked the same, hadn’t really improved!


IBM


Similar crude screen
-
scraping functionality


Has WebSphere requirement so big hardware cost


Not supported on our then version of i5/OS


LANSA

The Decision for LANSA


RAMP (Rapid Application Modernisation Process)


2 day proof
-
of
-
concept comparison with Seagull


Benefits over alternatives


Rich Visual Framework for Windows or Web


Snap
-
in dynamically refaced 5250 screens


Gives true Microsoft Office look
and

feel


Supports extensions and brand new applications


Sound architecture for team
-
based development


Initial investment


2 developer seats


2 servers (unlimited users, dev and prod)


Maintenance, training, expert mentoring

Project Estimate: Phase 1

The Pareto Principle: target the 20% of screens that
users work with 80% of the time


Project Plan: Phase 1

The Pareto Principle:

88
screens and 18 filters


Before and After screen
-
shots

Instance List

Command
Handler

Application

Navigation

Filter

Application View

Framework
Commands

Error Messages

Download to

MS Excel

Framework Menu
Options

Business Objects

Buttons to change the way
the framework view

Buttons to
minimise the
framework
components

Button to collapse /
expand the filter


LANSA Visual Framework

Before: GDS Article Screen

After: GDS Article Screen

Before: Order Inquiry


Header

Before: Order Inquiry


Detail

After: Order Enquiry
-

Header and Detail and More


Before: RA Action (Return Authorisation)

Before: RA Approval

Before: RA Print Control

After: RA Management Module

Export any I
n
stance List data to Microsoft Excel

File Name

Summary

Expectation

Original

Phase 1

END

USER