Beruflich Dokumente
Kultur Dokumente
Version: 3.0
Date: 2013-09-26
Status: Draft
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
1. Document Control
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 3 of 51
Document scope: Systems Specifications Document
File: 350528332
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:
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.
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 4 of 51
Document scope: Systems Specifications Document
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
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
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
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 5 of 51
Document scope: Systems Specifications Document
File: 350528332
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 6 of 51
Document scope: Systems Specifications Document
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
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
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 7 of 51
Document scope: Systems Specifications Document
File: 350528332
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
Terms and acronyms used in this document are defined in the following table.
Term Definition
FR Financial Reports
DBA Database Administrator
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 8 of 51
Document scope: Systems Specifications Document
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
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 9 of 51
Document scope: Systems Specifications Document
File: 350528332
Technical Architecture:
Design Overview
The entire Planning and Budgeting process can be designed to work as shown below:
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 10 of 51
Document scope: Systems Specifications Document
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.
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 11 of 51
Document scope: Systems Specifications Document
File: 350528332
3.1 AS-IS
The current Planning is carried out using Microsoft Office mainly Excel
3.2 TO-BE
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).
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 12 of 51
Document scope: Systems Specifications Document
File: 350528332
2 Hyperion Planning
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
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 14 of 51
Document scope: Systems Specifications Document
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
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 15 of 51
Document scope: Systems Specifications Document
File: 350528332
All_VP1 Covers VP1 details for the cost centres Sparse Attribute
All_VP2 Covers VP2 details for the cost centres Sparse Attribute
All_VP3 Covers VP3 details for the cost centres Sparse Attribute
5 Dimensional Structure
Project Spring -
Dimension Details.xlsx
6 Reports Dictionary
Project Spring -
Report Details.xlsx
7 Forms Inventory
Following forms will be created in system
8 Variables Inventory
Project Spring -
Variables List.xlsx
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 17 of 51
Document scope: Systems Specifications Document
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.
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
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 18 of 51
Document scope: Systems Specifications Document
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:
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 20 of 51
Document scope: Systems Specifications Document
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
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 21 of 51
Document scope: Systems Specifications Document
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
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 22 of 51
Document scope: Systems Specifications Document
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
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):
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
BS_S7_R1 Standard Pl items flow to BS for all Entities except Neotel
BS_S8_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
BS_S12_R Standard Pl items flow to BS for all Entities except Neotel
1
BS_S13_R Standard Pl items flow to BS for all Entities except Neotel
1
BS_S16_R Standard Pl items flow to BS for all Entities except Neotel
1
BS_S19_R Standard Pl items flow to BS for all Entities except Neotel
1
CF_R1 Standard Pl items flow to CF for all Entities except Neotel
Scripts:
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 24 of 51
Document scope: Systems Specifications Document
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_S7 Aggregation and Standard Pl items flow to BS for Neotel
BS_S8 Aggregation and Standard Pl items flow to BS for Neotel
BS_S9 Aggregation
BS_S10 Aggregation and Standard Pl items flow to BS for Neotel
BS_S11 Aggregation
BS_S12 Aggregation and Standard Pl items flow to BS for Neotel
BS_S13 Aggregation and Standard Pl items flow to BS for Neotel
BS_S14 Aggregation
BS_S15 Aggregation
BS_S16 Aggregation and Standard Pl items flow to BS for Neotel
BS_S17 Aggregation
BS_S18 Aggregation
BS_S19 Aggregation and Standard Pl items flow to BS for Neotel
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
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 25 of 51
Document scope: Systems Specifications Document
File: 350528332
014_plug","SB_12111220-016_plug","SB_12111230-001_plug","SB_12111230-
002_plug","SB_12111230-003_plug","SB_12111240-001_plug","SB_12111240-
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_22000000_plug","SB_23000000_plug","SB_24000000_plug","SB_13000
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:
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.
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 27 of 51
Document scope: Systems Specifications Document
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
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
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 28 of 51
Document scope: Systems Specifications Document
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
o SAP data in KSB1 Dump for extracting GL/CC wise details for TCL and TCIPL
entities
o Manual files for
License Fees
Bad Debts
Interconnect cost
MIS Line items level details for TCTSL, TCPSL and TCL Lanka entities
Data will be primarily captured in GL-CC level for each month and entity
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 29 of 51
Document scope: Systems Specifications Document
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
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
3. Once satisfied with the Budget draft, BU manager graduates the budget to corporate by
following 4 step process:
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.
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.
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 30 of 51
Document scope: Systems Specifications Document
File: 350528332
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 31 of 51
Document scope: Systems Specifications Document
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.
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 32 of 51
Document scope: Systems Specifications Document
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 satisfy Variance reporting requirement Plan data be loaded in Actual Cube in a batch
process.
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 33 of 51
Document scope: Systems Specifications Document
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 satisfy Variance reporting requirement Actuals data will be loaded in ASO Cube in a
batch process.
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
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 34 of 51
Document scope: Systems Specifications Document
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
3 Data conversion
NA
NA
NA
NA
1 Common specifications
NA
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 35 of 51
Document scope: Systems Specifications Document
File: 350528332
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
NA. Users will have to raise SDP ticket manually as and when they face issues.
1 Performance
Performance:
Hyperion Planning is a high query performance system. Performance for Hyperion
is data driven.
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 36 of 51
Document scope: Systems Specifications Document
File: 350528332
The Data synchronization timings will depend linearly upon data volume
synchronized.
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.
Mid scalable:
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 37 of 51
Document scope: Systems Specifications Document
File: 350528332
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.
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 38 of 51
Document scope: Systems Specifications Document
File: 350528332
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 39 of 51
Document scope: Systems Specifications Document
File: 350528332
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 40 of 51
Document scope: Systems Specifications Document
File: 350528332
4 Manageability
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.
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 42 of 51
Document scope: Systems Specifications Document
File: 350528332
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
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 43 of 51
Document scope: Systems Specifications Document
File: 350528332
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
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).
16 121.244.234.54
This needs to be installed via Add Roles. Install IIS, Application server,
ASP.NET and IIS6 metabase compatibility. Without this HFM will not run
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).
17 121.244.234.55
This needs to be installed via Add Roles. Install IIS, Application server,
ASP.NET and IIS6 metabase compatibility. Without this HFM will not run
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).
18 121.244.234.56
This needs to be installed via Add Roles. Install IIS, Application server,
ASP.NET and IIS6 metabase compatibility. Without this HFM will not run
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 44 of 51
Document scope: Systems Specifications Document
File: 350528332
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"
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
28 121.244.234.54
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"
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
29 121.244.234.55
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"
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
30 121.244.234.56
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"
Disable the Windows User option of "Delete Temporary folder content on log
31 121.244.234.53
off".
Disable the Windows User option of "Delete Temporary folder content on log
32 121.244.234.54
off".
Disable the Windows User option of "Delete Temporary folder content on log
33 121.244.234.55
off".
Disable the Windows User option of "Delete Temporary folder content on log
34 121.244.234.56
off".
35 121.244.234.53 Internet Explorer level of security should be low
36 121.244.234.54 Internet Explorer level of security should be low
37 121.244.234.55 Internet Explorer level of security should be low
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 45 of 51
Document scope: Systems Specifications Document
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
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 47 of 51
Document scope: Systems Specifications Document
File: 350528332
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
14 14031912 EPMA x
15 13905088 Planning x x
Disclosure
16 14153925 x x
Management
17 16238382 Smart View
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 48 of 51
Document scope: Systems Specifications Document
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.
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 49 of 51
Document scope: Systems Specifications Document
File: 350528332
Weekly
3.2.13 Troubleshooting
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
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 51 of 51
Document scope: Systems Specifications Document
File: 350528332
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.
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.