Process Interface Manual Sample Clauses

Process Interface Manual a. The Process Interface Manual will: (1) Document detailed processes requiring interface between the Vendor and ACI (for example, change management process, Problem Management/Incident Management, Asset Management). Confidential Exhibit A-1 — Delivery Management Services (Cross Functional) (2) Be used by Vendor to provide the Services. (3) Identify the process interfaces. (4) Describe how ACI and Vendor will interact during the Term. (5) Document all operations procedures, Services, Equipment, and Software for which Vendor is responsible. (6) Document, using ACI-provided information Application requirements that affect Operations, along with procedural information and contact information for each Application. (7) Document procedures to be utilized by End Users for the correct use of the Services, Equipment, Software, connectivity, security, and Service Desk. Until such time as ACI and Vendor complete and ACI approve the Vendor Process Interface Manual, Vendor will use ACI’s current processes and procedures existing as of, and delivered to Vendor prior to, the Effective Date to the extent that such processes and procedures are applicable to the new operating environment. In the event that ACI does not have existing processes and procedures as of the Effective Date or such processes and procedures do not apply to the new operating environment, Vendor will document the processes and procedures for ACI’s environment existing prior to the Effective Date as required by Vendor to perform the Services. The final Vendor Process Interface Manual will supersede all prior processes and procedures unless otherwise specified. b. Vendor Responsibilities Vendor will: (1) Assign an individual to be the single point of contact to ACI for the Process Interface Manual development and maintenance. (2) Provide ACI the proposed table of contents and format for the Process Interface Manual for ACI’s review and approval. (3) Develop and provide ACI the draft Process Interface Manual, which will be customized by Vendor to reflect the process interfaces between ACI and Vendor. (4) Review ACI feedback and revise the draft Process Interface Manual to incorporate mutually agreed changes. (5) Provide the final version of the Process Interface Manual to ACI. (6) Conduct joint annual process maturity assessments, identify process inhibitors, and propose process improvements to ACI. (7) Jointly review the Process Interface Manual on an annual basis or more frequently, as required, and upd...
Sample 1Sample 2
AutoNDA by SimpleDocs
Process Interface Manual. As Provider transitions and migrates Services in accordance with each applicable Transition Plan, Provider will as part of Transition, with Customer’s input and cooperation, develop and update as-needed at all times during the applicable SOW term, a detailed, Customer-specific Process Interface Manual for each of the Services in a mutually agreed form and scope that minimally includes the content specified on Schedule 7 (Program Management and Process Interface Manual). Provider will provide the Services in accordance with the Process Interface Manual. Prior to completion of the Process Interface Manual, Provider will provide the Services in accordance with the policies and procedures generally used by Customer.
Sample 1
Process Interface Manual. A. Within ninety (90) days after the Signature Date, IBM shall deliver to VMU for review and comment a draft of a manual (the “Process Interface Manual”) describing in detail how IBM shall perform the Services, the Equipment and Software used to provide the Services, and the Documentation (such as, for example, operations manuals, user guides, forms of Service Level reports, call lists, escalation procedures, emergency procedures, and requests for approvals or information) which provides further information regarding the Services. The Process Interface Manual shall describe the activities IBM proposes to undertake in order to provide the Services, including, where appropriate, those direction, supervision, monitoring, quality assurance, staffing, reporting, planning and overseeing activities normally undertaken at facilities that provide services of the type IBM shall provide under this Agreement, and further including acceptance testing and quality assurance procedures approved by VMU. The Process Interface Manual shall be based on the form of process interface manual set forth in Schedule A. IBM shall incorporate any reasonable comments and suggestions made by VMU and shall deliver a revised Process Interface Manual within fifteen (15) days after receipt of VMU’s comments. The final Process Interface Manual shall be subject to VMU’s approval. B. IBM shall update the Process Interface Manual throughout the Term to reflect changes in the Services and the procedures and resources used to provide the Services. Updates to the Process Interface Manual shall also be provided to VMU for review, comment and approval. IBM shall update and deliver to VMU for approval portions of the Process Interface Manual relating to any material operational change in the Services within fifteen (15) days of such change. C. IBM shall perform the Services in accordance with the then-current version of the Process Interface Manual. The Process Interface Manual shall be for operational purposes only, and shall not constitute a contractual document. Accordingly, in the event of a conflict between the provisions of this Agreement and the Process Interface Manual, the provisions of this Agreement shall control, and VMU’s acceptance of the Process Interface Manual shall not be deemed a waiver of any rights of VMU.
Sample 1
Process Interface Manual. On or before the Transition Date, IBM shall deliver to AMO, in the form and scope reasonably approved in advance by AMO, a management procedures manual (the “Process Interface Manual”) for the Covered Services to be provided by IBM. IBM shall prepare and provide to AMO updates, reasonably approved by AMO, to such Process Interface Manual to reflect any changes in the procedures described therein as soon as reasonably practicable after such changes are made. The Process Interface Manual and all such updates shall be included in the Annual Services Charge.
Sample 1

Related to Process Interface Manual

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Project Manual A bound manual prepared by the Design Professional. It includes the Invitation to Bid, Instructions to Bidders, the Bid Form, the Specifications, the General Conditions and Supplementary General Conditions.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles: (a) Such schedules shall be established by mutual agreement of the Home and the Union; (b) These schedules may pertain to full-time and/or part-time employees; (c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations; (d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules; (e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis. (f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Network Interface Device 4.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s on-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!