{"id":359,"date":"2026-04-13T03:36:28","date_gmt":"2026-04-13T03:36:28","guid":{"rendered":"https:\/\/binus.ac.id\/techtransfer\/?page_id=359"},"modified":"2026-04-13T03:37:40","modified_gmt":"2026-04-13T03:37:40","slug":"technology-used","status":"publish","type":"page","link":"https:\/\/binus.ac.id\/techtransfer\/technology-used\/","title":{"rendered":"Sustainable Technology Used \u2014 Bringing BINUS Research to Communities | BINUS Technology Transfer"},"content":{"rendered":"
\n

<\/p>\n

\n
BINUS Technology Transfer<\/div>\n

Sustainable Technology Used<\/h1>\n

Research becomes meaningful when it reaches people. Tech Used is how BINUS ensures that research products don’t stop at the lab \u2014 they go into communities and create lasting change.<\/p>\n

The goal is not a one-time demonstration. It is sustainable, documented, community-validated impact.<\/strong><\/div>\n<\/div>\n

<\/p>\n

\n

\u2014 What Is It<\/p>\n

What is Technology Used?<\/h2>\n

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 \u2014 and whether that community actually benefits from it.<\/p>\n

\n

Tech Used is defined as:<\/strong> a research-based technology, at TRL 4 or above, that is actively used to empower a community \u2014 with planned implementation, real on-the-ground evidence, and a binding acknowledgment document (BAST) from the community itself.<\/p>\n<\/div>\n

<\/p>\n

Four criteria must all be satisfied:<\/p>\n\n\n\n
\n

\ud83d\udcda<\/p>\n

Research-Based<\/p>\n

Must be a research output with a traceable publication.<\/p>\n<\/td>\n

\n

\u2699\ufe0f<\/p>\n

Technology<\/p>\n

TRL \u2265 4. Does not have to be a brand-new product.<\/p>\n<\/td>\n

\n

\u2705<\/p>\n

Used<\/p>\n

Real, on-the-ground implementation \u2014 not just a demo.<\/p>\n<\/td>\n

\n

\ud83d\udc65<\/p>\n

Community<\/p>\n

An identifiable beneficiary group must be receiving the benefits.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/p>\n

And implementation must be:<\/p>\n\n\n\n
\n

\ud83d\uddd3 Planned<\/p>\n

Strategically planned from the start \u2014 not rushed at year-end. A planning document must be prepared before implementation begins.<\/p>\n<\/td>\n

\n

\u267b\ufe0f Sustainable<\/p>\n

Ensures continuous usage and long-term value. Includes at least one monitoring follow-up after implementation.<\/p>\n<\/td>\n

\n

\ud83d\udccb Acknowledged<\/p>\n

Validated by the community through a signed BAST<\/strong> (Berita Acara Serah Terima) \u2014 this is non-negotiable.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

\n

<\/p>\n

\n

\u2014 Why It Matters<\/p>\n

Why Tech Used matters for lecturers<\/h2>\n
\n

Triple PI<\/p>\n

One product can unlock multiple PIs at once<\/h3>\n

If your product has associated IP, comes from a research project, is at TRL \u2265 4, and is sustainably implemented in a community, it can be claimed simultaneously under Technology Used, Impactful IP, and Product Commercialized<\/strong>. Potentially PI Community Empowerment (PkM) too.<\/p>\n<\/div>\n

\n

Product Validation<\/p>\n

Real users give you feedback, no lab can<\/h3>\n

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.<\/p>\n<\/div>\n

\n

Publications & Branding<\/p>\n

Field implementation generates new research output<\/h3>\n

Every Tech Used implementation is a publishable case study. It also builds social branding for you, your department, and BINUS \u2014 demonstrating that BINUS research creates measurable societal benefit.<\/p>\n<\/div>\n

\n

Student Development<\/p>\n

Involve students and teach them real-world skills<\/h3>\n

Tech Used implementations are natural vehicles for student involvement \u2014 in facilitation, community engagement, documentation, and monitoring. Students gain hands-on experience that no classroom can replicate.<\/p>\n<\/div>\n<\/div>\n

\n

<\/p>\n

\n

\u2014 The Process<\/p>\n

How to submit via BRIDGE Apps<\/h2>\n

The entire process runs through BRIDGE Apps. Start early \u2014 don’t wait until year-end. Cut-off: 6 December.<\/strong><\/p>\n

<\/p>\n

\n
1<\/div>\n
\n

Registration & Planning<\/h3>\n

Register your profile and product on BRIDGE Apps. Then prepare your planning document before<\/em> implementation begins \u2014 this is mandatory, not optional.<\/p>\n

Planning document must include:<\/strong> team info, product details, community snapshot, implementation strategy, adoption plan, and a monitoring schedule. Download the template \u2192 bit.ly\/TechUsedKit<\/a><\/div>\n<\/div>\n<\/div>\n

<\/p>\n

\n
2<\/div>\n
\n

Implementation in Community<\/h3>\n

Run your implementation activities according to plan. Typical activities include:<\/p>\n