Skip to main content
Northrop Grumman/2010

Finance I.R.M. Automation Process for Northrop Grumman

Finance I.R.M. Automation Process for Northrop Grumman

EPC Group was contracted by Northrop Grumman under a purchase order issued October 28, 2010, with buyer authorization dated October 29, 2010.

The purchase order describes the engagement in its own words as the "Finance I.R.M. Automation Process." The order forms page 1 of a 19-page document set; the referenced EPC quote and statement of work are not published.

Scope note. No technology is named anywhere in the published purchase order text. The record is filed under a SharePoint-era URL, but the document itself identifies no product. This case study therefore describes the engagement as the purchase order describes it — a finance process automation initiative — without attributing a platform.

Automate work

Northrop Grumman contracted an engagement the purchase order describes, in its own words, as the "Finance I.R.M. Automation Process." No technology is named anywhere in the published purchase order text, and the referenced EPC quote and statement of work are not published, so the detailed requirement is not part of the public record.

The agency's contribution

EPC Group was engaged for the "Finance I.R.M. Automation Process" as stated on the purchase order issued October 28, 2010, with buyer authorization dated October 29, 2010. The published order forms page 1 of a 19-page document set. Because the referenced quote and statement of work are unpublished and the order names no product, EPC Group describes the engagement as a finance process automation initiative without attributing a platform.

What was delivered

Finance I.R.M. Automation Process as stated on the purchase order
Results shared by the agency

No business-outcome metric is claimed for this engagement, and no baseline-versus-result comparison is published. The verification performed here is documentary rather than statistical. The contracted scope described above is checked line by line against one primary-source document — a purchase order issued October 28, 2010 by Northrop Grumman with buyer authorization dated October 29, 2010, forming page 1 of a 19-page set and stating the scope as "Finance I.R.M. Automation Process", reproduced in EPC Group's Evidence Center as rasterised page images with redactions burned into the pixels — carrying no text layer, annotations, form fields, or metadata. Evidence tier: Contracted — verified against one primary-source document. The order's value is neither published nor characterised. The published record does not establish that the contracted work was completed or accepted, and no measured business outcome is claimed.

Measurement period: Purchase order issued October 28, 2010; buyer authorization dated October 29, 2010

Context and limitations: No technology is named. The published order text identifies no product or platform, so none is attributed — the record is filed under a SharePoint-era URL, but the document itself names no product and EPC Group makes no platform claim. Only page 1 of a 19-page document set is published; the referenced EPC quote and statement of work are not. The order's value is neither published nor characterised, and no automation volume, cycle-time, or efficiency figure is claimed.

Northrop Grumman Global Intranet Implementation by EPC Group - SharePoint Global Rollout Enterprise Content Management
Northrop Grumman Global Intranet Implementation by EPC Group - SharePoint Global Rollout Enterprise Content Management

Challenge

The published purchase order names the engagement — Finance I.R.M. Automation Process — but does not elaborate on the requirement.

What can be stated from the public record:

  • **The subject was a finance process.**The order situates the work in the finance function rather than general IT. -Automation was the objective."Automation Process" is the order's own characterisation of the work. -Scope was defined elsewhere. The purchase order references an EPC quote and statement of work, neither of which is published. The order is page 1 of a 19-page set.

Beyond this, no challenge narrative is part of the public evidence record. EPC Group publishes no scope detail for this engagement, and this case study does not infer one — including no inference about which technology platform was involved.

Solution

EPC Group was engaged against a purchase order whose description of the work is "Finance I.R.M. Automation Process."

Engagement structure-Purchase order issued October 28, 2010by Northrop Grumman, with buyer authorization October 29, 2010. -**Page 1 of a 19-page document set.**Only the first page is published. -Scope governed by an EPC quote and statement of workreferenced by the order. Neither is published, so the detailed scope is unavailable.On technology attributionThe published purchase order text names no product or platform. Although this record sits under a SharePoint-era URL within the Evidence Center, the document itself does not identify SharePoint or any other technology. No platform is asserted here.What this record establishes

That Northrop Grumman issued a purchase order to EPC Group in October 2010 for a Finance I.R.M. Automation Process engagement. It does not establish completion, acceptance, deliverables, or any measured outcome.

Results

**Documented engagement record.**This entry reflects what is evidenced by primary-source contract documents published in EPC Group's Evidence Center. Consistent with EPC Group's evidence methodology, no completion, acceptance, or business-outcome claim is made for this engagement.What the published documents establish:-Purchase order issued October 28, 2010by Northrop Grumman, buyer authorization October 29, 2010 -Contracted scope as stated on the order:"Finance I.R.M. Automation Process" -**Evidence tier:**Contracted — verified against one primary-source document -**Document set:**the published page is page 1 of a 19-page set; the referenced EPC quote and statement of work are not published -**No technology named.The published order text identifies no product or platform, so none is attributedBoundaries from the published record:**the order's value is neither published nor characterised, and no completion, acceptance, or measured outcome is claimed.Verification. Each published excerpt is rebuilt from a rasterised page image with redaction boxes burned into the pixels, carrying no text layer, annotations, form fields, or metadata. Commercial amounts are redacted as a matter of policy.

Source documents: epcgroup.net/evidence/northrop-grumman-sharepoint-2010

Technologies & Tools

Process AutomationFinance Systems
Watch Project Video

The purchase order calls this the "Finance I.R.M. Automation Process," and that is the most specific language the public record contains. The document names no technology at all. It sits under a SharePoint-era URL, which would make it easy to imply a platform — so we state explicitly that none is attributed, because the paper does not support one.

Errin O'Connor, Founder and Chief AI Architect

Project Details

Year

2010

Client Websitenorthropgrumman.com
Live ProjectView →