GeneXus en Mitsubishi Heavy Industries (MHI) – Japón

© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved.

Genexus in MHI

10 01 2012

Kyoji Noda

Deputy Director

Project IT Department.

Engineering Headquarters

© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 2

Agenda

1. Profile of MHI - Company

2. History of Genexus in MHI – Yokohama Engineering Center

3. Why Genexus?

4. Typical example

a. Connection of Genexus and SAP

b. Application system common platform

c. Divide KB

d. Downsizing from Mainframe and SAP systems



Founded 1884

Capital JPY 265.6 Billion (Mar. 31 2011)

Employee 32,494 (Mar. 31 2012)

FY2011 Net SalesJPY 2,821 Billion (Mar. 2012)

(Consolidated)

Organization 8 Headquarters

6 R&D Centers

14 Manufacturing Works

Mitsubishi Heavy Industries, Ltd.



8 HeadQuarters of Mitsubishi Heavy Industries

Power Systems

NuclearEnergy Systems

Machinery & Steel Infrastructure Systems

General Machinery & Special Vehicles

Air-Conditioning& Refrigeration

AerospaceSystems

Shipbuilding &Ocean Development

Machine Tool

Yokohama Engineering Center

Yokohama Engineering Center


2. History of Genexus

Apr. 2000 ~ Mar. 2001 Implementation SAP R/3 4.6C(PS,MM,FI,CO)

Apr. 2003 ~ Mar. 2004 Evaluation of Genexus

Dec. 2004 ~ Mar. 2005 First system development with Genexus8.0

Apr. 2005 ~ Sep. 2006 Connection of Genexus - SAP

Apr. 2008 Version up to Genexus9.0

Nov.2008 ~ Jul. 2009 Version up to SAP ERP6.0

Aug. 2010 Version up to Genexus X Evo1

Sep. 2010 ~ Aug. 2012 Application system common platform (Genexus)

Jun. 2011 ~ Aug. 2012 Split KB

Jan. 2011 ~ Mar. 2014 Downsizing from Mainframe and SAP systems

in MHI – Yokohama Engineering Center


3. Why Genexus?

Motivation :　 Existing systems are fairly working, but ……

1. Shortage of Mainframe system engineer

2. Big Expense for following to change of IT technology?

3. Dissatisfaction to UI of a package system

4. Development from scratch is expensive

Major Requirements : 1. Easy to learn

2. Capability to build the functions required for application systems

3. High productivity of development and Ease of maintenance

4. Not outdated by change of IT technologyGenexus

1. Prototype system is created at the stage of data analysis.

2. Operation of DBMS is almost needless.

3. The code of data manipulation is very simple by an “ExtendedTable” concept.

4. Since language is simple and coding work is very few, - maintenance , taking over and trouble shooting are easy.

5. Since it is not necessary to master a lot of languages, -skill level easily becomes high.

6. Mainframe system engineers was able to shift to Web systems development smoothly.


3. Why Genexus?

The effect by Genexus



c. Divide KB



4. Typical example


SAPSAPBusiness Connector Business Connector 4.7 CoreFix74.7 CoreFix7

SAPSAP 　　 ERP6.0ERP6.0GeneXus X Ev1GeneXus X Ev1

Common module

BAPI

User PGM

WSDLImport

Server

Developer

Service

WSDLFile

GeneXusKB

SAP DB

SDT

Data Type

Method

PropertyMethod

Property

Object

&Variable Webservice

9© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved.



Merit from a Genexus application :SAP standard functions (BAPI, general-purpose module) and Addon programs can be used as a Genexus object.Common master data are unified in SAP

Merit from SAP : Released from SAP GUI inconvenience

Many functions or items are not usually used.SAP original term Operation of many screens for one businessHeavy user training

Taking advantage of the development efficiency of Genexus, the Addon development cost and periods in SAP is reduced.

Platform in Mainframe


Mainframe

OS

Lang.

ZOS

COBOL EASY （ EUC)

DB UDB （ RDB)DL/I （ Hierarchical ）

Exec.Env. Online 　：　 CICS

Batch 　：　 JCLScheduler 　：　CA7

APsystem

Procurementsystem

Accountingsystem

Filetransfer

HULFT

Printing control

Spooler

Reportserver

Fibridge


Windows server

Platform on a Downsizing Environment （ Before)



OS

Lang.

DB

Exec.Env.

APsystem

Filetransfer

Printingcontrol

Reportserver

Windows 　 Server

.NET

SQLserver

Online 　：　 IIS

Procurementsystem

Accountingsystem

Batch : CommandScheduler : Task

HULFT

Windows server

Platform on a Downsizing Environment （ After)


OS

Lang.

DB

Exec.Env.

APsystem

Filetransfer

Printingcontrol

Reportserver

Windows 　 Server

.NET

SQLserver

Online 　：　 IIS

Procurementsystem

Accountingsystem

Genexus Genexus

Batch : CommandScheduler ： Genexus

HULFT


Sample screen -- JOB scheduler by Genexus --



Sample screen -- Report server by Genexus --



conventional 1-KB environment

c. Divide KB

Production server

Main KB

Application system B

Application system A

【 Common Function 】Login MenuAccess control Common master

・・・

Demerit1. "Build" takes long time.

2. Verification of “DB Impact” result is time-consuming

3. All the systems stop at the time of a system maintenance.


multi-KB environment

c. Divide KB

Production server(under IT general controls)

Main KB

Application system D 　 KB

Application system C 　 KB

Application system B

Application system A

【 Common Function 】Login MenuAccess control Common master

Production server (Non -IT general controls)

Application system F 　 KB

Application system E 　 KB

Application system H 　 KB

Application system G 　 KB

・・・


Merit Build per each subsystem shorter "build" timeExtent of “DB Impact” can be limited. Common use of menu, login, access control, common master, and common processing

CautionWhen the object in other KB(s) is called

Web session is not kept because of screen change. Save Web session information in cookiesHow to call a common procedure Web Service Object copy (Export / Import)


c. Divide KB

Effect by dividing KB

Genexus environment

SAP

PS CO


Application system common platform

System　１

Common Master dataUser , Organization , Vender , Right to access …etc

Menu


AccessControl

WorkflowReportserver

JobScheduler

Other commonProcedure/Webpanel

Mainframe

System　２

System　３

System　４

SAPFunction

SAPFunction

・・・・

・・

・・

・・

GeneXus en Mitsubishi Heavy Industries (MHI) – Japón

Documents

Transcript of GeneXus en Mitsubishi Heavy Industries (MHI) – Japón