1. Saravana Kumar
CEO/Founder - Kovai
Atomic Scope – Product Update

2. Empowering Business Users to visualize end-to-end
Business Activity Tracking
Functions
Logic Apps
App Services
Custom

3. End-to-End : Healthcare

4. End-to-End : Supply Chain

5. Common Challenges End-to-End Visibility Exception Handling
Edit & Resubmit Failed Messages
Message Archiving
Security & Access for Business Process
Monitoring Business Processes

6. Addressing these challenges using
*custom solution* requires significant efforts

7. 20-30% of time is spent on building end-to-end trackability
…still you can’t get a polished solution
Atomic Scope tries to reduce this effort to less than 5%

8. How does it work? 1 2 3 Your Solution – Hybrid Integration
ATOMIC SCOPE
Web Portal
Your Solution – Hybrid Integration
(ex: Purchase Order Processing) 1
Define your Business Process
How does it work? 2
Define Stages & Transaction in your Business Process
Logic Apps
Functions
App Services
Custom
Add Properties to Track (JSON Path, XPath, Context Properties, HTTP Headers)
Add Instrumentation in your solution (BizTalk Pipelines, Orchestrations, Azure Logic Apps, Azure Functions, .NET Code, Web API) using Atomic Scope components 3

9. ATOMIC SCOPE Components BizTalk Pipeline Components .NET SDK
Logic Apps
REST API
ATOMIC SCOPE
Components
Functions
App Services
.NET SDK
REST API
Custom
Modern Web Interface
Persistent Data Store

10. High level architecture

11. ATOMIC SCOPE Features End-to-End Business Process Visibility
Configuration based Business Process Definition and Data collection
Powerful Search, Message Archiving & Exception Management
Support for De-Batching Scenarios  
Authentication and User Access Policy
Monitoring and Notification
With that let us look at key features of AtomicScope
Monitor hybrid integrations solutions or monitor them individually. Whether your system is on-premise only, cloud or both. We support all types.
All the tracing happens through port names, artifact names, orchestrations, etc. In our portal you will be able to map these artifacts to stages, which are part of your transactions within business process. You will configure those in the portal by providing names that can be easily understood by your functional team and then enter those names inside the instrumentation that we provide for BizTalk and LogicApps, then the data starts being collected.
As mentioned before you are going to define a business process, within that some transactions and then stages within that transaction. We allow you to specify what data you want to collect at each particular stage and by what you want to search. Then once you go live you are free to remove and add different fields without any re-deployment.
You can clearly see the e2e workflow in a graphical way. Each of the nodes are interactable and when you click on them you will clearly see how to message is propagated across your stages and if there is a problem you will see a red node together with all the details why it has failed.
Many solutions will use something like ESB to log the exceptions and they will view them in their portal, but how do we link the exception with the message flow ? When an order is coming in and there was problem processing it you will be able to see it inside the actual stage. We also provide archiving to satisfy your auditing or legal req.

12. ATOMIC SCOPE is designed to help Business Users
TECHNICAL

13. BOOK A DEMO