www.cadwolf.com<p>When an engineer/scientist/worker solves a problem, they generally use Excel, Matlab, MathCAD, or python to do their work. They then document their results in Word and email that to their boss. This causes problems in that documentation and analysis almost always get out of sync, and bosses/customers will have a license to check your work.<p>CADWOLF solves these problems by doing all of these things in the browser. Users create web pages called "documents" and add blocks to the document through a gui. These blocks can be text, tables, plots, equations, etc. Equations solve top to bottom in the document and update in real time.<p>In short, it replaces all of the above platforms with a web page - with nothing to download or install.<p>For engineers, the platform does considerably more. Whenever a large structure - like a space vehicle - is built, every part is given a unique number through a part numbering scheme. Our part tree module lets the user create this scheme and then add systems and components to the structure.<p>This gives us two big functionalities : the ability to query the structure for items like "weight" in real time; and the mathematics will update along with design changes.<p>What would we do with the grant:<p>Complete an AWS server side to solve large problems, publicize the site, and begin working on a CAD system to go along with the mathematics. This will be unique in that it will be browser based and linked to a backside mathematical model. As the design changes, the math and the CAD will update as well.<p>This will drastically reduce the time and manpower it takes to design cars, space vehicles, planes, etc.<p>The system is in beta now and you can see several videos and demos on the main page.<p>Short intro video here - (2 min)
<a href="https://www.youtube.com/watch?v=pdFf7jfA5EE" rel="nofollow">https://www.youtube.com/watch?v=pdFf7jfA5EE</a><p>Longer video giving full explanation (15 min)
<a href="https://www.youtube.com/watch?v=MkdSZhrsxrU" rel="nofollow">https://www.youtube.com/watch?v=MkdSZhrsxrU</a>
Thanks to everyone that has asked a question. I wanted to add a little more info on how this will speed up engineering in the future.<p>A "fitting" is a small component that usually attaches a rod to another item. The fitting consists of a base plate and two vertical extrusions. There is a bolt at each corner of the base plate connecting it on that end and an eye bolt sits between the two vertical extrusions and screws into the rod.<p>I CADWOLF, you will be able write a single web page or "document" that takes in the load on the fitting through the rod and then calculate the base plate size, the thickness, the size of the vertical extrusions, and the sizes of the bolts needed. These items will populate your part tree automatically. When the load changes, everything updates automatically. If you change this document, the design updates.<p>Now imagine that you are building a large structure with dozens of these fittings and any engineer can simply place the fitting into their structure in the same way that you call a function. You don't have to worry about whether or not the engineer did the design properly as everyone is using the company standard analysis and the engineer can go about doing the more complicated things.<p>Now imagine that CADWOLF provides a large array of built in structures like this where a single engineer can design large and complicated structures faster than teams of engineers do today.
I'm no domain expert here, just a random HN user. But I think this looks cool though, is trying to solve a real problem.<p>My first thought: This is a very big problem space to be tackling all at once. Massively huge.<p>I could see it taking a lot of engineering time to build out a featured product, which has parity with the incumbents at the things they do well. Also your target customers are very process oriented, so you've a big challenge to sell to them. For any given engineering application, you're probably going to be missing some features or feature-richness they consider 'key', for at least the medium term.<p>Unless something has changed that means they can achieve their needs with a lot less functionality?
E.g. Spreadsheet software, by virtue of the inherent power and simplicity of the metaphor, turned out to be good at a lot of things, and killed a lot of special purpose apps. Even then it took a lot of resources to write an early spreadsheet package. And its really difficult to build horizontally successful products like that.<p>So the common pattern to tackle this is to pick a really narrow niche you can specialize in and dominate, within the wider market. Ideally a new or underserved niche, or one that has changed recently in some important way, which means it isn't being served optimally by existing solutions. And getting enough better than an incumbent in just that niche that you can get some traction, get funding, bootstrap your development, and [>5-10 years later] eventually build the more general product.<p>Have you thought about doing that? Its not always the best thing to do, but it should be given a lot of thought?
How does this integrate with existing tools?<p>> This will drastically reduce the time and manpower it takes to design cars, space vehicles, planes, etc.<p>I don't understand how this follows. Can you give an example of the savings your software will offer?<p>How well do you understand this market? Have you worked in it before?<p>To me, it's obvious that writing things in a word doc and emailing it to my boss sucks. But do you know why it's done this way? Are there better options without traction? Is there something about accountability that I'm missing?
Interesting concept. The aggregating of documentation and analysis together reminds me of a Jupyter notebook. If you add in a fully-featured CAD plugin and connect everything to AWS or whatever, does that approximate your product plan?