Your Tasks
| Task | Status |
|---|---|
| Loading... | |
Explorer Software
Welcome, Loading...
Your onboarding dashboard keeps your current status, project progress, tasks, links, and key contacts in one place.
Onboarding Progress
Current phase shown in amber
Important Links
-
Loading...
Key Contacts
?
Loading...
Explorer Software
Your onboarding guide for this project
Meet your project team
Explorer Team
Your Team
Goals and objectives
Onboarding roadmap
What to expect during the journey
Responsibilities and key milestones
Your responsibilities
Typical milestone timing
Frequently asked questions
Project Reference
Onboarding Scope & Responsibilities for your project
Your Explorer onboarding project is a collaborative implementation designed to configure Eclipse for your organization, train your team on the processes you will use, validate your data and workflows, and prepare your organization for a successful go-live.
Primary Project Tool
Explorer Project Plan & Onboarding Dashboard
Target Operational Date
-
Shared Goal
A tested, trained, and operationally ready Eclipse environment
What your onboarding engagement includes
Your exact implementation will vary based on the products, modules, data, business processes, and services included in your project.
Project Management & Communication
Explorer maintains the Project Plan, coordinates major milestones, communicates status and risks, and provides a shared view of the work required to reach go-live.
Configuration & Setup
Explorer guides your team through the configuration of Eclipse based on your purchased modules and business requirements. Setup is an active part of implementation and preparation for training.
Data & Imports
Explorer provides applicable import templates, guidance, and implementation assistance. Your team provides and validates the business data being brought into Eclipse.
Process Training
Explorer provides structured training for applicable Eclipse modules and processes so your team can perform its normal business activities in the system.
Testing & Validation
Your team tests workflows, reports, forms, imported information, and other critical processes before production use. Explorer assists with questions and issues discovered during testing.
Go-Live & Transition
Explorer evaluates readiness with your team, supports the move into production, assists during stabilization, and coordinates transition to Support when onboarding work is complete.
How onboarding time is used
One of the most important things to understand at the beginning of your project is that onboarding time is broader than instructor-led training sessions.
Onboarding time supports the implementation as a whole
Onboarding time may be used for project-specific configuration, setup, implementation consulting, data and import assistance, process training, testing, report or form review, project working sessions, follow-up work, and other implementation activities required to move the project toward go-live.
If additional work is required because configuration, business requirements, requested deliverables, staffing, or project scope changes, the project may require additional onboarding time.
If an issue is confirmed to be a product or technical issue rather than implementation, configuration, or training work, Explorer will route it to the appropriate technical or Support process.
Onboarding Time ≠ Training Time Only
It represents the implementation effort required to configure,
prepare, train, test, and successfully move your organization
into production.
Not sure whether planned work will use onboarding time? Ask your Explorer project team before the work proceeds. We want you to understand how your onboarding time is being used throughout the project.
Shared project responsibilities
Explorer leads the implementation process, but successful onboarding requires active participation from both teams.
Explorer responsibilities
Explorer provides the structure, guidance, expertise, and project visibility needed to move the implementation forward.
- Maintain the high-level Project Plan, milestones, and project status.
- Provide recommended configuration and implementation guidance.
- Provide applicable setup and process training.
- Communicate known blockers, risks, and schedule concerns.
- Document project-specific working sessions and major outcomes.
- Help coordinate issues requiring Support, IT, Development, or other Explorer resources.
- Review customer feedback during onboarding and adjust the project where appropriate.
- Conduct a formal Go-Live Readiness Review before production launch.
- Coordinate post-go-live stabilization and transition to Support.
Your team's responsibilities
Your team provides the business knowledge, participation, decisions, data, and testing required to make Eclipse work for your organization.
- Provide appropriate project decision-makers and subject-matter experts.
- Attend scheduled implementation and training sessions.
- Complete agreed homework and preparation between sessions.
- Provide requested data in the required format and agreed timeline.
- Review and validate imported or converted information.
- Test normal day-to-day workflows, forms, reports, and outputs.
- Communicate questions and concerns when they occur rather than waiting until the end of the project.
- Inform Explorer of staffing, business, scope, or scheduling changes that may affect the implementation.
- Provide required project approvals and readiness acknowledgements.
Successful onboarding is collaborative. Explorer cannot independently determine whether every converted record, workflow, report, configuration decision, or business process is correct for your organization. Customer review, participation, and validation are required parts of the implementation.
Your operational date is a target tied to readiness
The Project Plan provides the path to your operational date. That date depends on completion of the work leading up to it.
1
Planning & Kickoff
Goals, team, scope, timeline, and responsibilities are reviewed.
2
Setup & Training
The system is configured while your team learns the applicable
processes.
3
Data & Testing
Data, workflows, reports, forms, and business processes are
validated.
4
Readiness Review
Open items, risks, training, data, and testing are reviewed
before launch.
5
Go-Live
Production use begins when the organization is ready to move
forward.
The operational date may need to change when required data is delayed, scheduled sessions are missed or moved, assigned homework or testing is incomplete, required team members are unavailable, project scope changes, additional work is requested, or technical blockers prevent planned work from continuing.
Reaching the calendar date alone does not mean a project is ready for go-live.
Data and import responsibilities
Data conversion is a shared process because Explorer understands Eclipse and your organization understands the meaning and accuracy of its business information.
Explorer provides
- Applicable import spreadsheets, templates, or data structures.
- Guidance on required information and configuration dependencies.
- Assistance preparing and performing applicable imports.
- Help identifying import errors or information that needs correction.
- Guidance on the sequence in which data must be prepared and imported.
Your team provides
- Accurate and complete source information.
- Business decisions regarding how legacy information maps into Eclipse.
- Timely corrections when data is incomplete or cannot be imported as submitted.
- Subject-matter experts who understand the source data.
- Final validation that imported information represents your organization correctly.
Import validation is a shared project checkpoint. Explorer will assist with the import process, but the customer remains responsible for confirming that its business information is complete, accurate, and represented appropriately in Eclipse.
Training expectations
Training is most successful when the right people participate and the work between sessions is treated as part of the project.
What to expect from Explorer
- Training follows a structured module and process path.
- Training is adjusted to the modules and processes included in your implementation.
- Sessions should connect system functionality to your actual business processes.
- Setup, configuration, training, and testing may overlap because they depend on one another.
- Questions or configuration gaps discovered during training are documented and addressed through the appropriate project path.
What Explorer needs from your team
- Participate during working sessions rather than treating them as passive demonstrations.
- Ask questions and raise concerns while the relevant process is being reviewed.
- Complete assigned homework, setup, or testing before the next dependent session.
- Include the employees who understand and perform the processes being configured or trained.
- Practice the applicable processes in the training environment so gaps can be identified before go-live.
If required preparation or homework is incomplete, a scheduled training session may need to be used to complete that work before new material can continue. This can affect both the project timeline and onboarding time usage.
Bring the right people into the project early. A controller, administrator, or project lead may understand much of the organization, but they may not know every operational requirement. Involving the people who perform the work helps prevent configuration from needing to be revisited later.
Go-live readiness
Go-live is a readiness decision, not simply the next date on the calendar.
✓
Required configuration is complete.
✓
Critical modules have been tested.
✓
Applicable imports have been validated.
✓
Users and permissions are ready.
✓
Required forms and reports have been reviewed.
✓
User acceptance testing has been performed.
✓
Applicable payroll and financial testing is complete.
✓
Key users are trained on required processes.
✓
Open critical issues and known risks are reviewed.
✓
The Support transition and operational date are confirmed.
Explorer documents its recommendation through the Go-Live Readiness Recommendation & Acknowledgement. If Explorer recommends delaying go-live and the customer chooses to proceed, the customer is asked to acknowledge the incomplete items, known risks, and decision to proceed.
Onboarding and Support
You should never need to understand Explorer's internal organization chart in order to ask for help.
Onboarding generally includes
- Project-specific configuration and setup.
- Implementation consulting and guidance.
- Data and import assistance.
- Process training and additional education.
- Implementation testing and readiness work.
- Activities required to complete the original implementation.
Support generally includes
- Product or system issues requiring investigation.
- Ongoing assistance after the onboarding transition.
- Questions arising during normal production use.
- Technical investigation routed to the appropriate Explorer team.
- Issues that are not part of project-specific implementation work.
Not sure where your issue belongs? Submit the issue through the Customer Portal and include enough information for Explorer to understand what you are trying to do and what happened. Explorer will determine the appropriate owner and route the work internally.
What successful onboarding means
The goal is not simply to complete a list of meetings. The goal is to leave your organization prepared to operate successfully.
Required system configuration and data are ready for production.
Key users can perform the normal processes required for their roles.
Critical workflows, reports, forms, and outputs have been tested.
Significant open issues and known risks are understood and addressed.
The organization is prepared to begin normal production work in Eclipse.
The customer understands how to obtain assistance after transition to Support.
This page summarizes Explorer's onboarding process, project roles, and
working expectations. If any information on this page conflicts with
the terms of a signed agreement, the signed agreement governs.