OpenAccess Coalition: Goals and Status

Slides:



Advertisements
Similar presentations
Configuration management
Advertisements

OpenAccess Workshop Presentation, March Joining OpenAccess: the R&D balance sheet Ivo van Zandvoort VP Engineering Sagantec Netherlands.
HP Quality Center Overview.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Copyright © 2014 Pearson Education, Inc. 1 Managers from across organizations are involved in developing and acquiring information systems Chapter 5 -
Presented by: Nick McHugh Date: 15/11/2005 Security, Safety, Confidence.
1 ITRC Mission ITRC is A state-led coalition working together with industry and stakeholders to achieve regulatory acceptance of environmental technologies.
When Should We Adopt Open Access? Igor Markov University of Michigan.
Emerging Standards in the Electronic Design Automation (EDA) Industry Phil Fisher (SEMATECH) Don Cottrell (Si2) UC Berkeley October 20, 1999.
Microsoft Office Open XML Formats Brian Jones Lead Program Manager Microsoft Corporation.
From Concept to Silicon How an idea becomes a part of a new chip at ATI Richard Huddy ATI Research.
INFORMATION SYSTEMS DPM ARCHITECT: STATUS AND NEXT STEPS Presented by Bartosz Ochocki Authored by Víctor Morilla Rome, May 2014.
Michael Solomon Tugboat Software Managing the Software Development Process.
Know More. Do More. Spend Less. January 24, 2006 Monica Loomis, Senior Sales Consultant Oracle Contract Management.
Sl.NoUnitContents 1.Unit - 1 What is Open Source?, Why Open Source? 2Unit – 2 What is Open Standard? - Why Open Standards? 3Unit – 3 Peek into history.
OSIAM4HE Proposed org structure Authored by the strategy and organization team.
TEAM FOUNDATION SERVER (TFS) By Sunny Niranjana Devi. M.
The Software Development Life Cycle: An Overview
Interoperability with CMIS and Apache Chemistry
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Typical Software Documents with an emphasis on writing proposals.
IBM Governmental Programs Open Computing, Open Standards and Open Source Recommendation for Governments.
“Integrating Standards in Practice” 10th Open Forum on Metadata Registries July 9-11, 2007 New York City, NY USA An international conference to share and.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
1 Performing Procurement Due Diligence with an Open Source ERP?
Promoting Web Services Interoperability Across Platforms, Applications and Programming Languages Basic Profile 1.0 August 12, 2003 Copyright © 2003 by.
Versus JEDEC STAPL Comparison Toolkit Frank Toth February 20, 2000.
EDA Standards – The SPIRIT View Gary Delp VP and Technical Director SPIRIT.
Georgia Institute of Technology CS 4320 Fall 2003.
1 / Name / Date IDA Interface for Distributed Automation The journey toward Distributed Intelligence.
Database Administration
GenX- XML Mapping of GenCAM Andy Dugenske Andy Scholand Manufacturing Research Center Georgia Institute of Technology January 23, 1999.
RequisitePro Software Requirement Management Tool A peresentation by: Mojdeh Jalali-Heravi Maryam Daneshi.
State of Georgia Release Management Training
ELECTRONIC SERVICES & TOOLS Strategic Plan
Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner Boot Camp Training Courseware.
ISCUG Keynote May 2008 Acknowledgements to the TI-Nokia ESL forum (held Jan 2007) and to James Aldis, TI and OSCI TLM WG Chair 1 SystemC: Untapped Value.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Systems Development Process and Methodologies Dr. T. Ravichandran.
The System Development Life Cycle
TEXAS NODAL (ERCOT REVISIONS)
Software Project Configuration Management
Game Design, Development, and Technology
Managing the Project Lifecycle
Integrated Management System and Certification
Francis Bordeleau Chairman, Papyrus IC May 11th, 2016
Guiding Principles The Acquisition, Technology & Logistics Team must INNOVATE AND COLLABORATE to deliver EFFECTIVE, AFFORDABLE tools for the joint warfighter.
Ian Bird GDB Meeting CERN 9 September 2003
Reuse of IEEE Content in Vendor Documentation
Proposed SysML v2 Submission Plan
ESMF Governance Cecelia DeLuca NOAA CIRES / NESII April 7, 2017
API Documentation Guidelines
Project Roles and Responsibilities
CMMI – Staged Representation
The System Development Life Cycle
Guidance notes for Project Manager
Verilog-AMS Integration with P1800 SV Standard
Teneo Ganymede Simultaneous Release Graduation Review
Governance, Intellectual Property and Membership
Metadata The metadata contains
Portfolio, Programme and Project
Strategy
Creating fhir® Clinical Documents with Trifolia & Camara
{Project Name} Organizational Chart, Roles and Responsibilities
Mark Quirk Head of Technology Developer & Platform Group
NM Department of Homeland Security and Emergency Management
Presentation transcript:

OpenAccess Coalition: Goals and Status Sumit DasGupta VP of Technology Silicon Integration Initiative (Si2) Austin, TX 1/13/2019

OpenAccess Coalition (OAC) Structure and Process Outline OpenAccess Goals OpenAccess Coalition (OAC) Structure and Process OAC Participation OpenAccess Technology OpenAccess Status 1/13/2019

OpenAccess Goals Provide an IC design tool infrastructure that yields Integrated systems rather than sequential flows Choice of design tools and provider Technology transfer of innovative research Collaborative design capability for ICs Promote an open standard for IC design data access Gain adoption of the standard within the EDA industry and university research programs 1/13/2019

EDA Interoperability Genealogy Design to Manufacturing Data Sharing Process level integration Multi-vendor integrated systems 2002 Open Data API Single vendor integrated systems Proprietary Data APIs Loosely coupled systems Open File Formats Tool-Data Binding Proprietary File Formats 1/13/2019

Openness Defined... Accessible by all parties: Anyone can use, change, embed, or redistribute according to clearly established terms Reasonable cost: Established prices (if any) are based on service value and do not present an undue barrier to any company, regardless of size Managed migration by stakeholders: Controlled evolution of the technology by an elected Change Team 1/13/2019

Founded on a Technology Transfer from Cadence Design Systems What is OpenAccess? Commercial EDA Tools Internal Proprietary Tools University Research Cores/Cells Gates Transistors Layout Standard API HDL Mask . Reference Database Founded on a Technology Transfer from Cadence Design Systems 1/13/2019

OpenAccess Structure/Membership Cadence HP IBM Intel LSI Logic Mitsubishi Motorola Nassda Numerical Tech Philips Sagantec ST Microelectronics Sun Synplicity Tektronix Verisity Artisan* OpenAccess Community Governing Coalition 12 Member Change Team Two Architects 1/13/2019

OpenAccess Coalition Coalition members have specific rights and responsibilities Share in funding Operate to open, unbiased decision-making policy Abide by OpenAccess Participation agreement terms, and joint funding for development and facilitation Guide future of API and Reference Code Elect Change Team to manage revisions Coalition member benefits Early access to planned/future releases of reference database code Participate in Change Team Set direction and vote on development priorities All things equal, higher priority for member requests Discounted training, support and access to Si2 1/13/2019

OpenAccess Change Team Responsibilities Approving body for API & Reference DB changes Specifies changes to code integrator Caretakers for OA Technical Roadmap Makeup 12 annually-elected Coalition company representatives 1 representative per company, 1 vote per company Max of 5 EDA companies (4 plus Cadence) Chaired by 2 architects who must be CT members (Cadence and 1 elected non- EDA company) Approval of change requires 9 “Yes” votes 1/13/2019

OpenAccess Community Any person/enterprise can download OpenAccess package Click-through Internal Use License Free access to API Free access to reference database binaries for Internal Use Signed Distribution License Free access to reference database source code for Internal Use Royalty-free distribution rights for OA reference database binaries with derivative works Rights to fix bugs (cannot alter API syntax, semantics or behavior) and distribute corrected binaries to customers 1/13/2019

Si2 Role Manages licensing of OpenAccess packages Facilitates and supports the OpenAccess Coalition Facilitate, assist and participate in DWGs and activities Oversee the Change Team Puts in place a program to resolve: Level-1 support for critical bug reports against standard package Resolve interoperability issues Assure compliance of delivered code to the specifications Coordinates with other standards organizations 1/13/2019

OpenAccess Process Community . . Change Team Coalition OpenAccess Packages Contributions Issues Code Repository Issue Tracking System Cadence or Contractor Change Team Coalition 1/13/2019

OpenAccess Technology OA features: Standard information model for IC design data Standard C++ interface (API) to access and manipulate data Reference commercial-grade database compliant with API Development support aids OA provides: Greater design productivity Standard Model & API provide for choice & tighter design flows Reduced development and support cost Reference DB provides solution for IC designers and EDA developers right out of the box Better interoperability Reference Database provides “golden behavior” for development & test, & for interoperability issue resolution 1/13/2019

Open Access Deliverables The Standard The Reference Implementation Information Model (Graphical) Runtime Memory Data Model (C++ Headers) API Implementation ( Solaris / HP-UX, C++ Binding ) API Specification (C++ Binding) The OpenAccess Standard The standard is the API, which is defined by several documents Information model: describes objects, attributes for each, and relationships for the design data model API Language Reference Manual: defines the function, syntax and semantics of each function (Method) within the API Header files: machine sensible description of the APIs and standard structures and enums Test cases: covering nearly 100% of the API functionality explicitly define the API’s behavior Freely available to anyone Ultimate goal is to gain IEEE accreditation as an industry standard The OpenAccess Reference Database Fully supports the API Production quality Freely available to all Available in binary and source form Royality-free redistribution rights for binaries Persistent Store Application(s) 1/13/2019

OpenAccess Code Availability Status/Schedule OpenAccess Version 1(C) OpenAccess API Specification and Code (C++) (OAC and Community) OpenAccess Reference Database (C++) (OAC and Community) Added function: OpenAccess API Specification/Code and OpenAccess Reference Database (OAC and Community) Now 06/30/2003 1/13/2019

OpenAccess Information Sources www.si2.org/openaccess www.openeda.org OpenAccess training classes 1/13/2019