eFundi Reporting (Jasper BI)

Project Description

Request was initiated by Gerda Schilling

This project forms part of the NWU internal Jasper reporting project set and is aimed at providing certain operational reports for the eFundi system.

 

Documents

No documents at this time.

Project Progress

100%

Project Timing

  • Start
    Mar 31 2015
  • End
    Nov 01 2016

03/31/2015 11/01/2016

100%

Overall Project Completion

  • 20%
  • 60%

100%

  • 40%
  • 80%

1. Groundwork and Determine Business Need Complete 100% Tasks 0 / 0

100%
Description

2. Analysis & Requirements Elicitation Complete 100% Tasks 3 / 3

100%
Description

3 of 3 completedTasks

  • Requirements Elicitation
  • Analysis of Requirements
  • Scope Definition

3. Data Modelling in ODS (Design and Implementation) Complete 100% Tasks 0 / 0

100%
Description

4. ETL Development Complete 100% Tasks 0 / 0

100%
Description

The task involved all the efforts required to get the ETL in place for extracting data from the source systems, processing and transforming that data to fit in the ODS model and then loading it into said model.

NOTE: Ticket#1095805 was created to address the infrastructure requirements for this process. The current ETL process catered for Oracle and now has to be adjusted to also cater for MySQL. Part of this change requires a shared disk space between source system servers and the various ODS service of each environment for Jasper Reporting.

5. Development of Formal Reports Complete 100% Tasks 0 / 0

100%
Description

6. Implementation, UAT and Data Validation Complete 100% Tasks 0 / 0

100%
Description

7. Go Live Complete 100% Tasks 0 / 0

100%
Description

Project Discussion 9 Responses to eFundi Reporting (Jasper BI)

  1. > Development efforts based on project scope completed
    > All reports are live on Jasper Production

    > Changes or issues will be handled as support
    > eFundi DB upgrade does not fall within the scope of this project
    > It is up to business how they want to expose the service to end users

    December 4, 2016 at 12:07 pm
    JEAN RAATH
  2. > UAT is still ongoing.
    > Various data issues with the ETL and resource limitations has pushed back implementation date.
    > Implementation timelines depend on the business owner but development team is pushing for 1 Nov 2016

    October 24, 2016 at 6:03 pm
    JEAN RAATH
  3. UAT ongoing by process / business owner

    September 22, 2016 at 11:27 am
    JEAN RAATH
  4. Development efforts for agreed upon formal reports complete. Awaiting UAT by PO / Business

    August 5, 2016 at 3:46 pm
    JEAN RAATH
  5. Development on EFUNBI001, EFUNBI002, EFUNBI003 and EFUNBI004 have been completed. EFUNBI005 should be completed within the next week. The completed reports have been made available for UAT by the Product Owner.

    July 3, 2016 at 7:48 pm
    JEAN RAATH
  6. Development in Progress. EFUNBI001, EFUNBI002 and EFUNBI005 in DEV.

    May 12, 2016 at 2:52 pm
    JEAN RAATH
  7. The planned timelines for the project has been moved out to March / April 2016. Due to the impact of waiting for shared disk space we’ve had to forego the availability of a 3rd party resource which has impacted our work effort. There were also additional complications in the requirements and data which has now been clarified but which does have an impact on the complexity of scope. Development work on the ETL has started and we’ve made good progress with the data modelling. Work efforts will continue when all resources return on 11-01-2016.

    December 18, 2015 at 8:20 am
    JEAN RAATH
  8. We’re currently waiting for shared disk space to start modifying the ETL process. A request was logged on 6/11/2015 for this. The initials report list has been finalized and as soon as the required architecture is in place we can continue with efforts on this project.

    November 20, 2015 at 3:47 pm
    JEAN RAATH
  9. INCLUDES the project request (15-31): Sakai reporting in Jasper. Request was ‘retracted’.

    October 22, 2015 at 11:29 am
    YVETTE LABUSCHAGNE

Leave a Reply