Bay Management

Bays are loading and unloading positions at a terminal. Coyote uses bay configuration during imports (file-to-bay assignment), transaction display, and API alarm validation on TransLog loads.

Bay management is done on the Facility detail page, not on a separate Bays menu.

Open bay settings

1. Go to Admin → Facilities in the sidebar.
2. Click the facility (terminal) you manage.
3. Open the Bays tab.

You need facility access and bay management permissions (facility:bays:create, facility:bays:update, or facility:bays:delete).

Bay list views

The Bays tab supports two layouts:

• Cards — visual grid with bay number, type, active status, and API alarm summary
• List — table with bay number, label, type, active flag, and actions

Use the toggle in the tab header to switch views.

Bay fields

Field	Description
Bay number	Unique number per facility (required when creating)
Label	Display name (for example North Rack)
Bay type	Loading, Unloading, or Bidirectional
Active	Inactive bays are hidden from new assignments but keep historical data
API alarm	Optional min/max API gravity range for import validation

Bay types and import behavior

Bay type	Import movement
Loading	Creates carrier out (delivery) movements
Unloading	Creates carrier in (receipt) movements
Bidirectional	Direction taken from file / parser context

When you upload a bay file in Imports, assign each file to the correct bay. Coyote uses the bay type to set the default movement type on created transactions.

Add a bay

1. On the facility Bays tab, click Add Bay.
2. Enter bay number and optional label.
3. Select bay type.
4. Optionally enable API alarm and set Min API and Max API.
5. Save.

Bay numbers must be unique within the facility.

Edit a bay

1. Click the bay card or the edit action in list view.
2. Update label, bay type, active status, or API alarm settings.
3. Save.

Tip

Deactivate a bay instead of deleting it if historical transactions reference that bay.

API alarms

When API alarm is enabled on a bay:

• Imports validate each load’s API gravity against the configured min and max.
• Out-of-range values raise warnings or alarms on import rows (depending on severity rules).
• Operators can acknowledge alarms during import review before approve.

Configure alarms per bay when different racks accept different API ranges.

Delete a bay

1. Open the bay edit dialog or use the delete action in list view.
2. Confirm deletion.

Deletion may be blocked if transactions or import batches still reference the bay. Prefer deactivating the bay if it is in use.

Bays and imports

During New Import:

• Coyote may suggest a bay from the filename (for example Bay2_20260115.txt).
• You must confirm the bay for each bay/carrier file before processing.
• Each processed file creates an import batch linked to that bay.

If loads appear on the wrong bay, re-import with the correct bay assignment or correct bay configuration before the next production day.

Bays and transactions

Approved loads show Bay on the transaction detail page (for example Bay 2). The bay comes from:

• Import batch bay assignment
• Manual transaction entry
• Integration mapping

Facility context

Bays belong to a single facility. Other facility settings that affect loads and imports:

• Timezone and operational cycle start — production day boundaries
• Pipelines tab — separate from bays; used for pipeline reading imports
• Meters — may be linked to bays via meter assignments

Configure facility-wide settings on the facility Overview and Settings tabs before adding bays.

Permissions

Action	Permission
View facility and bays	org:facilities:list + facility access
Create bay	facility:bays:create
Update bay	facility:bays:update
Delete bay	facility:bays:delete

Related topics

• Uploading Import Files — assign files to bays during upload
• Viewing Loads — see which bay a transaction used
• Overview — how bays fit in the load workflow