Patent Publication Number: US-2019197444-A1

Title: Multi-dimensional Situational Awareness and Risk Mitigation Apparatuses, Methods and Systems

Description:
OTHER APPLICATIONS 
     Applications of interest include: U.S. patent application Ser. No. 13/051,458, filed Mar. 18, 2011, entitled “Method For Assessing And Communicating Organizational Human Error Risk And Its Causes”, (attorney docket no. Presage0001US1). 
     The entire contents of the aforementioned applications are herein expressly incorporated by reference. 
    
    
     This application for letters patent disclosure document describes inventive aspects that include various novel innovations (hereinafter “disclosure”) and contains material that is subject to copyright, mask work, and/or other intellectual property protection. The respective owners of such intellectual property have no objection to the facsimile reproduction of the disclosure by anyone as it appears in published Patent Office file/records, but otherwise reserve all rights. 
     PRIORITY CLAIM 
     Applicant hereby claims benefit to priority under 35 USC § 119 to Canadian patent application serial no. 2,986,519, filed Nov. 23, 2017, entitled “Computer-Implemented Probability Assessment Tool, System and Method”, (attorney docket no Presage0002CA). 
     The entire contents of the aforementioned applications are herein expressly incorporated by reference. 
     FIELD 
     The present innovations generally address risk mitigation situational awareness alerts, and more particularly, include Multi-dimensional Situational Awareness and Risk Mitigation Apparatuses, Methods and Systems. 
     However, in order to develop a reader&#39;s understanding of the innovations, disclosures have been compiled into a single description to illustrate and clarify how aspects of these innovations operate independently, interoperate as between individual innovations, and/or cooperate collectively. The application goes on to further describe the interrelations and synergies as between the various innovations; all of which is to further compliance with 35 U.S.C. § 112. 
     BACKGROUND 
     Computer systems user interfaces like Apple&#39;s macOS and iOS allow for the presentation of computer information on both desktop and mobile devices. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Appendices and/or drawings illustrating various, non-limiting, example, innovative aspects of the Multi-dimensional Situational Awareness and Risk Mitigation Apparatuses, Methods and Systems (hereinafter “MdSARM”) disclosure, include: 
         FIG. 1  shows an architecture for situational awareness for MdSARM; 
         FIG. 2  shows a datagraph illustrating data flow(s) for the MdSARM; 
         FIG. 3  shows a screenshot illustrating user interface(s) of the MdSARM; 
         FIG. 4  shows a screenshot illustrating dashboard user interface(s) of the MdSARM; 
         FIG. 5  shows a screenshot illustrating heatmap user interface(s) of the MdSARM; 
         FIG. 6  shows a screenshot illustrating isolationist mapping user interface(s) of the MdSARM; 
         FIG. 7  shows a block diagram illustrating embodiments of a MdSARM controller. 
     
    
    
     Generally, the leading number of each citation number within the drawings indicates the figure in which that citation number is introduced and/or detailed. As such, a detailed discussion of citation number  101  would be found and/or introduced in  FIG. 1 . Citation number  201  is introduced in  FIG. 2 , etc. Any citations and/or reference numbers are not necessarily sequences but rather just example orders that may be rearranged and other orders are contemplated. Citation number suffixes may indicate that an earlier introduced item has been re-referenced in the context of a later figure and may indicate the same item, evolved/modified version of the earlier introduced item, etc., e.g., server  199  of  FIG. 1  may be a similar server  299  of  FIG. 2  in the same and/or new context. 
     DETAILED DESCRIPTION 
     The Multi-dimensional Situational Awareness and Risk Mitigation Apparatuses, Methods and Systems (hereinafter “MdSARM”) transforms survey, situational atmospheric (e.g., gps, camera, audio, time, etc.) inputs, via MdSARM components (e.g., survey ( 741 ), risk mitigation ( 742 ), UI situational awareness enqueue ( 743 ), augmented reality ( 744 ), etc. components), into situational risk awareness notices, situational prevention warnings, augmented reality situational risk awareness overlays outputs. The MdSARM components, in various embodiments, implement advantageous features asset forth below. 
     Introduction 
     The MdSARM provides unconventional features (e.g., identification risks based on correlation of survey results by searching risk database with correlated survey results over a specified threshold, search of identified risks in a mitigation strategy database, and provision of matching mitigation strategies specific to identified risks in a user interface, including augmented reality situational and preventative display) that were never before available in risk mitigation situational awareness alerts (e.g., upon receiving survey responses from an air traffic controller and performing analysis, MdSARM may provide notices to the employee and employers for preventative vacation, break time notices and warnings that may be in the form of texts, emails, system notifications and overlays on the employee/employer work screens, and/or on an augmented reality overlay. 
     The embodiments of the present invention relate to a multi-dimensional profiling methodology for measuring, evaluating and mitigating risk associated with degraded situational awareness within an organization. 
     The relationship between situational awareness and risk has been recognized by high complex operating environment organizations for many years, especially in the military and aviation. Over time, the application of situational awareness has expanded to include other complex decision making environments and processes as a means to mitigate serious consequences created by their operation. 
     Dr. Mica Endsley&#39;s widely accepted definition of ‘situational awareness’ states that it is “the perception of elements in the environment within a volume of time and space, the comprehension of their meaning, and the projection of their status in the near future.” In other words, situational Awareness involves being aware of what is happening around you to understand how information, events, and your own actions will impact your goals and objectives, both now and in the near future. See  FIG. 1  regarding Mica Endsley&#39;s Situation Awareness Levels 1. 
     Traditional situational awareness models require that a person, or a group of people, assess and become aware of relevant factors in their current environment, consider any implications of these factors and foresee future consequences. The primary factor in such an assessment is data about prior incident and accidents. Looking back on past incident or accident investigations often confirm that events could have been prevented or hazards could have been identified, prior to working in the area, had the work plan included situational awareness. However, incident theory research has shown that past accident ratios are poor predictors of the future escalation of events. 
     Situational awareness could be viewed as a multi-variate vector that could be quantified and analyzed using statistical techniques. 
     In its preferred forms, this invention can be applied to organizational risk management; quantifying situational awareness within organizations at its component variables levels, and then using a computer system to apply statistical methodology to identify, report, and mitigate organizational risk of accident due to degraded situational awareness. 
     The method and system substantially improves an organization&#39;s risk management capability by augmenting and complimenting traditional methods that only use historical data as predictors of future risk. By conducting quantitative situational awareness assessments of the of the current working conditions in the workplace, the system can identify future potential deviations from approved workplace standards and result in much improve risk mitigation. By quantifying situational awareness into a vector of variables, patterns in the underlying data can be identified to better understand an organization, predict future risk events, and suggest mitigation actions. 
     Embodied within the computer system, the invention of a multi-variate measure of situational awareness provides a multi-dimensional view of situational awareness, wherein clusters within the underlying data represent behavior risk profiles. The system uses a factor analysis (e.g., see  FIG. 3  (Multivariate Analysis of Situational Awareness Component Variables)) that groups or clusters employees together based upon their similar pattern of situational awareness measures. This similarity defines the unique psychological make-up of this group that puts them at risk of accidents and incidents. Each segmentation defines the distinct and separate psychological characteristics that put certain employee groups at risk, and as a result enables more targeted and effective mitigation strategies. 
     Examples of incidents arising from a lack of situational awareness would include an aborted landing due to misdirected aircraft on a runway, a collapse of poorly constructed scaffolding material in a construction worksite, or tools that were left in a position where they could easily fall if disturbed. Also see  FIG. 2  for an overview. 
     The embodiments of the present invention relate to a multi-dimensional computer-enabled behavioral risk profiling methodology for measuring, predicting and mitigating risk associated with degraded situational awareness within an organization. 
     The system employs empirical data for measuring situational awareness at an organizational level, and then using factor analysis and machine learning to predict the associated behavioral risk levels and types for an organization, and the most likely successful mitigation strategies. 
     The behavioral risk profiling system employs a survey design stage, a data query stage, a risk profiling stage, and a mitigation stage. 
     During the survey design stage, a survey model optimized for a given organization is generated. During the data query stage, empirical data is collected and manipulated in preparation for the risk profiling stage. During the behavioral risk profiling stage, the empirical data generated during the query stage is correlated against known behavioral risk profiles to generate predicted risk levels and types, which are then are communicated. During the mitigation stage, the generated risk profiles and levels combined with the organization type are correlated with known mitigation best practices and suggested actions are communicated. 
     The behavioral risk profiling system employs empirical data and machine learning during the survey design stage. The inputs required for the survey are not constant. The system finds that the inquires most effective at revealing underlying situational awareness factors vary depending in industry and internal organizational factors. A survey is generated from collected organizational information including, but not limited to client questions, industry profile, organizational profile, and prior survey results for the organization. The survey asks a series of questions that can be numerically answered. For instance, the survey may ask “are you aware of any incident or accidents in the last 30 days that were not reported?” The user provides answers along a numerical scale of 1 to 7, where the higher response indicates the higher agreement. 
     The behavioral risk profiling system employs internet-enabled devices, empirical data, factor analysis, and machine learning to collect, manipulate and store the results of the survey. The survey is deployed to users and completed by means for an internet-enabled device with secure access to the risk profiling system. The survey answers provided by the user are stored in the empirical database. 
     The behavioral risk profiling system uses factor analysis and machine learning to manipulate the survey results into a correlation matrix comprised of known constructs of situational awareness. The correlation matrix is analyzed to identify combinations of variables that are known to be associated with types of organizational risk. The system compares the constructs to the empirical database to generate an organizational risk profile including an overall risk index score, a safety awareness breakdown, a 3 cluster score, and a prediction of the population at high risk, the number of likely incidents, and the likely types of incidents. 
     The Behavioral Risk Profile depicts the unique scoring patterns or profiles within the organization that share common behavioral characteristics. As such, the system provides insight into the various “personalities” in the organization, as well as allowing for comparisons across all nine of the constructs or within a single construct. 
     The risk profile system generates an organizational risk profile report comprised of visual dashboard ( FIG. 4 ), a heat map ( FIG. 5 ), and a detailed organizational behavioral profile ( FIG. 6 ). 
     If the correlation matrix does not yield sufficient confidence against any of the known organizational profiles (clusters) , the risk profiling system generates a new organizational risk profile and stores the resultant profile in the risk profile database. The parameters and descriptors of this newly generated risk profile (cluster) are generated by using machine learning to reanalyze all previously stored profile data with the newly identified cluster as a new data vector. The result is a new risk profile that will be optimized on a go-forward basis. 
     Once a risk profile has been identified for an organization, the risk profiling system uses machine learning and factor analysis to compare the generated organizational risk profile to mitigation strategies known to improve situational awareness. The system compares the risk profile to the empirical database to generate suggested mitigation actions (e.g., as depicted in  FIG. 2 ). 
     MdSARM 
       FIG. 1  shows an architecture for situational awareness for MdSARM. 
       FIG. 2  shows a datagraph illustrating data flow(s) for the MdSARM. 
       FIG. 3  shows a screenshot illustrating user interface(s) of the MdSARM. 
       FIG. 4  shows a screenshot illustrating dashboard user interface(s) of the MdSARM. 
       FIG. 5  shows a screenshot illustrating heatmap user interface(s) of the MdSARM. 
       FIG. 6  shows a screenshot illustrating isolationist mapping user interface(s) of the MdSARM. 
     MdSARM Controller 
       FIG. 7  shows a block diagram illustrating embodiments of a MdSARM controller. In this embodiment, the MdSARM controller  701  may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through risk mitigation situational awareness alerts technologies, and/or other related data. 
     Users, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors  703  may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to allow various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory  729  (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components. 
     In one embodiment, the MdSARM controller  701  may be connected to and/or communicate with entities such as, but not limited to: one or more users from peripheral devices  712  (e.g., user input devices  711 ); an optional cryptographic processor device  728 ; and/or a communications network  713 . 
     Networks comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term “server” as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.” The term “client” as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is referred to as a “node.” Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is called a “router.” There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is, generally, an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another. 
     The MdSARM controller  701  may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization  702  connected to memory  729 . 
     Computer Systemization 
     A computer systemization  702  may comprise a clock  730 , central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary))  703 , a memory  729  (e.g., a read only memory (ROM)  706 , a random access memory (RAM)  705 , etc.), and/or an interface bus  707 , and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus  704  on one or more (mother)board(s)  702  having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc. The computer systemization may be connected to a power source  786 ; e.g., optionally the power source may be internal. Optionally, a cryptographic processor  726  may be connected to the system bus. In another embodiment, the cryptographic processor, transceivers (e.g., ICs)  774 , and/or sensor array (e.g., accelerometer, altimeter, ambient light, barometer, global positioning system (GPS) (thereby allowing MdSARM controller to determine its location), gyroscope, magnetometer, pedometer, proximity, ultra-violet sensor, etc.)  773  may be connected as either internal and/or external peripheral devices  712  via the interface bus I/O  708  (not pictured) and/or directly via the interface bus  707 . In turn, the transceivers may be connected to antenna(s)  775 , thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to various transceiver chipsets (depending on deployment needs), including: Broadcom® BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.); a Broadcom® BCM4752 GPS receiver with accelerometer, altimeter, GPS, gyroscope, magnetometer; a Broadcom® BCM4335 transceiver chip (e.g., providing 2G, 3G, and 4G long-term evolution (LTE) cellular communications; 802.11ac, Bluetooth 4.0 low energy (LE) (e.g., beacon features)); a Broadcom® BCM43341 transceiver chip (e.g., providing 2G, 3G and 4G LTE cellular communications; 802.11 g/, Bluetooth 4.0, near field communication (NFC), FM radio); an Infineon Technologies® X-Gold 618-PMB9800 transceiver chip (e.g., providing 2G/3G HSDPA/HSUPA communications); a MediaTek® MT6620 transceiver chip (e.g., providing 802.11a/ac/b/g/n, Bluetooth 4.0 LE, FM, GPS; a Lapis Semiconductor® ML8511 UV sensor; a maxim integrated MAX44000 ambient light and infrared proximity sensor; a Texas Instruments® WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, GPS); and/or the like. The system clock may have a crystal oscillator and generates a base signal through the computer systemization&#39;s circuit pathways. The clock may be coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. It should be understood that in alternative embodiments, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems. 
     The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. The CPU is often packaged in a number of formats varying from large supercomputer(s) and mainframe(s) computers, down to mini computers, servers, desktop computers, laptops, thin clients (e.g., Chromebooks®), netbooks, tablets (e.g., Android®, iPads®, and Windows® tablets, etc.), mobile smartphones (e.g., Android®, iPhones®, Nokia®, Palm® and Windows® phones, etc.), wearable device(s) (e.g., watches, glasses, goggles (e.g., Google Glass), etc.), and/or the like. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory  729  beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD&#39;s Athlon®, Duron® and/or Opteron®; Apple&#39;s® A series of processors (e.g., A 5 , A 6 , A 7 , A 8 , etc.); ARM&#39;s® application, embedded and secure processors; IBM® and/or Motorola&#39;s DragonBall® and PowerPC®; IBM&#39;s® and Sony&#39;s® Cell processor; Intel&#39;s® 80X86 series (e.g., 80386, 80486), Pentium®, Celeron®, Core (2) Duo®, i series (e.g., i3, i5, i7, etc.), Itanium®, Xeon®, and/or XScale®; Motorola&#39;s® 680X0 series (e.g., 68020, 68030, 68040, etc.); and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to various data processing techniques. Such instruction passing facilitates communication within the MdSARM controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., see Distributed MdSARM below), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller mobile devices (e.g., Personal Digital Assistants (PDAs)) may be employed. 
     Depending on the particular implementation, features of the MdSARM may be achieved by implementing a microcontroller such as CAST&#39;s® R8051XC2 microcontroller; Intel&#39;s® MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the MdSARM, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology. For example, any of the MdSARM component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the MdSARM may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing. 
     Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, MdSARM features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex® series and/or the low cost Spartan® series manufactured by Xilinx®. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the MdSARM features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the MdSARM system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGA&#39;s logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the MdSARM may be developed on FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate MdSARM controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the MdSARM. 
     Power Source 
     The power source  786  may be of any various form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell  786  is connected to at least one of the interconnected subsequent components of the MdSARM thereby providing an electric current to all subsequent components. In one example, the power source  786  is connected to the system bus component  704 . In an alternative embodiment, an outside power source  786  is provided through a connection across the I/O  708  interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power. 
     Interface Adapters 
     Interface bus(ses)  707  may accept, connect, and/or communicate to a number of interface adapters, variously although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O)  708 , storage interfaces  709 , network interfaces  710 , and/or the like. Optionally, cryptographic processor interfaces  727  similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters variously connect to the interface bus via a slot architecture. Various slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like. 
     Storage interfaces  709  may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices  714 , removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like. 
     Network interfaces  710  may accept, communicate, and/or connect to a communications network  713 . Through a communications network  713 , the MdSARM controller is accessible through remote clients  733 b (e.g., computers with web browsers) by users  733 a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair  10 / 100 / 1000 / 10000  Base T, and/or the like), Token Ring, wireless connection such as IEEE  802 . 11 a-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., see Distributed MdSARM below), architectures may similarly be employed to pool, load balance, and/or otherwise decrease/increase the communicative bandwidth required by the MdSARM controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; Interplanetary Internet (e.g., Coherent File Distribution Protocol (CFDP), Space Communications Protocol Specifications (SCPS), etc.); a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a cellular, WiFi, Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces  710  may be used to engage with various communications network types  713 . For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks. 
     Input Output interfaces (I/O)  708  may accept, communicate, and/or connect to user, peripheral devices  712  (e.g., input devices  711 ), cryptographic processor devices  728 , and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; touch interfaces: capacitive, optical, resistive, etc. displays; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), (mini) displayport, high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/ac/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One output device may include a video display, which may comprise a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. The video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.). 
     Peripheral devices  712  may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the MdSARM controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., gesture (e.g., Microsoft Kinect) detection, motion detection, still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices  528 ), force-feedback devices (e.g., vibrating motors), infrared (IR) transceiver, network interfaces, printers, scanners, sensors/sensor arrays and peripheral extensions (e.g., ambient light, GPS, gyroscopes, proximity, temperature, etc.), storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras). 
     User input devices  711  often are a type of peripheral device  512  (see above) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, security/biometric devices (e.g., fingerprint reader, iris reader, retina reader, etc.), touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, styluses, and/or the like. 
     It should be noted that although user input devices and peripheral devices may be employed, the MdSARM controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection. 
     Cryptographic units such as, but not limited to, microcontrollers, processors  726 , interfaces  727 , and/or devices  728  may be attached, and/or communicate with the MdSARM controller. A MC68HC16 microcontroller, manufactured by Motorola, Inc.®, may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used. Other specialized cryptographic processors include: Broadcom&#39;s® CryptoNetX and other Security Processors; nCipher&#39;s® nShield; SafeNef s® Luna PCI (e.g., 7100) series; Semaphore Communications&#39;® 40 MHz Roadrunner 184; Sun&#39;s® Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano® Processor (e.g., L2100, L2200, U2400) line, which is capable of performing  500 +MB/s of cryptographic instructions; VLSI Technology&#39;s® 33 MHz 6868; and/or the like. 
     Memory 
     Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory  729 . However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the MdSARM controller and/or a computer systemization may employ various forms of memory  729 . For example, a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation. In one configuration, memory  729  will include ROM  706 , RAM  705 , and a storage device  714 . A storage device  714  may be any various computer system storage. Storage devices may include: an array of devices (e.g., Redundant Array of Independent Disks (RAID)); a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); RAM drives; solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory. 
     Component Collection 
     The memory  729  may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s)  715  (operating system); information server component(s)  716  (information server); user interface component(s)  717  (user interface); Web browser component(s)  718  (Web browser); database(s)  719 ; mail server component(s)  721 ; mail client component(s)  722 ; cryptographic server component(s)  720  (cryptographic server); the MdSARM component(s)  735 ; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although unconventional program components such as those in the component collection may be stored in a local storage device  714 , they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like. 
     Operating System 
     The operating system component  715  is an executable program component facilitating the operation of the MdSARM controller. The operating system may facilitate access of I/O, network interfaces, peripheral devices, storage devices, and/or the like. The operating system may be a highly fault tolerant, scalable, and secure system such as: Apple&#39;s Macintosh OS X (Server) and macOS®; AT&amp;T Plan 9®; Be OS®; Blackberry&#39;s QNX®; Google&#39;s Chrome®; Microsoft&#39;s Windows® 7/8/10; Unix and Unix-like system distributions (such as AT&amp;T&#39;s UNIX®; Berkley Software Distribution (BSD)® variations such as FreeBSD®, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS® (i.e., versions 1-9), IBM OS/2®, Microsoft DOS®, Microsoft Windows 2000/2003/3.1/95/98/CE/Millenium/Mobile/NT/Vista/XP (Server)®, Palm OS®, and/or the like. Additionally, for robust mobile deployment applications, mobile operating systems may be used, such as: Apple&#39;s iOS®; China Operating System COS®; Google&#39;s Android®; Microsoft Windows RT/Phone®; Palm&#39;s WebOS®; Samsung/Intel&#39;s Tizen®; and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the MdSARM controller to communicate with other entities through a communications network  713 . Various communication protocols may be used by the MdSARM controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like. 
     Information Server 
     An information server component  716  is a stored program component that is executed by a CPU. The information server may be a an Internet information server such as, but not limited to Apache Software Foundation&#39;s Apache, Microsoft&#39;s Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects®, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM)®, Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger® Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force&#39;s® (IETF&#39;s) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber® or Open Mobile Alliance&#39;s (OMA&#39;s) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger® Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the MdSARM controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.” Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port  21 , and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the MdSARM database  719 , operating systems, other program components, user interfaces, Web browsers, and/or the like. 
     Access to the MdSARM database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the MdSARM. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the MdSARM as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser. 
     Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. 
     User Interface 
     Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as buttons, check boxes, cursors, menus, scrollers, and windows (collectively referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are called user interfaces. Graphical user interfaces (GUIs) such as the Apple&#39;s iOS®, Macintosh Operating System&#39;s Aqua®; IBM&#39;s OS/2®; Google&#39;s Chrome® (e.g., and other webbrowser/cloud based client OSs); Microsoft&#39;s Windows® varied UIs 2000/2003/3.1/95/98/CE/Millenium/Mobile/NT/Vista/XP (Server) (i.e., Aero, Surface, etc.); Unix&#39;s X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface®, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users. 
     A user interface component  717  is a stored program component that is executed by a CPU. The user interface may be a graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. 
     Web Browser 
     A Web browser component  718  is a stored program component that is executed by a CPU. The Web browser may be a hypertext viewing application such as Apple&#39;s (mobile) Safari®, Google&#39;s Chrome®, Microsoft Internet Explorer®, Mozilla&#39;s Firefox®, Netscape Navigator®, and/or the like. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox®, Safari® Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the MdSARM enabled nodes. The combined application may be nugatory on systems employing Web browsers. 
     Mail Server 
     A mail server component  721  is a stored program component that is executed by a CPU  703 . The mail server may be an Internet mail server such as, but not limited to: dovecot, Courier IMAP, Cyrus IMAP, Maildir, Microsoft Exchange, sendmail, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects®, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the MdSARM. Alternatively, the mail server component may be distributed out to mail service providing entities such as Google&#39;s® cloud services (e.g., Gmail and notifications may alternatively be provided via messenger services such as AOL&#39;s Instant Messenger®, Apple&#39;s iMessage®, Google Messenger®, SnapChat®, etc.). 
     Access to the MdSARM mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system. 
     Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. 
     Mail Client 
     A mail client component  722  is a stored program component that is executed by a CPU  703 . The mail client may be a mail viewing application such as Apple Mail®, Microsoft Entourage®, Microsoft Outlook®, Microsoft Outlook Express®, Mozilla®, Thunderbird®, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages. 
     Cryptographic Server 
     A cryptographic server component  720  is a stored program component that is executed by a CPU  703 , cryptographic processor  726 , cryptographic processor interface  727 , cryptographic processor device  728 , and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest  5  (MD 5 , which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), Transport Layer Security (TLS), and/or the like. Employing such encryption security protocols, the MdSARM may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to allow the MdSARM component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the MdSARM and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. 
     The MdSARM Database 
     The MdSARM database component  719  may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a fault tolerant, relational, scalable, secure database such as MySQL®, Oracle®, Sybase®, etc. may be used. Additionally, optimized fast memory and distributed databases such as IBM&#39;s Netezza®, MongoDB&#39;s MongoDB®, opensource Hadoop®, opensource VoltDB, SAP&#39;s Hana®, etc. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. Alternative key fields may be used from any of the fields having unique value sets, and in some alternatives, even non-unique values in combinations with other fields. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship. 
     Alternatively, the MdSARM database may be implemented using various other data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier™, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the MdSARM database is implemented as a data-structure, the use of the MdSARM database  719  may be integrated into another component such as the MdSARM component  735 . Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations (e.g., see Distributed MdSARM below). Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated. 
     In one embodiment, the database component  719  includes several tables  719   a - z:    
     An accounts table  719   a  includes fields such as, but not limited to: an accountID, accountOwnerID, accountContactID, asseaDs, deviceIDs, paymentIDs, transactionIDs, userIDs, accountType (e.g., agent, entity (e.g., corporate, non-profit, partnership, etc.), individual, etc.), accountCreationDate, accountUpdateDate, accountName, accountNumber, routingNumber, linkWalletsID, accountPrioritAccaountRatio, accountAddress, accountState, accountZlPcode, accountCountry, accountEmail, accountPhone, accountAuthKey, accountIPaddres s, accountURLAcces s Code, accountPortNo, accountAuthorizationCode, accountAcces sPrivileges, accountPreferences, accoun tRe striction s, and/or the like; 
     A users table  719   b  includes fields such as, but not limited to: a userID, userSSN, taxID, userContactID, accountID, assetIDs, deviceIDs, paymentIDs, transactionIDs, userType (e.g., agent, entity (e.g., corporate, non-profit, partnership, etc.), individual, etc.), namePrefix, firstName, middleName, lastName, nameSuffix, DateOfBirth, userAge, userName, userEmail, userSocialAccountID, contactType, contactRelationship, userPhone, userAddress, userCity, userState, userZlPCode, userCountry, userAuthorizationCode, userAccessPrivilges, userPreferences, userRes trictions, and/or the like (the user table may support and/or track multiple entity accounts on a MdSARM); 
     An devices table  719   c  includes fields such as, but not limited to: deviceID, sensorIDs, accountID, as s etID s, paymentID s, deviceType, deviceName, deviceManufacturer, deviceModel, devic eVersion, deviceSerialNo, deviceIPaddres s, deviceMACaddres s, device_ECID, deviceUUID, deviceLocation, deviceCertificate, deviceOS, appIDs, deviceResources, deviceSession, authKey, deviceSecureKey, walletAppInstalledFlag, deviceAccessPrivileges, devicePreferences, deviceRestrictions, hardware_config, software_config, storage_location, sensor_value, pin_reading, data_length, channel_requirement, sensor_name, sensor_model_no, sensor_manufacturer, sensor_typ e, sensor_serial_number, sensor_power_requirement, device_power_requirement, location, sensor_associated_tool, sensor_dimensions, device_dimensions, sensor_communications —  type, device_communications —  type, power_percentage, power_condition, temperature_setting, speed_adjust, hold_duration, part_actuation, and/or the like. Device table may, in some embodiments, include fields corresponding to one or more Bluetooth profiles, such as those published at https://www.bluetooth.org/en-us/specification/adopted-specifications, and/or other device specifications, and/or the like; 
     An apps table  719   d  includes fields such as, but not limited to: appID, appName, appType, appDependencies, accountID, deviceIDs, transactionID, userID, appStoreAuthKey, appStoreAccountID, appStoreIPaddress, appStoreURLaccess Code, app StorePortNo, appAccessPrivileges, appPreferences, app Restrictions, portNum, access_API_call, linked_wallets_list, and/or the like; 
     An assets table  719   e  includes fields such as, but not limited to: assetID, accountID, userID, distributorAccountID, distributorPaymentID, distributorOnwerID, assetOwnerID, assetType, assetSourceDeviceID, assetSourceDeviceType, assetSourceDeviceName, assetSourceD is tributionChannelID, assetSourceDistributionChannelType, assetSourceD is tributionChannelName, assetTargetChannelID, assetTargetChannelType, assetTargetChannelName, assetName, assetSeriesName, assetSeries Season, assetSeriesEpisode, assetCode, assetQuantity, assetCost, assetPrice, assetValue, assetManufactuer, assetModelNo, assetSerialNo, assetLocation, assetAddres s, assetState, assetZIPcode, assetState, assetCountry, assetEmail, assetIPaddres s, assetURLaccessCode, assetOwnerAccountID, sub scriptionIDs, assetAuthroizationCode, assetAcces sPrivileges, assetPreferences, assetRestrictions, assetAPI, assetAPIconnectionAddress, and/or the like; 
     A payments table  719   f  includes fields such as, but not limited to: paymentID, accountID, userID, couponID, couponValue, couponConditions, couponExpiration, paymentType, paymentAccountNo, paymen tAccountName, paymentAccountAuthorizationCodes, paymentExpirationDate, paymentCCV, paymentRoutingNo, paymentRoutingType, paymentAddress, paymentState, paymentZlPcode, paymentCountry, paymentEmail, paymentAuthKey, paymentIPaddress, paymentURLaccessCode, paymentPortNo, paymentAccessPrivileges, paymentPreferences, payementRestrictions, and/or the like; 
     An transactions table  719   g  includes fields such as, but not limited to: transactionID, accountID, assetIDs, deviceIDs, paymentIDs, transactionIDs, userID, merchantID, transactionType, transactionDate, transactionTime, transactionAmount, transactionQuantity, transactionDetails, productsList, productType, productTitle, productsSummary, productParamsList, transactionNo, transactionAccessPrivileges, transactionPreferences, transactionRestrictions, merchantAuthKey, merchantAuthCode, and/or the like; 
     An merchants table  719   h  includes fields such as, but not limited to: merchantID, merchantTaxID, merchanteName, merchantContactUserID, accountID, issuerID, acquirerID, merchantEmail, merchantAddress, merchantState, merchantZIPcode, merchantCountry, merchantAuthKey, merchantIPaddress, portNum, merchantURLaccessCode, merchantPortNo, merchantAccessPrivileges, merchantPreferences, merchantRestrictions, and/or the like; 
     An ads table  719   i  includes fields such as, but not limited to: adID, advertiserID, adMerchantID, adNetworkID, adName, adTags, advertiserName, adSponsor, adTime, adGeo, adAttributes, adFormat, adProduct, adText, adMedia, adMediaID, adChannelID, adTagTime, adAudioSignature, adHash, adTemplateID, adTemplateData, adSourceID, adSourceName, adSourceServerlP, adSourceURL, adSourceSecurityProtocol, adSourceFTP, adAuthKey, adAccessPrivileges, adPreferences, adRestrictions, adNetworkXchangeID, adNetworkXchangeName, adNe tworkXchangeCost, adNe tworkXchangeMetricType (e.g., CPA, CPC, CPM, CTR, etc.), adNetworkXchangeMetricValue, adNetworkXchangeServer, adNetworkXchangePortNumber, publisherID, publisherAddress, publisherURL, publisherTag, publisherIndustry, publisherName, publisherDescription, siteDomain, siteURL, siteContent, siteTag, siteContext, sitelmpression, siteVisits, siteHeadline, sitePage, siteAdPrice, sitePlacement, sitePosition, bidID, bidExchange, bidOS, bidTarget, bidTimestamp, bidPrice, bidImpressionID, bidType, bidScore, adType (e.g., mobile, desktop, wearable, largescreen, interstitial, etc.), assetID, merchant 1 D, deviceID, userID, accountID, impressionID, impressionOS, impressionTimeStamp, impressionGeo, impressionAction, impressionType, impressionPublisherID, impressionPublisherURL, and/or the like; 
     In one embodiment, the MdSARM database may interact with other database systems. For example, employing a distributed database system, queries and data access by search MdSARM component may treat the combination of the MdSARM database, an integrated data security layer database as a single database entity (e.g., see Distributed MdSARM below). 
     In one embodiment, user programs may contain various user interface primitives, which may serve to update the MdSARM. Also, various accounts may require custom database tables depending upon the environments and the types of clients the MdSARM may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing various data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components  719   a - z.  The MdSARM may be configured to keep track of various settings, inputs, and parameters via database controllers. 
     The MdSARM database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MdSARM database communicates with the MdSARM component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data. 
     The MdSARMs 
     The MdSARM component  735  is a stored program component that is executed by a CPU. In one embodiment, the MdSARM component incorporates any and/or all combinations of the aspects of the MdSARM that was discussed in the previous figures. As such, the MdSARM affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks. The features and embodiments of the MdSARM discussed herein increase network efficiency by reducing data transfer requirements the use of more efficient data structures and mechanisms for their transfer and storage. As a consequence, more data may be transferred in less time, and latencies with regard to transactions, are also reduced. In many cases, such reduction in storage, transfer time, bandwidth requirements, latencies, etc., will reduce the capacity and structural infrastructure requirements to support the MdSARM&#39;s features and facilities, and in many cases reduce the costs, energy consumption/requirements, and extend the life of MdSARM&#39;s underlying infrastructure; this has the added benefit of making the MdSARM more reliable. Similarly, many of the features and mechanisms are designed to be easier for users to use and access, thereby broadening the audience that may enjoy/employ and exploit the feature sets of the MdSARM; such ease of use also helps to increase the reliability of the MdSARM. In addition, the feature sets include heightened security as noted via the Cryptographic components  720 ,  726 ,  728  and throughout, making access to the features and data more reliable and secure 
     The MdSARM transforms survey, situational atmospheric (e.g., gps, camera, audio, time, etc.) inputs, via MdSARM components (e.g., survey ( 741 ), risk mitigation ( 742 ), UI situational awareness enqueue ( 743 ), augmented reality ( 744 )), into situational risk awareness notices, situational prevention warnings, augmented reality situational risk awareness overlays outputs. 
     The MdSARM component enabling access of information between nodes may be developed by employing various development tools and languages such as, but not limited to: Apache® components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft&#39;s® ActiveX; Adobe® AIR, FLEX &amp; FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo!® User Interface; and/or the like), WebObjects®, and/or the like. In one embodiment, the MdSARM server employs a cryptographic server to encrypt and decrypt communications. The MdSARM component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MdSARM component communicates with the MdSARM database, operating systems, other program components, and/or the like. The MdSARM may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. 
     Distributed MdSARMs 
     The structure and/or operation of any of the MdSARM node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion. As such a combination of hardware may be distributed within a location, within a region and/or globally where logical access to a controller may be abstracted as a singular node, yet where a multitude of private, semiprivate and publically accessible node controllers (e.g., via dispersed data centers) are coordinated to serve requests (e.g., providing private cloud, semi-private cloud, and public cloud computing resources) and allowing for the serving of such requests in discrete regions (e.g., isolated, local, regional, national, global cloud access). 
     The component collection may be consolidated and/or distributed in countless variations through various data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through various data processing communication techniques. 
     The configuration of the MdSARM controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like. For example, cloud services such as Amazon Data Services®, Microsoft Azure®, Hewlett Packard Helion®, IBM® Cloud services allow for MdSARM controller and/or MdSARM component collections to be hosted in full or partially for varying degrees of scale. 
     If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other component components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RAE), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components. 
     For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.: 
         w 3 c -post http:// . . . Value1 
     where Value 1  is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value Similarly, with such a grammar, a variable “Valuel” may be inserted into an “http://” post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment. 
     For example, in some implementations, the MdSARM controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below: 
     
       
         
           
               
             
               
                   
               
             
            
               
                 &lt;?PHP 
               
               
                 header(′Content-Type: text/plain′); 
               
               
                 // set ip address and port to listen to for incoming data 
               
               
                 $address = ‘192.168.0.100 ’ ; 
               
               
                 $port = 255; 
               
               
                 // create a server-side SSL socket, listen for/accept incoming communication 
               
               
                 $sock = socket_create(AF_INET, SOCK_STREAM, 0); 
               
               
                 socket_bind($sock, $address, $port) or die(‘Could not bind to address ’ ); 
               
               
                 socket_listen($sock); 
               
               
                 $client = socket_accept($sock); 
               
               
                 // read input data from client device in 1024 byte blocks until end of message 
               
               
                 do { 
               
            
           
           
               
               
            
               
                   
                 $input = “”; 
               
               
                   
                 $input = socket_read($client, 1024); 
               
               
                   
                 $data .= $input; 
               
            
           
           
               
            
               
                 } while($input != “”); 
               
               
                 // parse data to extract variables 
               
               
                 $obj = json_decode($data, true); 
               
               
                 // store input data in a database 
               
               
                 mysql_connect(″201.408.185.132″,$DBserver,$password); // access database server 
               
               
                 mysql_select(″CLIENT_DB.SQL″); // select database to append 
               
               
                 mysql_query(“INSERT INTO UserTable (transmission) 
               
               
                 VALUES ($data)”); // add data to UserTable table in a CLIENT database 
               
               
                 mysql_close(″CLIENT_DB.SQL″); // close connection to database 
               
               
                 ?&gt; 
               
               
                   
               
            
           
         
       
     
     Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation: 
                                            http://www.xav.com/perl/site/lib/SOAP/Parser.html           http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.d           oc/referenceguide295.htm                 and other parser implementations:                         http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.d           oc/referenceguide259.htm                        
all of which are hereby expressly incorporated by reference.
 
     In order to address various issues and advance the art, the entirety of this application for Multi-dimensional Situational Awareness and Risk Mitigation Apparatuses, Methods and Systems (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices, and otherwise) shows, by way of illustration, various embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Further and to the extent any financial and/or investment examples are included, such examples are for illustrative purpose(s) only, and are not, nor should they be interpreted, as investment advice. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components, data flow order, logic flow order, and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Similarly, descriptions of embodiments disclosed throughout this disclosure, any reference to direction or orientation is merely intended for convenience of description and is not intended in any way to limit the scope of described embodiments. Relative terms such as “lower”, “upper”, “horizontal”, “vertical”, “above”, “below”, “up”, “down”, “top” and “bottom” as well as derivative thereof (e.g., “horizontally”, “downwardly”, “upwardly”, etc.) should not be construed to limit embodiments, and instead, again, are offered for convenience of description of orientation. These relative descriptors are for convenience of description only and do not require that any embodiments be constructed or operated in a particular orientation unless explicitly indicated as such. Terms such as “attached”, “affixed”, “connected”, “coupled”, “interconnected”, and similar may refer to a relationship wherein structures are secured or attached to one another either directly or indirectly through intervening structures, as well as both movable or rigid attachments or relationships, unless expressly described otherwise. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations including the right to claim such innovations, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a MdSARM individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the MdSARM, may be implemented that allow a great deal of flexibility and customization. For example, aspects of the MdSARM may be adapted for user interfaces, augmented reality, early warning systems, fatigue prevention systems. While various embodiments and discussions of the MdSARM have included risk mitigation situational awareness alerts, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.