Component and interfaces Sample Clauses

Component and interfaces. Name Noona Related use cases All Due Date Implemented. Location source code Confidential. Responsibilities/ Functionality Noona is responsible for collecting the questionnaire data and enabling the clinic to be able to export the data. The main goal is to provide the psychological scales and other relevant eCRF forms to be filled in by the patients. Provided Interfaces [Interfaces implemented by the component] Interface Type Description Patient UI GUI Patient can track their questionnaires Clinic UI GUI Clinic can request a data export Required Interfaces [Interfaces used by the component] Interface Type Description Data Anonymizer API REST REST API to (semi-)automatically anonimyze and push data to the BOUNCE data lake/semantic tier Implementation Java, Kotlin, Angular, Typescript Third party Libraries BACKEND Library License Apache Avro Apache-2.0 Jersey CDDL Version 1.1 JAX-RS API CDDL Version 1.1 libphonenumber Apache-2.0 java-apns BSD-3-Clause Xxxxxxx JSON Processor Apache-2.0 Xxxxxxx Databind Apache-2.0 Joda Time Apache-2.0 Eclipse Link Eclipse Public License - v 1.0, Eclipse Distribution License - v 1.0 PostgreSQL JDBC driver BSD-3-Clause Apache Commons Beanutils Apache-2.0 jsonrpc4java MIT jade4j MIT Apache PDFBox Apache-2.0 Apache Commons FileUpload Apache-2.0 Metadata Extractor Apache-2.0 Amazon AWS Java SDK KMS Apache-2.0 GeoIP2 Java API Apache-2.0 FRONTEND Library License Angular: common, compiler, core, forms, http, platform- browser, platform-browser-dynamic, router, upgrade MIT AngularJS MIT AngularJS Animate MIT AngularJS Cookies MIT AngularJS JSON-RPC WTFPL AngularJS Moment MIT AngularJS Route MIT AngularJS Sanitze MIT AngularJS Scroll MIT Angular Tooltips MIT AngularJS Touch MIT AngularJS UI-router MIT Angular-toastr MIT Bootstrap MIT Bootstrap datepicker Apache-2.0 core-js MIT D3 BSD-3-Clause JQuery MIT JQuery transform MIT Moment MIT Moment timezone MIT ng-showdown BSD-3-Clause @ngrx/core MIT @ngrx/store MIT @ngrx/store-devtools MIT Photoswipe MIT RxJS Apache-2.0 Showdown BSD-3-Clause stacktrace-js The Unlicense loadsh MIT Zone.js MIT cookie-storage MIT fastclick MIT tinygradient MIT ngrx-store-logger MIT url-join MIT Xxxxxxx:xxxxxxx-plugin-camera,xxxxxxx-android,xxxxxxx- ios, xxxxxxx-plugin-device, xxxxxxx-plugin-file, xxxxxxx- plugin-media, xxxxxxx-plugin-media-capture, xxxxxxx- plugin-network-information, xxxxxxx-plugin-splashscreen, xxxxxxx-plugin-statusbar, xxxxxxx-plugin-vibration, xxxxxxx-plugin-whitelist Apache-2.0 Xxxxxxx-hot-c...
Sample 1
AutoNDA by SimpleDocs
Component and interfaces. The Access Controller is the component responsible for controlling the access to the different resources of the platform, like the platform’s datasets, added value services and internal components offered through the platform such as the decision support. The Access Controller functionality follows the main principles defined by the Attribute-Based-Access-Control8 (ABAC) paradigm, which is a logical access control model, where access to objects is controlled by evaluating rules (policies) against the attributes of the entities (subject and object) actions and the environment relevant to a request. More specifically, the Access Controller has two main functionalities:  It controls the access to the platform’s datasets, added value services and internal components.  It manages the process of requesting and granting access to the platform’s aforementioned resources. The implementation of the Access Controller which follows the ABAC paradigm comprises of three main modules:  The Policy Enforcement Point (PEP), which acts as the endpoint that receives the access requests to the different resources.  The Policy Information Point (PIP), which retrieves the required attributes of the resources and the active policies.  The Policy Decision Point (PDP), which evaluates the access requests based on the resources’ attributes and the policies and produces a decision to grant or deny access.
Sample 1
Component and interfaces. Τhe web based BOUNCE Model Repository (MR) will store the overall prediction model and the resilience trajectory prediction model. The key entities of the MR are the model, the parameters, the properties and the files (see Figure 20). The model entity includes all the descriptive information of a model, the parameters entity contains all the information regarding the input parameters needed for the execution of the model (data type, units, description etc.) as well as the output data of a model (description, type etc.), the property entity contains the properties that could characterize a model (e.g. statistical and machine learning techniques that were used) and the file entity contains the files linked to the model (e.g. several versions of binaries).
Sample 1

Related to Component and interfaces

  • Technical and Interconnection Requirements 2.1 Consumer agrees that his Rooftop Solar PV System and Net Metering System will conform to the standards and requirements specified in the Policy, Regulations and Supply Code as amended from time to time.

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection.

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • BACKGROUND AND INTRODUCTION The Federal-aid Highway Program (FAHP) is a federally-assisted program of State-selected projects. The Federal Highway Administration (FHWA) and the State Departments of Transportation have long worked as partners to deliver the FAHP in accordance with Federal requirements. In enacting 23 U.S.C. 106(c), as amended, Congress recognized the need to give the States more authority to carry out project responsibilities traditionally handled by FHWA. Congress also recognized the importance of a risk-based approach to FHWA oversight of the FAHP, establishing requirements in 23 U.S.C. 106(g). This Stewardship and Oversight (S&O) Agreement sets forth the agreement between the FHWA and the State of Florida Department of Transportation (FDOT) on the roles and responsibilities of the FHWA and the State DOT with respect to Title 23 project approvals and related responsibilities, and FAHP oversight activities. The scope of FHWA responsibilities, and the legal authority for State DOT assumption of FHWA responsibilities, developed over time. The U.S. Secretary of Transportation delegated responsibility to the Administrator of the FHWA for the FAHP under Title 23 of the United States Code, and associated laws. (49 CFR 1.84 and 1.85) The following legislation further outlines FHWA’s responsibilities: • Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991; • Transportation Equity Act for the 21st Century (TEA-21) of 1998; • Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) of 2005; and • Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012 (P.L. 112-141). The FHWA may not assign or delegate its decision-making authority to a State Department of Transportation unless authorized by law. Xxxxxxx 000 xx Xxxxx 00, Xxxxxx Xxxxxx Code (Section 106), authorizes the State to assume specific project approvals. For projects that receive funding under Title 23, U.S.C., and are on the National Highway System (NHS) including projects on the Interstate System, the State may assume the responsibilities of the Secretary of the U.S. Department of Transportation under Title 23 for design, plans, specifications, estimates, contract awards, and inspections with respect to the projects unless the Secretary determines that the assumption is not appropriate. (23 U.S.C. 106(c)(1)) For projects under Title 23, U.S.C. that are not on the NHS, the State shall assume the responsibilities for design, plans, specifications, estimates, contract awards, and inspections unless the State determines that such assumption is not appropriate. (23 U.S.C. 106(c)(2)) For all other project activities which do not fall within the specific project approvals listed in Section 106 or are not otherwise authorized by law, the FHWA may authorize a State DOT to perform work needed to reach the FHWA decision point, or to implement FHWA’s decision. However such decisions themselves are reserved to FHWA. The authority given to the State DOT under Section 106(c)(1) and (2) is limited to specific project approvals listed herein. Nothing listed herein is intended to include assumption of FHWA’s decision-making authority regarding Title 23, U.S.C. eligibility or Federal-aid participation determinations. The FHWA always must make the final eligibility and participation decisions for the Federal-aid Highway Program. Section 106(c)(3) requires FHWA and the State DOT to enter into an agreement relating to the extent to which the State DOT assumes project responsibilities. This Stewardship and Oversight Agreement (S&O Agreement), includes information on specific project approvals and related responsibilities, and provides the requirements for FHWA oversight of the FAHP (Oversight Program), as required by 23 U.S.C. 106(g).

  • Vaccination and Inoculation (a) The Employer agrees to take all reasonable precautions, including in-service seminars, to limit the spread of infectious diseases among employees.

  • Technical Characteristics The Participating Generator has provided to the CAISO in Schedule 1 the required information regarding the capacity and operating characteristics of each of the Generating Units listed in that schedule. Pursuant to Sections 8.9 and 8.10 of the CAISO Tariff, the CAISO may verify, inspect and test the capacity and operating characteristics provided in Schedule 1.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • CONTRACTOR PORTABLE DEVICES Contractor shall not place Data on any portable Device unless Device is located and remains within Contractor’s CONUS Data Center. For Authorized Users subject to ITS policies, the Data, and/or the portable device containing the Data, shall be destroyed in accordance with applicable ITS destruction policies (ITS Policy S13-003 Sanitization/Secure Disposal and S14-003 Information Security Controls or successor) when the Contractor is no longer contractually required to store the Data. TRANSFERRING OF DATA General Except as required for reliability, performance, security, or availability of the services, the Contractor will not transfer Data unless directed to do so in writing by the Authorized User. All Data shall remain in CONUS. At the request of the Authorized User, the Contractor will provide the services required to transfer Data from existing Databases to physical storage devices, to facilitate movement of large volumes of Data. The Authorized User may require several Cloud providers to share or transfer Data for a period of time. This will be provided for in the Authorized User Agreement or shall be assumed to be limited to a six month duration. Transfer of Data at End of Contract and/or Authorized User Agreement Term At the end of the Contract and/or Authorized User Agreement term, Contractor may be required to facilitate transfer of Data to a new Contractor. This transfer must be carried out as specified by the Authorized User in the Authorized User Agreement. Transfer of Data; Charges Contractor cannot charge for the transfer of Data unless the charges are provided for in response to an Authorized User RFQ. Transfer of Data; Contract Breach or Termination Notwithstanding Section 3.6.3, in the case of Contract breach or termination for cause of the Contract, all expenses for the transfer of Data shall be the responsibility of the Contractor.

  • Points of Interconnection As and to the extent required by Section 251 of the Act, the Parties shall provide Interconnection of their networks at any technically feasible point as described in Section 4.3. To the extent the originating Party’s POI is not located at the terminating Party’s relevant IP, the originating Party is responsible for transporting its traffic from it’s POI to the terminating Party’s relevant IP.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!