Mission Critical Sample Clauses

Mission Critical. Products/FRUs which are Mission Critical will be designated as such in Exhibit B-5 with the initials “MC” after the part number. All parts designated as Mission Critical must be complaint with the Mission Critical Process and report data provided by Supplier in the format specified in Supplier Guidelines.
Sample 1
AutoNDA by SimpleDocs
Mission Critical. The Product fails to function according to its published specifications and GENERAL MAGIC is unable to proceed without a fix to the problem or a work-around solution provided by ISOCOR (no functionality, e.g., system down problems). 2.1.1. MISSION CRITICAL category problems shall be directly reported to ISOCOR Technical Support by telephone at numbers provided by ISOCOR. All such problems will be assigned immediately upon receipt to a Technical Support Specialist. ISOCOR will initially respond to GENERAL MAGIC within two hours of receipt of the MISSION CRITICAL program error by ISOCOR. This response will inform GENERAL MAGIC of the identity of ISOCOR personnel assigned and of the plan to correct the problem. ISOCOR will in addition provide twice daily status updates until the problem has been fixed. The Technical Support Engineer assigned to the problem will use all commercially reasonable endeavors to reduce the MISSION CRITICAL program error to a MILD/MODERATE program error. If this is not accomplished within four hours from notification of the error by GENERAL MAGIC, then an ISOCOR Development Engineer will be assigned to the problem. The Technical Support Engineer and Development Engineer will work directly with GENERAL MAGIC to reduce the MISSION CRITICAL program error to a SEVERE program error.
Sample 1
Mission Critical. PROMOTIONS. Notwithstanding the foregoing, in the event that AOL fails to provide AG with any integrated Promotion included as a "Mission Critical Promotion" on Exhibit A-1 or an agreed substitute (to the extent such failure is due to the actions or inaction of AOL), in accordance with the express timeline for such integrated Promotion identified on such Exhibit A-1 (subject to Section 1.1.6 below) then a "Mission Critical Delayed Integration Event" shall be deemed to have occurred and shall continue until implementation of such Integrated Promotion in question. In the event of a Mission Critical Delayed Integration Event, AOL shall have[ ] full months thereafter to remedy such delay, and, if after such period AOL is unable to so remedy, then the Parties shall negotiate for an additional period of up to[ ] months to reach mutual agreement upon either one of the following two remedies: (A) extending this Agreement on a non-exclusive basis (but only with respect to AOL's obligations for all fixed placements for the particular AOL brand on which the specific Integrated Promotion was undelivered (i.e. a particular Exclusive AOL Property, e.g., only on the AOL Service or only the CompuServe Service, as and to the extent applicable), and expressly not with respect to any other carriage nor exclusivity) for a period equal to [ ] times the length of the duration of such Mission Critical Delayed Integration Event, at no additional charge to AG (for example, a [ ] week delay in achieving such a milestone would result in [ ] such weeks of extension to the Initial Term (with respect to the fixed placements on the applicable brand); any such additional weeks are referred to herein as "Extension Weeks"), but in any case only up to a maximum total extension period for any and all such delays of [ ] in the aggregate for any individual brand; or (B) delivering to AG a mutually agreed upon alternative Promotion of "comparable placement or value" to the extent of such undelivered or delayed scheduled Promotion; provided however, that if after so negotiating for such [
Sample 1
Mission Critical. Definition: All users and critical functions affected. Software is non-operational for multiple users using multiple computers. QueTel will diagnose the root cause of the failure and inform the Agency. Examples include, but are not limited to, users unable to logon (system wide) due to software failure.
Sample 1
Mission Critical. A mission critical service requires continuous availability. Breaks in service are intolerable and immediately and significantly damaging. Availability required at almost any price. Key characteristics of this type of service are: Generates revenue: customer of [Responsibility Unit] books orders through the service. External customers are direct users of the services. Underpins the service [Responsibility Unit] provides to its customers. The typical impacts of a service outage are: Inability to conduct business as usual. Damaging for the [Responsibility Unit] commercial reputation and credibility. Long-term outage threatens financial harm. An example of a mission critical service are the point-of-sale terminals for the Duck Store.
Sample 1
Mission Critical. 3 1.25 Multiemployer Plan ......................................................................................3 1.26 Notes ...................................................................................................3 1.27 Participant .............................................................................................4 1.28 Person ..................................................................................................4 1.29 Plan ....................................................................................................4 1.30 Quarter .................................................................................................4 1.31 SEC .....................................................................................................4
Sample 1
Mission Critical. The failure or disruption has an immediate, direct impact on DART's customers. DART's ability to provide one or more services to its customers is directly affected during the period of service interruption. Response Time. Within 1 hour of notification. MTTR. Within 6 hours of response. Service Window. 7 x 24. Continuous effort until the problem is resolved. Notification Method. Contact the Network/Operations Center x3030. • Priority 2 - Critical. The failure or disruption has an impact on DART's ability to maintain services to our customers that while not immediate, will cause services to degrade if not quickly restored. Priority 2 is also assigned to systems or hardware that are used to perform time-sensitive functions, or as otherwise negotiated during the SLA process. Response Time. Within 1 hour of notification. MTTR. Within 12 hours of response. Service Window. 7 x 24. Continuous effort until the problem is resolved. Notification Method. Contact the Network/Operations Center x3030. • Priority 3 - Normal. A single client cannot access an IT provided service needed perform normal business functions. This work or function can be performed by others or by the subject client using another person's system. Response Time. Within 4 hours of notification. MTTR. Within three working days of response. Service Window. 8 x 5. Effort will be during regular working hours. Notification Method. A completed and correct Help Desk On-line service request. • Priority 4 - Low. The problem with the provided service will not affect the agency's mission. In many cases, a workaround is available. It is a nuisance until fixed. Response Time. Within 4 hours of notification. MTTR. Within five working days of response. Service Window. 8 x 5. Effort will be on a workday basis. Notification Method. A completed and correct Help Desk On-line service request.
Sample 1
AutoNDA by SimpleDocs

Related to Mission Critical

  • Project Goals The schedule, budget, physical, technical and other objectives for the Project shall be defined.

  • Project/Milestones Taxpayer provides refrigerated warehousing and logistic distribution services to clients throughout the United States. In consideration for the Credit, Taxpayer agrees to invest in a new refrigeration and distribution facility in the XxXxxxxxx Park area of Sacramento, California, and hire full-time employees (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit A (“Milestones”) and must maintain Milestones for a minimum of three (3) taxable years thereafter. In the event Taxpayer employs more than the number of full-time employees, determined on an annual full-time equivalent basis, than required in Exhibit A, for purposes of satisfying the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” Taxpayer may use the salaries of any of the full-time employees hired within the required time period. For purposes of calculating the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” the salary of any full-time employee that is not employed by Taxpayer for the entire taxable year shall be annualized. In addition, the salary of any full-time employee hired to fill a vacated position in which a full-time employee was employed during Taxpayer’s Base Year shall be disregarded.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Evaluation Criteria 5.2.1. The responses will be evaluated based on the following: (edit evaluation criteria below as appropriate for your project)

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before December 31, 2020 Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving (either itself or through the acts of a SUBLICENSEE) the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Project Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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