System of standardized api interpretation for inter application communication

Abstract

Managed Inter Application Communications and Relationships (MIAC) is a system for business process automation that uses recognised standard application programming interfaces (API), data base schema mapping and raw data to collect, translate and transfer data to facilitate processes that incorporate data transfers, communications, event creations, alerts and physical inputs to build an end-to-end work flow where all actions and communications are recorded for audit and automated feedback response cycles. The system allows for an incremental build of a matrix computer network where all connected systems are separated but communicate in an intelligent rule and workflow driven process, controlled and influenced by the human workforce.

1 - 5 . (canceled) 
     
     
         6 . A user interface (UI) to create projects and tasks, set up processes within a task, invite and disable personnel accounts, set security for personnel, give access rights a privileges to individual accounts and access a generic API library for integrating software. 
     
     
         7 . A generic API library (GAL) where all API structures and known integrations are stored and where these structures integrations can be accessed and used for subsequent integrations via user interface (UI). 
     
     
         8 . A method of creating an integrated, process based workflow of data exchange and communication between different systems, services and people. 
     
     
         9 . (canceled) 
     
     
         10 . The user interface of  claim 6  wherein projects, child projects and tasks are set as a standard and understood tree structure for intuitive system building. 
     
     
         11 . The user interface of  claim 6  wherein processes within tasks are also simplified by giving the administrator or approved personnel the ability to create a single or set of forms to deploy through a task to personnel to facilitate individualised procedures and processes. 
     
     
         12 . The user interface of  claim 6  wherein security may be set individually or by role and wherein by setting a role based security the system applies a global set of rules over the roles where read/write, edit and viewing capabilities are set. 
     
     
         13 . The user interface of  claim 6  wherein administrators may also access the generic API library (GAL) and download a known API to use for integration with another known product. 
     
     
         14 . The library of  claim 7  wherein the user interface allows a person with the necessary security clearances to access the GAL and choose an API, Raw data sensor actions, mapped database schema etc. from a list of available products and places the available data fields into a column designated as an origin system and wherein the API data fields are listed and placed in separate text fields, 
     
     
         15 . The method of  claim 8  wherein all data exchange is retained within tasks. 
     
     
         16 . The method of  claim 8  wherein one action may trigger another within the task and where the actions are listed in sequence as a breadcrumb view to show a user where the process is up to. 
     
     
         17 . The method of  claim 16  wherein limits are set for each action thereby allowing both automated data exchanges and manual human actions to be a part of a single workflow within one task.