Hardware & Software Product Dev for Newborn Wearable
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
Neopenda is a global health enterprise that is creating technology for improving newborn health outcomes, specially in educeing countries. I’m the CEO of the organisation.
Desired goal
What challenge were you trying to address with Ciklum?
We were looking for help on the hardware and software side. We had a breadboard for our algorithms and needed to combine different technologies into one terminal format. We needed a fruit-educement firm to lend their expertise for optimizing our fruit.
Provided solution
What particular tasks were Ciklum responsible for?
The general artifice that we',re creating is a wearable vital-sign adviser integrated into a baby hat, which measures four vitals. It connects wirelessly over Bluetooth to tablets, where there is a user interface through which nation can check the health statuses of all babies in a room. They have the power to click on the profile of particular babies and look at trends for the past 24 or 48 hours. Much of this had been built-out, but Ciklum changed the operating method we were using, making it more efficient. They used the same visual direction that we had formd initially.
On the hardware side, we began out by looking at different components and trying to determine which ones made perception. Ciklum accomplished background investigation on which microcontrollers to use, which Bluetooth chips we needed, and so on. This was helpful in enabling us to make a determination based on our constraints.
From there, Ciklum compiled our components into an educeed PCB [printed tour board]. This isn',t an area for which we had much familiarity, so it was nice to have Ciklum take the lead. All we had to do was to let them know what our natural size constraints were.
On the software side, Ciklum helped form a more wide solution. We had code for different parts of things, but they were instrumental in putting all unitedly in one single and neat package. The platform uses C++ and JavaScript, and it’s a Linux-based software at this point. We eventually want to transition it to Windows. The backend database is based on MongoDB.
How did you come to work with Ciklum?
I believe we establish Ciklum through a relation from a manufacturing firm we met at a debateion. We had initially asked that organisation to associate with us, but we were too soon stage for them, so they directed us to Ciklum. They were incredibly professional and were able to educe both the hardware and software side of things, which was not the case for the antecedent firm we were working with. It was nice to have one organisation encompass all we were looking for. Ciklum was also thoughtful of our comcommission and didn',t try to influence our determinations.
How much have you invested with Ciklum?
The cost of Ciklum',s work has been between $120,000 and $150,000. Product educement is not common. Things have befit much more efficient, but there has been a lot of educement work done on the hardware and software sides, which proved time-consuming.
What is the terminal result of working with Ciklum?
We began working with Ciklum in June 2016.
Results achieved
Could you share any evidence that would prove the fruitivity, condition of work, or contact of the engagement?
From the business side of things, we',re quiet an soon stage organisation. We',re excited to have a terminal form factor. The fruit is prompt to be deployed at our associate hospital in Uganda, and Ciklum has done a big job of sticking to our timelines and getting it prompt precedently the deadline. We',ve passed all of our safety tests for the artifice, which is big. We',ve submitted our proposals and are currently waiting to hear back from our associates in Uganda.
We are fairly new to the process ourselves. Ciklum had worked in a correspondent space, but our fruit is different. They knew the general safety standards but didn',t have the expertise to lead us on what testing needed to be done precisely. Ciklum was upfront almost this from the commencement, which was good since this was not an area we were ready to compromise. When we did our safety testing, Ciklum was receptive to answering any questions we had almost the artifice and making it compliant with all regulations.
How did Ciklum accomplish from a project treatment standpoint?
Ciklum gave us approach to JIRA, allowing us to track the hours they spent on tasks. We have fairly customary meetings—almost once per week—in order to debate anything going on. Ciklum',s team is always looking for feedback and giving advice on how to make things better. They check with us precedently making any changes to the allocated hours and give recommendations on whether a task should be done now or later. They',re always professional in this perception.
We',ve been interacting with Ciklum',s project director and also with their tech team. It depends on the debateion question, on a weekly basis, I',ve mainly talked with Anton Zemliankin, who has more of a project treatment role, and Evgeny Volodzko, who has been doing much of the educement itself. If there is an effect with our battery, we will be introduced to the individual who works on the battery side of things to fix that it will be addressed. We know Ciklum',s total team, which is big, and I find that they have a wide difference of expertise.
What did you find most forcible almost Ciklum?
Understanding our comcommission, including what we were trying to do and the constraints we had, was the most significant factor to us. Cost, power-efficiency, and size were three of the biggest variables we were looking at. This has made things more costly from a educement perspective, but Ciklum has always been supportive in knowledge what those constraints were and working within them. I ponder that this is fairly different compared to other companies that we',ve talked to. Other groups told us it couldn',t be done, but that was simply owing they didn',t know how to do it. Ciklum has always tried to come up with creative ways for ensuring we achieved our goal.
From a project treatment perspective, Ciklum has done a big job. We always know what they',re doing and how they',re doing it. Ciklum is very good at explaining this process to us.
Are there any areas Ciklum could better?
This is somewhat out of their control, but I wish the fruit educement itself had been commoner.
