01
Documentation as the knowledge layer
Environment Summary, Upgrade Roadmap, Phase review. Owner on the cover. Utilization first. What was changed. What is still unofficial. That is Forge + Lattice with receipts, not a wiki dump.
Forge · Lattice · Stratum · written operating path
Knowledge layers fail without owners.
Agents fail without a measured definition of the customer.
This is how I leave the account running Forge without me in the chair.
Edisyl is hiring the person who makes the promise real inside data that was never prepared for an agent. The IPS artifacts are that motion on paper: what is running, what is on fire, what to change, how to prove it, and who on the client team can run it after go-live. Same loop as a knowledge-layer deployment — measure, isolate, write the standard, coach the team.
Three surfaces for this role
01
Environment Summary, Upgrade Roadmap, Phase review. Owner on the cover. Utilization first. What was changed. What is still unofficial. That is Forge + Lattice with receipts, not a wiki dump.
02
Baseline, goal, bottleneck, eliminate, repeat. Thread statistics before folklore. Farmers 30+ repos hanging a domain is the same failure mode as an agent with three definitions of an active patient.
03
Named skill-up. Walked loads. Whole stack in one room. The team praised in writing. Edisyl’s year-one line is playbooks from the field and clients who ask for you by name. That is this file.
Google Drive · IPS artifacts · 2017 floor
Not a slide with a logo. Owner, date, environment evidence, what was already changed, what is still open, and the recommendation the customer can execute without you in the building. These are the files from Drive: Environment Summary, Upgrade Roadmap v3, Phase 2 review, PC 10 deck.
Author and owner on the cover. Overview of how mixed internal / consultant / offshore developers actually use the platform. Then a numbered review of what was measured and changed — not a wish list.
Current-state performance review, then the product recommendation: PowerCenter with Grid and HA. Internal domain/gateway/node design. External clustering and the shared filesystem that makes or breaks Session on Grid.
Phase 2 is not “more of Phase 1.” Name the product features the next workload actually requires, the topology that will hang, the filesystem that will plateau partitioning, and the skill-up the team still needs.
Jeremy Panasuk / Informatica Professional Services. Why v10, PAM, three upgrade types, six classes of test, Data Validation Option to make same-data honest.
Edisyl translation. Environment Summary is the knowledge layer with owners — vocabulary in the systems vs vocabulary in the heads. Farmers’ 30+ repos hanging a domain is the same failure mode as an agent with three definitions of an active patient. Phase review = the next implementation is cheaper. Coaching named in the write-up is year-one success: playbooks from the field, clients who ask for you by name.
Sample Documentation · xyz teaching templates
Google Drive folder Informatica / Sample Documentation. Same author as the named floors. Cover says xyz. The operating path is identical. Public copy still does not publish hostnames, UNC aliases, or raw capacity tables.
Author and owner: Jeremy Panasuk. Company on the named original: Mercedes-Benz Financial. This is the file with the performance cheat sheet inside.
Author and owner: Jeremy Panasuk. Low utilization is a finding. Config that was actually applied is listed by number.
Author: Jeremy Panasuk. Two-node Windows 2008 VMs, 4 cores / 16 GB each. PowerCenter 9.1.0 plus Data Quality 9.6.1. A month of graphs, not a hallway anecdote.
Author: Jeremy Panasuk. Phase 2 is not more of Phase 1. Guidewire Advanced XML and real-time web-service consumers.
Why v10, PAM first, three upgrade types, six classes of test, Data Validation Option so same-data is honest.
These five files are the kit. Named copies (MBFS, Northwestern Mutual, Waddell & Reed, Farmers) are the work. xyz copies are how the next IPS consultant was taught to write the same document. Hostnames, UNC aliases, and capacity tables stay off this site.
Performance methodology · MBFS cheat sheet
Left inside the Mercedes-Benz Financial Environment Summary. Same loop as a GPU routing bench: a baseline that is allowed to be slow, a goal, one change between runs, notes that make the next person dangerous.
Upgrade operating path · PC 10 deck
The v10 overview is the coaching deck. The roadmap is the customer-specific evidence. Together they stop an account from “just running the installer.”
| When | Type | Why |
|---|---|---|
| Very short cycle, many installs already certified in a sandbox | In-place | No extra schemas. Users/groups stay. Outage for domain restore. Cannot change domain or node names. |
| Longer cycle, tight outage, want new names | Parallel | Fresh server + repo snapshot. No domain-install outage. Migrate users/groups. Small settings-drift risk. |
| Pre-prod go-live, minimize settings drift | Clone | Identical domain snapshot. Fast like-for-like. Still an outage. Cannot rename. Extra HTTPS caveats. |
Smoke: installer, domain start, repo wizard, services, connectivity, a workflow runs, client login.
Full, partial, or automated regression. The longest bar on the plan. DVO exists so you test all rows, not a sample.
External: injection, SSL, DB grants, open ports. Internal: admin passwords, folder / connection / tool rights.
Client, integration service, server, network. Equal or better than the legacy environment — with numbers.
Schedulers, SVN, deploy frameworks, encryption, file transfer, customer monitors. The item people skip.
HA = single-instance failover, measured in uptime. DR = data-center loss, measured in recovery time and stagnation.
Customer coaching
Customer satisfaction is worthless. Customer loyalty is priceless. Knowledge transfer is a deliverable. Skill-up is named in the architecture review. The whole stack sits in one room with GCS. The team is praised in writing. Loyalty is the runbook they keep.
The receipts in the files
Anonymized “xyz” copies were the teaching templates. The named copies are the work. This site carries the operating findings, not hostnames.
QA/prod domains brought to best practice (ulimit 64k, DB2 repo settings, concurrent jobs 500, heap, stale NFS logs). P1 workflow-start delay: GCS escalation, DB2 semaphore on the Informatica client. Grid/HA TCO path and a QA twin of production.
ALFA→ODS at 100% CPU. Cache RAM raised so large transformations stop spilling to disk — 20–30% runtime drop. PWX CDC POC vs bulk load. Performance cheat sheet and load walkthroughs left with the team.
2-node 9.1.0 grid measured for a month: 80–90% CPU, RAM under-used, disk wait 30–90 ms, SQL wait past 200 ms. UNC is not an HA filesystem. Upgrade types + six-class test plan. Adaptive dispatch, homogeneous nodes, Linux CFS.
Guidewire advanced XML and real-time consumers. 30+ repos / integration services as domain risk. NFS vs Veritas/GPFS. Skill-up named. Outstanding demos: Operational Insight and Advanced XML on their schema. Team praised in the write-up.
Informatica TDM 9.5.2 HF1 in Shared Analytics on AIX: PHI masking and subset so non-production is not production. Reusable generic rules (type + technique), POL_PHI / POL_PII wrappers, one table per assigning plan so PowerCenter masking workflows can run concurrently. LDAP groups for authorization. Discovery profiles before anyone guesses which columns are sensitive. Cover: IPS TDM Expert Aditya Mohanty. Platform: Jeremy’s 3,000-hour V1 — install, services, naming standards, go-live tests. Hostnames and production inventory stay off this copy.
Source artifacts from Google Drive: Northwestern Mutual Environment Summary (Apr 2017, Jeremy Panasuk, IPS); Mercedes-Benz Financial Environment Summary + cheat sheet (Jun 2017, Jeremy Panasuk, IPS); Waddell & Reed Upgrade Roadmap v3 (Jun 2017, Jeremy Panasuk, IPS); Farmers Phase 2 Architecture Review (Oct 2017, Jeremy Panasuk, IPS); PowerCenter 10.0.0 Upgrade Overview (Jeremy Panasuk, IPS); Navy Federal TDM-PHI masking Development Guide, TDM 9.5.2 HF1 (cover: Aditya Mohanty, IPS TDM Expert). Anonymized “xyz” copies were teaching templates. Internal hostnames, credentials, and production table inventory are not published.