Bedrock Estimating

Moves or reshapes markups, or changes the text of a note or callout. Only markups can be changed (rulers, highlights, notes, callouts and loose counts); what belongs to the job's takeoff is changed in Bedrock. Give points the same way add_markups takes them for that kind of markup. Get markup ids from list_measurements with show: markups. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

update_markups

Looks over a job's estimate for the mistakes that cost money: lines priced with no quantity or measured with no price, rates far from the cost database (a slipped decimal), a line's own 0% markup that strips overhead and profit, likely duplicates, takeoff quantities that never reached the estimate or no longer match it, sheets measured with no scale or at another scale than the one printed on them, lines in no bid item. Returns findings, worst first, each with the lines involved and what to do. Reads only; it changes nothing.

check_estimate

Compares the scales printed on a job's sheets (the title block, view titles, each detail's own scale) with the scales they are measured at, and lists where they disagree: a sheet set to another scale than its plan, measurements inside a detail drawn at its own scale with no scale box over it, a scale box set to another scale than its detail, measurements in a detail marked not to scale, and measurements on a sheet with no scale. Each finding says which measurements it affects, by how much, and where on the sheet (sheet coordinates). Checks every sheet with a scale or something measured on it, or just one sheet. Reads only: it never changes a scale, which would recalculate every measurement on the sheet.

check_scales

Draws again what one of this connection's drawings (draw_measurements) did not get onto the plans: a change that expired waiting for approval, was not applied, or was only partly drawn (get_change says which). It works the drawing out again on the job as it is now, snapped and measured afresh, and draws only what is not on the plans; nothing is ever drawn twice. A change a person rejected or undid is not drawn again. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

reapply_change

Draws on a plan sheet with the plan viewer's own annotation tools, so people see it on the sheet in Bedrock: a ruler (a measured line, labelled with its real length), a highlight (a tinted box), a note (text), a callout (a box around something with text beside it) or a count (a marker at each point, in count group 1 or 2). Points are sheet coordinates; get them from view_sheet with show_grid, zoomed in. Markups never change the takeoff or the estimate: they show a person what you found or measured. After adding, view_sheet with show_measurements shows the result. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

add_markups

Draws measurements on a plan sheet, the way a person draws them in the plan viewer: a length (a path of two or more points), an area (three or more corners, in order around it) or count markers (one at each point). Give points in sheet coordinates, from view_sheet with show_grid, zoomed in. Each point of a length or an area is moved onto the drawing's own lines and corners near it (a short way: about 0.4% of the sheet's size), so place them close; only solid lines count (dashed and dotted ones, such as grids, hidden walls and overhang lines, are passed over), a point with nothing near stays put, and the result says how each point moved. Values come from the sheet's scale, as in the plan viewer; a sheet with no scale is refused. What is drawn is a plain measurement, not yet part of a takeoff or the estimate: a person picks its assembly in the plan viewer. Use measure_on_sheet to measure without drawing. When a person has the job open, their screen draws them one by one, and they can press Stop; the result says which happened. Afterwards, check your drawing: view_sheet with show_measurements, zoomed in, and compare each corner with the drawing's solid lines. The result says how to put one right. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

draw_measurements

Looks up what the plans say in their notes, schedules and keynotes without reading whole sheets: numbered notes with their section (e.g. general note 7), keynotes by number, and schedules (footing, shear wall, door, window, finish, rebar, hold-down) read as tables. Filter by sheet, kind, a number (a note's number, or a mark like "F2" or "SW2" to get just that schedule row) or words. Each result gives the exact printed text, where it sits on its sheet (for view_sheet) and what it points to ("PER SW SCHED", "SEE NOTE 4" resolved to the schedule or note). Open a whole schedule with read_schedule.

find_plan_notes

One company from the CRM in full: its details and notes, its people, its open leads and bid invites, its open tasks, the jobs bid for it, and the latest calls, emails, meetings and notes logged against it.

get_crm_company

One job in full: its name, status, client, address, dates, scope notes and regional settings, and how much is on it (sheets, measurements, estimate lines, proposals).

get_job

A job's current budget by cost code (material, labor, equipment, subcontract, other) beside what has been spent against each code so far, from the costs recorded on the job. remaining is budget less spent.

get_job_budget

A job's contract and billing: the contract value with approved and pending change orders, the schedule of values, each pay application with its period and status, and the payments received.

get_job_billing

The estimate of one job: its totals, markups, bid items and lines, with each line's quantity, unit rates, cost and price. Totals are Bedrock's own, the same figures the Estimate tab shows. Pass lines: false for the totals alone, or bid_item_id to see one bid item's lines.

get_estimate

The proposal for a job: who it is addressed to, what it says (scope, inclusions, exclusions, schedule, terms), the versions that were issued with their totals, and each shared link with whether the client has opened it and how they answered. Prices in a proposal come from the job's estimate (get_estimate).

get_proposal

A job's schedule: each task with its start, how many working days it takes, how far along it is, the crew on it and the quantity it covers. Milestones are marked.

get_job_schedule

One sheet's details without its picture: number and title, the size of its coordinate grid, its scale (and any detail areas drawn at their own scale), how many measurements are on it and whether its text can be read.

get_sheet

One assembly in full: its inputs (what is measured, what is typed in, what is worked out from the others) with units and defaults, and each quantity it produces with the cost database items and crew that price it.

get_assembly

One change this connection proposed or made, in full: each thing it adds, alters or removes, what it does to the numbers, and what became of it.

get_change

What the field has logged as installed on a job: for each task, the quantity put in place so far and the crew hours it took, with the latest entries.

get_job_production

For one detail ("6/S4.2"): its exact text, the printed values found in it (dimensions, bar callouts and references, each with an id to cite and where it sits in sheet coordinates), the detail's own drawing scale when it can be worked out, the inputs of an assembly you name (or suggested assemblies), and any setup already made for it with what it gives per foot of run. Use it before propose_detail_setup. open_detail shows the picture.

get_detail_setup

The follow-ups and to-dos in the CRM: calls to make, emails to send, meetings, other tasks. By default the ones still to do, soonest due first.

list_tasks

A job's change orders: number, title, why it came up, where it stands (draft, pending, approved, rejected, void), the days it adds, and its cost, price and margin with the lines that make it up.

list_change_orders

The daily reports from the field for a job, newest first: the day, the weather, what was done, delays and their cause, and the hours each person worked.

list_field_reports

The plan sheets uploaded to a job, in plan order: sheet number, title, discipline, revision, whether a scale is set and how many measurements are drawn on each. Use the sheet id with view_sheet to look at one.

list_sheets

The purchase orders for a job: supplier, status, dates, and each line with what was ordered, at what price, and how much has been received. goods_total is the lines added up, before tax.

list_purchase_orders

What has been taken off a job's plans: each takeoff (an assembly placed on the plans, or a plain measurement) with what was measured, its other inputs and the quantities it produces. Quantities are Bedrock's own. An estimate line that comes from a takeoff carries its id as takeoff_id (get_estimate).

list_takeoff

The company's assemblies: the recipes that turn one thing measured on a plan (a length of footing, an area of slab, a count of piers) into every quantity it takes (concrete, rebar, forms, …). Each comes with what is measured and what it produces. get_assembly has one in full; calculate_assembly runs one.

list_assemblies

The company's field crews and the people in them, with each crew's foreman. These are the crews jobs are scheduled with.

list_crews

The company's jobs (bids and awarded work), most recently changed first. Search by name, code or client; filter by status. Each comes with its id, status, client, due date and stored total.

list_jobs

What the company prices labor and equipment with: its labor classes (hourly rate with burden), its equipment (hourly, daily, weekly and monthly rates) and its crews (who is in them and what an hour of the whole crew costs). Estimate lines priced by a crew use these rates.

list_resources

The leads and bid invites in the CRM: work the company has been asked to bid or has heard about, before there is a job for it. By default the open ones (new, bidding), soonest bid date first.

list_leads

Every numbered detail, section and elevation found on a job's sheets: its reference (e.g. "6/S4.2"), title, kind, drawing scale, how many places call it out and any problems (such as two details with the same number on one sheet). Details on sheets whose lettering is drawn as lines are read from the sheet's picture and marked so, with a confidence; sheets_without_readable_details says which sheets have not been read and why. Filter by sheet, kind or words in the title. Open one with open_detail.

list_details

The changes this connection has proposed or made, newest first, with what became of each: waiting for approval, applied, rejected, undone, expired, or not applied because the data had changed. Use it to find out whether something proposed earlier was approved.

list_changes

Everything drawn on a job's plans: the lines, areas and counts of its takeoffs, and the markups (rulers, highlights, notes, callouts, loose counts). Each comes with its value and unit, its sheet and, for a takeoff's measurement, the takeoff it belongs to. with_points adds where each one is, in sheet coordinates. To see them on the plan, use view_sheet with show_measurements.

list_measurements

Records something that happened with a CRM company: a call, an email, a meeting or a note, with who it was with and when. It appears on the company's timeline in Bedrock. This only records it; it does not send or schedule anything. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

log_activity

Returns a picture of a plan sheet. With no region it shows the whole sheet, which is right for finding your way around but too small to read dimensions. To read text or dimensions, call it again with a region (in sheet coordinates) around the part you want: the picture is then cut from the sharpest image there is. show_grid prints sheet coordinates along the edges, which is the easy way to work out a region or where to place a measurement. show_measurements draws the job's existing measurements, tagged M1, M2, … and listed in the result.

view_sheet

Works out real lengths and areas from points on a sheet, using the sheet's scale exactly as Bedrock's plan viewer does (a detail drawn at its own scale is measured at that scale). Nothing is drawn or saved. Give each shape as a length (a path of two or more points) or an area (three or more corners, in order); an area also comes back with its perimeter. Find the points with view_sheet and show_grid, zoomed in enough to place them well: the answer is only as good as the points.

measure_on_sheet

Opens one detail by its reference ("6/S4.2": detail 6 on sheet S4.2) or its id from list_details: a picture of just that detail, cut from the sheet's sharpest image, the exact text printed inside it, its title, kind and drawing scale, every place on the plans that calls it out, the other details it points to, and the schedules and notes its text names ("PER SW SCHED" with the row it means, where that can be told). If a sheet uses the number twice, it lists both to choose from.

open_detail

Stores your reading of one detail as an assembly and its input values, as a proposal a person confirms in the plan viewer before anything is priced. Every value says where it came from: printed (cite the candidate id from get_detail_setup; the number read from the text is kept), measured (two points in sheet coordinates; the length is worked out at the detail's calibration, so give calibration: a printed dimension candidate and the ends of its dimension line), referenced (where it comes from, e.g. "5/S4.1"; kept to be looked up), or worked_out (the value and how). Values that cannot be checked are refused or kept as unverified, and the result says which. Replaces an earlier proposal for the same detail and assembly; a setup a person confirmed is changed only by a person, in the plan viewer. The result says whether it was saved (applied: true) or is waiting for a person to approve it.

propose_detail_setup

Reads one schedule from a job's plans as a table, exactly as printed: its columns (stacked headings joined), every row keyed by its mark (F1, SW2, D3) with where the row sits on the sheet (for view_sheet), the notes printed under it, and the places on the plans that refer to it. Name it by its id from find_plan_notes, by the detail it is drawn as ("5/S4.1"), or by words of its title ("footing", "shear wall"). Give a row to get just that mark.

read_schedule

The text read off a sheet: notes, schedules, dimensions and labels as words. Faster and more exact than reading a picture when the sheet has a text layer. Give a region to get only the text inside it, with where each piece sits (in sheet coordinates). A scanned sheet may have no text; look at it with view_sheet instead.

read_sheet_text