CONTACTS 

SUBJECTS
Learning Continual Case Studies Experience History Knowledge Root Ca
Proof of Concept Connect Dots Experience Shows Attitudes Change New
Aerospace company Root Cause Analysis Inquiry SDS ASB Standard                    06
Root Cause Analysis Connecting Dots Cause Effect Causation Understan
SDS Inquiry Root Cause Analysis SDS ASB Standard
Definition Case Studies Root Cause Analysis Lessons Learned
Analysis Unaware SDS Supports Needs Support Services Analyst Demonst
Analysis Unaware SDS Supports Needs Support Services Analyst Demonst

3010 -
3010 -    ..
3011 - Summary/Objective
3012 -
301201 - Follow up ref SDS 11 0000. ref SDS 10 0000.
301202 -
301203 - Received correspondence showing progress helping people learn about
301204 - SDS through an inquiry on support for root cause analysis.  Gary set
301205 - an action item for follow up. ref SDS 0 W83T  Sent a letter
301206 - congratulating Gary on excellent work explaining SDS. ref SDS 0 4C9G
301207 - Reviewed the role of SDS support for chrolonogy that is the root of
301208 - analysis for understanding causation in formal settings. ref SDS 0
301209 - 5I9S
301210 -
301211 -     [On 040924 Gary followed up on inquiry for support to perform root
301212 -     cause analysis. ref SDS 13 K46N
301213 -
301214 -
301215 -
301217 -  ..
3013 -
3014 -
3015 - Progress
3016 -
301601 - Aerospace company Request for Support on Root Cause Analysis
301602 -
301603 - Follow up ref SDS 11 K46N, ref SDS 9 7P6X.
301604 -
301605 - Received ref DRT 1 0001 to Gary saying...
301606 -
301607 -        Thanks for calling back regarding my inquiry into SDS as a root
301608 -        cause anaysis tool.  Your info was very helpful in processing
301609 -        the request.
301611 -  ..
301612 - This letter reflects work on 040905 reporting inquiry for root cause
301613 - analysis support explained in the ASB filing setting a Aerospace company
301614 - standard. ref SDS 11 K46N   At that time, planning called for
301615 - submitting details on SDS and requesting feedback, ref SDS 11 GD9N, on
301616 - SDS support for root cause analysis. ref SDS 11 2S4J
301618 -  ..
301619 - Received ref DRT 2 0001 from Gary to Michael explaining...
301620 -
301621 -    1.  I have used SDS in my own work, but was not aware of the extent
301622 -        to which SDS had been used for anything resembling root cause
301623 -        analysis. With the help of the program's developer, I was able
301624 -        to locate references to the use of SDS in supporting several
301625 -        flavors of root cause analysis and the savings that resulted
301626 -        from making complex analysis of volumes of heterogeneous data
301627 -        cost effective.
301629 -  ..
301630 - This record supports root cause analysis from a case study on 040615
301631 - showing that people are not aware of SDS scope until experience is
301632 - gained with support services over a long period of time to become
301633 - familiar using and discussing common applications. ref SDS 7 6X5J  At
301634 - that time, using SDS to prepare technical documents was not a familiar
301635 - application. ref SDS 7 DN8O  Strategy in the annual review planned to
301636 - expand use of SDS by exposure, awareness, and experience for learning
301637 - the scope of intelligence support. ref SDS 6 8Q3N  After getting
301638 - experience using SDS to prepare the ASB, Gary asked about expanding
301639 - use of SDS for preparing technical documents. ref SDS 8 O47O  Earlier
301640 - on 961101 Tom Keesling reported similar experience enabled discovery
301641 - at USACE that SDS improves daily work for contract management.
301642 - ref SDS 2 8888
301643 -
301644 -     [On 040924 Gary followed up on inquiry for support to perform root
301645 -     cause analysis. ref SDS 13 K46N
301647 -  ..
301648 - On 040913 root cause analysis solved a problem, and positioned Gary to
301649 - avoid future similar problems. ref SDS 12 4Q5Y
301651 -  ..
301652 - Gary continues...
301653 -
301654 -    2.  While SDS isn't intended specifically for formal root cause
301655 -        analysis, it has been found to be of value when the issues
301656 -        pertain to matters contained in the SDS record, and for
301657 -        recording information for the pursuant root cause analysis when
301658 -        done after the fact as part of a discovery action.
301660 -  ..
301661 - The intent of SDS design to support analysis is reported on 000723.
301662 - ref SDS 5 G96O  This is reflected in the ASB filing shown by language
301663 - reviewed on 040905. ref SDS 11 B36J
301665 -  ..
301666 - Formal Root cause analysis is defined in professional literature
301667 - reviewed on 040905. ref SDS 11 AZ9J  Alignment with SDS support is
301668 - shown by SDS foundational documents, also, listed on 040905.
301669 - ref SDS 11 2S4J
301671 -  ..
301672 - Gary continues...
301673 -
301674 -    3.  Information on several experiences related to root cause
301675 -        analysis can be found here. [in SDS foundational documents,
301676 -        NWO. ref OF 2 HH5L
301678 -         ..
301679 -    4.  Analysis of ways that SDS can help reduce the often high cost
301680 -        of data analysis relating to root cause analysis can be found
301681 -        at [listed in a record on 040905, ref SDS 11 FT48, and in
301682 -        another record on 970702 illustrating a particular problem to
301683 -        solve. ref SDS 3 CV6O]
301685 -         ..
301686 -    5.  The real strength of SDS is its proactive use.  When used in
301687 -        conjunction with sound management practices, SDS supports a
301688 -        form of concurrent discovery, where issues are analyzed as they
301689 -        develop and before they become critical, thus requiring after
301690 -        the fact root cause analysis. There is an investment that needs
301691 -        to be made to transition to this way of working, but
301692 -        indications are that is quite cost effective over time.
301694 -         ..
301695 -        Need for root cause analysis supported by SDS is explained on
301696 -        921127. ref SDS 1 0674
301698 -         ..
301699 -        Cost savings using SDS explained by USACE. ref DRP 1 0001
301701 -         ..
301702 -        Case study illustrates root cause analysis of DOD project.
301703 -        ref SDS 4 9152
301705 -         ..
301706 -    6.  Studies of process or plant operations which deal with
301707 -        collecting volumes of data about a process that is ongoing
301708 -        often requires additional tools, but SDS has been used in such
301709 -        cases as well, listed on 040905. ref SDS 11 JA9I
301711 -         ..
301712 -    7.  Do any of these applications resemble the need that you have?
301713 -        I had assumed that you were looking for tools for formal root
301714 -        cause analysis, supporting Ishikawa (fishbone) diagrams and the
301715 -        like.
301717 -         ..
301718 -    8.  If you can provide me with a brief explanation of the task you
301719 -        need done, I may be able to provide more tightly directed
301720 -        resources within the existing SDS record.
301722 -         ..
301723 -    9.  Feel free to call if you would like to discuss this material
301724 -        and your application further.
301726 -  ..
301727 - This accomplishes the action item on 040905. ref SDS 11 GD9L
301729 -  ..
301730 - Called and talked to Gary.
301732 -  ..
301733 - He received an acknowledgement from Michael.
301735 -  ..
301736 - Gary set a task in the Schedule to call Michael in a week to see if he
301737 - solved his problem.
301738 -
301739 -     [On 040924 Gary followed up on inquiry for support to perform root
301740 -     cause analysis. ref SDS 13 K46N
301742 -  ..
301743 - Submitted ref DIT 1 0001 to Gary saying...
301744 -
301745 -    1.  Good letter to the Aerospace company employee inquiring about SDS support
301746 -        for Root Cause Analysis, shown in your letter yesterday, per
301747 -        below.  This makes progress on the action item in the record on
301748 -        040905. ref SDS 11 GD9N
301750 -         ..
301751 -    2.  Root cause analysis is explained in POIMS. ref OF 1 12F2
301752 -        and in NWO. ref OF 2 QP5I
301754 -         ..
301755 -    3.  Foundational documents provide a consistent explanation, and
301756 -        feedback from referrals helps improve the message.
301758 -         ..
301759 -    4.  The foundational docs explain "chronology" inherently imparts
301760 -        causation, which is why accountants track an "audit trail," and
301761 -        why lawyers and judges ask witnesses "Then what happened?"
301762 -        People feel that discovering the sequence of events, gets to
301763 -        the bottom of problems.  Since chronology is the engine that
301764 -        drives SDS, this architecture inherently supports analysis for
301765 -        understanding why things happened.  Additionally, SDS support
301766 -        for "connecting the dots" and constructing organic structure to
301767 -        manage context in the subject index, all impart deeper
301768 -        understanding that aids root cause analysis.
301769 -
301770 -
301771 -
301772 -
301773 -
301774 -
301775 -
301776 -
301777 -
301778 -
301779 -
3018 -