Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
sf3 sf3
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • OpsPortal
  • sf3sf3
  • Wiki
  • sombo

Last edited by Cyril L'Orphelin May 25, 2021
Page history

sombo

sombo

Overview

The Service Order Management Back Office [SOMBO] is a tool design to track trace of all the orders received by the marketplace and to propose different actions on these orders .

For a new order, the tool allows shifters to:

  • Analyse the orders
  • Approve/reject the orders
  • Request more information to the customer
  • Exchange information between third parties
  • Start a negotiation process
  • Generate automatically an SLA/OLA from given templates
  • Coordinate (semi-) automatic procedures to enable a customer to access a service

Architecture

Capture_d_écran_de_2021-05-25_15-37-22

Interfaces description

Currently the interface implemented in the Operations Portal is split into 4 parts:

  • Service order list
  • Authorization page
  • JIRA details page
  • Service Order Management page
Clone repository
  • API documentation
  • Sombo EOSC
  • architecture
  • authPage
  • broadcast
  • ci
  • connect_provider_eosc
  • cp
  • dashboard
  • docInternal
  • downtimes
  • Home
  • jira_details
  • lavoisier_instances
  • mainFeatures
View All Pages