---
title: "Bay"
space: "ServiceMS"
url: "https://support.aakvatech.com/ServiceMS/new-wiki-page"
updated: "2026-07-22"
---



---

## **1. Overview**
The **Bay** DocType is part of the *Service Management* module and is used to represent a specific physical or functional service bay in a workshop. Each bay is linked to a service workshop, allowing for better organization, scheduling, and resource tracking of vehicle servicing and repair operations.

---

## **2. Key Features**
- Unique identification of each service bay.
- Association with a specific **Service Workshop**.
- Easy filtering, searching, and list view visibility.
- Quick Entry support for faster data input.
- Change tracking enabled for audit purposes.

---

## **3. Pre-Requisites**
Before creating a Bay entry, ensure the following are available:
- A **Service Workshop** DocType already set up.
- User role with at least `System Manager` privileges (or custom roles with appropriate permissions).

---

## **4. Step-by-Step Usage**

### **To Create a Bay:**
1. Navigate to **Service Management > Bay**.
2. Click **New**.
3. Fill in the following fields:
   - **Bay**: Unique name/ID for the bay (e.g., BAY-01).
   - **Service Workshop**: Select the associated workshop.
4. Click **Save**.

### **Viewing Bays:**
- Go to the **Bay List View** to see all created bays, with filtering options available by bay name or service workshop.

### **Editing or Deleting:**
- Open the desired Bay record.
- Use **Edit** to update information.
- Use **Delete** if the bay is no longer in use (make sure it's not linked to active tasks).

---

## **5. Script Customizations**

You can add server-side or client-side customizations as needed.

### **Client-Side Example (Custom Script):**
```js
frappe.ui.form.on('Bay', {
  refresh(frm) {
    frm.add_custom_button('Go to Workshop', () => {
      frappe.set_route('Form', 'Service Workshop', frm.doc.service_workshop);
    });
  }
});
```

### **Server-Side Hook Example:**
Add validation to ensure bay name follows a pattern:
```python
def validate(self):
    if not self.bay.startswith("BAY-"):
        frappe.throw("Bay name must start with 'BAY-'")
```

---

## **6. Troubleshooting (Common Errors and Resolutions)**

| Error Message | Cause | Resolution |
|---------------|-------|------------|
| *Bay already exists* | Duplicate entry | Ensure the `Bay` field value is unique. |
| *Service Workshop not found* | Linked record missing or deleted | Verify that the linked **Service Workshop** exists. |
| *Permission Denied* | Role lacks access | Check user roles and permissions under the **Role Permissions Manager**. |

---

## **7. User Roles and Permissions**

| Role            | Permissions             |
|-----------------|--------------------------|
| System Manager  | Full access (Create, Read, Update, Delete) |
| Custom Role (optional) | Configure via **Role Permissions Manager** |

---

## **8. Key Notes**
- The `Bay` name is used as the document title and must be unique.
- Linking bays to workshops improves traceability and analytics in scheduling services.
- Enabling `track_changes` ensures auditability for updates made to Bay records.

---

## **9. What Business Process Pain Point Does It Help Remove**
The **Bay** DocType helps eliminate ambiguity in service bay usage and scheduling by:
- Clearly identifying and linking bays to service locations.
- Enabling efficient resource planning and workload distribution.
- Preventing double booking or overlapping assignments in vehicle servicing operations.
- Providing visibility into bay availability for managers and coordinators.

---