Preparing for trial operation

---

I think that in the steps up to this point, you have understood the basic operation of TimeTracker NX using the trial version.

As a next step, we recommend that you try it out using actual data.
By using it while assuming actual operation, you can get a concrete image of the operation after moving to actual operation.
By doing so, the issues to realize actual operation will also become clear, and the improvement effect will be easier to feel.

To try it out using actual data, build an evaluation environment and proceed with operation as follows.

• Server environment construction
• Master data registration

For smooth use

Select the edition of TimeTracker NX according to the functions you want to use

TimeTracker NX has the following two editions, which differ in the functions that can be used.

• Standard Edition
  Focus on labor input and labor management, and simple project management is fine (some functions are restricted)
• Professional Edition
  In addition to labor input and labor management, you want to perform full-scale project management (all functions are available)
  

Both are available in the evaluation version, but we recommend using the "Professional Edition" which allows access to all functions.
For details on the editions, please see below.

• Detailed explanation of the editions and the functions they provide: TimeTracker NX editions
• Changing the edition after installation: Can I change the edition later?

Start with a small-scale trial

In most cases, the trial operation is carried out with a maximum of about 10 people.
By including each layer of the role, such as one manager, two leaders, and three people in charge,
the scope of the actual operation can be covered and evaluated.

Background of trial operation with a few to 10 people

The scale is determined by the work content, individual situations, and schedule.
However, if we consider the following objectives, a large scale will hinder a smooth evaluation.

• Share the objectives and policy of the trial within the trial team
  
• Evaluate and reach a conclusion in a short period of time
  

Make the purpose of use clear

In order to proceed smoothly with the trial, it is effective for each member of the trial team to understand and share a common understanding of "what we want to achieve by introducing the tool."
If the objective is clear, you will not lose sight of the essence even if issues arise.
The following are examples of actual purposes for introduction so far.

• Improve development efficiency
• Understand workload status based on man-hours
• Improve accuracy of estimates
• Centralize man-hours management and schedule management
• Reduce management man-hours for administrators
  • Reduce communication costs within the organization

Case study link: "TimeTracker NX Case Study" (https://www.timetracker.jp/casestudies/)

Server environment construction

Once the department and project for trial operation have been decided, build an evaluation environment for the trial.
Since TimeTracker NX is a web application, build a server environment to provide the service.

The environment can be constructed in one of the following patterns.

No	OS to use in server environment	Cost	Recommended users	Link to environment setup procedure
1	Windows Server OS	Cost of Server OS	For those who want to check all the functions	"Setup Guide"
2	Docker	None	For those who want to keep the cost of evaluation down(※)	"Building an evaluation environment with Docker"

※You can start using it immediately by running a few batch script files provided on the Windows OS.

• There is no need to prepare Windows Server OS (paid).
• You can easily build the environment with a dedicated installer.

For those who want to start trialing without initial settings after installation, we also provide a sample database.

Key Points

Check the settings required for communication between the client and server

Here are some common problems when connecting from the client to the server.
If you get an error when connecting to the server, it may be that the following cases apply.

• TimeTracker NX setup screen or login screen is not displayed

Check the contents and set it up so that you can connect.

Build an environment with the scale to be evaluated and an eye on the future

The specifications of the server machine will vary depending on the scale of operation (number of users, number of projects, number of items, etc.), but
It is better to prepare something with a margin in anticipation of the future scale of operation.

• [Reference] TimeTracker NX guaranteed server PC specifications and software version: TimeTracker NX operating environment
• We recommend that the following users prepare the environment (server machine, server OS, database) introduced above at this stage.
  
  • I want to start official operation in the same environment after the trial
  • I will conduct a trial operation with 10 or more people

We do not support the use of client OS as a server in the official version environment or the operation of SQL Server Express in an environment with more than 10 people.

Master data registration

Once the server environment is built, the next step is to register the master data.
This is a task that the administrator (or promoter) should perform before the trial team starts.
Before actually starting project management and labor input, information such as each account, organization, and authority must be registered in advance.

Procedure

The method for registering master data is introduced in the following link.
First Step Guide - Preparation
With this setting, you can start the minimum operation.

Point

Start trial with organization and role settings as minimum

It is difficult to know how to define "organization" and "system role" in the master data.
However, there is no problem in keeping the configuration simple for trial operation.
Specifically, it is as follows.

• Department
• Trial operation is generally performed in one department.
  Therefore, it is possible to operate with only one "organization" data.
  
• Of course, there is no problem in creating multiple data for aggregation by organization, but if you set it to the minimum required, you can smoothly enter the evaluation of functions such as labor input and project management.
  
• System Roles
  
  • System roles are settings that determine which functions can be used (e.g., only inputting man-hours, can edit projects, etc.).
    
  • In actual operation, you will probably set it according to job title and position, but for now, it will be fine to simply create one role with a setting such as "All functions can be used."
    
  • It is also common to create multiple roles such as "Can edit projects" and "Cannot edit projects" as needed.
    

Here, we recommend that you proceed with trial operation with the simplest possible configuration to smoothly evaluate the functions.