Multiaxial Subassemblage Testing (MAST) System

1
Multiaxial Subassemblage Testing (MAST) System
University of Minnesota NSF George E. Brown, Jr.
NEES Site

• C. French, A. Schultz, J. Hajjar, C. Shield, R.
  Dexter
• Department of Civil Engineering
• D. Ernie
• Department of Electrical and Computer Engineering
• D. Du
• Department of Computer Science and Engineering

2
(No Transcript)
3
Overview of equipment proposal
MAST system enables multi-axial cyclic static
tests of large-scale structural subassemblages
including portions of beam-column frame systems,
walls, and bridge piers Stiff steel
cruciform-shaped crosshead manipulated with 6-DOF
control technology enables control of a plane in
space (can apply pure planar translations or
gradients) System features mixed-mode control
capabilities (each DOF may be controlled as
either load or deformation) System features four
vertical actuators capable of applying 5870 kN
(510 mm), and two sets of horizontal actuator
pairs capable of applying 3910 kN (400 mm) in
orthogonal directions, and four ancillary
actuators
4
Update on Project Status and Schedule

• Construction of MAST Laboratory (new facility to
  house NEES equipment) to begin Jan 02.
  Schematics for facility completed and scheduled
  for presentation at October UMN Board of Regents
  meeting for final approval.
• Hydraulic equipment and controller contract made
  to MTS 9/01.
• Developing pool of candidates and interviewing
  for two technical research coordinators (having
  telepresence and hydraulics/mechanical
  specialties)
• Project is on schedule however, UMN milestone
  dates for receiving significant input from SI are
  approaching

5
(No Transcript)
6
MAST System Teleparticipation Infrastructure
Internet 2
Campus Network
GigaPoP
Core Node
Internet 1
Gigabit LAN
Video Servers (2)
Client PCs (2)
Archiving Visualization Server
NEESPoP
Control DAQ Server
Still Image Servers (2)
MAST Controller
Control Sensors
Actuators
Still Cameras (8)
Measurement Sensors
MAST System
Video Cameras (8)
7
Information for SI

• Gigabit Ethernet Link available Jan 02 for beta
  testing on campus, Jan 03 for development within
  NEES facility
• Telepresence expertise covered by three co-PIs
  from 3 depts. (CivE, ElecE, and CompSci)
  research coordinator. Co-PIs have experience in
  streaming video, networking, multimedia
  computing, and teleparticipation
• UMN site contains remotely controllable still
  cameras (8) and video cameras (8) with required
  transmission rates of 200 Mbits/sec, and 200
  data channels with required transmission rates of
  20 Kbits/sec. Data synchronization is important.
• Tests on specimens may take 24-48 hours to
  completion. There may be pauses between load
  cycles for damage identification.
• UMN schedule of information needed from SI
• By 12/01 specifications for all hardware, OS,
  and software
• By 4/02 Beta versions of all SI software
• By 9/02 Initial verified versions of all
  software

8
Information for SI (cont.)

• UMN prioritization for functionality of MAST
  operations
• Local control of MAST system from Control and
  Data Acquisition Server
• Local sensor data acquisition and temporary
  storage of information on Control and Data
  Acquisition Server
• Archiving and retrieval of data after an
  experiment on Visualization and Archiving Server
  and at national repository
• Teleobservation on Client Machine during an
  experiment
• Rudimentary playback and visualization of an
  experiment on Visualization and Archiving server
  after experiment is completed
• Teleoperation on Client Machine during an
  experiment
• Sophisticated playback and visualization of an
  experiment on Visualization and Archiving server
  after an experiment is completed
• Model-based simulation and integration of
  simulation with experiments

9
Questions for SI

• What are expectations of SI of each individual
  equipment site?
• How will expectations and needs of individual
  sites regarding telepresence/telecollaboration,
  data archival/management, and model-based
  simulation be integrated by SI?
• With plan for 3 early adoptor sites, how will SI
  ensure that all sites are engaged, i.e., have a
  voice in decisions/direction benefit from
  learning/resources invested in development
  process and do not lose precious time to
  completion?
• As individual sites develop questions/needs, what
  expectations can sites have regarding
  responsiveness of SI? How should this
  communication be handled, from each individual
  site to SI or in coordinated fashion? Who is the
  appropriate contact (e.g. Tom Prudhomme)?
• How much involvement will SI have in development
  of metadata protocols, hardware
  specifications/structure, software
  specifications/development, telepresence/telecoll
  aboration, data archival/management, model-based
  simulation etc.?

10
Information for CD Team

• MAST system to be housed in new laboratory on
  campus w/in walking distance of department.
  Offices for visiting researchers elsewhere on
  campus.
• On-site research coordinators will participate in
  all tests (this ensures safety, functionality,
  and efficiency)
• Unique features of MAST include large force and
  stroke capacities and seamless 6DOF control
• MAST system can be used to investigate
  non-seismic research issues and industrial
  problems
• UMN prefers long-term vision of hard-funded
  annual operation and maintenance costs. This
  would facilitate site scheduling and coordination
  (e.g., if external researcher uses facility past
  predicted schedule, hard-funding will lessen
  impact on facilityresearchers will not need to
  be requested to leave facility for funding
  considerations). This also helps planning for
  facility prior to determining which proposals
  will be funded to use facilities.
• UMN has expectation for CD assistance with
  outreach activities and promotion of MAST facility

11
Questions for CD Team

• What are the expectations of CD for individual
  sites?
• What are CD short term goals (prior to site
  commissioning)?
• What is CD long term vision of management (after
  commissioning)?
• Short term questions
• Will CD have a role in determining issues such as
  the format for data archival and desirable
  features for telepresence? (CD can gather info
  from external user perspective.)
• Will CD facilitate/coordinate site task groups on
  common issues?
• What does CD envision as its relationship with
  individual sites and SI in short term?
• Will CD have or seek any funds for development
  of common resources/tools?
• Long-term questions
• - How will CD coordinate site scheduling, handle
  site operation and maintenance costs (hard-funded
  annually or from project to project), engage
  external users, integrate contract testing into
  research schedule, facilitate outreach and
  training, assess sites, help seek sources of
  research funding, coordinate proposals?