COMPANY STABILITY Sample Clauses

COMPANY STABILITY. 6.1 Describe your company's financial stability, available equipment, and other resources that will ensure the delivery of acceptable services to MALiA.
AutoNDA by SimpleDocs

Related to COMPANY STABILITY

  • Financial Stability The Contractor shall meet and comply with all requirements located in Title 27, Articles 1 through 15, of the Indiana Code. This includes, but is not limited to, the requirements pertaining to financial solvency, reinsurance and policy contracts, as well as administration of these processes. FSSA and the Indiana Department of Insurance (IDOI) will monitor the Contractor’s financial performance. FSSA will include IDOI findings in their monitoring activities. FSSA shall be copied on required filings with IDOI, and the required filings shall break out financial information for the Hoosier Healthwise line of business separately. The financial performance reporting requirements are listed in Section 9.1 and are further described in the Hoosier Healthwise MCE Reporting Manual, which shall be provided following the Contract award date.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Financial Viability and Regulatory Compliance 4.6.1 The Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. The Contractor further warrants and represents that it owes no outstanding delinquent federal, state, or local taxes or business assessments.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

  • Quality Monitoring 4.2.1. To prepare a Quality Assurance (QA) Plan

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf):

  • Staffing Concerns Nurses, individually or as a group, believing there is an immediate workload/staffing problem should bring that problem to the attention of the supervisor or Nurse Manager as soon as the problem is identified. Nurses believing there is a continuous or potential workload/staffing problem, which may include the ability to receive rest periods and lunch breaks, should attempt to resolve the problem in discussions at the work unit level. Continuous or potential workload/staffing problems discussed at the work unit level that have not been resolved may be raised through the Joint Conference Committee. The Joint Conference Committee may determine that a unit- based work team would best address the workload/staffing problem raised. If the Joint Conference Committee makes that determination, a sub-committee consisting of an appropriate number of staff nurses who are from the unit and shift(s) experiencing the workload/staffing problem (appropriate number of staff nurses to be determined by the Joint Conference Committee), a WSNA representative and appropriate management staff will meet to discuss the problem raised. The sub-committee(s) shall report its results back to the Joint Conference Committee.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • System Monitoring to ensure safe and continuous operation, the Customer must monitor key services and resource use as recommended by Deswik, and provide Deswik with details of monitoring and any relevant alerts as needed. Services to be monitors include, without limitation, disk space, CPU usage, memory usage, database connectivity, and network utilization.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

Time is Money Join Law Insider Premium to draft better contracts faster.