Project Spring - 220 (System Specifications) V 3.0 - 2013!09!26

Project: Project Spring
Document scope: System Specifications Document Page 1 of 51

File: 350528332
220-00 System Specifications
10270 PROJECT SPRING
<Systems specification for Hyperion Planning>
10270 Project Spring_-220-00System Specs-V2.0
Version: 3.0
Date: 2013-09-26
Status: Draft
10270 PROJECT SPRING 1

1. DOCUMENT CONTROL 3
1.1 VERSION HISTORY 3
1.2 REVIEW HISTORY 3
1.3 FINANCIAL CONTROL REVIEW HISTORY 4
1.4 REFERENCED DOCUMENTS 4
2. INTRODUCTION 4
2.1 CONTEXT 4
2.2 SUMMARY OF SOLUTION 5
2.3 SCOPE 5
2.3.1 Entity Scope 5
2.3.2 Functional Scope 6
2.3.3 Technical Scope 6
2.3.4 Integration Scope 7
2.4 ASSUMPTIONS 7
2.5 INTENDED AUDIENCE 8
2.6 ACRONYMS AND TERMINOLOGY 8
3. DESIGN DESCRIPTION 9
TARGET ARCHITECTURE OVERVIEW 9
DESIGN OVERVIEW 10
3.1 AS-IS 12
3.2 TO-BE 12
3.2.1 Solution Description 12
DIMENSION SUMMARY 15
DIMENSION DESCRIPTION 15
4. DATA SPECIFICATION 34
This document and its contents are the property of TATA communications or its affiliates. This document contains confidential proprietary information.
The reproduction, distribution, utilization or the communication of this document or any part thereof, without express authorization is strictly prohibited
Offenders will be held liable for the payment of damages.
2006, TATA communications or its affiliates. All rights reserved.
Project: Project Spring Page 2 of 51
Document scope: Systems Specifications Document
File: 350528332
4.1 DATA DESCRIPTION 34

4.2 DATA MODEL AND STRUCTURE 34
4.3 DATA CONVERSION 34
4.3.1 Condition of existing system data 34
4.3.2 Conversion strategy 34
4.3.3 Conversion rules description 34
5. FAILURE MANAGEMENT 35
5.1 FAILURE ANALYSIS 35
5.2 INTEGRATION WITH TROUBLE TICKET SYSTEM 35
6. HANDLING OF NON-FUNCTIONAL REQUIREMENTS 35
6.1 PERFORMANCE 35
PERFORMANCE: 35
6.1.1 Response time 35
6.1.2 Capacity 36
6.1.3 Scalability 36
6.2 RELIABILITY 37
6.3 SECURITY 37
6.4 MANAGEABILITY 40
6.4.1 Installation and Deployment 40
6.4.2 Upgrade 49
6.4.3 Configuration 49
6.4.4 Retention, Archive and Backup Strategy 49
6.4.5 Performance Management 50
6.4.6 Troubleshooting 51
6.4.7 Other Maintenance Activities 51
7. DEVELOPMENT TOOLS AND TECHNOLOGIES 51
8. TEST ASPECTS 51
9. OPEN ISSUES 52
10. DESIGN BOOKS 52
11. TEMPLATE CHANGE HIGHLIGHTS 52
1. Document Control
1.1 Version History
Version Date Description of Changes Made by

1.0 2013-08-28 1st draft created Abhishek Singhania
2.0 2013-09-20 Outlook, Capex and BS CF Details included Abhishek Singhania
File: 350528332
1.2 Review History
Version Date Reviewer Signature

1.0 2013-08-28 Mohammad Imran Project Manager
2.0 2013-09-20 Mohammad Imran Project Manager
1.3 Financial Control Review History
Version Date Reviewer Signature
1.4 Referenced Documents
2. Introduction
2.1 Context
Tata Communications Ltd (TCL) intends to implement improved AOP process across its
finance and other business operations with the following objectives:
Robust monthly reporting processes for the Group

Improved Annual Operating Planning process for Tata Communications Limited
Provide improved reports and dashboard to the management.
Reduce overall cycle time and improved planning and reporting process
accuracy.
TCL has approximately 50 entities, as a part of the Group. These entities are organized
in three levels of consolidation and are reported under IGAAP, US GAAP, IFRS. TCL is
looking for a focused approach on managing all aspects of the close process as well as
automating the last mile of Finance.
File: 350528332
TCL has five major Line of Business, namely GVS, GMS, GVG, Mobile and GNS. These
five LOBs consists of 30 product and customer segments namely Enterprise, SMB and
Service Provider. TCL is looking for a robust planning application which will not only
help them to monitor variance between actual and planned numbers, but will also help
them to monitor growth of individual businesses.
The proposed solution will also be used for monthly Management reporting of the
Group performance in form of a Board Pack
2.2 Summary of Solution

TCL envisages Hyperion planning to support its strategic 1 year plan, detailed
operational planning and detailed capital expenditure planning. Along with meeting its
planning needs, TCL also envisages the solution to serve as the single repository of
information from its transactional systems and have provision of slicing and dicing both
plan and actual data.
Hyperion Planning gives Web users the ability to enter, analyze, and report on data,
manage the planning process, and design data entry forms. Hyperion Planning on the
Web enables companies to easily roll out applications to large, distributed planning
organizations without having to install software on client computers. From the Web,
many users can simultaneously access an application anytime, anywhere, thus capable
enough to cater the planning process requirements of all the projects of TCL across all
the geographies.
2.3 Scope
2.3.1 Entity Scope
No. Entity Name Functional Local
Country Of Incorporation
1 Tata Communications Limited (TCL) India INR INR
2 TCIPL Multiple Multiple Multiple
3 TCPSL India INR INR
4 Tata Communications Transformation Services Limited India INR INR
5 S&A Internet Services Pvt. Ltd. India INR INR
6 Tata Communications Lanka Limited Sri Lanka LKR LKR
7 UTL Nepal NPR NPR
File: 350528332
8 Neotel South Africa ZAR ZAR
2.3.2 Functional Scope
2.3.2.1 Planning Budgeting and Reporting
oCost Allocation/distribution among various products/LOBs/etc.

oHR Planning,
oCash Flow Planning.
oRolling forecast
oBudget cycle seeding
oBusiness Case Preparation on Revenue increase and Cost Saving, tracking after
implementation.
o Product Costing and pricing
o Product wise profitability
o P&L Analysis by product, location, geography, segment
o Balance Sheet Analysis
o Product wise and Customer wise run rate analysis.
o Sales Commission Monthly Reports.
o Sales & Revenue Planning: Sales Planning for different Sales Organizations and
Customers
o Planning Levels in different stages
o Top-down and bottom up planning
o Multi-Currency Reporting
o Reduce budget, plan and forecast cycle time
o Spend more time on analysis and less time on transactional work
o Gain confidence in financial results and reports
o Drag & Drop Reports
o Predefined reports
o Multiple hierarchy across different dimensions e.g. Account & entity
o Drill down drill through capabilities
o Maintaining minimum 3 years of historical data
o Inclusion of Long Term Planning related data.
o The AOP figures should flow back to SAP for budget controlling
o What if analysis
o Management dashboards
Security should be applied to specific web forms / reports to ensure that users can only see that number
for which he is responsible
2.3.3 Technical Scope
File: 350528332
If there is any change required in TCL data source systems, respective TCL team
will be responsible to provide data in PwC specified format. Any data
transformation or quality check would be out of scope for PwC team.
Non Financial Data from SAP as well as from Non-SAP systems will be uploaded
into Hyperion using ODI Utility.
ODI will be used for loading data from source systems into planning applications.
There will be separate common repository, an additional Staging Relational
Database Management System, which will be populated with different source
system data. Necessary transformation would be performed here before loading
that data into Hyperion.
Apart from financial Data, any Non financial Inputs will be manually entered by the
Business Users.
For Reporting Purpose, Financial Reporting tool will be used for canned reports,
Smartview will be used for creating Ad hoc report format.
Data should be extracted in Monthly granularity, because for Hyperion month is
the lowest granular member of period.
From source system, if there is any change required from the output table, then
PwC team will not be involved for any change there
2.3.4 Integration Scope
As a part of this scope, there are a number of external systems which needs to be
integrated with the Planning processes. Following are the systems which needs to
be integrated
SAP
GBS
INTEC
CER
HFM
Prism Manual File through FTP server
2.4 Assumptions
TCL understands that translation of all the functional requirements may not be a
technical feasibility. It must be noted that Hyperion is a tool which supports
minimal customization of product source code. Rationalization of requirements
might be necessary.
TCL will be responsible for providing access to the relevant data sources
Technical environment set up requirement will be carried out by PwC with support
from the TCL Technical team
PwC understands source system integration will be restricted to source systems
mentioned in Technical Scope of the document. PwC team will identify the target
data and the structure of data points. TCL will develop Extraction and
File: 350528332
Transformation process to provide data in desired format. PwC will only be

responsible for loading data in the application.
Validation rules will be mostly uniform across all entities with variations for
selected few entities
Responsibility of sanctity of data /data quality will lie with TCL; PwC would not deal
with unstructured data. Any change in scope after design stage will attract
separate effort and commercials.
For any kind of data operation, lowest data granularity captured would be at
month level. No Week level analysis would be provided
PwC will help resolve issues highlighted during TCLs Vulnerability Assessment
(VA), however any issues that are due to tool design or existing tool limitations will
be taken up by the tool vendor. PwC will help TCL implement steps suggested by
tool vendor.
TCL will provide necessary software (s), hardware (s) and infrastructure/network
support to implement the solution
Software (Oracle Hyperion suite) vendors will be responsible for all the relevant
product related issue(s). PwC will help TCL in resolving issues and implementing
work around solutions as recommended by Oracle. PwC will be responsible only if
the issues are identified to be a result of incorrect configuration, implementation,
and deployment.
The proposed solution will be available over TCL network and capability to access
reports over internet will be subject to further network configuration by the TCL
network team.
If solution is deployed over internet, purchase of certificate will be the
responsibility of TCL Technical team.
System and Unit testing will be PwCs responsibility.
TCL will be responsible for providing source system data extracts. PwC will
validate that data reconciles to source data extracts. TCL resources will be
responsible for data reconciliation, testing and report tie out
2.5 Intended Audience
This section describes who potential readers of this document are and also the person/team
responsible for signing off this document
1. TCL IT Project Delivery Team
2. TCL IT Support Management Team
3. GISS
2.6 Acronyms and Terminology
Terms and acronyms used in this document are defined in the following table.
Term Definition
FR Financial Reports
DBA Database Administrator
File: 350528332
Term Definition
AOP Annual Operating Plan
HFM Hyperion Financial Management
GBS Global Billing System
ODI Oracle Data Integrator
EPMA Enterprise Performance Management Architect
HP Hyperion Planning
ETL Extract, Transform and Load
TCL Tata Communications Ltd
GMMS Global Mobility and Managed Services
GNS Global Network Services
GVS Global Voice Services
GVG Growth Ventures Group
SSU Shared Services Unit
IT Information Technology
VP Vice President
3. Design Description
Target Architecture Overview

Solution architecture is built on Hyperion Planning and Hyperion Essbase v11.1.2.2
standard features.
Hyperion Planning 11.1.2.2.3

- Comprehensive web based tool to coordinate and manage critical elements of planning
cycle
Hyperion Essbase 11.1.2.2
- Multidimensional OLAP database engine to consolidate plan numbers and calculate
KPIs
Hyperion EPMA 11.1.2.2.3
- Comprehensive web based tool to model Hyperion planning dimensions
Hyperion Financial Reporting 11.1.2.2.3
- Comprehensive reporting tool to generate pdf reports
Hyperion Calculation Manager 11.1.2.2.3
- Comprehensive web based tool to create calculations and deploy on planning solution
Hyperion Smart View 11.1.2.2.3
ODI 11g
File: 350528332
Oracle Database 11g R2
Technical Architecture:
The architecture comprises of 4 layers primarily:

Database layer hosts the Oracle database which consists of the various schemas used to
support the Planning metadata and various properties applicable to the Planning
applications.
Application Layer: Application framework corresponding to the various components of the
Oracle EPM Suite is installed in this layer. Essbase stores all the Planning data.
Web Layer: Web component of the applications are installed in the Web Layer. The web
components help access the applications.
Client Layer: Users can use reports, smartview, etc to enter and review the data.
Design Overview
The entire Planning and Budgeting process can be designed to work as shown below:
File: 350528332
ACTUALS
This section describes key planning and budgeting models in relation to the specific
requirements as outlined within the scope of this project.
- AOP preparation,
- MIS
- Outlook preparation
- Balance Sheet & Cash Flow
- Capex
- Depreciation Planning
- Reports
Every Hyperion Planning application uses Essbase as a database. Essbase uses cubes
for data storage. The models identified above are segregated in Hyperion Essbase. AOP
is arrived in separate AOP essbase cubes. Depreciation Planning, MIS and Outlook are
prepared in AOP essbase cube. Capex Planning takes place in 'CPX' essbase cube and
Balance Sheet & Cash Flow are prepared in the 'FS' cube. Reporting will primarily
happen from the 'AOP' cube.
File: 350528332
3.1 AS-IS
The current Planning is carried out using Microsoft Office mainly Excel
3.2 TO-BE
3.2.1 Solution Description
1 ETL Interface:
The data upload to the Hyperion Planning and Consolidation (HFM) will be achieved by
developing ETL interfaces using Oracle Data integrator (ODI).
The details of the Interface are in attached document..
Systems Interface Method

CERS Directly to the source
GBS Directly to the source
HFM Directly to the source
Intec Directly to the source
Manual File FTP Server Based
Prism FTP Server Based
The following interfaces will be developed: (These documents will be changed as

require)
- Prism Interface for Employee Related information
TCL - Project Spring - Planning -Prism Data Source details v0.1D.zip
- GBS interface for Traffic Minutes
TCL - Project Spring - Planning -GBS Data Source details v0.1D.zip
File: 350528332
- Intec Interface for Traffic minutes
TCL - Project Spring - Planning -Inec Data Source details v0.1D.zip
- SAP interface for Revenue
Data Identification Mapping.zip
- SAP ERP Financial Oracle HFM interface
TCL Interface Tasks

Design Document.zip
2 Hyperion Planning
1 General Application Description

Hyperion Planning gives Web users the ability to enter, analyze, and report on data,
manage the planning process, and design data entry forms. Hyperion Planning on the
Web enables companies to easily roll out applications to large, distributed planning
organizations without having to install software on client computers. From the Web,
many users can simultaneously access an application anytime, anywhere.
The application is designed to cater the planning process requirements of all the
projects of TCL across all the geographies.
Hyperion Essbase is a multi-dimensional database which stores all the data entered
through planning applications.
Essbase applications can be of 2 types: ASO and BSO. Planning applications can use
only BSO type Essbase applications. Each essbase application consists of multiple
File: 350528332
cubes. ASO application is primarily used for data aggregation, consolidation and
reporting purposes.
Admin
2 Application Configuration
Application Type: EPMA (Enterprise Performance Management Architect) Hyperion
Planning application
Multicurrency: Custom Multicurrency Application
3 Plan Types
Plan1 Name AOP
Plan2 Name-CPX
Plan2 Name-FS
Base Time Period Months, Start month: Apr; End month: March
Start Year FY09-FY20, valid for next 10 years
Base Currency Application will support multiple currencies that will allow users to
plan in their functional currencies.
Reporting Currency As per business decision, reporting currency of application will
be USD and INR. The consolidated plan will be available in USD and INR.
4 Dimensions
File: 350528332
Dimension Summary
Dimensions represent the core components of the Planning application(s) and are used
to categorize every line item. Hyperion Planning provides up to six required
dimensions: Account, Entity, Scenario, Version, Time Periods and Years and up to 13
custom or user defined Dimensions. Each member of the Account and Entity dimension
can be assigned to a specific Plan Type but User defined dimensions can only be
assigned to a Plan type at the dimension level. Multiple Planning applications have
been created based on the different BUs. All the applications have the 6 pre-defined
dimensions but the custom dimensions depend on the requirement of the BU and
accordingly they appear in the various applications All the dimensions are applicable
to the ASO application.
Dimension Description
Dimension Dense/Spar Dimension
Name Brief Description & Custom Attributes se Type
Basic Dimensions
Define Various years data TCL planning is Sparse Year

working with like if its 5 years then Actuals
Years
are used for reference to plan FY10-11, FY11-
12,FY13-14, FY14-15FY17-18.
Covers Various Time Period related members Dense Period
Periods where data is kept like YearTotal, Quarters,
Half yearly and Months.
Basic dimension of Planning which defines Sparse Scenario
Scenarios the type of data in the cube like Actual or
AOP.
Basic dimension of planning helps the user to Sparse Version
Version copy and save the data separately so that a
review history is in place.
Covers all Account heads or in other words Dense Account

measures where data being kept or data
Accounts which is used to calculate various measures.
It mainly covers all the hierarchy of Profit &
Loss Account and Balance sheet preparation
Function-CC-LOB It covers the various cost centers and profit Sparse Entity
centers with respect to the TCL. PwC
recommend that not more that 3000
representative CC be loaded in Hyperion
Planning altogether,
Strategic Business Units: GVS, GNS, GMMS
alongside which TCL organizes its business
The various products and services under the
different product segment will roll up to each
File: 350528332

product LOB
HSP_Rates Stores Rates. System Internal Dense Rate

Custom
Dimensions
Covers the geographies where TCL does Sparse Generic
Regions
business
Covers the nature of costs incurred or Sparse Generic
Mode
revenue earned.
Provides additional details of revenue and Sparse Generic
Subledger cost which cannot be provided by Product-GL
combination
Currency Covers the various plan currencies Sparse Generic
It covers the various cost centers and profit Sparse Entity
centers with respect to the TCL. PwC
recommend that not more that 3000
representative CC be loaded in Hyperion
Planning altogether,
Function-CC-LOB
Strategic Business Units: GVS, GNS, GMMS
alongside which TCL organizes its business
The various products and services under the
different product segment will roll up to each
product LOB
Entity Covers the hierarchy of TCL group Sparse Generic
Misc Grades of TCL employees Sparse Generic
Implementer Implementing BU for capex project Sparse Generic
Board Category Board Category of Capex Project Sparse Generic
Capex_projects WBS Code of Capex Project Sparse Generic
Currency Covers the various plan currencies Sparse Generic
Entity Covers the hierarchy of TCL group Sparse Generic
Board Sponsor Board Sponsor for Capex Project Sparse Generic
CERNO Attribute for CAPEX Projects Sparse Attribute

Project Manager Attribute for CAPEX Projects Sparse Attribute
Approving Attribute for CAPEX Projects Sparse Attribute
authority
Covers the allocation drivers for products and Sparse Generic
Misc
segments
File: 350528332

Covers the carry-forward or fresh type for the Sparse Generic
Mode
project
MIS_Line_Item MIS Grouping of Cost Centres Sparse Attribute
All_VP1 Covers VP1 details for the cost centres Sparse Attribute
5 Dimensional Structure
Project Spring -
Dimension Details.xlsx
6 Reports Dictionary
Following reports are identified as required reports from system
Project Spring -
Report Details.xlsx
7 Forms Inventory
Following forms will be created in system
Project Spring - Form

Details.xlsx
8 Variables Inventory
Project Spring -
Variables List.xlsx
File: 350528332
9 Business Processes
The entire Planning application has been split BU wise into 8 different BSO applications
and 1 ASO application.
1) GMMS & GVG For users of GMS, Mobile and GVG group
2) GNS & SME For users of GNS and SMB group
3) SSU For users of SSU
4) Network Operations For Users of Network team
5) Capex & Depreciation For users of Capex and Depreciation
6) MIS entries for Subsidiaries For Consol team
7) GDMS For users of Sales team
8) GVS For users of GVS team
1. AOP
Annual Operational Plan made for TCL Group can be split into the Revenue & Direct
Cost and Common Cost shared by the various business units. Revenue and Direct Cost
details are entered through forms developed in the Planning applications. Common
Cost is entered through templates and the data is directly submitted to the AOP cubes.
Data has to be entered in the respective Planning applications as applicable to the BU.
Once the data entry into BSO cubes is complete, calculation scripts are run which in
turn perform the required calculations. Calculation scripts will be available in the
various Planning applications as applicable to the BU the application represents. Once
the calculations are done, the data needs to be pushed from BSO to ASO cube. All the
reports have been prepared on the ASO application from the data can be verified.
AOP Dimensions/ Attribute dimensions:
a) Mode
b) Account
c) Currency
d) Misc
e) Products
f) Region
g) Segment
h) Subledger
i) Versions
j) Alias
k) LOB and Function
l) Entity
File: 350528332
m) Years
n) Periods
o) Scenario
p) MIS_Line_Items
q) VP1
r) VP2
s) VP3
AOP Reports: BU wise reports have been made (as required) and the final consolidated
reports are used for the final verification by the MIS team.
AOP Variables:
Applic Variabl Dimen

ation e Name sion
CORPtdv
all apps er Version
CORPtdv
all apps erPr Version
all apps CORPver Version
CORPver
all apps Pr Version
all apps CY Year
all apps Curmth Period
CurmthY
all apps TD Period
Scenari
all apps Curscn o
GDMStd
all apps ver Version
GDMStd
all apps verPr Version
GDMSve
all apps r Version
GDMSve
all apps rPr Version
GMMStd
all apps ver Version
GMMStd
all apps verPr Version
GMMSve
all apps r Version
all apps GMMSve Version
File: 350528332
Applic Variabl Dimen

ation e Name sion
rPr
GNStdve
all apps r Version
GNStdve
all apps rPr Version
all apps GNSver Version
GNSverP
all apps r Version
GVGtdve
all apps r Version
all apps GVGver Version
all apps GVStdver Version
GVStdver
all apps Pr Version
all apps GVSver Version
GVSverP
all apps r Version
all apps NEtdver Version
NEtdver
all apps Pr Version
all apps NEver Version
all apps NEverPr Version
all apps NY Year
Nopstdve
all apps r Version
all apps Nopsver Version
all apps PY Year
SMBtdve
all apps r Version
all apps SMBver Version
all apps SSUtdver Version
SSUtdver
all apps Pr Version
all apps SSUver Version
SSUverP
all apps r Version
all apps Subver Version
File: 350528332
2. Outlook
Rolling forecasts are prepared each month beginning June of each financial year.
Revenue is entered through forms developed in the Planning applications and Cost is
entered through templates at a GL-CC level and the data is directly submitted to the
AOP Cubes for all BU's except GVS. (All the data for GVS is entered through forms in
Planning applications.) Once the data entry into BSO cubes is complete, calculation
scripts are run which in turn perform the required calculations. Calculation scripts will
be available in the various Planning applications as applicable to the BU the application
represents. Once the calculations are done, the data needs to be pushed from BSO to
ASO cube. Aggregation of data happens in ASO cubes. All the reports have been
prepared on the ASO application from where the data can be verified.
Outlook Dimensions:
a) Mode
b) Account
c) Currency
d) Misc
e) Products
f) Region
g) Segment
h) Subledger
i) Versions
j) Alias
k) LOB and Function
l) Entity
m) Years
n) Periods
o) Scenario
p) MIS_Line_Items
q) VP1
r) VP2
s) VP3
Outlook reports: Reports will be generated for comparison of Actuals data with the AOP
and Outlook data.
Outlook Variables:
Variable Dimension
&RFYr1 Year
File: 350528332
Variable Dimension
&RFYr2 Year
&RFYr3 Year
&RFYr4 Year
&RFYr5 Year
&RFYr6 Year
&RFYr7 Year
&RFYr8 Year
&RFYr9 Year
&RFYr10 Year
&RFYr11 Year
&RFYr12 Year
&RFper1 Period
&RFper2 Period
&RFper3 Period
&RFper4 Period
&RFper5 Period
&RFper6 Period
&RFper7 Period
&RFper8 Period
&RFper9 Period
&RFper10 Period
&RFper11 Period
&RFper12 Period
&OutlookSSU Version
&OutlookNetops Version
&OutlookGMMS Version
&OutlookGNS Version
&OutlookGVG Version
&OutlookGVS Version
&OutlookSMB Version
&OutlookGDMS Version
&OutlookCORPver Version
&CORPfinAOPver Version
CORPfinAOPver Version
File: 350528332
Variable Dimension
GDMSfinAOPtdver Version
GMMSfinAOPtdver Version
GNSfinAOPtdver Version
GVGfinAOPtdver Version
GVSfinAOPtdver Version
NetopsfinAOPtdver Version
SMBfinAOPtdver Version
SSUfinAOPtdver Version
&CurOutlook Scenario
&CurOutlook2 Scenario
&CurOutlook3 Scenario
&OutlookElims Scenario
&OutlookElims2 Scenario
&OutlookElims3 Scenario
&CurOutlookFinal Scenario
&CurOutlookFinal2 Scenario
&CurOutlookFinal3 Scenario
3. Balance Sheet & Cash Flow
Balance Sheet and Cash Flow AOP process falls in sync with the period of P&L AOP
process. At the start of the process the schedule wise data is being entered for
beginning balance and for the other months. Post this the data for eliminations is also
being put and the final value is being derived. For cash flow also the data is pushed at
base and eliminations scenario to derive the final value. For the completion of BS and
CF AOP the closure of P&L AOP is must since the values from PL flows to Balance Sheet
and Cash Flow
Dimensions (DEVAOPCO.FS):
Dimension Dimension Type

Account Dense/Accounts
Periods Dense/Time
Currency Sparse
Years Sparse
File: 350528332
HSP_Rates Sparse
Mode Sparse
Entity Sparse
Versions Sparse
Region Sparse
Scenario Sparse
Products Sparse
Subledger Sparse
Misc Sparse
Segment Sparse
LOB and Function Sparse
Country
MIS_Line_Items Sparse/Attribute
Business Rules:
Business
Rules Description
BS_S2_R1 Standard Pl items flow to BS for all Entities except Neotel
Calc
BS_S10_R Standard Pl items flow to BS for all Entities except Neotel
1
1
1
1
1
CF_R1 Standard Pl items flow to CF for all Entities except Neotel
Scripts:
File: 350528332
Calc
Scripts Description
CpBeg To Copy Begbalance data for Non-Currency members
BS_Sum Aggregation and DBD calculation for Summary
BS_S1 Aggregation
BS_S2 Aggregation and Standard Pl items flow to BS for Neotel
BS_S3 Aggregation
BS_S4 Aggregation
BS_S5 Aggregation
BS_S6 Aggregation
BS_S9 Aggregation
BS_S11 Aggregation
BS_S14 Aggregation
BS_S15 Aggregation
BS_S17 Aggregation
BS_S18 Aggregation
BS_DTG Aggregation
BS Aggregation
CF Aggregation and Standard Pl items flow to CF for Neotel
SEBI5 Standard Pl Revenue Calculation
Substitution Variables
Variable Dimension
&BSver Version
&BStdver Version
Map Reporting Application:
Application Mapping Name Dimension
File: 350528332
DEVAOPCO Std PL Push plug and revenue data to

AOPCON
DEVAOPCO Push BS & CF data to AOPCON
Transparent Partition: Transparent partition was created from AOPCON. AOP to

DEVAOPCO.FS. to get Standard Pl data in DEVAOPCO.FS.
Source Database: AOPCON.AOP
Source Area: '@IDESCENDANTS("600000"),@IDESCENDANTS("400000"),"Gross Rev

All",@Remove(@IDESCENDANTS("SB_00000000"),@List(SB_12111110_plug,"SB_12111
111","SB_12111112","SB_12111113","SB_12111210-001_plug","SB_12111210-
002_plug","SB_12111210-003_plug","SB_12111210-004_plug","SB_12111210-
002_plug","SB_12111240-
003_plug","SB_12111270_plug","SB_12111280_plug","SB_12111261-
001_plug","SB_12111261-002_plug","SB_12111262_plug","SB_12111120-
001_plug","SB_12111120-002_plug","SB_12111120-
003_plug","SB_12112000_plug","SB_12210000_plug","SB_12220000_plug","SB_21000
000_plug","SB_14000000_plug")),"BegBalance",@IDESCENDANTS("YearTotal"),@IDESC
ENDANTS("Years"),@IDESCENDANTS("All_Md_Base"),@IDESCENDANTS("Entity"),@IDES
CENDANTS("All region"),@IDESCENDANTS("AOP Scenario1"),@IDESCENDANTS("AOP
Scenario2"),@IDESCENDANTS("AOP Scenario3"),@IDESCENDANTS("All_Prd"),"Common
Sub","Misc_All",@IDESCENDANTS("All Seg"),@IDESCENDANTS("Sub
Ver1"),@IDESCENDANTS("Sub Ver2"),@IDESCENDANTS("Sub
Vers3"),@IDESCENDANTS("Sub
Ver4"),@IDESCENDANTS("SubVer5"),@IDESCENDANTS("Sub
Ver6"),"Local","USD","INR",@IDESCENDANTS("Function")'
Target Databse: DEVAOPCO.FS

Target Area: '@IDESCENDANTS("600000"),@IDESCENDANTS("400000"),"Gross Rev
All",@Remove(@IDESCENDANTS("SB_00000000"),@List(SB_12111110_plug,"SB_12111
111","SB_12111112","SB_12111113","SB_12111210-001_plug","SB_12111210-
File: 350528332
002_plug","SB_12111240-
003_plug","SB_12111270_plug","SB_12111280_plug","SB_12111261-
001_plug","SB_12111261-002_plug","SB_12111262_plug","SB_12111120-
001_plug","SB_12111120-002_plug","SB_12111120-
000_plug","SB_14000000_plug")),"BegBalance",@IDESCENDANTS("YearTotal"),@IDESC
ENDANTS("Years"),@IDESCENDANTS("All_Md_Base"),@IDESCENDANTS("Entity"),@IDES
CENDANTS("All region"),@IDESCENDANTS("AOP Scenario1"),@IDESCENDANTS("AOP
Scenario2"),@IDESCENDANTS("AOP Scenario3"),@IDESCENDANTS("All_Prd"),"Common
Sub","Misc_All",@IDESCENDANTS("All Seg"),@IDESCENDANTS("Sub
Ver1"),@IDESCENDANTS("Sub Ver2"),@IDESCENDANTS("Sub
Vers3"),@IDESCENDANTS("Sub Ver4"),@IDESCENDANTS("Sub
Ver5"),@IDESCENDANTS("Sub
Ver6"),"Local","USD","INR",@IDESCENDANTS("Function"),"HSP_InputValue"'
Mapped Area:
Mapped globally ("Version") to ("Versions")

Mapped globally ("Reporting Currency") to ("Currency")
Mapped globally ("LOB-Functions") to ("LOB and Function")

Mapped globally ("") to ("HSP_InputValue");
PartitionDefinition.tx
t
Balance Sheet and Cash Flow related Application: The application used in development
environment for entering data of Balance Sheet and Cash Flow is DEVAOPCO and the
corresponding cube is FS
Balance Sheet and Cash Flow reports: Reports will be generated for comparison of
Actuals data with the AOP and Outlook data.
4. Capex
Fresh Capex AOP data is entered annually by the users through smartview templates.
The data is entered against dummy WBS Level 1 codes. The same can be verified by
the users via ad-hoc analysis.
File: 350528332
Fresh Capex actuals and Carry-forward Capex actuals data is brought from SAP every
month into the Essbase database via ODI. The data is brought at WBS Level 5 code and
the same can be verified by the users in the forms. Interest rate adjustments and Forex
rate adjustments can be done via forms.
Budgetary transfers and AOP transfers can be made through forms as and when
required. It is also at WBS Level 1 codes.
Once a project code is created in SAP, the Fresh Capex AOP data is transferred from
dummy WBS Level 1 codes to the actual WBS Level 1 code.
Capex Dimensions:
a. Implementer
b. Mode
c. Account
d. Currency
e. Misc
f. Products
g. Region
h. Segment
i. Subledger
j. Versions
k. Alias
l. LOB and Function

m. Board Category
n. Board Sponsor
o. CAPEX Projects
p. Entity
q. Years
r. Periods
s. Scenario
t. CERNO
u. Project Manager
v. Approving Authority
w. Capex Group
x. SUBS_DETAIL
File: 350528332
y. SUBSC_TYPE
5. Reports
The embedded excel shows the master list of all the reports for all the modules
developed along with the status, owner and BU details
Reporting_Tracker_1
9thSep.xlsx
6. MIS Consol
The proposed system automation will involve the following activities:
Data will be pulled from various systems like
o SAP data in KSB1 Dump for extracting GL/CC wise details for TCL and TCIPL
entities
o Manual files for
Access Cost for TCIPL
License Fees
Bad Debts
Interconnect cost
Adjustment Files for Standalone Entity Level
Consol Level Adjustment file
MIS Line items level details for TCTSL, TCPSL and TCL Lanka entities
MIS Revenue Details
o HFM Extracted Data from Oracle table for
Top Side Entries
Gap Adjustment and Elimination entries for Cost
Trial Balance Entries
Consol Level Entries
P&L details for Neotel and UTL entities
Data will be primarily captured in GL-CC level for each month and entity
File: 350528332
Data will be driven by various master tables and these masters need to be re-visited
and modified as require for each financial year.
At each month end the data will be processed using ODI and pushed to Hyperion
planning for MIS Consol Reporting
Data is primarily captured in two currencies INR/USD
The automation process has two control checks before running entire cycle and
generation of MIS Consol Report for a month
Actuals data from the various source systems is extracted and the same is sent to ASO
cubes. Reports are generated at an MIS level and the same is then verified. The data
goes through ODI where the mappings between the source and target ensure that data
is pushed across the right cross-section.
7. Depreciation
-Under Construct
Version Control
1. Application administrator opens BU wise versions as well as corporate versions.
2. BU managers prepare their budgets in BU versions.
3. Once satisfied with the Budget draft, BU manager graduates the budget to corporate by
following 4 step process:
a. Asking the application administrator to lock the active BU version.
b. Copy the data of active BU version to active corporate submission version.
c. Only if BU wants to update the submitted plan for another submission to corporate,
BU manager can ask application administrator to copy data of locked BU version to
active BU version and update the active LOB version. Once restated plan is ready
BU manager requests central MIS team to reject the submitted plan and ask the
administrator the repeat step b.
However ideal this complicated workflow will entail following overheads:
1. Accuracy and submission of plan in active corporate submission version becomes

core responsibility of BU manager. This entails that BU managers are very well
versed with application design and workings.
2. For all BUs GVS, GMMS, GNS, SSU, Net/ops and others, 2 scripts each Data clear
and Data copy each will need to be written. This will entail addition IT overhead of
maintenance.
File: 350528332
3. It is of paramount importance that once a BU version is finalized, it be locked before

its data is copied to active corporate submission version. This is required to preserve
the sanctity of submitted BU version and preserve snapshot of submitted data. BU
managers need to follow this guideline.
Note: Hyperion Planning records any update to data cells in HSP_AUDIT_RECORD

table in following format. This functionality is not available to end users but can be
used by Planning database administrator to track changes made to planning data
by running SQL statements on this table:
10 Data Flow Diagram
File: 350528332
Essbase
(BSO)
The data from the various source systems is processed via ODI. The Oracle
database acts as the staging area of the data being processed. ODI contains the
various mappings between the source and the destination. Data from the source
systems is mostly the Actuals data which is then again pulled via ODI from the Oracle
database and sent to ASO application. Reports are constructed to pull the data from
the ASO application which is then available to the end users. All the Planning data is
pushed to ASO application for variance analysis between the actuals, AOP and Outlook
data. Capex data is not pushed to ASO applications but directly produced in reports
from the BSO application. The planning data is therefore stored only in the Essbase
databases. The schemas in the Oracle database corresponding to the planning
applications contain the application Metadata.
The various source systems are:

a) SAP
b) GBS
c) CER
d) Intec
e) Manual File in FTP for Prism
f) HFM
File: 350528332
11 Data conversion
For Actual Reporting and Variance analysis of plan over Actuals MIS reports, separate
Essbase data marts other than planning cubes are envisaged. General approach is to
store the actual data in the same Essbase cube as the plan and budget cube. However
basis TCL financial reporting requirement to have ability to report costs form 15000
active cost centers, following this approach will lead to gigabytes of actual data in
planning cubes.
Hyperion Planning cubes are not optimized to store such high volumes of data.
To resolve this tradeoff another variant of Essbase technology Essbase Aggregate

Storage Object (ASO) technology is envisaged to be ideal solution for storing actual
data. As Essbase ASO can store far more data than Essbase planning cubes (which are
BSO not ASO). Essbase BSO cubes be utilized for plan preparation and Essbase ASO for
Actual data storage.
Comparison of BSO and ASO cube types:
To satisfy Variance reporting requirement Plan data be loaded in Actual Cube in a batch
process.
Envisaged benefits of usage of different technology stack:
Improved performance of actual data consolidation in ASO

Improved reporting performance and experience
More frequent refresh of GL data in ASO, with minimum impact on planning process
Limited downtime of planning cubes during monthly master data and metadata
management process
Higher scalability: Ability to deal with larger amount of data. Better query performance.
Data Transfer Activity:
File: 350528332
SOP for AOP and forecasts restatements: Plan will be finalized in planning cubes and
then transferred to ASO cube for variance reporting, and any changes in AOP / forecasts
in Planning cubes will reflect in ASO cube after planning data transfer from planning
cube to Actual cube by a batch process.
Variance Reports: Variance reports will be available from ASO cube after data has been
transferred from planning cube and loaded in ASO cube. However business users can
run ad-hoc analysis reports on both planning and Essbase cubes in this window to find
out variance. Reports will be prepared using Hyperion Financial Reporting and
Smartview.
To reduce IT administrative overhead and make metadata management look

uniform across all Hyperion Essbase data cubes, EPMA Shared library will be
implemented for centralized master data management system - for all Hyperion
Essbase cubes. Thus any changes in any dimension, say Cost Centers will need to be
made only in Hyperion centralized hierarchy in EPMA from where it will flow to all
Hyperion Essbase cubes following re-deployment.
To satisfy Variance reporting requirement Actuals data will be loaded in ASO Cube in a
batch process.
12 Currency conversion considerations- Classical Multicurrency v/s custom multi

currency application:
Hyperion supports multiple currencies for planning and reporting by it's out of the box
classical currency conversion functionality. This approach is more scalable, allows
quicker induction of new currency for entities in application. However in specialized
circumstances custom multicurrency application can also be built in case if the
currency requirements are not sufficed by classical multicurrency applications.
13 Currency rate variations modeling:

Basis discussion with central MIS team, given the exchange rate volatility, TCL will need
to review its final AOP in USD and INR not only on basis of AOP exchange rates but also
on the basis of 4 other exchange rates. Thus for all 20 business currencies in total 5
exchange rate tables are needed. As in Hyperion, only one exchange rate table can be
utilized for one scenario, 5 exchange rate tables call for 5 alternate scenarios (AOP 1
through 5) for one data point in functional currency to be converted in USD and INR a/c
to 5 different currency rates. Implementing 5 currency rate conversions in application
will result in
Quick growth of data in Essbase cubes- As each data in base currency will be
converted to USD and INR according to 5 rates and stored in database, database size
will grow quickly. To illustrate same, if 1 AOP data size is 250 MB, the resultant size of
dataset will shoot upto 250MBX5=1.25 GB.
Increase in calculation time: As calculations are driven by scenarios in Hyperion, for
finalizing PnL in five different scenarios, all calculations will need to run in all the 5
File: 350528332
scenarios. This means that if for an LOB calculation time were 30 minutes, this will
increase to 30X5=150 minutes. Thus this will entail additional time overhead before
reports are available in all the 5 currency exchange scenarios for a quick comparison.
However 3 Scenarios have been created for each planning cycle and further scenarios
will have to be created on a need basis
2 Data Specification
1 Data description
Please refer to sec 3.2.1.2.10
2 Data model and structure
Data logical model is controlled internally by the Hyperion Application
3 Data conversion
NA
3.2.2 Condition of existing system data
NA
3.2.3 Conversion strategy
NA
3.2.4 Conversion rules description
NA
1 Common specifications
NA
File: 350528332
2 Flat files specifications
NA
3 Failure Management
1 Failure Analysis
Some common error scenarios and possible solutions are listed as below:
Reports cannot be viewed. The error thrown: RunHDLG is not configured. Communication Error.
Resolution: Logout from the browser. Close all internet explorer windows. Clear the internet cache.
Any of the application home pages (Shared Services, Planning etc) cannot be viewed. Resolution:
Stop all the services and restart them according to the instructions provided. If required, restart the
server after stopping all the services.
All the services, managed servers and deployments are working fine, but the users cannot login.
Resolution: Check if the database is up and running.
Users are not being able to submit data in forms. Reports cannot be viewed. Resolution: Check if
Essbase is running
Users cannot connect to the Report Development Studio. Check if the service freporting is running in the
web-app server.
Essbase cannot be started after a reboot. Error: essbase.sec is corrupted. Resolution: Rename the file
essbase.sec. Copy the file essbase.bak to a file named essbase.sec. Start Essbase
2 Integration with Trouble Ticket System
NA. Users will have to raise SDP ticket manually as and when they face issues.
4 Handling of Non-Functional Requirements
1 Performance
Performance:
Hyperion Planning is a high query performance system. Performance for Hyperion
is data driven.
File: 350528332
The Data synchronization timings will depend linearly upon data volume
synchronized.
3.2.5 Response time

Calculations timing will not exceed 40 mins (upper boundary) by LOB. Lower limit
can be close to few seconds.
The query timings will be limited to 2 mins (upper boundary). Lower limit can be
close to instantaneous case to case.
The system maintenance time will depend upon data in Essbase database at any
given point in time and thus is subject to growth. It is recommend keeping this in
check that every 3 years a database archival should be performed.
3.2.6 Capacity
Essbase BSO (planning) cubes should not store more than 4 GB of data for
optimum performance.
Essbase ASO (Actual) should not store more than 20 GB of data for optimum
performance.
3.2.7 Scalability
Highly Scalable:
Given modular design (AOP and CAP cubes), Actual vs planning cubes; application is
out of the box scalable in terms of (no script changes needed):
1. CC addition: Addition of leaf Cost centers.
2. Region addition: Addition of markets/ regions
3. Year addition: Addition of FY
4. Currency addition: Incase executive decision is to go with classic multicurrency

application (refer to design consideration section) else not.
5. Employees/Grade: Addition of Employees
6. WBS codes: Addition of WBS codes
7. Implementer: implementer dept
8. Board Category: Board category
9. Board Sponsor: Board Sponsor
Mid scalable:
Addition or changes in these dimensions need mid to large enhancements
File: 350528332
1. Addition of products: Incase product budget is driven by drivers, same need to

encode in the system. This will necessitate creation of Driver accounts in the
system as well as creation of calculation scripts for these products.
2. Legal entity: Addition of Legal entity will entail medium to large scale change
subject to detail of budgeting and additional operational complexity.
Low scalable:
Addition or changes in these dimensions need large enhancements
1. LOB: Addition of a new LOB will need large scale enhancement. Will necessitate
feasibility analysis, requirement to tool mapping, delta design and construct.
2. Dimension: Addition an any new dimension is necessarily a major change and will
necessitate build, test and deploy of every single artifact (data entry screens,
calculation rules, reports etc) from scratch.
2 Reliability
Hyperion Planning is not a high availability critical application. Planned outage takes place after
approval from users.
Unplanned outage can happen primarily because of the following issues:
Network issue
One of the services of the application crashes
Archive logs space of the database server gets completely filled
One of the processes corresponding to the Hyperion services takes up too much RAM
making the server unstable.
3 Security
Security will be implemented at a group level. The grouping has been identified on the basis of the
existing BUs. Security will be implemented via MSAD. All the privileges are provided at 2 levels:
Application level security via Shared Services.
Artifact level security which has to given for each artifact.
BU Parent Group Groups Users Application

GMMS PLANTCL PLANGMMS Narayan Baheti DEVGMMS
GMMS PLANTCL PLANGMMS Pradeep Dubey DEVGMMS
GMMS PLANTCL PLANGMMS Ankur Bhandari DEVGMMS
GMMS PLANTCL PLANGMMS Mateen Pathan DEVGMMS
GMMS PLANTCL PLANGMMS Deepali Walia DEVGMMS
GNS PLANTCL PLANGNS Saurav Goyal DEVGNS
File: 350528332
BU Parent Group Groups Users Application

GNS PLANTCL PLANGNS Kaushik Ghosh DEVGNS
GNS PLANTCL PLANGNS Mandar Joshi DEVGNS
GNS PLANTCL PLANGNS Prateek Saria DEVGNS
GNS PLANTCL PLANGNS Prakash Bogi DEVGNS
GNS PLANTCL PLANGNS Santosh Karalkar DEVGNS
GVS PLANTCL PLANGVS Bhatu Nahar DEVGVS
GVS PLANTCL PLANGVS Padam Misra DEVGVS
GVS PLANTCL PLANGVS Amol Jadhav DEVGVS
GVS PLANTCL PLANGVS Jitendra Jain DEVGVS
GVG PLANTCL PLANGMMS Padam Misra DEVGMMS
Sameer
GVG PLANTCL PLANGMMS Bandodkar DEVGMMS
GVG PLANTCL PLANGMMS Aditya Verma DEVGMMS
GDMS PLANTCL PLANGDMS Vidya Srinivasan DEVGDMS
GDMS PLANTCL PLANGDMS Vijaya Pawshe DEVGDMS
GDMS PLANTCL PLANGDMS Yogesh Naik DEVGDMS
SSU PLANTCL PLANSSU Rashi Bedia DEVSSU
SSU PLANTCL PLANSSU Amit P Sharma DEVSSU
SSU PLANTCL PLANSSU Shilpa Chavan DEVSSU
SSU PLANTCL PLANSSU Manas Chatterjee DEVSSU
NETOPS PLANTCL PLANNETOPS Sanjay Agarwal TCLNETOP
NETOPS PLANTCL PLANNETOPS Rishma Shetty TCLNETOP
NETOPS PLANTCL PLANNETOPS Ganesh Poojari TCLNETOP
NETOPS PLANTCL PLANNETOPS Amit Deshpande TCLNETOP
NETOPS PLANTCL PLANNETOPS Kavya Gupta TCLNETOP
NETOPS PLANTCL PLANNETOPS Sagar Karalkar TCLNETOP
NETOPS PLANTCL PLANNETOPS Kalpak Neralkar TCLNETOP
NETOPS PLANTCL PLANNETOPS Mayur Gupte TCLNETOP
CAPEX PLANTCL PLANCAPEX Abhay Lahothy DEVCPX
Amaresh
CAPEX PLANTCL PLANCAPEX Patgaonkar DEVCPX
MIS CONSOL PLANTCL PLANAOPCO Rashi Bedia DEVAOPCO
MIS CONSOL PLANTCL PLANAOPCO Umesh Gopal DEVAOPCO
MIS CONSOL PLANTCL PLANAOPCO Ashish Kanthalia DEVAOPCO
MIS CONSOL PLANTCL PLANAOPCO Prasad Telang DEVAOPCO
MIS CONSOL PLANTCL PLANAOPCO Sanjay Ruikar DEVAOPCO
SMB PLANTCL PLANGNS Prakash Bogi DEVGNS
PLANSUPPOR
IT Team PLANTCL T Survinder Sondhi Administrator
PLANSUPPOR Panchapakesan
IT Team PLANTCL T KR Administrator
PLANSUPPOR
IT Team PLANTCL T Jogendar Padhy Administrator
PLANSUPPOR
IT Team PLANTCL T Amit Singhal Administrator
PLANSUPPOR
IT Team PLANTCL T Shobha Mendon Administrator
File: 350528332
Groups Application Role

Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVGMMS
Essbase Write Access
PLANGMMS Interactive User
Planner
AOPCON Essbase Viewer
Explorer
Reporting and Analysis
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVGDMS
PLANGDMS Interactive User
Planner
Explorer
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVSSU
PLANSSU Interactive User
Planner
Explorer
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
TCLNetops
PLANNETOPS Interactive User
Planner
Explorer
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVCPX
PLANCAPEX Interactive User
Planner
Explorer
Viewer
PLANAOPCO DEVAOPCO Ad Hoc Grid Creator
Ad Hoc User
Administrator
File: 350528332
Groups Application Role

Interactive User
Planner
Explorer
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVGVS
PLANGVS Interactive User
Planner
Explorer
Viewer
Ad Hoc Grid Creator
Ad Hoc User
Administrator
DEVGNS
PLANGNS Interactive User
Planner
Explorer
Viewer
4 Manageability
3.2.8 Installation and Deployment
Installation and deployment of the application happens on a distributed environment.

Network requirements
Selected ports need to remain open on all 4 servers such that all the 4 layers ( Database
layer, Application layer, Web layer and User layer) have uninterrupted access to the
Planning applications
Ports List Service / Process Protocol

80 Microsoft Internet Information Services (IIS) Manager Console HTTP
Browsers and Smart View use these ports to access EPM System/Web
443 SSL
Tier Firewall
19000 Oracle HTTP Server/Application Tier Firewall TCP/IP
Network 1423 Essbase Agent/Application Tier Firewall(Thick Client) TCP/IP
32768-33768 Essbase Server Applications (ESSSVR) TCP/IP
8205-8209 Financial Reporting RMI Services TCP/IP
1521 Database Tier Firewall TCP/IP
28080 Foundation Services Listen Port TCP/IP
File: 350528332
Between 7001 The Web Logic Administration Server port. TCP/IP

the 9043 Websphere Application Server port TCP/IP
Servers
19091 Performance Management Architect Web Application TCP/IP
19101 Data Synchronizer Web Application TCP/IP

5251 Performance Management Architect Server TCP/IP
5255 Net JNI Bridge TCP/IP
8500 Calculation Manger TCP/IP
3388 Oracle Essbase Integration Services Server TCP/IP
6711 Oracle Process Manager and Notification Server Local Port TCP/IP
6712 Oracle Process Manager and Notification Server Server Port TCP/IP
10080 Administration Services TCP/IP
13080 Provider Services Web Application TCP/IP
5300 Essbase Studio Listen Port TCP/IP
9080 Essbase Studio HTTP Listen Port TCP/IP
45000 Reporting and Analysis Framework Web Application TCP/IP
6860 Reporting and Analysis Framework Default Service TCP/IP
Reporting and Analysis Framework Services
1.Global Services Manager (GSM)

2.Core Service
3.Service Broker
4.Job Service
6800-6805 TCP/IP
5.Event Service
6.Repository Service
Note: Each service listed in this table is assigned a port within the
range, either the default range 6800 6805 or the range specified
during configuration.
8200 Financial Reporting Web Application TCP/IP

16000 Web Analysis Listen Port TCP/IP
6373 Financial Management Web Service Web Application TCP/IP
135-plus
ephemeral high-
Financial Management Service TCP/IP
range ports
(1024 5536)
9097 Financial Management DME Listener Service TCP/IP
25 Financial Management SMTP Port for Email Alerts TCP
8300 Planning web Application TCP/IP
11333 Planning RMI Server TCP/IP
8600 Disclosure Management Web Application Listen Port TCP/IP
135-plus
ephemeral high-
FDM load balancer And FDM application server TCP/IP
range ports
(1024 65536)
137-139 File sharing TCP/UDP
445 File sharing TCP
6550 ERP Integrator Web Application TCP/IP
8297 Financial Reporting Default Service TCP/IP
File: 350528332

8299 Financial Reporting Scheduler Service TCP/IP
Hardware
4 Servers have been used for the complete installation of the Oracle EPM Suite. Each
server has the same configuration apart from the Hard disk space.
o Processor: Intel Xeon E5645 64-bit 2.40GHZ (2 processors x 6 physical cores per
CPU x 2 threads per core = 24 virtual cores)
o RAM: 32GB
o Hard disk: 100GB (System Partition); 300GB (Data Partition)
Software packages
o Hyperion Financial Data Quality Management - Application User Perpetual
o Hyperion Financial Data Quality Management Adapter for Financial Management -

o Application User Perpetual
o Hyperion Financial Data Quality Management Adapter Suite - Application User
Perpetual
o Hyperion Financial Management Plus - Application User Perpetual
o Hyperion Planning Plus - Application User Perpetual
o Hyperion Financial Data Quality Management ERP Source Adapter for SAP -
Application
o User Perpetual
o Oracle Hyperion Disclosure Management - Application User Perpetual
o Hyperion Financial Data Quality Management - Application User Perpetual
o Hyperion Financial Data Quality Management Adapter for Financial Management -
o Application User Perpetual
o Hyperion Financial Data Quality Management Adapter Suite - Application User
Perpetual
o Hyperion Financial Management Plus - Application User Perpetual
o Hyperion Planning Plus - Application User Perpetual
o Hyperion Financial Data Quality Management ERP Source Adapter for SAP -
Application
o User Perpetual
o Oracle Hyperion Disclosure Management - Application User Perpetual
Application components
Activities to be carried out before the installation of the Oracle EPM Suite installation:
# Server Issue Description
Disable UAC permanently. Set up Group Policy Update to prevent resetting of
1 121.244.234.53
UAC status
2 121.244.234.54
UAC status
3 121.244.234.55
UAC status
4 121.244.234.56
UAC status
Disable Network Level Authentication on Server for non-administrator access

5 121.244.234.53
to servers from non-Windows 7/ Windows Server computers
File: 350528332

6 121.244.234.54

7 121.244.234.55
8 121.244.234.53 Set page file size as between 32768MB - 65536MB

11 121.244.234.53 Firewall should be off in all four production servers
Install IIS7 in both servers with IIS6 compatibility. IIS needs to have ASP
compatibility which is not installed by default in Windows 2008 (with IIS 7).
15 121.244.234.53
This needs to be installed via Add Roles. Install IIS, Application server,
ASP.NET and IIS6 metabase compatibility. Without this HFM will not run
16 121.244.234.54
17 121.244.234.55
18 121.244.234.56
19 121.244.234.53 Install Microsoft .NET Framework SP2 - 2.2.307293 in Hyperion Server
Install following softwares

- 7-Zip 64-bit
23 121.244.234.53 - Adobe PDF write/Ghostscript freeware (for PDF based reporting) in
Hyperion Server
- MS Office 2007 Licensed version (word and excel)

- 7-Zip 64-bit
Hyperion Server
File: 350528332

- 7-Zip 64-bit
Hyperion Server

- 7-Zip 64-bit
Hyperion Server
Create a user "hypadmin" and provide Administrator access. This user will be
used for Hyperion Components installation and configuration only. Add this
user as "Admin" group of the servers and the Admin group should have these
27 121.244.234.53
privileges: "Act as part of the OS", "Logon as a batch job", "Logon as a service",
"Bypass Traverse Checking" and " Logon as a part of operating system", "Log
On Locally" and "Interactive Login"
28 121.244.234.54
29 121.244.234.55
30 121.244.234.56
Disable the Windows User option of "Delete Temporary folder content on log
31 121.244.234.53
off".
32 121.244.234.54
off".
33 121.244.234.55
off".
34 121.244.234.56
off".
35 121.244.234.53 Internet Explorer level of security should be low
File: 350528332

39 121.244.234.53 JDK 1.6.0u39 64-bit to be installed on server
42 121.244.234.53 Disable Antivirus for installation
Server wise components installed :

121.244.234.5
# Component Sub-Component 121.244.234.53 121.244.234.55
4
Foundation Services
1 Foundation Services
Web Components
2 Foundation Services Static Content Files
3 Foundation Services Oracle HTTP Server
Weblogic Application
4 Foundation Services
Server
Performance
5 Management EPMA Batch Client
Architect
Performance
6 Management EPMA File Generator
Architect
Performance
7 Management EPMA Web Client
Architect
Performance
EPMA Data
8 Management
Synchronizer Service
Architect
Performance
EPMA Dimension
9 Management
Library Server
Architect
Calc Manager Web
10 Calc Manager
Application
11 Essbase EAS Web Application
Provider Services Web
12 Essbase
Application
13 Essbase Essbase Server
14 Essbase Essbase studio server
Planning Web
15 Planning
Application
Framework Web
16 Reporting & Analysis
Application
Framework Services and
Common Library
Financial Reporting
Web Application
Web Analysis Web
Application
Financial
20 HFM ADM Server
Management
File: 350528332
121.244.234.5
# Component Sub-Component 121.244.234.53 121.244.234.55
4
Financial
21 HFM Web Services
Management
Financial
22 HFM Service
Management
23 FDM FDM Web Application
24 FDM FDM Workbench Client
ERP Integrator Web
25 FDM
Application
26 FDM FDM Load Balancer
27 FDM FDM Task Manager
28 FDM FDM Server
ODI Studio and Java EE
29 ODI
components
30 ODI Standalone Agent
Configuration Performed for the installed Components:

# Server Components Activity Sub Activity
1 121.244.234.53 Hyperion Foundation Configure Common Settings
Configure Oracle Configuration
2 121.244.234.53 Hyperion Foundation
Manager
3 121.244.234.53 Hyperion Foundation Configure Database
4 121.244.234.53 Hyperion Foundation Deploy to application Server
Manager
8 121.244.234.55 Essbase Essbase Configure Essbase Server
9 121.244.234.55 Essbase Essbase Studio Configure Database
10 121.244.234.53 Essbase Provider Services Deploy to Application Server
11 121.244.234.53 Essbase Essbase Administration Services Configure Database
12 121.244.234.53 Essbase Essbase Administration Services Deploy to Application Server
13 121.244.234.53 Planning Configure Database
14 121.244.234.53 Planning Deploy to Application Server
Manager
18 121.244.234.54 Financial Management Configure DCOM
19 121.244.234.54 Financial Management Configure Database
20 121.244.234.54 Financial Management Configure Application Server
21 121.244.234.54 Financial Management Configure Application Cluster
22 121.244.234.53 Financial Management Configure DCOM
23 121.244.234.53 Financial Management Configure Web Server
24 121.244.234.53 Financial Management Deploy to Application Server
File: 350528332
# Server Components Activity Sub Activity

Performance Management
Architect
Performance Management
26 121.244.234.53 Hyperion Foundation Deploy to Application Server
Architect
27 121.244.234.53 Hyperion Foundation Calculation Manager Configure Database
28 121.244.234.53 Hyperion Foundation Calculation Manager Deploy to Application Server
29 121.244.234.54 Reporting and Analysis Configure Database
30 121.244.234.54 Reporting and Analysis Configure Framework Services
31 121.244.234.53 Reporting and Analysis Configure Database
32 121.244.234.53 Reporting and Analysis Deploy to Application Server
Configure Financial Reporting

33 121.244.234.53 Reporting and Analysis
RMI Ports
34 121.244.234.54 FDM Configure FDM Web Application
35 121.244.234.54 FDM Configure FDM Server
36 121.244.234.53 FDM Configure Database
37 121.244.234.53 FDM Deploy to Application Server
Disclosure
38 121.244.234.53 Configure Database
Management
Disclosure
39 121.244.234.53 Deploy to Application Server
Management
40 121.244.234.53 Hyperion Foundation Configure Web Sever
Patches applied:
Sl.N
Patch Number Patch Name PRDWEB PRDHFM PRDESS
o
1 6880880 Opatch
2 14020629 Shared Services
3 13936087 EPM Workspace
Reporting and
4 14200932 x x
Analysis
5 13997553 Financial Reporting x x
6 14173894 FDM x x
7 13967787 ERPI x x
8 13952743 ADF Patch1 x

9 14339256 ADF Patch2 x
10 14036837 HFM x x x
12 15850273 HFM x
13 13925741 Calculation Manager x x
14 14031912 EPMA x
15 13905088 Planning x x
Disclosure
16 14153925 x x
Management
17 16238382 Smart View
File: 350528332
3.2.9 Upgrade
Version upgrade of the various components of the Oracle EPM Suite can happen via patch
application as and when applicable.
3.2.10 Configuration
Administrator will have complete control over the application to make any configurational changes
as and when required.
Security privileges can be altered from Shared Services
Calculation Scripts can be changed from EAS.
Forms and tasklist changes can be made from the planning applications.
Metadata changes can be made from the EPMA (dimension library-central repository
for all planning applications)
Environment variable changes can be made from EAS.
Report changes can be made from FR Studio.
Application deployment and application specific metadata changes can be made from
Application Library.
3.2.11 Retention, Archive and Backup Strategy

Weekly
# Activity IP Backup Script Name Remark

Step Hyperion_Artifact_Expor
Hyperion Artifacts 121.244.234.53 Script Form,scripts, rules etc
1 t
Step Stop Hyperion
121.244.234.53 Script Stop_Hyp_Ser.bat Stops all hyperion services
2 Services
Step Stop Hyperion
3 Services
Step Stop Orphan
121.244.234.54 Script Stop_Orp_Ser.bat Stops all hyperion services
4 Processes
Step Stop Hyperion
5 Services
All Schema and
Step
Database Export 121.244.234.56 Script Oracle_SID_backup corresponding tables
6
backup
Step Windows Registry key
Registry Keys 121.244.234.53 Script Reg_key
7 export
8 export
9 export
10 export
Step Environment Windows environment
121.244.234.53 Script Env_Var.bat
11 Variables variables export
Step NetBack
FileSystem 121.244.234.53 NA Drive to be backed up
15 up
File: 350528332
Weekly
# Activity IP Backup Script Name Remark

Step NetBack
16 up
Step NetBack
17 up
Step NetBack
18 up
Step Start Hyperion
121.244.234.53 Script Start_Hyp_Ser.bat Starts all hyperion services
19 Services
Step Start Hyperion
20 Services
Step Start Hyperion
21 Services
RMAN is used for online DB backup on a daily basis.

Archive logs of the database server have been set to a maximum of 15Gb and the space would
have to be continually cleared by the DBA team to ensure smooth running of the application.
3.2.12 Performance Management
Hyperion Planning implementation is a managed system; hence external performance optimizations

will not be feasible
3.2.13 Troubleshooting
Troubleshooting can be carried out at 2 levels:

Standard Oracle Documents can be referred.
Service Requests can be raised with Oracle.
3.2.14 Other Maintenance Activities

Refer to Doc TCL HP Implementation - Operations Manual_v1 0
5 Development Tools and Technologies

Solution architecture is built on Hyperion Planning and Hyperion Essbase v11.1.2.2
standard features.
Hyperion Planning 11.1.2.2.3

- Comprehensive web based tool to coordinate and manage critical elements of planning
cycle
Hyperion Essbase 11.1.2.2
File: 350528332
- Multidimensional OLAP database engine to consolidate plan numbers and calculate

KPIs
Hyperion EPMA 11.1.2.2.3
- Comprehensive web based tool to model Hyperion planning dimensions
Hyperion Financial Reporting 11.1.2.2.3
- Comprehensive reporting tool to generate pdf reports
Hyperion Calculation Manager 11.1.2.2.3
- Comprehensive web based tool to create calculations and deploy on planning solution
Hyperion Smart View 11.1.2.2.3
ODI 11g
Oracle Database 11g R2
6 Test Aspects
The Development environment has been used to carry out the testing. Depending on the
requirement, separate applications are created for Development and testing. User manuals have
been provided to individual users for convenience.
Doc: 10270-Project Spring (User Acceptance Testing Log) describes the test cases which were
successfully covered during the UAT sessions.
7 Open Issues
ID Description Raised by whom, when Responsible person Status
resolve
4. Design Books
The following are book recommendations if you want to improve your design skills:
UML Distilled Third Edition, by Martin Fowler
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and
Iterative Development, by Craig Larman
File: 350528332
5. Template Change Highlights

[To be removed when using template for writing System Spec for project]
Version Date Change Made By
220-00 V0-1 2005-09-28 Replace first 3 pages (Cover, TOC, Document R. Tremblay
Control)
220-00 V0-2 2007-06-29 Added in Overview instructions to identify for users B. Christy
sections of document for their focus & approval
220-00 V0-2 2007-12-18 Restored page headers and footers and B. Christy
incorporated new logo 2007
220-00 V1-5 2009-12-16 Revamped structure of document not to require W. Eschebach
System Structure and System Architecture
documents anymore. Also providing more
instructions to author for each section.

Project Spring - 220 (System Specifications) V 3.0 - 2013!09!26

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Project Spring - 220 (System Specifications) V 3.0 - 2013!09!26

Caricato da

Copyright:

Formati disponibili

Project: Project Spring

Document scope: System Specifications Document Page 1 of 51

220-00 System Specifications

10270 PROJECT SPRING

<Systems specification for Hyperion Planning>

10270 Project Spring_-220-00System Specs-V2.0

10270 PROJECT SPRING 1

4.1 DATA DESCRIPTION 34

1.1 Version History

Version Date Description of Changes Made by

1.2 Review History

Version Date Reviewer Signature

2.0 2013-09-20 Mohammad Imran Project Manager

1.3 Financial Control Review History

Version Date Reviewer Signature

1.4 Referenced Documents

Robust monthly reporting processes for the Group

2.2 Summary of Solution

2.3.1 Entity Scope

No. Entity Name Functional Local

8 Neotel South Africa ZAR ZAR

2.3.2 Functional Scope

2.3.2.1 Planning Budgeting and Reporting

oCost Allocation/distribution among various products/LOBs/etc.

2.3.3 Technical Scope

2.3.4 Integration Scope

Transformation process to provide data in desired format. PwC will only be

2.5 Intended Audience

2.6 Acronyms and Terminology

Target Architecture Overview

Hyperion Planning 11.1.2.2.3

Oracle Database 11g R2

The architecture comprises of 4 layers primarily:

3.2.1 Solution Description

The details of the Interface are in attached document..

Systems Interface Method

The following interfaces will be developed: (These documents will be changed as

- Prism Interface for Employee Related information

TCL - Project Spring - Planning -Prism Data Source details v0.1D.zip

- GBS interface for Traffic Minutes

TCL - Project Spring - Planning -GBS Data Source details v0.1D.zip

- Intec Interface for Traffic minutes

TCL - Project Spring - Planning -Inec Data Source details v0.1D.zip

- SAP interface for Revenue

Data Identification Mapping.zip

- SAP ERP Financial Oracle HFM interface

TCL Interface Tasks

1 General Application Description

Define Various years data TCL planning is Sparse Year

Covers all Account heads or in other words Dense Account

Dimension Dense/Spar Dimension

HSP_Rates Stores Rates. System Internal Dense Rate

Board Sponsor Board Sponsor for Capex Project Sparse Generic

CERNO Attribute for CAPEX Projects Sparse Attribute

Dimension Dense/Spar Dimension

MIS_Line_Item MIS Grouping of Cost Centres Sparse Attribute

Following reports are identified as required reports from system

Project Spring - Form

AOP Dimensions/ Attribute dimensions:

Applic Variabl Dimen

Applic Variabl Dimen

3. Balance Sheet & Cash Flow

Dimension Dimension Type