You do not have to trust your employees. You have to honestly and rightly judge them as you desire to be judged and then decide how to use them accordingly. The employees that prove themselves to you to be trustworthy you consider keeping; the rest you quickly lay them off.
Years ago I was working on a virtual 3D composition and rending of a compound miter joint of I-beams (which I was responsible for creating in AutoCad 2000) for a building under contract to a structural steel company where I worked as a Senior Project Manager. My renderings were used for cut-sheets in the fabrication shop and for field assembly guides. I could have used collaboration software. I could have spent less time on the phone with the structural engineer and more time exchanging renderings and remotely observing his layout responses. I see use for what you are requesting.
You did not give enough base information for a solid exact answer of exactly what remote monitoring software to use.
So, I will generalize.
monitoring computers:
The monitoring is already there in a lot of current operating systems.
First lets look at what operating system that you are using.
You did not say, therefore
If you have Microsoft Windows beyond XP sp2, or 7 sp1, then Microsoft already has back-doors built in which (if you have enough knowledge about how they are doing that) you can use the back-doors yourself. Microsoft already said that they do that. It is not difficult. Knowing how they do it is a start.
If you have (somewhere beyond 2004 or so) computer hardware (motherboards, video cards, etc.) with some versions of built-in "firmware" then the same applies to using those built-in back-doors.
The most built-in back-doors are in public use software operating systems like Windows 10.
The least built-in back-doors are in business and commercial use software operating systems. Less in Windows Server and more in Windows 10, except that is changing and becoming more in both.
If you use
Windows Server 2003 (without updates past 2004), which has very limited back-doors built into it (and those are generally controllable by the user) then you do not have to research and study and learn how to use the more ingrained back-doors built into later Microsoft operating systems.
If you use
Windows 7 before service pack 1 and without any of the Microsoft updates, then you probably can use a software package from before 2004 which was for employee remote monitoring for your work.
If you use
Windows XP (32 bit) with service pack 2 and not with service pack 3 and not with any other Microsoft updates which came out after service pack 2 was released, then you probably can use a software package from before 2004 which was for employee remote monitoring for your work.
If you use
Windows XP (64 bit) and not with any service packs that came out after the 32 bit version of XP's service pack 2 was released, even though the 64 bit version of XP was occasionally incompatible with some other software, then you probably can use a software package from before 2004 which was for employee remote monitoring for your work.
If you use
Microsoft Windows 10 for business, and if a substantial part of your legal and economic livelihood depend upon that business' use of Microsoft Windows 10, then you might consider getting out of that business quickly and distancing yourself from it substantially. Or, remove Windows 10 from all of your business' computers quickly.
Other operating systems:
Unix, Linux, similar: Look at the code that they use in programming their software and decide for yourself if you want that as part of your life.
Sun Microsystems: You might like that. Your remote employees as users might have a lot of difficulty with it. You might not like it.
Apple/Macintosh: No.
Once you have decided which operating system to use, and if you have studied sufficiently to have at least a general understanding of what that operating system is doing itself in relation to "remote" then report back here and ask for further guidance on the "some [programs] or software for monitoring computers, employee productivity and control over different projects that can be used at remote work." There are a lot of ways to have remote control and remote monitoring of employees and knowing the operating system that the business uses in conjunction with the operating system(s) that the remote employees are using is important.
You mentioned, "architectural projects".
Look at your architectural projects software and in them sometimes you might find built in remote collaboration abilities. Again, dates of release are important.
If you are using AutoCad which was released before 2000 (before AutoCad 2000) and if you intend to monitor your employees use of it, then you might do best to use a third party remote monitoring system. Or write your own which subclasses AutoCad and uses some type of ftp communication handshake etc.
If you are using AutoCad 2000 or later up to 2008, then look for pre-written software to do that, or subclass and do it yourself.
If you are using AutoCad released after 2008, you might want to think more about your data security.
If you are using big commercial versions of 3D software (most types) released after 2008 then you might find that (for intrusive spying by the manufacturer) back-doors are already built in and you might find ways to use their back-doors to your benefit while your general security of your company's work is being stolen.
Read what I wrote here and remember the dates and the generalities about things and it is up to you.
If you have a business that has a large part of its productivity based upon the use of computers, and if that business is at least 5 years old, and if you have more than 5 employees, then I think that you should already know some of what I wrote so far.
Bottom line:
YOU have to study it.
3
