Pipeline Service Architecture Sample Clauses

Pipeline Service Architecture. After authoring the pipeline, the user invokes its submission to the Pipeline Service. Upon submission several things occur: first the authored pipeline that is represented in a native format to the authoring environment is translated into a common objected- oriented workflow model. A draft specification of this model was presented in the year 1 deliverable document D6.1. This representation has been expanded to accommodate further use cases and support other workflow paradigms such as service-based workflows. A full specification of the object-oriented workflow language is presented in section 3.2. After workflow translation, the workflow is planned for the execution. In workflow planning the abstract user specified workflow is transformed into a concrete executable workflow. The workflow structure may also be modified for more efficient execution in the grid. Workflow enactment is the final stage in the Pipeline Service. The Pipeline Service submits the planned workflow to the Grid via the Glueing Service. The Glueing Service abstracts all interactions between WP6 Services and the underlying Grid middleware. In the case of the Pipeline Service, the functionality that enables submission of a workflow to the grid and workflow monitoring capabilities are used primarily. Once a workflow has been executed, the Pipeline Service invokes the Provenance Service to initiate the retrieval of the provenance information and the output of the workflow. The user can then query the results through the Querying Service.
Sample 1
AutoNDA by SimpleDocs

Related to Pipeline Service 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.

  • 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 Resource Interconnection Service (check if selected)

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

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • SS7 Network Interconnection 9.7.1 SS7 Network Interconnection is the interconnection of Global Connection local signaling transfer point switches or Global Connection local or tandem switching systems with BellSouth signaling transfer point switches. This interconnection provides connectivity that enables the exchange of SS7 messages among BellSouth switching systems and databases, Global Connection local or tandem switching systems, and other third-party switching systems directly connected to the XxxxXxxxx XX0 network.

  • Service Area (a) SORACOM shall provide the SORACOM Air Global Service within the area designated on the web site of SORACOM (the “Service Area”), provided, that, the Service Area may be different if stated otherwise as specified by SORACOM separately. However, within the Service Area, you may not use the SORACOM Air Global Service in places where transmissions are difficult to send or receive.

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

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

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

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