Sage ERP 1000 v4

Project Overview

Russell Slaymaker – Sage ERP 1000 Product ManagerRichard Aird – Sage ERP 1000 Business Analyst

Agenda

• What is v4?• Project Overview• Explain some new functionality

What Version 4 is not

• It is not Sage 1000 v2.4• It is not a ‘tightly coupled’ integration

Why??

This is Sage 1000 v2.3

Advantages• All contained within one application• Functionality from both systems

available side by side

Dis-advantages• Every user requires both a CRM and ERP licence.• Unable to perform separate upgrades of either system• All patches from CRM and ERP require extensive regression testing due to heavy customisation.• Limited to Sage CRM, with no prospect of extensibility• Not aligned with Sage’s worldwide approach to CRM integration

What is Version 4

Sage 1000 v4 is a loosely coupled integration of two standalone products using a Sage endorsed integration protocol

Advantages of this approach

• Limited CRM customisation which allows quicker provision of service packs• As it uses a standard integration method all future CRM releases will be compatible

with Sage 1000 v4, therefore easy upgrade of either system• More flexible licensing, customers can buy only a CRM or ERP licence depending

on the users job role. Or both if necessary.• Potential to integrate with other CRM systems• It is aligned with the integration strategy of other Sage products (e.g. Sage 200, X3)

• Integration with Sage CRM

• Use of Synchronisation for Customers; Suppliers and Commodities only.

• Bespoke Functionality to handle converting Quotes to Orders

• Clear documentation of operation including any limitations

• Emphasis on enablement and supportability.

• Only minor enhancements to ERP functionality

What is included in phase 1

What is excluded from this phase?

• Integration with SLX

• Any requirement not considered a MUST

What are the Dates

Development phase: April - June

R&D Testing: April - July

Support UAT: August

BP Beta: September

Release: October

Process so far

Functional Requirements

• Customer\Supplier creation and management• Lead, opportunity and quotation management• Sales order creation and order fulfilment

The High Level Design has been split into two areas

Non Functional Requirements

• Licencing of Sage 1000• Supported platforms• Deployment

Functional RequirementsCustomer/Supplier Creation and Management

Design Principles

• Customer records can be created\amended in either CRM or ERP• Customer records will be synchronised between the two systems• The method will be SData synchronisation, adhering to the GCRM contract

Benefits

• Uses established technology• Some development work already carried out

Requirements

• The system should ensure this information only needs to be entered once• The system should enable customer creation with all the information required to

create an order at the first point of entry

Functional RequirementsCustomer Creation and Management

Functional Requirements - Customer Creation and ManagementSData Entities Synchronised

Linking an account in CRM

Linking an account in CRM

Functional Requirements - Customer Creation and ManagementDevelopment Priority

DEVELOPMENT CONSIDERED MUST SHOULD COULD

Provide two way synchronisation between ERP & CRM

X

Provide form popping in CRM to open accounts in ERP

X

Functionality prototyped but not part of this release phase

Functionality prototyped but not part of this release phase

Functional Requirements - Customer Creation and Management

Functional RequirementsLead, Opportunity and Quotation Management

Requirements

• The system provide information that enables the creation of valuable marketing lists

• The system should be able to record opportunities including probability of sale and estimated value

• The system can create quotes that; calculate accurate prices; apply the appropriate discounts; have an expiry date and have an option to add a contact.

• The system should allow quotes to be linked back to opportunities, leads and marketing campaigns.

• The system should lend itself to quick entry of quotes• The system should provide a sales pipeline that includes details of unexpired

quotes and opportunities

Design Principles

• All lead, opportunity and quotation functionality is CRM only• CRM quotes will therefore be held in CRM only and not visible to ERP users• An improved pricing service is required for CRM quotes• Quotes should be able to deal with bundles*• The system should be able to convert a quote to an order keeping the integrity of

the order details in placeBenefits

• ERP will not be ‘cluttered’ with quotations• Quotes can be created without the need for an ERP customer record • As the quotation data is CRM side they can be included in the CRM sales pipeline • Quotes can be included in CRM forecasting• CRM quote entry mechanism is currently more streamlined than that in Sage 1000

Functional RequirementsLead, Opportunity and Quotation Management

Functional RequirementsLead, Opportunity and Quotation Management

Functional Requirements – Leads, Opportunities & QuotesSData Entities Synchronised

Functional Requirements – Quote Stock Check

Functional Requirements – Quote Stock Check

Functional Requirements – Quote Pricing

Two pricing options on a CRM quote line

• Manually price the line• Use ERP pricing

Functional Requirements – Quotes Conversion

Functional Requirements - Leads, Opportunities & Quotes

Functional Requirements - Leads, Opportunities & QuotesDevelopment Priority

DEVELOPMENT CONSIDERED MUST SHOULD COULD

Convert a quote to a ERP sales order XRewrite pricing service to improve performance and quotes to be priced for non ERP customers

X

Provision of stock position within the context of CRM quotation

X

Provide form popping in ERP when a quote is converted

X

Functionality prototyped but not part of this release phase

Functionality prototyped but not part of this release phase

Functional RequirementsSales Order Creation and Fulfilment

Requirements

• The system should be able to check stock availability and allocate stock to an order during creation

• The system should provide the user with various options when dealing with out of stock items, e.g. back order, split order.

• The system should provide a full credit check of the customer and warn the user \ hold the order if the customer is on credit stop or will exceed their credit limit.

Design Principles

• All order creation and fulfilment, invoicing and payment functionality is ERP only• Sales orders will be available to view in CRM

Benefits

• Reduces the size of the payload when running a synchronisation (especially the initial synch)

• Uses rich ERP order entry functionality • Allows the same users to seamlessly create and despatch a sales order• No re-engineering of ERP functionality in CRM

Functional RequirementsSales Order Creation and Fulfilment

Functional RequirementsSales Order Creation and Fulfilment

Functional Requirements – Sales Order Creation and FulfilmentSData Entities Synchronised

Functional Requirements - Sales Order Creation and FulfilmentDevelopment Priority

DEVELOPMENT CONSIDERED MUST SHOULD COULD

It must be possible to view orders within CRM XProvide form popping within the CRM customer context to open ERP customer transaction enquiry

X

Provide form popping within the CRM customer context to open ERP sales order entry

X

Functional Requirements - Customer Creation and Management

Non Functional Requirements

• Licencing of Sage 1000• Supported platforms• Deployment

Non Functional High Level Design

Sage 1000 Licencing

Considerations

• CRM users can create customers, quotations and sales orders without the need for an ERP licence

• Any user that has a requirement to fulfil sales orders (e.g. print pick lists, despatch goods etc.) will need an ERP licence.

Supported Platforms

Overall principle

Sage 1000 will be supported on all Microsoft platforms still under general or extended support at the time of release. However we need to understand the priorities for this release.

REQUIREMENT MUST SHOULD COULD

Sage 1000 v4 supported with IE9 XSage 1000 v4 supported with Windows 8 (x86, x64) XSage 1000 v4 supported with SQL Server 2012 X

Other exclusions

Microsoft Server 2003 is not compatible with the integration technology and therefore it is only supported for v4 as a standalone.

Deployment

Approach to upgrades from v2.3

• Upgrades from Sage 1000 v2.3 will require a fresh installation of both products. It will not be possible to retain existing customisations.

• Data conversion tools may be available, a detailed guide to conversion will be available.