Integrated Apps & 3rd Party Solutions

Scan the QR Code to download the LaunchPoint Mobile App.

Download LaunchPoint Mobile App on: Google Play and Apple Store

Download the User Guide for: LaunchPoint Mobile App Guide (for On Premises)

Galaxy DoorPoint and PersonPoint mobile apps are no longer supported as of SG 11.8.6

For information about Galaxy LaunchPoint Cloud Concierge, contact Galaxy Customer Service.

Galaxy’s LaunchPoint Web App (on premises, thin client) supports cardholder enrollment, cardholder lookup, badge/dossier assignment, assignment of access privileges, as well as limited hardware/door control (such as Door Lock, Unlock, and Pulse (momentary unlock), assigning door schedules. Limited reporting capability is available such as Cardholder Activity, Reader Activity, etc.

REQUIREMENTS FOR LAUNCHPOINT ON PREMISES

1. You must have Administrative Rights to install System Galaxy software, LaunchPoint app, and the Badging solution.

2. Windows IIS must be installed.

3. System Galaxy database and software ( v11.3.0 or higher) must be installed before you install the LaunchPoint or idProducer Badging Solution.

4. The core GCS Services are installed with the SG Software. These services must be running for proper operation of the LaunchPoint web app: including the GCS Client Gateway service, GCS DBwriter Service,  GCS Communication Service, GCS Event Service, and the GCS Web API Service.

5. If using a badging solution, the Badging Application must be installed and properly licensed.

   1. The Badging Application must be properly registered the in System Galaxy system registration.

   2. You must determine how the badging templates will be stored and maintained, based on which solution you chose. Be aware that all Badge Templates must be created or designed within the Badging App.

6. The SG LaunchPoint App must be installed from the Galaxy Installation USB and must be properly registered in the System Galaxy system registration screen as Web Client support.  Your registration settings must match the customer purchase agreement.

7. The LaunchPoint User must have a valid System Galaxy Operator Login that is programmed through the Operator Programming screen System Galaxy software in the.

()

System Galaxy offers two on-premises license schemes. Requirements vary based on which License is installed.

1. BASIC LICENSE: License is for a single badging station.

   • Galaxy generates the idProducer license key when System Galaxy is registered.

   • Supports 1 Root Subscription for all badge templates. 

   • Supports 1 Badge Printer for all badges.

   • Customers are supported in the Basic License Model from current SG; but the system will not filter the badges by operator login or customer assignment since all badges are under one Root Subscription. Managing unique customer-based badges becomes a matter of policy. Filtered badges are supported in the Advance License model.

      

2. ADVANCE LICENSE: License for multiple badging stations. Contact Galaxy for obtaining a license. 

   • License must be obtained before Registering System Galaxy.

   • License can be installed before or after registering SG.

   • Supports customers with multiple Customer-Subscriptions

   • Supports multiple badging stations/printers.

General Requirements:

1. SG v11.1.0.2 minimum is required for Basic License (customers not supported in Basic model until 11.2.0).

2. idProducer build/version 1.6.6943.1226 as of SG 11.1.0

3. IIS must be installed to support idProducer Web Client Badge Designer. Galaxy IIS Utility available.

4. IIS Site must be created for idProducer and the IIS_IUSR permissions must have “full control”.

5. System Galaxy (all 3 parts) must be installed before idProducer is installed. You must create your Web API Credentials and configure the HTTP/HTTPS port number during part-3.

6. idProducer database must be published on the GCSSQLEXPRESS instance of SQL Server.

7. GCS Web API Service and both SpecsID services (server & connections services) must be running.

8. idProducer uses port 81 as the default. IF you change any port numbers from the default, you must update the appSettings file to match. Restart all services.

9. If you change any API reserved login credentials after the installation and registration are finished, you must update the appSettings file to match. Restart all services.

10. You cannot setup the idProducer Print Dispatcher(s) until idProducer is licensed.

11. You must manually add your badge printer to the idProducer Print Dispatcher(s).

12. You cannot live-print badges until the idProducer Print Dispatcher(s) is running. Offline print requests are saved in the Print Request table and will print as soon as the Print Dispatcher is online again.

13. You cannot delete a badge from SG if there is a pending print request. Launch the Print Dispatcher and Close or Print any Queued print requests. Print off any pending print requests.

14. You cannot create badge templates until the SG Cardholder fields have been pushed to idProducer. This happens when SG is registered for the Root subscription, and when the SG Customer-subscription is created and Synchronized for Customer-Subscriptions.

15. You cannot assign badges to cardholders until the badges are imported. Any changes after the fact must be Synchronized in Badge Designs screen (or the Customer screen if you are making customer badges).

()

PassagePoint Global is compatible with System Galaxy.

• There are no special registration requirements in System Galaxy. The integration is done through linked SQL Server connections and stored procedures. SG 10 includes the StopWare stored procedure for the SysGal database.

• At least one access profile must be created in System Galaxy to be used for visitor access privileges. The access profile name must be added to PassagePoint and is case sensitive.

• PassagePoint must be registered for Directory Linking if host names are imported from SysGal. Importing of names is administrative only. There is no linking of access rules through the host name.

• PassagePoint requires set up of the SysGal database connection, Access Profile name, and sign-in/sign-out scripts. 

()

System Galaxy supports IDEMIA Morpho Readers using MorphoManager/BioBridge software. Specifications below are based on current software.

NOTICE: Other Morpho Models are supported in ‘Biometric’ Multifactor Mode.

NOTICE: All Morpho Readers must be assigned a valid Multifactor Mode that is compatible and works with the intended credentials.

NOTICE: Also, each credential must be enrolled with the Authentication Type that matches the Multifactor Mode at the reader.

SYSTEM GALAXY SUPPORTS INTEGRATION WITH MORPHO READERS AS FOLLOWS:

1. System Galaxy database must be installed before you install MorphoManager Server/Database and Client.

2. Galaxy requires you use the correct version of MorphoManager/BioBridge that Galaxy provides on the installation media for your release of SG software. (Registered for Biometric Support; the assigned Biometric System must be set for MorphoManager/BioBridge).

3. Morpho Reader must be running the appropriate firmware version that is compatible with MorphoManager installed.

4. Finger Enrollment Station must be running the appropriate firmware supported by MorphoManager/BioBridge system.

5. Requires the compatible version of MorphoManager

6. MorphoManager Client must be installed at every Galaxy workstation that will perform enrollment. 

SYSTEM GALAXY SUPPORTS ENROLLMENT AS FOLLOWS:

1. Supports enrolling credentials from within System Galaxy Cardholder screen.

2. Supports all/any combination of Access Groups, Access Profiles, and Personal Doors are supported – access is decisioned/determined by the panel (not by the reader).

3. Supports two unique fingers per credentials

4. Supports two Authentication Types (Biometric only, Card + Biometric*, Multi-factor with PIN based on reader model).

* Proximity, HID iClass, DesFire, MiFare cards based on the reader model.

()

SCHLAGE AD400 WIRELESS & AD300 HARDWIRED

This section covers various Schlage models from Legacy to AD, LE, NDE series readers.

 

• System Galaxy supports Schlage AD-400 wireless readers/PIMs as of SG 10.1

• System Galaxy supports Schlage AD-300 hardwired readers (no PIM) as of SG 10.2/Flash 5.0

• All AD-Series hardware requires installer to obtain the new HHD Hand Held Device and download the Schlage Utility Software in order to “couple” and “configure” PIM address, set RF channels, as well as address and link the wireless Readers. Schlage offers technical training and certification for field installation. Hand-held wireless range testers are available to validate your reader-to-PIM channel frequency. Using an alternating configuration pattern helps to prevent range conflicts with the floors above and below the readers being installed.

 

HARDWARE UPGRADES AND EXPANSIONS:

When adding AD300 hardwired readers to a DSI board that already supports wireless readers, you have two options.

1. Separate Networks*: you can keep the readers separate (wired/wireless) by reserving one section of the DSI board for wireless (i.e. AD400 only) and the other section of the DSI for hardwired readers (i.e. AD300 only). 

2. Mixed Networks*:  you can add AD300 hardwired readers to the same bus that supports AD400 wireless readers (or legacy ODT Wireless PIMs if you have older equipment). 

 

*	NOTE:  You must configure the Serial Channel programming in the SG Software for the correct Network Type (i.e. wireless-only, hardwired-only, or mixed-network) to match what you installed on the 485-network).

 

 

 

 

 

See Galaxy Schlage AD-400/300 Guide for full requirements and instructions to integrate with System Galaxy. Also see manufacturer's documentation for product information.

()

SCHLAGE LE & NDE HARDWIRED

• System Galaxy supports Schlage LE & NDE wireless readers/PIMs as of SG 10.5.6

• All LE & NDE locks require using the ENGAGE Mobile App to configure the readers.

 

 

 

 

See Galaxy Schlage LE-NDE Guide for full requirements and instructions to integrate with System Galaxy. Also see manufacturer's documentation for product information, which may be found on Allegion website.

()

()