AIM

TA.100 ARCHITECTURE SUBSYSTEMS

PROPOSAL
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: April 26, 2007
Last Updated: April 26, 2007
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
TA.100 Architecture Subsystems Proposal Doc Ref: <Document Reference Number>
April 26, 2007

Document Control

Change Record
1

Date Author Version Change Reference

26-Apr-07 <Author> Draft 1a No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

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: 358736885.doc (v. DRAFT 1A )
TA.100 Architecture Subsystems Proposal Doc Ref: <Document Reference Number>
April 26, 2007

Contents

Document Control................................................................................................

Executive Summary..............................................................................................
Purpose...........................................................................................................
Introduction....................................................................................................
Background and Problem Statement..............................................................
Proposed Subsystem......................................................................................
Scope..............................................................................................................
Financial.........................................................................................................
Assumptions...................................................................................................
Risks...............................................................................................................
Background..........................................................................................................
Introduction....................................................................................................
Approach........................................................................................................
Proposed Subsystem......................................................................................
Background and Problem Statement..............................................................
Subsystem Requirements................................................................................
Approach........................................................................................................
Subsystem Integration....................................................................................
Diagram..........................................................................................................
Assumptions...................................................................................................
Open and Closed Issues for this Deliverable........................................................
Open Issues....................................................................................................
Closed Issues..................................................................................................

<Subject> Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. DRAFT 1A )
 Doc Ref:

Executive Summary

Purpose

The purpose of the Architecture Subsystems Proposal document is to identify

and propose the <Subsystem Name> needed to support and provide services
within <Company Short Name>s architecture.

Introduction

<Company Long Name> is undertaking the <Project Name>. During the

initial planning stages of the <Project Name>, it was understood that business
requirements may drive the need to propose additional project activities to support
the implementation of additional subsystems.

Background and Problem Statement

Proposed Subsystem

With the support of the project management team, we would like to propose the
establishment of additional funding and resources to address the implementation of
the following subsystem:
q
q
q
These benefits are achieved through the provision of these features:
Visibility to live production data by executive management
Proactive generation of warnings to all levels of management when
KPIs fall outside of preset boundaries
Real-time, world-wide consolidated forecasting via the web

Scope

Financial

Budgetary Requirements

Resource Requirements

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )
 Doc Ref:

Physical Requirements

Forecasted Return on Investment

Benefits
Improved customer service
Earlier intervention on production problems
Improved performance to targets
Improved utilization of production and transportation facilities
Improved sales performance management

Assumptions

<Assumption Name>

Risks

<Risk Name>
<Sentence Describing Risk>

<High|Medium|Low>

Consequence: <Consequence is Risk Does Occur>

Contingency: <What Can Be Done if the Risk Occurs>

Early Mitigation: <What Can Be Done to Avoid the Risk Coming True>

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )
 Doc Ref:

Background

Introduction

Architecture subsystems are considered to be components of information systems.

They provide enterprise-level services to the information systems architecture.
These types of architecture component generally impact multiple applications or
installations. Examples of such subsystems might include:
data distribution system (interface infrastructure) that links and
distributes data between multiple application databases
global data registries subsystems that distribute key reference business
objects across an enterprise (and would need a data distribution subsystem)
operational data repository that is synchronized to provide real-time
information about the state of business (and would need a data distribution
subsystem)
critical third party application package that needs to integrate with
multiple transaction systems at the enterprise level
data warehouse receiving input from multiple transaction systems
electronic commerce system that processes multiple types of inbound
and outbound business documents and transactions
intranet and internet interface to application systems for the use of
business users across the enterprise
OLAP facilities
business intelligence systems

Approach

It is often prudent to separate the specification, design, and build of these

subsystems into separate subprojects linked to the core Application and Technical
Architecture process, because of the:
possible impact of the subsystems on the overall systems architecture
and on multiple individual technical groups working in the project
risk associated with such complex custom development
Therefore a subsystem may be synonymous with a development subproject but
need not necessarily be. In this particular case we recommend that the
implementation of the subsystem be carried as a separate project to commence
post-cutover in to production of the Oracle Applications.

Proposed Subsystem

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )
 Doc Ref:

This <Subsystem Name> subsystem is

Background and Problem Statement

This section discusses the background to the proposal and the problem statement
for the <Subsystem Name> subsystem.

Subsystem Requirements

This section discusses the high level requirements for the <Subsystem Name>
subsystem.

Scope

Constraints

Risks

Objectives

Critical Success Factors

Benefits

Milestones

Approach

Project Methods

Project Deliverables

Organization

Relationship to Other Projects/Subprojects

Subsystem Integration

This section discusses the integration points for the <Subsystem Name>
subsystem with other applications, databases and systems within <Company
Short Name>s architecture.

Summary of Integration Points

The table in this section summarizes the integration points for <Subsystem
Name> subsystem.

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )
 Doc Ref:

Source Destination Business Business Event Projected

Application Application Process Object(s) Data Volume
Transferred

Detailed Discussion of Integration Points

Diagram

Assumptions

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )
 Doc Ref:

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Open and Closed Issues for this Deliverable

File Ref: 358736885.doc (v. )