Developing a Dashboard to Aid in Effective Project Management

  • 1,725 views
Uploaded on

Presentation at the SAS Global Forum by Ali Yorkos and Maureen Murray; SAS Developers, University of Central Florida

Presentation at the SAS Global Forum by Ali Yorkos and Maureen Murray; SAS Developers, University of Central Florida

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,725
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
33
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Requested by IR Dept Management to enhance tracking and coordination of technical support activities. IR Management defined the KPI with varied and ‘Alerts’ and ‘Need to Review’ items such as: Alert example- a project that stays in User test status for > 10 days or Need to Review example - projects due with a week. Initial Design requirements: a mixture of text Alerts and graphical data visualizations with some detail data views.
  • – this is the end result of our development effort – this is our CMS Dashboard surfaced by the SAS BI Dashboard tool Due to the short amount of time we have we wanted to show the result of our development early into this presentation – the rest of the presentation how we achieved this result and answer the why to the technical choices we made. Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Background – management viewed this project as an opportunity for 2 SAS programmers to gain analytic and technical experience in Dashboard development. So both Ali and were assigned the project. For the initial Dashboard we developed in parallel using the first technical approach after feedback from management of the first dashboard we spilt up the data visualizations and used the second technical approach. When we started development, the SAS BI Dashboard tool had not yet been released. Therefore, we referred to the SAS/GRAPH Dashboard samples available at support.sas.com for development ideas and techniques. Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Common to each technical approach was the data preparation, the computations required to determine the Alerts etc… and our use of the SAS Annotation facility to enrich the graphs with Alerts or indicate areas of concern.. Copyright © 2007, SAS Institute Inc. All rights reserved.
  • The source of our data is several PS/Oracle tables from the university’s Computer Services Dept in-house developed Project Management System. A single de-normalized dataset was created from these 7 Oracle tables. To support the requested data visualizations 5 SAS datasets were then created from the de-normalized table. Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Our management’s feedback requested different data visualizations and decided each visualization should include drill down capability to enhance the dashboard with detail data availability in conjunction with the high level at a glance functionality. Also, at this time SAS released the Dashboard tool which worked with the SSL protocol required by the university’s security policy for web/portal development.
  • We used SAS/Graph, Stored Processes and the SAS BI Dashboard tool. Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Read slide
  • Copyright © 2007, SAS Institute Inc. All rights reserved.
  • Copyright © 2007, SAS Institute Inc. All rights reserved.

Transcript

  • 1. Developing a Dashboard to Aid in Effective Project Management Ali Yorkos and Maureen Murray SAS Developers, University of Central Florida
  • 2. Introduction CMS Dashboard Project
    • Dashboard - to enhance Project Management
    • KPI(s) identified by Management
    • Data Visualizations – High Level & Detail Views
  • 3. UCF CMS Dashboard
  • 4. Technical Development Approaches
    • First – Tools
        • Enterprise Guide
        • SAS/GRAPH
        • PROC GREPLAY
    • Second – Tools
        • Enterprise Guide
        • SAS/GRAPH
        • Stored Processes
        • SAS BI Dashboard
  • 5. Common Elements of each Technical Approach
    • Table Development and Structure
    • Computed Fields for Alerts
    • Annotation facility
  • 6. Table Structure and Relationships
  • 7. SAS/GRAPH Development Annotation Feature
  • 8. SAS/GRAPH Development Using the Annotated Dataset
  • 9. First Technical Approach
    • SAS/GRAPH Development
    • PROC GREPLAY
    Bar size 2048
  • 10. SAS/GRAPH Development
    • Created in SAS Enterprise Guide 4
    • Vertical and Horizontal Bar Charts, Pie Charts
    • Modified SAS code for more robust graphs
    • Used .GIF format
  • 11. PROC GREPLAY Procedure 0 1 3 5 2 4
  • 12. PROC GREPLAY Procedure
  • 13. Initial Dashboard Output
  • 14. Why We Switched Development Tools
    • Management feedback from first design
      • Requested different data visualizations
      • Drill Down Capability requested for most data visualizations
    • Release of SAS BI Dashboard to use with the SSL Security Protocol
  • 15. Second Technical Approach
        • Technical Design
        • Develop all Top Level data visualizations using ONLY the BI Dashboard Tool
        • But
        • our functional design required the use of Stored Processes to create Dashboard Indicators.
  • 16. Why? – Stored Processes Bar Graph with Reference Line Bar Graph - Stored Process
  • 17. Second Technical Approach
    • SAS/GRAPH
    • Stored Processes to create Dashboard Indicators
    • SAS BI Dashboard
  • 18. Manage Dashboards Manage Indicators
  • 19. Dashboard Properties Page Assembly Indicators into a Dashboard Portlet
  • 20. UCF CMS Dashboard
  • 21. Pros / Cons of Tool Sets
    • GREPLAY
    • Requires precise coding of coordinates for Indicator Placement
    • No user customization available
    • On-going Maintenance may require modifications to both Indicator generation and placement code
    • .GIF Images were easier to line up but not as clear as ActiveX
    • SAS BI Dashboard
    • Easy to use Web based interface for Indicator Placement
    • User customization allowed
    • On-going Maintenance only requires modifications to Indicator generation code
    • ActiveX Images were clearer and provided ‘mouse over’ support
  • 22. UCF CMS Dashboard
  • 23. Contact Information
    • Presentation Online at http:// www.iroffice.ucf.edu/presentations/index.html
    • Office of Institutional Research
      • Email: [email_address]
        • Ali Yorkos, [email_address]
        • Maureen Murray, [email_address]
      • Web: http:// www.iroffice.ucf.edu
      • 12424 Research Parkway, Suite 215
      • Phone: (407) 823-5061 Fax: (407) 823-4769
  • 24. Copyright © 2007, SAS Institute Inc. All rights reserved. SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration.