|
|
|
|
Thanks, Peter. I've created a google docs presentation explaning how and why to set up a wiki. https://docs.google.com/presentation/d/102JrYJVhqU1BmjqqT5a5BYl5_9il1Mdr53gEXRPyT4c/present?ueb=true#slide=id.p Regards, ------------------------------------------- Wayne Eddy Strategic Asset Planning Coordinator City of Whittlesea BUNDOORA MDC VIC -------------------------------------------
Show Original Message
-------------------------------------------
Original Message:
Sent: 25-02-2013 22:50
From: Peter Buchanan
Subject: Asset Systems
Wayne
I applaud the notion of documenting "things that you do", In many circumstances key people leave the organisation and leave a void in local knowledge and systems. This is not to say that if we did it before like this , we need to continue do it the same way . but at least it is a starting point for the incoming.
Would a personal Wiki or Group Wiki be a good way to document procedures?
If so. How to set it up?
Peter Buchanan
Senior Technical Officer -Assets
Goondiwindi Regional Council QLD
-------------------------------------------
-------------------------------------------
Original Message:
Sent: 24-02-2013 16:47
From: Wayne Eddy
Subject: Asset Systems
Robert makes an interesting point about the advantages to an organisation of staff staying for many years.
I'd like to add to that thought. I think it would be super valuable to an organisation to have staff stay for a long time, AND during that time continually document their knowledge and learnings in way that would make that knowledge easily available to their eventual replacement.
I personally think that the best way of retaining the knowledge of long serving and knowledgable staff is to have them continuously contribute to a "wiki-based encyclopedic knowledge base", but I'd be very interested to hear any other ideas members of this forum have for retaining this sort of knowledge.
I'd like to challenge those of you that have been at an organisation for more than 5 years to respond to this thread and tells us what systems your organisation have in place to retain asset management and other knowledge, and what you in particular have done to ensure your knowledge stays with your organisation after you depart?
Regards,
-------------------------------------------
Wayne Eddy
Strategic Asset Planning Coordinator
City of Whittlesea
BUNDOORA MDC VIC
wayne.eddy@whittlesea.vic.gov.au
-------------------------------------------
-------------------------------------------
Original Message:
Sent: 23-02-2013 21:37
From: Robert Molyneux
Subject: Asset Systems
I suggest Darron and Terence are both right.
You need to:
- understand and disseminate what "asset management" is (for example by perusing the IIMA "bible");
- understand what the various corporate systems do;
- map the functions of asset management onto the various systems;
- decide on which systems handle the functions best;
- learn how to use them and share with others within the organisation who does what where and when...
Then
stay with the organisation for many years..
That is, critical components to the omelet are skilled people, sharing views across disciplines (especially engineering / technical and financial), and being retained, developed and challenged by the organisation.
Examples of system views include:
the GIS system holds an object register (of a pipe network) and where the objects are located (you need to distinguish between "objects" and "assets" - the bits and pieces of a pipe network are not assets per se, they add up to an asset) - the main function is to be able to easily see where objects are, and to use "spatial operators" to do useful things like "where are pipe breakage likely to occur, and which customers will be worst affected".
the CAD system holds another object register (of pipe networks AND treatment plants / works) which allows for knowing what parts of the Mech / Elec / Civil are in place, what they are (dimensions, brand, original supplier, current supplier...).. Ideally it should be able to easily handle multiple sources / suppliers, and to accurately show designed versus actual construction - and to feed the GIS with "future proofed" reliable data including connections between objects.
the Computerised Asset Management System (CAMS) holds another object register that shows what systems, subsystems, facilities and components are in place to deliver essential business / customer needs (deliver clean water, take away waste water, carry vehicular traffic, house staff and facilities...). The "aspatial" data (what is it, what condition is it in) may be displayed within the GIS, but generally GIS databases are not / have not been very good at this sort of data management.
the Finance System / Works Management System holds another object register that records where the money has gone, and some view of where it will go into future. Broadly, it needs to be able to roll up the detailed registers into summaries - "what is our pipe network worth, dissected by location and function" and how much will it cost in future, dissected by location (industrial versus residential) and function (industrial versus commercial versus domestic) - in other words, Business Intelligence functionality including spatial operators.
All of these registers of objects need to be able to be reconciled / matched to some degree, depending on business requirements and cost / benefit of "data custodianship / data stewardship" versus pro-active use of the data to deliver good customer service.
It is possible that a small new Council could have a single system to rule the world, and in the darkness bind them - but it is more likely that Terence's list of distinct / more or less incompatible "modules" will be the situation, and very likely that all the money the Council had or will have has already been spent on them.
-------------------------------------------
Robert Molyneux
Consultant
Drehmex Sales & Services Pty Ltd
TEMPE NSW
-------------------------------------------
-------------------------------------------
Original Message:
Sent: 23-02-2013 01:07
From: Darron Passlow
Subject: Asset Systems
Terence
No, you leave the systems you have to do what they were designed to do.
You purchase (not build) a proven asset management system and get stuck into bringing all your asset data together in one purpose built application. This is the only way to go if you are serious about doing proper AM.
You then may need to link to other systems you have to avoid duplication of data (and particularly of entry duplication).
Regards
-------------------------------------------
Darron Passlow
Asset Management
Pittwater Council
MONA VALE NSW
-------------------------------------------
-------------------------------------------
Original Message:
Sent: 21-02-2013 17:30
From: Terence Maru
Subject: Asset Systems
Hi guys,
I have found the most cost effective way to implement an Asset Management system is to build the processes on the systems the organization has already operating. E.g. GIS, AutoCAD, SQL, Fixed Asset Register, General Ledger, Chart of Accounts, Stakeholder/Customer Register, Complaints Register, As-built Register< Risk Register.
The goal is to create a single simple repository. This is hard when Asset Management covers all aspects of the organization and each department have their own systems, processes and protocols.
Terence Maru
Asset Engineer
Mackay QLD
-------------------------------------------
|
|
|