How did you select Sciant and what were the deciding factors?
Sciant is focused on three verticals, including Transportation & Logistics. For the first step we validated their industry experience. Secondly, we validated their technical aptitude. Finally, we conducted reference checks with their previous customers.
Describe the scope of work in detail, including the project steps, key deliverables, and technologies used.
Invata manifesting solution is a WebAPI restful application, that provides access to important packaging and manifesting process endpoints (object manipulation and additional actions).
Storage is primarily using MS SQL as a database and Entity Framework Core as ORM, utilizing DB first approach and scaffold context. Additional set of domain objects (POCO classes) exists and manual mapping between DB objects and POCO objects is implemented.
The architecture of “Invata Manifesting” application is dependent on existing WebApi project (“Invata.WebApi”), existing nuGet packages (managed and supported by Invata team), existing MS SQL database:
- All necessary DB tables should be added to the existing DB instance, but in a separate schema(s). This will make them logically separated from each other, but still easily maintained by Invata infrastructure team.
- All newly introduced WebApi (and supporting) projects had to be easily build and deploy as set of DLLs pasted in special folder under main starting point of the current solution.
- Introduced the concept of multiple, independent of each other carriers with autonomous configuration, setup, data store, but providing similar functionality and behavior for the manifesting system.
How many people from the vendor's team worked with you, and what were their positions?
The delivery team consisted of a Project manager, two .Net Developers, an Angular Developer and 2 QA engineers with expertise in the Transportation & Logistics vertical.