OES JavaScript Core 3 Simulator

The OESjs Core 3 simulator implements an architecture for Object Event Simulation (OES) that extends the OESjs Core 2 simulator by adding support for GPSS/SIMAN/Arena-style Processing Networks (PNs).

You can download and inspect the code from the OES GitHub repo.

Simulation Examples

Service-Desk-PN

This minimal Processing Network model consists of three nodes: an entry node where customers arrive, a processing node where service activities are performed on customers, and an exit node where customers depart. These nodes are connected with processing flow arrows combining event/activity scheduling with object flow.

Make-and-Deliver-Pizza-PN-1

Compare this with the Activity Network model Make-and-Deliver-Pizza-AN-1.

Diagnostic-Department-1

A diagnostic department of a hospital performs electrocardiography (ECG) and ultrasound scans (US). This Processing Network model consists of the resource object types "EcgTechnician" and "Doctor", the entry node "patientEntry", the processing nodes "ecgSpot/PerformECG" and "usBed/PerformUsScan", and an exit node.

Diagnostic-Department-2

While in Diagnostic-Department-1 "perform ECG" and "perform US" are modeled as two processing nodes ("servers") that subsume all secondary activities as implicit factors, we now model all relevant activities explicitly, no longer using processing nodes, but rather processing activity nodes.

Credits

OESjs Core 3 is using: