Service Architecture Sample Clauses

Service Architecture. Other Users (e.g. DWP & Energywatch) Transporters, Suppliers & Shippers Industrial & Commercial Consumers SECURITY LELVEL Password Entry ACCESS Access To SCOGES Access To SCOGES Access To SCOGES Triangulation Service View VIEWS & FACILITIES (if user is Transporter, Supplier, Shipper or Consumer for that site) Meter Point, Supply Point & Asset Data View Meter Point Search Facility Industrial & Commercial Consumer Data Access Facility Database(s) DATA Data Sources Figure 1 - Service Overview
Sample 1
AutoNDA by SimpleDocs
Service Architecture. Formatted: Heading 1,JPW-num-section Formatted: Font: Arial Formatted: Font: 11 pt, Not Italic Formatted: Heading 2, Left Formatted: Font: 11 pt, Not Italic Formatted: Font: 11 pt Formatted: Font: 11 pt, Not Italic Formatted: Heading 2 Formatted: Font: 11 pt, Not Italic Formatted: Font: 11 pt, Not Italic Formatted: Heading 2
Sample 1
Service Architecture. Implementation of an architecture for service access. The goal of this architecture is to ensure that internal services (such as dataset linking) can be integrated with external services such as those brought by Cortext (Text and Network analysis, Geographic), GATE (Text-Mining), and D4Science (DataMiner NLP Hub). The RCF will access those external services via their APIs and process the results using its internal architecture and interchange format. All these external services will be developed and enhanced in WP5. The task here is about defining the common architecture to process results from a variety of services.
Sample 1
Service Architecture. This section presents how the service is delivered in more detail, describing the different parts, components and internal or external activities, the owners/providers should undertake to make the service available. Details of the different fields for these three main sections, are reported in Table 1. The Table provides details of each section, with a brief description of the suggested fields as well as whether they are listed in the Service Catalogue (external) to be accessible by the users.
Sample 1
Service Architecture 
Sample 1Sample 2Sample 3See All (4)

Related to Service Architecture

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

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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

  • Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are in the SLA. The remedies above are Customer’s sole remedies for breach of the warranties in this section. Customer waives any breach of warranty claims not made during the warranty period.

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

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