Skip to main content

The APQC Process Classification Framework

The APQC Process Classification Framework (PCF) is another tool we can use when reviewing administration processes, particularly for support functions such as HR or Finance. The PCF is a cross-industry  taxonomy of business processes, intended to allow the objective comparison of performance within and among organizations.  Although it models commercial businesses rather than universities, it includes a section on management and support services covering HR, Finance, Estates, External Relationships, and so on.

Each section is basically a hierarchical catalogue of business functions.  To take Finance as an example, the framework includes top-level items such as "Perform revenue accounting", "Perform general accounting and reporting", "Process payroll", and so forth.  Each of these are broken down into sub-tasks, such as "Report time", "Manage pay" and "Process payroll taxes".  The image below illustrates the structure of the framework, showing the first page of the section on HR.

In the context of Enterprise Architecture at the University of Edinburgh, the PCF provides a useful baseline for the aspects of the business process that we should consider.  At simplest, it is a basic checklist to help ensure that we don't overlook aspects of the business process.  By using the PCF, we take advantage of the experience that the authors have encoded in the framework to guide our own reviews.  There is nothing complicated about this; it is just a very useful reference point.


Comments

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...