supply-chain-simulation-engine
Supply chain discrete-event simulation for scenario testing and optimization
What this skill does
# Supply Chain Simulation Engine
## Overview
The Supply Chain Simulation Engine provides discrete-event simulation capabilities for testing supply chain scenarios, policies, and disruptions. It enables what-if analysis, Monte Carlo integration, and performance optimization through simulation-based experimentation.
## Capabilities
- **End-to-End Supply Chain Simulation**: Full network modeling
- **What-If Scenario Testing**: Policy and configuration testing
- **Disruption Impact Modeling**: Shock and recovery simulation
- **Policy Optimization Testing**: Inventory, sourcing policy experiments
- **Monte Carlo Integration**: Stochastic variability modeling
- **Sensitivity Analysis**: Parameter impact assessment
- **Animation and Visualization**: Visual simulation playback
- **Performance Metric Tracking**: KPI measurement through simulation
## Input Schema
```yaml
simulation_request:
network_model:
nodes: array
- node_id: string
type: string # supplier, plant, DC, customer
capacity: float
processing_time: object
inventory_policy: object
arcs: array
- from_node: string
to_node: string
lead_time: object
cost: float
demand_model:
patterns: array
variability: object
events: array # promotions, seasonality
supply_model:
reliability: object
variability: object
simulation_parameters:
run_length: integer
warm_up_period: integer
replications: integer
random_seed: integer
scenarios: array
- scenario_name: string
parameters: object
```
## Output Schema
```yaml
simulation_output:
results_summary:
scenarios: array
- scenario_name: string
kpis:
fill_rate: object
inventory_turns: object
lead_time: object
cost: object
confidence_intervals: object
detailed_results:
time_series: array
event_log: array
bottleneck_analysis: object
scenario_comparison:
comparison_matrix: object
statistical_tests: object
best_scenario: string
sensitivity_results:
parameters_tested: array
impact_analysis: object
critical_parameters: array
optimization_insights:
recommendations: array
trade_offs: object
visualization_data:
animation_data: object
charts: array
```
## Usage
### Inventory Policy Simulation
```
Input: Network model, demand patterns, inventory policies
Process: Simulate multiple policy scenarios
Output: Policy comparison with fill rate and cost
```
### Disruption Impact Analysis
```
Input: Current network, disruption scenario
Process: Simulate disruption and recovery
Output: Impact quantification and recovery timeline
```
### Network Configuration Testing
```
Input: Alternative network configurations
Process: Simulate each configuration
Output: Configuration comparison and recommendation
```
## Integration Points
- **Simulation Platforms**: AnyLogic, Simul8, SimPy
- **Data Sources**: ERP, planning system data
- **Optimization Tools**: Combine with optimization
- **Visualization Tools**: Animation and dashboards
- **Tools/Libraries**: AnyLogic, Simul8, SimPy, discrete-event simulation
## Process Dependencies
- Supply Chain Network Design
- Business Continuity and Contingency Planning
- Capacity Planning and Constraint Management
## Best Practices
1. Validate model against historical data
2. Use adequate replications for statistical validity
3. Include warm-up period for steady-state analysis
4. Document model assumptions
5. Involve operations in model validation
6. Use sensitivity analysis to identify key drivers
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.