User Requirements. School employees, governors, and third party staff using school systems must comply with the requirements below. Failure to do so could possibly mean disciplinary procedures being started. Please note that school systems and users are protected and monitored by security and filtering services to provide safe access to digital technologies. Your behaviour online when in school and on all school devices whether in school or otherwise may be subject to monitoring.
User Requirements. Access is granted to an individual as needed to support business functions for stated business purposes only through user requests in the Banner Authorization Request application (BAR), requiring supervisor and data xxxxxxx approval. Access should be safeguarded by the individual; • Work through appropriate business unit contact to seek training, understand business procedures and/or to make enhancement and application access requests; • Utilize online self-service resources and department IT, if available; • View IT Alerts for scheduled maintenance and outages.
User Requirements. The Service is provided exclusively to common carriers in air transportation. The carrier must have 1) the economic authority required pursuant to 49 U.S.C. § 41101 or § 41301 to provide passenger and/or cargo air transportation services in the United States; 2) licensed the Aviaton 2.0 Operating Standard; 3) registered for the airspace reservation auction; 4) executed the Escrow Agreement for the auction; and 5) made required prepayments as outlined in the registration form.
User Requirements. Please describe your requirements for use of the Argos system in terms of satellite coverage, location accuracy, data throughput time, transmitter power consumption, size and weight, service con- tinuity and reliability, platform compatibility, system access mode, dual GPS/Argos location and, for governmental entities, cost-effec- tiveness. Note: it is the individual agency that determines what is cost- effective for their particular agency. > Besoins de l’utilisateur Veuillez décrire vos besoins d’utilisation du système Argos en ce qui concerne la couverture satellitaire, la précision de localisation et le temps d’accès aux données, la taille, le poids et la consom- mation de l’émetteur, la continuité et la fiabilité du service, la compatibilité des plates-formes, les modes d’accès au système, la localisation duale GPS/Argos et, pour les entités gouvernementa- les, l’optimisation des coûts. Note : chaque agence détermine ses propres critères d’évaluation des coûts. ❏ Polar coverage (> 60° lat.) Couverture polaire (> 60° lat.) ❏ Global coverage Couverture mondiale ❏ Location accuracy Précision de localisation ❏ Data throughput time Temps d’accès aux données ❏ Low transmitter power (< 1 watt) Faible puissance d’émission (< 1 watt) ❏ Transmitter small size and light weight Poids et taille réduits de l’émetteur ❏ Service continuity and reliability Fiabilité et pérennité du service ❏ Platform compatibility Compatibilité des plates-formes ❏ System access Accès au système ❏ Test and evaluation (manufacturer only) Test et évaluation (constructeurs) ❏ Dual GPS/Argos location Localisation duale GPS/Argos ❏ Cost effectiveness Optimisation des coûts ❏ Other / Autre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Requirements. All Pavilion Users, including Briargrove Park or Briar Court property owners or residents, must:
User Requirements a. The Health Plan’s presence on such social networking sites shall include an avatar and/or a username that clearly indicates the Health Plan that is being represented and cannot use any Agency logo or State of Florida seal. When registering for social networking applications, the Health Plan shall use its email address. If the application requires a username, the following syntax shall be used: hxxx://xxxxxxx.xxx/<Healthplan_identifier><username>
User Requirements. Moreover, the table includes references to specific requirements from section 3.2 of D8.1 that each tool addresses. Finally, it should be noted that during the project‘s timeline some web services will be available to PANACEA partners only. Availability of the web services to users outside the consortium will be the subject of task WP2.1, Exploitation. 33 Functionality Tool to be deployed as a WS Host of the WS Month of delivery as a WS License Corresponding D8.1 requirements Monolingual Crawler Monolingual Crawler ILSP T12 Proprietary Req-TOL-100, Req-TOL-111, Req-TOL-120 Bilingual Crawler Bilingual Crawler ILSP T12 Proprietary Req-TOL-100, Req-TOL-110, Req-TOL-111, Req-TOL-120 Boilerplate removal Boilerplate removal tool ILSP/DCU T14 Proprietary Req-TOL-100, Req-TOL-121 Duplicate detection Duplicate detection tool ILSP/DCU T14 Proprietary Sentence Splitter for EL ILSP Sentence Splitter and Tokenizer ILSP T14 Proprietary Req-TOL-100, Req-TOL-130 Tokenizer for EL ILSP Sentence Splitter and Tokenizer ILSP T14 Proprietary Req-TOL-100, Req-TOL-150 POS Tagger and Lemmatizer for EL ILSP FBT Tagger & ILSP Lemmatizer ILSP T14 Proprietary Req-TOL-100 Chunker for EL ILSP Chunker ILSP T20 Proprietary Req-TOL-100 Sentence Splitter for DE LT-SentenceSegmentiser LT T14 Proprietary Req-TOL-100, Req-TOL-130 Sentence Splitter for EN LT-SentenceSegmentiser LT T14 Proprietary Req-TOL-100, Req-TOL-130 Tokeniser for DE LT-Tokeniser LT T14 Proprietary Req-TOL-100, Req-TOL-150 Tokeniser for EN LT-Tokeniser LT T14 Proprietary Req-TOL-100, Req-TOL-150 Lemmatiser for DE LT-Lemmatiser LT T14 Proprietary Req-TOL-210 Lemmatiser for EN LT-Lemmatiser LT T14 Proprietary Req-TOL-210 Decomposer for DE LT-Lemmatiser LT T14 Proprietary Req-TOL-210 TopicIdentifier for DE LT-TopicIdentifier LT T14 Proprietary Req-TOL-210 Term Extraction (mono) DE LT-TermExtract LT T22 Proprietary Req-TOL-210 Term Extraction (mono) EN LT-TermExtract LT T22 Proprietary Req-TOL210 Term Extraction (biling.) EN/DE LT-BiExtract LT T30 Proprietary Req-TOL-230 NE recognition DE LT-Namer LT T30 Proprietary Req-TOL-260 NE recognition EN LT-Namer LT T30 Proprietary Req-TOL-260 Document and sentence segmentation for IT Syn SG ** CNR-ILC T14 Proprietary Req-TOL-100, Req-TOL-130 Tokenizer for IT Syn SG ** CNR-ILC T14 Proprietary Req-TOL-100, Req-TOL-150 POS Tagger and Lemmatizer for IT Syn SG ** CNR-ILC T14 Proprietary Req-TOL-100 Chunker for IT Syn SG ** CNR-ILC T20 Proprietary Req-TOL-100 Dependency Parser for IT Syn SG ...
User Requirements. R1.1.1 An interface is required for the upload of images and data sets into data stores. This should allow images to be imported into a “storage area” D (perhaps a drag and drop interface or list of file names.)
User Requirements. 3.1. Log-in Details: Bidder must provide access log in details to a minimum of 10 users per region. Log-in details must allow users to make their own bookings and provide reference numbers for tracking purposes. Reference numbers should be accessible by any other user. Automated notification of delivery should be linked to the user’s email.
User Requirements. All users must abide by the University’s Acceptable Use Policy and all UAB IT policies, standards, and guidelines that govern the proper use and protection of UAB data and information technology assets while using Tableau. • Tableau publishers must agree to the Tableau Acceptable Use Requirements to create and provide access to visualizations using UAB licensed Tableau software. o If Tableau Creator licenses were purchased outside of the UAB IT Enterprise contract, permission to publish on Tableau server will be granted upon agreement to these requirements. • UAB data classified as Restricted within the Tableau environment is not allowed. If there is a need to publish Restricted data internal to UAB, please log an AskIT ticket so discussions can be held to develop an approved solution. • Obtain consent from the appropriate data xxxxxxx(s) before using UAB data sets. • Publishers are to restrict access to the content published on UAB’s Tableau Server to individuals permitted to see the data being used. Standard Requirements • End-users will reach out to their appointed Project Leader or to the Tableau Administrator for first-level triage of incidents. • End-users will utilize AskIT for first-level triage of creator license service requests. • Users will view the UAB IT Systems Status Page for scheduled maintenance and outages. UAB IT Requirements • Make an effort to provide a solution when end-users need additional assistance. • Deactivate hosts and/or Departments when infection or violation of security policies are identified. • Audit content on UAB’s Tableau Server site to confirm that data are used appropriately. • See the following Appendices for general UAB IT support management standards: o Appendix C: Service Management o Appendix D: Escalation Requests and Process o Appendix E: Service Exceptions o Appendix F: Monitoring Service Performance o Appendix G: Conditions of Services Provided Boundaries of Service • This service excludes all licenses and accounts created by UAB Medicine/Hospital for the Tableau Server managed by HSIS. • UAB IT support will only be provided for UAB IT-delivered services and software. This service excludes all accounts not managed by UAB IT. • This SLA does not cover integration with systems and applications. SERVICE SECURITY Services provided by UAB IT will conform to UAB IT’s security and data classification policies outlined at xxxxx://xxx.xxx.xxx/it/home/policies. If it is determined that any component of the service is ...
