Integration and Interface Requirements Sample Clauses

Integration and Interface Requirements. 2.4.5.1 File based integration. The system must be able to facilitate file-based integration via a purpose-built application at least on an hourly basis. This application must be able to extract or import data according to dynamically defined business rules. This application must also be able to manage and track processed data, regenerated files and enable additional file layouts as required. The system must be able to record the erf number and municipal account number for every individual meter as to enable integration with the municipal financial system. 2.4.5.2 Web services based integration The system must be able to facilitate both real-time and file-based integration via a purpose-built application at least on an hourly basis. This application must be able to extract or import data according to dynamically defined business rules within a central directory as agreed upon by Mossel Bay Municipality.
AutoNDA by SimpleDocs

Related to Integration and Interface Requirements

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection. 2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by PNG.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Listing and Maintenance Requirements The Common Stock is registered pursuant to Section 12(b) or 12(g) of the Exchange Act, and the Company has taken no action designed to, or which to its knowledge is likely to have the effect of, terminating the registration of the Common Stock under the Exchange Act nor has the Company received any notification that the Commission is contemplating terminating such registration. The Company has not, in the 12 months preceding the date hereof, received notice from any Trading Market on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing or maintenance requirements of such Trading Market. The Company is, and has no reason to believe that it will not in the foreseeable future continue to be, in compliance with all such listing and maintenance requirements.

  • COMMUNICATION AND NOTICE REQUIREMENTS All communications, notices and approvals provided for hereunder shall be in writing and mailed or delivered to the Seller or the Purchaser, as the case may be, addressed as set forth in the related Sale Agreement or at such other address as either party may hereafter designate by notice to the other party. Notice given in any such communication, mailed to the Seller or the Purchaser by appropriately addressed registered mail, shall be deemed to have been given on the day following the date of such mailing.

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