Mobility Requirements Sample Clauses

The mobility requirements clause sets out the expectations and obligations regarding an employee’s need to travel or relocate for work purposes. Typically, it outlines the geographic areas where the employee may be required to work, the frequency or conditions under which travel or relocation may occur, and any notice or support provided by the employer. This clause ensures both parties understand the extent of mobility expected, helping to prevent disputes and clarify the employee’s responsibilities related to work location and travel.
POPULAR SAMPLE Copied 2 times
Mobility Requirements.  The system shall be device agnostic, i.e., performance shall be identical whether the end user is connecting from a desktop or a tablet or any mobile device.  Menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation.  The system shall be designed for optimal performance over slower or unreliable connections.  The system shall be designed as the primary expected input methods through the use of drop-down lists, and context-specific fields.
View SourceView Similar (2)
Mobility Requirements a. Application shall be designed in a way that is device agnostic, i.e., application performance will be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. All menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. c. Alternatively, application may provide alternate interfaces or points of entry depending on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured application for workstations and laptops. d. If offline access is required, the application shall accommodate devices with limited space by downloading the minimum amount of data needed to function without an active connection to the server. e. All forms and menus shall be designed for optimal performance over slower or unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi- Fi, or a tethered internet connection. f. Whenever possible, application shall offload large workloads to the server to accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. g. Forms and menus shall be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. h. Application shall support native functions of the client device, including but not limited to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS location services.
View SourceView Similar (2)
Mobility Requirements. 31 a. Application shall be designed in a way that is device agnostic, i.e., application 32 performance will be identical whether the end user is connecting from a desktop versus a tablet or 33 mobile device. 34 b. All menus and forms shall scale to display appropriately on any device, regardless of 35 screen resolution, aspect ratio, or orientation. 36 // 37 // 1 c. Alternatively, application may provide alternate interfaces or points of entry depending 2 on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured 3 application for workstations and laptops. 4 d. If offline access is required, the application shall accommodate devices with limited 5 space by downloading the minimum amount of data needed to function without an active connection to 6 the server. 7 e. All forms and menus shall be designed for optimal performance over slower or 8 unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi-Fi, or a 9 tethered internet connection. 10 f. Whenever possible, application shall offload large workloads to the server to 11 accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. 12 g. Forms and menus shall be designed with touch interaction as the primary expected 13 input method through the use of drop-down lists, on/off switches, and context-specific fields. 14 h. Application shall support native functions of the client device, including but not limited 15 to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, 16 and GPS location services.
View Source
Mobility Requirements a. Application shall be designed in a way that is device agnostic, i.e., application performance will be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. All menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. c. Alternatively, application may provide alternate interfaces or points of entry depending on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured application for workstations and laptops. County of Orange, Health Care Agency File Folder: M042DR089 Page 12 of 25 Contract MA-042-18011826 d. If offline access is required, the application shall accommodate devices with limited space by downloading the minimum amount of data needed to function without an active connection to the server. e. All forms and menus shall be designed for optimal performance over slower or unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi-Fi, or a tethered internet connection. f. Whenever possible, application shall offload large workloads to the server to accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. g. Forms and menus shall be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. h. Application shall support native functions of the client device, including but not limited to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS location services.
View Source
Mobility Requirements a. Be device agnostic, i.e., application performance shall be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. Menus and forms shall (i) scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation, (ii) be designed for optimal performance over slower or unreliable connections, e.g., VPN, satellite or burst wireless connections, Wi-Fi, or a tethered Internet connection, and (iii) be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. c. Provide for alternate points of entry depending on the end user’s device, e.g., mobile application for tablets, iPads and smart phones versus a full featured application for workstations and laptops.
View Source
Mobility Requirements. 1. The system shall be device agnostic, i.e., application performance shall be identical whether the end user is connecting from a desktop or a tablet or any mobile device. 2. Menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. 3. The system shall be designed for optimal performance over slower or unreliable connections. 4. The system shall be designed with the primary expected input methods using drop- down lists, and context-specific fields. 5. If required for functional use, the application shall support native functions of the client device, including but not limited to on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS virtualization technology, whenever possible, for all new systems.
View Source

Related to Mobility Requirements

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.