BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20260730T152729Z
LOCATION:Seaside Ballroom B
DTSTART;TZID=America/Los_Angeles:20260727T141500
DTEND;TZID=America/Los_Angeles:20260727T143000
UID:dac_DAC 2026_sess271_ENGPRES112@linklings.com
SUMMARY:Advanced Hard IP Integration Requirement Extraction and Checker
DESCRIPTION:Mili Johnson, Ben Thomas, Kavithaa Rajagopalan, and Pankaj Tal
 war (Texas Instruments (TI))\n\nMotivation: In SoCs 3rd party and TI inter
 nal hard IPs such as PHY, PLL, Dividers, etc are often required and integr
 ated. An integration and specification document is often shared which cont
 ains the intricacies to be taken care during implementation. However, the 
 integration requirements are often scattered across multiple pages, embedd
 ed on figures/tables, etc. The current manual approach of extracting, revi
 ewing, and translating these requirements into actionable checklists is ti
 me-consuming and error-prone. The requirements can be scattered across dif
 ferent documents too. Eg ODP and efuse controller are expected to be in th
 e same power domain but, the requirement is present in the fusefarm docume
 nt and not in the ODP document. These need to be clubbed together and migh
 t be missed unless the user has read all documents. \n\nSolution: An AI ba
 sed automated approach in two phases. Phase 1 leverages AI-based document 
 parsing to intelligently extract and categorize integration requirements i
 nto multiple categories - floorplan, IR, timing, placement etc. with autom
 atically correlating cross-document dependencies. Phase 2 employs AI to tr
 anslate these requirements into automated TCL-based checkers and where fea
 sible, provide TCL based fix coding scripts. \n\nImpact: The Physical Desi
 gn (PD) team emerges as the most significant beneficiary of this AI-powere
 d solution, as they are directly responsible for implementing majority of 
 integration requirements extracted from specification documents. Experimen
 tal validation across various design integration documents have shown sign
 ificant time saving up to 2 weeks and zero requirement omission rates, mak
 ing it a scalable solution. \n\nFuture scope: While the current system req
 uires prompt refinement and domain expertise for evolving IP types and doc
 umentation formats, future enhancements will incorporate automated prompt 
 optimization to minimize specialist dependencies.\n\nTopics: AI, Design, E
 DA\n\nSession Chair: Karunveer Singh (Meta)\n\n
END:VEVENT
END:VCALENDAR