Workflows Clause Samples

Workflows. Several relevant workflows are listed in this section regarding the 3rd version of the platform. The rest of the workflows are presented can be found on the PANACEA myExperiment portal. WP5 and WP6 new workflows will be presented in D5.4 and D6.2 respectively.

Workflows. PANACEA has delivered various workflows that implement the way web services are chained as sequences, with specific input and output (all are at PANACEA myExperiment). For instance, a workflow that consists of a sequence of two "calls" to web services and may take as input a set of URL and identify the language(s) in which they are written and hence give as out a table with pairs (URL, language). It could be chained with one that crawl all URLs that are in a given language. Such work flow could be (identify-languages (list of URLs) + Crawl (URL, Language=Fr). (1) (Input = set of URLs) 🡺 Web services 1: identify languages 🡺 (output (URLs, languages) (2) (input (URLS, Languages) 🡺 Web services 2: Crawl (URLs, Language=Fr) and store 🡺 output (set of XML, HTML, PDF, … pages stored on a given address) It is clear that more sophisticated workflows could be designed, requiring deep analysis and more creativity and hence triggering the application of copyright and other property rights. Some of the workflows are illustrated by the diagrams given below. More details are given in the appendix elaborating on legal issues. The consortium took seriously all aspects related to the ownership of workflows, both to ensure that the exploitation within the consortium is done in a cleared legal framework as well as to ensure that such assets can be licensed to third parties under clean, easy to understand and implementable licensing schema. From a technical point of view, the consortium can easily work out the arguments about the added value of its achievements but it is also crucial that the legal aspects involved behind such a paradigm should not be neglected. When dealing with workflows, data are not only stored on the server of the different web services, but are also “travelling” between web services. To guarantee the privacy of the data transferred from one web service to another, the transfer protocol must be secured so as to avoid any security bridge. Indeed, data going from one server to another (e.g. in the case of a workflow process) or from a client machine to a server (e.g. in the case of a single web service process) should be secure enough so as not to be corrupted or retrieved by a third user. In PANACEA, this process is secured by using SOAP8 (Simple Object Access Protocol), which allows to reach a sufficient level of security since SOAP transports data using both SMTP and HTTP (and although not implemented in the current version, potentially HTTPS). Workflow...

Workflows. Within the PANACEA platform, Taverna workflows are designed to provide a seamless end-to- end solution for lexical acquisition. In the WP6 workflows, tools for creating lexica are chained together, demonstrating the ability to perform automatic lexical acquisition. The PANACEA lexical acquisition components were particularly designed to use technologies that are scalable and implementable in a distributed environment.

Workflows a. The Riskonnect System will be delivered with workflows, approval process and e-mail notifications using e-mail templates b. The workflows will be triggered by a data condition (e.g., new event report, property damage estimate in excess of $5,000, liability claim with bodily injury paid, etc.) and the associated workflow automation can initiate any number of: i. E-mail notification(s) – e-mail templates that will auto-populate with data from the record associated with the workflow rule ii. Task assignment(s) to user(s) (e.g., escalate a claim for supervisor review) iii. Field update(s) to some other related data (e.g., update a subrogation status field) c. Workflows for approval will include multiple layers of approval and will comply with standard platform approve/reject functionality. d. The Riskonnect System will be delivered with the following workflow rules, approvals, and e-mail templates to produce up to a total of 25 workflows, 5 approval process and 10 e-mail notifications with their associated email templates.

Workflows. The standard out-of-the-box workflows within the Software Scope listed above shall be available for implementation. Re-design of standard out-of-the-box workflows and/or new workflows not anticipated or included in implementation services. The County will adapt their business processes and use the delivered business processes and workflows to meet their needs. Workflows will be configured, tested, validated, and approved after Conference Room Pilot 1 (CRP1). Only those workflow designs tested and approved during Conference Room Pilot 2 (CRP2) will be used for SIT, UAT and deployment to Production. Any material updates (i.e., adding a level of approval, such as changing from 3 levels to 4 levels) to workflows after CRP2 will be handled through a contract amendment fully executed by the County’s Purchasing Agent. Immaterial deviations may be rectified through SIT, without going through the contract amendment process if prior approval is received. CRP2 shall include scenarios of each workflow template. Changes made to workflow configuration shall be done through the User Interface. The final list of in scope workflows will be identified as part of Exhibit F – Functional and Technical Requirements

Workflows. The SNMP protocol is used to communicate between SNMP Managers (monitoring and aggregation) and SNMP Agents (on devices). The agent collects device status, monitoring data and counter in situ and offers it through the SNMP protocol. The MS contains a Monitoring Tool running an SNMP Manager that communicates with each of the agents of the set of resources monitored by the MS. The Monitoring Tool will periodically request a subset of the SNMP MIBs from each resource, to later trans- form and store its monitored data into the Monitoring database, as pictured in Figure 3.4.

Workflows. The current monitoring tool in the island monitors each of its switches and stores their monitoring data into the appropriate MS database. The perfSONAR SequelService, developed by NICT (Japan's National Institute of Infor- mation and Communications Technology), provides archived monitoring data and statuses through a perfSONAR interface in order to communicate with other monitoring tools. The Monitoring Data Collector of the MS collects the monitoring data accessing perfSONAR interface and imports such information to make it available within the ▇▇▇▇▇ Framework. Figure 3.5: Design for perfSONAR

Workflows. ‌ The MS interacts with other modules as in the workflow described in Figure 3.4 (this sequence diagram and any other appearing in this document are generated using ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇). Figure 3.4: Monitoring Workflow

Workflows. 4.1. FITI and NANOX may engage under two different workflows: • Products with supporting Forecast • Products without supporting Forecast 4.2. Products with Forecast • Lead time on Products with supporting Forecast will be as shown in Appendix A. NANOX will convert Forecast to Purchase Orders with requested delivery dates set at lead time or greater. FITI will confirm delivery dates for Purchase Orders placed at lead time and with supporting Forecast. • For Purchase Orders that are placed inside lead time, FITI will review the request and advise NANOX within five (5) business days outlining what commitments can be made to the request inside lead time, what effect, if any, the expedited delivery may have to previously committed Purchase Orders, and any out-of-pocket costs and expenses that will need to be paid, including, freight, overtime and the like, to expedite deliveries. 4.3. Products without Forecast • Lead time on Products without supporting forecast are listed in Appendix B. NANOX will place Purchase Order’s to their requirements at this leadtime. • FITI will confirm delivery dates for Purchase Orders placed at these lead times. • For Purchase Orders that are placed inside lead time, FITI will review the request and advise NANOX within five (5) business days outlining what commitments can be made to the request inside lead time, what effect, if any, the expedited delivery may have to previously committed Purchase Orders, and any premium that will need to be paid, including, freight, overtime and the like, to expedite deliveries.