Technical Implementation. 16.1 Upon Google’s request, Opera shall provide Google with the latest version of the Opera Desktop Browser, Opera Mini Browser and/or the Opera Mobile Browser for testing and evaluation purposes [***].
16.2 Google will assign a technical representative to Opera, who will provide reasonable assistance to Opera with the implementation of the Opera Desktop Browser, Opera Mini Browser and/or Opera Mobile Browser in accordance with this Agreement. The Google technical representative will only be responsible for providing assistance to Opera, and will not provide any direct support to End Users or any other third party. Opera will assign a technical representative to Google who will act as the primary contact for Google in any technical or support issues. Each party shall use reasonable endeavours to respond to technical and support queries within seven (7) days of receiving the query.
16.3 Opera shall provide support services with respect to each Included Opera Browser and/or the Existing Install Base to End Users as generally available at its own expense. Google will make available support to End Users as generally available for all users of the same Google Products, applications or services distributed organically by Google.
16.4 If Google modifies the Google Branding Guidelines, the Google Technical Protocols or any other technical requirements and such modification requires action by Opera, Opera will implement the applicable changes no later than thirty (30) days from receipt of notice from Google, or such longer time frame as may be agreed by Google in writing (including by email).
16.5 Google may require Opera to make immediate fixes or changes to the implementation of any Included Opera Browser, the Existing Install Base or Search Access Point if a fault in such implementation could reasonably cause or is causing an interruption or degradation of the applicable Google Product and Opera shall make such fixes or changes as soon as reasonably possible.
Technical Implementation. The Grantee and MO complete technical work necessary to enable HIE services. For the eligible inpatient hospital/facility onboarding grant or eligible outpatient practice or other outpatient provider organization onboarding, Grantee must complete the development, implementation, and configuration of technical capabilities to permit IHE standard interoperability between the Grantee’s systems and the MO’s EHR. For the portal onboarding grant, this includes arranging for and implementing web services for the MO, and any work to modify or extend the HIO’s portal. For all grants, implementation includes the analysis work to support workflow integration of HIE capabilities by the MO. The Grantee and MO must complete the Technical Implementation Attestation and Survey form attached hereto as Attachment A to confirm completion of this phase.
Technical Implementation. During Year 5, work in the two main technical areas, capacity building and research, will begin. The RedLEI team will, in early 2018, start to develop the research lines for RedLEI. These will include for national level research to be funded by RedLEI and for the signature research study, which will be designed and carried out by personnel from all of the founding members under the under the leadership of the RedLEI technical staff. Additionally, a key and complementary focus in the area of research in Year 5 will be the research grants program funded by URC/Global Reading Network, described in more detail in 4.2 below. The RedLEI team will also, in the first quarter of calendar year 2018, design the methodology to assess training and capacity building needs in the founding partners, and then will carry out this participatory research. This will be used to form the basis of workshops that will be held later in Year 5, focused on institutional development and capacity building with founding members.
Technical Implementation i. PredPol to conduct a kickoff meeting or conference call with appropriate Client staff (as identified by the Client) – with 7 days of receiving the signed Agreement;
ii. Client to complete an informational form – within 7 days after the kickoff meeting;
iii. Upon receipt of the Client’s completed information form, PredPol will send installation instructions to Client;
iv. Client must complete the installation instructions for the Data Pipe and complete the online setup form with 30 days of the agreement Effective Date. PredPol staff will be available for support as needed; and
v. Upon successful installation of Data Pipe and completion of setup form, PredPol will complete initial data processing. The PredPol Service will generally be available to Client within two weeks from the completion of this step. Successful completion of this step is contingent on the Client confirming that the data mapping is correct.
Technical Implementation. (1) After the end of the respective tenancy period, the tenant can be sent an email in which the tenant receives a link to the review page related to the holiday property they have just rented. With agency bookings for which the booking process is regularly transacted by the service provider, the tenant receives an invitation from the service provider. With so-called advertisements, with which the landlord regularly transacts the booking process in person, the landlord has the opportunity to invite the tenant to submit a review via email.
(2) In his/her capacity as an agency client, the landlord receives a client number upon conclusion of the agency contract. Additionally, the landlord will receive a password on request so that he/she can use the access data to reach the landlord area. On completion of the rental period the tenant will automatically receive an invitation to submit a review. After the submission of a review with comments, the landlord has the opportunity to answer the comments in the log-in area.
(3) If the landlord is also an advertiser he/she will receive a client number and a password with the upload of an advertisement. This access data gives the landlord the opportunity to request a review from the holidaymaker after completed rental contracts. After the submission of a review with comments, the landlord is able to answer the comments in the log-in area.
Technical Implementation. 1. Contractor shall attend OC-MEDS Taskforce meetings to aid in understanding the information management needs of Orange County EMS System participants.
2. Contractor shall assist with the technical implementation of each of the following OC-MEDS modules: o OC-MEDS EMS Service Bridge, o OC-MEDS Hospital Dashboard, o OC-MEDS Field Bridge, o OC-MEDS Field Bridge Xpress, o OC-MEDS STEMI Registry, and o OC-MEDS Stroke Registry.
3. Contractor shall complete each OC-MEDS module based on the timeline specified in the table below: Deliverables Title Projected Start Date Projected End Date 1 OC-MEDS Service Bridge Implementation 01/012/20135 12/301/20136 2 OC-MEDS Hospital Dashboard Implementation 01/012/20135 12/301/20136 3 OC-MEDS Field Bridge Implementation 01/012/20135 12/301/20136 4 OC-MEDS Field Bridge Xpress Implementation 01/012/20135 12/301/20136 5 OC-MEDS STEMI Registry Implementation 01/012/20135 12/301/20136 6 OC-MEDS Stroke Registry Implementation 01/012/20135 12/301/20136
Technical Implementation. 4.1 The object of purchase shall be manufactured on the basis of technical standards and norms customary in the industry, taking into account the valid "Technical Implementation", which is available for download on xxxxxx.
Technical Implementation. Company will operate in good faith to implement any reasonable technical requirements requested by Microsoft that do not impose an undue burden upon Company.
Technical Implementation. The Tools Catalogue is one of the services that Presto4U has now published through the existing PrestoCentre online platform. The PrestoCentre online platform is built as an open-source Drupal7 platform and can handle core complex user permissions and workflows. By choosing Drupal as platform, the Tools Catalogue has at its disposal an expandable and flexible setup for the future of the service, which is especially important towards the Market Place integration later in the project. It also continued from the already implemented Community of Practice personalisation and filter features from Deliverable
Technical Implementation. The prototype application shows the potential of automatically enriching television content for an enriched end-user experience. The chosen scenario allows a wide variety of enrichment techniques to be deployed: techniques to link AV content to Wikipedia articles, named entity recognition and linking of person, location and art style names, feature detection techniques to link close ups of art objects to visually similar objects in the Europeana data set, metadata based linking, etc. For this prototype demonstration the front-end is built for web browsers, using HTML5 and JavaScript for the implementation of the interactive user interface. This front-end works on top of the existing LinkedTV platform used for the project, an XML based service-oriented platform where audiovisual content is stored, processed into different formats and qualities and made accessible through a RESTful web service. It's capable of storing and manipulating the audiovisual content, metadata and fragment [6] based annotations of the enriched broadcast. In addition, the prototype shows how the linked content can be unobtrusively integrated into a simple but aesthetically attractive TV interface that can be used both during and after the original broadcast, and thus forms a potential to make archived content more attractive. It was possible to control the prototype using a default apple remote control.
