Imagine you're working on a design faced with tight timelines and a challenging problem: your Physical Design engineers are in one city, and the Architecture team is 3000 miles and 3 timezones away. You are in the middle of tape-out and the physical design team needs input from the architecture team to fix the floorplan for some critical paths and to validate that the problems they are seeing are indeed real problems. Sharing screens can work once in a while, but it gets tedious over the entire tapeout. Is there a better way?

Ever feel like you’re swimming in data but without the ability to understand what it all means? Most vendors believe that theirs should be the only tool you use, which typically means writing lots of scripts to try to extract insight from a deluge of data. Meet George. He had exactly this problem, right in the midst of trying to tape-out his design. How did he solve this problem?

Collaborating with your team is good, and having access to all the data sets the stage, but now you've got work to do. It's time to implement. Often times, the knobs that you can turn on your EDA tools have indeterminate results. One of our customers was trying to close timing on a very critical datapath block and was lamenting that he knew what to do but needed better control to be able do it. It’s an increasingly common problem. How did Tuscany help him out...?