|
Teamwork
and Collaboration
| |
File
sharing and co-editing |
|
Document
Review |
| |
The
workbench allows team members to share any file in any format
that they usually work with. Changes to files are automatically
synchronised between members. Team members can co-edit and review
Microsoft Word documents and Microsoft Powerpoint presentations. |
|
When
teams need to review and finalise handouts, workbooks and other
documents, the workbench handles the workflow - managing and
routing sets of documents by multiple reviewers. A document
review wizard helps them set up and manage review cycles while
avoiding endless email chains. |
| |
Project
Management |
|
Co-browsing |
| |
Teams
can be assigned to projects, with leaders, start dates and objectives,
and create, assign and track the status of tasks collaboratively.
The workbench supports import/export of project items with Microsoft
Project. |
|
A
team often needs to look at the same content at the same time
to establish shared context and understanding. The workspace
supports full co-browsing of all content and tools, including
the co-browsing of external web sites. |
| |
Training
Forms |
|
Meetings
Management |
| |
TNA,
session design, training objectives design, training appraisal
and review, all have unique requirements for definition, communication,
tracking and management. The workbench's forms allow the team
to work to consistent, best practice standards and can be customised
to your organisation's own standards. |
|
Almost
every design/development project includes meetings: kickoff,
updates, reviews, and ad hoc. decision making sessions. The
meetings manager allows users to create meeting profiles and
identify participants, create and view agenda items, add attachments
for reviewing, create and edit meeting minutes, and assign and
track action items and tasks. |
Team
member 'connectivity' and usage
| |
Use
anywhere / connect any way |
|
Online
and Offline |
| |
The
workbench may be used on a desktop or laptop PC, at the office,
at home or on the road, It is possible for a team member to
have multiple access on multiple PCs, to the same, synchronised
workbench content. Synchronisation connection is via internet
IP, via a company LAN or any other (external) ISP. |
|
The
workbench can be used online or offline. When online any changes
to content and activity are immediately reflected on the workbench
of other members who are online. When offline, any changes made
are synchronised with others in the team, when they next connect.
Version control and tracking is managed through the workbench. |
| |
Internal
& external team members |
|
Team
member roles and permissions |
| |
The
workbench security and network model fully supports teams being
made up from individuals within, and external to, an organisation,
even across company firewalls. This allows external training
suppliers or subject content specialists to be invited and participate,
as full or restricted members of the team. |
|
Access
to both content and functionality within the workbench environment,
can be set and/or restricted, at an individual team member level.
For example, sub-teams can be setup for document review and
sign-off, before being 'published' to the rest of the team.
Team member permissions can be set to view-but-not-modify both
tool components and content. |
Security
and Networking
| |
Secure
content and data |
|
Secure
synchronisation between members |
| |
All
content within, and activity on, the workbench, including all
messaging and external files, are encrypted, and only accessible
and available to invited team members. |
|
Content
changes and other activities made by team members are immediately
synchronised and duplicated on the workbench of other team members.
This synchronisation data is encrypted as it passes over the
internet or LAN. |
| |
Peer-to-Peer
Networking |
|
Currency
and back-up of content |
| |
The
workbench sits directly on each members PC, not on a web site
or centralized server. All application logic and data is stored
locally on the desktop of each member of the team. If there
are 4 members in the workbench team, there are four local copies
of the workbench. |
|
There
is no 'master copy' of the data in the workbench. Each member's
copy of the data is a peer in the network. The workbench platform
ensures that the content and state is synchronised across all
members' machines, including data recovery in the event of problems. |
|
 |
