Technology Bricks Workflow Sample Clauses

Technology Bricks Workflow. After the introduction of the components to be realized inside the platform, this section provides an overview on how the modules developed by the partners (technology bricks – WP3) will work together within the platform to offer complex features.
Sample 1
AutoNDA by SimpleDocs
Technology Bricks Workflow. The diagram above describes the core module groups and interactions of these technology bricks within the CPN platform. In the diagram, we are referring to families of modules. Thus, for the sake of simplicity we are not including every individual module that will be developed. This will be covered during the further design of the architecture and the full definition of components. All calls to the CPN platform will be directed to the API gateway. The API gateway is responsible for the delegation of these calls to the related modules, based on the defined workflow. A message queue will implement a pub/sub protocol to enable modules to fetch and analyse content. For convenience, the synchronous communication between the modules has been represented directly, although in reality, as described in section 3.4, this kind of communication is implemented through an orchestrator. One of the goals is to avoid centralized DBs. Therefore, all modules follow a Microservices approach and store data internally in their own repository of choice. Web App for Producers Producers will use the Cute4LE module for pushing content to the platform. The content will be published to a message queue. Before pushing content, producers will also access the Reward Framework in order specify the contracts (e.g. cost per access) that apply to a given content and that producers and distributors have to comply. The web application and the recommender module will also interact with the Reward Framework to provide information on how contents are distributed. The information, published on a distributed ledger for transparent accountability, will allow the Reward Framework to rewarded producers according to the selected contract.
Sample 1

Related to Technology Bricks Workflow

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Technology Discoveries, innovations, Know-How and inventions, whether patentable or not, including computer software, recognized under U.S. law as intellectual creations to which rights of ownership accrue, including, but not limited to, patents, trade secrets, maskworks and copyrights developed under this Agreement.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

  • Research, Science and Technology Cooperation 1. The aims of cooperation in research, science and technology, carried out in the mutual interest of the Parties and in compliance with their policies, will be: (a) to build on existing agreements already in place for cooperation on research, science and technology; (b) to encourage, where appropriate, government agencies, research institutions, universities, private companies and other research organizations in the Parties to conclude direct arrangements in support of cooperative activities, programs or projects within the framework of this Agreement, specially related to trade and commerce; and (c) to focus cooperative activities towards sectors where mutual and complementary interests exist, with special emphasis on information and communication technologies and software development to facilitate trade between the Parties. 2. The Parties will encourage and facilitate, as appropriate, the following activities including, but not limited to:

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

Time is Money Join Law Insider Premium to draft better contracts faster.