Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

New Data Source for Activity Hubs

Ui expand
titleLong Term Solution

Long Term Solution

  • What:
    • Data Source is added to the applicable Activity Hub(s)
  • Pros:
    • Data is blended with key attributes of other Activity Hubs
    • Top performance in report speed
    • DAGC  governance and support
    • Allow for data to be used by data integrations
    • Field names follow AH naming standards
    • Underlying structures follow BIA development standards
    • ITS-BIA support for data issues
  • Cons:
  • How:
Ui expand
titleInterim Solution

Interim Solution

  • What:
    • Connect BI Tool directly to data source
    • Report developer creates Tableau data source or Cognos data module
    • Report developer then creates reports off the Tableau data source or Cognos data modules
  • Pros:
    • Allows report developers to build Cognos or Tableau report prior to the data source being added the applicable Activity Hub(s)
    • Once the data source is available in the applicable Activity Hub(s), the reports can be re-pointed
    • Can be blended with Activity Hub views (may reduce speed of report)
    • Works best with on-prem servers
  • Both Pro & Con:
    • Maintenance of Tableau data source or Cognos data module is performed by Report developer
  • Cons:
    • May not be available for applications located in the cloud or Amazon Web Services (AWS)
    • A poorly written report can negatively impact the performance of the data source
    • Does not allow for data to be used by data integrations
    • May not use AH naming standards or BIA development standards
  • How:
Ui expand
titleShort Term Solution

Short Term Solution

  • What:
    • Upload data via Excel or CSV to Cognos server directly or Tableau server directly
  • Pros:
    • Can be used immediately
    • Can blend with Activity Hub views (may reduce speed of report)
    • Good solution for historical data or data that rarely changes
  • Cons:
    • Must be manually uploaded by report developer
    • Does note allow for data to be used by data integrations
  • How:Instructions Coming Soon

    Moved to Adding New Data for Blending in Cognos or Tableau

    Monthly Enhancement Process

    1. Customer submits an enhancement request to busintel@ucsd.edu.
    2. BIA and the SME group schedules which enhancements to include in the monthly release based on priority and level of effort, grouped by view.
    3. BIA makes the enhancements to the EAH views, Tableau and Cognos.
      1. BIA completes data validation
    4. BIA releases the enhancements into User Acceptance Testing (UAT) for 1 week of customer testing.  After which UAT deletes the UAT items as they are no longer needed.
    5. Finding no issues after 1 week, BIA releases the enhancements to Production.


    Monthly User Acceptance Testing (UAT)

    UAT is a time for report developers to complete their own testing scenarios against any enhancements being release.  During UAT field names, folder names and aggregations may change quickly and break reports (AH Changes That Break Report or Column Group Connections). 

    Reports using data in UAT should not be shared with customers.

    AH User Acceptance Testing (UAT)


    Hana QA Duty Cycle

    A duty cycle has been implemented for Hana QA.  During this time, Hana QA will not be available.  Please schedule your UAT work around this duty cycle.

    • Hana QA will not be available from 7pm-5am nightly
    • Hana QA will not be available Saturday and Sunday
    • Data loads will occur from 5am-10am on weekdays

    Monthly Release Notes

    Notification of UAT start and end dates, what is included in UAT and when objects are moved into Production are shared via Release Note emails sent to the Community of Practice (COP) mail lists for each associated Activity Hub. 

    You can sign up for COP mail lists here by emailing busintel@ucsd.edu.