Overall system architecture Sample Clauses

Overall system architecture. Figure 6 provides an overview of the overall system architecture that was developed for the TagItSmart project, indicating the architecture and the integration process of the different components developed in the BehavAuth project as well as the TagItSmart project. The core entities of the overall system architecture are the mobile phone that the user owns and the TagItSmart platform. At the mobile device level, the end user interacts with the different authentication components that are the University of Surrey location based authentication, the University of Padova keystroke based authentication components and the BehavAuth authentication app. All these three components provide some authentication estimation about the users, if they are the actual owners of the devices or not. The results of the different authentication components are forwarded to the Polling Manager that is located also in the mobile device. The Polling Manager is responsible for listening on a common communication channel for the authentication results from the different authentication components. In this way, multiple authentication apps could be added to the mobile device without the need of modifying the initial core structure. The Polling Manager, once it receives authentication results from the different authentication components located on the same device, merges the different authentication results and propagates the outcome of the authentication process to the TagItSmart platform and in particular to the User Repository. The User Repository is a core component of the TagItSmart platform which manages and stores the users information. In this way, the TagItSmart platform is able to keep updated the authentication process, by continuously authenticating its users through these authentication components. Following, there is a brief description of each of the core components that were showcased in Figure 6 and discussed above.
Sample 1
AutoNDA by SimpleDocs
Overall system architecture. The general system overview has been translated into a technical architecture within Task 3.2 “Technical requirement and architectural design”. In order to provide a secure, reliable, scalable and GDPR4 compliant solution, a Cloud based architecture has been chosen. This also allows to focus on the development of end-user requirements while exploiting advances and ready-to-use tools and services. In the following, the benefits of the Cloud computing approach are briefly explained, together with the reasons behind the selection of the Cloud provide for VISCA.
Sample 1

Related to Overall system architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

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

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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

  • Design At no cost to SCE, Seller shall be responsible for:

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

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

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

  • Contract Database Metadata Elements Title: Spencerport Central School District and Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO (2015) Employer Name: Spencerport Central School District Union: Spencerport Paraprofessional Association, New York State United Teachers (NYSUT), American Federation of Teachers (AFT), AFL-CIO Local: Effective Date: 07/01/2015 Expiration Date: 06/30/2018 PERB ID Number: 6253 Unit Size: Number of Pages: 27 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT between the SUPERINTENDENT OF SCHOOLS SPENCERPORT CENTRAL SCHOOL DISTRICT Town of Ogden, Gates, Greece and Parma and SPENCERPORT PARAPROFESSIONAL ASSOCIATION July 1, 2015 - June 30, 2018 TABLE OF CONTENTS ARTICLE PAGE PREAMBLE 1 RECOGNITION 1 ELIGIBLITY FOR BENEFITS 1 ARTICLE 1 DUES DEDUCTION 2 ARTICLE 2 SICK LEAVE 2 ARTICLE 3 PERSONAL LEAVE 3 ARTICLE 4 ILLNESS IN FAMILY 4 ARTICLE 5 FAMILY MEDICAL LEAVE ACT 4 ARTICLE 6 HEALTH INSURANCE 5 ARTICLE 7 WORKER'S COMPENSATION 8 ARTICLE 8 BEREAVEMENT 9 ARTICLE 9 SNOW DAYS AND EMERGENCY CLOSING 9 ARTICLE 10 JURY DUTY 9 ARTICLE 1 WORK YEAR 9 ARTICLE 12 EXTRA HOURS WORKED 10 ARTICLE 13 1:1 AIDES 10 ARTICLE 14 LUNCH & BREAKS 10 ARTICLE 15 LONGEVITY 10 ARTICLE 16 PAID HOLIDAYS 1 ARTICLE 17 SALARY 12 ARTICLE 18 UNUSED SICK DAYS AT RETIREMENT 14 ARTICLE 19 GRIEVANCE PROCEDURE 15 ARTICLE 20 UNPAID LEAVE OF ABSENCE 17 ARTICLE 21 SENIORITY, ASSIGNMENT, AND LAYOFF 18 ARTICLE 22 VACANCY NOTIFICATIONS 20 ARTICLE 23 CREDIT FOR IN-SERVICE COURSES 20 ARTICLE 24 PROBATIONARY PERIOD 21 ARTICLE 25 FLEXIBLE SPENDING ACCOUNT 21 ARTICLE 26 ATTENDANCE INCENTIVE 21 ARTICLE 27 PERSONNEL FILES 22 ARTICLE 28 EVALUATIONS 22 ARTICLE 29 EARLY DISMISSAL - i - 22 ARTICLE 30 DIRECT DEPOSIT 23 ARTICLE 31 PAYROLL DEDUCTION 23 ARTICLE 32 PAYROLL DISTRIUBTION 23 ARTICLE 33 CONFORMITY OF LAW 23 ARTICLE 34 CHAPERONING AND PROCTORING 23 ARTICLE 35 BUS ATTENDANTS 24 ARTICLE 36 DURATION OF AGREEMENT 24 P R E A M B L E The Spencerport Central School District and the Spencerport Paraprofessional Association desire to enter into the agreement in order to effectuate the provisions of the Public Employees' Fair Employment Act and to encourage and increase the effective and harmonious work relationship between the district and the paraprofessionals who comprise the unit members within the bargaining unit represented by the association. The association hereby reaffirms that it will not engage in any strike, or cause, instigate, encourage, assist or condone any strike. The district recognizes the right of these unit members to organize and to bargain collectively through the association on such matters as salaries, hours and other terms and conditions of employment. The agreement is made and entered into on the 23rd day of June, 2015, by and between the Superintendent of Schools, SPENCERPORT CENTRAL SCHOOL DISTRICT, Spencerport, New York, hereinafter referred to as the "district," and the unit members of this unit of aforementioned school district, represented by the SPENCERPORT PARAPROFESSIONAL ASSOCIATION, hereinafter referred to as the "association." RECOGNITION Pursuant to the New York State Public Employees Fair Employment Act, the Board of Education of Spencerport Central School District has recognized the Spencerport Paraprofessional Association, hereinafter referred to as "association," as the exclusive negotiating representative for all Accompanists, Bus Attendants, Licensed Practical Nurses, Microcomputer Maintenance Technicians, School Aides and Teacher Aides employed by said district. ELIGIBILITY FOR BENEFITS All unit members employed by the District on June 30, 2000, while serving in a 27.5 (or more) hours per week position, will be considered as “full time” and will receive all of the benefits of unit members working 30 or more hours per week as detailed in Articles 2, 3, 4, 6, and 12 of this agreement. All unit members hired after June 30, 2000 are eligible for all of the benefits as detailed in Articles 2, 3, 4, 6, and 12 of this agreement and considered “full time” when serving in a 30 (or more) hours per week position. Any unit member hired after July 1, 2000 in a 30 (or more) hours per week capacity who is involuntarily reduced to at least 27.5 hours per week will receive the benefits associated with “full time” employment (Articles 2, 3, 4, 6, and 12). Spencerport Paraprofessional Association - 1 - July 1, 2012 - June 30, 2015

  • Construction Phase Services 3.1.1 – Basic Construction Services

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