@ The PLC Kid, that's what I have thought until trying to run audits on CPUs; then I realized that "plain" FTAC is good only for keeping tabs on the applications' implemented security; the users will have to "ckeck-out" and "check-in" the files under their own Windows Login; if an application is "checked-out", it is not available to anyone else but the "current user" until "in" again.
In order to run automatically scheduled audits on assets (10 only!-you are correct)and retrieve the current application (adding it to the History Log), you will need a suplementary FTAC Disaster Recovery license- $5400 list.
Right I know you need the Disaster recovery module to audit cpu's as I felt all the pain when I had to pay for licensing for 722 CPU's on this site.
But from the OP's first post he indicated he just needed change management for himself and did not give any verbage that he may have anyone other than him to manage.
Maybe he does and if so he would want disaster recovery like you said.
If it's just him I would just stick with the file and folder option or something like SVN if he is not well disciplined.
I used to use Sharepoint here as it was alreay our corporate back bone so I just built a site that only I had access to and used the check in /out versioning features.
The OP stated he does not know what's different between the files in his manual archive now. To solve that just take good notes and store them with the version.
When I begin a program change or even a check I always upload what's in the processor and compare to the latest version if it's the same I use it so I have the stored version there on my laptop for a chick backup recovery and if what I upload is different I save it and investigate.
I also start a word document and write down the purpose for my check and or edit and what changes I make such as
"added a extended down branch rung from the first OTE in Ladder 5 rung 219 and added an OTE to this branch rung tagged "oil temp waring feed roll 7"
This word document gets converted to PDF format also and both stored with the program.
All my stuff is together also. I may have a folder for Line 1 and then subfolders for Oven, winder, wrapper, conveyor system, etc.
In each of those folders I have folders labeled PLC program, HMI program, Drive Programs,Drawings /Prints, Manuals, Emails, Misc,etc.
When I do a check out I check out the whole folder and If I install a new field device the changed prints,plc program,hmi program,etc are all stored with it and a manual for the field device then I check that whole folder back in. I have always used this method on code projects using SVN on Share Point and when doing it in a manual fashion and it has never failed me