Loading color scheme

Boston Enterprise
Cloud-based conceptual modelling

Develop your Enterprise Model from anywhere in the world using Boston Enterprise. Do your enterprise modelling in a web browser. Open Boston Enterprise in your browser, Mac or PC, in full screen mode and use Boston as if it were installed on your computer.

Collaborate with your team no matter where they are in the world.

Install Boston Enterprise on your own server (contact FactEngine for pricing) or use a FactEngine configured cloud service.

Rich Windows Experience - In A Web Browser

Boston Enterprise is Boston virtualised in a browser. That means you get the rich experience of a Windows application right from your browser, wherever you are in the world.

Have all the features you expect in an Windows application, including

  • Drag-and-drop;
  • Windows help;
  • Right-clicking to access contextual menus; and
  • Tabs

The Boston Enterprise experience is the same as your Boston Professional desktop experience.


No Installation Required

If you choose Boston Enterprise in the cloud there is no need to worry about maintaining installation files for Boston. Simply log-in with your username and password from a web browser.



Collaborative Modelling

Boston Enterprise supports:

Users   Groups
Projects   Roles





User login details, the Roles they play, and the Groups they participate in are established in Boston Enterprise so that teams can collaboratively work on conceptual modelling and have access to the FactEngine database query tool.


Groups are a collection of Users within Boston, and for which Permissions can be set on Projects that include those Groups.

For instance, when editing the "Nolana Health Care" Group for the fictitious Nolana Health Aliance company, a Group of Users with access to Boston can be created.
The image below, shows a list of Users allocated to the Group and as apposed to the list of available Users who have access to Boston.

NB Groups are allocated to Projects via the Edit Project form, and play no other role other than to be able to have Group based Permissions for Users within that Project.


Projects are placeholders for Users and Groups, and that ultimately provide access to Models allocated to Namespaces of the Project.
NB Models, in Boston, are allocated to Namespaces, and Namespaces to Projects. I.e. Models are allocated to the Namespace under which they are created.
NB "Default" is the name of the default Namespace for a Project, and many Projects may only ever use that one Namespace. So, in that instance, one can say that Models are accessed via their Project.

Here are a set of rules that apply to Projects:

1. Users are allocated to Projects, along with the Role/s they play on that Project;
        See the image below, where we are editing the Roles played by the User, Victor Morgante, within the Nolana Health Care Project.

2. Permissions are allocated to Users within a Project, and where Permissions supersede the Functions of the Roles played by that User on the Project;
        See the bottom of the image below, where the Permissions for the User, Victor Morgante, are set within the Project.
        NB Group Permissions are more restrictive than User Permissions, see also below.

3. Groups are allocated to Projects, and where Permissions are allocated to each Group within the Project.
        NB Group Permissions are more restrictive than User Permissions.

4. Namespaces are created for Projects;
        NB Models are allocated to the Namespaces under which they are created.

5. Models can be shared between Projects. I.e. A Model created under a Namespace within one Project can be shared with another Project.