Configuration Management Benchmarking Group Conference June 6 – 9, 2004 Kansas City, MO © 2004 CMBG Characteristics of a Good Calculation Program Presented By: John Rothe SSES
Characteristics of a Good Calculation Program 1.There is an identifiable set of calculations to be maintained 2.Tools/data are effective in identifying the affected calculations when making a change 3.Calculations are easy to retrieve 4.Methods for revising calculations are efficient and effective
Characteristics (Continued) 5.Calculation format/content is consistent 6.There is clear ownership of calculations at the appropriate level 7.Errors are minimized in calculations 8.There is a process for notifying users of existing errors in calculations
Characteristics (Continued) 9.There is a clear status control imposed on calculations 10.Calculations are electronic and word searchable (enhancement) 11.Process requires approved calculations prior to design change package approval
Characteristics (Continued) 12.New and revised calculations are evaluated for potential impact and implemented through an appropriate change process
One approach: Identify target areas
7. Errors are minimized Historical errors, new errors Utility 1 - Anything prior to certain date is suspect and requires a re-verification Utility 2 – with tier 1 (Design Basis) if it hasn’t been re-verified in last 2 years requires re- verification. Sanity check when using a calculation
Errors are minimized Calculation Update program Margin review Validate against operating procedures Electronic media Re-validate classification Consolidate if possible Re-verify or not?
There is a clear status control imposed on calcs Approved / pending Limited edition calc Interim revisions for mods Committed (mod) final (as-built)
List of discussion topics Timeliness of change incorporation Handling of margin in calc. Ownership Wants to know how #11 can really be done Best practices to identify affected calcs. Cultural resistance to documenting the calc. per ANSI N What are the challenges? Issues with aging work force and tribal knowledge
List of discussion topics Future generations able to use calcs Source of basis difficult to determine Third party calc handling Sequencing & calc updating Cross ref’ing calcs to calcs, procedures Tracking inputs and outputs Old Standards –Where are they? Backlog reduction Build in quality with benchmarking ideas How to identify affected calc, input and affected documents
Identify Affected Calcs Calculation review and indexing DB cross referencing & search capability Supplemental tribal knowledge capture Culture & tools to capture info as part of work Affected document screening form – not just eng docs
Identify Affected documents Route document to those who might be impacted to identify other documents (builds with experience). Multiple calcs on same system – Data base design; owner control
Margin Acceptance criteria and relation to results clear in calc. Use Margins as indicator of calc health Requirement to discuss low margin in conclusion section of calc. Maint./Ops - Will come in and request the margin…..Maybe not the best thing to loudly expose margin
Ownership Yes Owner can delegate who can revise calcs Assign owner with calc health and innovation in calc methodology
Sequencing and Calc Updating Add step to t-week schedule to validate change calcs How many changes spur a revision? After 7 th addenda they have to be incorp. Banking changes can lead to balloon payments In manpower
Third party calcs 25 question owners acceptance validation Vendor calcs are reviewed and formatted in house
As-built vs Engineering Calcs Change notices vs revisions Discussion of pros and cons