Logical Conclusions Inc.

horizontal rule

Logical Conclusions, Inc. is a business services organization providing business consulting and teaching to private corporations and government agencies since  1981.

We provide practical training and consulting in:

bulletEvent Driven Business Systems, 
bulletBusiness Process Analysis
bulletBusiness Information Analysis
bulletBusiness Process Management and Process Improvement BPM/BPI
bulletEvent Based Systems Design and Architecture
bulletReEngineering Organizations for Customer Satisfaction
 

You'll notice that a the word Event is used in some of the above titles. When I formed Logical Conclusions Inc I felt like a lone voice teaching seminars at organizations and giving talks at conferences about the importance of Events as a basis for structuring a business architecture. Now it appears the main stream academic and technical world has finally caught up. We see the term used in many areas, such as Event Based Architecture EBA, Service Oriented Architecture SOA and Event Stream Processing.

Of course any author can use the term Event but its their definition that's obviously important, as Events can apply at many levels in an organization and it's systems. For example:

bullet a mouse click can be classed as an Event to a computer tracking application. 
bulletone department within an organization sending a Completed Order to another department could be classed as an event to the second department. 
bulleta transaction entering a computer system can be classed as an Event to a program. 
bulleta customer request entering an organization can be an Event to the organization
bulletand even a meteor approaching earth is a significant Event to the people on earth, (I hope someone is taking care of this last one). 

Obviously the definition is context specific. When we use the term Events in our seminars and talks it is best used within the context of the organization as that is the most important to a customer of the organization and therefore will provide the best basis for partitioning an efficient  response to the customers needs. We call these types of Events - Organizational Events. That does not mean that one can't use the concept of Events within a smaller context, its just most powerful when viewed from an outside customer perspective rather than from a department or computer system view.

I've discovered over my many years of teaching and writing that an "expert" is someone that has thought about a particular subject longer than most people (or at least longer than his client who's paying for his knowledge and advice). So having taught and written on this concept for over a quarter of a century I hope I can claim tenure.

So, there are many Event "types" and you can also say there are many "flavors" within Event types. In the above bulleted list of Events the most important to me, as I have already stated, are Organizational Events. Within this type I identify 5 flavors, with the most important being a Business Event. These are the ones that define the "reason-for-being" of any organization.

It is very important to identify the Business Events that make up an organization and to model them in an analysis effort and even to use them as a means for a new design or architecture and then on through to implementation of the improved organization. Using Business Events as a basis will, I believe, produce the ultimate implementation structure (I call the ultimate 'partitioning') for an organization. It has to be because it is Customer Focused and not based on any arbitrary, internal, political, historical industrial age, (use whatever adjective you want here) view.

Of course there is everything right in carrying the concept of Event processing into smaller levels of detail. For example, in my early days as a systems designer/programmer I would try to obtain as much reusability of blocks of code as I could. It saved me rewriting and testing the same logic repeatedly in different programs. This reusability was easily obtained with separately compiled modules/subroutines. To the actual module a "call" to execute it was equivalent to a local Event. It was a "black box"; it didn't care who its boss was. (Does this sound like a concept of Service Oriented Architecture SOA?) An organization is just a bigger black box - especially to a customer.

Needless to say all of LCI's seminars use Events as a basis for partitioning it's deliverable. A Process Model is partitioned by Events In our Business Process Analysis, an Information Model is partitioned by Events in our Business Information Analysis and even management models are partitioned by Events in our management seminars.

If this subject is your area of interest please view more details in the following links:

Seminars Consulting Presentations Books/Articles Client List LCI's Founder 

horizontal rule

Logical Conclusions’ Mission Statement:

"Our mission is to teach and work with our clients to help them obtain the best organizational structure and systems architecture for the most efficient and reliable satisfaction of their customer's needs."

Using our proven methods your management, business people and systems developers will be able to identify an unbeatable customized solution for your organization.

   LCI’s Corporate Philosophy

Our ultimate goal is to improve the quality of life for all of us…

we’re all customers.

horizontal rule

 

What LCI Does for Its Clients -

Logical Conclusions provides the skill sets required for an organization’s management and business/technical staff to recognize their organization’s true business, devoid of outdated, unnecessary procedures and technology. 

This business view allows an organization to produce quality, maintainable business systems for future strategic growth.    

A little history on the Evolution of Organizations

With the Internet driving e-business organizations are trying to make their old organization's structure fit a new paradigm.

The old structure of departments and legacy systems based on old industrial age boundaries hinders the customer.

LCI's Business Event based methodology leads to a new infrastructure which will give you the fastest and most customer-focused response to your customer's requests.

The measure of success for this is customer satisfaction with longevity and expansion of the organization.

horizontal rule

A sample of what our clients say about:

 

bullettraining and consulting, please click here -     Sample Training Reference

 

bulletlatest book by LCI's President, please click here -     Sample Book Reference

 

bulletteaching abilities, please click here -     Teaching Ability Reference

 

horizontal rule

Contact Information

U.S.A.
16001 E Burro Drive,
Fountain Hills AZ 85268
Tel./Fax: (480) 836-8747
Email
: Talk2Us@Logical-Inc.com
Web: www.logical-inc.com
England
18 Honister Avenue,
Blackpool, Lancs.
England FY3 9PF
Email: Talk2Us@Logical-Inc.com


 

Telephone
(480) 836-8747 Office    (480) 225-3611 Cell
Postal address
16001 E Burro Drive, Fountain Hills Arizona 85268
Electronic mail
Sales and general Information: Talk2Us@Logical-Inc.com
 

 

For all enquiries please send email to Talk2Us@Logical-Inc.com