Definition of EUC 1559
Anyone out there have a definition for End User Computing (EUC) - we have been struggling with the definition for an EUC versus an Application and about the only thing all sides agree on is the an EUC is not fully IT supported. However, than what do you consider SAS script that business created that runs on an IT supported Unix box?
Everyone and their uncle seems to have a different definition but we can’t be the only company out there struggling with this.
All help is appreciated
Hi and welcome to the forums
Some quick thoughts on this:
- As a starting point, I saw some good initial references in a Google search with the keyword of ‘End User Computer’
- I’ve always simply viewed these complementary processes as ‘non-production’ from an IT standpoint.
- Hopefully, management has emphasized the need for users to balance back to production controls , so that there are assurances the information is accurate.
- On the mainframe side, our users have developed queries and reports with Easytrive, SAS, and Focus in the past. Excel, Access, Toad (for Oracle), and other products provide these capabilities in the client/server world. Encourage users to document, use meaningful naming conventions, IT standards where practical, and other best practices.
- End-user computing should not be exempt from standards, or if the ‘power user’ leaves the company it’ll be difficult to support the process.
- Where there are SOX related financial reports or queries done by the end-user, the IT area may have to ‘reign these in’ and get them under better balancing controls and standards – where it’s practical to do so.
- It’s also beneficial to have each major area inventory these complementary reports and applications for Disaster / Recovery, SOX compliancy analysis, and other corporate needs.
All good comments. However, what is your definition of EUC or End User Computing
This is indeed difficult to define and ‘non-production’ is about the best definition I can think of …
EUC = Any application or reports that are developed outside of the IT production standards framework and are solely supported outside of it as well.
Ok - if one goes with that though - what is to stop the business units from running there own little ‘IT shops’ ? A business unit could decide to build it’s own application and totally not involve IT - would that application (running on multiple windows servers with oracle on unix servers for database) then also be considered an EUC?
The definition we finally came up with was ‘any application developed using MS Office tools or similiar’ …
Any better ideas?
lol - you make some good points and they are realistic, as I’ve seen this in the past and it’s a support nightmare
what is to stop the business units from running there own little ‘IT shops’?
Nothing, unless senior management puts it’s foot down and recognizes there might be issues in the future, if this process goes unchecked. Although short-term the business area will receive needed IT services quickly, it could backfire if it’s not done properly. For example, in some cases I’ve seen there can be a lack of documentation, backup/recovery, standard use of software, a lesser focus on balancing controls, the EUC developer leaves the company, etc … If it’s a SOX application, then most likely it would need to be reigned back into the formal IT support infrastructure.
A business unit could decide to build it’s own application and totally not involve IT - would that application (running on multiple windows servers with oracle on unix servers for database) then also be considered an EUC?
A good question … This might be seen as a decentralized IT approach, if it were staffed with IT professionals (e.g., developers, server admins, DBA types, etc). If it’s canned software and supported solely by users, it might be seen as a more advanced or robust EUC computing solution.
The definition we finally came up with was ‘any application developed using MS Office tools or similiar’
That’s a good definition and I think each company could have it’s own way of identifying EUC v. formal IT based systems. For example, we have IBM mainframe applications and users write SAS or Easytrieve programs for adhoc or even routine reports.
Any better ideas?
I’ll take a 2nd try at this below
EUC = The development of reports or applications using tools like MS Office, reportwriters, query tools, etc. by business professionals outside of normal IT development and control process.
EUC = The development of reports or applications using tools like MS Office, reportwriters, query tools, etc. by business professionals outside of normal IT development and control process.’
I LIKE that one. … what really floored me when I was first looking was the fact the EUCs are something that all companies have to remediate for and yet when I searched McKinsey, Gartner, Hoover’s, etc… I couldn’t find a single definition.
Thanks for your input.
Denis last edited by
I also like that definition Harry. Think I’ll use it. Where do I send the royalty cheque
lol - Denis, instead I’ll give you all these EUC systems we have at work as a free gift … Actually one of my current assignments has been to analyze and reengineer a major EUC application into a production IT system (with 00’s of regularly scheduled mainframe and server programs). There’s benefits to the EUC process for business areas, as long as they don’t go too far and create an ‘island of automation’ that can’t be easily supported in the future.