Project FAQs
Short answers to the questions teams ask before kicking off a project with Comans.
Need help right now?
Email: [email protected]
Phone: 1800 112 872
Hours: Mon & Fri (business hours) + after-hours options for critical
Most projects follow a simple pattern: discovery (1 to 3 weeks), design (2 to 6 weeks), then build (2 to 12 weeks), depending on scope. Migrations and OT projects can take longer because of validation and safety checks.
Yes. We use local Australian engineers for onsite delivery and trusted suppliers for hardware. We also handle what we can remotely, where it’s safe to do so.
Security comes first: Entra ID, MFA, least privilege, Defender EDR, device management via Intune, backups with Veeam or Zerto, and documented incident response runbooks.
Yes. We coordinate with incumbent providers and third parties (KiwiRail, telcos, OEMs) to keep the transition smooth.
Fixed price, time and materials, co-sourced (embedded engineers), or validation-led delivery. We recommend fixed price for well-defined scope and time and materials for complex work with unknowns.
We provide up-to-date runbooks, training, knowledge transfer sessions and a named Service Lead, plus hypercare after go-live.
Projects include a short warranty period and hypercare. Ongoing support is provided via Managed IT plans (business hours by default; after-hours optional).
We run scheduled restores and produce test reports with actions to fix what we find. Tests are tracked in Jira and reported at quarterly reviews.
We plan migrations and live work to minimise disruption. Weekend cutovers, pilots and staged rollouts are common.
Yes. All projects include operational documentation, runbooks in Jira and training sessions tailored to your team.
Still have questions?
If you don’t see your question here, book a consult and we’ll answer your specific concerns.
