System Build Sample Clauses

System Build. IBM to provide the hardware and software environment to support the baseline, development and production environments.
View Source
System Build. Registry Operator and IFFOR will work with the designated back-end registry provider to provide the back-end Registry system and services related to providing and maintaining the system (e.g., registrar help desk and billing). The system will integrate with databases that record and manage the authentication data. Registry Operator and designated back end provider will conduct comprehensive testing of the registry system and registration procedures (including the interfaces with Registrars and the Authentication Services provider(s)). This testing will occur in cooperation with a select group of ICANN accredited registrars (the “Testbed Registrars”) with in put from sTLD Community members as appropriate. The goal of OT&E testing is the confirmation that all entities involved in the registration process are prepared for the commencement of full operations and that escalation, support and reporting processes are in place and ready ICM will ensure that the processes and procedures for registrars and registrants are clearly established and published in time to meet the above schedules. Registry Operator shall provide a mechanism whereby, during a specified period of no less than sixty (60) days prior to the TLD’s Limited Launch date (as defined in the Start-Up Plan), ICANN’s Government Advisory Committee and/or the government of any country or distinct economy participating in the GAC (collectively, “Governments”) may identify for reservation from registration names that match words of cultural and/or religious significance (“Culturally Significant Names”). Intellectual Property (‘IP’) holders will have an extended period in which they can make an IP Claim prior to the Limited-launch of .xxx names. Once registrations begin, if a registrant attempts to register a name that has an IP claim against it, the prospective registrant will be notified of the existence of IP Claim(s) and the identity of the claimant(s) before the registration is confirmed and once registration is confirmed, the IP Claimant(s) will be notified the name has been registered. The IP claimant may challenge the registrant’s rights to the name within a set timescale, during which time the challenged name will be designated not to resolve. Likewise, the domain holder may also initiate a dispute resolution process to challenge the IP claim(s) and obtain a resolving name. If a proceeding is initiated during the allotted time the challenged name will continue not to resolve until the dispute resol...
View Source

Related to System Build

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Use (a) An electronic site access system may be used on site, subject to the requirements of this statement. (b) The system operates via: (i) a facial recognition device; and (ii) an electronic gate. (c) The system will be installed at the access and egress point/s of the site and will only be utilised to identify presence on site. (d) The purpose for which the electronic site access system will be implemented is to ensure: (i) avoiding unauthorised access to site; (ii) confirmation and co-ordination of effort in emergency situations; and (iii) confirmation that all entrants to site have received a site specific induction; (e) The only personal data collected by the system is a site entrant’s: (i) image; (ii) first & last name; (iii) mobile phone number; (iv) email address; and (v) employer’s name. (the Collected Data) (f) The Collected Data will only be held or used for the purposes specified above, unless otherwise by consent or required by law. (g) The Employer will not use the electronic site access control system to verify who was on a site at a particular time for the purpose of: (i) evaluating whether a variation claim regarding labour costs made by a subcontractor can be substantiated; (ii) taking disciplinary action against an Employee, or assisting a subcontractor to take disciplinary action against its own employees, regarding their start and finish times; or (iii) otherwise generally tracking a worker’s movements whilst on the site.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

  • 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.