0% found this document useful (0 votes)
65 views4 pages

Project Worked

The document discusses the roles and responsibilities of an Enterprise Integration Architect/Manager. Key responsibilities include managing the integration artifacts repository, defining the integration architecture, and monitoring and supporting integration development and requirements. The role is also responsible for cataloging integrations across the enterprise and performing daily monitoring to proactively address issues. Several integration projects are described, including using JMS to send employee timesheets to SAP and designing XML integration between carriers and automakers.

Uploaded by

vadivel.km1527
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
65 views4 pages

Project Worked

The document discusses the roles and responsibilities of an Enterprise Integration Architect/Manager. Key responsibilities include managing the integration artifacts repository, defining the integration architecture, and monitoring and supporting integration development and requirements. The role is also responsible for cataloging integrations across the enterprise and performing daily monitoring to proactively address issues. Several integration projects are described, including using JMS to send employee timesheets to SAP and designing XML integration between carriers and automakers.

Uploaded by

vadivel.km1527
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Project worked on

SMS & Mobile server –Jms to send and receive message and different protocols and when ever the
changes are made to the configuration the same data has to be published to the program to use the
same.

Websphere Mq to send and receive data from the sales counters to the central ware-house about
the sale
Ware house

Sales Point Sales Point Sales Point Sales Point

using above architecture

Sending Employees daily approved time sheet SAP from all the application server using JMS and
from JMS the service get the aggregated data and push the data to SAP the same will be used for
inter company invoicing.

Design and developed the Ford EDI and XML data from the carriers of the Jaguar and Landrover cars
made in UK and send to US.

EDI will have control data and exact data will be available. Segregating data and control data and
validating the same.

Development of reports and data download are intiated and the same will be processes in back end
and the file is generated and the user can download the file after entering to the applicatons using
Command pattern with search criteria.

As Enterprise Integration Architect/Manager

I am responsible for the Integration artifacts repository and the architecture and monitoring ,
support the Integration and development with regarding to the requirements.
PI/PO
SAP TAFE
Windchill Azure

SAP TMTL Webmethod


s
MES
Portal Application
B2B External Service

We have the catalog of integration done in the enterprise and also we do monitoring every day to
proactively solve the issues.

Also we have

Four Of the TOGF Features are used

All the below are done for a business requirement that is said to be Business Architecture

 Data Architecture Information system


 Application Architecture Information system
 Technology Architecture
 Architecture Change management

Eg Businees requirement: VSME/JIT process at TAFE Or Business Architecture.

Business requirement -: We have to get the material for a tractor when one tractor is rollout .

Step 1 select the reference model:

We had selected Mr Furahsi from japan who implemented the same in multiple automotive
companies Developed Use case documents.

Step 2: Develop Baseline Business Architecture Description

Businees architecture at least they should have Kanban trigger to vendor before that is the baseline
for all the vendors to be in the system.So that in the same mode we can trigger the VSME also.

Step 3: Define candidate roadmap components

From the planning and sequencing system which knows the next model to be build has to send the
trigger to the vendors for parts which has to pick from the stores and one hour production or one
day production depends upon the vendor configuration the trigger will be generated and shown to
the vendor to send the materials to TAFE.

Step 4: Conduct formal stakeholder review

Had a review that how and what are the process to be newly improved in the sytem that the user
have to take care and how it will work and have the review with them.

Business befit like TAFE don’t want to hold big amount of stock and space for whare housing in one
plant is used for another bay for building tractor efficiently.

Step 5: Create Architecture Definition Document

Create a Architecture definition document having who will be working on which process and how it
will helpful for the system Like receiving officer new role to receive goods and get the sign off from
business on the following documents use case documents and process flow document.

Data Architecture Information system

Step 1:Select reference model view point and tools

Selected reference model a Kanban trigger from the base system.

Step 2: Develop Target Data Architecture Description

Step 3: Define candidate roadmap components

Step 4: Conduct formal stakeholder review

Defining CIA rrating for those data transfer from one system to other
Defining the process

Step 5:Fianlize the Data Architecture

Application Architecture

Step 1:Select reference model view point and tools

Already we are showing the Kanban data from SAP to vendor portal

Step 2: Develop Target Application Architecture Description

Step 3: Define candidate roadmap components

Step 4: Conduct formal stakeholder review

Defining the process by the different application side and the suer should be having acces to the
applications and the process adherence to have the system to work smooth.

Step 5:Fianlize the Application Architecture

Technology Architecture:

Step 1:Select reference model view point and tools

Already we are showing the Kanban data from SAP to vendor portal

Step 2: Develop Target Technology Architecture Description

Step 3: Define candidate roadmap components

Step 4: Conduct formal stakeholder review

Defining the process by the different application side and the suer should be having acces to the
applications and the process adherence to have the system to work smooth.

Step 5:Fianlize the Technology Architecture


Opportunities and solution

Implemetation govrnance

Architecture Change Management

You might also like