Business Phone Systems →
Cloud, on-premises or a mix of both. Dial plan, carrier connections, 911 with a dispatchable location, and what each site keeps when its link goes down.
Alaska
IT Services and Technology Projects in Alaska
We design, build and support phone systems, contact centers, meeting rooms, networks and security for organizations in Alaska, from the main office to the sites reached only by air or water.
What We Do
Trybus Solutions designs, builds and supports the technology an organization runs on: phone systems and contact centers, meeting rooms and video conferencing, networks and Wi-Fi, security, and the support behind all of it. In Alaska that work usually covers more distance than it does in the rest of the country. One organization can run a main office in Anchorage, clinics or offices in hub communities, and sites in villages reached only by air or by water.
Most of our work starts for one of a few reasons. A system is coming up on end of support. A contract for circuits or a calling platform is up for renewal. A funding award has arrived with a spending deadline attached. Or a network built for one building is now carrying a dozen sites over links it was never designed for.
Funding is often part of the picture. The Alaska Rural Health Transformation Program, the Healthcare Connect Fund and the state and federal broadband programs each come with their own rules and dates, and a project has to be scoped to fit them.
We work nationwide from Chattanooga, Tennessee. Most of an Alaska project runs remotely. Whether engineers travel to site, and for which stages, depends on what the project requires, and that is agreed at scoping. Our clients usually have their own IT team, and we are there for the parts that need people who have done this before.
Why Alaska Organizations Bring Us In
- We are not tied to one manufacturer.
We carry a range of technology partners, so what we recommend is decided by your sites and your links, not by what we happen to sell. If the system you have still fits, we will say so. - We design for the links you actually have.
Fiber, microwave and satellite paths behave differently, and a design that assumes the same connection at every site tends to fail at the smallest one. We measure each link before deciding what runs over it. - We plan around travel and freight.
The Alaska Department of Transportation and Public Facilities has reported that 82 percent of Alaska communities are not connected to the road system. Equipment is configured and tested before it ships, spares are planned for, and site visits are grouped so one trip covers as much as it can. - One team across the whole estate.
Calling, meeting rooms, contact center, security and the network underneath all affect each other. One team across them avoids the gaps that open up between separate vendors working to separate schedules. - Design and procurement in one place.
We can design the solution and supply the hardware and licensing for it, and our procurement can work with your purchasing system instead of sitting outside it. - We are still there after go-live.
Support is available as a separate agreement, with coverage hours agreed in Alaska time. Plenty of clients keep their own team and use us only for the project, which is fine.
What You Get
Scope depends on the project. A phone replacement at one office does not need the documentation a network refresh across twenty sites does. Below is what we produce on a typical mid-size project, and we agree which of it you need during scoping.
Everything we produce is yours. If you take the design elsewhere to be built, it will be complete enough for somebody else to build it.
- Site and link inventory:
Every site, what connects it, and what each link actually delivers, measured rather than taken from a contract. - Assessment of the current environment:
What is running today, taken from the live systems as well as from whatever documentation exists. - Recommendation and options:
What we suggest, what else was considered, and the reasoning. Written so it can be taken to a board or a council without an engineer to translate it. - Design documentation:
A high-level design on most projects, and a detailed low-level design where the build warrants one. - Bill of materials:
Hardware, licensing, spares and services itemized, so procurement and any funding application are working from real numbers. - Project plan and travel schedule:
Stages, dependencies, change windows and site visits, planned around flights, freight and the time of year. - As-built documentation and handover pack:
What was built, how it is configured, and what your team needs to run it from wherever they sit.
The Systems We Work On
Six areas. Each has its own page on how the work runs in Alaska, and most projects touch more than one.
Contact Center →
Routing, queues, agent design, recording and reporting for teams that answer callers from across the state, often from more than one location.
Video Conferencing and Meeting Rooms →
Room standards by size, audio and displays, and video that holds up over the link each site has. For many statewide organizations, video is how the team meets.
Network, Wi-Fi and SD-WAN →
Switching and Wi-Fi inside the building, the wide area network between sites, and traffic policy for links that are limited and expensive.
Cybersecurity →
Firewalls and segmentation, identity and multi-factor authentication, endpoint protection, logging, and secure access for staff and vendors connecting from outside.
Managed IT Services and Support →
Monitoring, patching, administration and a support desk, co-managed or fully managed, with coverage hours agreed in Alaska time.
How a Project Runs in Alaska
Broadly the same shape whether it is one office in Anchorage or thirty sites across a region. Timescales depend on circuit lead times, freight, and how much of your team is available.
- Scoping and kickoff:
Agree what is in scope, the deliverables, who is involved on both sides and how decisions get made. Funding deadlines and procurement rules are set out here, because they often decide the calendar. - Discovery:
Remote sessions with the people who run the systems now, configuration pulled from the live environment, and measurements of each site link. When discovery changes the scope, we price it and you decide before we carry on. - Site survey:
Where the project requires it, on site at the locations where the building decides the design. Visits are grouped so one trip covers as many sites as it reasonably can. - Design and review:
Design documented, then walked through with your team. Sign-off here is what the build gets measured against. - Procurement and staging:
Hardware ordered, configured and tested before it ships, so the work at a remote site is installation and verification rather than configuration. Freight time is in the schedule from the start. - Cutover:
Site by site, inside agreed change windows and with a way back. On larger projects one site goes first so the rest can learn from it. - Handover:
A period of closer support while the snags come out, then documentation, training for your team, and a decision about the old equipment.
What Is Quoted Separately
Most of what is below is work we do. It is not part of a project by default, because each piece carries its own scope, its own schedule and its own cost. If you want any of it included, say so at scoping and we will quote it in. The last one is different: it is work we do not do at all.
- Structured cabling and pathways.
We do not pull cable ourselves. We survey the building, write the specification and coordinate the cabling partners who install against it, then check the results before the switching goes on top. - Travel and freight.
Site visits and shipping are itemized on their own, because they depend on where the sites are and when the work happens, and you should be able to see them. - Funding applications.
We provide the bill of materials and the scoped cost for the project, which your team can use in a funding application. Writing and submitting the application stays with you or your grants team. - Ongoing operation and support.
Managed services is a separate agreement with its own service levels. Some clients run the systems themselves after handover and some hand them to us. - Internet and wide area circuits.
We specify what each site needs and design around whatever you buy. We do not become your carrier, and circuits stay with whoever bills them.
Who We Work With in Alaska
The technology does not change much between sectors. The order of priorities does.
Tribal Health and Tribal Government →
Health, government and enterprise operations on one estate, sovereignty over data and systems, and funding cycles that do not follow a commercial year.
Alaska Native Corporations →
Holding companies with subsidiaries in many industries and many states, often still carrying the systems of every acquisition they have made.
Hospitals and Clinics →
Clinical communications, video between hub hospitals and village clinics, and the privacy rules that come with patient contact.
Boroughs, Cities and State Agencies →
Public procurement, emergency calling, records retention, and services that cannot stop because a link went down.
Technology We Work With
We hold partner relationships across the technology industry, and our engineers also work in platforms we do not sell. A project starts on whatever you are running now, whoever supplied it.
We do not publish comparisons between manufacturers. Which platform suits an organization is something an assessment works out, not something a website should decide.
Talk to Us About a Project in Alaska
Tell us how many sites you have, how each one connects, and what date is driving the timeline. We will tell you what we think needs doing and what does not, and put a scope and a number against it.