Buy FECForge

Set up and use the Repair Log

Create the equipment registry, record asset or category-only problems, assign technicians, and import older spreadsheets.

For
Technicians, managers, and staff
Length
11 minute quick start
Mid-tier module

Use an asset when the problem belongs to a specific game, kart, blaster, or device. Use a category-only ticket for facility or technology problems that do not have a sensible asset record.

Repair Log interface with fictional demo data
Actual FECForge interface · fictional demo data shown
1

Before you begin

These instructions describe FECForge 1.32.35. If a control is missing, check your role and installed version before continuing.

  1. Prepare your account and source information

    Open Repair Log from the launcher. Managers maintain categories, assets, and technicians. Staff and technicians use the actions their account permits. Have a clear asset name and problem description ready.

2

Build the repair registry

  1. Open Settings → Assets & categories

    As a manager, create stable groups such as Arcade Games, Go Karts, Facility, or Network. Expect them in the repair category choices.

  2. Add the individual assets

    Create records such as Kart 1, Red Blaster 4, or a named cabinet. Assign each to the correct category so its repairs can be found in Asset history.

  3. Open Settings → Technician roster

    Managers maintain the technician list. A technician can select their name in Repaired by when completing work without needing assignment authority.

3

Open and complete repairs

  1. Describe the problem

    Choose a category, select an asset when one applies, set priority and service state, then record enough detail for the next person to act.

  2. Track the work

    Use status, technician, date, asset, and text filters to keep the active queue focused. Resolved tickets are hidden by default unless a filter or asset history asks for them.

  3. Record the resolution

    Add repair details, parts cost, downtime, and the person who repaired it before resolving the ticket.

4

Import historical logs

  1. Choose the workbook and map columns

    Map the columns used for dates, descriptions, status, cost, and other available fields.

  2. Map worksheets to assets

    For workbooks with one sheet per kart or blaster, assign each worksheet to the matching asset before import.

  3. Review the preview

    Confirm a sample of rows and asset assignments, then import. Start the next workbook as a separate import session.

5

Check the result and keep your data safe

  1. Reopen the repair ticket.

    Check its asset/category, service state, priority, and work history. After resolving it, use the resolved filter or asset history to find it again.

  2. If the result is not what you expected

    If an import targets the wrong asset, cancel its preview. Keep the original workbook and review a small sample first. Do not erase the repair history to make the active queue shorter.

Keep going

All users Common problems A first-response checklist for a blank screen, failed sign-in, missing module, stalled import, update, or printer. Installation owners Users and permissions Choose the right role, limit module access, reset a password, and decide which accounts may remain signed in. Inventory managers and counters Inventory Create departments and units, arrange a walking order, choose a count view, and limit each user to relevant areas.