AIM

TA.020 TECHNICAL ARCHITECTURE

BASELINE
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: June 2, 1999
Last Updated: June 2, 1999
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Document Control

Change Record
1

Date Author Versio Change Reference

n

2-Jun-99 <Author> Draft No Previous Document

1a

Reviewers

Name Position

Distribution

Copy Name Location

No.

1 Library Master Project Library

2 Project Manager
3
4

Note To Holders:

If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document
control purposes.

If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Contents

Document Control.......................................................................................ii

Introduction................................................................................................iv
Purpose................................................................................................iv
Data Centers/Hosting Facilities...................................................................v
<Data Center 1/Hosting Facility>.........................................................v
<Data Center 2/ Hosting Facility >.......................................................v
Applications...............................................................................................vi
Existing Application Summary..............................................................vi
Application Usage by Business Units....................................................vi
Application Interfaces...............................................................................viii
Existing Interfaces Summary..............................................................viii
Hardware (Platforms).................................................................................ix

Network Architecture..................................................................................x
Network Diagram...................................................................................x
Peripheral Devices.....................................................................................xi

System Management................................................................................xii
Current System Availability.................................................................xii
System Management Procedures and Tools........................................xii
Expected Architecture Changes...............................................................xiii

Areas For Improvement............................................................................xiv

Open and Closed Issues for this Deliverable.............................................xv

Open Issues.........................................................................................xv
Closed Issues.......................................................................................xv

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Introduction

Purpose

The purpose of the Current Technical Architecture Baseline

document is to describe the existing application and technical
architecture of the components of <Company Long Name> within the
scope of the <Project Name>. The existing architecture may need to be
documented early on in the project for several reasons.

Reuse of existing infrastructure, hardware and/or networks. To be

able to redeploy or reuse the existing infrastructure for the application
and technical architecture, an understanding of what exists currently is
needed.

Replacement of existing systems. Business and technical analysts on

the project may need at least some elementary knowledge of the
applications they are replacing in order to be able to map business
processes onto the new applications, and design technical solutions.

Integration with retained existing systems. Business and technical

analysts on the project will need a knowledge of the applications and
technology they are attempting to integrate with.

Integration cross check. Cross check all existing interfaces have either
been subsumed by the new applications or have been identified as being
replaced wholly or partially by new interfaces.

The deliverable provides a summary of what is in existence currently and

helps ensures that nothing is missed. The existing architecture can
potentially affect significant parts of the eventual proposed architecture
and the new systems that are to be configured and integrated.

This deliverable is a useful summary of the existing infrastructure for the

following processes in the <Project Name> project:

• Application and Technical Architecture

• Data Conversion
• Module Design and Build (especially Interface modules)
• Business Requirements Mapping

However, any individual in the <Project Name> project team should have
access to this deliverable for reference purposes.

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Data Centers/Hosting Facilities

This section describes the data centers and hosting facilities within
<Company Short Name>‘s current architecture and the applications,
systems and user communities they support.

<Data Center 1/Hosting Facility>

<Describe the data center/hosting facility here>

<Data Center 2/ Hosting Facility >

<Describe the data center/hosting facility here>

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Applications
This section describes the current applications that handle the processing
within <Company Short Name>‘s current architecture.

Existing Application Summary

The following table lists the applications within <Company Short Name>’s
current architecture.

Application Description Vendor Architectu Database Version

Name re

General Financial Bann 2-Tier CS Oracle 3.5

Ledger
Payables Financial Baan 2-Tier CS Oracle 3.5
Order Entry Sales Order Baan 2-Tier CS Oracle 3.5
Admin
Web OE Sales Order Internal 3-Tier Web Oracle 1.1
Admin

Application Usage by Business Units

This section lists the business units that access or process within each
existing application.

Applicatio Databas Business Site # of Named Access

n Name e Name Organizatio Users Method
n /Concurrent
Users

General PROD Corp Finance Reston, VA 142 Client-

Ledger Hamburg, Gr 245 Server

<Application Name>
Description

<Describe the application here>

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999
Supported Processes

<Describe the processes or functions the application supports here>

Technical Description

<Describe the technical architecture and functioning of the application

here>

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Application Interfaces
This section describes the current interfaces in <Company Short Name>‘s
architecture.

Existing Interfaces Summary

The table on the following page summarizes the main specifications for
the interfaces within the scope of the <Project Name> project.

Source Destinatio Mechanis Business Triggerin Frequen Data

Applicatio n m Objects g Event cy Volume
n Applicatio Transferre
n d

Leasing General Auto GL Journals Trx Exist Nightly 200/Nt

Ledger Interface (JEs)

Existing Interfaces Diagram

<Include a diagram of the existing application interfaces here>

<Application Interface>
Description

<Describe the application interface here>

Supported Processes

<Describe the processes or functions the application interface supports

here>

Technical Description

<Describe the technical architecture and functioning of the application

interface here>

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Hardware (Platforms)
This section describes the current computing platforms in <Company
Short Name>‘s architecture.

Platfor Platfor Platfor OS & # of Memor Disk Appl. Databas

m m m Versio CPUs y /MB Spac e
Name Vendor Model n e /GB

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Network Architecture
This section describes the architecture and capacity of <Company Short
Name>‘s current networks.

Seq. Network Location Network Location Node 2 LAN/ WAN

No. Node 1 Node 1 Node 2

1 Data Center Milan Italy Office Toronto, Cdn WAN

Seq. LAN O/S , Topology Service Vendor Protocol Capacity

No. File Mbps/Latenc
Server y

1 NA Digital Leased MCI/Worldcom TCP/IP 1000

Network Diagram

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Peripheral Devices
This section describes the peripheral devices in <Company Short
Name>’s current systems architecture.

Device Type Device Name Location Purpose Organization

Usage

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

System Management
This section discusses the systems management metrics, tools and
procedures that are used to manage the current <Company Short
Name>‘s systems architecture.

Current System Availability

<Describe the availability metrics for the current systems here>

System Management Procedures and Tools

<Describe or reference existing system management procedures and

tools here>

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Expected Architecture Changes

This section documents expected changes to <Company Short Name>’s
baseline architecture during the implementation time frame.

The expected changes are in summary:

1.
2.
3.

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Areas For Improvement

This section describes specific opportunities for improvement in
<Company Short Name>’s business based on the findings of the baseline
analysis.

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TA.020 Technical Architecture Baseline Doc Ref: <Document Reference Number>
June 2, 1999

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Impac

Date t Date

Closed Issues

ID Issue Resolution Responsibility Target Impac

Date t Date

<Subject> Open and Closed Issues for this Deliverable

File Ref: 51173101.doc (v. DRAFT 1A )
Company Confidential - For internal use only