scope is limited to simulation
- BBSIM status, performance, adequacy as the detailed simulation of the final detector design
- Aslund ditto as a physics performance evaluation tool for the final detector design
- Coupling of simulation to downstream computing; interfacing to C++-based reco and real data
- Status and future of key simu tools (geometry database, simu output) and migration path to long term solutions
- Final simulation design
  - Geant4 viability as the underlying toolkit: feature set, timescale
  - G4-based simu design
  - Migration path from today to final simu
  - fast simulation integration into Geant4 for a unified simulation with selectable levels of detail
  - first prototype (limited geometry) in place?
- Production system performance, scalability, long term plans

What should we have in place?

Geometry and materials up to date with respect to engineering design
BBSIM output satisfies requirements of reconstruction, trigger codes in their present state of development. Requirements eg. for sophistication of digitizations will vary among subsystems
Digitization completely outside BBSIM, in Framework, not necessarily all C++ (but preferably of course)
Clean geometry interface to C++ as well as Fortran
Aslund geometry up to date, preferably derived from geometry database
Completed round of Aslund parametrization updates based on current full simulation
Partial Aslund interface to reconstruction objects for Framework based Aslund analysis?
BBSIM and Aslund near term todo lists well in hand.
Documented long term plan and system design, with migration plans for short term solutions (geometry db, event IO)
Assessment of anticipated physics capability in Geant4 relative to Geant3 and our needs
Demonstrated compatibility of Geant4 hits/digi design with BaBar multi-stage (raw & feature extracted) digitization
BaBar Geant4 prototype, fast simulation oriented, with basic geometry, tracking to subdetector volumes, tracking preemption by fast simulation code
Graphics available in the prototype (via our graphics toolkit)
Advancement of automation level of production bookkeeping over what exists now; comfortable 1 year extrapolation
Resource requirements and availability assessment, 1 year and longer term
Adequate data compatility and analysis transparency among production data sets (versioning issue)
generators for the physics and background channels currently needed by simulation's consumers (trigger and physics performance studies, reconstruction and analysis development, etc.) available in the simulation, with full Monte Carlo truth information provided in simulation output