My companies have a base technology caller RT/AI Agentware which allows
one to develop multiple "organizations" of "intelligent agents" which can
communicate with one another via shared memory objects, local area
networks, modems, etc. The theory and practice is thus: place specialized
knowledge in each agent, provide whatever level(s) of "meta-agents",
connect all this to your machines, databases, etc. and they derive their
facts from real-time information, make decisions, argue and vote among
themselves (avoiding sub-optimization) (hint at chaos use, George) and
render decisions which turn into justified recommendations to people and
commands to machines.
Based on commentary on TQM and LO lists, we recently implemented IDEF
notation (standardized means of graphically depicting manufacturing and
"business" processes as empty AGENTS. These can be strung together in
various combinations, renamed to suit, etc. and communication links
between them can be set up. The idea was to make a tool for reengineering
that would emit an "empty knowledge based system", replete with
communication and fact sources, instead of emitting a book or plan a la
normal reengineering exercises.
FINALLY, my question: We used th National Center for Manufacturing
Sciences IDEF notation for this. I am interested in other IDEF-like
notations that are at least standardized or, at best, agreed upon among
"industry leaders". My goal is to provide all notations in interoperable
form, thereby enriching the choices my customers can make as they use the
tool.
I am entralled with the idea of a reengineering consultant being able to
leave her/his client with a "runable" knowledge system into which the
organization could pour some of its knowledge in order to provide a
"knowledge distribution infrastructure" to aid in not only the
reengineering process but of lasting value in optimizing processes and
people.
Sorry for being so long-winded.
"If I'd had more time I would have written less."
-- Hal Popplewell GaltJohn22@aol.com