hexagon logo
Register Sign in
  • Replies 8 replies
  • Subscribers 222 subscribers
  • Views 84 views
  • Users 0 members are here
Options
Related

Programmer/Authors Notes

acgarcia
Just wanted to see what everyone else is doing. I need to get in the habit of documenting like the date I proved a program in $$ comment for record keeping and just general notes of changes I made.

Does anyone have a specific format or style that they can share for ideas? I'm thinking something like my Name, Date, maybe CAD revision, drawing names and revisions?

Thanks.
  • We make a simple text block, list the 'Issue'(revision) of the program, declare what type of changes we make then add the programmer's initials and the date of change.
    This matches the description of change in our program log. None of this information shows on any report, you just see that the revision of the program has been updated and you can dig from there.
  • Possibly look into the "Protect" module.
    What's New In PC-DMIS 2019 R1? Protect

    ​
  • I use document comments to keep track of program changes. This allows me to track any program changes down the line by knowing what has been changed that could have caused an issue if any arise. I also keep the backup of the program prior to changes in the event a change needs to be reversed.
    My format looks like this:
    *********************************************************PROGRAM HISTORY*********************************************************
    12.19.22 "OPERATOR NAME"-"DESCRIPTION OF CHANGES/COMMENTS"
    ********************************************************************************************************************************************
  • in reply to R2ah1ze1l
    Program Log? What kind of log you have? An excel or Word format or something else?
  • in reply to R2ah1ze1l
    It was built with Access Database, we can track approvals through the log. It's not the most advanced but it has its advantages.
  • I use document comments to keep track of program changes. This allows me to track any program changes down the line by knowing what has been changed that could have caused an issue if any arise. I also keep the backup of the program prior to changes in the event a change needs to be reversed.
    My format looks like this:
    *********************************************************PROGRAM HISTORY*********************************************************
    12.19.22 "OPERATOR NAME"-"DESCRIPTION OF CHANGES/COMMENTS"
    ********************************************************************************************************************************************

    We do the same thing in our programs and we also use our doc control software to keep the latest changes in the correct folder. The doc control software also gives us access to previous versions of said program as far back as initial creation. By saving each changed version of a program into doc control has saved me many a time when someone made changes without going through doc control.

  • we have a Program Log in our master folder for each program to track changes made to the masters. we have a default template that has the below info

    $$ NO,
    **********************************************
    ENTER PROGRAM REVISION DATA
    **********************************************
    $$ NO,
    PROGRAMMER:
    DATE CREATED:
    NOTE:
    REVIEWED BY:
    DATE:
    DWG No.: REV.:
    PART NAME:
    MODEL USED:
    DATE OF LAST CHANGE: REV.: E/DCN#:
    BY:
    REASON:
    1.
    2.
    3.

    $$ NO,
    *********************************​
  • we have a Program Log in our master folder for each program to track changes made to the masters. we have a default template that has the below info

    $$ NO,
    **********************************************
    ENTER PROGRAM REVISION DATA
    **********************************************
    $$ NO,
    PROGRAMMER:
    DATE CREATED:
    NOTE:
    REVIEWED BY:
    DATE:
    DWG No.: REV.:
    PART NAME:
    MODEL USED:
    DATE OF LAST CHANGE: REV.: E/DCN#:
    BY:
    REASON:
    1.
    2.
    3.

    $$ NO,
    *********************************​

    I also have an add on to note if there is a revision change, by how and why and approved. I save all my Masters programs as Master Program & Date
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement