IETEL OS
Processes
The first-class business flows — grouped by department, each tied to the lifecycle stages it touches. A Process exists because there is a meaningful transition, control, or handoff — not a checklist entry for every small task.
Ordered department-by-department, roughly the order work flows between them.
Sales & Business Development
Lead Qualification
Confirm a lead is a real, fit opportunity before investing site survey or estimate effort.
Requirements Discovery
Understand what the customer actually needs the technology to accomplish, before any product is selected.
Integrated Site / Infrastructure Assessment
Verify reality before specifying technology — assess the physical and digital environment across only the modules the Operational Requirements actually call for.
Solution Design
Translate requirements, assessment findings, constraints, dependencies, and risks into a proposed solution architecture — then verify it actually holds together before Estimate begins.
Estimate Preparation
Translate scope and site conditions into an accurate, standard-compliant priced estimate.
Proposal Approval
Get the priced scope in front of the customer and secure a signed commitment.
Operations & Project Management
Sales-to-Operations Handoff
Give the Project Manager everything needed to instantiate the project without re-asking the customer for information Sales already has.
Project Planning
Turn a newly created project’s contract scope into an executable plan and schedule.
Procurement Coordination
Order and stage the equipment and materials a project needs before Installation begins.
Crew / Contractor Assignment
Get employees and/or approved contractors assigned to a project's start date.
Project Mobilization
Confirm every prerequisite — permits, procurement, crew — is actually satisfied before work starts on site, instead of discovering a gap on day one.
Change Management
Capture and approve scope changes requested mid-project, rather than letting them proceed un-priced or unapproved. Complements the cross-cutting Change Order concept already in the lifecycle model.
Project Closeout
Formally close the project record with a complete, verifiable package rather than letting it linger open.
Technical / Field Services
Installation Execution & Commissioning
Do the physical and technical work, and verify it actually functions before calling it done.
Installation Documentation & Sign-Off
Produce accurate as-built records and a technical sign-off that the work matches scope and standards — the gate before the customer is asked to accept.
EOD Reporting
Capture what happened on site each day while it's fresh, instead of reconstructing it at Documentation time.
Administration & Finance
People / HR & Contractors
Customer Success / Service
Customer Acceptance
Confirm the customer accepts the delivered scope, subject to any documented exceptions — a different question from Testing/Commissioning's "does the installed system meet its technical criteria."
Customer Post-Project Follow-Up
Maintain the relationship after closeout and surface genuine expansion opportunities without re-opening the closed project.