Overview
All of the inputs and outputs associated with a package's model are stored in a single file (with an extension of .ssim). This file is referred to as a SyncroSim library.
When a library is first created (using the New... option on the File menu), SyncroSim automatically creates the database schema (in SQLite format) required to store all the inputs and outputs required by the package in the library file. The inputs and outputs of a library are organized into datasheets, which consist of a single table of data, although there are times when several datasheets are combined to form a datafeed.
SyncroSim also allows users to (optionally) subdivide their library into projects. Projects, in turn, can contain any number of scenarios. New projects can be created using the New Project... option on the Edit menu, while scenarios can be created using the New Scenario option on the Scenario menu.

To illustrate this concept, in the example shown above we see a hypothetical library in the SyncroSim Studio Explorer: Library A. We have further divided Library A into two projects: Project A-1 and Project A-2. Each project, in turn, contains a number of scenarios.
Note
Every project and scenario is automatically assigned a unique ID when it is first created. The ID value for each scenario is displayed in square brackets before the scenario name in the Explorer, while the ID value for each project is shown on the project's summary datasheet,
All of the data associated with a particular library are organized into datasheets. There are three types of datasheets:
- Library datasheets contain data that is specified only once for the entire library. These are typically global settings for your model.

- Project datasheets contain data specified only once for each project. These are typically Definitions for a model - i.e. values that must be consistent across scenarios in order for the results of multiple scenario runs to be meaningfully compared.

- Scenario datasheets contain data that are specified once for each scenario, including both model inputs and outputs.

Note
By default an empty library always starts with a single project named Definitions and a single scenario named New Scenario.
Tip
To help keep your library organized, both projects and scenarios can be further organized into nested folders in the Explorer using the New Folder... option on the Edit menu.