Industry solution

Defense Industry & Sustainment

Keep the fleet ready: parts found, repairs on time, people current, records controlled

Readiness boards, depot turnaround, parts holds, technician rosters, deliverables and release reviews, designed to work as one.

Products
8
Challenges
6
Concepts
15
Talk to us about Defense & SustainmentAsk a question
Technicians inspecting a truck transmission in a depot repair hall beside shelves of tagged components and a status screen
AssetHandler(opens AssetHandler in a new tab)ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)CrewFoundry(opens CrewFoundry in a new tab)ProServiceWorld(opens ProServiceWorld in a new tab)IntelWatchtower(opens IntelWatchtower in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

Why sustainment is hard to run from spreadsheets and inboxes

Equipment status sits in site spreadsheets, parts on carrier portals, repairs on depot whiteboards, qualifications in personnel files and deliverables in email, while a controlled drawing is one forward away from the wrong recipient.

Sustainment keeps fielded equipment ready long after it is delivered. Parts are requisitioned, unserviceable units come back from the field, the depot overhauls them against turnaround commitments, and repaired units refill an exchange pool for the next removal. Under performance-based contracts the contractor answers for readiness and turnaround, not only for hours worked, so a part sitting in the wrong warehouse or a unit that is never shipped back shows up directly in the customer's numbers.

The information that would prevent it is scattered. Equipment status lives in the customer's systems and site spreadsheets, shipments on carrier portals, repair status on depot whiteboards, qualifications in personnel files, access status with the security office, contract deliverables in email, and markings on documents anyone can forward. Parts go obsolete, suppliers change, experienced technicians retire, and export-control and controlled-information rules leave little room for error.

The customer's supply and maintenance systems of record and the approved technical data are not the problem, and this concept does not replace them. It is designed to sit around them, so the parts, repairs, people, deliverables and releases that keep equipment ready are visible to the people who answer for them. It covers administrative and sustainment work only.

Who this is for

  • Program sustainment manager

    Readiness at or above the contract goal, get-well dates the customer believes, and one set of facts for the morning call and the monthly review.

  • Depot manager or production controller

    Repairs inside the turnaround commitment, a stated reason for every unit that is waiting, and unserviceable returns arriving on time.

  • Quality manager

    Suspect parts quarantined and traced to exact serial numbers quickly, supplier findings closed with evidence, and holds released only on sign-off.

  • Facility security officer

    Access status kept by the security office, visit requests sent on time, and supervisors who see only what they need to staff a job.

  • Contracts and data manager

    Every contract data item delivered on time, customer comments never lost, and figures that match from one report to the next.

  • Trade compliance officer

    No controlled drawing or report leaving without a review for its recipient, and a record of every release that was made.

A day in the life

The story behind the solution

One Tuesday at Kestrel Ridge Sustainment, from the readiness call to the last email out

Mariana runs a performance-based sustainment contract. Her company keeps a customer's 212 heavy transport trucks and 90 mobile generators ready at three sites, overhauls their transmissions, alternators and starters at its own depot, builds new alternators for the customer's spares orders, and delivers a set of reports to the customer every month. Most days she learns about problems late: on the readiness call, from the customer, or from someone who happened to be copied on an email. This illustrative story follows one of those Tuesdays.

  1. 06:40 · Readiness call

    Six trucks waiting on parts, one part lost

    The customer's morning call starts with Site North: 9 of 78 trucks are not mission capable, 6 of them waiting on parts. Truck TR-2217 has waited 16 days for a starter motor whose requisition shows it shipped nine days ago. The depot stockroom thinks it went to Site South. A field lead proposes taking the starter from TR-2231, which is already down for maintenance. The program office wants a get-well date for every down truck by noon, and Mariana's team starts making phone calls.

    How this is solved: Trucks down for parts, and nobody can say when they are back

  2. 09:20 · Depot floor

    Day 34 of a 30-day promise

    The program office asks about transmission TX-40718, inducted at the depot 34 days ago against a 30-day turnaround. The whiteboard says it is in work. Depot supervisor Joaquín Ferreira walks the floor and finds it finished teardown twelve days ago and has waited since for a bearing set. Meanwhile two unserviceable transmissions removed at Site East in September still sit on a pallet there, so the exchange pool is two units short and the next removal will have no spare.

    How this is solved: Depot repairs that stall and unserviceable units that never return

  3. 11:05 · Receiving

    A certificate that leads nowhere

    At receiving inspection, quality manager Tobias Lindgren opens a box of 60 voltage regulators from a newly approved distributor. The certificate of conformance does not trace back to the original manufacturer, and the date codes look re-marked. He quarantines the box, then remembers that the same distributor delivered 40 regulators in August. Twenty-four went into overhauled alternators: some on the shelf, some on the road, some already fitted to trucks. Eight more went into new alternators built for a spares order. The build records are paper travelers.

    How this is solved: A suspect parts lot already inside overhauled and new units

  4. 13:30 · Site request

    Two technicians for a gate they may not pass

    Site South asks for two technicians on Monday to change an engine inside a restricted maintenance area. The site needs a visit request three working days ahead, current hazardous materials training and a qualified technician to sign off the engine run-up and operational check. Joaquín's first choice let her hazardous materials refresher lapse in August. His second is marked pending in the facility security officer's weekly spreadsheet. The visit request is due tomorrow.

    How this is solved: Technicians who are not current for the site or the task

  5. 15:45 · Contracts office

    Friday's report, last quarter's comments

    Data manager Rahul Menon starts the monthly status report, one of 14 data items on the contract, due Friday. Its readiness, turnaround and backorder figures sit in four spreadsheets that disagree. Last quarter's reliability report came back rejected with comments, and the comments sit in the inbox of an engineer on leave. The customer's contracting officer's representative emails to ask when the corrected report will arrive.

    How this is solved: Contract deliverables assembled by hand, comments lost in email

  6. 17:20 · Outbox

    One email away from an unauthorized release

    An engineer prepares to send a failure analysis report and two transmission drawings to a newly qualified overseas subcontractor that repairs gearboxes. The drawings carry an export-control marking. The authorization covering that subcontractor includes gearbox repair data, not transmission drawings, and two paragraphs of the report quote fleet usage figures the customer marked as controlled unclassified information. Trade compliance officer Keiko Adeyemi stops it only because she was copied.

    How this is solved: Controlled technical data one email away from the wrong recipient

In the concept, each of those moments arrives earlier and in one place: the lost starter shows on the readiness board, the waiting transmission has a clock and a reason, the suspect batch becomes a list of serial numbers, the roster shows who can pass the gate, the report draws on one set of figures with last quarter's comments attached, and the drawings stop at a release review. Mariana still makes the calls, with the facts in front of her.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Trucks down for parts, and nobody can say when they are back

AssetHandler(opens AssetHandler in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

Site North's supply lead joins the readiness call with 9 of its 78 heavy trucks not mission capable and 6 of them waiting on parts. A starter motor requisitioned for TR-2217, down for 16 days, shows as shipped nine days ago. The depot stockroom believes it went to Site South, but the carrier's tracking says it was delivered to the Site North warehouse, where nobody has looked. A field lead wants to pull the starter from TR-2231, which is already down for maintenance. By noon the program office expects a get-well date for every down truck, and the answers are spread across a supply system screen, three spreadsheets and a round of phone calls.

What it costs

Readiness sits below the contract goal while parts sit on a shelf, cannibalization doubles the maintenance work and hides the real shortage, and get-well dates become guesses the customer stops trusting.

How the products work together

When a truck is waiting on a part, AssetHandler is designed to show it on one readiness board with the part it needs. MoveTheWheels follows that part's shipment, and FluidGrids brings its delivery status back to the board, so each down truck has a realistic back-in-service date and a stalled or misdelivered part is noticed in days, not weeks.

How it works — technical detail

Technical detail

AssetHandler is designed to hold every truck and generator as an end item with its readiness status (mission capable, down for maintenance, down for supply), its open work orders and the requisitions each work order waits on. MoveTheWheels is designed to track each inbound parts shipment against its requisition, from supplier or depot stockroom to the site warehouse, and to raise an exception when a shipment stalls, lands at the wrong location or passes its expected date. A FluidGrids workflow is designed to match those shipment updates to the requisition on the AssetHandler work order, so the readiness board shows a get-well date backed by a tracked shipment. A proposed cannibalization is designed to be recorded as a controlled exchange that links the donor and receiving work orders and waits for the site lead's approval; approval workflows are on AssetHandler's roadmap.

The outcome it is designed for

Site leads and the program office are designed to see each down truck with a tracked part and a get-well date, and stalled parts shipments surface before the readiness call.

The concepts behind it

Challenge 2 of 6

Depot repairs that stall and unserviceable units that never return

ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)AssetHandler(opens AssetHandler in a new tab)

The problem

Depot supervisor Joaquín Ferreira takes a call from the program office about transmission TX-40718: inducted 34 days ago against a 30-day turnaround commitment, and marked in work on the depot whiteboard. On the floor he finds that it cleared teardown and evaluation twelve days ago and has sat since for a bearing set. A crack found on a second transmission is waiting for an engineering disposition in someone's inbox. Out at Site East, two unserviceable transmissions removed in September have never been picked up, which leaves the exchange pool the contract counts on two units short.

What it costs

Turnaround commitments slip without warning, the exchange pool shrinks until the next removal has no spare, and the program office learns about late repairs from its own down trucks.

How the products work together

The field repair job in AssetHandler is designed to start the broken unit's trip back, which MoveTheWheels follows to the depot door and chases when it is late. ManufacturedOps then shows each unit's repair stage, the days left on the turnaround promise and exactly why anything is waiting, so late repairs and missing returns are chased while there is still time.

How it works — technical detail

Technical detail

When a field technician removes an unserviceable reparable, the AssetHandler work order records its serial number, the removal reason and the replacement fitted from the exchange pool. That record is designed to open a retrograde shipment in MoveTheWheels, which tracks the unit from site packing through pickup and transit to the depot dock against a return-due date and flags returns that are overdue or never picked up; dedicated returns management is on MoveTheWheels's roadmap. The depot receipt is designed to open a repair order for that serial in ManufacturedOps, which moves it through teardown and evaluation, awaiting parts, repair, test and quality release on a turnaround clock, with the reason for every wait. A finding beyond repair limits raises a non-conformance for engineering disposition on the same order, and awaiting-parts time is designed to show against the part's inbound shipment in MoveTheWheels.

The outcome it is designed for

The depot and the program office are designed to see each serial's stage, days left and reason for waiting, and every overdue unserviceable return by site.

The concepts behind it

MoveTheWheels

Reparable Retrograde and Carcass Return Tracker

Every unserviceable unit removed in the field, followed from site to depot dock against its return-due date, with overdue returns and the exchange pool shown by item.

Works with AssetHandler, ManufacturedOps

Concept pagefor Reparable Retrograde and Carcass Return Tracker on the MoveTheWheels website (opens in a new tab)

Challenge 3 of 6

A suspect parts lot already inside overhauled and new units

ManufacturedOps(opens ManufacturedOps in a new tab)FluidGrids(opens FluidGrids in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)AssetHandler(opens AssetHandler in a new tab)

The problem

Receiving inspection flags a box of 60 voltage regulators from a newly approved distributor: the certificate of conformance stops at the distributor instead of tracing to the original manufacturer, and the date codes show signs of re-marking. Quality manager Tobias Lindgren quarantines the box and pulls the distributor's history. It delivered 40 regulators in August. Twenty-four went into overhauled alternators now spread across the depot shelf, a truck bound for Site South and vehicles at two sites; eight went into new alternators built for a spares order; the last eight are still in the stockroom. The build records are paper travelers, and site installation records live in another system.

What it costs

Suspect parts may be running in fielded equipment while quality reads paper, the customer expects a prompt and precise notice, and a hold drawn too wide takes serviceable equipment out of use.

How the products work together

Quality is designed to check the batch back to its source, mark it suspect in ManufacturedOps and see every overhauled or new alternator it went into. FluidGrids is designed to pass that list on: MoveTheWheels stops those units on shelves and on the road, and AssetHandler shows which vehicle each fitted unit is on. Suspect parts stay out of stock, and the customer gets an exact list.

How it works — technical detail

Technical detail

ManufacturedOps is designed to receive incoming parts as material lots with supplier and status (certificate records are on its roadmap), so quality can check a lot back to an authorized source, quarantine a suspect lot and trace forward through the repair and production orders that consumed it to every overhauled or new alternator it went into; full lot genealogy is still being built. A FluidGrids workflow is designed to route that serial list to MoveTheWheels, which blocks picking in stockrooms and warehouses and flags in-transit loads for intercept, and to AssetHandler, whose custody records show where each serial is and whose asset hierarchy is designed to record the truck or generator it is fitted on. Findings stay on the non-conformance in ManufacturedOps until the lot is authenticated and released, or confirmed counterfeit and kept out of the supply chain rather than returned to the distributor, with the customer sent a serial-level notice.

The outcome it is designed for

Quality is designed to scope a suspect lot to exact serial numbers in one sitting, hold only those units, keep suspect parts out of the supply chain and give the customer a serial-level notice.

The concepts behind it

Challenge 4 of 6

Technicians who are not current for the site or the task

CrewFoundry(opens CrewFoundry in a new tab)AssetHandler(opens AssetHandler in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

Joaquín has until tomorrow to name two technicians for a Monday engine change inside Site South's restricted maintenance area. The site's rules call for a visit request from the security office three working days ahead, current hazardous materials handling training and a qualified technician to sign off the engine run-up and operational check. Working through it by hand, he finds that his first choice's hazardous materials refresher lapsed in August and that his second shows as pending in the facility security officer's weekly spreadsheet. Training sits in an older learning system, qualifications in personnel files and access status with the security office.

What it costs

Visits are turned back at the gate, jobs slip a week, and a technician signing work outside their qualification becomes a finding in the customer's next audit.

How the products work together

CrewFoundry is designed to keep each technician's qualifications, training dates and site access status on one profile, with access status and visit requests handled by the security office. Rosters that offer only people current for everything a job from AssetHandler needs are on its roadmap. FluidGrids sends reminders before training lapses or a visit request falls due, so nobody is turned back at the gate.

How it works — technical detail

Technical detail

Site jobs are designed to arrive from AssetHandler work orders carrying their requirements: craft qualification, sign-off authority, recurring training and the site's access conditions, with the visit request lead time. CrewFoundry is designed to hold each technician's qualifications and training as dated entries on one profile, with access status entered and owned by the facility security officer through role-based access, so supervisors see only whether a person can be requested; the security office sends each visit request against its deadline. Learning paths carry recurring training such as hazardous materials refreshers. The planned roster offers only technicians current for every requirement, and the approved roster is designed to go back to the job; site rosters are on CrewFoundry's roadmap. A FluidGrids workflow on a daily schedule trigger is designed to read upcoming expiries and visit request deadlines and remind the technician, supervisor and security office in time.

The outcome it is designed for

Supervisors are designed to staff site jobs only with people current for the task and the site, with visit requests sent by the security office on time and lapses surfaced days ahead.

The concepts behind it

CrewFoundry

Sustainment Technician Access and Qualification Roster

A site job's requirements against each candidate technician: qualifications, training currency, access status set by the security office and the visit request deadline, with gaps shown first.

Works with AssetHandler, FluidGrids

Concept pagefor Sustainment Technician Access and Qualification Roster on the CrewFoundry website (opens in a new tab)

Challenge 5 of 6

Contract deliverables assembled by hand, comments lost in email

ProServiceWorld(opens ProServiceWorld in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

Rahul Menon, the data manager, is rebuilding the list of what is due from the contract itself, because nothing else holds it. The monthly status report, one of 14 items on the contract's data requirements list, is due Friday, and the readiness, turnaround and backorder figures he needs disagree across four spreadsheets. The customer rejected last quarter's reliability report with comments that are stuck in the inbox of an engineer on leave, and the contracting officer's representative is now asking when the corrected version will arrive. Test reports the gearbox subcontractor owes under the contract's flowdown are not tracked anywhere.

What it costs

Late or rejected deliverables are visible to the customer and can hold up acceptance and payment, figures that disagree between reports erode trust, and every month costs days of rework.

How the products work together

ProServiceWorld is designed to list every report the contract requires, including those owed by suppliers, with its due date, owner, version and the customer's verdict and comments, so a rejected report comes back with its fixes in one place. FluidGrids gathers the month's figures into BigConsole, which shows one agreed set of numbers for the author to check. Customer review steps and notes on what changed are still on roadmaps.

How it works — technical detail

Technical detail

ProServiceWorld is designed to hold the contract as an engagement and each data item as a deliverable with its item number, frequency, due date, owner, version and distribution marking; data owed by subcontractors under flowdown is tracked the same way. Review and acceptance cycles are on its roadmap: the customer's outcome and comments are designed to attach to the item, and a rejected item reopens with a resubmission date. For the figures, FluidGrids workflows are designed to collect readiness from AssetHandler, repair turnaround from ManufacturedOps and shipment status from MoveTheWheels on a schedule and write them into BigConsole datasinks. BigConsole is designed to keep one set of month figures, and its planned Explain panel is designed to give short findings on what changed, each cited to the sink and field behind it, for the author to check before quoting.

The outcome it is designed for

The data manager is designed to see every deliverable's status and open comments in one register, with month figures drawn from one source and cited.

The concepts behind it

ProServiceWorld

Defense Contract Data Deliverables Register

Every contract data item and supplier data item with its due date, owner, version, marking and the customer's review outcome, with rejected items reopened and their comments attached.

Works with BigConsole, FluidGrids, IntelWatchtower

Concept pagefor Defense Contract Data Deliverables Register on the ProServiceWorld website (opens in a new tab)

Challenge 6 of 6

Controlled technical data one email away from the wrong recipient

ProServiceWorld(opens ProServiceWorld in a new tab)IntelWatchtower(opens IntelWatchtower in a new tab)

The problem

Trade compliance officer Keiko Adeyemi is copied, by chance, on an engineer's email to a newly qualified overseas subcontractor that repairs gearboxes. Attached are a failure analysis report and two transmission drawings. The drawings carry an export-control marking, and the subcontractor's export authorization covers gearbox repair data, not transmission drawings. Two paragraphs of the report quote fleet usage figures that the customer marked as controlled unclassified information. She stops the email in time, but only because she happened to see it.

What it costs

An unauthorized release of export-controlled data or controlled unclassified information can mean disclosures to regulators, penalties and lost customer trust, and today the control depends on someone noticing.

How the products work together

Marked drawings and reports are kept in ProServiceWorld with their versions. Anything going to a supplier or partner is designed to pass through a review in IntelWatchtower: first against what that recipient is authorized to receive, then paragraph by paragraph, with a named reviewer approving the copy. What was sent, to whom and by whom is recorded. Much of this is still on the products' roadmaps.

How it works — technical detail

Technical detail

ProServiceWorld holds engineering and program documents with classification, version and download tracking. Legal hold, each subcontractor's export authorization as a dated compliance check with its scope and expiry, and secure document rooms are on its roadmap. A document bound for a supplier or partner is designed to go first to a release review in IntelWatchtower. The package is checked against the scope of the recipient's authorization before any paragraph review, so a drawing outside it is withheld in full; report paragraphs are then cleared, withheld or summarized for that recipient, and a named reviewer approves the version. IntelWatchtower keeps a disclosure log of what was released, to whom, in which version and by whom, and the approved version is designed to go to the recipient's ProServiceWorld document room. Releasability controls are on IntelWatchtower's roadmap.

The outcome it is designed for

Trade compliance is designed to see every outgoing controlled document checked against the recipient's authorization and reviewed before it leaves, with a disclosure record for each release.

The concepts behind it

IntelWatchtower

Export-Controlled Technical Data Release Review

A release review per recipient that checks the package against the recipient's export authorization, withholds drawings outside it, clears or withholds report paragraphs and logs every disclosure.

Works with ProServiceWorld

Concept pagefor Export-Controlled Technical Data Release Review on the IntelWatchtower website (opens in a new tab)

How it fits together

How one failed part moves through the products, from field removal to released report

One unserviceable alternator, followed from the field job that takes it off a truck to its failure analysis report, which goes to the customer and, after a release review, to a subcontractor. Each step shows one product doing one job and what it is designed to hand on to the next.

  1. To AssetHandler: Who is cleared to do the field job

  2. To MoveTheWheels: The part on order and the broken unit to send back

  3. To ManufacturedOps: The broken unit's arrival at the depot and why it was removed

  4. To FluidGrids: The unit's repair progress and the parts batches used

  5. To BigConsole: The month's readiness, repair and shipment figures

  6. To ProServiceWorld: Checked figures for the monthly report

  7. To IntelWatchtower: The failure report, to be cleared before it goes outside

Step 1 of 8: Staff the field job

How each hand-off works — technical detail

Technical detail

  1. 1. CrewFoundry — Staff the field job: Is designed to staff the alternator change raised on the truck's AssetHandler work order with a technician current for the task and site; site rosters are on its roadmap.Hands to AssetHandler: The approved technician for the job, designed to go back to the field work order.
  2. 2. AssetHandler — Record the removal: Marks the truck down for supply on the readiness board, records the removed alternator's serial on the field work order, and links the requisition for its replacement.Hands to MoveTheWheels: The requisition and the removed serial, designed to open an inbound parts shipment and a retrograde return.
  3. 3. MoveTheWheels — Move parts both ways: Is designed to track the replacement to the site warehouse and the unserviceable alternator back to the depot, flagging stalled, misdelivered or overdue shipments.Hands to ManufacturedOps: The depot receipt of the unserviceable serial, with its removal reason and field work order, designed to open the repair order.
  4. 4. ManufacturedOps — Repair, test and trace: Opens a repair order for the alternator's serial, runs it through teardown, repair, test and quality release on a turnaround clock, and records the parts lots it consumes.Hands to FluidGrids: The alternator's repair stages, turnaround and consumed lots, designed to be picked up by FluidGrids.
  5. 5. FluidGrids — Collect the figures: Is designed to write the alternator's repair status, with readiness and shipment status, into BigConsole datasinks, and to route a serial list if one of its lots turns suspect.Hands to BigConsole: Keyed datasink rows for readiness by site, turnaround by item and shipments by status.
  6. 6. BigConsole — Review the program: Is designed to show one sustainment console for the morning call and the monthly review, with a planned Explain panel whose findings cite the fields behind them.Hands to ProServiceWorld: Month figures, including the alternator's turnaround, that the author checks and quotes in the monthly status report.
  7. 7. ProServiceWorld — Deliver the data items: Is designed to track the monthly status report and the alternator's failure analysis report (data item A006) with due date, owner, version and marking; review cycles are planned.Hands to IntelWatchtower: The A006 failure analysis report, bound for a subcontractor, designed to go to release review before it leaves.
  8. 8. IntelWatchtower — Release under control: Is designed to check the report against the recipient's authorization, review it paragraph by paragraph, record a named approval and log the disclosure; this is on its roadmap.Hands to ProServiceWorld: The approved recipient version, designed to be placed in that recipient's ProServiceWorld document room.

Products in this solution

What each product brings

  • AssetHandler

    Readiness board, field work orders and serialized custody

    It is designed to keep one record for every truck, generator and tracked component: whether it is ready, what work is open on it, who holds it and which vehicle it is fitted to.

    Technical detail

    Technical detail

    AssetHandler's registry, work orders, custody trail and tagging are designed to give each truck, generator and serialized reparable one record, from its readiness status to the vehicle a repaired unit is fitted on.

    Visit AssetHandlerAll concepts

  • ManufacturedOps

    Depot repair orders, quality holds and lot traceability

    It is designed to run the depot: each unit's repair from arrival to release, the batches of parts that went into it and any problem found along the way, so a suspect batch can be traced in one sitting.

    Technical detail

    Technical detail

    ManufacturedOps's production orders, routings, material lots and non-conformance workflow map onto depot repair and new builds: an order per serial, stages on a turnaround clock, lots consumed and findings sent for disposition. Lot genealogy is still being built.

    Visit ManufacturedOpsAll concepts

  • MoveTheWheels

    Parts shipments, retrograde returns and stock holds

    It is designed to follow parts on their way to the sites and broken units on their way back, warn when something is late or in the wrong place, and stop suspect stock from being shipped.

    Technical detail

    Technical detail

    MoveTheWheels tracks shipments, warehouses and inventory with exception alerts, and is designed to cover inbound parts to sites, holds on suspect stock and unserviceable units returning to the depot; returns management is on its roadmap.

    Visit MoveTheWheelsAll concepts

  • CrewFoundry

    Technician qualifications, training and site rosters

    It is designed to keep each technician's qualifications, training dates and site access status in one place. Rosters that offer only people who meet every requirement of a job are still on its roadmap.

    Technical detail

    Technical detail

    CrewFoundry's worker profiles, skills, learning paths and certificates carry each technician's qualifications and training currency; site rosters that offer only people current for a job's requirements and access conditions are on CrewFoundry's roadmap.

    Visit CrewFoundryAll concepts

  • ProServiceWorld

    Contract deliverables and marked document records

    It is designed to list every report the contract requires with its owner and due date, and to keep marked drawings and reports with their versions and a record of who downloaded them. Customer review steps are still on its roadmap.

    Technical detail

    Technical detail

    ProServiceWorld's engagements carry milestones and deliverables, and its documents carry classification, versions and download tracking. Review and acceptance cycles, legal hold, compliance checks and document rooms are on its roadmap; together they fit data items and marked records.

    Visit ProServiceWorldAll concepts

  • IntelWatchtower

    Release review and disclosure log for controlled documents

    It is designed to check each part of a controlled document against the person or company receiving it, record who approved the release and keep a list of everything sent out; this is still on its roadmap.

    Technical detail

    Technical detail

    IntelWatchtower moves reports through draft, review, release and recall with every step recorded, and its releasability controls, on its roadmap, are designed to review a document per recipient and per paragraph and keep a log of every disclosure.

    Visit IntelWatchtowerAll concepts

  • FluidGrids

    Reminders, status matching and figures between products

    It passes information between the products: it matches deliveries to the parts on order, sends urgent lists to the right teams, sends reminders on time and gathers the month's figures.

    Technical detail

    Technical detail

    FluidGrids workflows with schedule and webhook triggers are designed to match shipment status to requisitions, route suspect-lot serial lists, send expiry reminders and write figures into BigConsole datasinks.

    Visit FluidGridsAll concepts

  • BigConsole

    Sustainment console and cited monthly figures

    It is designed to show one agreed set of readiness, repair and shipment figures for the morning call and the monthly report. Short notes on what changed and where each number came from are still on its roadmap.

    Technical detail

    Technical detail

    BigConsole turns FluidGrids datasinks into one live console for the morning call and the monthly review, and its Explain panel, on BigConsole's roadmap, is designed to give short findings cited to the sink and field behind each one.

    Visit BigConsoleAll concepts

One platform underneath: Burdenoff Workspaces

Burdenoff Workspaces is the shared foundation: one sign-on for depot, field, quality, security and contracts staff, role-based access per product and workspace, one audit trail across every work order, hold, roster, deliverable and release, and one bill.

Concept gallery

Every concept in this solution

15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Defense & Sustainment solution in one minute

Sustainment programs lose readiness in the gaps between systems: a part nobody is tracking, a repair nobody is timing, a batch nobody can trace, a technician nobody checked. Burdenoff is designing eight products to connect on one workspace: AssetHandler and MoveTheWheels for readiness and parts, ManufacturedOps for depot repair and quality, CrewFoundry for qualified people, ProServiceWorld and IntelWatchtower for deliverables and release, and FluidGrids with BigConsole for the figures.

  • Designed so each down truck or generator shows the part it waits on, the tracked shipment and a get-well date the customer can trust
  • Designed so every inducted serial has a repair stage, a turnaround clock and a stated reason for waiting, and every unserviceable return is tracked
  • Designed so a suspect parts lot is traced to exact serial numbers and held on shelves, on the road and on the vehicles they are fitted to
  • Designed so site jobs are staffed only with technicians current for the task, the training and the site's access rules
  • Designed so every contract data item and controlled document is tracked, reviewed for its recipient and recorded when released
Email it

Questions

Frequently asked

Is this a live, deployed solution?

No. This page describes how these products are designed to work together for defense depots and sustainment teams. The products are pre-launch, with waitlists open. Several features shown here, such as site rosters, release reviews and notes on what changed, are still on roadmaps, and most handoffs are designed, not built. We are happy to show what exists now.

Technical detail

Technical detail

No. This page describes a solution concept: how these Burdenoff products are designed to work together for defense manufacturers, depots and sustainment contractors. The products are pre-launch, with waitlists open. Some capabilities shown here are on product roadmaps, such as IntelWatchtower's releasability controls, CrewFoundry's site rosters, BigConsole's Explain panel, ProServiceWorld's deliverable review cycles, legal hold, compliance checks and document rooms, MoveTheWheels returns management and ManufacturedOps's full lot genealogy, and most hand-offs between products are designed rather than built-in integrations today. We are happy to walk through what exists now.

Can it hold classified information, and does it meet rules for controlled unclassified information or export-controlled data?

No. The concept covers everyday sustainment records, not classified information, which stays in the approved systems your security office already runs. The products control who sees what and record who did what, but they hold no security certifications today, and this page does not claim they meet rules for controlled information. Your security and trade compliance teams decide that.

Technical detail

Technical detail

No. The concept covers administrative and sustainment records, not classified information, which stays in the accredited systems your security office already runs. Every product applies role-based access and keeps an audit trail, and enterprise plans are designed to include dedicated tenancy. The products hold no security certifications, accreditations or assessments today, and this page does not claim that any deployment meets rules for controlled unclassified information or export-controlled data; that is for your security team, trade compliance officer and assessors to decide.

Does this replace the customer's supply and maintenance systems or our ERP?

No. The customer's own supply and maintenance systems, your business systems and the approved technical manuals remain the official record. These products sit alongside them, bringing in updates where they can and tying parts, repairs and people together for your teams.

Technical detail

Technical detail

No. The customer's supply and maintenance systems of record, your ERP and the approved technical data stay authoritative. The concept is designed to sit around them: FluidGrids workflows can bring requisition, shipment and status updates in where a connection is available, and AssetHandler, ManufacturedOps and MoveTheWheels hold the working picture that ties parts, repairs and people together for your teams.

Does CrewFoundry store security clearance or investigation details?

No. CrewFoundry would hold only a simple status and its dates, entered by your security officer, so a supervisor knows whether someone can be sent to a site. Investigation records and decisions stay with the government's systems and your security office.

Technical detail

Technical detail

No. In the concept, CrewFoundry holds only an access status and its dates, entered by the facility security officer, so a supervisor can see whether a person can be requested for a site or area. Investigation records and eligibility decisions stay in the government's personnel security systems and with your security office, and role-based access is designed to show even that status only to the people who staff jobs.

Does it cover weapons, targeting or operations?

No. It covers the everyday work of keeping equipment ready: parts, repairs, quality, people, contract reports and controlled documents. It does not touch weapons, targeting or military operations.

Technical detail

Technical detail

No. The scope is administrative and sustainment work: equipment readiness, parts and shipments, depot repair and quality, workforce qualifications and access, contract deliverables and the release of controlled records. It does not plan, control or analyze weapons, targeting or tactical operations.

Can the products carry our program's name, or be built specially for our program?

No. Each product keeps its own name and is set up through its settings: your sites, equipment types, repair steps, qualifications, report lists and markings. Everything described here is built into the products, not built separately for one customer.

Technical detail

Technical detail

No. Each product is offered under its own name and is configured, not customized: sites, end item types, repair stages, turnaround goals, qualification requirements, data item lists, review states and markings are set up in each product's configuration, and every capability described here is built into the products rather than developed for one customer.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.