Forum Discussion

NathanielHammer's avatar
NathanielHammer
Qrew Cadet
6 years ago

Creating a "Component" of with a varying amount of other components from other Tables and Applications

I have been an App designer on Quick Base for approaching 3 years. My Applications are starting to get bigger and more complex. The newest application I have been tasked with entering and creating is something along the following lines:

-Be able to create an inventory list for departments utilizing vendors, mfgs. price. min order qty. etc
-Be able to create a department work order (or Component I would call it) out of the above 'purchased inventory list'. 
-Track the hours it took to create that component with the employee(s) that worked on it (I already do this a lot).
-Be able to create a larger "component" comprised of other components (purchased or made here in-house by different departments ie the one listed above) into a Larger List of components. All of which will eventually have a home on a machine we build and be inventoried to that machine along with its hours it took to get it to Finish Goods ( Again, I already have an application tracking all hours by every department down to the employee hour level. So, I just need to add an inventory list to that machine....eventually).

Lay of the Land for my application is this:
Main Application Tracks: Employees, Departments, Customers, Customer jobs, Customer job work orders,  Job Hours, Work Order Hours, Employee Work order hours
My Other Two Applications are almost identical. They Track the in-house side of departmental work. I have electrical and I have tooling.

Tooling: Creates Stock Components, Creates Work Orders to Make stock components then tracks time for employees

Electrical is where I am starting the above venture due to the nature of the department. They have to use both purchased and in-house components of varying quantites to create a larger component in an almost endless combination(currently the field count is in the upper 70s). I want to track that combination as a work order and relate every component they use to either tooling or a purchased component.

Once I figure out how to create components from other components and then into even larger more complex components I will track the hours it took to get there.

I am asking the community for some help in arranging my next application. Mostly, how would you go about creating larger components from a multitude of smaller components from different departments and purchased components. Do you think the data will be usable when one record is just a non-stop combinational nightmare of components?

If you are curious what my company does, we are a tier 3 automotive supplier that works to create production machines. Our work can be seen on companies like Honda, Tesla, Ford, GM, FCA, Nissan, the list goes on.

Thank you for any repsponse in advance!

------------------------------
Nathaniel Hammersmith
------------------------------
  • I have done apps like that for costing purposes of the assemblies.  
    You can have a table related to itself, and that can allow you to build say a Tier 2 Assembly out of other Assemblies and perhaps also some extra components.

    Then you can use that in a higher level Assembly and if you go high enough, I guess eventually you would have the whole car.

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    markshnier2@gmail.com
    ------------------------------
    • NathanielHammer's avatar
      NathanielHammer
      Qrew Cadet
      That's ultimately what they want to get out of the application. We know the labor side(thanks to the first app) and a round-about number of the material side due to varying nature of every machine. It takes a lot of man-hours to count the components on a machine (purchased or built in-house). 

      I forgot the mention cost: TJ wants to reflect varying costs changes in purchased components into the overall cost of the machine.

      Thank you for the tip!

      ------------------------------
      Nathaniel Hammersmith
      ------------------------------
    • NathanielHammer's avatar
      NathanielHammer
      Qrew Cadet
      I also mentioned creating a work-order to create such smaller components. The best Example I can give is the same place where I am stuck in my app.

      The electrical department builds our Control Panels with a work order.
      The work-order tells them the amount and type of components to use. 
      - I have a table of all the electrical components, part numbers, price, mfg etc.
      - I have another table that allows my electrical supervisor to create a work order. The form leads him to select the different options that a control panel can have and how many of each he wants in it.
      Currently these two tables are unrelated. How do I go about getting every component to be related in the work order dependent on the type of component it is? I don't want any 'Ethernet switch' component to show up when I ask him what 'PLC' he wants to use.

      I have to do this component selection process for about 35 fields in the form.

      ------------------------------
      Nathaniel Hammersmith
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        Quick Base nicely supports Conditional Drop downs.  So, if you have selected in a field a type of PLC, you can then set the field for the drop down relationship to be conditional

        Look for

        The values in this field depend on a selection in another field

        as a field property for the field [related component] - the reference field in selecting a part.

        ------------------------------
        Mark Shnier (YQC)
        Quick Base Solution Provider
        Your Quick Base Coach
        http://QuickBaseCoach.com
        markshnier2@gmail.com
        ------------------------------