Process Management Sample Clauses

Process Management. 3.1 SVTC shall exercise day-to-day managerial authority over the semiconductor wafer fabrication facilities, referred to as the “Line,” including over the allocation of Activities and all aspects of the operation, development and planning of the Line, consistent with the provisions of this Agreement. 3.2 Customer shall appoint employees with decision-making authority to an operating committee (“Operating Committee”) to work with SVTC. The Operating Committee shall meet in person or telephonically once every […***…] at a regularly scheduled time to review operational results and approve future operational matters, including changes to the Line operating procedures applicable to Customer; provided however, that SVTC shall retain ultimate control over any changes to the Line and its operating procedures. The Operating Committee shall attempt to resolve by good faith negotiations any operating disputes that arise with respect to the Line, or any other disputes arising under this Agreement, except as specifically set forth herein. 3.3 SVTC will hold a daily Line operations meeting in which the daily Activities on the Line are reviewed, discussed and planned; a Customer representative is expected to attend all operations meetings. 3.4 Customer shall submit for prior written approval to the Operating Committee or its designee, a list of all proposed operations, including all equipment intended to be used. Failure to adhere to the approved list may be considered grounds for termination as provided in Section 12.3 of the Master Services Agreement. 3.5 SVTC shall have no liability nor be responsible for any costs or damages arising out of or related to the work of Customer Personnel including but not limited to results other than those desired by Customer in the wafers processed on the Line solely by Customer Personnel.

Process Management. The process management must describe in detail how operations operate in a formal manner (see Figure 2). This formalisation is generally conducted through a description of the organisation and its processes supporting the services to their stakeholders. EuroFIR will include such process support based on workflow management. The main processes assisting the integration are: • Common use of infrastructure; • Joint execution of research program; • Co-programming; • Resources relocations; • Staff mobility; • Knowledge dissemination. Other processes related to the internal working of the ▇▇▇ will be included: budget allocation, auditing, committee selection and various communications to the researchers, private sector, professions, consumer, policy makers and other NGOs. • Communication management and internet technology The integration of the IT communication software platform into the network is a key activity that will take place within the first 3 months of the commencement of the project. Around the operating system, the database and the communication system are the essential components of the EuroFIR system architecture. EuroFIR will be underpinned by a robust and well-established web-based e-community software platform. This software will provide a common shared platform, which will facilitate the co-ordination and implementation of the programming and adaptation of the partners’ activities. Critically, the software will reinforce the electronic information and communication networks to support interactive working between the teams involved and in the spreading of excellence via dissemination, communication and networking activities both within the network and to teams external to the network. In addition, the software will support the mobility of researchers within the network by alerting members of the researcher positions open within the network organisations. Furthermore, it will enable members to connect with existing relevant pan-European food research and information networks. An online newsletter will be included, being updated regularly (monthly) to highlight additions and changes to the site content. The network’s IT operating system will support the generic applications: Knowledge Management (KM), Document Management (including publications and methods repositories, reports and publications; DM); Centres Skills & Infrastructure Inventory Management (CSM) and the Food Composition Database Management (FCDM). Other tools such as video conferencin...

Process Management. The Process Management class of services is dedicated to the management of gCube Compound Services (CS), i.e. complex services obtained by composing other simpler services through an appropriate workflow management language. The components in this family cover all aspects related to CS management. In particular, they allow to design via a dedicated user interface the CS and perform various validation activities related to CS design, to manage CS definitions, to execute instances of the services and control in various ways the execution. Finally, a component in this family allows managing gLite jobs as “services” in a CS.

Process Management. During the GMP preparations, the CM will work with the Design team to notify bidders, conduct pre-bid meetings, conduct site visits and/or walk-throughs, and receive trade contractor bids. Upon receipt of bids, the CM will analyze all bids to verify that bids are complete and that no unacceptable qualifications are made. The CM’s bid analysis, together with the CM’s recommendation for award, shall be reviewed with PCMC and the architect prior to award of trade contracts or purchase orders.

Process Management. Identify and implement all types of improvements to the Service in a reactive and/or proactive manner, such as: Implement front-end modifications (Attendance application used during the operations); Introduce alterations to the Audible Response Unit (ARU); Introduce modifications to the Attendance model; Draw up the Orbitall Clients requirements specification (analysis of impact and associated risks).

Process Management. Both Parties shall ensure that all research and development activities conducted within the scope of this Collaboration are managed, documented, and maintained in adherence to the prevailing industry-leading standards. To this end, the Parties shall implement and maintain appropriate measures to ensure effective and timely management, documentation, and maintenance of the following: (a)

Process Management. The first major component of any TSSSA is Process Management. During the mobilization phase of the TSSSA, the contractor is responsible for developing necessary implementation, staffing, material controls, and management plans to establish the successful execution of the TSSSA for the duration of the contract. The process management component represents the critical building blocks for a successful TSSSA. The process management component of a TSSSA may include any or all of the following: Maintenance Plan, Joint Fleet Planning, Service Order Handling, Resource Management and Depot & Investment Management. The contractor shall be required to work in conjunction with the agency to ensure that all maintenance activities are forecasted in a way to optimize maintenance and increase reliability and availability without affecting scheduled revenue service. The contractor shall develop and propose a comprehensive maintenance plan which shall be updated and submitted annually for review and approval by the agency. The maintenance plan shall include all activities, schedules and documentation required by the contractor, regulatory agencies, and the agency to maintain, inspect, and restore equipment to maintain intended design function over the design life of the equipment. The maintenance plan shall be a detailed documented process describing all maintenance activities that are required for the equipment throughout its life and must be reviewed and approved on an annual basis against the performance of the equipment. The maintenance plan shall include the frequency and duration of each activity required and provide a scheduling tool to demonstrate how the equipment will be maintained throughout the life of the project. Ultimately, the maintenance plan shall fulfill the requirements of 49 CFR 238.107.

Process Management. 2.3.1 The Provider will plan the key service processes in a comprehensive way, including identifying responsibilities, service standards and the steps involved in providing the service and references to supporting documentation. 2.3.2 The planned processes will be documented in a clear and integrated manner (i.e. linked together). 2.3.3 The Provider will implement a system for monitoring the Leisure Facility on a daily basis and making any necessary adjustments in line with identified service

Process Management. ‌ This sections analyses generic maturity models for process improvement. In theory, these models can be used to improve processes independently of the domain and context of those processes. A.5.1 ISO/ IEC 15504‌ Description: The ISO/IEC 15504 [39] was born as the “Software Process Improvement and Capability Evaluation” (SPICE) [38] in 1993. The acronym is still used today by the user groups of the standard and in the title of the annual conference. ISO 15504 is a reference model for maturity models that consist of capability levels that consist of the process attributes and further consist of generic practices. The standard is divided into nine components or parts which are, (1) Concepts and introductory guide; (2) A model for process management; (3) Rating processes; (4) Guide to conducting assessment;