Skip to main content

 

 

Coupa Success Portal

2.1 Conduct Business Process Review, Design and Architect the Solution

Overview

Business Process Design is a key project activity that drives towards optimal system configuration and architecture. Complete signed off business process design ensures there are no process blockers later in the project that could impact other project milestones and overall timelines. Design process review sessions should educate customers on our best practices and demonstrate our recommendations in alignment with their requirements and success goals.

Activities

Activity Key Inputs Roles & Responsibilities Deliverables Supporting Documents
Schedule and lead Business Process Design Workshops

Core Project Team (Procurement, Finance, System Admin)

 

Solution Architect

 

SME

  • Coupa Solution Architect leads workshops for Coupa led project.  Attends workshops and supports partner on partner led project.
  • Initial workshops should be on site at Tier 1 and 2 customers
Completed Business Process Workshops

Business Design Workshop Decks

  1. Requisitioning Goods and Services
  2. Approvals
  3. Purchase Order Management
  4. Accounting
  5. Receiving
  6. Invoicing Workflow
  7. Master Data Handling
  8. Security Controls (Roles, Content Groups, Account Groups)
  9. Reporting/Analytics
  10. Budgets
  11. Expenses
  12. Inventory
  13. Contracts
  14. Sourcing
  15. SIM
  16. Data Dependency
Capture customer requirements in Business Process Requirements Document

Core Project Team (Procurement, Finance, System Admin)

 

Project Manager

 

Solution Architect

 

SME
  • Coupa SA responsible for capturing business requirements on Coupa led project.  Partner functional architect will do so on partner led.
  • Partner to review with Coupa SA before requesting sign off from customer
Signed off Business Requirement Process Document

Business Process Requirements Document

 

 

Capture Integrations requirements in Integration Requirements Document and Review Integrations Design Checklist  
  • Partner/Client is responsible for capturing the requirements.
  • Client responsible for sign off on design checklist
  • Client/Partner is responsible for completing the data mapping document.
  • Coupa TS architect is responsible for driving the partner/client to complete the documents and tasks
  • Coupa TS architect is responsible for reviewing the content and providing feedback to partner/client

Signed off Integrations Requirement Document

 

Signed off Integrations Design Checklist

Integrations Requirements Document

 

Integration best practices

 

Integrations Design Checklist

 

Integration mapping

 

 

 

 

Architect the solution

Client/Partner

 

Solution Architect

 

Technical Architect

  • Coupa solution and technical architects work with client/partner to finalize solution architecture diagram
  • Signed off Solution Architecture diagram that defines what business functions are mapped to Coupa vs. other systems in customer's enterprise landscape.
 
Discuss and finalize customer enterprise architecture  
  • Coupa TS architect is responsible for having the discussions with the Client IT and enterprise architecture teams - resolve any issues/questions, provide recommendations on the choice of middleware, endpoint, data transformation, integration interfaces, error handling, monitoring etc.
   
Data Modeling Partner technical architect, Client technical architect, Partner Business architect, Partner SME, Client Business Architect, Client SME (procurement and AP)
  • Coupa PS solutions architect will work together with the Coupa TS technical architect to model and design key data elements like COA, Suppliers, Addresses etc.
   
Security requirements management Coupa PS, Partner, Client technical team
  • Coupa TS architect will triage the security related questions and address them
  • Coupa TS architect will reach out to the Coupa security team appropriately to address some of the advanced topics
   
  • Was this article helpful?