"We Telcos often tend to implement things the way they have always been done. Alvatross doesn't hold back here and has the courage to question our old habits."
Jan Lemmermann
OSS Lead Architect at EWE TEL
"We highly appreciate vendors like Alvatross who demonstrate a strong commitment to the ODA. It is crucial for us to have vendors who are dedicated to it, since we rely on them to transform the ideas and proposals we envision as CSPs into reality."
Sylvie Demarest
Enterprise Architect at Orange Group
“alvatross became one of the first companies to achieve ‘Ready for ODA’ status, showcasing their dedication to a cloud-native product portfolio with a roadmap commitment to support ODA’s evolving standards.“
Andy Tiller
EVP of Member Products & Services, TM Forum.
"I have always found that the OSS layer in Telco lacked proper products that covered, with a TM Forum approach, the main needs of operators, modular and API based. alvatross was born to cover that need."
We were born in 2020 as a product unit inside SATEC, a global System Integrator based in Spain. Since 2023, we are an independent company part of the group that also owns SATEC.
Where are our development centers located?
Alvatross has two main centers, both are located in Spain.
• Palacio de Maqua, Calle de la Cámara 23, Avilés, Asturias. • Avenida de Europa 34A, Aravaca, Madrid.
How long does it take to implement Alvatross?
Most implementations that include some data migration, integrations, and training can take between 6 months and 1 year depending on the complexity of the scope.
Can I see a demo of Alvatross?
Yes! Please fill up your details at our contact page and we will contact you asap.
Does Alvatross offer a POC?
Definitely
Can Alvatross be deployed on-premise or only in the cloud?
Both. Our platform is built as cloud-native so we can benefit from its main traits: Scalability, elasticity, resiliency, and, most importantly, flexibility. However, it can also be deployed on-premise if preferred.
What DB do we support?
We are proud to be DB-agnostic. Today we support Oracle, SQLServer, MariaDB, PostgreSQL and MySQL. However, if you prefer to use adifferent one for any reason, we will handle it.
What happens if I don't use Open APIs?
Using Open APIs unfortunately is not always possible. For those cases, we can create ad-hoc adaptations and connectors through API Gateways.
Is Alvatross open to work with SI's?
Yes, we are.
What activation connectors are already available on the Activation Engine?
We have a bunch of them! However, if we don't have the ones you need, we can easily develop new ones with our SDK or train you on how to do it.
What happens if I don't use TMF standards?
The risk of not using TMF standards is that short-term gains can lead to highly expensive and inefficient processes that can be challenging to rectify or overcome. Adopting standards unlocks the opportunities to expand ecosystems creating new revenue streams efficiently and future-proofing the way you communicate with your partners and customers.
I use TMF standards but not ODA yet...
No problem. The ODA is the natural progression to the TM Forum's classic frameworks.
Why ODA?
The ODA defines components that address functional domains which are seamlessly integrated using a suite of standardised APIs. It provides a common language that benefits all parties involved. It is the industry blueprint for industry integration as well as defining the functional baseline for all applications with in the front and back-end technology stacks.
Alvatross is contributing to defining ODA standards in different collaboration groups. Why?
Alvatross is recognized as a leading light in supporting the ODA's industry initiatives and serves as one of the main destinations for CSPs seeking to witness how "theory" is put into "practice". Contributing to ODA standardization is important for us because it promotes industry-wide collaboration, leading to more efficient and scalable digital ecosystems for everybody.
What ODA components does Alvatross Support?
Core Commerce Management Layer: • Full coverage with conformance certification for all mandatory Open APIs: - TMFC001 Product Catalog Mgt • Full coverage of the functional scope of the component: - TMFC003 Prod Order Delivery Orch & Mgt • Partial coverage: - TMFC027 Product Configurator
Production Layer: • Full coverage with conformance certification for all mandatory Open APIs: - TMFC007 Service OrderMgt - TMFC010 Resource Catalog Mgt - TMFC008 Service Inventory - TMFC012 Resource Inventory - TMFC014 Location Mgt • Full coverage of the functional scope of the component: - TMFC011 Resource Order Mgt • Partial coverage with mandatory API certification: - TMFC006 Service Catalog Mgt • Partial coverage: - TMFC009 ServiceQualification Mgt
-01.svg)
-03.svg)
-02.svg)
