Sunflower Mobilesystem Office — Installation, Pricing & Best Practices
Overview
Sunflower Mobilesystem Office (likely part of Sunflower Systems’ Sunflower Mobile / Sunflower Assets suite) is an enterprise asset-management mobile/offline data-collection solution used by government agencies, universities and large organizations to track physical assets, perform inventories, and sync mobile field data with back-office asset records.
Installation
Server / Back‑Office
- Ensure prerequisites: supported Windows Server version, IIS, SQL Server (match vendor matrix).
- Install Sunflower Assets / Server component using vendor installer.
- Configure database: create instance, restore or initialize Sunflower schema, apply vendor patches.
- Configure IIS application pool and site, set service account with DB access.
- Apply SSL/TLS certificate for secure sync endpoints.
- Configure scheduled jobs (sync, reports, backups).
- Test with a staging dataset before production.
Mobile Client (MobileTrak / Mobile app)
- Confirm device requirements (Android/iOS versions, barcode/RFID hardware).
- Install MobileTrak or Sunflower Mobile via MDM or app store / provided installer.
- Configure server endpoint, credentials, and sync schedules in app settings.
- Provision users and roles in back office, assign mobile permissions.
- Pair any Bluetooth scanners or RFID readers and test scans.
- Run full sync and perform a sample inventory to validate workflows.
Best practices for rollout
- Deploy in a staging environment first; validate data mapping and sync.
- Use role-based access controls; give mobile users only necessary functions.
- Harden endpoints: enforce HTTPS, strong passwords, and device controls (MDM).
- Schedule incremental rollouts by department or site.
- Train end users with task-focused sessions and quick reference guides.
- Maintain version control and a patching schedule for server and mobile apps.
- Keep a rollback plan and backups before major upgrades.
Pricing
- Sunflower Solutions typically use quote-based pricing. Costs vary by:
- Number of user licenses (concurrent or named),
- Number of mobile devices,
- Modules (Assets, Inventory, MobileTrak, ExcessTrak, APIs),
- Implementation, integration, and training services,
- Support level (annual maintenance).
- Expect enterprise licensing and professional services to be quoted after requirements review.
- For exact pricing request a quote from Sunflower Systems / Sunflower Assets vendor or authorized reseller.
Operational Best Practices
- Data quality: clean and normalize asset records before first sync.
- Use standardized asset tags (barcodes/RFID) and naming conventions.
- Automate backups and retention policies for DB and attachments.
- Monitor sync logs and implement alerting for sync failures.
- Periodic reconciliation: schedule quarterly/full inventories to detect drift.
- Integrations: use the API for ERP/finance integrations; test mapping thoroughly.
- Reporting: create standard dashboards for asset health, location, and lifecycle events.
Quick checklist before going live
- Server prerequisites met and patched
- SSL configured and tested
- Database initialized and backed up
- Mobile devices provisioned and paired to scanners
- User roles and permissions configured
- Staging validation completed
- Training delivered and support plan in place
If you want, I can draft a phased rollout plan (timeline, tasks, and testing steps) tailored to a specific organization size — tell me company size and number of mobile devices.
Leave a Reply