Automation Studio Installation and Administration Guide

Installation and Administration
User’s Guide
Famic Technologies Inc. All rights reserved.©
Automation Studio™ Installation and Administration User’s Guide

Document Reference: DASADENFTP62U_020
REPRODUCTION
Reproduction or re-transmission of this manual or software, in whole or in part, by any means

is strictly prohibited without the express written consent of Famic Technologies Inc.
Windows is a registered trademark of Microsoft Corporation.

Automation Studio™ is a registered trademark of Famic Technologies®
Table of Contents
1 Introduction ................................................................................................................... 1-3
1.1 Contents ................................................................................................................. 1-4
2 Presentation ................................................................................................................... 2-1
2.1 License ................................................................................................................... 2-1
2.1.1 Automation Studio™ License Manager .................................................. 2-2
2.1.2 License Management Interface ................................................................ 2-4
2.2 Operation Mode ..................................................................................................... 2-4
2.2.1 Automation Studio™ Project Server ....................................................... 2-6
2.2.2 Application Rights ................................................................................... 2-7
2.2.3 Project and Documents Rights ................................................................. 2-7
2.3 Authentication Modes ............................................................................................ 2-8
3 Installing and Starting Automation Studio™ ............................................................. 3-1
3.1 Minimum Required Configuration ........................................................................ 3-1
3.2 Installing Automation Studio™ ............................................................................. 3-2
3.2.1 Installation from the DVD ....................................................................... 3-2
3.2.2 Installation from a Download .................................................................. 3-8
3.2.3 Silent Installation ..................................................................................... 3-9
3.3 Starting Automation Studio™ ............................................................................... 3-1
3.3.1 Template and Standards Database Update ............................................... 3-1
3.3.2 Windows firewall .................................................................................... 3-4
3.3.3 Quick Start ............................................................................................... 3-5
3.3.4 Choosing the License Type ..................................................................... 3-5
3.3.5 Connection to a Remote Project Server ................................................. 3-14
3.3.6 Connection Profiles ............................................................................... 3-18
4 Automation Studio™ License Manager ...................................................................... 4-1
4.1 Minimum Required Configuration ........................................................................ 4-1
4.2 Installing Automation Studio™ License Manager ................................................ 4-1
4.3 Installing the License Management Interface ........................................................ 4-4
4.4 Using the License Management Interface .............................................................. 4-4
4.4.1 Starting the License Management Interface ............................................ 4-5
4.4.2 Configuration ........................................................................................... 4-8
4.4.3 Reports ................................................................................................... 4-12
4.4.4 License Profiles ..................................................................................... 4-16
© Famic Technologies Inc. 1-1

Automation Studio™ - Installation and Administration User’s Guide
4.4.5 Access Points .........................................................................................4-22

4.4.6 Access Schedules ...................................................................................4-25
4.4.7 User Accounts ........................................................................................4-27
4.4.8 License Management Interface Options .................................................4-35
5 Application Rights Management ..................................................................................5-1
5.1 Minimum Required Configuration .........................................................................5-1
5.2 Installing a Project Server ......................................................................................5-1
5.3 Using the Automation Studio™ Project Server .....................................................5-3
5.3.1 Starting the Application Rights Management Interface ...........................5-3
5.3.2 Application Profiles .................................................................................5-4
5.3.3 User Accounts ..........................................................................................5-8
5.3.4 Application Rights Management Interface Options ...............................5-10
6 Project Rights Management .........................................................................................6-1
6.1 Project Profiles .......................................................................................................6-2
6.1.1 Project Profiles List..................................................................................6-2
6.1.2 Creating a Project Profile .........................................................................6-2
6.1.3 Modifying a Project Profile......................................................................6-7
6.2 User Accounts ........................................................................................................6-7
6.2.1 Users List .................................................................................................6-8
6.2.2 Creating a User Account ..........................................................................6-9
6.2.3 Modifying a User Account .....................................................................6-10
6.3 Object Permissions ...............................................................................................6-10
6.3.1 Object Permissions List .........................................................................6-10
6.3.2 Creating a Group of Object Permissions ................................................6-11
6.3.3 Modifying a Group of Object Permissions ............................................6-13
7 Technical Support ..........................................................................................................7-1
7.1 Direct Contact ........................................................................................................7-1
7.2 Contact via Technical Support Portal ....................................................................7-1
7.3 Installing a Service Release or a New Version ......................................................7-3
7.4 Documentation Download .....................................................................................7-4
A Glossary ............................................................................................................................. 1
B Index .................................................................................................................................. 1
1-2
Introduction
1 Introduction
Automation Studio™ is an innovative product always trying to meet the changing needs of
its users. The purpose of the present guide is to help you in the installation procedure of
the product.
Licenses
Before its first launch, Automation Studio™ must obtain a “license”. All the information
about one or more of your licenses is stored on a protection key. This information includes:
● The Automation Studio™ version;
● The Automation Studio™ edition (Professional, Educational, Simulation or Design);
● The workshops and modules that are activated;
● The license type (local or network).
In the case of a local license, the USB key must be connected directly into the USB port of
the workstation where Automation Studio ™ is installed. In this scenario, the license can
only be used by the local user.
A network license is meant to be shared by multiple workstations. The USB key must then
be connected into the USB port of a machine, which can be accessed by the workstations.
That machine runs the “License Manager”.
This guide describes how you can configure Automation Studio™ depending on whether
you use a local or a network license. In the latter case, if this task is your responsibility,
you will also learn how to install the components required to use a network license, as
well as how to manage your network licenses.
Operation Mode
Regardless of the type of license you use, Automation Studio™ supports two operation
modes:
● Single-user mode, in which a project can only be opened by a single user at a
time;
● Multi-user mode, in which multiple users can work on a same project at the same
time.
This guide explains how you can configure Automation Studio ™ to use either mode.
© Famic Technologies inc. 1-3

If your organization is mainly interested in the multi-user features of Automation Studio™,

this guide will explain how to set up a Project Server and how to manage users.
Once installed, Automation Studio™ is preconfigured to use a local license and the single-
user mode. This quick and simple start-up meets most common needs and allows a user
already comfortable with the product, to move quickly into the working process.
If this configuration fulfils your needs, you might want to skip the sections 4 and 5 below
that present both the use of network licenses and the multi-user mode
Project and Documents Rights
For their security and confidentiality, each Automation Studio ™ project contains its own
“Project and Documents Rights”. These rights specify for instance which users can open,
edit or simulate a project or one of its documents. By default, a new project is not protected
and can be opened by anyone.
This guide explains how the rights can be modified in your projects. If this feature does not
apply to your situation, you might prefer to skip the related sections below.
This guide is completed by the Common Features User’s Guide, which describes the main
functions of the product, including how to work in a multi-user mode. You might also refer
to the workshop guides to get information on various functions, components and samples
in order to guide you through your learning process.
1.1 Contents
This guide is structured as follows:
Chapter 2 Presentation: This chapter develops the notions already presented in the
introduction: licenses, operation modes and project/documents rights.
Chapter 3 Installing and Starting Automation Studio™: This chapter explains how to install
Automation Studio™ on a workstation. You will also learn how to setup the application to
make it connect to an Automation Studio™ License Manager or a remote Automation
Studio™ Project Server.
Chapter 4 Automation Studio™ License Manager: You will learn in this chapter how to
manage your network licenses from the License Management Interface.
1-4
Introduction
Chapter 5 Application Rights Management: This chapter explains how to install a remote
project server and how to get access to multi-user functionalities. The chapter also explains
how to manage application rights.
Chapter 6 Project Rights Management: This chapter explains how a project administrator
can manage its project rights.
Chapter 7 Technical Support: This chapter provides information about the Technical Support
Portal and the update process for Automation Studio ™.

2 Presentation
This chapter provides details on the concepts presented in the Introduction: licenses,
operation modes and project/documents rights. The chapter also describes the
components that are required for Automation Studio ™ to function properly, depending on
the license type and the operation mode you choose.
2.1 License
Each copy of Automation Studio™ used inside your organization requires a license in order
to work.
A single copy of Automation Studio™ can connect at any time to a local license. Multiple
instances of Automation Studio™ can connect concurrently to the same network license. In
other words, each of your network licenses can be attributed simultaneously to many
users.
The maximum number of users allowed at any time is built-in for each network license.
We call this number, the “capacity” of the license. A local license always has a unit capacity.
 Using a local license does not require any extra component. The rest of this section
concerns only network licenses.
When you launch Automation Studio™ on your workstation, the application must first
connect to a network license. If the number of connections to the license is less than the
capacity of the license, the connection will be established and you will be able to use
Automation Studio™.
On the other hand, if the license has already reached its full capacity, you will not be able
to obtain the license. You can then try to connect to a different license, or you will have to
wait until the license is made available (see Allocation and revocation of a network license
under section 3.3.4.1 Connecting to a Network License to learn more about the role of
priorities in the allocation of licenses).
 Note that Automation Studio ™ will only connect to a single license at a time. When

you close the application, the license is made available for another user.
Figure 2-1: Network Licenses
2.1.1 Automation Studio™ License Manager
The Automation Studio™ License Manager is the central element on which rely all
communications related to network licenses. Automation Studio ™ communicates with the
Automation Studio™ License Manager in order to obtain a network license. The Automation
Studio™ License Manager verifies the user’s permissions on the licenses, and assigns these
licenses.
The Automation Studio™ License Manager is installed on a dedicated machine. The

protection key that contains your licenses information is connected into the USB port of
this machine (see Figure 2-1: Network Licenses).
The Automation Studio™ License Manager can work on a LAN as well as on a WAN network.
However, the network type might be limited by the license itself, depending on the options
selected at purchase:
1. WAN Support: the Automation Studio™ License Manager and the workstations must
2-2
Presentation
be on the same WAN. Depending on the time zones where the server and
workstations are located, we have:
● WAN 1: the time zone difference between the server and the workstation must
be plus or minus one hour or less (available with the educational and professional
version);
● WAN 3: the time zone difference between the server and a workstation must be
plus or minus three hours or less (available with the professional version only);
● WAN 4: the time zone difference between the server and a workstation must be
plus or minus four hours or less (available with the professional version only);
● World WAN: there is no constraint on time zone differences (available with the
professional version only).
2. LAN Support: the Automation Studio™ License Manager and the workstations must
be on the same LAN;
● Temporary WAN Support: the license offers WAN support until a predefined date,
after which it falls back on LAN support.
To be able to use an Automation Studio™ License Manager, you need to know the server’s
URI, as well as two port numbers: the first port corresponds to the “Manager Service” (by
default, port 5301) and the second corresponds to the “Interface Service” (by default,
port 8095).
Figure 2-2: License Manager’s Services
Both services are part of the Automation Studio™ License Manager, and are automatically
started with the server itself. In section 4.4.2 Configuration, you will see how you can stop
each service independently.

 If the machine hosting your Automation Studio™ License Manager does not belong
to your organization, you will also need to know your “Organization ID”. This ID is a
simple character string unique to your organization that you received with your
license numbers.
A “User Account” must have been defined inside the Automation Studio™ License Manager
in order to connect to it. If the user is not recognized, the server will not grant a license to
this user and give him the name “Anonymous”.
 Every Automation Studio™ License Manager has its own list of user accounts.
Defining user accounts is part of the administrative tasks described below.
2.1.2 License Management Interface
The “License Management Interface” is the tool used by the administrator to manage your
network licenses. The management interface can be installed on the same machine where
the Automation Studio™ License Manager is installed, or on another machine that belongs
to your organization or to a third party. A remote access to the Automation Studio™ License
Manager is necessary in case that the License Management Interface is installed on another
machine than the one where the server is installed.
Managing licenses includes the following tasks:

● Set-up the network licenses purchased by your organization;
● Define the user accounts that will be recognized by the Automation Studio™
License Manager;
● Assign license rights to the users.
In addition, the License Management Interface can be used to generate reports of your
licenses usage. These reports may be exported to PDF or Microsoft Excel files.
The administrative tasks are usually not performed by the Automation Studio™ users, but
rather by an “Administrator”.
2.2 Operation Mode

While in use, Automation Studio™ maintains a constant communication with a Project
Server.
2-4
Presentation
When you install Automation Studio™ on a workstation, an Automation Studio™ project

server is also installed on the same machine. Automation Studio ™ is preconfigured to
connect to this local Project Server. This setup corresponds to the single-user mode (Figure
2-3: Single-User Mode).
Figure 2-3: Single-User Mode
To be able to operate in the multi-user mode, you must have purchased the module
“Client/server multi-user” and you must configure Automation Studio™ so it can connect
to a remote Automation Studio™ project server, hosted on a dedicated machine. Both this
machine and the workstation must be on the same network (LAN or WAN).
On Figure 2-4: Multi-user Mode, we can see a multi-user configuration. Note that even if
each workstation has its own local project server, these servers are not used in a multi-
user environment.

Figure 2-4: Multi-user Mode
 When Automation Studio™ connects to the local Automation Studio™ Project Server,
it operates under the single-user mode. It uses the multi-user mode only when it
connects to a remote project server.
2.2.1 Automation Studio™ Project Server
In single-user mode as well as in multi-user mode, the primary role of the project server
is to maintain a table of the open projects with the corresponding users lists.
As with the network Automation Studio™ License Manager, a user account must have been
created on the project server in order to connect to it. The server will name by default an
unknown user "Anonymous".
 Every project server has its own list of user accounts.
In its initial default configuration, Automation Studio™ establishes a connection with the
2-6
Presentation
local project server, using the predefined user “Anonymous”.
Every project server is subject to the following constraint:
 A server can open a maximum of 20 projects simultaneously.
In addition, the following constraints apply for the multi-user mode:

● A maximum of 20 clients can be connected to a project server at the same time;
● A maximum of 10 project servers can be installed on a same LAN.
2.2.2 Application Rights
The Project Server allows you to assign different “Application Rights” to users. These rights
allow or deny access to certain features of Automation Studio™.
The task of defining users and their application rights is usually not performed by the
Automation Studio™ users, but rather by an “Administrator”.
2.2.3 Project and Documents Rights
Project and documents rights are very similar to application rights; for instance, they also
allow or deny access to some features of Automation Studio™ (for users in a specific list).
Both types of rights differ in the source and extent of the constraints:
Source:
● Application rights are defined inside a project server;
Project and documents rights are defined inside a project file.
Extent:
● Application rights affect every project created or opened with the Project Server;
● Project and documents rights affect the project itself or one of its documents,
regardless of the Project Server that is used.
 Every project file has its own list of user accounts.
We call “current User” the user that was used when Automation Studio™ connected to the
project server (launch).

When a new project is created, the current user is the only one that can manage the project
rights. This will allow to:
● Add new user accounts to the list in the project file;
● Assign project and documents rights to the users defined in the project;
● Allow other users the privilege of managing the project rights.
2.3 Authentication Modes

When Automation Studio™ initiates a communication with an Automation Studio™ License
Manager or project server, the application tries to authenticate the user account you chose.
This is necessary to determine which rights are granted.
There are different ways, or “Authentication Modes” that can be used to connect to a
server. An authentication mode is established for each user account when it is created:
● Authentication by Username & Password: when Automation Studio™ is launched,
the user must enter a valid username and password;
 In the current context, the user name and the password are those created for
Automation Studio™. They are not related to the name and password used to log in
to Windows.
● Authentication by Windows Domain User: the user is authenticated based on the
SID (Security Identifier) of the current Windows session that launches Automation
Studio™;
● *Authentication by Computer ID: the user is authenticated based on the
workstation’s unique ID;
 This authentication mode is not available for a project server connection; it is only
available for a licence server;
● Anonymous Authentication: this authentication mode is exclusive to the
“Anonymous” user.
2-8
3 Installing and Starting Automation Studio™
This chapter explains the installation procedure for Automation studio ™. You will also learn how to
configure the application to connect to an Automation Studio™ License Manager. If you are
interested in using the multi-user mode, this chapter will also explain how to configure a connection
to a remote Automation Studio™ Project Server.
3.1 Minimum Required Configuration

Please be sure to have the minimum required configuration:
 Operating System Professional Edition (32-bit or 64-bit): Windows 7 SP1, 8, 8.1, 10 or

Windows Server 2008R2 SP1, 2012, 2012R2 and 2016. It is not recommended to install
Automation Studio™ on a server machine.
 Microsoft Office not required, but if present, must be 32 bit for 32-bit installation of
Automation Studio™ or 64 bit for 64-bit installation of Automation Studio™.
 CPU: Intel Core 2 Duo 1.83 GHz or equivalent. Recommended: Intel Core i7.
 Automation Studio™ takes advantage of multi-core processors.
 Memory: 2 GB more than the amount required by the operating system. Recommended: 3
GB for the 32-bit version and 8 GB for the 64-bit version.
 Graphic Card: Video memory 512 MB and up, with a screen resolution of 1024 x 768
minimum.
 Disk space: 2.5 GB of free space (without considering the catalogues).
 USB port required, to support the protection key

3.2 Installing Automation Studio™

Automation Studio™ Professional must be installed at each workstation on which it will be used.
This chapter describes three installation methods :
● From the DVD;
● From a download;
● Silent installation.
 To install the application, the user must have administrative rights.
3.2.1 Installation from the DVD
Following your purchase, you will receive the application’s installation DVD. For this chapter you
will need the DVD labeled “Automation Studio™ Installer” to execute the following sequence:
● Opening of the DVD dialogue window;
● Installation of prerequisites;
● Automation Studio™ installation;
3.2.1.1 DVD Dialogue Window
Ensure that Windows is set to launch automatically when a DVD is inserted into the player. The
following window appears on the screen after inserting the disc into your player:
Figure 3-1: DVD Dialog
3-2
Installing and Starting Automation Studio™
Here is the description of the elements in the dialogue:
Area Description
User Install Automation Studio™ *You must select 32-bit or 64-bit,

only the compatible version will be highlighted.
? When hovering it with the mouse, information about

compatibility will appear.
Administrator ● Install the Project Server

● Install the Automation Studio™ License Manager
Guides Access to the different Automation Studio™ modules User’s

Guides (Hydraulics & Pneumatics, Catalogue Manager, OPC, etc.)
Tutorials Access to Automation Studio ™ Tutorials: information such as

“What’s new”, “Automation Studio™ P6”, a Quick Start Video,
etc.
Support Installation requirements, FAQ, Contact Your Technical Support

Team.
3.2.1.2 Installation Prerequisites
Before installing Automation Studio ™, it may be necessary to update the computer and install
certain drivers and utilities. Here is the sequence of actions to follow:
1. Make sure all the updates suggested by Microsoft have been installed;
 Do not install Automation Studio™ while you update Windows.
 If you use a Windows Server 2008R2 SP1 64-Bit, go in the Control Panel, under Programs and
Features and make sure that “Microsoft .NET Framework 3.5” (or more) is turned ON.
2. Insert the application’s installation DVD in your DVD drive. If your drive is configured to run
automatically, the autorun file will start and the Figure 3-2: Automation Studio™ version
selection will appear. If not, please open the DVD and double-click on LaunchAS.exe.

Figure 3-2: Automation Studio™ version selection

3. Depending on the compatibility with your system, click the “32-bit” or “64-bit” button in the
middle of the dialogue to launch the installation;
 On this window in the top-right, you have also the possibility to select the installation
language.
The installation of prerequisites is necessary. DirectX drivers are installed each time the installation
is executed.
3.2.1.3 Install Automation Studio™
Once the “32-bit” or “64-bit” button is clicked, the installation of Automation Studio™ starts.
1. Select the language and click on “Continue”;
3-4
Figure 3-3: Automation Studio™ Installation
 The selected installation language is the language in which Automation Studio ™ will be also
launched for the first time. Afterwards, the user can modify it if needed.
2. Read the license agreement. Click “I accept …”, and then click on “Continue”;
Figure 3-4: License Agreement

3. This dialogue requires you to enter your name and your organization information. Once this is
done, click on “Continue”;

Figure 3-5: Customer Identification

4. Choose a destination folder. You can modify the suggested path by clicking on the browse
button . Then click on “Install”;
Figure 3-6: Destination Folder

5. The installation will continue automatically from this point. The wizard will show the
following:
3-6
Figure 3-7: Installation Process

6. The wizard will also open automatically the Famic Technologies website showing the new
features in Automation Studio™;
7. Depending on the programs and features installed in the computer some prerequisites for
Automation Studio™ will appear in the installation process;
Figure 3-8: Prerequisite Installation
Some of the prerequisites are:

● Microsoft .NET Framework
● Microsoft Access Database Engine 2010
● Microsoft Visual C++ 2013 Redistributable Package
● Sentinel Driver
● Text to Speech
8. The installation will continue automatically with Automation Studio ™;

Figure 3-9: Installing Automation Studio™

9. A window will inform you when the installation is done. Click “Finish” to close the window.
Figure 3-10: Installation Completed
3.2.1.4 Installation of a Software Patch
Go to Famic Technologies Inc. Technical Support Portal to download and install the latest updates.
For more details, see section 7.3 Installing a Service Release or a New Version.
3.2.2 Installation from a Download
Installing Automation Studio™ from a download is very similar to the installation from the DVD.
However, you do not have the possibility to install the Automation Studio™ License Manager, Project
Server or to view Automation Studio™ Guides if you proceed with the download method.
Please proceed as follows:

1. Download the full version of Automation Studio™ from Famic Technologies Inc. Technical
Support Portal;
3-8
 Refer to chapter 7 Technical Support to know how to access our Technical Support Portal.
2. Decompress the downloaded file into a temporary folder. Make sure the decompression
preserves the directory structure;
3. Execute the file “setup.exe”, located in the temporary folder.
Then, follow the steps described beginning in sections 3.2.1.2 Installation Prerequisites and 3.2.1.3
Install Automation Studio™.
3.2.3 Silent Installation
In some cases, especially when you have to install Automation Studio ™ on several workstations,
the installation can be done automatically with minimal human intervention.
With the silent installation, no dialogue will appear during the installation process. You will only
notice the new desktop icon created after the installation has ended.
Still the user sets the information for Automation Studio™ but prior to the installation.
These installation settings are:

● Installation language: The selected installation language will be the language in which
Automation Studio™ will be launched for the first time. Afterwards, you may be able to
modify the language if needed.
The available languages are:
Code Language
En English
Fr French
Al German
Ch Chinese
It Italian
Po Portuguese
Es Spanish
● User information: it is possible to set by default the “Company name” and the “User
name”. This information will be later available in the Automation Studio ™ projects and will

be displayed in fields or title blocks.

● Installation folder: the default path to install Automation Studio ™ is “C:\Program Files
(x86)\Famic Technologies\Automation Studio P6.3”. Depending on your operating system,
the latter may be different.
(x86) indicates Automation Studio™ 32 bits and without (x86), 64 bits
P6.3 indicates Professional edition and E6.3 indicates Educational edition.
This option allows you to modify the default path.
In silent installation, the above information can be set by editing the file “AutomationStudio
SilentInstallation.xml”. This file can be found in the Automation Studio ™ installation files and can
be edited using notepad.
If this file is not modified prior to the silent installation, then the default values will be considered:
● Default installation language: English;
● Default installation folder: C:\Program Files (x86)\Famic Technologies\Automation Studio
P6.3.
Figure 3-11: Editing File “AutomationStudio SilentInstallation.xml”
Follow these steps to continue with the silent installation:

1. Open a Command Interpreter: in the Windows’ “Start” menu, type CMD in the “Run” dialogue;
2. Reach the folder that contains Automation Studio ™ installation files by typing CD path at the
prompt (e.g.: CD C:\Install);
3. Type the following in the Command window as shown in the next figure:
setup.exe -s
3-10
Figure 3-12: Command Interpreter Window

4. Press the ENTER key to validate the command;
If necessary, it is possible to check on the Windows Task Manager that the process setup.exe is
running.
 You will know that the installation is completed when a shortcut to the application will
appear on your desktop.
Figure 3-13: Shortcut to Automation Studio™
If the silent installation is executed and Automation Studio ™ is already present on the computer,
then the silent uninstallation will start automatically. You will only notice that the shortcut will
disappear at the end of the process.
Note that you might still need to install a software patch after a silent installation. For more details,
see section 3.2.1.4 Installation of a Software Patch.

3.3 Starting Automation Studio™
After the installation of Automation Studio™, a shortcut to the application appears on your desktop.
Double-click on the shortcut to start Automation Studio ™.
You can also start Automation Studio™ through Windows’ “Start” menu.
3.3.1 Template and Standards Database Update
When there is a new fix or a new release of Automation Studio ™, if any change was made on
enterprise standards (project or document options) a database update must be done, otherwise
Automation Studio™ would not start.
Automatic Update
During the first launch of the new installed version, a warning message is displayed to inform the
user that the standards database must be updated, based on the evolutions included in the new
release of Automation Studio™. For a local mode use of Automation Studio™, this update is done
automatically but the following dialogue is displayed to inform the user about what will be done
by the update tool.
Figure 3-14 : Warning message “Update”
Click “Yes” to continue.

Figure 3-15 : Enterprise Standards Update Dialogue
Progress Window appears; the command is used to finish the update. Now Automation
Studio™ is ready to use.
Manual Update
If your company shares its standards for Automation Studio™ users, it means that the Standards
database is located on a server elsewhere than on the computers using Automation Studio™. In this
case, an administrator with WRITE permissions must do the database update manually on the
server.
To do so, the administrator would launch (from a machine where the new version of Automation
Studio™ is installed) an external application called ASEnterpriseStandardsUpdateTool.exe (would be
found on the Automation Studio™ installation folder). This application would open the dialogue
described above.
3-2
Figure 3-16 : Enterprise Standards Update Tool Dialog

● “Path of the database TemplateASStandards”: the default path corresponds to the
template database that will be used for the update;
● “Path of the database ASEnterpriseStandards”: the default path corresponds to the local
database. If this database is placed on a server, the path must be edited in this field;
● “Progress Bar”: to view the update progress status.
The command is used to finish the update. Now Automation Studio™ is ready to use.
 To see the Enterprise Standard location for an installed version, click on the Automation
Studio™ Options that you will find in the menu .
Automation Studio™ is by default configured to use a local license and operate under the single-
user mode. If this setting answers your needs, you can go to 3.3.3 Quick Start and skip the rest of
this chapter.
If you plan to use a network license, you will need to configure a connection to an Automation
Studio™ License Manager (section 3.3.4.1 Connecting to a Network License).
If you wish to use the multi-user mode, you will need to configure a connection to a remote Project

Server (section 3.3.5 Connection to a Remote ).
3.3.2 Windows firewall
Automation Studio™ does not need to be connected to the Internet to run. Automation Studio™ is
not an internet-based application.
Some messages may appear and are related to internal servers that communicate with Automation
Studio™ via the internal network protocol. In a standalone setup, the communications never get out
of the PC.
When using a multi-user setting, the communications are done between the Automation Studio™
Project Server and the clients’ machines.
The only exception where Automation Studio ™ will attempt to connect to the Internet is when it is
checking for software updates (fixes). By default, this automatic update feature is set to run only
once a month, but it can also be set to be run manually so that you can decide when you will check
for updates.
The Automation Studio™ installation does not turn off the Firewall.
Regarding the exceptions allowed by the Firewall for the entire Automation Studio™ Software, the
following list is provided; some may not apply to your installation (setup):
● During the installation, if the “OPC Server” module is checked, it will add some rules to
allow communication using the OPC protocol (OLE for Process and Control, used in the
Automation industry);
● Also, at the first Automation Studio™ launch, Windows sends a popup message to the user
regarding the approval to run three essential services for internal AS communications. If
the user approves, Windows will add these 3 services in the Firewall Exception List to allow
these communications to go through. Automation Studio™ needs these services in order
to run properly;
Therefore, if we get a warning message like the one shown below, the user may click on “Unblock”
and Automation Studio™ will open normally.
3-4
Figure 3-17: Message from Windows Firewall
3.3.3 Quick Start
Read this section if the initial configuration of the application meets your needs (using a local
license, and operate in single-user mode).
 Before you launch Automation Studio™, make sure that the USB key that contains your
license is connected in the USB port of your workstation.
Automation Studio™ should start normally when you launch the application. However, it is possible
that the dialogue “License Information” (Figure 3-18: “License Information” Dialog) appears before
Automation Studio™ is started: if it happens, check that the USB key that contains your license is
properly connected to your workstation. Then, click the “Retry” button.
 You can update your local license from the “License Information” dialogue. The procedure is
described in section 3.3.4.3 Connecting to a Local License.
If Automation Studio™ refuses to open, and if other dialogue windows appear when you launch the
application, it is probable that the initial configuration of Automation Studio ™ has been modified.
You might want to consult the following sections.
3.3.4 Choosing the License Type
You choose the type of license you want to use (local or network) inside the “Profile Properties”
dialogue (Figure 3-20: “Profile Properties”).

You can access this dialogue by clicking on the “Network Configuration” button in the “License
Information” dialogue (Figure 3-18: “License Information” Dialog). This dialogue appears when
Automation Studio™ cannot obtain a license when it is started. This situation happens if:
● Automation Studio™ is configured to use a local license, but no USB key is connected to the
workstation;
● Automation Studio™ is configured to connect to a remote Automation Studio™ License Manager,

but this server does not have access to any license, or cannot be found.
Figure 3-18: “License Information” Dialog
You can also access the “License Information” dialogue from Automation Studio™: choose the
command “Licenses” in the “Administration” group, under the “Tools” tab (Figure 3-19: “Licenses”
Command).
Figure 3-19: “Licenses” Command
You will see in section 3.3.6 Connection Profiles another method to access the “Profile Properties”
dialog.
3-6
3.3.4.1 Connecting to a Network License
To use a network license, you must configure Automation Studio ™ to connect to an Automation
Studio™ License Manager. To do so, open the “Profile Properties” dialogue (Figure 3-20: “Profile
Properties”) by clicking on the “Network Configuration” button in the “License Information”
dialogue.
The “Profile Properties” dialogue contains items that will be seen later (section 3.3.5 Connection to
a Remote ). Here, we will only describe topics related to licenses (the highlighted part in the above
figure).
Before you connect to an Automation Studio™ License Manager, make sure that:
● The keys that contain your licenses are connected to the USB ports of the machine that
hosts the Automation Studio™ License Manager;
● The Automation Studio™ License Manager is running and configured; for configuration
please refer to the sections 4.4.2 Configuration and 4-16 License Profiles.
Figure 3-20: “Profile Properties”
To configure a connection to an Automation Studio™ License Manager, proceed as follows (the

controls described below are those in the “License” right part section):

● “Automation Studio™ License Manager”: check this radio button;

● “URI”: enter the URI of the running Licence Server or server’s IP;
● “ Port”: enter the Manager Service Port Number of the Automation Studio™ License
Manager (port 5301 by default);
● “Authentication Mode”: choose the authentication mode that matches the user account
you wish to use.
 If you select the “Username & Password” authentication mode, you may enter your
username and password in the reserved fields but it is optional.
● “Organization Identifier”: if the Automation Studio™ License Manager is installed on a
machine you own, simply check the “Default” radio button; otherwise, check the “Other”
radio button and enter your organization ID in the corresponding field.
Clicking on the “Exit Automation Studio” button will quit the application.
When you click on “Retry”, Automation Studio™ will display a dialogue box asking if you want to
save the modifications in the connection profile: choose “Yes” so the profile remembers your
modifications (for more information, see section 3.3.6 Connection Profiles).
If the application successfully contacts the Automation Studio™ License Manager, Automation
Studio™ will proceed with the user authentication.
The authentication is done automatically, unless you chose authentication by Username &
Password, and the required information was not given in the “Profile Properties” dialog: in that
case, you will have to provide the required information in a dialogue like Figure 3-21: “Login”
Dialog.
Figure 3-21: “Login” Dialog
Depending on the permissions, a user might have access to several network licenses: if so,
Automation Studio™ will ask you to choose the license you want to use. In the “Select License”
dialogue (Figure 3-22: “Select License” Dialog), simply highlight the license you want and click
3-8
“Select”.
Figure 3-22: “Select License” Dialog
If the user has access to a single license, the license is automatically selected and the “Select
License” dialogue is skipped.
Automation Studio™ then goes back to the “License Information” dialog. An error message is
displayed in the dialogue if an error occurred in a previous step (Figure 3-18: “License Information”
Dialog). Otherwise, click on “OK” (Figure 3-23: “License Information” Dialogue– Normal) to obtain
the network license and start the application.
Note on the firewall: During the Network Automation Studio™ License Manager’s installation
(which is not recommended to install on a client PC), some rules are added to the Firewall for these
specific program communications.
Figure 3-23: “License Information” Dialogue– Normal

Allocation and revocation of a network license
Once communication with the Automation Studio™ License Manager is established, whether a
network license is granted or not, depends on the configuration of the user account within the
server (section 4.4.7 User Accounts). Moreover, if the license you try to obtain has already reached
its full capacity (already used by the maximum number of users), you will not be able to obtain a
license.
In that situation, if the “Priority Number” (see section 4.4.2 Configuration) is high enough, the user
can still obtain a license that has reached its full capacity. However, this will revoke the license of
a lower-priority user.
 If you choose a license that has reached its full capacity, you will obtain the license only if
one of the current users has a priority lower than yours.
 A lower number indicates a higher priority.
The “License Information” dialogue (Figure 3-18: “License Information” Dialog) appears to inform a
user that the allocated license was revoked. The user might then try to obtain another license.
 If the user fails to obtain another license, nothing will be lost. By choosing the “Close
Automation Studio™” command, the application will prompt the user to save all open
projects.
Apart from the revocation of a license by a higher-priority user, there are other situations that would
make you lose your license:
● The Automation Studio™ License Manager is no longer available due a power failure;
● The manager service has been stopped by an administrator (see section 4.4.2
Configuration);
● The USB key that contains your network license has been unplugged from the Automation
Studio™ License Manager.
3-10
3.3.4.2 Mass Deployment of the Network License’s Configuration
In large companies or schools, manual installation and configuration of Automation Studio™ to use
a server license can be a daunting task. However, this process can be greatly simplified by creating
one default configuration for all users and then deploying this configuration to each workstation.
This chapter will describe step by step this procedure and how to deploy the configuration file.
After installing Automation Studio™, the first step will be to configure the Automation Studio™
License Manager profile (section 3.3.4.1 Connecting to a Network License) for the current user.
Each Windows user has his own personal Automation Studio™ License Manager configuration that
is stored in the Accounts.xml file located in:
%USERPROFILE%\AppData\Roaming\Famic Technologies\Automation Studio <ASversion>\
Where %USERPROFILE% is the location of the current Windows user’s files and
C:\User\<user_name> and <ASversion> stands usually for E6.1 (Educational version) or P6.1
(Professional version).
Figure 3-24 Access to Accounts.xml File
To share this configuration with other users on the same computer, rename the Accounts.xml file
DefaultAccounts.xml and copy this file to:
C:\ProgramData\Famic Technologies\Automation Studio <ASversion>\

Figure 3-25 File Copy/Paste into ProgramData
From now on, whenever a new user starts Automation Studio ™ for the first time on this computer,
the DefaultAccounts.xml file will automatically be copied into that user’s License Manager
configuration.
To deploy the same license configuration to other computers, simply copy the
“DefaultAccounts.xml” file to that computer’s ProgramData directory:
C:\ProgramData\Famic Technologies\Automation Studio <ASversion>\
3.3.4.3 Connecting to a Local License
You can also connect to a local licence.
 Before you launch Automation Studio™, check that the USB key containing your local license
is properly connected to your workstation.
Check the “Local Key” radio button in the “License” section. All other controls in the section should
be disabled, except for the “Update Local Key” button.
Click the “Retry” button to get back to the “License Information” dialog. Automation Studio™ will
display a dialogue box asking if you want to save the modifications in the connection profile: choose
“Yes” and your modifications will be saved (for more information, see section 3.3.6 Connection
Profiles).
3-12
Updating a local license
The “License Information” dialogue allows you to update your local licenses. An update is necessary
if you want to:
● Upgrade your license for a new version of Automation Studio™;
● Add workshops and/or modules to your license.
 The “Update Local Key” button in the “Profile Properties” dialogue (Figure 3-20: “Profile
Properties”) also opens the “Key Update” dialog.
To update your license, follow these steps:

1. Contact Famic Technologies Inc. at production@famictech.com, to get the update code for
your license. You need to provide your 5-digit serial number key;
 If you have an annual maintenance plan, you will automatically receive update codes for
your licenses when a new version is available.
2. Make sure you have the latest version of Automation Studio™, with the latest patches. For
more information, refer to section 3.2.1.4 Installation of a Software Patch;
3. Connect the key that contains your license to the USB port of your workstation;
4. Go to the “License Information” dialogue and click the “Key Update” button.
The “Key Update” window opens;
Figure 3-26: “Key Update” Window

5. Copy and paste the codes you obtained from Famic Technologies Inc. in the “Update Code”
and “Validation Code” fields. The “Network Code” field remains empty.

 The codes in Figure 3-26: “Key Update” Window are not valid. Use ONLY the codes sent to
you by Famic Technologies Inc. for your license.
 Do not write the codes. It is better to copy and paste them in their respective fields.
6. Click on the “Update Key”. A dialogue appears, asking you to confirm that you want to
proceed with the update. Click “Yes”;
7. A dialogue appears to inform you that the update was successful.
3.3.5 Connection to a Remote Project Server
By default, Automation Studio™ connects to the local Project Server. To operate under the multi-
user mode you need to configure the application to connect to a remote server. You can do this
through the “Profile Properties” dialog.
In the “License Information” dialogue (Figure 3-23: “License Information” Dialogue– Normal): from
Automation Studio™, by clicking on the “Licenses” button in the “Administration” group, under the
“Tools” tab (Figure 3-19: “Licenses” Command).
Click on the “Network Configuration” button to open the “Profile Properties” dialog. Now you can
configure Automation Studio™ to connect to the Automation Studio™ Project Server of your choice.
Figure 3-27: “Profile Properties” Dialogue Box – Normal
 The “License” section in the dialogue has already been described above (Figure 3-20: “Profile
3-14
Properties”).
 For the Automation Studio™ Project Server, during its installation, some exception rules are
added to the Firewall for these specific program communications.
Section/Control Description
Section “Project ● Check the “Local” radio button if you want to use the local
Server” Project Server (Single-User Mode).
● Check the “Remote” radio button if you want to use a remote
project server (Multi-user Mode).
If you choose the last case, you must enter (in the “URI” field)
the URI or the IP address of the machine where the Automation
Studio™ Project Server is running.
Subsection
Choose the authentication mode associated with your user
“Authentication”
account on the Automation Studio™ Project Server.
The “Username” and “Password” fields are available only when

the “Username & Password” authentication mode is selected.
Those fields are optional.
Section “License”
Check the “Local Key” radio button if you want to use a local key;
to connect to a Automation Studio™ License Manager (network
license), check the “License Manager” button.
In the latter case, you must provide the following information:

● Enter (in the “URI” field) the URI or the IP address of the
machine where the Automation Studio™ License Manager is
running.
● Enter (in the “Port” field”) the port number used by the
Manager Service in the Automation Studio™ License Manager
(port 5301 by default).
Subsection
Choose the authentication mode associated with your user
“Authentication”

Section/Control Description
account on the Automation Studio™ License Manager.
If you use a remote Project Server, the drop-down box also offers
the option “Identical to the Automation Studio™ Project Server”.
The “Username” and “Password” fields are available only when

the “Username & Password” authentication mode is selected.
Those fields are optional.
Subsection
If the Automation Studio™ License Manager is hosted on your own
“Organization
machine, simply check the “Default” radio button. Otherwise,
Identifier”
check the “Other” button, and enter your organization ID in the
corresponding field.
“Profile Name”
Give a unique local name to the connection profile.
Validate the modifications.
Cancel the modifications and leave the dialog.
?
Get help for the dialog.
The single-user operation mode is obtained when using a profile where the “Local” radio button is
checked under the “Project Server” section. If the “Remote” radio button is checked, the multi-user
mode is obtained.
The diagram in Figure 3-20: “Profile Properties” and Figure 3-27: “Profile Properties” Dialogue Box
– Normal gives an indication on the profile’s configuration, as described in the following table:
3-16
Diagram Project Server License

Local Local
Local Remote
Remote Local
Remote Remote
You must restart Automation Studio™ if you want a change of Automation Studio™ Project Server to
be effective.

 Before you can connect to a remote Automation Studio™ Project Server, make sure this server
is running, and is accessible from your workstation.
If the Automation Studio™ Project Server is not reachable, the next time Automation Studio™ is
launched, the “Profile Properties” dialogue will open (Figure 3-20: “Profile Properties”).
If you chose the “Username & Password” authentication mode and the required information was
not recorded in the section “Project Server”, Automation Studio™ will prompt you with a dialogue
where you will have to provide the required information:
Figure 3-28 : “Login” Dialog
Click on the “OK” button to validate and launch Automation Studio ™. The “Cancel” button closes the
window.
3.3.6 Connection Profiles
Connection profiles have already been mentioned in previous sections: a profile gives the possibility
to regroup all the information required by Automation Studio ™ to connect to any given Project
Server, local or remote.
The license type to be used is also defined in a connection profile. In the case of a network license,
the information required by Automation Studio ™ to connect to the Automation Studio™ License
Manager is also included.
You can define as many connection profiles as you wish, and you can launch Automation Studio ™
using any of these profiles. For instance, you could define the “Work” profile that operates under
the multi-user mode and uses a network license and another “Home” profile that operates under
the single-user mode and uses a local license.
3-18
Figure 3-29: The “Connection Profiles” Command
You can choose what profile you want to use in the “Profiles” (Figure 3-30: “Profiles” Dialog) dialog.
This dialogue appears when Automation Studio™ is launched and the “Automatic Connection”
option is disabled (see below). You can also access the dialogue from Automation Studio™: choose
the command “Connection Profiles” (Figure 3-29: The “Connection Profiles” Command) in the
“Administration” group, under the “Tools” tab.
Figure 3-30: “Profiles” Dialog
The available profiles are displayed in the main part of the dialog. You can select a new default
profile by moving the tick mark in the “Is Default” column. The default profile is automatically
selected when Automation Studio™ is launched, when the “Automatic Connection” option is
activated.
Name Description
Create a new connection profile.
Remove the selected connection profile.
Modify the selected connection profile.
You can also double-click on a profile to modify it.

Name Description
Automatic
When activated, the default connection profile will be automatically
Connection
selected the next time Automation Studio™ is launched.
If this option is activated, and if a default connection profile exists, the

application will not show the “Profile” dialogue next time it is launched.
Validate modifications.
Exit Automation
Leave the application.
Studio™
?
Show contextual help for the dialog.
 A connection profile called “Anonymous” is created when Automation Studio™ is installed.

This profile specifies a connection with the local Project Server with the user “Anonymous”,
and indicates that a local license is to be used. Automation Studio ™ is initially configured to
automatically select this profile when it is launched (for more information, refer to
section 3.3.3 Quick Start).
To select the connection profile you wish to use, simply select it in the upper part of the dialog, and
click on . If you wish that Automation Studio™ automatically selected that profile in the
future, mark the profile as the default one and check the “Automatic Connection” option.
The diagram displayed in the lower part of the dialogue summarizes the selected profile’s
configuration.
 To effectively change the profile you are using, you will need to restart Automation Studio ™.
3-20
4 Automation Studio™ License Manager
This chapter does not apply to you if you plan only to use local licenses.
You will learn in this chapter how to install and start the components that are required to
use network licenses. You will also learn how to use the License Management Interface to
manage your network licenses.

 Operating System Professional Edition (32-bit or 64-bit): Windows 7 SP1, 8, 8.1, 10

or Windows Server 2008R2 SP1, 2012, 2012R2 and 2016.
 TCP/IP Protocol.
 100 MB of available hard-disk space
 USB port required, to support the protection key
4.2 Installing Automation Studio™ License Manager

This section explains how to install the Automation Studio™ License Manager, in the case
where your organization wants to host its own server. If the machine that hosts your server
belongs to a third party organization, you can proceed to section 4.3 Installing the License
Management Interface.
To install the Automation Studio™ License Manager, insert the DVD labeled “License
Manager Installer, Project Server Installer” in the target machine’s DVD-player. When the
DVD dialogue appears (Figure 4-1: Installation Menu, “Administrator” Section), click the
highlighted button 32-bit or 64-bit (the Version Identifier is selecting automatically the
compatible version for your computer), this will start the installation.

 In case both buttons are highlighted select the 64-bit.
“Project Server” will be available only for the professional version.
Figure 4-1: Installation Menu, “Administrator” Section
An information dialogue will appear. Carefully read the information and click on “Install”.
This window will be displayed:
Figure 4-2 : Automation Studio™ License Manager Installation
4-2
Automation Studio™ License Manager
If you plan to manage, the licenses from the computer where the server service is installed,
select both “Server” and “Client” check boxes.
If you plan to install the License Management Interface (“Client”) on a different machine
than the Automation Studio™ License Manager (“Server”), select only “Server” and click
“Next” (see Figure 4-2 : Automation Studio™ License Manager Installation). In this case,
you must edit a configuration file to ensure access to the configuration screen:
1. Open the file « ASNETLMPref.config » with a text editor (e.g. Notepad), you will find
the file in: « C:\ProgramData\Famic Technologies\Automation Studio ».
2. The fourth line is the line where you have to do modifications:
<add key="ConfAccesslpList" value="127.0.0.1;::1"/>
3. Modify this line as it follows:
● To access the Automation Studio™ License Manager from a client located on a
certain machine:
<add key="ConfAccesslpList" value="127.0.0.1;[IP];::1"/> (replace the [IP] with
the computer’s IP where the client will be installed)
● To access the Automation Studio™ License Manager from a client located on any
computer from a network:
<add key="ConfAccesslpList" value="127.0.0.1;*;::1"/> (replace the [IP] with
the *)
4. Save the file in the new configuration.
 If your server has two or more Ethernet cards, you have the possibility to choose,
which card the Automation Studio™ license manager should use. To do this open the
file “ASNETLM.config.xml” (located in C:\ProgramData\Famic
Technologies\Automation Studio) with a text editor (e.g. Notepad). The second line
is the line where you have to do modifications; at the end of the line add
EthernetAdapter=”IP Address”.
 Enter the IP address for the selected Ethernet card. The line should have the
configuration shown in the following example: <ASLService name="servername"
ServiceDefaultPort="5301" EthernetAdapter="192.168.0.4">

4.3 Installing the License Management Interface

The License Management Interface is the tool installed on a machine that belongs to your
organization. The tool is used to remotely manage your network licenses. This section
explains how you can install a management interface.
To install the License Management Interface, insert the DVD labeled “License Manager
Installer, Project Server Installer” DVD player of the machine where the interface should be
installed.
 Automation Studio™ does not need to be installed on the same machine where the
License Management Interface will be installed.
When the DVD dialogue appears (Figure 4-1: Installation Menu, “Administrator” Section),
click the highlighted button 32-bit or 64-bit. When you are asked to select the features to
install (Figure 4-3: License Management Interface installation), choose only “Client” and
click on “Install”.
Figure 4-3: License Management Interface installation
4.4 Using the License Management Interface

This section explains all the tasks you can perform on your licenses.
These administrative tasks are usually not performed by an Automation Studio ™ user, but
4-4
rather by an administrator.
4.4.1 Starting the License Management Interface
Before you start the License Management Interface, check that:

● The keys with your licenses are connected to the USB port of the computer where
Automation Studio™ License Manager (Server) it is installed;
● The Automation Studio™ License Manager is running.
 If a firewall is active on the machine that runs the Management Interface, make
sure the communication with the Automation Studio™ License Manager is allowed.
The communication is done using the ports 8095.
Once the Management Interface has been installed, it can be started by clicking on the
“Automation Studio License Management” shortcut that has been created in “Start” →
“Programs” → “Automation Studio License Management”:
Figure 4-4: Automation Studio License Management
The “Authentication” dialogue will appear and prompt you for your administrator name
and password:
Figure 4-5: “Authentication” Dialogue for the License Management Interface
 The management interface will only start with a user account that has been tagged
as an administrator in the License Manager. The user “administrator” is initially

created for you, with the password admin.
Clicking on the “Advanced” button will display the “Advanced Settings” Dialogue (Figure
4-6: “Advanced Settings” Dialogue for the License Management Interface), where you can
enter the URI for the Automation Studio™ License Manager, and the port for the interface
service inside the Automation Studio™ License Manager.
 If the machine that hosts your Automation Studio™ License Manager belongs to your
organization, you do not need to modify the “Organization ID” field (“Default” by
default). Otherwise, you will need to type in the ID you received with your license
numbers.
The next time you start your Management Interface, it will remember the information
provided in the “Advanced Setup” dialog. Normally, you will not have to return to that
dialog.
Figure 4-6: “Advanced Settings” Dialogue for the License Management Interface
The “Authentication” dialogue also has a button “Forgot your password?” When you click
on it, you can initiate the process to generate a new password for the administrator, whose
name and email are entered in the dialogue “New Password” (Figure 4-7: “New Password”
dialog). The new password will be sent to the email address entered if it matches with the
address on the server.
Figure 4-7: “New Password” dialog
Once all the information have been correctly entered in the filled in the “Advanced Setup”
dialog, and when you have entered the information in the “Authentication” dialog, clicking
4-6
on the “Sign In” button will launch the Management Interface.
The Management Interface window includes a sidebar on the left side (Figure 4-8: Sidebar,
License Management Interface), with which you select what you wish to display in the
main part of the window. The information shown in this main part will evolve according to
the current action.
The sidebar is divided into two groups: “License Manager” and “Administration”. Click the
title of a group to show its contents.
Finally, you can hide the sidebar by clicking on the pushpin displayed in the top right corner
of the sidebar. A “Menu” button will then replace the sidebar. Drag the mouse on this
button to display the sidebar.
Figure 4-8: Sidebar, License Management Interface

4.4.2 Configuration
You can access the “Configuration” screen by clicking on the icon in the sidebar
(under the “License Manager” group).
The “Configuration” screen allows you to define the network licenses bought by your
organization. You can also update or delete licenses.
 If you do not have access to the configuration screen, please verify that the
configuration file of the Automation Studio™ License Manager has been modified
like described in the section 4.2 Installing Automation Studio™ .
The “Configuration” screen has three main parts:
Figure 4-9: License “Configuration” Screen
“General Information” Part
This part contains two fields:

● “Name”: An arbitrary name to identify the Automation Studio™ License Manager
with the URI you entered in the “Advanced Setup” dialogue (Figure 4-6: “Advanced
Settings” Dialogue for the License Management Interface);
● “Connection Port”: The port assigned to the manager service, inside the
Automation Studio™ License Manager (port 5301 by default).
“Action” Part
This part contains the buttons that allow you to stop and restart the manager service (the
interface service is not affected).
4-8
 To apply the modifications you make in the “Configuration” screen, you need to
restart the manager service.
 Note that Automation Studio ™ will not be able to communicate with the Automation
Studio™ License Manager if the manager service is stopped.
“Available Licenses” Part
This part initially lists the network licenses that have been defined. The following table
explains the meaning of the columns:
Column Description
Click this button to update the network license.
Number Network license number. You have to type this number

when you define a license, this correspond with the 5
digit from the protection key.
Name Name of the network license. You have to type a name

when you define a license. This name is used when
licenses are granted, and in the “Select License”
dialogue (Figure 3-22: “Select License” Dialog). We
recommend these names to be related to the workshops
you have on the key (e.g. Hydraulic, Electrical…)
Connected This box shows whether the license is connected and is

“valid”.
A license is valid if it can be found on a USB key
connected to the Automation Studio™ License Manager.
Version If the network license is valid, this field shows the

Automation Studio™ version defined in the license.
Max. Users If the network license is valid, this field shows the
capacity of the license, i.e. the maximum number of
users allowed to use the license simultaneously.
Expiration Date If the network license is temporary, this field shows the

Column Description
license expiration date..
Scope If the network license is valid, this field shows the scope
of the license. This can be LAN or WAN, see 2.1.1
Automation Studio™ License for more details.
WAN Expiration If the network license is valid and supports the WAN
functionalities, this field shows expiration date for the
WAN support (if applicable).
The and buttons are used to add a new license or remove the selected one.
Any modification to this screen, including the definition of a new license and the deletion
of a license, will be saved only when you click on the “Apply” button on the
bottom right corner of the screen. When you click this button, the Automation Studio™
License Manager checks the validity of the licenses.
You will have to restart the manager service for your modifications to be applied (see the
“Action” part above).
As long as you did not click on the “Apply” button, all your modifications can be cancelled
by clicking on the “Reset” command , or by leaving the “Configuration” screen.
 You can leave the current screen and cancel the modifications by choosing an item
in the sidebar or an action in the main menu.
Defining a New License
You can define a new license clicking on the button above the list. You can also right-
click on the list and choose “Add” in the pull-down menu that appears.
Then, you have to fill the “Number” and “Name” fields in the new row. You can put any
information you choose in the “Name” field. Your license numbers were given to you when
you bought them and they correspond with the five digits from the USB key.
Updating a Network License
You can update any of your network licenses if you want to:
4-10
● Increase you license capacity;

● Upgrade your license for a new version of Automation Studio™;
● Add workshops and/or modules to your license.
To update a license, you must first contact Famic Technologies Inc. at

production@famictech.com, to get the Update Code for your license.
 If you have an annual maintenance plan, you will automatically receive update
codes for your licenses when a new version is available.
Once you received your Update Codes, you can click on the “Update” button to proceed
with the actual update (the button is to the left of the license number).
The “License Update” dialogue will appear:
Figure 4-10: “License Update” dialogue
Enter the codes you have received in the “Update Code”, “Validation Code” and “Network
code” fields, and click on “Apply”.
 The codes in Figure 4-10: “License Update” dialogue are not valid. Use ONLY the
codes sent to you by Famic Technologies Inc. for your license.
 It is recommended not to type the codes but to copy and paste them in their
respective fields.
 If you do not have a “Network Code“, these codes are possibly meant for a
standalone license. Before you continue, please verify the key type.
 It is not possible to update standalone licenses using the network license manager
because the network code is required. You can use Automation Studio™ to update

any type of key.
4.4.3 Reports
You can access the “Reports” screen by clicking on the icon (“Reports”) in the toolbar
(under the “License Manager” group).
The “Reports” screen allows you to generate reports, in order to obtain useful information
on your license usage.
The screen shows the list of available reports (Figure 4-12: “Reports” Screen). You select
the report you desire by double-clicking on its name.
 In this as in other screens, you can reorder the lines in the table by clicking on a
column header: for instance, if you click once on “Description”, the lines are sorted
in increasing alphanumeric order according to their descriptions. A small upward
arrow then appears next to the header’s title. A second click on the header inverts
the ordering, and the small arrow then points downward.
Figure 4-11 : Ordering the lines by their descriptions:

Alphanumeric order ascending or descending
 In this as in other screens, you can filter the displayed reports by entering a character
string in the field at the top of the screen, and by clicking on the “Search” button.
The list will then only display the reports whose description contains the character
string.
Reports can be exported to PDF or Microsoft Excel format: .
4-12
Figure 4-12: “Reports” Screen
License Usage Summary Report
The License Usage Summary report gives information on your network licenses’ usage in
a simplified form.
Figure 4-13: License Usage Summary Report
In the “License” box of the “Filter(s)” area, you can choose the license you want to display.
Choose “(All)” to obtain information about all your licenses.
The “From” and “To” controls allow you to specify the period you are interested in.
With the “License” and “User name” radio buttons, you can choose how you want to group
the results.
Finally, click the “Refresh” button to update the report.
The following figure shows how the report from the Figure 4-13: License Usage Summary

Report looks like when it is grouped by user name.
License Usage Summary

User name Usage hours
Anonymous 1.09
LAP0702f65b9d .81
JohnDoe 1.40
Total 3.30
Figure 4-14: License Summary Report, grouped by user name
License Usage Details Report
The License Usage Details report gives complete information on your network license
usage.
Figure 4-15: License Usage Details Report
Controls for this report are the same as for the License Usage Summary report.
If you enter a string in the “User name” field, the report will display only those sessions
where the user name contains the string. Leave the field empty if you want to view the
information for AllUsers.
The following figure shows the same report as in Figure 4-15: License Usage Details Report,
4-14
grouped by user name.

Licence Usage Details, grouped by User Name
User Name Computer Date IP Adress License Hours
LOC\jdoe PC10.famictech.com 2010-11-01 10:54 172.17.10.72 Hydraulic Engeneering ( 57033) .10
PC10.famictech.com 2010-11-03 11:43 172.17.10.72 Hydraulic Engeneering ( 57033) .02
Subtotal .12
jdupont PC10.famictech.com 2010-11-03 11:57 172.17.10.72 Hydraulic Engeneering ( 57033) .03
Subtotal .05
tester1 PC10.famictech.com 2010-11-01 09:23 172.17.10.72 Hydraulic Engeneering ( 57033) 1.58
Subtotal 1.71
Figure 4-16 : License Usage Details, grouped by User Name
Licenses in Use
This report allows you to view which licenses are currently in use, by which users, and for
how long.
Figure 4-17 : Licenses in Use Report
You can choose which license you want to view in the “License” box. Choose “(All)” to
obtain information about all your licenses.
If you enter a string in the “User name” field, the report will display only those sessions
where the username contains the string. Leave the field empty if you want to view the
information for AllUsers.
Finally, click the “Refresh” button to update the report.
Available Licenses
This report allows you to know which licenses are available on the Automation Studio™

License Manager. The report also informs you about the workshops and modules in each
license.
Figure 4-18 : Available Licenses Report
You can choose which license you want to view in the “License” box. Choose “(All)” to
obtain information about all your licenses.
Use the “Refresh” button to update the report.
4.4.4 License Profiles
To be able to launch Automation Studio™ and use the application, you must obtain a license.
Some constraints can apply when a user tries to obtain a license:
● The user can have no access to some of the organization’s network licenses;
● The user can have access to a network license only from certain particular
workstations;
● The user can have access to a network license only according to some schedule.
All these constraints constitute the user’s “permissions”. As an administrator, you can
4-16
define the permissions of users in a very precise way.
To do this, you must first define the “License Profiles”. Then, you decide for each user
which profiles they belong to. Permissions for a user are derived from the profiles they
belong to.
 You can think of a profile as a set of users that share the same permissions.
 A Automation Studio™ License Manager initially contains a single license profile

called “AllUsers”. This is a special profile that always contains all the users defined
in the server.
Apart from the profile “AllUsers”, a user may belong to many license profiles. Refer to
section 4.4.7.4 Deduction of Permissions to learn how the permissions are decided for a
user that belongs to multiple profiles.
Users License Profiles

Figure 4-19: Users and License Profiles
4.4.4.1 License Profiles List
You can access the list of licenses “Profiles” screen by clicking on the icon (“Profiles”)
in the sidebar (under the “Administration” group).

Figure 4-20: License “Profiles"
The profiles that are currently known to the Automation Studio™ License Manager are
shown in a tabular format in the main part of the screen.
 By clicking a column header, you can change the display order of the lines.
 To filter the displayed profiles, type a string in the field above the table and click
the “Search” button. The table will only display the profiles corresponding to the
string you entered.
The buttons and allow you respectively to create a new profile and delete the
selected one. The creation of a new profile opens the Figure 4-21: License profile details
screen (section 4.4.4.2 Creating a License Profile below).
This contextual menu will appear if you make a right-click on a profile in the table:
Action Description
Create a new Profile To create a new license profile (open the “License Profile
Detail” screen).
Set as Default Set the current profile as the default profile.
Change Profile Status Toggle the activation status for the selected profile, from
“Active” to “Inactive” or vice versa.
Delete Delete the selected profile.
 At any time, a single profile is defined as the default profile. Initially, the profile
“AllUsers” is the default profile and every newly created user belongs to “AllUsers”.
When another profile is set as the default profile, then every newly created user
4-18
belongs to that profile and to “AllUsers”.
 The profile “AllUsers” cannot be deleted.
4.4.4.2 Creating a License Profile
To create a new profile, go to the Figure 4-20: License “Profiles" and click on the button.
You can also choose the command “Create a New Profile” from the contextual menu that
appears when you right-click on the main part of the screen.
When you create a new profile, the Figure 4-21: License profile details screen appears. This
screen has five parts:
Figure 4-21: License profile details screen
“General” Part
The information you provide here also appears in the Figure 4-20: License “Profiles".
You must choose a name for the profile in the “Name” field. If you wish, you can also enter
a short description for the profile in the appropriate field.

The “Is the default profile” box indicates whether the profile is set as the default profile or
not.
 Setting the profile as the default one is done via the contextual menu that appears
when you right-click on the main part of the Figure 4-20: License “Profiles".
The “Active” checkbox allows you to modify the activation state of the profile, from
“Active” to “Inactive”, or vice versa.
The “Priority” field allows you to assign a priority number to the member of the profile:
the number is chosen between zero (maximal priority) and 100 (minimal priority).
“License(s)” Part
In this part, you can choose the network licenses that can be granted to the members of
the profile.
For the users who are only members of the current profile, “Undefined” is equivalent to
“Denied”. For more details, refer to section 4.4.7.4 Deduction of Permissions.
“Members” Part
In this part, you can choose the users that belong to the profile.
The users that are member of the profile appear under “Selected”. All other users are under
“Available”.
Use the “>” and “<” arrows to move a selected user from “Available” to “Selected”, or vice
versa.
Use the “>>” and “<<” double arrows to move AllUsers under “Available” to “Selected”, or
vice versa.
 You can also define the profiles a user belongs to from the “User Details” screen, as
explained in section 4.4.7.2 Creating a User Account.
“Access Schedules” Part
In this part, you can choose the schedules under which member users are allowed access
to the licenses.
4-20
The access schedules permitted appear under “Selected”. All other access schedules are
under “Available”.
Use the “>” and “<” arrows to move a selected schedule from “Available” to “Selected”,
or vice versa.
Use the “>>” and “<<” double arrows to move all schedules under “Available” to
“Selected”, or vice versa.
If no access schedule is chosen, the member users can access the licenses anytime. In that
case, the string “Anytime” appears under “Selected”.
If several schedules are selected, the schedule constraints to which the users are subject
correspond to the union of the constraints imposed by the selected schedules: for example,
let us suppose that the following schedules are selected in a profile:
● “Week”: access licenses from Monday to Friday, from 8:00 AM until 7:00 PM;
● “Weekend”: access licenses only on Saturday and Sunday, from 8:00 AM
until 7:00 PM.
Users member of that profile have access to the licenses every day of the week,
from 8:00 AM until 7:00 PM.
“Access Points” Part
In this part, you can define from which locations (workstations) member users are allowed
access to the licenses.
The access points permitted appear under “Selected”. All other access points are under
“Available”.
Use the “>” and “<” arrows to move a selected access point from “Available” to “Selected”,
or vice versa.
Use the “>>” and “<<” double arrows to move all accesses points under “Available” to
If no access point is selected, the member users can access the licenses from anywhere.
In that case, the string “Anywhere” appears under “Selected”.
If several access points are selected, the users will have access to licenses from any

workstation defined in at least one of the access points.
4.4.4.3 Modifying a License Profile
To modify an existing profile, you must double-click on the line of the profile in the “License
Profiles List” screen. This action opens the Figure 4-21: License profile details screen where
the profile can be edited.
 You can change the activation state of a profile via the contextual menu that appears
when you right-click on the profile in the main part of the “License Profiles List”
screen.
 You cannot modify the name of the “AllUsers” profile. Also, the “Members” part is
disabled (since every user is always a member of that profile).
Any modification to the “License Profile Details” screen is saved only when you click on
the “Apply” button in the bottom right corner of the screen.
If you did not click the “Apply” button, you can cancel the modifications by clicking on the
“Reset” button, or by leaving the screen.
4.4.5 Access Points
Access points are used to define location constraints that apply to the members of a profile.
The constraints consist in a list of allowed IP addresses.
The access points you define appear in the “Access Points List” part of the Figure 4-21:
License profile details screen.
4.4.5.1 Access Points List
You can access the “Access Points” list screen by clicking on the icon (“Access
Points”) in the sidebar (under the “Administration” group).
4-22
Figure 4-22: “Access Points” list screen
The access points that are currently known to the Automation Studio™ License Manager are
shown in a tabular format in the main part of the screen.
 To filter the access points, type a string in the field above the table and click on the
“Search” button. The table will only display the access points corresponding to the
string you entered.
The buttons and allow you respectively to create a new access point or delete one
of them. These actions are also offered in the contextual menu that appears when you
right-click on the main part of the screen.
4.4.5.2 Creating an Access Point
To create a new access point, go to the Figure 4-22: “Access Points” list screen and click
on the button. You can also choose the command “Create a New Access Point” from
the contextual menu that appears when you right-click in the main part of the screen.
When you create a new access point, the Figure 4-23: “Access Point” details screen
appears. This screen has two parts:

Figure 4-23: “Access Point” details screen
“General” Part
The information you provide here also appears in the Figure 4-22: “Access Points” list
screen.
You must choose a name for the access point in the “Name” field. If you wish, you can also
enter a short description for the access point in the appropriate field.
“Access Point Identification” Part
This part lists the IP addresses already defined in the current access point.
To remove an address from the access point, select it and click on the button.
To add a new address, proceed as follows:
● Click the button. You can also right-click anywhere on the “Access Point
Identification” part, and select “Add” in the contextual menu that appears;
● In the adjacent field, type the IP address you want to authorize.
Masks can be used for IP addresses: for instance, the IP address 172.16.*.* authorizes all
addresses from 172.16.0.0 to 172.16.255.255. Each of the bytes in the address can be
4-24
replaced by the character “*”.
4.4.5.3 Modifying an Access Point
To modify an existing access point, you must double-click on the line of the access point
in the Figure 4-22: “Access Points” list screen. This action opens the Figure 4-23: “Access
Point” details screen, where the access point can be modified.
Any modification to the Figure 4-23: “Access Point” details screen is saved only when you
click on the “Apply” button in the bottom right corner of the screen.
If you did not click the “Apply” button, you can cancel the modifications by clicking on the
“Reset” button or by leaving the screen.
4.4.6 Access Schedules
Access schedules allow you to define access constraints, which apply to the members of a
profile. The constraints concern access time.
The access schedules you defined appear in the “Access Schedules List” part of the “License
Profile Details” screen.
4.4.6.1 Access Schedules List
You can access the “Access schedules” list screen by clicking on the icon (“Access
Schedules”) in the sidebar (under the “Administration” group).
Figure 4-24: “Access Schedules” list screen
The access schedules that are currently known to the Automation Studio™ License Manager

are shown in a tabular format in the main part of the screen.
 By clicking on a column header, you can change the display order of the lines.
 To filter the access schedules, type a string in the field above the table and click the
“Search” button. The table will only display the access schedule corresponding to
the string you entered.
The buttons and allow you respectively to create a new access schedule or delete
the selected one. These actions are also offered in the contextual menu that appears when
you right-click on the main part of the screen.
4.4.6.2 Creating an Access Schedule
To create a new access schedule, go to the Figure 4-24: “Access Schedules” list screen and
click on the button. You can also choose the command “Create a New Access Schedule”
from the contextual menu that appears when you right-click on the main part of the screen.
When you create a new access schedule, the Figure 4-25: “Access Schedule” details screen
appears. This screen has three parts:
Figure 4-25: “Access Schedule” details screen
“General” Part
The information you provide here will appears in the Figure 4-24: “Access Schedules” list
screen.
4-26
You must choose a name for the access schedule in the “Name” field. If you wish, you can
also enter a short description for the access schedule in the appropriate field.
“Time” Part
In this part, you can define the period of the day during which you want to allow access to
the licenses.
You have to specify the start and end access period in the HOUR/MINUTE/SECOND format.
You can use either 24 hours or AM/PM format.
 If you want to allow access during the whole day, select “00:00:00” (or
“12:00:00 AM”) to “24:00:00” (or “12:00:00 PM”) for the start and end hours.
“Recurrence Pattern” Part
In this part, you have to activate the checkbox for each day of the week where you want
to authorize access to the licenses, according to the selected hours of the previous part.
4.4.6.3 Modifying an Access Schedule
To modify an existing access schedule, you must double-click on the line of the access
schedule in the Figure 4-24: “Access Schedules” list screen. This action opens the Figure
4-25: “Access Schedule” details screen, where the access schedule can be modified.
Any modification to the “Access Schedule” details screen is saved only when you click on
the “Apply” button in the bottom right corner of the screen.
If you did not click on the “Apply” button, you can cancel the modifications by clicking on
the “Reset” button or by leaving the screen.
4.4.7 User Accounts
The “User accounts” screen allows you to define the users that will be recognized by the
Automation Studio™ License Manager.
Every user is member of the profile “AllUsers” and can be a member of many other profiles.
The user’s permissions are determined by the profiles the user belongs to.
 If your user account does not exist in the Automation Studio™ License Manager, you

will be asked to confirm the username and the password and to try to connect one
more time. The network Automation Studio™ license manager will not give a license
until a user name and password is entered correctly.
4.4.7.1 Users List
You can access the “Users List” screen by clicking on the icon (“User Accounts”) in
the sidebar (under the “Administration” group).
Figure 4-26: “Users Accounts” Screen
The user accounts that exist in the Automation Studio™ License Manager are displayed in
a tabular format in the main part of the screen.
 To filter the displayed user accounts, type a string in the field above the table and
click the “Search” button. The table will only display the user accounts that contain
the string in the field you selected.
The button allows you to create a new user account. These actions are also offered in
the contextual menu that appears when you right-click in the main part of the screen. The
creation of a new profile opens the Figure 4-27: “User Account” details screen (section
4.4.7.2 Creating a User Account).
To remove a user from the user accounts’ list, select it and click on the button.
Right clicking on a user in the main part of the screen shows a contextual menu, from
which you can “Create a New User Account”, or change the selected user’s activation state:
● “Active”: the normal mode of operation;
4-28
● “Inactive”: the user cannot be used to open an Automation Studio™ session. The
user cannot be included in any profile;
● “Suspended”: the user cannot be used to open an Automation Studio™ session.
However, the user can be included in any profile.
A user can also be put in the “Quarantine” state, which is similar to the “Suspended” state.
This state, however, cannot be set manually: a user is automatically put in the “Quarantine”
state, when the number of failed access attempts exceeds the authorized limit (see
section 4.4.8 License Management Interface Options).
 You can choose the activation state assigned by default to any new user in the main
options of the interface (see section 4.4.8 License Management Interface Options).
 A Automation Studio™ License Manager initially contains two user accounts:

“Administrator” and “Anonymous”.
4.4.7.2 Creating a User Account
To create a new user account, go to the “User Accounts” screen and click on the button.
You can also choose the command “Create a New User Account” from the contextual menu
that appears when you right-click in the main part of the screen.
When you create a new user account, the “User Account Details” screen appears (Figure
4-27: “User Account” details screen). This screen has five parts:

Figure 4-27: “User Account” details screen
“General”, “Access” and “New Password” Parts
In the “General” part, you must provide user’s full name and email address, in the
appropriate fields.
The “Status” box in the “Access” part allows you to modify a user’s activation state.
Check the “Can administrate GDA” checkbox to give the user administrative rights. The user
can then manage the licenses from the License Management Interface.
 To be administrator, the user must use the Username & Password authentication
mode.
To choose the user’s authentication mode and provide the required information, follow the
steps below:
 The Anonymous authentication mode is reserved exclusively for the “Anonymous”
4-30
user, and cannot be used by any other user.
Authentication by Username & Password

● In the “Access” part, select “Username & Password” in the “Type” box;
● In the “Username” field (“General” part), enter the user account name. The user
will need to provide this name when Automation Studio™ will be launched;
● In the “New password” part, you can fill the “Password” and “Re-enter password”
fields. The user will need this password when Automation Studio™ will be
launched.
 In the current context, the user’s name and password are created for Automation
Studio™ only. There is no connection with the name and password used to log on
to Windows.
If you omit to enter a password, the Management Interface will ask whether it must
generate automatically a password for the user (Figure 4-28: Automatic Creation of a
Password) when you click the “Apply” button. This password will be sent to the e-mail
address you supplied for the user.
Figure 4-28: Automatic Creation of a Password
If you check the “Must change password” checkbox, the user will be asked to modify the
password next time Automation Studio™ will be opened (or the License Management
Interface, if user has the administrator’s rights).
Authentication by Windows Domain User

● In the “Access” part, select “ Windows Domain User” in the “Type” box;
● In the “Username” (“General” part), click the button next to the “Username”
field;
● The standard “Select User” dialogue opens and you have to find and select the
Windows user you want;
● The “Full name” (“General” part) and “GUID” (“Access” zone) fields are filled

automatically with the appropriate values;

● You also have to fill the “Username” field in the “General” part.
For this authentication mode, you must ignore the “New password” part.
Figure 4-29: “Select User” Dialog
Hybrid Authentication
The hybrid authentication mode allows a user to use either the Username & Password, or
the Windows Domain User authentication modes.
To use this mode, first select “Both Modes” in the “Type” box of the “Access” part. Then,
you have to proceed in the same way as for Windows Domain User authentication mode.
Finally, you have to enter the necessary information in the “New password” part, just as
you do for the Username & Password authentication mode.
Authentication by Computer ID
For this authentication mode, you proceed in the same way as for the authentication by
Username & Password. However, the “Machine Identifier Generator” utility is used to get
the values to be entered in the “Username” field (“General” area) and “New password”
area.
You can launch the generator by clicking on the shortcut “Machine Identifier Generator” in
“Start” → “Programs” → “Automation Studio Licence Management”:
4-32
Figure 4-30 : Machine Identifier Generator
When you launch the generator on the target machine, a window is displayed with the
required codes. Simply copy the contents of the “Name” field to the “Username” field in
the “User Account Details” screen, and copy the contents of the “Code” field into the field
in the “New Password” section.
Figure 4-31 : “Machine Identifier Generator” window
“Profiles” Part
In this zone, you can indicate the profiles the user account belongs to.
The profiles the user belongs to are shown under “Selected”. All other profiles appear
under “Available”.
Use the “>” and “<” arrows to move a selected profile from “Available” to “Selected”, or
vice versa.
Use the “>>” and “<<” double arrows to move all profiles under “Available” to “Selected”,
or vice versa.
 You cannot move a user out of the “AllUsers” profile.
“License(s)” Part
This part summarizes the user’s permissions, by showing which network licenses can or
cannot be granted to the user. These permissions are derived from the profiles the user
belongs to.

4.4.7.3 Modifying a User Account
To modify an existing user account, you must double-click on the line of the user account
in the Figure 4-26: “Users Accounts” Screen. This action opens the Figure 4-27: “User
Account” details screen, where the user can be modified.
 You can change a user’s activation state from the contextual menu that appears
when you right-click on the user in the Figure 4-26: “Users Accounts” Screen.
 You cannot modify the “Anonymous” user. Double-clicking on this user in the Figure
4-26: “Users Accounts” Screen has no effect.
Any modification to the Figure 4-27: “User Account” details screen is saved only when you
click on the “Apply” button in the bottom right corner of the screen.
the “Reset” button, or by leaving the screen.
4.4.7.4 Deduction of Permissions
A user can be member of several profiles, which can grant contradictory permissions. This
section explains how these contradictions are resolved, to deduce a user’s permissions.
Let us suppose that you created a user called “JohnDoe”, that you declared to be member
of the profile “TestProf”. The user is also, by definition, member of the profile “AllUsers”.
 A disabled profile is not considered in the deduction of its users’ permissions.
What happens for “JohnDoe” if both profiles do not agree on the permissions to grant their
respective members, for a given network license?
● The license is granted to “JohnDoe” if at least one of the profiles grants the license
to its members, and no profile denies it;
● In all other cases, “JohnDoe” is denied the license.
4-34
The following table illustrates how the permissions are deduced:
User Permission Permission

Permission “AllUsers” “TestProf”
Denied Undefined Undefined
Denied Undefined Denied
Granted Undefined Granted
Denied Denied Denied
Denied Granted Denied
Granted Granted Granted
In the same manner, what would be the priority number given to “JohnDoe” if both profiles
disagree in that respect?
 A user’s priority number corresponds to the smallest priority number defined in all
the profiles the user belongs to.
For instance if “TestProf” and “AllUsers” respectively assign the priority numbers 10 and 60
to their members, then “JohnDoe”’s priority number will be 10 (the smallest of both
values).
4.4.8 License Management Interface Options
You can access to the Management Interface “Options” screen by choosing “Tools” menu
→ “Options”. The “Options” screen allows configuring some parameters, mainly related to
security.

Figure 4-32: Management Interface “Options” Screen
“Language” Part
This allows you to choose the interface language.
“Authentication” Part
When the “Activate unauthorized access attempt count” box is disabled, users are not
limited in the number of failed authentication attempts. An authentication attempt fails,
for example, if the wrong password is used (authentication by Username & Password).
When the box is activated, the others controls in the “Authentication” part are activated:
you then have to specify the maximal number of failed attempts admissible.
When the maximum number is reached, the user account is put in a “Quarantine” state for
the duration specified in the appropriate field, or until manual reactivation by the
administrator if the corresponding box is checked.
“User Accounts” Part
You can specify in the “Default User Account Status” box, the default activation state of a
4-36
new user.
In the “Enable Anonymous Account”, you can choose whether the “Anonymous” user can
be used.
 You can also forbid the use of “Anonymous” by deactivating the user from the “User
Accounts List” screen (see section 4.4.7.1 Users List).
The “Activate Password Expiration” box indicates whether users defined with the
Username & Password authentication mode must renew their password or not. You have
to specify the password duration time in the appropriate field.
If you check “Activate Password Security Level Verification” checkbox, the passwords
entered in “User Account Details” screen (section 4.4.7.2 Creating a User Account) will be
accepted only if they satisfy the minimum level of security specified in the appropriate
field.

5 Application Rights Management
This chapter describes how to install a remote Project Server, necessary to work under the
multi-user mode. Details regarding this mode of operation can be found in the User’s Guide.
You will also learn in this chapter how you can manage the application rights for the users
defined in a project manager.
 This chapter is aimed only at Automation Studio™ Professional users. If you require
this functionality in the Educational version, please contact the support team. See
chapter 7 Technical Support.

 Operating System Professional Edition (32-bit or 64-bit): Windows 7 SP1, 8, 8.1, 10

or Windows Server 2008R2 SP1, 2012, 2012R2 and 2016.
 Microsoft Office not required, but if present must be 32 bit for 32-bit installation of
Automation Studio™ or 64 bit for 64-bit installation of Automation Studio™.
 CPU: Intel Core 2 Duo 1.83 GHz or equivalent. Recommended: Intel Core 2 Quad.
 3 GB RAM Memory.
 Graphic Card: Video memory 512 MB and up, with a screen resolution of 1024 x 768
minimum.
 Disk space: 500 MB of free space.
5.2 Installing a Project Server

This section describes how you can install a remote Automation Studio™ Project Server.
 A local Automation Studio™ Project Server is automatically installed when

Automation Studio™ is installed on a workstation. To access multi-user
functionalities, an Automation Studio™ Project Server must be installed on a

dedicated machine.
To install Automation Studio™ Project Server, insert the DVD labeled “License Manager
Installer, Project Server Installer” in the target machine’s DVD player. When the DVD
dialogue appears (Figure 4-1: Installation Menu, “Administrator” Section), click the
highlighted button 32-bit or 64-bit (the Version Identifier is selecting automatically the
compatible version for your computer), this will start the installation.
 In case both buttons are highlighted select the 64-bit.
You can also install the Automation Studio™ Project Server from an installation file, which
can be downloaded from our technical support’s portal.
You must select 32-bit or 64-bit.
Follow the instructions to finish the installation. Once the installation is done, you will have
the possibility to configure the Automation Studio™ Project Server: this is required to give
the manager service the required rights.
Figure 5-1: Automation Studio™ Project Server Configuration
 You can change the Automation Studio™ Project Server configuration at any time by
launching the application Automation Studio™ Server Configuration: this
5-2
Application Rights Management
application is in the folder “Automation Studio 6.3”, in the Start menu.
5.3 Using the Automation Studio™ Project Server

This section describes how, as an administrator, you can use the Project Server Manager
to define user accounts, and assign application rights to these users.
Each Project Server (local or remote) is independent. For each Project Server, you must
define the list of users and assign their application rights. These operations are performed
from the application rights management Interface that can be found on the same machine
as the Project Server itself.
5.3.1 Starting the Application Rights Management Interface
You can start the Application Rights Management Interface by launching the application
Project Server’s Access Right Management that can be found in the folder “Automation
Studio”, in the Start menu (on the machine where the Automation Studio™ Project Server
has been installed). An “Authentication” dialogue should appear where you must enter the
administrator’s username and password.
 The communication is done using the ports 8096, 8097 and 8098.
Figure 5-2: “Authentication” dialogue for the Application Rights Management Interface
 The interface will only open with a valid administrator account. An administrator
“Administrator” is initially created for you, with the password admin.
The “Authentication” dialogue also has a button “Forgot your password?”. When clicking
on that button you can ask the Automation Studio™ Project Server to generate a new
password for the administrator whose name and email will be entered in the dialogue
“New Password” (Figure 5-3: “Forgotten Password” ). The new password will be sent to

the email address, if it corresponds to the address in the server.
Figure 5-3: “Forgotten Password” dialogue for the Application Rights Management
Interface
Once the administrator has been successfully authenticated, the interface should appear.
This interface is very similar to the license management interface (section 4.4 Using the
License Management Interface).
The window includes a sidebar on the left side where you can select the part to display in
the main window. The information there will evolve according to the current action.
Figure 5-4: Application User accounts
Application profiles and User accounts can be configured in the application rights
management interface.
5.3.2 Application Profiles
Each application profiles may contain many user accounts and allow you to assign
application rights to these users.
Application rights allow or deny access to certain features of Automation Studio ™.
When Automation Studio™ is launched, the application connects to a Automation Studio™
5-4
Project Server. The user has then access to the rights granted by that server.
 An Automation Studio™ Project Server initially contains a single application profile

called “AllUsers”. This is a special profile that contains all the users defined in the
server.
Apart from the profile “AllUsers”, a user may belong to many application profiles.
5.3.2.1 Application Profiles List
To view the list of “Profiles” screen, click on the icon (“Profiles”) in the sidebar.
Figure 5-5: Application profiles list
Controls for the application “Profiles” are identical to those of the “License Profiles” list:
please refer to section 4.4.4.1 License Profiles List.
5.3.2.2 Creating an Application Profile
To create a new profile, go to the Figure 5-5: Application profiles list and click on the
button. You can also choose the command “Create a New Profile” from the contextual
menu that appears when you right-click in the main part of the screen.
When you create a new profile, the “Application Profile Details” screen appears. This screen
has two tabs: “Profile” and “Application permissions”.

“Profile” Tab
Figure 5-6: Application profiles, “Profile” Tab
“General” Part
The information you provide here also appears in the Figure 5-5: Application profiles list.
The “Is the default profile” box indicates whether the profile is set as the default one or
not.
 To set a profile as the default one is an operation that can be done also in the
contextual menu that appears when you right-click in the main part of the Figure
5-5: Application profiles list.
“Members” Part
In this part, you can choose the users that will be included in the profile.
“Available”.
versa.
vice versa.
5-6
“Application Permissions” Tab
In this tab, you can define the application rights for the profile. The values for these rights
are used to determine the final rights for the users pertaining to the profile.
Figure 5-7: “Profiles” Screen, “Application Permissions” Tab
The application rights for a given user are deduced in the manner described in
section 4.4.7.4 Deduction of Permissions.
Application Right Description

Automation Studio Options When disabled, the user cannot change the locations of
Modification: Enterprise the data used by Automation Studio™.
Data Locations
Standards, Types and

Naming Rules Transfer into When disabled, the user cannot transfer standards, types
the Enterprise’s Options and naming rules from a project.
5.3.2.3 Modify an Application Profile
To modify an existing profile, you must double-click on the line of the profile in the Figure
5-5: Application profiles list. This action opens the Figure 5-6: Application profiles, “Profile”
Tab, where the profile can be modified.
when you right-click on the profile in the main part of the “Application Profiles List”
screen.
 You cannot modify the name of “AllUsers” profile. Also, the “Members” part is
disabled (every user is always a member of that profile).

Any modification to the Figure 5-6: Application profiles, “Profile” Tab screen is saved only
when you click on the “Apply” button in the bottom right corner of the screen.
If you did not click on the “Apply” button, you can cancel the modifications clicking on the
“Reset” button, or leaving the screen.
5.3.3 User Accounts
The Figure 5-4: Application User account allows you to define the users that will be
recognized by the Automation Studio™ Project Server.
Every user is member of the profile “AllUsers”, and can be a member of many profiles. The
user’s permissions are determined by the profiles the user belongs to.
 If your user account does not exists on the Automation Studio™ Project Server you
are connected to, the server will return a “User account does not exist“ message
and you will be pointed back to the Figure 3-27: “Profile Properties” Dialogue Box –
Normal.
5.3.3.1 Users List
You can access the user’s list screen by clicking on the icon (“User Accounts”) in the
sidebar.
Figure 5-8: “Users accounts” Screen
The user accounts that exist on the project server are shown in a tabular format in the main
part of the screen.
Controls for this screen are identical to those used in the license management interface:
please refer to section 4.4.7.1 Users List.
5-8
 The Automation Studio™ License Manager initially contains two user accounts:
“Administrator” and “Anonymous”.
5.3.3.2 Creating a User Account
To create a new user account, go to the Figure 5-8: “Users accounts” Screen and click on
the button. You can also choose the command “Create a New User Account” from the
contextual menu that appears when you right-click in the main part of the screen.
When you create a new user account, the “User Account” screen appears:
Figure 5-9: “User Account” Screen
This screen has five parts. For their descriptions, please refer to section 4.4.7.2 Creating a
User Account.
5.3.3.3 Modifying a User Account
in the “User Accounts List” screen. This action opens the “User Account” screen (Figure 5-9:
“User Account” Screen), where the user can be modified.

when you right-click on the user in the “User Accounts” screen.
 You cannot modify the “Anonymous” user. Double-clicking on this user in the “Users
List” screen has no effect.
Any modification to the “User Account Details” screen is saved only when you click on the
“Apply” button in the bottom right corner of the screen.
If you did not click on the “Apply” button, you can cancel the modifications clicking on the
“Reset” button, or leaving the screen.
5.3.4 Application Rights Management Interface Options
For this screen, refer to section 4.4.8 License Management Interface Options.
5-10
6 Project Rights Management
The project administrator defines project and documents rights inside every project file. By
default, the project administrator is the user that initially created the project. For any given
user, the project and documents rights are combined with the application rights to allow
or deny access to some Automation Studio™ functions.
When you create a new project, it can initially be opened by anybody. If you are concerned
with your project security or confidentiality, you should learn to work with project and
documents rights, as explained in this chapter.
The interface from which you can manage these rights is very similar to both the License
Management Interface (section 4.4 Using the License Management Interface), and the
application rights management interface (section 5.3 Using the Automation Studio™
Project Server). However, you launch the project and documents rights management
interface from within Automation Studio™, using one of the following methods:
● Choose the command “Project” → “Project Permissions” in the Automation
Studio™ menu;
● Choose the command “Permissions” in the group “Administration”, under the
“Tools” tab;
Figure 6-1: “Project Permissions” Command

● Choose the command “Project and Documents Permissions” in the contextual
menu that appears when you right-click on a project in the project explorer.
Whichever method you choose, it would bring the project and document rights
management interface for the current project.
 If the current user is not an administrator for the project, you will not be able to

open the interface.
The elements that can be configured in the interface are the following:
● Project profiles;
● User accounts;
● Object permissions.
6.1 Project Profiles

Each project profiles may contain many user accounts. The project and documents rights
are defined in these profiles.
 A project initially contains a single project profile called “AllUsers”. This is a special
profile that contains all the users defined in the project.
Apart from the profile “AllUsers”, a user may belong to many project profiles.
6.1.1 Project Profiles List
You can access the list of “Project Profiles” screen clicking on the icon (“Profiles”) in
the sidebar.
Figure 6-2: Project “Profiles” Screen
Controls for the project “Profiles” are identical to those of the license, Figure 4-20: License
“Profiles" : please refer to section 4.4.4.1 License Profiles List.
6.1.2 Creating a Project Profile
To create a new profile, go to the “Profiles” screen and click on the button. You can
also choose the command “Create a New Profile” from the contextual menu that appears
when you right-click in the main part of the screen.
6-2
Project Rights Management
When you create a new profile, the Figure 6-3: “Profiles” Screen, “Profile” Tab screen
appears. This screen has three tabs:
“Profile” Tab
This tab is identical to that described in section 5.3.2.2 Creating an Application Profile:
Figure 6-3: “Profiles” Screen, “Profile” Tab
“General” Part
The information you provide here also appears in the Figure 6-2: Project “Profiles” Screen.
The “Is the default profile” box indicates whether the profile is set as the default one.
 Setting the profile as the default profile is done via the contextual menu that
appears when you right-click in the main part of the “Project Profile List” screen.
“Members” Part
In this part, you can choose the users that belong to the profile.
“Available”.
versa.

vice versa.
“Application Permissions” Tab
In this tab, you can assign values to the project rights for the profile. These values are used
to decide the rights of the users that belong to the profile, for the current project.
Figure 6-4: “Profiles” Screen, “Object Permissions” Tab
For a particular user, the project rights are deduced in the manner described in
section 4.4.7.4 Deduction of Permissions.
Project right Description
Simulation When disabled, user cannot simulate the project.
Plotters Access When disabled, user cannot access plotters.
6-4
Project right Description

Dynamic Measuring When disabled, user cannot use measuring instruments
Instruments Access features.
Modification of Standards, When disabled, user cannot create, modify or remove
Types and Naming Rules standards, types and naming rules.
Selection of Standards, When disabled, user cannot create, modify or remove
Types and Naming Rules standards, types and naming rules.
for Project and Documents
Manual Modification of When disabled, user cannot choose which standard to
Technology Components’ use with a project.
Appearance
Insertion and Paste of When disabled, users cannot insert a new technology
Technology Components component.
on Documents
Technology Components’ When disabled, user cannot access components’
Properties Access properties.
Technology Components When disabled, user cannot remove components.
Removal
Layers’ Management When disabled, user cannot modify layers.
Access
Variable Manager Access When disabled, user cannot access the variable manager.
Project’s Structure When disabled, user cannot modify the project’s structure.
Modification
“Object Permissions” Tab
In this tab, you can choose the object permissions groups (section 6.3 Object Permissions)
that belong to the profile. Also, these groups are used to determine the user’s rights on
the different documents within the project.
As the project’s administrator, you can assign each of the project’s documents to a group
of object permissions: a document must belong to at least one group. Each object
permissions group is in turn member of at least one project profile (Figure 6-5: Object
Permissions Groups).

An object permissions group contains the list of project rights. You can assign those rights
the values you choose (including the value “Undefined”). The project rights for a given
document and a given user are determined in the following manner:
● We identify the groups of object permissions the document belongs to;
● We find the project profiles the user belongs to;
● From the object permissions groups identified, we discard those that are not
member of any of the profiles above (the groups that are kept are marked in Figure
6-5: Object Permissions Groups);
● Finally, the remaining object permissions groups are used to determine the
document rights, using the approach described in section 4.4.7.4 Deduction of
Permissions.
User
Account
Document
Project
Permission
Groups Project
Profiles
Figure 6-5: Object Permissions Groups
In the “Object Permissions” tab, you choose which groups belong to the current project
profile in the “Object Profiles” part. The groups that belong to the profile are under
“Selected”. All other groups appear under “Available”.
6-6
Figure 6-6: “Profile”, “Object Permissions” Tab
Use the “>” and “<” arrows to move a selected group from “Available” to “Selected”, or
vice versa.
Use the “>>” and “<<” double arrows to move all groups under “Available” to “Selected”,
or vice versa.
6.1.3 Modifying a Project Profile
To modify an existing profile, you must double-click on the line of the profile in the Figure
6-2: Project “Profiles” Screen. This action opens the Figure 6-3: “Profiles” Screen, “Profile”
Tab screen, where the profile can be modified.
when you right-click on the profile in the main part of the “Project Profiles List”
screen.
 You cannot modify the name of the “AllUsers” profile. In addition, the “Members”
part is disabled (every user is always a member of that profile).
Any modification to the “Project Profile Details” screen is saved only when you click on the
6.2 User Accounts

The “User accounts” screen allows you to define the users that will be recognized by the
project.

Every user is member of the profile “AllUsers”, and can be a member of many profiles. The
user’s permissions are determined by the profiles the user belongs to.
 If your user account exists in the project, the latter will assume you are the
“Anonymous” user.
6.2.1 Users List
You can access the “Users List” screen by clicking on the icon (“User Accounts”) in
the sidebar.
Figure 6-7: “Users accounts” Screen
The user accounts that exist in the project are shown in a tabular format in the main part
of the screen.
Controls for this screen are identical to those of the License Management Interface: please
refer to section 4.4.7.1 Users List.
 A project initially contains the user “Anonymous”, and the administrator (if
different).
Compared to the version presented in License Management Interface, the current “Users
List” screen has an extra element: the address book is opened by clicking on the icon
in the upper part of the screen.
Clicking on the icon opens a dialogue that contains the list of users, as defined on the
Automation Studio™ Project Server in use (see section 5.3.3 User Accounts). By double-
clicking on a user in the dialogue, you import that user into your project.
 Imported users are initially members of the “AllUsers” profile, as well as the default
6-8
profile.
Figure 6-8 : Address Book
6.2.2 Creating a User Account
To create a new user account, go to the Figure 6-7: “Users accounts” Screen and click on
the button. You can also choose the command “Create a New User Account” from the
contextual menu that appears when you right-click in the main part of the screen.
When you create a new user account, the “User Account Details” screen appears:
Figure 6-9: “User Account” Screen

This screen has five parts. For their descriptions, please refer to section 4.4.7.2 Creating a
User Account.
“Permissions” Part
“Permissions” is the only part different from the Creating a User Account section. In the
“Boolean” you can find a sum of all the “Applications permissions” from all the profiles this
user is member.
6.2.3 Modifying a User Account
in the “User Accounts List” screen. This action opens the “User Account Details” screen
(Figure 6-9: “User Account” Screen), where the user can be modified.
when you right-click on the user in the “User Accounts List” screen.
 You cannot modify the “Anonymous” user. Double-clicking on this user in the “Users
List” screen has no effect.
Any modification to the “User Account Details” screen is saved only when you click on the
6.3 Object Permissions

The rights for a given project are determined through the object permissions.
6.3.1 Object Permissions List
You can access the “Object Permissions List” screen by clicking on the icon (“Object
Permissions”) in the sidebar.
6-10
Figure 6-10: “Object Permissions” Screen
The groups of object permissions that exist in the project are shown in a tabular format in
the main part of the screen
 A project initially defines a single group of object permissions, called “New

Document”, and that grants the maximal rights to its documents.
 To filter the displayed groups, type a string in the field above the table and click the
“Search” button. The table will only display the groups that contain the string you
are looking for.
The buttons and allow you respectively to create a new group and delete the
selected one. These actions are also offered in the contextual menu that appears when
you right-click in the main part of the screen.
6.3.2 Creating a Group of Object Permissions
To create a new group of object permissions, go to the Figure 6-10: “Object Permissions”
Screen and click on the button. You can also choose the command “Create a New Object
Permission” from the contextual menu that appears when you right-click in the main part
of the screen.
When you create a new group, the screen “Object Permissions” appears. This screen has
three parts:

Figure 6-11: “Object Permissions” Screen
“General” Part
The information you provide here also appears in the “Object Permissions List” screen.
You must choose a name for the object permissions group “Name” field. If you wish, you
can also enter a short description for the group in the appropriate field.
“Members” Part
In this part, you can choose which documents are member of the object permissions group.
The documents that are members of the group appear under “Selected”. All other
documents are under “Available”.
Use the “>” and “<” arrows to move a selected document from “Available” to “Selected”,
or vice versa.
Use the “>>” and “<<” double arrows to move all documents under “Available” to
“Permissions” Part
In this part, you can assign values to the project rights, for the current object permissions
6-12
group:
Category Command Description

Document ● Read-Write- Modify these rights to choose what
Access Right Simulation fundamental operations are allowed on the
document.
● Read-Simulation
● Read
● Simulation
● None
6.3.3 Modifying a Group of Object Permissions
To modify an existing group of object permissions, you must double-click on the line of the
group in the “Object Permissions List” screen. This action opens the “Object Permissions
Details” screen (Figure 6-11: “Object Permissions” Screen), where the group can be
modified.
Any modification to the “Object Permissions Details” screen is saved only when you click
on the “Apply” button in the bottom right corner of the screen. If you did not click on the
“Apply” button, you can cancel the modifications by clicking on the “Reset” button, or by
leaving the screen.

7 Technical Support
7.1 Direct Contact
You can contact our technical support team by email to support@famictech.com or by
phone to 1-514-7488050.
You can also contact our technical support from the Automation Studio ™ menu “Support”
→ “About”.
Figure 7-1 Send System Information Command from the "About" Window
The command opens the default e-mail application with an email automatically
addressed to the technical support and containing the system information. This allows
quick communication of important data to our support team.
7.2 Contact via Technical Support Portal

We recommend that you register on our Technical Support Portal after you have installed
Automation Studio™:
https://support.famictech.com/PORTAL/portal/index.jsp
You will receive a username and password by email, which will allow you to:

● Download Automation Studio™, the Network Automation Studio™ License Manager

and License Management Interface. This is particularly important if you lose your
DVD;
● Download the latest Service Release. Note that the last Service Release includes
all the previous one;
● Download the user’s guides in PDF format;
● Download the manufacturer catalogues.
● Contact our Technical Support with any issue you might have. You can also follow
the progress of the issues that you have submitted;
● Activation codes;
● And more …
When you register on the portal, make sure you identify any person who uses Automation
Studio™ within your organization, so they also can benefit from our support.
Figure 7-2: Automation Studio Technical Support Portal
Once you have registered, you can ask to receive an email notification whenever a new
Service Release becomes available for your version of Automation Studio ™. It is
recommended that you always keep your version up to date.
If you have an annual maintenance plan, updates are free for the duration of your plan.
If you are using an older version of Automation Studio ™, we recommend that you get the
latest version in order to take full advantage of the latest functions. To learn more about
7-2
Technical Support
the latest version, please visit our website and ask for a free online presentation with one
of our specialists.
7.3 Installing a Service Release or a New Version

You can download at any time the Service Releases for your version of Automation Studio ™.
To do this, just follow the steps below:
First, make sure you have:

● Your username and password;
● Your licenses’ activation codes (contact by e-mail production@famictech.com to
obtain these codes).
1. Make sure no protection key is connected to your workstation;
2. Go to our technical support page;
3. To finish these steps, you will need to connect to the Technical Support Portal with
Internet Explorer:
https://support.famictech.com/PORTAL/portal/index.jsp
4. Enter your username and password, and click the “Login” button;
5. Select the “Product Downloads” tab;
6. Adjust the filters so the interface only presents you with the items compatible with
your version of Automation Studio™;
7. From the list, click on the product code in the “Code” column for the desired item;
Figure 7-3: “Product Downloads” Tab

A page containing the item’s description opens.
8. Click on the “Download” button;
 The “Download” button may be inactive. This is related to the fact that the “Software

Maintenance & Support Program” has expired. Please contact your sales
representative to renew your plan.
9. Save the file on your local disk;
10. Unzip the file and launch the setup.exe file to start the installation;
11. Once the installation is done, connect your protection key into your workstation in
order to update it.
 If you want the package containing the software, the documentation and the
Automation Studio™ License Manager, please contact your sales representative who
will help you with the formalities.
7.4 Documentation Download

To download the documentation, first follow the procedure of section 7.3 Installing a
Service Release or a New Version until the fourth step:
1. Select the “Product Documentation” tab;
2. Adjust the filters so the interface only presents you with the items compatible with
your version of Automation Studio™;
3. From the list, click on the product code in the “Code” column for the desired item;
A page containing the item description opens.
4. Download “DASZZENFTP60U06.zip” for the English documentation;
5. Save the file on your local disk;
6. Unzip the file in order to access the guides.
7-4
A Glossary
Access Points
An Access Point is associated with one or more License Profile(s) inside a Network
Automation Studio™ License Manager, and with one or more Application Profile(s) inside a
Automation Studio™ Project Server. It defines from which machines the profile members can
access the server, in terms of allowed IP addresses.
Access Schedule
An Access Schedule is associated with one or more Profile(s) inside a Network Automation
Studio™ License Manager, and with one or more Application Profile(s) inside an Automation
Studio™ Project Server. It defines when the profile members can access the server.
Application Profile
Application Profiles are defined inside an Automation Studio™ Project Server, and are used
to group user accounts, access schedules and access points, as well as to grant Application
Rights.
Application Rights
Application Rights are associated with a User Account, in a Project Server. These rights control
access to Automation Studio™ functionalities, for that user.
Application Rights Management Interface
The application rights management interface allows managing the Automation Studio™
Project Server.
Authentication Mode
An authentication Mode describes the method that allows a user to be recognized by a

Network Automation Studio™ License Manager, or by a Automation Studio™ Project Server.
Connection Profile
Connection Profiles are used to group the information concerning the type of license to be
© Famic Technologies Inc. A-1

used, as well as how to access the Network Automation Studio™ License Manager (if
applicable). The profile also specifies what Automation Studio™ Project Server to connect to.
Firewall
A firewall is a part of a computer system or network that is designed to block unauthorized

access while permitting authorized communications.
IP Address
An IP Address is a numerical label assigned to each device (e.g., computer, printer)

participating in a computer network that uses the Internet Protocol for communication.
LAN
Local Area Network.
License Profile
License Profiles are defined inside a Network Automation Studio™ License Manager, and are
used to group user accounts, access schedules and access points, as well as to grant rights
on the network licenses.
Local License
A Local License is an Automation Studio™ license that can only be used by a single user. The
protection key that contains the license must then be plugged into the workstation that runs
Automation Studio™.
Network License
A Network License is an Automation Studio™ license that can be used by multiple users on
many workstations. The protection key that contains the license must be plugged into the
Automation Studio™ License Manager.
Network License Management Interface
The Network License Management Interface is the tool used to manage the network licenses
remotely. The interface communicates with the Automation Studio™ License Manager.
A-2
Glossary
The Automation Studio™ License Manager is the central element for all operations related to
network licenses. The Automation Studio™ License Manager contains the Manager and
Interface Services.
Organization ID
The Organization ID is a character string unique to each organization. The ID is used to identify
the organization on a Network License Manager that is shared by multiple organizations.
Project Profile
Project Profiles are defined inside a project file and are used to group user accounts and their
Project Rights.
Project and Documents Rights
Project and Documents Rights are associated with a user account in a project file. These rights
control access to Automation Studio™ functionalities by a user, for a project or its documents.
Automation Studio™ Project Server
The Automation Studio™ Project Server main task is to maintain a table that identifies which
projects are currently open, and by whom. The local Project Server installed with Automation
Studio™ only allows single-user operations. A remote Project Server is used for multi-user
functionalities.
Protection Key
The Protection key is a key that is plugged into the USB port of a workstation or the License
Manager and it contains one or more Automation Studio™ Licenses.
SID
A SID (Security Identifier) is used by Windows to identify a subject implied in a transaction.

A SID uniquely identifies each system, user or object on a machine or a network.
Update Codes
Update Codes are generated by Famic Technologies Inc., and are required to update the
© Famic Technologies Inc. A-3

license(s) on protection key.
URI
A URI (Uniform Resource Identifier) is a string of characters used to identify a name or a

resource on the Internet.
User Account
User accounts are defined inside a Automation Studio™ License Manager, and are used to
determine the permissions of a user. A user account is member of one or more License
Profiles.
User accounts are defined inside a Automation Studio™ Project Server and are used to
determine the Application Rights of a user. A user account is member of one or more
Application Profiles.
WAN
Wide Area Network.
A-4
B Index
Startup ............................................. 3-1

Access Point ............................ 4-21, 4-22
Access Schedule ...................... 4-21, 4-25
User Account
Administrator ............. 2-4, 2-7, 4-4, 4-30 Anonymous ............................... 4-29
Application Connection Profile ............................. 3-18
Mise à jour des normes .................. 3-1 Anonymous.................................... 3-20
Application Profile ............................... 5-5 Introduction ......................................... 1-3
AllUsers ............................................ 5-8
License .................................. 1-3, 2-1, 3-5
AllUsers ............................................ 5-5
Local ......................................... 1-3, 2-1
By Default ........................................ 5-6
Update ....................................... 3-13
Application Rights Management Interface Network ........................................... 4-7
............................................................. 5-3
Network .................... 1-3, 2-1, 3-7, 4-1
Options ........................................... 5-11
Capacity ............................. 2-1, 3-10
Authentication Mode ...................2-8, 3-8 Revocation ................................... 3-9
Anonymous ........................... 2-8, 4-31 WAN/LAN Support ....................... 2-3
Computer ID ........................... 2-8, 4-32 Network
Hybrid ............................................ 4-32 Capacity ....................................... 4-9
Username & Password ... 2-8, 3-8, 4-31 Network
Windows Domain User .......... 2-8, 4-31 WAN/LAN Support ..................... 4-10
Network
Automation Studio™
Update ....................................... 4-11
Installation ....................................... 7-3
Installation ....................................... 3-2 License Management Interface .. 2-4, 4-4
Silent ............................................ 3-9 Installation ....................................... 4-4
Required Configuration ................... 3-1 Options ........................................... 4-35
© Famic Technologies Inc. B-1

License Manager AllUsers .......................................... 4-22

Manager Service .............................. 3-8 AllUsers .......................................... 4-28
By Default ............................ 4-18, 4-20
License Manager ......................... 2-2, 3-7
Interface Service .............................. 2-3 Machine Identifier Generator ........... 4-32
Manager Service .............................. 2-3
Object Permissions .................... 6-6, 6-11
User Account
New Document .............................. 6-12
Anonymous ................................. 2-4
Operation Mode
License Manager
Multi-Users .............. 1-3, 2-5, 3-16, 5-1
User Account
Single-User ..................... 1-3, 2-5, 3-16
Priority ....................................... 3-10
Organization ID ............................ 2-4, 3-8
License Manager
Installation ....................................... 4-1 Project
Save ................................................ 6-14
License Manager
User Account Project and Document Rights1-4, 2-7, 6-1
Administrator ............................... 4-5 User Account .................................... 6-8
Anonymous.................................. 6-8
License Manager
Manager Service .............................. 4-8 Project Profile ...................................... 6-2
AllUsers .............................6-2, 6-7, 6-8
License Manager
By Default ........................................ 6-3
User Account .................................. 4-28
Project Server ............. 2-4, 2-6, 3-14, 5-3
License Manager
Application Rights .................... 2-7, 5-1
User Account
Installation ....................................... 5-2
Administrator ............................. 4-29
User Account .................................... 5-8
License Manager Administrator ............................... 5-4
User Account User Account .................................... 2-6
Anonymous ............................... 4-37 Anonymous........................ 2-6, 3-20
User Account
License Profile ................................... 4-16
Anonymous.................................. 5-9
Activation Status ............................ 4-18
User Account
AllUsers .......................................... 4-17
Administrator ............................... 5-9
AllUsers .......................................... 4-19
B-2
Index
Protection Key ...................... 1-3, 2-2, 7-3 Update Code ............................ 3-13, 4-11
Reports ...................................... 2-4, 4-12 User Account

Activation Status ........................... 4-29
Technical Support ................................ 7-1
© Famic Technologies Inc. A-7-3

Automation Studio Installation and Administration Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Automation Studio Installation and Administration Guide

Uploaded by

Copyright:

Available Formats

Installation and Administration

Automation Studio™ Installation and Administration User’s Guide

Reproduction or re-transmission of this manual or software, in whole or in part, by any means

Windows is a registered trademark of Microsoft Corporation.

© Famic Technologies Inc. 1-1

4.4.5 Access Points .........................................................................................4-22

© Famic Technologies inc. 1-3

If your organization is mainly interested in the multi-user features of Automation Studio™,

Project and Documents Rights

© Famic Technologies inc. 1-5

© Famic Technologies Inc. 2-1

Figure 2-1: Network Licenses

2.1.1 Automation Studio™ License Manager

The Automation Studio™ License Manager is installed on a dedicated machine. The

Figure 2-2: License Manager’s Services

© Famic Technologies inc. 2-3

Defining user accounts is part of the administrative tasks described below.

2.1.2 License Management Interface

Managing licenses includes the following tasks:

2.2 Operation Mode

When you install Automation Studio™ on a workstation, an Automation Studio™ project

Figure 2-3: Single-User Mode

© Famic Technologies inc. 2-5

Figure 2-4: Multi-user Mode

2.2.1 Automation Studio™ Project Server

 Every project server has its own list of user accounts.

local project server, using the predefined user “Anonymous”.

Every project server is subject to the following constraint:

 A server can open a maximum of 20 projects simultaneously.

In addition, the following constraints apply for the multi-user mode:

2.2.2 Application Rights

2.2.3 Project and Documents Rights

 Every project file has its own list of user accounts.

© Famic Technologies inc. 2-7

2.3 Authentication Modes

3.1 Minimum Required Configuration

 Operating System Professional Edition (32-bit or 64-bit): Windows 7 SP1, 8, 8.1, 10 or

 Automation Studio™ takes advantage of multi-core processors.

 Disk space: 2.5 GB of free space (without considering the catalogues).

 USB port required, to support the protection key

© Famic Technologies Inc. 3-1

3.2 Installing Automation Studio™

 To install the application, the user must have administrative rights.

3.2.1 Installation from the DVD

3.2.1.1 DVD Dialogue Window

Figure 3-1: DVD Dialog

Here is the description of the elements in the dialogue:

User Install Automation Studio™ *You must select 32-bit or 64-bit,

? When hovering it with the mouse, information about

Administrator ● Install the Project Server

Guides Access to the different Automation Studio™ modules User’s

Tutorials Access to Automation Studio ™ Tutorials: information such as

Support Installation requirements, FAQ, Contact Your Technical Support

3.2.1.2 Installation Prerequisites

 Do not install Automation Studio™ while you update Windows.

© Famic Technologies inc. 3-3

Figure 3-2: Automation Studio™ version selection

3.2.1.3 Install Automation Studio™

Figure 3-3: Automation Studio™ Installation

Figure 3-4: License Agreement

© Famic Technologies inc. 3-5

Figure 3-5: Customer Identification

Figure 3-6: Destination Folder

Figure 3-7: Installation Process