Prime Campus Link
Who's on campus, who just left, and every parent notified — automatically. A smart school ID system joining RFID turnstiles to a live student, parent and teacher database.
Built as lead developer at PrimeIT Source Inc., which has since closed. Presented here as professional history, not as an AscenderTek client project.
- Sector
- Education
- Market
- Philippines
- Year
- 2018
- Role
- Lead developer
A campus has two blind spots that software alone never closes.
The first is physical. Once a student walks through the gate there is no verified record of who is actually on the premises — a logbook at reception answers the question slowly, incompletely, and only if someone remembers to sign it.
The second is communication. When classes are suspended or enrolment opens, the announcement travels by word of mouth and social media posts: reaching some families, missing others, and arriving too late for the ones who needed it most.
Two systems that should have been one.
No verified presence record
Nobody could say with certainty who was on campus at a given moment, which is the question that matters most when it matters at all.
Parents left guessing
A parent had no way of knowing their child arrived safely, short of calling the school office and asking someone to check.
Announcements that didn't arrive
Class suspensions reached whoever happened to see the post. The families who missed it found out by sending a child to a closed campus.
Records kept apart
Student, parent and teacher information lived in separate places, so the gate could not know who to notify even if it wanted to.
One system joining the gate to the database to the parent's phone.
Access control
- RFID turnstile integration at campus entry points, verifying each credential against the student record before the turnstile releases
- ZKTeco readers handling the credential scan at the gate
- Entry and exit both recorded, so presence is a live state rather than a morning snapshot
The database
- A unified record of students, parents and teachers, linking every credential to the people who need to be informed
- Each tap resolved in real time to a person, a guardian and a notification rule
Notification
- Automated SMS to parents on entry and exit — a parent knows their child arrived without having to ask
- Campus-wide broadcast for class suspensions, enrolment announcements and emergencies
- A multi-SIM GSM modem array sized to the campus: single-SIM for a small school, dual, four or eight-SIM arrays for larger populations
Most of this project was not web development.
It was hardware integration. Turnstile controllers, RFID readers and a modem array had to talk to a database in real time, at a gate, during the morning rush — where a failed read is not a logged exception but a child standing in front of a locked barrier while a queue forms behind them.
That constraint sets the engineering standard for everything else. The gate decision has to be fast enough to feel instant and reliable enough that staff trust it, because the moment they stop trusting it they prop the turnstile open and the system is worth nothing.
Sizing the modem array to the campus
SMS throughput is the quiet bottleneck. A single SIM sends messages at a fixed rate, so a campus-wide suspension notice to a large school would queue behind itself — the last parent receiving the message long after the decision stopped being useful.
So the modem capacity was specified against the population it served: single-SIM for a small school, scaling to dual, four and eight-SIM arrays as roll size demanded. Shipping one configuration and hoping would have worked in a demo and failed on the first real suspension day.
Access control and notification stopped being two problems.
The gate knows who came in. The parents know within seconds. The administration can reach every family on campus in minutes rather than hoping a social media post travels far enough.
The system was completed and deployed. PrimeIT Source Inc. has since closed and the product site is no longer online, so the public demo video below is the record of it working.
The stack reflects when it was built. The systems integration it required has not dated.
Software that has to meet hardware?
Access control, device integration, SMS at volume — systems where the failure case is physical. Tell us what it has to do and we'll scope it properly.