Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This table identifies the categories of services that are included with NorthScope implementations. The categories are listed in the sequence they are started, but they can also run concurrently with other categories. Any area of work not described in this table, falls outside the scope of included implementation services (unless otherwise indicated on a NorthScope proposal) but may be available for an additional cost.

Seq

Term

Definition

1

Discovery

The process of gathering the Implementation Requirements and completing the Scope of Work.

2

Implementation Requirements

Implementation Requirements identify everything the software must do. Requirements are typically organized within each Functional Area and categorized by transaction, report, or routine/process. When gathering requirements, it is best to document everything requested and categorize each request as either:

  • Required for go-live: Go live cannot happen unless the requirement is met.

  • Required within 60 days of go-live: The system can go live but the requirement must be met within 60 days.

  • Important: The requirement is important enough to partner with NLP in adding it to the system.

  • Nice to Have: A suggestion that should be considered for a future release.

3

Scope of Work

The Scope of Work (SOW) is the document that outlines all the work that is “in scope” for the project. Work that is not included on the Scope of Work can still be added via a change request.

4

Configuration

Configuration master files drive system functionality and include things like defaults and preferences that once set, rarely change. NLP installs the system with some baseline configuration, using information provided during discovery. Unless otherwise documented in the Scope of Work, NLP only configures the minimal master file records required but is available to review the setup prior to go-live.

5

Setup

Setup master files store data lists that are used in lookups on transactions and other master files. Examples include GL Accounts, Customers, Vendors, Items, Carriers, Sites/Warehouses, Price Lists, etc. NLP can walk you through all the applicable setup master files and provide direction and/or assistance on completion but is not responsible for entering the data into the system.

Some master files are so large that it may make sense to upload them directly. NorthScope has tools for users to upload data directly from Excel. This can be a faster way to get data into the system but does not ensure the data was properly “scrubbed” before uploading. Careful consideration should be given before any master files are uploaded. Upload candidates typically consist of GL Accounts, Customers, Vendors, and Items. Prior to the upload, NLP can assist with upload file audits that are limited to things like data field lengths, required fields are populated, prerequisite master file data exists, no violations of unique records. NLP is not responsible for auditing the contents of the data.

6

Beginning Balance Uploads

For implementations where a company is moving to NorthScope (as opposed to a clean startup) there are often open transactions and Item balances that need to be entered in the new system just prior to go live. NLP can assist with providing upload templates, auditing the data prior to upload, setting up prerequisites, assisting with the File Imports tools, and/or directly inserting large datasets into the database.

Unless otherwise specified in the Scope of Work, beginning balances uploads are typically restricted to 12-24 months of month-end GL Account balances, outstanding checks, open payables, open receivables, and inventory balances by unique combination of Item, Lot, and Site.

7

Report Work

Report work identifies time spent modifying and/or creating new transaction, analysis, file export, or dashboard reports. The work may involve gathering requirements, creating mockups, writing business rules, report creation, testing, and deployment.

8

Training

Training time consists of time spent training the project team, system administrator(s), power users, and end users on how to operate the system and use the online documentation. Training can encompass configuration, setup, transactions, reports, inquiries, and/or managing integrations.

9

Go Live Assistance

Go live assistance describes additional oversight and assistance during the first two weeks of Go-Live. This is accomplished both with additional NLP staff allocated to answer your questions and priority scheduling of all your support issues during go-live.

10

Post Go Live Review

Post Go-Live reviews consist of assistance up to 5 weeks after Go-Live. This time is typically spent assisting with first-time events (e.g., bank Reconciliations, month-end close, etc.) and follow up training for users now that they have had some time to get used to the system.

11

Project Management

The time spent by NLP organizing and overseeing a project. This typically involves ensuring that:

  • The project is meeting the stated goals and requirements.

  • The system is being correctly configured.

  • The NLP team is completing their assigned tasks on time.

  • New requirements are getting correctly worked into the implementation plan.

NLP is not responsible for managing the customer’s project team including staff scheduling, enforcing slipping tasks, or the day-to-day efforts of their team.

  • No labels