API Support. Motorola will use commercially reasonable efforts to maintain the Application Programming Interface (“API”) offered as part of the CommandCentral Services during the term of this Addendum. APIs will evolve and mature over time, requiring changes and updates. Previous versions of APIs will be supported for a minimum of a 6 month time period after new version is introduced. If support of the API is no longer a commercially reasonable option, Motorola will provide reasonable advance notification to Customer. If an API presents a security risk to the Subscription Services or the Solution, Motorola will discontinue an API without prior warning.
API Support. SISW will provide advice and guidance on how to use the API’s delivered with the Polarion Software.
API Support. As part of SB's obligations under this Agreement, -----------
(i) the SB API's shall contain all functionality reasonably necessary to support, use, and interoperate with (including, without limitation, to use the principal functions of) the [**] Database in accordance with this Agreement; provided, however, -------- ------- that, to the extent that such SB APIs are insufficient to enable such interoperability, SB shall modify such APIs, as promptly as commercially reasonable, to enable such interoperability; (ii) SB will provide AOL with all APIs reasonably necessary to allow the AOLYP User Interface to interoperate with the YP Databases and the DLA Platform and to afford AOL (and AOL Users) with access to the [**] Database and the DLA Platform in accordance with this Agreement, as further set forth in Exhibit C; and (iii) no modifications by SB to the DLA Platform or the YP Databases shall materially impair or degrade any of the foregoing functionality, provided that such -------- obligation in this clause (iii) shall not apply to modifications requested by AOL outside the scope of the All-In Services. During the License Period, to the extent reasonably necessary for AOL to modify, develop, add, delete or use any Level II Data Enhancements in connection with the functionality or features of the DLA Platform, the [**] Database, the AOL YP User Interface and/or the YP Product, upon AOL's request, SB shall develop and provide to AOL APIs to the DLA Platform, the YP Databases and/or AOL YP Product (as applicable) so that such Level II Data Enhancements can interoperate with (including, without limitation, use the principal functions of) the DLA Platform, the YP Databases and/or the YP Product.
API Support. As part of AOL's obligations under this Agreement, ----------- the AOL API's shall contain all functionality reasonably necessary to support, use, and interoperate with (including, without limitation, to use the principal functions of) the [**] Database, AOL YP User Interface, AOL Features or Functionality and aspects of the [**] Database as incorporated therein in accordance with this Agreement.
API Support. Motorola will use commercially reasonable efforts to maintain its Application Programming Interface (“API”) sold in connection with any Mobile Video System. APIs will evolve and mature over time, requiring changes and updates. Motorola will use reasonable efforts to continue supporting any version of an API for six (6) months after such version is introduced, but if Motorola determines, in its sole discretion, to discontinue support of an API for any reason, Motorola will provide reasonable advance notification to DIR Customer. If an API presents a security risk, Motorola may discontinue an API without prior notice.
API Support. Described in the MCA.
API Support. Motorola will use commercially reasonable efforts to maintain the Application Programming Interface (API) offered as part of the CommandCentral Services during the term of this Agreement. APIs will evolve and mature over time, requiring changes and updates. Previous versions of APIs will be supported for a minimum of 6 month time period after new version is introduced. If support of the API is no longer a commercially reasonable option, Motorola will provide reasonable advance notification to Customer. If an API presents a security risk to the Services or the Solution, Motorola will discontinue an API without prior warning 13.5. COMMANDCENTRAL SERVICE LEVEL TARGETS Commercially reasonable efforts will be made to ensure monthly availability of 99.9% with the exception of maintenance windows. There are many factors beyond Motorola’s control that may impact Motorola’s ability to achieve the goal, including but not limited to a Force Majeure. Additionally, Motorola will strive to meet the response time goals set forth in the table below. RESPONSE TIME GOALS SEVERITY LEVEL DEFINITION RESPONSE TIME 1 Total System Failure - occurs when the System is not functioning and there is no workaround; such as a Central Server is down or when the workflow of an entire agency is not functioning. This level is meant to represent a major issue that results in an unusable System, Subsystem, Product, or critical features. No work around or immediate solution is available. Telephone conference within 1 Hour of initial voice notification 2 Critical Failure - Critical process failure occurs when a crucial element in the System that does not prohibit Telephone conference within 3 Business Hours continuance of basic operations is not functioning and there is usually no suitable work-around. Note that this may not be applicable to intermittent problems. This level is meant to represent a moderate issue that limits a Customer’s normal use of the System, Subsystem, Product or major non-critical features. of initial voice notification during normal business hours 4 Inconvenience - An inconvenience occurs when System causes a minor disruption in the way tasks are performed but does not stop workflow. This level is meant to represent very minor issues, such as cosmetic issues, documentation errors, general usage questions, and product or System Update requests. Telephone conference within 2 Standard Business Days of initial notification 13.6. MAINTENANCE Scheduled Maintenance will be perf...
API Support. Netcentives hereby warrants that for so long as AOL or its affiliates have rights under the License, Netcentives agrees that the Loyalty Network Infrastructure (or any successor thereto) shall contain all functionality reasonably necessary to support and use the APIs provided to AOL or its affiliates by Netcentives, and agrees that no modifications by Netcentives to the Loyalty Network Infrastructure shall materially impair or degrade such functionality. To the extent reasonably necessary for AOL to modify, develop, add, delete or use any functionality or features of the Loyalty Network Infrastructure, Payment System Software or Rewards Broker Software in connection with the development of any Additional Modifications pursuant to Section 13(a)(iii) hereof, Netcentives shall provide to AOL APIs to the Loyalty Network Infrastructure, Payment System Software and/or Reward Broker Software (as applicable) so that such Additional Modifications can interoperate with (including use of the principal functions of) the Loyalty Network Infrastructure, Payment System Software or Rewards Broker Software; provided, however, that, to the extent that such APIs are insufficient to enable such interoperability, Netcentives shall modify, as promptly as commercially reasonable, the APIs (to be paid by AOL in accordance with the technical customization provisions of Section 9 hereof), the Loyalty Network Infrastructure, Payment System Software or Rewards Broker Software to enable such interoperability. Netcentives shall own all additions and extensions to such API (but not the Additional Modifications, which shall be owned by AOL) and such additions and extensions shall form part of the License granted by Netcentives to AOL and its affiliates hereunder.
(i) Other. The Parties will agree to negotiate in good faith the other relevant terms of the License (e.g., terms relating to AOL building and/or implementing a replacement loyalty network infrastructure during a wind-down period using the APIs related to the Loyalty Network Infrastructure) as part of the Supplemental Agreements. Part 6 *** 12. ***
API Support. Barcode Scanning Solution must ensure API supports REST web service. Yes Data at rest includes information that resides in persistent storage in files, disks, blobs, tables,relational and object databases. InThing’s platform primarily employs relational data (such as SQL Azure, PostgreSQL Azure), files, and blobs as storage. Data encryption at rest is typically required for sensitive business data that primarily resides in relational storage. Depending on the customer's need, data encryption at rest is available across all services. Transparent Data Encryption (TDE) is used to encrypt data in real‐time using Database Encryption Key (DEK) stored in the database boot record. Unless specifically desired, encryption keys are managed by respective cloud service providers and are not accessible to either InThing or its customers
API Support. In general, each API used by the user application for the dynamic reconfiguration must share the same architecture as shown in Figure 4. The API must implement the following operations related directly to reconfiguration support: Operation Description init Initialization of reconfiguration subsystem stop Stops the operation of the reconfigurable component cooperatively (after end of operation cycle) and disable its IO interfaces kill Stops the reconfigurable part immediately and disable its IO reconfigure Loads new configuration into reconfigurable component start Enables IO and starts execution of reconfigurable section In case of AMP platform on Zynq processor, the reconfiguration of EdkDSP accelerator is performed by writing to its firmware memory. The speed of the memory interface is then given by the clock frequency on the memory port, i.e. CLK_FREQ*4 MB/s (400MB/s at 100MHz clock for example). Similarly, the reconfiguration of the PL is executed using DMA & PCAP interface of the Zynq. Its speed is given in the non-encrypted case as 400MB/s (100 MHz clock). API operation Implementation Firmware reconfiguration PL reconfiguration init PcapInit() stop PLstop(); kill wal_reset_worker() XXxxxxx(); reconfiguration wal_set_firmware() PcapLoadPartition() start wal_start_operation() PLstart(); The Zynq platform with asymmetric multiprocessing has been documented in the electronically published application notes [16] and [17]. The corresponding evaluation packages with the precompiled designs can be downloaded from [18] and [19]. UTIA is already supporting the mature Xilinx ISE 14.5 design flow in [16], [18] and the new state of the art Xilinx Vivado 2013.4 design flow [17], [19]. Firmware based dynamic reconfiguration of floating point accelerators is already implemented in these two evaluation packages and it is already evaluated. The dynamic reconfiguration of the Zynq programmable logic part will be implemented, documented and tested in the second year of the EMC2 project. Software Layer User App Configuration data Reconfiguration API Reconfiguration Controller Reconfigurable Component Hardware Layer
