Software and Tools. (A) As between the Parties, Supplier is the exclusive owner of the Supplier Software and Supplier Tools and WaMu Group Companies will have no rights or interests in the Supplier Software or Supplier Tools except as set forth in this Agreement.
Software and Tools. Client will provide to Sitel with remote access to and use of the Client technical service and customer service systems Client uses in the normal course of business to perform the functions assigned to Sitel by this SOW (the “Client Software and Tools”). Licenses for Client Software and Tools will be paid by [***]; provided, however, that [***] shall not be responsible for any costs or expenses Sitel incurs to obtain and maintain valid privacy certifications. Client, in accordance with its then-applicable procedures, will issue and manage a unique user name and password (collectively, a “Log-in”) for each Agent assigned by Sitel to perform Services. Sitel shall (i) notify Client as soon as practicable (but in any event within [***]) that any given Agent (whether because of termination, reassignment or otherwise) has temporarily or permanently ceased performing Services, (ii) make all commercially reasonable efforts to ensure that all Log-ins are used only by the Agent to whom they have been assigned and only for the purposes of performing Services, and (iii) notify Client if Sitel has reason to believe that any party other than the responsible Sitel Manager and the applicable Agent has gained access to a given Agent’s Log-in. Training: Client will provide the training set forth in Section 7 of this SOW. Monitoring: Client will have the right to monitor Calls as set forth in Section 8 of this SOW.
Software and Tools. (a) Subject to Section 5.1(a), Supplier shall provide information to Triple-S or the Successor Supplier concerning any Supplier Software or Supplier Tools that are used for the provision of the Affected Services (including those for tracking Projects and service information requests, and those used for knowledge transfer), which shall include a complete inventory of such Supplier Software and Supplier Tools, the corresponding licensor of such Supplier Software and Supplier Tools, the nature of such Supplier Software and Supplier Tools (e.g., Software, process), the corresponding Services each Supplier Software or Supplier Tool is used to provide, all Documentation related to Supplier Software and Supplier Tools required to be made available under Section 17.1(f) (Disengagement Assistance) of the General Terms and Conditions, and other information reasonably requested by Triple-S.
Software and Tools. 8.3.1 Except for software and tools for which this Agreement expressly designates VITA as having financial responsibility, the Supplier is responsible for acquiring the software and tools (including modifications, upgrades, enhancements, additions and replacements of software and tools) as necessary or appropriate to render the Services, in its own name, subject to the remainder of this Section 8.3
Software and Tools. 8.3.2 The Supplier will not use any Supplier-owned (or Supplier Affiliate-owned) software or tools to provide the Services without VITA’s prior written consent, which may be granted or withheld in VITA’s discretion. The Supplier grants to VITA (and designees including any then-current or future Integrated Suppliers or other Agent for the sole purpose of providing services to or for the benefit of VITA and Customers), a perpetual, worldwide, fully paid up, non-exclusive, transferrable license to Use the Supplier- owned, and the Supplier Affiliate-owned, software and tools used by the Supplier to provide the Services (including Source Code, programmer interfaces, available Documentation, manuals and other items that may assist VITA with the Use of such software and tools) to provide services similar to the Services to or for the benefit of VITA and the Customers, at no additional charge to VITA. Such license will be effective during the Term and thereafter (including in connection with a partial termination or expiration of this Agreement). The Parties will mutually agree on applicable terms for the Supplier’s support of such software and tools after such termination or expiration; provided that in no event will such terms be more restrictive or otherwise less favorable than offered by the Supplier to similar entities in similar circumstances, and further provided that if VITA elects, support for such software and tools will be done on a time and materials basis using the Personnel Rates set forth in Exhibit 4 (Pricing and Financial Provisions).
Software and Tools. To enable software to target the MCENoC platform, several software tools have been developed. These include: • A simple driver for the UART provided to the PicoRV32 through PCPI instruction extensions. This includes interrupt support. • A driver for the MCENoC Network Interface (NI). • A bootloader for the PicoRV32’s ROM, allowing programs to be loaded over UART (fully functional) or MCENoC NI (work-in-progress). • A syscall handler, implementing a subset of the stubs provided through newlib. • A Python based route calculator for network permutations, providing configuration bits for communication phases between nodes. The syscall handling provides sufficient functionality to enable standard read/write functions with stdin and stdout directed over the UART interface. This allows programs to be compiled with standard tools and libraries, using a version of GCC that targets RISC V’s RV32IMC specification. 7xxxx://xxx.xxxxxxxx.xxxxxxxxxx/system-on-modules-som/som-modules/te0715-7030-xilinx-zynq-arm-fpga- som The route calculator provides the header bits needed for node A to establish communication with node B, in the presence of communication between other nodes, up to all nodes communicating. Provided no destination is sought twice in a single communication phase, the route calculator will provide valid routes for all nodes. This static routing method is based on Waksman’s [22] routing algorithm for Xxxxx networks. It is extended to consider the switching element size at each network stage, which is configurable in an MCENoC implementation. Route setup for MCENoC is performed in-band by the source nodes, whereas Waksman’s algorithm assumes a global control plane, so a modification is made to map between these two configuration methods. A routing phase for a 8192 node system can be calculated in 0.1 seconds on an Intel Xxxxxxx-based laptop, and scales linearly with the number of nodes.
