Using OpenChain for IP Management
summary
OpenChain (ISO/IEC 5230) is presented as a checklist style compliance framework that Ericsson uses to align open source use with IP management, claiming concrete wins: ISO/IEC 5230 defines required policy, training, intake/internal/outbound processes, documented artifacts and self-certification; Ericsson reports scaling from 6,000 to 22,000 top‑level components and holding 60,000 patents generating about $1B/year, so OpenChain is used to get patent/IP teams to accept OSS, reduce legal friction in procurement and M&A, and create measurable business value.
AI-written summary · about
chapters (14)
- 0:00OpenChain for IP management
- 1:04From patent attorney to advocate
- 3:13OpenChain as ISO standard
- 7:04Ericsson’s IP strategy
- 9:11OpenChain requirements for IP teams
- 12:42Why IP departments fear open source
- 14:06Translating OpenChain to IP terms
- 19:03Turning IP teams into allies
- 22:31Overcoming cultural and ideological gaps
- 26:43Aligning IP and open source
- 28:52OpenChain community resources
- 31:20Industry best practices with OpenChain
- 32:45Finding OpenChain allies
- 33:51Q&A on ORT and alignment
related talks
42mOpen Source Compliance Management - Removing the Thorn from...
33mHow OpenChain Became The International Standard for Compliance
17mUnderstanding How OpenChain ISO/IEC 5230 and ISO/IEC 18974 Support InnerSource
31mOpenChain’s Strategic Direction for 2027 in Global Practices
30mHow To Talk To Your Lawyer about Open Source
29mTrusted Supply Chains - How OpenChain Makes a Difference in a...
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
50mHow to talk your lawyer about FOSS