In this chapter, we will be taking a look at the database concepts and design of KipwareCYC®. These databases are designed to maximize and ensure the accurate calculations for non-cutting or idle time, and material cutting times in cycletime estimates.
Our recommendation for entering information into the database is to create machinery and cutting parameters based around the current estimate being created. For example, today you are working on an estimate for rough and finish turning 3 0 3 stainless on your Haas lathe. Enter the specs for that Haas lathe into the machine database. Then gather the cutting parameters for rough and finish turning and enter them into the cutting parameter database. And now you can create the estimate with that machine and cutting parameters and they are entered into the database for future use. So you are populating the databases as you are creating quotes and estimates. This ensures that the database contains accurate information. And only the information pertinent to your shop without any unnecessary data, Unnecessary data will only clutter the database and make finding the needed information more complicated.
The first database we will review in KipwareCYC® is for machine parameters.
As you can see the values in this database reflect the specifications for the machinery to be used in cycletime estimates. Available machines can be for turning, milling, live tool centers, saw, edm or waterjet type machines. You can also use a general classification just to give the user the ability to include a general non-cutting time when estimating non-standard equipment.
Although this database is primarily designed for CNC machinery, the database is flexible enough so that manual machinery of all types can be included. For example, a manual turret lathe where the time to manually index the tool holder is included as ATC or tool change time. The speed at which the operator can move the slides can be included as rapid speed. Including manual machinery as mentioned ensures consistency and accuracy across all cycletime estimates involving this type of equipment.
The second database is for cutting parameters.
This database is designed around the concept that most shops have a favorite insert or grade to perform common tasks on common materials. For example, when rough turning 303 stainless … the shop floor probably has a favorite insert and grade. This tool can then be added to the cutting parameter database and used for rough turning 303 stainless.
To add another level of flexibility, each main operation like rough turning can include 10 sub categories of tooling and cutting parameter configurations. This gives the user the ability to include multiple tool configuration options for say, rough turning of 3 0 3 stainless.
In addition to the pre-defined turning and milling operations, the user can configure two user defined operations. One using surface feet per minute and inches per revolution feedrate, most commonly an operation where the workpiece is rotating. And the other using inches per minute feedrate … most commonly where the tool is rotating.
Sawing operations can also be included under the sawing specifications.
Cutting parameters can be stored for square and rectangular solids, round solids, and tubing, pipe or structural stock. In the machine database under the parameters for saws, inputs are available for head lift speed and stock feed speed. These parameters allow for the inclusion of head lift and stock advance times for automatic saws.
The last database to talk about is the handling time database.
To add consistency to the estimates, users can store commonly encountered non-machining operations. Examples might be loading a piece into the chuck, or loading a part into a fixture. Other examples can be indexing the 4th axis, changing the pallet, or transferring the part to a sub spindle.
---------------------------------------------------------
Database Editing
All database entry or alterations operate using the same process. So although we will be illustrating the process for the machine database, the basic procedure is the same for all the databases.
Since database files are loaded at the time the application starts, we recommend that any changes be made prior to the desired implementation of the new entry data. We also suggest re-starting the application after the data entry is complete and the database has been saved. This will ensure that the information is properly loaded as the application re-starts.
To add a new option to the database, open the database from the left menu bar.
Select the ADD button and enter the name for the new entry.
Then select the add to database button
The new name will then become available from the drop down list. Selecting it will give the user the ability to enter the pertinent information for the entry.
Once the inputs are complete, select the save database button to record the entries and make the change permanent.
To delete an entry from the database select the delete button from the menu. Select the desired entry from the drop down list and then select the remove from database button. The entry will be removed and the database automatically saved and re loaded so it is not necessary to save the database after an entry is deleted.
As mentioned in the beginning, it is always recommended that the application be re started after any database editing to insure the proper loading of the information as the application re starts.
---------------------------------------------------------
Editing Names for Materials and Machines
To edit or change a name for any established material or machine, select the EDIT NAME button on the desired database main screen.
Pull down and select the current name from the drop down list. Edit the name to the desired setting in the drop down box and select SAVE to make the change permanent in the database file.
---------------------------------------------------------
Backing Up the KipwareCYC® Databases
Backing up the KipwareCYC databases can be done under the SETTINGS tab for KipwareCYC versions 19.2.0 and later.
In addition to options for creating backup copies, this page will also display the date and time the last backup copies were created.
Backup copies will be auto created for the machine, cutting parameter and handling time databases.
To create backup copies of the current versions of the database, open the SETTINGS page and select the backup KipwareCYC databases button. The new files will be created under the name with the prefix "BACKUP COPY - " followed by the database filename.
In addition the current date will be logged into the SETTINGS file and will be displayed in the field on this SETTINGS page.
To restore the last backup copy select the restore KipwareCYC databases button. Please heed the warning that the current databases will be over written by the backup copies and select the option to continue or abort. The backup copies will now become the active database contents and the oldest date for a database file will be displayed in the last backup date field.
Users are encouraged to use this auto backup process whenever they make major changes to any of the databases to insure unintentional loss of data.
|