The Bureau of the Dubai EXPO 2020

ERP Program
Statement of Need
17 March 2016
Version 1.0

Version 1.0

Table of Contents
1. Purpose ................................................................................................................................. 3
1.1. Context ......................................................................................................................................................... 3
1.2. Objective ...................................................................................................................................................... 3
2. ERP Programme Overview .................................................................................................... 4
3. Scope of Required Services ................................................................................................... 5
3.1. Implementation .......................................................................................................................................... 5
3.2. Application Management ........................................................................................................................... 5
4. Organisational Scope ............................................................................................................ 6
4.1. Organisational Scope .................................................................................................................................. 6
4.2. In-scope functions ...................................................................................................................................... 7
4.2.1. Finance .............................................................................................................................................. 7
4.2.2. Procurement ..................................................................................................................................... 8
4.2.3. Commercial ....................................................................................................................................... 9
4.2.4. HR ................................................................................................................................................... 10
4.2.5. Operations ........................................................................................................................................ 11
4.3. Timing considerations ............................................................................................................................... 11
4.4. Volumetrics ................................................................................................................................................12
4.4.1. No. of employees ..............................................................................................................................12
4.4.2. No. of Oracle Users ..........................................................................................................................12
5. Solution Components ...........................................................................................................13
5.1. Application Landscape ...............................................................................................................................13
6. Data .....................................................................................................................................15
6.1.1. Approach to Master Data ................................................................................................................. 15
6.1.2. Data Migration Requirements......................................................................................................... 15
7. Reporting Requirements ..................................................................................................... 16
7.1. Reporting landscape ..................................................................................................................................16
8. Design considerations ......................................................................................................... 17
8.1. Deployment Approach (Cloud vs OnPremise) ......................................................................................... 17
8.2. Security ...................................................................................................................................................... 17
8.3. Non-functional Requirements .................................................................................................................. 17
8.3.1. Availability........................................................................................................................................ 17
8.3.2. Scalability ......................................................................................................................................... 17
8.3.3. Backup and recovery ....................................................................................................................... 17
8.3.4. Disaster recovery ............................................................................................................................ 18
8.3.5. System performance ....................................................................................................................... 18
Appendices ............................................................................................................................. 19
A.1. Assumptions ..............................................................................................................................................19
A.2. Detailed requirements ............................................................................................................................. 22
General Ledger .......................................................................................................................................... 22
General Ledger Controls ........................................................................................................................... 23

Version 1.0

Fixed Assets ............................................................................................................................................... 23

Fixed Assets Controls ............................................................................................................................... 25
Accounts receivable .................................................................................................................................. 25
Accounts receivable controls .................................................................................................................... 28
Cash and Bank........................................................................................................................................... 29
Procure to Pay ........................................................................................................................................... 29
Procure to Pay Controls ............................................................................................................................ 34
Project Accounting .................................................................................................................................... 35
Project Accounting Controls .................................................................................................................... 36
Human Capital Management ................................................................................................................... 37
Human Capital Management controls .................................................................................................... 43
General Reporting Requirements ............................................................................................................ 44
Management Information Reporting ...................................................................................................... 45
General financial requirements ............................................................................................................... 46
General Ledger reporting ......................................................................................................................... 49
Accounts Payable reporting ...................................................................................................................... 50
Accounts Receivable reporting ................................................................................................................. 52
Fixed Assets reporting .............................................................................................................................. 54
Inventory reporting .................................................................................................................................. 55
Project accounting reporting .................................................................................................................... 56

Version 1.0

1. Purpose
1.1. Context
The Bureau of the Dubai EXPO 2020 requires an ERP solution to provide support back office and operations
functions from 2016 through to completion of the execution of EXPO 2020.
This Statement of Needs document outlines the requirements of this ERP solution, the environment into which
this solution will be deployed, the user base, scope of functionality, and any other such relevant information as
pertains to the target solution.

1.2. Objective
This document outlines a set of baseline requirements to inform the scoping and early stages of solution
analysis and design of the implementation project.

ERP Program

17 March 2016
3

Version 1.0

2. ERP Programme Overview

At a systems level, the Bureau is currently evaluating between deployment options (i.e. On Premise, Cloud or
Hybrid solutions). It is seeking the lowest risk approach, and shortest possible timeframe, without compromising
on the quality of the solution, and the ability to futureproof the design.
Given the timescales of EXPO, a major consideration is the desire to avoid a major application upgrade in the
period immediately preceding EXPO execution as this will have an operational impact on operations that should
be avoided.
Due to the nature of the organisation, EXPO has a clear set of ERP related business requirements set out for back
office functions, for implementation in 2016. Further downstream requirements will continue to evolve over
time, particularly with respect to operational requirements (e.g. inventory management, revenue management)
and technical integration requirements arising from new systems coming online.
As such, it is essential that this Programme has a 5 year view with respect to requirements, the evolution of the
ERP solution, and the ongoing support and enhancements that will be required for the solution to remain relevant
to the needs of the organisation.
For this reason, and to simplify the requirement, the high level need can be categorized as follows:
-

Implementation services
o

Wave 1: Back office (for delivery in 2016)

Wave 2: Operations (for delivery 2018/19)

Support services

ERP Program

Ongoing fix on fail support for a period up to 5 years

Minor enhancements, as required, through the life of the support contract.

17 March 2016
4

Version 1.0

3. Scope of Required Services

3.1. Implementation
Wave 1 is required to be delivered in 2016, to support core back office functions. As the bulk of processing
activity is currently manual, speed to value is important for the Bureau who require a fit for purpose solution in
the shortest possible timeframe, without compromising on quality.
At the time of writing, related applications (BAYT, Tejari and PRISM G2) are either live, or planned to go-live
during 2016, meaning the business will be operating with an interim set of semi-automated processes until such
time as an ERP solution can be deployed.
Wave 2 will be a subsequent tranche of activity estimated to be required in mid-late 2018/19. The operational
element of EXPO2020 will bring an additional set of ERP requirements towards 2018 to support the actual
execution of the Dubai EXPO. Although these are understood at a high level currently, the underlying detail is
not yet available. Consequently, the solution deployed during 2016 to meet current, known, requirements will
need to be extended at a later date (likely during 2018) to incorporate future emerging requirements,
specifically around revenue recognition (e.g. integration with ticketing systems), and inventory and asset
management functionality.
The ability to integrate the planned Oracle ERP solution with EXPOs existing contract management platform
(PRISM G2), will be considered a critical success factor in helping EXPO achieve tight fiscal control, and rapid
management information, across their existing and future planned portfolio of investments.

3.2. Application Management

EXPO is seeking outsourced application management support services for the life of the Oracle ERP solution.
This should include Level 2 helpdesk support.
Any infrastructure related to the ERP will be hosted under an existing infrastructure hosting arrangement with
Du, and is considered to be excluded from the scope of existing requirements.

ERP Program

17 March 2016
5

Version 1.0

4. Organisational Scope
4.1. Organisational Scope
EXPO is split into 3 distinct entities/operating units:
-

ERP Program

17 March 2016
6

Version 1.0

4.2. In-scope functions

4.2.1. Finance
To support the EXPO finance function, core back office finance capability should be delivered using Oracle
wherever feasible. The finance function is currently using an application called Focus as an interim solution
until this can be replaced by Oracle.
The notable exceptions to this are as follows:

The budgeting and forecasting process will remain a manual activity with all activities against a given
budget being tracked in Oracle (5yr budgets are prepared and revised annually during the last quarter
of each calendar year)

Consolidation will remain a manual activity.

As the EXPO gears up for execution in 2020, the focus of finance activities will shift towards revenue
management. Revenue will come from a number of sources associated with EXPO 2020, including ticketing
fees, car parking, food & beverage outlets, and general merchandising. This will require downstream
integration with front office systems (e.g. ticketing) that are future planned, therefore the requirements for
which have not yet been defined.
The primary currency for EXPO is the Emirati Dirham (AED) although support will also be required in Oracle
for the following currencies: USD, EURO, and GBP. Integration to a 3rd party for access to real-time currency
exchange rates should be included in Oracle for ease of maintenance.
EXPO currently uses a number of bank accounts from one bank. Bank integration will be required as part of
the solution to support supplier payments, employee payments (payroll, allowances and expenses), and bank
statement reconciliation.

Aspect

Comments
The finance function is internal to the Bureau and led by Mukhtar Safi (SVP Finance), supported by
Hamad Said, Financial Controller.

Organisation

A Revenue Operations Manager role is planned at a later stage to support revenue management during
the execution of the EXPO.
The finance team will be located at EXPO2020 HQ in Jebel Ali.

People

The current finance headcount is 4 FTEs, expected to scale to 10 by 2018

Transactional finance operations are insourced and currently supported by an interim solution called
Focus, which will be replaced by Oracle Financials. Processes not currently enabled by Focus are
handled manually.

Process

Budgeting and forecasting is currently handled manually, however may be automated in the future
(tbd).
Treasury is also within the scope of the finance function and is currently manual.
The following policy and supporting documents exist for Finance and latest versions should be
referenced as part of solution design:

Policy

ERP Program

EXPO 2020_Accounting policies_v12_20.pdf

Chart of Accounts_Maintain v12.15.pdf

17 March 2016
7

Version 1.0

4.2.2. Procurement
The Procurement function owns the end to end source to settle process, with sourcing residing in the Tejari
solution, which will handle the RFx process. Tejari is the government procurement platform, hence its use in
the context of EXPO. Tejari should be considered the master data source for approved suppliers.
Only active (live) suppliers will be added to, and maintained, in Oracle via an integration to the Tejari system.
All procurement activities are governed by EXPOs Procurement Policy that sets out guidelines for EXPO with
respect to sourcing and procurement activities. The solution design should be aligned to corporate
procurement policy.
The Oracle solution will provide accounts payable and receivables capability, with invoice scanning and
workflow a must have requirement.
Although Tejari will act as the master data source for supplier data, this will need to be synchronized with
Oracle for all active suppliers with whom EXPO is transacting. This is reflected in the requirements for data
migration and interfacing. A decision on whether to use iSupplier Portal remains pending as this would require
suppliers to maintain their records in both Tejari and Oracle.

Aspect

Organisation

Comments
The procurement function is internal to the Bureau and led by Mukhtar Safi (SVP Finance), supported
by Richard Maguire, Procurement Director.
The Procurement team will be located at EXPO2020 HQ in Jebel Ali.

People

The current procurement headcount is 4 FTEs, expected to scale to 12 FTEs by end 2017.

Process

Procurement operations are managed in-house by the Bureau. The systems landscape in scope of the
procurement function will be Tejari (for RFx processing and supplier master data), Oracle E-Business
Suite, and PRISM (for contract management).
The following policy and supporting documents exist for Procurement and latest versions should be
referenced as part of solution design:

Policy

ERP Program

EXPO Procurement Manual Issue 6Aug2015 V1.1.pdf

Procurement Contracts Delegation of Authority 06 August 2015.pdf

17 March 2016
8

Version 1.0

4.2.3. Commercial
Commercial management is provided by two teams within EXPO who work in close collaboration. The internal
commercial team has overall responsibility and accountability for contract management and related activities.
This team is supported by the Programme Management Consultants (PMC) which comprises representatives
from third parties CH2M and Mace, respectively.
The contract types being managed by the commercial team have been categorized as follows:

Strategic Projects that are procured via the PMC are referred to as strategic projects. They will
range from the appointment of design consultants and contractors to general site wide consultancy
agreements.
Tactical these are projects that are not procured via the PMC. Individual business units will act as
project managers and will ensure successful delivery. There will be no involvement of the PMC in
tactical projects.
P99 - Expo, procure manage and deliver a wide range of projects. There is a contract in place with
CH2M Hill/Mace to act as Programme Management Consultants (PMC), the management of this
contract is task order based and is known as P99.

Aspect

Comments
The commercial function is internal to the Bureau and led by Andy Tarrant, Commercial Director,
supported by Mustafa Jama.

Organisation

Strategic contracts associated with large capital projects being undertaken as part of EXPO are
managed by the PMC, which is a joint venture between CH2M Hill and Mace. This group is out of
scope for Oracle, as PRISM will be the primary system for managing strategic contracts for EXPO.
The Commercial team will be located at EXPO2020 HQ in Jebel Ali.

People

The internal commercial team headcount is 4 FTEs, and is expected to scale to circa 15 FTEs by 2018.

Process

The systems landscape in scope of the commercial team is PRISM G2 application for the management
of strategic contracts (large capital projects related) and Oracle for managing tactical spend.
The following policy and supporting documents exist for Procurement and latest versions should be
referenced as part of solution design:

Policy

ERP Program

160111 Commercial Handbook rev3.pdf

EXPO 2020 Cost Reporting Calendar 2016 FINAL 19th Jan 2016.pdf

17 March 2016
9

Version 1.0

4.2.4. HR
To support the EXPO HR function, employee lifecycle management will be delivered using an Oracle HCM and
Payroll solution. The only notable exception to this is the use of a BAYT instead of an Oracle solution to provide
online recruitment and selection capabilities.
Self-service functionality should be deployed where feasible to enable end users, and to reduce the
administrative overhead on the HR function. Manual processes are expected to be fully automated, using
standard functionality wherever feasible.
A single monthly payroll is planned on Oracle for core employees. Additional payrolls may be introduced at a
later stage under separate commercial arrangement.
The legacy of EXPO is a high priority for the HR function, with learning and enablement a primary focus.

Aspect

Comments

Organisation

The HR function is internal to the Bureau and led by Rita Penteado (Head of HR) and reports directly
into the CEO. The HR team will be located at EXPO2020 HQ in Jebel Ali.

People

The current HR headcount is 3 FTEs, expected to scale to 10 by 2018.

Process

The BAYT application is used for online recruitment and will be integrated to Oracle for setting up new
employees once an offer letter has been accepted. Otherwise, core HR functionality will be delivered by
Oracle.
The following policy and supporting documents exist for HR and latest versions should be referenced
as part of solution design:

Policy

ERP Program

[ERP01] HR Policies Manual Expo 2020 v1 20143112.pdf

[ERP02a] Performance Appraisal Management System Manual Expo 2020 v1.2 20161401.pdf
[ERP02b] Performance Appraisal Form 2016 v2 20161401.pdf
[ERP03] Delegation of Authority Human Resources v02 20152912.pdf
[ERP04] Recruitment Journey V1 20151312.pdf
[ERP05] POL Travel Policy V1 20150601.pdf
[ERP06] TEMP Travel Authorisation Form v1.2.pdf
[ERP07] TEMP Manpower Request Form V1.docx
[ERP08] TEMP Education Allowance Claim Form V1.3.pdf
[ERP09] TEMP Employee Index File.docx
[ERP10] TEMP Business Card Request Form.docx
[ERP11] TEMP Certificate Request Form.docx
[ERP12] TEMP Housing Loan Request FormV1.docx
[ERP13] TEMP Leave Request Form V2.docx
[ERP14] TEMP Mobile Allowance Request Form V1.docx
[ERP15] Temp Probation Review Form V2.docx
[ERP16] TEMP Training Request Form.docx

17 March 2016
10

Version 1.0

4.2.5. Operations
Inventory management will be required as part of Wave 2 to support the operational execution of the EXPO in
2020. This is not considered to be Wave 1 scope and, at the time of writing, future requirements cannot yet be
defined, with the exception of assumptions around scope and timing of Wave 2.

4.3. Timing considerations

Oracle modules that have already been identified as relevant to meeting business requirements have been listed
below, with associated timings for implementation. Current assumptions around in scope modules should be
verified by the SI during Analysis and Design, and finalised once a decision has been taken on deployment
approach (Cloud vs OnPremise):

Functional Area

Modules

Delivery
Phase

Oracle Financials

General Ledger

Wave 1

Accounts Payable

Wave 1

Accounts Receivable

Wave 1

Cash Management

Wave 1

Fixed Assets

Wave 1

Project Accounting

Wave 1

iExpenses

Wave 1

Core HR

Wave 1

Payroll

Wave 1

Time & Labor

Wave 1

Manpower planning

Wave 2

iProcurement

Wave 1

iSupplier Portal (tbd)

Wave 1

Oracle Purchasing

Wave 1

Oracle Inventory Management

Wave 2

Oracle Warehouse Management for

Oracle Inventory Management (tbd)

Wave 2

Oracle UPK Content (tbd)

Wave 1
(as
relevant
to scope
of
modules)

HR

SCM

UPK

ERP Program

17 March 2016
11

Version 1.0

4.4. Volumetrics
4.4.1. No. of employees
Employee numbers for the Bureau are projected to grow as follows. In addition to core employees, an
anticipated 30,000 volunteers will be involved in supporting execution of the EXPO in 2020. These employees
are expected to be contracted under a separate LCC entity.
The number of core vs self-service Oracle application users should be firmed up during the high level design
phase of the implementation, with a vendor negotiation that takes into account the future ramp up of users over
a 5 year period.

Year

Expected
no. of
employees

2016

150

2017

250

2018

470

2019

530

2020

600

2021

650

4.4.2. No. of Oracle Users

Oracle users have been categorized between core users and self-service users. Each of the functional areas will
be ramping up their teams between now, and 2020, in preparation for execution of the EXPO. Overall core
users will be relatively low in volume, with

Users by function

Finance
(10)

ERP Program

Procurement(12)

Commercial
(15 by 2018)

HR & Payroll (10

core, 650 selfservice)

Operations (tbd future)

17 March 2016
12

Version 1.0

5. Solution Components
5.1. Application Landscape
The EXPO architecture is largely in place, with the following systems either already live, or planned:

The initial wave of Oracle functionality is expected to be delivered in late 2016. For Wave 1, key integration
points between the core Oracle ERP solution, and existing 3 rd party applications, are as shown.
Due to the temporary nature of the EXPO organisation, and the requirement to execute a major event in 2020,
this applications landscape will continue to evolve between now and 2020, with applications coming online at a
later stage that are required to support actual execution of the Dubai EXPO. This includes applications with a
more operational focus, e.g. ticketing solution, which will drive additional requirements for Oracle beyond the
current planned implementation in 2016.

ERP Program

Application

Planned Usage

Aconex

Document management system

PRISM G2

Contract management system

Primavera P6

Project scheduling

GIS ESRi

Spatial planning

Dundas

BI Dashboards

17 March 2016
13

Version 1.0

Solibri

BIM modelling tool

RiskHive

Risk management

CostX

Cost management

Credit 360

KPI Management

Synchro

Logistics Management

A separate data warehouse is planned, using Dundas as the MI tool for Programme level dashboard reporting.
This will provide consolidated reporting capabilities from the underlying data sources of the disparate systems
currently in use at EXPO.

ERP Program

17 March 2016
14

Version 1.0

6. Data
6.1.1. Approach to Master Data
The master data governance is currently evolving within EXPO, and will continue to be managed as an internal
process.
Due to the complexity of the EXPO architecture, with a number of disparate data sources, strong master data
governance will be required to avoid any reconciliation issues between systems, once operational.

6.1.2. Data Migration Requirements

The following data will need to be migrated into Oracle:
Data/Source

Source

Migration Requirement

Tejari

Master data for active suppliers with whom transactions will be processed in
Oracle should be source from Tejari. This will be a live integration between
Tejari and Oracle to synchronise active supplier data between the two systems.
A one-time requirement will therefore exist to create supplier records for all
active suppliers at the point of go-live.

Transactional finance
data

Focus

Focus is the interim finance solution that is in use until an Oracle ERP solution
can be deployed. Focus holds transaction data from 2011. Transactional level
detail from April 2014 should be migrated into Oracle.

Employee master
data

Manual

Existing employees will be required setup in Oracle as part of the initial

implementation. Subsequent employees will be transferred to Oracle as part of
an automated interface between BAYT and Oracle HCM.

Supplier Master Data

Strategic contracts

PRISM G2

Strategic Projects information will need to be migrated from PRISM G2 to

Oracle ERP, this includes the following information:
- Project
- WBS
- Budgets
- Actual Costs (Posted Payment Certificates).
-Contracts/Purchase orders and Contract Purchase agreements
- All posted and open Invoices
Also the Contract information for strategic contracts currently held in PRISM
will be required to be migrated to Oracle as a one-time migration activity prior
to go-live. Subsequent contract information setup will be automated by an
interface between PRISM and Oracle Projects module.

Tactical contracts

Tactical projects will be required to be setup in Oracle. These are currently

managed as part of a manual process and are excluded from the scope of
PRISM.

Manual

ERP Program

This includes the following information:

- Project
- WBS
- Budgets
- Actual Costs (Posted Payment Certificates)
-Contracts/Purchase orders and Contract Purchase agreements
- All posted and open Invoices.

17 March 2016
15

Version 1.0

7. Reporting Requirements
7.1. Reporting landscape
At the time of writing, a separate activity is underway to address enterprise wide reporting requirements.
For back office functions, transactional reporting requirements should be satisfied by the core ERP solution.
See Appendix A for requirements.

ERP Program

17 March 2016
16

Version 1.0

8. Design considerations
8.1. Deployment Approach (Cloud vs OnPremise)
The Bureau is currently evaluation the feasibility of a Cloud deployment approach for the Oracle ERP solution.
Where Cloud elements of the solution can be adopted, without introducing undue risk or security issues (as this
is a pseudo government solution), this should be considered the preferred approach. Any implementation
estimates should, however, take into account that this is not finalized and the deployment approach is subject to
change.

8.2. Security
Standard role based user security will be used to support segregation of duties for finance users, and control
access to data and Oracle based reporting.
Authentication is currently controlled by Microsoft Active Directory as the identity management solution for
EXPO.
Due to the relatively small scale of the finance function, there will be exceptions to segregation of duties for key
roles within the finance function. This will be mitigated through the risk and controls framework that will be
applied to the Oracle solution.

8.3. Non-functional Requirements

The non-functional requirements set out the minimum requirements for the new ERP solution, based on
current and future known requirements. Where future requirements may be subject to change, this has been
noted.

8.3.1. Availability
Solution availability should be design in the context of the systems within which Oracle will be integrated. The
system should be available to end users during business hours.

8.3.2. Scalability
As future business requirements and transaction volumes for operations and inventory management are not yet
known, the solution needs to be sufficiently scalable to accommodate the additional modules, processing
volumes and requirements that will form part of Wave 2, currently estimated for 2018.

8.3.3. Backup and recovery

Daily backups of the solution will be required as a minimum with the ability to rollback to recover to a specific
point in time.

ERP Program

17 March 2016
17

Version 1.0

8.3.4. Disaster recovery

Disaster recovery and failover is a key requirement of the solution and options should be presented to EXPO as
part of solution design.

8.3.5. System performance

End user response times that are optimised for a modern ERP solution will be expected, regardless of whether a
Cloud or OnPremise (or Hybrid) solution is delivered.

ERP Program

17 March 2016
18

Version 1.0

Appendices
A.1. Assumptions
The following assumptions have been captured during the preparation of this document. These should be revisited
periodically through the implementation, to validate, or otherwise, as the implementation progresses.

Ref:

Functional Area

Item

All

3 entities will exist: the Bureau of EXPO 2020 Bureau, EXPO Co (LLC) and
Volunteers

All

Business processes, controls and security will be consistent across all in scope
entities

All

Volunteers do not fall within the scope of the Oracle user based, even for self-service
functionality

All

The ERP solution will support English language only, however some document
types will require Arabic translation

IT

Users will access Oracle via a link from the corporate intranet

General Ledger

Master data maintenance such as GL accounts and cost centres values will be
managed manually (not requirement for workflow approval etc.)

General Ledger

There is no requirement to use an integrated schedule workflow functionality to

manage close activities. This will be performed manually.

General Ledger

There is no requirement to monitor the status of balance sheet reconciliations, and

to process approvals of these reconciliations using a workflow tool. This will be
performed manually.

Fixed Assets /
Inventory

There will be a future technology requirement for a facilities/inventory/asset

management system. The full requirements for these system are not known but the
Oracle ERP should be able to integrate with these systems.

10

Order to Cash

There will be a future technology requirement for an order Management system,

Point of Sales (PoS) and there is a CRM solution currently being implemented. The
Oracle ERP should be able to integrate with these systems.

11

HR

The HR function will remain internal to EXPO.

12

HR

The volunteers will be managed under a separate arrangement and do not fall
within the scope of the Oracle HR & Payroll solution.

13

HR

The employee based for EXPO will grow as follows: 150 employees in 2016, 250 in
2017, 470 by 2018, 530 in 2019, 600 in 2020, and 650 by 2021.

14

HR

The total number of volunteers supporting EXPO execution is anticipated to be

circa 30,000. These volunteers will be managed separately under LLC.

15

HR

Permanent, temporary, seconded and contractors/consultants (contingent workers)

will be supported by the target solution.

16

HR

The same grading structure will be applied to all employees.

17

HR

A revised grading structure will be determined in March 2016.

18

HR

The probation period for onboarding is 3 months for new employees (can be
extended for a further 3 months).

19

HR

A Case Management system is not required to manage disciplinary and grievance

cases. This will remain a manual process.

ERP Program

17 March 2016
19

Version 1.0

Ref:

Functional Area

Item

20

HR

Employee types will also include part time employees, Interns and Apprentices.
They will not be reflected in the Workforce plan. However, HR will be responsible
for raising a Requisition form to initiate the recruitment process for these
employees

21

HR

There will be no Time & attendance system for employees to clock in and out.
Overtime will be applied for through the self-service option.

22

HR LMS

Employee training records will be maintained and reported in Oracle (training

hours per employee).

23

HR - LMS

Personal development plans will be maintained in Oracle.

24

HR - LMS

Training costs will be tracked and reporting in Oracle.

25

HR - LMS

HR training budgets will be derived manually on an annual basis, and associated

spend tracked in Oracle.

26

HR LMS

Training effectiveness (survey results) will be stored and reported in Oracle.

27

HR Performance
Management

Performance management will be conducted in Oracle (objective setting and

competency ratings).

28

HR Performance
Management

Expo currently uses a 5-point rating scale for their performance appraisals. They are
expected to move to a 4-point scale in 2017.

29

HR Performance
Management

There is currently one development programme, which is the Apprenticeship

programme. There is a possibility of including other development programmes in
2017 and beyond.

30

HR Recruitment
& Onboarding

Currently, apprentices are assigned a Supervisor, who is internal to Expo, and a

Mentor, who are not employees of Expo. There may be a move towards assigning
mentors who are employees of Expo.

31

HR Recruitment
& Onboarding

The Requisition process and generation of Employment contracts will be done on

the ERP. The sourcing, selection and generation of the offer letter will be done on
BAYT.

32

HR Reward

Overtime and absence reporting will be tracked and calculated in the ERP solution.

33

HR Reward

There will be one salary structure per employee segment (permanent, temporary
employees and consultants).

34

HR Reward

The Bureau will not have Recognition schemes which require to be managed by the
system.

35

Payroll

Multi-currency requirements for payroll include AED, USD, GBP and Euro

36

Payroll

One monthly payroll will be run for all in scope employees.

37

Payroll

Currently, payroll is paid through one bank account. However, there may additional
bank accounts included for process payroll.

38

Payroll

Ad hoc payment capability will be required for payment of certain allowances,

subject to timings.

39

Payroll

Employee expenses will be paid via Oracle payroll.

40

Payroll

The organisation will have variable pay options to incentivize employees (including
bonus schemes and merit increases).

41

Procurement

Tejari will continue to be used as the supplier Master and RFP platform.

42

Procurement

Tejari will continue as the solution for Master Data and RFx process

43

Procurement

Annual satisfaction surveys to monitor the performance of the Procurement

Department will be handled manually/off-system

44

Procurement

Code of Conduct documentation signed by procurement team members will not be

stored in Oracle

ERP Program

17 March 2016
20

Version 1.0

Ref:

Functional Area

Item

45

Procurement

The Technical Evaluation Form for RFX evaluations will be stored in Tejari

46

Procurement

The Commercial Evaluation Form for RFX evaluations will be stored in Tejari

47

Procurement

The Recommendation Report for sourcing decisions will be stored in Tejari

48

Procurement

Corporate credit card purchases will be paid directly through finance

49

Procurement

Supplier records cannot be created directly in Oracle as supplier header level detail
will be sourced from Tejari as the supplier master

50

Procurement

Supplier records can be amended in Oracle to populate detailed supplier site level
detail

51

Procurement

Suppliers will not have access to amend their own details in Oracle (iSupplier)

52

Procurement

The preparation and maintenance of the Annual Procurement Plan will remain a
manual activity and is out of the scope of the ERP solution

53

Procurement

Emergency purchase requests will remain a semi-manual process with a

retrospective purchase requisition and PO being raised in the ERP solution for
auditability

54

Procurement

For Single Source purchasing scenarios, a manual form will be replaced by an

automated approval hierarchy in the ERP solution

55

Procurement

No electronic invoices will be received from 3rd party sources

56

Procurement

Support for multi-currency invoices will not be required

57

Contract
management

PRISM G2 will act as the master data source for Strategic contracts, with a
synchronization to Oracle. Oracle will act as the master data source for Tactical
contracts.

ERP Program

17 March 2016
21

Version 1.0

A.2. Detailed requirements

General Ledger
Priority
(M/S/C)

Ref

Module

Requirement

GA01

General
Ledger

To comply with both IFRS reporting, local GAAP reporting in the UAE and IPSAS
where appropriate.

Must

GA02

General
Ledger

To allow postings to be stored in multiple currencies, using multiple FX rates

(transaction currency). These FX rates should be maintainable centrally.

Must

GA03

General
Ledger

To allow the recording of additional information in GL postings. The ability to enter

comments with Journal entries both at transaction level and journal level.

Must

GA04

General
Ledger

To provide drill-down functionality from GL posting to the sub-ledger(s) document(s).

Must

GA05

General
Ledger

To allow the creation of recurring entries based on a pre-defined calculation rule these
would run at pre-defined intervals and automatically create and post the appropriate
journal.

Must

GA06

General
Ledger

To automatically calculate and post unrealised and realised FX gains / losses.

Must

GA07

General
Ledger

To allow for the immediate reversal of journals where required, without the need to
manually create a new reversing journal manually.

Must

GA08

General
Ledger

To allow the creation of auto-reversing journal entries.

Must

GA09

General
Ledger

To allow two concurrent GL periods to be open at the same time, potentially on

separate ledgers/layers.

Must

GA10

General
Ledger

To allow the recording of budget transaction or balances for all spend categories,
budget versus actual comparisons and to generate alerts when specified thresholds are
reached, specifically for purchases.

Must

GA11

General
Ledger

To allocate costs automatically based on pre-defined allocation rules.

Must

GA12

General
Ledger

To allow the upload of journals from MS EXCEL or other text-based files.

Must

GA13

General
Ledger

To allow querying data in the GL on all data recorded, search, select etc.

Must

GA14

General
Ledger

To allow the recall of archived documents within the required tax requirements.

Must

GA15

General
Ledger

To provide a detailed audit trail for all transactions, and a means of creating early
warnings related to controls.

Must

GA16

General
Ledger

To perform the enforcement for the automated journal workflow approval.

Must

GA17

General
Ledger

To control postings on GL accounts (i.e., auto postings allowed only on certain

accounts).

Must

GA18

General
Ledger

User defined journal entry types and templates.

Must

GA19

General
Ledger

To offer at least 8 dimensions for GL account postings (e.g. Company, Natural

Account, Cost Centre, Programme, Project, Contract, Spare (Future Use), Spare
(Future Use)).

Must

ERP Program

17 March 2016
22

Version 1.0

Priority
(M/S/C)

Ref

Module

Requirement

GA20

General
Ledger

Ability to support a single chart of accounts, shared across with all legal entities and to
activate or deactivate accounts by entity.

Must

GA21

General
Ledger

Single log-on to all entities using single user ID.

Must

GA22

General
Ledger

To allow the activation of local language packs where required, and the maintenance of
master data records in local languages.

Must

GA23

General
Ledger

The ability to perform consolidation for legal entities transactions without impacting
or changing source ledger transaction.

Must

GA24

General
Ledger

The ability to perform and record the intercompany transactions.

Must

GA25

General
Ledger

The ability to perform the currency revaluation function for posted transactions.

Must

GA26

General
Ledger

The ability to perform the balances translation for reporting purposes.

Must

GA27

General
Ledger

To maintain different levels of hierarchy, establish parent-child accounts and

associated hierarchies.

Must

General Ledger Controls

Ref.

Requirement

Requirement

CGL1

Configurable
controls

There will be a requirement to configure between 20 to 25 Oracle configurable controls

around journals workflow approval, across the Record to Report process.

CGL2

Profile

There will be a requirement to configure between 12 to 16 Oracle configurable profile

options across the Record to Report process.

User Access and

Segregation of
Duties

User access policies should be built based on business requirements. Role Based Access
Control (RBAC) should configured to control user access to key functions across the
Record to Report processes.

S1

Fixed Assets

Ref

Module

Requirement

Priority
(M/S/C)

FA001

Fixed
Assets

The solution will provide the ability to add, register, modify, transfer, dispose,
automatically calculating gains / losses, revalue, write off and re-life assets (including
part disposals, different life spans) and create journals in the General Ledger module.

Must

FA002

Fixed
Assets

To maintain cost of improvements to existing assets as component of asset value.

Should

FA003

Fixed
Assets

To maintain a register of leased assets, and to meet all accounting requirements

including the calculation of financial leases values and operating leases.

Must

FA004

Fixed
Assets

Ability to register assets but not depreciate them.

Must

FA005

Fixed
Assets

Maintain cost of improvements to existing assets as component of asset value (e.g.

major overhaul expenses).

Must

ERP Program

17 March 2016
23

Version 1.0

Ref

Module

Requirement

Priority
(M/S/C)

FA006

Fixed
Assets

The solution will provide the ability to import / export information from and to spread
sheet applications and other defined formats (Mass uploads).

Must

FA007

Fixed
Assets

The ability to capitalise fixed assets under construction (CIP).

Must

FA008

Fixed
Assets

Ability to assign different life spans to assets and process accordingly.

Must

FA009

Fixed
Assets

The ability to make bulk changes to asset master data.

Must

FA010

Fixed
Assets

The solution will provide revaluation capability by category and by location.

Must

FA011

Fixed
Assets

The solution will provide the ability to transfer fixed assets from one legal entity
and/or an analytical section to another.

Must

FA012

Fixed
Assets

System should be able to track and record assets that have been retired from use but
not physically disposed of.

Must

FA013

Fixed
Assets

System to support physical verification and reconciliation of defined Assets.

Must

FA014

Fixed
Assets

The solution will provide the ability to manage useful life, depreciation method
(including non-standard depreciation methods and the ability to create new
depreciation methods where required).

Must

FA015

Fixed
Assets

System should facilitate for generating reports for Depreciation per the depreciation
calendar.

Must

FA016

Fixed
Assets

To calculate and report unplanned depreciation.

Should

FA017

Fixed
Assets

To calculate future depreciation based upon budgeted additions and disposals.

Must

FA018

Fixed
Assets

To register assets but not depreciate the delayed depreciation (with the ability to set
the depreciation start date in the future) or non-depreciated assets.

Must

FA019

Fixed
Assets

The solution will provide impairment capability for all fixed assets and by category as
required.

Must

FA020

Fixed
Assets

The solution will provide the ability to define, categorise and create a schedule for the
amortisation and depreciation of fixed assets.

Must

FA021

Fixed
Assets

The solution will provide the ability to calculate future depreciation based on the
existing assets by different criteria.

Must

FA022

Fixed
Assets

The system has an interface with the asset barcoding system to allow easy
identification.

Must

FA023

Fixed
Assets

The solution will provide the ability to transfer data and attachment jointly and
separately from other modules. (E.g. Invoice copy attached in Accounts Payable must
flow to Fixed Asset). Support multiple attachments with text update.

Must

FA024

Fixed
Assets

System should able to map different entity's asset defined at different books with
different categories/accounts

Should

FA025

Fixed
Assets

The system should support to interface data from other internal and external systems
including asset management and facilities management systems.

Must

FA026

Fixed
Assets

System to provide workflow and sign off functionality with escalation including
retirement, transfer, disposal etc.

Must

FA027

Fixed
Assets

The solution will provide the ability to drill down into source for transaction details
across all modules by location, cost centre.

Must

ERP Program

17 March 2016
24

Version 1.0

Ref

Module

Requirement

Priority
(M/S/C)

FA028

Fixed
Assets

The solution will provide the ability to produce an asset summary showing cost,
salvage value, accumulated & current depreciation, and book value.

Must

Fixed Assets Controls

Ref.

Requirement

Requirement

CFA1

Configurable
Controls

There will be a requirement to configure around 3 Oracle configurable controls in the

Fixed Asset module.
All asset additions, transfers or disposals are subject to automated approval workflows.

CFA2

Profile

There will be a requirement to configure 2 Oracle configurable profile options across the
Fixed Assets module.

SFA1

User Access and

Segregation of
Duties

User access policies should be built based on business requirements. Role Based Access
Control (RBAC) should be configured to control user access to key functions across the
Fixed Asset module.

Accounts receivable
Priority
(M/S/C)

Ref

Module

Requirement

AR01

Accounts
Receivable

To allow the maintenance of multi-level customer hierarchies, with the ability to

maintain credit limit and block status at various levels.

Must

AR02

Accounts
Receivable

To allow the customisation of the credit blocking process.

Must

AR03

Accounts
Receivable

To allow the maintenance of a wide range of contact details in the customer master
record.

Must

AR04

Accounts
Receivable

To allow the maintenance of multiple language translations of all fields used in the
customer master record.

Could

AR05

Accounts
Receivable

To post and generate output for sales invoices (email, print etc.) in one transaction.

Must

AR06

Accounts
Receivable

To allow the automated allocation of cash according to multiple criteria.

Must

AR07

Accounts
Receivable

Multi-level approvals for deductions applied to customer payments (approvals

should apply to a credit note).

AR08

Accounts
Receivable

To automatically distribute sales invoices via email, paper, EDI, PDF, and load onto
a self-service supplier portal.

Must

AR09

Accounts
Receivable

To manage data within sub-ledger accounting for multi-entities.

Must

AR10

Accounts
Receivable

To process multiple currencies and FX rates.

Must

AR11

Accounts
Receivable

To post intercompany transactions.

Must

AR12

Accounts
Receivable

To operate a cash collection and reminder process along with a related detailed
action plan.

Must

ERP Program

Should

17 March 2016
25

Version 1.0

Priority
(M/S/C)

Ref

Module

Requirement

AR13

Accounts
Receivable

To manage refunds of clients, with the link with order number, amount, status,
payment method, financial address.

AR14

Accounts
Receivable

To maintain different types of customer profiles to be used for automated credit hold
model.

AR15

Accounts
Receivable

To search or look up customer based on any criteria stored in the customer record.

AR16

Accounts
Receivable

To define credit hold conditions based A/R account balances and aging history.

Must

AR17

Accounts
Receivable

To list cash receipts to a customer account and allocate to multiple invoices at a later
date.

Must

AR18

Accounts
Receivable

To import order information from external systems and automatically generate sales
invoices.

Should

AR19

Accounts
Receivable

To record user defined A/R aging criteria.

Should

AR20

Accounts
Receivable

To use customer classes for pricing purposes that is to enable pricing to be applied
based on a variety of criteria related to the customer, whilst remaining easy to
maintain.

Should

AR21

Accounts
Receivable

To configure error and warning conditions during the posting validation process.

Must

AR22

Accounts
Receivable

To include a free form field in credit memos for additional reference information.

Must

AR23

Accounts
Receivable

To calculate cash discounts and deduct in the receiving process.

Must

AR24

Accounts
Receivable

Ability to attach documents to customers, orders, invoices, dispute/credit requests

etc. in the system.

Should

AR25

Accounts
Receivable

Ability to record revenue on accrual basis as collection orders are issued without
having to record manual adjustments.

Should

AR26

Accounts
Receivable

Ability to generate various types of invoice format.

Must

AR27

Accounts
Receivable

Ability to manage data within sub-ledger accounting for multi-entities.

Must

AR28

Accounts
Receivable

Ability to enter payments with various means of payments, bank cheques, transfers
and bank orders credit card and cash including split and multi payments.

Must

AR29

Accounts
Receivable

Ability to use the posting of intercompany trading partner IDs (legal entity, cost
objects etc.)

Must

AR30

Accounts
Receivable

Ability to allow automated accounting booking of payments on several legal entities,

within a same batch and for different fiscal year periods

Must

AR31

Accounts
Receivable

Ability to tag the types of payment received (manual, selected, automated, refund,
etc.)

Must

AR32

Accounts
Receivable

Ability to manage refunds of clients, with the link with booking reference number,
invoice number, amount, status, payment method, financial address.

Must

AR33

Accounts
Receivable

Ability to maintain multiple ship to codes and addresses.

AR34

Accounts
Receivable

Allow entry and maintenance of primary contact name and contact information like
telephone, fax, email etc.

ERP Program

Should
Must
Should

Should
Must

17 March 2016
26

Version 1.0

Priority
(M/S/C)

Ref

Module

Requirement

AR35

Accounts
Receivable

Ability to create and monitor customer credit limits and changes.

Must

AR36

Accounts
Receivable

Ability to define credit hold conditions based A/R account balances and aging
history.

Must

AR37

Accounts
Receivable

Ability to define user access to by customer type or other dimension.

Must

AR38

Accounts
Receivable

Ability to support different types of customer remittances for example cheque, credit
cards, EFT payments etc.

Must

AR39

Accounts
Receivable

Ability to support multiple bank accounts.

Must

AR40

Accounts
Receivable

Ability to support multiple currencies as required by specific entities.

Must

AR41

Accounts
Receivable

Ability to provide receipts and unapplied receipts reports based on different

parameters for example, customer, date range,

Must

AR42

Accounts
Receivable

Generate overdue letters to customers based on days sales outstanding (escalating

severity of dunning letters)

Must

AR43

Accounts
Receivable

Ability to provide Invoice, credit notes and debit notes based on different parameters
for example, Customer, Date range.

Must

AR44

Accounts
Receivable

Ability to import order information and automatically create invoices.

AR45

Accounts
Receivable

Ability for invoices to feed into A/R from order entry module.

Must

AR46

Accounts
Receivable

Ability to record user defined A/R aging criteria.

Must

AR47

Accounts
Receivable

Ability to amend invoices and credit memos.

Must

AR48

Accounts
Receivable

Provide option to print user-defined text on customer statements.

AR49

Accounts
Receivable

Calculate multi-level finance charges.

Must

AR50

Accounts
Receivable

Ability to configure error and warning conditions during the posting validation
process.

Must

AR51

Accounts
Receivable

Ability to record credit memos for deductions requested for returns and to apply
credit memos to open invoices.

Must

AR52

Accounts
Receivable

Ability to incorporate multiple approvals in return authorisations, credit memos,

and other adjustment activities based on amount

Must

AR53

Accounts
Receivable

Ability to refund customer based on specific historic pricing rules.

Should

AR54

Accounts
Receivable

Ability to define refunds by customer with pre-defined reason codes.

Should

AR55

Accounts
Receivable

Ability to include a free form field in credit memos for additional reference
information.

Must

AR56

Accounts
Receivable

Ability to create reports for deductions taken/applied against a customer account.

Must

AR57

Accounts
Receivable

Ability to override default GL code for deductions.

Must

ERP Program

Should

Should

17 March 2016
27

Version 1.0

Priority
(M/S/C)

Ref

Module

Requirement

AR58

Accounts
Receivable

The solution is able to calculate cash discounts and deduct in the receiving process.

Must

AR59

Accounts
Receivable

Ability to receive management fees in relation to managed funds as part of standard

AR process

Should

AR60

Accounts
Receivable

Ability to perform intercompany invoices for non-automated flows (e g occasional

cost reallocation)

Must

AR61

Accounts
Receivable

Ability to send automated customer statement of account through E mail.

Could

AR62

Accounts
Receivable

Statement of Accounts as of given date (For Balance Conformation).

Must

AR63

Accounts
Receivable

Ability to enter discount(Value/Percentage) in invoice (With Proper Approval)

Must

AR64

Accounts
Receivable

Customer wise transaction movement report.

Must

AR65

Accounts
Receivable

Ability to provide customer statement of account with all open Invoices report.

Must

AR66

Accounts
Receivable

Ability to do AR/AP netting (With approvals from both AR & AP).

Should

AR67

Accounts
Receivable

Report of Customers Account with No Transactions for Past 3 Months/ 6 Months/

1Year

Should

AR68

Accounts
Receivable

Ability to integrate with Order Management, rate card, CRM and Point of Sale (POS)
systems.

Must

AR69

Accounts
Receivable

Ability to support Lockbox functionality.

Must

Accounts receivable controls

Ref.

Requirement

Requirement
There will be a requirement to configure between 8 to 12 Oracle configurable controls in
the Receivable module.

CAR1

Configurable
Controls

Related controls need to be defined in the interface programs to check validated data is
transferred to the Oracle Receivable module.
Exception reports and alerts should be designed to address interfaces errors on timely
basis.
Approvals should be configured in the Oracle Receivable module for credit notes.

CAR3

Alerts

Alerts will be required as part of control mechanism. This includes alerts in the in the
interface process where an alert should be triggered if there is any failure in the interface
process.

CAR4

Profile options

There will be a requirement to configure around 2 Oracle configurable profile options in

the Receivable module.

SAR1

User Access and

Segregation of
Duties

User access policies should be built based on business requirements. Role Based Access
Control (RBAC) should configured to control user access to key functions across the
Receivable module.

ERP Program

17 March 2016
28

Version 1.0

Cash and Bank

Priority
(M/S/C)

Ref

Module

Requirement

CM01

Cash &
Bank

Ability to upload bank statements from multiple banks for all legal entities.

Must

CM02

Cash &
Bank

Ability to book a single cash transaction on one entity and distribute to other
entities in one transaction (funds transfer for all legal entities).

Must

CM03

Cash &
Bank

To ability to create and manage bank accounts for all legal entities.

Must

CM04

Cash &
Bank

To ability to perform bank reconciliation, manually and automatically, for all

legal entities.

Must

CM05

Cash &
Bank

To ability to perform cash positioning functions for all legal entities.

Must

CM06

Cash &
Bank

To ability to perform the cash forecasting functions for all legal entities.

Must

CM07

Cash &
Bank

The ability to perform the online queries for reconciled balances, cash
forecasting and cash positioning for all legal entities.

Must

Procure to Pay
Ref:

Module

Requirements

P01

Procurement

Ability to enforce compliance to contracted suppliers & categories

Must

P02

Procurement

The ability to support the approval process using automated workflows based
on business rules

Must

P03

Procurement

The ability to track and trace compliance measures in accordance with

corporate procurement policy

Must

P04

Procurement

The ability to procure single product from multiple suppliers

Must

P05

Procurement

The ability to restrict user access to PO status, payment status and other
related attributes based on job role

Must

P06

Procurement

The ability to integrate to existing systems Tejari and PRISM G2 to provide

end to end contract lifecycle management (including creation, negotiation,
administration and management)

Must

P07

Procurement

The ability to provide common coding across systems to support spend

analysis

Must

P08

Procurement

The ability to link category information with complete contract, PO, vendor
type, & GL account

Must

P09

Procurement

The ability to map, aggregate, report and analyse total spend data: by category,
by supplier, and by product.

Must

P10

Procurement

The ability to track spend against approved budgets

Must

ERP Program

M/S/C

17 March 2016
29

Version 1.0

Ref:

Module

Requirements

P11

Procurement

The ability to provide insight into the performance of suppliers per category/
product type/ product group

Must

P12

Procurement

The ability to provide risk profiles of current suppliers and identify any
changes in their risk profiles based on business rules

Must

P13

Procurement

The ability to collect, share, report and analyse data linked to supplier master
data elements

Must

P14

Procurement

The ability to support the master data alignment required in terms of:
suppliers, products, and product groups together with unique vendor and
product identification

Must

P15

Procurement

The ability for suppliers to create their own system profile based on predefined business rules

Must

P16

Procurement

The ability to monitor and trace the end to end sourcing process as a closed
loop cycle

Must

P17

Procurement

The ability to translate a master framework agreement to local product item

level detail to make the contract operational

Must

P18

Procurement

The ability to identify and manage support risks associated to the

implementation of a new contract

Must

P19

Procurement

The ability to capture history of interactions with suppliers to feed into

supplier performance management process

Must

P20

Procurement

The ability to measure supplier performance in a consistent and objective way

Must

P21

Procurement

The ability to specify/quantify all elements of the contract so work can be

called off with ease

Must

P22

Procurement

The ability to restrict purchasing behaviours based on users role in the P2P
process.

Must

P23

Procurement

The ability to set approval thresholds based on business rules

Must

P24

Procurement

The ability to conduct an audit trail of where PO/invoice is at in the end to end
process

Must

P25

Procurement

The ability to transfer prices from system contract to purchase order

Must

P26

Procurement

The ability to restrict payments (where no PO exists) based on specific

business rules, allowing exceptions to these rules where applicable

Must

P27

Procurement

The ability to support blanket/framework orders for certain types of category

spend

Must

P28

Procurement

The ability to send PO's electronically via email (integration with email server)

Must

P29

Procurement

The ability to send PO's to supplier site level (as opposed to header level)
addresses held in the system

Must

P30

Procurement

The ability to receive and record confirmation from a supplier than an order
can be fulfilled (linking this to PO/invoice)

Must

P31

Procurement

The ability to record one or multiple GRN's against a purchase order

Must

P32

Procurement

The ability to have automatic matching of GRN/PO/Invoices with built in

tolerances

Must

P33

Procurement

The ability to support automated matching of invoices against blanket PO's,

amending the PO as required to reflect latest position.

Must

ERP Program

M/S/C

17 March 2016
30

Version 1.0

Ref:

Module

Requirements

P34

Procurement

The ability to ensure closed PO's cannot be re-selected for matching

Must

P35

Procurement

Ability to raise a requisition

Must

P36

Procurement

Ability to prevent a PO being raised without an approved requisition

Must

P37

Procurement

Ability to raise a purchase order based on an approved quotation from Tejari

Must

P38

Procurement

The ability for purchase requisitions to be routed into an automated approval

process

Must

P39

Procurement

Ability to amend a requisition and re-route through relevant approval

workflow

Must

P40

Procurement

Ability to maintain supplier contract information against which purchase

orders can be raised

Must

P41

Procurement

Ability to process emergency purchases (i.e. raise and approve PO

retrospectively)

Must

P42

Procurement

Ability to process blanket purchase orders

Must

P43

Procurement

P44

Procurement

Ability to raise a requisition against a contract/blanket purchase order

agreement

Must

P45

Procurement

Ability to validate requisitions raised against relevant contract funds/limit

Must

P46

Procurement

Ability to identify emergency procurement activities (PO's) to allow quarterly

reporting on volume/type of emergency procurement events

Must

P47

Procurement

Ability to restrict purchasing limits by role/authority level

Must

P48

Procurement

Ability to create new supplier record via automatic interface from Tejari

Must

P49

Procurement

Ability to prevent creation of new supplier records directly in Oracle

Must

P50

Procurement

Ability to amend supplier records in Oracle

Must

P51

Procurement

Ability to maintain multiple contacts/sites per supplier

Must

P52

Accounts
Payable

Ability to link the suppliers return to a specific purchase order

Must

P53

Accounts
Payable

Ability to link to return of goods received against closed purchase orders

Must

P54

Accounts
Payable

Link return's debit memo to a single purchase order

Must

P55

Accounts
Payable

Link return's debit memo to multiple purchase orders

Must

P56

Accounts
Payable

On-line or electronic supplier payments

Must

P57

Accounts
Payable

Set limits and apply payment holds at supplier level

Must

P58

Accounts
Payable

Record refunds to ensure complete history of supplier activity

Must

P59

Accounts
Payable

Review current balances on-line

Must

ERP Program

M/S/C

Must

17 March 2016
31

Version 1.0

Ref:

Module

Requirements

P60

Accounts
Payable

Review and audit supplier information and control duplicate records

Must

P61

Accounts
Payable

Provide self-service inquiry of invoice and payment status

Must

P62

Accounts
Payable

The ability to capture supplier status (e.g. preferred, strategic) for each
supplier record

Must

P63

Accounts
Payable

Ability to create vendors through interface from online portal

Must

P64

Accounts
Payable

Ability for Vendors to see the status of invoices and payment details in online
portal

Must

P65

Accounts
Payable

The ability to store and retrieve scanned invoices for review and approval

Must

P66

Accounts
Payable

The ability to accrue for non-received invoices

Must

P67

Accounts
Payable

The ability to reverse and match a non-received invoice once the

corresponding invoice is booked

Must

P68

Accounts
Payable

The ability to manage credit notes, including functionality to support credit

notes not yet received

Must

P69

Accounts
Payable

The ability to view budget commitments and associated invoices

Must

P70

Accounts
Payable

The ability to cross validate rules to ensure that non-valid entries are not
posted or accepted by the system

Must

P71

Accounts
Payable

The ability to define different levels of authorisations to Accounts Payable

users

Must

P72

Accounts
Payable

The ability to view the transactions that constitute the balance on accounts

Must

P73

Accounts
Payable

The ability to select batches of invoices to be paid based on due date

Must

P74

Accounts
Payable

The ability to manually select and make payments to suppliers

Must

P75

Accounts
Payable

The ability to modify a payment during the payment process i.e. add or erase
one or several lines

Must

P76

Accounts
Payable

The ability to manage invoice or cheque payment cancellation and provide an

audit trail of the action

Must

P77

Accounts
Payable

The ability to manage the following means of payment: bank transfer, cheque,
credit card

Must

P78

Accounts
Payable

The ability to generate payments in more than one pre-determined currency

(AED, USD, GBP, Euro)

Must

P79

Accounts
Payable

The ability to specific staff members authorised to approve payment of

invoices

Must

P80

Accounts
Payable

The ability to generate alerts/notifications to pre-defined staff when payments

to a supplier exceed a defined threshold

Must

P81

Accounts
Payable

The ability to support advanced payments to suppliers, within the boundaries

of an agreed approval mechanism

Must

P82

Accounts
Payable

The ability to report on payments and payment status (including invoice

summary and detail, supplier payment deadlines, past due payables, and
supplier balances)

Must

ERP Program

M/S/C

17 March 2016
32

Version 1.0

Ref:

Module

Requirements

P83

Accounts
Payable

The ability to report on future payments to be processed based on payment

terms with the supplier

Must

P84

Accounts
Payable

The ability to restrict reporting access based on defined roles within the
procurement function

Must

P85

Accounts
Payable

The ability to report on cash receipts, reconciling differences, unreconciled

transactions, mismatched items, and other related views

Must

P86

Accounts
Payable

Ability to support multiple remit-to locations and/or payment instructions per

vendor

Must

P87

Accounts
Payable

Ability to support user defined blanket payment terms e.g. due date, discount
date, discount % or amount

Must

P88

Accounts
Payable

Ability to support user defined payment terms e.g. net due days, discount days,
discount % or amount

Must

P89

Accounts
Payable

Ability to track and report on administrative changes to the vendor master file
(for reconciliation to Tejari master file)

Must

P90

Accounts
Payable

Ability to allow scanned entry of invoices (via OCR recognition)

Must

P91

Accounts
Payable

Ability to distribute expenses to multiple accounts per line item

Must

P92

Accounts
Payable

Ability to track and report information for regular and temporary vendor by
the invoice line item

Must

P93

Accounts
Payable

Ability to support user-defined parameters for invoice approval (to assign

relevant invoices for manual approval and release)

Must

P94

Accounts
Payable

Ability to setup automatic account ageing

Must

P95

Accounts
Payable

Ability to allow user-defined ageing criteria

Must

P96

Accounts
Payable

Ability to hold an invoice

Must

P97

Accounts
Payable

Ability to identify duplicate invoices

Must

P98

Accounts
Payable

Ability to automatically calculate discount terms

Must

P99

Accounts
Payable

Ability to manually override discount terms

Must

P100

Accounts
Payable

Ability to report on open invoices

Must

P101

Accounts
Payable

Ability to produce cash flow projections based on: invoice due dates, invoices
released for payment, user-defined time periods

Must

P102

Accounts
Payable

Ability to report on past due payables

Must

P103

Accounts
Payable

Ability to part pay invoices

Must

P104

Accounts
Payable

Ability to manually select invoices for payment

Must

P105

Accounts
Payable

Ability to assign payment priority by vendor

Must

ERP Program

M/S/C

17 March 2016
33

Version 1.0

Ref:

Module

Requirements

M/S/C

P106

Accounts
Payable

Ability to place vendor on hold

Must

P107

Accounts
Payable

Ability to support cheque printing

Must

P108

Accounts
Payable

Ability to re-print cheques

Must

P109

Accounts
Payable

Ability to support full bank statement reconciliation for in scope banks

Must

P110

Accounts
Payable

Ability to report on reconciled and non-reconciled items

Must

P111

Accounts
Payable

Ability to schedule bank data uploads

Must

P112

Expenses

Ability for individual employee to submit employee expenses online via a

portal

Must

P113

Expenses

Ability for employees to scan and store receipts in support of expense

submissions

Must

P114

Expenses

Ability to link employee expense capability with corporate credit cards for
automated statement upload

Must

P115

Expenses

Ability for employees to upload expenses that do or do not include VAT line
items

Must

P116

Expenses

Ability for employee to track status of expense claim online

Must

P117

Expenses

Ability to apply validation controls to manage input of employee expenses

Must

Procure to Pay Controls

Ref.

Requirement

Requirement

CPP1

Configurable
Controls

There will be a requirement to configure between 30-40 Oracle configurable controls

across the Accounts Payable (AP) and Procurement (PO) modules.

CPP2

AME workflow

Workflow approval rules are required for key transactions processed through the
Procure to Pay cycle. This includes rules built for purchasing documents, Supplier
invoices and employee expenses. These should be built using Oracle Approval
Management Engine (AME)) and should reflect the EXPO Delegation of Authority
(DoA).

CPP3

Alerts

Alerts will be required as part of control mechanisms across key Procure to Pay
transactions. This includes updates to approval configurations (e.g. approval limits) and
Banks (including Supplier Banks).

SPP5

User Access and

Segregation of
Duties

User access policies should be built based on business requirements. Role Based Access
Control (RBAC) should configured to control user access to key functions across the
Accounts Payable (AP) and Procurement (PO) modules in Oracle.

ERP Program

17 March 2016
34

Version 1.0

Project Accounting

Ref:

Function

Requirement

Priority
(M/S/C)

PA01

Define Project

Oracle Projects must mirror projects created in Prism on a one to one basis.

Must

PA02

Define Project

The Project Number in Prism, and Oracle Projects SHOULD be number the
same, or simple human interpretable mapping

Should

PA03

Define Project

Budgets will be maintained in Prism as detailed budgets. For financial

purposes, the ability to store budgets against a project is mandatory

Must

PA04

Define Project

Values will be specified for risks and contingency, these should not be
included in the core budget, but must be available when examining total
exposure of the Expo

Should

PA05

Define Project

All Oracle Projects must reporting into the Expo2020 WBS structure. Project
Accounting and its objects must align to the group reporting requirements

Must

PA06

Define Project

All Projects will store a Project Manager

Must

PA07

Define Project

The ability to capture and classify different project types within Oracle

Must

PA08

Define Project

A project will represent a unit of work with many contractors or directly

procured goods and services recorded against the project.

Must

PA09

Define Project

The Project WBS structure will support the granular cost capture and
alignment into the wider Expo2020 reporting requirements.

Should

PA10

Capitalise
Cost

Strategic projects like produce a range of tangible and intangible assets. The
solution must support the capture and capitalization of cost.

Must

PA11

Capitalise
Cost

Tactical may produce assets and a combination of costs depending on the

activity and phase of work. Finance users must have the ability to review and
adjust the capitalization status on transactions.

Must

PA12

Capitalise
Cost

A Project may produce one or many assets from a project. Assets may have
different profiles, classes and asset lifes.

Must

PA13

Capitalise
Cost

The solution must have the ability to capture and capitalize late costs and
back date any depreciation as a result,

Must

PA14

Obtain
Approval

The solution must have the ability to control the status change on projects

Must

PA15

Obtain
Approval

The solution should have the ability to store approval documentation

Could

PA16

Budget
Capture

The solution must have the ability to record a budget by Project and Activity

Must

PA17

Budget
Capture

The solution must have the ability to record version of each budget with the
ability to report changes and adjustments.

Must

PA18

Budget
Capture

The solution must have the ability to record different types of budget against
the project.

Must

PA19

Resource
Management

The solution could have the ability to plan, forecast and allocate resources to a
project or activity

Could

PA20

Capture Time

The solution must have the ability to capture time and cost of time

Must

PA21

Capture Time

The solution must have the ability to utilize standard costing principals for the
definition and production of costs relating to time.

Must

ERP Program

17 March 2016
35

Version 1.0

Ref:

Function

Requirement

Priority
(M/S/C)

PA22

Capture Cost

The solution must have the ability to capture costs from a variety of sources

Must

PA23

Capture Costs

The solution must have the ability to record the outstanding retention due to
contractors

Must

PA24

Capture Costs

The solution must have the ability to record accruals and facilitate the
automatic reversal.

Must

PA25

Capture Costs

The solution must provide the ability to capture purchase order and report
open commitments.

Must

PA26

Capture Costs

The solution should accommodate the capture of costs related to time. These
costs can be captured as costed transactions or as individual timesheets

Could

PA27

Capture Costs

The solution must support the ability to adjust and correct costs within a
project.

Must

PA28

Adjust Costs

The solution must support the transfer of costs between projects and tasks
(the ability to adjust, correct the allocation of the cost or just a small part of
it.)

Must

PA29

Capitalise
Costs

The solution must support the capture of costs in preparation for

capitalization

Must

PA30

Capitalise
Costs

Goods and Services will be procured against a WBS structure, the output of
the work can be capitalized when a finance specialist identifies the assets as
complete.

Must

Project Accounting Controls

Ref.

Module

Requirement

CPA1

Configurable
Controls

There will be a requirement to configure between 4 to 6 Oracle configurable controls in the

Oracle Projects module.
Depending on the project type appropriate workflows should be configured in the Oracle
projects module so that all projects are approved before transactions are processed against
them.

CPA2

Profile

There will be a requirement to configure around 5 Oracle configurable profile options across in
the Projects module.

SPA1

User Access
and
Segregation
of Duties

User access policies should be built based on business requirements. Role Based Access
Control (RBAC) should configured to control user access to key functions across the Oracle
Projects module.

ERP Program

17 March 2016
36

Version 1.0

Human Capital Management

Ref:

Function

Requirement

Priority
(M/S/C)

HCM1

Workforce
Planning

Ability to provide visibility over the cost of each position (including salary
and recruitment costs)

Must

HCM2

Workforce
Planning

Ability to identify the type of FTE required in the Workforce Plan

(Permanent, temporary employees, secondees and consultants)

Must

HCM3

Workforce
Planning

Ability to capture cost to company which takes into account differences by

grade, country of hire, nationality, employee status

Must

HCM4

Workforce
Planning

Ability to view the consolidated Workforce Plan across the different

employee segments, divisions and grades

Must

HCM5

Workforce
Planning

Ability to conduct resource scenario planning which will include the impact
of transfers and restructuring from the event build up to demobilization

Could

HCM6

Workforce
Planning

Ability to link the Workforce Plan to the Recruitment Plan

Should

HCM7

Workforce
Planning

Ability to link the Employee Requisitions to specific positions in the

Workforce Plan

Must

HCM8

Workforce
Planning

Ability to capture Business Cases/ justifications for unbudgeted positions in

the Workforce Plan (required field / no attachment)

Must

HCM9

Workforce
Planning

Ability to monitor the status of the Workforce Plan. View available to Line
Managers for their span of control

Should

HCM10

Workforce
Planning

Ability to link the Separation of Service (leavers) process to the Workforce

Plan in order to measure the attrition rate

Must

HCM11

Workforce
Planning

Ability to monitor budgeted recruitment costs

Should

HCM12

Workforce
Planning

Ability to transfer employees between cost centres and reflect in the

Workforce plan

Must

HCM13

Workforce
Planning

Flexibility to hire temporary employees, interns and apprentices in positions

which are reserved for permanent employees

Must

HCM14

Workforce
Planning

Ability to link employee movement to the recruitment plan

Must

HCM15

Recruitment &
Selection

Ability to track recruitment costs including medical test, visa, travel, and
operation costs

Must

HCM16

Recruitment &
Selection

Ability to link job descriptions to Requisitions

Should

HCM17

Recruitment &
Selection

Ability to link Requisition Form to Applicant Tracking System (BAYT)

Must

HCM18

Recruitment &
Selection

Ability for Line Managers and HR to raise requisition forms based on

employee types

Must

HCM19

Recruitment &
Selection

Ability to offer to Manager self-service option for raising Requisitions

Must

HCM20

Recruitment &
Selection

Ability to pull the required information for selection if the candidate is

sourced internally

Must

HCM21

Recruitment &
Selection

Ability to generate employment contracts and manage the contract

acceptance

Must

ERP Program

17 March 2016
37

Version 1.0

Function

HCM22

Recruitment &
Selection

Ability of system to generate automatic trigger to all stakeholders involved

in the onboarding such as IT, security clearance, etc. (onboarding process
workflow)

Must

HCM23

Recruitment &
Selection

Ability to integrate with the visa management portal in order to push the
relevant data required for visa processing

Must

HCM24

Recruitment &
Selection

Ability to track status of onboarding activities from offer acceptance stage

until completion post joining formalities and induction

Must

HCM25

Recruitment &
Selection

Ability to pull documents automatically from the Applicant Tracking system

as required for the onboarding process

Must

HCM26

Performance
Management

Ability to integrate Performance Management system with Learning and

Development

Must

HCM27

Performance
Management

Ability to confirm, extend or terminate an employee during the probation

period

Must

HCM28

Performance
Management

Ability to set objectives in system

Must

HCM29

Performance
Management

Ability to cascade objectives from an organization level to department level

to individual level

Must

HCM30

Performance
Management

Ability to weight or rank objectives

Must

HCM31

Performance
Management

Ability to categorize objectives (behavioral vs. personal vs. company

objectives)

Could

HCM32

Performance
Management

Ability to align and include project-specific objectives (for cross-functional

activities)

Should

HCM33

Performance
Management

Ability to allow different people to provide input into different objectives

(i.e. multiple inputs and appraisers), especially for programs and projects

Should

HCM34

Performance
Management

Flexibility to amend objectives and input feedback at any point during year
(in case of job role change)

Must

HCM35

Performance
Management

Ability to capture an employee's performance trend throughout the year

Must

HCM36

Performance
Management

Ability to carry over objectives from one performance cycle to another

Could

HCM37

Performance
Management

Ability to conduct performance appraisal twice a year

Must

HCM38

Performance
Management

Ability to accommodate a 4 or 5-scale rating system

Must

HCM39

Performance
Management

Ability for to include a primary and secondary assessor in the Performance

Management system

Must

HCM40

Performance
Management

Ability to link 360 feedback with L&D and Performance Management &
Talent Management

Could

HCM41

Performance
Management

Ability to capture output of manual case management on an employee's

record

Should

HCM42

Performance
Management

Ability to track history of appraisals and feedback

Must

HCM43

Performance
Management

Ability to automatically generate triggers and escalation at all levels, at any

time during the performance appraisal process (i.e. individual level and
team level)

Must

ERP Program

Requirement

Priority
(M/S/C)

Ref:

17 March 2016
38

Version 1.0

Ref:

Function

Requirement

Priority
(M/S/C)

HCM44

Performance
Management

Ability to have visibility over an employee's disciplinary actions during the

performance management process

Should

HCM45

Performance
Management

Ability of system to capture performance management eligibility

requirements and determine who is eligible for a performance rating (for
example, a person who is on maternity leave or who started on a certain
date may not be eligible for a rating during a particular cycle)

Must

HCM46

Performance
Management

Ability of system to capture audit trail and performance history (i.e. this
person did not receive a rating during this period for a particular reason)

Must

HCM47

Performance
Management

Ability to upload supporting documentation for performance appraisals

(complimentary letters)

Could

HCM48

Performance
Management

Ability to rate individuals based on defined competencies

Must

HCM49

Performance
Management

Ability to weight and rate individual competencies

Must

HCM50

Performance
Management

Ability of system to support 3 phases (Planning, Assessment and Review) of

performance management process

Must

HCM51

Performance
Management

Ability to calibrate and moderate ratings across the organisation

Should

HCM52

Performance
Management

Ability to record the appeals decision, in case of disagreement of ratings

Must

HCM53

Performance
Management

Ability to measure an employees potential using the 9 box grid (for

development and career planning purposes)

Must

HCM54

Performance
Management

Ability to link an employees performance and potential rating

Must

HCM55

Performance
Management

Ability to assess an employee's performance on a development programme

(apprenticeship programmes, graduate programme). This includes
assessing whether an individual has successfully completed the programme
requirements.

Must

HCM56

Performance
Management

Ability to tag high potential interns, apprentices and temporary employees

to be considered for full time roles.

Must

HCM57

Performance
Management

Ability to designate a Supervisor and a mentor for employees. A supervisor

and a mentor will be two different individuals.

Must

HCM58

Performance
Management

Ability to generate a Personal Development Plan (for career development

purposes or to manage under-performance) at any time during the year

Must

HCM59

Performance
Management

Ability to track individual employee skills, capabilities, qualifications,

responsibilities and career development

Must

HCM60

Performance
Management

Flexibility in system to integrate and extract information from Personal

Development Plans

Should

HCM61

Learning &
Development

Ability to embed competencies in Performance Management and Learning

Management System

Must

HCM62

Learning &
Development

Ability to set up generic training profiles for new joiners with the option of
add-on trainings based on grade and career path

Should

HCM63

Learning &
Development

Ability to link Training Needs Analysis to the Workforce Plan and

Performance Management

Must

HCM64

Learning &
Development

Ability to manage the learning catalogue

Must

ERP Program

17 March 2016
39

Version 1.0

Ref:

Function

Requirement

Priority
(M/S/C)

HCM65

Learning &
Development

Ability to include social learning tools through the collaboration tool

(discussion boards and sharing of information)

Wish

HCM66

Learning &
Development

Ability to include a scheduler for trainings, linked to the training plan

Should

HCM67

Learning &
Development

Ability to link cost of trainings, budgets and profit centers

Must

HCM68

Learning &
Development

Ability to integrate with virtual training software and monitor completion

rate and results

Could

HCM69

Learning &
Development

Ability of system to trigger notifications/ emails to employees for trainings

that are overdue and escalate any non-compliance

Could

HCM70

Learning &
Development

Ability to incorporate the process for no show charges, charged back to the
cost center

Must

HCM71

Learning &
Development

Ability to reflect any non-compliance/ overdue trainings in the performance

management system

Should

HCM72

Learning &
Development

Ability to record an employees participation in external trainings

Must

HCM73

Learning &
Development

Ability to monitor training attendance

Must

HCM74

Learning &
Development

Ability to generate completion certificates for in house trainings

Should

HCM75

Learning &
Development

Ability to trigger a notification for mandatory trainings

Should

HCM76

Learning &
Development

Ability for Line Manager or employee self-nomination for training

Must

HCM77

Learning &
Development

Ability to set registration limits and criteria for attendance of training

courses

Should

HCM78

Learning &
Development

Ability to generate an alert for employees scheduled to attend a training

event (or any rescheduled training)

Must

HCM79

Learning &
Development

Ability to automate different levels of feedback for training programmes

(Kirkpatrick)

Must

HCM80

Learning &
Development

Ability to capture feedback on trainees, training and trainers, at the end of a

training session

Must

HCM81

Workforce
Administration

Ability to upload documents at any point during a workflow to serve as an

input for particular processes

Must

HCM82

Workforce
Administration

System should include an audit trail for documents and actions associated
with each position and employee

Must

HCM83

Workforce
Administration

Ability of the Manager to initiate / view / action change requests, check

employee leave record, manage approvals, view employee performance
details, attendance records

Must

HCM84

Workforce
Administration

Ability to calculate overtime based on pre-defined criteria

Must

HCM85

Workforce
Administration

Ability of system to manage specific leaves policies (up to 14 types) and

criteria by employee group

Must

HCM86

Workforce
Administration

Ability to record an employees joining date (upon return of leave) and

trigger the required workflow for escalation if they have not resumed in time

Must

ERP Program

17 March 2016
40

Version 1.0

Function

HCM87

Workforce
Administration

Ability to process all employee changes in the organization including

promotion, transfer, cost center changes, grades

Must

HCM88

Workforce
Administration

Ability to notify / automatically generate triggers for action (including

contract and visa renewal, end of probation)

Must

HCM89

Workforce
Administration

Ability to temporarily deactivate an employees status while on secondment

to another entity / on military service

Must

HCM90

Workforce
Administration

Ability to maintain a record of changes to an employees personal data

Must

HCM91

Workforce
Administration

Ability to manage the process of approvals for all employee movements

(transfer, promotions, grade changes)

Must

HCM92

Workforce
Administration

Ability to generate letters based on pre-defined templates (English and

Arabic). Flexibility to amend or add new templates for such letters

Must

HCM93

Workforce
Administration

Ability of system to capture exit interviews

Should

HCM94

Workforce
Administration

Ability to notify HR when an employee reaches retirement age

Must

HCM95

Workforce
Administration

Ability to manage the end to end employee separation process which

includes processing of the exit checklist by the different stakeholders

Must

HCM96

Workforce
Administration

Ability of system to tag different assets to each individual employees

Must

HCM97

Workforce
Administration

Ability to tailor employee entitlements at the end of service based on

circumstances of separation

Must

HCM98

Reward

Ability to link the Grade, salary and related allowances, loans and benefits to
a particular position/job code

Must

HCM99

Reward

Ability to access approved and evaluated job descriptions through the

system

Must

HCM100

Reward

Ability to manage the Grading structure with variations in the different pay
elements

Must

HCM101

Reward

Ability to capture recognition elements as part of performance history

Could

HCM102

Reward

Ability to capture benefit programmes (including medical and life

insurance) across different employee groups

Must

HCM103

Reward

Ability to schedule renewal of benefit plans globally through a notification

Must

HCM104

Reward

Ability to ensure a uniform split between basic salary and allowances (60%40% split)

Must

HCM105

Reward

Ability to generate any pay-related letters for staff based on a standard

template

Must

HCM106

Reward

Ability to capture the different pay elements and track changes to each
element separately

Must

HCM107

Reward

Ability to link payroll to Recruitment, Separation from service, Changes in

employee status, Leave Management, Time and Attendance workflows

Must

HCM108

Reward

Ability to set up multiple payroll runs by employee segments (permanent

and temporary employees, secondees, consultants, interns, part time
employees)

Must

ERP Program

Requirement

Priority
(M/S/C)

Ref:

17 March 2016
41

Version 1.0

Ref:

Function

Requirement

Priority
(M/S/C)

HCM109

Reward

Ability to run supplementary payroll at different frequency intervals for

salary advance payments, education allowance, annual leave air ticket
allowance, and annual leave advance payment etc.

Must

HCM110

Reward

Ability to manage exceptions in terms of salary and benefits

Must

HCM111

Reward

Ability to route all approved employee changes to payroll

Must

HCM112

Reward

Ability to link any payroll change to pay solutions and incentive schemes
payment

Must

HCM113

Reward

Ability to create recurring, non-recurring and variable pay elements

Must

HCM114

Reward

Ability to handle the UAE pension scheme

Must

HCM115

Reward

Processing of accruals (leave accrual, pension accrual, end of service

accrual)

Must

HCM116

Reward

Ability to process variable payments and/or deductions

Must

HCM117

Reward

Ability to generate pay slip which includes all details/ elements including
leave, pay, benefits, deductions

Must

HCM118

Reward

System should be able to capture any multi-currency requirements

Could

HCM119

Reward

Ability to link the Bank transfer directly to bank portal (electronic fund
transfer) and linked to Accounts Payable

Must

HCM120

Reward

Ability to process and account for termination payroll

Must

HCM121

Reward

Ability to automate payment of employee expenses via payroll

Must

HCM122

Reward

Ability to capture various payment schemes including monthly payments,

hourly wages and day rates

Must

HCM123

Organisation
Design

Ability to generate Organisation charts which can be broken down by

division and department

Must

HCM124

Organisation
Design

Ability to link approval levels and rights to roles (as opposed to individual
employees)

Must

HCM125

Organisation
Design

Ability to create unique identifiers for each position to avoid duplications

and recreation of jobs in the workforce plan.

Must

HCM126

Organisation
Design

Ability to tag each position requirement to a particular position on the

organization structure (including grade, job evaluation score, competencies
required)

Must

HCM127

Employee Self
Service

Ability for employee to view and amend personal details, including

uploading of any required documents (which also includes recording of any
external, personal trainings)

Must

HCM128

Employee Self
Service

Ability to classify personal information to trigger specific workflows

Must

HCM129

Employee Self
Service

Ability to view available trainings, mandatory trainings and training record

Must

HCM130

Employee Self
Service

Ability to view and print pay slips

Must

HCM131

Employee Self
Service

Ability to apply for duty travel

Must

ERP Program

17 March 2016
42

Version 1.0

Ref:

Function

Requirement

Priority
(M/S/C)

HCM132

Employee Self
Service

Ability to apply for any type of leave

Must

HCM133

Employee Self
Service

Ability to apply for any allowances and/or benefits

Must

HCM134

Employee Self
Service

Ability to request for any employment documents / letters (based on predefined templates)

Must

HCM135

Employee Self
Service

Ability for employees to route any queries through the system (Query
Management)

Must

HCM136

Employee Self
Service

Ability to apply for overtime

Must

HCM137

Employee Self
Service

Ability for employees to apply for claims, advances, housing allowance

Must

HCM138

Travel

Ability to route the approval workflow based on travel criteria and grade
entitlement

Must

HCM139

Travel

Ability to route approved travel request to a third party travel agent (email
notification)

Must

HCM140

Employee
Information

Ability to classify employee data as mandatory and generate a notification if

not complete

Must

HCM141

Employee
Information

Ability to escalate such notifications (through a system generated system),

till resolved

Must

HCM142

Change
Management

Inclusion of UPK's for end user online help

Must

Human Capital Management controls

Ref.

Category

Requirement

CHCM1

Configurable
Controls

There will be a requirement to configure up to 5 Oracle configurable controls across

the Human Resource and Payroll module.

CHCM2

AME workflow

Workflow approval rules are required for the key Human Resource and Payroll
transactions. This includes rules built for employee onboarding, leaves requests and
payroll transactions etc. These should be built using Oracle Approval Management
Engine (AME)) and should reflect the EXPO Delegation of Authority (DoA).

CHCM3

Alerts

Alerts will be required as part of control mechanisms. This includes an amendment

to employee bank account information.

CHCM4

Profile

There will be a requirement to configure around 12 Oracle configurable profile

options across the Human Resource and Payroll processes.

CHCM5

User Access and

Segregation of
Duties

User access policies should be built based on business requirements. Role Based
Access Control (RBAC) should configured to control user access to key functions
across the Human Resource and Payroll processes.

ERP Program

17 March 2016
43

Version 1.0

General Reporting Requirements

Ref

Category

Requirement

Priority

RGR01

General
Reporting

Access control linked to organization structure

Must

RGR02

General
Reporting

Access control should be role based and hierarchy based

Must

RGR03

General
Reporting

Ability to generate different levels of detail in reports: from summary to details

Must

RGR04

General
Reporting

Ability to personalise reporting templates based on parameters

Must

RGR05

General
Reporting

Ability to share templates

Could

RGR06

General
Reporting

Possibility of delegation of access control at user-level

Must

RGR07

General
Reporting

Ability to export to Microsoft Office formats

Must

RGR08

General
Reporting

Ability to customize outputs based on user requirements

Must

RGR09

General
Reporting

Ability to integrate brand requirements in report generation

Must

RGR10

General
Reporting

Ability to schedule generation of reports based on user requirements

Must

RGR11

General
Reporting

Ability to also trigger scheduled reports for other users. Ability to receive such
reports in an email

Must

RGR12

General
Reporting

System should have a forecasting module

Must

RGR13

General
Reporting

Ability to roll up subsidiary reporting requirements to a Group level

Must

RGR14

General
Reporting

Ability to build new report requirements into the system. Should not be a
technical function

Must

RGR15

General
Reporting

Any new data element added in the data management module should flow into
the reporting module

Must

RGR16

General
Reporting

Special audit module separate from the audit trail

Must

RGR17

General
Reporting

Ability for users to subscribe to standard reports

Must

RGR18

General
Reporting

Ability to save report results in the system and share with other users.

Must

RGR19

General
Reporting

Support of proactive analysis and triggering of alerts to users based on rules

that can be defined by users for themselves or others, or by administrators

Must

RGR20

General
Reporting

Ability to integrate and source information from non-ERP systems and use the
information for analysis

Should

RGR21

General
Reporting

Ability to integrate with MS Office to allow for ad hoc/Just in time analysis

from with tools like Excel

Must

RGR22

General
Reporting

Mobile support

Must

ERP Program

17 March 2016
44

Version 1.0

Management Information Reporting

Ref:

Category

Requirement

Priority

RMI01

Functionality

Provide reporting functionality to accommodate static reporting, dashboard

reporting, statistic and analytical reporting to accommodate a number of user
groups

Must

RMI02

Functionality

Support out of the box reporting for core Financial, HR, and Procurement
data

Should

RMI03

Functionality

Provide OLAP type functionality to drill-down to lowest level of data

submitted, including pivot, sort, and filter data

Must

RMI04

Functionality

Provide user-friendly, flexible, interactive, multi-dimensional reporting via

graphical interface for end-user ad-hoc reporting

Must

RMI05

Functionality

Provide a broad range of standard reporting templates that can be configured

by the end users

Should

RMI06

Functionality

Support local variations while maintaining group standardization

Must

RMI07

Functionality

Support multiple hierarchies

Must

RMI08

Functionality

Ability to archive prior period reports and retrieve them for viewing and
printing

Must

RMI09

Functionality

Ability to integrate data into MS Office applications

Must

RMI10

Functionality

Ability to access and/or distribute reports via the Web and e-mail

Must

RMI11

Functionality

Ability to add commentary into various reports for submission to

management teams

Must

RMI12

Functionality

Ability to provide workflow for questioning reporting variances and

commentary

Must

RMI13

Functionality

Ability to support Arabic in reporting

Must

RMI14

Functionality

Ability to support statistical analysis

Must

RMI15

Functionality

Ability to support multi-cost allocation processes for different BUs. (Some are
complex and others straight forward)

Must

RMI16

Functionality

Support for offline BI (an interactive dashboard can be downloaded).

Must

RMI17

Functionality

Performance Process Status Dashboard with up to date data

Must

RMI18

Functionality

Ability to invoke business processes from within the dashboard

Must

RMI19

Functionality

Ability to create customized KPIs for targeted analysis

Must

RMI20

Functionality

Ability to search within the dashboards, reports and features like dynamic
filtering

Must

RMI21

Functionality

Ability to capture in-process MI ("live status") for faster decision making

Must

RMI22

Functionality

KPI reporting for all processes; summarized KPIs for dashboards

Must

RMI23

Insight

Provide real time reporting for certain information sets

Must

RMI24

Insight

Ability to create and integrate data into interactive dashboards combining

tables, reports and graphical representations of data

Must

RMI25

Insight

Provide self service reports

Must

ERP Program

17 March 2016
45

Version 1.0

Ref:

Category

Requirement

Priority

RMI26

Insight

Provide push-pull functionality

Must

RMI27

Insight

Ability to incorporate graphical trend indicators (e.g. a down arrow if data is

trending down) and stoplights based on defined thresholds

Must

RMI28

Insight

Ability to create exception reports with "alert" features

Must

RMI29

Insight

Ability to drill-down on data (both graphical and tabular) presented in

dashboards or scorecards to view underlying data or reports, including ability
to drill-down on details of "alerts"

Must

RMI30

Insight

Ability for reports to be distributed automatically when triggered by an event

(e.g. a cash flow report is distributed when cash falls below a defined
threshold)

Must

RMI31

Efficiency

Reporting tool should have the ability to integrate data from multiple source
systems and provide multi-dimensional reporting support

Must

RMI32

Efficiency

Provide a simple end-user driven report writing tool, for "production" report
development

Must

RMI33

Efficiency

Ability to reuse row/column templates/objects in reporting tool

Should

RMI34

Governance

Provide robust security across dimensional, entity and costs elements

Must

RMI35

Governance

Ability to support multiple user groups and provide appropriate security and
training for each

Must

RMI36

Governance

Ability to support reporting validation to ensure data accuracy

Must

RMI37

Governance

Ability to provide flexibility so when there are changing business

requirements, reporting can be updated quickly and effectively

Must

General financial requirements

Ref:

Category

Requirement

Priority

RFR01

Financial
Reporting

Ability to define multiple forecasting templates

Should

RFR02

Financial
Reporting

Ability to forecast interest income

Could

RFR03

Financial
Reporting

Ability to retain historic data / forecasts

Should

RFR04

Financial
Reporting

Ability to support multiple-period rolling forecasts

Should

RFR05

Financial
Reporting

Produce cash flow projections ability to include only invoices released for payment

Should

RFR06

Financial
Reporting

Produce cash flow projections ability to support all obligations, regardless of status

Should

RFR07

Financial
Reporting

Produce cash flow projections by invoice due date

Should

RFR08

Financial
Reporting

Produce cash flow projections by user-defined time periods

Should

RFR09

Financial
Reporting

The solution will provide bank statement reconciliations in multiple currencies

Must

ERP Program

17 March 2016
46

Version 1.0

Ref:

Category

Requirement

Priority

RFR10

Financial
Reporting

The solution will provide the ability to calculate future cash flows, over specific
time periods, based on historic data and the ability to view all known AP
commitments

Could

RFR11

Financial
Reporting

The solution will provide the ability to define consolidated cash positions as
required for current and prior periods

Should

RFR12

Financial
Reporting

The solution will provide the ability to report on cash receipts

Should

RFR13

Financial
Reporting

The solution will provide the ability to report on daily reconciled cashbook position

Should

RFR14

Financial
Reporting

The solution will provide the ability to report on detailed reports of mismatched
items

Should

RFR15

Financial
Reporting

The solution will provide the ability to report on detailed reports of reconciled and
un-reconciled transactions and payments issued

Should

RFR16

Financial
Reporting

The solution will provide the ability to report on future payments to be processed
based on payment terms with the supplier (e.g. 3 year contract set up in system,
rental contracts)

Must

RFR17

Financial
Reporting

The solution will provide the ability to report on reconciling differences

Should

RFR18

Financial
Reporting

The solution will provide the ability to support on-demand cash forecasting,
requirements and positioning on different dates

Should

RFR19

Local
reporting

The solution will provide the ability for appropriate users to view all revenue
related information including but not limited to per revenue stream, per business,
per activity, and per timeframe

Must

RFR20

Local
reporting

Ability to support predefined, modifiable financial statements by entity or

consolidated

Must

RFR21

Local
reporting

Ability to report on account balances in summary or detail and account

movements to interface and populate the cash flow

Must

RFR22

Local
reporting

Ability to produce all standard period and yearly financial statements

Must

RFR23

Local
reporting

Ability to support comparative income statement and/or balance sheet

Must

RFR24

Local
reporting

Ability to report on accounts as present of total or another account and account

movements to interface and populate the cash flow

Should

RFR25

Local
reporting

Ability to support cash flow analysis and account movements to interface and
populate the cash flow

Must

RFR26

Local
reporting

Ability to create and modify Financial Statements for example, Balance Sheet and
Profit and Loss statements

Must

RFR27

Local
reporting

Ability to create custom reports at multiple levels (detail and summary)

Must

RFR28

Local
reporting

Ability to use multiple querying capabilities to feed the results of one query into
another and roll them up into a single report

Must

RFR29

Local
reporting

The solution will provide the ability to round up figures on predefined parameters,
including but not limited to budget, allowance, and report figures

Must

RFR30

Local
reporting

The solution will provide entities access to pre-defined information to design their
own reports either by user-defined daily views or XML export

Must

RFR31

Local
reporting

Ability to flag large value discrepancies from the reconciliation process for
management attention

Must

ERP Program

17 March 2016
47

Version 1.0

Ref:

Category

Requirement

Priority

RFR32

Local
reporting

The solution will provide the ability to allow automatic calculation of taxes payable
to all tax authorities as appropriate

Should

RFR33

Local
reporting

Tools to generate disclosures or notes automatically

Must

RFR34

Local
reporting

Tools to generate directors or auditors reports automatically

Could

RFR35

Local
reporting

The solution will provide standard reports to monitor matching payments with the
supplier accounts

Must

RFR36

Local
reporting

Standard Reporting available ad hoc in the system

Must

RFR37

Local
reporting

Reports can be extracted from the system and downloaded in an editable format

Must

RFR38

Local
reporting

Pre-defined security and access measures are in place to ensure security measures
for report access are in place

Must

RFR39

Local
reporting

The solution will provide a common shared reporting platform functionality to

ensure the interface of the consolidation data model aligned with the general
ledger data model

Must

RFR40

Regulatory
reporting

The solution will provide the ability for appropriate users to view all segment
related information (at a consolidated and entity level) including but not limited to
per revenue stream, per business (currency and geography), per activity, and per
timeframe

Must

RFR41

Regulatory
reporting

Ability to report on account balances in summary or detail

Must

RFR42

Regulatory
reporting

Ability to produce all standard period and yearly financial statements and include
commentary

Must

RFR43

Regulatory
reporting

Ability to support comparative income statement and/or balance sheet and include
commentary

Must

RFR44

Regulatory
reporting

Ability to report on accounts as percent of total or another account

Should

RFR45

Regulatory
reporting

Ability to support cash flow analysis and include commentary

Must

RFR46

Regulatory
reporting

Ability to create custom reports at multiple levels (detail and summary) and
include commentary

Must

RFR47

Regulatory
reporting

The solution will provide the ability to round up/down figures on predefined
parameters, including but not limited to budget, allowance, and report figures

Must

RFR48

Regulatory
reporting

The solution will provide administrative entities access to pre-defined information

to design their own reports either by user-defined daily views or XML export

Must

RFR49

Regulatory
reporting

The solution will provide the ability to output / input data in a supplier neutral
format such as XML and user-defined views

Must

RFR50

Regulatory
reporting

The solution will provide the ability to allow automatic calculation of taxes payable
to all tax authorities as appropriate (group and entity level)

Must

RFR51

Regulatory
reporting

Tools to generate disclosures and notes automatically

Must

RFR52

Regulatory
reporting

System will enable full consolidation accounting as well as minority

interests/limited partnership reporting.

Must

RFR53

Regulatory
reporting

Reports can be extracted from the system and downloaded in an editable format
(e.g. spreadsheets)

Must

ERP Program

17 March 2016
48

Version 1.0

Ref:

Category

Requirement

Priority

RFR54

Regulatory
reporting

The system must support a process monitoring tool for tracking the local entity
submissions

Must

RFR55

Regulatory
reporting

The system will support the scheduling of recurring entries

Must

RFR56

Regulatory
reporting

The system must support functionality to create reports and perform consolidation
in pre-defined acceptable timescales

Must

RFR57

Statutory
reporting

The solution will provide the ability for appropriate users to view all segment
related information including but not limited to per revenue stream, per business
(currency and geography), per activity, and per timeframe)

Must

RFR58

Statutory
reporting

Ability to support predefined, modifiable financial statements by entity or on a

consolidated basis

Must

RFR59

Statutory
reporting

Ability to support comparative income statement and/or balance sheet

Must

RFR60

Statutory
reporting

Ability to support cash flow analysis

Must

RFR61

Statutory
reporting

Ability to produce all standard period and yearly financial statements

Must

RFR62

Statutory
reporting

Standard reports will be available in real time and through ad-hoc requests to the
system

Must

RFR63

Statutory
reporting

Solution vendor provides system updates in the case of amendments to accounting

standards

Must

RFR64

Statutory
reporting

The system must have functionality which supports equity and investment
accounting and consolidation treatment, including intercompany eliminations

Must

General Ledger reporting

Ref:

Category

Requirement

Priority

RGL01

General
Ledger

The solution will provide the ability to create reports in different output formats
(doc, pdf, xml, csv)

Must

RGL02

General
Ledger

The solution will provide the ability to drill-down from financial reports or any level
into source for transaction details across all modules

Must

RGL03

General
Ledger

The system will provide the ability to restrict access to financial and reporting
information and specific accounts as per pre-defined rules It will allow the
implementation of internal controls based on the separation of duties

Must

RGL04

General
Ledger

The solution provides easy to use self-service reports, based on user defined
parameters

Must

RGL05

General
Ledger

Relevant control and sign-off capability for reporting units is to be implemented (eg.
monthly tracking, closing process tracking and submission status, automated
notifications and one consolidated view of stage status)

Must

RGL06

General
Ledger

The solution will provide the ability to report on detailed reconciliation statements

Should

ERP Program

17 March 2016
49

Version 1.0

Accounts Payable reporting

Ref:

Category

Requirement

RAP01

Accounts
Payable

The solution will provide the ability to produce reports to monitor payment,
including:

RAP02

Accounts
Payable

- invoice summary

RAP03

Accounts
Payable

- details

RAP04

Accounts
Payable

- user alert for expected invoice

RAP05

Accounts
Payable

- average deadline of supplier payment

RAP06

Accounts
Payable

- past due payables report

RAP07

Accounts
Payable

- payment litigations

RAP08

Accounts
Payable

- supplier balances

RAP09

Accounts
Payable

The solution will provide the ability to report on future payments to be processed
based on payment terms with the supplier

Priority

Must

Must

The solution will provide the ability to report on:

- cash receipts
- reconciling differences
RAP10

Accounts
Payable

- daily reconciled cashbook position

Must

- detailed reports of reconciled and un-reconciled transactions and payments

issued
- detailed reports of mismatched items
- detailed reconciliation statement General Ledger
RAP11

Accounts
Payable

Appropriate business user must be able to create reports

Must

Ability to support quick vendor review with:

- Outstanding balance
- Last check date

RAP12

Accounts
Payable

- Last check amount

Must
- Invoices paid
- Last purchase date
- Last purchase amount
- Year-to-date purchases

ERP Program

17 March 2016
50

Version 1.0

Ref:

Category

Requirement

Priority

- Purchases in previous years

- Default expense account
Provide reviews/queries of open invoices:
- By vendor

RAP13

Accounts
Payable

- By invoice
Must
- By voucher
- By expense account
- By due date
Produce cash flow projections:
- By invoice due date

RAP14

Accounts
Payable

- Ability to support all obligations, regardless of status

Must

- Ability to include only invoices released for payment

- By user-defined time periods
RAP15

Accounts
Payable

Produce past due payables report

Must

Produce partial payment of specified invoices:

RAP16

Accounts
Payable

- Ability to select specific invoices

Must
- Ability to select specific vendors
- Ability to pay a designated percentage of the total due
Ability to support invoice summary:

RAP17

Accounts
Payable

- By vendor
Must
- By GL account number
- By due date
Ability to support transaction register:

RAP18

Accounts
Payable

- Sort by GL account

Must

- Sort by vendor
Ability to support cash requirements:
RAP19

Accounts
Payable

- By due date

Should

- By discount date

ERP Program

17 March 2016
51

Version 1.0

Ref:

Category

Requirement

Priority

RAP20

Accounts
Payable

Ability to support aged accounts payable report

Must

Ability to support vendor analysis report:

RAP21

Accounts
Payable

- All transactions
Should
- Purchases history
- Payments history
Ability to report on:

RAP22

Accounts
Payable

- Cash receipts
Should
- Reconciling differences
- Daily reconciled cashbook position

RAP23

Accounts
Payable

Detailed reports of reconciled items and un-reconciled items

Must

RAP24

Accounts
Payable

Detailed reports of mismatched items

Should

RAP25

Accounts
Payable

The solution will provide the ability to use multiple currencies such as accounting,
transaction and reporting

Must

RAP26

Accounts
Payable

The system must provide AP prepayment report in foreign currency as well as in

local currency on required dates

Must

RAP27

Accounts
Payable

The system should provide the pre-paid expense balance report invoice wise and
account wise

Must

RAP28

Accounts
Payable

Ability to run Supplier Aging report in SOB currency or multiple currency in a

single report

Must

RAP29

Accounts
Payable

Ability to have country specific WHT rules and reporting requirements (already
detailed discuss had with Tax department)

Must

RAP30

Accounts
Payable

Able to generate report based on Vendor Category & Sub-category with date
parameter

Must

Accounts Receivable reporting

Ref:

Category

Requirement

Priority

RAR01

Accounts
Receivable

The solution will provide the ability to use multi currencies such as accounting,
transaction and reporting currency

Must

Accounts
Receivable

The solution will provide the ability to have a list of standard AR related reports
available in the solution, including but not limited to:

RAR02

Accounts
Receivable

Customer account details

Should

RAR03

Accounts
Receivable

Aged Balance invoice reports

Must

RAR04

Accounts
Receivable

Statement of settlements

Should

ERP Program

17 March 2016
52

Version 1.0

Ref:

Category

Requirement

Priority

RAR05

Accounts
Receivable

Statement of adjustments

Should

RAR06

Accounts
Receivable

Statement of settlement applications

Should

RAR07

Accounts
Receivable

Statement of action customers

Should

RAR08

Accounts
Receivable

Statement of key indicators of recovery

Should

RAR09

Accounts
Receivable

Summary of the client situation (Credit Snapshot)

Must

RAR10

Accounts
Receivable

Short list of clients

Should

RAR11

Accounts
Receivable

Detailed list of customers

Must

RAR12

Accounts
Receivable

List of customer profiles

Must

RAR13

Accounts
Receivable

List of customer relationships

Must

RAR14

Accounts
Receivable

Invalidated list of movements

Should

RAR15

Accounts
Receivable

Statement of bills in arrears

Should

RAR16

Accounts
Receivable

Sales journal

Must

RAR17

Accounts
Receivable

Journal of settlements

Must

RAR18

Accounts
Receivable

Register of settlements

Must

RAR19

Accounts
Receivable

Statement of key indicators of client module

Could

RAR20

Accounts
Receivable

Statement of inactive customers

Must

RAR21

Accounts
Receivable

Statement of revenue, tonnage and transactions by customer

Must

RAR22

Accounts
Receivable

Ability to search or look up customer based on any criteria stored in the customer
record

Must

RAR23

Accounts
Receivable

Ability to provide holistic customer view

Must

RAR24

Accounts
Receivable

Ability to monitor customer credit limits and changes

Must

RAR25

Accounts
Receivable

Ability to provide receipt and unapplied receipts reports based on different

parameters for example, customer, date range,

Must

RAR26

Accounts
Receivable

Produce Aged Trial Balance Reports

Must

RAR27

Accounts
Receivable

Ability to create reports for deductions taken/applied against a customer account

Must

ERP Program

17 March 2016
53

Version 1.0

Ref:

Category

Requirement

Priority

RAR28

Accounts
Receivable

Customer wise transaction movement report

Must

RAR29

Accounts
Receivable

Ability to provide customer statement of account with all open Invoices report

Must

RAR30

Accounts
Receivable

Report of Customers Account with No Transactions for Past 3 Months/ 6

Months/ 1Year

Should

RAR31

Accounts
Receivable

Relevant control and sign-off capability for reporting units is to be implemented

in a workflow system (e.g. monthly tracking, closing process tracking and
submission status, automated notifications and one consolidated view of stage
status)

Must

RAR32

Accounts
Receivable

Tools to generate directors or auditors reports automatically

Could

RAR33

Accounts
Receivable

Ability to generate consolidated reports in multiple currencies

Must

RAR34

Accounts
Receivable

The solution will provide the ability to report on cash receipts

Must

RAR35

Accounts
Receivable

The solution will provide the ability to report on daily reconciled cashbook
position

Should

Fixed Assets reporting

Ref:

Category

Requirement

Priority

RFA01

Fixed Assets

The solution will provide the ability to produce an asset summary showing cost,
salvage value, accumulated & current depreciation, and book value in
functional/reporting currencies, AED & USD

Must

RFA02

Fixed Assets

The system will provide a Fixed Assets roll forward by item and by category
(cost, additions, transfers, additions, disposals, depreciation/amortisation, net
book value)

Must

RFA03

Fixed Assets

Ability to model what-if scenarios within the system

Must

RFA04

Fixed Assets

Ability to post and report movement types in order to prepare an automated

movement table (for all balance opening, movement and closing for any given
period) at entity level and consolidated level with multiple currencies for
different calendar (e.g. PPE Schedule)

Must

RFA05

Fixed Assets

System should be capable of generating reports on a query basis capturing fields

including but not limited to asset number, description, category, and cost

Must

RFA06

Fixed Assets

System should be able to generate reports such as variance reports, budget vs.
actual report, and cost summary report for entity and consolidated level

Must

RFA07

Fixed Assets

The solution will provide the ability to create reports in different output formats
(doc, pdf, xml, csv)

Must

RFA08

Fixed Assets

Facility to review available Budget for specified asset category / project

Must

RFA09

Fixed Assets

The system will provide the ability to restrict access to asset category
information and specific location as per pre-defined rules It will allow the
implementation of internal controls based on the separation of duties

Must

ERP Program

17 March 2016
54

Version 1.0

Ref:

Category

Requirement

Priority

RFA10

Fixed Assets

The solution provides self-service reports, based on user defined parameters

Must

RFA11

Fixed Assets

Tools to generate audit reports automatically

Should

RFA12

Fixed Assets

Facilitate for both real time Reports and closed period reports

Must

RFA13

Fixed Assets

Facility to auto scheduling and delivery of data and reports

Should

RFA14

Fixed Assets

Real time budget availability for assets category, cost centre, and project

Should

RFA15

Fixed Assets

System should facilitate for generating reports for Depreciation for any given
specific day, week, or month

Must

Requirement

Priority

Inventory reporting
Ref:

Category

Ability to display stock on hand including but not limited to:

a) Volume
RIN01

Inventory

b) Value
c)

Should

Warehouse locations

d) Supplier geography
Ability to display stock on order including but not limited to:
a) Volume
b) Value
RIN02

Inventory

Should
c)

Warehouse locations

d) Supplier geography
e) Port
RIN03

Inventory

Ability to support an inventory point snapshot i.e. for QC auditing purposes.

Should

RIN04

Inventory

Ability to track stock on order which is in transit and capture financial value in
the inventory ledger.

Should

RIN05

Inventory

Ability to show and track stock movements between outstations.

Should

Ability to provide inbound and outbound volumes by multiple dimensions,

including but not limited to:
a) Stock on hand
RIN06

Inventory

b) Locations
c)

Should

Geography

d) SKU level

ERP Program

17 March 2016
55

Version 1.0

Ref:

Category

Requirement

Priority

RIN07

Inventory

Ability to perform "what if" scenarios to see the required stocking levels when
the parameters change.

Should

Project accounting reporting

Ref:

Category

Requirement-

Priority

The solution will provide the following reporting capabilities including but not
limited to:
RPA01

Project
Accounting

Current Forecast

Must

RPA02

Project
Accounting

Current Budget

Must

RPA03

Project
Accounting

Current Project Contingency

Must

RPA04

Project
Accounting

Current Value of Awarded Work

Must

RPA05

Project
Accounting

Actual Cost to Date

Must

RPA06

Project
Accounting

Current Value of Approved Funding

Must

RPA07

Project
Accounting

Actual Cost to Date Vs Original Budget

Must

RPA08

Project
Accounting

Actual Cost to Date Vs Revised Budget

Must

RPA09

Project
Accounting

Project Contingency Vs Project Risk Allowance

Must

RPA10

Project
Accounting

Period Movement in Forecast Total

Must

RPA11

Project
Accounting

Period Movement in Revised Budget

Must

RPA12

Project
Accounting

Period Movement in Actual Cost

Must

RPA13

Project
Accounting

Three Period Tracking of Forecast Total

Must

RPA14

Project
Accounting

Three Period Tracking of Revised Budget

Must

RPA15

Project
Accounting

Three Period Tracking of Actual Cost

Must

RPA16

Project
Accounting

Three Period Tracking of Project Contingency Draw-Down

Must

RPA17

Project
Accounting

Three Period Tracking of Programme Contingency Draw-Down

Must

RPA18

Project
Accounting

Original Budget for the Rest of the Year

Must

ERP Program

17 March 2016
56

Version 1.0

Ref:

Category

Requirement-

Priority

RPA19

Project
Accounting

Revised Budget for the Rest of the Year

Must

RPA20

Project
Accounting

Forecast Total for the Rest of the Year

Must

RPA21

Project
Accounting

Forecast Project Contingency Draw-Down based on Three Period Tracking

Must

RPA22

Project
Accounting

Forecast Programme Contingency Draw-Down based on Three Period Tracking

Must

ERP Program

17 March 2016
57