Quick Start Service
Eager to unlock the potential of next-generation information applications? The MarkLogic Quick Start program makes it easy for you to evaluate MarkLogic’s capabilities and strengths through a working pilot, where we’ll focus on helping you accomplish three major objectives:
- Ensure your first MarkLogic project is a resounding success
- Create a repeatable model to ensure future successes
- Deliver a working pilot application underpinned by a best-practice architecture
Getting Started
In an agile, iterative manner, we’ll help you build pilot functionality. Fundamental program activities include the following:
- Data ingestion and migration strategy, including ingestion of sample data
- Data access and delivery channel capability
- Software and information architecture
With our proven Quick Start approach, you’ll gain a working pilot that demonstrates how MarkLogic enables you to leverage all your data to meet your information accessibility, sharing, and delivery needs.
The Quick Start Approach
The Quick Start approach affords you a great deal of flexibility in choosing which business scenario to target as the working pilot. Based on our experience implementing high-value, rapid-return solutions, we’ll work closely with you to determine the scenario that makes the most sense for your organization. This process will involve collaborating on the following four pre-implementation planning activities:
Identify a business scenario for initially applying MarkLogic
Identify goals relative to this initial data-management project
Identify resources and targeted timeline for implementation
Identify key factors that can influence project success
8 Weeks to a Working Pilot
Looking to build a pilot? Our recommended Quick Start timeline follows the structure below. In just eight weeks, you’ll see how efficiently you can build applications on MarkLogic.
Project Setup (~1 Week)
- Kickoff meeting (½ day)
- Review pilot objectives
- Discuss scope and prioritization
- Identify roles, responsibilities, schedules, and availability of integrated team
- Identify representative stakeholders
- Logistics
- Onboard consultants (network access, mandatory training, connectivity to servers, etc.)
- Finalize/validate scope and target schedule for Iteration I
- Install MarkLogic Server (if environment is available)
Iteration I (~2 Weeks)
- Iteration I activities as agreed upon, typically focused on loading and enriching a sample set of data
- Conduct 1-day MarkLogic Fundamentals course onsite
- Attend MarkLogic public training course(s) (based on public course schedule and available seats)
- End-of-iteration demonstration to stakeholders
- Update pilot environment (if available)
- Finalize/validate scope and target schedule for Iteration II
Iteration II (~2 Weeks)
- Iteration II activities as agreed upon, typically focused on exposing data through user interfaces or integration APIs
- End-of-iteration demonstration to stakeholders
- Update pilot environment (if available)
- Finalize/validate scope and target schedule for Iteration III
Iteration III (~2 Weeks)
- Iteration III activities as agreed upon, typically focused on additional functionality discussed in Iteration I and Iteration II demonstrations
- End-of-iteration demonstration to stakeholder
- Update pilot environment (if available)
- Finalize/validate scope and target schedule for wrap-up activities
Pilot Wrap-up (~1 Week)
- Incorporate prioritized feedback from Iteration III demonstration as time allows
- Demonstration of pilot to executive sponsors and key stakeholders
- Provide production architecture recommendations
- Deliver proposal for the Phase 1 production implementation, including features, timeline, and estimated resources
We recommend working with a regular, contiguous resource schedule. If the most effective use of your resource time is in non-contiguous periods, we’ll work with you on a mutually agreeable schedule.