2006 CMBG Conference Mike Stout Spescom Software, Inc. Configuration Management For The Next Generation

2006 CMBG Conference Agenda Purpose: Generate Discussion –Some issues we face today –Some of the causes –Some potential solutions –Discussion

2006 CMBG Conference Some of Today’s CM Issues Design Basis Information –Not captured by Architect/Engineer –Recovery by A/E manpower intensive and expensive –Tribal knowledge at A/E and tribe now gone –Some conflicts with License Basis information –Margin difficult to identify Information intended to convey ‘design’ to constructor is often not adequate in detail and/or format for operations and maintenance. Drawings –Too many to maintain with available resources –Large numbers of unincorporated changes –Many drawings not verified or validated –Differing levels of user training causes demand for multiple drawings with essentially the same information. –No drawings that were intended to support Plant Operations –How to tell which information is a ‘design requirement’ and which is intended simply to be ‘helpful’.

2006 CMBG Conference More of Today’s CM Issues Master Equipment List –Data from A/E not validated or collected under QA program controls –Data incomplete –Poor understanding of data quality vs. allowable use –No simple way to get errors/omissions corrected –Engineering ‘owns’ it, Maintenance/construction ignores need to provide updates. Failure to understand or appreciate the difference between controlling containers for information (eg; documents) and controlling the content (eg; the information). ‘Cool’ technology with no commitment to update the information, combined with lack of clarity on allowed or intended use of the information. –Plant video tours an example…if not updated when modifications are done, usually advertised as ‘for information only’. Meaning, for any safety related work, must verify (walkdowns). Why spend the money for the technology if walkdowns are still required? Terminology- ie; controlled vs. configuration controlled

2006 CMBG Conference Some Probable Causes A/E’s focused on ‘design-build-get paid’ Lack of Operations/Maintenance input in design/build contracts Focus on compliance with regulations over efficient operation Regulations don’t address quality of information or use Regulation requires “Records Management” but don’t address quality of information in use for operation, maintenance and modification.

2006 CMBG Conference Some Potential Solutions Pay the A/E to capture and deliver information for operations –Put it in the contract! –Don’t get stuck using the A/E’s information system ($$$$$) Require delivery in the format/system you intend to use Better yet, require A/E to use your format/system- no data conversion! –Ensure Ops/Maintenance get input here as well as Engineering Minimize the volume of information delivered Plan ahead for training operations, maintenance to use the information format to be provided Plan for operations and maintenance involvement in validating the information received Ensure you will be managing content, not just containers.