India

Title: Microfluidic Flow Management System
 
Purpose: to provide flawless flow of microfluids from various sources to various destinations.
 
 
1. Project Scope
 
We need to build a system to control micro fluids from various sources to different destinations using micro-fluidic valves of brand Labsmith or VICI. Pressure to pump/push liquid is available from source. These micro fluids are hazardous/radio active in nature. To ensure that expected path and system set path are same, pressure testing or other closed loop feedback systems should be used. It is also necessary to purge chosen path by neutral liquid and gas to avoid cross contamination. System should also indicate error in case of difference between set and selected path.&nbsp;
Developer is expected to use suggested hardware, write operation software including user interface and box it to make a complete deliverable solution.
 
 
2. Technical Background
 
Developer is expected to design PLC based system preferably of Delta make. User interface (2 types) is to be developed using 1) HMI &amp; 2) BCD output knobs - one to select source and another to select destination. System should have wired and wireless communication option between operator-control-switching module. System should be able to choose path, indicate it, test and or purge it and indicate error if any before actual flow is allowed. In case of power outage, it should remember and maintain position to commence flow from where it got interrupted. Developer can suggest battery back up or UPS if required. System should be able to maintain and recall time based records of all operations including error stages for 3 months.
All necessary documtation, links, literature, domain knowledge etc will be provided.
 
 
3. Architecture &amp; Design
 
System will have 3 basic modules.&nbsp;
a) Operator interface
b) Control Module
c) Switching Unit
 
A single phase 230 V 50 Hz AC power will be provided for all modules.
Distance between operator interface and remaining modules can be up to 25 meters. Flow of liquid will be from/to multiple peek tubes of 1/16 size. These tubes will bring liquid under pressure from various sources and is required to be directed to various destinations. There will be 2 valves. First valve will have multiple inputs and single output. Second valve will have single input (connected to output of first valve) and multiple outputs. For ease of use and maintenance, developer can select 2 valves of single model design.
 
 
4. Functionalities
 
At a time, only one tube will bring liquid. All incoming tubes will go to first switching valve. From there, depending on operator selection, valve will position itself to select incoming liquid port and direct it to one single output port. This output port will be connected to another valve of single input port. There will be multiple outputs to this valve and depending on operator selection, valve will position itself to selected output port.
Before actually sending liquid to sitching module, operator should be able to indicate, test, purge slected path and indicate error if any based on closed loop feedback. Only after ensuring that the selected path is the same as desired path, a flow should begin.
 
 
5. Data Flow and APIs
 
Based on production schedule, operator will select desired liquid source and expected destination. He will confirm it with supervisor and ensure that selected path is activated by action of both valves. He will test this path by applying pressure and using pressure sensors connected at both ends of path. Operator will purge this path by liquid or gas. After doing so, he will request/allow supervisor to commence liquid flow. After completing liquid transfer, operator will purge flow path, reset valve positions and wait for the next scheduled liquid transfer.
On completion of set no.s of operations or time limit, system will indicate redyness for periodic maintenance of the system.
There should be 3 levels of password protected operator levels. Namely, Engineer, Operator and Supervisor. Engineer with all rights, operator ro only select and test path and supervisor to allow liquid transfer.
 
 
6. Timeline and Milestones
 
Week 1: Understanding basic comcept, function and queries resolution if any
Week 2: Preparation, list Software modules, finalise functionality scope
Week 3: Design, finalise hardware vendors, enclosures, communication arrangements.
Week 4: Functional Software testing and user interface finalization.
Week 5: Procurement of all hardware and sub-assemblies, parts etc.
Week 6: Commissioning, testing of software with hardware.
 
 
7. Potential Challenges
 
a. Establishing proper interdevices communication
b. Error feee operation between desired and selected/implemented path
c. Ease of use for operator
 
 
8. Communication and Collaboration
 
This will primarily be required for domain knowledge sharing and operating procedure. Design of proper work flow and software flow chart will minimise this requirement. Owners of the job will be available round the clock to clarify domain queries and operator related procedure.
 
 
9. Documentation
 
During software development and at the end of it, developer will keep on maintaining and submitting versions of source codes with necessary remarks. Also developer will make owner easy to replace, upgrade software in future whenever required.

Micro fluidic management system using PLC, HMI, total hardware build incl. boxing From Mumbai

Useful links

Company

Information

Content Writers

Freelancers

Freelance Jobs

Online Jobs

Designers

Developers

Translations