Sample of Kent's Work

1
Indian and Northern Affairs Canada
Financial Status Reporting Manager Model

(Using Cognos Enterprise Planning)
Release 1.0 REQ
Draft Version # 0.1 CIDM # XXX March 25, 2009
CFO
Indian and Northern Affairs Canada (INAC)
INAC FSR Business Requirements
Business Requirements
Document Change Control

Version 0.1 0.2 0.3 Date of Issue March 24, 2009 Comments Initial Draft Author Kent Lysell
CIDM # XXX
Last updated: 13/04/2011
06:28:00 PM
Page 3 of 113
Table of Contents Introduction.............................................................................................8

Scope............................................................................................................................................8 Business Objectives.....................................................................................................................8
Process Overview....................................................................................9
Introduction..................................................................................................................................9 Overview - As Is..........................................................................................................................9 Swimlane Diagram To Be.......................................................................................................10 Activity......................................................................................................................................10
Appendix A Use Cases.......................................................................13

UC 1.1 CFO Sends Call Letter to All RC Managers..............................................................13 Process Steps..........................................................................................................................13 UC 1.2 RC Manager Opens Up EP Workflow and EP Contributor and Views Their RCMs Financial Data on the Financial Summary and RCM Plan Tabs...............................................13 Process Steps..........................................................................................................................14 UC 1.3 RC Manager Opens Up RCM Plan - OM Tab Within EP Contributor and Identifies and Records RCM Plans for Remainder of Fiscal Year............................................................14 Process Steps..........................................................................................................................15 UC 1.4 RC Manager Opens Up Anticipated Transfers Tab Within EP Contributor, Identifies Outstanding, Unrecorded Transfer Opportunities and Enters This Data into the Anticipated Transfers Tab.............................................................................................................................15 Process Steps..........................................................................................................................15 UC 1.5 RC Manager Opens Up Anticipated Expenditures Tab Within EP Contributor, Identifies Unrecorded Anticipated Expenditures and Enters This Data into the Anticipated Expenditures Tab.......................................................................................................................16 Process Steps..........................................................................................................................16 UC 1.6 RC Manager Opens Up Variance Explanation Tab Within EP Contributor, Analyzes Variances and Reduces Them to Zero.......................................................................................17 Process Steps..........................................................................................................................17
Appendix B Products.........................................................................19
EP 1.1 Contributor Workflow.................................................................................................19 EP 1.2 RCM Plan....................................................................................................................20 Business and Content Rules...................................................................................................20 EP 1.3 Anticipated Transfers..................................................................................................22 Business and Content Rules ................................................................................................................................................22 EP 1.4 Anticipated Expenditures............................................................................................24 Business and Content Rules ................................................................................................................................................25 Business and Content Rules ................................................................................................................................................26
CIDM # XXX
06:28:00 PM
Page 4 of 113
EP 1.6 Variance Explanation..................................................................................................30 Business and Content Rules ................................................................................................................................................30
Appendix C BI Reports.....................................................................33
BIR-1 RCM Plan........................................................................................................................33 General Requirements............................................................................................................33 Design Requirements.............................................................................................................33 Data Requirements.................................................................................................................36 BIR-2 Anticipated Transfers......................................................................................................43 General Requirements............................................................................................................43 Design Requirements.............................................................................................................44 Data Requirements.................................................................................................................47 BIR-3 Anticipated Expenditures................................................................................................53 General Requirements............................................................................................................53 Design Requirements.............................................................................................................54 Data Requirements.................................................................................................................57 BIR-4 Financial Summary.........................................................................................................63 General Requirements............................................................................................................63 Design Requirements.............................................................................................................64 Data Requirements.................................................................................................................66 BIR-5 Variance Explanation......................................................................................................74 General Requirements............................................................................................................74 Design Requirements.............................................................................................................74 Data Requirements.................................................................................................................77
Appendix D BI Cubes........................................................................83
General Requirements and Benefits...........................................................................................83 Overview....................................................................................................................................83 BIC-1 RCM Plan........................................................................................................................85 General Requirements............................................................................................................85 Design Requirements.............................................................................................................86 Data Requirements ................................................................................................................................................88 Other Requirements...............................................................................................................91 BIC-2 Anticipated Transfers......................................................................................................92 General Requirements............................................................................................................92 ................................................................................................................................................92 Design Requirements.............................................................................................................93 Data Requirements ................................................................................................................................................95
CIDM # XXX Last updated: 13/04/2011
06:28:00 PM
Page 5 of 113
Other Requirements ................................................................................................................................................96 BIC-3 Anticipated Expenditures................................................................................................97 General Requirements............................................................................................................97 Design Requirements.............................................................................................................98 Data Requirements ..............................................................................................................................................100 Other Requirements ..............................................................................................................................................101 BIC-4 Financial Summary.......................................................................................................102 General Requirements..........................................................................................................102 Design Requirements...........................................................................................................103 Data Requirements ..............................................................................................................................................105 Other Requirements ..............................................................................................................................................107 BIC-5 Variance Explanation....................................................................................................108 General Requirements..........................................................................................................108 Design Requirements...........................................................................................................108 Data Requirements ..............................................................................................................................................110 Other Requirements ..............................................................................................................................................112
CIDM # XXX
06:28:00 PM
Page 6 of 113
CIDM # XXX
06:28:00 PM
Page 7 of 113
Introduction
Scope
IBM Cognos Enterprise Planning tool (EP) provides a number of capabilities which will support the financial planning process. The diagram below provides an overview of the various INAC financial planning sub-processes involved.
Dept Resource Planning In Year Financial Status Reporting Year End ARLU Manage ment Initial Budget Allocation Risk Management(Pressures, Surpluses, Cash Mgmt) Budget Tsf, Supps, Reallocations
Based on a preliminary review of these processes, the in-year financial status reporting (FSR) sub-process is the first candidate for initial EP development. As noted in the Business Opportunity Proposal, this sub-process is well suited for the following reasons: The data is easily accessible; The EDW team is very familiar with the process; The EP solution can be controlled centrally and rolled out selectively; The timelines for rollout can be met; and Automating the process can provide significant benefit relative to the current approach. The financial status reporting work can leverage the existing BI work done to support FSR and therefore should have minimal impact on the EDW and existing datamarts.
Business Objectives
The current FSR process is supported by a number of Cognos-based reports and analytical cubes. This requirement will continue to build on the existing tools and will leverage the Enterprise Planning (EP) product to achieve the following: a) To provide an alternative to black books and spreadsheets for managers and directors to manage and track their planned (i.e., not recorded in OASIS) financial activities on a daily basis; b) To support the monthly gathering of forecast-related information from each responsibility centre across the organization; c) To create an integrated and streamlined process that leverages technology to provide management with reliable, accurate and timely information to support strategic in-year resource decisions; and d) Will provide managers with key financial and operational information in support of the accountability framework for resources entrusted to them
CIDM # XXX
06:28:00 PM
Page 8 of 113
It is the official framework for reporting on financial status and resource utilization to the departmental Financial Management Committee (FMC).
Process Overview
Introduction
The Financial Status Reporting (FSR) process is currently designed to obtain and communicate financial forecasting information from across the department to the Finance group for the purposes of: a) Confirming the finances and the financial situation of each RCM; b) Forecasting spending to the end of the year; c) Identifying funding pressures; d) Identifying surplus funds available for transfer to other priorities; e) Identifying needs to transfer funds between votes; and f) Identifying cash management requests.
Overview - As Is
A FSR Call Package is sent out by Finance to each RCM beginning in June of each year. The purpose of the Call Package is to provide the framework for completing the FSR, with the first reporting period starting in September. Other months where this FSR process takes place and where there may be further iterative changes are October, December, January, February and March. The package includes financial information generated from the Integrated Financials System (IFS) datamart using Cognos reporting tools and provides each recipient with their current financial status i.e., actual expenditures, current budget, commitments, obligations and free balance. The packages are received by each Responsibility Centre Manager (RCM) or Director who confirms the financial status for their responsibility centre(s), updates their forecasted spending to the end of the year and identifies funding pressures or surpluses. Funding variances due to funding pressures or surpluses (free balance less forecasted expenditure) are then addressed through internal transfers or cash management. As each Manager or Director completes their FSR package i.e. submits their final numbers the results are rolled up and reviewed by the next level in the organizational hierarchy. For example: each package of RC Managers FSRs is consolidated to, and reviewed at, the Regional level by the DG; each package of DGs FSRs is consolidated and reviewed at the departmental level by ADM. Remaining or unexplained funding variances not managed within a managers or DGs domain are passed up to the next level of the hierarchy, and it is at this higher level where alternative means for offsetting funding variances such as internal cash management or external budget and
06:28:00 PM
Page 9 of 113
vote transfers may be used. After all organizational levels have completed their FSR updates, Finance then reviews the results and puts together a Summary Report for review and action by the FMC.
Swimlane Diagram To Be
Activity
Step 1.0 CFO Sends Call Letter to All RC Managers: Call Letters are sent out to all RC Managers in select months of the fiscal year, which are September, October, December, January, February and March, and this instructs the RC Managers that they are to start the FSR updating process. Step 1.1 Review Financial Data: RC Managers open up Enterprise Planning Contributor and view their RCMs to become familiar with Actuals, Commitments, Obligations and Free Balances. The tools that are available for them to view the financial information are EP Contributor RCM Plan and Financial Summary. In addition, the RC Manager can use the following tools for more information: the BI Reports RCM Plan and Financial Summary; and BI Cubes RCM Plan and Financial Summary
CIDM # XXX
06:28:00 PM
Page 10 of 113
Step 1.2 Identify and Record RCM Plans: The recording of RCM Plans is the first of the four pieces of information entered in by the RCM Manager. In EP Contributor, the RC Manager opens up the RCM Plan tab and fills in their plans in the Plan column, which is associated with other fields of data populated from Oasis such as Auth-BA, Planning Objects, Authority Description, Budget Activity Description, Budget, Anticipated Transfers, Revised Budget, Plan, Actual, Obligation, Commitment, Soft Commit, Remain Balance, Anticipated Expenditures, Total Forecast and Plan Forecast. In addition to viewing the financial information on the RCM Plan tab, RC Managers can use the BI Report RCM Plan and BI Cube RCM Plan to assist in providing the necessary information in order to complete the entering in of their plans. Step 1.3 Identify Unrecorded Transfers: Identifying and recording anticipated transfers is the second of four pieces of information entered into the FSR by the RCM Manager. After identifying all unrecorded, anticipated transfers, the RC Manager opens up the Anticipated Transfers tab in EP Contributor and inputs each transfer associated with an Auth-BA code and fills in additional fields of data such as: Project Code, Amount, Budget Transfer Type, RCM Explanation, Sector or Corp Contact, From Reg or Sector and To Reg or Sector. RC Managers can use the BI Report Anticipated Transfers and BI Cube Anticipated Transfers to assist in providing the necessary information in order to complete the entering in of their plans. Step 1.4 Identify Unrecorded Anticipated Expenditures: The FSR Manager inputs unrecorded and anticipated expenditures into the FSR, which is the third of four pieces of information. He or she first identifies all outstanding and unrecorded anticipated expenditures and then opens up the Anticipated Expenditures tab in EP Contributor. All anticipated expenditures are then entered in each with an associated Auth-BA code along with the other fields of data such as: Planning Object; Planning Code; Amount; Anticipated Exp Type and RCM Explanation. To assist in the analysis of anticipated expenditures, RC Managers can use the BI Report Anticipated Transfers and BI Cube Anticipated Transfers. Step 1.5 Identify and Analyze Variances: Budget pressures (deficits) and surpluses (lapses) are calculated by subtracting anticipated expenditures from funds available. Each RCM owner level should be able to identify how their forecast variance should be addressed within their domain and then generate a list of resulting pressures, surpluses as well as the means to address them vis--vis anticipated transfers and expenditures. Variances are revised and explained by changes in anticipated transfers and expenditures or internal cash management, with the goal of creating a zero variance. Any remaining variances are identified as one of Declared Surplus, Declared Deficit, Cash Managed Internally-Surplus or Cash Managed Internally-Deficit.
CIDM # XXX
06:28:00 PM
Page 11 of 113
Within EP Contributor, the RC Manager opens up the Financial Summary tab and views the data in the Revised Variance column. Any variances that are left over after the RC Manager has entered in Anticipated Transfers and Anticipated Expenditures can be offset resulting in a zero variance. This is achieved by entering in the fourth piece of information which entails opening up the Variance Explanation tab and for every variance identified in the Revised Variance column, the RC Manager will fill in the fields associated with each variance such as: Auth-BA, Project Code, Amount, Variance Type, RCM Explanation, Sector or Corp Contact, Sector to Address and Branch to Address. To assist in the analysis of revised variances, RC Managers can use the BI Reports Financial Summary and Variance Explanation and BI Cubes Financial Summary and Variance Explanation. Step 1.6 Submit to Regional Manager: Upon completion, the user will submit their FSRs for review at the next level of the organization, which is the Director General for the Region. This is achieved by opening up EP Workflow and first pressing the Validate button. After correcting any noted errors from data entry errors and omissions of key fields, the RC Manager presses the Submit button, which enables the FSRs to be reviewed at the Regional level in the hierarchy. Step 2.0 DG Reviews, Analyzes Variances and Approves FSRs : The Regional Manager (DG) signs into their BI portal, reviews the status report for their RCMs FSRs and addresses unexplained variances via cash management or budget transfers at the regional level. If necessary, the DG will move a variance disposition from one column to another for example a pressure request could be moved to be cash managed if the DG has an alternate funding source for the line item. When all FSRs have been submitted and all variances explained to the degree possible, the DG will approve all reporting RCMs variance dispositions.
CIDM # XXX
06:28:00 PM
Page 12 of 113
Appendix A Use Cases

UC 1.1 CFO Sends Call Letter to All RC Managers
Goals Actors Timing 1) To inform RC Managers that they can go into EP Contributor to update their FSRs CFO Office, individual RC Managers responsible for their respective FSRs. During the third week of September, October, January, February and March 1) All actuals and budgetary information must have been entered accurately into Oasis. 2) All FSRs must reflect accurate information from Oasis before being updated in the Enterprise Planning (EP) Contributor. 3) All RC Managers responsible for their respective FSRs must be identified and their access rights set in order for them to view only their FSRs within EP Contributor. 1) Open lines of communication are kept through regular correspondence with the various RC Managers to answer any outstanding questions. 1) Expenditures and budgets were entered correctly into Oasis as they were incurred and registered, and this data is being reflected properly in the FSRs. 2) All Call Package financial information is being accessed within EP Contributor by the correct RC Manager, who is directly responsible for these FSRs at the lowest management level of RC responsibility in the hierarchy. 3) There are direct lines of communication open to the appropriate representative of the CFO Office during regular business hours. 1) The RC Managers by whom the FSRs are being assessed are the lowest management level in the RC hierarchy. 1) RM Managers are given access to only their RCMs FSRs. 2) The RC Manager will not be able to directly alter financial data populated from Oasis into the FSRs as reported in EP Contributor. Only information that will help explain variances will be entered into the FSR(s). 3) The RC Manager will not be able to alter formulas in the FSRs that calculate variances and link data into summarized FSR views. 1) Financial officers in the CFO Office must be prepared to answer questions from the RC Manages regarding their FSRs. If necessary, they also must be able to provide training. 2) RC Managers must be made aware of the Call Package/FSR financial data updating process and the significance of their roles relative to the CFO Offices role in the context of the Accountability Framework.
Pre-conditions
Post Conditions
Assumptions
Business Rules
Security
Training
Process Steps
Step Action RC Managers are made aware of the existence of their financial information in EP Contributor vis--vis e-mail or a formal letter. The e-mail (letter) contains instructions and any supporting attachments as warranted. Comments
UC 1.2 RC Manager Opens Up EP Workflow and EP Contributor and Views Their RCMs Financial Data on the Financial Summary and RCM Plan Tabs
Goals 1) To ensure that RC Managers are able to view and become familiar with their financial data at a summarized level
CIDM # XXX
06:28:00 PM
Page 13 of 113
Actors Timing Pre-conditions Post Conditions Assumptions Business Rules Security Training
2) To provide a broad summarized view of the statuses of the RC Managers FSRs (i.e. incomplete, in progress, complete). 1) RC Managers 1) Once RC Managers have received their Call Letter, they will open up EP Workflow and EP Contributor starting on the third week of September, October, January, February and March. 1) All RC Managers must have received their Call Letters instructing them to commence the FSR process. 2) All RC Managers have been trained on how to access their FSRs within EP Workflow 1) None 1) None 1) RC Managers will only see the FSRs for which they are responsible within EP Workflow. 1) RC Managers will only have read access for data coming from Oasis and write access to data on which they are expected to report. 1) RC Managers must be trained on how to open up the EP Workflow and EP Contributor on-line sites within their Internet browser and how to maneuver around to access their FSRs.
Process Steps
Step 1 2 3 4 Action RC Managers open up their Internet browser and enter in the URL for the Cognos EP Workflow site. RC Managers then click on their RCMs for which they are responsible to complete the FSRs. For each RCM, RC Managers open up the RCM Plan tab and become familiar with the financial information. For each RMC, RC Managers open up the Financial Summary tab and become familiar with financial information contained on this tab. Comments
UC 1.3 RC Manager Opens Up RCM Plan - OM Tab Within EP Contributor and Identifies and Records RCM Plans for Remainder of Fiscal Year
Goals Actors Timing Pre-conditions Post Conditions Assumptions Business Rules Security 1) To ensure that the RC Manager accurately enters in his or her RCM Plan data as instructed and reflecting reality as closely as possible 2) To provide an easy to use format for RC Managers to enter in their RCM Plan RC Managers RC Managers enter in their RCM Plans starting on the third week of the months September, October, January, February and March. 1) All data must be reflected accurately from Oasis in order for RC Managers to be able to enter in their RCM Plans accurately. 2) RC Managers must be trained on how to calculate their RCM Plans for the remainder of the current fiscal year. 1) None 1) It is assumed that all RCM Managers are aware of their RCM Plans. 1) None 1) RC Manager only will be able to view their RCM Plans for which they are responsible. 2) RC Manager will not be able to change data in the RCM Plan OM tab other than data in the Plan column.
CIDM # XXX
06:28:00 PM
Page 14 of 113
Training
1) RC Managers must be trained on how to calculate their RCM Plans.
Process Steps
Step 1 Action RC Manager opens up the RCM Plan tab in EP Contributor RC Manager calculates their RCM Plans for remainder of the year. RC Manager enters in his/her RCM Plans into the Plan column corresponding to the Auth-BA and Planning Object row headings. Comments This is out of scope for the project. It is assumed that RC Managers will have been trained on calculating their RCM Plans.
UC 1.4 RC Manager Opens Up Anticipated Transfers Tab Within EP Contributor, Identifies Outstanding, Unrecorded Transfer Opportunities and Enters This Data into the Anticipated Transfers Tab
Goals Actors Timing 1) To identify outstanding and unrecorded transfer opportunities budget or vote transfers in or out of the RCM and then updating this data in the Anticipated Transfers tab with the goal of minimizing budget variances 2) To create accurate and up-to-date information Actors are the RC Managers and their staff who would be able to identify these outstanding and unrecorded transfer opportunities This activity occurs starting on the third week of the months September, October, January, February and March. 1) RC Managers must have accurate and organized interim financial records in order to identify outstanding and unrecorded transfer opportunities not captured in Oasis. Each outstanding and unrecorded transfer opportunity must be attached to an Auth-BA code. The responsibility of maintaining accurate interim financial records lies with the RC Managers and is out of scope for the project. 1) All identified outstanding and unrecorded transfer opportunities must be entered into the Anticipated Transfers tab corresponding to the Auth-BA code. 1) See Pre-conditions above. 1) The identification of the outstanding, unrecorded transfer opportunities and entering them into the Anticipated Transfers tab must be performed in conjunction with an understanding of the information on the Financial Summarize tab and how this data is used in a calculation to minimize unexplained variances. There also must be allowance for Anticipated Expenditures in the calculation for minimizing unexplained variances. 1) The RM Manager must not be able to view the Anticipated Transfers tab in other RCMs for which they are not responsible. 1) RC Managers must be trained on how to identify and record transfer opportunities into the Anticipated Transfers tab in the context of minimizing unexplained variances.
Pre-conditions
Post Conditions Assumptions Business Rules
Security Training
Process Steps
Step 1 2 Action RC Manager opens up the Anticipated Transfers tab in EP Contributor Identify outstanding and unrecorded anticipated transfers Comments This falls out of scope for
CIDM # XXX
06:28:00 PM
Page 15 of 113
for the remainder of the fiscal year not captured by Oasis. 3 4 5 6 Open up the Financial Summary tab and understand the calculation incorporating the anticipated transfer that will minimize the unexplained variance. Open up the Anticipated Transfers tab and if not already done so, click on the Take Ownership button. Enter in the data, with each transfer corresponding to an Auth-BA row heading. Validate the data by clicking on the green checkmark button. Correct any errors noted.
this project and thus is the responsibility of the Department.
UC 1.5 RC Manager Opens Up Anticipated Expenditures Tab Within EP Contributor, Identifies Unrecorded Anticipated Expenditures and Enters This Data into the Anticipated Expenditures Tab
Goals Actors Timing 1) To ensure that all expenditures for the remainder of the fiscal year not captured by Oasis are reflected in the FSR with the express objective of minimizing unexplained variances 2) To create accurate and up-to-date information RC Managers and their staff privy to anticipated expenditures data not reflected in Oasis. This activity occurs starting on the third week of the months September, October, January, February and March. 1) RC Managers must have accurate and organized interim financial records in order to identify unrecorded anticipated expenditures not captured in Oasis. Each unrecorded, anticipated expenditure must be attached to an Auth-BA code. The responsibility of maintaining accurate interim financial records lies with the RC Managers and is out of scope for the project. 1) All identified outstanding and unrecorded transfer opportunities must be entered into the Anticipated Transfers tab corresponding to the Auth-BA code. 1) See Pre-conditions above. 1) The identification of the unrecorded anticipated expenditures and entering them into the Anticipated Expenditures tab must be performed in conjunction with an understanding of the information on the Financial Summary tab and how this data is used in a calculation to minimize unexplained variances. There also must be allowance for Anticipated Transfers in the calculation for minimizing unexplained variances. 1) The RM Manager must not be able to view the Anticipated Expenditures tab in other RCMs for which they are not responsible. 1) RC Managers must be trained on how to identify and record anticipated expenditures for the remainder of the fiscal year into the Anticipated Expenditures tab in the context of minimizing unexplained variances.
Pre-conditions
Post Conditions Assumptions Business Rules
Security Training
Process Steps
Step 1 2 3 Action RC Manager opens up the Anticipated Expenditures tab in EP Contributor Identify unrecorded anticipated expenditures for the remainder of the fiscal year not captured by Oasis. Open up the Financial Summary tab and understand the Comments This falls out of scope for this project and thus is the responsibility of the Department.
CIDM # XXX
06:28:00 PM
Page 16 of 113
4 5 6
calculation incorporating the anticipated expenditures that will minimize the unexplained variance. Open up the Anticipated Expenditure tab and if not already done so, click on the Take Ownership button in the top left of the menu bar. Enter in the data, with each unrecorded anticipated expenditure corresponding to an Auth-BA row heading. Validate the data by clicking on the green checkmark button. Correct any errors noted.
UC 1.6 RC Manager Opens Up Variance Explanation Tab Within EP Contributor, Analyzes Variances and Reduces Them to Zero
Goals Actors Timing Pre-conditions 1) To reduce remaining budget variances to zero after accounting for anticipated transfers and anticipated expenditures by explaining variances as declared surplus, declared deficit, cash managed internally-surplus or cash managed internally-deficit RC Managers and their staff privy to the in-house financial data This activity occurs starting on the third week of the months September, October, January, February and March. 1) RC Managers must have entered in their anticipated transfers and anticipated expenditures, and this information must be as accurate as possible. 1) All attempts must be made to reduce revised variances to zero by explaining these variances. 2) Any declared surpluses, declared deficits, cash managed internally-surplus and cash managed internally-deficit will be managed at the next level up, which is at the regional level. See pre- and post-conditions above. 1) Reduction of revised variances by explaining them as being one of declared surpluses, declared deficits, cash managed internally-surplus or cash managed internally-deficit is done only after anticipated transfers and anticipated expenditures have been accounted for. 2) Final Unexplained Variances will be reflected on the Financial Summary after Revised Variances are explained by one of Declared Surplus, Declared Deficit, Cash Managed Internally-Surplus or Cash Managed Internally-Deficit 3) The sign of the Variance Explanation is dictated by the Variance Type, and only this amount with its sign is linked into the Financial Summary tab. 4) The Variance Type of Declared Surplus, Declared Deficit, Cash Managed InternallySurplus and Cash Managed Internally-Deficit have an associated sign of positive, negative, positive and negative, respectively. 1) The RM Manager must not be able to view the Variance Explanation tab in other RCMs for which they are not responsible. 1) RC Managers must be trained on whether to flag a variance explanation as a Declared Surplus or Cash Managed Internally-Surplus and as a Declared Deficit or Cash Managed Internally-Deficit
Post Conditions Assumptions
Business Rules
Security Training
Process Steps
Step 1 2 Action RC Manager opens up the Financial Summary tab in EP Contributor RC Manager identifies and notes Revised Variances along with their associated Auth-BA code that are not zero in the Financial Summary tab and analyzes their natures Comments
CIDM # XXX
06:28:00 PM
Page 17 of 113
RC Manager opens up the Variance Explanation tab in EP Contributor RC Manager explains all non-zero Revised Variances in the Variance Explanation tab adjacent to their associated Auth-BA code as one of Declared Surplus, Declared Deficit, Cash Managed Internally-Surplus or Cash Managed Internally-Deficit. Validate the data by clicking on the green checkmark button. Correct any errors noted.
CIDM # XXX
06:28:00 PM
Page 18 of 113
Appendix B Products
EP 1.1 Contributor Workflow
The EP Contributor Workflow gives an overview of the FSRs for which the manager is responsible, their statuses - i.e. Not Started, Work in Progress or Complete - as well as ownership, reviewer and last date changes were made. RCM Managers can launch any FSR that they choose from the Contributor Workflow view. There is also a window below corresponding to the RCM that has been selected that can used for instructions or other notes. See below for an illustration.
CIDM # XXX
06:28:00 PM
Page 19 of 113
EP 1.2 RCM Plan

The RCM Plan tab contains fields corresponding to combinations of AUTH-BA and Planning Objects used to record RCM Managers plans for the remainder for the current fiscal year. RCM Plan has the following columns: AUTH-BA, Planning Objects; Authority Description; Budget Activity Description; Budget, Antic Transfers, Revised Budget, Plan, Actual, Obligation, Commitment, Soft Commit, Remain Bal, Total Forecast and Plan-Forecast. See below for an illustration.
Business and Content Rules

Row # 1
Column Authority Description Budget Activity Description
Column Calc Data (Text)
Data (Text)
3 4
Budget Antic Transfers
Data (Currency) Data (Currency)
Business Description - Defined as the authority description e.g. Salaries & Wages - Defined as the budget authority description e.g. Information technology services - Defined as the initial funds available to fund operations for the current fiscal year - Defined as transfers of funds in or out necessary to explain
Sourcing Option IFS
Business Rule
IFS
IFS Summation of Anticipated Tsfs from 2 Anticipated - Based on all input sheet rows from 02
CIDM # XXX
06:28:00 PM
Page 20 of 113
all or part of a budget variance
Tsfs
Anticipated Tsfs where Budget Tsf Type is one of Budget Transfer In(+), Budget Transfer Out(-), Vote Transfer In(+), Vote Transfer Out(-), or Declared Surplus(+)
Revised Budget Plan
Budget + Antic Tsfs (Currency) Data (Currency)
Actual
Data (Currency)
Obligation
Data (Currency)
Commitment
Data (Currency)
10
Soft Commit
Data (Currency)
11
Remain Balance
Plan (Actual + Obligation + Commitment + Soft Commit)
12
Antic Exp
Data (Currency) Actuals + Obligations + Commitments + Soft
13
Total Forecast
- Defined as the budget after factoring in anticipated transfers - Defined as the planned expenditures for the remainder of the current fiscal year - Defined as cumulative actual expenditures up to the most recent completed period - Defined as an expenditure not having yet occurred but is an obligation and may occur - Defined as an expenditure not having yet occurred but is committed to being expended vis--vis a purchase order - Defined as an expenditure not having yet occurred but may occur vis--vis a purchase requisition - Defined as the planned expenditures remaining after accounting for Actuals, Obligations, Commitments and Soft Commitments - Defined as expenditures anticipated to the year end, but not part of encumbrances - Defined as the total forecast after accounting for Actuals, Obligations,
Calculated
User Input
IFS
IFS
IFS
IFS
Calculated
Summation of Anticipated Exp from 3 Anticipated Exp Calculated
CIDM # XXX
06:28:00 PM
Page 21 of 113
Commitments + Anticipated Expenditures

14
Plan Forecast
Plan - Total Forecast
Commitments, Soft Commitments and Anticipated Expenditures - Defined as variance between Plan and Total Forecast
Calculated
EP 1.3 Anticipated Transfers

The Anticipated Tsfs tab contains fields corresponding to each AUTH-BA code used to calculate anticipated transfers for the RCM being reported on and has the following fields: AUTH-BA; Project Code; Amount; Budget Tsf Type; RCM Explanation; Sector Corp Contact; Reg Sec From; and Reg Sec To. See below for an illustration.

Row # 1
Column AUTH-BA
Column Calc Drop-down from DList (Text)
Business Description - AUTH-BA Hierarchy in the Dlist is based on the IFS hierarchy and the Chart of Accounts - enables user to select from the complete list of AUTHBA codes present in drop-down list
Sourcing Option IFS
Business Rule - Cell value = all valid Auth-BA combinations - Selecting a AUTH-BA code enables all data entered in the same row to map to the chosen drop-down value - User can also type in an existing AUTH-BA code - Data validation prevents User from
CIDM # XXX
06:28:00 PM
Page 22 of 113
entering in an inadmissible AUTH-BA code

2
Project Code
Data (Text)
- a numeric data entry field without data validation - part of the Chart of Accounts - a currency field enabling the user to enter in an amount for the anticipated transfer
IFS Dropdown - Figures in the Amount field must be positive - The sign of the figure will be set by the Budget Tsf Type field - Entering one of these four dropdown choices carries the figure from the Amount field in the 2 Anticipated Tsfs tab to the Antic Transfers field in the 4 Financial Summary and 1 RCM Plan tabs. - If the dropdown is Budget Transfer In, Budget Transfer Out, Vote Transfer In, or Vote Transfer Out, the amount will be positive, negative, positive, or negative, respectively. - Only the figure in the Amount field with the correct sign is carried back to the Financial Summary and RCM Plan tabs. - Data validation prevents the user from saving their choice if it is not one of the above four items. - will accept any type of input of an undefined length - can accept any type of character - selection that the user chooses will reflect (as a negative amount) in the selected Region (from the drop-down) in the same RCM as the current RCM being
Amount
Data (Currency)
IFS
Budget Tsf Type
Drop-down from DList (Text)
- a drop-down field with four choices: (i) Budget Transfer In(+) (ii) Budget Transfer Out(-); (iii) Vote Transfer In(+); and (iv) Vote Transfer Out(-)
IFS Dropdown
RCM Explanation Sector Corp Contact Reg Sec From
Data (Text)
Data (Text) Drop-down field from DList (Text)
- used to enter in an explanation for the anticipated transfer - used to enter in a contact name for the individual who is responsible for this anticipated transfer - enables the user to choose a Region from which to transfer funds.
User Input
User Input IFS Dropdown
CIDM # XXX
06:28:00 PM
Page 23 of 113
Reg Sec To
Drop-down field from DList (Text)
- enables the user to choose a Region to which to transfer funds.
IFS Dropdown
reported on - Data validation prevents the user from entering in data that is not an item in the dropdown list - User selection will reflect (as a positive amount) in the selected Region (from the dropdown) in the same RCM as the current RCM being reported on - Data validation prevents the user from entering in data that is not an item in the dropdown list
EP 1.4 Anticipated Expenditures

The Anticipated Exp tab contains fields corresponding to each AUTH-BA code used to calculate anticipated expenditures for the RCM being reported on and has the following fields: AUTH-BA; Planning Object; Project Code; Amount; Anticipated Exp Typ; and RCM Explanation. See below for an illustration.
CIDM # XXX
06:28:00 PM
Page 24 of 113

Row #
Column
Column Calc
Business Description - AUTH-BA Hierarchy in the Dlist is based on the IFS hierarchy and the Chart of Accounts - enables user to select from the complete list of AUTHBA codes present in drop-down list - a numeric dropdown field - part of the Chart of Accounts - a numeric dropdown field - part of the Chart of Accounts - a currency field enabling the user to enter in an amount for the anticipated transfer
Sourcing Option
Business Rule - Cell value = all valid AuthBA combinations - Selecting a AUTH-BA code enables all data entered in the same row to map to the chosen dropdown value - User can also type in an existing AUTH-BA code - Data validation prevents User from entering in an inadmissible AUTH-BA code
AUTH-BA
IFS dropdown
Planning Object Project Code
Data (Text)
IFS Dropdown
Data (Text)
IFS Dropdown - Figures in the Amount field must be positive - The sign of the figure will be set by the Budget Tsf Type field - Entering one of these two dropdown choices carries the figure from the Amount field in the 3 Anticipated Exp tab to the Antic Exp field in the 4 Financial Summary and 1 RCM Plan tabs. - If the dropdown is Increase or Decrease, the amount will be positive or negative, respectively. - Only the figure in the Amount field with the correct sign is carried back to the Financial Summary and RCM Plan tabs. - will accept any type of input of an undefined length
Amount
Data (Currency)
User Input
Anticipated Exp Type
- a drop-down field with two choices: (i) Increase(+); (ii) Decrease(-)
IFS Dropdown
RCM Explanation
Data (Text)
- used to enter in an explanation for the anticipated expenditure
User Input
CIDM # XXX
06:28:00 PM
Page 25 of 113
EP 1.5 Financial Summary

The Financial Summary tab contains a combination of data extracted from Oasis and data that is inputted in the three tabs - 2 Anticipated Tsfs, 3 Anticipated Exp and 5 Revised Variance. Fields extracted from Oasis are: AUTH-BA; Authority Description; Budget Activity Description; Budget (Current); Actual; Obligation; Commitment and Soft Commitment. Fields with data inputted by the user from either of the three tabs are: Antic Transfers; Antic Exp and Variance Expl. Fields that are calculated are: Revised Budget; Free Balance; Total Forecast, Revised Variance and Unexplained Var. See below for an illustration.

Row #
Column
Column Calc
AUTH-BA
Business Description - Enables User to select from the complete list of AUTHBA codes present in the drop-down list - AUTH-BA Hierarchy in the Dlist is based on the IFS hierarchy and the Chart of Accounts
Sourcing Option
Business Rules
IFS drop-down
- Cell value = all unique and valid Auth-BA combinations rolled up from the other four tabs 1 RCM Plan, Antic
CIDM # XXX
06:28:00 PM
Page 26 of 113
Authority Description
Data (Text)
Budget Activity Description
Data (Text)
Budget
Data (Currency)
Antic Transfers
Data (Currency)
Revised Budget
Budget + Antic Tsfs (Currency)
Actual
Data (Currency)
Obligation
Data (Currency) Data (Currency)
Commitment
- Defined as the authority description e.g. Salaries & Wages - Defined as the budget authority description e.g. Information technology services - Defined as the initial funds available to fund operations for the current fiscal year - Defined as transfers of funds in or out necessary to explain all or part of a budget variance - Defined as the budget after factoring in anticipated transfers - Defined as cumulative actual expenditures up to the most recent completed period - Defined as an expenditure not having yet occurred but is an obligation and may occur - Defined as an expenditure not having yet occurred but is committed to being expended vis-vis a
IFS
IFS
IFS
Summation of Anticipated Tsfs from 2 Anticipated Tsfs
- Based on all input sheet rows from 02 Anticipated Tsfs where Budget Tsf Type is one of Budget Transfer In(+), Budget Transfer Out(-), Vote Transfer In(+), Vote Transfer Out(-), or Declared Surplus(+)
Calculated
IFS
IFS
IFS
CIDM # XXX
06:28:00 PM
Page 27 of 113
10
Soft Commit
Data (Currency)
11
Free Balance
Revised Budget Actual Obligation Commitment Soft Commitment (Currency)
12
Antic Exp
Data (Currency)
13
Total Forecast
Actuals + Obligations + Commitments + Soft Commitments + Anticipated Expenditures
14
Revised Variance Variance Expl
Revised Budget Forecast Exp (Currency) Data (Currency)
15
purchase order - Defined as an expenditure not having yet occurred but may occur vis-vis a purchase requisition - Defined as the funds available after factoring in Actuals, Obligations, Commitments and Soft Commitments - Defined as expenditures anticipated the fourth week of the current period (from the cut-off date in Oasis), but not part of encumbrances - Defined as the total forecast after accounting for Actuals, Obligations, Commitments, Soft Commitments and Anticipated Expenditures - Defined as a Pressure (Deficit) or Lapse (Surplus) - Defined as the management of a budget surplus (lapse) or budget deficit (pressure) where the
IFS
Calculated
Summation of Antic Exp data
Calculated
Calculated Summation of Variance Expl data - Variances that are not offset by one of these Variance Type choices will carry into the next column as an unexplained variance
CIDM # XXX
06:28:00 PM
Page 28 of 113
16
Unexplained Var
Variance Revised Var Expl (Currency)
Variance Type for all input sheet rows from 5 Variance Explan is one of Cash Managed InternallyDeficit, Cash Managed InternallySurplus, Cash Management Request, Declared Pressure, or Declared Surplus - Defined as the variance that is yet unexplained after considering the revised variance explanations in the previous column.
Summation of Unexplained Var data
- Variances that are unexplained will be managed at the next level up in the hierarchy at the Regional level.
CIDM # XXX
06:28:00 PM
Page 29 of 113
EP 1.6 Variance Explanation

The Variance Explanation tab contains fields corresponding to each AUTH-BA code used to calculate variance explanations (in the Variance Expl fields in the 4 Financial Summary tab) for the RCM being reported on and has the following fields: AUTH-BA; Project Code; Amount; Variance Type; RCM Explanation; Sector Corp Contact; Sector to Address; and Branch to Address. See below for an illustration.

Row #
Column
Column Calc
AUTH-BA
Business Description - Enables User to select from the complete list of AUTH-BA codes present in the dropdown list - AUTH-BA Hierarchy in the Dlist is based on the IFS hierarchy and the Chart of Accounts - a numeric dropdown field - part of the Chart of Accounts - a currency field enabling the user to
Sourcing Option
Business Rules
IFS drop-down
- Cell value = all unique and valid Auth-BA combinations rolled up from the other four tabs 1 RCM Plan, Antic
2 3
Project Code Amount
Data (Text) Data (Currency)
IFS Dropdown User Input - Figures in the Amount field must be positive
CIDM # XXX
06:28:00 PM
Page 30 of 113
enter in an amount for the revised transfer
- The sign of the figure will be set by the Variance Type field - Data validation prevents the user from saving their choice if it is not one of the above four items. - Entering one of these four choices carries the figure from the Amount field in the 5 Revised Variance tab to the Variance Expl field in the 4 Financial Summary tab on the line corresponding to the AUTH-BA field in the first column. - Only the figure in the Amount field with the correct sign is carried back to the Financial Summary tab. - will accept any type of input of an undefined length
Variance Type
- a drop-down field with four choices: (i) Cash Managed Internally-Deficit(-); (ii) Cash Managed Internally-Surplus(+); (iii) Declared Pressure (-) and (v) Declared Surplus(+)
IFS Dropdown
RCM Explanation
Data (Text)
Sector Corp Contact
Data (Text)
Sector to Address
Drop-down field from DList (Text)
Branch to Address
Data (Text)
- used to enter in an explanation for the anticipated expenditure - used to enter in a contact name for the individual who is responsible for this variance explanation - a drop-down field that enables the user to choose a Region to which the revised variance pertains. - selection that the user chooses will reflect (as a negative or positive amount depending on the selection in the Variance Type field) in the selected Region (from the drop-down) in the same RCM as the current RCM being reported on - Data validation prevents the user from entering in data that is not an item in the drop-down list - will accept any type of input of an undefined length
User Input
User Input
- can accept any type of character
IFS Dropdown
User Input
CIDM # XXX
06:28:00 PM
Page 31 of 113
- used to enter in a Branch within the Region to which the variance explanation pertains
CIDM # XXX
06:28:00 PM
Page 32 of 113
Appendix C BI Reports
BIR-1 RCM Plan
General Requirements
Purpose of the Report This report will be used to facilitate the forecasting function for RC Managers through an analysis of items such as Budget, Antic Transfers, Revised Budget, Current Plan, Actuals, Obligations, Commitments, Soft Commitments, Remaining Balance, Anticipated Expenditures, Total Forecast and Plan - Forecast along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Report RCM Plan to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this report.
Audience Requirements
The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate.
Approach
Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Reports. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Report Studio Access Settings / Restrictions There are no access settings or restrictions for these reports at this initial design stage.
Design Requirements
Prompt Parameters The user is able to drill down to subsequent levels using the plus signs adjacent to entities in the organizational hierarchy. Below is an illustration of the parent drill-down entity.
CIDM # XXX
06:28:00 PM
Page 33 of 113
The user can drill down until reaching the desired level. The entities within Indian and Northern Affair Canada (INAC) follows the hierarchical structure starting with regions (codes starting with E such as E900 BC Region) and then responsibility centres (RCMs) (codes starting with A such as A910 Manager, Assets & Planning). See below for an illustration.
CIDM # XXX
06:28:00 PM
Page 34 of 113
Header and Footer Information Header: centre - INAC Logo, name of the report Footer: left - date; centre - page number; left - time of report generation
CIDM # XXX
06:28:00 PM
Page 35 of 113
Report Samples
Footnotes None
Data Requirements
Reporting / Data Elements
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Region (D) Definition All major INAC reporting regions in Canada There are five regions listed: (i) E900 BC Region (ii) EB00 Executive Direction (iii) EK00 Aboriginal Economic Development (iv) EM00 Chief Financial Officer Regional codes start with E e.g. EB00 Executive Direction User selected by drill-down functionality 2 RCM (E) Organizational unit within INAC based on the IFS hierarchy that is 1.3 FSR Mgr - EList Source of Data 1.3 FSR Mgr - DList
CIDM # XXX
06:28:00 PM
Page 36 of 113
responsible for the transaction There are about 1500 RCMs RCM codes start with A e.g. AB00 Ministers Office 3 Vote (D) Vote is defined as the parent2 in the DList There are five main categories: Vote 1 Salary and O&M Vote 5 Capital Vote 10 Grants & Contributions Vote 20 Federal Interlocutor Operating Exp. Vote 25 Federal Interlocutor G&C 4 Resource Category (D) Resource Category is defined as the parent to Auth in the DList Examples of Resource Categories are: NS1 - INAC NON SALARY SA1 INAC SALARY NS2 - OFI NON SALARY 5 Auth-BA (D) Auth-BA hierarchy in the DList is based on the IFS hierarchy and the Chart of Accounts Defined as part of the line object hierarchy Defined as the initial funds available to fund operations for the current fiscal year Imported from IFS Expressed as a currency with two decimal places 8 Antic Transfers (M) Defined as transfers of funds in or out necessary to explain all or part Summation of all RCM FSRs anticipated transfer data, input by User, for the RCMs being 1.3 FSR Mgr DList 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr Auth-BA DList
Planning Object (D)
1.2 FSR Mgr D List
Budget (M)
1.3 FSR Mgr Summation of all RCM FSRs initial budget data, for the RCMs being analyzed.
CIDM # XXX
06:28:00 PM
Page 37 of 113
of a budget variance Based on all input sheets rows from 02 Anticipated Tsfs Expressed as a currency with two decimal places 9 Revised Budget (C) = Initial Budget + Antic Transfers Defined as the budget after factoring in anticipated transfers. Expressed as a currency with two decimal places 10 Plan (M) Defined as the initial plan as formulated by managers and previously entered into the Oasis Payments made under Section 33 of the Financial Administration Act (FAA), up to the most recent completed period Imported from IFS Expressed as a currency with two decimal places 12 Obligation (M) Obligations made under Section 32 of the FAA Defined as expenditures not having yet occurred but expressed as a likely expenditure Imported from IFS Expressed as a currency with two decimal places 13 Commitment (M) Defined as an expenditure not having yet occurred but is committed to being expended vis-vis a purchase order Defined as an expenditure not
analyzed.
Summation of all RCM FSRs Revised Budget data, for the RCMs being analyzed
1.3 FSR Mgr Summation of all RCM FSRs Plan data, for the RCMs being analyzed 1.3 FSR Mgr Summation of all RCM FSRs Actual data, for the RCMs being analyzed
11
Actual (M)
1.3 FSR Mgr - Summation of all RCM FSRs Obligations data, for the RCMs being analyzed
1.3 FSR Mgr - Summation of all RCM FSRs Commitments data, for the RCMs being analyzed 1.3 FSR Mgr Summation of all
14
Soft Commit (M)
CIDM # XXX
06:28:00 PM
Page 38 of 113
having yet occurred but may occur vis--vis a purchase requisition Imported from IFS Expressed as a currency with decimal places 15 Remain Balance (C) = Initial Plan (Actuals + Encumbrances)
RCM FSRs Soft Commit data, for the RCMs being analyzed
Summation of all RCM FSRs Remaining Balance data, for the RCMs being analyzed Summation of all RCM FSRs Antic Exp data, for the RCMs being analyzed
16
Antic Exp (M)
Defined as expenditures anticipated to the year end, but not part of encumbrances Based on all input sheets rows from Anticipated Exp Expressed as a currency with two decimal places
17
Total Forecast (C)
= Actual + Encumbrances + Antic Exp Defined as the expected total expenditures for the fiscal year Expressed as a currency with two decimal places
Summation of all RCM FSRs Total Forecast data, for the RCMs being analyzed
18
Plan - Forecast (C)
= Remain Balance Antic Exp
Summation of all RCM FSRs Plan Forecast data, for the RCMs being analyzed
Report Page Contents None Potential Data Sources (Data)

IFS datamart
Optional Requirements None
CIDM # XXX
06:28:00 PM
Page 39 of 113
Graph/Chart Information None Drill down Options Right-clicking anywhere on the report yields a menu with three items: 1) Drill down; 2) Drill up; and 3) Go to. However, none of these selections seems to be active. Drill through Options None Time Frame / # of Years reported There are no date parameters in this version. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None Data Requirements None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
Requirement Description Priority Scope Decision Included in Design Notes / Issues
Content and Business Rules None since covered in previous section - Data/Reporting Elements The table below details the information content included in this report.
# Column Column Calc Business Description Sourcing Option
CIDM # XXX
06:28:00 PM
Page 40 of 113
Filtering Options There are no filtering options for this report. Sorting Options This table below details the sort options required for this report.
Sort Order
1 2 3 4 5 6 Region RCM Vote Resource Category Auth-BA Planning Object
Column
Ascending (A) or Descending (D)

N/A A A A A A Y Y Y Y Y N
Subtotal (Y or N)
Reporting Requirements Not sure what I can put into this section Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
Training Requirements
Requirement Description
Show users how to bookmark Cognos reports in Internet Explorer Show users how to drill-down to select their RCM
Priority
Scope Decision
Included in Design
Notes / Issues
Accomplished via a URL link sent in body of an e-mail Locating an RCM and generating a report is simple and would not require much if any training
Low
Included in scope
No
Low
Included in scope
Yes
CIDM # XXX
06:28:00 PM
Page 41 of 113
Show users how to read and interpret report Show users how to print, e-mail and save report
Medium Medium
Included in scope
No Built-in features in Cognos Report Studio
Managers using these reports should already have the training required. Users can easily be shown through e-mailed instructions with screen shots.
Operational Requirements Not sure what to put into this section Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
Integration Requirements
BI Reports are integrated with EP/FSR Call Package reports, which require data input IFS datamarts
Priority
Scope Decision
Included in Design
Notes / Issues
All worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations in order for BI reports to reflect the correct data. Fresh datamarts must repopulate these BI reports at regular intervals to show current information.
High
Included
Yes
High
Included
Yes
Other Requirements Not sure what to put into section Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.)
CIDM # XXX
06:28:00 PM
Page 42 of 113
Scope Decision: is it included in scope Notes/Issues: Additional notes and comments

Totals Summary at bottom Grand totals Column 1: Region Sub totals Column 2: RCM Sub totals Column 3: Vote Sub totals Column 4: Resource Category Sub totals Column 5: Auth-BA Sub totals Footnotes None Other Requirements None Scheduling These reports can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the Financial Summary BI report. Exception Report Sample N/A
BIR-2 Anticipated Transfers

Purpose of the Report This report will be used to indicate the type of funds transfer Vote or Budget transfers in or out of the region or sector along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Report Anticipated Transfers to reflect this information and that all Call Packages have been sent to the respective RC Managers.
CIDM # XXX
06:28:00 PM
Page 43 of 113
Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this report. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Reports. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Report Studio Access Settings / Restrictions There are no access settings or restrictions for these reports at this initial design stage.
Design Requirements
The user can drill down until reaching the desired level. The entities within Indian and Northern
CIDM # XXX
06:28:00 PM
Page 44 of 113
Affair Canada (INAC) follows the hierarchical structure starting with regions (codes starting with E such as E900 BC Region) and then responsibility centres (RCMs) (codes starting with A such as A910 Manager, Assets & Planning). See below for an illustration.
CIDM # XXX
06:28:00 PM
Page 45 of 113
Header and Footer Information Header: centre - INAC Logo, name of the report Footer: left - date; centre - page number; left - time of report generation
CIDM # XXX
06:28:00 PM
Page 46 of 113
Report Samples
Footnotes None
Data Requirements
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Region (D) Definition All major INAC reporting regions in Canada There are five regions listed: (i) E900 BC Region (ii) EB00 Executive Direction (iii) EK00 Aboriginal Economic Development (iv) EM00 Chief Financial Officer Regional codes start with E e.g. EB00 Executive Direction Source of Data 1.3 FSR Mgr - DList
CIDM # XXX
06:28:00 PM
Page 47 of 113
User selected by drill-down functionality 2 RCM (E) Organizational unit within INAC based on the IFS hierarchy that is responsible for the transaction There are about 1500 RCMs RCM codes start with A e.g. AB00 Ministers Office 3 Vote (D) Vote is defined as the parent2 in the DList There are five main categories: Vote 1 Salary and O&M Vote 5 Capital Vote 10 Grants & Contributions Vote 20 Federal Interlocutor Operating Exp. Vote 25 Federal Interlocutor G&C 4 Authority Code (D) Authority is defined as the first three characters of the Auth-BA DList Defined as the last five characters of the Auth-BA DList Defined as a hierarchical view of the organizations special projects tracked in Oasis. The hierarchy consists of 2 levels. There are over 6500 project codes. Defined as the amount of the transfers of funds in or out depending on the value in the Budget Transfer Type field. Based on all input sheets rows from Anticipated Tsfs Expressed as a currency with two 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr - EList
Budget Activity Code (D)
1.3 FSR Mgr Auth-BA DList
Project Code (D)
1.3 FSR Mgr - DList
Amount (M)
Summation of all RCM FSRs anticipated transfer data, input by User, for the RCMs being analyzed.
CIDM # XXX
06:28:00 PM
Page 48 of 113
decimal places 8 Budget Transfer Type (E) Defined as a type of budget transfer, with possible values being: Budget transfer in; Budget transfer out; Vote Transfer in; and Vote Transfer out This field enables add descriptive text attached to the anticipated transfer transaction. This field adds a contact name to the transaction for further reference This field indicates from where the transfer will originate. This field indicates to where the transfer will be sent. This field enables the transaction to be submitted once the submit button has been pressed. 1.3 FRS Mgr - EList
Explanation
RCM FSRs
10
HQ Contact
RCM FSRs
11
Reg/Sec From
RCM FSRs
12
Reg/Sec To
RCM FSRs
13
Submit
RCM FSRs

IFS datamart
Optional Requirements None Graph/Chart Information None Drill down Options Right-clicking anywhere on the report yields a menu with three items: 1) Drill down; 2) Drill up; and 3) Go to. However, none of these selections seems to be active.
CIDM # XXX
06:28:00 PM
Page 49 of 113
Drill through Options None Time Frame / # of Years reported There are no date parameters in this version. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None Data Requirements None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 50 of 113
Sort Order
1 2 3 4 5 7 Region RCM Vote
Column

N/A A A A A A Y Y Y Y N N
Subtotal (Y or N)
Authority Code Budget Activity Code Project Code
Show users how to bookmark Cognos reports in Internet Explorer Show users how to drill-down to select their RCM Show users how to read and interpret report Show users how to print, e-mail and save report
Priority
Scope Decision
Included in Design
Notes / Issues
Accomplished via a URL link sent in body of an e-mail Locating an RCM and generating a report is simple and would not require much if any training Managers using these reports should already have the training required. Users can easily be shown through e-mailed instructions with screen shots.
Low
Included in scope
No
Low
Included in scope
Yes
Medium Medium
Included in scope
CIDM # XXX
06:28:00 PM
Page 51 of 113
Although only the Antic Tsfs worksheet data input is integrated into this BI Anticipated Transfer report, all worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations in order for other BI reports to reflect the correct data. Fresh datamarts must repopulate these BI reports at regular intervals to show current information.
BI Reports are integrated with EP/FSR Call Package reports, which require data input
High
Included
Yes
IFS datamarts
High
Included
Yes
Other Requirements Not sure what to put into section Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 52 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
Totals Summary at bottom Grand totals Column 1: Region Sub totals Column 2: RCM Sub totals Column 3: Vote Sub totals Column 4: Authority Code Sub totals Footnotes None Other Requirements None Scheduling These reports can only be viewed once the respective RC Managers have verified and entered in all data for Anticipated Transfers into their FSRs. Therefore, this activity is a precedent to the user being able to view the Anticipated Transfers BI report. Along with the Anticipated Transfers, RCM Plan, Anticipated Expenditures and Variance Explanation worksheets must be filled out by the RC Manager. Exception Report Sample N/A
BIR-3 Anticipated Expenditures

Purpose of the Report This report will be used to indicate the anticipated expenditure to the end of the period along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning
CIDM # XXX
06:28:00 PM
Page 53 of 113
module in order for the BI Report Anticipated Expenditures to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this report. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Reports. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Report Studio Access Settings / Restrictions There are no access settings or restrictions for these reports at this initial design stage.
Design Requirements
CIDM # XXX
06:28:00 PM
Page 54 of 113
CIDM # XXX
06:28:00 PM
Page 55 of 113
Header and Footer Information Header: centre - INAC Logo, name of the report Footer: left - date; centre - page number; left - time of report generation Report Samples
CIDM # XXX
06:28:00 PM
Page 56 of 113
Footnotes None
Data Requirements
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Region (D) Definition All major INAC reporting regions in Canada There are five regions listed: (i) E900 BC Region (ii) EB00 Executive Direction (iii) EK00 Aboriginal Economic Development (iv) EM00 Chief Financial Officer Regional codes start with E e.g. EB00 Executive Direction User selected by drill-down functionality 2 RCM (E) Organizational unit within INAC based on the IFS hierarchy that is responsible for the transaction There are about 1500 RCMs RCM codes start with A e.g. AB00 Ministers Office 3 Vote (D) Vote is defined as the parent2 in the DList There are five main categories: Vote 1 Salary and O&M Vote 5 Capital Vote 10 Grants & Contributions Vote 20 Federal Interlocutor Operating Exp. Vote 25 Federal Interlocutor 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr - EList Source of Data 1.3 FSR Mgr - DList
CIDM # XXX
06:28:00 PM
Page 57 of 113
G&C 4 Authority Code (D) Authority is defined as the first three characters of the Auth-BA DList Defined as the last five characters of the Auth-BA DList Defined as part of the line object, in the DList Defined as a hierarchical view of the organizations special projects tracked in Oasis and part of the Chart of Accounts. The hierarchy consists of 2 levels. There are over 6500 project codes. Defined as the amount of the anticipated expenditure. The sign of this amount will depend on the value in the Anticipated Exp Type field i.e. increase or decrease. Based on all input sheets rows from Anticipated Expenditures Expressed as a currency with two decimal places 9 Anticipated Exp Type (E) Defined as a type of anticipated expenditure, with possible values being: Increase Decrease This field enables add descriptive text attached to the anticipated expenditure transaction. This field enables the transaction to be submitted once the submit button has been pressed. 1.3 FRS Mgr - EList 1.3 FSR Mgr Auth-BA DList
Budget Activity Code (D)
1.3 FSR Mgr Auth-BA DList
Planning Object (D)
1.3 FSR Mgr - DList
Project Code (D)
1.3 FSR Mgr - DList
Amount (M)
Summation of all RCM FSRs anticipated expenditure data, input by User, for the RCMs being analyzed.
10
Explanation
RCM FSRs
11
Submit
RCM FSRs
CIDM # XXX
06:28:00 PM
Page 58 of 113

IFS datamart
Optional Requirements None Graph/Chart Information None Drill down Options Right-clicking anywhere on the report yields a menu with three items: 1) Drill down; 2) Drill up; and 3) Go to. However, none of these selections seems to be active. Drill through Options None Time Frame / # of Years reported There are no date parameters in this version. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None Data Requirements None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 59 of 113
Sort Order
1 2 3 4 5 6 7 Region RCM Vote Authority Code Budget Activity Code Planning Object Project Code
Column

N/A A A A A A A Y Y Y Y N N N
Subtotal (Y or N)
CIDM # XXX
06:28:00 PM
Page 60 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
Low
Included in scope
Yes
Medium Medium
Included in scope
Priority
High
Scope Decision
Included
Included in Design
Yes
Notes / Issues
Although only the Antic Tsfs worksheet data input is integrated into this BI Anticipated Transfer report, all worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures
CIDM # XXX
06:28:00 PM
Page 61 of 113
IFS datamarts
High
Included
Yes
and Variance Explanations in order for other BI reports to reflect the correct data. Fresh datamarts must repopulate these BI reports at regular intervals to show current information.
Totals Summary at bottom Grand totals Column 1: Region Sub totals Column 2: RCM Sub totals Column 3: Vote Sub totals Column 4: Authority Code Sub totals Footnotes None Other Requirements None Scheduling These reports can only be viewed once the respective RC Managers have verified and entered in all data for Anticipated Expenditures into their FSRs. Therefore, this activity is a precedent to the user being able to view the Anticipated Expenditure BI report. Along with the Anticipated Expenditures, RCM Plan, Anticipated Transfers and Variance Explanation worksheets must be filled out by the RC Manager.
CIDM # XXX
06:28:00 PM
Page 62 of 113
Exception Report Sample N/A
BIR-4 Financial Summary

Purpose of the Report This report will be used to summarize financial information from the Call Package as well as managerial Financial Status Reports (FSR) inputs from RCM Plan, Anticipated Transfers, Anticipated Expenditure and Variance Explanation. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Report - Financial Summary to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this report. Audience Requirements The intended audience are the RC Managers, who will need to check that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Reports. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Report Studio Access Settings / Restrictions There are no access settings or restrictions for these reports at this initial design stage.
CIDM # XXX
06:28:00 PM
Page 63 of 113
Design Requirements
CIDM # XXX
06:28:00 PM
Page 64 of 113
Footnotes None
CIDM # XXX
06:28:00 PM
Page 65 of 113
Data Requirements
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Region (D) Definition All major INAC reporting regions in Canada There are five regions listed: (i) E900 BC Region (ii) EB00 Executive Direction (iii) EK00 Aboriginal Economic Development (iv) EM00 Chief Financial Officer Regional codes start with E e.g. EB00 Executive Direction User selected by drill-down functionality 2 RCM (E) Organizational unit within INAC based on the IFS hierarchy that is responsible for the transaction There are about 1500 RCMs RCM codes start with A e.g. AB00 Ministers Office 3 Vote (D) Vote is defined as the parent2 in the DList There are five main categories: Vote 1 Salary and O&M Vote 5 Capital Vote 10 Grants & Contributions Vote 20 Federal Interlocutor Operating Exp. Vote 25 Federal Interlocutor G&C 4 Resource Category (D) Resource Category is defined as the parent to Auth in the DList 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr - EList Source of Data 1.3 FSR Mgr - DList
CIDM # XXX
06:28:00 PM
Page 66 of 113
Examples of Resource Categories are: NS1 - INAC NON SALARY SA1 INAC SALARY NS2 - OFI NON SALARY 5 Auth-BA (D) Auth-BA hierarchy in the DList is based on the IFS hierarchy and the Chart of Accounts Defined as the initial funds available to fund operations for the current fiscal year Imported from IFS Expressed as a currency with two decimal places 7 Antic Transfers (M) Defined as transfers of funds in or out necessary to explain all or part of a budget variance Based on all input sheets rows from 02 Anticipated Tsfs Expressed as a currency with two decimal places 8 Revised Budget (C) = Initial Budget + Antic Transfers Defined as the budget after factoring in anticipated transfers. Expressed as a currency with two decimal places 9 Actual (M) Payments made under Section 33 of the Financial Administration Act (FAA), up to the most recent completed period Imported from IFS Expressed as a currency with two decimal places 1.3 FSR Mgr Summation of all RCM FSRs Actual data, for the RCMs being analyzed Summation of all RCM FSRs Revised Budget data, for the RCMs being analyzed Summation of all RCM FSRs anticipated transfer data, input by User, for the RCMs being analyzed. 1.3 FSR Mgr DList
Budget (M)
1.3 FSR Mgr Summation of all RCM FSRs initial budget data, for the RCMs being analyzed.
CIDM # XXX
06:28:00 PM
Page 67 of 113
10
Obligation (M)
Obligations made under Section 32 of the FAA Defined as expenditures not having yet occurred but expressed as a likely expenditure Imported from IFS Expressed as a currency with two decimal places
1.3 FSR Mgr - Summation of all RCM FSRs Obligations data, for the RCMs being analyzed
11
Commitment (M)
Defined as an expenditure not having yet occurred but is committed to being expended vis-vis a purchase order Defined as an expenditure not having yet occurred but may occur vis--vis a purchase requisition Imported from IFS Expressed as a currency with decimal places
1.3 FSR Mgr - Summation of all RCM FSRs Commitments data, for the RCMs being analyzed 1.3 FSR Mgr Summation of all RCM FSRs Soft Commit data, for the RCMs being analyzed
12
Soft Commit (M)
13
Free Balance (C)
= Initial Budget (Actuals + Encumbrances)
Summation of all RCM FSRs Free Balance data, for the RCMs being analyzed Summation of all RCM FSRs Antic Exp data, for the RCMs being analyzed
14
Antic Exp (M)
Defined as expenditures anticipated to the year end, but not part of encumbrances Based on all input sheets rows from Anticipated Exp Expressed as a currency with two decimal places
15
Total Forecast (C)
= Actual + Encumbrances + Antic Exp Defined as the expected total expenditures for the fiscal year
Summation of all RCM FSRs Total Forecast data, for the RCMs being analyzed
CIDM # XXX
06:28:00 PM
Page 68 of 113
Expressed as a currency with two decimal places 16 Revised Variance (C) = Revised Budget Total Forecast Defined as a pressure (deficit) or lapse (surplus) if revised variance is not zero Expressed as a currency with two decimal places 17 Variance Expl (C) Defined as the management of a budget surplus (lapse) or budget deficit (pressure) from the Revised Variance input sheets Expressed as a currency with two decimal places 18 Unexplained Var (C) = Revised Variance - Variance Expl Defined as the variance that is yet unexplained after considering the revised variance explanations from the previous column Variances that are unexplained will be managed at the regional level Expressed as a currency with two decimal places Summation of all RCMs Unexplained Var data, for the RCMs being analyzed Summation of all RCMs Revised Var Exp data, for the RCMs being analyzed Summation of all RCM FSRs Revised Variance data, for the RCMs being analyzed

IFS datamart
Optional Requirements None
CIDM # XXX
06:28:00 PM
Page 69 of 113
Graph/Chart Information None Drill down Options Right-clicking anywhere on the report yields a menu with three items: 1) Drill down; 2) Drill up; and 3) Go to. However, none of these selections seems to be active. Drill through Options None Time Frame / # of Years reported There are no date parameters in this version. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None Data Requirements None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 70 of 113
Sort Order
1 2 3 4 5 Region RCM Vote Resource Category Auth-BA
Column

N/A A A A A Y Y Y Y N
Subtotal (Y or N)
Show users how to bookmark Cognos reports in Internet Explorer Show users how to drill-down to select their RCM Show users how to read and interpret report
Priority
Scope Decision
Included in Design
Notes / Issues
Accomplished via a URL link sent in body of an e-mail Locating an RCM and generating a report is simple and would not require much if any training Managers using these reports should already have the training required.
Low
Included in scope
No
Low
Included in scope
Yes
Medium
Included in scope
No
CIDM # XXX
06:28:00 PM
Page 71 of 113
Show users how to print, e-mail and save report
Medium
Built-in features in Cognos Report Studio
Users can easily be shown through e-mailed instructions with screen shots.
Priority
Scope Decision
Included in Design
Notes / Issues
All worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations in order for the Financial Summary to reflect the correct data. Fresh datamarts must repopulate these BI reports at regular intervals to show current information.
High
Included
Yes
IFS datamarts
High
Included
Yes
06:28:00 PM
Page 72 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
Totals Summary at bottom Grand totals Column 1: Region Sub totals Column 2: RCM Sub totals Column 3: Vote Sub totals Column 4: Resource Category Sub totals Footnotes None Other Requirements None Scheduling These reports can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the Financial Summary BI report. Exception Report Sample N/A
CIDM # XXX
06:28:00 PM
Page 73 of 113
BIR-5 Variance Explanation

Purpose of the Report This report will be used to indicate the amount and type of the variance along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Report Variance Explanation to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this report. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Reports. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Report Studio Access Settings / Restrictions There are no access settings or restrictions for these reports at this initial design stage.
Design Requirements
CIDM # XXX
06:28:00 PM
Page 74 of 113
CIDM # XXX
06:28:00 PM
Page 75 of 113
Footnotes None
CIDM # XXX
06:28:00 PM
Page 76 of 113
Data Requirements
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Region (D) Definition All major INAC reporting regions in Canada There are five regions listed: (i) E900 BC Region (ii) EB00 Executive Direction (iii) EK00 Aboriginal Economic Development (iv) EM00 Chief Financial Officer Regional codes start with E e.g. EB00 Executive Direction User selected by drill-down functionality 2 RCM (E) Organizational unit within INAC based on the IFS hierarchy that is responsible for the transaction There are about 1500 RCMs RCM codes start with A e.g. AB00 Ministers Office 3 Vote (D) Vote is defined as the parent2 in the DList There are five main categories: Vote 1 Salary and O&M Vote 5 Capital Vote 10 Grants & Contributions Vote 20 Federal Interlocutor Operating Exp. Vote 25 Federal Interlocutor G&C 4 Authority Code (D) Authority is defined as the first three characters of the Auth-BA 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr Auth-BA DList 1.3 FSR Mgr - EList Source of Data 1.3 FSR Mgr - DList
CIDM # XXX
06:28:00 PM
Page 77 of 113
DList 5 Budget Activity Code (D) Defined as the last five characters of the Auth-BA DList Defined as a hierarchical view of the organizations special projects tracked in Oasis and part of the Chart of Accounts. The hierarchy consists of 2 levels. There are over 6500 project codes. Defined as the amount of the variance. The sign of this amount will depend on the value in the Variance Type field i.e. Declared Pressure or Declared Surplus. Based on all input sheets rows from Variance Explanation worksheets Expressed as a currency with two decimal places 9 Variance Type (E) Defined as a type of variances, with possible values being: Declared Pressure Declared Surplus This field adds descriptive text attached to the variance. This field adds descriptive text attached to the variance. This field attaches a contact name to the variance This field attaches a sector to which this variance is addressed This field attaches a branch to which this variance is addressed This field enables the transaction to be submitted once the submit 1.3 FRS Mgr - EList 1.3 FSR Mgr Auth-BA DList
Project Code (D)
1.3 FSR Mgr - DList
Amount (M)
Summation of all RCM FSRs Variance Explanation data, input by User, for the RCMs being analyzed.
10
Variance ID
RCM FSRs
11
Explanation
RCM FSRs
12
Sector/Corp Contact
RCM FSRs
13
Sector to Address
RCM FSRs
14
Branch to Address
RCM FSRs
15
Submit
RCM FSRs
CIDM # XXX
06:28:00 PM
Page 78 of 113
button has been pressed.

IFS datamart
Optional Requirements None Graph/Chart Information None Drill down Options Right-clicking anywhere on the report yields a menu with three items: 1) Drill down; 2) Drill up; and 3) Go to. However, none of these selections seems to be active. Drill through Options None Time Frame / # of Years reported There are no date parameters in this version. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None Data Requirements None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 79 of 113
Sort Order
1 2 3 4 5 6 Region RCM Vote Authority Code Budget Activity Code Project Code
Column

N/A A A A A A Y Y Y Y N N
Subtotal (Y or N)
CIDM # XXX
06:28:00 PM
Page 80 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
Low
Included in scope
Yes
Medium Medium
Included in scope
Priority
Scope Decision
Included in Design
Notes / Issues
All worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations in order for other BI reports to reflect the correct data.
High
Included
Yes
CIDM # XXX
06:28:00 PM
Page 81 of 113
IFS datamarts
High
Included
Yes
Fresh datamarts must repopulate these BI reports at regular intervals to show current information.
Totals Summary at bottom Grand totals Column 1: Region Sub totals Column 2: RCM Sub totals Column 3: Vote Sub totals Column 4: Authority Code Sub totals Footnotes None Other Requirements None Scheduling These reports can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the Financial Summary BI report. Exception Report Sample N/A
CIDM # XXX
06:28:00 PM
Page 82 of 113
Appendix D BI Cubes
General Requirements and Benefits
The requirements for the Cognos BI Cubes will continue to build on existing tools and will achieve the following: e) Provide an alternative to black books and spreadsheets for managers and directors to manage and track their planned (i.e., not recorded in OASIS) financial activities on a daily basis; f) To support the monthly gathering of forecasting related information from each responsibility centre across the organization; g) To create an integrated and streamlined process that leverages technology to provide management with reliable, accurate and timely information to support strategic in-year resource decisions; and h) Will provide managers with key financial and operational information in support of the accountability for the resources entrusted to them.
Overview
The use of BI Cubes is part of the official framework for reporting on financial status and resource utilization to the departmental Financial Management Committee (FMC). They are part of the suit of BI Cognos tools supporting the Financial Status Reporting (FSR) process, which is currently designed to obtain and communicate financial forecasting information from across the department to the finance group for the purposes of: g) Confirming the finances and the financial situation of each RCM; h) Forecasting spending to the end of the year; i) Identifying funding pressures; j) Identifying surplus funds available for transfer to other priorities; k) Identifying needs to transfer funds between votes; and l) Identifying cash management requests. The process is initiated by a Call Package sent out by finance to each RCM beginning in June of each year. The purpose of the Call Package is to provide the framework for completing the FSR, with the first reporting period starting in September. The package includes financial information generated from the Integrated Financials System (IFS) datamart using Cognos Query Studio tools and provides each recipient with their information on their current financial status i.e., actual expenditures, budget, commitments, obligations and free balance. As each Manager or Director completes their FSR package i.e. submits their final numbers to the regional manager these users will utilize BI Cubes to check for accuracy of the numbers in the Call Package before the results are rolled up and reviewed by the next level of the RC hierarchy. There are five Cubes comprising Cognos Query Studio: RCM Plan; Anticipated Transfers; Anticipated Expenditures; Financial Summary; and Variance Explanation. The user is able to drill down to subsequent levels of dimensions and measures to the left of the Data section by using the adjacent plus signs, which can then be dragged to the appropriate
06:28:00 PM
Page 83 of 113
sections. There are two categories of data Dimensions and Measures. Below is an illustration.
Dimensions
Data Section
Measures
A User adds either a Dimension or Measure by dragging it across to the Data section. Below is an illustration of dragging across the Authorities dimension to replace the default Activities dimension in the Row Headings section. Measures are only dragged onto the Data sections.
Column Headings section
Row Headings section before Dragging the Dimension All Authorities
Data section
CIDM # XXX
06:28:00 PM
Page 84 of 113
BIC-1 RCM Plan

Purpose of the Cube This RCM Plan Cube will be used to enable RC Managers to validate information in the Call Packages sent to them by the CFO Office. Through manipulating items in a cube such as Budget, Antic Transfers, Revised Budget, Current Plan, Actuals, Obligations, Commitments, Soft Commitments, Remaining Balance, Anticipated Expenditures, Total Forecast and Plan - Forecast along with identifying fields such as the Region and RCM RC Managers will able to create their own reports and in this process, answer their unique reporting needs. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Cube RCM Plan to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this Cube. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate by creating their own cube reports. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Cubes. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Analysis Studio Access Settings / Restrictions There are no access settings or restrictions for this BI Cube at this initial design stage.
CIDM # XXX
06:28:00 PM
Page 85 of 113
Design Requirements
The general design the cube follows standard Cognos Analysis Studio cube functionality. Header and Footer Information Header: None Footer: None Cube Sample
Footnotes None Parameters Dimensions 1. The RCM Plan BI Cube should provide data at the lowest RC level in the organization and should map to the RCM hierarchy (Manager, Director, DG, ADM, Department) used for managing the FSR process. 2. For each RC assigned to the reviewer, the cube should be able to: a. Display data summarized by the following dimensions listed and nested on the rows: i. Authority hierarchy (Vote, Exp Type, Authority) ii. RCMs 1. Users should be able to view their data for any specific RCM or RCM rollup level by either: a. Budget activity b. Authority c. Project d. Combination of Budget activity Authority Project iii. Planning Object
CIDM # XXX
06:28:00 PM
Page 86 of 113
Measures 1. The User should be able to display the following measures in the columns in the specified order below:
Item 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Authority (D) Definition Authority hierarchy (VoteExp Type Authority) RCM hierarchy (Region RCM) Activity hierarchy ( Source of Data IFS 1.3
RCM (D)
IFS 1.3
3 3
Activities (D) Planning Object Initial RCM Budget or Current Budget (D) Anticipated Transfers (E) Revised Budget Plan Actual Obligation Commitment Soft Commitments Remain Balance Anticipated Expenditures (E) Total Forecast Plan - Forecast
1 2 3 4 5 6 7 8 9 10 11 12
EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR
Cube Page Contents None Potential Data Sources (Data)

IFS datamart
CIDM # XXX
06:28:00 PM
Page 87 of 113
Optional Requirements All optional requirements follow the standard options as available with Cognos Analysis Studio. Graph/Chart Information Graph/chart information follow the standard Cognos Analysis Studio functionality. Drill down Options Drill-down options follow standard Cognos Analysis Studio functionality. Drill through Options Drill-down options follow standard Cognos Analysis Studio Functionality. Time Frame / # of Years Reported Time frames are selected by choosing the appropriate dimensions of fiscal year, periods and quarters. Data refresh Frequency Data is refreshed when a new datamart is available and FSRs have been validated and updated from the RC Managers. New Data elements needed to be brought into the Data Architecture None
Data Requirements
None since there is no data input required by user. Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
Content and Business Rules None The table below details the information content included in this Cube.
CIDM # XXX
06:28:00 PM
Page 88 of 113
CIDM # XXX
06:28:00 PM
Page 89 of 113
Filtering Options Filtering options are standard Cognos Analysis Studio functionality. Sorting Options Sorting options are standard Cognos Analysis Studio functionality. Reporting Requirements None Training Requirements
Show users how to bookmark Cognos Cubes in Internet Explorer Show users how to create their own cubes based on their individual analytical needs Show users how to read and interpret a Cube Show users how to print, e-mail and save Cube
Priority
Scope Decision
Included in Design
Notes / Issues
Accomplished via a URL link sent in body of an e-mail
Low
Included in scope
No
High
Included in scope
Yes
Generating a Cube can be counter-intuitive and would necessitate medium-effort training Managers using these Cubes should already have the training required. Users can easily be shown through e-mailed instructions with screen shots.
High Medium
Included in scope
No Built-in features in Cognos Analysis Studio
Operational Requirements None Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 90 of 113
BI Cubes are integrated with EP/FSR Call Package reports, which require data input IFS datamarts
Priority
Scope Decision
Included in Design
Notes / Issues
All worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations in order for BI Cubes to reflect the correct data. BI Cubes must be linked to fresh datamarts at regular intervals to show current intervals.
High
Included
Yes
High
Included
Yes
Other Requirements
None Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
Totals Totals are managed by the User through standard Cognos Analysis Studio. Footnotes None Scheduling These Cubes can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the RCM Plan BI Cube.
CIDM # XXX
06:28:00 PM
Page 91 of 113
Exception Cube Sample N/A
BIC-2 Anticipated Transfers

Purpose of the Cube This Cube will be used to indicate the type of funds transfer Vote or Budget transfers in or out of the region or sector along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Cube Anticipated Transfers to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this Cube. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Cubes. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Analysis Studio Access Settings / Restrictions There are no access settings or restrictions for these Cubes at this initial design stage.
CIDM # XXX
06:28:00 PM
Page 92 of 113
Design Requirements
The design the cube follows standard Cognos Analysis Studio cube functionality. Header and Footer Information Header: None Footer: None Cube Sample
Footnotes None Dimensions 1. For each RC assigned to the reviewer, the cube should be able to: a. Display data summarized by the following dimensions listed and nested on the rows: i. Authority hierarchy (Vote, Exp Type, Authority) ii. RCMs 1. Users should be able to view their data for any specific RCM or RCM rollup level by either: a. Budget activity b. Authority c. Project d. Combination of Budget activity Authority Project iii. Activities iv. Planning Object v. Budget Transfer Type vi. Region/Sector To vii. Region/Sector From viii. Submit Measures 1. The User should be able to display the following measures in the columns in the specified
CIDM # XXX
06:28:00 PM
Page 93 of 113
order below:
Col. 1 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Amount Definition Source of Data EP/FSR

IFS datamart
CIDM # XXX
06:28:00 PM
Page 94 of 113
Data Requirements
Content and Business Rules 1. The total for all intra-region budget transfers should net to zero at the region level. 2. Each budget transfer should balance to zero 3. The total for all inter-region budget transfers should net to zero at the departmental level Filtering Options Filtering options are standard Cognos Analysis Studio functionality. Sorting Options Sorting options are standard Cognos Analysis Studio functionality. Reporting Requirements None Training Requirements
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
High
Included in scope
Yes
High Medium
Included in scope
CIDM # XXX
06:28:00 PM
Page 95 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
High
Included
Yes
High
Included
Yes
Other Requirements
CIDM # XXX
06:28:00 PM
Page 96 of 113
Totals Totals are managed by the User through standard Cognos Analysis Studio. Footnotes None Other Requirements None Scheduling These Cubes can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the Anticipated Transfers BI Cube. Exception Cube Sample N/A
BIC-3 Anticipated Expenditures

Purpose of the Cube This Cube will be used to indicate the anticipated expenditure to the end of the period along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Cube Anticipated Expenditures to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this Cube. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements
CIDM # XXX
06:28:00 PM
Page 97 of 113
are being gathered and incorporated into the design of the BI Cubes. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Analysis Studio Access Settings / Restrictions There are no access settings or restrictions for these Cubes at this initial design stage.
Design Requirements
Footnotes None Dimensions 1. For each RC assigned to the reviewer, the cube should be able to: a. Display data summarized by the following dimensions listed and nested on the rows: i. Authority hierarchy (Vote, Exp Type, Authority) ii. RCMs 1. Users should be able to view their data for any specific RCM or RCM rollup level by either: a. Budget activity b. Authority c. Project d. Combination of Budget activity Authority Project
06:28:00 PM
Page 98 of 113
iii. Activities iv. Planning Object Measures 1. The User should be able to display the following measures in the columns in the specified order below :

IFS datamart
CIDM # XXX
06:28:00 PM
Page 99 of 113
Data Requirements
Content and Business Rules None Filtering Options Filtering options are standard Cognos Analysis Studio functionality. Sorting Options Sorting options are standard Cognos Analysis Studio functionality. Reporting Requirements None Training Requirements
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
High
Included in scope
Yes
High Medium
Included in scope
CIDM # XXX
06:28:00 PM
Page 100 of 113
Priority
Scope Decision
Included in Design
Notes / Issues
High
Included
Yes
High
Included
Yes
Other Requirements
Not sure what to put into section Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope Notes/Issues: Additional notes and comments
CIDM # XXX
06:28:00 PM
Page 101 of 113
Totals Totals are managed by the User through standard Cognos Analysis Studio. Footnotes None Other Requirements None Scheduling These Cubes can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the Anticipated Transfers BI Cube. Exception Cube Sample N/A
BIC-4 Financial Summary

Purpose of the Cube This Cube will be used to summarize financial information from the Call Package as well as managerial Financial Status Reports (FSR) inputs from RCM Plan, Anticipated Transfers, Anticipated Expenditure and Variance Explanation. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Cube - Financial Summary to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this Cube.
Audience Requirements The intended audience are the RC Managers, who will need to check that their financial data from the Call Package and FSR inputs are accurate.
CIDM # XXX
06:28:00 PM
Page 102 of 113
Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Cubes. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Analysis Studio Access Settings / Restrictions There are no access settings or restrictions for these Cubes at this initial design stage.
Design Requirements
Footnotes None Dimensions 1. For each RC assigned to the reviewer, the cube should be able to: a. Display data summarized by the following dimensions listed and nested on the rows: i. Authority hierarchy (Vote, Exp Type, Authority) ii. RCMs 1. Users should be able to view their data for any specific RCM or RCM rollup level by either:
CIDM # XXX
06:28:00 PM
Page 103 of 113
a. b. c. d. iii. Activities
Budget activity Authority Project Combination of Budget activity Authority Project
Measures 1. The User should be able to display the following measures in the columns in the specified order below:
Col. 1 2 3 4 5 6 7 8 9 10 11 12 13 Measure (M) / Dimension (D) / Entity (E) / Calculated (C) Initial RCM Budget or Current Budget Anticipated Transfers Revised Budget Actual Obligation Commitment Soft Commitments Free Balance Anticipated Expenditures Total Forecast Revised Variance Variance Expl Unexplained Var Definition Source of Data EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR EP/FSR

IFS datamart
CIDM # XXX
06:28:00 PM
Page 104 of 113
Data Requirements
Content and Business Rules None Filtering Options Filtering options are standard Cognos Analysis Studio functionality.
CIDM # XXX
06:28:00 PM
Page 105 of 113
Sorting Options Sorting options are standard Cognos Analysis Studio functionality. Reporting Requirements None Training Requirements
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
High
Included in scope
Yes
High Medium
Included in scope
BI Cubes are integrated with EP/FSR Call Package reports, which require
Priority
High
Scope Decision
Included
Included in Design
Yes
Notes / Issues
All worksheets must be completed i.e. RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations
CIDM # XXX
06:28:00 PM
Page 106 of 113
data input
IFS datamarts
High
Included
Yes
in order for BI Cubes to reflect the correct data. BI Cubes must be linked to fresh datamarts at regular intervals to show current intervals.
Other Requirements
Totals Totals are managed by the User through standard Cognos Analysis Studio. Footnotes None Other Requirements None Scheduling These Cubes can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the RCM BI Cubes. Exception Cube Sample N/A
CIDM # XXX
06:28:00 PM
Page 107 of 113
BIC-5 Variance Explanation

Purpose of the Cube This Cube will be used to indicate the amount and type of the variance along with identifying fields such as the Region and RCM. Assumptions It is assumed that that all necessary FSR inputs have been made in the Enterprise Planning module in order for the BI Cube Variance Explanation to reflect this information and that all Call Packages have been sent to the respective RC Managers. Requirements Owner Sherri Elrick of the EDW Directorate is the owner of this Cube. Audience Requirements The intended audience are the RC Managers, who will need to verify that their financial data from the Call Package and FSR inputs are accurate. Approach Through a series of workshops and one-on-one meetings with Sherri Elrick, user requirements are being gathered and incorporated into the design of the BI Cubes. These meetings and workshops will be facilitated to illicit user requirements and needs through directed questions and concise meeting objectives geared towards meeting this end. Cognos Tool Used For Development IBM Cognos Analysis Studio Access Settings / Restrictions There are no access settings or restrictions for these Cubes at this initial design stage.
Design Requirements
The design the cube follows standard Cognos Analysis Studio cube functionality. Header and Footer Information Header: None Footer: None
CIDM # XXX
06:28:00 PM
Page 108 of 113
Cube Sample
Footnotes None Dimensions 1. For each RC assigned to the reviewer, the cube should be able to: a. Display data summarized by the following dimensions listed and nested on the rows: i. Authority hierarchy (Vote, Exp Type, Authority) ii. RCMs 1. Users should be able to view their data for any specific RCM or RCM rollup level by either: a. Budget activity b. Authority c. Project d. Combination of Budget activity Authority Project iii. Activities iv. Variance Type v. Sector to Address vi. Submit Measures 1. The User should be able to display the following measures in the columns in the specified order below:
CIDM # XXX
06:28:00 PM
Page 109 of 113

IFS datamart
Data Requirements
CIDM # XXX
06:28:00 PM
Page 110 of 113
Content and Business Rules None The table below details the information content included in this Cube.
Filtering Options Filtering options are standard Cognos Analysis Studio functionality. Sorting Options Sorting options are standard Cognos Analysis Studio functionality. Reporting Requirements None Training Requirements
Priority
Scope Decision
Included in Design
Notes / Issues
Low
Included in scope
No
High
Included in scope
Yes
High Medium
Included in scope
Operational Requirements None Requirement Description: A clear and concise description of this requirement item. Priority: The priority of the requirement. This can be numerical (1, 2, 3, etc.) or non-numerical (Low, Medium, High, etc.) Scope Decision: is it included in scope
CIDM # XXX
06:28:00 PM
Page 111 of 113
Notes/Issues: Additional notes and comments

Priority
Scope Decision
Included in Design
Notes / Issues
High
Included
Yes
High
Included
Yes
Other Requirements
Totals Totals are managed by the User through standard Cognos Analysis Studio. Footnotes None
06:28:00 PM
Page 112 of 113
Other Requirements None Scheduling These Cubes can only be viewed once the respective RC Managers have verified and entered in all data for the RCM Plan, Anticipated Transfers, Anticipated Expenditures and Variance Explanations into their FSRs. Therefore, these activities are a precedent to the user being able to view the RCM BI Cubes. Exception Cube Sample N/A
CIDM # XXX
06:28:00 PM
Page 113 of 113

Sample of Kent&#39;s Work

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Sample of Kent&#39;s Work

Încărcat de

Drepturi de autor:

Formate disponibile

1

Indian and Northern Affairs Canada

Financial Status Reporting Manager Model

Release 1.0 REQ

Draft Version # 0.1 CIDM # XXX March 25, 2009

Indian and Northern Affairs Canada (INAC)

INAC FSR Business Requirements

Document Change Control

Last updated: 13/04/2011

INAC FSR Business Requirements

Table of Contents Introduction.............................................................................................8

Appendix A Use Cases.......................................................................13

Last updated: 13/04/2011

INAC FSR Business Requirements

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

Appendix A Use Cases

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

1) RC Managers must be trained on how to calculate their RCM Plans.

Post Conditions Assumptions Business Rules

Last updated: 13/04/2011

INAC FSR Business Requirements

this project and thus is the responsibility of the Department.

Post Conditions Assumptions Business Rules

Last updated: 13/04/2011

INAC FSR Business Requirements

Post Conditions Assumptions

Last updated: 13/04/2011

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

Last updated: 13/04/2011

INAC FSR Business Requirements

EP 1.2 RCM Plan

Business and Content Rules

Column Authority Description Budget Activity Description

Column Calc Data (Text)

Budget Antic Transfers

Data (Currency) Data (Currency)

Sourcing Option IFS

Last updated: 13/04/2011

INAC FSR Business Requirements

all or part of a budget variance

Revised Budget Plan

Budget + Antic Tsfs (Currency) Data (Currency)

Plan (Actual + Obligation + Commitment + Soft Commit)

Data (Currency) Actuals + Obligations + Commitments + Soft

Summation of Anticipated Exp from 3 Anticipated Exp Calculated

Last updated: 13/04/2011

INAC FSR Business Requirements

Sample of Kent's Work

Sample of Kent's Work