FACILITY ACCESS CONSIDERATIONS Sample Clauses

FACILITY ACCESS CONSIDERATIONS. For an open innovation model to become established and sustainable, it is essential for it to deliver predictable and repeatable levels of service, such that Industry view positively further innovation activities. The following are desirable to deliver such a service: – Lead facility contact. – Published availability schedule. – Defined pricing policy. – Access policy, including selection criteria for oversubscription. – Summary of facility health & safety requirements, including user risk assessment. – IPR and Technology transfer policy. – Standard legal & commercial documentation. – Pre-assigned staff resource to undertake innovation work. In an idealised scenario, these requirements should be harmonised across all AMICI Partners. Where legacy considerations make implementation difficult or delayed, policies should be aligned to AMICI best practice wherever practicable. Timing is critical. In many cases, having clarity on scheduling and possible delays is as important to collaborators as having quick access. The effect of delays can often be countered, but there needs to be clarity at the start of engagement as to what those timescales are, so that Industry can draft project plans and accurately assess impact, since use of an AMICI Technical Platform may form just one part of a much larger development programme. This requirement to efficiently process access extends to legal processes. If an AMICI overarching Legal framework is established to govern access, it may still be necessary for individual National Laboratory legal teams to issue documentation (e.g. quotations, IPR agreements, non-disclosure agreements) as part of the process. As with communications regarding initial enquiries, a prompt response is critical in keeping Industry engaged. As with other elements of the AMICI coordination model, a valuable element of the formal creation would be to evaluate each facility’s preparedness levels using test cases.
Sample 1
AutoNDA by SimpleDocs

Related to FACILITY ACCESS CONSIDERATIONS

  • Facility Access Notwithstanding any other provision of the Agreement, the Customer shall provide the Authority with such access to the Facility, and such documentation, as the Authority deems necessary to determine the Customer’s compliance with the Customer’s Supplemental Commitments specified in this Schedule B.

  • Interconnection Facility Options The Intercarrier Compensation provisions of this Agreement shall apply to the exchange of Exchange Service (EAS/Local) traffic between CLEC's network and Qwest's network. Where either Party acts as an IntraLATA Toll provider, each Party shall xxxx the other the appropriate charges pursuant to its respective tariff or price lists. Where either Party interconnects and delivers traffic to the other from third parties, each Party shall xxxx such third parties the appropriate charges pursuant to its respective tariffs, price lists or contractual offerings for such third party terminations. Absent a separately negotiated agreement to the contrary, the Parties will directly exchange traffic between their respective networks without the use of third party transit providers.

  • Use of Interconnection Facilities by Third Parties 46 9.9.1 Purpose of Interconnection Facilities 46 9.9.2 Third Party Users. 46

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Open Access Same-Time Information System (OASIS): The information system and standards of conduct contained in Part 37 and Part 38 of the Commission’s regulations and all additional requirements implemented by subsequent Commission orders dealing with OASIS.

  • Building Access i. Access to Secured buildings: Contractor will work through the GIT Contract administrator for access to the building.

  • Access to Facility 13.1 Each Party shall ensure that its facilities are secured at all times.

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