CONTACTS 
0201 - Dynamic Alternatives                                                                                                                                               O-00000793 0101
020101 - Mr. Garold L. Johnson
0202 - Boeing                                                                                                                                                             O-00000816 0505
020201 - Mr. Garold L. Johnson; 714 762 4936                                                                                                                              O-00000816 0505

SUBJECTS
Johnson, Gary Given Interest in SDS to Work on SDS and Intellectu
Ownership Product Development Collaborating with Morris
Windows C Version Propose Developing Based on SDS Prototype
Windows C Version of Medit to Drive SDS
Gary Proposes Working on Windows C Version of SDS to Make SDS Work Be
Medit C Version Update to Run SDS on Windows Solve Memory Problem
Macro Language C Version Medit Update so SDS Macros Run
Morris Uniquely Qualified SDS Development Only Person Who Can Meld Co
C Version Medit Update so SDS has All Memory of Windows
Johnson, Gary Proposes Working on C Version of Medit to Improve SDS b
Johnson, Gary Terms Conditions Contribute to SDS Development
Johnson, Gary Will Review Prepare Development Plan, Morris Will Send
Development Plan Gary Review C Version Medit
SDS Develop Strategy Ideas Evaluate Current SDS for Designing Next Ge
Gary Offers to Work on Creating Next Version of SDS Starting by Revie
Agrees to Terms in Welch Record on 030126 for SDS Project
Terms Conditions Agreed Upon for Gary to Use SDS for Communic

3319 -
3319 -    ..
3320 - Summary/Objective
3321 -
332101 - Follow up ref SDS 18 0000, ref SDS 13 0000.
332102 -
332103 -
332104 -
332105 -
332106 -
332107 -
332109 -  ..
3322 -
3323 -
3324 - Agreement
3325 -
332501 - Collaboration on SDS Agreed Between Gary and Rod
332502 -
332503 - Follow up ref SDS 26 NO4F.
332504 -
332505 - We agreed that, in accordance with Gary's letter on 030208 saying
332506 - nothing objectionable was noticed in terms and conditions discussed on
332507 - 030126, ref SDS 26 NO4F, and that he would make further review to
332508 - determine that those terms and conditions satisfy or otherwise
332509 - supersede issues in Gary's record on 030202, which was received by
332510 - Welch, also, on 030208, ref SDS 26 0001, we further agree this evening
332511 - that the record on 030126 satisfies other issues of interest to Gary
332512 - necessary for full agreement, and therefore, as a result, of such
332513 - further consideration over the past four (4) weeks or so, Gary is
332514 - agreeable to the language in the record on 030126 as the basis for
332515 - continuing collaboration on SDS development and marketing, ref SDS 24
332516 - TB4F, which satisfies objectives in the letter to Gary on 030127,
332517 - ref SDS 25 HJ9O, transmitting SDS code and the record of discussions
332518 - on 030126. ref SDS 24 TB4F
332519 -
332520 -     [On 030313 letter to Gary confirms these understandings.
332521 -     ref SDS 29 0001
332523 -      ..
332524 -     [On 030316 Gary received the letter on 030313 and indicated this
332525 -     accurately reflects our understandings. ref SDS 30 7V5K
332527 -  ..
332528 - We also agreed this evening that, as a result of these understandings,
332529 - we have substantially met plans to reach agreement on ownership and
332530 - development of SDS in accordance with planning and commitments in the
332531 - record on 021125 that set a target date of 030301 for agreeing to
332532 - collaborate on developing and marketing SDS. ref SDS 18 YG3K and
332533 - ref SDS 18 WF4M
332535 -  ..
332536 - There was further understanding in our call today that the parties may
332537 - modify terms and conditions in the record on 030126 through mutual
332538 - agreement.
332540 -  ..
332541 - Two issues that were open in the record on 030126 are termination and
332542 - breach. ref SDS 24 N86G  Gary makes the point that if no revenue is
332543 - ever generated from SDS, including any follow-on product, then these
332544 - issues are moot.  In the event revenue does result, then equitable
332545 - distribution is acceptable, and Welch is further protected by
332546 - royalties under para 6. ref SDS 24 EH69
332548 -  ..
332549 - Termination for cause ordinarily lies for failure to perform, and for
332550 - bad faith performance.  While this is not expected, in the event of
332551 - such occurrence Gary should be compensated based on value added, and
332552 - if no revenues have been generated to make cash payment, he would be
332553 - vested for such amount plus legal interest from the date of
332554 - termination.  The parties may mutually agree to terminate for
332555 - convenience upon 30 days notice.
332557 -  ..
332558 - We also need to think about what happens in the event of death or
332559 - incapacity.
332560 -
332561 -
332562 -
332563 -
332564 -
3326 -

SUBJECTS
Information Overload at Aerospace company Makes Keeping Up Record with   S Diffi
Goal for Next Six Months is to Enable Gary to Work Methodology for Ca
Information Overload Makes Capturing Record Difficult
Drowning in Details, Can't Keep Head Above Water.
Information Overload Not Enough Time to Understand Intelligence Conne
Capture Record After-the-fact Not Enough Time Not Familiar with Plann
Flexible Structure Balance Between Power of Flexibility that is Fragi
Plan Perform Report Integrated Each Supports Other Intelligence Proce
Time Not Enough to Capture the Record Difficult to Balance Allocating
Progress Learning to Capture a Greater Share of the Record Using SDS
Crisis Management Emergencies Work Behind Schedule Take Short Cuts Ca
Meetings Dilemma Cannot Attend Every Meeting and Write Everything Dow
Johnson, Gary Meetings Constant 200 Page Documents Not Enough Time Wr
Communication Manager Role Needed to Balance Time for Using SDS to Th

5316 -
531701 -  ..
531702 - SDS Implementation Modalities for Aerospace company Project Next Objective
531703 -
531704 - We further agreed this evening that development work on SDS at this
531705 - time should not be the main priority.  The main priority will be to
531706 - experiment and support Gary's efforts to use SDS on his assignment at
531707 - Aerospace company based on Gary's letter dated 030308 responding to my letter
531708 - asking Gary to submit his SDS records (shown as attached to Gary's
531709 - letter today, ref DRT 1 7X4I) IAW para 11 of the agreement discussed
531710 - on 030126. ref SDS 24 HF6N
531712 -  ..
531713 - Below, discuss "best practices" using SDS. ref SDS 0 GJ47
531714 -
531715 -       [On 030313 letter to Gary confirms planning to focus on learning
531716 -       and using SDS best practices. ref SDS 29 E97F
531718 -  ..
531719 - Gary's letter on 030308 says...
531720 -
531721 -     1.  I started at Aerospace company about that time and have been going
531722 -         non-stop since then. ref DRT 1 0001
531724 -  ..
531725 - This aligns with Gary's letter on 030125 reporting plans to use SDS at
531726 - Aerospace company. ref SDS 23 0001  Gary's letter on 030123 explained the work is
531727 - starting out behind schedule, and so people are scrambling to catch
531728 - up. ref SDS 22 Y55G
531729 -
531731 -          ..
531732 -         KM Dilemma Allocating Time Between Thinking and Doing
531733 -         Planning Managing Thinking and Doing Things KM Dilemma
531734 -         Thinking and Doing KM Dilemma Management Planning Operations
531735 -
531736 -         Follow up ref SDS 21 3O7K.
531737 -
531738 -     2.  I am forced to admit I have done nearly nothing with SDS at
531739 -         home and am just trying to keep my head above water at work.
531740 -         ref DRT 1 5Y6F
531742 -  ..
531743 - Challenge of keeping "head above water" was cited on 920210.
531744 - ref SDS 4 8400  This issue was considered when Gary planned to use SDS
531745 - on the Aerospace company project that started late and was behind schedule,
531746 - reported on 030123. ref SDS 22 Y55G
531748 -  ..
531749 - Gary continues...
531751 -          ..
531752 -     3.  It is not uncommon for me to spend most of a day in meetings
531753 -         or working on trying to understand another document.
531754 -         ref DRT 1 BY6J
531756 -  ..
531757 - Allocating time between meetings and analysis is a common challenge to
531758 - balance thinking and doing, illustrated by experience on Broadwater
531759 - Dam, reported on 890215. ref SDS 1 P116  Below, the goal using SDS is
531760 - not perfection, but improvement. ref SDS 0 GJ47  SDS is an aid, shown
531761 - by the example of Morris Jones on 910520, ref SDS 3 655O, and so
531762 - judgement is exercised to avoid allowing a powerful asset, for better
531763 - command and control of the record, to evolve into a crushing burden by
531764 - trying to write everything down.  Since the human mind can essentially
531765 - absorb endless information sequentially and process it on automatic
531766 - pilot with parallel processing in the subconscious mind, much like a
531767 - cow grazes continually in a pasture, any attempt to apply sequential
531768 - processing for knowledge management is necessarily futile, as noted by
531769 - Dave Snowden in his paper published last May, and reviewed on 020608.
531770 - ref SDS 11 S48O
531772 -  ..
531773 - In a call this evening, Gary said he is getting some of his work into
531774 - SDS, which is a significant start, per below. ref SDS 0 2J47  We also
531775 - noted that chronic information overload that crowds out time for
531776 - thinking, as related today, requires more people so that thinking gets
531777 - done, which leads to the Communication Manager role.  Drucker points
531778 - out that the character of work in the modern era is changing, and so
531779 - requires changes in organizational structure and roles, reviewed on
531780 - 931130. ref SDS 6 1855
531781 -
531782 -      [On 030313 discussed Com Manager role in letter to Gary.
531783 -      ref SDS 29 8E5J
531785 -  ..
531786 - Gary reported on 030123 that the project was starting behind schedule,
531787 - ref SDS 22 Y55G, which compounds the knowledge management dilemma that
531788 - arises in allocating time between thinking and doing. ref SDS 22 QU8L
531789 - On 960205 a report published by PMI related that people waste 70% of
531790 - the day in unproductive meetings because nobody is prepared, which
531791 - indicates that spending a lot of time in meetings gives an illusion of
531792 - progress. ref SDS 7 5902
531794 -  ..
531795 - Struggling to keep "head above water," spending most of the day in
531796 - meetings is another way of saying there is not enough time to think,
531797 - reported on 970910. ref SDS 8 3479  Since thinking is the engine of
531798 - progress, chronic information overload requires more bodies to
531799 - distribute the work, as reported on 920210. ref SDS 4 N84M  On 030120
531800 - Gary worried about entering the record "after-the-fact" rather than
531801 - planning tasks, then performance and then reporting. ref SDS 21 3O7K
531802 - At that time analysis showed the record need not be captured all at
531803 - once, and that entering the record at any time, contributes to
531804 - planning.  Sometimes planning is implicit, ref SDS 21 5N8G, because
531805 - humans innately use a plan, perform, report "intelligence" process,
531806 - ref SDS 21 5N88  SDS supports these innate mental metrics that
531807 - allocate time between thinking and doing better than other methods by
531808 - enabling people to quickly create a flexible structure, explained on
531809 - 890523, ref SDS 2 P13O, so that everything is in the right place at
531810 - the right time, as Morris noted on 010425. ref SDS 9 EP7F  This means
531811 - people can more quickly and easily fill in the gaps in the record over
531812 - time using SDS, rather than simply forget about the details and rely
531813 - on remembering only the gist of the story, also as discussed in the
531814 - record on 030120. ref SDS 21 NQ4F
531815 -
531816 -       [On 030313 letter to Gary confirms planning to focus on learning
531817 -       and using SDS best practices. ref SDS 29 E97F
531819 -  ..
531820 - On 030224 we discussed getting Aerospace company's contract with the Army to
531821 - identify objectives for the project, which provide simple, direct
531822 - guidance for developing the SDS organic subject structures.
531823 - ref SDS 27 PP4O  Having a baseline organic structure makes it faster
531824 - and easier to capture the record day-to-day.  Gary indicated today
531825 - that he is making subject assignments.
531826 -
531827 -       [On 030313 letter to Gary confirms planning to focus on learning
531828 -       and using SDS best practices. ref SDS 29 E97F
531829 -
531830 -
531831 -
531832 -
531833 -
531834 -
5319 -

SUBJECTS
Omnipage Converts PDF Files into Text that Can be Managed by SDS
PDF Converted by Omnipage into Text that Can be Managed by SDS
PDF Converted to ASCII Using Omnipage for Organizing the Work in SDS
PDF Not Effective for Intelligence Links Summary to Details Multiple
PDF Converted by Omnipage for Addressability Organization in SDS Know
PDF Print Prefered Familiar Way of Working Need Experience to Discove
PDF Converted by Omnipage to ASCII for Addressability Organization in

6309 -
631001 -          ..
631002 -         OmniPage Converts PDF into Text for SDS, But No Anchors
631003 -
631004 -
631005 - Gary continues...
631006 -
631007 -     4.  OmniPage Pro 12 does indeed OCR PDF files, so I now have a way
631008 -         of getting text out of nearly any PDF file. ref DRT 1 JY6N
631009 -
631010 -
631011 -
631012 -
6311 -

SUBJECTS
Anchors Added Automatically by SDS So Fact that Documents Do Not Have
Segment Large Documents Split into Segments of 100K Anchors Added Aut

6504 -
650501 -          ..
650502 -         Anchors Added Automatically by SDS
650503 -         Segment Large Documents Enables Better Knowledge Management
650504 -
650505 -
650506 - Gary continues...
650507 -
650508 -     5.  I am encountering the problem we always knew is a major issue,
650509 -         that none of the documents have any internal addressability.
650510 -         When the documents run to 200+ pages with heavy graphics,
650511 -         turning them into text for SDS and then splitting them into
650512 -         small enough pieces is simply too time consuming to be
650513 -         practical. I am simply going to have to find a way around that
650514 -         problem, but I don't have a clue yet. ref DRT 1 SY7H
650516 -  ..
650517 - Splitting 200 page text files into smaller text files of say 125K or
650518 - so, is fast and easy to do using MS Word, Wordpad and/or Notepad.  SDS
650519 - macro 0122 that adds HTML automatically adds anchors to every para,
650520 - and even without using 0122, once in SDS, the linking feature adds
650521 - anchors automatically.
650523 -  ..
650524 - Below, in the next record segment discuss best practice using SDS for
650525 - managing documents does not require writing everything down.
650526 - ref SDS 0 JU84
650527 -
650528 -       [On 030313 letter to Gary confirms planning to focus on learning
650529 -       and using SDS best practices. ref SDS 29 E97F
650530 -
650531 -
650532 -
650533 -
650534 -
650535 -
650536 -
6506 -

SUBJECTS
Goal for Next Six Months is to Enable Gary to Work Methodology for Ca
Tendency Use Bad Management Being Avoided by Gary's Determination and
Goal Next Six Months is to Enable Gary to Work Methodology for Captur
Dilemma Time Not Enough to Attend Every Meeting Write Everything Down
Capture Greater Share of the Record Using SDS Gary Making Progress Wr

7107 -
710801 -          ..
710802 -         Gary Using SDS to Capture Greater Share of Daily Information
710803 -         SDS Enables Flexibility Capturing Important Information
710804 -         Capture Important Information, Don't Write Everything Down
710805 -         Writing Everything Down Not Best Practice for Using SDS
710806 -
710807 -
710808 - Gary continues...
710809 -
710810 -
710811 -     6.  I had (temporarily) forgotten the extent to which these sorts
710812 -         of documents can take pages to express information that should
710813 -         take no more than paragraphs. ref DRT 1 JY8F
710815 -          ..
710816 -     7.  I hope to start using SDS at work shortly. At the moment I
710817 -         can't even keep up with meeting notes. ref DRT 1 RY8K
710819 -  ..
710820 - SDS does not require writing everything down from calls and meetings
710821 - nor tracking everything in documents.  Typically, enter information
710822 - into SDS within the time available that impacts objectives,
710823 - requirements and commitments, like using ordinary diary and journal
710824 - methods, illustrated by the record on 910520 that shows Morris Jones
710825 - using SDS. ref SDS 3 655O, per above. ref SDS 0 TY4G  Once something
710826 - is identified in the flexible structure of SDS, it can be fleshed out
710827 - later as needed with analysis to support planning and performance.
710828 - The goal of working "intelligently" using SDS is not perfection, but
710829 - improvement that adds value to communication by adding "intelligence"
710830 - to information in meetings, calls and documents, explained in POIMS.
710831 - ref OF 1 0367
710833 -  ..
710834 - Out of a 200 page document, pull out what is important and place it in
710835 - the record with links to related sources for context, and cite the
710836 - source if it cannot be linked directly, saying where it was found
710837 - using traditional bibliography methods.
710839 -  ..
710840 - These procedures provide opportunity to expand analysis later, if
710841 - needed, and maintains balance between thinking and doing, explained on
710842 - 030123, ref SDS 22 3V4L, and citing prior analysis of this core issue
710843 - developed on 030120. ref SDS 21 Y36H
710845 -  ..
710846 - Gary clarified his letter yesterday, per above, ref SDS 0 JU6I, saying
710847 - during our call this evening that he has started using SDS on the
710848 - Aerospace company project.  Daily working information is captured within the time
710849 - available on the job.  Rather than trying to write everything down,
710850 - Gary is focusing analysis on what is important to objectives,
710851 - requirements and commitments.  Analysis to be prepared for meetings,
710852 - calls and other work by understanding the record, using the SDS
710853 - "report" process explained in POIMS, ref OF 3 2300, aids the common
710854 - practice of doing "homework" to plan follow up, also, described in
710855 - POIMS. ref OF 3 8535  Gary's approach of not trying to write
710856 - everything down is "best practice" for using SDS, as set out in the
710857 - record on 030120, ref SDS 21 Y36H, and again on 030123 discussing
710858 - judgement that balances allocating time between thinking and doing.
710859 - ref SDS 22 3V4L
710861 -        ..
710862 -       [On 030313 letter to Gary confirms planning to focus on learning
710863 -       and using SDS best practices. ref SDS 29 E97F
710865 -  ..
710866 - Gary advised that next week there will be fewer meetings, because a
710867 - number of staff, including his boss, will be out of town all week.
710868 - This will provide more time for analysis.
710870 -  ..
710871 - Under all of the problems that augur against using SDS, per above,
710872 - ref SDS 0 1M6L, Gary is making remarkable progress in overcoming the
710873 - natural tendency to use bad management, that is particularly strong
710874 - in the software industry, reported previously on....
710875 -
710876 -       [On 030316 telecon discusses need to see SDS records transferred
710877 -       on Aerospace company project; no records indicates problems producing work
710878 -       product. ref SDS 30 865L
710879 -
710880 -
710881 -
710882 -
710883 -
710884 -
7109 -

SUBJECTS
POIMS Graphic Diagram Illustrating Concept of Automated Integration N
Gary Asked to Consider Making Improvements to Graphic at End of POIMS
Diagram Illustrating Concept of Automated Integration Needs Improveme
Integrated Features Complementary Data Bases SDS New Way of Working D

8006 -
800701 -  ..
800702 - POIMS Graphic on Automated Integration Needs Improvement
800703 -
800704 - We discussed briefly the advantage of SDS that integrates a critical
800705 - mass of tasks so that each supports the other, explained in POIMS,
800706 - ref OF 3 2688  Gary analysed this issue in his record on 030116 cited
800707 - in his letter on 030119, which was reviewed on that date. ref SDS 20
800708 - 346X
800710 -  ..
800711 - Gary affirmed understandings from his record on 030116 that
800712 - integration is a big advantage of SDS.
800714 -  ..
800715 - I asked Gary to take a look at the graphic for POIMS at the end of
800716 - POIMS in the section on Conclusion, ref OF 5 1116, that strives to
800717 - illustrated the power of integration for strengthening knowledge work,
800718 - and see if it can be improved.  The aim is to convey the idea that
800719 - "integration" is more than providing a lot of important functions, but
800720 - rather getting functions to complement each other, like assignments to
800721 - function keys on the keyboard, so there is harmony in doing the work,
800722 - as set out in POIMS. ref OF 2 8559
800724 -  ..
800725 - While we talked, Gary opened POIMS and examined the diagram that shows
800726 - the central concept of integration. He feels the fuzziness can be
800727 - reduced, and will ask someone to help.
800729 -  ..
800730 - Gary feels something can be done with this.
800732 -  ..
800733 - He will let me know.
800734 -
800735 -     [On 030312 followed up on improvements Joyce made to POIMS
800736 -     graphic. ref SDS 28 0001
800737 -
800738 -
800739 -
800740 -
800741 -
800742 -
800743 -
800744 -
8008 -