CONTACTS 

SUBJECTS
Called Clarify Scope of Inquiry on SDS Support for Knowledge Managem

1603 -
1603 -    ..
1604 - Summary/Objective
1605 -
160501 - Follow up ref SDS 7 0000. ref SDS 6 0000.
160502 -
160503 -
160504 -
160505 -
160507 -  ..
1606 -
1607 -
1608 - Progress
1609 -
160901 - Called John at the number listed in his letter received on 060309.
160902 - ref SDS 7 LN47
160904 -  ..
160905 - John does not seem to know how information he is gathering on KM
160906 - tools will be used.  He is handing it over to someone, who asked him
160907 - to collect it.
160909 -  ..
160910 - John is new with Boeing.
160912 -  ..
160913 - John is unfamiliar with the ASB system, and so has not seen the ASB on
160914 - SDS.
160916 -     ..
160917 -    Background on ASB for SDS is reported on 041119. ref SDS 3 N28O
160919 -  ..
160920 - Gave him my phone number to call if he has questions.
160921 -
160922 -     [On 060314 Gary cites this call in a follow up letter to John
160923 -     transmitting answers to questions about SDS support for KM.
160924 -     ref SDS 9 OX6N
160925 -
160926 -     [On 060317 called John to follow up discuss thinking about KM in
160927 -     relation to John's recent class on FAR requirements for
160928 -     procurement and contract management, which fits John's assignment
160929 -     to develop KM for program management. ref SDS 10 AQ5H
160930 -
160931 -
160932 -
160933 -
160934 -
160935 -
1610 -

SUBJECTS
Prepare Draft Response Discussion to Inquiry on SDS Support for KM

1703 -
1704 - 1044
170501 -  ..
170502 - Draft Response Explain SDS Support Knowledge Management Submitted
170503 -
170504 - Follow up ref SDS 7 UZ7N.
170505 -
170506 - Submitted the following letter to Gary...
170507 -
170508 -    1.  Subject: Information on SDS for KM
170509 -        Date: Fri, 10 Mar 2006 10:44:29 -0800
170516 -         ..
170517 -    2.  Gary,
170519 -         ..
170520 -    3.  This responds to your letter yesterday, transmitting a letter
170521 -        from John Refling on March 8 with questions about SDS.  I
170522 -        talked to John this morning.  He has not seen the ASB, which
170523 -        explains why Boeing wants another explanation of SDS.
170525 -         ..
170526 -    4.  If possible, we should point John and his team to the ASB with
170527 -        Boeing's official explanation on most of the questions he asks.
170528 -        Additionally, here are responses you and Gil can consider
170529 -        listed in the order presented by John's letter dated March 8,
170530 -        2006...
170531 -
170532 -        1.  Is SDS proprietary or export controlled?
170534 -             ..
170535 -            SDS is proprietary and is not export controlled.
170537 -             ..
170538 -        2.  Is the data/knowledge it generates proprietary or export
170539 -            controlled?
170541 -             ..
170542 -            SDS work product is proprietary and not export controlled.
170544 -  ..
170545 - Turns out his is an error, because it leaves out the word "not", as
170546 - intended in the initial draft prepared yesterday, 060309. ref SDS 7
170547 - 6V5Y
170548 -
170549 -                [...see below Jack Park asks about this issues.
170550 -                ref SDS 0 WN5L
170552 -                 ..
170553 -                [...see below respond to Jack noting error in para 2.
170554 -                ref SDS 0 434B
170556 -                 ..
170557 -                [On 060312 submitted corrected letter to Gary and Gil,
170558 -                with copy to Jack. ref SDS 8 175N
170560 -  ..
170561 - Response continues...
170562 -
170563 -        3.  If new intellectual property is involved, what is it and
170564 -            who owns it?  Patents granted, pending?
170566 -             ..
170567 -            Rod Welch owns the intellectual property of the SDS
170568 -            program.  Patent filing is planned for later this year.
170570 -             ..
170571 -            SDS has many innovations for managing chronology, context,
170572 -            and connections that are not used by other tools, and it
170573 -            combines methods common to other tools in unique ways, as
170574 -            explained in the ASB.  The basic "intelligence" recipe of
170575 -            "plan, perform, report" converts information into
170576 -            "knowledge," as set out in the ASB with citations to
170577 -            POIMS...
170578 -
170579 -               http://www.welchco.com/03/00050/01/09/01/02/00030.HTM#6649
170581 -             ..
170582 -            An example of work product is on the Internet...
170583 -
170584 -               http://www.welchco.com/sd/08/00101/02/04/12/30/140051.HTM
170586 -  ..
170587 - Another example doing Boeing work is the case study on filing the ASB,
170588 - listed on 041119. ref SDS 3 N28O
170590 -  ..
170591 - Draft response continues...
170592 -
170593 -            SDS makes it possible to perform this kind of
170594 -            "intelligence" work in a few hours, rather than a few weeks
170595 -            with conventional tools.
170597 -             ..
170598 -        4.  Brief history including who / where developed, e.g., COTS
170599 -            or internally developed;
170601 -             ..
170602 -            History of SDS at Boeing is listed in the ASB under
170603 -            "Background" and has a link to a record on July 23, 2000
170604 -            that presents SDS development history.
170605 -
170606 -               http://www.welchco.com/sd/08/00101/02/00/07/23/141404.HTM#0008
170608 -             ..
170609 -            Briefly, initial design concept formed in 1985.  Many
170610 -            iterations over the years yielded a workable design.
170611 -            Building effective tools for "knowledge" that improve
170612 -            conventional IT requires continual refinements based on
170613 -            experience, including the past three years at Boeing under
170614 -            Gil Caughman's leadership.
170616 -             ..
170617 -            SDS is not commercially sold.
170619 -             ..
170620 -        5.  What it does, in what processes is it used;
170622 -             ..
170623 -            The ASB explains SDS supports the "intelligence" process of
170624 -            plan, perform, report" for "personal and organizational
170625 -            memory and management."  A link in the ASB shows an outline
170626 -            of SDS "intelligence support"...
170627 -
170628 -               http://www.welchco.com/03/00050/01/09/03/02/03/0309.HTM#LW5I
170630 -             ..
170631 -            SDS supports 8 steps for a practice of "Communication
170632 -            Metrics" where the core metric of communication is accuracy
170633 -            maintained by chronology, context, and connections.  The 8
170634 -            steps are listed in POIMS...
170635 -
170636 -               http://www.welchco.com/03/00050/01/09/01/02/00030.HTM#685K
170638 -             ..
170639 -            These 8 steps improve the core "process" of literacy --
170640 -            reading and writing -- by enabling people to generate
170641 -            "knowledge" rather than "information" in traditional
170642 -            "documentation." Accurate communications improves personal
170643 -            and organizational memory, which in turn makes
170644 -            communication effective for getting things done.  That's
170645 -            the process of SDS.
170647 -             ..
170648 -            In a business setting like Boeing SDS adds value to
170649 -            meetings, calls and email, illustrated by the case study
170650 -            listed on 050812...
170651 -
170652 -               http://www.welchco.com/sd/08/00101/02/05/08/12/102500.HTM
170654 -             ..
170655 -        6.  What other innovative uses might be possible?
170657 -             ..
170658 -            SDS use for general management, engineering management,
170659 -            law, government, education, etc, are listed on 020708...
170660 -
170661 -               http://www.welchco.com/sd/08/00101/02/02/07/08/104022.HTM#MZ6O
170663 -             ..
170664 -        7.  Pointers to other KM tools not commonly known.
170666 -             ..
170667 -            Recently, on February 11, SRI announced release of Open
170668 -            IRIS, which fits goals of Knowledge Management...
170669 -
170670 -               http://www.welchco.com/sd/08/00101/02/06/02/11/141753.HTM
170672 -             ..
170673 -            Jack Park is the sponsor for Open Iris at SRI.  His email
170674 -            address is park@AI.SRI.COM.  By copy will notify Jack of
170675 -            this referral for follow up.
170677 -         ..
170678 -    5.  Thanks.
170680 -         ..
170681 -    6.  Rod
170682 -
170683 -
170684 -
1707 -

SUBJECTS
Error Draft SDS Support for Knowledge Management Response Request Bo

2303 -
2304 - 1149
230501 -  ..
230502 - Feedback Shows Error in Draft Respons Para 2
230503 -
230504 - Follow up ref SDS 5 4Q5T, ref SDS 4 U171.
230505 -
230506 - Received feedback from Jack Park on the copy he received of the letter
230507 - sent to Gary, per above, ref SDS 0 V184, saying...
230508 -
230509 -    1.  Subject: Re: Information on SDS for KM
230510 -        Date: Fri, 10 Mar 2006 11:31:59 -0800
230514 -         ..
230515 -    2.  Just one little comment.
230517 -         ..
230518 -    3.  Where you said...
230519 -
230520 -           SDS work product is proprietary and not export controlled.
230521 -           ref SDS 0 JJ5X
230522 -
230523 -        ...it seems to me that you might need to clarify SDS work
230524 -        product ownership.  It's not clear from this, given that SDS is
230525 -        proprietary and is owned by Rod Welch, whether the work product
230526 -        is also owned by Rod Welch, no matter where it is generated.
230527 -        We both know that the work product Gary creates at Boeing is
230528 -        owned, and still proprietary -- but it could be public instead
230529 -        -- by Boeing and not Rod Welch.  If that's not the case, then
230530 -        why on earth would Boeing even let Gary do what he is doing
230531 -        with it?
230533 -         ..
230534 -    4.  Cheers,
230535 -
230536 -        Jack
230538 -  ..
230539 - Helpful feedback from Jack today further repairs former rift reported
230540 - on 040315. ref SDS 2 0001
230541 -
230542 -
230543 -
230544 -
230546 -  ..
2306 -
2307 -
2308 - 1210
2309 -
230901 - Submitted response to Jack saying...
230902 -
230903 -    1.  Subject: SDS Work Product Proprietary
230904 -        Date: Fri, 10 Mar 2006 12:16:22 -0800
230910 -         ..
230911 -    2.  Jack,
230913 -         ..
230914 -    3.  Thanks for feedback on this issue, shown in your letter below.
230916 -         ..
230917 -    4.  I don't follow your point.
230919 -  ..
230920 - After sending this letter, further review revealed an error in para 2
230921 - of the letter to Gary and Gil, per above. ref SDS 0 JJ5X  Left out
230922 - the word "not," so the response should have been...
230923 -
230924 -            SDS work product is not proprietary and not export
230925 -            controlled.
230926 -
230927 -                [...see below Jack Park asks about this issues.
230928 -                ref SDS 0 WN5L
230930 -                 ..
230931 -                [...see below submitted correction to Boeing and
230932 -                commended Jack's feedback. ref SDS 0 434B
230933 -
230935 -  ..
230936 - Letter to Jack continues...
230937 -
230938 -    5.  My sense is that the design and so forth of SDS is something I
230939 -        developed.  If you, Gary or anyone else uses SDS to create work
230940 -        product, that belongs to you, in the same way that if you buy a
230941 -        pencil and paper and jot down some notes, the folks who
230942 -        developed the pencil, paper, wordprocessor, etc, have
230943 -        proprietary rights to the design of the tools, but the "work
230944 -        product" you generate, e.g., a list of groceries, an email, a
230945 -        specification for an airplane, etc, belongs to you.  If you buy
230946 -        a shovel and dig a ditch, you own the ditch and the spoil.
230948 -         ..
230949 -    6.  Am I missing something in the term "work product"?
230950 -
230951 -                [...see below submitted correction to Boeing and
230952 -                commended Jack's feedback. ref SDS 0 434B
230954 -         ..
230955 -    7.  Possibly the design of SDS records in which the "work product"
230956 -        is presented creates an issue of "ownership."  I guess I am
230957 -        confused.  I separate content from presentation.
230958 -
230959 -            [...see below Jack responds to this comment. ref SDS 0 LN5L
230961 -         ..
230962 -    8.  Thanks for adding perspective.  My guess is they are looking
230963 -        for something like Open Iris, and not something for doing 8
230964 -        steps that "looks like work dressed in coveralls."
230966 -         ..
230967 -    9.  Rod
230969 -         ..
230970 -   10.  PS.  Did Gary answer your questions presented on 060131?
230971 -
230972 -
230974 -  ..
2310 -
2311 -
2312 - 1253
2313 -
231301 - Further review showed that Jack's feedback points out an error in para
231302 - 2, ref SDS 0 JJ5X, which should have read...
231303 -
231304 -            SDS work product is not proprietary and not export
231305 -            controlled.
231307 -               ..
231308 -              [On 060312 submitted corrected letter to Gary and Gil,
231309 -              with copy to Jack. ref SDS 8 175N
231311 -  ..
231312 - Sent thank you to Jack, with copy to Gary and Gil for correcting the
231313 - response to John...
231314 -
231315 -    1.  Subject: SDS Work Product Not Proprietary
231316 -        Date: Fri, 10 Mar 2006 13:06:29 -0800
231323 -         ..
231324 -    2.  Jack,
231326 -         ..
231327 -    3.  I think I see your point now.  There is an error in para 2 of
231328 -        the letter submitted to Gary and Gil this morning.  The
231329 -        response should read...
231330 -
231331 -            "SDS work product is not proprietary and not export
231332 -            controlled."
231333 -
231334 -        ...and in accordance with my letter to you a few moments ago
231335 -        responding to your comment raising this issue.
231336 -
231337 -            [On 060312 submitted corrected letter to Gary and Gil, with
231338 -            copy to Jack. ref SDS 8 175N
231340 -         ..
231341 -    4.  Again, thanks for feedback, which incidentally is "step 8" in
231342 -        the 8 steps of Com Metrics. ref OF 6 365F
231343 -
231344 -            [On 060322 finally got some feedback process working at
231345 -            Kaiser. ref SDS 11 NU6M
231347 -         ..
231348 -    5.  This further illustrates the challenge of email you mentioned
231349 -        on 010908, ref SDS 1 YF3I, and set out in POIMS. ref OF 4 YF5L
231351 -         ..
231352 -    6.  Since I intended to say "not" my mind read it into the text
231353 -        even though it was omitted.  Collaboration that yielded timely
231354 -        feedback helped save the day.
231356 -         ..
231357 -    7.  Thanks again.
231359 -         ..
231360 -    8.  Rod
231362 -         ..
231363 -    9.  PS.  By copy notifying Gary and Gil to make this change in
231364 -        their submittal to John.
231365 -
231366 -            [On 060312 submitted corrected letter to Gary and Gil, with
231367 -            copy to Jack. ref SDS 8 175N
231368 -
231369 -
231371 -  ..
2314 -
2315 -
2316 - 1347
2317 -
231701 - Gil responded to Jack saying...
231702 -
231703 -    1.  Subject: RE: SDS Work Product Not Proprietary
231704 -        Date: Fri, 10 Mar 2006 13:24:54 -0800
231710 -         ..
231711 -    2.  Jack,
231713 -         ..
231714 -    3.  You guys just talked past each other. The Work Product gary
231715 -        creates, The software SDS is owned by Rod.  We had a Boeing
231716 -        prepared License agreement for use under evaluation purposes.
231717 -        This agreement was constructed by the general procurement of
231718 -        shared services.
231720 -         ..
231721 -    4.  Gil
231722 -
231723 -          [...see below Jack comments on Gil's letter. ref SDS 0 4T8J
231724 -
231725 -          [On 060312 submitted corrected letter to Gary and Gil, with
231726 -          copy to Jack. ref SDS 8 175N
231727 -
231728 -
231729 -
231731 -  ..
2318 -
2319 -
2320 - 1448
2321 -
232101 - Received a response from Jack to the letter answering his comments,
232102 - per above. ref SDS 0 GF7N
232104 -  ..
232105 - Jack says...
232106 -
232107 -    1.  Subject: Re: SDS Work Product Proprietary
232108 -        Date: Fri, 10 Mar 2006 14:35:50 -0800
232112 -         ..
232113 -    2.  Nope, you're not missing anything. You echoed what I suggested.
232114 -        I was merely pointing out that there is a possible unlicensed
232115 -        inference in what you said in what you originally sent out that
232116 -        the work product might actually be owned by you.
232117 -
232118 -            [On 060312 submitted corrected letter to Gary and Gil, with
232119 -            copy to Jack. ref SDS 8 175N
232121 -         ..
232122 -    3.  No big deal.
232123 -
232124 -        Jack
232125 -
232126 -
232127 -
232128 -
232129 -
232131 -  ..
2322 -
2323 -
2324 - 1451
2325 -
232501 - Received copy of a letter from Jack answering Gil's observation about
232502 - communications, per above. ref SDS 0 MP6M
232503 -
232504 -    1.  Date: Fri, 10 Mar 2006 14:39:47 -0800
232511 -         ..
232512 -        Subject: Re: SDS Work Product Not Proprietary
232514 -         ..
232515 -    2.  Thanks Gil,
232517 -         ..
232518 -    3.  In some sense, we did talk past each other, mostly because
232519 -        Rod's post did not mention the license.  My comment to Rod was
232520 -        that I had observed the potential for unlicensed inference that
232521 -        the work product from SDS might be owned by Rod.
232523 -         ..
232524 -    4.  Jack
232525 -
232526 -            [On 060312 submitted corrected letter to Gary and Gil, with
232527 -            copy to Jack. ref SDS 8 175N
232528 -
232529 -
232530 -
232531 -
232532 -
232533 -
232534 -
232535 -
232536 -
232537 -
232538 -
232539 -
232540 -
2326 -