Platform as a Service
Build integrations on a platform we operate
ECOM's Platform as a Service gives you the full PRISM integration platform, including the B2B gateway, translation, partner connectivity, MFT, workflows and monitoring, delivered and maintained by ECOM. Your team, ECOM's specialists or both build and run the integrations; ECOM operates and supports the platform.
At a glance
- PRISM platform access
- Platform operations
- Development tooling
- Optional expert help
What is iPaaS?
Integration platform as a service (iPaaS) is a cloud-delivered platform for building and running integrations between applications, data sources and external partners. The provider operates the infrastructure, including hosting, scaling, security patching and upgrades, while the customer's team designs and manages the integrations themselves.
Why teams choose it
Benefits
No infrastructure to manage
ECOM handles hosting, patching, scaling and upgrades.
Full control of integrations
Your team builds maps, workflows and partner connections on your schedule.
Room to grow
Add EDI, API, MFT and automation capabilities on one platform.
Scope
What's included
-
PRISM platform access
PRISM-EDI, translation, managed file transfer and PRISM-SCV.
-
Platform operations
Hosting, availability monitoring, security updates and upgrades by ECOM.
-
Development tooling
Map design, partner management and workflow configuration tools.
-
Optional expert help
Add EDI Team as a Service when you need extra capacity or skills.
Fit
When it fits
Experienced integration teams
Teams that want control without operating servers.
Replacing on-premises EDI software
Move to a platform that ECOM keeps current.
Responsibilities
Who does what in Platform as a Service (PaaS)
ECOM operates the PRISM integration platform; your team, ECOM's specialists or both build and run the integrations. The same matrix covers all five delivery models, so you can compare them directly.
-
- Hosting and platform operations
- ECOM Hosting, availability, security patching and upgrades.
- Maps and document rules
- You Your team builds maps, or contracts ECOM specialists to.
- Partner setup, testing and certification
- You Your team onboards partners, or contracts ECOM specialists to.
- Daily transaction monitoring
- Shared ECOM watches the platform; your team watches transactions.
- Technical incident resolution
- Shared ECOM resolves platform incidents; your team resolves integration errors.
- Correcting business data (items, prices, orders)
- You Your team corrects the data in your own systems; ECOM reports what failed and why.
- Approvals and business decisions
- You You approve go-lives, changes and priorities.
Typical responsibilities. Each customer's service agreement defines the exact scope, and models can be combined, for example PaaS with EDI Team as a Service.
Implementation
How implementing Platform as a Service (PaaS) works
Integration projects move through these five stages. What changes is who does each task, which depends on the delivery model you choose.
-
Discover and scope
- ECOM
- Reviews your trading partners' requirements, documents, systems and volumes, and confirms the scope in writing.
- Your team
- Share partner guides or vendor manuals, sample documents, your ERP and version, and your deadlines.
-
Design and build
- ECOM
- Designs the flows and builds the maps, rules and connections, or supports your team building them on the platform.
- Your team
- Confirm business rules and field meanings, and provide test data and access to the right people.
-
Test and certify
- ECOM
- Tests each document internally, then completes the partner's testing or certification steps.
- Your team
- Check test results in your own systems and approve them before go-live.
-
Transition and go-live
- ECOM
- Plans the cutover, including a move from a current provider or platform, and watches the first live transactions.
- Your team
- Approve the go-live date and coordinate your internal teams and partner dates.
-
Support and improve
- ECOM
- Monitors and supports the integration as your delivery model and service agreement define, and handles partner changes in scope.
- Your team
- Tell ECOM about business changes, new partners and priorities.
What affects timing and price
ECOM sends a scoped proposal after reviewing your requirements. These factors make the most difference:
- How many trading partners and document types are in scope
- Each partner's testing and certification process and schedule
- Your ERP or application, and whether a standard connector fits or custom integration is needed
- Custom business rules, data quality and the work needed to map them
- Connection methods (AS2, SFTP, VAN, API) and security requirements
- Delivery model and support coverage, for example 24×7
- Transaction volumes and any migration from an existing platform
Frequently asked questions
What is the difference between iPaaS and SaaS?
With iPaaS, your team builds and runs integrations on the platform. With SaaS, you use ready-made applications, such as WebEDI, with less configuration work.
Who is responsible for integrations on iPaaS?
Your team owns the integrations, while ECOM operates the platform. Responsibilities are defined in your agreement.
Can we get help building integrations?
Yes. ECOM implementation services and EDI Team as a Service are available alongside iPaaS.
Talk to an EDI/API expert
Tell us about your partners, systems and goals. We will show you how PRISM and our team can help.