Service Assumptions Clause Samples
POPULAR SAMPLE Copied 32 times
Service Assumptions. 1. The Service Provider shall not sublet any part of the Contract. He shall be solely responsible and liable to deliver the services as per the contract.
2. The manpower provided by the Service Provider shall not be deemed employees of the Buyer department in any manner, hence the compliance of the applicable acts/ laws will be the sole responsibility of the Service Provider. The Service Provider must assess all the proposed candidates of desired requirement on the parameters of educational qualification, work experience, skill assessment, pre-interviewing, short- listing and proposing to Buyer all pre-screened candidates (“Services”).
1. The Service Provider would be required to provide sufficient and qualified manpower, capable of supporting the functioning of the project/department in a manner desired by the Buyer. Any mismatch in demand and supply of the manpower such as number of employees, educational qualification, sectorial/ desired work experience etc. may lead to penalties and/or replacement of the resource with the matching skill set or profile desired by the Buyer.
2. The persons deployed by the Service Provider shall not claim nor shall be entitled to pay, perks and other facilities admissible to regular/ confirmed employees during the currency or after expiry of the Agreement.
3. No medical facilities or reimbursement or any sort of medical claims thereof in respect of employees provided by the Service Provider will be entertained by the Buyer. The working hours and days of the outsourced manpower shall be as per the existing applicable rules of the Buyer. The deployed manpower shall get the benefit of holidays as notified/ declared by the Buyer. However, outsourced manpower has to work on holidays, if necessary and required based on demand of work. The requirement of the manpower may increase or decrease during the period of initial contract also. In case of decrease in the requirement, the same will be informed to the Service Provider and additional manpower shall be withdrawn at the given time. If the requirement is increased, the Service Provider shall provide additional manpower on the same terms and conditions in reasonable time.
1. The persons deployed shall, during the course of their work be shall perform integrity to the Buyer and shall not disclose/ share any qualified documents and information which they are not supposed to divulge to Service Provider/ third parties. In view of this, they shall be required to sign the confid...
Service Assumptions. Assumptions related to in-scope services and/or components include: • Changes to services will be communicated and documented to all stakeholders.
Service Assumptions i. The Service Providershall not sublet any part of the Contract and shall be responsible and liable to deliver the services as per the contract.
ii. For all intents and purposes, the Service Provider shall be the "Employer'' within the meaning of different Rules & Acts in respect of manpower so deployed. The persons deployed by the Service Provider shall not have any claim whatsoever like employer and employee relationship against the Buyer Department.
iii. Only authorized staff of the Service Provider will be allowed entry at the premises of the buyer on production of identity badge.
iv. The premises are the property of the Buyer and Service Provider is only permitted to enter and manage the premises as long the contract remains valid.
v. Guarding/maintaining the Service Provider’s machinery at Buyer’s premises shall be the responsibility of Service Provider.
vi. Service Provider will not usehis consumables(when deployedat Buyer premises) or Buyer’s consumables for any personal use or for any other activity not related to the scope of work under the contract.
vii. Any violation of contractual obligations by the Service Providershall attract penalties, before imposing a penalty, the Buyer will provide 3 days prior notice to the Service Provider to make its representation. The Service Provider confirms and agrees that penalty whenever becomes payable, shall be deducted by the Buyer from the payments due to the Service Provider.
Service Assumptions. Assumptions related to in-scope services and/or components include: • Upendo will use commercially reasonable efforts to resolve errors by providing a workaround or fix, or a specific action plan for how the error will be addressed, and an estimate of how long it will take to rectify the error. • All support calls and e-mails will be logged into Upendo’s support system. Upendo will assign a priority level to an error upon confirmation of the error.
a) if the Services has been modified by anyone other than Upendo;
b) if the Services are being interfered with, or the error is caused by, any hardware or third party software, or if the Services are being run on a third party platform not expressly approved for Client’s version of the Services;
c) for any non-Upendo or non-Hotcakes’ computer programs, technology or hardware;
d) for any portion of the Services for which Upendo has provided a fix or workaround which has not been applied; or
e) for any development work being performed during or on evaluation software.
Service Assumptions. The services and costs within this Agreement are based on the assumptions below. Any assumption found invalid could have an effect on ability to meet service targets and/or costs charged for services. Changes to assumptions will be handled in accordance with the Service Change Control Procedure described in this Agreement. The service assumptions included with this Agreement are:
a) The customer can create any Service Request on ADAM’s Service Request Tool (▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇▇▇▇.▇▇▇).
b) For Incidents and Problems, the customer includes detailed information, such as user, profile, module, input data, output data, and expected data.
c) The customer follows the following procedures appropriately:
a. Service Request Fullfilment Management Procedure
b. Incident Management Procedure
c. Problem Management Procedure
Service Assumptions. Assumptions related to in-scope services include
Service Assumptions. EMI provides technical support to users of its publicly released Components. The support provided by EMI is typically at “expert level” and it is directed at handling incidents that lower level support desks within the Customer Organization could not solve without changing the Component source code or by applying known workarounds. The Technical Support and Escalation Procedures are described in the EMI Project Support Plan. The latest version of the Support Plan can be found on the EMI web site at: User support is provided via the GGUS portal managed by the EGI InSpire project (see section 5.4.1, Web-based Support), which is the single point of contact for infrastructure users to access the EMI Service Desk. The EMI Service Desk within GGUS is organized in Support Units. Every Support Unit is responsible for one or more Components. The number and definition of the EMI Support Units in GGUS is not regulated by this SLA and can change at any time to fulfill the EMI Incident and Problem Management requirements. Incidents are analysed by the EMI Technical Experts to identify the Problem or Problems that have caused them. If available, suitable workarounds are proposed to restore the Service to its agreed level as soon as possible. If the incident is caused by Problems in the software and a change is required, a software defect report is filed by the EMI Technical Experts in one of the EMI defect tracking systems and a change request is produced and scheduled for a future release depending on the Problem priority. The priority levels and their relationship with the Problem impact and severity are defined in Appendix: Definitions, the agreed response policies are defined in section 6 (Service Management). This Service Level Agreement applies to Services provided by EMI for any Component making part of the EMI Product Catalogue. Conversely, the Product Catalogue lists all software Components that at any given time are supported by EMI. Components can be deprecated and removed from the Product Catalogue and new Components can be added during the lifetime of EMI according to the procedures described in the EMI Support Plan and the terms described in this SLA in section 5.3.2 (Support Lifecycle).
5.4.1 Web-based Support EMI web-based Support is available through GGUS at: ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/pages/home.php It provides the Customer with access to EMI support via the Customer GGUS- based escalation process or via approved third-party organizations acting as first and s...
Service Assumptions. 1. The Service Provider shall not transfer or assign or sublet any part of the service once agreed or any share or interest here in any manner or degree directly or indirectly to any person, firm, or corporation whatsoever.
2. The Service Provider at his/ her own cost will arrange all the equipment(s), materials (in case of printing with the material), and other things/ services, etc. necessary for printing depending on the type of printing (with or without material).
Service Assumptions. EMI provides technical support to developers using its Components even before their public release. The support provided by EMI is typically at “expert level” and it is directed at handling incidents that lower level support desks within the Contributor Organization could not solve. The Technical Support and Escalation Procedures are described in the EMI Project Support Plan. The latest version of the Support Plan can be found on the EMI web site at: User support is provided via the GGUS portal managed by the EGI InSpire project (see section 5.4.1, Web-based Support), which is the single point of contact for infrastructure users to access the EMI Service Desk. The EMI Service Desk within GGUS is organized in Support Units. Every Support Unit is responsible for one or more Components. The number and definition of the EMI Support Units in GGUS is not regulated by this OLA and can change at any time to fulfill the EMI Incident and Problem Management requirements. Incidents are analysed by the EMI Technical Experts to identify the Problem or Problems that have caused them. If available, suitable workarounds are proposed to restore the Service to its agreed level as soon as possible. If the incident is caused by Problems in the software and a change is required, a software defect report is filed by the EMI Technical Experts in one of the EMI defect tracking systems and a change request is produced and scheduled for a future release depending on the Problem priority. The priority levels and their relationship with the Problem impact and severity are defined in Appendix: Definitions, the agreed response policies are defined in section 6 (Service Management). This Operational Level Agreement applies to Components provided by EMI and making part of the EMI Product Catalogue. Conversely, the Product Catalogue lists all software Components that at any given time are supported by EMI. Components can be deprecated and removed from the Product Catalogue and new Components can be added during the lifetime of EMI according to the procedures described in the EMI Support Plan and the terms described in this OLA in section 1.3.2 (Support Lifecycle).
5.4.1 Web-based and E-Mail Support
(a) Product documentation, release notes, troubleshooting guides and technical white papers about EMI software Products, as releases become publicly available. Technical previews can be obtained as part of the the “Works with EMI” technical program.
(b) Software Downloads, a public repository of...
Service Assumptions. Customer will provide a healthy working environment for the Vendor professionals visiting customer site for this engagement • Customer will ensure that site readiness is complete before implementation phase • Customer will configure Public network including Jumbo frames, Load balancer and/or firewall • Customer to register the system after the service is complete to ensure support and warranty for this system • Customer to own the decision for the final cut-over to production after this service is complete • Vendor will remove all the IP, including tools and scripts, used for implementation and testing of the environment • Customer will provide a healthy working environment for the Vendor professionals visiting customer site for this engagement