CMS vendor Interwoven today announced the release of a "Content Provisioning" solution (note: "solution" for Interwoven remains somewhat more a marketing concept than a technology adaptation), emphasizing new enterprise compliance needs. This is really a new justification for "OpenDeploy," a longstanding Interwoven product that has seen some traction after undocking from the TeamSite family 2 years ago. There has always been a good case for OpenDeploy, recently beefed up a bit and joined by a snazzier management interface. If compliance concerns now help IT departments find resources to help automate and synchronize the code-and-app deployment process, so be it. Among other benefits, greater automation should reduce unnecessary but seemingly endemic conflict between editors and developers over update choreography. Just remember that the kinds of deployments suggested here are technically very demanding, (where, for example, heterogeneous source and target environments throw the vendor and its customers into the land of "custom connectors"), and Interwoven has never competed on its engineering prowess. The company may well come up with another new rationale for OpenDeploy next year, but this is one of those times where the underlying need will always remain quite constant...