Service Architecture Clause Samples

The Service Architecture clause defines the structural framework and components of the services to be provided under the agreement. It typically outlines how different service elements interact, the technologies or platforms involved, and the responsibilities for maintaining or integrating these components. For example, it may specify whether services are delivered via cloud infrastructure, on-premises systems, or a hybrid model, and detail the interfaces or data flows between them. This clause ensures both parties have a clear understanding of how the service will be delivered and maintained, reducing the risk of misunderstandings or technical disputes during the contract term.
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.
View Source
Service Architecture. Other Users Data Sources 6.1 Views and Facilities The service will provide a link between Meter Serial Number, Site Address and Postcode, using the MPRN as the key data item. 6.1.1 SCOGES Home Page The options presented to the user when accessing SCOGES will depend on the type of user logged into the system. 6.1.2 „Triangulation Service‟ View (A) Users are able to search the Triangulation Service using one or any combination of the following variables: (i) MPRN; and (ii) Site Address; and (iii) Postcode; and (iv) Meter Serial Number. (B) Users are presented with all records containing the data searched for. Users can then select the appropriate record or refine their search further. (C) Upon selection of a record, the user is presented with an initial high level summary of the basic site data – the Transporter that supports that site, site address, MPRN, MSN, MAM Id, Gas Act Owner, Market Designation and LDZ ID. The Triangulation Service data items list can be found in Section 6.4. (D) To view the current and incoming Supplier information fields, the user must confirm that it has permission from the Customer to view that data. (E) If the user is a Transporter, Supplier or Shipper, an option to view further data will then take the user through to the „Meter Point Search‟ facility. 6.1.3 „Meter Point Search‟ Facility This facility allows the user to access the „Meter Point, Supply Point & Asset Data‟ view for single MPRNs. If the user is the registered Transporter, Supplier, Shipper or Customer for that Meter Point (determined from the password used by the user to log on to the system) it is presented with the „Meter Point, Supply Point & Asset Data‟. 6.1.4 „Meter Point, Supply Point & Asset Data‟ View Upon completion of a search from the „Meter Point Search‟ facility, the user is presented with a detailed view of the „Meter Point, Supply Point & Asset Data‟ view (see Section 6.5for a list of the data items in this view), but only for sites connected to Large Transporter networks. Only the „Triangulation Service‟ view is available for sites connected to Small Transporter networks. 6.1.5 „Industrial and Commercial Consumer Data Access‟ Facility Industrial and Commercial Customers are provided with access to SCOGES to view Meter Point, Supply Point and Asset Data for their portfolio of Meter Points.
View Source
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.
View Source
Service Architecture. Formatted: Heading 1,JPW-num-section Formatted: Font: Arial 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
View Source
Service Architecture 
View SourceView Similar (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.

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

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

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.