Data Consumption Sample Clauses
Data Consumption. RMH shall be responsible for "Thoroughly ---------------- Utilizing" the MCI Data and shall follow MCI's guidelines with respect to MCI Data consumption. "Thoroughly Utilizing" means that RMH's Call attempts (i.e., Calls dialed) and Completes (leads dispositioned out of the system by a TMR, i.e., not called again during a Call Campaign) per Work Hour fall within plus or minus [REDACTED DUE TO REQUEST FOR CONFIDENTIAL TREATMENT] of the Call attempts and Call completes per Work Hour achieved by the Internal Centers .
Data Consumption. RMH shall be responsible for “Thoroughly Utilizing” the MCI Data and shall follow MCI’s guidelines with respect to MCI Data consumption. “Thoroughly Utilizing” means that RMH’s Call attempts (i.e., Calls dialed) and Completes (leads dispositioned out of the system by a TMR, i.e., not called again during a Call Campaign) per Work Hour fall within plus or minus [*] of the Call attempts and Call completes per Work Hour achieved by the Internal Centers.
Data Consumption. To surface the data stored in the Azure Data Lake and/or Cosmos DB, insight will create an oAuth2- secured REST API. This API can be called by the client visualization application through standard REST HTTPS API calls. 2 types of data will be exposed by this API: Standard Data. This is non-geospatial data. This data will be made available through the standard JSON format for Web Services. Geospatial data. Geo-spatial data will be made available in the standard Keyhole Format Language (KML) format, which is a universally supported format for geo-spatial data. Event Hubs Cosmos DB Web Sockets Interface KML, JSON, etc.. ESRI React‐ArcGIS Map Azure Cloud HeatMap charting component An overview of the REST API and its consuming components is shown below: