It's old school enterprise speak. When software-being-built consisted of a number of "Configuration Items" (CIs), such as .doc files, .xls files and of course heaps of .c files. There would be a dedicated "Configuration Manager" who's job it was to make sure that people wouldn't Visual SourceSafe their files over other people's files. He'd also write the batch files for the build server, assuming they had a build server.

They really do mean source control. Just that it doesn't have to be source code. It can be any "configuration item". Just like with git or svn or mercurial or zipping-directories-and-uploading-them-to-a-network-share.

Personally, I like "version control" for that reason. It just removes the subject of the operation from the name entirely.