PMO Report Dashboard

Document Information

1.0 Overview

Business Context and Application Overview

Provide an overview of the app (e.g Domain, key processes, purpose of the app, etc)
Application User Profile

Describe the key User profiles that exist for the application. 

General role/Viewer role:

Approver role:

Target Users:

As examples: Controllers / Accountants

Application Type

Application Overview

Application Contact Details

Sign-Off / Approval

Application Access Rights 

Access to the PMO dashboard depends on the user's profile which ensures that the user is allowed to perform the requested action (e.g. Run reports and download results). The user profiles (“normal user” and “advanced user”) at the same time correspond to the privileges granted according to the Business Unit the user belongs to using Single Sign On functionality

Business Context

Scope: 

In-Scope

This document covers the requirements for the PMO Dashboard to be migrated onto Tableau

• Main dashboard visualisation and filters
• Access to data post corporate action (split)
• Access to the dashboard

Out Of Scope

• Data Sourcing requirements are out of scope of this document. 

2.0 Business Process

Capture the business process that the application supports . This can be describe through a process diagram or a business capability model.

The PMO team regularly monitors the overall financial and operational status of several programmes and projects within the organisation and provide update to stakeholders on project or programme status.  The team needs the capability to extract and transform data seamlessly for the required parameters that have been pre-defined as part of the reporting process.

Specifically, the PMO team objectives are: 

• Portfolio Monitoring:  The team requires the capability to monitor projects and programmes that are Open or Closed within a defined time period in order to determine status, be aware of risks to project delivery and provide decision useful information to stakeholders.
• Data sourcing: The PMO team sources project operational and financial data from Accolade (Solvay internal DB) and vshare.
• Reporting: The PMO team requires the capability to create reports from the data extracted from Accolade/vshare, highlighting several defined KPIs to provide updates on project financial and operational status. 
• Automation: The extraction, refresh and KPI update process are to be performed without manual intervention.

2.1 Challenge/Opportunities

Clearly articulate the specific problem or opportunity that the application is addressing within the business by leveraging from data. This should be a concise and well-defined statement that captures the essence of the challenge or opportunity that the application is trying to solve by providing insight from the data.  

The new PMO dashboard in Tableau will provide authorised users with the capability to leverage multiple data sources within Solvay to review Financial and Operational performance of programmes and projects within a 3.5 year rolling window and have instant access to KPIs, with automated data refresh, eliminating the need for any manual interference. 

• Effective presentation of data: The PMO team require the capability to present KPIs and project status information in an automated fashion, showing the most impactful metrics. 
• Consolidated reporting: A single source pf reporting Financial and Operational status of projects and programmes including KPIs
• Eliminate manual spreadsheets: The reporting process should not involve manual intervention

3.0 Application Feature Overview

Information about the existent features in the application.

4.0 Business Objects

This section should contain a table with the business objects used in the reports with links to the business object definition in LeanIX.  The purpose is to ensure that all DA&AI Products adhere to a centrally maintained list of business objects and definitions to allow us to achieve our digital ambitions.  For any questions about business objects and LeanIX, contact Data Governance or the Enterprise Information Architect.

Functional Description

6.0 System view (Architecture)

The purpose of this part is to describe the physical components that supports the functionalities of the product. From that point of view, this part should capture and visualizes the physical components of the data products such as backend, front end, data providers, libraries for ML models, etc. 

Functional Requirements

7.0 Non-functional Descriptions 

Please populate the relevant section and delete those that are not applicable.

7.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system.  In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required.  Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

7.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region.  The software systems must be secure from unauthorized access.  The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

7.3 Security

Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks.  Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

7.4 Performance

Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload.  In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now.  Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers. 

7.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period.  Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period.  Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations.  The Maintenance Dashboard will display data from the previous refresh of data.   

7.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work.  The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.  

7.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components.  It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job.  To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

7.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

7.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product. 

Storage of the Data