This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Subject: Whose job is it to produce Reports?
This has always been a major subject of interest by the project leads during implementation. The success of any EAM system depends heavily on the ability to extract useful information.
Assuming the report engine was successfully installed then you have embedded standard reports which can be run from within the application. But it is a misconception to think that these delivered (O.O.B.) reports will always meet your exact needs. Therefore you will need to create new reports (or alter existing std reports).
But ... who is responsible for designing analytical reports, and coding/testing? Note: I am not talking about the basic, single-line reports. Is it the IT Department - or - the user community?
To be fair, maybe we should qualify the type of reports from simple to complex.
A. Simple View List download
B. Adhoc do-it-yourself (with 7x)
C. Alter existing O.O.B. Reports (need knowledge in report editor)
D. Write new (ditto above)
The last category could be sub-divided into additional options:
1. ODBC: Use Excel Pivot tables
2. ODBC: MS Access
3. Use the standard reporting tool
4. Use some other external reporting tool
But where many administrators fall short is on the design/creation of advanced analytical reports which are more complex. Examples of these are backlog growth trending, time-in-status, failure analysis with graphical drilldown capabilities, and automated resource-leveled weekly scheduling.
To answer the original question, I think both groups need to have a shared responsibility. Users should learn SQL basics to work comfortably with Saved Queries AND learn Excel Pivot table creation. Plus the IT Dept should accept responsibility for coding the complex reports.
> what are your thoughts?
w/br
John Reeve
Manager, Practice Leader Maintenance and Reliability Solutions
Cell: 423 314 1312
http://www.linkedin.com/pub/john-reeve/11/644/9b2
I agree that report writing is a joint venture, but lean toward the responsibility lying with the user community or super user community. I am a Maximo 7 user and have very limited knowledge of IT (my IT support will second that) But, it is my data, I choose how to populate the fields, how to schedule and code the many types of work orders.
While it helps to have IT understand our work process, I am the maintenance/calibration expert. I am the one who should know which KPIs are useful and which are noise.
Yes, it will behoove me to learn some SQL and some of the structure behind our database. Then when needed, I can more accurately ask IT for what I need. And we can work together to get appropriate results.
--- In MAXIMO@yahoogroups.com, "John" <planschd@...> wrote:
>
> Subject: Whose job is it to produce Reports?
>
> This has always been a major subject of interest by the project leads during implementation. The success of any EAM system depends heavily on the ability to extract useful information.
> Assuming the report engine was successfully installed then you have embedded standard reports which can be run from within the application. But it is a misconception to think that these delivered (O.O.B.) reports will always meet your exact needs. Therefore you will need to create new reports (or alter existing std reports).
>
> But ... who is responsible for designing analytical reports, and coding/testing? Note: I am not talking about the basic, single-line reports. Is it the IT Department - or - the user community?
> To be fair, maybe we should qualify the type of reports from simple to complex.
> A. Simple View List download
> B. Adhoc do-it-yourself (with 7x)
> C. Alter existing O.O.B. Reports (need knowledge in report editor)
> D. Write new (ditto above)
>
> The last category could be sub-divided into additional options:
> 1. ODBC: Use Excel Pivot tables
> 2. ODBC: MS Access
> 3. Use the standard reporting tool
> 4. Use some other external reporting tool
>
> But where many administrators fall short is on the design/creation of advanced analytical reports which are more complex. Examples of these are backlog growth trending, time-in-status, failure analysis with graphical drilldown capabilities, and automated resource-leveled weekly scheduling.
>
> To answer the original question, I think both groups need to have a shared responsibility. Users should learn SQL basics to work comfortably with Saved Queries AND learn Excel Pivot table creation. Plus the IT Dept should accept responsibility for coding the complex reports.
>
> > what are your thoughts?
>
> w/br
> John Reeve
> Manager, Practice Leader Maintenance and Reliability Solutions
> Cell: 423 314 1312
> http://www.linkedin.com/pub/john-reeve/11/644/9b2
>