Total Identified Annual Value
—
Integration Innovation serves the Army, MDA, and NASA with 700+ team members and a portfolio spanning systems engineering, AI, and cybersecurity. The next chapter of growth — more contracts, a larger workforce, faster program execution — requires a data foundation equal to the mission.
Figures from Salesforce / Org62 records. BVC inputs are industry benchmarks — to be replaced with i3 actuals.
i3 already invested in Informatica Data Integration to fix a failed legacy data warehouse. These are the gaps that remain — and why a master data and governance layer is the logical next step. Hover or tap any card to see how the platform answers it.
The same customer or contract appears differently in Deltek, the applicant tracking system, and SharePoint. There's no single record a program manager, recruiter, or BD lead can trust — so every cross-department handoff starts with reconciliation.
Clearances, skills, utilization, and availability live in different systems with no common view. Staffing a new contract means calling around rather than querying a record — which slows captures, delays programs, and makes workforce planning a guessing game.
Program managers spend hours each week pulling together a status picture from disconnected systems. Without a unified data layer, leadership visibility into contracts, staffing, and performance requires manual assembly — which is slow, error-prone, and hard to audit.
In January 2026, i3 invested $66,758.40 in Informatica Data Integration and self-implemented it — demonstrating real engineering capability and a genuine commitment to fixing the data problem. That investment is not being replaced. It's being built on.
i3 purchased Informatica Data Integration IPUs and self-implemented, replacing a legacy third-party data warehouse that had failed. Ron Givens led the implementation. The investment reflects real urgency around data silos and fractured reporting.
Informatica MDM, Data Quality, and Governance sit directly on top of IDMC. The integration pipelines Ron built keep running — MDM adds the match-and-merge layer that turns the integrated data into one trusted record per contract, customer, and employee. No rework. No replacement. One coherent platform.
Why this matters for i3: Past enterprise software didn't stick at i3 — Tableau and Slack both lapsed because one person owned them. MDM is different because it serves every team that touches a contract, a person, or a program. Adoption comes from the record itself being more reliable than what each team currently has.
Phase 1 extends the Informatica IDMC i3 already owns with three new capabilities. Roadmap items are clearly labeled — nothing is being sold speculatively. Click any card for what it does specifically for i3.
Match and merge records from Deltek, ATS, and SharePoint into one golden record per contract, customer, and employee.
In Scope · Proposed · $150KFlag stale clearance data, incomplete skills profiles, and duplicate records before they reach a bid response or a program report.
In Scope · ProposedApply field-level privacy tags to clearance and sensitive data, enforce retention policies, and produce audit-ready lineage for Infosec vetting.
In Scope · Proposed · $25KTableau, Data Cloud, Agentforce, and Sales Cloud for BD capture are deliberately out of scope today. They sit as labeled roadmap items throughout this site — not as anything being proposed now — and each one builds directly on the MDM layer being established in Phase 1.
Informatica is the platform core. MDM, Data Quality, and Governance each extend the IDMC Ron's team already configured — not a separate purchase or a new install.
Dr. Sarah Chen appears under different names, IDs, and clearance levels in Deltek, the ATS, and SharePoint. Every cross-department handoff starts with "which one is right?"
Demo note
All names, IDs, and contract numbers are illustrative. The workflow shown is what Informatica MDM + Governance does in production — it's not a mockup of capabilities that require additional configuration beyond Phase 1 scope.
Walkthrough complete
Tap to see what changes across all three focus areas when MDM, Data Quality, and Governance sit on top of the Informatica layer i3 already owns.
Designed for a DoD contractor's Infosec vetting requirements. Click any layer to expand the detail.
Deltek is i3's ERP and system of record for contract financials and labor. The applicant tracking system holds hire, clearance, and skills data. SharePoint holds program documents and assignment records. Each system keeps running unchanged — Informatica reads from all of them. Nothing about these systems changes on Phase 1 go-live.
The Informatica Data Integration IPUs i3 purchased in January 2026 ($66,758.40) run the extract, transform, and load pipelines that pull data from the source systems and make it available for MDM and downstream consumers. Ron Givens configured these pipelines. Phase 1 does not replace or reconfigure these pipelines — MDM sits on top of the data they already produce.
Informatica MDM receives the integrated data from Layer 2, runs a configurable match engine to identify duplicates and related entities, applies survivorship rules to decide which field value becomes the master, and writes a single trusted record to the golden record store. Data Quality rules run in parallel — flagging expired clearances, missing skills, incomplete contract fields — so the issues reach a steward rather than a downstream consumer. This is the core of the $150K MDM line item.
Informatica Data Governance + Privacy IPUs apply field-level access policies to the golden record — so clearance data, SSNs, and other sensitive fields are masked or restricted by role. Complete data lineage records where every field came from and every transformation applied, which satisfies IT and Infosec vendor-vetting requirements (noted as a friction point in the Informatica close plan). This is the $25K Governance + Privacy line item. It also provides the compliance traceability needed as i3 works toward CMMC and DFARS requirements.
These are roadmap items only — not in Phase 1 scope. Once a trusted data layer exists, Tableau dashboards draw from it without manual pre-aggregation. Data Cloud can activate employee and contract records for real-time program management. Agentforce can apply predictive staffing and capture intelligence that i3 currently delivers for its DoD customers to i3's own operations. Slack would serve as the collaborative command center — alerting stewards, routing approvals, and surfacing insights where i3's teams already work. Each of these was suggested by the i3 leadership website, not confirmed in any discovery session.
i3's Infosec and vendor-onboarding requirements were cited as friction in the 2026 Informatica close. This architecture is designed to satisfy those requirements: field-level privacy controls, complete data lineage, role-based access, and a separation of concerns between integration, mastering, and governance that maps to a standard security review framework.
The data foundation serves every team that touches a contract, a person, or a program. Here is what Phase 1 delivers to each of i3's key stakeholders, and what the roadmap makes possible on top of it.
A governed MDM layer on top of the Informatica i3 already owns. Complete data lineage satisfies Infosec vetting. Field-level privacy controls for clearance data. The data quality rules Ron configured are now enforced automatically — not manually verified on each export.
A platform that has earned its Infosec approval once — and never has to go through vendor vetting again for each new capability. Tableau and Data Cloud activate on the same governed layer.
A trusted, governed data foundation — which is the prerequisite for any AI model trained or operated on i3's own enterprise data. Every AI output is only as reliable as the data it's trained on. MDM provides the clean, validated input.
Agentforce and Einstein Prediction Builder can apply the same AI workflows i3 delivers for the warfighter — predictive staffing, program risk scoring, capture intelligence — to i3's own internal operations. Built on the Phase 1 data layer.
The architecture in Slide 7 — source systems untouched, IDMC pipelines extended not replaced, MDM and Governance as a layer above. Separation of concerns between integration, mastering, and governance maps directly to a DoD-grade security review framework.
Data Cloud provides a real-time activation layer on top of the Informatica master records — multi-cloud compatible, with connectors to every system in the current stack and to future systems as i3 grows through program wins and potential acquisition.
A data foundation that supports all three focus areas — Contract Growth, Workforce Readiness, and Program Visibility — from one investment. The BVC on the next slide shows the value model for each. Every number is a benchmark today; discovery replaces them with i3 actuals.
When the data is trusted, the growth strategy has evidence. Capture teams can see exactly which skills, clearances, and program experience are on hand when they write a bid. Business strategy decisions rest on a single version of the truth.
bids × hrs-saved × rate
bids × lift% × ACV
hires × days-saved × daily-rateemployees × util-lift × $350/day × 250 daysPMs × hrs/wk × 52 × reduction% × ratehrs/wk × 52 × reduction% × raterecords × 12% duplicate rate × $50 / recordAll inputs are industry benchmarks until replaced with i3 actuals during discovery. Values are directional estimates for executive discussion, not a guarantee of results. The $200K investment covers Informatica licensing; implementation services are priced separately through the implementation partner.
Three outcomes that move all three focus areas forward — before a single line of new code is written.
A half-day with Betsy, Ron, and Zak to map i3's entity types (contract, customer, employee, program), define survivorship rules, and agree on the scope for Phase 1 MDM configuration. This session replaces every discovery assumption in the BVC with real i3 numbers.
A structured review of the IDMC implementation Ron built — what's working, what the IPU consumption rate implies about scale, and whether the current configuration is the right foundation for MDM and Governance to build on. Ravi Rangas leads alongside Ron.
A conversation with IT, the Information Assurance Manager, and the ISSO to document i3's specific compliance requirements — CMMC level, CUI handling, field-level access policy needs — so the Governance + Privacy IPU configuration is right-sized from day one.
The next step is a 30-minute conversation with JJ, Ravi, and the Informatica team to scope the MDM design session and confirm the Infosec requirements. Everything in the business case above updates the moment we have i3's real numbers.