Computer for Torgsoft: preparation and pre-purchase checklist

Before buying a computer for Torgsoft, prepare a description of its tasks: where users will work, where the database will be, and what equipment needs to be connected. Give this information to a technical specialist to agree on the configuration, exact software versions, and licenses.

Arrange to test the proposed computer before buying it. Decide in advance which operations to test, the workload, and an acceptable completion time. The preparation should result in a completed checklist, an agreed configuration, and a test report listing the scenarios that were and were not tested.

Define the role of each device

Make a list of devices and write down the purpose of each one. Use separate rows for the server and the seller’s workstation. If one computer will perform several tasks, list them all.

Record how many people will work at the same time during the busiest period. Separately note any new workstations planned. The total number of employees does not replace a description of concurrent work.

How the Torgsoft installation option determines the computer’s role

With the “Only on this computer” option, Torgsoft deploys the server and client environment on one device: the database, SQL Server, and program are installed. In the configuration request, state that this computer will perform both roles.

The “Connect to a remote server” option installs the components needed to run the program and connect to a remote database. Record the specifications of this workstation and the device hosting the database separately. The installation option itself does not determine the required amount of RAM or processor power.

When using Torgsoft-Terminal over the internet, computers connect to the server through a remote desktop. Mark this specific work method in the plan. Describe connecting the program to a remote database and a terminal session separately. Agree on the specific terminal environment and license package with a technical specialist.

Collect information to agree on the configuration

The owner describes the work tasks, and a technical specialist helps record the technical specifications. For existing devices, note their actual parameters. For a new computer, ask the seller for an exact specification.

• Software: Torgsoft version and license, required additional options, Windows edition and build, SQL Server version and edition.
• Resources: processor model, installed RAM, type and capacity of each drive, used and free space.
• Records: number of product items and documents, size of the database, photos, and archives. To estimate growth, record the sizes on two dates and the time between measurements.
• Workload: peak number of concurrent users, their operations, and other programs that will run in parallel.
• Equipment: models of scanners, printers, scales, and other devices, connection method, driver versions.
• Infrastructure: network diagram, noted connection drops, backup power and connectivity, locations where copies are stored.
• Support: person responsible for configuration, data recovery, and reporting faults.

Ask the technical specialist to approve in writing the exact combination of Torgsoft, Windows, and SQL Server, equipment compatibility, and the proposed configuration for each role. Separately ask them to check component support periods and required licenses. Keep the approval with the computer specification.

Assess archive storage separately from working data

Decide how many archives you plan to keep and measure the size of one archive. For a preliminary estimate, multiply the number of copies by that size. If their sizes differ significantly, add up their volumes separately.

Illustrative example. Suppose a store plans to keep 14 archives, each 2 GB. Their total size will be 14 × 2 = 28 GB. This estimate applies only to these copies.

Account for the working database, photos, programs, temporary files, measured growth, and agreed reserve in separate rows. Repeat the estimate for each storage location. Do not use archive volume to determine the required processor or RAM.

Test the configuration with agreed scenarios

Before testing, agree with the technical specialist on representative data: its volume and composition should match the planned work. Define the required operations, equipment, concurrency, and acceptable time for each operation. Check separately whether the selected test license supports the required features and concurrent work.

1. Prepare a separate test database on the proposed configuration.
2. Run the agreed scenarios with the expected number of concurrent users and any other required programs.
3. Check the specific equipment models and the results of record-keeping operations.
4. Record completion times, errors, resource usage, and whether the results meet expectations.
5. Mark unavailable scenarios as untested and agree on how to test them.

For each scenario, keep a record of the conditions, expected result, actual result, and technical specialist’s conclusion. If the configuration or conditions change, repeat the relevant scenarios. Do not count a demonstration on another computer as a test of the device you plan to buy.

Torgsoft archiving and recovery check

For the backup plan, determine when copies will be created and where they will be stored. Torgsoft archiving task automatically archives the database at a set time or when exiting the program. Align this schedule with the store’s working hours.

The additional “Cloud data archive” feature creates and sends an archive of the database or program directory to Google Drive. Specify in the plan which data to archive, who will check that copies are present, and how much storage space is allocated for them.

The “Load database” feature lets you load a previously saved database into Torgsoft. Together with the technical specialist, test restoring a copy in a separate environment, compare the agreed data, and record the result. Include a repeat recovery check in the maintenance plan. The presence of an archive file alone is not the result of such a test.