nmrbox.org

Budget: Operatingvery lean staffing

• UCHC• 2 FTEs

• Sysadmin (operations; web site; TRD 1; training & dissemination)• Developer (TRD 2)

• Schuyler – 80% (TRD 1, TRD 2, training & dissemination; DBP support)• Others 20% or less

• Hoch (20%), Gryk (20%), Maciejewski (15%), Gorbatyk (10%), Moraru (5%)

• Wisconsin• 2 FTEs

• Research associate (TRD 2; support of DBPs)• Programmer (TRD 2; sysadmin)

• Others 20% or less• Maziuk (10%), Ulrich (5%), Livny (5%), Markley (2%, no cost)

nmrbox.org

• Cincinnati• 1 FTE

• PD research associate (TRD 3)

• Eghbalnia (50%) (TRD 3; training and dissemination)

Budget: Operating (cont.)

nmrbox.org

NetworkingLeverage existing high-bandwidth interconnects, but “last mile” infrastruture

dedicate to project servers needed

Storage architectureAmpliStor, Isilon mirroring between Farmington and Madison for high availability,

security

Compute serversVMs and SaaSCloud services generally don’t support VMs because of security issues

Budget: Capitalphased roll-out based on projected need

nmrbox.org

BMRB funding• Requested funds will support projects that do not overlap

with existing BMRB activties:• Maintenance of off-site mirrored NMRbox hardware and software systems (TRD 1)• Software projects specific to the integration of BMRB services with the CONNJUR

WB infrastructure (TRD 2), including data deposition and retrieval systems• Construction of data models for the archiving of new kinds of information

(TRD 2 and 3)• Collaborations with DBP and collaborative partners

• Current BMRB NLM and proposed NIGMS support funds:• Maintenance of current data acquisition, validation, annotation and distribution

systems• Archive data maintenance and remediation• Development of new methods for acquiring data not currently in the archive from

publications• Design and construction of improve data archival and distribution infrastructure• wwPDB responsibilities including data deposition and processing support