CONTACTS 
0201 - Dan Palanza and NSF                  508 548 7421
020101 - Mr. Dan Palanza

SUBJECTS
Security, Privacy - Discovery
Office 2000 Risks Virus Security Problems
Risk Communication Main Factor of Management Success
Common Administration
Palanza, Dan Com Metrics Helps Engineering Management
Security Issue, 990718
Common Administration, 990802
Context Linking Analysis Intelligence Adds Value
Quantum Leap, Paradigm Shift
Pattern Language, 990802

1512 -    ..
1513 - Summary/Objective
1514 -
151401 - Follow up ref SDS 23 0000, ref SDS 22 0000.
151402 -
151403 - Common Administration relates to Dan's work; may be used differently
151404 - from application under Communication Metrics. ref SDS 0 4234  Dan
151405 - requests information about SDS architecture for context management and
151406 - privacy. ref SDS 0 1628  Network bookkeeping limits access to
151407 - information on a right and need-to-know basis, with a process that
151408 - seems to be called "pattern savvy," where 6 or less people share
151409 - common access. ref SDS 0 2340
151410 -
151411 - Context management and pattern recognition are part of Controlled
151412 - Visibility in POIMS technology that guides the design of the SDS
151413 - program. ref SDS 0 0960
151414 -
151415 - Privacy is an important design criteria of SDS. ref SDS 0 0828
151416 - ..
151417 - Need more on distinguishing distributed management from
151418 - centralized administration. ref SDS 0 8966
151419 -
151420 - Submitted ref DIT 1 linked to this record.
151421 -
151422 -      [On 990803 received letter from Dan. ref SDS 25 0001
151423 -
151424 -      [On 990804 another letter from Dan. ref SDS 26 0001
151425 -
151426 -      [On 990806 sent letter to Dan. ref SDS 27 0001
151427 -
151428 -
151429 -
151430 -
151431 -
151432 -  ..
1515 -
1516 -
1517 - Progress
1518 -
151801 -  ..
151802 - Common Administration Supports Dan's Network Bookkeeping Goals
151803 -
151804 - Received ref DRT 1 from Dan responding to my letter, ref DIP 3 0877,
151805 - sent on 990728, and requesting comment on using Common Administration,
151806 - ref SDS 23 0624
151807 -
151808 - Dan does not quote the explanation of Common Administration on 990328,
151809 - ref SDS 14 9641, nor the analysis on 990716 that led to putting this
151810 - idea forward for his consideration. ref SDS 19 0877  Therefore it is
151811 - unclear whether we are using this phrase in the same way.  See also
151812 - below. ref SDS 0 4234
151813 -
151814 -     [On 990804 language quoted, but not this subject. ref SDS 25 1148]
151815 - ..
151816 - He says...
151817 -
151818 -       In my bookkeeping research, Common Administration is the precise
151819 -       issue a communication era must come to terms with.  The problem
151820 -       is how to control a Common Administrative system. ref DRT 1 4160
151821 -
151822 -       When administration is centralized, privacy is at risk.
151823 -
151824 -       The solution is a control system that is capable of partitioning
151825 -       information.  This is not hard to do... Pattern study revolves
151826 -       around the issue of context, and is capable of handling the
151827 -       problem. ref DRT 1 5355
151828 -
151829 - Dan explained network bookkeeping on 990710. ref SDS 18 LF5I
151830 -
151831 -     [On 990803 Dan requests disclosing SDS design. ref SDS 25 7068
151832 - ..
151833 - Experience indicates "control" is not a major objective using
151834 - Common Administration, as it has been implemented so far.  The big
151835 - idea is to help executives and everyone else, "know what is going on,"
151836 - so they don't make the mistakes they are making now due to information
151837 - overload, as related in the Fortune article reviewed in the record on
151838 - 990625. ref SDS 17 3000  There is initial shock and fear about the
151839 - level of detail that people overlook, as reported on 940901.
151840 - ref SDS 4 4920 and on 961007, ref SDS 10 6621
151841 - ..
151842 - Shock wears off, people are amazed by improvement in the work,
151843 - per 970107. ref SDS 11 4953
151844 -
151845 -     [On 990802 medical manager found Communication Metrics on the
151846 -     Internet is pretty neat. ref SDS 24 0406]
151847 -
151848 -     [On 990803 Dan does not address this issue. ref SDS 25 0001]
151849 -
151850 -
151851 - Dan asks about architecture that demonstrates...
151852 -
151853 -       Communication Metrics places information into controlled context
151854 -       -- in other words, is it pattern savvy? -- so that it can be
151855 -       addressed only by those people who have both the right and the
151856 -       need to know. ref DRT 1 6435
151857 -
151858 -        ..
151859 -       Pattern Recognition Derived From Controlled Visibility in SDS
151860 -
151861 -       POIMS technology defines Controlled Visibility provided in the
151862 -       SDS program, which supports pattern recognition, as part of
151863 -       "intelligence."  ref OF 1 1103  Pattern recognition is further
151864 -       discussed in the New World Order... paper. ref OF 2 7337
151865 -
151866 -       Pattern recognition is a major goal of Communication Metrics,
151867 -       and a key deliverable of SDS.
151868 -
151869 -       It is used everyday, all day long, as a key "metric" of business
151870 -       communications.  Subject reports to find out what has been done,
151871 -       considered, analysed and discussed, assembles a chronology that
151872 -       shows the evolution of cause and effect.  This comprises a
151873 -       "pattern" that points to future implications.
151874 -
151875 -
151876 -
151877 -
1519 -

SUBJECTS
Bookkeeping Accounting Payment Attribution Open Source Encourages Con
Network Bookeeping Payment Attribution Open Source Encourages Contrib
Network Bookkeeping Accounting Attribution Credit, Polanza, 990716
Accountability Attribution Credit Recognition Accounting Pattern Lang
Accounting, Bookkeeping Double Entry Feedback Loops

2108 -
210801 -  ..
210802 - Shared Accounts (6+/-) in Network Bookkeeping Manage Context
210803 -
210804 - Dan makes the following comment...
210805 -
210806 -       In network bookkeeping context specificity takes place in a
210807 -       system of pools that often have 6 or less members.  In essence
210808 -       members share an account which holds data common to the group.
210809 -       This pattern system in bookkeeping, it seems to me, must be
210810 -       extended to the communication diary you are keeping. ref DRT 1
210811 -       0980
210812 -
210813 -  ..
210814 - Dan needs information about SDS structure in order to correlate and
210815 - discuss details of how his bookkeeping methods can be extended to
210816 - Communication Metrics. ref DRT 1 2800
210817 -
210818 - At this time, I do not want to present specific SDS design details,
210819 - which have taken many years to develop through trial and error.
210820 -
210821 -     [On 990803 Dan feels information on SDS architecture can be
210822 -     disclosed, without risk to business interests. ref SDS 25 0648]
210823 - ..
210824 - Information on 940901 explains major features and provides a
210825 - schematic. ref SDS 4 2929
210826 -
210827 - We can talk on the phone to develop further information Dan needs.
210828 -  ..
210829 - If the NSF grant is awarded, I can go visit with Dan and map out the
210830 - architecture, explaining how the various elements interact to
210831 - accomplish design objectives.
210832 -
210833 -
210834 -
210835 -  ..
210836 - Context Controlled by Subject, Function, Time, Organizations, People
210837 - Integration of Communication Metrics and Network Bookkeeping
210838 -
210839 - Follow up ref SDS 19 LV4K.
210840 -
210841 - Dan's idea to use technology for applying principles of accounting and
210842 - bookkeeping on a wider scale, per above, ref SDS 0 2340, and as set
210843 - out in his Phase I report for his NSF project. ref SDS 19 LV4K is
210844 - supported by SDS under POIMS technology.
210845 -
210846 -     [On 001224 Xanadu developed similar technology for attribution of
210847 -     added value of contributors on the Internet. ref SDS 29 6I7K
210848 -
210849 - Essentially, it appears we are working toward the same goal to
210850 - integrate...
210851 -
210852 -
210853 -                  time       cost       communication
210854 -
210855 -
210856 - ...per Kerzner lecture on 950202. ref SDS 5 5093
210857 - ..
210858 - I am pretty sure that SDS provides a framework to accomplish
210859 - this goal.  We are in the beginning of a design path for creating
210860 - tools and work processes that are inherently complimentary, which is
210861 - the essence of integration.  When we get that we will have an...
210862 -
210863 -
210864 -            Operating System for People and Organizations
210865 -
210866 -
210867 - ...discussed with Intel on 950927. ref SDS 8 8400
210868 -
210869 -     [On 990804 Dan's Phase I report for his NSF project explains
210870 -     network bookkeeping for tracking and credting contributions of
210871 -     added value on the Internet. ref SDS 26 0306 and ref SDS 26 7944
210872 - ..
210873 - Less attention given to accounting in SDS, because opportunities
210874 - for application, which yield experience for improving the technology,
210875 - have needed more help with time and information, than with accounting
210876 - issues.  So, accounting support in SDS is largely untested, except for
210877 - doing billings to customers.
210878 - ..
210879 - "Context" is design goal for SDS called "Controlled Visibility,"
210880 - as shown in the record on 970116. ref SDS 12 2909 and above.
210881 - ref SDS 0 0960
210882 - ..
210883 - A principle control for context is time; specifically,
210884 - chronology, or the sequence of events, which imparts cause and effect,
210885 - that is the foundation of human intelligence. This is the driving
210886 - force of SDS, as reviewed on 900303. ref SDS 1 3002
210887 -
210888 - Additionally, organic subject structure for objects and functions
210889 - provides an unlimited range of context management, and serves as the
210890 - foundation for improved earnings by avoiding overlooked subjects, and
210891 - which, otherwise, escalate time and cost as "rework" reported by the
210892 - U.S. Army Corps of Engineers on 971008. ref DRP 2 4680
210893 -
210894 -
210895 -
210896 -
2109 -

SUBJECTS
Security, Privacy - Discovery
Office 2000 Risks Virus Security Problems
Risk Communication Main Factor of Management Success
Secuity Issue, 990718
Binary Forces Permeate Human Endeavors, Cause Stress, Conflict
Bookkeeping Double Entry Feedback Loops
Feedback Loops Double Entry Bookkeeping SDS Record
Confidentiality Communication Balanced by SDS POIMS
Concepts Security and Privacy, SDS Records
Plannng Concepts

3213 -
321301 -  ..
321302 - Privacy Balances Competition and Cooperation
321303 -
321304 - Privacy is developed in the SDS design for managing the tension
321305 - between competition and cooperation, reviewed on 930326. ref SDS 2
321306 - 5468
321307 -
321308 -     [On 990803 Dan does not address this subject. ref SDS 25 8120]
321309 -
321310 - The balance of binary forces in time management is applied...
321311 -
321312 -     SDS is about the future as well as the past. It uses a continual
321313 -     process of understanding history, i.e., what happened just now,
321314 -     ten minutes ago, yesterday, last week, last month, 10 years ago,
321315 -     as a control and context for deciding what to do next:  in 10
321316 -     minutes, an hour, a day, a week, etc.
321317 -     ..
321318 -     The Internet environment does not present the Schedule side
321319 -     of SDS, because the Internet record is designed to support history
321320 -     -- the knowledge, the "intelligence" side of SDS -- which is the
321321 -     Diary.
321322 -
321323 -     The Schedule side of SDS is primarily private and personal.
321324 -
321325 -     The Diary is a record of what has happened, and so some of it can
321326 -     be public and/or shared in a controlled manner.
321327 -
321328 -     The Schedule is what we are doing and planning to do about what
321329 -     has happened, as developed in the Diary.  Users control what is
321330 -     released into the public Diary, and they can control what links
321331 -     are active in the public Diary, while retaining control to all
321332 -     links in their own environment.
321333 - ..
321334 - Communication Metrics has been applied in a similar manner that
321335 - Dan describes assigning a single account for a pool of people,
321336 - typically working closely on a project.
321337 -
321338 - SDS permits everyone having separate accounts to segment the Diary,
321339 - and exercise control on what is released into the public domain,
321340 - including what is shared among colleagues.
321341 -
321342 - There is not enough experience using SDS in a multi-account setting to
321343 - say that all of the design issues have been recognized and resolved.
321344 -
321345 - Access to records is controlled by passwords, and authority; and we
321346 - can cross-link between users.  There are certainly issues to be
321347 - discovered that will require refinement to make multi-user application
321348 - work as smoothly as the single-user implementation, since the latter
321349 - is used every day, and has been constantly refined for 15 years.  If
321350 - the NSF effort is funded, we may be able to encourage a broader based
321351 - test of this design feature on a project.
321352 -
321353 -
321354 -
321355 -  ..
321356 - MS Office 2000 Security Not at Issue for Com Metrics
321357 -
321358 - Dan is not concerned about security issues raised in the article on
321359 - Office 2000, relative to Communication Metrics.  He is focused on
321360 - privacy of "centralized administration" and notes his bookkeeping
321361 - system accomplishes this requirement, ref DRT 1 5355, as reviewed
321362 - above. ref SDS 0 1628
321363 -
321364 -
321365 -
321366 -
3214 -
3215 -

SUBJECTS
Security, Privacy - Discovery
Common Administration
Distributed Management Network Management Enterprise Management
Knowledge Repository Needs Redundancy Avoid Risk Bumbling
Enterprise Management DKR Mainframe Centralized Control Bumbling Priv
Enterprise Management
Dynamic Knowledge Repository (DKR)

4110 -
411001 -  ..
411002 - Distributed Management and Centralized Administration???
411003 - Changing Management Paradigm Comparable to Renaissance
411004 -
411005 - Dan explains the prospect of a significant shift in the way management
411006 - is performed, because...
411007 -
411008 -      ... intellectually driven communication systems become a primary
411009 -      product focus, rather than the economic property of corporate
411010 -      America. ref DRT 1 4485
411011 -
411012 - He says further...
411013 -
411014 -      Management becomes distributed into a network and administration
411015 -      requires a hierarchy. ref DRT 1 2112
411016 -      ..
411017 -      Administration then loses its power to communicate out into
411018 -      the network. The solution is to centralize administration.
411019 -
411020 -      In essence where mechanical industry used hierarchical management
411021 -      and network administration, communication systems reverse this
411022 -      need.  They require distributed management and centralized
411023 -      administration.  This, in essence, is the kernel of the paradigm
411024 -      shift from mechanical industry, that dominated our past, to
411025 -      intellectual communication, that will dominate our future.
411026 -
411027 - Centralized "administration" becomes management because it has control
411028 - over receipt and distribution of information.  Unlike the U.S. Mail
411029 - system, Dan's vision of Distributed Management requires continual
411030 - functioning of the centralized information system.
411031 -
411032 -    [On 000305 Xanadu proposes a single source for all information to
411033 -    gain efficiencies of linking. ref SDS 28 0184
411034 -
411035 - ..
411036 - Increased mobility of people and information comprises a new
411037 - world order, ref OF 2 1675, that brings challenge and opportunity
411038 - which require a paradigm shift on a number of fronts in traditional
411039 - management practice.  The the New World Order... paper describes the
411040 - difficulty of accomplishing the paradigm shift from documents to a
411041 - continuous knowledge stream on changing 5,000 years of management
411042 - practice. ref OF 2 4305
411043 -
411044 - To deal constructively with Dan's formulation, I need a definition
411045 - and a scenario that distinguishes....
411046 -
411047 -    a.  Management and administration
411048 -
411049 -    b.  Distributed management and centralized administration.
411050 -
411051 -      [On 990803 Dan does not deal with this subject. ref SDS 25 8388]
411052 - ..
411053 - This may not be a big deal, but I generally think of
411054 - "administration" as being part of "management."  When we "administer"
411055 - the contract, we are "managing" the work, etc.  How are these
411056 - processes distinguished in Dan's work?.
411057 -
411058 - If Dan's Phase I Final Report to NSF covers this, perhaps he can point
411059 - to the language?
411060 -
411061 -                             ..
411062 - Need to see how Dan relates explanation of Common Administration
411063 - on 990328, which is largely managing projects, ref SDS 14 9641, with
411064 - what he has in mind for "centralized administration." ref DRT 1 4160
411065 -
411066 - Dan has not quoted any of the explanation submitted in the record,
411067 - showing a correlation to his use of Common Administration.  It may be
411068 - that we are using the same words to refer to different things.
411069 -
411070 -     [On 990804 language quoted, but not this subject. ref SDS 25 1148]
411071 -
411072 - For example, I do not have in mind that "authority" be centralized by
411073 - Common Administration.  My initial thought is to extend experience
411074 - that shows a neutral can help contracting parties, and others,
411075 - communicate so they retain the edge of competition that drives
411076 - progress, while avoiding the more egregious pitfalls of building the
411077 - job with conversation under the guise of "expediting," which leads to
411078 - endless mistakes, extra cost and delay.
411079 - ..
411080 - Common Administration avoids mistakes that drive parties into
411081 - conflict; and, it brings forward patterns that yield opportunities for
411082 - improving work processes.  This improves earnings, while getting the
411083 - job done correctly, on time and within budget. These goals have been
411084 - achieved wherever Communication Metrics has been applied, and so
411085 - suggest broader application. ref SDS 11 4953
411086 -
411087 -
411088 -
411089 -  ..
411090 - Future: Integrate Management of Time and Administration of Money
411091 -
411092 - Dan explains...
411093 -
411094 -      ... money was the medium of exchange controlling centrally
411095 -      managed systems.
411096 -
411097 -      ...[in] distributed management with centralized administration,
411098 -      time becomes the primary medium of exchange.
411099 -
411100 -      Time does not replace money, the two become complimentary, but
411101 -      time becomes the primary control medium.  So in essence the
411102 -      control system -- read bookkeeping -- of the future must manage
411103 -      time and administer money. ref DRT 1 4316
411104 - ..
411105 - In my view a key paradigm shift is changing from traditional
411106 - "documentation" to a continuous knowledge stream, which is the essence
411107 - of the POIMS design for SDS. ref OF 1 7117
411108 -
411109 - Integrating time, money and communication is discussed above.
411110 - ref SDS 0 4950
411111 -
411112 -
411113 -
411114 -
411115 -
411116 -
411117 -
411118 -
411119 -