Overview
Objects represent physical locations or buildings where you perform service for customers. They could be office buildings, retail stores, warehouses, production facilities, or any other site. Objects help you organize customer assets by location and track service history at each site.
Objects are child records of Customers. Each object must belong to a customer and represents a specific location where that customer has equipment or requires service.
When to Use Objects
Use the Objects module when you need to:- Define multiple service locations for a single customer
- Track which assets are at which location
- Organize work orders by site or building
- Maintain site-specific access information (gate codes, parking, etc.)
- Generate reports by location
- Assign technicians based on geographic area
Understanding Objects
Object Hierarchy
- Customer: “Acme Corporation”
- Object: “Acme HQ - Downtown”
- Assets: Machine System #1, Machine System #2, Elevator #1
- Object: “Acme Warehouse - Industrial Park”
- Assets: Forklift #1, Loading Dock Door #1, Dock Door #2
- Object: “Acme HQ - Downtown”
Objects vs Customers vs Assets
Customer
The Company or organization.
Example: “Acme Corp”
Example: “Acme Corp”
Object
A Physical Location where the customer operates.
Example: “123 Main St Office”
Example: “123 Main St Office”
Asset
Equipment at that location that requires service.
Example: “Rooftop Machine Unit”
Example: “Rooftop Machine Unit”
Objects List View
Key Features
Branch Filtering
Branch Filtering
Filter objects by branch to see locations relevant to your service area.
Search and Sort
Search and Sort
Search by object name, address, or customer. Sort by any column to organize your view.
Customer Grouping
Customer Grouping
View all objects for a specific customer to see all their locations at once.
Object List Columns
When Fentu FSM is integrated with SAP Business One, locations are created via the integration: SAP Business One ShipTo → Fentu FSM Location. New locations created directly in Fentu FSM will not be synced back into SAP B1.
Creating a New Object
1
Click 'New Object'
Click the “New Object” or ”+” button in the top right corner.
2
Select Customer
Choose which customer this object belongs to from the dropdown.
3
Enter Location Details
Fill in the object name, address, and other location information.
4
Add Access Information
Document gate codes, parking instructions, key locations, etc.
5
Save
Click “Save” to create the object record.
Object Information Fields
Basic Information
Address Information
Access Information
Contact Information
Site Details
Service Information
Notes and Instructions
Common Object Types
Office Buildings
Office Buildings
Typical Assets: Machine systems, elevators, security systems, lightingKey Information to Track: Floor number, access hours, parking validation, reception check-in procedures
Retail Stores
Retail Stores
Typical Assets: Refrigeration units, Machine, point-of-sale systems, lighting, security camerasKey Information to Track: Store hours (service typically after closing), manager contact, loading dock access
Warehouses
Warehouses
Typical Assets: Forklifts, dock doors, lighting, security systems, material handling equipmentKey Information to Track: Loading dock hours, forklift certification requirements, safety equipment requirements
Production Facilities
Production Facilities
Typical Assets: Production machinery, machines, electrical systems, specialized equipmentKey Information to Track: Production schedules (to avoid service during production), safety requirements, specialized training needs
Data Centers
Data Centers
Typical Assets: machines/cooling systems, electrical/UPS systems, security systems, fire suppressionKey Information to Track: Strict access control procedures, change management requirements, uptime SLAs
Object Actions
From the List View
View Details
Click the object name to see complete information, assets at this location, and service history.
Edit Object
Update address, access information, or other object details.
View Assets
See all equipment and assets registered at this location.
Create Work Order
Quickly create a new work order for service at this location.
From the Detail View
When viewing an object record, you can access all related records:Multi-Location Customers
Best Practices for Managing Multiple Locations
When a customer has multiple objects (locations), follow these strategies:1
Use Consistent Naming
Establish a naming convention: “Customer Name - Location Descriptor”
Example: “Acme Corp - Headquarters”, “Acme Corp - Warehouse 1”, “Acme Corp - Retail Store North”
Example: “Acme Corp - Headquarters”, “Acme Corp - Warehouse 1”, “Acme Corp - Retail Store North”
2
Assign Site-Specific Contacts
Create contacts for key people at each location, not just corporate contacts.
3
Document Site Differences
Each location may have different access procedures, hours, and requirements. Document these carefully.
4
Assign to Service Territories
Use the service area or branch field to route work orders to the appropriate technicians.
Tips and Best Practices
Create Objects Even for Single-Location Customers
Create Objects Even for Single-Location Customers
Even if a customer only has one location now, create an object record. This makes it easy to add more locations later without restructuring your data. It also provides a place to document site-specific access information.
Use Descriptive Names
Use Descriptive Names
Object names should clearly identify the location. “Building 3” is unclear, but “Acme Corp - Warehouse Building 3, Industrial Park” tells technicians exactly where to go.
Keep Access Information Current
Keep Access Information Current
Gate codes, key locations, and access procedures change frequently. Review and update access information regularly, especially after security changes.
Document Parking and Access
Document Parking and Access
Technicians waste time and create poor impressions when they can’t find parking or don’t know how to access the building. Document clear instructions for first-time visits.
Link Site Contacts
Link Site Contacts
Identify and link contacts specific to each location. Don’t rely solely on corporate contacts who may not know site-specific details.
Use Object Types Consistently
Use Object Types Consistently
Establish standard object types and use them consistently for better filtering and reporting. Examples: Office, Retail, Warehouse, Production, Data Center, Remote Site.
Document Special Requirements
Document Special Requirements
Some sites require background checks, safety certifications, insurance certificates, or special equipment. Document these requirements so technicians are prepared before arriving.
Track Service Territory
Track Service Territory
Use the service area or branch field to ensure work orders are routed to technicians who cover that geographic area.
Common Questions
Do I need to create objects for customers with only one location?
Do I need to create objects for customers with only one location?
Yes, it’s recommended. Creating an object even for single-location customers:
- Provides a place to document site-specific access information
- Makes it easy to add more locations later
- Maintains consistent data structure across all customers
- Improves reporting and analytics
What's the difference between a customer address and an object address?
What's the difference between a customer address and an object address?
The customer address is typically the billing or corporate headquarters address. The object address is where service is actually performed. For many small customers, these are the same. For larger customers, they’re often different (corporate HQ vs various service locations).
Can an asset belong to multiple objects?
Can an asset belong to multiple objects?
No, each asset is registered at one specific object (location). If equipment is moved to a different location, update the asset record to reflect the new object.
How do I handle temporary locations?
How do I handle temporary locations?
Create object records for temporary locations (construction sites, pop-up stores, etc.) and mark them as inactive once the project is complete. This preserves historical service records while keeping current location lists clean.
Should I create separate objects for different buildings on the same campus?
Should I create separate objects for different buildings on the same campus?
It depends on your service needs. If buildings have different access procedures, contacts, or equipment types, create separate objects. If they’re managed as one unified site, a single object may suffice. Consider: Do technicians need different instructions or contacts for each building?
Can I delete an object?
Can I delete an object?
You can delete objects that have no associated assets or work orders. Objects with historical data should be marked as inactive instead of deleted to preserve service history.
How do I move an asset from one object to another?
How do I move an asset from one object to another?
Edit the asset record and change its assigned object. This is useful when equipment is relocated from one site to another. The service history moves with the asset.
What should I put in the Object Code field?
What should I put in the Object Code field?
Use a short, memorable code for internal reference. Common approaches:
- Customer abbreviation + location: “ACME-DT”, “ACME-WH1”
- Geographic code: “NYC-001”, “CHI-SOUTH”
- Facility number: “FAC-0123” Keep codes short (under 10 characters) and consistent across your organization.
Related Documentation
Customers
Manage parent customer records for objects.
Assets
Register equipment at each object location.
Work Order Wizard
Select objects when creating work orders.
Contacts
Assign site-specific contacts to objects.