Be the first to like this
This slide set summarizes my work at Tenix Defence from around 1992 through 2002 to manage the authoring and delivery of maintenance documentation and engineering technical data to support life-cycle management of the 10 ANZAC frigates Tenix built for the Australian and New Zealand Navies and more than 300 M113 light-armored vehicles rebuilt as-new for the Australian Army. Today (in 2013) this is still a state-of-the-art application of the content management technology. So far as I know, the full benefit of this technology (as described in this 2002 presentation) has not yet been realized anywhere in the world.
Arguably, implementation of this technology played a major role in the successful completion of the ANZAC Ship Project 17 years after its stringently fixed-price contract was negotiated in 1989. Finished on-time, on budget, with every ship delivered on-time to happy customers and a healthy corporate profit. Unfortunately, Tenix Defence management failed to understand how this system worked, and chose to implement new, supposedly less expensive technology they thought they understood for their next major project. As a consequence of this choice and the failure to transfer human knowledge developed in the ANZAC Project the company’s performance on their next large project (but still less than 10% the size of the ANZAC Project) was so bad that Tenix Defence was closed and its assets sold to the highest bidder. See Hall, W.P., Nousala, S., Kilpatrick B. 2009. One company – two outcomes: knowledge integration vs corporate disintegration in the absence of knowledge management. VINE: The journal of information and knowledge management systems 39(3), 242-258 - http://tinyurl.com/yzgjew4; and Hall, W.P., Richards, G., Sarelius, C., Kilpatrick, B. 2008. Organisational management of project and technical knowledge over fleet lifecycles. Australian Journal of Mechanical Engineering. 5(2):81-95 - http://tinyurl.com/5d2lz7.