Information Technology – Roll Out of OracleBI Discoverer to
the Worldwide User Community
Final Status Report of 11/25/2012
Scott Mc Coy
MS-PTC 610-851
November 25, 2012
Academic Research
Additional Progress in Completing the Usability Study
Results of the Interview
Twenty-two users (key users) within certain worldwide (North America, South America, Europe and Africa)
operation areas (Booking, Documentation, and Equipment) were identified to be data collectors and were given
the interview template. These twenty-two users canvassed their geographical areas to determine what existing
reports were needed for daily operations.
Two hundred twenty reports (220), normally executed from Star-Net or through vendor systems were converted
to Oracle(BI) Discoverer Plus and can be run through either Oracle(BI) Discoverer Plus or Oracle(BI)
Discoverer Viewer. The selection was based on resource requirements needed to run the reports (execution
statistics), the reports that were created in the vendor system, and as of a result of the interview questions
created by the Usability Department (AKA training department). The latter reports were identified by these key
users as crucial to a department’s operations, but were also cross referenced as ones that caused the most calls to
the support group. More specifically, Star-Net reports, along with the vendor reports number approximately
800, of which 220 were converted. Vendor system reports number 45, so interviewing uncovered 175 Star-Net
reports that needed to be converted. A representative list of converted reports is shown in the below screen
print:
Results of the Task based Focus Groups
The objectives of this activity:

To discover what the structure of an XXX department is, to efficiently implement Oracle(BI)
Discoverer
The Usability and ADP Group discovered that most departments canvassed, consisted of
managers and subordinates. In the larger agents, there is one manager and several supervisors. In
the smaller agents, there is one manager and subordinates.

To discover what users use Star-Net (the existing system)
Lists of users were accumulated in order to set them up in the Oracle(BI) Discoverer System.
Larger agents, those judged by container handling volume or those representing multiple
shipping companies, tended to have a segregated staff for each shipping company. Smaller
agents tended to inter-mingle staff to handle multiple shipping companies.

To discover how users adapt to new a new technology
For all agents, the learning of a new system is an issue, due to perceived learning curves and
limited time to switch interfaces while performing functions.

To discover changes that need to be made to this new technology to increase adaptability
Issues with adaptability centered on the following concerns:
a. Performance for some workbooks was extremely slow.
b. Necessary Items (fields or columns) are not available in Oracle(BI) Discoverer
that are available in Star-Net.
c. Functionality available to the ADP Staff for the creation of workbooks was not
available to the Discoverer Plus user (the participants in the task-based focus
group).
d. Reports failed to produce data even though data was contained in the system.
e. Missing data which could not be explained by differences between the production
system (updated continuously) and the test system (frozen on 26-OCT-2012).
f. Functionality (emailing, scheduling) in Star-Net that is not in Oracle(BI)
Discoverer.
g. A physical limit (10 Megabytes) on the size of an exported file which may
necessitate breaking up of data based on smaller date ranges. These multiple
workbooks will need to be recombined necessitating more time for job
completion.

To discover the aptitude of different users groups in understanding this new technology
Individuals within the task-based focus group were the more knowledgeable users of the
previous system. A broader base of users exists. These users will be encountered in January
when the Group Task Analysis is conducted in Chicago, IL.

To discover the user’s current aptitude in Structured Query Language (SQL)
It is not expected that SQL knowledgeable users will be trying to alter the tool generated code.
A finding of this task-based focus group was that the functionality to view the automated
generated code does not allow modification of the code.
The following data will be collected:

Notes on the interactions, concerns and frustration of the task-based focus groups in conceptually and
physically evaluating a new reporting and analysis tool
To summarize, there are concerns by agents
a. On using a new tool due to time available to perform functions.
b. On the current product as implemented because of perceived performance and data
retrieval issues.
c. On users mentioning that Discoverer Plus as a replacement for Star-Net will lead to more
work to remove unnecessary data from the raw data produced.
d. On the lack of columns available.
e. On the loss of functionality compared to the existing system used.

Observations by the Application Development Pool (Developers, Support, and Trainers) on how the
task-based group evaluates a new reporting and analysis tool
a. ADP is investigating enhancements to accommodate the users concerns
b. Support has voiced concern that additional calls may be received, not only about the current
performance issues, but now about utilizing the new tool, if ADP and training cannot
accommodate all the users concerns.
c. Training is further adjusting material based on a more thorough understanding of what the users
wish to accomplish.
Tasks Accomplished
1. Results of Interview questions will be analyzed and are reported (This status)
2. Surveys will be sent out the week of November 18, 2012 and expected back by November 23, 2012 (In
progress)
3. Task-based focus group statistics are being analyzed and are reported (This status)
Tasks to be Accomplished
1. Group Task Analysis Proposal will be completed by December 2, 2012
Tasks Dispensed With
1. Group Task Analysis for Additional “Discoverer Plus” users has been pushed to January 2013 so it will be
dropped
2. Group Task Analysis for all Discoverer Viewer users has been pushed to February 2013 so it will be
dropped.
Proposed Schedules – Completion Status Noted
Proposed Schedule – Interview Proposal
Work Package
Meet with UI Team to finalize
proposal
Book Conference Room
User access list and automated
script
Conduct Sessions - North America
Users (Remote) Multiple meetings
Conduct Sessions - South America
Users (Remote) Multiple meetings
Conduct Sessions - Europe Users
(Remote) Multiple meetings
Analyze Data and produce findings
of workbook changes
Create Draft Report
Review and comment on report
Publish final Report
Owner
Scott (UI Team), Linda (Support),
Marsha (ADP Manager)
Linda (Support)
Lydia (ADP Team Lead)
Scott(UI Team), Linda (Training),
Marsha, Rajan (ADP Managers)
Scott(UI Team), Linda (Training)
Scott(UI Team), Linda (Training)
Scott(UI Team), Linda (Training),
Marsha, Rajan (ADP Managers)
Scott (UI Team)
(ADP & Support)
Scott (UI Team)
Estimated Time-to-Complete
2 hours (Completed)
1 hour (Completed)
10 hours compile, 5 hours write
script (Completed)
3 hours on November 5 – 9
(Completed)
3 hours on November 5 – 9
(Completed)
3 hours on November 12 – 16
(Completed)
1 week (Completed)
1 week
1 week
1 week
Proposed Schedule – Task-Group Proposal
Work Package
Meet with UI Team to finalize
proposal
Book Conference Rooms – Send
meeting notices.
Create User Tasks
Participants
Scott (UI Team), Linda (Support),
Marsha (ADP Manager)
Linda (Support)
Conduct Task-based Group Focus
meetings
Scott(UI Team), ADP & Support
(Moderators) Business Process
Group and Users (NA, SAM, EU),
ADP),
Analyze Data and produce findings
of the survey
Create Draft Report
Review and comment on report
Publish final Report
Scott(UI Team), Linda (Training),
Marsha, Rajan (ADP Managers)
Scott (UI Team)
(ADP & Support)
Scott (UI Team)
Scott (UI Team), with review by
Linda (Training), Marsha, Rajan
(ADP Managers)
Estimated Time-to-Complete
2 hours (Completed)
1 hour (.25 hour for 4 sessions)
(Completed)
1 hour November 5 , 2012 and
November 12, 2012 (Creation)
(Completed)
2.5 hours on November 7, 2012 at
0700 hours, 1100 hours and 1400
hours (NA, SAM)
2.5 hours on November 14, 2012 at
0800 hours (EU) (Completed)
1 week (Completed)
1 week
1 week
1 week
Proposed Schedule – Survey Proposal
Work Package
Meet with UI Team to finalize
proposal
Book Conference Room
Create Survey
Owner
Scott (UI Team), Linda (Support),
Marsha (ADP Manager)
Linda (Support)
Scott (UI Team), with review by
Linda (Training), Marsha, Rajan
(ADP Managers)
Distribute Survey
Fill out Survey (individual users)
Scott(UI Team), Business Process
Group (NA, SAM, EU)
Users (NA, SAM America, EU)
Analyze Data and produce findings
of the survey
Create Draft Report
Review and comment on report
Publish final Report
Scott(UI Team), Linda (Training),
Marsha, Rajan (ADP Managers)
Scott (UI Team)
(ADP & Support)
Scott (UI Team)
Estimated Time-to-Complete
2 hours (Completed)
.25 hour (Completed)
4 hours November 18, 2012
(Creation) (Completed)
4 hours on November 19, 2012
(Review)
3 hours on November 19, 2012
(Completed)
.25 hours from November 19 – 23
(Completed)
1 week
1 week
1 week
1 week
Appendix A – Heuristic Analysis of Oracle(BI) Discoverer
Visibility of system status
Purpose Statement: The system should always keep users informed about what is going on, through
appropriate feedback within reasonable time.
Oracle(BI) Discover messages are received by the user concerning execution of queries such as
estimated time to completion or null data results. Invalid logic messages, in the creation of conditions,
calculations, use of parameters, etc. are received while workbooks are being created.
Match between system and the real world
Purpose Statement: The system should speak the users' language, with words, phrases and concepts
familiar to the user, rather than system-oriented terms. Follow real-world conventions, making
information appear in a natural and logical order.
This is a function of the Oracle(BI) Discoverer Administrator (ODA). Users have voice concerns about
this because there was no standard followed in naming Business Areas, Folders and Items. Some ODAs
did consider the users in the naming convention, but others did not. Some Business Areas, Folders and
Item names contain acronyms and initialisms of the data they represent.
User control and freedom
Purpose Statement: Users often choose system functions by mistake and will need a clearly marked
"emergency exit" to leave the unwanted state without having to go through an extended dialogue.
Support undo and redo.
There are exits and cancel options available to the user to terminate erroneous actions.
Consistency and standards
Purpose Statement: Users should not have to wonder whether different words, situations, or actions
mean the same thing. Follow platform conventions.
Across Business Areas, Oracle(BI) Discoverer offers the same interface for creating and running
workbooks. Different Applications Areas have chosen to implement different Oracle(BI) Discoverer
products initially, so for a period of time (estimated to be several months), users will need to log into
different front ends (login screens) to access workbooks. After all applications are combined, this
should not be an issue.
Error prevention
Purpose Statement: Even better than good error messages is a careful design which prevents a
problem from occurring in the first place. Either eliminate error-prone conditions or check for them
and present users with a confirmation option before they commit to the action.
Invalid logic messages, in the creation of conditions, calculations, use of parameters, etc. are received
while workbooks are being created.
Recognition rather than recall
Purpose Statement: Minimize the user's memory load by making objects, actions, and options visible.
The user should not have to remember information from one part of the dialogue to another.
Instructions for use of the system should be visible or easily retrievable whenever appropriate.
Oracle(BI) Discoverer offers a workspace that is visually pleasing and all inclusive. Oracle(BI) Discoverer
offers the user a wizard that walks the user though the mechanics of creating a workbook.
Flexibility and efficiency of use
Purpose Statement: Accelerators -- unseen by the novice user -- may often speed up the interaction for
the expert user such that the system can cater to both inexperienced and experienced users. Allow
users to tailor frequent actions.
Oracle(BI) Discoverer offers the user a wizard that walks the user though the mechanics of creating a
workbook. Cross enabled functionality, such as tabbed dialogue boxes that allow the choosing of
alternate functions regardless of the original functionality chosen, exists.
Aesthetic and minimalist design
Purpose Statement: Dialogues should not contain information which is irrelevant or rarely needed.
Every extra unit of information in a dialogue competes with the relevant units of information and
diminishes their relative visibility.
Dialogue boxes filter out information that does not meet use criteria. For example, in the calculation
dialogue box, alphanumeric items are not presented to the user, whereas numeric items are presented
for use.
Help users recognize, diagnose, and recover from errors
Purpose Statement: Error messages should be expressed in plain language (no codes), precisely
indicate the problem, and constructively suggest a solution.
Oracle(BI) Discoverer error messages are expressed in plain language, although codes are sometimes
included. In essence, among users, system mechanic knowledge varies. Therefore the error messages
contain information for all users, and this information can assist a novice user in addressing the issue
with an appropriate expert user.
Help and documentation
Purpose Statement: Even though it is better if the system can be used without documentation, it may
be necessary to provide help and documentation. Any such information should be easy to search,
focused on the user's task, list concrete steps to be carried out, and not be too large.
Oracle(BI) Discoverer help is online, searchable, cross-hyperlinked within topic and segregated by
product (Oracle(BI) Discoverer Administrator, Oracle(BI) Discoverer Plus, Oracle(BI) Discoverer Viewer,
etc.). The index is not so good, which hampers the use of a printed document, but Chapter 23, entitled
Dialog Reference is very searchable based on Keywords as is the entire help document.
Appendix B – Sample Findings of the Task-based Focus Group
Note: Unedited from original
Tracking #
Issue
BR8000002806
Create the same report from Current system and Discoverer
to confirm if information available in both databases.
BR8000002806
Create the same report from Current system and Discoverer
to confirm if information available in both databases.
BR8000002807
Create the same report from Current system and Discoverer
to confirm if information available in both databases.
US8000002840 After expanding the list of worksheets under the IMDL INTERMODAL DISPATCH REPORT workbook and clicking on
the separate worksheets to execute them, an error message is
received (See attached screen print) This has occurred
somewhat sporadically for different worksheets for multiple
users. To attachments
US8000002841 Get the attached error when trying to pull up the Outgate
TPO CTI Report. I entered "Outgate TPO CTI Report", "Outgate
TPO CTI", "Outgate TPO" and "Outgate" and received the
below for all.
TH8000002846 Create a workbook named 'Export Turnaround by Vessel' to
extract ECS data from ECODW. The needed columns are, for
example, Prv Atloc Code, Prv Xns Code, Prv Xns Dttm, Curr
Eqp No, Curr Eqp Chkd, Curr Eqp Typ, Prv Vsl Code, Prv Voy
Code, etc. Note that these column only available in the folder
'Illogical xns lcn check N'.
US8000002966 Testing the reports in Discoverer Viewer. Users ran into many
performance issues, including errors, log report times, no data
found, missing data, and time outs. The attached document
describes the issues found from each tester.
TH8000003001 Submit the report 'EQP-ECS Monthly IMP-EXP Rp - History'
with the parameters:
EQP XNS Date From 01-Aug-2012
EQP XNS Date To 15-Aug-2012
EQP XNS Code 'IRO'
Result or Comments of the User or
Usability Team
Error retrieved when tried to
generate report via Discoverer
Viewer. Report was duly generated
via Current system IMDRR27,
comparison was not possible since we
were not able to retrieve information
from Discoverer.
Error retrieved when tried to
generate report via Discoverer
Viewer. Report was duly generated
via Current system ¿ IMDRR27,
comparison was not possible since we
were not able to retrieve information
from Discoverer.
Data was retrieved from Current
system, however, nothing was
retrieved from Discoverer. (as per
attached ref file)
Intermittent error received when user
attempts to execute a workbook.
Error message received for several
workbooks
Inability to find or utilize the correct
items to create a workbook
See Attached Document
The report could be exported
successfully, but BL Shipper Name is
blank while checking in ECS
transaction, there exists 'Customer'
information.
Disposition Code 'EXP'
At Location Starts with 'THLCH%'
And export to CSV file
TH8000003004 Run report 'IMDL - CFS Cargo Report' with parameters
Vessel 'MAV2'
Voyage '0119S'
Line 'CBW'
Discharge Port 'THLCHPT'
Then export to CSV file
Example: TGHU1095707
Customer : NATIONAL STARCH AND
CHEMICAL (THAIL
The report could be run successfully.
The report can be export to CSV and
saved with no problem.
However, when export CSV and
clicked at open, no result is shown
(the screen is blank for a long time
despite the file size is only 31k.)