Overview
The BuildOps connector with Viewpoint Spectrum streamlines the flow of customer, contract, and job data between Viewpoint Spectrum and BuildOps. This integration enables construction businesses to manage operations efficiently, improve communication, and gain valuable insights into their financial and job performance data.
This document outlines:
The mechanics of the integration
Objects shared between BuildOps and Spectrum
Triggering events and expected behaviors
Integration Mechanics
Supported Spectrum Offerings
BuildOps supports both Cloud and On-premise Spectrum implementations. During onboarding, we will:
Identify your Spectrum version
Create BuildOps-specific system users
Ensure security controls over financial data
Data Processing Workflows
The integration operates in two directions:
BuildOps-to-Spectrum: Operational data (e.g., invoices) is sent from BuildOps to Spectrum.
Spectrum-to-BuildOps: Financial data (e.g., customers, payments, tax rates) is imported from Spectrum into BuildOps.
By reducing duplicate data entry, this integration minimizes errors and maintains consistency across platforms.
Data Workflow – BuildOps to Spectrum
A BuildOps user creates a financially relevant document (e.g., an Invoice).
The BuildOps Operations Platform processes the document and sends it to the BuildOps Integration Service.
The Integration Service transforms the data into a Spectrum-compatible format and sends it to Spectrum.
Spectrum writes data to its database and displays it in its user interface.
Spectrum sends a success/failure response back to BuildOps.
The Integration Service forwards the response to BuildOps.
Every 1-2 minutes, BuildOps updates its database and user interface accordingly.
Data Workflow – Spectrum to BuildOps
A Spectrum user creates a document (e.g., new Customer, Tax Rate, AP Invoice, or Payment).
Every 30 minutes, the BuildOps Integration Service reads the Spectrum database for new or updated data.
If new or updated data is found, the Integration Service transforms it into a BuildOps-compatible format.
Every 1-2 minutes, BuildOps updates its database and user interface accordingly.
Notification Emails
BuildOps’ Spectrum integration includes an automated email notification system. Notifications can be sent for both successful and failed syncs.
Businesses commonly use this feature to:
Alert compliance teams about jobs that require review
Provide fallback alerts for sync failures
Object Definitions & Data Syncing
User-Defined Fields (UDFs)
Spectrum supports User-Defined Fields (UDFs) for customized data tracking.
During onboarding, BuildOps will configure UDF support for documents such as:
Jobs
Service Agreements
Purchase Order Receipts
AR Invoices
Accounting Data & Transactions
Accounts Receivable (AR) Invoice
Description:
A BuildOps AR Invoice itemizes labor, materials, discounts, and tax.
AR Invoices may originate from a Job-to-Invoice process or be created ad-hoc.
BuildOps exports AR Invoices to Spectrum.
Triggering Event:
A user clicks “Export Invoice” after review and approval.
Behavior Notes:
Tax Rate: If tied to a Job, the Job’s tax rate is used. Otherwise, the Invoice’s selected tax rate applies.
GL Account Mapping: Defined during onboarding (e.g., mapped by department or cost center).
Accounts Receivable (AR) Payment
Description:
Payments are created in Spectrum and imported into BuildOps.
Triggering Event:
A Spectrum user posts a Payment, and BuildOps syncs it during the next polling cycle.
Classes
Description:
In BuildOps, Classes map to Spectrum’s GL Departments.
Classes define departments throughout BuildOps.
Triggering Event:
A Spectrum user creates, updates, or deletes a Department.
Customers
Description:
Customers are created in Spectrum and imported into BuildOps.
Triggering Event:
A new Customer is created in Spectrum.
Behavior Notes:
Some businesses only allow Customers to be created in Spectrum for compliance reasons.
General Ledger (GL) Accounts
Description:
GL Accounts categorize transactions (Revenue, Expenses, etc.).
Created in Spectrum and imported into BuildOps.
Triggering Event:
A GL Account is created or updated in Spectrum.
Jobs
Description:
Jobs are created in BuildOps and exported to Spectrum.
Tracks costs, wages, time, and other Job-specific data.
Triggering Event:
A user creates or updates a Job in BuildOps.
Behavior Notes:
Job updates in Spectrum do not sync back to BuildOps.
Purchase Orders & Bills
Purchase Order Receipts
Description:
Represents received materials from a PO.
Created in BuildOps and exported to Spectrum.
Triggering Event:
A user posts a PO receipt in BuildOps.
Behavior Notes:
All POs must be linked to a JC Job and have assigned cost types.
Purchase Order Bills
Description:
Represents Vendor Invoices for received items.
Created in Spectrum and imported into BuildOps.
Triggering Event:
A Spectrum user posts a Vendor Invoice referencing a PO Receipt.
Sales Tax (AR & AP)
Sales Tax (AR) – Customer Sales Tax
Description:
Tax applied to customer invoices.
Created in Spectrum and imported into BuildOps.
Triggering Event:
A Spectrum user updates a Sales Tax Rate.
Sales Tax (AP) – Vendor Tax
Description:
Tax applied to vendor purchase order bills.
Created in Spectrum and imported into BuildOps.
Triggering Event:
A Spectrum user updates a Purchase Tax Rate.
Service Agreement Maintenance
Description:
Service Agreements are tracked in BuildOps, but only individual Maintenances are exported to Spectrum.
Triggering Event:
A user schedules a Maintenance in BuildOps.
Behavior Notes:
Service Agreement updates in Spectrum do not sync back to BuildOps.
Vendors
Description:
Vendors are created in Spectrum and imported into BuildOps.
Vendors are used for POs and materials.
Triggering Event:
A new Vendor is added in Spectrum.
Enhancement Requests
If a required feature is missing, businesses can provide feedback to their sales or implementation team. The BuildOps product team will evaluate enhancement requests for future releases.