← all publishers

nelchandler

@nelchandler source repo

Report this profile Claim this profile

• 2 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Simulation Engineer · nelchandler bundle

   Operations Research and simulation engineering agent. Designs, codes, verifies, validates and runs stochastic simulation models — discrete-event (simpy), agent-based (mesa), system dynamics, Markov/Bayesian — following a strict 8-step simulation lifecycle with statistical rigor: distribution fitting, Welch warm-up, replication counts from a target confidence interval, variance reduction, ANOVA across scenarios. Use whenever the user wants to simulate, model or size anything stochastic — queues, capacity, staffing, throughput, lead times, inventory, risk or "what are the odds" questions, load models, agent populations, sensitivity sweeps, what-if scenarios. Use it when the user types START and expects the OR workflow. Use it too when simulation code is slow, noisy, non-reproducible or producing numbers nobody trusts — including when you merely see simpy, mesa, np.random, random.seed, a replication loop or a results-averaging script and the word "simulation" is never spoken.
   0 installs
2. ▌
   Continuous Improvement · nelchandler bundle

   Lean Six Sigma Master Black Belt and continuous improvement agent. Runs DMAIC — Define, Measure, Analyze, Improve, Control — as a gated state machine with statistical rigor: process capability (Cp, Cpk, Pp, Ppk, DPMO, sigma level, rolled throughput yield), measurement system analysis, SPC control charts (X-bar/R, I-MR, p, c, u) with Nelson rules separating common from special cause, hypothesis testing to prove root causes rather than guess them, DOE, and control plans that hold the gains. Use whenever the user wants to improve, optimize, stabilize or de-bottleneck a process — defect rates, cycle time, lead time, throughput, rework, yield, deployment failure rate, incident volume, variation, waste. Use it when the user types START and expects the DMAIC workflow. Use it too when someone asks why a process got worse, whether a change helped, or what the root cause is — and when you merely see defect counts, cycle-time logs, a before/after comparison or a run of measurements someone is eyeballing for trends.
   0 installs