AIM
TA.030 PRELIMINARY CONCEPTUAL ARCHITECTURE
Author: Creation Date: Last Updated: Document Ref: Version:
May 27, 1999 August 21, 2009 DRAFT 1A
Approvals:
Copy Number
_____
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Document Control
Change Record
3
Date 27-May-99
Author
Version Draft 1a
Change Reference No Previous Document
Reviewers
Name
Position
Distribution
Copy No. 1 2 3 4
Name Library Master
Location Project Library Project Manager
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.
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Document Control
ii
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Contents
Document Control .................................................................................................................. ii Introduction ............................................................................................................................. 1 Purpose ............................................................................................................................. 1 Sources .............................................................................................................................. 1 Business Operations ............................................................................................................... 2 Key Business Organizations and Functions ................................................................. 2 Financial Structure........................................................................................................... 3 Major Business Processes................................................................................................ 3 Data Center and Hosting Facility Operations..................................................................... 4 Data Center/Hosting Facility - .............................. 4 Business Information Model.................................................................................................. 5 Information Flows ........................................................................................................... 5 Information Access .......................................................................................................... 5 Key Applications..................................................................................................................... 7 Existing Applications Retained...................................................................................... 7 Replacement Applications .............................................................................................. 7 Conceptual Architecture ........................................................................................................ 8 Analysis of Architecture Model ..................................................................................... 8 Project Environment Architecture ...................................................................................... 10 Server Environments ..................................................................................................... 10 Server Capacity Requirements .................................................................................... 11 Client Environments...................................................................................................... 12 Open and Closed Issues for this Deliverable .................................................................... 13 Open Issues..................................................................................................................... 13 Closed Issues .................................................................................................................. 13
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Document Control
iii
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Introduction
Purpose
The purpose of this document is to provide a reference at any time for resources working on the Application and Technical Architecture of the . This document is used to circulate for feedback and support of the entire project team to proposed conceptual approaches to resolving architecture requirements. This document is also the source for current application and technical architecture information for project team members in processes with a dependency on the high level architecture model for ’s future information systems. This document describes: high level business operations requirements for the future architecture data center operations requirements for the future architecture high level conceptual view of each of the integrated application and technical architecture models for the business conceptual approaches to resolving architecture requirements as defined in the Architecture Requirements and Strategy document advantages and disadvantages of each conceptual architecture model preferred architecture model out of the candidate architectures The Conceptual Architecture is a critical milestone in the development of security, reporting, application, database and application server, and network architectures.
Sources
This Conceptual Architecture document was prepared with input from the following sources: Project Management Plan [PJM.CR.010, initial complete], produced in task PJM.CR.030, for the Architecture Requirements and Strategy (TA.010) for the
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Introduction
1 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Business Operations
is a:
Key Business Organizations and Functions
Business Organization
Site
Business Functions
Business Organizations Serviced
Comments
The following diagram represents the geographical distribution of business operations:
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Business Operations
2 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Financial Structure
Chart of Accounts Revenue Recognition Corporate Finance Subledgers and Local General Ledgers Consolidation Approach Intercompany Settlements
Major Business Processes
The following are the key business processes that will significantly affect the application architecture:
Sales and Market Management Order Fulfillment Post Sales Service Procurement Operations Materials Management Planning and Forecasting
Product Development Financial Management Human Resource Management Enterprise Management Quality Management Information Technology Management
Sales and Market Management
Order Fulfillment
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Business Operations
3 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Data Center and Hosting Facility Operations
Data centers and hosting facilities which support 's information needs are located in the following cities and countries:
Location Istanbul, Turkey Serves Business Organizations All in Europe, Middle East Company Owned or Managed Hosted Facility by Inkora Facilities Plc. (Istanbul, Turkey)
The following diagram represents the geographical distribution of the data centers:
SIT E: LOCAT ION: FUNCT ION: SIT E: LOCAT ION: FUNCT ION: EMPLOYEES: <# emps> EMPLOYEES: <# emps>
SIT E: LOCAT ION: FUNCT ION: EMPLOYEES: <# emps>
SIT E:
Update the diagram to ref lect the key sites and operations in y our business
LOCAT ION: FUNCT ION: EMPLOYEES: <# emps>
Data Center/Hosting Facility -
Current Operations Planned Operations
Data Center and Hosting Facility Operations File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
4 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Business Information Model
Information Flows
The information model describes the information flows that result from the key business processes executed in the corporation. The information flows documented here are associated with the following business processes:
Sales Commission Data
Legacy HR
Legacy Sales & Marketing
Legacy Budget System
Manman GL
Labor Availabilit y
ENG
Labor Requirement s
Sales Order Feedback
Oracle Applications
C U S T O M E R S
Budget Upload Import Financia l Data
Engineering Change Order Design
Engineerin g Change Request
Forecast Data Products / Component s
Sales Order Data
Customer Informatio n
Sales Orders
Invoices
Payment s
BOM
INV
Order Shipmen t Data Shipped Sales Orders
OE
Shipped Orders
AR
Invoice & Collectio n Data
GL
MPS/ MRP
Receipt Accrual
Material Requirement s Finished Goods
Internal Requisition s
Invoices/ Payments
External Reports Assets/ Depreciation
Planned Orders
PO WIP
Matched Invoices
AP
Asset Addition s
FA
Resource Costs
Raw Materials & WIP Material Costs
Purchase Orders Materials / Supplies
Invoices for Payment
Payment s
S U P P L I E R S
COST
Costs
Information Access
The information model describes the access to information that business units need in order to execute the business process steps in which they provide services without compromising the integrity and security of the enterprise information as a whole. Information access is concerned with: information (data) partitioning to provide security and maintain integrity information (data) aggregation, consolidation, and summation to provide appropriate reporting views of the state of the business
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Business Information Model
5 of 13
TA.030 Preliminary Conceptual Architecture
Information Security Ownership of Reference (Master) Data Objects
Doc Ref: XXX 0, 0000
The following sets of (reference) master data objects are important for the business:
Chart of Accounts Part Master Vendor Master Customer Master The security and ownership policies and requirements relevant to the creation, change, or deletion of these master data objects are: Information Aggregation, Consolidation, and Summation
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Business Information Model
6 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Key Applications
This section describes the major or key applications that will be part of the future architecture.
Existing Applications Retained
The following key applications will be retained in the future architecture: Application -
Replacement Applications
The following key replacement applications will be added in the future architecture: Application -
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Key Applications
7 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Conceptual Architecture
Following is a summary of the architecture conceptual approaches to requirements defined in the Architecture Requirements and Strategy (TA.010). Information Systems Organization Application Deployment Applications Architecture User Desktop and User Interfaces Foreign Currency and National Language Support Data and System Security Reporting Systems Business Intelligence Systems Strategic Enterprise Management (SEM) Systems Workflow Automation eCommerce and Internet Based Functions Authentication Services Telephony/Call Center Automation Systems System Availability Technical Architecture and Enabling Technology Platform and Networks Mobile Computing Support Specialized Printing Systems Custom Development Interface Requirements Integration with Other Information Systems Approximate System Capacity
Analysis of Architecture Model
Business Advantages The perceived advantages of this conceptual architecture option are:
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only Conceptual Architecture 8 of 13
TA.030 Preliminary Conceptual Architecture
Business Disadvantages
Doc Ref: XXX 0, 0000
The perceived disadvantages of this conceptual architecture are: Major Custom Extensions or Modifications Needed To support this conceptual architecture, the following custom extensions or modifications are likely to be needed: Risks
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Conceptual Architecture
9 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Project Environment Architecture
This section describes the architecture for the project environments. will initially use a single series of servers for training, mapping, and development environments. The specific Oracle Applications environments required are: Seed Data Demo Development Test Production
Server Environments
This diagram illustrates the database environments installed on the project server. Boxes that resemble buildings with a roof represent an application environment— shared executable code and environment variables that identify application directories. Multiple databases may share the same environment for executables, concurrent log and output files, and so on. The database names correlate to the database instance names (ORACLE_SID).
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Project Environment Architecture
10 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
Development Server: Server Class:
APPLTEST
APPLSYS
DEMO
TEST
FINPROD
(FND, GL, PO, AP, AR, OE)
SHADOW
APPLDEV
CASE
APPDEV
(Customization Development)
CONVTEST
(Conversion T esting)
Application Extensions and Modifications
Server Capacity Requirements
Server Processing Capacity Server Disk Capacity Preliminary server sizing has been performed for the project servers using the Oracle Applications Sizing Spreadsheet. The results are summarized below with additional requirements for operating system and software tools. Note that these are servers to support the development of the production environments. The production environments are sized elsewhere. The forms server and the database server are segregated for each environment. Modified source code and application setup data will affect the purity of environments unless segregated.
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only Project Environment Architecture 11 of 13
TA.030 Preliminary Conceptual Architecture Component Con- current Processing Server (MB) Admin Server (MB) TRAIN Forms Server (MB) MAP Forms Server (MB) DEV Forms Server (MB)
Doc Ref: XXX 0, 0000 TRAIN Database Server (MB) MAP Database Server (MB) DEV Database Server (MB)
DNS Name Operating System Swap Space User Directories Documentation Repository Oracle Executables Application Executables SYSTEM Tablespaces Rollback Segments Archiving files Temp Space Total Applications Data Total Applications Indexes Oracle Documentation Files Space for Export files Log files Output files TOTAL DISK SPACE
0 0 0 0 0 0 n/a n/a n/a 0 n/a n/a 0
0 0 0 0 0 0 n/a n/a n/a 0 n/a n/a 0
0 0 0 0 0 0 n/a n/a n/a 0 n/a n/a 0
0 0 0 0 0 0 n/a n/a n/a 0 n/a n/a 0
0 0 0 0 0 0 n/a n/a n/a 0 n/a n/a 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0
n/a 0 0 0
0 0 0 0
n/a 0 0 0
n/a 0 0 0
n/a 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
Client Environments
File Ref: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
Project Environment Architecture
12 of 13
TA.030 Preliminary Conceptual Architecture
Doc Ref: XXX 0, 0000
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: 41b2a5c3-4d9b-4dee-9a11-c8db4d085d39.doc (v. DRAFT 1A ) Company Confidential - For internal use only
13 of 13