Workflow Management Clause Samples

Workflow Management. (i) Workflow Management shall comply with and otherwise not take action inconsistent with each representation and statement made, or to be made, by or on behalf of any member of the Workflow Group in connection with this Agreement or to USOP's outside Tax counsel in connection with such firm's rendering an opinion to the Companies as to certain Tax aspects of the Contributions and Distributions. (ii) Until two years after the Distribution Date, Workflow Management will maintain its status as a company engaged in the active conduct of a trade or business, as defined in Section 355(b) of the Code.

Workflow Management. The CMS shall include a multi-stage workflow engine (up to five stages), allowing for serial workflow paths. For each section of a Web Site, and dependent on the content type, the workflow controls shall be configurable to have a different flow/approval path with any number of users assigned at each point in the process. Site and Subsite administrators shall have capability to define user workflows on a per Web Site, per page (based on Contractor’s folder structure) and per Module basis, shall be able to customize global workflow e-mail notifications, and should have an intuitive interface to manage content items in the workflow queue. All rejected/approved submissions shall be tracked with associated history information stored for future reference and reporting. Reports shall be available that detail a workflow summary/status report. Workflow shall enable content Modules to include delayed publication and auto-expiration of content based on date and time input.

Workflow Management. The Contractor’s System shall: i. Include a configurable service-oriented workflow engine to allow the modeling of business processes and the execution and management of workflows. The workflow engine will emulate the real world activities and policies surrounding a given artifact (referral, authorization, consent etc.) or data entry session. Activities to be modeled include, but are not limited to, review, assign, approval and denial. ii. Execute the appropriate event at each step of the workflow process, based on that step of the process. iii. Provide a workflow engine that allows the User to graphically model the workflow processes and easily update them without a core release of the Contractor’s System requiring no downtime. iv. Have workflow management to allow Users and the System to electronically send referrals or other documentation through the organizational hierarchy for review, approval and/or denial.

Workflow Management. Supports workflow management feature for defining, managing, and automating spatial data workflows, including data collection, processing, analysis, and dissemination. • Enable users to create customized workflows tailored to their specific project requirements, allowing for efficient task allocation and collaboration. • Include features for workflow visualization, status tracking, and task assignment, facilitating transparency and accountability throughout the workflow lifecycle.

Workflow Management. Supports service initiation and triggering of the service order distribution API after an order is created or changed. Order versioning is used to help manage change to existing orders. Utilizing a work flow manager and ordered set of tasks (work plan) are created and then scheduled and tracked to completion. Tasks defined by the customer are manual and are completely user definable. CSG can also support the creation of tasks that will initiate the Service Order Distribution Interface (SODI) to feed downstream OSS and provisioning systems that would be used for order management and service activation.

Workflow Management. The Workflow Management System (WMS) addresses service orchestration and monitoring, hence “autonomic behaviour”. One or more WMSs can be configured by developers to autonomously execute workflows. D-Net workflows are resources describing sequences of steps, where each step may consist of business logic (i.e. Java code), remote service invocations, workflow forks (i.e. parallel sub-workflows), and workflow conjunctions (confluence of parallel workflows). Typically, service invocations are preceded by a look-up into the Information System (IS) to discover the “best” service of the needed kind and available to execute the call. Workflows can be fired manually or as a consequence of the notification of a resource-related event from the IS or because of time-events, i.e. cron jobs. Workflows are commonly used to automatically schedule data aggregation (i.e. collection and transformation of metadata records into a common format) from data sources.

Workflow Management. Workflow automation shall use software to guide system users through various business activities that should be established for recurring sets of business operations that are done within the context of established procedures. The workflow software should retain all the artifacts, such as documents, e-mails, files, spreadsheets, and images within a centralized document/media management repository. The software should also capture the status of business activities and any administrative actions (approvals/disapprovals) collected along the course of any instance of a business process controlled by workflow automation. The workflow software should be configured to enforce the established procedures or business rules related to the workflow, such as what documents are required, who needs to review and approve at each level, who needs to be notified of the progress, the routing and decision points along the workflow path, and the access to the workflow content based on the roles of the participants in the process. The use of workflow software should help to automate manual processes by integrating the documentation, generating notifications and alerts, scheduling and queuing work, and enabling electronic retrieval and status reporting. The workflow software should enforce standardization of the flow of business processes by ensuring routing, approvals, and content of each workflow in accordance with established business rules. The new MEMS solution shall utilize this workflow management tool for any DDI components but it is not required to utilize for COTS solutions. The MEMS should have the capability to set user defined system and personal alerts, such as ticklers and reminders.

Workflow Management. Oozie is a server-based tool for organizing Hadoop workflows (setting up jobs, starting, stopping, scheduling etc). It’s necessary for managing Hadoop jobs through an API. It will execute tasks forwarded through the job management service, which abstracts its options.

Workflow Management. The Contractor’s System shall: i. Include a configurable service-oriented workflow engine to allow the modeling of business processes and the execution and management of workflows. The workflow engine will emulate the real-world activities and policies surrounding a given artifact (referral, authorization, consent etc.) or data entry session. Activities to be modeled include, but are not limited to, review, NE1.18 assign (R1), approval and denial. ii. NE1.19 Execute the appropriate event at each step of the workflow process, based on that step of the process. (R1) iii. NE1.20 Provide a workflow engine that allows the User to graphically model the workflow processes and easily update them without a core release of the Contractor’s System requiring no downtime. (R1) iv. Have workflow management to allow Users and the System to electronically send referrals or other documentation through the organizational hierarchy for review, approval and/or denial.