Messaging system and method with dead man switching

Abstract

A messaging system and method with dead man switching providing for hierarchical delivery of messages based on selected message hierarchy levels with controlled delivery/response timing is disclosed. The system and method incorporates a messaging host that communicates with a messaging source client that creates and prioritizes a message and targets address(es) for the message. This message is then transmitted to the target address(es) using a hierarchical transmission thread having set limits on response times for each address within the thread. Reception of the message by each target(s) produces visual and/or auditory notification at the target(s). messages are automatically forwarded to remaining target(s) within the thread upon expiration of a timer should the target(s) fail to respond to the message within a predetermined time. Failure of the target(s) to respond to the message(s) is reported bi-directionally along the thread and forwarded to remaining target(s) in the thread.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

Applicants claim benefit pursuant to 35 U.S.C. §119 and hereby incorporates by reference Provisional Patent Application for “MESSAGING SYSTEM AND METHOD WITH DEAD MAN SWITCHING”, Ser. No. 61/459,931, filed Dec. 20, 2010, and submitted to the USPTO with Express Mail on Dec. 20, 2010 with tracking number EB483477834US.

PARTIAL WAIVER OF COPYRIGHT

All of the material in this patent application is subject to copyright protection under the copyright laws of the United States and of other countries. As of the first effective filing date of the present application, this material is protected as unpublished material.

However, permission to copy this material is hereby granted to the extent that the copyright owner has no objection to the facsimile reproduction by anyone of the patent documentation or patent disclosure, as it appears in the United States Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

REFERENCE TO A MICROFICHE APPENDIX

Not Applicable

FIELD OF THE INVENTION

The present invention is related to the field of computer messaging systems incorporating severity and urgency protocols to ensure delivery of time sensitive information to appropriate personnel or automated information systems. Included within the scope of this field is the ability to convert from a variety of mobile device messaging systems to computerized text and visa-versa, thus integrating smartphone/mobile device communications within the overall framework of computerized communications. Within this context the present invention promotes absolute delivery of information, within a client designated path and designated timeframe, and also incorporating auto-forwarding features and detection of offline receivers and/or receiver response timeouts.

DESCRIPTION OF THE PRIOR ART

The field of prior art associated with computer messaging includes the use of electronic mail (EMAIL) and text messaging (TEXT) that are both integrated into a wide variety of computer information frameworks. Both of these systems incorporate store-and-forward messaging technologies to route messages to a target destination from a messaging source, and generally rely on PULL of data from servers. While multiple recipients are possible in both existing paradigms, little if any automated feedback or chronological tracking of message transmission is performed in either system.

DEFICIENCIES IN THE PRIOR ART

Traditionally, these message transmission systems lack a high degree of security and can be “hacked” to uncover information contained within the messages. Furthermore, there is generally no assurance that once a message is sent that its intended recipients have received the message or that they have read it or acted on it. In situations where the information is of a critical nature and must be acted on promptly, often “broadcast” messages are issued to a number of individuals, hoping that one of these individuals will act on the information contained in the message to avert injury to or loss of human life or destruction of property, etc.

However, even with the use of broadcast messaging there is no assurance that the message will be received or acted on appropriately. For this reason, the prior art approaches to the handling of messages incorporating a scaled severity level and urgency level are insufficient to ensure proper action on the message. As such, the prior art fails to address this need within the computer messaging community.

Generally speaking, prior art technologies rely on PULL data techniques, rather than PUSHing data to the user terminal interface. This results in unacceptable delays in many circumstances involving time critical applications or events.

Traditional EMAIL systems permit the receiver to ignore the incoming message, or alternatively to fail to open the message or attachment. This can result in unacceptable delays in responding to critical events that must be addressed by management on an immediate basis. Additionally, there is generally no logging of message events and the failure of the recipient to deal with the message and its contents.

Within the context of messaging systems, the prior art does not generally teach the use of a secure and centralized messaging facility incorporating hierarchical guarantees of message reception and action by message recipients based on message severity and urgency.

OBJECTIVES OF THE INVENTION

The present invention, while not being limited by the following list, can in some embodiments achieve one or more of the following objectives:

• • To provide a messaging system and method which has all of the advantages of the prior art and none of the disadvantages.
  • To provide a messaging system and method that incorporates message severity levels.
  • To provide a messaging system and method that incorporates message urgency levels.
  • To provide a messaging system and method that incorporates customizable client specified severity and urgency levels.
  • To provide a messaging system and method that provides for hierarchical message routing.
  • To provide a messaging system and method that provides for dead man switching to ensure routing of messages to proper individuals within a hierarchy.
  • To provide a messaging system and method that provides for timed message delivery.
  • To provide a messaging system and method that provides for absolute certainty of message delivery.
  • To provide a messaging system and method that provides PUSH data transmission to the message receiver.
  • To provide a messaging system and method that provides for logging of recipient activity associated with message reception.
  • To provide a messaging system and method that provides for logging of recipient activity associated with the message both upstream and downstream from the message recipients list.
  • To provide a messaging system and method that provides for mandatory action by the recipient on the message contents.
  • To provide a messaging system and method that provides for audible/visual status indicators of message reception.
  • To provide a messaging system and method that provides for active participation by the recipient in the message reception process.
  • To provide a messaging system and method that provides for maximum message delivery and response timing.
  • To provide a messaging system and method that provides for positive transmission of a message that cannot be stopped or redirected by the recipient.
  • To provide a messaging system and method that provides for secure message encryption and decryption during transmission to the recipient.

Other objects, features, and advantages of the present invention will become more readily apparent from the following detailed description of the preferred embodiment when considered with the attached drawings and appended claims.

While these objectives should not be understood to limit the teachings of the present invention, in general these objectives are achieved in part or in whole by the disclosed invention that is discussed in the following sections. One skilled in the art will no doubt be able to select aspects of the present invention as disclosed to affect any combination of the objectives described above.

BRIEF SUMMARY OF THE INVENTION

The present invention utilizes a “dead man” message switching methodology to ensure that messages sent to a particular recipient are indeed reviewed by the recipient. A given message is associated with a hierarchical target message address list that identifies a number of individuals and/or organizations that will sequentially receive the message if a higher priority individual on the list fails to respond to the message within a predetermined amount of time. In this fashion, the delivery of the message is always confirmed, regardless of the response status of the recipient. In this manner, critical messages can be forwarded to a sequential stream of responsible individuals and feedback can be received by the message source user to determine if the persons ultimately responsible for action on the message have indeed received the message and are acting on its contents.

The system and method described herein incorporate timed response triggers for each level of target user within the message targeting hierarchy to ensure that message latencies are appropriate both for the target individual and the overall delay in acting on the message. A variety of message severities and urgencies can be associated with the message to automatically modify the timing latencies associated with message response to ensure an overall optimum response to the message based on its declared importance.

The use of “dead man” switching to retransmit messages to other individuals within the target message hierarchy thread ensures a degree of assured message delivery and response not available with the prior art messaging methodologies. This functionality, in conjunction with secure message transmission and optional plug-in software and/or hardware modules, permits the present invention to provide a wide variety of time-critical and mission-critical message delivery mechanisms that are not addressed by the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the advantages provided by the present invention, reference should be made to the following detailed description together with the accompanying drawings wherein:

FIG. 1 illustrates a general preferred exemplary embodiment system architecture of the present invention;

FIG. 2 illustrates a general preferred exemplary embodiment method architecture of the present invention;

FIG. 3 illustrates a general preferred exemplary embodiment system overview of the present invention;

FIG. 4 illustrates a general preferred exemplary embodiment method overview of the present invention;

FIG. 5 illustrates a preferred exemplary embodiment top level system overview of the present invention;

FIG. 6 illustrates a preferred exemplary embodiment top level method overview of the present invention;

FIG. 7 illustrates an exemplary expanded system network layout for some preferred exemplary embodiments of the present invention;

FIG. 8 illustrates an exemplary expanded system network layout for some preferred exemplary embodiments of the present invention;

FIG. 9 illustrates an exemplary parallel message transport methodology useful in some preferred embodiments of the present invention;

FIG. 10 illustrates an exemplary cascade message transport methodology useful in some preferred embodiments of the present invention;

FIG. 11 illustrates an exemplary parallel/cascade message transport methodology useful in some preferred embodiments of the present invention;

FIG. 12 illustrates an exemplary cascade/parallel message transport methodology useful in some preferred embodiments of the present invention;

FIG. 13 illustrates a preferred exemplary embodiment of the present invention utilizing message delivery auto-forward timeouts;

FIG. 14 illustrates a preferred exemplary embodiment of the present invention utilizing anticipatory message queuing (AMQ);

FIG. 15 illustrates an alternate preferred exemplary embodiment of the present invention utilizing anticipatory message queuing (AMQ);

FIG. 16 illustrates an autonomous preferred exemplary embodiment of the present invention utilizing anticipatory message queuing (AMQ);

FIG. 17 illustrates an exemplary system embodiment illustrating the use of a decision matrix to determine message routing;

FIG. 18 illustrates an exemplary method embodiment illustrating the use of a decision matrix to determine message routing;

FIG. 19 illustrates an exemplary Boolean syntax that may be used in some preferred invention system/method embodiments as the basis for the routing decision matrix evaluation;

FIG. 20 illustrates a preferred system embodiment employing a CA/user management architecture;

FIG. 21 illustrates a preferred exemplary message definition architecture used in some preferred embodiments of the present invention;

FIG. 22 illustrates an exemplary message definition form;

FIG. 23 illustrates an exemplary message delivery hierarchy map used in generating a message definition form;

FIG. 24 illustrates an exemplary message originator method used in some preferred embodiments of the present invention;

FIG. 25 illustrates an exemplary Message Originator/Recipient Login Validation Method used in some preferred embodiments of the present invention;

FIG. 26 illustrates an exemplary Message Routing/Delivery Method used in some preferred embodiments of the present invention;

FIG. 27 illustrates an exemplary On-The-Fly Message Transport Method used in some preferred embodiments of the present invention;

FIG. 28 illustrates an exemplary On-The-Fly Transport Detail Method used in some preferred embodiments of the present invention;

FIG. 29 illustrates an exemplary On-The-Fly Transport Detail Method used in some preferred embodiments of the present invention;

FIG. 30 illustrates an exemplary Message File Attachment Method used in some preferred embodiments of the present invention;

FIG. 31 illustrates an Anonymous Message Interrogator Method used in some preferred embodiments of the present invention;

FIG. 32 illustrates an exemplary Message Arrival Method used in some preferred embodiments of the present invention;

FIG. 33 illustrates an exemplary software plug-in API system architecture used in some preferred embodiments of the present invention;

FIG. 34 illustrates an exemplary hardware plug-in API system architecture used in some preferred embodiments of the present invention;

FIG. 35 illustrates an exemplary secure scanner hardware architecture used in some preferred embodiments of the present invention;

FIG. 36 illustrates an exemplary secure scanner method used in some preferred embodiments of the present invention;

FIG. 37 illustrates an exemplary system embodiment employing a PLC plug-in API;

FIG. 38 illustrates an exemplary system embodiment employing a licensing plug-in API;

FIG. 39 illustrates the user of mobile devices and Multi-protocol Label Switching (MPLS) within the context of the present invention;

FIG. 40 illustrates an exemplary mobile login application dialog used in some preferred embodiments of the present invention;

FIG. 41 illustrates an exemplary login screen useful in some preferred embodiments of the present invention;

FIG. 42 illustrates an exemplary CA authentication screen useful in some preferred embodiments of the present invention;

FIG. 43 illustrates an exemplary CA steady state screen useful in some preferred embodiments of the present invention;

FIG. 44 illustrates an exemplary CA Create Message screen useful in some preferred embodiments of the present invention;

FIG. 45 illustrates an exemplary CA Severity screen useful in some preferred embodiments of the present invention;

FIG. 46 illustrates an exemplary CA Urgency screen useful in some preferred embodiments of the present invention;

FIG. 47 illustrates an exemplary CA Reply To Message screen useful in some preferred embodiments of the present invention;

FIG. 48 illustrates an exemplary CA History screen useful in some preferred embodiments of the present invention;

FIG. 49 illustrates an exemplary user definition dialog used in some preferred embodiments of the present invention;

FIG. 50 illustrates an exemplary user definition dialog used in some preferred embodiments of the present invention;

FIG. 51 illustrates an exemplary user definition dialog used in some preferred embodiments of the present invention;

FIG. 52 illustrates an exemplary user definition dialog used in some preferred embodiments of the present invention;

FIG. 53 illustrates an exemplary user login screen useful in some preferred embodiments of the present invention;

FIG. 54 illustrates an exemplary steady state messaging dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 55 illustrates an exemplary standard severity dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 56 illustrates an exemplary executive severity dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 57 illustrates an exemplary standard urgency dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 58 illustrates an exemplary executive urgency dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 59 illustrates an exemplary Create Message dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 60 illustrates an exemplary Reply To Message dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 61 illustrates an exemplary Read Message Update dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 62 illustrates an exemplary History dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 63 illustrates an exemplary On-The-Fly Message dashboard dialog screen useful in some preferred embodiments of the present invention;

FIG. 64 illustrates an exemplary File Attachment dashboard dialog screen useful in some preferred embodiments of the present invention.

DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS

While the present invention is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detailed preferred embodiment of the present invention with the understanding that the present disclosure is to be considered as an exemplification of the principles of the present invention and is not intended to limit the broad aspect of the present invention to the embodiment illustrated.

The numerous innovative teachings of the present application will be described with particular reference to the presently preferred embodiment, wherein these innovative teachings are advantageously applied to the particular problems of a MESSAGING SYSTEM AND METHOD WITH DEAD MAN SWITCHING. However, it should be understood that this embodiment is only one example of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed inventions. Moreover, some statements may apply to some inventive features but not to others.

Communications Network not Limitive

The present invention anticipates that many preferred embodiments may make use of the Internet to communicate messages and control structures among various system components. However, the present invention should be interpreted to broadly define the term “communications” to include all communication means including but not limited to the Internet. This definition also includes local or private networks that are not publicly accessible.

System Interface not Limitive

The present invention anticipates that many preferred embodiments may make use of personal computers and other networked devices with display screens to act as the system interfaces for human interaction within the context of the disclosed invention. However, the term “interface” as it applies to a human interface within the context of the present invention should be broadly interpreted to mean any means for communicating with an individual. This might (for example) include screen displays and the like as well as lights and other visual indicia, sirens, klaxons (and other audible indicia), as well as vibratory means. Generally speaking, the interface selected will depend on a wide variety of factors known to those of skill in the art depending on the environment in which the particular invention embodiment is applied. Generally speaking, it should be noted that many present invention preferred embodiments specifically anticipate that personal computers (PCs), standalone file servers, and mobile (wireless) telephones (including but not limited to smartphones, mobile devices, computer-operated phones, and the like) will operate as the message processing hosts and/or sources/targets within the context of this disclosure.

Severity/Urgency not Limitive

The present invention anticipates that messages may be routed and identified based on severity levels and/or urgency levels. However, the present invention anticipates that these two broad categories are not limitive of the classifications and identifications that may be given to a particular message. The present invention specifically anticipates that a wide variety of other message “tags” and classifications may be associated with a given message in order to ensure that it is routed to and acted on by appropriate individuals within the hierarchical target message thread.

Customizable Hierarchy/Status Levels not Limitive

The present invention anticipates that the generic “tags” illustrated above in the severity/urgency level description may be made fully customizable to meet client needs. As stated previously there is no limitation on two-level severity/urgency tagging of messages, the system/method may incorporate a plethora of customizable message category hierarchy levels, with each category hierarchy level containing one or more hierarchy status markers. The category hierarchy levels and the hierarchy status markers may be fixed or individually customizable.

Severity Levels not Limitive

The present invention anticipates that messages may be routed and identified based on severity levels comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS classifications. The present invention specifically anticipates that this list of classifications may be larger or smaller than this list and teaches that this list is only exemplary of some preferred embodiments of the present invention. One skilled in the art will recognize that this list may be contracted or expanded in a wide variety of ways to address the messaging needs of a particular embodiment implementation.

Urgency Levels not Limitive

The present invention anticipates that messages may be routed and identified based on urgency levels comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS classifications. The present invention specifically anticipates that this list of classifications may be larger or smaller than this list and teaches that this list is only exemplary of some preferred embodiments of the present invention. One skilled in the art will recognize that this list may be contracted or expanded in a wide variety of ways to address the messaging needs of a particular embodiment implementation.

Encryption not Limitive

Many presently preferred embodiments utilize a variety of military grade 64-bit encryption algorithms that are commonly known to those skilled in the art, but one skilled in the art will recognize that longer encryption keys may be utilized and that there are a wide variety of encryption technologies available for use in this application, with no loss of generality in the teachings of the present invention.

Message Security not Limitive

Many presently preferred embodiments anticipate that custom software and/or other security measures may be installed at target system interfaces to ensure that messages received by these target system interfaces are held secure. This could include elements of physical security as well as software to prevent message copying (printing, screen shots, transfer to cut-and-paste buffers, etc.) from occurring and thus compromising message security. While many operating systems currently do not have this capability currently, the present invention anticipates that these restrictions may be lifted in the future.

The present invention teaches the use of a hierarchical message transmission thread to sequentially (or in parallel) send a message to a series of target system interfaces for presentation to end users. However, the system also anticipates the use of ancillary polling of target system interfaces to determine if they are in fact online/available, and if not, these target system interfaces can be eliminated (skipped) from consideration for message transfers.

Hierarchical Message Transmission Thread not Limitive

The hierarchical message transmission thread described herein may contain a plethora of target source interface addresses contained in a variety of physical formats and information pathway names. This list length is limited only by specific implementation of a particular embodiment and the present invention makes no limitation on this length. Furthermore, the response time values associated with each leg of the hierarchical message transmission thread may be individually set and are not necessarily uniform. The hierarchical message transmission thread may be augmented with conditional branching requirements to permit branching to other hierarchical message transmission threads based on requirements made by the message sourcing process.

Dashboard not Limitive

The present invention in some preferred embodiments utilizes “dashboards” to describe the graphical user interface to the messaging system/method detailed herein. This term should be broadly construed to incorporate any human interface device to a computer communications network, but is currently though to optimally encompass any form of GUI human and/or machine interface.

Color Indicia not Limitive

The present invention in some preferred embodiments utilizes a variety of colors that are associated with message severity and/or urgency classifications. While it is anticipated that some color combinations will be optimal for conveying message severity/urgency levels to the message recipients, no limitation on the range of color schemes is to be construed by the use of color in message presentation.

Message Fixation not Limitive

The present invention in many preferred embodiments utilizes a “fire and forget” methodology in transmission of messages in that once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified. While the currently preferred embodiments prohibit message modification and/or changing of message recipients, some alternate embodiments anticipate that these features may be implemented in some alternately preferred embodiments.

Coherent Thread Delivery not Limitive

The present invention in many preferred embodiments assumes that the message delivery thread hierarchy is fully defined such that there is never a “message delivery failure” in the context of a transmitted message never reaching and being acknowledged by at least one message recipient. However, some alternative embodiments may utilize message hierarchy threads that permit “dead” messages to be acknowledged as “undeliverable” if none of the targeted message recipients are available or capable of acknowledging the message.

Message Delivery Failure not Limitive

The present invention in many preferred embodiments assumes that the transmitted message is properly delivered to a recipient such that a message delivery “failure” is only noticed to the message originator when (a) the message is auto-forwarded or (b) the message originator views (via a mouse or other instrument) the status of a given transmitted message. Other forms of message delivery “failure” are possible, providing for more robust status information to be relayed to the message originator (and possibly inter-stage message recipients). Thus, the present invention while preferring a limited message delivery “failure” definition, may incorporate a wide variant of status and reporting mechanisms to track messages transmitted by the message originator.

Message Logging not Limitive

The present invention in many preferred embodiments reports an auto-forwarded message to all previous message recipients in the message delivery hierarchy (including the message originator), as well as logging the auto-forward condition to a log file. While this form of auto-forward status notification it (10), and control is returned to step (1) with he the recipient then able to access the attachment on screen at its destination presentation interface (3011).

One skilled in the art will recognize that these method steps may be individually eliminated, augmented, modified, and/or rearranged without limiting the teachings of the present invention.

Anonymous Interrogator of Message (AIM) Scanner (3100)

The present invention anticipates integrated scanning of messages during data entry to check for threats to life and/or property that may require immediate attention. Any time the Severity or Urgency Selection of ANONYMOUS is chosen from any level of messaging menu, an Anonymous Interrogator of Message (AIM) scanning and review subsystem may be activated. The sole purpose of this Anonymous Interrogator of Message program is necessitated due to the threats that may be directed to or against the client personnel, facilities, or other client property, or activities.

The Anonymous Interrogator of Message is a proactive discovery of insider threats and is designed to read in real time as a message is being composed. The Anonymous Interrogator of Message scans messages, but is initially thought to be optimally limited to ONLY interrogation of Anonymous messages.

The Anonymous Interrogator of Message scans Anonymous Messages for behavior, certain words or certain phrases, to identify a client computer location and allow client directed response in an attempt to intercept an employee before he or she becomes a danger to them or company or society. The system was developed to assist clients with the earliest internal and external terrorist threat identification.

Initially, the Anonymous Interrogator of Message will scan only the anonymous Messages generated by a client, but may be expanded if a client chooses. But the very existence of such a program is sure to unnerve some client employees. If they—the client management choose to make this information public within the enterprise. The real-time scans work only on internal anonymous messages in the client's message system, not the client's computer network and or system. By monitoring for “anomalies” and predicting extreme behavior based on words and phrases, catastrophes can be prevented.

This is how the Anonymous Interrogator of Message detection engines works. As soon as anyone chooses the Anonymous Severity or Urgency, from the Menu, the message system will start the program interrogator. This program interrogator will look for in real-time as the message is being entered those words and or phrases that the client has chosen to have encoded into the program that they have deemed as dangerous or terrorist-centered in nature.

The Anonymous Interrogator of Message is contained within the system framework of some preferred embodiments of the present invention, but all words or phrases are developed by and are included at the request of the client.

But the issue is not the scanning technology itself; it's how the information is used and whether it ultimately helps at all. Since there is no real data publicly available to substantiate that any of this technology is preventing terrorist attacks or strengthening the client from within, there is no definitive proof that as of today that this type of program interrogator has really thwarted a threat. However, it can be definitively stated that this technology will provide the ability to react in as close to real-time as possible to the client system where the threat is being generated, and therefore in a best case scenario provide the opportunity to intercept the threatening originator as the message is being generated.

A generalized method associated with the AIM process is illustrated in the flowchart of FIG. 31 (3100), wherein the method comprises the steps of:

• • (1) The client defines “suspicious” text/phrase combinations (3109) in a text/phrase database (3101);
  • (2) The message originator activates the Create Message dialog dashboard process (3102);
  • (3) The message originator enters message text via the message entry interface (3103);
  • (4) The dialog box dashboard process dynamically compares message originator input to the text/phrase database (3109) using a variety of matching algorithms that may include direct word matching and/or context sensitive text/phrase constructions (3104);
  • (5) If a text/phrase match is found, control is passed to step (7) (3105);
  • (6) Otherwise, message originator message entry continues as normal until and end-of-message or SEND is entered by the message originator with control passing to step (3) (3106);
  • (7) The suspicious message text/phrase match is reported to the CA and/or management personnel (3107); and
  • (8) The suspicious message text/phrase match is logged to an archive suspicious message database (3110) for later analysis and/or review and control passes to step (3) (3108).

One skilled in the art will recognize that these method steps may be individually eliminated, augmented, modified, and/or rearranged without limiting the teachings of the present invention.

New Message Arrival and Reply

The processing of new message arrivals and optional user replies will now be discussed. Generally speaking, a given user must be logged into the system to receive and reply to messages.

Upon receipt of a new message the entire dashboard will flash in the alternating colors of the Severity of the message as well as make an alert sound upon arrival.

The dashboard will continue to flash in the alternating colors of the Severity of the message and background color and continue to play the alert tones until the message receipt has been acknowledged by clicking on the dashboard.

The new incoming message will appear in the Current Status column at the top position and will flash in the Severity of the message color and background color at a rate of two times per second, and will continue to do so until the auto forward timer has reached zero. At this point the message will be auto forwarded to the next message stop and the message will now go into the steady-state and stop flashing. The user will no longer have the ability to reply to message.

If the user wishes to examine any message located under the current status section he only needs to hover the mouse over the message and an abbreviated amount of information will be displayed including the time remaining till auto forward.

From the user dashboard select the Reply to Message tab and then click the message you wish to reply to in the Current Status section of the dashboard. Note: The clock at the top of the current status section will now change to display the countdown until auto forward information for the selected message. As can be seen on the dashboard picture the selected message will be displayed in the Original Message Here box.

In the Enter Reply Here box the user may enter their reply while keeping an eye on the auto forward countdown clock and word count remaining. Note: When the auto forward countdown clock reaches zero the message will auto forward to the next message stop and the system will terminate all reply to message functionalities and the message will auto-forward to the next recipient with a notation: Auto Forwarded—No Action Taken.

When the user is satisfied with their reply they hit the SEND button to forward the message to the next recipient. Once the message has been successfully sent to the next recipient(s), it will appear in the Current Status window with the steady-state color of the severity confirming delivery of the message to the next recipient(s).

Message Auto-Forwarding (3200)

An important feature of the present invention messaging system is that of “auto-forwarding on non-response” by a message recipient. Generally speaking, non-response from a message recipient causes the message to be auto-forwarded to the next individual recipient in the chain of designated recipients. The methodology behind this behavior can be best understood using the flowchart of FIG. 32 (3200), wherein the method steps comprise:

• • (1) The message arrives at a client presentation interface (3201);
  • (2) A countdown timer is initialized with an Auto-Forward Time value that represents the amount of time the message recipient has to acknowledge and respond to the message, the timer is started, and an asynchronous system trap (AST) is configured to proceed to step (10) if the countdown timer reaches zero (3202);
  • (3) The client presentation message dialog box dashboard flashes with the message severity color code and audibly sounds an incoming message alert (3203);
  • (4) If the message is not acknowledged, control passes to step (3) (3204);
  • (5) The message is moved to the Current Status section of the client presentation interface dashboard dialog box and flashes in the message severity code (3205);
  • (6) The user selects the Reply To Message option from the client presentation interface dashboard dialog box (3206);
  • (7) The user selects the specific message to actually read and possibly reply (3207);
  • (8) The client presentation interface dashboard dialog box presents the user with text edit areas to read and reply to the message (3208);
  • (9) The countdown timer is stopped, the AST is released, and the message arrival method terminates (3209);
  • (10) An AST constantly monitors steps (3)-(8) to determine if the countdown timer has not expired, and continues if the AST has not been triggered by a countdown timer value of zero (3210); and
  • (11) If the AST detects a countdown timer value of zero, the message is automatically forwarded to the next recipient with a message reply of “Auto Forwarded—No Action Taken” sent to the message originator and all previous upstream message recipients (3211).

One skilled in the art will recognize that these method steps may be individually eliminated, augmented, modified, and/or rearranged without limiting the teachings of the present invention.

API Plug-in Modules (3300)

While the disclosed messaging system/method is very robust as to the intended purpose of reliably delivering messages to a variety of message recipients, the present invention anticipates that a wide variety of add-on software modules will be utilized in a spectrum of invention embodiments and applications. This anticipated expansion of system/method functionality is depicted generally in FIG. 33 (3300).

Referencing FIG. 33 (3300), the mechanism anticipated to be utilized in this context is that of Application Program Interface (API) plug-in software modules (3320) that interface with and become a part of the communications process (3302) and which are installed via the use of computer readable media (3321). This API plug-in support may incorporate the use of software and/or hardware additions to the basic system/method. Some of the currently anticipated options will now be discussed.

Hardware Plug-in Modules (3400)

As generally illustrated in FIG. 34 (3400), the present invention anticipates incorporation of a wide variety of hardware devices and their associated API plug-in software, including but not limited to data input terminals (3411, 3412), scanners (3421, 3422), still/video cameras (3431, 3432), audio input/output (3441, 3442), communications servers (3451, 3452), and portable/mobile devices such as tablets and/or smartphones/mobile devices (3461, 3462) that may operate over a variety of communication networks (3481) and be wireless (3482).

Secure Scanner Plug-in Modules (3500)

As generally illustrated in FIG. 34 (3400), the present invention anticipates incorporation of a scanner (3421, 3422) within the context of the messaging system. A typical implementation of this secure scanner plug-in is illustrated in FIG. 35 (3500).

This is anticipated as a purpose built stand-alone imaging system containing a flatbed scanner and touch screen monitor to display the dashboard connected to a computer housed in a tamper-proof enclosure. The connection to the Internet is hardwired and tamper resistant and constantly monitored. In commercial applications the unit is fixed to either a wall or the floor or both to prevent its movement. Any attempt to gain entry to the unit will trigger a message that is sent to the local authorities and will cause the system to become inoperative requiring an on-site reset.

The purpose of this secure scanner subsystem is to allow the scanning of documents and transmission of documents under the messaging system. It will provide a secure, real-time, transmission of encrypted documents from the originator to the recipient in minutes, as compared to the current prior art secure document transmission methods utilizing priority packaging, overnight mail, or private courier services.

This system provides complete integrity and security of all documents. The system provides the necessary legal constraints for bi-directional transmission of documents with signatures. The recipient will receive an original scanned document whose integrity is digitally signed and can be tracked from creation to reception with time in seconds to one ten thousandth accuracy.

The use of secure scanner applications are not limited to businesses where scanning and sending of documents is the normal course of business or having the units placed in commercially accessible locations for use by the general public.

The amount of space necessary for scanning a document will be designed and built to meet the client's requirements for use. Items necessary for use in a business environment of the secure scanner are relatively few and include operational power, Internet connection, the documents to be scanned, and the ability to select the recipient from the message recipient database. If the recipient is not in the database then the recipients' information may be manually entered. Items necessary for use in a commercial environment of the secure scanner are relatively few and include operational power, internet connection, a credit card, the documents, and as a minimum: the e-mail or IP address of the recipient.

In order to support secure document transmission with in situations where a single document is to be signed securely by two individuals, the document is securely scanned into the messaging system and transmitted to both parties, with each party signing the document separately. Then the signed original documents are transmitted to the opposing party for review and acceptance, in addition to archival of the documents within the messaging system infrastructure.

An example of this methodology can be seen in FIG. 35 (3500), wherein an initial user (3511) prepares/procures a document (3510) for signing and scans this using a secure scanner (3512) that then interacts with the communication process and/or its scanner API (3530) to store the document within a message database (3531). A second user (3521) with corresponding scanner (3522) may also perform similar operations to load one or more documents (3520) onto the message database (3531) via the API (3530).

The document(s) (3510, 3520) are then presented on the client presentation interfaces (3513, 3523) for user signature (3514, 3524) and the signed documents are then securely delivered electronically (3515, 3525) to the opposing party using the communication process/scanner API (3530) after being stored in a signed document archive (3532). Document signatures (3514, 3524) can be accomplished via video/still pictures (FIG. 34 (3432)), audio confirmation (FIG. 34 (3442)), secure server encryption authentication keys (FIG. 34 (3452)), tablet interfaces (FIG. 34 (3462)), and/or other biometric authentication interfaces.

Secure Document Signing/Scanner Method/(300)

The secure document scanner application generally illustrated in FIG. 35 (3500) may have associated with it a corresponding secure document signing/scanner method comprising the following method steps:

• • (1) One or both of USER-1 or USER-2 scans a document on a secure scanner (3601);
  • (2) The secure scanner transmits the document to a message archive database (3602);
  • (3) The communication process transmits the stored document to USER-1 and USER-2 simultaneously (3603);
  • (4) USER-1 “signs” the document using any authorized signature method, including but not limited to picture identification, voiceprint identification, handwriting sample, encryption key, password, etc. (3604);
  • (5) The signed USER-1 document is archived in the message database (3605);
  • (6) USER-2 “signs” the document using any authorized signature method, including but not limited to picture identification, voiceprint identification, handwriting sample, encryption key, password, etc. (3606);
  • (7) The signed USER-2 document is archived in the message database (3607);
  • (8) The communications process combines the USER-1 and USER-2 documents to form a combined USER-12 document on the message server (3608);
  • (9) The USER-12 document is transmitted to USER-1 and USER-2 via message by the communications process to verify two-party signature of both USER-1 and USER-2 (3609); and
  • (10) The secure document signing/scanner method terminates (3610).

One skilled in the art will recognize that these method steps may be individually eliminated, augmented, modified, and/or rearranged without limiting the teachings of the present invention.

PLC Plug-in Modules (3700)

A programmable logic controller (PLC) or programmable controller is a digital computer used for the automation of electromechanical processes, such as control of machinery on factory assembly lines, amusement rides, or light fixtures. PLCs are used in many industries. Unlike general-purpose computers, the PLC is designed for multiple inputs and outputs, extended temperature ranges, immunity to electrical noise, and resistance to vibration and impact. Programs to control machine operation are typically stored in battery-backed-up or non-volatile memory. A PLC is an example of a hard real-time system since output results must be produced in response to input conditions within a bounded time or unintended operation will result.

PLCs have built in communications ports, usually 9-pin RS-232, but optionally EIA-485 or Ethernet. Modbus, BACnet or DF1 is usually included as one of the communications protocols. Other options include various field busses such as DeviceNet or Profibus. One skilled in the art will recognize that there are other communications protocols that may be commonly used in industry within the scope of this teaching.

Most modern PLCs can communicate over a network to another system such as computers running a Supervisory Control and Data Acquisition (SCADA) system or web browser. PLCs used in larger I/O systems may have peer-to-peer (P2P) communication between processors. This allows separate parts of a complex process to have individual control while allowing the subsystems to co-ordinate over the communication link. These communication links are also often used for HMI devices such as keypads or PC-type workstations.

As generally illustrated in FIG. 37 (3700), the present invention anticipates that some API interface (3720) (and associated non-transitory computer readable medium (3721)) may be provide for PLC control within the messaging system, possibly with the use of an additional license or other authentication access mechanism. With this context, the machine PLC will be tab accessible by those with the proper credentials from the message dashboard. The use of a centralized command listing wherein predefined decisions are stored in a message definition format will simplify the process of selection for the user in situations where the PLC (3708) (with its associated non-transitory computer readable medium containing control software (3709) and associated industrial equipment processes (3719)) must be controlled within the messaging framework.

The authorized user can then make a selection of the appropriate machine and PLC control codes based on the severity and urgency to send a message. A notification verifies the message was sent to the right machines and/or PLC's in the right order and designated timeframe. Authorized clients that have machines/PLCs with communications capabilities tied to a networked can use the messaging system to allow communications to/from PLCs when necessary.

Depending upon the magnitude and scope of the event there well may be different machine codes and PLC commands sent in parallel to different machines and PLC's. This provides real-time updates and responses, for the Command Director originating the message, by machine and PLC. Due to the real-time informational feedback it is possible for the message originator to make efficient, informed decisions based on the information to discontinue a particular command set and/or send another command set. The use of this information would be of critical value during the event as well as during the post event investigations and will be pivotal in the development of better command and control structures to be used in the future. The abilities of the messaging system to be utilized in these circumstances allow scalability for future expansion of the messaging system to control a wide variety of disasters and other serious situations in which intelligent and immediate machine control may result in reduced property and/or life loss.

Licensing Plug-in Modules (3800)

The present invention anticipates that a variety of licensing plug-in API modules may be added to the basic communication process as depicted in FIG. 38 (3800), with the API (3820) optionally comprising computer readable media for license keys and other license specific enablement information. Included within this scope is the use of security tokens and the like to enable access to specific messaging functions and/or specific PLC (3808) controls.

Voice Recognition Interface

The present invention anticipates that the use of voice recognition software within the context of the messaging system. As generally illustrated in FIG. 34 (3442), the use of audio input as an auxiliary data stream is anticipated by the API plug-in structure of the messaging system/method. While this voice recognition API may support disabled users, the system can also be utilized by non-impaired individuals.

People with disabilities can benefit from the use of speech recognition programs. Individuals who have physical limitations ranging from mild repetitive stress injuries to involved disabilities that preclude the use of conventional computer input devices. Speech recognition is also a benefit to the deaf for the creation of voicemail to text, relay services, and closed-captioned telephony. Individuals with learning disabilities who have problems with thought-to-paper communications can benefit from the use of this type of software.

While many speech recognition applications are available, the present invention anticipates a commercial software package such as DRAGON NATURALLYSPEAKING®/DICTATE® brands of speech recognition software would be suitable for this use. This application is a speech recognition software package developed and sold by Nuance Communications for GUI-based personal computers, including 32-bit and 64-bit systems and a variety of operating systems.

DRAGON NATURALLYSPEAKING® brand of speech recognition software utilizes a minimal user interface. The software has three primary areas of functionality: dictation, text-to-speech and command input. The user is able to dictate and have speech transcribed as written text, have a document synthesized as an audio stream, or issue commands that are recognized as such by the message System Program. In addition voice profiles can be accessed through different computers in a networked environment, although the audio hardware and configuration must be identical on both machines. The present invention anticipates that these commercial software packages can be integrated into the user messaging interface to permit dictation, text-to-speech, and a variety of command inputs to be driven audibly without the need for a tactile human messaging interface.

Mobile Devices and Multiprotocol Label Switching (MPLS) (3900)

The present invention anticipates the use of mobile devices as the hardware platform from which message are originated and on which messages are received. Within this context, the use of Multiprotocol Label Switching (MPLS) is specifically anticipated as an optimal communication methodology for data transmission to/from the mobile devices. Multiprotocol Label Switching (MPLS) is a mechanism in high-performance telecommunication networks that directs data from one network node to the next based on short path labels rather than long network addresses, avoiding complex lookups in a routing table. The labels identify virtual links (paths) between distant nodes rather than endpoints. MPLS can encapsulate packets of various network protocols. MPLS supports a range of access technologies, including T1/E1, ATM, Frame Relay and DSL.

Use of Mobile Broadband to Connect to the Internet

As generally illustrated in FIG. 39 (3900), mobile devices (3901, 3902) include smart devices such as: tablet computers, smartphones, mobile devices, notebooks, etc. Mobile broadband technology, also called wireless wide area network (WWAN) technology (3903), provides mobile Internet connectivity. Use of mobile broadband generally requires a data card and a data plan with a mobile broadband provider. After procurement of a smart device and data plan, the Subscriber Identity Module (SIM) and the mobile broadband service for the SIM is activated by the mobile services provider.

Messaging System and Mobile Applet

Mobile Application Definition—Also called mobile apps, this is a term used to describe Internet applications that run on smartphones and other mobile devices. Mobile applications grant users access to Internet services more commonly accessed on desktop or notebook computers. For the purposes of the present invention the mobile app is the mobile-based messaging System client.

Mobile System Log on (4000)

The Mobile System user will be presented with the logon screen as generally illustrated in FIG. 40 (4000). In this instance the authenticator code can be generated via the watch FOB and or use of a mobile application authenticator code generator. The mobile application user will enter password and authenticator code and will generally be limited to three attempts to logon. If the user is unsuccessful after the third attempt they will be locked out from a further attempt and will need to contact the certified administrator (CA) for assistance.

A CA will use the same warning code protocol. See warning code protocol for additional information. Upon successful logon, the user/CA will be able to utilize any services for which they are licensed. They will be presented with either the user or CA mobile user dashboard.

Messaging System Using Mobile Application

The messaging system mobile applet will allow a user/CA (hereafter referred to simply as user) access to various services within the messaging application for which they are properly licensed (message on the fly, attachment, interactive checklist, machine controls, etc.) on any mobile device. Certain application functionalities may be limited due to size and scope of use and viewing on a mobile device.

Technical Process

The Mobile Applet will provide the ability to communicate on the WWAN which is displayed in FIG. 39 (3900). Once the WWAN's connection to the MPLS is made the mobile application functionality will be appropriately scaled for use on a mobile device. The user of the smartphone or mobile device will have to determine what data/files to display based on the screen size of the smart phone or mobile device. The standard user will need to update their administration files to show their contact priority preferences, i.e. desktop first, notebook second, mobile device, etc. The system may select contacts based on the selected preferences. As in all cases, if a user is not online or available the message will simply look for the next alternate. In the event where there is no alternate available, the message will auto forward to the next recipient in the chain.

The mobile system application will provide the CA with the same abilities to create a message, modify a message, or create a user message, reply to a message, select contact preferences and/or read a message. The mobile system application is not necessarily intended as a replacement for a desktop computer but may be scaled for use and viewing on the mobile device.

System/Method Variations

The present invention anticipates a wide variety of system/method variations in the basic theme of construction. The examples presented previously do not represent the entire scope of possible usages. They are meant to cite a few of the almost limitless possibilities. Some preferred system/method embodiments include the following:

• • An embodiment wherein the message is classified based on a customizable hierarchy level.
  • An embodiment wherein the message is classified based on a hierarchy level.
  • An embodiment wherein the message is classified based on a hierarchy level, the hierarchy level comprising one or more customizable hierarchy status markers.
  • An embodiment wherein the message is classified based on a customizable hierarchy level, the hierarchy level comprising one or more customizable hierarchy status markers.
  • An embodiment wherein the message is classified based on severity level.
  • An embodiment wherein the message is classified based on severity level, the severity level further comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS levels.
  • An embodiment wherein the message is classified based on urgency level.
  • An embodiment wherein the message is classified based on urgency level, the urgency level further comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS levels.
  • An embodiment wherein the message is classified based on a specific menu selection from the source user interface.
  • An embodiment wherein the message is classified based on a specific menu selection from the source user interface, the message classification further comprising LIFE CRITICAL/MISSION CRITICAL, CRITICAL, URGENT, CORRECTIVE ACTION/AUDIT, CONTINUOUS IMPROVEMENT/SUGGESTION, INFORMATION TRANSFER, and/or ANONYMOUS REPORTING.
  • An embodiment wherein the message is encrypted by the source messaging client process.
  • An embodiment wherein the message is encrypted when stored on the message database.
  • An embodiment wherein the message is decrypted by the target messaging client process.
  • An embodiment wherein the predetermined time is set individually for each of the target system interfaces.
  • An embodiment wherein the predetermined time is based on calendar-based information.
  • An embodiment wherein the transmission of the message to the target system interface is sequentially prioritized via use of a hierarchical target message thread.
  • An embodiment wherein the source messaging client process receives conditional branching requirements for the target system interface via the source messaging system interface.
  • An embodiment wherein the message host process further comprises anticipatory message queuing wherein the message is sent to the target system interface and the next target system interface addressed by a hierarchical target message address list with information indicating that the next target system interface is to wait to process the message until instructed to do so by the message host process.
  • An embodiment wherein the target system interface is polled to determine if it is online/available, and if not, the target system interface is skipped and the next target system interface addressed by a hierarchical target message address list is utilized as the new target for delivery of the message.

One skilled in the art will recognize that other embodiments are possible based on combinations of elements taught within the above invention description.

Generalized Computer Usable Medium

As generally illustrated in FIG. 1 (0100), the system embodiments of the present invention can incorporate a variety of computer readable media (0105) that comprise non-transitory computer usable medium having computer readable code means embodied therein. One skilled in the art will recognize that the software associated with the various processes described herein can be embodied in a wide variety of computer accessible media from which the software is loaded and activated. Pursuant to In re Beauregard, 35 USPQ2d 1383 (U.S. Pat. No. 5,710,578), the present invention anticipates and includes this type of computer readable media within the scope of the invention.

CONCLUSION

A messaging system and method with dead man switching providing for hierarchical delivery of messages based on selected message hierarchy levels with controlled delivery/response timing is disclosed. The system and method incorporates a messaging host that communicates with a messaging source client that creates and prioritizes a message and targets address(es) for the message. This message is then transmitted to the target address(es) using a hierarchical transmission thread having set limits on response times for each address within the thread. Reception of the message by each target(s) produces visual and/or auditory notification at the target(s). Messages are automatically forwarded to remaining target(s) within the thread upon expiration of a timer should the target(s) fail to respond to the message within a predetermined time. Failure of the target(s) to respond to the message(s) is reported bi-directionally along the thread and forwarded to remaining target(s) in the thread.

Claims

1. A non-transitory computer usable medium having computer-readable program code comprising a messaging method wherein said method controls a messaging system comprising:

(a) a communications server having—

1) message database;

2) message file server;

3) message host process operating on said file server; and

4) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said message host process;

(b) a remote source message system interface stored in memory for data entry and generation of messages on the communication server;

(c) source messaging client process residing on the communication server and monitoring status of acceptance/reading by target;

(d) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said source messaging client process;

(e) a remote target messaging system interface stored in memory for receiving, displaying and replying to said message data;

(f) target messaging client process residing on the communication server; and

(g) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said target messaging client process;

wherein,

said source messaging client process receives the messages and message severity/urgency classifications from a source user via said source messaging system;

said source messaging system transmits said messages and said message severity/urgency classifications to said message host process for storage on said message database via said message file server;

said message host process transmits said message and said message severity/urgency classification to said target system interface via a communications medium for display by said target system interface under control of said target message process;

said target message process responds to said message host process if said message is examined on said target system interface by a user;

said message host process initiates a dead man messaging process that waits a predetermined amount of time for said response to said message by said user and if said predetermined time is exceeded, said message is updated and forwarded to another target system interface for inspection by another user; and

said message host process reports to said source message process the status of said message to each of said target systems;

with said method comprising the steps of:

(1) logging onto the communication server by a message originator through the message entry interface

(2) Entering data into a message entry interface by a message originator and creating a message within the communication server;

(3) entering a message severity/urgency classification data from said messaging source interface for message residing on communications server;

(4) transmitting said message said message severity/urgency classification to said message host and storing the message on said message database via said communications server;

(5) traversing a hierarchical target message thread to determine the targets for said message;

(6) selecting the next message target within said hierarchical message thread;

(7) determining if said hierarchical message thread is exhausted, and if so, proceeding to step (11);

(8) transmitting said message within the communications server to the currently selected remote target system interface within said hierarchical message thread;

(9) determining if said message has been read by said currently selected remote target system interface within said hierarchical message thread, and if so, proceeding to step (12);

(10) determining if a target response timer has expired, and if not, proceeding to said step (9);

(11) transmitting said message to said currently selected remote target system interface within said hierarchical message thread;

(12) reporting to said source messaging interface that message reception has failed and proceeding to said step (6);

(13) reporting to said source messaging interface that said message has been received and returning any optional user comment; and

(14) optionally entering comments on said message and/or passing through said message to said current or another hierarchical message thread.

2. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a hierarchy level.

3. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a customizable hierarchy level.

4. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

5. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a customizable hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

6. The non-transitory computer usable medium of claim 1 wherein said message is classified based on severity level.

7. The non-transitory computer usable medium of claim 1 wherein said message is classified based on severity level, said severity level further comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS levels.

8. The non-transitory computer usable medium of claim 1 wherein said message is classified based on urgency level.

9. The non-transitory computer usable medium of claim 1 wherein said message is classified based on urgency level, said urgency level further comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS levels.

10. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a specific menu selection from said source user interface.

11. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a specific menu selection from said source user interface, said message classification further comprising LIFE CRITICAL/MISSION CRITICAL, CRITICAL, URGENT, CORRECTIVE ACTION/AUDIT, CONTINUOUS IMPROVEMENT/SUGGESTION, INFORMATION TRANSFER, and/or ANONYMOUS REPORTING.

12. The non-transitory computer usable medium of claim 1 wherein said message is encrypted by said source messaging client process.

13. The non-transitory computer usable medium of claim 1 wherein said message is encrypted when stored on said message database.

14. The non-transitory computer usable medium of claim 1 wherein said message is decrypted by said target messaging client process.

15. The non-transitory computer usable medium of claim 1 wherein said predetermined time is set individually for each of said target system interfaces.

16. The non-transitory computer usable medium of claim 1 wherein said predetermined time is based on calendar-based information.

17. The non-transitory computer usable medium of claim 1 wherein the transmission of said message to said target system interface is sequentially prioritized via use of a hierarchical target message thread.

18. The non-transitory computer usable medium of claim 1 wherein said source messaging client process receives conditional branching requirements for said target system interface via said source messaging system interface.

19. The non-transitory computer usable medium of claim 1 wherein said message host process further comprises anticipatory message queuing wherein said message is sent to said target system interface and the next target system interface addressed by a hierarchical target message address list with information indicating that said next target system interface is to wait to process said message until instructed to do so by said message host process.

20. The non-transitory computer usable medium of claim 1 wherein said target system interface is polled to determine if it is online/available, and if not, said target system interface is skipped and the next target system interface addressed by a hierarchical target message address list is utilized as the new target for delivery of said message.

21. A messaging system comprising:

(a) a communications server having—

1) a message database;

2) a message file server;

3) a message host process operating on said file server; and

4) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said message host process;

(b) a remote source message system interface stored in memory for data entry and generation of messages on the communication server;

(c) source messaging client process residing on the communication server and monitoring status of acceptance/reading by target;

(d) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said source messaging client process;

(e) a remote target messaging system interface stored in memory for receiving, displaying and replying to said message;

(f) target messaging client process residing on the communication server; and

(g) non-transitory computer readable medium in communication with a processor executing computer instructions to perform said target messaging client process;

wherein,

said source messaging client process receives the messages and message severity/urgency classifications from a source user via said source messaging system;

said source messaging system transmits said messages and said message severity/urgency classifications to said message host process for storage on said message database via said message file server;

said message host process transmits said message and said message severity/urgency classification to said target system interface via a communications medium for display by said target system interface under control of said target message process;

said target message process responds to said message host process if said message is examined on said target system interface by a target user;

said message host process initiating a dead man messaging method that waits a predetermined amount of time for said response to said message by said target user and if said predetermined time is exceeded, said message is updated and forwarded to another target system interface for inspection by another target user; and

said message host process reports to said source message process the status of said message to each of said target systems

with said messaging system utilizing a processor to perform the steps of:

(1) logging onto the communication server by a message originator through the message entry interface

(2) entering data into a message entry interface by a message originator and creating a message within the communication server;

(3) entering a message severity/urgency classification data from said messaging source interface for message residing on communications server;

(4) transmitting said message said message severity/urgency classification to said message host and storing the message on said message database via said communications server;

(5) traversing a hierarchical target message thread to determine the targets for said message;

(6) selecting the next message target within said hierarchical message thread;

(7) determining if said hierarchical message thread is exhausted, and if so, proceeding to step (11);

(8) transmitting said message within the communications server to the currently selected remote target system interface within said hierarchical message thread;

(9) determining if said message has been read by said currently selected remote target system interface within said hierarchical message thread, and if so, proceeding to step (12);

(10) determining if a target response timer has expired, and if not, proceeding to said step (9);

(11) transmitting said message to said currently selected remote target system interface within said hierarchical message thread;

(12) reporting to said source messaging interface that message reception has failed and proceeding to said step (6);

(13) reporting to said source messaging interface that said message has been received and returning any optional user comment; and

(14) optionally entering comments on said message and/or passing through said message to said current or another hierarchical message thread.

22. The messaging system of claim 21 wherein said message is classified based on a customizable hierarchy level.

23. The messaging system of claim 21 wherein said message is classified based on a hierarchy level.

24. The messaging system of claim 21 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

25. The messaging system of claim 21 wherein said message is classified based on a customizable hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

26. The messaging system of claim 21 wherein said message is classified based on severity level.

27. The messaging system of claim 21 wherein said message is classified based on severity level, said severity level further comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS levels.

28. The messaging system of claim 21 wherein said message is classified based on urgency level.

29. The messaging system of claim 21 wherein said message is classified based on urgency level, said urgency level further comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS levels.

30. The messaging system of claim 21 wherein said message is classified based on a specific menu selection from said source user interface.

31. The messaging system of claim 21 wherein said message is classified based on a specific menu selection from said source user interface, said message classification further comprising LIFE CRITICAL/MISSION CRITICAL, CRITICAL, URGENT, CORRECTIVE ACTION/AUDIT, CONTINUOUS IMPROVEMENT/SUGGESTION, INFORMATION TRANSFER, and/or ANONYMOUS REPORTING.

32. The messaging system of claim 21 wherein said message is encrypted by said source messaging client process.

33. The messaging system of claim 21 wherein said message is encrypted when stored on said message database.

34. The messaging system of claim 21 wherein said message is decrypted by said target messaging client process.

35. The messaging system of claim 21 wherein said predetermined time is set individually for each of said target system interfaces.

36. The messaging system of claim 21 wherein said predetermined time is based on calendar-based information.

37. The messaging system of claim 21 wherein the transmission of said message to said target system interface is sequentially prioritized via use of a hierarchical target message thread.

38. The messaging system of claim 21 wherein said source messaging client process receives conditional branching requirements for said target system interface via said source messaging system interface.

39. The messaging system of claim 21 wherein said message host process further comprises anticipatory message queuing wherein said message is sent to said target system interface and the next target system interface addressed by a hierarchical target message address list with information indicating that said next target system interface is to wait to process said message until instructed to do so by said message host process.

40. The messaging system of claim 21 wherein said target system interface is polled to determine if it is online/available, and if not, said target system interface is skipped and the next target system interface addressed by a hierarchical target message address list is utilized as the new target for delivery of said message.

41. A messaging method wherein said method controls a messaging system comprising:

(a) a communications server having—

1) a message database;

2) a message file server;

3) a message host process operating on said file server; and

4) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said message host process;

(b) a remote source message system interface stored in memory for data entry and generation of messages on the communication server;

(c) source messaging client process residing on the communication server and monitoring status of acceptance/reading by target;

(d) non-transitory computer readable medium in communication with a processor executing computer instructions to perform said source messaging client process;

(e) a remote target messaging system interface stored in memory for receiving, displaying and replying to said message data;

(f) target messaging client process residing on the communication server; and

(g) non-transitory computer readable medium in communication with a processor executing computer instructions to perform said target messaging client process;

wherein,

said source messaging client process receives the messages and message severity/urgency classifications from a source user via said source messaging system;

said source messaging system transmits said messages and said message severity/urgency classifications to said message host process for storage on said message database via said message file server;

said message host process transmits said message and said message severity/urgency classification to said target system interface via a communications medium for display by said target system interface under control of said target message process;

said target message process responds to said message host process if said message is examined on said target system interface by a user;

said message host process initiating a dead man messaging method that waits a predetermined amount of time for said response to said message by said user and if said predetermined time is exceeded, said message is updated and forwarded to another target system interface for inspection by another user; and

said message host process reports to said source message process the status of said message to each of said target systems;

with said method comprising the steps of:

(1) logging onto the communication server by a message originator through the message entry interface

(2) entering data into a message entry interface by a message originator and creating a message within the communication server;

(3) entering a message severity/urgency classification data from said messaging source interface for message residing on communications server;

(4) transmitting said message said message severity/urgency classification to said message host and storing the message on said message database via said communication server;

(5) traversing a hierarchical target message thread to determine the targets for said message;

(6) selecting the next message target within said hierarchical message thread;

(7) determining if said hierarchical message thread is exhausted, and if so, proceeding to step (11);

(8) transmitting said message within the communications server to the currently selected remote target system interface within said hierarchical message thread;

(9) determining if said message has been read by said currently selected remote target system interface within said hierarchical message thread, and if so, proceeding to step (12);

(10) determining if a target response timer has expired, and if not, proceeding to said step (9);

(11) transmitting said message to said currently selected remote target system interface within said hierarchical message thread;

(12) reporting to said source messaging interface that message reception has failed and proceeding to said step (6);

(13) reporting to said source messaging interface that said message has been received and returning any optional user comment; and

(14) optionally entering comments on said message and/or passing through said message to said current or another hierarchical message thread.

42. The messaging method of claim 41 wherein said message is classified based on a hierarchy level.

43. The messaging method of claim 41 wherein said message is classified based on a customizable hierarchy level.

44. The messaging method of claim 41 wherein said message is classified based on a customizable hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

45. The messaging method of claim 41 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

46. The messaging method of claim 41 wherein said message is classified based on severity level.

47. The messaging method of claim 41 wherein said message is classified based on severity level, said severity level further comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS levels.

48. The messaging method of claim 41 wherein said message is classified based on urgency level.

49. The messaging method of claim 41 wherein said message is classified based on urgency level, said urgency level further comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS levels.

50. The messaging method of claim 41 wherein said message is classified based on a specific menu selection from said source user interface.

51. The messaging method of claim 41 wherein said message is classified based on a specific menu selection from said source user interface, said message classification further comprising LIFE CRITICAL/MISSION CRITICAL, CRITICAL, URGENT, CORRECTIVE ACTION/AUDIT, CONTINUOUS IMPROVEMENT/SUGGESTION, INFORMATION TRANSFER, and/or ANONYMOUS REPORTING.

52. The messaging method of claim 41 wherein said message is encrypted by said source messaging client process.

53. The messaging method of claim 41 wherein said message is encrypted when stored on said message database.

54. The messaging method of claim 41 wherein said message is decrypted by said target messaging client process.

55. The messaging method of claim 41 wherein said predetermined time is set individually for each of said target system interfaces.

56. The messaging method of claim 41 wherein said predetermined time is based on calendar-based information.

57. The messaging method of claim 41 wherein the transmission of said message to said target system interface is sequentially prioritized via use of a hierarchical target message thread.

58. The messaging method of claim 41 wherein said source messaging client process receives conditional branching requirements for said target system interface via said source messaging system interface.

59. The messaging method of claim 41, wherein said message host process further comprises anticipatory message queuing wherein said message is sent to said target system interface and the next target system interface addressed by a hierarchical target message address list with information indicating that said next target system interface is to wait to process said message until instructed to do so by said message host process.

60. The messaging method of claim 41 wherein said target system interface is polled to determine if it is online/available, and if not, said target system interface is skipped and the next target system interface addressed by a hierarchical target message address list is utilized as the new target for delivery of said message.

61. A non-transitory computer usable medium having computer-readable program code comprising a messaging method wherein said method controls a messaging system comprising:

(a) a communications server having—

1) a message database;

2) a message file server;

3) a message host process operating on said file server; and

4) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said message host process;

(b) a remote source message system interface stored in memory for data entry and generation of messages on the communication server;

(c) a source messaging client process residing on the communication server and monitoring status of acceptance/reading by target;

(d) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said source messaging client process;

(e) a remote target messaging system interface stored in memory for receiving, displaying and replying to said message data;

(f) a target messaging client process residing on the communication server; and

(g) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said target messaging client process;

wherein,

said source messaging client process receives the messages and message severity/urgency classifications from a source user via said source messaging system;

said source messaging system transmits said messages and said message severity/urgency classifications to said message host process for storage on said message database via said message file server;

said message host process transmits said message and said message severity/urgency classification to said target system interface via a communications medium for display by said target system interface under control of said target message process;

said target message process responds to said message host process if said message is examined on said target system interface by a user;

said message host process initiating a dead man messaging method that waits a predetermined amount of time for said response to said message by said user and if said predetermined time is exceeded, said message is retransmitted to another target system interface for inspection by another user; and

said message host process reports to said source message process the status of attempts to deliver said message to each of said target systems;

with said method comprising the steps of:

(1) logging onto the communication server by a message originator through the message entry interface

(2) entering data into a message entry interface by a message originator and creating a message within the communication server;

(3) entering a message severity/urgency classification data from said messaging source interface for message residing on communications server;

(4) transmitting said message said message severity/urgency classification to said message host and storing the message on said message database via said file server;

(5) traversing a hierarchical target message thread to determine the targets for said message;

(6) selecting the next message target within said hierarchical message thread;

(7) determining if said hierarchical message thread is exhausted, and if so, proceeding to step (10);

(8) transmitting said message within the communications server to the currently selected remote target system interface within said hierarchical message thread;

(9) determining if said message has been read by said currently selected remote target system interface within said hierarchical message thread, and if so, proceeding to step (12);

(10) determining if a target response timer has expired, and if not, proceeding to said step (9);

(11) transmitting said message to said currently selected remote target system interface within said hierarchical message thread;

(12) reporting to said source messaging interface that message reception has failed and proceeding to said step (6);

(13) reporting to said source messaging interface that said message has been received and returning any optional user comment; and

(14) optionally entering comments on said message and/or passing through said message to said current or another hierarchical message thread.

62. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a hierarchy level.

63. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a customizable hierarchy level.

64. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

65. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a customizable hierarchy level, said hierarchy level comprising one or more customizable hierarchy status markers.

66. The non-transitory computer usable medium of claim 61 wherein said message is classified based on severity level.

67. The non-transitory computer usable medium of claim 61 wherein said message is classified based on severity level, said severity level further comprising SEVERE, SERIOUS, MODERATE, MINOR, and/or ANONYMOUS levels.

68. The non-transitory computer usable medium of claim 61 wherein said message is classified based on urgency level.

69. The non-transitory computer usable medium of claim 61 wherein said message is classified based on urgency level, said urgency level further comprising IMMEDIATE, URGENT, NEED SOON, INFORMATIONAL ONLY, and/or ANONYMOUS levels.

70. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a specific menu selection from said source user interface.

71. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a specific menu selection from said source user interface, said message classification further comprising LIFE CRITICAL/MISSION CRITICAL, CRITICAL, URGENT, CORRECTIVE ACTION/AUDIT, CONTINUOUS IMPROVEMENT/SUGGESTION, INFORMATION TRANSFER, and/or ANONYMOUS REPORTING.

72. The non-transitory computer usable medium of claim 61 wherein said message is encrypted by said source messaging client process.

73. The non-transitory computer usable medium of claim 61 wherein said message is encrypted when stored on said message database.

74. The non-transitory computer usable medium of claim 61 wherein said message is decrypted by said target messaging client process.

75. The non-transitory computer usable medium of claim 61 wherein said predetermined time is set individually for each of said target system interfaces.

76. The non-transitory computer usable medium of claim 61 wherein said predetermined time is based on calendar-based information.

77. The non-transitory computer usable medium of claim 61 wherein the transmission of said message to said target system interface is sequentially prioritized via use of a hierarchical target message thread.

78. The non-transitory computer usable medium of claim 61 wherein said source messaging client process receives conditional branching requirements for said target system interface via said source messaging system interface.

79. The non-transitory computer usable medium of claim 61 wherein said message host process further comprises anticipatory message queuing wherein said message is sent to said target system interface and the next target system interface addressed by a hierarchical target message address list with information indicating that said next target system interface is to wait to process said message until instructed to do so by said message host process.

80. The non-transitory computer usable medium of claim 61 wherein said target system interface is polled to determine if it is online/available, and if not, said target system interface is skipped and the next target system interface addressed by a hierarchical target message address list is utilized as the new target for delivery of said message.

81. The non-transitory computer usable medium of claim 1 wherein the human interface is selected from visual, audible, speech, and tactile.

82. The non-transitory computer usable medium of claim 1 wherein the messaging processor host is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

83. The non-transitory computer usable medium of claim 1 wherein the source is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

84. The non-transitory computer usable medium of claim 1 wherein the target is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

85. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more fixed hierarchy status markers.

86. The non-transitory computer usable medium of claim 1 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more individually customizable hierarchy status markers.

87. The non-transitory computer usable medium of claim 1 wherein said message is classified based on severity level, wherein said severity level is customizable.

88. The non-transitory computer usable medium of claim 1 wherein said message is classified based on urgency level, wherein said urgency level is customizable.

89. The non-transitory computer usable medium of claim 1 wherein the encryption algorithm is selectable.

90. The non-transitory computer usable medium of claim 1 wherein the military grade encryption algorithm is selected from 64-bit, 128 bit, 256 bit, 512 bit, 1024 bit, 2048 bit, and 4096 bit.

91. The non-transitory computer usable medium of claim 1 wherein said message is secured at the target interface through software to prevent message reproduction.

92. The non-transitory computer usable medium of claim 1 wherein target system interface availability is determined by ancillary polling.

93. The non-transitory computer usable medium of claim 1 wherein the response time value associated with each leg of the hierarchical message transmission thread may be individually set.

94. The non-transitory computer usable medium of claim 1 wherein said message is “fire and forget” wherein once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified.

95. The non-transitory computer usable medium of claim 1 wherein said message host and file server are geographically diverse.

96. The non-transitory computer usable medium of claim 1 wherein said target message system anticipates an incoming message and queues the target system for an activation message to process the incoming message.

97. The non-transitory computer usable medium of claim 1 wherein multiple target message systems simultaneously anticipate an incoming message and queues the target systems for an activation message to process the incoming message.

98. The non-transitory computer usable medium of claim 1 wherein said message routing is based on calendar information selected from time of the day, day of the week, seasonal events, holidays, vacations schedules, meetings, and appointments.

99. The non-transitory computer usable medium of claim 1 wherein said message routing is determined by a decision matrix with the inputs selected from calendars, external-real-time events and programmable logic unit inputs.

100. The non-transitory computer usable medium of claim 1 wherein an Anonymous Interrogator of message Scanner real-time scans messages for behavior, pre-determined words and pre-determined phrases to identify a potential threat and threat location within the message system.

101. The messaging system of claim 21 wherein the human interface is selected from visual, audible, speech, and tactile.

102. The messaging system of claim 21 wherein the messaging processor host is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

103. The messaging system of claim 21 wherein the source is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

104. The messaging system of claim 21 wherein the target is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

105. The messaging system of claim 21 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more fixed hierarchy status markers.

106. The messaging system of claim 21 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more individually customizable hierarchy status markers.

107. The messaging system of claim 21 wherein said message is classified based on severity level, wherein said severity level is customizable.

108. The messaging system of claim 21 wherein said message is classified based on urgency, wherein said urgency level is customizable.

109. The messaging system of claim 21 wherein the encryption algorithm is selectable.

110. The non-transitory computer usable medium of claim 21 wherein the military grade encryption algorithm is selected from 64-bit, 128 bit, 256 bit, 512 bit, 1024 bit, 2048 bit, and 4096 bit.

111. The messaging system of claim 21 wherein said message is secured at the target interface through software to prevent message reproduction.

112. The messaging system of claim 21 wherein target system interface availability is determined by ancillary polling.

113. The messaging system of claim 21 wherein the response time value associated with each leg of the hierarchical message transmission thread may be individually set.

114. The messaging system of claim 21 wherein said message is “fire and forget” wherein once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified.

115. The messaging system of claim 21 wherein said message host and file server are geographically diverse.

116. The messaging system of claim 21 wherein said target message system anticipates an incoming message and queues the target system for an activation message to process the incoming message.

117. The messaging system of claim 21 wherein multiple target message systems simultaneously anticipate an incoming message and queues the target systems for an activation message to process the incoming message.

118. The messaging system of claim 21 wherein said message routing is based on calendar information selected from time of the day, day of the week, seasonal events, holidays, vacations schedules, meetings, and appointments.

119. The messaging system of claim 21 wherein said message routing is determined by a decision matrix with the inputs selected from calendars, external-real-time events and programmable logic unit inputs.

120. The messaging system of claim 21 wherein an Anonymous Interrogator of message Scanner real-time scans messages for behavior, pre-determined words and pre-determined phrases to identify a potential threat and threat location within the message system.

121. The messaging method of claim 41 wherein the human interface is selected from visual, audible, speech, and tactile.

122. The messaging method of claim 41 wherein the messaging processor host is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

123. The messaging method of claim 41 wherein the source is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

124. The messaging method of claim 41 wherein the target is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

125. The messaging method of claim 41 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more fixed hierarchy status markers.

126. The messaging method of claim 41 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more individually customizable hierarchy status markers.

127. The messaging method of claim 41 wherein said message is classified based on severity level, wherein said severity level is customizable.

128. The messaging method of claim 41 wherein said message is classified based on urgency level, wherein said urgency level is customizable.

129. The messaging method of claim 41 wherein the encryption algorithm is selectable.

130. The non-transitory computer usable medium of claim 41 wherein the military grade encryption algorithm is selected from 64-bit, 128 bit, 256 bit, 512 bit, 1024 bit, 2048 bit, and 4096 bit.

131. The messaging method of claim 41 wherein said message is secured at the target interface through software to prevent message reproduction.

132. The messaging method of claim 41 wherein target system interface availability is determined by ancillary polling.

133. The messaging method of claim 41 wherein the response time value associated with each leg of the hierarchical message transmission thread may be individually set.

134. The messaging method of claim 41 wherein said message is “fire and forget” wherein once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified.

135. The messaging method of claim 41 wherein said message host and file server are geographically diverse.

136. The messaging method of claim 41 wherein said target message system anticipates an incoming message and queues the target system for an activation message to process the incoming message.

137. The messaging method of claim 41 wherein multiple target message systems simultaneously anticipate an incoming message and queues the target systems for an activation message to process the incoming message.

138. The messaging method of claim 41 wherein said message routing is based on calendar information selected from time of the day, day of the week, seasonal events, holidays, vacations schedules, meetings, and appointments.

139. The messaging method of claim 41 wherein said message routing is determined by a decision matrix with the inputs selected from calendars, external-real-time events and programmable logic unit inputs.

140. The messaging method of claim 41 wherein an Anonymous Interrogator of message Scanner real-time scans messages for behavior, pre-determined words and pre-determined phrases to identify a potential threat and threat location within the message system.

141. The non-transitory computer usable medium of claim 61 wherein the human interface is selected from visual, audible, speech, and tactile.

142. The non-transitory computer usable medium of claim 61 wherein the messaging processor host is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

143. The non-transitory computer usable medium of claim 61 wherein the source is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

144. The non-transitory computer usable medium of claim 61 wherein the target is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

145. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more fixed hierarchy status markers.

146. The non-transitory computer usable medium of claim 61 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more individually customizable hierarchy status markers.

147. The non-transitory computer usable medium of claim 61 wherein said message is classified based on severity level, wherein said severity level is customizable.

148. The non-transitory computer usable medium of claim 61 wherein said message is classified based on urgency level, wherein said urgency level is customizable.

149. The non-transitory computer usable medium of claim 61 wherein the encryption algorithm is selectable.

150. The non-transitory computer usable medium of claim 61 wherein the military grade encryption algorithm is selected from 64-bit, 128 bit, 256 bit, 512 bit, 1024 bit, 2048 bit, and 4096 bit.

151. The non-transitory computer usable medium of claim 61 wherein said message is secured at the target interface through software to prevent message reproduction.

152. The non-transitory computer usable medium of claim 61 wherein target system interface availability is determined by ancillary polling.

153. The non-transitory computer usable medium of claim 61 wherein the response time value associated with each leg of the hierarchical message transmission thread may be individually set.

154. The non-transitory computer usable medium of claim 61 wherein said message is “fire and forget” wherein once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified.

155. The non-transitory computer usable medium of claim 61 wherein said message host and file server are geographically diverse.

156. The non-transitory computer usable medium of claim 61 wherein said target message system anticipates an incoming message and queues the target system for an activation message to process the incoming message.

157. The non-transitory computer usable medium of claim 61 wherein multiple target message systems simultaneously anticipate an incoming message and queues the target systems for an activation message to process the incoming message.

158. The non-transitory computer usable medium of claim 61 wherein said message routing is based on calendar information selected from time of the day, day of the week, seasonal events, holidays, vacations schedules, meetings, and appointments.

159. The non-transitory computer usable medium of claim 61 wherein said message routing is determined by a decision matrix with the inputs selected from calendars, external-real-time events and programmable logic unit inputs.

160. The non-transitory computer usable medium of claim 61 wherein an Anonymous Interrogator of message Scanner real-time scans messages for behavior, pre-determined words and pre-determined phrases to identify a potential threat and threat location within the message system.

161. A messaging system comprising:

(a) a communications server having—

1) a message database;

2) a message file server;

3) a message host process operating on said file server; and

4) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said message host process;

(b) a remote source message system interface stored in memory for data entry and generation of messages on the communication server;

(c) source messaging client process residing on the communication server and monitoring status of acceptance/reading by target;

(d) a non-transitory computer readable medium in communication with a processor executing computer instructions to perform said source messaging client process;

(e) a remote target messaging system interface stored in memory for receiving, displaying and replying to said message;

(f) target messaging client process residing on the communication server; and

(g) non-transitory computer readable medium in communication with a processor executing computer instructions to perform said target messaging client process;

wherein,

said source messaging client process receives the messages and message severity/urgency classifications from a source user via said source messaging system;

said source messaging system transmits said messages and said message severity/urgency classifications to said message host process for storage on said message database via said message file server;

said message host process transmits said message and said message severity/urgency classification to said target system interface via a communications medium for display by said target system interface under control of said target message process;

said target message process responds to said message host process if said message is examined on said target system interface by a target user;

said message host process initiating a dead man messaging method that waits a predetermined amount of time for said response to said message by said target user and if said predetermined time is exceeded, said message is updated and forwarded to another target system interface for inspection by another target user;

said message host process initiating a dead man messaging method that monitors the communication between remote target messaging system and the message host and if monitoring detects a loss in communication, said message is updated and forwarded to another target system interface for inspection by another target user;

said message host process monitors availability conditions of said remote target messaging system to detect if said remote target messaging system is logged on, said remote target messaging system has been logged off for non-use; and if there is an anomaly with said remote target messaging system; and

said message host process reports to said source message process the status of said message to each of said target systems

with said messaging system utilizing a processor to perform the steps of:

(1) logging onto the communication server by a message originator through the message entry interface

(2) entering data into a message entry interface by a message originator and creating a message within the communication server;

(3) entering a message severity/urgency classification data from said messaging source interface for message residing on communications server;

(4) transmitting said message said message severity/urgency classification to said message host and storing the message on said message database via said communications server;

(5) detecting said remote target messaging system availability through polling of the said hierarchical target message thread and if so, proceeding to step (7);

(6) modifying said hierarchical target message thread removing said remote target messaging system if unavailable and proceeding to step (4);

(7) traversing a hierarchical target message thread to determine the targets for said message;

(8) selecting the next message target within said hierarchical message thread;

(9) determining if said hierarchical message thread is exhausted, and if so, proceeding to step (14);

(10) transmitting said message within the communications server to the currently selected remote target system interface within said hierarchical message thread;

(11) determining if said message has been read by said currently selected remote target system interface within said hierarchical message thread, and if so, proceeding to step (15);

(12) determining if a target response timer has expired, and if not, proceeding to said step (11);

(13) determining if a remote target messaging system is in communication with a message host and if so, proceeding to said step (8);

(14) transmitting said message to said currently selected remote target system interface within said hierarchical message thread;

(15) reporting to said source messaging interface that message reception has failed and proceeding to said step (8);

(16) reporting to said source messaging interface that said message has been received and returning any optional user comment; and

(17) optionally entering comments on said message and/or passing through said message to said current or another hierarchical message thread.

162. The non-transitory computer usable medium of claim 161 wherein the human interface is selected from visual, audible, speech, and tactile.

163. The non-transitory computer usable medium of claim 161 wherein the messaging processor host is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

164. The non-transitory computer usable medium of claim 161 wherein the source is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

165. The non-transitory computer usable medium of claim 161 wherein the target is selected from personal computers, file servers, mobile telephones, mobile devices, computer-operated telephones, and PLCs.

166. The non-transitory computer usable medium of claim 161 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more fixed hierarchy status markers.

167. The non-transitory computer usable medium of claim 161 wherein said message is classified based on a hierarchy level, said hierarchy level comprising one or more individually customizable hierarchy status markers.

168. The non-transitory computer usable medium of claim 161 wherein said message is classified based on severity level, wherein said severity level is customizable.

169. The non-transitory computer usable medium of claim 161 wherein said message is classified based on urgency level, wherein said urgency level is customizable.

170. The non-transitory computer usable medium of claim 161 wherein the encryption algorithm is selectable.

171. The non-transitory computer usable medium of claim 161 wherein the military grade encryption algorithm is selected from 64-bit, 128 bit, 256 bit, 512 bit, 1024, 2048, and 4096.

172. The non-transitory computer usable medium of claim 161 wherein said message is secured at the target interface through software to prevent message reproduction.

173. The non-transitory computer usable medium of claim 161 wherein target system interface availability is determined by ancillary polling.

174. The non-transitory computer usable medium of claim 161 wherein the response time value associated with each leg of the hierarchical message transmission thread may be individually set.

175. The non-transitory computer usable medium of claim 161 wherein said message is “fire and forget” wherein once a message is transmitted, its content cannot be modified and its target destination delivery hierarchy cannot be modified.

176. The non-transitory computer usable medium of claim 161 wherein said message host and file server are geographically diverse.

177. The non-transitory computer usable medium of claim 161 wherein said target message system anticipates an incoming message and queues the target system for an activation message to process the incoming message.

178. The non-transitory computer usable medium of claim 161 wherein multiple target message systems simultaneously anticipate an incoming message and queues the target systems for an activation message to process the incoming message.

179. The non-transitory computer usable medium of claim 161 wherein said message routing is based on calendar information selected from time of the day, day of the week, seasonal events, holidays, vacations schedules, meetings, and appointments.

180. The non-transitory computer usable medium of claim 81 wherein said message routing is determined by a decision matrix with the inputs selected from calendars, external-real-time events and programmable logic unit inputs.

181. The non-transitory computer usable medium of claim 161 wherein an Anonymous Interrogator of message Scanner real-time scans Anonymous messages for behavior, pre-determined words and pre-determined phrases to identify a potential threat and threat location within the message system.