![]() ![]() Each assembly has a mini gantt chart created by the project manager assigned to that job so the system knows roughly the steps (i.e. The PM define the hours for each task and dependencies so it knows whats sequential or what can be run parallel. Knowing for all projects when its due, and the resources needed as well as sequence of steps is the raw material for a scheduler. That and real time feed back as things happen and people spend hours on it. Its tied to the quote and order system so effort is not duplicated - i.e. the detail you put into quoting gets refined into a BOM gets refined into a project plan etc so when a shipment of steel arrives the shipper knows what job each piece is for and where it goes to next (stock, plasma, saw etc)- we're fabrication so pieces can be large and heavy and duplicate handling can kill you.Īnyways, that's the basics of what I came up with, half exists in the really world, half in my head but its coming along. What did you find with the workflow, any insights or ideas what works/doesn't work? i've a brilliant young software engineering building it in SQL so its all browser based, kiosks around the plant, dashboards on phones etc. Our database acts as a central hub to manage job scheduling, workflow, inventory, human resources, customer relationships, sales & marketing, finances, quality control and machine maintenance. Material Size (the base includes a comprehensive list of material sizes to choose from) Material Grade/Type (the base includes a comprehensive list of material grades/types to choose from) Here you enter new parts/products into your base with the applicable data With regard to workflow, a part is uploaded into the base using a form. Teams can then utilize various views (Grid, Gallery, Kanban and Calendar) to display and/or edit the information. Each job tracks machining time, material costs, fixture cost, tooling (with links for purchasing), etc. Perhaps another opportunity to use API calls?.To do scheduling, you simple drag and drop the job's card in the the machine it is going onto next. I also need to find a way to collate Toggl time into a format that can be used to generate a QuickBooks Online invoice via automation. Toggl integrates much better with Asana, and offers Tagging of time entries allowing more meaningful data to be recorded for reporting purposes. Now I’m getting ready for phase 2 of this project: Replacing Harvest with Toggl for time tracking. This was not easy for me, but I stuck with it, and I’m so happy I saw this through to completion. Also, plenty of standard modules for all the services. I use Asana, Dropbox & Harvest API calls to get the desired functionality. To trigger the workflow, I made an Airtable Form that collects project-specific data and fires an email to the web hook address that kicks off everything else in Make. I have been using to drive Asana + Harvest (time tracking) Airtable (reference data storage & data syncing hub) + Dropbox to build a Project kickoff workflow that builds my Asana project, customized per client using client-specific data stored in Airtable bases) then builds an associated Harvest project for tracking time to the project and finally builds a folder structure for my working files in Dropbox, following client-specific templates. I’m not a coder, though I am pretty technical in many other computer productivity realms. ![]() I’m going down the exact path you suggest. Let me know in the comments if you are interested, let’s get that code vibe going! I won’t lie: this is not straightforward, but that’s definitely the easiest way in, and we can help by guiding you! For example, let’s say that a “Duplicate task” action doesn’t exist in Zapier: no problem, you can use an action of type “Webhooks by Zapier” and call the Asana API directly. But with actions, you can create your own. You can’t really easily create your own triggers, you are stuck with Asana’s. ![]() Asana has created a few triggers and a few actions. Let me explain.Īn automation in Zapier is made of 2 things: trigger(s) and action(s). Which is perfectly understandable!īut did you know that there is actually an easy way in? Instead of writing code, you can use a tool like Zapier (or equivalent) to do calls to the API. That’s a highly under-rated feature, that most people overlooks because they don’t have the skills to understand how it works and don’t know how to code. I can talk all day about how great the Asana API is. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |