Data Layer Sample Clauses

Data Layer. Also known as a Feature Class, is a group of geographic features that reside in a table of information with corresponding locations on the earth (map) represented as either points, lines, or polygons.
Sample 1Sample 2
AutoNDA by SimpleDocs
Data Layer. MDStore Service The MDStore needs to improve its stability in the presence of large files and needs optimization in the file indexing process. Index Services Two implementations of the Index Service are available, one from ICM (Java-based, based on Yadda index technology developed at ICM Labs) and one from UniBi (Per-based, built on top of Lucene). Both implementations need “search refinement” to be better specified and implemented. UniBi requires instead a re-development in Java language. The need of such implementation and its delivery in D-NET 1.0 or D-NET 2.0 is to be evaluated based on the human and time resources available to the partner.
Sample 1
Data Layer. All microservices in this layer (Figure 6) have the goal to persist the raw data necessary to run the microservices of the recommendation layer but also to store some intermediate results of the recommendation layer for easier and faster execution (e.g., avoid training a machine learning model every time it is needed). Figure 7 includes an initial overview of how the data will be organized — i.e., the data model for the stakeholders’ recommender engine. As with the architecture, we do not discard that this model will evolve as the implementation progresses. The data model presented in Figure 7 is compliant with the first version of the OpenReq ontology presented in deliverable D5.1. Further details about the mapping of the data model in Figure 7 and the OpenReq ontology will be presented in further deliverables (specifically, in D5.4). Part 1 of the model is formed by the raw data necessary to run the microservices of the recommendation layer. That includes information about the requirements projects (i.e., Project, Requirement, Requirement Property, and Dependency), from where this data came from (in case it was imported to the system) (i.e., Issue, Social Media, and Requirement File), and the stakeholders involvement (i.e.., Stakeholder, Participation31, and Requirement Rating). The information about Requirement and Requirement Property will come from the Milla microservice of WP5, while the information Issue, Social Media, and Requirement File will come from the Issues Tracker Data, Social Media Data and Requirement Files microservices of WP2. Part 2 of the model includes intermediate results of the recommendation layer. This part of the model, together with the services of this layer, are explained in the following paragraphs. Data Manager microservice This microservice is the entry point for the storage and retrieval of data, orchestrating all the actions needed in relation to these tasks (i.e., this microservice will decide what should be done and what other services to use from this layer). On one hand, it routes data from the recommendation layer to the appropriate microservice. On the other, it stores the data used by recommender systems and machine learning algorithms in the recommendation layer. From a data model perspective (see Figure 7), Part 1 of the model represents such abstracted data. The Data Manager helps decoupling the raw data from the models data. One challenge is that the Data Manager needs to be updated once a new type of machine ...
Sample 1

Related to Data Layer

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

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

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

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

  • MOBILE DATA COMPUTERS 20 1. As part of the law enforcement services to be provided to CITY, COUNTY 21 has provided, or will provide, mobile data computers (hereinafter called 22 “MDCs”) that are or will be mounted in patrol vehicles and motorcycles, 23 designated by COUNTY for use within CITY limits.

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

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

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.

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