The present invention relates generally to a dynamically adaptable rules and communication system, and more specifically to a computer-implemented method for utilizing the dynamically adaptable rules system, including interconnected rules engines and databases to automatically manage process control-based use cases, including automatically determining the applicability of those use cases to an entity.
With the advent of the internet and mass communications of data worldwide, a host of data management issues have arisen. Many entities are gaining and sharing access to an increasingly large variety of data types, including personal data, much of which may be sensitive. In addition, this is occurring among a proliferation of data privacy, security policies, export controls, etc. For example, various governments, standard bodies and other entities have instituted a large variety of laws, regulations or rules addressing and enforcing certain data management policies. As a result, it is becoming substantially more difficult to manage the use and sharing of data types while complying with a multitude of laws, regulations and rules.
Whether certain laws regulations or rules apply for a given use case depends on a variety of conditions including the type of entity, where the entity and its workers are located, the size of the entity, the type of data being accessed or shared, the location of where the data was accessed or shared, the sensitivity of the data, etc. As a result, just determining whether a certain law, regulation or rule applies is a complex and formidable task. In addition, if it is determined that a certain law, regulation of rule does not apply to a given entity, then that entity typically does not have to show compliance with that law, regulation or rule, thereby saving significant resources.
An example of mapping multiple governance, risk and compliance (GRC) mandates against each other in order to identify “common controls” is provided by the Unified Compliance Framework (UCF). UCF maintains a database of mandate “authority documents”, mandate citations, common controls and a defined terms dictionary. The UCF allows a user to input mandates of interest and to map the mandates on a one to one, one to many and many to many basis in order to produce a hierarchical list of common controls among the selected mandates. These common controls are linked to roles, assets, records, activities, events and audit questions. This list and related reports help UCF users identify overlaps among mandates, identify and remedy gaps in the user organization's GRC program and support a compliance audit program.
The illustrative embodiments of the present invention provide a method, system, and/or computer usable program product for determining applicability of a set of use cases to an entity comprising the steps of receiving a dynamic profile of an entity, the profile including attributes of that entity; receiving a dynamic set of applicability rules, each set of applicability rules corresponding to at least one of the set of use cases, for determining whether the set of use cases applies to the entity based on the attributes of that entity; applying the dynamic set of applicability rules against the dynamic entity profile to determine whether the set of use cases is applicable to the entity; upon a positive determination that the at least one of the set of use cases is applicable to the entity, notifying a managing user of the positive determination; responsive to receiving an indication that the dynamic profile of the entity has been modified, automatically repeating the step of applying the dynamic set of applicability rules against the dynamic entity profile to determine whether the set of use cases is applicable to the entity and, upon the positive determination, automatically repeating the step of notifying the managing user; and responsive to receiving an indication that the dynamic set of applicability rules has been modified, automatically repeating the step of applying the dynamic set of applicability rules against the dynamic entity profile to determine whether the set of use cases is applicable to the entity and, upon the positive determination, automatically repeating the step of notifying the managing user.
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, further objectives and advantages thereof, as well as a preferred mode of use, will best be understood by reference to the following detailed description of illustrative embodiments when read in conjunction with the accompanying drawings, wherein:
Processes and devices may be implemented and utilized for utilizing a dynamically adaptable rules and communication system to manage process control-based use cases. These processes and apparatuses may be implemented and utilized as will be explained with reference to the various embodiments below.
In data processing system 100 there is a computer system/server 112, which is operational with numerous other general purpose or special purpose computing system environments, peripherals, or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 112 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 112 may be described in the general context of computer system-performable instructions, such as program modules, being processed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 112 may be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 118 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 112 typically includes a variety of non-transitory computer system usable media. Such media may be any available media that is accessible by computer system/server 112, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 128 can include non-transitory computer system readable media in the form of volatile memory, such as random-access memory (RAM) 130 and/or cache memory 132. Computer system/server 112 may further include other non-transitory removable/non-removable, volatile/non-volatile computer system storage media. By way of example, storage system 134 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a USB interface for reading from and writing to a removable, non-volatile magnetic chip (e.g., a “flash drive”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 118 by one or more data media interfaces. Memory 128 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of the embodiments. Memory 128 may also include data that will be processed by a program product.
Program/utility 140, having a set (at least one) of program modules 142, may be stored in memory 128 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 142 generally carry out the functions and/or methodologies of the embodiments. For example, a program module may be software for utilizing a dynamically adaptable rules and communication system to manage process control-based use cases.
Computer system/server 112 may also communicate with one or more external devices 114 such as a keyboard, a pointing device, a display 124, etc.; one or more devices that enable a user to interact with computer system/server 112; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 112 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 122 through wired connections or wireless connections. Still yet, computer system/server 112 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 120. As depicted, network adapter 120 communicates with the other components of computer system/server 112 via bus 118. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 112. Examples, include, but are not limited to: microcode, device drivers, tape drives, RAID systems, redundant processing units, data archival storage systems, external disk drive arrays, etc.
Server 220 and client 240 are coupled to network 210 along with storage unit 230. In addition, laptop 250 and facility 280 (such as a home or business) are coupled to network 210 including wirelessly such as through a network router 253. A mobile device 260 such as a mobile phone may be coupled to network 210 through a cell tower 262. Data processing systems, such as server 220, client 240, laptop 250, mobile device 260 and facility 280 contain data and have software applications including software tools processing thereon. Other types of data processing systems such as personal digital assistants (PDAs), smartphones, tablets and netbooks may be coupled to network 210.
Server 220 may include software application 224 and data 226 for utilizing a dynamically adaptable rules engine to manage process control-based use cases or other software applications and data in accordance with embodiments described herein. Storage 230 may contain software application 234 and a content source such as data 236 for utilizing a dynamically adaptable rules and communication system to manage process control-based use cases. Other software and content may be stored on storage 230 for sharing among various computer or other data processing devices. Client 240 may include software application 244 and data 246. Laptop 250 and mobile device 260 may also include software applications 254 and 264 and data 256 and 266.
Facility 280 may include software applications 284 and data 286 on local data processing equipment. Other types of data processing systems coupled to network 210 may also include software applications. Software applications could include a web browser, email, or other software application for utilizing a dynamically adaptable rules and communication system to manage process control-based use cases.
Server 220, storage unit 230, client 240, laptop 250, mobile device 260, and facility 280 and other data processing devices may couple to network 210 using wired connections, wireless communication protocols, or other suitable data connectivity. Client 240 may be, for example, a personal computer or a network computer.
In the depicted example, server 220 may provide data, such as boot files, operating system images, and applications to client 240 and laptop 250. Server 220 may be a single computer system or a set of multiple computer systems working together to provide services in a client server environment. Client 240 and laptop 250 may be clients to server 220 in this example. Client 240, laptop 250, mobile device 260 and facility 280 or some combination thereof, may include their own data, boot files, operating system images, and applications. Data processing environment 200 may include additional servers, clients, and other devices that are not shown.
In the depicted example, data processing environment 200 may be the Internet. Network 210 may represent a collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) and other protocols to communicate with one another. At the heart of the Internet is a backbone of data communication links between major nodes or host computers, including thousands of commercial, governmental, educational, and other computer systems that route data and messages. Of course, data processing environment 200 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area network (LAN), or a wide area network (WAN).
Among other uses, data processing environment 200 may be used for implementing a client server environment in which the embodiments may be implemented. A client server environment enables software applications and data to be distributed across a network such that an application functions by using the interactivity between a client data processing system and a server data processing system. Data processing environment 200 may also employ a service-oriented architecture where interoperable software components distributed across a network may be packaged together as coherent business applications.
The present embodiment is described as an automated rules and communication system for developing a model of an entity(ies) from both organization chart and business process data flow points of view in order automatically to determine the scope of laws, regulations, policies and other mandates (i.e., use cases) that apply to that particular entity. This model, also referred to herein as a knowledge base, as well as the rules to be applied against that model, may be developed and updated collaboratively among multiple users in a structured but adaptable manner. An entity may be a single entity or multiple interrelated entities combined and treated as a single entity for purposes of describing the present embodiment. In the case of multiple interrelated entities, each entity may also be treated as a single entity as described below, then the result combined to determine the use cases that apply to the combined entity. Also, for multiple entities, data for and processing of the present embodiment may be maintained on separate virtual systems or as isolated copies with firewalls in-between for each entity or group of entities so as to preserve the confidentiality of data from other entities or groups of entities.
System management module 320 includes a User 1322 interacting with a graphical user interface (GUI) 324 to manage the various elements of system management module 320. As described in greater detail below with reference to
User 1 may be a single user, multiple users, a set of users with a given access profile, or other set of users authorized to utilize User 1 GUI 324. User 1 may also be the same as or separate from any other users (e.g., Users 2-4) shown herein. User 1 may also be from or support a different entity than other users. For example, User 1 may be from or supporting an entity managing software implementing this embodiment while other users may be from or supporting an entity applying the software implementing this embodiment to a specific entity. An entity may be a sole proprietorship, a partnership, a corporation or a set of interconnected entities such as a corporation and its subsidiaries. An entity also may be a set of processes performed by a generally defined set of users. A set of governing requirements for a use case 326 may be received, developed and/or approved by User 1 for generating of a set of applicability rules 303 and a set of attributes and queries 328 while utilizing framework 330. A use case may be a set of process controls or criteria (i.e., standards) to be met for a set of process controls for managing certain processes including regulatory, policy, contractual, code of other governing standard requirement such as privacy requirements, a set of governing standards received, generated and/or implemented by User 1, or other set of process control-based governing requirements. Use cases may include privacy laws (laws that deal with the regulating, storing and using of personally identifiable information of individuals), including the GDPR (General Data Protection Regulation) in Europe, CalOPPA (California Online Privacy Protection Act) in California, and numerous other privacy laws worldwide. Applicability rules 303 may be a set of rules to determine whether a use case applies to an entity based on that entity's profile and processes, such as described within knowledge base 305. Attributes and queries 328 may include a set of queries about an entity utilized for asking a user (such as User 2 as described below) to obtain a desired set of entity attributes. Attributes may include public or private information regarding an entity, such as annual revenue, number of employees, jurisdictions where the employees are located, types of data collected and stored from employees, customers and other users, where that data is stored and shared, data flows and processes utilizing that data, etc. That is, attributes may include various types of process data flows. For example, selling products in the European Union or collecting personal information from European Union residents may result in a determination that the GDPR use case applies. Such a determination of applicability may result in a task of documenting those process data flows to determine whether those process data flows are in compliance with the applicable GDPR use case rules.
Once these attributes have been documented, or as they are being documented, applicability rules 303 may then be applied to this obtained set of entity attributes to determine whether one or more use cases applies to an entity. Compliance rules 304 may then be applied to use cases by compliance engine 302 to generate tasks for moving towards compliance to the applicable use cases. Rules may be a logical expression for evaluating the application of a control or set of controls or whether a particular action or task is needed. Framework 330 may include a structured hierarchy of process controls that are common to a particular set of mandates, such as privacy or security, to which a variety of prior use cases have been applied. Often multiple use cases may utilize the same or similar criteria determining applicability or requirements for achieving compliance and Framework 330 provides a hierarchical listing of such criteria and requirements that can be cross-referenced and utilized across multiple use cases. Framework 330 may also include a set of prior applicability rules, attributes related to those prior use cases for possible utilization with an incoming use case. In an alternative embodiment, certain queries for eliciting input of certain attributes could be included in the framework so multiple entities could have a base of standard queries to work from in generating the queries in attributes and queries 328.
Profile management module 340 includes a User 2342 interacting with a User 2 GUI 344 to manage the various elements of profile management module 340. As described in greater detail below with reference to
Use case management module 360 includes a User 3362 interacting with a User 3 GUI 364 to manage the various elements of use case management module 360. As described in greater detail below with reference to
Task management module 380 includes a User 4382 interacting with a User 4 GUI 384 to manage the various elements of task management module 380. As described in greater detail below with reference to
The automated rules and communication system described with reference to
Then in step 434, applicability engine 301 can be rerun with any updated applicability rules 303 utilizing the current knowledge base 305 to generate updated dashboard 350, detail report 366 and applicable use cases 307 for viewing and action by the other users. This may be rerun only for those applicability rules 303 and applicability engine 301 that have been updated through the above steps by User 1. Alternatively, applicability rules 303 and applicability engine 301 may only be rerun upon the request of User 3. Then in step 436, an audit trail of the attributes rules and attributes engines updates is preserved including the identity of User 1, either in the knowledge base as a snapshot or in a separate audit trail database. This audit trail may be generated concurrently with attributes data entry of step 432 or at the end of the attributes data entry session by User 1.
In a third step 464 User 3 may review the use cases identified as applicable by applicability engine 301 as well as use cases not identified as applicable for the entity. User 3 may then approve or modify the results of applicability engine 301. If User 3 modifies the results of applicability engine 301, User 3 may either select use cases as applicable or not regardless of whether they were deemed applicable or not by applicability engine 301. User 3 may also have an option to log into User 2 GUI for profile management module 340 to modify the entity attributes and profile. These modifications to the entity profile may alter which end cases are applicable for that entity. User 3 may also have an option to log into User 2 GUI for profile management module 340 to generate or modify a test version of the entity attributes and profile. A test profile can be managed similar to an entity profile by User 3 to determine use case applicability of that test profile. Then in step 466, User 3 may prioritize those use cases identified as applicable to the entity by User 3 (through approval or modification of the results of applicability engine 301). This prioritization may focus attention to and efforts for accomplishing tasks generated pursuant to the applicable higher priority use cases. Based on User 3's applicability approvals, modifications and prioritization, in step 468, the resulting set of use cases are provided to task management module 380 for determining and obtaining compliance to those use cases. As described below, this includes generating tasks that are prioritized based on the use case prioritization by task management module 380. In an alternative embodiment, some or all tasks could then be generated in the use case management module for approval and assignment to various individuals by User 3. In another alternative embodiment, a use case may be simulated in this module to identify the various tasks to be performed pursuant to that simulated use case in task management module 380. In step 470, an audit trail of the use cases provided, approved, modified and prioritized with the identity of User 3 are stored, either in the dashboard 350 as a snapshot or in a separate audit trail database. This audit trail may be generated concurrently with use case management by User 3 in steps 464 to 466 or at the end of the use case data management session by User 3.
Graphical User Interface (GUI) 600 is accessible by the managing user as shown above with reference to User 3 of
A listing of all use cases deemed not applicable to the entity, shown in entity description 605, are listed in not applicable listing 620. Not applicable listing 620 includes a description of each use case 622, reason for not applicable box 624, Add applicability 626, and previous status 628. Description 622 describes the use case that has been deemed not applicable. This may be a full use case such as GDPR, or it may be a portion of a use case with each non-applicable portion listed separately as applicable or not. In this embodiment, no priority is given for use cases deemed not applicable. Reason box 624 can be selected to view the reason that use case was deemed applicable. Pressing or clicking reason box 624 can generate a pop-up box or other method for showing the detailed reasons the use case was deemed applicable. The managing user can then select add applicability button 626 to add a use case as applicable. A history of each use case may also be also shown by selecting history button 624, allowing the managing user to view a history of the use case for this entity in a pop-up box or other method.
GUI 600 provides the managing user the capability of adding use cases not listed above in box 630. These may be use cases where there is not currently a set of rules for determining applicability. GUI 600 also provides a link 640 for the managing user to log onto Profile Management module 640. Also provided is a clickable button 650 for rerunning applicability engine 301. This can be useful after the managing user has made modifications to the entity profile or at other times convenient to the managing user. An additional link may be provided for the managing user to view various audit trails generated by the various processes described herein. Other users may also be given this capability, possibly some users with broader viewing rights, other users with narrower viewing rights.
As described above, various elements of
In step 700, applicability engine receives a request or is otherwise initiated by circumstances such as described below to make an applicability determination for a given set of use cases for a given entity. In the case of multiple use cases or multiple entities, the following could be performed for all those uses cases and entities. The applicability engine then requests and/or obtains a set of applicability rules for the given set of use cases in step 705. Then in step 710, the applicability engine then requests and/or obtains an entity profile for the given entity such as from a knowledge base for that entity. The set of applicability rules and the entity profile may have been generated as described above with reference to
In step 725, the applicability engine indicates whether additional information is needed to make a determination of applicability. This can occur if there is missing information in the entity profile or other circumstances as set forth in the applicability engine. For example, additional tasks such as identifying certain data flows may be needed for making a determination of applicability. If yes in step 725, then in step 730 a managing user may be notified of this indication. The managing user can then correct the shortcoming directly or may generate a task requesting another user, such as a profile user, to correct this shortcoming. Processing can then return to step 700 until this shortcoming is corrected. If no in step 725, then processing continues to step 740.
In step 740, the applicability engine makes a determination of applicability in accordance with applicability rules and the entity profile. Applicability engine then provides a communication of this determination in step 745, such as to a managing user. This communication may be made through a dashboard, a report, stored in a database for later retrieval by a user or agent, etc. Upon providing the communication of this determination of applicability, in step 750, applicability engine awaits receiving an approval or rejection of this determination, such as from the managing user. Upon receiving an approval or rejection of the determination of applicability, the results are stored in a database of applicable use cases in step 755.
Then in step 760, the applicability engine awaits an indication that the entity profile has been modified. This could be a general indication of a modification to the entity profile or it could be a specific indication of a modification to an attribute needed for the applicability rules of the given set of use cases. If yes, then processing returns to step 700 above. In addition, in step 765, the applicability engine awaits an indication that the applicability rules for the given set of use cases have been modified. If yes, then processing returns to step 700 above. This indication of a modification to the entity profile or the applicability rules may be automatically provided to the applicability engine by the GUIs used to make these modifications, automatically by the modules storing the entity profile and the applicability rules, upon request of a user, as a result of a periodic query by the applicability engine, etc.
The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction processing device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may be processed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may process the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are processed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which are processed on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more performable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be processed substantially concurrently, or the blocks may sometimes be processed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
A data processing system suitable for storing and/or processing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual processing of the program code, bulk storage media, and cache memories, which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage media during processing.
A data processing system may act as a server data processing system or a client data processing system. Server and client data processing systems may include data storage media that are computer usable, such as being computer readable. A data storage medium associated with a server data processing system may contain computer usable code such as for utilizing a dynamically adaptable rules and communication system to manage process control-based use cases. A client data processing system may download that computer usable code, such as for storing on a data storage medium associated with the client data processing system, or for using in the client data processing system. The server data processing system may similarly upload computer usable code from the client data processing system such as a content source. The computer usable code resulting from a computer usable program product embodiment of the illustrative embodiments may be uploaded or downloaded using server and client data processing systems in this manner.
Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
The terminology used herein is for the purpose of describing particular embodiments and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Application No. 62/858,979, filed Jun. 8, 2019, entitled “DYNAMICALLY ADAPTABLE RULES AND COMMUNICATION SYSTEM TO MANAGE PROCESS CONTROL-BASED USE CASES”, and claims priority to U.S. Provisional Application No. 62/858,980, filed Jun. 8, 2019, entitled “DYNAMICALLY ADAPTABLE RULES AND COMMUNICATION SYSTEM FOR MANAGING PROCESS CONTROLS”, the disclosures of which are incorporated in their entirety herein by reference.
Number | Date | Country | |
---|---|---|---|
62858979 | Jun 2019 | US | |
62858980 | Jun 2019 | US |