Federal Reserve Bank of New York — SharePoint Consulting Engagement: Evidence Record
Claim level: Contracted — countersigned
Verified against the 1 primary source document and 1 historical work-product exhibit published on this page. Every published file carries a SHA-256.
In October 2010 the Federal Reserve Bank of New York entered into a consulting agreement with O’Connor Enterprise Group, Inc., doing business as EPC Group, for a SharePoint best-practices needs assessment, architectural and governance gap analysis, and a roadmap for a global SharePoint Center of Excellence. The accompanying architecture deliverable maps that hierarchy across all twelve Reserve Bank districts.
O'Connor Enterprise Group, Inc., doing business as EPC Group, is the legal contracting entity for the engagements documented here.
Verification summary
| Verification vector | Validated value |
|---|---|
| Client entity | Federal Reserve Bank of New York |
| EPC contracting entity | O'Connor Enterprise Group, Inc. d/b/a EPC Group |
| Document type | Executed Contract — Master Agreement, countersigned by both parties |
| Date | October 25, 2010 |
| Technology | Microsoft SharePoint |
| Scope shown in source | Best-practices needs assessment; architectural gap analysis and review; governance gap analysis and development; review of existing infrastructure design; roadmap for the new global implementation of a SharePoint Center of Excellence |
| Architectural scope shown in the work product | The FedShare ECM hierarchy deliverable maps content architecture across all twelve Reserve Bank districts — Boston, New York, Philadelphia, Cleveland, Richmond, Atlanta, Chicago, St. Louis, Minneapolis, Kansas City, Dallas and San Francisco — plus the Board of Governors, National IT and the national business lines. The engagement was contracted through the Federal Reserve Bank of New York. |
| Signatory authority | Client signatory title: V.P. Engineering. EPC signatory: Founder & SharePoint Architect |
| Evidence ID | EPC-EV-FRBNY-2010-001 |
Source documents
Master Agreement — scope page and execution page
- Document type:
- Executed Contract (countersigned)
- Date:
- October 25, 2010
- Issuer:
- Federal Reserve Bank of New York
- Published:
- Pages 1 and 12 of 12
SHA-256 of the published file: 079b866b2cca3fbffb6fe542cc801f1c5a7538409cfbcd99b47422fd9c7c523b
What this document establishes
- The Federal Reserve Bank of New York and O’Connor Enterprise Group, Inc. d/b/a EPC Group are named as the two contracting parties.
- The agreement is dated October 25, 2010 and is signed by both parties.
- The scope covers SharePoint needs assessment, architectural and governance gap analysis, infrastructure review, and a Center of Excellence roadmap.
- The client signatory held the title V.P. Engineering.
What it does not establish
- It does not establish which deliverables were completed.
- It does not establish the value of the engagement.
- It does not establish any current relationship.
Redactions applied
- Fax transmission header (both pages)
- Handwritten per-page initials block
- Both handwritten signatures
- Client signatory’s printed name
No client name, EPC Group identity, project description or date has been altered.
Project work product
What this page does not claim
- This page does not claim any involvement in TARP, eDiscovery, litigation support, or any programme not named in the document above.
- This page does not claim a total contract value.
- This page does not claim which deliverables were completed, or that the engagement was accepted.
- This page does not claim a current commercial relationship, sponsorship or endorsement.
Document provenance
Source: EPC Group historical corporate records.
Public version: privacy-redacted reproduction of the pages listed above.
Material alterations: none, other than the redactions disclosed against each document.
Original retained: yes, by EPC Group.
Redaction method: Each published excerpt is rebuilt from a rasterised image of the page, with redaction boxes burned into the pixels before the file is reassembled. The derivative carries no text layer, no annotations, no form fields and no metadata, so nothing beneath a redaction box can be recovered by text extraction. Every derivative was additionally reviewed by eye at high magnification.
What a hash proves: The SHA-256 confirms the downloaded file matches the published file; it does not independently authenticate the underlying agreement.
Text transcripts: 01 · 02 · 03 — generated by optical character recognition from the published, redacted images, never from the originals; where an image is boxed the transcript reads [REDACTED].
Review cycle: this record is reviewed every 90 days.
Questions about this record
Has EPC Group worked with Federal Reserve Bank of New York?
Federal Reserve Bank of New York contracted EPC Group for SharePoint consulting in 2010; this record publishes 1 primary-source document and 1 historical work-product exhibit at claim level "Contracted — countersigned". EPC Group publishes historical contracting records supporting this engagement; the published material does not establish every claimed delivery outcome.
Did EPC Group work for the Federal Reserve Bank of New York?
Yes. A Master Agreement dated October 25, 2010, countersigned by both parties, names the Federal Reserve Bank of New York and O’Connor Enterprise Group, Inc. d/b/a EPC Group. The excerpt published on this page carries a SHA-256 hash so the file can be checked against this record.
Why does this engagement not appear in federal contract databases?
The Federal Reserve Bank of New York is not a federal agency, so its procurement is not published in FPDS or USASpending. That is why documentary evidence is published here instead of a government award reference. The absence of a federal award record is expected for this counterparty, not a gap in the record.
Why are the signatures redacted?
Handwritten signatures and the client signatory’s printed name are removed for privacy. The signatory’s title and the execution date are retained, because those are the elements that establish that an authorised representative executed the agreement.
Client names, trademarks and documents are displayed for factual verification of historical business relationships only. Their inclusion does not imply a current commercial relationship, sponsorship or endorsement.
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group