Summary

  • In a 2009 interview, Lawson State network specialist James Mankowich described choosing a single-channel campus wireless design partly to preserve continuity for an existing network-based voice service.
  • He also described using an additional firewall and separate student and employee networks, turning traffic separation into an operating boundary rather than a general promise of perfect security.
  • The decision sat inside practical constraints: a very small IT staff, ageing buildings, departmental requirements, expenditure, service quality, existing voice traffic and future growth.
  • EdTech reported a three-campus deployment and institution-level outcomes, but its CDW affiliation and CDW-G's role in the project mean those claims are not independent validation of savings, product superiority or learning impact.
  • The durable lesson is about accountable infrastructure choice: preserve a running service, make decision rights visible, qualify promotional evidence and keep missing measurements and alternatives open.

The wireless project's most consequential choice can be stated in ordinary language. Lawson State wanted broader access without breaking the voice service already running on its network. Mankowich told EdTech that single-channel operation was one reason for selecting the system. EdTech also attributed to him an additional-firewall design separating student traffic from the employee network. Its evidentiary limits matter just as much.

Those are person-level decisions. Approval belonged to the president's cabinet, deployment belonged to the college and reported outcomes belonged to Lawson State. That separation lets readers learn from an operator without turning a bounded interview into a hero story or product endorsement.

Start with the service that already had to work

Wireless projects are often narrated as expansions: more coverage, devices and places to connect. That framing can hide the first responsibility of an infrastructure team—avoid damaging a service people already depend on. Lawson State's network carried Voice over Internet Protocol, or VoIP: calls travelled through the data network rather than a separate telephone system.

That existing voice path changed the nature of the wireless decision. A person walking with a network-connected voice device may move from the area served by one access point to another. If the transition interrupts connectivity or changes the network path badly, a live call can suffer. The source record does not provide independent call-quality measurements, but it does record the continuity problem Mankowich said he was trying to manage.

EdTech expressly wrote that another reason Mankowich chose the Foundry/Brocade system was its single-channel operation. It reported his explanation that the approach allowed the existing VoIP service to continue as users roamed between access points. That is the article's strongest person-level choice claim because the publication assigns both the selection and the stated operational reason to him.

The evidence does not show that Mankowich held final purchasing authority. It does not disclose a scoring sheet, a competitive field, a formal procurement method or rejected alternatives. The responsible formulation is therefore precise: EdTech attributed a technical selection to him, and he gave voice-service continuity as one reason. It would be inaccurate to say that he unilaterally bought the system or independently proved it superior.

For a non-specialist, the design tried to make movement across coverage areas feel less like switching between islands. It does not prove seamless behaviour under every condition. It was presented as supporting continuity for an application whose interruptions would be immediately noticeable.

The project should therefore be judged by whether it respected a dependency already in production, not by whether the new network looked modern.

Who Jim Mankowich was in the record

The 2009 article identified James Mankowich as a network specialist at Lawson State Community College. A later vendor bid hosted by the Alabama Community College System named James Mankowich at Lawson State and included a lawsonstate.edu contact address. That record is useful for identity continuity, not for proving project results.

Official ACCS material later fills out the name and role bridge. A personnel listing records James Paul Mankowich and an ACCS employment date in August 2023. January 2024 Board minutes introduce Jim Mankowich as a Systems Manager. The current staff directory lists Jim Mankowich as Director of IT Infrastructure. The uncommon surname, first-name variant and institutional path support treating these records as one person.

Those later titles do not retroactively enlarge the 2009 evidence. A current director title can establish where Mankowich sits today. It cannot show that he approved every Lawson State decision, controlled a later ACCS procurement or personally produced a college-wide outcome. The article therefore uses official records to establish identity and role progression only.

This separation matters for overlooked operators. A directory profile is often the easiest public record to find, but it is usually the weakest evidence of what someone actually decided. The 2009 interview supplies the observable choice and implementation statements. The later official records keep the person anchored across time. Neither type of source should be asked to do the other's job.

The result is a profile built from decisions rather than rank. Mankowich matters here because a dated account connects him to a continuity choice and a traffic-separation design under named constraints. His later role helps confirm identity, but it is not the reason the story qualifies as an operating case.

A campus problem larger than coverage

Lawson State's stated ambition extended beyond providing a convenient wireless signal. Mankowich told EdTech that the college wanted to deliver voice, video, Internet access and online classrooms across its campuses. That combination placed several kinds of traffic and user need on the same infrastructure.

Voice calls are sensitive to interruption and delay. Video can consume sustained capacity. General Internet access varies sharply with user behaviour. Online course delivery depends not only on coverage but also on authentication, platforms, support and teaching practice. Putting these aims together creates a coordination problem, not a single feature request.

The physical environment added another constraint. Mankowich described ageing buildings. Older campuses can present thick walls, irregular layouts, legacy cabling routes and spaces not designed around modern radio coverage. The source does not provide a building-by-building engineering survey, so those specific obstacles should not be invented. What it does support is that building age was part of the planning problem.

Departments also had different requirements. A library, classroom, administrative office and technical lab do not necessarily use the network in the same way. Mankowich described the need to understand those demands rather than assume one magic solution. That phrase is important because it resists a common project myth: buying a platform does not remove the work of reconciling local needs.

EdTech reported that Lawson State used mapping before implementation and testing. Mapping can help a team understand where coverage and capacity may be needed, but the article does not disclose survey data, acceptance thresholds or final test results. It is safe to describe a sequence of planning, installation and testing. It is not safe to claim that every building or use case was independently certified.

The small-team constraint

Mankowich described Lawson State's IT staff as very small. The source gives no exact headcount, so the phrase should remain qualitative. Even without a number, the constraint changes the decision. A design that works only with constant specialised intervention may be unsuitable for a team that must support a whole college with limited personnel.

Small teams pay for complexity repeatedly. They pay during installation, when each exception takes time. They pay during incidents, when responsibility is unclear. They pay during upgrades, when undocumented dependencies reappear. They also pay when a new system needs skills or monitoring that were not included in the purchase decision.

This does not prove that the chosen system reduced labour. EdTech's account has a commercial context, and no independent support ledger or staffing study was found. The defensible conclusion is that staffing capacity was a named decision constraint. Any claim about actual support savings would need records that are not in the current source set.

For management readers, this is a useful distinction between design intent and measured result. A team may choose an architecture because it appears easier to operate. That intent can be rational and attributable. Whether the system later reduced workload is a separate empirical question. Conflating the two turns a planning reason into an outcome claim.

Mankowich's account is strongest at this level: a small-team reality shaped a consequential choice, but no measured before-and-after productivity result is available.

Separating student and employee traffic

The second person-level design claim concerns traffic separation. Mankowich described using an additional firewall and creating separate student and employee networks so student traffic would be isolated from the rest of the network. This is a concrete implementation statement, not merely a general interest in security.

A firewall applies rules to traffic moving between network areas. Separate networks can limit which systems different user groups can reach and make policy easier to express. In plain language, the design attempted to prevent every connected student device from occupying the same trusted space as employee systems.

The public record does not include an architecture diagram, rule set, penetration test or incident history. It would therefore be wrong to call the separation independently audited or breach-proof. A boundary can reduce exposure while still containing errors, exceptions or poorly maintained rules. Security design is not the same as verified security performance.

The use of an additional firewall also carried an operational cost. Every boundary needs configuration, monitoring and ownership. When legitimate access fails, someone must determine whether the cause is policy, identity, routing, application behaviour or the device itself. For a small team, separation can make risk more manageable while adding troubleshooting responsibilities.

What can be attributed to Mankowich is the decision pattern: use another enforcement point and separate the two traffic populations. What belongs to Lawson State is the ongoing effectiveness of that boundary. Without audit data, incident records or rule-change history, the result must be described as an implemented design rather than a proven security outcome.

The meaning of single-channel operation

Wireless terminology can make a choice sound more conclusive than the evidence supports. The 2009 article presented single-channel operation as a feature of the selected Foundry/Brocade system. Mankowich's stated continuity rationale is relevant, but it should not be converted into a universal technical verdict.

In conventional wireless deployments, neighbouring access points may use different radio channels to reduce interference. A coordinated single-channel architecture presents a different management model. The precise internal operation of the selected product is outside the current evidence packet, and this article does not attempt an unsourced product tutorial.

The important organizational fact is that the architecture addressed movement. A voice user might cross campus coverage areas during a call. Mankowich's explanation connected the selected design to maintaining that service. This made roaming behaviour part of the selection rationale instead of an issue deferred until after deployment.

The source also does not identify competing systems or explain how alternatives handled roaming. Without that comparison, there is no basis for declaring that only one vendor could meet the need. A source may document why an operator selected an option without establishing that it was the uniquely best option.

Continuity is not the same as quality. A call can remain connected and still suffer delay, loss or degraded audio. No call-quality baseline, failure rate or independent comparison was found. “Preserved” therefore names Mankowich's stated design aim, not measured perfection or unique product superiority.

Approval was an institutional act

EdTech reported that Lawson State's president's cabinet approved the wireless implementation. That detail prevents a misleading biography. Mankowich may have shaped the technical choice, but the record assigns final institutional approval to a governance body.

Approval and recommendation are different decision rights. A technical operator can define requirements, compare architectures and explain risk. A cabinet can decide whether the institution will commit resources and accept the project. Procurement staff, vendors and implementation teams may hold still other responsibilities. The available record does not map every role, but it clearly rules out a one-person approval story.

No cabinet minutes for the project were found. The article therefore relies on EdTech's report for the approval fact and does not claim to know the cabinet's debate, vote, conditions or budget authority. Those omissions are not minor; they define what the public evidence cannot answer.

The same restraint applies to expenditure. Mankowich discussed balancing spending and service, and EdTech reported certain cost effects. No public invoice, budget, return-on-investment calculation or independent before-and-after ledger was found. The project may have had a rational financial case, but the public record does not permit an audit of that exact case here.

Accountability improves when these layers remain separate. Mankowich can receive accurate credit for documented technical choices without absorbing cabinet authority, while the institution owns the project outcome.

From mapping to a three-campus deployment

EdTech reported that Lawson State installed 135 access points across three campuses. It also described roughly three months from mapping through implementation and testing after equipment selection. Those are project-level facts in a vendor-affiliated publication, not official acceptance records.

The three-month timeline should be handled with similar care. It indicates a compressed execution sequence in the source. It does not show the preparation that preceded equipment selection, nor does it disclose whether remediation continued afterward. It also should not be rewritten as something Mankowich personally completed alone.

The vendor involvement does not make the account unusable. It changes its evidentiary status. Direct statements attributed to Mankowich remain valuable primary interview evidence. Project numbers and outcome claims can be reported as EdTech's account. Promotional inferences require independent support that the current packet does not contain.

That source discipline produces a more informative story. The project reached a reported operating scale under a short schedule, but the article does not claim independent certification. Mankowich's decision can be situated inside the deployment without making him its sole implementer. The result stays consequential and bounded at the same time.

What the college said it gained

EdTech reported several institution-level outcomes. It described campus wireless access, less congestion in computer labs, video streaming, web-supported classes, growth in library computers from eight to forty, reduced switch and cabling expense and the ability to establish labs. These statements belong to Lawson State as reported by EdTech, not to Mankowich alone.

The list is significant, but its source context is material. EdTech discloses that it is published by CDW, and the project article says CDW-G assisted Lawson State. The publication can preserve a useful contemporary interview while still lacking independence from a commercial participant.

Two official Lawson State catalogs provide narrower corroboration. The 2009–2011 catalog identifies Blackboard for online and web-supported course delivery and lists Tegrity. A later catalog describes Blackboard-based distance education, institution-wide Tegrity adoption and online access to archived lectures. Those official records show that the institutional delivery capabilities existed and persisted.

The library figure is not independently corroborated in the current packet. Neither are the claimed savings, reduced congestion or ability to build labs without additional funds. They can be described only with explicit EdTech attribution. An article that silently promotes them to verified facts would exceed the evidence.

No student-learning dataset was found. Wider access may support study, but plausible benefit is not measured impact. The contemporary account documents what the college and operator said; official catalogs confirm only a narrow capability environment.

Evidence from an affiliated publisher

Source affiliation should affect language, not erase evidence. EdTech's current About page says the publication is published by CDW. The 2009 article credits CDW-G with helping Lawson State through the project. Readers therefore should not treat the article as detached evaluation of a vendor-assisted deployment.

At the same time, the article contains directly attributed statements from Mankowich. A primary interview can establish what a named participant said, which choice a report expressly assigns to him and which constraints he described. The correct response to affiliation is disciplined attribution, not pretending the interview never happened.

Official catalogs are independent of CDW in organizational authorship but are still associated-organization records. They can confirm Lawson State's own course-delivery environment. They are not independent journalism, external audit or causal evaluation. Calling them independent outcome reporting would also overstate their role.

No genuinely independent outcome-reporting source was found in the bounded review. That absence must travel with the article. It is not a reason to discard the person-level decision; it is a reason to keep result claims narrow and qualified.

For readers, the method is clear: extract the observable decision, preserve speaker and publisher attribution, compare narrow official corroboration and refuse claims that need missing measurements or independence.

Constraints without invented numbers

Mankowich described balancing expenditure, service quality and future growth. These are real decision variables, but the source gives no exact budget, staff number, service-level target or capacity forecast. Good analysis should not fill those gaps with plausible-looking figures.

Service quality is equally broad. For voice, it might include continuity, delay and clarity. For classes, it might include reachability and capacity. For staff, it might include reliability and support burden. The source records a concern with quality but not a formal measurement framework.

Future growth creates another planning problem. An architecture can appear affordable at launch yet become expensive as users, devices or applications increase. Mankowich described future growth as one of the variables the college had to balance. That stated concern is not proof of how long the hardware remained sufficient.

Naming constraints without manufacturing numbers is not evasive. Readers can see why continuity, separation, manageability and expansion mattered while understanding that a procurement audit requires unavailable records.

What the record does not show

The public sources do not reveal who held budget authority below the president's cabinet. They do not disclose a procurement scorecard, the competing products, a rejected alternative or the contract terms for the 2009 deployment. These omissions prevent a complete account of resource allocation.

No independent architecture diagram or security assessment was found. The firewall separation is therefore an attributed implementation choice, not an audited control result. There is also no public incident series that would show whether the boundary prevented, contained or failed during particular events.

No before-and-after voice data was found. The single-channel choice had a stated continuity rationale, but there are no disclosed call-drop rates, latency measurements or user surveys. The evidence supports intent and choice, not a quantified voice-service outcome.

No independent cost dataset was found. Claims about fewer switches, less cabling or labs established without additional funding remain EdTech-reported institution-level statements. Exact savings, payback periods and support costs are unknown.

No independent learning-impact evidence was found. Official catalogs show web-supported and archived lecture-delivery capability, but capability is not the same as academic effect. A network can enable access without determining how courses are designed or how students perform.

The review also found no documented failure or reversal. That does not prove permanent success. It means the bounded public record did not surface a reversal that could be responsibly described. Absence of a failure report must not be converted into evidence that no failure occurred.

These unknowns identify what could change the assessment: procurement files for alternatives and authority, incident and performance data for continuity and separation, audited costs for the financial account and independent research for learning effects.

Five questions answered

What problem did Lawson State need to solve? It wanted broad wireless support for voice, video, Internet and online classrooms across multiple campuses while preserving a voice service already carried by the network. The physical and organizational environment included ageing buildings, differing departmental needs and a small IT staff.

Why did Mankowich say single-channel operation mattered? EdTech attributed the selected system to him and reported his view that its operation preserved existing VoIP continuity as users moved between access points. The evidence does not independently measure that result or compare every alternative.

How did the design divide traffic? Mankowich described an additional firewall and separate student and employee networks. That is an observable implementation boundary. The source set does not contain an independent audit of its effectiveness or a record of every exception.

Who owned the project outcome? Mankowich owns only the choices and statements expressly attributed to him. The president's cabinet owns final approval as reported. Lawson State owns deployment and institutional results. CDW-G assisted the project, and EdTech reported it from an affiliated publishing context.

What remains unresolved? Budget authority, procurement alternatives, exact staffing, measured voice continuity, security outcomes, audited savings, long-term hardware sufficiency and learning impact all remain unknown. Those gaps set the ceiling on the article's conclusions.

The bounded conclusion

Jim Mankowich's 2009 decision record is valuable because it connects a technical choice to a running service. The college did not approach wireless as an empty field. Voice calls already depended on the network, and the selected architecture was described as protecting that continuity while coverage expanded.

His second documented choice created a traffic boundary. The additional firewall and separate student and employee networks expressed a practical security model. It was not proof of perfect security, but it made responsibility and exposure more explicit.

The institutional project was larger than either choice. Cabinet approval, vendor assistance, mapping, installation, testing and reported campus outcomes involved a wider set of actors. Accurate attribution lets Mankowich receive credit without absorbing their authority or work.

The source record also disciplines enthusiasm. EdTech preserved a useful dated interview, yet its CDW affiliation and CDW-G's project role prevent the article from serving as independent validation. Lawson State catalogs corroborate a narrow capability outcome, not product superiority, savings or sole causation.

The leadership lesson is therefore not “buy this system.” It is to begin with the service that cannot be lost, identify the constraints that make the decision real, divide trust deliberately, assign approval correctly and demand evidence at the level of the claim.

The case remains open to revision. Procurement records, performance measurements, incident evidence or independent outcome research could strengthen or challenge the current reading. Until then, the most responsible conclusion is bounded: Mankowich made documented infrastructure choices under real constraints, and the public record supports their rationale more strongly than it supports their promised results.

Image disclosure

Alt text: AI-generated photorealistic editorial scene of an anonymous campus-network worker, seen strictly from behind, routing blue and yellow cables through a blank enclosure.

Caption: AI-generated photorealistic editorial scene illustrating campus-network continuity work. It does not depict Jim Mankowich, his appearance, a specific device or a documented event.

Sources