421 672 Management Of Technological Enterprises (2008 Lecture 2)
•Télécharger en tant que PPS, PDF•
1 j'aime•465 vues
![421-672 Management of Technological Enterprises Managing Knowledge in Technological Enterprises (II) – Knowledge Engineering in the Organisation William P. (Bill) Hall (PhD) Evolutionary Biology of Species and Organizations http://www.orgs-evolution-knowledge.net Ex Documentation and KM Systems Analyst Head Office Tenix Group Williamstown, Vic. 3016 National Fellow Australian Centre for Science, Innovation and Society Melbourne University Uni Office: ICT 3.67, 111 Barry St., Carlton Phone: +61 3 8344 1488 (Thurs-Fri) Email: [email_address] 1 April 2008 People Process Infrastructure Organizational knowledge Leave one of the legs off, and the stool will fall over](https://image.slidesharecdn.com/421672managementoftechnologicalenterprises2008lecture2-13081190790195-phpapp02-110615012720-phpapp02/85/421-672-Management-Of-Technological-Enterprises-2008-Lecture-2-1-320.jpg)
![What are organisations? ,[object Object],[object Object],ORGANISATION — People, Machines — Living Cells, Parts ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
En vedette
En vedette (20)
Similaire à 421 672 Management Of Technological Enterprises (2008 Lecture 2)
Similaire à 421 672 Management Of Technological Enterprises (2008 Lecture 2) (20)
Plus de William Hall
Plus de William Hall (20)
421 672 Management Of Technological Enterprises (2008 Lecture 2)
- 1. 421-672 Management of Technological Enterprises Managing Knowledge in Technological Enterprises (II) – Knowledge Engineering in the Organisation William P. (Bill) Hall (PhD) Evolutionary Biology of Species and Organizations http://www.orgs-evolution-knowledge.net Ex Documentation and KM Systems Analyst Head Office Tenix Group Williamstown, Vic. 3016 National Fellow Australian Centre for Science, Innovation and Society Melbourne University Uni Office: ICT 3.67, 111 Barry St., Carlton Phone: +61 3 8344 1488 (Thurs-Fri) Email: [email_address] 1 April 2008 People Process Infrastructure Organizational knowledge Leave one of the legs off, and the stool will fall over
- 8. "Living knowledge“ : source of organisational knowledge Vines, R., Hall, W.P., Naismith L. 2007. Exploring the foundations of organisational knowledge: An emergent synthesis grounded in thinking related to evolutionary biology . actKM Conference, Australian National University, Canberra, 23-24 October 2007.
- 10. Cycling between W2 and W3 to build personal knowledge
- 15. L. Greiner 1998. Evolution and revolution as organizations grow. Harvard Business Review May-June 1998 creativity direction delegation coordination collaboration leadership autonomy control red tape -???- AGE OF ORGANISATION SIZE OF ORGANISATION Small Young Large Old organisatioal revolution evolutionary growth
- 18. Managing contractual knowledge • 20 - 50 year lifecycle Project A Design Study Review, edit, signoff Negotiate Review, negotiate, amend Project A Prime Contract RFT and Bid Review, edit, signoff Project A Bid Documents RFQs Bids Negotiations Project A Subcontracts Review, negotiate, amend Project A Procedures, Design Docs Review, edit, signoff Project A Support Documents Project B Design Study Review, edit, signoff Project B Design Study Review, edit, signoff Project B Design Study Review, edit, signoff Operational experience
- 22. Document Assembly - defined Document assembly is the process by which an instance document is produced from a template document. Exari™ Software TEMPLATE DOCUMENT INSTANCE DOCUMENT A template document is a document which may contain certain blanks and pieces of optional text. It captures what is common, and what may differ, between a set of similar instance documents. An instance document is a document created to meet a particular need in some transaction. Input from a person or database is required in order to fill in the blanks and choose between the optional texts.
- 26. Tenix/Navy architecture developed in Melbourne for managing ANZAC Ship support knowledge DESIGN / ENG PRODUCT DATA MANAGEMENT • Product Model • CAD / Drawing Mgmt • Config Mgmt • Eng Change • Workflow Process Control • Doco Revision & Release DOCO CONTENT MANAGEMENT DOCUMENT AUTHORING LSAR DATABASE LOGISTIC ANALYSIS TOOLS (prime) PRODUCT CONFIG MANAGEMENT • Product Model • Drawing Mgmt • Config Mgmt • Change Request • Workflow Process Control • Doco Revision & Release MAINTENANCE MANAGEMENT • Schedule • Resource Reqs • Procedures • Completion • Downtime • Resource Usage RECORDING REPORTING ANALYSIS TOOLS (prime) MRP SYSTEM • Plan • Fabricate • Assemble SUPPLY SYSTEM change request config change doco change ECO change effected doco change order released doco change config changes EC / doco change request maintenance history doco server Analysis & optimisation orders receipts change task doco change shared systems? data change & Release UPDATE MAINT DATA / PROCEDURE UPDATE CONFIG Navy Systems Crossbow Validates and i ntegrates data across 15 legacy systems TeraText Content management AMPS Navy's maint mgmt CSARS Provides corrective feedback from AMPS into supplier's knowledge development activities
- 29. This is what the revolution looks like now! MRP = Mfg. Resource Planning CAD = Computer Aided Design LORA = Level of Repair Analysis RAM = Reliability & Maintainability LSA = Logistic Support Analysis
- 32. Content Management in the M113 Upgrade Users Manual This is section 1 of the document This is the Work File System Chapter Section Document PDF Fragment Fragment Graphic Storage and Dis/assembly Rules WEB Protocol Save Edit
- 33. The cost/benefit equation for content management vs DMS Implementation Initial document set Proliferation of configurations In-service maintenance Cost Time Traditional DMS Note: CMIS cost is for first project only. New CMS
Notes de l'éditeur
- Explicit knowledge for a long lived project is expressed in its documentation. Project documentation is developed through a number of phases, and at least for defence engineering projects the same information and knowledge is often contained in many different documents, in both similar contexts and in different contexts. A major issue is to manage this redundant content consistently over the life-cycle in relation to changing product configurations and to reflect project experience. The remainder of the presentation discusses architectures and tools we have implemented in Tenix to do these things.
- Probably the most problematic and costly area for knowledge flow through the project cycle is in the request and bidding stage. The diagram explains why. Beyond this, it must be understood that the inefficiencies in each and every bid have to be amortised and charged by suppliers to the projects they actually win. Every supplier will lose several bids for the few that are actually won.
- The ANZAC Ship Alliance is a consortium formed to provide in service support for the Australian ANZAC Frigates. It is comprised of Tenix Defence (responsible for platform and mechanical systems), SAAB (responsible for the combat and electronic systems), and the ANZAC SPO (the RAN organisation responsible for managing logistic support for the class. In this structure, Tenix is responsible for managing engineering changes and the related technical data and documentation affected by the engineering changes. This diagram shows the technical data/content repositories used to control and manage the knowledge required to provide in-service support for the ANZAC frigates. Tenix's systems are shown in red, client's systems in blue. There are four core systems that need to be considered in optimising total life-cycle cost: engineering change/configuration management, document and content management, maintenance management, and a maintenance audit and costing system to feed back requests for change based on in service operational experience. Here we put the spotlight on the two systems Tenix has implemented to close the circle between the fleet technical data/documentation package , the AMPS maintenance management system, and the need to analyse the fleet's in-service operational experience to minimise continuing support costs. TeraText (AKA SIM) system is the document and content repository that minimises costs to maintain and deliver accurate and configuration specific maintenance documentation. CSARS provides analytical capabilities to help identify systems and components contributing disproportionately to downtimes and support costs.