NASA (agency-wide, across the NASA Centers) — Agency SharePoint Phase 1 Initiative: needs assessment, architectural review, governance, and a global SharePoint Center of Excellence for knowledge management, intranet and enterprise content management across the NASA Centers (2009–2010)

Contracted at center level (JSC, federal instrument) + EPC-authored agency SOW and work product on file; agency-wide instruments pending. NASA (agency-wide, across the NASA Centers) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Agency SharePoint Phase 1 Initiative: needs assessment, architectural review, governance, and a global SharePoint Center of Excellence for knowledge management, intranet and enterprise content management across the NASA Centers — EPC Group statement of work 'NASA Agency SharePoint Phase 1 Initiative' v1.0 (May 15, 2009, submitted) describing a 6,000-user Phase 1 scope across all NASA Centers; NASA JSC Standard Form 1449 purchase order (September 21, 2009) published; NASA Ames and JSC SharePoint health-check and assessment work product (2009–2010) on file. Project ID EPC-2009-NASA-AGENCY-COE. The engagement was completed and paid in full (EPC Group accounts-receivable record).

First-pass edition. The facts in the verification line and the project-facts table come from the documents named there. The engagement narrative below is written by EPC Group from the engagement type and the documented scope, is marked EPC-reported, and is pending review by Errin O'Connor. Delivery status comes from EPC Group's accounts-receivable record as stated by Errin O'Connor on 2026-10-15; no other result is claimed that the documents or project records do not support.

Summary

In 2009–2010, EPC Group completed Agency SharePoint Phase 1 Initiative: needs assessment, architectural review, governance, and a global SharePoint Center of Excellence for knowledge management, intranet and enterprise content management across the NASA Centers for NASA (agency-wide, across the NASA Centers) on Microsoft Office SharePoint Server 2007, SharePoint 2001/2003 and file-share migration, Active Directory, SQL Reporting Services, led by Errin O'Connor, EPC Group's founder and the architect named in the engagement documents (the Phase 1 statement of work is submitted by Errin O'Connor, Senior SharePoint Architect and author), addressing knowledge and content siloed by center, with no shared platform architecture or governance across the agency. The work ran through the phases the documents define: requirements gathering, architecture and hierarchy design, implementation review, migration best practices for existing intranet content, knowledge transfer and training, team task monitoring, and the agency-wide SharePoint governance strategy. The client accepted the deliverables and paid in full, per EPC Group's accounts-receivable record; EPC Group reports that its objectives for the engagement were met. Verification: Contracted at center level (JSC, federal instrument) + EPC-authored agency SOW and work product on file; agency-wide instruments pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported). What the documents establish, and what they do not, is stated in Evidence and limitations below.

Project facts

What the document states

EPC Group Statement of Work 'NASA Agency SharePoint Phase 1 Initiative' (v1.0, May 15, 2009, marked Submitted; drafts from April 28, 2009): a needs assessment, architectural review, governance development and roll-out of a 6,000-user SharePoint initiative to be 'utilized enterprise wide as a cohesive SharePoint Ecosystem for global collaboration and true enterprise content management [across] all NASA Centers and their related partnerships', including a global NASA SharePoint Center of Excellence charter, governance strategy with planning and enforcement, migration planning for SharePoint 2001, SharePoint 2003 and file-share content, custom content types and retention schedules, My Site pilot, a partner-only external access model for universities, a CoE roadmap (3 to 24 months) and training curricula. Related documents on file: 'NASA Ames Global SharePoint Initiative' CoE statement-of-work drafts (April 29, 2009); 'NASA Ames SharePoint System Health Check' (September 2009); 'NASA JSC SharePoint Health Check and Assessment' (2009; updated May 2010); 'NASA's SharePoint Business Value Proposition' deck (June 2009). Published: NASA JSC Standard Form 1449 purchase order (September 21, 2009) for the EPC Group SharePoint Site Provisioning Solution. EPC-reported: Errin O'Connor served as lead architect for NASA's SharePoint, Office 365 and Azure efforts across the agency's major centers, reporting to NASA CIO Chris Kemp; EPC Group's own later statements of work say 'all 8 of NASA's major facilities' while Errin O'Connor's October 2026 statement says seven centers — the claims register carries one number before this page leaves first-pass status.

Starting environment (EPC-reported, first pass)

An engagement of this type begins with NASA's centers, each with its own SharePoint and content estates, and an agency need for shared knowledge management, intranet and content-management practice across the centers. The specific inventory for this engagement is held in EPC Group's project records and will replace this paragraph when published.

Business problem (EPC-reported, first pass)

Knowledge and content siloed by center, with no shared platform architecture or governance across the agency.

EPC Group's responsibility

Lead architecture for NASA's SharePoint, Office 365 and Azure implementation efforts across the agency's major centers, including a global SharePoint knowledge-management, intranet and content-management system, as EPC Group reports the engagement.

Technical decisions (EPC-reported, first pass)

The decisions this kind of engagement turns on are agency-wide information architecture, center-level autonomy versus shared services, search and knowledge-management design, content-management governance, and the path from on-premises SharePoint to Office 365 and Azure. The decisions actually taken for NASA will be stated here from the project record.

Delivery sequence (EPC-reported, first pass)

Typical sequence for this engagement type: agency architecture → center-by-center implementation → shared knowledge-management and search → governance and operations. Dates and acceptance for this engagement will be stated from the project record.

Results

Completion, acceptance and payment are stated from EPC Group's records; the technical rows stay pending until the project record is published. No figure is invented.

Client perspective

The client accepted the deliverables and paid every invoice in full. No client quotation is published on this page; where a client has given a written statement or a review, it is linked from the evidence record.

Evidence and limitations

The evidence record at https://www.epcgroup.net/evidence/nasa-johnson-space-center-sharepoint-2009 publishes the document(s) with redacted page images and SHA-256 hashes. The instrument establishes the client, the supplier, the service and the date as stated above. It does not by itself establish delivery dates, volumes, acceptance or outcomes; those require the project records referenced in the Results table. Completion and payment in full are established by EPC Group's accounts-receivable record (paid invoices on file; not published because they carry commercial terms).

Lessons for similar organizations (EPC-reported)

• Shared architecture with local autonomy is the only model that survives in a multi-center agency.
• Search is the knowledge-management system; everything else feeds it.

Related service

Enterprise SharePoint and Microsoft 365 architecture ·Talk to a senior architect

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.