SDVOSB software consulting for Hill AFB, OO-ALC, and the depot sustainment mission
Veteran-owned engineers along the Wasatch Front building, modernizing, and integrating the software that keeps F-35, F-16, A-10, and ICBM sustainment running.
Depot sustainment software is held together by Excel, tribal knowledge, and the planner who's about to retire
Walk any back shop at OO-ALC and you'll find the same pattern: a system of record like IMDS or GCSS-AF feeding a sprawl of Access databases, SharePoint lists, and 14-tab Excel workbooks that a senior planner rebuilt in 2011. The official tool can't answer the question the shift lead needs answered, so someone wrote a workaround. The workaround became load-bearing. Now an F-35 panel, an F-16 wing box, or an ICBM component schedule depends on a macro nobody fully understands, and the person who wrote it is six months from a retirement ceremony.
- AWP tracking lives in Excel because IMDS and DPAS don't talk cleanly
- Oracle Forms apps from the early 2000s still drive shop-floor scheduling
- RAG and AI pilots die at the ATO boundary because nobody planned for IL5
- Contractors deliver a slide deck and a prototype, then leave before ATO
Depot-grade software delivery, built around how OO-ALC actually works
- STEP-01
Site walk and system inventory
We spend the first week on-site at Hill or Layton mapping the actual data flow — IMDS, GCSS-AF, DPAS, MILSTRIP feeds, the Access databases nobody wants to admit run the shop floor. No assumptions from a slide deck.
- STEP-02
Cut a narrow vertical slice
Pick one airframe, one back shop, or one ICBM component line. Ship a working tool against real depot data in 6–8 weeks. Prove it survives a swing shift before expanding scope to the wing or complex level.
- STEP-03
Modernize without breaking sustainment
Legacy Oracle Forms, COBOL batch jobs, and VB6 clients get strangler-pattern replacements behind .NET or Python APIs. Old system keeps running. New system takes traffic incrementally. No big-bang cutover during a surge.
- STEP-04
Cleared delivery, IL4/IL5 ready
Code ships through Platform One or a Cloud One pipeline when required. SBOM, SCA, and STIG compliance built into CI. Cleared engineers handle anything touching CUI or above; we don't subcontract that out.
- STEP-05
Transition to organic Air Force teams
Every engagement ends with runbooks, ATO artifacts, and a 30/60/90 handoff plan. Government civilians and blue-suiters own the system when we leave. We stay on retainer for surge work, not as a permanent crutch.
# Example: pulling IMDS work-order backlog into a modern API
# so depot planners stop exporting to Excel every morning.
from fastapi import FastAPI, Depends
from sqlalchemy import create_engine, text
from datetime import datetime, timedelta
app = FastAPI(title="OO-ALC Backshop Backlog Service")
engine = create_engine(IMDS_READ_REPLICA_DSN, pool_pre_ping=True)
@app.get("/backlog/{msn}")
def backlog_by_msn(msn: str, days: int = 30):
"""Return open work orders for a Mission Design Series
(e.g. F-35A, F-16C, A-10C) over the last N days."""
cutoff = datetime.utcnow() - timedelta(days=days)
with engine.connect() as conn:
rows = conn.execute(text("""
SELECT wo_id, jcn, wuc, opened_ts, priority, awp_flag
FROM imds_work_orders
WHERE mds = :msn
AND status IN ('OPEN','AWP','HOLD')
AND opened_ts >= :cutoff
ORDER BY priority ASC, opened_ts ASC
"""), {"msn": msn, "cutoff": cutoff}).mappings().all()
return {
"mds": msn,
"window_days": days,
"open_count": len(rows),
"awp_count": sum(1 for r in rows if r["awp_flag"]),
"orders": list(rows),
}
# Deployed to Cloud One IL5. Auth via CAC + Platform One SSO.
# Replaces a 14-tab Excel workbook maintained by three planners.Representative pattern: a read-only API over IMDS data that retires a brittle Excel workflow without touching the system of record.
Field FAQ.
→ Are you actually local to Ogden, or flying people in from out of state?
We have engineers based along the Wasatch Front and routinely work on-site at Hill AFB, the Ogden Air Logistics Complex, and Falcon Hill. For programs that require regular badge access, we staff with people who already live within driving distance of Roy, Layton, Clearfield, and Ogden. Remote-only delivery doesn't work for depot environments where you need to walk the shop floor.
→ Is VooStack SDVOSB certified, and can you prime or sub on Hill AFB contracts?
Yes. VooStack is a Service-Disabled Veteran-Owned Small Business verified through the SBA's Veteran Small Business Certification (VetCert) program. We can prime SDVOSB set-asides and sub to large primes already on vehicles supporting OO-ALC, AFSC, and AFLCMC. We're also comfortable on GSA MAS, SeaPort-NxG teams, and various agency-specific BPAs when the work fits.
→ What kind of depot sustainment software do you actually build?
Typical work includes back-shop scheduling tools, AWP (awaiting parts) tracking dashboards, supply chain visibility layers over DLA and GCSS-AF data, predictive maintenance models for specific components, and modernization of Oracle Forms or Access-based tools that planners have outgrown. We've also built tooling around ICBM ground systems sustainment and F-16 structural repair workflows. We don't touch flight-safety-critical software — that's a different qualification path.
→ Do you have cleared engineers, and what levels?
Yes. We maintain a bench of engineers with active Secret and Top Secret clearances, and a smaller group with TS/SCI. For CUI and IL4 work we can usually start within a week or two; for collateral Secret programs, staffing depends on current bench availability. We do not crosswalk clearances or sponsor brand-new clearances on a fixed-price effort — that math doesn't work for either side.
→ How do you handle modernization of a legacy system that the depot can't afford to break?
Strangler pattern, every time. The legacy Oracle Forms app, COBOL batch, or VB6 client keeps running. We stand up a modern API in front of the same database, migrate one screen or one workflow at a time, and route traffic incrementally. Planners see continuous improvement instead of a 'go-live weekend' that wrecks a production surge. Full cutover usually takes 9–18 months depending on system complexity and ATO scope.
→ Can you integrate Claude, GPT, or RAG into Air Force workflows?
Where it makes sense, yes — and we'll tell you when it doesn't. Practical wins so far: RAG over technical orders and -1 manuals so maintainers stop hunting through PDFs, summarization of long deficiency reports, and structured extraction from supply chain emails. We deploy against IL4/IL5-authorized model endpoints (Azure Government, AWS Bedrock GovCloud, or on-prem) — never against public ChatGPT for government data.
→ What does a typical engagement timeline and budget look like?
Discovery and a working prototype: 6–8 weeks, generally in the $80K–$150K range depending on data access and clearance requirements. A production-deployed tool with ATO artifacts: another 4–6 months, typically $300K–$900K. Staff augmentation with senior cleared engineers runs at standard SDVOSB rates on a T&M or labor-hour basis. We share fixed-price risk when scope is genuinely fixed, and refuse to pretend it's fixed when it isn't.
→ Do you only work with the Air Force, or other branches and agencies too?
Hill AFB and OO-ALC are a natural anchor because of where we sit, but we work across DoD and federal civilian agencies. Past and current work spans Army sustainment commands, Navy logistics, VA, and a handful of DHS components. The patterns are similar: long-cycle systems, real consequences for downtime, and people who've been burned by consultants who didn't understand the mission.
→ How do you transition the work back to government civilians or blue-suiters?
Built into the contract from day one. We pair with government developers during the build, write runbooks as code ships, and structure a 30/60/90 handoff at the end. ATO artifacts, SBOMs, architecture decision records, and on-call rotations all get transferred. We're happy to stay on retainer for surge capacity or major version work, but we don't engineer dependency into the relationship.
Continue recon.
Services overview
Custom builds, AI integration, modernization, and cleared staff augmentation across DoD programs.
REL-02Case studies
Representative depot, logistics, and federal modernization work with concrete outcomes and timelines.
REL-03Engagement packages
Fixed-scope discovery sprints, prototype builds, and modernization retainers sized for federal budgets.
REL-04Talk to an engineer
Skip the sales funnel. Get a working call with someone who's shipped this kind of system.
Have a depot sustainment or Hill AFB program that needs to ship? Let's talk.
Talk to a VooStack operator. We respond within one business day.