Decoupled Data-driven and Event-driven Architecture Sample Clauses

Decoupled Data-driven and Event-driven Architecture. The COCOP system architecture strives for scalability and enabling extensive utilisation of data either as refined information or as massive amounts of raw data. One of the main drivers is also decoupling the information producers from their consumers through a centralised bus or - depending on the implementation - a pool of queues for data and events. The event-driven approach comes from the requirement for reactive actions possibly also in real- time. In some cases, the end of a process step may trigger the start of another. For instance, when a batch of process finishes, it may enable the execution of another process step for that particular piece of material. From a performance point of view, scalability is achieved by removing redundant queries to low- level systems and by having a central managed bus architecture in between producers and consumers of information and data. A centralised message bus allows for efficient scaling, caching and managing access independent of the consumers and producers. From a systems integration point of view, a centralised bus provides uniform access to the data thus reducing engineering effort for the plant-wide control applications. A centralised bus, however, can introduce a single point of failure, and additional preventive measures might be needed to ensure reliability, e.g., through redundancy or in restrictions how plant-wide monitoring and control applications are required to operate in case of manual intervention. This kind of architecture benefits especially the development of new plant-wide monitoring and control applications in a platform-like development framework. From a development perspective, the burden is on integrating existing systems with a multitude of different communication interfaces to the bus and the event-driven approach. The development of adapters is needed, as it is not intended to replace existing control systems but integrate them into the new (COCOP) control environment (full replacement would be expensive and create a significant hurdle towards implementation in plants as a new systems with new, unknown risks with potential production losses).
Sample 1
AutoNDA by SimpleDocs

Related to Decoupled Data-driven and Event-driven Architecture

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Elements Unsatisfactory Needs Improvement Proficient Exemplary IV-A-1. Reflective Practice Demonstrates limited reflection on practice and/or use of insights gained to improve practice. May reflect on the effectiveness of lessons/ units and interactions with students but not with colleagues and/or rarely uses insights to improve practice. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues, and uses insights gained to improve practice and student learning. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues; and uses and shares with colleagues, insights gained to improve practice and student learning. Is able to model this element.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

Time is Money Join Law Insider Premium to draft better contracts faster.