Is iLogic and API something for me?

[victoria.rasmussenRVU94]

I am working in a company that manufacture boilers for customers. Very few boilers are standard. Size of boiler, dimensions and nozzle orientation is different almost every time, and causes a lot of work for each boiler. 

Now we use "copy design" from a similar boiler, and then change everything that is needed. No experience with iLogic and API. 

How will this process be improved with iLogic and API? Is it possible to built up new assemblies with only "some" inputs in an Excel file?

How do I even start?

[dalton98]

What you described seems to be the Parameters tab? You can change dimensions and link excel files with no coding needed. From there you could start using forms which is a customizable/user friendly way to change Parameters. The nozzle orientation would require a bit of coding. But yes, I bet you would find a lot of uses for it in your everyday work.

[A.Acheson]

I would say yes ilogic and as you progress further the API coupled with Vb.Net have infinite uses when it comes to automating any task that your doing manually. Configurations that might have key design parameters defined in excel and you want to define your configuration based on these parameters. You could start by simply using the forms to manually add only key parameters that are changing rather than sifting through the parameters dialogue. An example could be matching a text parameter for Boiler output say 1000kw that sizes the flow and return nozzle sizes, firebox size and wall thickness etc. 

When it comes to releasing projects to production. You can create tools to process drawings individually or in batches with tasks such as partslist checked against balloons to ensure none are missed, revision information, table creation, pdf creation and folder organization. 

Can you post a simple example even just basic configurations you might want to automate? 

[victoria.rasmussenRVU94]

Thank you for your answer!

Well for instance for this project I'm working on(simplified): 
Be able to adjust the diametre, hight(one or two shellplates?), thickness of the components, and maybe the most time consuming (back and forth with customer) orientation and elevation of nozzles. 

 

[A.Acheson]

as @dalton98  had mentioned the best place to start would be to create a form which requires no ilogic coding experience. Simply drag in the parameters you need. I assume you have it set up as a Skelton part with multiple solid bodies or are is everything individually assembled in an assembly? 

If you then want to start driving those parameters because you have set configurations you can set up a text parameter and an internal rule. Right click on the parameter and click capture current state this adds to the ilogic editor. 

If ModelType = "M1200" Then
	WallThickness = 19 mm
	N1_Elevation = 2.5 m
	N1_Angle = 45 deg
	pN2_Elevation = 2596 mm
	pN2_Angle  = 20 deg
ElseIf ModelType = "M1500"
	WallThickness = 25 mm
	N1_Elevation = 1.5 m
	N1_Angle = 90 deg
	pN2_Elevation = 1000 mm
	pN2_Angle  = 100 deg
End If

[victoria.rasmussenRVU94]

Thanks for the tips!

Right now it is an assembly with individual parts with no linked parameters. I have had a try on skeleton part that is derived, but found it somewhat difficult to work with. But is that maybe the first step for me? Or should I link the parts to an excel form? Not sure about pros and cons with those methods. 
https://www.youtube.com/watch?v=CMApjCzcG0c

[basautomationservices]

If you do not have time/motivation to do it all yourself feel free to reach out

[A.Acheson]

I would personally use a skeletal model to drive as many aspects of the design as possible. Deriving the skeletal model would be beneficial with manually using this approach but with ilogic you can link the parameters directly to the part file. I have found that assembly level sketches and work planes can get a little unwieldy especially if you start replacing parts etc. Really I think it is whatever works for you.