Like any good ingredient, there are a variety of ways AllSpice can help improve the recipe that is your hardware development process. Here are some of the ways our customers have baked AllSpice into their design process.
1 - Organizing and documenting designs with markdown and integrated wiki
As hardware developers, you know documentation is an inevitable and necessary step in communicating your design. Still, design input alone shouldn't feel like a full-time job.
From talking to your team via email chains to PDF exports to in-person meetings, keeping track of your design intent can get messy fast. When the notes are coming from multiple places rather than a standardized location, things can get confusing and important feedback can get lost. Sifting through all the conversations and trying to organize and understand them (or let alone even remember them) is not how you should be spending your time.
With AllSpice, our customers can keep track of their design intent in a standard format like Markdown. By using this format to integrate documentation into their day-to-day design work, users no longer face the hassle of gathering information from multiple sources like email and PDFs.
Sounds like a win-win, right? 🙌
What our customers love about it:
Documenting feedback in a way that's easily accessible and organized
Integrating notes with their company's wiki
Knowing what changes are introduced in each revision to speed up troubleshooting if problems arise
Capturing design intent as development progresses
2 - Hosting digital, asynchronous design reviews
Say it with us: 👏 design reviews don't have to be an enormous effort. 👏
From finding time in everyone's busy work schedules to preparing a 45 slide deck with schematic screenshots, hardware design input is an unnecessarily lengthy process.
With AllSpice, our users accelerate their design reviews and run them asynchronously on a digital platform.
What are you going to do with all that extra time?
What customers love about it:
Being able to input and review the latest design data at any time, without having to boot up an ECAD tool
Tracking issues and product release approvals in the same system as their revision-controlled designs
Seeing the updates between revisions in a visual format
Using the automated diffs to verify that all the intended changes make it in
Making sure the unintended changes don't 😉
Steering clear of screenshot-packed slide deck review packages
Skipping unnecessary in-person meetings
Looking like rockstars in front of other teams because of their extraordinary design review organization
3 - Sharing diffs with external stakeholders (techs, operations)
When it comes time to share your designs with external stakeholders like technicians or operations teams, you shouldn't have to spend hours detailing the changes you made between rev 2.0 and 2.1.
Using AllSpice's releases, our customers can share production packages with external groups, preventing both parties from having to do extra work like building designs from scratch or guessing what the revisions were.
What customers love about it:
Breaking down the traditional silos and demystifying what's happening in hardware design
Letting people outside their direct electrical engineering team look at PCBs and schematics on a web browser
Making it easy for mechanical, software, and firmware engineers to give feedback on the reviews
Not spending hours manually summarizing updates between revisions for external stakeholders
Sharing diff packages via URLs that can be viewed from any device with technicians on the shop floor
Setting groups with different permission levels to manage what information is shared
Using Github, Gitlab, and Bitbucket authenticators to streamline their credential management
Curious about some of the other ways AllSpice can improve your hardware development? Let us know below so we can tackle them in a future post, or send us an email at email@example.com.