This project utilizes the built-in capabilities of Eagle to store part data. Use this project to capture your bill of materials. Use it to track inventories. Use it to create builds and consume inventory accordingly! It's not meant to replace PLM (Product Lifecycle Management) systems like Aligni but rather supplement product makers who may not be able to pay for it. (By the way, Aligni is free for open source projects!)
Using mrp parts create and mrp parts delete you can easily add and remove parts.
Creating parts manually is a pain though. Why not add them using an EagleCAD schematic!
mrp bom import -f ~/Documents/eagle/projects/pm25/pm25.sch
You can then create a new "build" based on a BOM. In my case my BOM part number is PS-AQW:
You can also check shortages using mrp inventory show -s Without the -s argument, this command will show all your inventory.
If you have inventory, you can track it here! You can add inventory one by one or use a .csv file to do the work. This is great for importing Digikey purchases, etc.
Finally you can check your shortages and then complete your build. Use mrp build complete -b <your build id> to finish up. This command will double check your inventory is up to snuff before completing your build though!
And it never may make it out of Alpha. Use at your own risk.
To build run cargo build --release. The release will be placed in target/release. As of this writing
the bin is called mrp.
You do need an .env file. You should define your DB name/location and also the database you're using inside your schematic.
Example:
DATABASE_URL=./database.db
DEFAULT_LIBRARY_NAME=wolff-den
If you have parts distributed across many libraries, this solution will not work for you.
diesel migration run to get to the latest
diesel migration revert to roll back
- Tests
- How to set up a library (what entries are required, etc)
- Multiple library support
- Importing a specific variant / or create BOMs based on different variants
- Import a BOM from a .sch file
- Adds/updates parts to DB from BOM import.
- Create BOM relationships
- Create a build based on a BOM
- Check shortages based on inventory
- Add inventory from CSV
- Update inventory from CSV
- Update a exiting inventory item
- Complete a build and consume inventory
- Unified binary
- Import inventory fails without unit_price column and notes column
- Creating inventory includes price
- Updating BOM version makes the old one inaccessible
- Create the idea of a part "alias". Whereas a part is simply an alias of another part. Could be multiple quantities too with MQTY.
- Delete a version of a bom
- Alternates +
- Part substitutions
- Searching for parts
- Importing purchase (shortage check only)
-
bom showwithout-vshows latest - Exporting shortage list to CSV for easy purchases
- Export bom to CSV
- Integration of Digikeypn
- Documentation
- Migration built in
- Prompts user to allow migration on startup on new version
- Tracking inventory change history
- Central config and database location
- Allocation with attrition
- Part reservation
- Usage descriptions in help dialog
- Inventory import csv format
- https://github.com/tafia/quick-xml
- https://www.techiediaries.com/sqlite-create-table-foreign-key-relationships/
cargo run --bin mrp bom import -f /Users/jaredwolff/Documents/eagle/projects/pm25/pm25.sch
cargo run --bin mrp build create
cargo run --bin mrp inventory show -s
cargo run --bin mrp inventory create -f test/inventory.csv
cargo run --bin mrp inventory show -s
cargo run --bin mrp inventory show
cargo run --bin mrp build show -a
cargo run --bin mrp build complete -b 1
-
Q: I use this with ?
A: this CLI application only supports Eagle
BSD-3 Licensed 🎉