The document describes a dashboard system that allows users to access reports from multiple application systems through a single portal. It provides concise summaries of key sections of the document: - The dashboard mechanism involves defining projects, reports, roles, user rights, and users. Projects link the dashboard to application servers hosting reports. Reports are organized and assigned to roles to control user access. - The server requirements to run the dashboard interface and reports include Windows, Oracle database, forms builder, and sufficient disk space and RAM. - A users' guide outlines the sign-in process and navigation menu for administrators to configure projects, reports, roles and users, and for regular users to access reports through their assigned roles and rights.

1. Application Document

2. 1 | P a g e
Index
 Introduction & Scope ..………………………………………………………… 2
 Dashboard Mechanism ……………………………………………………… 3-4
 Server Requirement …………………………………………………………. 5
 Users’ Guide ……………………………………………………………………… 6
 Sign In ……………………………………………………………..……………… 7
 Projects & Reports Control ……………………………………….……. 8
 Reports Definition & Role Definition ………………………………. 9
 Rights per Reports ………………………………………………………….. 10
 User Creation ……………………………………………………………..….. 11
 Region & Branch Setup …………………………………………………… 12
 Dashboard MIS Portal …………………………………………………….. 13
 Flow Chart ….……………………………………………………………………… 14
 Summary ….……………………………………………………………………….. 15

3. 2 | P a g e
Introduction
With the advent of System technology, it is now feasible to provide effective and efficient
MIS Reporting service over the local or Internet to meet customers' requirements and
satisfaction. In this research, we have designed and developed a Desktop & Web-based
intelligent MIS Reporting support environment.
DASHBOARD is single portal from where user can access multiple systems reports with all
parameters definitions and in a proper hierarchy. Through proper role specification, all users
can be differentiate with each other as well as all application systems also manage through
role specification.
As a Result, DASHBOARD helps to save cost in eliminating the reduction in machine down
time and number of on-site visits on multiple application login to access each report. This
paper describes the basic architecture of the environment that supports the major
functions of environmental MIS Reporting.
SCOPE

4. 3 | P a g e
Dashboard Mechanism
Dashboard designed to maintain multiple application system’s MIS Reports on one portal
to make easy and quick interface to access every single report according to parameter.
Most easy way to understand the mechanism of Dashboard system is to understand all
basic topics of the system i.e.
a) Projects Definition.
b) Reports Definition & Controlling.
c) Roles Definition.
d) Rights Per Reports.
e) Dashboard Users Creation.
a) Projects Definition:
The main and most basic step in Dashboard is Project Definition. If this section is correctly
configured, further steps are too easy to configure. In this section user have to configure
all application servers’ details which are active and have required MIS Reports to access
through Dashboard portal. To configure application servers’, user need following details
i.e.
 Project Name
 Application or Project Name.
 Project Description
 Application or Project details
 Server Type
 Application Server is internal /same or external
 Server Name
 Application Server Name
 Server IP
 Application Server IP Address
 Directories
 Application Server directories where all reports installed
 User ID
 Application DB User ID.
 Passcode
 Application DB Password
 Server TNS
 Application TNS Network SID Name

5. 4 | P a g e
b) Report Definition & Control:
After project setup second main step is to configure all Reports through Reports Control
related to configured projects. In this section all reports should be defined with correct
details such as Report Name, Report Source File Name and parameters with correctly
selected items. After controlling all reports user has to define it for menu screen through
Reports Definition section. For Report Definition section user has to define menus and
their sub menus (if required) and then user has to attach report regarding the mentioned
described menu.
c) Role Definition:
Group of reports regarding to specific part is called Roles. For user specified duties,
Dashboard requires a specific Role for such specified duties through which users can be
differentiate from each other. A set of reports can be call through one single role. To
configure a Role user has to define Role Name and required reports and also enable /
disable each report for its effects for run time on reports menu screen.
d) Rights per Reports:
Some users required few reports which are not in their specified role. For this reason,
Dashboard allows to access such reports by just sanctioning such reports through Rights
per Reports section. To perform this action requires User ID and reports name.
e) Dashboard User Creation:
Every Application / Project has a user creation section, by which application can be
access and to perform duties. For creation of user, following details are required.
 User id
 User name
 Password
 User session (In-Active, Active)
 User status (Enabled, Disabled)
 Branch code
 Branch type (Head Office, Region, Branch)
 Role id (Will populate after Roles Definition)
 Rights (Admin, M.I.S.)
 Employee CNIC
 Employee ID
 Employee name

6. 5 | P a g e
Server Requirement
DASHBOARD system’s GUI designed on Oracle Forms 10g. Accordingly, its basic requirements
are as common as Oracle Required. Such as:
 Windows XP, 7 (with static IP / HOST)
 Oracle 10g exe / SE Database
 Form Builder / Application Server 10g
 Min 10GB space required where application configured
 Min RAM 2GB
 Healthy Network Configuration

7. 6 | P a g e
Users’ Guide

8. 7 | P a g e
- Sign In
Let’s start with DASHBOARD. By default, in configuration there is an ADMIN ID created with user
ID / password ADMIN/ADMIN to control newly interaction with DASHBOARD. It’s up to client to
remain default ID or create new one with the admin rights.
After login with Admin ID menu will appear with all admin rights. i.e.
User ID
Password
Menu

9. 8 | P a g e
- Projects
Through Project Line-up screen, all projects can easily configured.
- Reports Controlling
To install report in dashboard related to configured project, user have to access Reports Control
screen.

10. 9 | P a g e
- Reports Definition
Definition of all reports list in Tree format and in proper menu, sub menu manner.
- Roles Definition
A set of reports can be call through one single role.

11. 10 | P a g e
- Rights per Reports
Dashboard allows to access such reports by just sanctioning such reports through Rights per
Reports section.

12. 11 | P a g e
- User Creation
Dashboard user creation can be perform from below attached screen.

13. 12 | P a g e
- Region Setup
Region setup is must for user creation and branch setup.
- Branch Setup
Branch setup is must for user creation.

14. 13 | P a g e
If user login with MIS rights, only Dashboard Report Panel menu will appear. i.e.
- Dashboard MIS Portal
The main screen Dashboard users to Access reports according specified rights.
Menu
Projects
Grid
Reports
Grid
Parameters

15. 14 | P a g e
Flow Chart
Projects
Reports
Control
Reports
Definition
Reports
Branch
SetupRoles
User
Creation
Dashboard
M.I.S.
Portal
Server
1
Server
2
Server
1
Server
n’
Production
Servers
Region
Setup

16. 15 | P a g e
Summary
Give more people more Knowledge in no time.
Access multiple application system’s reports on single screen.
View and save all reports on PDF/html format.
User can perform easily long and difficult tasks by sitting their own places and without
any hurdle.
Manage bulk reports with single role.
View reports as fast as storm.
Friendly application GUI.
Independent Report Run Algorithm (IRRA).
Handle Reports Overloading automatically.
Maintains logs of all activities.
Help Solve problem faster.
Faster than any other system.

17. 16 | P a g e