Enterprise Web Quick Facts

11 October 2017

WHAT: The U.S. Army Installation Management Command is in the process of migrating to a unified web content management system (CMS) for their public-facing websites.
IMCOM Enterprise Web (IEW), uses concrete5, a commercial, off-the-shelf CMS.
G9 uses Concrete5 for its content management system. Most Army Family and MWR websites are on their system.
We will provide:
 Ease of use, allowing PAOs to focus on their communication mission
 Standardization across installations, benefitting our customers
 
WHY: AR 360-1 puts PAO squarely in charge of the content of the websites and calls for PAO to ensure they are available.
Garrison PAOs have been asking for a CMS for as long as IMCOM has existed. For the last 10 years we’ve been telling the garrisons to go out and buy their own bailing wire and duct tape. Though many have been hosted by the NEC, each has a different experience and in too many cases, the relationship has been difficult.
WHEN: The first installations in the Enterprise Web CMS are Fort Leavenworth. Fort Bragg and Fort Wainwright. Some 20 other garrisons are in development, beginning with high-priority garrisons and the US Army Environmental Command. IMCOM is in the process of moving IEW from the Army Analytics Group to milCloud, a DISA service.


KEEP IN MIND, PAO IS DRIVING THIS CAR.

In the past, we could have bought tickets on a contractor’s cruise ship and had everything done for us. This isn’t the case now. Enterprise Web is like a cross-country trip in a good car. We are in the drivers’ seat and can take it where we want, but WE have to make it happen.
We – as in the IMCOM public affairs community – will be primarily responsible for operating and improving it. Those of us with web skills will be building the site and will make our improvements available to the entire community. Some NECs and garrison CIO operations are supporting this effort. They are welcome to do so depending on the guidance of the garrison and senior commanders.
Support will be provided in three ways. Keeping the system up-and-running will be the responsibility of the host. Questions specific to the CMS will be handled first by a knowledge base maintained on imcom.army.mil and a community of users. What can’t be answered by our own community will be elevated to experts in Concrete5.
Training – what little you will need – will come through video tutorials available from Concrete5 augmented by material from IMCOM PAO. If you aren’t a developer, CONCRETE5 IS EASY. Members of the tiger team will be available by phone.
Analytics: To track performance, we plan to use GSA digital analytics program, a free (to govt. agencies) application of Google premium analytics – still under development.
Standardization: The sitemap, menu, and graphic design are set, as are the names and locations of your pages. In some cases we will mandate the inclusion of a page. In other cases, if you need a page on a subject, there’s an optional place in the hierarchy. Boilerplate (such as disclaimers) will be shared.  Within those constraints, the layout is flexible enough to match your mission. We have a recommended content set for the body of the front page, but it is up to the garrison to determine what goes there.
Non-PAO content: The CMS will allow PAOs, at their option, to let garrison organizations edit their own pages (with PAO oversight and security training).
Other “goodies,” such as integration with CORE via APIs and shared features with MWR are under discussion. Our current goal is to get garrison websites functioning on the CMS.
CONTACT NEAL SNYDER on the Global as Neely A. Snyder for more information.