The document provides a resume for Clayton P. Cobb, who has experience as a SharePoint architect. It outlines his education, certifications, training, skill areas, community involvement, professional experience, and responsibilities in various roles providing SharePoint expertise and solutions. His experience includes architecting large SharePoint implementations, troubleshooting complex environments, and integrating legacy systems with SharePoint.

1. CLAYTON P. COBB
SharePoint Architect
Microsoft Certified Professional
warrtalon@gmail.com
EDUCATION
Graduate Master of Business Johns Hopkins 90% Complete
Administration (MBA) University 3.6 GPA
Undergraduate Computer Networking (BSCN) Strayer University 2003
- W2K Focus Summa Cum Laude
4.0 GPA
Certification Microsoft Certified Technology Microsoft Certified 2008
Specialist – MOSS Professional Score: 947
Configuration (70-630) (MCP)
Certification Microsoft Certified Technology Microsoft Certified 2008
Specialist – WSS 3.0 Professional Score: 972
Configuration (70-631) (MCP)
Training SharePoint 2010 Ignite Atlanta, GA 2009
conducted by Microsoft
Training InfoPath Master Training Denver, CO 2009
(Qdabra)
Training SharePoint Bootcamp Las Vegas, NV 2008
(SharePoint Experts)
Training SharePoint Architect Advanced Milwaukee, WI 2008
Training (Microsoft)
Training SharePoint Bootcamp – Admin Las Vegas, NV 2007
& Planning (SharePoint
Experts)
Certification ITIL Foundations of IT Service Colorado Springs, 2006
Management CO
KEY SKILL AREAS
TS/SCI with Polygraph (SCI-eligible) SharePoint 2007 Architect (MOSS 2007)
SharePoint 2010 Experience/Training / Office 2010 (daily use/testing)
Deployment
SharePoint Designer 2010 – Workflows InfoPath 2010 – Custom Forms
MCTS: MOSS Configuration (70-630) MCTS: WSS 3.0 Configuration (70-631)
Enterprise-level SharePoint 2007 SeeUnity – Integrating SharePoint 2007 with
Administration, Planning, and Design legacy Document Management Systems
Electronic, workflow-enabled, browser-based Infopath 2007 (and 2003)
form automation SharePoint Designer 2007

2. SUMMARY OF SHAREPOINT COMMUNITY INVOLVEMENT
Mr. Cobb has taken a very active role in the community in an attempt to spread his knowledge and
passion about SharePoint and its associated products like Microsoft Office. Here is Mr. Cobb’s list of
activities:
• Chairman – SharePoint Saturday Denver
• Vice President – Colorado SharePoint User Group (COSPUG)
• Microsoft InfoPath MVP Nominee
• Major Contributor on the MSDN Social Forums – Clayton Cobb
SUMMARY OF PROFESSIONAL EXPERIENCE
As a professional, Mr. Cobb has 13 total years of experience, 8 of which are in the IT consulting
realm, providing a wide range of services: SharePoint development, computer networking, system
administration, systems integration, project management, testing management, knowledge
management, radio communications, and multimedia support; technical editing, document
organization and tracking; and web design, development, and architecture. As of 2008, Mr. Cobb is a
Microsoft Certified Professional with a specialty in SharePoint (MOSS) 2007 configuration. As a
United States Marine, Mr. Cobb has 5 years of experience in the Communications and Signals
Intelligence field. Through his professional years, Mr. Cobb has gained practical experience with
SharePoint 2003/2007, InfoPath 2003/2007, SharePoint Designer 2007, InfoPath 2007, MS Office
2003/2007, SQL Server 2005, Windows Server 2003, IIS 6.0, .NET, C#, Visual Studio 2005, EAI
technologies, and most RF communications mediums.
EXPERIENCE
Planet Technologies 02/2008-Present
SharePoint Architect
As a Technical Architect for Planet Technologies, Mr. Cobb has provided advanced SharePoint
expertise for three major clients – the National Renewable Energy lab (NREL), the Oak Ridge
National Laboratory (ORNL), and the Millennium Challenge Corporation (MCC).
NREL
Mr. Cobb is the lead architect and liaison to NREL who has embarked upon a major SharePoint 2007
implementation using Planet as the implementer. Mr. Cobb is currently conducting active pilots to
determine the most important features to provide when the system goes live in late FY09. Mr. Cobb
has already performed up-front requirements gathering and has built multiple pilot sites in order to
help NREL stakeholders understand the value of SharePoint and to help them make decisions on
what functionality they would like to implement right away when the FY09 build begins. Mr. Cobb’s
areas of responsibility for the current phase (phase 3):
• Finalize logical architecture and attain Cyber Security approval
• Finalize and procure hardware, software, and licensing for that architecture
• Build 14-server Production environment along with staging and development environments
• Migrate existing pilots into new architecture
• Begin rollout of Intranet to first department, which includes web application, site collection,
and sub-site creation along with full taxonomy derived from requirements gathering

3. • Simultaneously begin rollout of fully-secure Extranet to project teams
• Begin training of first department
Mr. Cobb completed these tasks during Phase 2:
• Continue to develop pilots to in order to determine most effective pieces of functionality that
will provide the most impact lab-wide upon full release
• Evangelize the value of SharePoint and a fully-integrated Microsoft-based infrastructure
through demonstrations and presentations of SharePoint along with the rest of the advanced
Microsoft technology stack (Exchange 2007, Office Communications Server 2007, Office 2007,
etc.)
• Train SharePoint team members to the point they can begin managing sites, training end-
users, and building custom solutions using relevant tools (i.e. Infopath, SharePoint Designer)
• Develop an implementation plan for all aspects of the full-scale deployment, including the
hardware, software, taxonomy, permissions, security, and internal/external access for the
development, testing, staging, and production environments
Mr. Cobb completed these activities during Phase 1:
• Interviewed stakeholders across the lab to determine business requirements
• Developed and delivered an architecture diagram along with hardware cost estimates to fit
that architecture
• Delivered a professional services estimate for what it would take to deploy a basic SharePoint
environment in FY09 as well as an estimate for what it would cost to develop additional
functionality thereafter
• Created pilot sites for specific teams/groups and provided actionable functionality on these
sites that helped (and continues to help) increase efficiency and improve collaboration.
Examples include a list-based opportunity pipeline solution that provides reporting and
immediate information in place of an old spreadsheet-based system that took an extra 11 hours
per week to maintain. Also, an important paper-based process was replaced with an Infopath-
based electronic form driven by workflow that has automated the entire process. It is in full
use and has completely replaced the old process. These are example of actionable pilots that
show true value as opposed to just being unguided dumping grounds for documents, which
does not show much value
• Trained new SharePoint team members on advanced SharePoint concepts as well as advanced
usage of both Infopath 2007 and SharePoint Designer 2007. Also, held multiple training/demo
sessions with both the regular workforce and management in order to increase buy-in
After Phase 3 is complete, Mr. Cobb will be responsible for continuing the full deployment of
SharePoint to the entire organization.
ORNL
Mr. Cobb was called on a Thursday morning to answer an emergency at ORNL regarding their
SharePoint infrastructure – MOSS 2007 is used as the primary Intranet in this organization with
nearly 8,000 users. Mr. Cobb worked directly with the CIO, the CIO’s best people, other Planet
Technologies experts, and Microsoft experts (Technical Account Manager and SharePoint Field
Engineer) for 30 straight hours troubleshooting, planning, and fixing the environment. Two main
problems existed – one that affected SharePoint without being a SharePoint-specific problem and
another that was directly related to an improperly built MOSS environment that needed to be fixed.
Mr. Cobb provided troubleshooting support on the first problem, which was resolved at hour 30 after
his arrival, but he provided his most significant value when planning for and actually fixing the
infrastructure:

4. - The one SSP being used for all web applications had been built without specifying a dedicated
SSP Administration Site Host web application. Because a dedicated SSP Admin web app was
not created, then the SSP Admin dropdown box defaulted to an existing content web
application – the one that housed all current SharePoint 2007 content
- Additionally, the root site collection of this web app was the ONLY site collection in the web
app (other than the SSP Admin site collection that was generated upon creation of the SSP),
which meant there was only one content database for the entire farm that was serving the
Intranet. Over the course of 1.5 years, this content database grew to over 110 GB, and it had
become unmanageable in terms of backups. Plus, it was mated to the SSP Admin site, which
further complicated things
- The team had made a previous attempt to build a new farm and perform a migration, but
when they built the new SSP from scratch, migrated over the MySite web application, and
performed a profile import, they noticed that many of the custom profile properties had lost
their data. There is a specific reason for this that I was aware of once I heard what had
happened. It was directly related to the old SSP, which is what they needed to use for
building the new SSP (they had not), but this was basically unfeasible due to the fact that the
old SSP was forever tied to the 110 GB content database because of the mistake made when
creating that SSP
- Mr. Cobb devised a plan that separated the site collection containing over 100 GB of the total
data from the web application, put that site collection in its own new web application, and
allowed for restoring the old SSP to the new farm without it taking 10-11 hours, and all
without losing a single piece of data – not from content or user profiles.
- Due to time constraints, Mr. Cobb was not able to see the last few steps through, but he did get
the plan all the way to the point where he executed the 100GB site collection, and since that
was going to take 5 hours itself, he left it to the rest of the team that was to arrive at 8am the
next morning right after the operation completed. He left detailed instructions on what he had
done and on what was remaining, but the remaining steps were easy, minimal, and without
risk. While en route back to his home, Mr. Cobb verified with the ORNL lead that everything
had gone as planned and was still progressing as planned.
- In the end, it was a very successful mission on a high impact situation. The details of the plan
were devised solely by Mr. Cobb, and the Microsoft Field Engineer confirmed that they were
the proper steps to take when he arrived on site.
Department of Treasury 11/2007-02/2008
SharePoint Architect
Mr. Cobb is contracting to the Department of Treasury Office of the Comptroller of the Currency
(OCC) through Booz Allen Hamilton as the SharePoint Architect/Expert and SeeUnity Subject Matter
Expert/Lead. This massive undertaking by OCC requires integration of their legacy document
management (DM) system – HummingBird – with SharePoint (MOSS) 2007 through the use of
SeeUnity, which is a 3rd-party integration tool that specializes in integration/migration of legacy DM
systems with MOSS. Mr. Cobb has already proven the concept in prototypes built on the Booz Allen
system where he successfully integrated the three applications – HummingBird, MOSS, and SeeUnity
– and is now providing that expertise to the live project. Mr. Cobb has completed the following work
on the project:

5. - Established rapport with the OCC database administrator and virtual machine administrator
in order to seamlessly and efficiently build out the five required MOSS environments:
sandbox, dev, test, staging, production
- Built the sandbox environment remotely
- Built the development environment on site at OCC
- Verified correct documentation of each build as a deliverable to OCC
- Developed and conducted a training/presentation session to OCC leadership
Mr. Cobb is still responsible for the following work:
- Build test, staging, and production
- Build separate Project Server 2007 farms in each environment while sharing the same database
instances
Sand Ridge Energy 11/2007-2/2008
SharePoint Architect
Mr. Cobb contracted to Sand Ridge as a SharePoint Architect. Mr. Cobb built the entire MOSS 2007
medium server farm from scratch along with a mimicked staging farm and a small development farm
hosted on virtual servers. Mr. Cobb also built out the Intranet so that it could become the primary
source of intellectual capital and collaboration for Sand Ridge employees by utilizing published
pages, workflows, and electronic forms. Mr. Cobb used his experience and ability with multiple
Microsoft products to provide an integrated, automated, browser-enabled electronic forms
environment with the following features:
• Replaced HR paper forms with electronic forms
• Electronic forms were built in InfoPath 2007 but were web-enabled within SharePoint 2007 to
provide an easy and efficient method of submitting forms by anyone with an Internet
connection. This removed the need to have InfoPath 2007 on every client
• Electronic forms were integrated directly with Active Directory user profile information so as
to automatically identify the submitter; automatically route forms to managers, HR, and
payroll; and auto-populate user-specific details to alleviate having to type (or write) the same
information over and over (also reduced user error)
• Electronic forms were tied directly to existing data sources (i.e. SQL Server) via Web Services
in order to interact with (read and write) live data so that users could see current data within
the form before submitting and so that database owners did not have to manually insert,
change, or delete data upon request of users. Instead, upon review and approval by the data
owner, the form itself could be submitted and thus update the database automatically
• Workflows were attached to the forms using SharePoint Designer. These workflows included
complex and specific business logic in order to properly route documents for approval in all
scenarios
• Within the forms themselves, much business logic and data validation was incorporated to
ensure a user-friendly experience with minimal user input and thus reduced user error: users
were notified when data input was not valid, fields and views were locked or unlocked
depending on user identity and/or data input, and forms would fail to submit if certain
parameters of the form were not met
• SharePoint form libraries housing these forms were configured so that users could only see
forms relevant to them (e.g. those created by the user, those created by direct reports of the
user, etc.). This helped to prevent a cluttered view while also enhancing data integrity.

6. In creating the production farm, Mr. Cobb put a heavy emphasis on scalability, reduction of user
error, and minimization of administrative overhead through the use of Site Definitions. It required
more up-front work to create the site definitions, features, master pages, page layouts, CSS files,
content types, and site columns, but once all of those were bundled into a Site Definition Template, it
made future site provision extremely easy, efficient, and precise. It allowed administrators and even
users to create sites based off new templates that would automatically apply the aforementioned
attributes to the site, which was especially useful when there were many sites that needed to be
created with the same attributes. This reduced administrative overhead by combining all attributes
into the site creation itself, which was done through the GUI or through the command line. It also
removed the potential for user error by eliminating all the manual steps required when creating sites
without custom site definitions. Lastly, these Site Definition Templates were easily modifiable once
created, so as the company changes in the future, the site definitions can change accordingly.
MCC
Mr. Cobb joined a Booz Allen Hamilton (BAH) team in order to help save a SharePoint project that
was behind schedule and spiraling downward quickly. Mr. Cobb jumped right in, assessed the
situation, took control, and quickly brought back the SharePoint side of the project in time to meet
deadlines. Mr. Cobb was responsible for and accomplished all of the following:
• Developed and created the test architecture – both a dev and test environment – that included
Microsoft best practices for deployment and that met the security requirements of MCC, which
is a government agency within the State Department
• Incorporated security measures that included a Microsoft Internet and Security Acceleration
2006 server in an Enterprise Array that sat in front of each environment. Mr. Cobb established
VeriSign Class 3 SSL encryption between the end-user and ISA while also configuring the
system to work with Kerberos authentication
• Mr. Cobb documented the entire process of the implementation step-by-step so that it could be
taken over and maintained by a BAH resource to be hired at a later date. Mr. Cobb also
trained and mentored this resource once he was eventually hired near the end just before the
deadline
• Mr. Cobb worked doggedly with the hosted solution provider used by MCC to make sure all
facets of the infrastructure were in place and ready on time, to include DNS entries, correctly-
assigned IPs, SSL certificates, Service Principal Names (SPNs), and Active Directory settings
When Mr. Cobb left this project, the SharePoint deliverables were complete, and the implementation
was ahead of schedule – just waiting on the hosting company to complete its side of the
infrastructure. The BAH manager in charge of that team later commented that he needed another
“hero like Clayton” on another project that had a similar emergency.
Booz Allen Hamilton 10/2005-11/2007
SharePoint Subject Matter Expert
Mr. Cobb has spent the last three years working primarily within SharePoint to provide many
capabilities to clients: document management, records management, custom workflows, custom web
parts, custom forms, MS office integration, InfoPath integration, as well as internal and external
collaboration. In addition to his development work, Mr. Cobb has also conducted many SharePoint
2003 & 2007 demonstrations and training sessions for clients, Booz Allen employees, and teammates.

7. USAF B-52 LCMP – Custom portal development within MOSS 2007 to help track the lifecycle of
B-52s using workflows and forms that interact with existing, external SQL Server 2005 databases
• Installed and configured standalone environment: IIS 6.0, ASP.NET 2.0, .NET 3.0, and WSS 3.0
• Customized look and feel by editing the default.master and creating a custom Cascading Style
Sheet (CSS)
• Created custom workflows in SharePoint Designer to meet the business needs of the LCMP
office
• Configured security-trimmed web part roll-ups to aid with program planning
Multi-Client Maturity Assessment Tool – Built custom tool within MOSS to automate the maturity
assessment process
• Designed tool from scratch based off requirements and existing MS Access design that was
tedious to use, not easily re-usable, and not scalable
• Design included using InfoPath 2007 to build dynamic forms with built-in logic that were tied
to MOSS pre-defined/pre-configured lists
• Assessment team loved the functionality and is using the initial prototype to perform current
assessments on a major Air Force project
Dept of Treasury – Bank auditing tool using MOSS 2007 Enterprise, SQL Server 2000/2005, InfoPath
2007, Designer 2007, and Office 2007 Professional Plus
• Created custom workflows in SharePoint Designer that facilitated a robust document approval
process with conditional branches and escalation for overdue tasks
• Created custom content types with custom metadata fields that were then manipulated in
InfoPath 2007 and leveraged within the Document Information Panel (DIP), a new feature
within Word 2007. Utilizing the DIP allowed me to utilize metadata fields that were
connected to disparate data sources all within one document: SQL Server 2000/2005, MS
Access, SharePoint lists, and Web Services. I made metadata fields that could pull data from
each of these sources and even filter the data of some fields based off selections of earlier
fields. All of this metadata was selectable and visible to the user at the top of the Word 2007
document, and upon submission, this metadata was pulled back into MOSS 2007. That
metadata then allowed for custom views, more robust searching after mapping the new
metadata properties, and provided triggers and conditions for workflows
• Once I found that I could not take metadata selections from the DIP and interact with a web
service that would populate fields inside the document itself, my team learned how to create a
custom Word 2007 ribbon add-in. Using Visual Studio Tools for Office, we were able to create
a ribbon that had all the same metadata fields and the same database conditions along with
filtering based off selections. Based off the bank that was chosen in the ribbon metadata field,
we were then able to invoke a web service that returned all the bank data and populated a pre-
formatted table within the Word 2007 document itself. The web service would return an XML
file, and the fields in the document were tied directly to a parameter in that XML file, so they
would display that information instantaneously upon retrieval of the information.
• Created custom web-enabled forms that interacted with web services by allowing the user to
select a bank name from a pulldown list (list populated from a SQL Server 2005 connection)
and then hit a submit button that invoked the web service, pulled back data, and populated
the form fields. All field mapping and setup was done through InfoPath 2007, and then both
the form and the form library were configured to make the form web-enabled, which then
allowed users to not need any version of InfoPath when interacting with the form. This

8. method was incredibly fast, since the interaction took place all within the browser and within
SharePoint. The data fields in the forms were all then usable as metadata within other parts of
SharePoint, including within advanced metadata searches
• Integrated MOSS 2007 with HummingBird 6.0, the client’s existing document management
(DM) application, using SeeUnity, a 3rd-party integrator. SeeUnity’s application allowed us to
provide seamless interaction with the DM from SharePoint through out-of-the-box web parts.
We were able to interact directly with HummingBird in the following ways:
o Upon creation of a document in a SharePoint document library, an event was triggered
that ported the document over to HummingBird along with all of its metadata. We
also were able to set it where the document did not port until its Content Approval
Status was set to “Approved” at the end of an approval workflow
o A search web part allowed users to pull up existing HummingBird search profile forms
within SharePoint as if they were using HummingBird but were not logged into that
application directly. The metadata search parameters could be chosen and submitted,
which then returned a list of all documents in the DM meeting those criteria. The
documents could also be opened directly from this search result list in the user’s native
application (MS Word, MS Excel, etc.), and that doc would be pulled straight out of
HummingBird through the SharePoint interface
o A document creation web part allowed for users to create a HummingBird document
directly from SharePoint as if they were logged into the HummingBird application itself
o A customized view web part allowed us to specify certain files that a user would
automatically see based off that user’s field of expertise. For instance, if a user only
deals with Bank of America, then we would preset the web part to only display
documents in HummingBird that were specific to Bank of America per the “Bank
Name” metadata field
• Created a Search Center with customized scopes and metadata property mappings to facilitate
efficient searching by users
• Upon completion of the work, I presented an hour-long, live demonstration to the entire firm
with 50+ participants in person and 100 more dialed in from all over the world
IRS – Developed a transition strategy and execution plan for the IRS Criminal Investigation (CI)
division to upgrade from SPS 2003 to MOSS 2007
• IRS CI already has an SPS 2003 environment that they use extensively, but it does not provide
them all of the functionality they require. Due to this, they were eager to upgrade to MOSS
2007, since it has many of the features they want out-of-the-box.
• Booz Allen was already under contract, so they requested that we develop a transition strategy
for them that they could then use to understand the benefits of going to MOSS 2007 and
justify the cost to the CIO
• The strategy was 65 pages long and included two main sections: Key Added Benefits and a
Migration Plan. Writing each section required gathering requirements and being able to meet
stated business needs with known MOSS 2007 capabilities. To more effectively illustrate the
Key Added Benefits, I created my own prototype system that included not only the look and
feel (styling, layout, colors, and CI logo), but also physically showed the execution of those
benefits within a live environment. Doing it this way helped to show how the features
actually worked instead of telling them, and it showed how quickly and efficiently an
environment could be created. Demonstrating these features in a familiar
• After initial submission, IRS-CI leadership requested that we do assessments on two other
existing systems (one on SPS2003, the other on a non-Microsoft platform) to see if those could

9. be migrated into the new 2007 environment at the same time. I led a team who assessed the
other two systems, put together additional briefing slides, and incorporated them all into the
master plan, which was then re-submitted and is awaiting funding/approval from the client
FEMA – MOSS 2007 Executive Management System for use by FEMA executives who need to track
documents and activities within workflows that ultimately end with approved documents going to
Congress
• Created a requirements traceability matrix that mapped FEMA EMS requirements with MOSS
2007 capabilities along with the solution for each and level of effort, to include whether or not
the solution was out-of-the-box or required custom development in Visual Studio
• For all requirements that did not require custom code, I created a prototype environment that
was also customized to be familiar to FEMA executives through design and by using real-life
group names within the custom workflows
• Created custom workflows within SharePoint Designer 2007 that had many steps and went
both inside and outside the FEMA environment multiple times before final approval
PME – Booz Allen’s internal Project/Program Management tool (MOSS and Project Server 2007)
• Built a Maturity Assessment site and tool for the Booz Allen CMM team to conduct maturity
assessments on existing projects. The site was built in MOSS, and the custom forms were built
in InfoPath 2007 with data connections to SQL Server 2005 and SharePoint lists. I used
sophisticated filtering logic to make the forms dynamic so that the assessors did not have to do
anything except open the form, choose an interviewee, and then ask the questions given by the
form (the questions were shown dynamically based on the user’s role)
• On the ETASS proposal, which leveraged PME, I built custom auditing modules using custom
forms built in InfoPath 2003 and integrated directly with SPS 2003
iShare – Booz Allen’s internal SPS 2003 collaboration environment
• Created, built, administered, and maintained over 50 team sites
eShare – Booz Allen’s external SPS 2003 collaboration environment
• Built and maintain client-facing support site for Uni-Comm AFSPC
On these assignments, Mr. Cobb has used MOSS 2007, SPS 2003, WSS 2.0/3.0, .NET 2.0, SharePoint
Designer 2007, InfoPath 2003/2007, MS Office 2003/2007, Excel Services, Reporting Services, and
SQL Server 2000/2005.
Booz Allen Hamilton 11/2001-10/2005
Previous projects include project management, test team management, web development,
UNIX/W2K system installation/integration/administration, and military intelligence. All
experience available upon request but is not related to Microsoft SharePoint technologies.
United States Marine Corps 7/1996-8/2001
Communications/Signals Intelligence Intercept Operator/Analyst
Mr. Cobb served five years in the Marine Corps as a field intelligence specialist responsible for front-
line support of infantry units. He led a team of six with a wide array of skills whose job it was to
protect the infantry with indications and warning (I&W). The technology and methods used are
classified, but as part of this job, Mr. Cobb had to be adept at maintaining advanced computer
systems in the field while also maintaining 24/7 communications with HQ in the rear via multiple RF

10. bands – HF, VHF, UHF. Mr. Cobb also had to manage and maintain all the networking of his
equipment that was being operated by multiple Marines at once in live situations.