Sustainable Technology Used — Bringing BINUS Research to Communities | BINUS Technology Transfer
Sustainable Technology Used
Research becomes meaningful when it reaches people. Tech Used is how BINUS ensures that research products don’t stop at the lab — they go into communities and create lasting change.
— What Is It
What is Technology Used?
Technology Used (Tech Used) is a performance indicator and program that measures whether a BINUS research product has been implemented in a real community setting — and whether that community actually benefits from it.
Tech Used is defined as: a research-based technology, at TRL 4 or above, that is actively used to empower a community — with planned implementation, real on-the-ground evidence, and a binding acknowledgment document (BAST) from the community itself.
Four criteria must all be satisfied:
|
📚 Research-Based Must be a research output with a traceable publication. |
⚙️ Technology TRL ≥ 4. Does not have to be a brand-new product. |
✅ Used Real, on-the-ground implementation — not just a demo. |
👥 Community An identifiable beneficiary group must be receiving the benefits. |
And implementation must be:
|
🗓 Planned Strategically planned from the start — not rushed at year-end. A planning document must be prepared before implementation begins. |
♻️ Sustainable Ensures continuous usage and long-term value. Includes at least one monitoring follow-up after implementation. |
📋 Acknowledged Validated by the community through a signed BAST (Berita Acara Serah Terima) — this is non-negotiable. |
— Why It Matters
Why Tech Used matters for lecturers
Triple PI
One product can unlock multiple PIs at once
If your product has associated IP, comes from a research project, is at TRL ≥ 4, and is sustainably implemented in a community, it can be claimed simultaneously under Technology Used, Impactful IP, and Product Commercialized. Potentially PI Community Empowerment (PkM) too.
Product Validation
Real users give you feedback, no lab can
Community implementation exposes your product to actual users in real conditions. The feedback you collect is invaluable for improving your product, strengthening your next grant proposal, and proving market readiness.
Publications & Branding
Field implementation generates new research output
Every Tech Used implementation is a publishable case study. It also builds social branding for you, your department, and BINUS — demonstrating that BINUS research creates measurable societal benefit.
Student Development
Involve students and teach them real-world skills
Tech Used implementations are natural vehicles for student involvement — in facilitation, community engagement, documentation, and monitoring. Students gain hands-on experience that no classroom can replicate.
— The Process
How to submit via BRIDGE Apps
The entire process runs through BRIDGE Apps. Start early — don’t wait until year-end. Cut-off: 6 December.
Registration & Planning
Register your profile and product on BRIDGE Apps. Then prepare your planning document before implementation begins — this is mandatory, not optional.
Implementation in Community
Run your implementation activities according to plan. Typical activities include:
- Introductory socialization session (60–90 min)
- Hands-on workshop (2–3 hours)
- Follow-up clinic or mentoring (weekly or biweekly)
- Training of Local Champions (ToT) for sustained adoption
At the end of implementation, get the BAST signed by the community. This is the binding acknowledgment that validates your claim.
Documentation & Submission (Checklist 1)
After implementation, compile all evidence as a PDF and upload via the BRIDGE Apps. Go to your product profile → click Edit → tick “Is there any impacted community” → upload your Checklist 1 evidence → save.
Checklist 1 — Required documents:
- Link to product profile on BRIDGE
- Link to planning document
- Link to signed BAST
- Link to implementation report
- Link to article or documentation write-up
Monitoring & Follow-Up (Checklist 2)
Tech Used must be sustainable — not a one-time event. At least one monitoring visit is required after implementation. This is where you confirm the community is still using the technology and collect structured feedback.
Checklist 2 — Monitoring report must include:
- Link to monitoring report
- Follow-up result and community feedback
- Plan for the product going forward
- Any inquiries or needs flagged to RTT
— Important Notes
Common questions and key rules
Rules to Know
- The product must be a research output — traceable to a publication or research project.
- The technology must be at TRL 4 or above — it doesn’t need to be brand new, but it needs to work.
- The community must be non-BINUSIAN — external groups only (UMKM, NGOs, local communities, government bodies, etc.).
- A signed BAST from the community is mandatory — without it, the claim cannot be validated.
- Implementation must happen before the cut-off — do not plan a December implementation.
- The same product can be submitted in subsequent years, but must show continued or expanded use.
Example
A researcher from the Food Technology department develops a low-cost water filtration tool (TRL 5, with a registered copyright). They implement it in a rural UMKM cluster in Tangerang, run two workshops, get the BAST signed, and conduct one monitoring visit three months later. This qualifies for Technology Used, Impactful IP, and potentially PI PkM — all from one implementation.
Ready to implement your technology?
Download the planning template and checklist kit, then register on BRIDGE to get started.