Northrop Grumman — 'Finance I.R.M. Automation Process' statement of work on SharePoint (2010)
ContractedFirst-pass editionNorthrop Grumman · 2010 · Project ID EPC-2010-NGC-FIRM
Evidence record: Northrop Grumman evidence record with redacted documents and SHA-256 hashes
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Contracted. Northrop Grumman engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for 'Finance I.R.M. Automation Process' statement of work on SharePoint — per Northrop Grumman purchase order referencing EPC Group's quote and statement of work. Project ID EPC-2010-NGC-FIRM. 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 2010, EPC Group completed 'Finance I.R.M. Automation Process' statement of work on SharePoint for Northrop Grumman on SharePoint Server, led by EPC Group's senior architects addressing a manual finance process that needed automation on the SharePoint platform. The work ran through EPC Group's delivery lifecycle as EPC Group describes its engagements: assess, modernize, govern, operate, enable. 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; 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
| Field | Value | Source |
|---|---|---|
| Client | Northrop Grumman | document |
| Industry | Aerospace and defense | document / public record |
| Engagement date | October 28, 2010 | document |
| Work | 'Finance I.R.M. Automation Process' statement of work on SharePoint | document |
| Microsoft products | SharePoint Server | document / scope |
| Scope unit | per Northrop Grumman purchase order referencing EPC Group's quote and statement of work | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | EPC Group senior architects (the published instrument does not name the lead; EPC-reported) | EPC-reported |
| Delivery status | Completed; invoiced and paid in full. Source: EPC Group's accounts-receivable record (paid invoices on file, not published because they carry commercial terms), stated by Errin O'Connor on 2026-10-15. EPC Group treats payment as acceptance; no client acceptance record is published for this engagement. | EPC AR record (EPC-reported) |
| Verification class | Contracted; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | https://www.epcgroup.net/evidence/northrop-grumman-sharepoint-2010 | — |
| External source | none published yet | — |
| Project ID | EPC-2010-NGC-FIRM | EPC Group |
What the document states
Purchase order (October 28, 2010) authorised by a Northrop Grumman buyer, referencing EPC Group's quote and the statement of work 'Finance I.R.M. Automation Process'. EPC Group separately reports that it led an eRoom to SharePoint Online migration for Northrop Grumman involving about 18 terabytes of content (EPC-reported; instrument not published).
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a finance organization's Information Resource Management process in an aerospace and defense company, and the SharePoint platform it ran on. 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)
A manual finance process that needed automation on the SharePoint platform.
EPC Group's responsibility
The 'Finance I.R.M. Automation Process' statement of work referenced by the purchase order.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are process design, workflow automation approach on SharePoint, and integration with existing finance systems. The decisions actually taken for Northrop Grumman will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: process analysis → design → build → validation. Dates and acceptance for this engagement will be stated from the project record.
Results
| Metric | Baseline | Observed result | Period | Source | Verification class |
|---|---|---|---|---|---|
| Scope delivered against the instrument | as contracted | Completed; invoiced and paid in full | engagement period | EPC AR record (paid invoices on file; not published) | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Client acceptance | — | Deliverables accepted; EPC Group's objectives met | close-out | payment in full + EPC-reported | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Primary technical outcome (migration completeness, platform live, deliverable detail) | pending | pending project record | — | project record | pending |
| Service interruption during cutover (where applicable) | planned window | pending | cutover | cutover log | pending |
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/northrop-grumman-sharepoint-2010 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)
- Automate the process as the business runs it, then improve it — not the other way around.
Related service
SharePoint business-process automation ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.