Configuration Management Sample Clauses

Configuration Management. Seller shall establish and maintain a configuration management system acceptable to Buyer for the Goods and services purchased under this Contract. Seller shall permit Buyer to review procedures, practices, processes, and related documents to determine such acceptability. Seller shall have a continuing obligation to promptly notify Buyer of any violation of or deviation from Seller’s configuration management system and to advise Buyer of the quantity and specific identity of any Goods delivered to Buyer during the period of any such violation or deviation. Additional terms and conditions may be required by SUPP-00883 – Supplier Configuration Management Requirements, incorporated herein by reference.

Configuration Management. Jamf will have policies that govern the installation of software and utilities by personnel.

Configuration Management. Configuration Management will provide a logical model of the IT infrastructure by identifying, controlling, maintaining, and verifying information related to all Configuration Items that support the Services offered to DIR and DIR’s Customers. Configuration Management will include the implementation of a system (the Configuration Management System) which incorporates information from multiple databases (Configuration Management Databases – CMDBs) that contains details of the components or configuration items (CIs) that are used in the provision, support and management of its IT services. This is more than just an “asset register,” since it will contain information that relates to the maintenance, movement, and problems experienced with the CI, and their relationships. The CMS or the DIR records that reside within Service Provider-provided CMS will be DIR Data. Service Provider’s responsibilities include: 1. Facilitate and lead in the development and documentation of processes with Service Provider and other Service Component Provider(s). 2. Facilitate and lead information exchange between and among Service Provider and other Service Component Provider(s), DIR and DIR Customer, and/or Third Party Vendor(s) to improve end-to-end Configuration Management. 3. Validate that the Configuration Management process provides an audit trail that meets the legislative and policy requirements to which DIR and DIR Customer must comply. 4. Integrate Service Provider’s Configuration Management process with the Configuration Management processes of DIR and other Service Component Provider(s), as well as authorized Third Party Vendor(s)’ Configuration Management processes, with and where the processes interact; including providing Configuration data electronically to DIR’s CMS / CMDB. 5. Integrate Service Provider’s Configuration Management process with the other Service Management processes, including Incident Management, Problem Management, Change Management, and Release Management. 6. Coordinate Configuration Management activities across all functions, other Service Component Provider(s), DIR Customer Sites, regions, and Third Party Vendor(s) that provide services to DIR Customers. 7. Communicate and coordinate the Configuration Management processes and policies within Service Provider’s own organization, other Service Component Provider(s), DIR, DIR Customers, and designated Third Party Vendor(s). 7.1. Provide on-going methods for training Service Provider staff, other S...

Configuration Management. The Contractor shall maintain a Configuration Management Plan (CMP) based on NAVSEAINST 4130.12B Configuration Management Policy and Guidance and MIL-HDBK-61B. The Contractor’s CM efforts shall include configuration identification, configuration change control, hardware Configuration Status Accounting (CSA), configuration verification and audits, and configuration data management. The Contractor shall establish a CM process capable of processing required configuration changes in a time frame that enables identification, evaluation, and implementation of proposed changes without impact to production schedules. The Contractor shall provide their CM Plan to the Government for review and approval. (CDRL A009)

Configuration Management. Lotame utilizes automated configuration management tools to manage application runtimes and configuration parameters across its infrastructure, with access restricted to employees that support releases and operations. Within the configuration management information architecture, credentials used by automated systems (e.g., database logins) are isolated from general application configuration parameters to further limit access to such credentials.

Configuration Management. BUYER'S PARTICIPATION IN PRODUCTION AND INSPECTION SYSTEM AUDITS; RELEASE OF INFORMATION. 14 Article 19.

Configuration Management. BUYER'S PARTICIPATION IN PRODUCTION AND INSPECTION SYSTEM AUDITS; RELEASE OF INFORMATION. 18.1 Configuration Management The Seller shall maintain a configuration management system for control of changes in the Uncooled Imaging Module. Subject to paragraph 18.3, below, the Seller shall provide copies of all Engineering Change Orders (ECOs) to the Buyer as they are approved by the Seller's Configuration Review Board (CRB). The Seller shall forward minor changes (class II ECO's) to the Buyer in the Seller's format for the Buyer's information. The Seller shall forward major changes (class I ECO's) to the Buyer for approval. The Seller shall classify class I ECO's as "Routine" or "Urgent". "Routine" ECOs shall be within 60 calendar days of the date sent. If the Buyer fails to respond within this time, the Seller may assume the Buyer's approval. For "Urgent" ECOs, the disposition time limit shall be 20 calendar days. The Seller shall at its option prepare and submit proposals for equitable adjustment of the contract price, delivery and other terms for any ECO activity arising from Buyer-initiated changes, including those due to the needs of the Buyer's vendors. The Seller shall include rough-order-of-magnitude estimates of price impact with the initial technical proposals, and follow with formal price proposals if the Buyer decides to go forward.

Configuration Management. In wireless networks, the broadcasting nature of the channel mandates that the nodes control their transmissions in order to avoid collisions or inter- ▇▇▇▇▇▇▇. In WSNs, one can schedule the communi- cations, according to algorithms such as the Traffic- Aware Scheduling Algorithm (TASA) [10], which uses matching and coloring heuristics to find a commu- nication solution, given the nodes topology and the required traffic load. In WSNs, radio link quality estimation is crucial to predict if the agreed-upon QoS will be met [3]. It permits, alongside with other raw measures (e.g. re- maining energy of the nodes [8], traffic statistics), to elaborate the composite metrics defined in the SLOs. Some of these metrics prove that the QoS require- ment of each SLO is met, and guide the real-time control actions on the network. Others are defined as Key Performance Indicators (KPIs), and sent to the clients and the WSN operator to show them high level statistics of the network. The communication protocols for WSNs have for long been studied and implemented with the goal of meeting QoS constraints. A classification of the MAC layer mechanisms is proposed in [17]. At the routing layer, the IETF ROLL RPL [15] proposes the construction of the routing topology based on Objective Functions (OFs). The OFs include QoS constraints that the topology must meet at buildup. IETF CORE CoAP [11] is an application level proto- col based on UDP and adapted for constrained nodes. WSN Operator Finally, one may design WSNs applicative behavior in order to provide easier resource allocation for con- current applications [8].

Configuration Management. Supplier’s responsibilities for configuration management include: (a) Maintaining a library of Supplier-provided information and documentation for any new, enhanced or modified Software Installed by Supplier, and thereafter maintaining a library of Supplier-provided updates to such materials. (b) On an ongoing basis, evaluating alternative configurations and recommending solutions that shall enable significant cost reductions or performance improvements to Gap. (c) Complying with the agreed upon standard configurations.