PROTECTING & STORING YOUR MOBILE LEARNING DEVICE Sample Clauses

PROTECTING & STORING YOUR MOBILE LEARNING DEVICE. 7.1 MLD Identification Student MLDs will be labeled in the manner specified by the school. MLDs can be identified in several ways: • Record of district asset tag and serial number • Individual user account name and password All MLDs will be checked out to the students to provide maximum asset accountability.
AutoNDA by SimpleDocs

Related to PROTECTING & STORING YOUR MOBILE LEARNING DEVICE

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

  • Anti-Doping I understand and agree that the UCI Anti-Doping Rules and U.S. Anti-Doping Agency (USADA) Protocol apply to me. I agree to submit to drug testing. If it is determined I may have committed an anti-doping rule violation, I agree to submit to the results management authority and processes of USADA or the results management authority of the UCI and my national federation. I agree that arbitration is my exclusive remedy under the above rules.

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

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Protecting Your Personal Information In addition to protecting your access codes, you should also take precautions to protect your personal identification information, such as your driver’s license, Social Security number, or tax identification number. This information by itself or together with account information may allow unauthorized access to your accounts. You should treat personal information with the same level of care that you would for your account information. You should also protect and secure all information and data stored in any personal computer or other equipment you use to access our Online Banking service.

  • Visitors to and Conduct on School Property Petitions or written correspondence to the Board shall be presented to the Board in the next regular Board packet. LEGAL REF.: 5 ILCS 120/2.06, Open Meetings Act. 105 ILCS 5/10-6 and 5/10-16. CROSS REF.: 2:220 (School Board Meeting Procedure), 8:10 (Connection with the Community), 8:30 (Visitors to and Conduct on School Property) Adopted: September 5, 2019 Meridian CUSD 223 2:240 Board Policy Development The School Board governs using written policies. Written policies ensure legal compliance, establish Board processes, articulate District ends, delegate authority, and define operating limits. Board policies also provide the basis for monitoring progress toward District ends. Policy Development Anyone may propose new policies, changes to existing policies, or elimination of existing policies. Staff suggestions should be processed through the Superintendent. Suggestions from all others should be made to the Board President or the Superintendent. A Board Policy Committee will consider all policy suggestions, and provide information and recommendations to the Board. The Superintendent is responsible for: (1) providing relevant policy information and data to the Board,

  • INFORMATION TECHNOLOGY The following applies to all contracts for information technology commodities and contractual services. “Information technology” is defined in section 287.012(15), F.S., to have the same meaning as provided in section 282.0041, F.S.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Developer and Connecting Transmission Owner agree to report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of this Agreement.

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