CONTACTS 
0201 - Intel Corporation                                                                                                                                                  O-00000704 0201
020101 - Mr. Morris E. Jones;

SUBJECTS
Background History Morris Evaluation SDS for Preparing Comments on S

1003 -
1003 -    ..
1004 - Summary/Objective
1005 -
100501 - Follow up ref SDS 12 0000, ref SDS 11 0000.
100502 -
100503 - On 040714 Gary submitted the 1st draft of the ASB filing to Morris,
100504 - and requested comments on how to consolidate, particularly in defining
100505 - a new standard for software tools and application. ref SDS 12 0001
100507 -  ..
100508 - We discussed this briefly on 040724. ref SDS 13 0001
100510 -  ..
100511 - Today, submitted a letter saying...
100512 -
100513 -    1.  Subject: Test Data for Get, Split, Join, and Recl Commands
100514 -        Date: Mon, 26 Jul 2004 13:21:30 -0700
100521 -         ..
100522 -    2.  Morris,
100523 -
100524 -        Following up our discussion this past Saturday, 040722, on
100525 -        preparing an ASB filing for an SDS standard at Aerospace company, a few
100526 -        weeks ago, on 040630, Gary submitted an explanation of
100527 -        "situational awareness." ref SDS 10 FZ6L, which suggests there
100528 -        is an audience for theory and practice of SDS, as set out in
100529 -        POIMS.  This background seems to align with your analysis of
100530 -        SDS reported on November 23, 1991, ref SDS 1 0477, and so might
100531 -        support your review and comments on the current draft the ASB
100532 -        to define a standard for SDS. ref DIT 1 0001
100534 -         ..
100535 -    3.  At that time, in November 1991, you explained SDS is different
100536 -        from the way executives work using conversation to expedite,
100537 -        ref DIT 1 BU6Q, because talk is cheap, fast and easy using
100538 -        "feel good" management. ref SDS 1 1331
100540 -         ..
100541 -    4.  A year later on 921127 you related that feel good management on
100542 -        the job causes inconsequential details to become major
100543 -        problems. ref DIT 1 BU6X  You further indicated SDS support for
100544 -        tracking communication in meetings, calls and documents to
100545 -        maintain alignment with objectives, requirements and
100546 -        commitments helps people avoid little deviations that later
100547 -        escalate into big problems. ref SDS 2 0674  A few years later,
100548 -        after gaining more experience with SDS support, on 950303 you
100549 -        drafted your famous bow and arrow diagram to illustrate how SDS
100550 -        strengthens command and control of the work, ref SDS 3 M34O, as
100551 -        explained in POIMS. ref OF 1 1113
100553 -         ..
100554 -    5.  The following year, on 960406, you mentioned part of the
100555 -        problem is that people cannot find relevant details quickly,
100556 -        when needed, and so wind up relying on remembering only the
100557 -        gist of the story, ref DIT 1 BV3U, which often proves to be
100558 -        incorrect. ref SDS 5 4249  On 010425 you noted SDS solves the
100559 -        problem by positioning everything in the right place at the
100560 -        right time. ref SDS 7 EP7F  On 010916 other people began
100561 -        noticing SDS solves the problem by making finding critical
100562 -        details fast and easy. ref SDS 8 0001  A week or so later on
100563 -        010924 you made a similar comment noting that nobody uses
100564 -        software the way SDS is used to make finding relevant details
100565 -        fast and easy. ref SDS 9 XT5F
100567 -         ..
100568 -    6.  Our current assignment preparing an ASB filing is to come up
100569 -        with one, or, at most, two words that summarize the "standard"
100570 -        for SDS capability, ref OF 2 PR3O, which you have previously
100571 -        described. ref DIT 1 BV4S
100573 -         ..
100574 -    7.  In our discussion on Saturday, you mentioned a "standard" for
100575 -        communication that has several thousand pages.  In this
100576 -        exercise, we want to start with only one or two words, and then
100577 -        construct one or two paragraphs that distinguish the standard
100578 -        for SDS from say the standard for email, wordprocessing, and
100579 -        Sharepoint. ref DIT 1 4P4K
100581 -         ..
100582 -        You initially proposed the word "organization," based on the
100583 -        telecon we had with Bill DeHart on 000709, when you asked Bill
100584 -        what SDS does that is different, ref DIT 1 4P5I, and he used
100585 -        "organization" to summarize the benefit of getting information
100586 -        in the context of daily work, background and objectives that is
100587 -        timely and accurate for getting things done quickly and
100588 -        correctly. ref SDS 6 2419
100590 -         ..
100591 -    8.  As noted, you made the same point a year later on 010425 by
100592 -        observing that the typical day scenario using SDS is
100593 -        unbelievable (i.e., a "utopia"), ref DIT 1 BV6Q, because
100594 -        everything is in the right place at the right time. ref SDS 7
100595 -        EP7F
100597 -         ..
100598 -    9.  How then to prepare a write up that helps people see the
100599 -        opportunity to accomplish the "unbelievable" ability to quickly
100600 -        and accurately draw on a wide range of critical details across
100601 -        days, months, years and decades of experience, but without
100602 -        stepping on the toes of other vendors, which you cautioned
100603 -        about in our discussion on Saturday. ref DIT 1 BV6Y
100605 -         ..
100606 -   10.  Does Gary's research on "situational awareness" help,
100607 -        ref DIT 1 BV7V, as shown in the record on 040630? ref SDS 10
100608 -        Z656
100609 -
100610 -
100611 -
100612 -
100613 -
100614 -
100615 -
1007 -