21 A Auto Ver7.1 E Pdf A4

BSP Inc. 2009.01 AUT-0901-0908-1000-3

* A-AUTO is a registered trademark of BSP Incorporated.* All company names and product names in this brochure are trademarks or registered trademarks of their respective companies.* The information presented in this brochure is subject to change without prior notice.

Head Quarters

Osaka Office

Nagoya Office

Fukuoka Office

Sapporo Office

Head Quarters

BSP, Inc. www.bsp.jp

BSP Solutions Incorporated www.kaizen-ikasu.com

Shinagawa Intercity A-29, 2-15-1 Kounan, Minato-ku, Tokyo 108-6029, Japan Tel: +81-3-5463-6381 Fax: +81-3-5463-6392Konishi-Nissei Bldg., 4-12-12 Minami-Senba, Chuo-ku, Osaka-shi, Osaka 542-0081, Japan Tel: +81-6-6245-4595 Fax: +81-6-6245-4186Suzuki Bldg., 4-17-4 Meieki, Nakamura-ku, Nagoya-shi, Aichi 450-0002, JapanTel: +81-52-561-6808 Fax: +81-52-533-0266Hakata-higashi Honey Bldg., 2-2-2 Hakataeki-higashi, Hakata-ku, Fukuoka-shi, Fukuoka 812-0013, JapanTel: +81-92-437-3200 Fax: +81-92-437-32322-6-6 Shimonopporo Techno Park, Atsubetsu-ku, Sapporo-shi, Hokkaido 004-0015, JapanTel, Fax: +81-11-775-4242

Shinagawa Intercity A-29, 2-15-1 Kounan, Minato-ku, Tokyo 108-6029, Japan Tel: +81-3-6718-2120 Fax: +81-3-6718-1650

License Supported platforms

Basic license

Remote license

Mainframe integration

ERP interface

A-AUTO/Reports

■ Mainframe z/OS、MSP、XSP、VOS3 ■ UNIX AIX、Solaris、HP-UX、MP-RAS、Solaris10x86 ■ Linux RedHat、TurboLinux、z/Linux、SUSE Linux ■ Windows Windows 2000 Server、Windows Server 2003

■ UNIX AIX、Solaris、HP-UX、MP-RAS、Solaris10x86 ■ Linux RedHat、TurboLinux、z/Linux、SUSE Linux ■ Windows Windows 2000 Server、Windows Server 2003 ■ AS400 OS400

■ SAP R/3 AIX、Solaris、HP-UX、Windows 2000 Server、Windows Server 2003、z/Linux ■ BW interface AIX、Solaris、HP-UX、Windows 2000 Server、Windows Server 2003、z/Linux ■ Oracle EBS AIX、Solaris、HP-UX

Windows 2000 Server、Windows Server 2003、Windows XP

A-AUTO/Server Windows Server 2003、Windows Server 2008

A-AUTO/WebClient Internet Explorer 6/7

Operating environment

■ Mainframe z/OS、MSP、VOS3 ■ UNIX AIX、Solaris、HP-UX、MP-RAS、Solaris10x86 ■ Linux RedHat、TurboLinux、z/Linux、SUSE Linux ■ Windows Windows 2000 Server、Windows Server 2003

* Supported platforms differ depending on the versions of A-AUTO. Please consult your sales representative for the latest information.

● For inquiries, please contact to:

Excellent IT operations management system designed for mission-critical applicationEnables standardization of systems operation and IT application control through job management on various platforms

Stable, Safe, and SecureA-AUTO provides a smooth transition to excellent IT systems operation

Head Quarters

BSP (Shanghai), Inc.11E Qianjiang Tower, 971 Dongfang Rd, Pudong, ShanghaiTel: +86-21-50588268 Fax: +86-21-50588218

Ver7.1

The BSP Group supports those in IT systems operation

a-auto.com

A-AUTO is a job management tool that runs on various platforms, including mainframe, Unix, MS Windows, Linux, and IBM i. It integrates job scheduling automatically across different platforms, for various applications, from information systems to mission-critical systems, providing nonstop job scheduling 24 hours a day, 365 days a year. Even when the workload is at its heaviest, A-AUTO continues its secure progress management and gives stable support for efficient job management, without requiring additional staffing.

◆ Flexible job scheduling across heterogeneous platformsA-AUTO integrates job scheduling across heterogeneous platforms, including mainframe, UNIX, and MS Windows, with complete upward and downward compatibility.

◆ Secure job management based on scheduled dateReliable execution of batch jobs is essential to the operation of mission-critical applications. A-AUTO provides secure job management, taking advantage of its long-standing experience, including batch processing on mainframes.

◆ Effective for controlling IT applicationsA-AUTO keeps a record of every job, to provide proof that batch jobs have been executed as scheduled.

A-AUTO, a BSP product, is a job management tool that controls the order and execution times of jobs. Released in July 1977, it has been used by numerous companies for over 30 years.

Overview of A-AUTO

Over 900 companies have used BSP products or services, including A-AUTO. Of the 150 leading companies rated highly by Nikkei PRISM 2008, a corporate evaluation system, 66 use BSP products or services.

Over 900 trusted customers

COBIT* presents an internal control framework for IT, including 34 processes for four domains. One of those processes, operations management, is defined in section DS13 of COBIT, which states the requirements of operations management as follows:

■ Control objective in COBIT/DS13・ Formulating procedures and instructions for operations・ Organize the scheduling of jobs・ Monitoring the IT infrastructure

■ Maturity model in COBIT/DS13Level 3: Defining Process・ Repeatable functions are formally defined, standardized, documented and communicated.・ To minimize the need for intervention by operators, automated scheduling and other tools are used.

・Strict controls are exercised over putting new jobs in operation and a formal policy is used to reduce the number of unscheduled events.

Level 4: Keeping jobs managed and measurable・ Responsibilities for executing operations are clearly defined, and ownership is assigned.・ Daily activities can be measured and monitored on the basis of the established service levels.・ Any deviations from established norms are quickly reported so that they can be addressed and, if necessary, corrected. A continuing effort exists to increase the auto-mation of the process and thus to ensure continuing improvement.

By keeping track of all these processes, A-AUTO provides IT governance compliant with COBIT.

Internal control and A-AUTO

● A-AUTO integrates the management of all batch processes, including mission-critical applications, and automatically controls the execution of jobs.

Out of 150 companies

Out of 50 companies

29 companies

53 companies

66 companiesSource: Prepared by BSP, Inc. from data reported in Nikkei PRISM 2008.

* COBIT (Control Objectives for Information and Related Technology) is a formulation of best practices for IT management. It was started in 1992 by the Information Systems Audit and Control Association (ISACA) and the IT Governance Insti-tute (ITGI), and the first edition was released in 1996.

It makes your job management easier and more flexible

Business Processes

Application Systems

Automated executions of jobs by A-AUTO

Businessopportunity Quote Receiving

Stocks

Manufacturinginstructions

Instructionsfor shipment Shipment Sales

Billing Receivingpayment

Placingorder

Read-timeinformation

Arrival ofgoods

Acceptanceof goods

Payment CashdisbursementManufacturing

reportDemandforecast MRP

InventoryclearanceInventoryadjustment

ReceivingEC order

Productioncontrol

Salesadministration HR & payrollOrderingAccounting Inventory

control Billing

JOB5JOB8

JOB2 JOB3

JOB4 JOB6

JOB7 JOB9 JOB10 JOB12 JOB13

Outstanding advantage of A-AUTO

A-AUTO is a job management tool that runs on various platforms, including mainframe, Unix, MS Windows, Linux, and IBM i. It integrates job scheduling automatically across different platforms, for various applications, from information systems to mission-critical systems, providing nonstop job scheduling 24 hours a day, 365 days a year. Even when the workload is at its heaviest, A-AUTO continues its secure progress management and gives stable support for efficient job management, without requiring additional staffing.

◆ Flexible job scheduling across heterogeneous platformsA-AUTO integrates job scheduling across heterogeneous platforms, including mainframe, UNIX, and MS Windows, with complete upward and downward compatibility.

◆ Secure job management based on scheduled dateReliable execution of batch jobs is essential to the operation of mission-critical applications. A-AUTO provides secure job management, taking advantage of its long-standing experience, including batch processing on mainframes.

◆ Effective for controlling IT applicationsA-AUTO keeps a record of every job, to provide proof that batch jobs have been executed as scheduled.

A-AUTO, a BSP product, is a job management tool that controls the order and execution times of jobs. Released in July 1977, it has been used by numerous companies for over 30 years.

Overview of A-AUTO

Over 900 companies have used BSP products or services, including A-AUTO. Of the 150 leading companies rated highly by Nikkei PRISM 2008, a corporate evaluation system, 66 use BSP products or services.

Over 900 trusted customers

COBIT* presents an internal control framework for IT, including 34 processes for four domains. One of those processes, operations management, is defined in section DS13 of COBIT, which states the requirements of operations management as follows:

■ Control objective in COBIT/DS13・ Formulating procedures and instructions for operations・ Organize the scheduling of jobs・ Monitoring the IT infrastructure

■ Maturity model in COBIT/DS13Level 3: Defining Process・ Repeatable functions are formally defined, standardized, documented and communicated.・ To minimize the need for intervention by operators, automated scheduling and other tools are used.

・Strict controls are exercised over putting new jobs in operation and a formal policy is used to reduce the number of unscheduled events.

Level 4: Keeping jobs managed and measurable・ Responsibilities for executing operations are clearly defined, and ownership is assigned.・ Daily activities can be measured and monitored on the basis of the established service levels.・ Any deviations from established norms are quickly reported so that they can be addressed and, if necessary, corrected. A continuing effort exists to increase the auto-mation of the process and thus to ensure continuing improvement.

By keeping track of all these processes, A-AUTO provides IT governance compliant with COBIT.

Internal control and A-AUTO

● A-AUTO integrates the management of all batch processes, including mission-critical applications, and automatically controls the execution of jobs.

Out of 50 companies

29 companies

53 companies

66 companiesSource: Prepared by BSP, Inc. from data reported in Nikkei PRISM 2008.

* COBIT (Control Objectives for Information and Related Technology) is a formulation of best practices for IT management. It was started in 1992 by the Information Systems Audit and Control Association (ISACA) and the IT Governance Insti-tute (ITGI), and the first edition was released in 1996.

It makes your job management easier and more flexible

Business Processes

Application Systems

Automated executions of jobs by A-AUTO

Businessopportunity Quote Receiving

Stocks

Manufacturinginstructions

Instructionsfor shipment Shipment Sales

Billing Receivingpayment

Placingorder

Read-timeinformation

Arrival ofgoods

Acceptanceof goods

Payment CashdisbursementManufacturing

reportDemandforecast MRP

InventoryclearanceInventoryadjustment

ReceivingEC order

Productioncontrol

Salesadministration HR & payrollOrderingAccounting Inventory

control Billing

JOB5JOB8

JOB2 JOB3

JOB4 JOB6

JOB7 JOB9 JOB10 JOB12 JOB13

Outstanding advantage of A-AUTO

Renewed screen made available on the webBecause a user can maintain master files in the unit of application group, it simplifies the acceptance of additions and modifications from development environment into production environment.

Multiple job networks can easily be assigned to a single application group for various kinds of process-ing, such as maintaining master files, scheduling, and queuing.

Simplified transition from development to production

Thanks to its capability to distribute loads among systems, which is made possible by a new load-balancing function, system operations can be more stable and job networks can be processed in a shorter time than it previously could.

Stable operation made possible by load balancing

Because the conditions for operating job networks on a server become increasingly complicated, more detailed and precise functions are required, so that system operators can manage the conditions with the least burden. For example, one new function uses the return code of the preceding job to determine which job to process next. This function makes it possible to execute complicated jobs by changing a setting of the master file, without complicating the script for the batch job.

Flexible configuration of job networks

Advanced capability for large-scale systems

The next job can be selected depending on the return code of the preceding job.

A-AUTO monitor

Job networks

Job networks are automatically assigned to a machine with lower CPU utilization.

JOB001 JOB002a

JOB002b

JOB003Return code is not 0.

Return code is 0.

Jobs can be added or deleted on a date preset by the operator.

Monitoring screen

Screen from previous version

Screen from new Ver7.1

The increased scalability and performance of A-AUTO Ver 7.1 enable it to handle larger amounts of data and integrated servers. It provides stress-free control of tens of thousands of job networks a day. The new version offers improvements in the speed of job networks initiation and control, so that any job operations in an increasingly scaled-up open system can be handled perfectly.

A-AUTO Ver 7.1 integrates job network definition, job network monitoring, and system monitoring into one screen on the web. This is an improvement over the earlier version, which required individual client software for each function.

Jobs can be initiated up to 10 times as fast as with the previous version.

A-AUTO provides excel lent se r v i ce to l a rge sys tems formed by the integration of servers or caused by increased amounts of data.

Job network monitoring

Load balancing functionThis function distributes load by selecting a server among predefined servers whose CPU utilization is low, and executing the job network in that machine.

Renewed screen made available on the webBecause a user can maintain master files in the unit of application group, it simplifies the acceptance of additions and modifications from development environment into production environment.

Multiple job networks can easily be assigned to a single application group for various kinds of process-ing, such as maintaining master files, scheduling, and queuing.

Simplified transition from development to production

Thanks to its capability to distribute loads among systems, which is made possible by a new load-balancing function, system operations can be more stable and job networks can be processed in a shorter time than it previously could.

Stable operation made possible by load balancing

Because the conditions for operating job networks on a server become increasingly complicated, more detailed and precise functions are required, so that system operators can manage the conditions with the least burden. For example, one new function uses the return code of the preceding job to determine which job to process next. This function makes it possible to execute complicated jobs by changing a setting of the master file, without complicating the script for the batch job.

Flexible configuration of job networks

Advanced capability for large-scale systems

The next job can be selected depending on the return code of the preceding job.

A-AUTO monitor

Job networks

Job networks are automatically assigned to a machine with lower CPU utilization.

JOB001 JOB002a

JOB002b

JOB003Return code is not 0.

Return code is 0.

Jobs can be added or deleted on a date preset by the operator.

Monitoring screen

Screen from previous version

Screen from new Ver7.1

The increased scalability and performance of A-AUTO Ver 7.1 enable it to handle larger amounts of data and integrated servers. It provides stress-free control of tens of thousands of job networks a day. The new version offers improvements in the speed of job networks initiation and control, so that any job operations in an increasingly scaled-up open system can be handled perfectly.

A-AUTO Ver 7.1 integrates job network definition, job network monitoring, and system monitoring into one screen on the web. This is an improvement over the earlier version, which required individual client software for each function.

Jobs can be initiated up to 10 times as fast as with the previous version.

A-AUTO provides excel lent se r v i ce to l a rge sys tems formed by the integration of servers or caused by increased amounts of data.

Job network monitoring

Load balancing functionThis function distributes load by selecting a server among predefined servers whose CPU utilization is low, and executing the job network in that machine.

Modifying a scheduleThe operator can view the details of a scheduled job network on the web, and can easily modify the date scheduled for a job network.

Defining a job networkThe definition of a job network can be maintained on the screen easily. Detai led and precise execution conditions for a job network, including the preceding job, starting time, maximum return code, hold and data wait attributes, and execution priority, can be specified.

A-AUTO can be easily operated by almost anyone, without special skills. Therefore, it does not depend on a particular operator, and makes seamless operation possible, even on a complex system.

A-AUTO integrates the management of all batch processes, including mission-critical applications, and processes jobs automatically without requiring particular attention to the platforms or systems being used. Since it has proven compatibility with a wide range of ERP software, monitoring tools, and clustering software provided by various manufacturers and vendors, your choice of tools is wide open.

Monitoring progress of job networksInformation on the execu-tion status of a job network and its preceding and following job networks can be easily monitored on this screen. Automatic e-mail notifica-tion of any failure in the processing of a job network is also available.

A-AUTO operates on two concepts of date: an operation date for overall control of job network processing, and a schedule date for control of the order in which job networks are processed. If for some reason a daily job network cannot be processed on its scheduled day, it must be processed on the following day. Because A-AUTO operates on two concepts of date, the system will process the job network twice on the following day: the job network for the proceeding day followed by the job network for the current day. Another benefit is that, for IT application control, both the originally scheduled date for a job network and the date of its actual execution can be clearly recognized.

Making job management easy

Managing jobs by schedule dates

JOB2 JOB3

Concurrentjobs

JOB13 JOB14JOB11

JOB5 JOB6

Open mainframe server: IBM zSeries

z/OS z/Linux z/Linux z/Linux

for z/Linux for z/Linux for z/Linux

WindowsLinux

IBM System i5(AS400)

for UNIX

for OS400for Oracle E-Business Suite

for Windows

for R/3TM

for Linux

Operation date: April 1 Operation date: April 2

Change of operation date

Schedule date: April 1 Schedule date: April 1

ANET0001 BNET0001

Standardizing job management

A-AUTO makes it possible to distinguish the job network for April 1 from the one for April 2 although these two are in the same job network.

An e-mail will be sent to a designated person if any failure occurs during the processing of a job.

Modifying a scheduleThe operator can view the details of a scheduled job network on the web, and can easily modify the date scheduled for a job network.

Defining a job networkThe definition of a job network can be maintained on the screen easily. Detai led and precise execution conditions for a job network, including the preceding job, starting time, maximum return code, hold and data wait attributes, and execution priority, can be specified.

A-AUTO can be easily operated by almost anyone, without special skills. Therefore, it does not depend on a particular operator, and makes seamless operation possible, even on a complex system.

A-AUTO integrates the management of all batch processes, including mission-critical applications, and processes jobs automatically without requiring particular attention to the platforms or systems being used. Since it has proven compatibility with a wide range of ERP software, monitoring tools, and clustering software provided by various manufacturers and vendors, your choice of tools is wide open.

Monitoring progress of job networksInformation on the execu-tion status of a job network and its preceding and following job networks can be easily monitored on this screen. Automatic e-mail notifica-tion of any failure in the processing of a job network is also available.

A-AUTO operates on two concepts of date: an operation date for overall control of job network processing, and a schedule date for control of the order in which job networks are processed. If for some reason a daily job network cannot be processed on its scheduled day, it must be processed on the following day. Because A-AUTO operates on two concepts of date, the system will process the job network twice on the following day: the job network for the proceeding day followed by the job network for the current day. Another benefit is that, for IT application control, both the originally scheduled date for a job network and the date of its actual execution can be clearly recognized.

Making job management easy

Managing jobs by schedule dates

JOB2 JOB3

Concurrentjobs

JOB13 JOB14JOB11

JOB5 JOB6

Open mainframe server: IBM zSeries

z/OS z/Linux z/Linux z/Linux

for z/Linux for z/Linux for z/Linux

WindowsLinux

IBM System i5(AS400)

for UNIX

for OS400for Oracle E-Business Suite

for Windows

for R/3TM

for Linux

Operation date: April 1 Operation date: April 2

Change of operation date

ANET0001 BNET0001

Standardizing job management

A-AUTO makes it possible to distinguish the job network for April 1 from the one for April 2 although these two are in the same job network.

An e-mail will be sent to a designated person if any failure occurs during the processing of a job.

Scheduling jobs in the proper order is only part of maintaining internal control. Each job must also be registered in the master files by an authorized user. With A-AUTO, you can control each user's operation authority to maintain each file. Also it can log any change to the files for audit purposes, and from that log you can confirm that no unauthorized change has been made.

Security management function for internal control

When the execution of a job network is to be triggered by the creation or update of external files, A-AUTO's "data wait" function enables you to have the job network wait until multiple conditions have been met. A-AUTO/Event monitors the creation or update of the files; when that occurs, it automatically releases the wait conditions set by A-AUTO.

Completely automated procedures, from data arrival to job execution

Users of A-AUTO for mainframe can integrate job management, with those on A-AUTO for Unix, Linux, or MS Windows. A-AUTO for mainframe makes possible not only entirely integrated job management, but also partial utilization of its functions, focusing only on job dependency and leaving the management of individual jobs to individual systems.

A-AUTO V7.1 offers a test mode. Developers can use it to execute test jobs along the production environment. Test mode enables batch libraries to be defined by job network unit. Therefore, in case a part of job network has been modified, there is no need to prepare all the job networks in a development environ-ment. Instead, you can use produc-tion library and configuration. This makes through testing easier.

Test mode function

When? What?Who? How?

Audit trail log

Only the modified job network is set to be executed using the development environment.

Developmentlibraries

Development environment

Production environment

Productionlibraries

ANET0001 ANET0002 ANET0003

ANET0002

File monitoring

Arriveddata

A-AUTO/Event　Agent

A-AUTOmaster files

Master files and schedule informationare centrally managed in mainframe.

Job dependencies

A-AUTO

A-AUTO/Link

A-AUTO basic license A-AUTO basic license

A-AUTO/Link

A-AUTOmaster files

Master files and schedule informationare managed individually.

A-AUTOmaster files

Job dependencies

A-AUTO

A-AUTO/Connect

■ Mainframe centered integration ■ Integrated operations - coexistent with Unix/Linux/Windows

Screen defining each user's authority to maintain master files

When a file defined for an event is created or updated, the data wait conditions are automatically released. It can also be triggered by various kinds of event monitor-ing, such as message monitor-ing and process monitoring.

Scheduling jobs in the proper order is only part of maintaining internal control. Each job must also be registered in the master files by an authorized user. With A-AUTO, you can control each user's operation authority to maintain each file. Also it can log any change to the files for audit purposes, and from that log you can confirm that no unauthorized change has been made.

Security management function for internal control

When the execution of a job network is to be triggered by the creation or update of external files, A-AUTO's "data wait" function enables you to have the job network wait until multiple conditions have been met. A-AUTO/Event monitors the creation or update of the files; when that occurs, it automatically releases the wait conditions set by A-AUTO.

Completely automated procedures, from data arrival to job execution

Users of A-AUTO for mainframe can integrate job management, with those on A-AUTO for Unix, Linux, or MS Windows. A-AUTO for mainframe makes possible not only entirely integrated job management, but also partial utilization of its functions, focusing only on job dependency and leaving the management of individual jobs to individual systems.

A-AUTO V7.1 offers a test mode. Developers can use it to execute test jobs along the production environment. Test mode enables batch libraries to be defined by job network unit. Therefore, in case a part of job network has been modified, there is no need to prepare all the job networks in a development environ-ment. Instead, you can use produc-tion library and configuration. This makes through testing easier.

Test mode function

When? What?Who? How?

Audit trail log

Only the modified job network is set to be executed using the development environment.

Developmentlibraries

Development environment

Productionlibraries

ANET0001 ANET0002 ANET0003

ANET0002

File monitoring

Arriveddata

A-AUTO/Event　Agent

A-AUTOmaster files

Master files and schedule informationare centrally managed in mainframe.

Job dependencies

A-AUTO

A-AUTO/Link

A-AUTOmaster files

Job dependencies

A-AUTO

A-AUTO/Connect

■ Mainframe centered integration ■ Integrated operations - coexistent with Unix/Linux/Windows

Screen defining each user's authority to maintain master files

When a file defined for an event is created or updated, the data wait conditions are automatically released. It can also be triggered by various kinds of event monitor-ing, such as message monitor-ing and process monitoring.

A-AUTO provides interfaces with ERP tools such as SAP R/3 and Oracle E-Business Suite. With its excellent job-scheduling functions, A-AUTO manages batch jobs on ERP and controls their execution. Thus A-AUTO makes it possible to connect jobs on other systems with jobs on ERP, and thus to standardize the operations management of all systems.

A-AUTO with ERP (Enterprise Resource Planning)

To build a data warehouse (DWH), data from various sources must be extracted and processed. A de facto standard software of an ETL tool reduces the workload required for processing and converting data during system development. A-AUTO can control jobs created by this tool just as it can control other jobs. With this interface, Waha!Transformer®, works as an automation system of data transformation and reduces operations management load significantly for DWH system.

DWH interface

A-AUTO/Mail connects data attached to e-mails sent or received with data processed by applications. A-AUTO/Mail makes it possible to automatically extract file(s) attached to email you receive, or automatically attach file(s) to e-mail that you send.

E-mail integration

The A-AUTO/Reports function is provided to meet users' requirements for such tasks as releasing information on scheduled jobs managed by A-AUTO to end users or summarizing master information in a report so that schedules can be checked in advance.

Operations management report *Japanese only

System configuration of A-AUTO for R/3 System configuration of A-AUTO for Oracle EBS (example)

A-AUTOmaster file

Job execution control for R/3

Job JobABAP

Concurrent job

Job execution control for Oracle EBS

Job JobConcurrent job

A-AUTO remote license

A-AUTO for R/3 AUTO R3definition file

OracleEBS

Job execution control

Job execution control Jobexecutioncontrol

R/3 DB server

R/3 AP serverA-AUTO for R/3 BWinterface option

BW Server

Operations management server Operations management server

A-AUTO for OracleEBS

Oracle EBS server

ABAP execution control

SAP R/3 system

Concurrent jobs

BW InfoPackageexecution control

Job for executingconcurrent jobs

ETL tool

Database

Operation tool

Arrival monitoringCreation monitoring

Integrity checkRecovery

Failure notification・・

ExecutionMonitoringRecovery

Failure notificationConnection with applications

・・

CreationEdit

ProcessingConversionLoadingTransfer

Hyperion EssbaseIBM Red Brick WarehouseMicrosoft SQL ServerOracleIBM DB2

Data Data Job

* "Waha!Transformer®" is a registered trademark of Beacon Information Technology Inc.

On this report the correlation of preced-ing and following job networks can be viewed in flowchart format.

On this report, the scheduled dates for job networks can be viewed in list format.

Monitoringon receiptof e-mail

Sendinge-mail

Mail server

Applicationdata

Monitoring receivede-mail and extracting

attached files

Monitoring arrived filesand sending email with

the files attachedA-AUTO/Mail

Connectionwith

applications

Connectionwith

applications

A-AUTO provides interfaces with ERP tools such as SAP R/3 and Oracle E-Business Suite. With its excellent job-scheduling functions, A-AUTO manages batch jobs on ERP and controls their execution. Thus A-AUTO makes it possible to connect jobs on other systems with jobs on ERP, and thus to standardize the operations management of all systems.

A-AUTO with ERP (Enterprise Resource Planning)

To build a data warehouse (DWH), data from various sources must be extracted and processed. A de facto standard software of an ETL tool reduces the workload required for processing and converting data during system development. A-AUTO can control jobs created by this tool just as it can control other jobs. With this interface, Waha!Transformer®, works as an automation system of data transformation and reduces operations management load significantly for DWH system.

DWH interface

A-AUTO/Mail connects data attached to e-mails sent or received with data processed by applications. A-AUTO/Mail makes it possible to automatically extract file(s) attached to email you receive, or automatically attach file(s) to e-mail that you send.

E-mail integration

The A-AUTO/Reports function is provided to meet users' requirements for such tasks as releasing information on scheduled jobs managed by A-AUTO to end users or summarizing master information in a report so that schedules can be checked in advance.

Operations management report *Japanese only

System configuration of A-AUTO for R/3 System configuration of A-AUTO for Oracle EBS (example)

A-AUTOmaster file

Job execution control for R/3

Job JobABAP

Concurrent job

Job execution control for Oracle EBS

Job JobConcurrent job

A-AUTO for R/3 AUTO R3definition file

OracleEBS

Job execution control

Job execution control Jobexecutioncontrol

R/3 DB server

R/3 AP serverA-AUTO for R/3 BWinterface option

BW Server

Operations management server Operations management server

A-AUTO for OracleEBS

Oracle EBS server

ABAP execution control

SAP R/3 system

Concurrent jobs

BW InfoPackageexecution control

Job for executingconcurrent jobs

ETL tool

Database

Operation tool

Arrival monitoringCreation monitoring

Integrity checkRecovery

Failure notification・・

ExecutionMonitoringRecovery

Failure notificationConnection with applications

・・

CreationEdit

ProcessingConversionLoadingTransfer

Hyperion EssbaseIBM Red Brick WarehouseMicrosoft SQL ServerOracleIBM DB2

Data Data Job

* "Waha!Transformer®" is a registered trademark of Beacon Information Technology Inc.

On this report the correlation of preced-ing and following job networks can be viewed in flowchart format.

On this report, the scheduled dates for job networks can be viewed in list format.

Monitoringon receiptof e-mail

Sendinge-mail

Mail server

Applicationdata

Monitoring receivede-mail and extracting

attached files

Monitoring arrived filesand sending email with

the files attachedA-AUTO/Mail

Connectionwith

applications

Connectionwith

applications

Kobe Steel, Ltd. (hereafter "Kobe Steel"), has been a leading iron and steel producer in Japanese and global markets since its foundation in 1905. It holds the largest share in various industrial segments, ranging from iron and steel and welding products (such as steel plates and wire rods) to aluminum and copper, industrial machinery, and construction machines.One of its group companies, Kobelco Systems Corporation (hereafter "Kobelco Systems), provides a variety of IT services, such as consulting, system integra-tion, and outsourcing in various areas including product design, production planning, and logistics of the products Kobe Steel produces. Kobelco Systems also has strength in IT infrastructure solutions, including data center solution.Kobe Steel is currently collaborating with Kobelco Systems on the transition of its headquarters' business systems to open systems. In 2006, as a part of the project, it began a major shift of the headquarters accounting system to a new system that uses BSP's job management software, A-AUTO. This shift took only about a year. Regarding the project, BSP has recently interviewed Mr. Nobutaka Koga and Mr. Masahiro Kanto of the IT Planning Department of Kobe Steel and Mr. Masaki Nakanishi and Mr. Seiji Okubo of the Strategic Outsourcing Group of Kobelco Systems headquarters.

Case study: Kobe Steel Ltd.Facilitating Migration to Open Systems by Use of A-AUTOBy sharing information and preparing thoroughly, Kobe Steel's migration team achieved a smooth, relatively fast transition from its legacy systems to open systems.

Migration to IT infrastructure on the open systems for the next generation was conducted aggres-sivelyKobe Steel headquarters is working to renovate its IT infrastructure by migrating from its mainframe-based system to open systems by the end of March 2012. In the former system environment, every revision of applicable laws and regulations required a modification, which entailed high costs for maintenance. Another major problem was that the many changes and modifica-tions had made the system so complicated that overall control and management were difficult.Taking all this into consideration, the company determined to place open

systems taking the maximum advantage of application packages as a core of the new system, and set a goal to establish an IT infrastructure that would offer high availability, low operational cost, and the ability to adapt flexibly to future modifica-tions and extensions.The company launched full-scale discus-sions for the renovation of the accounting system in 2006, and began planning and designing a new system architecture based on application packages. In April 2007, Kobe Steel set up a test environ-ment and the preparation for the full-scale development phase started.A-AUTO was selected for the job manage-ment of the new accounting system. Said Mr. Koga, "Internally developed operation

tools had been used on the mainframe, but as part of our move to the open systems we had already adopted A-AUTO to manage jobs on open systems, such as those on financial and HR systems. Our choice for the new accounting system was also A-AUTO. Because so far we have encountered no problems in operations management, we believe that there is no reason to install any job management software other than A-AUTO."

Throughout the project, all of the team members shared the same awareness and purposeIn the migration project, the highest emphasis was placed on establishing the framework, by preparing thoroughly and

selecting the team members carefully. It was very important to ensure that all of those involved in the project would achieve a consensus and a common awareness in the transition process. "The project was expected to involve 100 to 200 members at the peak period," said Mr. Nakanishi. "We believed that it would succeed only if all members united their efforts. Because we prepared as carefully, and devoted all of the time and effort needed, the system development was completed in about six months." Mr. Nakanishi commented.The hardest part of the development was to validate the output from the new system. They needed to be compared every day against the output from the current system. All these checks required much time and patience. Having them done by a single staff member could easily have led to mistakes or low performance, and the validation would have taken two or three months. Therefore, the project team developed a procedure by which the workload was shared by multiple staff members, in cooperation with operation staff of the old system.Reflecting on the difficulties he faced, Mr. Kanto said, "A-AUTO was adopted in the expectation that it would work as an effective tool for job management covering the interface processing between multiple

systems. We needed some efforts to control EAI tool. At the beginning of the project, we did not plan to have a test environment for A-AUTO but we ended up to set up one and tested job scheduling carefully before going into the production." The support services provided by BSP made a large contribution to the success of the project. Mr. Okubo rated BSP's services highly, commenting, "When I sent an e-mail to my BSP contact asking questions on something I did not under-stand, I received a prompt reply within 20 to 30 minutes. Thanks to the quick, kind, and complete responses to my e-mails, I was able to bring the project forward smoothly without delaying the validation processes.

With the best formation of the team, successful migration of the system was finally completed.In April 2008, the project was about to switch over to the production phase. This was the final stage of the project, allowing no mistake. To migrate all the data for the full-year financial closing to the new system, Kobe Steel planned to process its financial data on the old system up to the account-closing transactions for the term ending March 2008, and therefore, keep the old system operating even after the cutover of the new system. That means

that two systems would be running in parallel. The migration process was tackled by a carefully chosen team, in which the opera-tion and development staff of the old system collaborated closely with the project team. As the project was handled mainly by people fully familiar with both systems, operations of the new system after migration went smoothly. This was the key to the success of the migration.In May 2008, the complete migration to the new accounting system was finished in a short time, without any major problem. It was an excellent accomplishment. Its success was due to the careful and detailed making of plans and selection of team members, and the enthusiastic efforts of all of those involved.With this project successfully completed, Kobe Steel is now working on a second one, scheduled for completion in April 2010. The next goal is to standardize the format of all data connections among the companies in headquarters. This will lead to the integration of the systems of all of these companies, and ultimately that of the entire Group. The challenges of Kobe Steel and Kobelco Systems are far from over, but past performance makes success seem assured.

● Headquarters (Shinko building)● Back-up environment of Kobe Steel's SAS (Nadahama)

Windows2003 Windows2003

● New accounting system (Nadahama)

Windows 2003 (test) Windows 2003 (test)

● Job management (Nadahama)

Windows 2003 (back-up) Windows 2003 (production) Windows 2003 (test)

…A-AUTO/Client

A-REMOTE/Win A-REMOTE/Win A-REMOTE/Win A-REMOTE/Win

A-REMOTE/Win A-REMOTE/Win

A-AUTO/WinA-SUPERVISION

Server

■ System configuration of new accounting system of Kobe Steel using A-AUTO

Mr. Seiji Okubo Headquarters Technical Development OfficeService Business DivisionStrategic Outsourcing Group, Department IKobelco Systems Corporation

Mr. Masaki NakanishiSection ChiefHeadquarters Technical Development OfficeService Business DivisionStrategic Outsourcing Group, Department IKobelco Systems Corporation

Mr. Masahiro KantoIT Planning DepartmentKobe Steel, Ltd.

Mr. Nobutaka KogaIT Planning DepartmentKobe Steel, Ltd.

Server

A-AUTO/Client

A-SUPERVISIONClient

Company Name: Kobe Steel, Ltd.Founded: 1905Description of Business: Iron and steel products, wholesale power supply, aluminum and copper products, machinery, construction machinery, real estate and other businesses.ＵＲＬ: http://www.kobelco.co.jp/

Company Name: Kobelco Systems CorporationFounded: 1983Description of Business: Consulting services, design, development, and maintenance for business systems and networks, outsourcing and other servicesＵＲＬ: http://www.kobelcosys.co.jp/

KOBE STEEL GROUPKOBE STEEL GROUP

Windows 2003 (production)