![\"\"](\"https:\/\/binus.ac.id\/techtransfer\/wp-content\/uploads\/2026\/05\/image_2026-05-21_133741998-300x168.png\")
Most BINUS lecturers manage their PI claims the way most people manage their taxes \u2014 they account for what they have, they submit it, and they stop there. The problem with this approach is that the BINUS performance framework, particularly around research products, is structured to reward people who think one step further. One product, properly packaged, can simultaneously fulfil three distinct Performance Indicator categories. Most lecturers are claiming one.<\/span><\/p>\n The triple PI configuration \u2014 RTT’s informal name for the simultaneous claim across Product Commercialized, Impactful IP, and Technology Used \u2014 is not a workaround. It is the intended outcome of how BINUS has designed its research performance architecture. A product with a registered HKI (Hak Kekayaan Intelektual \u2014 Intellectual Property Rights), a TKT (Tingkat Kesiapterapan Teknologi \u2014 Technology Readiness Level) of at least 4, and documented use or implementation by a non-BINUSIAN beneficiary meets the threshold conditions for all three PIs simultaneously. If that implementation is community-facing, a fourth claim under PI Community Empowerment (PkM) becomes available as well.<\/span><\/p>\n To make this concrete: consider a lecturer from BINUS’s Computer Engineering programme who has developed a smart fall-detection system for elderly patients using IoT sensors. The system sits at TKT 5 \u2014 a validated prototype tested in a controlled environment. The lecturer has filed a patent application, written a technical specification document, and completed a pilot deployment at a Jakarta nursing home. This single output generates a Product Commercialized claim (TKT \u2265 4, HKI, market documentation), an Impactful IP claim (patent application plus documented societal relevance), a Technology Used claim (nursing home deployment with a non-BINUSIAN beneficiary), and \u2014 if the nursing home partnership qualifies as community-facing research \u2014 a PkM claim. That is up to four PI categories from one research project. In BKD (Beban Kerja Dosen) terms, this represents a meaningful reduction in the number of separate activities a lecturer needs to generate to meet annual obligations.<\/span><\/p>\n This matters most for lecturers approaching senior functional positions. At the Lektor Kepala and Guru Besar (Profesor) levels, cumulative credit requirements for Jabatan Fungsional become significantly heavier, particularly in the research and community service categories. Lecturers who treat each output as a single-PI event are working harder than necessary. The triple PI structure rewards strategic documentation \u2014 identifying all the PI categories a single product can support and building the evidence base for each claim at the same time.<\/span><\/p>\n The sequencing matters too. Evidence for Product Commercialized (rubric parameters, TKT documentation, HKI, market notes), Impactful IP (the same HKI registration plus a societal impact statement), and Technology Used (beneficiary documentation, adoption records) overlap substantially. A lecturer who builds the full evidence package once \u2014 with RTT support \u2014 can submit across all three categories without duplicating effort. The only additional work is reframing the same documentation for each PI’s specific submission format.<\/span><\/p>\n Among the 270+ prototypes documented in BINUS RTT’s portfolio, the strongest performers in the annual Product Commercialized assessment are consistently products where the submitting lecturer understood that documentation was the strategic asset, not the technology alone. The rubric allocates 15% each to IP ownership and TKT \u2014 but it is the quality and completeness of supporting evidence that separates a Score 3 from a Score 5.<\/span><\/p>\n For lecturers who want to build this strategy into their research planning rather than discovering it at the December deadline, the time to start is during product development, not submission month. RTT offers Product Strategic Roadmap consultations specifically for this purpose \u2014 a structured session that maps your product’s current state against all relevant PI categories and identifies the documentation gaps you need to close before December 6.<\/span><\/p>\n One eligibility note worth stating clearly: the same Score awarded to a product can apply to a maximum of three departments. For cross-departmental products \u2014 a design-engineering-computer science collaboration, for example \u2014 a single well-documented innovation multiplies its value across multiple study program KPI targets simultaneously, making collaborative product development one of the highest-leverage moves in the BINUS research ecosystem.<\/span><\/p>\n For the full framework, eligibility criteria, and submission process, contact our<\/strong> Product Commercialization team at BINUS Technology Transfer.<\/strong><\/span><\/p>\n #BINUSresearch #triplePI #PIstrategy #BKDdosen #JabatanFungsional #KPIdosen #BINUStechtransfer #productcommercialization<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" Most BINUS lecturers manage their PI claims the way most people manage their taxes \u2014 they account for what they have, they submit it, and they stop there. The problem with this approach is that the BINUS performance framework, particularly around research products, is structured to reward people who think one step further. One product, […]<\/p>\n","protected":false},"author":2,"featured_media":432,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[71],"tags":[83,86,84,85,82],"class_list":["post-431","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tech-transfer-essentials","tag-bkd-jabatan-fungsional-binus","tag-impactful-ip-technology-used-pi","tag-kpi-penelitian-binus","tag-lektor-kepala-pi-strategy","tag-pi-klaim-binus-dosen"],"_links":{"self":[{"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/posts\/431","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/comments?post=431"}],"version-history":[{"count":7,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/posts\/431\/revisions"}],"predecessor-version":[{"id":493,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/posts\/431\/revisions\/493"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/media\/432"}],"wp:attachment":[{"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/media?parent=431"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/categories?post=431"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/binus.ac.id\/techtransfer\/wp-json\/wp\/v2\/tags?post=431"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n