One Big Green organizes your customer portfolio and operational data in a structure that reflects how plant service work is managed in the real world.

The Service Site is the top level of the customer portfolio. From there, you can organize the services you provide, the physical layout of the site, the field inventory, and the work your team performs.

Understanding this structure helps you set up your data consistently, import information correctly, and make it easier for your team to find the right site, service, and inventory when they need it.

The main structure can be understood as follows:

Service Site
├─ Services
│ └─ Field Inventory
│ └─ Display
│ └─ Planter(s)
│ └─ Plant(s)
├─ Site Contacts
└─ Site Structure
└─ Floor(s)
├─ Zone(s)
└─ Room(s)

Services, Site Contacts, the physical site structure, and Field Inventory are separate parts of the Service Site.
​
A Service defines the service relationship you manage at the location.
​
Site Contacts belong to the Service Site and provide contact information for the people associated with that location.
​
Floors, Zones and Rooms describe the physical layout, while Field Inventory is created per Service because different Services can have completely different inventories.
​

A Service Site represents a physical customer location where your company performs work. It is the top level of the customer portfolio in One Big Green and the main container for the information related to that location.

A Service Site can have only one address. If the same client has several service locations at different addresses, it is usually most sensible to create separate Service Sites for those locations. This keeps each physical location and its address clearly defined in OBG.

A Service Site can contain one or more Services, its physical structure, and its field inventory. It can also have site-specific information such as contacts, access details, parking information, water source, and other operational notes.

A Service represents a service your company provides at a Service Site.

You can create as many Services as you need at a Service Site. There is no restriction that a Service Site can have only one Interior Service, one Exterior Service, or one Service of any other type.

Multiple Services can be used whenever different services need to be managed, assigned, or scheduled separately.

For example, a customer location might have two interior services: one Interior Service for the floor plants and another Interior Service for a living wall. You can log these as separate Services so they can be assigned to different technicians and placed on different Service Visit schedules.

When a Service Site has several Services of a similar type, Service nicknames provide a practical way to distinguish them.

A Service nickname is a short description that helps your team understand what a particular Service is for.

Using the example above, you could have two Interior Services with nicknames such as "Floor Plants" and "Living Wall". The nickname does not change the type of Service. It simply makes the Services easier to identify in everyday work.

This is particularly useful when managers are scheduling visits, assigning technicians, or reviewing work and need to immediately understand which part of the customer's operation a Service refers to.

Remember that a Service is not the same as a Service Visit. The Service describes the ongoing service relationship, while a Service Visit is a specific occurrence of work.

Site Contacts are information that belongs to the Service Site itself rather than to a particular Service or Field Inventory. They identify the contact persons associated with the customer location and can be useful across the services managed there.

Site Contacts are separate from the physical structure of the Service Site.

The physical structure is described through Floors, Zones, and Rooms, while Site Contacts provide the people and contact information associated with the location.

Floors, Zones and Rooms are part of the physical structure of a Service Site. They describe the physical layout of the location and help field teams find the Displays they need to service.

A Service Site can be divided into Floors. A Floor can then be divided either into Zones or into Rooms. Zones and Rooms are alternative ways of organizing a Floor, depending on what makes more sense for the building.

For example, a large office building might be easier to organize into Zones such as Reception, Restaurant, and Open Office. Another building might be easier to organize directly into Rooms such as Meeting Room 1, Meeting Room 2, and Kitchen.

This structure also makes it easier for technicians to use filters when working through a larger Service Site.

Rooms do not belong to Zones. Both Zones and Rooms belong directly to a Floor. You do not have to use both.

Choose the structure that gives your field team enough information to find the right place without making the data unnecessarily complicated.

Field Inventory is created per Service, not per Service Site. This is important when a customer has several different Services whose inventories are completely different.

For example, an Interior Service might have an indoor plant inventory, while an Exterior Service and a Floral Service have their own separate inventories.

A Display represents a serviced plant display or installation within a Service's Field Inventory. A Display can contain one or several Planters, depending on how the installation is set up and how your company wants to represent it.

For example, a styled group of containers that match in color, shape, and style can be represented as one Display, with several Planters belonging to that Display.

If you are unsure whether a group should be logged as one Display or several Displays, we recommend separating them into individual Displays. This gives you more flexibility when managing the inventory, service work, and future changes.

A Display can be associated with the relevant Floor, Zone, or Room in the Service Site's physical structure. This helps technicians locate the Display and makes it easier to use the available filters when working through a larger Service Site.

Planters belong to Displays. A Display can have one or several Planters.

Keeping Planters under the Display reflects the physical installation: the Display is the overall serviced arrangement, while the Planters are the individual containers that make up that arrangement.

Plants belong to Planters. A Planter can contain one plant or several plants.

Several plants are common in mixed plantations, where different plant varieties are planted together in the same planter. Plants remain associated with their Planter, and Planters remain associated with their Display.

Several plants are common in mixed plantations, where different plant varieties are planted together in the same planter.

This structure allows OBG to record each plant while keeping it connected to the specific Planter and Display where it belongs.

The structure above provides the context for the work your team performs. Jobs and visits connect planned and completed work to the relevant Service Site, Service, and field inventory.

A Service Visit is a specific occurrence of work performed for a Service. The Service defines the ongoing service relationship, while the Service Visit represents the actual visit that is scheduled and completed by the field team.

Different Services within the same Service Site can have different technicians and different Service Visit schedules.

A Delivery is a type of visit with the purpose of bringing certain physical goods to the customer location.

For example, a Delivery can be used to bring plants, planters, materials, or other goods to a site.

Deliveries can also be used to schedule and manage installations.

A Quality Inspection is a type of visit used to carry out a structured check of service quality at a customer location.

The connected operational data can also include:

A clear structure helps everyone work with the same information. Field team members can find the right location and inventory more easily, while managers can schedule work and review operational information with the right context.