01
Whiteboard
A retro sci-fi portable whiteboard with a built-in kanban mode, for sketching and planning entirely in the browser.
Green Shoe Garage est. 2012
FI Field Instruments · Project Toolkit
Tools to help manage the work in a fun and beautiful way. Sketch, plan, and watch a build move from waiting to done, right in the browser. Source on GitHub under GPL-3.0.
01
A retro sci-fi portable whiteboard with a built-in kanban mode, for sketching and planning entirely in the browser.
02
Kanban plus can-do: a sticky-note project board for the maker who takes the work seriously but not solemnly. Lanes for what is waiting, what is in hand, and what is done, with cards you move across the bench as the build progresses. Light on its feet, no ceremony, just somewhere to see the whole project at a glance and keep it moving.
03
Seat inventory planning and supply-and-demand reconciliation: compare available seats against organization requests, generate seating options, and save planner scenarios.
04
A small inventory instrument for parts, tools, consumables, and materials. Track what is on hand, where it lives, what is low, and whether the shop can build the next kit.
05
A skeuomorphic card knowledge system: capture ideas on index cards, then stack, tag, link, and review them across board and relationship-map views. Autosaves, with JSON and Markdown export.
06
A whimsical engineering record that connects ideas, calculations, builds, tests, failures, repairs, revisions, and lessons learned.
07
A field-friendly process mapper. List steps, dependencies, roles, handoffs, delays, and failure points, and it generates a simple swimlane, checklist, or process table. Built for documenting how work actually happens before you try to automate or improve it.
08
A local-first investigation board for collecting notes, files, observations, links, quotes, and decisions around a question. Not a full project manager, more a structured notebook for what you know, what is uncertain, what supports it, and what to do next.
09
For a workshop, site visit, inspection, class, repair clinic, or field job, it manages what to bring, prepare, print, charge, confirm, and leave behind, with reusable templates and post-event notes.
10
A local-first decision memory system focused on rationale depth: choices, options, assumptions, criteria, tradeoffs, risks, dissent, follow-up, outcomes, and lessons learned.
11
Project-centered shop management for a small tradigital team. Plan the work, prove readiness, protect people, buy what is missing, and keep machines healthy.
12
Walks an engineer through the Analytic Hierarchy Process (AHP) station by station, producing a deliverable at every step. Named for the single-beam balance where a sliding counterweight weighs a load against a graduated arm, exactly what pairwise comparison does to a decision.
13
A practical engineering and project cockpit for turning loose ideas into buildable, testable, documented artifacts. A self-contained HTML, CSS, and JS app: no build step, package manager, server, or database required.
14
An interface manager for the boundaries between systems, people, teams, hardware, software, mechanical parts, electrical signals, documents, and responsibilities. It keeps an interface register across mechanical, electrical, data, and human interfaces, with an owner on each side, interface risk, compatibility checks, change history, and an exportable ICD report.
15
A costing and quoting bench: price and source a bill of materials, then build a job quote on top of it with shop rate, time, and margin.
16
A maintenance log for shop machines: track preventive maintenance intervals, log the work, and see what is due before the machine tells you the hard way.
17
An engineering ethics decision instrument. It helps engineers, teams, reviewers, and public-interest practitioners examine difficult technical decisions without reducing ethics to a single score, mapping stakeholders, benefits, burdens, consent, safety and environmental effects, privacy risks, reversibility, evidence, professional duties, alternatives, safeguards, dissent, monitoring, and decision history.
18
A local-first reverse-engineering notebook for understanding unfamiliar objects, machines, circuits, and spaces. It helps an investigator move from first contact with an artifact to a defensible reconstruction plan without letting observations, assumptions, and conclusions blur together.
19
A bidirectional Revit and CxAlloy equipment data translator. Spreadsheet in, spreadsheet out, reconciled at both ends. A manifest is the cargo list that travels with the shipment and gets checked at both ends, which is exactly the job here: equipment lists crossing between the design model and the commissioning record, reconciled before anyone imports anything.
20
A dragoman was an interpreter and guide, the person you hired at a border because you could not read the language on the other side of it. This one translates building automation point data between four dialects that describe the same buildings and refuse to describe them the same way: BACnet point lists, Niagara (delimited exports and station XML), Project Haystack (Zinc, Trio, and JSON), and Brick (read from Turtle, written as Turtle and JSON-LD). It carries meaning across the gap and tells you where the meaning got thin.
21
A CMMS to CMMS data translator that works entirely from exported files. Portage never connects to a CMMS: you export from the old system, carry the files across, and it hands you load files in the shape the new system wants, plus a reconciliation and exception record you can put in front of an owner, an auditor, or a vendor and defend line by line.
Nothing matches that. Try a shorter word.
Ready when you are
Concept to delivered product. Mechanical, electronics, and software, built under one roof. Quickly and within budget.
Schedule a consultation