Process Commonality Sample Clauses

Process Commonality. Supplier shall have the capability to control and make common across ail repair locations, any and all processes that could affect Product quality or the fulfillment of Sun requirements. These processes may include but are not limited to: • Configuration control • Minimum acceptable level • Test equipment and software • Process instructions Labeling • Closed loop corrective action (CLCA) • Packaging • Inspection criteriaFinished goods and raw inventory planning • ECO implementation • Continuous improvement • Process change control • Deviations • Stop ships/purges
AutoNDA by SimpleDocs
Process Commonality. Supplier shall have the capability to control and make common across all repair locations, any and all processes that could affect Product quality or the fulfillment of Dot Hill requirements. These processes may include but are not limited to: • Configuration control • Minimum acceptable level • Test equipment and software • Process instructions • Labeling • Closed Loop Corrective Action ("CLCA") • Packaging • Inspection criteriaFinished goods and raw inventory planning • Engineering Change Order ("ECO") implementation • Continuous improvement • Process change control • Deviations • Stop ships/purges
Process Commonality. Infortrend shall have the capability to control, and make common across all repair locations, any and all processes that could affect Product quality or the fulfillment of Dot Hill requirements. These processes may include but are not limited to: • Configuration control • Minimum acceptable level • Test equipment and software • Process instructions • Labeling • Closed Loop Corrective Action ("CLCA") • Packaging • Inspection criteriaFinished goods and raw inventory planning • Engineering Change Order ("ECO") implementation • Continuous improvement • Process change control • Deviations • Stop ships/purges
Process Commonality. Supplier shall have the capability to control and make common across all repair locations, any and all processes that could affect Product quality or the fulfillment of Dot Hill requirements. These processes may include but are not limited to: • [...***...].

Related to Process Commonality

  • Solution The Supplier’s contractually committed technical approach for solving an information technology business objective and associated Requirements as defined and authorized by the scope of the Contract or any order or Statement of Work issued under the Contract. Solution means all Supplier and Supplier’s third-party providers’ components making up the Solution, including but not limited to Software, Product, configuration design, implementation, Supplier-developed interfaces, Services and Work Product.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, Xxxxx XxXxxxxxxx, Xxxx Xxxxxx, Xxxxx Xxxxxxxx, or a substitute agreed to by the parties, shall at the request of either party:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When Southern Telecom or its authorized agent owns the splitter, Line Splitting requires the following: a non-designed analog Loop from the serving wire center to the NID at the End User’s location; a collocation cross connection connecting the Loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The Loop and port cannot be a Loop and port combination (i.e. UNE-P), but must be individual stand-alone Network Elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog Loop from the serving wire center to the NID at the End User’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port. 3.8.2 An unloaded 2-wire copper Loop must serve the End User. The meet point for the Voice CLEC and the Data LEC is the point of termination on the MDF for the Data LEC's cable and pairs. 3.8.3 The foregoing procedures are applicable to migration to Line Splitting Service from a UNE-P arrangement, BellSouth Retail Voice Service, BellSouth High Frequency Spectrum (CO Based) Line Sharing. 3.8.4 For other migration scenarios to line splitting, BellSouth will work cooperatively with CLECs to develop methods and procedures to develop a process whereby a Voice CLEC and a Data LEC may provide services over the same Loop.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Volunteer Firefighting Leave Leave without pay will be granted when an employee who is a volunteer firefighter is called to duty to respond to a fire, natural disaster or medical emergency.

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