THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: May 24, 1999 08:17 AM Monday; Rod Welch

Morris comments on subject indexing.

1...Summary/Objective
2...SDS Subject Index Solves Information Retrieval Problems
3...Engineering Management SDS Tools Make Alignment Fast Easy
4...SDS May Support Design, E.G., Buildings, Software, Chips
5...Contemporaneous Notes Improve Engineering Save Time and Money

ACTION ITEMS.................. Click here to comment!

1...I think it would be useful to develop some baseline structures for

CONTACTS 
0201 - Intel Corporation
020101 - Mr. Morris E. Jones; Director of Architecture

SUBJECTS
Internet Doc Log Evaluation
Complexity of Knowledge, Overwhelming
Subject Indexing is Complex, Others Have
Subject Index Manages Complexity Like WBS
3 x 5 Cards, Improve Organization of
Procedures Subject Indexing
Subject Index WBS Methodology
Overwhelming Map Needed to Maintain Focus Subject Search
Find Information Organic Subject Structure
Find Right Information at Right Time Segment Multiple Paths Cross-ref
Good Management Hard Work Organic Subject Structure, Subjects Complex
WBS Subjects Organic Structure CNA

2114 -
2114 -    ..
2115 - Summary/Objective
2116 -
211601 - Follow up ref SDS 40 0000, ref SDS 38 0000.
211602 -
211603 - Received ref DRT 1 from Morris responding to ref DIP 6 0660 with link
211604 - to ref SDS 40 1652.  He indicates data may be overlooked because there
211605 - is no subject for it in the index.  Analysis indicates that SDS has
211606 - been very successful enabling retrieval of anything useful, even
211607 - though we do not always know what will be useful at the time data is
211608 - first developed.  That is because there are alternate routes to
211609 - information.
211611 -  ..
211612 - Discussed this evening the potential of using SDS to manage software
211613 - and chip design. ref SDS 0 0876
211615 -  ..
211616 - Submitted ref DIT 1 1147 linked to this record on subject indexing,
211617 - and to discussion on SDS for design support. ref SDS 0 0876
211618 -
211620 -  ..
2117 -
2118 -
2119 - Progress
212001 -  ..
212002 - SDS Subject Index Solves Information Retrieval Problems
212003 -
212004 - Follow up ref SDS 40 9633.
212005 -
212006 - Received ref DRT 1 from Morris responding to ref DIP 6 with link to
212007 - ref SDS 40 1652.
212009 -  ..
212010 - Morris asks in this letter...
212011 -
212012 -     You still haven't addressed the search issue.
212013 -
212014 -     You never know how data will be used in the future.  You could be
212015 -     in an Affirmative Action audit, and need to know the age and sex
212016 -     of all the workers on the site.  This would not be in a link
212017 -     thread. ref DRT 1 4836
212019 -  ..
212020 - The search issue was reviewed on 990521. ref SDS 40 9633
212021 -
212022 -     [On 990615 NSF proposal sets research objectives for Internet
212023 -     search capability using subject index. ref SDS 46 1610 and
212024 -     ref SDS 46 5124]
212025 -
212026 -     [On 990525 offered to meet and demonstrate SDS subject management
212027 -     methods. ref SDS 41 7072]
212029 -      ..
212030 -     [On 000303 offered to meet with Morris to design improvements to
212031 -     SDS subject management. ref SDS 54 0896]
212033 -  ..
212034 - The SDS record is searched every day all day long.  This experience
212035 - shows SDS successfully searches the record for needed information.
212036 - Most take seconds.  A few take a minute or so to identify applicable
212037 - subjects. Occassinally, it takes 10 or 20 minutes to try alternate
212038 - paths.
212039 -
212040 -      [On 990526 example of difficult search. ref SDS 42 0977]
212042 -  ..
212043 - Sent ref DIT 1 1147 with link to this record for response.
212044 -
212045 -      [On 990525 letter from Morris does not comment on this analysis.
212046 -      Sent letter asking if Morris wants a demonstration of organic
212047 -      subject structure. ref SDS 41 7072]
212049 -  ..
212050 - With respect to "data"...
212051 -
212052 -    1.  SDS keeps track of "data" in a manner that adds "intelligence"
212053 -        to management. ref OF 1 0582
212054 -
212055 -        An example are tire tread, ref SDS 35 2025, and break lining
212056 -        "data" in the record on 990507, ref SDS 35 3483, which are
212057 -        linked to original source records issued by specific mechanics
212058 -        on particular days.
212060 -         ..
212061 -    2.  SDS tracks the "story" that emerges in connection with the
212062 -        collection and disposition of "data," as shown in the record on
212063 -        990507. ref SDS 35 0945
212064 -
212065 -        a.  What criteria govern collection of data?
212066 -        b.  Should the criteria be changed?
212067 -        c.  Is the data useful?
212068 -        d.  For how long?
212069 -        e.  How was data collected, assembled, organized
212070 -        f.  Who did the collection, under what conditions?
212071 -        g.  Who maintained the data, and how was it done?
212072 -        h.  etc.
212073 -        i.  etc...
212075 -         ..
212076 -    3.  SDS facilitates connecting the "story" on data with the history
212077 -        of decisions, conduct, and controlling authority on components
212078 -        that are impacted by data, see for example application of
212079 -        warranties on 990507. ref SDS 35 2090
212081 -         ..
212082 -        Connecting information over time, yields "understanding" which
212083 -        is an "intelligence" role, reviewed on 980815. ref SDS 25 1173
212085 -         ..
212086 -        Understanding is explained in the NWO paper... ref OF 4 5361
212088 -         ..
212089 -    4.  SDS tracks Action Items that are connected to data, and to
212090 -        analysis, so that analysis of future data can be accomplished
212091 -        quickly and accurately.
212093 -         ..
212094 -    5.  SDS places data on one thing in context with data on related
212095 -        things, sub-assemblies and so on.
212096 -
212097 -
212099 -  ..
2121 -
2122 -
2123 - 0925 called Morris
2124 -
212401 - Morris indicated his letter was not meant to be taken litterally about
212402 - tracking data per se.  He seems to recognizes SDS is not intended to
212403 - replace DBMS, but rather to help people apply whatever "data" they may
212404 - have, by connecting chains of chronology that impart cause and effect,
212405 - i.e., intelligence. ref OF 1 0582
212407 -  ..
212408 - On 911123 Morris described SDS as...
212409 -
212410 -     ...a tool to record, assemble and analyse facts and ideas about
212411 -     events to guide decision making, plan the work and follow up to
212412 -     ensure decisions and plans are carried out. ref SDS 3 0477
212414 -  ..
212415 - Andy Grove says in his book reviewed on 980307 that human mental maps
212416 - are awfully forgiving of ambiguity. ref SDS 24 3668
212418 -  ..
212419 - He was not talking about keeping track of "data."  Grove wanted to
212420 - understand what people think, say and do in relation to objectives,
212421 - requirements and commitments.  He was talking about "intelligence".
212422 - ref OF 1 0582  Andy developed "intelligence" by "taking copious notes"
212423 - and asking people questions about what was meant by various
212424 - discussions he did not understand.  The link between understanding,
212425 - intelligence and "data", was reviewed on 980815. ref SDS 25 1173
212427 -  ..
212428 - SDS helps Andy and others do this kind of task better by providing
212429 - access to their memory of recent, and not-so-recent, history faster,
212430 - better and cheaper.
212432 -  ..
212433 - Morris seemed to indicate this evening that people encounter things
212434 - they want to look up that are not in the Subject Index.
212435 -
212436 -      [On 990526 example of difficult search. ref SDS 42 6491]
212438 -  ..
212439 - That is true.  Until there is a subject index, there are 0 ways to
212440 - look things up.  When starting something new we can create a baseline
212441 - index and then it grows and grows, as experience is gained.  Sometimes
212442 - we have to start over.
212444 -  ..
212445 - Experience shows that using a single list of "subjects" does not work
212446 - well.  Conceptual structures or classes of subjects with cross-
212447 - references, seems to work better.
212449 -  ..
212450 - When a particular subject is not in the Index, related subjects can be
212451 - used, or we can look up the history of a document, e.g., a file, a
212452 - letter, memo, publication, or a person or meeting where a subject
212453 - arose, and find the subjects associated with that information.  We can
212454 - use those subjects, or define new subjects, in the index, so that at a
212455 - future time, when needed, that information is more readily available.
212457 -  ..
212458 - Experience shows that it is rare, about 1 time out of 10, when a
212459 - subject is needed that is not in the Subject Index.  That is because
212460 - the index is formed based on using "natural structures."  Since the
212461 - SI is used all day long, each day a few subjects are added to the
212462 - index.
212464 -  ..
212465 - Morris mentioned this evening that construction has natural structures
212466 - that impart an inherent order or structure for a subject index.
212467 -
212468 -      [On 990526 example of difficult search that does not have an
212469 -      evident "natural structure." ref SDS 42 6491]
212471 -  ..
212472 - I agreed, and noted that all human activity is organic.  Some
212473 - structures are more easily recognized than others.
212475 -  ..
212476 - Common elements include...
212477 -
212478 -                          WBS
212479 -                          schedule
212480 -                          budget
212481 -                          objectives
212482 -                          requirements
212483 -                          specifications
212484 -                          plans
212485 -                          organization (i.e., people)
212486 -                          geography
212487 -                          components
212489 -  ..
212490 - SDS provides a process and tools for identifying and using organic
212491 - structures for information management, that works better than most
212492 - other systems.
212494 -  ..
212495 - I think it would be useful to develop some baseline structures for
212496 - industires, and guidance on primary subject levels.
212497 -
212498 -      [On 990525 received letter from Morris that does not comment on
212499 -      this analysis. ref SDS 41 7072]
212500 -
212501 -      [On 000311 did some work on this. ref SDS 55 0001
212502 -
212503 -
212504 -
212505 -
2126 -

SUBJECTS
Engineering Management Technology Chip Design Software SDS Improves

5103 -
510401 -  ..
510402 - Engineering Management SDS Tools Make Alignment Fast Easy
510403 - SDS May Support Design, E.G., Buildings, Software, Chips
510404 - Contemporaneous Notes Improve Engineering Save Time and Money
510405 -
510406 - Follow up ref SDS 38 6822, ref SDS 32 3468.
510408 -  ..
510409 - Research on 951221 recommends engineers develop prototype software
510410 - code to study, analyse, plan, and figure out what to program.
510411 - ref SDS 16 FJ6J  Industry standards require contemporaneous notes for
510412 - accurate understandings that aid study, analysis, and planning to save
510413 - time and money on software engineering. ref SDS 16 0966
510415 -  ..
510416 - On 990226 Intel reported delays in product releases due to design
510417 - errors on impedance issues. ref SDS 26 0001
510419 -  ..
510420 - Morris has reported difficulties working on Medit in recent years,
510421 - because there is very little documentation in the code.  Finding where
510422 - the code has been changed to accomplish program operations takes a lot
510423 - of time to re-learn how the software works.  This makes doing the work
510424 - emotionally traumatic, and takes longer.  These circumstances cause
510425 - resistance to making improvements, due to limited time.
510427 -  ..
510428 - This evening discussed using SDS to support software programming and
510429 - chip design, i.e., engineering management, by providing a well ordered
510430 - record with precision access using traceability to original sources,
510431 - also, called "alignment," which is a key dimension of "intelligence."
510432 - ref OF 1 0367   The ability to maintain order enables "root cause
510433 - analysis," explained in NWO. ref OF 4 KR6O  Order also yields the
510434 - power of knowledge to control the future through command and control
510435 - of the record, explained in POIMS. ref OF 3 1113  During a meeting on
510436 - 970526, Morris reported that root cause analysis improves management
510437 - based on experience presented at a Cal Tech seminar he attended that
510438 - discovered important ideas from root cause analysis on why the
510439 - Challenger Space Shuttle exploded after take-off in 1986. ref SDS 21
510440 - 2168  Earlier on 950204 Morris cited an executive management
510441 - conference he attended that presented practices that sounded similar
510442 - to using SDS for command and control of the record. ref SDS 8 5932
510444 -  ..
510445 - Documentation for engineering management to save time and money by
510446 - reducing mistakes aligns with project management that requires
510447 - traceability to original sources, reviewed on 950721. ref SDS 13 1740
510449 -  ..
510450 - SDS supports seven (7) dimensions to maintain a "well ordered record,"
510451 - explained on 890523. ref SDS 1 TP8O
510452 -
510453 -            [On 990625 SDS for intelligence support for a well ordered
510454 -            record of complex daily work in engineering management
510455 -            meets requirements in health care for a well ordered record
510456 -            of patient history in the medical chart, called out in
510457 -            Kaiser's Healthwise Handbook. ref SDS 47 TD5S
510459 -  ..
510460 - Engineering management applies Communication Metrics for executive
510461 - training on good management practice. ref SDS 38 0287
510463 -  ..
510464 - Support is similar to facilities and equipment management that tracks
510465 - history of service, which was discussed with Tom Keesling at the Corps
510466 - of Engineers on 990521. ref SDS 39 5561
510468 -  ..
510469 - Morris said there are better commercial programs than SDS for
510470 - engineering management, which aligns with his report on 950228 that
510471 - Chips could perform engineering management without SDS. ref SDS 10 VK6H
510472 - Today, Morris said it is hard to get people to use programs and
510473 - methods he feels are better than SDS, because marketing managers drive
510474 - engineers to expedite producing code.  Failure to use good management
510475 - practices causes a lot of mistakes, as Henry Kissinger noted
510476 - concerning management of government activity, reviewed on 940609,
510477 - ref SDS 6 4238, rather use good engineering practices for saving time
510478 - and money by producing useful and correct code.  This aligns with
510479 - Morris' report on 951228 that he uses about 20% of features in Ecco
510480 - Pro to manage daily work. ref SDS 17 5850
510481 -
510482 -     [On 990525 Morris confirmed engineers don't like to write, focus
510483 -     is on "doing the work." ref SDS 41 0966]
510485 -      ..
510486 -     [On 010425 Morris advised that using SDS explained in the Typical
510487 -     Day Scenario is a utopia compared to other tools and methods,
510488 -     because SDS has everything in the right place at the right time.
510489 -     ref SDS 60 EP7F
510491 -      ..
510492 -     [On 010924 Morris reported that SDS improves management better
510493 -     than other methods. ref SDS 61 NK4J
510495 -      ..
510496 -     [On 010924 Morris reported that nobody uses software the way SDS
510497 -     is used to capture organizational memory and add intelligence.
510498 -     ref SDS 61 XT5F
510500 -      ..
510501 -     [On 020110 Morris reported research showing people use about 5% of
510502 -     features in Microsoft programs. ref SDS 62 CK4K
510504 -  ..
510505 - Morris' report that engineers avoid good management in hopes of
510506 - meeting schedule objectives aligns with reporting on 950428 that poor
510507 - mangement in Information Technology (IT) is commonly tolerated as
510508 - accepted practice, ref SDS 11 7007, causing productvity to decline.
510509 - ref SDS 11 3921
510511 -  ..
510512 - On 960326 people resist reading the record to prepare for working
510513 - effectively. ref SDS 18 LO5G
510514 -
510515 -     [On 990525 Morris reports engineers don't like to write, just want
510516 -     to work on technology without being prepared to work effectively.
510517 -     ref SDS 41 0966
510519 -      ..
510520 -     [On 990527 Andy Grove says engineers don't like read. ref SDS 43
510521 -     5110
510523 -      ..
510524 -     [On 001101 article confirms engineers don't like to prepare
510525 -     requirements nor documentation; they want to write code.
510526 -     ref SDS 59 MX6H and ref SDS 59 NG3J
510528 -  ..
510529 - Previously on 911121 Morris indicated Chips was using an AI program
510530 - for engineering management support which he initially represented was
510531 - superior for SDS, yet later reported that the AI program did not work
510532 - very well, ref SDS 2 5609, because subject identification is more
510533 - difficult than people realize per POIMS, ref OF 1 0582, and our
510534 - meeting on 970116. ref SDS 20 3109
510536 -  ..
510537 - On 911123 Morris reported SDS is unique.  Nobody can work consistently
510538 - in the manner SDS supports. ref SDS 3 4930
510540 -      ..
510541 -     [On 990625 medical management calls for tasks supported by
510542 -     Communication Metrics. ref SDS 47 4185]
510544 -      ..
510545 -     [On 990625 executives don't like to read and write. ref SDS 48
510546 -     4914]
510548 -      ..
510549 -     [On 990711 NSF research grantee proposed Communication Metrics
510550 -     support software design. ref SDS 49 0001  Sent letter to Morris
510551 -     asking about new terms. ref SDS 49 5280]
510553 -      ..
510554 -     [On 990925 Intel reported further delays. ref SDS 50 0001
510556 -      ..
510557 -     [On 991222 Doug Engelbart pioneer in using links applied to
510558 -     computer software engineering. ref SDS 51 5727]
510560 -      ..
510561 -     [On 000517 engineer reports success using good engineering
510562 -     practices on a project in Texas. ref SDS 57 2064
510564 -      ..
510565 -     [On 001017 engineer on DKR project reports engineering management
510566 -     helps architecture make sense. ref SDS 58 IO6J
510568 -  ..
510569 - Morris explained Concurrent Engineering performs production concurrent
510570 - with design, i.e., before the design is substantially complete, as a
510571 - way to shorten project completion.  On 940103 article on Concurrent
510572 - Engineering was reviewed. ref SDS 5  This method was used to deliver
510573 - an oil tanker that crashed on its maiden voyage, and was cited at a
510574 - PMI Conference on 940611 to show Partnering expedites resolution of
510575 - disputes when small problems grow into major disasters. ref SDS 7 8473
510576 - Communication problems were reviewed on 970724, that cause continual
510577 - rework and delays, that frustrate the goals of concurrent engineering.
510578 - ref SDS 22 0866
510580 -  ..
510581 - Concurrent Discovery was developed on 960620 to apply concurrent
510582 - engineering practices to improve management. ref SDS 19 1101
510584 -  ..
510585 - This problem was cited on 950428 in a seminar on IT project
510586 - management. ref SDS 11 7007  Morris commented on the impact of poor
510587 - project management on 950705. ref SDS 12 2165
510589 -  ..
510590 - On 920110 AEC magazine explained need for better technology to support
510591 - engineering management, ref SDS 4 4977, which aligns with Morris'
510592 - experience at Chips reported on 911121. ref SDS 2 5609
510594 -  ..
510595 - SDS advantages for design support were reviewed in relation to ISO
510596 - criteria on 951026. ref SDS 14 7773
510598 -  ..
510599 - Morris will comment on using SDS for design support.
510600 -
510601 -      [On 990525 Morris says engineers don't like to write, but does
510602 -      not comment on advantage of traceability to original sources...
510603 -      ref SDS 41 9600]
510605 -  ..
510606 - Recently on 990430 an Engineer at Caltrans advised that SDS would be
510607 - usefully applied to design. ref SDS 31 3468
510609 -  ..
510610 - An example of these benefits is recent work on upgrading the Doc Log
510611 - system on the web, done on 990505. ref SDS 34 0505
510613 -  ..
510614 - An earlier example is the work on the Action Item system, reported on
510615 - 951209. ref SDS 15 0001
510616 -
510617 -      [On 990530 example improving linking process. ref SDS 44 0001]
510619 -  ..
510620 - SDS might be a different kind of support that would add value to
510621 - current IT practice.  Possibly supervisors would benefit from SDS to
510622 - interface between design, management, marketing and manufacturing.
510624 -  ..
510625 - Sent ref DIT 1 0855 with link to this record for response.
510626 -
510627 -      [On 990425 Morris says managers are responsible for the big
510628 -      picture and impacts. ref SDS 41 0996]
510629 -
510630 -      [On 000106 Morris indicated SDS is different from other knowledge
510631 -      management systems. ref SDS 52 5628]
510633 -       ..
510634 -      [On 000116 Morris confirmed SDS is unique capability. ref SDS 53
510635 -      0877
510637 -       ..
510638 -      [On 000516 received letter from Eugene Kim proposing SDS
510639 -      capability would improve software engineering. ref SDS 56 1978
510640 -
510641 -
510642 -
510643 -
510644 -
510645 -
510646 -
5107 -
Distribution. . . . See "CONTACTS"