FieldEx allows Admins to define and manage three core entities that drive operations: Customers, Sites, and Projects.
Understanding the Differences
Entity | What It Represents | Example Construction Use |
Customer | The business, company, or internal team you're working for. |
|
Site | The actual location where work is done or equipment is installed. |
|
Project | A defined scope of work tied to a customer (and optionally, multiple sites). |
|
In construction: Customer = Who owns it, Site = Where it’s happening, Project = What you’re doing. |
Configure Customer Fields
Path: Settings > Modules > Customers > Configuration
Customers represent who you're doing work for external clients, departments, or internal divisions.
Field Name | Description | Example |
Customer Number Format | Auto-number format for customer IDs |
|
Type | External or internal client categorization |
|
Category | Function of the customer or account |
|
Why This Matters: Proper segmentation helps filter customers, apply workflows, and keep external vs. internal work tracked separately. |
Setting Up Site Configuration
Path: Settings > Modules > Sites > Configuration
Sites represent where your services take place such as jobsites, customer facilities, or equipment yards.
Field Name | Description | Example |
Site Number Format | Auto-generated identifier for the site |
|
Area | Geographic region used for planning or filtering |
|
Category | Purpose of the site |
|
Subcategory | More specific classification |
|
Type | Operational role of the site |
|
Best Practices: Align Areas with field planning zones. Keep Category/Subcategory consistent with how you assign equipment. |
Setting Up Project Configuration
Path: Settings > Modules > Projects > Configuration
Projects represent the scope of work and group job orders across customers and sites. This is especially useful for construction, infrastructure, and multi-phase engagements.
Field Name | Description | Examples |
Project Number Format | Auto-generated project ID used for reference and traceability |
|
Project Type | Describes the nature of the engagement or contract |
|
Project Category | Used for analytics, filtering, and reporting by trade or business line |
|
Best Practices: Prefix project numbers with a year or business unit (e.g., PRJ-2025-001 or TX-PRJ-####). Use Project Type to control which workflows apply (e.g., PM, Emergency), and Category for visual grouping and analytics reporting across your organization. |