Haskell — Power BI Report Server to Power BI Service Migration (2019): Evidence Record
Claim level: Contracted — countersigned
Verified against the 1 primary source document and 2 redacted page images published on this page. Every published file carries a SHA-256.
On January 30, 2019 EPC Group issued Haskell a statement of work for a 150-hour migration from Power BI Report Server to the Power BI Service, version 2.0. A Haskell director-level signatory countersigned it on February 11, 2019. The cover and execution page are published here as redacted images with SHA-256 hashes.
Engagement fact, as the document states it
Statement of Work "SOW for Haskell Power BI Report Server to Power BI Service Migration Initiative", version 2.0, dated January 30, 2019: a 150-hour block of Power BI consulting services, executed for EPC Group on January 30, 2019 and countersigned for Haskell on February 11, 2019 by a director-level signatory (handwritten title: Dir. Ent. Apps).
Delivery status: completed and paid in full per EPC Group’s accounts-receivable record (EPC-reported, 2026-10-15). EPC Group treats payment as acceptance; no client acceptance record is published for this engagement.
- Discovery and assessment of the existing Power BI Report Server environment and guidance for moving to the Power BI Service (SOW-stated scope)
- An end-to-end migration plan, Power BI Service branding and theme development aligned with Haskell's guidelines, and an app and workspace strategy (SOW-stated scope)
- Migration support for existing reports and data into the Power BI Service, with post-deployment support; 150-hour block purchase (SOW-stated scope)
150 hours or units as stated on the document. Period on the paper: 2019-01 (no end date is stated on the published documents).
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 | Haskell (as printed on the statement of work) |
| EPC contracting entity | EPC Group — O'Connor Enterprise Group, Inc., doing business as EPC Group |
| Document type | Statement of Work, version 2.0, countersigned by both parties |
| Effective date | January 30, 2019 (EPC Group signed); countersigned February 11, 2019 |
| Engagement | Power BI Report Server (June 2017 release) to Power BI Service migration |
| Block purchased | 150 hours |
| Client signatory | Director-level signatory, handwritten title Dir. Ent. Apps (name redacted) |
Source documents
SOW for Haskell Power BI Report Server to Power BI Service Migration Initiative, version 2.0 — 150-hour initiative
- Document type:
- Statement of Work (countersigned)
- Date:
- January 30, 2019 (countersigned February 11, 2019)
- Issuer:
- EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group), countersigned by Haskell
- Published:
- Cover (page 1) and execution page (printed page 11) of 11, redacted
What this document establishes
- EPC Group issued a statement of work to Haskell on January 30, 2019 for a 150-hour Power BI Report Server to Power BI Service migration initiative.
- A Haskell signatory countersigned it on February 11, 2019; both parties' execution blocks are on the published page.
What it does not establish
- That the 150 hours were consumed, that the migration was completed, or that Haskell accepted any deliverable.
- Any amount invoiced or paid.
- Any outcome, report count or adoption figure.
Redactions applied
- The preparer line on the cover (name, direct telephone, main office number and e-mail)
- Both handwritten signatures and the client signatory's handwritten name on the execution page
- The pricing and hourly-rate pages, and the Microsoft credit line, are not published at all
No client name, EPC Group identity, project description or date has been altered.
What this page does not claim
- Delivered: no acceptance form, closeout letter or client sign-off is published; the public documents do not establish that the contracted work was completed or accepted — both are EPC-reported from EPC Group's own delivery and accounts-receivable records (see the delivery status line).
- Paid: no client remittance or payment record is published; the public documents do not establish payment — payment in full is EPC-reported from EPC Group's own delivery and accounts-receivable records (see the delivery status line).
- Outcome: no business result, adoption figure or satisfaction measure is claimed; the page states what the instrument says and nothing more.
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.
Basis for publication: written consent of the client. The owner's written instruction of 2026-10-15 (checkpoint word HASKELL keep; Addendum 10 item 140), not a client letter. No confidentiality or publicity clause appears in the statement of work (full-text search of the OCR text on 2026-10-15).
Text transcripts: 01 · 02 — 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 Haskell?
Haskell contracted EPC Group for Power BI Report Server to Power BI Service migration services in 2019; this record publishes 1 primary-source document at claim level "Contracted — countersigned". EPC Group publishes historical contracting records supporting this engagement; the published material does not establish every claimed delivery outcome.
Why is the client signatory's name not shown?
The handwritten name and both signatures are removed for privacy; the handwritten title and the execution date are retained because they establish that an authorized Haskell signatory executed the document on February 11, 2019.
Does this record say the migration succeeded?
No. It establishes the contracted scope, the hours purchased and the execution of the instrument. Delivery, acceptance and results are not evidenced by the published documents; completion, acceptance and payment are EPC-reported from EPC Group's own records (see the delivery status line), and no result is claimed.
Case study for this record
Haskell: Power BI Report Server to Service Migration (2019) — project ID EPC-2019-HASKELL-PBIRS · service: Power BI Consulting
Related evidence records
- Haskell — Contracted — countersigned
Service pages this record supports
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