Skip to main content

3. Context and Scope

3.1 Business Context

PSSaaS operates within the mortgage secondary marketing ecosystem. Users are lender secondary marketing desk personnel who manage loan pipelines, execute best-execution pricing analysis, trade loans with investors, pool loans for agency delivery, and manage hedge positions.

3.2 External Interfaces

InterfaceDirectionProtocolDescription
Users (browser)InboundHTTPSLender secondary marketing desk personnel access PSSaaS through a web browser.
PowerSeller X APIBidirectionalREST/HTTPSSaaS App can query external marketplace pricing. PSX can pull loan data for marketplace listing.
MBS AccessInboundREST/HTTPSMarket data (MBS values, rate sheets) consumed by the pricing engine. Replaces legacy DDE feeds.
Agency SystemsOutboundSFTP / APIPool commitment and delivery data sent to Fannie Mae, Freddie Mac, Ginnie Mae in agency-required formats.
Price FeedsInboundREST / WebSocketInvestor rate sheets and pricing updates. Replaces the DDE-based pricing mechanism in the desktop app.
OdooInboundREST / WebhookTenant provisioning, subscription status, user management signals. Odoo is the commercial layer.
Azure SQL MIInternalTDSDatabase-per-tenant. Each tenant has its own database on SQL MI.

3.3 Technical Context

3.4 Scope Boundaries

In scope for PSSaaS:

  • Pipeline management (loan intake, status tracking, lock management)
  • Best-execution pricing analysis
  • Trade lifecycle (creation, designation, settlement)
  • Pooling engine (constraint satisfaction, agency delivery)
  • Risk analysis (position reconciliation, hedging)
  • Document tracking
  • Bid packaging
  • Import/export
  • Reporting
  • Configuration and administration

Out of scope (handled by other products):

  • Marketplace execution → PowerSeller X (PSX)
  • MBS market data subscriptions → MBS Access
  • Billing, CRM, customer management → Odoo
  • Loan origination → not a PowerSeller capability