Solution Proposal

OLAM SAP PI Solution Proposal
Feb 2014
Copyright 2012 NTT DATA, Inc.
Agenda
Problem Statement System Landscape Handshake Transactions Design Approach for OPS/OFS Integration with SAP GT/QC a) c) Option1 : Using IDOC Adapter to JDBC Adapter Option3 : Using RFC Adapter to JDBC Adapter b) d) Option2 : Using ABAP Proxy to JDBC Adapter Options Analysis & Our Recommended option
Design Approach for OPS/OFS Integration with SAP GT/QC a) c) Option1 : Using JDBC Adapter to IDOC Adapter Option3 : Using JDBC Adapter to RFC Adapter b) d) Option2 :Using JDBC Adapter to ABAP Proxy Options Analysis & Our Recommended option
Design Approach for OPS/OFS Integration with iOlam a) c) Option1 : Using JDBC Adapter to JDBC Adapter Options Analysis & Our Recommended option b) Option2 :Using FILE Adapter to JDBC Adapter
Interface Transactions Design Approach for MiniOPS Integration with iOlam a) c) Option1 : Using IDOC Adapter to JDBC Adapter Option3 : Using RFC Adapter to JDBC Adapter b) d) Option2 : Using ABAP Proxy to JDBC Adapter Options Analysis & Our Recommended option
Error Handling and Alert Notification Plan and Resource loading OLAM Interface Estimations Key Expectation from OLAM NTTDATA SAP Process Integration Practice Overview NTTDATA SAP PI Case Studies
Copyright 2012 NTT DATA, Inc. 2
Problem Statement
To design best design solution approach for the various handshake and Interface Transaction Scenarios to be implemented in OLAM by using SOA Middleware Tool (SAP PI) between various legacy systems like OPS (Order Processing System), OFS (Oracle Finance System), iOlam, MiniOPS with SAP systems like SAP GT (Global Template Instance) and SAP QC (Australia Instance) To configure Alert Mechanism to handle to various technical, business and miscellaneous exceptions like if transaction is not valid or missing some important data, etc. via email communication automatically
2012 NTT DATA, Inc.
OLAM System Landscape
SAP GT
OPS OPS
iOlam
SAP PI
OFSOFS
SAP QC
Mini OPS
Handshake Transactions Interface Transactions
Handshake Transactions
Design Approach for OPS/OFS Integration with SAP GT/QC Option 1: Using IDOC to JDBC Adapter
SAP GT
IDOC Adapter
Purchase Contract To Be Decided (TBD) TBD Sale Credit Memo Purchase Credit Memo Sale invoice Purchase Invoice
SAP PI SAP PI
JDBC Adapter
Sale Deal Sampling Shipment Planning Purchase Debit note Sale Credit note Purchase Credit note Sale Debit note
OPS
SAP QC
IDOC Adapter
Sale Contract Goods Issue Sale Invoice Sale Invoice Sale Credit memo
SAP PI SAP PI
JDBC Adapter
Purchase Contract Stock Shipment Purchase Invoice Purchase Credit note Purchase Debit note
OPS
SAP GT
IDOC Adapter
Expense Debit notes
SAP PI SAP PI
JDBC Adapter
Account Payable
OFS
SAP QC
IDOC Adapter
Expense Debit notes
SAP PI
JDBC Adapter
Account Payable
OFS
Pros: Simplest of all designs Easy to Track and Monitor Reprocessing failed IDOC is possible Better Performance
Cons It will work in Asynchronous mode only
Design Approach for OPS/OFS Integration with SAP GT/QC Option 2: Using ABAP Proxy to JDBC Adapter SAP GT
ABAP Proxy
SAP PI SAP PI
JDBC Adapter
OPS
SAP QC
ABAP Proxy
SAP PI SAP PI
JDBC Adapter
OPS
SAP GT
ABAP Proxy
Expense Debit notes
SAP PI SAP PI
JDBC Adapter
Account Payable
OFS
SAP QC
ABAP Proxy
Expense Debit notes
SAP PI
JDBC Adapter
Account Payable
OFS
Pros: Better error handling mechanism Good for large volume of data Reduction of overhead function calling Can make Synchronous & Asynchronous calls
Cons Increased effort as a different ABAP Proxy has to be programmed for each interface
Design Approach for OPS/OFS Integration with SAP GT/QC Option 3: Using RFC Adapter to JDBC Adapter
SAP GT
RFC Adapter
SAP PI SAP PI
JDBC Adapter
OPS
SAP QC
RFC Adapter
SAP PI SAP PI
JDBC Adapter
OPS
SAP GT
RFC Adapter
Expense Debit notes
SAP PI SAP PI
JDBC Adapter
Account Payable
OFS
SAP QC
RFC Adapter
Expense Debit notes
SAP PI
JDBC Adapter
Account Payable
OFS
Pros: Avoid making multiple calls to the same BAPI / RFC, rather have wrapper BAPI and send all records in one time RFC/BAPI support BE (Best Effort) when used synchronously.
Cons Not Good for Large Volume of data RFC or BAPI has its own overhead of function call Not advisable for Asynchronous communication
8
Design Approach for OPS/OFS Integration with SAP GT/QC Option Analysis and Recommended Option
Based on Efforts Comparison vs. Technical trade off

Options Option1 Option2 Option3 Detail IDOC Adapter ABAP proxy RFC Adapter Efforts Complexity Flexibility /Scalability Limitations
Our Recommendation
would suite for MM/SD/FI/GL related Transactions for OPS / OFS system Integration with SAP GT / QC Systems Note: As we are using standard IDOC Contents
OPTION 1:IDOC to JDBC Adapter
Copyright 2012 NTT DATA Corporation
Design Approach for OPS/OFS Integration with SAP GT/QC Option 1: Using JDBC to IDOC Adapter OPS
JDBC Adapter
Purchase Deal Sale Invoice Price Fixing Purchase Debit note Sale Credit note Purchase Credit note Sale Debit note
SAP PI SAP PI
IDOC Adapter
Sale Contract Purchase Invoice Price Fixing Sale Credit Memo Purchase Credit Memo Sale invoice Purchase Invoice
SAP GT
OPS
JDBC Adapter
Sale Deal
SAP PI SAP PI
IDOC Adapter
Sale Contract
SAP QC
OFS
JDBC Adapter
Prepayment Account Receivable
SAP PI SAP PI
IDOC Adapter
Account Payable DA Bill
SAP GT
10
Design Approach for OPS/OFS Integration with SAP GT/QC Option 2: Using JDBC to ABAP Proxy OPS
JDBC Adapter
SAP PI SAP PI
ABAP Proxy
SAP GT
OPS
JDBC Adapter
Sale Deal
SAP PI SAP PI
ABAP Proxy
Sale Contract
SAP QC
OFS
JDBC Adapter
SAP PI SAP PI
ABAP Proxy
SAP GT
11
Design Approach for OPS/OFS Integration with SAP GT/QC Option 3: Using JDBC to RFC Adapter OPS
JDBC Adapter
SAP PI SAP PI
RFC Adapter
SAP GT
OPS
JDBC Adapter
Sale Deal
SAP PI SAP PI
RFC Adapter
Sale Contract
SAP QC
OFS
JDBC Adapter
SAP PI SAP PI
RFC Adapter
SAP GT
12
Design Approach for OPS/OFS Integration with SAP GT/QC Option Analysis and Recommended Option

Our Recommendation
OPTION 1:JDBC to IDOC Adapter would suite for MM/SD/FI/GL related Transactions for
OPS / OFS system Integration with SAP GT / QC Systems Note: As we are using standard IDOC Contents
13
Design Approach for OPS/OFS Integration with iOlam Option 1: Using JDBC to JDBC Adapter
iOlam
JDBC Adapter
Sale Contract Purchase Contract Sales Way Bill Shipment Advice Export Invoice Sale Credit note Purchase Credit note Sale Debit note Purchase Debit note
SAP PI SAP PI
JDBC Adapter
Purchase Deal Sale Deal Stock Shipment Stock Shipment Purchase Invoice Purchase Debit note Sale Debit note Purchase Credit note Sale Credit note
OPS
OPS
JDBC Adapter
Sale Deal Purchase Debit note Sales Debit note Purchase Credit note Sales Credit note
SAP PI SAP PI
JDBC Adapter
Purchase Contract Sale Credit note Purchase Credit note Sales Debit note Purchase Debit note
iOlam
iOlam
JDBC Adapter
Expense Debit notes
SAP PI SAP PI
JDBC Adapter
Account Payable
OFS
OFS
JDBC Adapter
SAP PI
JDBC Adapter
iOlam
Pros: Can read any database if proper drivers are installed Creates XML structure of data from db automatically No content conversion required Can be used for both Synchronous & Asynchronous
Cons Correct drivers need to be deployed for each type of database Cannot update or insert multiple tables with sequence
14
Design Approach for OPS/OFS Integration with iOlam Option 2: Using FILE to JDBC Adapter
iOlam
FILE Adapter
Sale Contract Purchase Contract Sales Way Bill Shipment Advice Export Invoice Sale Credit note Purchase Credit note Sale Debit note Purchase Debit note
SAP PI SAP PI
JDBC Adapter
Purchase Deal Sale Deal Stock Shipment Stock Shipment Purchase Invoice Purchase Debit note Sale Debit note Purchase Credit note Sale Credit note
OPS
OPS
FILE Adapter
Sale Deal Purchase Debit note Sales Debit note Purchase Credit note Sales Credit note
SAP PI SAP PI
JDBC Adapter
Purchase Contract Sale Credit note Purchase Credit note Sales Debit note Purchase Debit note
iOlam
iOlam
FILE Adapter
Expense Debit notes
SAP PI SAP PI
JDBC Adapter
Account Payable
OFS
OFS
FILE Adapter
SAP PI
JDBC Adapter
iOlam
Pros: Simplest of all design
Cons Not Good for Large Volume of data Difficult to Track and monitor
15
Design Approach for OPS/OFS Integration with iOlam Option Analysis and Recommended Option

Options Option1 Option2 Detail JDBC Adapter FILE Adapter Efforts Complexity Flexibility /Scalability Limitations
Our Recommendation
would suite for MM/SD/FI/GL related Transactions for OPS / OFS system Integration with iOlam / MiniOPS System Note: As we are using standard Oracle Drivers for the database
OPTION 1:JDBC to JDBC Adapter
16
Interface Transactions
17
Design Approach for MiniOPS Integration with SAP GT Option 1: Using JDBC to IDOC Adapter
JDBC Adapter
MiniOPS
Sales Deal Purchase Deal Stock Shipment Merge Direct Shipment Direct Shipment Purchase Invoice Sale Invoice Purchase Debit note Sales Debit note Purchase Credit note Sales Credit note Price fixing Futures Processing Journals Negotiation
SAP PI
IDOC Adapter
SAP GT
Sale Contract Purchase Order Goods Receipt Goods Issue Goods Receipt Goods Issue Purchase Invoice Sale Invoice Purchase Credit memo Sales Invoice Purchase invoice Sales Debit memo Price fixing FI Journals LockBox application
18
Design Approach for MiniOPS Integration with SAP GT Option 2: Using JDBC to ABAP Proxy
JDBC Adapter
MiniOPS
SAP PI
ABAP Proxy
SAP GT
19
Design Approach for MiniOPS Integration with SAP GT Option 3: Using JDBC to RFC Adapter
JDBC Adapter
MiniOPS
SAP PI
RFC Adapter
SAP GT
20
Design Approach for MiniOPS Integration with SAP GT Option Analysis and Recommended Option

Our Recommendation
OPTION 1:JDBC to IDOC Adapter would suite for MM/SD/FI/GL related Transactions for
OPS / OFS system Integration with SAP GT / QC Systems Note: As we are using standard IDOC Contents
21
Error Handling and Alert Notification

List of Different Errors that can be handled in SAP PI both Integration Engine (IE) and Advanced Adapter Engine (AAE) as categorized below 1. Business Error 2. Technical Error 3. Miscellaneous Error Alert Notification a) In case, If there is a problem in handling MM/SD/FI/GL related Transactions in PI, then it needs to be flagged so a business user / Group Distribution list is alerted. b) E-Mail Notifications can be sent accordingly if PI Mapping fails or Connectivity fails or any other problems.
22
Plan and Resource Loading
23
OLAM Interfaces Estimation-1
24
OLAM Interface Estimation - 2
25
Key Expectations from OLAM
Phase
Expected activities from OLAM Arranging development systems and environment for development Creating user id with authorizations and providing the user ids to on-site / Offshore teams Creating User credentials in Oracle DB for both OPS and OFS system along with JDBC drivers details
Initiate
Technical Design & Build
Ensuring availability of concerned teams for review, approval and sign-off on technical design documents Coordinate any development/technical object identification in PI Configure Alert Categories and Alert Rules for both Integration Engine and Adapter Engine Message failures Review and Approve test cases Participate if required in Actual Testing Coordination with other concerned teams(BASIS/OPS and OFS DBA Team) along with Functional Teams too
Testing
26
NTTDATA SAP Process Integration Practice Overview

NTT DATAs approach on SAP Process Integration (SAP PI) that provides Service Oriented Architecture (SOA) foundation capabilities for SAP customers. SAP PI is an integration platform that provides seamless integration between SAP and non-SAP applications within the organization (A2A) as well as outside the organization boundary (B2B). The enterprise services bus performance of SAP PI is specifically tuned for a high-volume and reliable exchange of information across distributed business applications. SAP PI offers all functions of an ESB
Overview
Size & Scale : Multiple SAP PI Experts (Architects, Technical Experts, and Technical Consultants) Readiness : Over 10 ready apps ready to be customized per customer needs
Highlights
PI COE SAP PI 7.31 Certified Consultants Pool 15% Architectural Capability SCN Contributions Silver & Bronze contributors SAP PI 7.31 Ramp up Partner Testing EDI Legacy / subsystem Migration to PI PI EDI Implementation PI EDI AMS Services RNIF Legacy / subsystem Migration to PI PI RNIF Implementation PI RNIF Services Rapid Delivery of Enterprise Services (RADES) Accelerated Mappings
Verticals : Aerospace, CPG, Manufacturing, High Tech and Public sector

LOB : Retails, Pharmaceuticals, Aerospace, Oil & Gas, Telecommunication Platform : Classical Swing client, Eclipse based NWDS client Key Clients: Hospira, REI, Palo Alto Networks, Orion Carbons, T-Mobile
PI EDI Offerings

Services
PI Implementation & Consulting PI AMS service PI Upgrade Service PI Migration service PI Assessment and Roadmap Rapid Development service B2B Add-ons service EDI Factory service
PI RNIF Offerings
PI Integration Factory
Unique Capabilities
SOA Foundation Capability High volume and reliable message support Service mediation Capability Protocol Translation Capability Message Routing B2B Add-ons Capability Capability for EDI/RNIF/CIDX Message Transformation messages Capability Strong BPM and Process Security Orchestration capability Reliable Messaging Monitoring & Administration Tool
27
NTTDATA SAP PI Case Studies
28
Hospira Phoenix Case Study

Scope & Objectives Business Challenges & Learning Solution Values Added
Objectives
Replace Contract Administration(CAS), Chargeback System & Replace Delphi system Migrate AHA functionality to SAP ECC from Delphi. Synygy to be the new Sales Performance Management system
Scope
Develop Interfaces between ECC, Model N, Synygy SFDC staging , BW and other systems using SAP PI/XI Master Data changes flow mutually between SAP, Model N and other systems to sync them up.
Business Value
Simplify contracting processes and reduce/eliminate manual efforts Write better contracts that deliver margin improvement Reduce time the sales rep spends in contract activities Reduce cycle time from initial customer contact through signed contract Enforce contract compliance commitments Reduce risk profile related to government reporting Reduce application support activities and Copyright 2012 NTT DATA, Inc.
Challenges Mapping of inventory materials to saleable material drug, pumps or service items. Executing multiple sub projects within Phoenix, without affecting one another. IT Challenges Use of a enterprise wide Interfacing mechanism(IDOC) for master data to cater to varying needs of different Application systems. Setting up of new processes around development using new Information technology areas like SAP PI and JAVA. Learning Maintenance consistence of master data changes across multiple options.
Solution Migration of AHA functionality to SAP with added features and functionalities Interface to Model N to get the real time pricing Integrate web services provided by Model N job framework with AUTOSYS system, using SAP PI. Interface various dataflows that support OTC and FI processes between the various application systems. Enhance core SAP functionality wherever needed, to support interfaces.
Value Adds Leverage existing investments by integration of Hospiras standard job scheduling tool with the web service based job scheduling tool of Model N. Flexible design & configuration to allow switch over when needed Enhanced INet Interface to create any type of sales documents Streamlining and classification of the material master data based on material groups. Enabling hub and spoke model using a unified integration middleware system (SAP PI) to leverage the benefits offered by the model.
29
Harvey Nichols PI 7.31 IS-Retail Implementation for ALFA.

Scope & Objectives
Business Challenges & Learning
Solution
Values Added
Objectives Replacement of Retails TIMS system with SAP ISRetail POS SAP POS will be used for sales activities & should record daily transactions to POSDM. Using PI inbound interface. Sap will be generating Article, Merchandise category, Sales, Seasons, Discounts, Promotion, employee related master data which need to be updated in POS system through interfaces. Scope Perform POS integration and monitor activities. Complete configuration of PI end to end implementations and making sure SAP POS replace TIMS & fully functional from Business standpoint.
Challenges POS Transactions containing cash & credit Sales information segregate & channelled to different SAP systems. Configuration of IDOC_AAE adapter with NWA activities so as to accomplish full fledged PI7.3 Enhancements provided by SAP. Testing of all 14 outbound and 2 Inbound interfaces very integral part of upgrade project Learning Learnt PI7.3 implementation and required nwa activities needed for PI7.3 Faced some new issues and quickly we are working with SAP through Note implementation and trace capturing.
Solution Usage of IDOC instead of IDOC_AAE adapter as workaround to meet the requirements in time. Learnt new monitoring ways instead of RWB in PI7.3 and creating the requirements myself in the absence of Net Weaver Admins and Basis for PI pre configuration activities.
Value Adds Developed one interface instead of 7 for promotions based on discount types. Cutting Edge PI 7.3 features deployment and benefiting customer with all the functionality & providing customer training by giving hands-on workshop training.
T-Mobile Fullerton PI 7.1 Case Study

Scope & Objectives Business Challenges & Learning Solution Values Added
Objectives Integrating T-mobile SAP system with third party non sap system using SAP PI 7.11. T-Mobile HR Benefits related data like Employee, Payroll Deduction Data, Actual hours worked ,LSF and ATP need to be update in TMOs vendor FTP system and vice versa. TMO vendor is AON-Hewitt and the data needs to be transferred securely between these two networks. Scope Integration between TMOs SAP HCM system with AONs TBA system. Complete configuration check and Testing by using Readiness check document
Challenges PI will receive Employee, Actual hrs worked, Org hierarchy, Employee Leave Status, Advice 2 pay ,Deductions data from SAP ECC and AON TBA system. PI should read and write the data securely between TMO and AON systems. Use of See burger's SFTP adapters for secure data transfer & content conversions. Managing single target folder for all the environments. Learning Working with Certificates & secure connection between B2B Learnt methodologies to perform smooth Go-live on time
Solution Integrating the TMOs SAP HCM system and AONs TBA system using SAP PI 7.11. Develop ABAP client Proxies for outbound messages and ABAP server proxies for Inbound messages. Implementing both Inbound and Outbound interfaces along with content conversions using SEEBURGER-SFTP adapters. Providing alert mechanism for the failed messages.
Value Adds Direct interaction with AONs legacy system in secured way . Customized Monitoring transaction for the archived and failed messages in PI. Lower memory consumption and performance optimization of cache refresh Continuous enhancements and optimizations
31
Orion Engineered carbons PI 7.1 EHP 1 Implementation Case Study Objectives Business Challenges & Learning Solution Value Adds
Objectives Orion Engineered Carbons Integration objects are developed in SAP PI 7.1 (EHP 1) system Integrating various customers following Chem eStandards with SAP system of Orion. Implementing EDI message exchange with various business partners using SAP PI. Integrating various database systems with Orions SAP system using SAP PI. Integrating web services with Orions SAP system using SAP PI. Implementing SFTP transmission along with encryption and decryption of messages for banking interfaces of CITI Bank and JP Morgan using SAP PI.
Challenges Implementing the Order To Cash business interfaces with various Chem eStandard customers using CIDX in SAP PI. Implementing EDI Integration for various customers using Seebuger was a big challenge. Each EDI transaction followed a different version of EDI document. Testing the EDI and CIDX Interfaces for various business partners. Implementing Encryption and decryption of messages for banking interfaces. Learning Learnt implementing CIDX interfaces Encountered certain new issues and resolved them quickly. Performed RCA for frequently occurring issues and fixed them.
Solution Implemented the Encryption and Decryption of messages for banking interfaces using SAP SECURITY ADDON Implemented the CIDX (Chemical Industry Data Exchange) Interfaces using CIDX business content and CIDX Adapter. Implemented the EDI interfaces using Seeburger and developed custom adapter module for handling free form segments (which were not supported by Seeburgers module). Developed the EDI conversion mappings using Seeburger BIC Mapping Designer tool.
Value Adds Developed user defined message search solution using which messages can be tracked based on content of payload. For certain critical interfaces like Process Order, customers were informed via mail for any failure of process order in SAP PI.
NTTDATA SAP PI Case Studies - Summary

Total No of systems
10 BS 4 BS 7 BS 5 BS 5 3 5 3
Customers
Hospira Phoenix TMOBILE Fullerton Hospira HSST Olympus SORRA Harvey Nichols ORION Carbon Synergy
Project Type
Implementation
Version
PI 7.31 PI 7.11 PI 7.31 PI 7.31
Environment
Team Size
10 2 2 1
Implementation
Implementation
Up gradation
Implementation
PI 7.31 PI 7.11 PI 7.31 PI 7.31
4 BS 5 BS 8 BS 5 BS
3 3 3 3
2 2 3 3
Implementation
Support
Implementation
Support
LSI Logic
PI 7.1
4 BS
33
NTTDATA Customer Footprint

We have delivered end-to-end SAP services in most industries.
Implementation Support Upgrades/ Migrations
34
Commercials
NTT DATA's commercial Offer based on proposed scope for Integrating Legacy Systems with SAP is INR 25,00,000 ( Twenty Five Lakhs only) .
35
This document contains confidential Company information. Do not disclose it to third parties without permission from the Company.

Solution Proposal

Uploaded by

Copyright:

Available Formats

Solution Proposal

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solution Proposal

Uploaded by

Copyright:

Available Formats

OLAM SAP PI Solution Proposal

Copyright 2012 NTT DATA, Inc.

2012 NTT DATA, Inc.

OLAM System Landscape

Handshake Transactions Interface Transactions

Copyright 2012 NTT DATA, Inc.

Copyright 2012 NTT DATA, Inc.

Cons It will work in Asynchronous mode only

Based on Efforts Comparison vs. Technical trade off

OPTION 1:IDOC to JDBC Adapter

Copyright 2012 NTT DATA Corporation

Cons It will work in Asynchronous mode only

Based on Efforts Comparison vs. Technical trade off

Copyright 2012 NTT DATA Corporation

Pros: Simplest of all design

Copyright 2012 NTT DATA, Inc.

Based on Efforts Comparison vs. Technical trade off

OPTION 1:JDBC to JDBC Adapter

Copyright 2012 NTT DATA Corporation

Copyright 2012 NTT DATA, Inc.

Cons It will work in Asynchronous mode only

Based on Efforts Comparison vs. Technical trade off

Copyright 2012 NTT DATA Corporation

Error Handling and Alert Notification

Copyright 2012 NTT DATA Corporation

Plan and Resource Loading

Copyright 2012 NTT DATA Corporation

OLAM Interfaces Estimation-1

Copyright 2012 NTT DATA Corporation

OLAM Interface Estimation - 2

Copyright 2012 NTT DATA Corporation

Key Expectations from OLAM

Technical Design & Build

Copyright 2012 NTT DATA Corporation

NTTDATA SAP Process Integration Practice Overview

Verticals : Aerospace, CPG, Manufacturing, High Tech and Public sector

Copyright 2012 NTT DATA Corporation

NTTDATA SAP PI Case Studies

Copyright 2012 NTT DATA, Inc.

Hospira Phoenix Case Study

Harvey Nichols PI 7.31 IS-Retail Implementation for ALFA.

Business Challenges & Learning

T-Mobile Fullerton PI 7.1 Case Study

NTTDATA SAP PI Case Studies - Summary

PI 7.31 PI 7.11 PI 7.31 PI 7.31

Copyright 2012 NTT DATA Corporation

NTTDATA Customer Footprint

Copyright 2012 NTT DATA, Inc.

Copyright 2012 NTT DATA, Inc.

Copyright 2012 NTT DATA, Inc.

You might also like