Teamwork Server

Teamwork Server
For more information or a quote
please contact
sales@nomagic.com
or call +1-214-291-9100.

Get everyone on your team working collaboratively

Teamwork Server makes it easy to exchange data directly in the context of your work. It provides a central repository for storing any kind of models. Using Teamwork Server, team members can access, review, or modify the same model or even the same diagram at the same time. It supports importing, exporting, updating, branching or comparing in-server-stored models.

Server data and configuration can be managed through a separate administrative console with a minimal technical knowledge and effort.

See the latest features of Teamwork Server

collaborate administer security
Improve Team Collaboration Administer Easier Enhance Security


Benefits of the Teamwork Server

  • Faster team collaboration. Teamwork server supports collaborative modeling and versioning of Cameo Systems Modeler, Cameo Business Modeler, Cameo Enterprise Architecture and MagicDraw projects. Users can access and modify the same model or even the same diagram in parallel. Every user may instantly obtain the newest version of the model
  • Simpler configuration management. All designs are stored in a single place, there are no more files that are scattered around in the network; changes can be introduced orderly and without conflicts
  • Controlled access to your artifacts. Different people in the project may have different access levels to the projects stored in the teamwork server repository.
  • Remote access. No matter where you are, if you are connected to the Internet you may work with the model that is stored in the repository. A project manager may provide read only or full access to the repository for the overseas developers, customers, subcontractors, management, and other interested parties
  • Offline mode support. Everyone may save their teamwork project locally and work offline. Changes done while working offline can later be committed to the Teamwork Server
  • Data synchronization between different sites. Several Teamwork Server deployments can be synchronized. Projects available on one Teamwork server can be accessed as read-only replicas by other Teamwork Servers that are deployed on remote sites.

Accelerates Enterprise Team Collaboration

MagicDraw Teamwork server is a central repository for all Cameo tools. It forms a base for integrating different models from different clients as all models reside in a single repository. Make it easy to exchange data directly in the context of your work. Teamwork server provides a central repository for storing:

  • MagicDraw projects
  • Cameo Systems Modeler projects
  • Cameo Business Modeler projects
  • Cameo Enterprise Architecture projects

With Teamwork server, team members can access and modify the same model or even the same diagram in parallel. It supports importing, exporting, updating, committing, merging and comparing stored models.

Server configuration can be managed through a separate console, which allows user administration of server and stored data with minimal technical knowledge and effort.

 


collaborate

 

 

accessible

Improve Team Collaboration

Versioning

Teamwork server provides state of the art version control for your artifacts. It supports teams doing parallel modeling and has many powerful features like atomic check-ins, merging, concurrent check-outs (updates) and element locking policies for avoiding parallel modeling conflicts.

Team collaboration

Teamwork server supports collaborative modeling and versioning of Cameo Systems Modeler, Cameo Business Modeler, Cameo Enterprise Architecture and MagicDraw projects. Users can access and modify the same model or even the same diagram in parallel. Every user may instantly obtain the newest version of the model.

Instant Remote Access

No matter where you are, if you are online you may work with the model that is stored in the repository.

Data synchronization between different sites

Teamwork server supports data synchronization among several Teamwork Server deployments all around the world. Projects available on one Teamwork server can be accessed by other Teamwork Servers that are deployed on remote sites. 

Administer Easily

Teamwork server is a powerful yet easy to manage collaboration solution. All configurations can be managed through the administrative console, which let every user administrate server and stored data with a minimal technical knowledge and effort. In additional to server management features, there you can also:

  • Manage licenses
  • View license usage statistics
  • Access server status information
  • Control active sessions
  • Administrate stored data
  • Import/export server projects

A permission system allows controlling each user capabilities to perform a specific operation in the server.

administer
security

Enhance Security

Teamwork server comes with a full security feature set, guaranteeing secure communication of information and protection for your confidential data:

Authentication

Teamwork allows you to use LDAP authentication as well as built-in authentication.

Encryption

Teamwork server supports secure socket layer (SSL) connections. This ensures your data remains secure as it is transmitted between clients and Teamwork.

Permission System

The Teamwork server has built-in permission system allowing you to protect the access to your data.

 

To run Teamwork Server, your system must meet the following requirements:

Resource Minimum Recommended

RAM 512 MB 2 GB or more
Disk space* 25 GB 1 TB or more

* Use the formula to estimate the storage required for the Teamwork Server disk space.

Operating System

The server is based on a Java platform, and it is interoperable with most operating systems, where the supported Java is running.

NOTE. For Unix platforms, XWindow server is required for starting Teamwork Server with GUI and for starting Teamwork Server Console

Software

Any modeling tool client version except the Personal Edition can be connected to the Teamwork Server. Whenever you install teamwork server you supply a license key, which bears information on how many simultaneous connections can be made to this server at a single time. There is no limitation on how many installed client versions of modeling tool may access the teamwork server potentially. The limitation of the connections specified in the server limits the number of the clients that can work with the server (perform updates, commit, etc.) in parallel. The number of the projects you can create in the repository is also not limited.

Formula to estimate Teamwork Server disk space

The following formula describes how to approximately estimate the storage required for the Teamwork Server disk space:

Required Disk Space = Project Size x Average Commits per Day x Active Users x 250 days x Estimated Project Life Cycle

Where:

Project Size The size of your project in megabytes (MB). The project size may vary depending on number of used profiles and attached files (the size is usually larger if the images or other files are embedded to the project).
Average Commits per Day An average number of savings to the server (commits) per day for one active user.
Active Users The number of the users that actively contributes to a project.
250 Days Average work days per year.
Estimate Project Life Cycle Estimated time in years for your project development.

The space of the project depends on how many versions are committed to the server. Every time a change is committed to the repository, a new version of the entire project is created. Calculate the required disk space of the server with your own characteristics. Several examples of the different size of the projects are provided below.

Note. The required disk space depends on how many active projects are stored in one server. For instance, if you are working with more than one similar size projects concurrently, then the calculated size should be multiplied by the number of projects.

Example 1. Medium size projects (30MB; 200 000 elements)
Required Disk Space = 30 MB x 2 Commits x 8 Users x 250 Days x 5 Years = 600 GB

Example 2. Large projects (50MB; 400 000 elements)
Required Disk Space = 50 MB x 2 Commits x 12 Users x 250 Days x 5 Years = 1 500 GB (1,5 TB)

Example 3. Small projects (2 MB; 25 000 elements)
Required Disk Space = 2 MB x 2 Commits x 5 Users x 250 Days x 5 Years = 25 GB

 

DemoPlay

Teamwork Server: Add project to teamwork
This demo presents easy way to make a local project accessible for the Teamwork Server users.

3:04

Teamwork Server: Create a new user in teamwork
This demo presents the management of users accounts, guides through creation of a new user or edition of existing one, introduces various kinds of permissions and how they can be set to project.

2:55

Teamwork Server: Working in teamwork
This demo introduces the main functionality of teamwork, when two or more users work with the same project. You will see how to lock part of the model and work on this part individually, how to commit changes to the server and share with the other team members.

4:30

Teamwork Server: Project branching
This demo introduces the Branching functionality and presents samples of branch creation.

6:48

Efficient Teamwork Server Repository analysis with Project Usage Map
In this short demo, we will present the Project Usage Map and its use case. You will get in-depth information on the use of this powerful analysis capability.

3:46

 

iic member logo 225x108

nomagic gartner ad 2015

omg-member-logo

facebook 32 linkedin 32 twitter 32 youtube 32 rss 32
For more information or a quote
please contact
sales@nomagic.com
or call +1-214-291-9100.