QSI S1 Hub
Quantum StateHALO-SI from QSI. Planned capability. In development.
HALO-SI from QSI: program workflow map
From the first requirement to the day a product is retired, a program manager carries a lot: people, documents, schedules, funding and contracts. This map walks through the life of a program in 10 phases. Tap any phase to see what the program manager does and what HALO-SI from QSI is designed to help with. People review every output. Your team keeps the final say.
The 10 phases
Tap a phase. Concept shown. Fictional data.
1. Requirement intake
What the PM does
- Understands the need, the users and the stakeholders.
- Receives the validated requirement.
What HALO-SI from QSI is designed to help with
- Build a stakeholder map.
- Store the requirement with links to its source.
2. Pathway selection
What the PM does
- Picks the acquisition pathway that fits the cost, urgency and type of product.
- Plans how to tailor that pathway.
What HALO-SI from QSI is designed to help with
- Set up the chosen pathway's milestones and decision points from a pathway pack built from public acquisition pathway guidance.
3. Acquisition strategy
What the PM does
- Plans how the program will buy, build, test and support the product.
- Leads market research and gets the strategy approved.
What HALO-SI from QSI is designed to help with
- Store strategy documents with links to their sources.
- Track reviews and approvals.
4. Funding and budget
What the PM does
- Requests funds and lines them up with the work.
- Watches how money is planned and spent by year and type.
What HALO-SI from QSI is designed to help with
- Funding allocation tracking and planning: link planned funds to milestones.
- Flag spending that looks ahead of plan for people to review. HALO-SI from QSI does not obligate or move funds.
5. Contracting
What the PM does
- Helps shape the solicitation, evaluation and award.
- Manages the contract once it is in place.
What HALO-SI from QSI is designed to help with
- Contract execution tracking: follow deliverables and milestones.
- Flag late or missing deliverables for your team.
6. Development
What the PM does
- Runs design reviews and manages risk.
- Keeps the schedule on track.
What HALO-SI from QSI is designed to help with
- Import Microsoft Project schedules; your team reviews the changes before they update the master schedule.
- Track risks and action items.
- Log reviews, decisions and action items.
7. Test
What the PM does
- Plans and runs testing.
- Records and acts on results.
What HALO-SI from QSI is designed to help with
- Log test events, decisions and action items.
8. Production
What the PM does
- Reaches the production decision.
- Manages quality and delivery.
What HALO-SI from QSI is designed to help with
- Show whether cost, schedule and performance are tracking to plan.
- Check readiness against milestone gates.
9. Fielding
What the PM does
- Delivers the product, trains users and hands over support.
What HALO-SI from QSI is designed to help with
- Keep fielding dates in the master schedule.
- Keep stakeholders updated from one shared picture.
10. Sustainment and disposal
What the PM does
- Supports and upgrades the product, then plans its retirement.
What HALO-SI from QSI is designed to help with
- Keep the program's full history in one searchable place.
- Track sustainment funding over time.
Across all phases
HALO-SI from QSI is designed to draft briefs and summary charts from current program data in your own template, with each number linked to its source and dated. It is designed to keep a record of who changed what and when. People review every output.
The embedded specialist
Engagements include a dedicated QSI data management and SI specialist, as set out in each signed agreement. The specialist:
- Builds your program's knowledge management database: gathers documents, organizes them by phase, contract and decision, and keeps them current.
- Tailors HALO-SI from QSI to how your team works: templates, brief formats, schedule imports and stakeholder lists.
- Trains your team and checks data quality.
The specialist does not make program decisions. Your team keeps the final say.
How the parts connect
- Inputs: program documents, Microsoft Project schedules, contract deliverable lists, funding plans, and notes from reviews and tests.
- Knowledge base: stores everything with source links and dates.
- Pathway guidance: milestones and decision points built from public acquisition guidance, dated, and reviewed for updates.
- Trackers: schedule, funding, contract, stakeholder, and reviews, decisions and action items.
- Outputs: dashboards and draft briefs for people to review and approve before anything is shared.
A day in the life (Illustrative example)
Before
- The morning goes to chasing the latest numbers by email.
- Much of the day goes to rebuilding slides for the weekly brief, and numbers may not match across decks.
- Schedule changes are typed into the master schedule by hand.
- Late deliverables are noticed late.
- Decisions sit in scattered notes.
After (planned capability)
- One dashboard shows cost, schedule and performance, with flags for late or missing items.
- A draft weekly brief is built from current data, then reviewed and edited.
- The contractor's Microsoft Project file is imported, and the PM reviews what moved and what it affects before accepting it.
- Late or missing deliverables are flagged for the team.
- Reviews, decisions and action items are logged in one place.
- More time goes to managing the program and the people.