OpenReq Interfaces Sample Clauses

OpenReq Interfaces. The following table describes user studies and related data collected for analysis purposes which are used to develop the OpenReq platforms and algorithms and publish corresponding research results. The usage of this data for the purposes of documenting OpenReq results in the OpenReq knowledge base is described thereafter. Planned studies & resulting data WP Task Study description Task 6.1 Design OpenReq user interface approach Evaluation of the OpenReq User Interfaces by means of Usability Studies. These studies will be conducted with students at TU Graz, User-Communities of the trial partners and within the scope of questionnaires and prototype evaluations and supported by anonymous communities and micro worker platforms. Resulting Data: Anonymous user feedback on usability questionnaires such as SUS. Task 6.2 Continuous integration No user studies and data collection are planned in this context. Task 6.3 Development of the OpenReq integrated version and API No user studies and data collection are planned in this context. Task 6.4 Integration of OpenReq in issue trackers & collaboration tools No user studies and data collection are planned in this context. Task 6.5 OpenReq cloud platform and services No user studies and data collection are planned in this context. Task 6.6 Integration of OpenReq in requirements tools No user studies and data collection are planned in this context (usability studies are covered in Task 7.3). Task 6.7 Open-Call technical supervision No user studies and data collection are planned in this context. OpenReq data used in OpenReq knowledge base Scientific publications representing outcomes of the mentioned user studies and beyond are stored in the OpenReq knowledge base and are publicly accessible. The accessibility of deliverables (related to WP6) will follow the policy defined in the OpenReq proposal. Technical reports will be publicly accessible except that partners define a different policy (which is the exception of the rule). Source Code will be made publicly accessible always taking into account the policy defined in the OpenReq proposal. Running prototypes hosted in Engineering premises and potentially containing data from knowledge base will not be publicly available. All such data will be hosted only in Engineering data center located in Europe, and will not be accessible from outside, unless otherwise agreed with the consortium. All data stored in the Virtual Machine used to host OpenREQ cloud services will be protec...
Sample 1Sample 2
AutoNDA by SimpleDocs
OpenReq Interfaces. The OpenReq Interfaces will provide open, unified interfaces for easily integrating OpenReq into external tools in form of connectors (see Figure 1). Examples for high-level interfaces include among others (a) Register/Unregister for Recommendation, (b) push context, (c) display recommendation, (d) open artefact and (e) configure. As a proof of concept, we will integrate these interfaces in the tools used by the OpenReq industry partners and Open Source communities within the scope of the trial implementations. To assure the accessibility of OpenReq in Cloud contexts, OpenReq will be built upon the following service infrastructure.
Sample 1

Related to OpenReq Interfaces

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

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

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

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

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

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

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