Customer Case 1:  TEAM WORK.

  • Scenario: The physical designer gave 10-minute notice before heading to the airport (due to family emergency), while the final RTL netlist was ready for final round of P&D. He was the only P&R/STA person on this project.
  • Solution: The design Director took over the job himself. Final RTL delivered the next day, chip was successfully taped out in about 1 week.
  • How he did it?  A key feature of ICO kept the entire records & run history. They spent 5 mins to complete the project knowledge transfer, and that was sufficient for the design director to take over the full project at the very last minute!


  • Scenario: Front-end designer decided to replace some memory with new ones
  • Solution: It takes less than ONE MINUTE for all designers to have information received and scripts updated properly
  • How he did it?
  1. Run  incremental project initialization to collect memory models
  2. Run synchronization to update whole ICO environment
  3. Run all other ICO jobs as before

Customer Case 3: DESIGN EFFORT.

  • Scenario: A newly assigned engineer worked very hard on synthesis for all blocks and fullchip. The schedule was at risk.
  • Solution: He was surprised that even high level management knew when he worked overtime, when he finished pipe-cleaning, when he launched full scale synthesis, and what problems he still has headache with.
  • Explanation: ICO does self registration. From that a tech leader can easily tell whether an engineer works in a proper way what problems left.

Customer Case 4: PLUG & PLAY.

  • Scenario: High-end networking and security chip. Need to bring up TSMC 65nm, ICC, PrimeRail, IPs and others the 1st time. 5 engineers (2 newly recruited), finish RTL to GDS2 (including DFT) in 3 month.
  • Solution: Chip taped out in 3.5 months by combining new process/EDA development with chip design. Incremental trials absorbed most business negotiation delay. One time success and mass production.
  • Explanation: ICO Plug and Play enables new process node, new technology files, new IPs and new hires. Polished methodology allows proactive problem capture and critical path catching.

Customer Case 5: KNOWLEDGE-BASE.

  • Scenario: The system administrator of company A panicked because he accidentally lost the backup of one project, and the division VP wanted a re-spin with MINIMUM changes.
  • Solution: Everything else looked identical to the management but the bug fixes. Nobody knew the design was redone from scratch other than two designers.
  • Explanation: ICO’s knowledge-base captured the methodology of this project, and basically backend designers duplicated the design with the limited lines of code in Knowledge-base