Service Dependencies. In addition to any specific obligations that you have agreed to in an Order, You will provide to Hitachi, on a timely basis, the information, facilities, staffing, decisions and co-operation as Hitachi reasonably expects of you as a recipient of the type of Services involved and you will ensure that any exclusions, dependencies and assumptions set out in the Order are, respectively, correct and will be met. If this does not happen, You accept that the Services may not be performed as set out in the Order, related targets and deliverables may not be met and that Hitachi is not liable for such consequences.
Service Dependencies. We set out in the Master Service Agreement and individual Service Description our dependencies.
Service Dependencies. You agree that where Services to be provided and/or completed by Magnolia are dependent on others performing work (e.g., providing power, building enclosures or cabinetry) we will not be liable for any delays in completing the Services due to incomplete work of others. Upon discovery of any unknown or undisclosed information concerning the condition of the project site or the status of dependencies, the project scope and/or schedule is subject to alteration.
Service Dependencies. As already mentioned in Section 1, service dependencies may be explicit, or implicit. Explicit dependencies play a central role in Service-Oriented Comput- ing. The assumption here is that a service’s logic (the functionality it delivers) depends on some other service by means of composition. If we assume that a service implements an algorithm, and that an algorithm is represented by a se- xxxx of atomic operations (instructions) as shown in Figure 1, then one or more of those instructions are carried out by the services on which this former service depends on. A typical example are business processes, usually modeled as work- flows, that bind to external services and invoke them during execution. Complete outsourcing of one’s work is also an example; in this case, a service provider who cannot satisfy the demand of its customers, acts as a customer to another ser- vice provider and delegates some of its work to this latter provider. A service modeled as part of a composition may or may not be actually used, depending on the composition’s logic. It is use-case-specific details which define if a service is invoked or not. Still, dependencies exist in the form of candidate invocations. Figure 2 illustrates a composed service (“Composition”) that relies on four dif- ferent services (“A”, “B ”, “C ” and “D ”). The instructions that correspond to the composite service are representing the glue code for the composition, which performs invocations, data staging and similar tasks. Time a1 a2 a3 a4 a5 a6 ... aN
Service Dependencies. NBC recognises that it will need to co-operate with and give SOTCC information and access to its systems as necessary to enable SOTCC to deliver the services properly. NBC agrees to timeously provide to SOTCC such information/access as well as any instructions that SOTCC may from time to time request.
Service Dependencies. The service is dependent on basic training for the member of the Customer’s or End User’s personnel making and dealing with the Support Request and also as listed under General Service Dependencies (F) below Service Exclusions: As listed under General Service Exclusions (G) below B. Description of Service and Support where remote support is given
Service Dependencies. 3.1 The following Service Dependencies are specific to the Hybrid Hosted Infrastructure and the On-Premise Hosted Infrastructure:
Service Dependencies. 3.1. In order to enable implementation and/or use of this Service, Customer shall (at its own cost and expense):
Service Dependencies. 4.1 It is the responsibility of the Customer to maintain and keep up to date all of its equipment that is not supported herein.
Service Dependencies. 6.1 The Customer will allocate space and fixtures reasonably necessary to provide the Services.
