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 Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

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

  • Building Commissioning Services The Owner may provide as a part of its testing services the Building Commissioning services involving the project’s HVAC and exhaust systems, temperature control systems, fire detection and alarm systems, emergency power and lighting system, fire suppression system, security locks and security locking control systems, food service equipment (if applicable), and laundry equipment (if applicable). In the event the Using Agency’s Program specifies additional commissioning services, the Owner shall procure such services as well. The Owner, through its Executive Administrator, may engage an independent Commissioning Authority. It is the intent of this Article that the Commissioning Authority enforce the requirements mentioned herein and certify that the systems and equipment listed all function properly prior to the initiation of each final inspection.

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

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