Pilot implementations Sample Clauses

Pilot implementations. In order to compare the two remaining options, pilot implementations of the PID micro-services were created using the two acceptable options. The final decision about which option to use was based on the results and experiences from these practical exercises. The proof-of-concept implementation of the PID manipulation micro-services in C was provided by Jedrzej Rybick (FZJ). The results8 of this exercise are available in the EUDAT SVN repository. The implementation facilitates external libraries for JSON manipulation (jansson) and HTTP communication (libcurl). In particular, it was noted that manipulating JSON was much harder than in Python, and that there was a lack of C-programming expertise amongst the partners. Hence there was a possibility that the production-ready implementation would not be ready in time, and it was likely to be harder to maintain the module. The proof-of-concept implementation of a Python-based EPIC client was provided by Xxxxxx Xxxxxxxxx (BSC) and the integration into iRODS was done by Xxxxxx Xxxxxx (MPI-PL) and subsequently by other partners. It was found that the JSON manipulation was much easier when using the Python external library (simplejson). For the HTTP interactions, the Python library (httplib2) was used. The implementation9 was made available in the project SVN repository. This was tested by all the partners and was proven to work properly. A further advantage of this approach was that there was much more Python expertise available among the project partners. Hence quicker development, testing and integration were possible. Maintenance was also expected to be easier. Recommendation After internal discussions, the Safe Replication Task Force made the following recommendations:  For the pilot implementations, the Python module should be used.  Because native iRODS modules are written in the C programming language it is advisable when the service reaches production-ready status and is handed-over to operations to revive the effort on a C implementation of the micro service.
Sample 1
AutoNDA by SimpleDocs

Related to Pilot implementations

  • Project Implementation 2. The Borrower shall:

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Implementation Program 1. The Borrower shall:

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Implementation Services The Company and the Client have developed a plan for implementing the services to be provided hereunder, including with respect to the transition of responsibility for such services from the Client and its current administrator to the Company, which plan attached hereto as Schedule I (the “Implementation Plan”). The Company shall perform the services required to complete the Implementation Plan, as set forth therein (the “Implementation Services”). The Company and the Client shall comply with any applicable requirements agreed in the Implementation Plan.

  • Implementation and Management 1.1 Properly constituted Occupational Health and Safety (OH&S) Committees or, where there is no OH&S Committee, Site Safety Supervisors/Safety Officers in conjunction with worker representatives, are the appropriate bodies to implement and administer alcohol and drug policy/programs (* see below).

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that Xxxxxx’s behalf.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!