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: April 16, 2004 07:49 AM Friday; Rod Welch

Gary called on submitting SDS to Aerospace company Architecture Committee.

1...Summary/Objective
2...Request Copy Submission Explain SDS to Aerospace company Architecture Committee
3...Morris Has Ideas on Explaining SDS
4...Interoperability Strong Point of SDS for Architecture Committee


..............
Click here to comment!

CONTACTS 

SUBJECTS
Aerospace company Architecture Committee Needs Explanation of SDS                 04
Aerospace company Architecture Committee ASB Requests More Detailed Exp  nation   05
ASB Aerospace company Architecture Committee Requests More Detailed Exp  nation   14
SDS Submitted Architecture Committee OA 040305 for Approval of SDS P

1606 -
1606 -    ..
1607 - Summary/Objective
1608 -
160801 - Follow up ref SDS 18 0000, ref SDS 17 0000.
160802 -
160803 - Gary submitted an updated version of the section on "Situation" that
160804 - incorporates revisions developed yesterday. ref SDS 18 KZ5O
160806 -  ..
160807 - We made a number of other revisions to sharpen the distinctions
160808 - between what SDS does and what is available from other vendors and
160809 - systems.
160811 -  ..
160812 - Gary was worried we have made too many revisions for Gil to follow --
160813 - looks like we don't know what we are doing.
160815 -  ..
160816 - Over the several calls, also, suggested to Gary that some work is
160817 - needed on the original para in the form for "Situation."  It has some
160818 - important points explaining SDS is available from the Welch Company
160819 - and that Gil wants to set the software as a company standard.
160820 - ref SDS 18 JU6S
160822 -  ..
160823 - As a result, sent a follow up letter to Gary and to Gil asking for a
160824 - copy of the final document on AR 1269, shown in the record yesterday,
160825 - ref SDS 18 JP4K, sent to the Architecture Committee.  The response
160826 - from Gary shows the following has been submitted.
160827 -
160829 -  ..
160830 - Request Copy Submission Explain SDS to Aerospace company Architecture Committee
160831 -
160832 - Submitted ref DIT 1 0001 to Gary with a copy to Gil saying....
160833 -
160834 -        Very sorry for multiple discussions this morning in shaping the
160835 -        description of SDS for Gil's submission to the Arch Com.  Think
160836 -        we have something now that may be helpful for people, who have
160837 -        not experienced working with SDS, to recognize a basis for
160838 -        Gil's goal to set a new Aerospace company standard.  If permissible,
160839 -        please send me a copy of the completed submission to the Arch
160840 -        Com. ref DIT 1 0001
160841 -
160842 -           [On 040426 letter from Gary transmits explanation of SDS
160843 -           that was submitted to the Architecture Committee.
160844 -           ref SDS 19 0001
160846 -  ..
160847 - This letter reflects experience at DNRC, PG&E, USACE, etc., showing
160848 - that people, who gain experience with using SDS records, have
160849 - confidence in the methodology, but are unable to explain their support
160850 - for SDS to others who have yet acquired any experience working with
160851 - SDS records.
160852 -
160853 -
160854 -
160855 -
1609 -

SUBJECTS
Aerospace company Architecture Committee Needs Explanation of SDS
Explain SDS for Aerospace company Standard Organizational Memory Approv   SDS D
Aerospace company Architecture Committee Needs Explanation of SDS
Breakthrough Design Integrates Hierarchial Relational Data Base Meth

2006 -
2007 - 0849
200801 -  ..
200802 - Morris Has Ideas on Explaining SDS
200803 -
200804 - Called Morris.
200805 -
200806 - He has received copies of the letters, ref DIP 5 0001, and, also,
200807 - ref DIP 6 0001, sent to Gary and Gil at Aerospace company yesterday, ref SDS 18
200808 - 0001, which included a copy of Gary's letter, ref DRP 4 0001,
200810 -  ..
200811 - Morris said he had problems understanding the initial draft to
200812 - Architecture Committee. ref DRP 4 WU3H
200814 -  ..
200815 - He said that the Architecture Committee will likely only spend a few
200816 - minutes considering Gil's proposal.
200818 -  ..
200819 - Morris suggested the committee has a company-wide perspective, and so
200820 - support for interoperability could be helpful to point out, citing SDS
200821 - work product based on an ASCII text file format that can be opened in
200822 - most wordprocessors and other editor programs, and likewise, most
200823 - programs like Microsoft Word, Outlook, etc., can save information to
200824 - text that can then be improved by adding "intelligence" for creating
200825 - useful knowledge, as explained in POIMS. ref OF 6 0367
200827 -  ..
200828 - I asked Morris to submit a letter with his ideas.  He will get to it
200829 - later today.
200831 -  ..
200832 - Morris indicated that he has a new assignment at Intel, and it will
200833 - entail travel to develop information from remote sites.
200834 -
200836 -  ..
2009 -
2010 -
2011 - 0902
2012 -
201201 - Called Gary.
201202 -
201203 - He likes Morris point about interoperability.  If there is further
201204 - submission required by the Architecture Committee, Gary feels Morris'
201205 - point should be added to SDS advantages.
201206 -
201207 -
201209 -  ..
2013 -
2014 -
2015 - 1439
2016 -
201601 - Interoperability Strong Point of SDS for Architecture Committee
201602 -
201603 - Follow up ref SDS 4 0477, ref SDS 2 8211.
201604 -
201605 - Received ref DRT 1 0001, a letter from Morris following up the telecon
201606 - this morning, when he suggested that interoperability might be
201607 - mentioned in the submission to the Architecture Committee at Aerospace company.
201609 -  ..
201610 - Morris says...
201611 -
201612 -    1.  You might also explain:
201614 -         ..
201615 -    2.  The files are plain text ASCII. ref DRT 1 UK5M
201617 -  ..
201618 - This needs a little more work to make the point Morris discussed in
201619 - the call about the advantage of interoperability, per above.
201620 - ref SDS 0 VL93
201621 -
201622 -           [On 040426 submission to Architecture Committee did not
201623 -           mention interoperability. ref SDS 19 6O7I
201625 -  ..
201626 - Morris continues...
201627 -
201628 -    3.  Line numbering techniques are used to organize information in
201629 -        each file. The numbering system is visible in plain text ASCII.
201630 -        ref DRT 1 5L6F
201632 -  ..
201633 - Line numbering is a component of "flexible structure" mentioned in the
201634 - description already, per Gary's letter yesterday, ref SDS 18 3E5N, and
201635 - explained in the record on 890523. ref SDS 1 T1VQ
201637 -  ..
201638 - Previously, on 890809 Morris explained SDS architecture. ref SDS 2
201639 - 8211  Later on 910810 Morris described a "breakthrough" design that
201640 - SDS applies to integrate hierarchial and relational data base
201641 - structures. ref SDS 3 7793  On 911123 he explained how the
201642 - breakthrough design enables a new way of working that improves
201643 - productivity for people and organizations. ref SDS 4 0477
201645 -  ..
201646 - On 031215 Gary expanded on Morris' idea to explain SDS design that
201647 - integrates data base methods. ref SDS 11 ZU6O
201649 -  ..
201650 - Morris continues...
201651 -
201652 -    4.  The program publishes information in HTML web pages for public
201653 -        viewing and searching. ref DRT 1 FL6J
201655 -  ..
201656 - Morris' explanation needs some fine tuning to clarify that SDS does
201657 - not publish anything, but does support publishing SDS records and
201658 - other documents on the Internet and on a secure company intranet,
201659 - which is already mentioned in the current draft, shown in the record
201660 - yesterday. ref SDS 18 3E5N
201662 -  ..
201663 - Morris continues...
201664 -
201665 -    5.  The data base is a windows file structure. ref DRT 1 9N6N
201667 -  ..
201668 - SDS applies several data bases....
201669 -
201670 -        SDS records
201671 -        Documents
201672 -        Contacts
201673 -        Dirctory Maintenance
201674 -        Subjects
201676 -  ..
201677 - We might say that SDS provides a common organization structure for
201678 - files stored under the Windows operating system that makes finding
201679 - information fast and easy, as reported on 010916. ref SDS 7 0001  This
201680 - solves the problem using other methods where people report nobody can
201681 - find anything.  An example is Millie's report on 960406, confirmed by
201682 - Morris on the same day, ref SDS 5 4249; and, later confirmed again by
201683 - Eric Armstrong on 011003. ref SDS 8 EC5N  A year later, on 020822 Ray
201684 - Ozzie, credited for developing Lotus Notes, reported people using
201685 - Lotus Notes and Grove are feeling a lot of pain. ref SDS 9 Q99G  A
201686 - few months later Bill Gates announced a project to solve the problem
201687 - by improving microsoft programs. ref SDS 10 EF5I  Since at this time,
201688 - Microsoft has not announced completion of the project, SDS still
201689 - offers the best solution, which Morris described on 010525 as a
201690 - "utopia," compared to using other methods, because in SDS everything
201691 - is in the right place at the right time. ref SDS 6 EP7F
201693 -  ..
201694 - Morris continues....
201695 -
201696 -    6.  ASCII index files are used to locate information. ref DRT 1
201697 -        GN7G
201699 -  ..
201700 - This idea is unclear, unless it restates the earlier point that SDS
201701 - provides superior interoperability using common ASCII text files for
201702 - converting information into knowledge. ref SDS 0 HX6F
201704 -         ..
201705 -    7.  Records contain direct links to other records for quick
201706 -        historical perspective. ref DRT 1 SN7J
201708 -  ..
201709 - Gary has already made this point. ref SDS 18 UG9V
201710 -
201711 -
201712 -
201713 -
201714 -
201715 -
201716 -
201717 -
201718 -
201719 -
201720 -
201721 -
201722 -
201723 -
201724 -
2018 -