Dicode integration approach Sample Clauses

Dicode integration approach. As mentioned above, the Dicode workbench has been implemented as a web application aimed to integrate heterogeneous services, from data mining services to collaboration services. The workbench should present the different services under a common graphic interface and allow users to use them together. The integration has to be done at two levels: (i) at user interface (UI) level, and (ii) at operational level. Integration at UI level deals with the visualization of services under a unique environment or application. After reviewing the state-of-the-art concerning graphical user interfaces (GUIs) on web applications, the consortium decided to adopt a widget-based approach. Widgets allow users to personalize the workbench as needed. More detailed information about this topic is given in next section. On the other hand, integration at operational level is aimed to ensure the communication and exchange of data between different services. On this regard, we decided to design and implement a registry of services to store metadata about services (see Section 3.1.2 for details). To complement the registry of services, a Single Sign-On (SSO) approach has been adopted. This approach facilitates credential delegations between services. Users only have to login the system once to use all the existing services of the workbench. In this section, the abovementioned strategies are explained in detail, introducing the general concepts and how each approach is being used in the Dicode project.
Sample 1
AutoNDA by SimpleDocs

Related to Dicode integration approach

  • 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.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • 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.

  • 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:

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • 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.

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