BST10 Visual Settings Guide

1. Connection Credentials

In Mosaic

Connection Credentials allow Mosaic to authenticate against the replicated BST10 SQL Server database. BST10 is replicated to Mosaic's cloud infrastructure on Azure — credentials are provisioned during onboarding by the Mosaic Solutions team and do not need to be re-entered manually.

📝

In BST10: Mosaic reads from the BST10 Final schema on your replicated SQL Server. The Final schema contains posted (committed) records only — unposted timesheets and unposted transactions are not visible to Mosaic.

To Get Started

1. Follow the full setup instructions in the BST10 Integration Setup guide.
2. Provide your IT contact and BST10 DBA contact to the Mosaic Solutions team so the replica can be configured.
3. Once the replica is in place, the Mosaic Solutions team will validate connectivity and run an initial sync.

⚠️

Replica credentials are managed by the Mosaic Solutions team. If your BST10 database is moved, upgraded, or credentials rotate, notify your CSM so the replication can be re-validated.

1. Standard Roles

In Mosaic

Standard Roles define the set of available Roles that can be assigned to Members across the platform. These are used for resource planning, filtering, and rate calculations.

📝

In BST10: Standard Roles map to Labor Bill Classes in BST10. Each Labor Bill Class becomes a Standard Role in Mosaic.

Setting Options

• Transfer — The full list of BST10 Labor Bill Classes will appear as available Roles in Mosaic. Any changes in BST10 will overwrite the corresponding Roles in Mosaic on each sync.
• Do not transfer — Roles must be created and maintained manually within Mosaic. Choose this if your firm manages Roles independently or if BST10 Labor Bill Classes do not align with how your team plans work.

2. Default Roles

In Mosaic

A Member's Default Role determines which Role is automatically assigned when they are added to a Project. This drives resource planning defaults and rate assignments.

📝

In BST10: The Default Role maps to the employee's assigned Labor Bill Class on the Employee record (Employee.BillClass).

Setting Options

• Transfer — Each Member's Default Role is kept in sync with BST10. Any time the Labor Bill Class changes in BST10, it will be updated in Mosaic on the next sync.
• One time at first link — The Role is transferred once during the initial Member link. After that, the Role can be changed independently in Mosaic without being overwritten.

3. Bill Rates

In Mosaic

Bill Rates represent the rate that is charged to clients per hour of a Member's work. They appear on Member profiles and are used for budget calculations, invoice projections, and rate-driven Time Entry rates.

📝

In BST10: Bill Rates come from the Labor Bill Rate Schedule assigned to a project's Labor Terms. Member rates can also be overridden at the project level via Project_LaborTerm_LaborBillRateScheduleOverride.

Setting Options

• Transfer — Each Member's Bill Rate is kept in sync with BST10. Standard and override rates are both synced.
• Do not transfer — Bill Rates must be managed manually in Mosaic.

4. Cost Rates

In Mosaic

Cost Rates represent a Member's salary or expected cost per hour. They appear on Member profiles and are used for financial calculations including profit margins, project health metrics, and budget forecasting.

📘

You must Enable Cost Rates for the Organization to transfer Cost Rates. This setting is controlled by the Cost Rates feature flag — contact your Mosaic team if this option is not visible.

Setting Options

• Transfer — Cost Rates are kept in sync with BST10 where available.
• Do not transfer — Cost Rates must be managed manually in Mosaic.

1. Default for new Projects

In Mosaic

A Portfolio is a folder used to organize multiple Projects — for example, by department, client, manager, or type of work. This setting determines which Portfolio newly linked BST10 Projects are placed into by default.

📘

In BST10: There is no direct equivalent to Portfolios in BST10. This is a Mosaic-only organizational concept.

Setting Options

• No Portfolio (default) — Newly linked Projects will not be assigned to any Portfolio. They can be moved into a Portfolio manually later.
• Import — A built-in Portfolio provided by Mosaic specifically for integration-linked Projects.
• [Your Portfolios] — Select any other existing Mosaic Portfolio to automatically place newly linked BST10 Projects into that Portfolio.

This setting only applies to new Projects at the time they are first linked. It does not retroactively move existing linked Projects.

1. Linking Method

In Mosaic

This setting determines how BST10 Projects are connected to Mosaic. Importing means bringing a Project from BST10 into Mosaic for the first time. Linking means establishing an ongoing connection so that changes in BST10 are synced to Mosaic automatically.

📝

In BST10: Projects live in the BST10 Project Master. The data imported includes Project name, code, dates, fee, client, billable status, and project status.

Setting Options

• Manually linked — No Projects will be automatically linked. You choose which BST10 Projects to import and link on a project-by-project basis.
• Automatically linked — All Projects that meet the criteria specified in the Automatic Linking Filter will be automatically linked.

2. Linked Project and Phase Titles

In Mosaic

This setting controls whether Mosaic keeps Project and Phase titles in sync with BST10, or allows them to diverge after the initial link.

Setting Options

• Overwrite — Mosaic Project and Phase titles will match the BST10 titles. If a linked title is edited in Mosaic, it will be overwritten back to match on the next sync.
• Do not overwrite — Mosaic Project and Phase titles can be edited independently.

3. Project and Phase Billable

In Mosaic

The billable status indicates whether a Project or Phase is charged to the client.

📘

In BST10: Billable status is derived from the HasChargeable flag on the Project or Project_Task record.

Setting Options

• Transfer — Billable statuses stay in sync with BST10. Any time the billable flag changes, it will be updated in Mosaic on the next sync.
• Do not transfer — Mosaic is the source of truth for billable status.

4. Project and Phase Dates

In Mosaic

Project and Phase start and end dates drive timelines, scheduling, and resource planning in Mosaic.

📘

In BST10: Dates come from the StartDate and FinishDate fields on Project and Project_Task records.

Setting Options

• Transfer — Timelines in Mosaic stay in sync with BST10. If dates change in BST10, Mosaic schedules update automatically.
• One time at first link — Dates are imported during the initial link and can then be adjusted independently in Mosaic.

5. Project and Phase Fee

In Mosaic

The Fee represents the total amount you plan to bill for a Project, or the portion allocated to a specific Phase.

📝

In BST10: Project Fees come from Project.FeeAmount. Phase Fees are aggregated from child labor budgets (ProjectTaskSummary.ChildBudgetSum), falling back to the phase's own budgeted labor amount.

Setting Options

• Transfer — The Fee for each Project and Phase stays in sync with BST10. Fee changes will overwrite the corresponding values in Mosaic on each sync.
• One time at first link — Fees are imported during the initial link and can then be adjusted independently in Mosaic.

6. Archived Projects

In Mosaic

Archiving hides Projects from active planning views but preserves all data and associations for historical tracking and reporting.

📝

In BST10: Archiving is triggered by the Project Status value on the Project record. Status Inactive (1) maps to archived in Mosaic.

Setting Options

• Automatically archive Inactive Projects — Archives Mosaic Projects marked as Inactive in BST10.

Archived Projects also archive any related Work Plans and stop new Time Entry syncing.

7. Project Status Matching

In Mosaic

Maps each BST10 project status to a corresponding Mosaic Project status. The mapping is applied any time a project's status changes in BST10.

Default Mapping

For each BST10 status, select the Mosaic Project status that should be applied. The change is applied when the status is updated in BST10.

How it works

• Each BST10 status is matched to a Mosaic status. The list of source statuses comes from your connected tool, so you'll need a tested connection before you can edit.
• Unmapped statuses sync as Active — if a status isn't listed, Mosaic sets the project or phase to Active.
• Click Reset to default at any time to restore Mosaic's recommended mapping for this integration.
• Changes apply on Save (the button reads Done when there are no changes). Updates affect future syncs; already-synced records keep their current status until they next change in BST10.

📘

For a full walkthrough of the mapping editor, see Project & Phase Status Matching.

1. Linking Method

In Mosaic

A Phase is a distinct stage within a Project's lifecycle, with its own date range, Fee, and status. This setting determines how BST10 Phases are connected to Mosaic.

📘

In BST10: Phases correspond to Project Tasks (Project_Task) under a Project. Sub-phases are nested via ParentNodeId.

Setting Options

• Manually linked — No Phases will be automatically linked. You choose which BST10 Phases to import and link.
• Automatically linked — All Phases that meet the filter criteria will be automatically linked.

2. Phase Status Matching

In Mosaic

Maps each BST10 phase status to a corresponding Mosaic Phase status. The mapping is applied any time a phase's status changes in BST10.

📘

In BST10: Phase status is read from the EffectiveStatus field on the Project Task record.

Default Mapping

For each BST10 status, select the Mosaic Phase status that should be applied. The change is applied when the status is updated in BST10.

How it works

• Each BST10 status is matched to a Mosaic status. The list of source statuses comes from your connected tool, so you'll need a tested connection before you can edit.
• Unmapped statuses sync as Active — if a status isn't listed, Mosaic sets the project or phase to Active.
• Click Reset to default at any time to restore Mosaic's recommended mapping for this integration.
• Changes apply on Save (the button reads Done when there are no changes). Updates affect future syncs; already-synced records keep their current status until they next change in BST10.

📘

For a full walkthrough of the mapping editor, see Project & Phase Status Matching.

3. Order

In Mosaic

This setting controls how Phases within a Project are ordered in Mosaic.

📘

In BST10: Phase hierarchy and ordering come from Project_Task.HierarchyCode and Project_Task.Code.

Setting Options

• Phase Code — Orders Phases by their BST10 task code.
• Set on Mosaic — Phase order is managed entirely within Mosaic.

1. Transfer Time Entries

In Mosaic

Controls whether posted Time Entries from BST10 are synced into Mosaic. Time Entries provide the actuals used in budget tracking, utilization, and project health metrics.

📝

In BST10: Time Entries are sourced from ProjectDetail rows in the Final schema, filtered to labor entries on active projects.

📘

Only posted time entries are synced — Mosaic reads from the BST10 Final schema, which contains posted data only. Unposted timesheets cannot be synced.

Setting Options

• Transfer — Posted Time Entries are synced from BST10.
• Do not transfer — Time Entries are not synced.

2. Billable Status

In Mosaic

Determines whether each Time Entry's billable flag is taken from BST10 or set by Mosaic rules.

📘

In BST10: Billable status comes from ProjectDetail.Billable.

Setting Options

• Transfer — Billable status syncs from BST10 per Time Entry.
• Do not transfer — Mosaic applies its own billable rules based on Project or Phase configuration.

3. Hourly Rate

In Mosaic

Determines the hourly rate stored on each Time Entry.

📘

In BST10: Hourly rate is calculated as ProjectDetail.EffortCC ÷ ProjectDetail.Quantity (returns 0 if hours are 0).

Setting Options

• Transfer — The calculated hourly rate is stored on each Time Entry.
• Do not transfer — Mosaic applies rate-based calculations using Project, Phase, and Member rate configuration.

1. Standard Bill Rates

In Mosaic

Controls whether organization-wide Member Bill Rates from BST10 Labor Bill Rate Schedules are transferred.

📝

In BST10: Standard Bill Rates come from LaborBillRateSchedule_RateType_Rate.RegularRateDC joined to each Member via LaborBillRateSchedule_RateType.

Setting Options

• Transfer — Standard Bill Rates sync from BST10.
• Do not transfer — Bill Rates must be managed manually in Mosaic.

2. Project-Level Member Rate Overrides

In Mosaic

Controls whether project-specific Member Bill Rate overrides from BST10 are transferred.

📝

In BST10: Project-level overrides come from Project_LaborTerm_LaborBillRateScheduleOverride and Project_LaborTerm_LaborBillRateScheduleOverride_Rate. They replace the standard rate for a specific Member on a specific Project.

Setting Options

• Transfer — Project-level rate overrides sync from BST10 and take precedence over the standard rate.
• Do not transfer — Project-level rate overrides are ignored; only the standard rate is used.