Technique Enforced Process (Orthogonality)

An Event initiates a Process. The Process collects, manipulates and saves Data including a State setting. Each change in State (including from No State to a State) can be used as an Event.

There are many external Events which occur and trigger their associated Processes within an automated application. As examples:

1. A sale  of a product or service occurs online or in person
2. A bank teller or an ATM device receives a request to accept a deposit or service a withdrawal
3. A shipment of goods is initiated or arrives at its destination and is recorded in the appropriate applications

Two Master Processes are always running which monitor their “Event Threshold(s)”:

• Calendar Dates and Events:
  • Week Ends and Endings
  • Month and Quarter Ends
  • Annual Ends
  • Special Event Dates and Timings
• Data From State Changes
  • Which are Events that trigger other Processes

Each of these monitored Events are associated with and will initiate their necessary Processes.

And so the circle goes.

Some sample events include:

1. Midnite on any date
2. Midnite on special days like:
   1. End of a Week
   2. End of a Calendar Month
   3. End of a Year
   4. End of a Century
   5. New date matching a Birthday, Anniversary, Renewal dates for Subscriptions, Licenses, or other things expecting a renewal Payment (Rent, Lease, Copyrights, etc.)
3. Receipt of a Payment from a Customer to a Vendor
4. Insertion of a Credit or Debit card at a Purchase point
   1. Or at an ATM
5. When an electronic record of a Customer, Order, Invoice, Shipping Order, or other “master” type data is changed from one state to a “retired” or “archived’ state
6. When an electronic record of a Customer, Order, Invoice, Shipping Order, or other “master’ type data is changed from a “New” state to a more “Active” state
7. Etc…