Skip to main content

Overview

Equipment Management is a critical component of the service order system, enabling precise tracking of equipment through part numbers, serial numbers, equipment types, and delivery conditions. This ensures accurate service history and warranty management.

Equipment Data Structure

Equipment information is embedded within each service order:
types/ServiceOrder.ts
export interface ServiceOrder {
    id: number,
    number: number,
    type: string,
    part_number: string,           // Equipment part identification
    serial_number: string,         // Unique equipment serial
    description: string,           // Equipment condition/issues
    solution: string,              // Service performed
    // ... other fields
    delivery_conditions: DeliveryConditions
}

Equipment Type Interface

Equipment types categorize the kind of equipment being serviced:
types/ServiceOrder.ts
export interface EquipmentType {
    name: string
}

Common Equipment Types

The system tracks various equipment brands and types:

Lenovo

Laptops and desktops

HP

PCs and peripherals

Dell

Business equipment
Example from the system:
composables/useServiceOrders.ts
{
  id: 1,
  equipment_types: { name: "Lenovo" },
  part_number: "ab123",
  serial_number: "6303934"
}

Part Numbers

Part numbers identify the specific model or SKU of equipment:
part_number
string
required
Alphanumeric identifier for the equipment model (e.g., “ab123”, “cd456”, “ef789”)

Part Number Usage

  • Warranty Verification: Confirms equipment is under warranty
  • Parts Ordering: Ensures correct replacement parts are ordered
  • Service Documentation: Creates accurate service records
  • Inventory Management: Tracks which equipment models require service most frequently
composables/useServiceOrders.ts
{
  type: "garantía",
  part_number: "ab123",
  description: "Lorem ipsum dolor sit amet..."
}

Serial Numbers

Serial numbers uniquely identify individual equipment units:
serial_number
string
required
Unique identifier for the specific equipment unit (e.g., “6303934”, “7304945”, “8305956”)

Serial Number Importance

Serial numbers are essential for warranty claims, as manufacturers track warranty coverage by serial number.
Each serial number has a unique service history, helping identify recurring issues with specific units.
Companies track their equipment inventory using serial numbers for asset management.
Serial numbers help identify and recover stolen equipment.

Equipment Information in Order Form

When creating a service order, equipment details are captured:
pages/serviceorders/order.vue
<div class="mb-3 col-2">
    <label for="company" class="font form-label fw-bold">N° parte:</label>
    <div class="input-group" style="height: 7px;">
        <select id="company" class="form-select">
        </select>
    </div>
</div>
<div class="col-4 mb-3">
    <label for="contact" class="font form-label fw-bold">Nombre equipo:</label>
    <div class="input-group" style="height: 7px;">
        <select id="company" class="form-select">
        </select>
    </div>
</div>
<div class="col-2 mb-3">
    <label for="serialNumber" class="font form-label fw-bold">Número de serie:</label>
    <div class="input-group" style="height: 7px;">
        <select id="company" class="form-select">
        </select>
    </div>
</div>
The form uses dropdowns for part numbers and serial numbers to ensure data consistency and allow quick selection of previously serviced equipment.

Equipment Description

The description field captures the equipment’s condition when received:
pages/serviceorders/order.vue
<div class="col-9 mb-3">
    <label for="floatingTextarea" class="font form-label fw-bold">Descripción:</label>
    <textarea class="form-control"
        placeholder="Ingrese aqui la descripción del estado en el que se recibe el equipo"
        rows="5" id="floatingTextarea" v-model="selectedOrder.description"></textarea>
</div>

What to Include in Descriptions

1

Physical Condition

Note any scratches, dents, cracks, or physical damage observed on receipt.
2

Operational Issues

Describe the reported problems (e.g., “pantalla rota” - broken screen, “no enciende” - won’t power on).
3

Included Accessories

List accessories received with the equipment (charger, cables, bag, etc.).
4

Customer Concerns

Document specific concerns or requests from the customer.
Example descriptions from the system:
composables/useServiceOrders.ts
// Example 1: Detailed description
{
  description: "Lorem ipsum dolor sit amet consectetur adipisicing elit. Qui expedita temporibus ipsum, incidunt hic doloremque a voluptas magnam perferendis architecto harum, obcaecati adipisci ea recusandae. Veniam eveniet a quidem sequi?"
}

// Example 2: Specific issue
{
  description: "pantalla rota",
  solution: "cambio de pantalla"
}

// Example 3: Maintenance service
{
  description: "mantenimiento general",
  solution: "limpieza interna"
}

Delivery Conditions

Delivery conditions document recommendations and the state of equipment upon delivery:
types/ServiceOrder.ts
export interface DeliveryConditions {
    description: string
}

Delivery Conditions in Order View

pages/serviceorders/order.vue
<div class="col-9 mb-3">
    <label for="solution" class="font form-label fw-bold">Recomendaciones:</label>
    <textarea class="form-control" rows="5" id="solution"
        v-model="selectedOrder.delivery_conditions.description"></textarea>
</div>

Typical Delivery Condition Notes

con funda protectora
(with protective case)
Examples from the system:
composables/useServiceOrders.ts
{
  delivery_conditions: { description: "descripcion" }
},
{
  delivery_conditions: { description: "con funda protectora" }
},
{
  delivery_conditions: { description: "sin cargador" }
}

Equipment in Detail View

The service order detail view displays all equipment information:
pages/serviceorders/detail.vue
<div class="card-body col-6 shadow shadow-lg m-2 p-3">
    <a href="#" class="text-decoration-none text-dark fw-bold fs-4">
        <img src="../../public/house-solid.svg" alt=""
            style="width: 16px; height: 16px; margin-right: 5px;">
        <span style="color: #666168;">Información del Servicio</span>
    </a>
    <ul>
        <li class="mb-2 mt-4"><strong style="color: #5d5d5d;">Tipo servicio: </strong>{{ order.type }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Nombre del equipo: </strong>{{ order?.equipment_types?.name }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Número de parte: </strong>{{ order.part_number }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Numero de serie: </strong>{{ order.serial_number }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Descripción: </strong>{{ order.description }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Solución: </strong>{{ order.solution }}</li>
        <li class="mb-2"><strong style="color: #5d5d5d;">Condiciones de entrega: </strong>{{ order?.delivery_conditions?.description }}</li>
    </ul>
</div>

Service Types and Equipment

The system supports three main service types:
Equipment under manufacturer warranty. Requires valid part number and serial number verification.
{
  type: "garantía",
  part_number: "ab123",
  serial_number: "6303934"
}

Equipment Tracking Workflow

Best Practices

Verify Serial Numbers

Always verify the serial number physically on the equipment matches what’s entered in the system.

Photograph Equipment

Take photos of equipment condition on receipt for documentation and dispute resolution.

Complete Descriptions

Provide detailed descriptions including all visible issues and customer concerns.

Document Delivery

Clearly note delivery conditions, missing items, and recommendations for customer.

Equipment Data Validation

The system should validate:
  • Serial number uniqueness for warranty tracking
  • Part number format consistency
  • Required fields (serial number, part number) before order creation
  • Equipment type selection from predefined list
Maintaining accurate equipment records enables:
  • Faster warranty claim processing
  • Better inventory management
  • Identification of problematic equipment models
  • Improved customer service through complete history

Build docs developers (and LLMs) love