What is the team size for a typical engagement?
Advisory review: Nam Pham solo. Embedded support: Nam Pham lead + 1-3 ESEC engineers. Program oversight: Nam Pham lead + 1-3 ESEC engineers + 2-5 specialist collaborators.
Team and Collaborators
The pharmaceutical automation and GxP validation practice is built on a small, focused team with deep domain expertise, supported by a network of trusted collaborators for specialized scopes.
Operating model
Senior-led engagements: every project is led by Nam Pham with 10+ years of experience. Specialist network: for scopes that require specialized expertise (OT cybersecurity, AI/ML, regulatory), the practice engages a vetted network. Client capability building: every engagement includes client team training, so the client can own the system after the engagement ends.
Core team and ESEC network
Nam Pham — Principal, Pharmaceutical Automation Engineer. ESEC engineering network — historian deployment, OT network design, on-site validation testing (5-10 engineers available for short-term and embedded engagements).
Trusted collaborators
OT cybersecurity specialists (IEC 62443, penetration testing, incident response). AI/ML and data science (AI readiness, MLOps, model validation). Validation testing (large-scale IQ/OQ/PQ execution). Regulatory affairs (pre-IND, IND, NDA submissions).
What we do not do
We do not provide bodies for routine staffing. We do not white-label for other consultancies. We do not take on engagements where the client does not have a named sponsor.
How to use this page
Use this Team and Collaborators page as a planning checkpoint before vendor selection, architecture review, validation scoping or implementation sequencing. The strongest next step is to compare the guidance with your current SOPs, system inventory, batch records, data flows and QA review routines so the discussion starts from evidence instead of assumptions.
Evidence to prepare
For Team and Collaborators, prepare the records, owners, risks and decision criteria linked to operating model, core team and esec network, trusted collaborators, what we do not do. Useful evidence includes current process maps, interface lists, audit trail expectations, exception workflows, data retention rules and the business reason for changing the current operating model.
Frequently asked questions
How do I become a collaborator in the network?
Send a note via /contact with areas of specialization, years of pharma experience, sample project descriptions, and current capacity. Applications are reviewed quarterly.
Is the practice part of ESEC?
The practice is associated with ESEC (East Sea Energy Environment) for the engineering backbone, but the practice operates as a distinct pharmaceutical-automation focus area with its own engagements and engagements.