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: February 21, 2001 07:49 AM Wednesday; Rod Welch

Jack Park clarifies SDS role in architecture; discussess Open Source.

1...Summary/Objective
2...Architecture Clarified SDS Context Layer
.....IBIS with SDS Supports Lexus/Nexus and Energy Problem
3...OHS Core Can be Completed Within Calendar Year 2001
4...Patents Need to be Assigned to the Public
5...Open Source Can be Combined with IP and Copyright
6...IRS Dispute Personal Exposure for John
7...VC Seminar Planning Cancelled; Conover Action Plan Revised
8...Command Center and Control Room Application for SDS

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

1...The next step is to meet with Pacific Consultants to hear what they

CONTACTS 
0201 - Deneen Consulting
020101 - Mr. John Deneen

SUBJECTS
Knowledge Management Technology SDS Context Component Content Genera

1403 -
1403 -    ..
1404 - Summary/Objective
1405 -
140501 - Follow up ref SDS 41 0000, ref SDS 40 0000.
140502 -
140503 - Jack Park clarified architecture he is formulating applies SDS for a
140504 - content generator that adds context, rather than a traditional data
140505 - base.  He identifies a "knowledge" capability, which is undefined.
140506 - ref SDS 0 0G8I  The core engine of OHS design is the content layer,
140507 - which is SDS. ref SDS 0 EM6G  Functionality of DKR is mentioned, but
140508 - not explained.  There is discussion that SDS and IBIS can support
140509 - Lexus/Nexus (legal??) research, and help solve the energy problem.
140510 - ref SDS 0 GY6W   The core of OHS is anticipated to be complete this
140511 - year. ref SDS 0 039L  Jack offers constructive ideas to promote Open
140512 - Source after SDS and other capabilities are established, through
140513 - various license agreements. ref SDS 0 008P  John Deneen talked to Matt
140514 - Conover and Jack Park yesterday; he met Doug Engelbart for lunch at
140515 - SRI.  Will not attend VC seminar. ref SDS 0 SP35  John is developing
140516 - possible business deal with Pacific Consultants to support project.
140517 - ref SDS 0 K4RK   May have a meeting in a few weeks, when Jack returns
140518 - from Texas where he is writing a book. ref SDS 0 F77F  In the
140519 - afternoon, Matt Conover called and requested assistance on responsding
140520 - to the record on 010217. ref SDS 0 PS6G
140521 -
140522 -     [On 010223 Jack explains onion-skin architecture. ref SDS 43 C58M
140523 -
140524 -
140526 -  ..
1406 -
1407 -
1408 - Progress
1409 -
140901 - Jack is working on his book manuscript.  John Deneen said in a latter
140902 - call that the manuscript is due in one or two weeks, and he has to
140903 - incorporate information from contributors.  Jack is evidently in
140904 - Texas or is going to Texas to complete the manuscript, and then plans
140905 - to attend a seminar Jim Spohrer that will last several days.  The
140906 - result is that Jack is not available for a meeting during the next
140907 - two weeks.
140908 -
140910 -  ..
140911 - Architecture Clarified SDS Context Layer
140912 -
140913 - Received ref DRT 1 0001 from Jack Park responding to the copy of the
140914 - letter, ref DIP 1 0001, to John submitted yesterday, ref SDS 41 0001,
140915 - and discussing the project launch action plan prepared by Matt
140916 - Conover, reviewed on 010217. ref SDS 40 0001
140918 -  ..
140919 - Jack clarifies the role of SDS in the architecture (also, business
140920 - product model) submitted by Matt Conover on 010211. ref SDS 36 1V6L At
140921 - that time, review proposed the following scope for the role of SDS
140922 - that is likely perceived by the parties, based on past experience,
140923 - where people think of SDS as a "data base," ref SDS 36 SF4J, and so
140924 - stated......
140926 -      ..
140927 -     Most likely the principles are thinking of SDS as a component
140928 -     "data base," rather than an "intelligence" support engine for
140929 -     carrying out the work.
140931 -  ..
140932 - It helps a lot to get a link or at least the date of the record, in
140933 - order to find references to place the work in context.
140935 -     ..
140936 -    Simply say...
140937 -
140938 -             The record on 010211 says....
140940 -  ..
140941 - Today, Jack says.....
140942 -
140943 -     Actually, you have provoked me to make some improvements to my
140944 -     /ohs/ web site which I cannot do at this time owing to getting a
140945 -     book manuscript to Addison Wesley within the next few weeks.
140946 -     ref DRT 1 RH7G
140948 -      ..
140949 -     I think [the representation in the record on 010211 of SDS as a
140950 -     "data base," ref SDS 36 SF4J, is] ...backwards. ref DRT 1 7A7K
140952 -      ..
140953 -     I originally drew, with the help of Mary Keeler, a three layer
140954 -     architecture. At the top, I had a user interface -- a kind of
140955 -     viewing portal into the insides.  The insides were comprised of
140956 -     two other layers. At the bottom, I called the layer the raw data
140957 -     (even legacy data) layer.  In the middle, I had a knowledge layer.
140958 -     There, an ontology and link database would emerge while users at
140959 -     the top create more content at the bottom. ref DRT 1 VC7N
140961 -      ..
140962 -     Lee Iverson drew a three-bubble diagram similar to Jack's 3-layer
140963 -     architecture, per above.  One of his bubbles is called Content.
140964 -     That's my raw data layer. One of his bubbles is called Knowledge.
140965 -     Direct hit on my middle layer.  His third bubble is called
140966 -     Context, which, I think is a much better way to describe my user
140967 -     interface layer.  Lee did a much better job of thinking that layer
140968 -     through than I did. ref DRT 1 JD8K
140970 -      ..
140971 -     SDS is functionality at the Context layer that Lee describes
140972 -     ref DRT 1 UD9H
140973 -
140974 -         What is knowledge?   What is "context"?
140975 -
140976 -            See discussion on 000503. ref SDS 8 5033
140977 -            ..
140978 -            Again on 000615. ref SDS 12 6271
140980 -          ..
140981 -         How does "knowledge" differ from "context," based on Perice's
140982 -         work, from Mary Keeler's research reviewed on 000515,
140983 -         ref SDS 9 0042, and presented by Jack and Mary at SRI on
140984 -         000518? ref SDS 11 3528
140985 -
140986 -             [...below, John Deneen characterizes SDS as Command Center
140987 -             support. ref SDS 0 786K
140989 -          ..
140990 -         How does "knowledge" differ from this record?
140992 -          ..
140993 -         Suppose an "engine" is created and put to work on this record,
140994 -         as proposed on 000623, ref SDS 13 2915, and again on 001130.
140995 -         ref SDS 21 CC7K
140997 -          ..
140998 -         What does "knowledge" look like, so people can say when they
140999 -         see it, "this is knowledge," while this other stuff over here
141000 -         that is waiting to be processed by the engine is "information"
141001 -         or "raw data," "content," etc, per above?
141003 -          ..
141004 -         Still sounds like we're trying to get Hal to do our thinking
141005 -         for us???
141007 -  ..
141008 - Jack continues....
141009 -
141010 -     ....SDS (in my view) is not a database.
141011 -
141012 -     SDS is a content generator, one that clearly implies putting
141013 -     context on content. The Content/RawData layer will serve as the
141014 -     database for SDS.  By doing that, mining SDS work product for
141015 -     ontology is automatic. ref DRT 1 6E9K
141016 -
141017 -            [On 010222 John Deneen submitted an extract from Jack's
141018 -            letter to Pacific Consultants as an explanation of SDS
141019 -            scope. ref SDS 42 UL5I]
141021 -             ..
141022 -            [On 010223 Jack confirms SDS is core front-end for
141023 -            generating content of OHS. ref SDS 43 954L
141024 -
141025 -         "Automatic ontology" to mine SDS work product seems to align
141026 -         with Jack's planning on 001130 to develop subjects and links
141027 -         automatically. ref SDS 21 MN3W
141029 -          ..
141030 -         Why, though, does SDS need a Content/RawData layer to serve as
141031 -         a data base, when data and information are coming in the door,
141032 -         over the phone and through the mail, all day long, everyday?
141034 -          ..
141035 -         Who is going to grab up all this stuff up and put it in the
141036 -         Content/RawData data base
141038 -  ..
141039 - Jack says in a second letter today....
141040 -
141041 -     The core engine is the Content layer.
141042 -
141043 -     It will provide a variety of services to the Context layer, mostly
141044 -     covering the functionality of a DKR -- dynamic content repository.
141045 -     SDS will only have to know how to send it messages and receive
141046 -     messages from it. ref DRT 2 T47K
141047 -
141048 -            [On 010223 Jack does not mention DKR as part of OHS
141049 -            architecture. ref SDS 43 1X4O
141051 -             ..
141052 -            [On 010223 Jack confirms SDS is core front-end to generate
141053 -            content for OHS. ref SDS 43 954L
141055 -          ..
141056 -         On 000208 Eric Armstrong asked about the "core" of KM.
141057 -         ref SDS 6 0001
141059 -          ..
141060 -         Where is the "functionality" of DKR specified.
141062 -          ..
141063 -         Last year on 000505 reviewed specs prepared by Eric for a CDS,
141064 -         which was adopted for OHS on 000615. ref SDS 12 5880
141066 -          ..
141067 -         At that time on 0000615 the OHS/DKR team reported that a DKR
141068 -         was too difficult to design. ref SDS 12 6271
141070 -          ..
141071 -         On 000623 Jack explained ideas for an ontology "engine," and
141072 -         has since expanded the concept, for example on 001130.
141073 -         ref SDS 21 0001  No requirements, no specs no implementation
141074 -         has been prepared.
141076 -          ..
141077 -         On 001025 Doug Engelbart submitted an OHS launch plan that
141078 -         described an OHS with some functions in Eric's specs.  Doug
141079 -         also mentioned a DKR of sorts, but without any specifics on
141080 -         functions. ref SDS 19 C9WP
141082 -          ..
141083 -         This record shows specs have been prepared for an OHS, but
141084 -         nothing so far that identifies functions of a DKR.  None of
141085 -         the functions proposed for OHS have been implemented.
141087 -          ..
141088 -         POIMS defines a "DKR" for augmenting intelligence, ref OF 2
141089 -         6649, and SDS supports that scope.  Perhaps it could be
141090 -         considered a kind of OHS, though certainly not with the bells
141091 -         and whistles being contemplated. see 001130. ref SDS 21 0001
141093 -          ..
141094 -         SDS provides essential aid in producing a body of expanding
141095 -         "knowledge," as defined in POIMS. ref OF 2 0561  "Knowledge"
141096 -         was discussed at Intel on 000517, ref SDS 10 5096, and again at
141097 -         SRI on 000518. ref SDS 11 3528  SDS is necessarily "dynamic" in
141098 -         ways that nobody else can achieve, nor, in most cases
141099 -         contemplate, much less describe, relative to how technology
141100 -         can usefully advance beyond IT, as reported by Bill DeHart at
141101 -         PG&E on 000709. ref SDS 14 1029  This work product might be
141102 -         called a Dynamic Knowledge Repository (DKR), per planning on
141103 -         971021 for a "Repository of Knowledge." ref SDS 4 2635
141104 -
141105 -             [On 010223 Intel recommends focusing on applications that
141106 -             exist and help customers, rather than dreaming about a
141107 -             future vision; wireless industry going bankrupt.
141108 -             ref SDS 44 W56J
141110 -          ..
141111 -         We have a record showing this can be done, and that it is
141112 -         useful, i.e., saves time and money. see USACE report on
141113 -         971008. ref SDS 3 2979  SDS capability is best characterized
141114 -         as "computer aided thinking," rather than any effort to
141115 -         "automate" thinking, which some in the AI community strive to
141116 -         accomplish.  Going beyond POIMS for a more powerful DKR is
141117 -         extremely important work, so long as it is understood to be
141118 -         R&D, and that there is no inkling of whether it can be created
141119 -         in our lifetime, or will be useful, if produced.
141120 -
141122 -  ..
141123 - Jack continues in his first letter today....
141124 -
141125 -     SDS, itself, generates links, all within the Content/RawData
141126 -     layer.  It will be quite interesting for the Knowledge layer to
141127 -     think about the nature of those links, not to mention the words
141128 -     being used. ref DRT 1 ZZ4F
141130 -          ..
141131 -         We need careful thinking about requirements after people get
141132 -         experience working with SDS and learn what is entailed to
141133 -         organize the record.  People need experience working with
141134 -         granular flexible structures explained on 890523. ref SDS 1
141135 -         TP8O  The complexity of breaking the "big picture" into
141136 -         components of context requires experience applying the design
141137 -         of complementarity. ref SDS 1 LV59
141138 -
141139 -
141140 -
141141 -
141142 -
141143 -
141144 -
1412 -

SUBJECTS
IBIS Processing SDS Record Supports Lexus Research
Lexus/Nexus Research Supported by SDS and IBIS
IBIS Decision Support
IBIS Rigid Ineffective, 000218
AI Computer Science Cognitive Science
AI Cannot Think No Biological Drives Cannot Map Human Experience
Legal Problems Avoided with SDS
Law Lexus/Nexus Research
IBIS with SDS Aids Lexus/Nexus Research
Energy Problem Solved by Market Forces
Problems Energy Solve SDS and IBIS, Jack Park
IBIS and SDS Support Lexus/Nexus Research for Legal Practice, Jack Pa

2714 -
271501 -      ..
271502 -     IBIS with SDS Supports Lexus/Nexus and Energy Problem
271503 -
271504 -     In some sense, I think SDS is an extremely interesting Content
271505 -     generator.  What is particularly interesting is that its work
271506 -     product represents an individual user's *view* of events that it
271507 -     composes.  Imagine what happens when several individuals place SDS
271508 -     work product based on the same events into the same Content space.
271509 -     That's food for a great IBIS discussion, which, itself, is another
271510 -     Content generator.  The possibilities here are endless. I would
271511 -     think that such a system, in the context of Lexus/Nexus-like work
271512 -     would be of enormous value, not to mention thinking about the
271513 -     energy crunch, etc. ref DRT 1 SI4K
271514 -
271515 -         We have been trying to solve the energy problem since 000120.
271516 -         ref SDS 5 7592
271518 -          ..
271519 -         IBIS was reviewed recently on 010211 in connection with Matt
271520 -         Conover's diagram incorproating Jack's OHS ideas. ref SDS 36
271521 -         UP5K  On 010127 IBIS came up considering SDS has a certain
271522 -         "logic" support. ref SDS 32 2P7G  Previously on 010114 IBIS
271523 -         was cited in analysis of "deliberatey" managed conversation.
271524 -         ref SDS 23 1550
271526 -          ..
271527 -         On 001220 one authority urges caution to avoid rigid IBIS
271528 -         requirements that stifle creativity and participation.
271529 -         ref SDS 22 RD9N  This aligned with earlier warnings on 000218.
271530 -         ref SDS 7 7050
271531 -
271532 -
271533 -
2716 -

SUBJECTS
Development Plan
OHS Module Core Can Be Complete within Calendar Year 2001
OHS Core Engine Available Perhaps within Calendar Year 2001, Jack Par
Schedule OHS Mostly Complete by End of 2001
OHS Schedule Mostly Complete by End of 2001, Jack Park
OHS Mostly Complete by End of 2001, Jack Park

3308 -
3309 - 1254
331001 -  ..
331002 - OHS Core Can be Completed Within Calendar Year 2001
331003 -
331004 - Received a second letter, ref DRT 2 0001 commenting further on the
331005 - letter, ref DIP 1 0001, submitted 010220. ref SDS 41 0001
331006 -
331007 - Jack cites the record on 010217, which was submitted with the letter
331008 - on 010220, and notes in relation to a task proposed by Matt Conover
331009 - that.....
331010 -
331011 -      Jack Park and Doug can meet to flesh out schedules for each of
331012 -      their modules.
331013 -
331014 -          This is a good task.  The OHS/DKR team at SRI has been
331015 -          working on this for a year; so, identifying modules and
331016 -          determing work packages, time and cost would be helpful.
331017 -          ref SDS 40 DH5J
331019 -  ..
331020 - Jack submits today an opinion that the OHS core engine, explained
331021 - above, ref SDS 0 EM6G, will be completed perhaps within this calendar
331022 - year. ref DRT 2 7P6H
331023 -
331024 -     [On 010223 Jack reports it will not be easy to sort out all the
331025 -     details of the OHS architecture. ref SDS 43 N5RW
331027 -      ..
331028 -     [On 010223 report at world conference in Paris that wireless
331029 -     telecom industry is going bankrupt. ref SDS 44 FM6J
331031 -      ..
331032 -     [On 010223 Intel tells world conference in Paris to work on
331033 -     implementing existing technologies, rather than continuing to
331034 -     pursue future visions. ref SDS 44 W56J
331035 -
331036 -
331037 -
331038 -
331039 -
331040 -
3311 -

SUBJECTS
Open Source Can be Combined with IP Copyright
Open Source Developement with Adequate Management Operations
Licneses can Limit Open Source Development to Maintain Competitive Ad
Patents Assigned to Public or OHS Team
Open Source Must be Available on Proprietary Project for Jack to Part
Ownership Rewards Lost Using Funding to Advance SDS Requires Open Sou

4208 -
420901 -  ..
420902 - Patents Need to be Assigned to the Public
420903 - Open Source Can be Combined with IP and Copyright
420904 -
420905 - Follow up ref SDS 41 NB6M.
420906 -
420911 -  ..
420912 - Jack says today that in any open source effort, the owner of the
420913 - copyright to the IP that is the product has the right to do
420914 - proprietary things with that product. ref DRT 2 008P
420915 -
420916 -     This part of Jack's letter responds to the note in the letter on
420917 -     010220 that business arrangements need to be worked out in order
420918 -     to collaborate effectively through an alliance for Jack to
420919 -     contribute to SDS development, ref DIP 1 ZT7N, cited, as well in
420920 -     the SDS record yesterday on 010220. ref SDS 41 NB6M
420921 - ..
420922 - That is because the owner of the IP has the right to construct
420923 - OSS licenses any way he/she chooses.  One for *them*, and another for
420924 - *us*. The downside to such licensing practices is that the OSS
420925 - community tends not to participate in double-licensed projects.  The
420926 - primary thought that I inject into the OHS open source licensing is
420927 - this....
420928 -
420929 -      ....any entity that chooses to use OHS as a substrate for a
420930 -      proprietary product gives up the right to block any other entity
420931 -      from implementing the same or similar functionality. No blockades
420932 -      may be setup to impede the evolution of OHS in any direction it
420933 -      may want/need to go.
420934 -
420935 - ..
420936 - Proprietary products may "plug" into OHS as a substrate, but
420937 - they may not sue anyone else for doing the same product, open or
420938 - otherwise.  That means, any patents will necessarily need to be
420939 - assigned to the public, or at least, to the OHS development
420940 - environment. ref DRT 2 005J
420942 -  ..
420943 - Jack will not work on any project that is not, at least, available to
420944 - open source.  He does not mind working on proprietary IP, but will
420945 - only do so with the understanding that he is clear to do the same
420946 - thing in the open community.  He feel this reduces his value to a
420947 - proprietary projects. ref DRT 2 IF4F
420948 -
420949 -
420950 -
420951 - //
420952 -
420953 -
4210 -

SUBJECTS
Meeting John on Joining Welch Team
VC Seminar Not Feasible, Necessary to Attend

4504 -
4505 - 1152
450601 -  ..
450602 - IRS Dispute Personal Exposure for John
450603 -
450604 - John called this afternoon to follow up correspondence yesterday.
450605 -
450606 - John has been in the mountains the past several days with his two
450607 - kids.
450609 -  ..
450610 - He is facing a personal financial situation involving the IRS.  This
450611 - is the tax dispute discussed on 000924, ref SDS 16 0001, and again on
450612 - 000927. ref SDS 17 R39F  There is a tax payment deadline coming up
450613 - next week which will take up a lot of John's time.
450614 -
450615 - //
450616 -
450617 -
450618 -
450619 -
4507 -

SUBJECTS
VC Seminar Planning

4803 -
4804 - 1152
480501 -  ..
480502 - VC Seminar Planning Cancelled; Conover Action Plan Revised
480503 -
480504 - Follow up ref SDS 41 0001, ref SDS 40 0001.
480505 -
480506 - John talked to Matt Conover yesterday for about 10 hours, and he
480507 - talked to Jack Park for an hour or so.
480508 -
480509 -     John advised that Jack will not be available for a meeting during
480510 -     the next two weeks, because he is going to Texas to finish the
480511 -     manuscript for a book he has to submit.  The following week he is
480512 -     attending a seminar Jim Spohrer is conducting.
480514 -        ..
480515 -       [On 010222 Jack confirmed he is out of town next week.
480516 -       ref SDS 42 JM8E
480518 -        ..
480519 -       [On 010223 Jack going to Texas to present a paper on using
480520 -       technology for education. ref SDS 43 WW6G
480521 - ..
480522 - He, also, seemed to indicate he had lunch Doug Engelbart at SRI,
480523 - per below. ref SDS 0 AJ6K
480524 - ..
480525 - John said Matt's plan to participate with a booth at the SDForum
480526 - VC forum in April, proposed in Matt's letter on 010216, and rviewed on
480527 - 010217, ref SDS 40 UM6M, is not a useful exercise.
480529 -  ..
480530 - He explained that VC money is in a freeze at this time.
480531 -
480532 -     This aligns with letter to John on 010220, ref DIP 1 PL6G, and
480533 -     explained in the record on that date. ref SDS 41 PI6G
480535 -  ..
480536 - John feels that Jim Spohrer can obtain money for the venture being
480537 - discussed.
480538 -
480539 -     This addresses the letter to John on 010220 asking why meeting
480540 -     with Jim Spohrer. ref DIP 1 U67N
480541 -
480542 - ..
480543 - Did not discuss schedule to complete business planning details
480544 - proposed by Matt, reviewed on 010217. ref SDS 40 6Q9N
480546 -  ..
480547 - John concurred with the letter on 010221 that agreement needs to be
480548 - worked out to establish the core team, ref DIP 1 ZT7N, which is part
480549 - of Matt's organization planning on 010217. ref SDS 40 GH5A
480551 -  ..
480552 - He feels once business planning is done, then a meeting with Jim
480553 - Spohrer could be productive.
480554 -
480555 -
480557 -  ..
4806 -
4807 -
4808 - 1806
4809 -
480901 - Matt Conover called.
480902 -
480903 - Matt appreciated getting the copy of the letter, ref DIP 1 0001, to
480904 - John Deneen, linked to the record on 010217, ref SDS 40 0001, which
480905 - reviewed Matt's letter on 010216. ref DRP 1 0002
480907 -  ..
480908 - Matt plans to submit feedback to clarify understandings in SDS that
480909 - are attributed to his work product, and which he feels do not
480910 - accurately reflect his intent.
480911 -      ..
480912 -      Feedback is essential to refine accuracy of communication,
480913 -      as reported during the meeting at SRI on 000518. ref SDS 11 O43M
480915 -       ..
480916 -      On 950721 management standards require feedback loops for
480917 -      effective communication. ref SDS 2 1593
480919 -  ..
480920 - Matt said it takes a long time to write down issues identified in the
480921 - record on 010217.  He asked for ideas on how to expedite feedback.
480923 -  ..
480924 - Investing time to organize feedback deepens understanding of
480925 - correlations, implications and nunace by adding alignement with
480926 - objectives, requirements and commitments in relation to prior events,
480927 - called traceability to original sources, called out by ISO criteria
480928 - reviewed on 950721. ref SDS 2 1740
480929 - ..
480930 - Jack Park's letter this morning is an example of expediting
480931 - feedback by using cut and paste to capture issues in SDS records for
480932 - ogranizing a response. ref DRT 1 0001  This can be strengthened by
480933 - linking to the original source, as recommended by Eugene Kim on
480934 - 001126. ref SDS 20 QW8I
480936 -  ..
480937 - Linking takes extra take, so for now, simply identifying the original
480938 - source is adequate.
480940 -  ..
480941 - Pointed out that all of the issues in the record on 010217 dealing
480942 - with the VC conference, have been eliminated, since John reported in a
480943 - call earlier today that the SDForum VC conference will not be pursued,
480944 - per above. ref SDS 0 KN6O
480946 -  ..
480947 - Matt will submit a response in light of this understanding.
480948 -
480949 -      [On 011011 Matt objected to providing feedback; proposed using
480950 -      speech recognition and recording technologies to avoid the need
480951 -      for refining accuracy of the record. ref SDS 46 RC5O
480952 -
480953 -
480954 -
4810 -

SUBJECTS
New Development Contact Software Engineers Want to Use SDS for Contro
Control Room Management, John Deneen New Contact
Pacific Consultants May Support Doug's OHS Project Have Military Cont
Pacific Consultants Met on OHS Project, John Deneen
Pacific Consultants New Development Contact Has Military Contract, We
Military Contract for Soldier Field Management, John Deneen
SDS Provides Command Center Capability, John Deneen
SRI Provides Geo Graphic Mapping ???, John Deneen
Command & Control of the Record, Context
Command and Control Center, 010221
SDS Development Interest for Finance Product Integration, John Deneen
Command Control Center Application for SDS

6114 -
6115 - 1152
611601 -  ..
611602 - Command Center and Control Room Application for SDS
611603 -
611604 - Follow up ref SDS 39 K4RK.
611605 -
611606 - John reported progress with the contact he made at the wireless
611607 - conference, and reported on 010216. ref SDS 39 K4RK
611609 -  ..
611610 - The name of the organization is.....
611611 -
611612 -
611613 -                        Pacific Consultants
611614 -
611616 -  ..
611617 - John understands this firm has a contract with the military to develop
611618 - technology for the soldier and command operations of the future,
611619 - generally called.....
611620 -
611621 -                           Land Warriar
611622 -
611623 - ..
611624 - They got the contract when Ratheon was unable to perform.
611626 -  ..
611627 - John believes this company is well funded, and has on staff software
611628 - engineers who can do production work; he indicated his contacts so far
611629 - are enthusiastic about developing SDS as a Command Center application
611630 - somehow, someway.
611631 - ..
611632 - John seemed to indicate having introduced his contacts at
611633 - Pacific Consultants to Doug Engelbart and to Carla Woodworth, who
611634 - works at SRI, and was designated on 001017 as a systems trainer and
611635 - implementor for the OHS project. ref SDS 18 01DP
611636 -
611637 -     Carla's experience training military people on a related program,
611638 -     called "Urban Warriar," reported on 001017 may support this
611639 -     opportunity. ref SDS 18 MO8J
611641 -  ..
611642 - Sounded like they all had lunch at SRI last week, and discussed ideas
611643 - for helping Pacific Consultants.
611645 -  ..
611646 - John described today a general idea for Welch, SRI and others to
611647 - provide complimentary capability that enables Pacific Consultants to
611648 - meet its commitment to the military, and/or offer expanded support.
611649 - ..
611650 - The scope of this effort is anticipated to be along the lines
611651 - set out in the letter from Matt Conover on 010211 that describes
611652 - satallite photography, OHS and Lexus/Nexus for facilities management.
611653 - ref SDS 36 UP5K and Matt's diagram. ref SDS 36 1V6L
611654 - ..
611655 - We considered the role of SDS in this scheme, per question on
611656 - 010211. ref SDS 36 8S7J
611658 -  ..
611659 - John described SDS as "Command Center" support.
611660 -
611661 - "Command Center" aligns with POIMS explanation of Command and Control.
611662 - ref OF 2 1113  The idea was discussed at Intel on 000517. ref SDS 10
611663 - QF8L  POIMS explains Command and Control as providing "context," which
611664 - aligns with Jack Park's idea for SDS explained above. ref SDS 0 3Z9G
611665 -
611666 -        [On 010222 John submitted a letter to Pacific Consultants
611667 -        identifying application of SDS for control room/command
611668 -        center/medical ER, and general shift-change and/or
611669 -        rotating-shift work environments. ref SDS 42 614H
611670 -    ..
611671 -    We noted that SDS doesn't require a physical Command Center,
611672 -    since it is used every day in San Francisco, Concord, Menlo Park,
611673 -    anywhere necessary.
611675 -     ..
611676 -    John feels this reflects a flexible Command Center capability that
611677 -    could be useful in a military setting, possibly in combination with
611678 -    satallite communications.
611679 -
611680 -        [...above Jack explains SDS is the context layer of his 3-layer
611681 -        architecture. ref SDS 0 3Z9G
611683 -         ..
611684 -        [On 010222 John Deneen submitted an extract from Jack's letter
611685 -        to Pacific Consultants as an explanation of SDS scope.
611686 -        ref SDS 42 UL5I]
611687 - ..
611688 - We reviewed the record showing SDS is the only functioning
611689 - element of the deliverables being contemplated to support Pacific
611690 - Consultants. Other capabilities do not exist, and reflect aspects of
611691 - AI efforts, which nobody has yet been able to produce. see discussion
611692 - above, ref SDS 0 3Z9G, and previously on 001025. ref SDS 19 LR6N,
611693 - also, review on 001130. ref SDS 21 HM5J
611695 -  ..
611696 - At this time, the most we can promise is to deliver SDS, and develop
611697 - enhancements in a follow on product.  R&D may yield innovations along
611698 - the lines Jack Park proposed for SDS on 001130. ref SDS 21 0001 Such
611699 - future improvements are unproven with respect to development and
611700 - usefulness.
611701 - ..
611702 - John expects to be tied up for several weeks working on personal
611703 - matters.
611705 -  ..
611706 - The next step is to meet with Pacific Consultants to hear what they
611707 - want to accomplish, and consider how SDS and OHS development, might
611708 - contribute to their program.
611710 -  ..
611711 - Sounds like this meeting will occur in two weeks or so, when Jack gets
611712 - back from Texas and finishes up with the seminar Jim Spohrer is
611713 - presenting, per above. ref SDS 0 SP35
611714 -
611715 -     [On 010223 John reports having met on 010122, along with Matt
611716 -     Conover, Jim Murray at Pacific Consultants, Lee Iverson with SRI
611717 -     and Jim Spohrer at IBM. ref SDS 45 008G
611718 -
611719 - ..
611720 - No plans were discussed to do business planning set out in
611721 - Matt's letter reviewed on 010217. ref SDS 40 S56K
611722 -
611724 -  ..
6118 -
6119 -
6120 - 2111
6121 -
612101 - John called back.
612102 -
612103 - He suggests attending the meeting at SRI tomorrow for Doug's
612104 - presentation at noon.
612106 -  ..
612107 - John's contact with Pacific Consultants may attend.  His name is....
612108 -
612109 -
612110 -                         John Murray
612111 -
612112 - ..
612113 - John will call in the morning to confirm that John Murray will
612114 - either attend Doug's event at SRI, or he will be in the office and can
612115 - meet after Doug's presentation at Pacific Consultant's office in
612116 - Mountain View. // John indicated that Doug is not enthusiastic about
612117 - working with Pacific Consultants.
612118 -
612119 -     [On 010222 received letter from John Deneen asking John Murray to
612120 -     call about meeting on 010222. ref DRP 2 0001
612122 -      ..
612123 -     [On 010223 John reports having met on 010122, along with Matt
612124 -     Conover, Jim Murray at Pacific Consultants, Lee Iverson with SRI
612125 -     and Jim Spohrer at IBM. ref SDS 45 008G
612126 -
612127 -
612128 -
612129 -
612130 -
612131 -
612132 -
612133 -
612134 -
612135 -
612136 -
612137 -
612138 -
612139 -
612140 -
612141 -
612142 -
6122 -
Distribution. . . . See "CONTACTS"