The Workflow Modeling Engine (WME) is a software module of the Content Distribution Management (CDM) software suite. A standard component of the Central Media Manager (CMM), it enables the creation of flexible workflow templates that automate business processes centered on the creation, management and distribution of content. The WME is a development tool used to create reusable workflow templates that execute a set of tasks to perform a business process.

The WME is used to design and build policy-based heterogeneous workflows to control and connect the islands of file based processes such as transcoders, QC and compliance tools, scheduling, antivirus tools, databases and MAM systems. The WME is based on an open ecosystem and SDK that enables workflow components to be created for any product or process. Interconnecting these islands reduces labor costs and reliance on tape and makes operations much more efficient.

Reusable Workflow Templates: The ability to create reusable templates that model business processes and can be executed independently.

Open Signiant Integration Product Program (SIPP) Ecosystem: Workflow components can be built for any product regardless of vendor or custom and process using the WME SDK

A workflow template can be constructed to process content in numerous ways. For instance, a template may be as simple as move a file from one Media Agent to another. Other packages may need to be processed differently, such as transcoding and a watermarking before publishing. Workflows are build modeling the specific business process for a particular company by linking components together in the WME and publishing the template to the library. Jobs are scheduled using the templates.

• Components: A Component defines the task such as a trigger, Transcode, run report.  Components are linked together with program logic for the template. Components are linked together to form a Workflow template.
• Workflow Template: a pre-defined sequence of tasks to be performed by Agents.
• Job Template Library: database of workflow templates.
• Jobs: an instance of an execution of a Workflow Template
• Job Groups: a container containing a ‘family’ of jobs.  Used primarily for reporting on jobs of similar type of scope.

1. Workflow designer creates or modifies a job template by laying out job template components in a sequence and mapping inputs to outputs. 
2. The job template is saved in the job template library database.
3. A job is created from a job template by: a) an operator supplying job parameters and a schedule, through the administrative interface or b) an external trigger. External triggers include media exchange package submissions and third party applications calling Signiant's job scheduling APIs.
4. Schedule monitors system for jobs to run and tells the Supervisor to run a job using a specific job template and job parameters.
5. Supervisor requests and receives the job template from the job template library database and merges this with the job parameters.
6. Supervisor passes relevant job template components and job state information to Agents for execution.
7. In the case of file transfer components, the supervisor contacts the controlling agent who in turn connects with one or more slave agents to perform the data transer.
8. Agents report the execution status of each component back to the manager.

 

• A Workflow Template is constructed using the Workflow Modeling Engine (Customizer in the CMM menu) by dragging and dropping components onto the canvas
• At a minimum a Workflow Template is composed of a ‘start’ component plus 1 additional component.  The ‘start’ component contains the prompts a user would get as well options passed into the workflow.
• Components are linked together to represent the sequence of tasks.
• The outputs (e.g. “File Listing”) of one component are mapped to the inputs (e.g. “Directory Name”) of the next component.
• Workflow Templates are saved to the Job Template Library. Workflow Templates can be edited or duplicated and renamed.

There are three types of components:

1. Standard included with CDM
2. Optional require a separate license
3. Custom developed using the included SDK

For an up to date list of current component integrations please go to: http://www.signiant.com/Products-sipp-application-integrations/

Foundation (standard)	Triggers and Transport
MediaExchange                             (standard)
Notification (standard)	EMail and Reporting
Transcode (optional)	Grab Agility, Rhozet Carbon Coder, others supported
Transport (standard and optional)	FTP, SmartJog, Aggregate, Distribute
Watermark (optional)	Civolution NexGuard
Verification / QC (optional)	Interra Baton
Video Editors (optional)	Avid-Transfer Manager, FinalCutPro
Storage	EMC Atmos Cloud Storage
Scripts	Standard Library with commonly used functions plus ability to centrally manage your custom scripts

Internet Explorer 7, 8

Firefox 3, 3.5, 3.6

Safari 3 (Mac)