Building a SharePoint Site

Kim Jeffries, an application analyst at the Van Andel Institute, began developing the SharePoint site in February, 2006. She first met with Culhane and Fahrenkrug’s administrative assistant, who explained which stakeholders were involved in the design phase of the construction process and the associated workflows. The admin told Jeffries that the project was going to have different teams focused on areas such as brainstorming, parking, construction and sustainability, and that these teams would need different levels of access on the site. She gave Jeffries a spreadsheet listing all of the people involved in the design process and the levels of access they’d need. Culhane and Fahrenkrug also wanted an area of the site that only they could use.

“We drew it all out and we ended up with a home page that everybody hits, with about five sub-sites off the home page, a couple of document libraries, main contacts, discussions and at least one private site for our owner rep team [Culhane and Fahrenkrug],” says Jeffries.

Because the Van Andel Institute was already using SharePoint Team Services internally at the time, Jeffries had to build accounts for each participant locally on the existing SharePoint server. Then she had to bring in each participant page by page, library by library, and meeting workspace by meeting workspace. She says provisioning access for users in Team Services was “tedious” and “the most difficult part” of building the site.

It took about 40 hours over the course of a month to get the site up and running, Jeffries says. When it was complete in March, she turned the design and the content administration over to Fahrenkrug and Culhane’s administrative assistant. Jeffries continued to create accounts for new teams and individuals as they came on board, because that process was complicated and it needed to be done on Van Andel’s local SharePoint server.

Fahrenkrug says it generally took users two to three weeks to get accustomed to SharePoint. Jeffries hired a local training centre to teach the owner representatives and a handful of employees from the architecture firm and construction offices to use SharePoint. But, Fahrenkrug says, most users learned the system on the fly.

Though the SharePoint site took some getting used to, Fahrenkrug says, the user interface is more intuitive than an FTP site, which looks more like a computer file than a Web page and never offers enough storage, in his experience. As such, SharePoint makes storage and retrieval of documents easier, he says. Users can access the site whenever they want; and they don’t have to wait for Federal Express deliveries. Jeffries adds that users receive alerts via e-mail whenever a new document is added to the site.

When users need to find a spec, they can simply type the name of it into the search engine on the home page, which takes them right to it, as opposed to drilling through folders to find it, he notes.

Troubleshooting problems is also easier on SharePoint than on an FTP site, says Fahrenkrug.

“If people couldn’t get into an FTP site, it was pretty hard to figure out why,” he says. “With SharePoint, my admin can go in, figure out why they can’t get access, and if there is a glitch on our end, we can easily fix it.”

Upgrading to Microsoft Office SharePoint Server (MOSS)

When the Van Andel Institute migrated to Microsoft Office SharePoint Server (MOSS) in January, 2007, Jeffries had to update external users’ security levels because they could no longer access their specific site with the local accounts she had originally set up for the previous version of SharePoint, Team Services. (Security is set up differently in Microsoft Office SharePoint Server than it is in Team Services.)

Drawing on research she had done about the best way to set up user access on MOSS, she worked with the Van Andel Institute’s server administrator, Russell VanderMey, to create Active Directory accounts which she could then bring into SharePoint. VanderMey created an external Active Directory domain that’s not on the Van Andel Institute’s network, yet provides Jeffries with a domain that she can use to create and maintain security for SharePoint users who are not Van Andel employees.

“With MOSS, the maintenance is so much easier because I created security groups for every level necessary on each page and sub-site and I created security groups within SharePoint,” says Jeffries. “Now, when someone new joins, I go out to the external active directory site, I get their name and plug them into whatever site they need to belong to.”

Jeffries adds that it now takes less than five minutes to provision access for users, because she doesn’t have to drill through 30 sub-sites to maintain security.