1. Genexus in MHI
Kyoji Noda
Deputy Director
Project IT Department.
Engineering Headquarters
10 01 2012
© 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
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 2

3. 1. Profile of MHI - Company
Mitsubishi Heavy Industries, Ltd.
Founded 1884
Capital JPY 265.6 Billion (Mar. 31
2011)
Employee 32,494 (Mar. 31
2012)
FY2011 Net Sales JPY 2,821 Billion (Mar. 2012)
(Consolidated)
Organization 8 Headquarters
6 R&D Centers
14 Manufacturing Works
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 3

4. 1. Profile of MHI - Company
8 HeadQuarters of Mitsubishi Heavy
Industries Yokohama
Engineering Center
Power Nuclear
Shipbuilding & Systems Energy Machinery &
Ocean Development Systems Steel Infrastructure
Systems
Aerospace
Systems General Machine Air-Conditioning
Machinery & Tool & Refrigeration
Special Vehicles
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 4

5. 2. History of Genexus
in MHI – Yokohama Engineering Center
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
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 5

6. 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
Genexus
4. Not outdated by change of IT technology
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 6

7. 3. Why Genexus?
The effect by Genexus
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.
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 7

8. 4. Typical example
a. Connection of Genexus and SAP
b. Application system common platform
c. Divide KB
d. Downsizing from Mainframe and SAP systems
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 8

9. a. Connection of Genexus and SAP
GeneXus X Ev1 SAP SAP ERP6.0
Business Connector
GeneXus 4.7 CoreFix7 Common module
KB
Server
Object
&Variable Web Service User PGM
service
Data Type BAPI
Method
Method
Property
Developer Property
SDT
WSDL WSDL
Import File SAP DB
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 9

10. a. Connection of Genexus and SAP
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 business
Heavy user training
Taking advantage of the development efficiency of
Genexus, the Addon development cost and periods in
SAP is reduced.
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 10

11. b. Application system common platform
Platform in Mainframe
Mainframe
File
AP Procurement Accounting
transfer
system system system
Lang. COBOL EASY （ EUC) HULFT
Printing Report
Exec. Batch ： JCL
Online ： CICS Scheduler ： control server
Env.
CA7
Spooler Fibridge
DL/I （ Hierarchical
DB UDB （ RDB)
）
OS ZOS
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 11

12. b. Application system common platform
Platform on a Downsizing Environment （ Before)
Windows server
File
AP Procurement Accounting
transfer
system system system
Lang. .NET HULFT
Printing Report
Exec. Batch : Command
Online ： IIS control server
Env. Scheduler : Task
DB SQLserver
OS Windows Server
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 12

13. b. Application system common platform
Platform on a Downsizing Environment （ After)
Windows server
File
AP Procurement Accounting
transfer
system system system
Lang. .NET HULFT
Printing Report
Exec. Batch : Command
Online ： IIS control server
Env. Scheduler ： Genexus
Genexus Genexus
DB SQLserver
OS Windows Server
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 13

14. b. Application system common platform
Sample screen -- JOB scheduler by Genexus --
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 14

15. b. Application system common platform
Sample screen -- Report server by Genexus --
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 15

16. c. Divide KB
conventional 1-KB environment
Demerit
Production server
1. "Build" takes long time.
Main KB 2. Verification of “DB
Impact” result is time-
【 Common Function 】
Login consuming
Menu
Access control 3. All the systems stop at
Common master the time of a system
maintenance.
Application system A
Application system B
・
・
・
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 16

17. c. Divide KB
multi-KB environment
Production server Production server
(under IT general controls) (Non -IT general controls)
Main KB Application system E KB
【 Common Function 】 Application system F KB
Login
Menu
Application system G KB
Access control
Common master
Application system H KB
Application system A
・
Application system B ・
・
Application system C KB
Application system D KB
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 17

18. c. Divide KB
Effect by dividing KB
Merit
Build per each subsystem  shorter "build" time
Extent of “DB Impact” can be limited.
Common use of menu, login, access control, common
master, and common processing
Caution
When the object in other KB(s) is called
Web session is not kept because of screen change.
 Save Web session information in cookies
How to call a common procedure
 Web Service
 Object copy (Export / Import)
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 18

19. d. Downsizing from Mainframe and SAP systems
Mainframe SAP
PS CO
System System SAP SAP
・・ ・ ・ ・
３ ４ Function Function
・・ ・ ・ ・
Genexus environment
System System
１ ２
Application system common platform
Access Report Job Other common
Menu Workflow
Control server Scheduler Procedure/Webpanel
Common Master data
User , Organization , Vender , Right to access …etc
© 2012 MITSUBISHI HEAVY INDUSTRIES, LTD. All Rights Reserved. 19

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