Browse Prior Art Database

A Pattern and Context Analytics based Orchestration to orchestrate and manage activities and meetings to achieve business outcomes

IP.com Disclosure Number: IPCOM000239730D
Publication Date: 2014-Nov-27
Document File: 5 page(s) / 187K

Publishing Venue

The IP.com Prior Art Database

Abstract

More and more interactions/collaborations between employees, Line of Businesses(LoBs), partners, and users are driven by business out-comes 1. Multiple activities/meetings (with one-or-more participants in different time zones) with dependencies and concurrency constraints, deadlines, deliverables, etc 2. Each participant could play multiple roles in each meeting and has constraints on when that participant can participate in a meeting or perform an activity 3. New participants can join anytime during the course of the execution of the meetings 4. There is a context which grows as the team makes progress towards the outcome :Context comprises of voice, video, documents, project plan , team rooms, etc that have been input, output, or delivered in each meeting/activity and is driven by milestones and activities

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 5

A Pattern and Context Analytics based Orchestration to orchestrate and manage activities and meetings to achieve business outcomes

Presently, there is an ad hoc and highly manual approach to achieving a business outcome in terms of setting up activities and meetings, and managing them from a global perspective to track milestone and deliverables. This ad hoc nature and manual elements increase time wastage, turnaround time, productivity of individuals and the business outcome. The manual nature does not allow for fast adaptability when exceptions occur. The ad hoc ness in setting up meetings also results in loss of information as well as precludes the possibility of systematically presenting a context to members during a meeting or activity because of a lack of a systematic approach to organization and tracking of meetings and artefacts.

A need to have a Development framework: i. to define (encode) interaction/collaboration patterns (or workflows) required to achieve a particular business objective.

ii. to define the roles for the participants, constraints, deadlines, etc along with adaptation of the workflow patterns when exceptions occur.

iii. define "context" for each meeting ,activity and deadline.

iv. a runtime framework that: a) Execute the collaboration patterns.

b) Uses service components to composes the overall runtime.

c) Uses analytics that help in automatic context creation to provide a quick summary of the past work for the current activity and meeting.

EXISTING APPROACHES

1. Lotus notes/MS Outlook /any standard Email /collaboration tool allows to choose the best times convenient to different participants but it does have a business outcome driven focus and is a very primitive partial solution.

2. Share meeting notes across all participants through email, wikis, activities, etc. 3. Share documents/pdfs/ppts/xls etc in team rooms/wikis etc and assign actions. 4. Microsoft project allows manual creation of project plan to achieve a business outcome but it does not actively control the creation and management of activities/meetings based on the roles, responsibilities, of the participants and

1


Page 02 of 5

manage the context of the meetings/activities.

Define Workflow Patterns for Collaboration and Interaction to achieve a Business Outcome

A. A Workflow is a collection of activities and an activity could be a meeting, dependencies between activities, and a taxonomy

B. Activities and meetings each have 1. Participants with roles and constraints on availability, timezones, etc 2. Inputs, outputs, and context (e.g. documents, presentations, emails, blogs, wikis, project plan etc etc)

a. Work products could be inputs and outputs and could be named in the workflow pattern

b. For each output there is a repository that stores all the outputs - voice, documents

3. Flow constraints (whether an activity or meeting can be setup before another activity or meeting or not)

4. Deadlines and durations of activities and meetings 5. Cos...