Build Plan (BP)

The BP acts as a container for data related to all work done in a contiguous stretch of time, for a single "Site," under a single contract. Construction company operations and financials center on individual Site builds, represented in FieldCLIX as "Build Plans." BP is approximately equal to what is called a "Customer Job" in many ERP systems. Each BP gets a single Budget and COP. A BP might have 1 or several Client POs, Vendor POs, Vendor Bills, Sales Orders/Quotes, BOMs and WOs. It can have Milestones and is a key delimiter on all operational and financial dashboards. A BP might represent all work and finances associated with a Monopole Upgrade done for Ericsson AT&T in the fall of 2019. It might also be a Rooftop Trouble-Ticket for ACAS or a DFW Airport Terminal IDAS project done for a multi-carrier escrow account. A BP sometimes equates to what companies have traditionally called a "Project" but is not to be confused with an FCX "Project" which is more of a "Line-Of-Business." BPs are Subordinate to Project Scenarios and Predominate to Work Orders.

Build Plan Owner (BPO)

The BPO is a Project "Role" which is a required attribute on any BP and must be assigned to a single Employee per BP. Construction company operations and financials center on individual Site builds, represented in FieldCLIX as BPs. The Employee with final responsibility for the financial success of a build is therefore usually assigned as the BP's "Owner." BPO is assigned at the time of BP Generation and is and can be used for many process, notification and access rights configurations throughout the system.

Checklist Item

An item on a WO Task, Photo/Video or Document Checklist which requires users of the mobile application to take return some deliverable, most commonly a photo using a built-in camera interface. Checklist Item results are recorded along with GPS and time data and can be reviewed via the CLPM Review Interface.

Component

A type of Conterra Object which stores or manages structured information. Conterra Components include References/Reference Records, wizards and reports.

Conterra Explorer

The user interface through which Conterra and any Business Solutions built on it can be accessed. The Conterra Explorer is the "home" screen of Conterra first encountered at startup and the point from which Objects and processes can be opened/launched.

Conterra

An Enterprise Content Management (ECM) Platform for software Business Solutions which use its core features of a union repository, Workflow services and structured information management to help companies do work with improved collaboration and efficiency.

Deliverable

Goods or service products to be delivered as part of an agreement. For example: photos or videos required by the client as proof of work done.

Dynamic Dispatch Management (DDM)

DDM centers around the Dispatch Calendar Dashboard which presents info like PTO and weekly OT accrual per Employee to help Dispatchers make data-driven decisions about the Dispatch Schedule. WOs are scheduled to crews based on scope and can be used to deliver documents to and from the field, like COP Checklist Photos, and collect data on the deployment like Site arrival/departure times. DDM Contains the FieldCLIX Chat Module (Powered by Telegram) which enables auto-created Chat groups per BP.

ECM Object

A type of Conterra Object which stores of manages unstructured information. Conterra ECM Objects include inbox Objects and documents.

FieldCLIX (FCX)

FieldCLIX is an Enterprise Software Solution Suite built to manage every part of a field service company's business. FCX Business Solutions address HR, Dispatching, Timekeeping, AP and AR, Material/Inventory Control, Equipment/Asset Mgmt., Close-Out Package Mgmt., and Financial Planning and Analysis. FCX brings users operationally-focused Job Costing with data and process mgmt. that tracks all revenue and spend against each Site Build. Unlike accounting software, FCX is built to enable data-driven operational decisions to increase the efficiency and profitability of field projects.

Job

A type of Conterra ECM actionable Object that helps formalize a Workflow by conveying work to a work performer and documenting their completion of that work. Jobs are delivered to the Conterra inbox and contain information/instructions, links and buttons one can click to document that the work has been done.

Lifecycle

The path an Object takes through its possible life Stages as determined by work done and choices made by users.

Object

A body of data in a software system. An Object may store static information or may be a script which when run acts on other Objects to cause some change. Conterra Objects come in two forms: Components and ECM Objects.

Photo/Video Checklist

A checklist which can be set up to require users of the FCX Mobile App to take certain photos or videos during field deployment. Users take the photos/videos using a camera interface built into the application. The photos/videos are automatically named and uploaded as Deliverables.

Reference Record

A card which holds a specific type of structured information. Taken together, the collection of cards of the same type is a Reference.

Reference

An information table composed of individual Reference Records which hold the same type of structured information.

Requisite

An individual piece of structured information stored in a Reference Record.

Role

The position a person fills in a system as defined by his or her responsibilities.

Time Keeping (TK)

Time Keeping (note the spelling) is, itself, neither a payroll nor an accounting system, but is used to record, audit, allocate and prep hours which can then be ported to a payroll system for final execution. With field Resources dispatched through FCX DDM and GPS-tracked through our smartphone App, time can be Auto-Allocated based on Site Geofences. A Time Card Review Interface helps reviewers analyze TK data and quickly process TCs for a more efficient Payroll.

Time Keeping Administrator (TKA)

The TKA is a System Role in FCX Time Keeping that grants access and channels processes to Employees authorized and responsible for adjusting recorded labor hours for accurate Job Costing and Payroll Export. TKAs may be Payroll Clerks who port the processed hours from FCX to a payroll system, or, may work with the person who does this at the end of each Payroll Period.

Work Order (WO)

A Work Order in FCX is used to assign work and track labor and deliverables against a specific scope under a BP. Common WO Types include things like "Tower Install," "Site Walk," "Tiger Team," "Training" and "Integration." Both "Direct-Cost" type WOs and "Overhead" types are used so that every hour of labor in the company can be bucketed with WOs for Financial Planning and Analysis, and to inform quoting and Invoicing. WOs are often used as "Work Authorization" forms for field deployments and can have deliverable Checklists attached to them to aid Close-Out Package Mgmt. WOs are Subordinate to BPs and Predominate to Checklists.