Inventory system team - The DUNE logis/cs management. - Minnesota - - PowerPoint PPT Presentation

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 1

• The DUNE logis/cs management.
• Minnesota group: Hajime, Bill Miller, Ron Poling, Aaron Mislivec, 


Greg Pawloski, and Marvin Marshak.

• There are other groups who show interest in this project.


David DeMuth (Valley City State)
 Ernesto Kemp (UNICAMP, Brazil)
 For now, just ini/ated email changes with them.
 We’ll start to have more regular mee/ngs with them in the near future.

Inventory system team

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 2

• We envision endusers input info to the DB though web browsers.


So we would need a few PCs at ITF/SURF/4850.

• We would need some (e.g., RF) readers/scanners at places like ITF.


Note: S/ckers on certain parts might not work in LAr.Might need to laser-etch serial # or bar-code. (thanks Charles for poin/ng this out)

The system

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 3

• Currently, we are looking at two possibili/es to build the system:
• 1. Form the system with Python based APIs.
• Easier to expand/add 


features we need (very important!)

• But needs to develop from scratch.


Here is our ini/al test run, 
 accessing to a Sqlite 
 through a web browser locally.

• 2. Open-source based more-or-less-developed system
• Ernesto ini/ally brought up this idea.


A candidate package is Apache OFBiz (hbp://ociz.apache.org).
 One of his students has experience with such package.

• It is mostly already developed for typical inventory system needs.
• So we are currently looking into see how easily we could modify the package.


It is Java based. And we are trying to see what modifica/ons can be done without coding in Java.

DIY from scratch or…?

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 4

• In principle, we should avoid depending on commercial soiwares whenever

possible, especially for a long term project (and cost-/modifica/on-wise..etc).

• A possible reason for going this route would be that


in case if we need to rent warehouse(s) near/around Rapid City.
 The warehouse(s) likely use commercial inventory system.

• S/ll, in this case, we are hoping that our DB would be able to talk to their DB.
• Exchanging shipping/receiving info should be easy and trivial.. we hope.
• But adding capabili/es of storing addi/onal info, such as QA or other test results

(pictures, plots? etc) might require us to communicate with the contracted company.
 E.g., one of the largest warehouse in Rapid City, Dakota Warehouse, uses
 3PL Central. If/when we know exactly what/how we like to modify their system,
 we could start to talk to Dakota Warehouse + 3PLCntr.

another op/on… commercial route

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 5

• The system consists of clients and a server, where each clients talk to the

server through web browsers.

• Manpower :


Minnesota + 
 Valley City State, North Dakota (David DeMuth) + 
 UNICAMP, Brazil (Ernesto Kemp) +
 students.

• Y18 : Finalize the basic plamorm and perform basic tests, at least locally.


The DIY or open-source.

• Y19 : Soiware development : 


Develop each components, 
 such as shipping/receiving/storing test results at ITF, by students.
 Perform realis/c tests through the web.

• Y20 : Deploying the system and perform final tests


(i.e., the main DB needs to be set and running by this /me).

• >Y20 : maintenance…

Overview of our plan for the next few years

Installation coordination meeting JUN/27/2018 Hajime Muramatsu U of Minnesota 6

• Y18 : NONE
• Y19 :
• Two students for 52 weeks : $30000.
• Y20 : Deploying the system:
• The main server : $7000 each : $7000×2 = $14000 


(an extra in case of failure).

• Clients ( a few PCs that are capable of running web browsers) at each

loca/ons, an ITF, SURF, and 4850. $2000 each : $2000×3 = $6000.
 We are assuming that sta/ons at shipping sites are covered by each consor/a.

• Bar-code scanners/readers : 


For now, assuming 12 iPad scanners, $500 each.
 $500×12 = $6000.

• >Y20 : maintenance…

• TOTAL : $56000

Const Es/mate for this project