LogoLogo
  • GETTING STARTED
    • Violet Documentation
    • What is Violet?
    • Platform Overview
  • Integrations
    • Connect self-hosted software
  • FEATURES
    • Dashboards
      • Customization
      • FAQ
    • Data Explorer
      • FAQ
    • Automations
      • Jira to Smartsheet
        • Auto-update Jira data using formulas
      • Solidworks PDM to Fusion
      • Teamcenter to Datum
      • Teamcenter to ION
      • Teamcenter to Netsuite
      • FAQ
    • Reports
      • Multisource
        • Custom Columns
        • FAQ
      • Clear To Build
      • Build Velocity
    • Requirements
      • View: Table vs. Graph
      • Structure: Hierarchy vs. System
      • Systems
      • Import via CSV
      • Custom Fields
      • Verifications
      • Satisfaction
    • Parameters
    • Scripts
      • Creating and running scripts
      • Violet Variables
      • Live scripts
      • History and notifications
      • FAQ and Examples
    • SysML
    • Change Orders [Beta]
    • Schedules [Beta]
    • Workflows [Beta]
  • RESOURCES
    • Administrative
      • Invite your team
      • Permissions
      • Single Sign-On
      • On-Premises Deployment
        • Azure Deployment
        • AWS Deployment
        • Nutanix AHV Deployment
    • Security & Compliance
      • ITAR/EAR Compliance
      • SOC 2 Certification
      • NIST/CMMC Compliance
      • Data Retention, Backup and Recovery
      • Legal Stuff
    • Videos and Tutorials
    • FAQ
    • Pricing
  • APPS
    • A
      • Acumatica (Coming Soon)
      • AllSpice (Coming Soon)
      • Altium 365
        • Connect Altium 365 in Violet
      • Altium Designer
      • Aras
      • Arena
      • Asana
        • [Optional] Connect using a PAT
      • AutoPCB (Coming Soon)
    • B
      • Basecamp (Coming Soon)
      • Bild (Coming Soon)
      • BILL
        • [Advanced] Retrieve your Organization ID
        • [Optional] Import BILL data
      • Bitbucket
        • [Optional] Connect Bitbucket with API Token
      • Box
      • Brex
        • [Optional] Connect to Brex using an API Token
    • C
      • Cameo
      • Capella (Coming Soon)
      • ChatGPT (Coming Soon)
      • ClickUp
      • Cofactr
      • Confluence
      • Costpoint (Coming Soon)
      • Coupa (Coming Soon)
      • Creo (Coming Soon)
    • D
      • DOORS (Coming Soon)
      • Datum
      • Docusign (Coming Soon)
      • Dropbox (Coming Soon)
      • Duro
    • E
      • Enterprise Architect (Coming Soon)
      • Epicor (Coming Soon)
      • Epsilon3
    • F
      • Factor
      • FactoryLogix (Coming Soon)
      • Flow
      • Fleetio (Coming Soon)
      • Fulcrum
      • Fusion360 (Coming Soon)
      • Fusion
    • G
      • Gitea
      • GitHub
        • [Optional] Connect with an API Token
      • GitLab
        • Generate a GitLab API Token
        • Connect self-hosted GitLab
      • GENESYS
      • Google Drive
      • Google Sheets
    • I
      • Innoslate (Coming Soon)
      • InvenTree
      • ION
        • Connect ION in Violet
    • J
      • Jama
        • Connect self-hosted Jama
        • [Optional] Connect with Jama Client ID & Secret
      • Jira
        • Self-hosted Jira
        • [Optional] Connect via Jira API Token
      • Julia
      • JITX (Coming Soon)
    • K
      • Kiwi TCMS (Coming Soon)
    • L
      • LeoTrack (Coming Soon)
      • Linear
      • Lucidchart
      • Lucidscale
      • Lucidspark
      • Luminary Cloud (Coming Soon)
    • M
      • Manufacturo
      • Mathcad (Coming Soon)
      • MATLAB
      • Microsoft 365
      • Microsoft Teams (Coming Soon)
      • Microsoft Project (Coming Soon)
      • Monday.com
        • [Optional] Connect to Monday.com with an API Token
    • N
      • NetSuite
        • Configure NetSuite to connect
        • Connect NetSuite in Violet
        • Configuring NetSuite data syncs
      • Nuclino
      • Notion (Coming Soon)
      • NX (Coming Soon)
    • O
      • Octopart
        • Connect Octopart in Violet
      • Odoo (Coming Soon)
      • Onshape
      • Opcenter (Coming Soon)
      • OpenBOM
    • P
      • Parasoft (Coming Soon)
      • Pathfinder
      • Polarion (Coming Soon)
      • Precoro
      • Procurify
      • Puzzle
      • Python
    • Q
      • QuickBooks
    • R
      • Ramp
    • S
      • SAP ME (Coming Soon)
      • SAP S/4 HANA (Coming Soon)
      • SatCatalog
      • Sedaro
        • Using Violet data in Sedaro
      • SimScale
      • Simulink (Coming Soon)
      • Slack
      • Smartsheet
        • Smartsheet Gov
      • Solidworks PDM
      • Solumina (Coming Soon)
      • StartProto (Coming Soon)
      • Syndeia (Coming Soon)
      • SysML
      • Syteline (Coming Soon)
    • T
      • Teamcenter
        • Configure Teamcenter to connect
        • Connect Teamcenter in Violet
        • Set up Teamcenter integration
        • Data fetched from Teamcenter
        • Teamcenter FAQ
      • Teamcenter X (Coming Soon)
      • TestRail
      • Trello
      • Tulip (Coming Soon)
    • V
      • Valispace
      • Visure (Coming Soon)
      • VOLTA (Coming Soon)
    • W
      • Wasp (Coming Soon)
      • Wayfinder
      • Windchill
      • Wrike
    • X
      • Xero
      • Xray (Coming Soon)
  • Z
    • Zuken E3 (Coming Soon)
Powered by GitBook
On this page
  • Getting Started
  • Understanding the Report
  • How does it work?
  • FAQ

Was this helpful?

  1. FEATURES
  2. Reports

Clear To Build

Get a clear view of part availability to determine build readiness.

PreviousFAQNextBuild Velocity

Last updated 9 days ago

Was this helpful?

Clear To Build reports indicate whether the piece-parts that make up an assembly are available. This provides valuable insight into build readiness during production planning.

Getting Started

Access this feature from Reports in the navigation panel. Click + REPORT then select Clear To Build.

Begin by searching for a part by name or number in the input field. The dropdown will automatically suggest matching entities - click on the desired part to populate the report.

Note: this report is intended for assemblies - only parts with a BOM will be selectable.

Understanding the Report

The following information will be populated for each line in the assembly:

  • Procurement Type is the method of procurement defined for that part.

  • Qty Line is the quantity required for that line in the assembly.

  • Qty Available is the total quantity of that part available in inventory.

  • Qty Needed indicates any additional quantity needed for that line.

  • Last, the OK to Build? status indicates whether the line item is ready to build based on the inventory status of its sub-components.

Navigate through the report by expanding each sub-assembly to track its build readiness as well.

How does it work?

The OK to Build? status is determined according to the following logic:

  • For lines where Procurement Type is Buy:

    • OK to Build for that line, and for each of its child lines, will be N/A

  • For lines where Procurement Type is Make:

    • If Qty Needed for all child parts is 0, OK to Build will be Yes

    • If Qty Needed for any child part is greater than zero, and/or the Ok to Build for any child part is Unknown, OK to Build will be No

    • If there are no sub-components, OK to Build will be Unknown

  • For lines where Procurement Type is empty:

    • OK to Build will be Unknown

You can choose whether or not to treat part revisions as interchangeable by clicking on the three dots just above the top right corner of the report. If part revisions are interchangeable the report will reflect Qty Available values for all revisions of each part. If part revisions are not interchangeable, the report will reflect Qty Available values for only the most recent revision of each part. By default, part revisions are treated as not interchangeable.

Once you've developed a report for your assembly, you can save it for future reference.

Your report will automatically update with any changes to the BOM, the Procurement Type, or the inventory status of a part.

Reports can also be exported in .csv format for offline use.

FAQ

Where does Violet get the data for a Clear To Build Report?

Violet populates the assembly information as well as Name and Qty Line from the part you select. This will generally come from the PLM you've connected to Violet, such as Teamcenter, Duro, Solidworks PDM or Windchill.

The Qty Available and Procurement type are typically populated from the MES you've connected in Violet, for example ION, Fusion or Manufacturo. If those fields are empty, Violet will attempt to populate them based on data from your PLM.

The Name, Qty Line, Qty Available, and Procurement Type columns will display a logo based on the app used to populate the column.

Last, Violet calculates Qty Needed and the OK to Build based on the logic described above.

Example Clear To Build Report for our Magic Toaster