DisplayChannel
type: Class
subclass of: Restriction
  cardinality: 1
  on property: isTimeChannel
subclass of: Restriction
  on property: hasUnit
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: mappings
subclass of: Restriction
  on property: hasUnit
  min cardinality: 0
subclass of: Restriction
  on property: mappingParameter
  min cardinality: 0

isTimeChannel
type: DatatypeProperty
domain: DisplayChannel
range: boolean
comment: The title of a periodical presenting articles on a particular subject.

hasUnit
type: ObjectProperty
domain: Class
  union of: DisplayChannel
  union of: Measurement
range: Unit
type: FunctionalProperty
comment: Defines the relationship of "contains" -- A domain such as a DisplayChannel or Measurement has a specified Unit of measure.

DataTurbineChannel
type: Class
subclass of: Restriction
  on property: dtChannelType
  cardinality: 1
subclass of: Restriction
  on property: actualDAQChannel
  cardinality: 1
subclass of: Restriction
  on property: dtChannelURI
  cardinality: 1

EventGroup
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: hasDAQSetups
subclass of: Restriction
  min cardinality: 0
  on property: hasWaveFormSetups
comment: EventGroup is defined as a collection of Events. Any change to the data acquisition setup, sensor setup or to the specimen setup initiates a new Event Group. The sequence of EventGroups is determined by startDateTime.
subclass of: Restriction
  on property: hasSpecimenSetups
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasDataTurbineSetups
subclass of: Restriction
  on property: hasEvents
  min cardinality: 0
subclass of: SingleSiteActivity
subclass of: Restriction
  min cardinality: 0
  on property: hasSensorSetups

hasDAQSetups
type: ObjectProperty
range: DAQSetup
comment: Defines the relationship of "contains" -- A class such as EventGroup has a DAQSetup of one or more electronic devices whose primary purpose is to acquire data.
domain: EventGroup

hasWaveFormSetups
type: ObjectProperty
comment: Defines the relationship of "contains" -- An Event has a WaveFormSetup.
domain: Class
  union of: Event
  union of: SubEvent
  union of: EventGroup
range: WaveFormSetup

hasSpecimenSetups
type: FunctionalProperty
range: SpecimenSetup
type: ObjectProperty
domain: EventGroup
comment: Defines the relationship of "contains" -- A domain such as EventGroup has one or more SpecimenSetups.

hasDataTurbineSetups
type: ObjectProperty
comment: Defines the relationship of "contains" -- An EventGroup has a DataTurbineSetup.

hasEvents
type: ObjectProperty
domain: Class
  union of: EventGroup
  union of: MultiSiteEvent
range: Event
comment: Defines the relationship of "contains" -- A domain such as an EventGroup or MultiSiteEvent have at least one Events, which is defined as one run of an experiment or a simulation.

SingleSiteActivity
type: Class
comment: SingleSiteActivity is a collection of Tasks, Eventgroups and Events that are carried out at only one Site.
subclass of: Restriction
  on property: hasSite
  cardinality: 1
subclass of: Activity

hasSensorSetups
type: ObjectProperty
range: SensorSetup
domain: Class
  union of: EventGroup
  union of: Specimen
comment: A specimen has one or many associated SensorSetups, which define the setup of Sensors with respect to Specimen.

Person
type: Class
subclass of: Restriction
  on property: title
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: address
subclass of: Restriction
  min cardinality: 0
  on property: homePage
subclass of: Restriction
  min cardinality: 0
  on property: phoneNumberType
subclass of: Restriction
  on property: phoneNumber
  min cardinality: 0
subclass of: Restriction
  on property: firstName
  cardinality: 1
subclass of: Restriction
  on property: otherInfo
  min cardinality: 0
subclass of: Restriction
  on property: lastName
  cardinality: 1
subclass of: Restriction
  on property: affiliation
  min cardinality: 0
subclass of: Restriction
  on property: title
  min cardinality: 0
subclass of: Restriction
  on property: personID
  cardinality: 1
subclass of: SiteInformation
comment: This class represents all of the personnel who participate in projects and experiments.
subclass of: Restriction
  min cardinality: 0
  on property: email

title
type: DatatypeProperty
domain: Person
range: string
type: FunctionalProperty
comment: A descriptive or general heading (as of a chapter in a book) or name of a person.

address
type: DatatypeProperty
domain: Class
  union of: Person
  union of: Organization
comment: A place where a person or organization may be communicated with.
range: string
type: FunctionalProperty

homePage
type: FunctionalProperty
range: string
comment: The opening or main page of a website, intended chiefly to greet visitors and provide information about the site or its owner.
domain: Class
  union of: Person
  union of: Organization
type: DatatypeProperty

phoneNumberType
type: FunctionalProperty
domain: Person
range: DataRange
  one of: voicePhone
  one of: voiceMail
  one of: faxNumber
  one of: mobilePhone
comment: The type of phone or fax number of the Person or entity.
type: DatatypeProperty

phoneNumber
type: FunctionalProperty
domain: Person
comment: Digital telephone number or FAX number.
type: DatatypeProperty
range: string

firstName
type: FunctionalProperty
comment: A given name or the name that occurs first in a given name.
type: DatatypeProperty
domain: Person
range: string

otherInfo
type: DatatypeProperty
domain: Person
comment: Other information about this entity. Such as for a Person, their responsibilities to the Project.
range: string

lastName
type: DatatypeProperty
domain: Person
type: FunctionalProperty
range: string
comment: Surname; a name shared in common to identify the members of a family, as distinguished from each member's given name.

affiliation
type: ObjectProperty
range: Organization
comment: The company or group that this entity is associated with. If the entity is an employee, for example, this would be the company which employs him/her. This can be a foreign key to another instance of Person. It is not required that the other instance be instantiated.
domain: Person

personID
type: DatatypeProperty
comment: Identification number for a person affiliated with a NEES project.
range: string
type: FunctionalProperty
domain: Person

SiteInformation
type: Class
comment: This group of classes defines the abstraction of a specific site. A typical site may have certain organizations, persons, facilities, and others.

email
type: DatatypeProperty
comment: An address such as "name@location.org", used within a system for sending and receiving messages electronically over a computer network, as between personal computers.
domain: Person
type: FunctionalProperty
range: string

ApparatusSetup
type: Class
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: Restriction
  max cardinality: 1
  on property: longDescription
subclass of: Restriction
  on property: longDescription
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: shortDescription
comment: The assembly and arrangement of the tools and apparatus required for an Activity. ApparatusSetup is defined by a set of associated parameters.
subclass of: Restriction
  on property: shortDescription
  min cardinality: 0

name
type: FunctionalProperty
comment: a word or set of alphanumeric characters by which any entity is identified or distinguished from others, however, name might not be unique, that's why a uniquely assigned NEESCode or URI is needed to internally identify an object.
domain: Class
  union of: Unit
  union of: File
  union of: Folder
  union of: Apparatus
  union of: Organization
  union of: ApparatusSetup
  union of: Activity
  union of: Site
  union of: SpatialLocation
  union of: SensorGroup
  union of: WaveForm
  union of: Publication
type: DatatypeProperty
range: string

longDescription
type: FunctionalProperty
comment: More detailed description of an object and its high level information.
type: DatatypeProperty
range: string
domain: Class
  union of: ApparatusSetup
  union of: Apparatus
  union of: Activity
  union of: Site

shortDescription
type: DatatypeProperty
domain: Class
  union of: ApparatusSetup
  union of: Apparatus
  union of: Activity
  union of: Site
comment: A short "display style" description of an object.
range: string
type: FunctionalProperty

FloatMeasurement
type: Class
comment: Measurement described using real number(s), single-precision floating point. 'Float' is a primitive data type supported by Java (size/format: 32-bit IEEE 754).
subclass of: Measurement
subclass of: Restriction
  cardinality: 1
  on property: value

Measurement
type: Class
comment: The dimensions, capacity, or amount of something ascertained by measuring; a measured quantity.
subclass of: Restriction
  on property: hasUnit
  cardinality: 1
subclass of: ComplexDataType

value
type: DatatypeProperty
comment: A numerical quantity that is assigned or is determined by calculation or measurement
range: double
type: FunctionalProperty
domain: FloatMeasurement

PrimaryEquipment
type: Class
comment: PrimaryEquipment is the major equipment that is used for the execution of an ExperimentEvent. PrimaryEquipment categorizes a system of equipment with respect to a specific research area.
subclass of: Restriction
  min cardinality: 0
  on property: hasFigures
subclass of: Restriction
  min cardinality: 0
  on property: operators
subclass of: Apparatus
subclass of: Restriction
  max cardinality: 1
  on property: manufacturer
subclass of: Restriction
  min cardinality: 0
  on property: manufacturer

Organization
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: description
subclass of: Restriction
  max cardinality: 1
  on property: address
subclass of: Restriction
  max cardinality: 1
  on property: description
subclass of: SiteInformation
subclass of: Restriction
  max cardinality: 1
  on property: homePage
comment: An administrative and functional structure, such as a business, including the personnel of such a structure.
subclass of: Restriction
  cardinality: 1
  on property: NEESCode
subclass of: Restriction
  on property: address
  min cardinality: 0
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: Restriction
  on property: homePage
  min cardinality: 0

description
type: FunctionalProperty
domain: Class
  union of: File
  union of: Folder
  union of: Organization
  union of: WaveForm
  union of: SoftwareProgramCapability
  union of: SpatialLocation
  union of: Unit
range: string
type: DatatypeProperty
comment: A simple description of the object.

NEESCode
type: FunctionalProperty
comment: A unique reference code assigned by the NEES Consortium for an object.
domain: Class
  union of: Project
  union of: Organization
range: string
type: DatatypeProperty

SoilDeposit
type: Class
comment: Molded soil specimen comprising test article. A soil deposit may consist of one to many soil layers and other components.
subclass of: Specimen

Specimen
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: hasFigures
subclass of: Restriction
  min cardinality: 0
  on property: hasMaterials
subclass of: Restriction
  min cardinality: 0
  on property: hasDescriptions
subclass of: Apparatus
comment: Specimen is a primary component of the data model. A Specimen is one of many Apparatus used in conducting an Activity. One or more Specimens may be created during a Project and performance of subsequent Tasks. An Event or EventGroup is conducted utilizing the Specimen.
subclass of: Restriction
  min cardinality: 0
  on property: hasSensorSetups

VersionedSoftware
type: Class
subclass of: Software
comment: Particular Version of a Software Program

Software
type: Class
comment: This group of classes defines software and associated properties used for simulation, data analysis, etc.

ShakingTableEquipment
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: tableClearance
subclass of: Restriction
  on property: maximumSpecimenMass
  max cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: tableWidth
subclass of: Restriction
  max cardinality: 1
  on property: tableLength
subclass of: Restriction
  min cardinality: 0
  on property: tableClearance
comment: Shaking table includes the structure upon which test specimen(s) are mounted and may include the subcomponents such as actuators, power, control systems, and various types of specimens.
subclass of: Restriction
  on property: maximumSpecimenMass
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: tableWidth
subclass of: Restriction
  min cardinality: 0
  on property: tableLength
subclass of: PrimaryEquipment
subclass of: Restriction
  min cardinality: 0
  on property: mountedOnCentrifuge
subclass of: Restriction
  on property: mountedOnCentrifuge
  max cardinality: 1

tableClearance
type: DatatypeProperty
comment: Overhead clearance of shake table in z direction (10 to 20000 mm), a standard specification for a shaking table system.
type: FunctionalProperty
domain: ShakingTableEquipment
range: string

tableWidth
type: FunctionalProperty
range: double
comment: Table lwidth in y direction (10 to 20000 mm), a standard specification for a shaking table system.
type: DatatypeProperty
domain: ShakingTableEquipment

tableLength
type: FunctionalProperty
comment: Table length in x direction (10 to 20000 mm), a standard specification for a shaking table system.
range: double
domain: ShakingTableEquipment
type: DatatypeProperty

mountedOnCentrifuge
type: FunctionalProperty
range: boolean
domain: ShakingTableEquipment
type: DatatypeProperty
comment: {Boolean} Indicator of whether a shaking table associated with a specified Centrifuge test/Event is mounted on the Centrifuge Apparatus.

Task
type: Class
subclass of: Restriction
  on property: hasPublications
  min cardinality: 0
subclass of: SingleSiteActivity
subclass of: Restriction
  min cardinality: 0
  on property: keyWords
subclass of: Restriction
  min cardinality: 0
  on property: hasEventGroups
comment: A Task belongs to a particular Project. It identifies a particular aspect of a Project that has a specific goal. Each Task has a distinct InfrastructureSetup. In other words any changes to the InfrastructureSetup initiates a new Task. A Task may include one or more EventGroups.
subclass of: Restriction
  on property: hasInfrastructureSetups
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasRolePersons

hasPublications
type: ObjectProperty
range: Publication
comment: Defines the relationship of "contains" -- Domains such as Project and Task have Publications identified with them, and/or produced through the project.
domain: Class
  union of: Project
  union of: Task

keyWords
type: DatatypeProperty
domain: Class
  union of: Publication
  union of: Task
  union of: Project
range: string
comment: A word used as a reference point for finding other words or information.

hasEventGroups
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as a Task or MultiSiteEventGroup have at least one EventGroups, which is defined as a collection of Events.
domain: Class
  union of: Task
  union of: MultiSiteEventGroup
range: EventGroup

hasInfrastructureSetups
type: ObjectProperty
range: InfrastructureSetup
domain: Task
comment: Defines the relationship of "contains" -- A domain such as a Task has one or more InfrastructureSetups.

hasRolePersons
type: ObjectProperty
domain: Class
  union of: Task
  union of: Site
  union of: Project
range: RolePerson
comment: Defines the relationship of "contains" -- Domains such as Task, Site and Project have identified RolePersons.

WaveFormSetup
type: Class
subclass of: Restriction
  on property: hasWaveForm
  cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: hasDirection
comment: The setup of a wavform for specified event(s). The waveform may be a record of a previous event or synthetic signals.
subclass of: InputDataSetup
subclass of: Restriction
  cardinality: 1
  on property: scaleFactor

hasWaveForm
type: ObjectProperty
domain: WaveFormSetup
comment: Defines the relationship of "contains" -- A WaveFormSetup as a specified WaveForm.

hasDirection
type: ObjectProperty
domain: WaveFormSetup
range: Location
comment: Defines the relationship of "contains" -- A domain such as WaveFormSetup has a defined direction from which the Wave was generated. The direction may be relative (to some part of the experiment apparatus) or a measured using a coordinate system.
type: FunctionalProperty

InputDataSetup
type: Class
subclass of: ApparatusSetup
comment: The setup of InputData for a specified event(s). Inputdata is defined as the control signals to the Apparatus.

scaleFactor
type: DatatypeProperty
domain: Class
  union of: WaveForm
  union of: WaveFormSetup
range: double
comment: A real number that is used to modify the original value of a quantity
type: FunctionalProperty

SubEvent
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: hasOutputData
subclass of: SingleSiteActivity
subclass of: Restriction
  min cardinality: 0
  on property: hasWaveFormSetups

hasOutputData
type: ObjectProperty
comment: Defines the relationship of "contains" – An Event has output data, which includes raw or processed data. The output can be organized in Folders.
domain: Class
  union of: Event
  union of: SubEvent
range: Folder

ShakingSystem
type: Class
subclass of: SecondaryEquipment
comment: Shaking system parameters are common to many different types of Primary Equipment.

SecondaryEquipment
type: Class
subclass of: Restriction
  cardinality: 1
  on property: manufacturer
comment: SecondaryEquipment may be a component of the PrimaryEquipment or may be a piece of equipment that facilitates the excution of Event, data collection, observation.
subclass of: Apparatus
subclass of: Restriction
  on property: owner
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: hasFigures
subclass of: Restriction
  on property: owner
  min cardinality: 0
subclass of: Restriction
  on property: manufacturersPartNumber
  cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: manufactuersModelNumber
subclass of: Restriction
  on property: serialNumber
  cardinality: 1

DAQDevice
type: Class
subclass of: SecondaryEquipment
comment: A piece of equipment used to facilitate the reading, processing and recording of Sensor output.

Site
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: longDescription
comment: An inventory of devices, equipments, and personnel. This is the modeling of large scale facilities, such as shake table or centrifuge. Detailed information of equipments is modeled in other classes.
subclass of: Restriction
  on property: hostedBy
  min cardinality: 0
subclass of: Restriction
  on property: shortDescription
  max cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: hostedBy
subclass of: SiteInformation
subclass of: Restriction
  on property: shortDescription
  min cardinality: 0
subclass of: Restriction
  on property: hasPrimaryEquipments
  min cardinality: 0
subclass of: Restriction
  on property: hasRolePersons
  min cardinality: 0
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: Restriction
  on property: longDescription
  min cardinality: 0
subclass of: Restriction
  on property: hasSecondaryEquipments
  min cardinality: 0

hostedBy
type: FunctionalProperty
comment: The organization where a site is hosted.
domain: Site
type: ObjectProperty
range: Organization

hasPrimaryEquipments
type: ObjectProperty
domain: Class
  union of: InfrastructureSetup
  union of: Site
  union of: SpecimenSetup
range: PrimaryEquipment
comment: Defines the relationship of "contains" -- Domains such as InfrastructureSetup and Site have PrimaryEquipment.

hasSecondaryEquipments
type: ObjectProperty
comment: Defines the relationship of "contains" -- Domains such as InfrastructureSetup and Site have SecondaryEquipment.
domain: Class
  union of: InfrastructureSetup
  union of: Site
range: SecondaryEquipment

MultiSiteActivity
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: hasSites
comment: MutiSiteActivity is a collection of Tasks, Eventgroups and Events that may be carried out at more than one Site. MultiSiteActivity is used to establish the link among related activities.
subclass of: Activity

hasSites
type: ObjectProperty
domain: Class
  union of: MultiSiteActivity
  union of: Project
range: Site
comment: Defines the relationship of "contains" -- Domains MultiSiteActivity and Project have more than one Site accociated with an Activity.

Activity
type: Class
subclass of: Restriction
  on property: shortDescription
  max cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: Restriction
  min cardinality: 0
  on property: longDescription
subclass of: Restriction
  on property: startDateTime
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: endDateTime
subclass of: Restriction
  min cardinality: 0
  on property: localTimezone
subclass of: Restriction
  max cardinality: 1
  on property: startDateTime
comment: This is an abstraction of project, task, event group and event (and associated activities), which have a duration and objectives.
subclass of: Restriction
  on property: localTimezone
  max cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: longDescription
subclass of: Restriction
  on property: shortDescription
  min cardinality: 0
subclass of: Restriction
  on property: endDateTime
  min cardinality: 0

DateTime
type: Class
subclass of: Restriction
  on property: millisecond
  cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: minute
subclass of: Date
subclass of: Restriction
  on property: hour
  cardinality: 1
comment: The time at which an event occurs, recorded as required; minutes, hours, seconds, and/or milliseconds.
subclass of: Restriction
  on property: second
  cardinality: 1

millisecond
type: DatatypeProperty
comment: One thousandth of a second.
domain: DateTime
type: FunctionalProperty
range: int

minute
type: DatatypeProperty
comment: A unit of time equal to one sixtieth of an hour, or 60 seconds. Also, a unit of angular measurement equal to one sixtieth of a degree, or 60 seconds.
domain: DateTime
range: int
type: FunctionalProperty

Date
type: Class
comment: The month, day and year at which an event occurs.
subclass of: ComplexDataType
subclass of: Restriction
  cardinality: 1
  on property: month
subclass of: Restriction
  on property: year
  cardinality: 1
subclass of: Restriction
  on property: day
  cardinality: 1

hour
type: FunctionalProperty
range: int
domain: DateTime
type: DatatypeProperty
comment: The time of day determined on a 24-hour basis.

second
type: FunctionalProperty
comment: The 60th part of a minute of time or 60th part of an angular measurement.
type: DatatypeProperty
domain: DateTime
range: int

WaveForm
type: Class
subclass of: Restriction
  on property: peakDisplacement
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: peakVelocity
subclass of: Restriction
  on property: peakVelocity
  max cardinality: 1
subclass of: Restriction
  on property: description
  min cardinality: 0
subclass of: Restriction
  on property: name
  cardinality: 1
subclass of: Restriction
  on property: peakDisplacement
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: scaleFactor
subclass of: Restriction
  max cardinality: 1
  on property: samplingRate
subclass of: Restriction
  on property: recordUnit
  max cardinality: 1
subclass of: Restriction
  on property: peakAcceleration
  max cardinality: 1
subclass of: InputData
subclass of: Restriction
  on property: motionRecord
  cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: recordUnit
subclass of: Restriction
  min cardinality: 0
  on property: scaleFactor
subclass of: Restriction
  min cardinality: 0
  on property: samplingRate
comment: This class represents input strong ground motions. For future implementation, it can be linked to the existing strong ground motion databases.
subclass of: Restriction
  on property: peakAcceleration
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: description

peakDisplacement
type: ObjectProperty
domain: WaveForm
type: FunctionalProperty
comment: Maximum absolute value of displacement that is recorded or that can be achieved by an apparatus
range: FloatMeasurement

peakVelocity
type: ObjectProperty
comment: Maximum absolute value of velocity that is recorded or that can be achieved by an apparatus
range: FloatMeasurement
type: FunctionalProperty
domain: Class
  union of: WaveForm
  union of: ShakingSystem

samplingRate
type: FunctionalProperty
type: ObjectProperty
comment: the frequency of sampling per unit time; the number of data points per second; that a DAQ channel records or that defines a strong motion data, waveform
domain: Class
  union of: DAQChannel
  union of: WaveForm
range: FloatMeasurement

recordUnit
type: FunctionalProperty
range: Unit
comment: The Unit in which a time series record is presented.
type: ObjectProperty
domain: WaveForm

peakAcceleration
type: ObjectProperty
range: FloatMeasurement
domain: WaveForm
comment: Maximum absolute value of acceleration that is recorded or that can be achieved by an appratus. The peak acceleration or rate of change of velocity with respect to time in a specified time series record.
type: FunctionalProperty

InputData
type: Class
subclass of: DataElement
comment: InputData is defined as the control signals to the Apparatus.

motionRecord
type: FunctionalProperty
comment: The strong motion record, usually organized as columns of real numbers.
type: ObjectProperty

Penetrometer
type: Class
comment: A calibrated spring-loaded rod used to perform soil laboratory static strength measurements. A standard pocket penetromenter in 1/4" in diameter, and is pushed into the soil to a penetration of 6 mm and the gauge read = 2 x tiraxial compression. Yields approximate values in clays, and is used primarily for soil classification by consistency.
subclass of: SecondaryEquipment

Event
type: Class
comment: An Event is defined as one run of an experiment or a simulation. Events within an EventGroup may have different input motions, loading protocols, etc. The sequence of Events is determined by the startDateTime of the Event.
subclass of: Restriction
  on property: testType
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasOutputData
subclass of: Restriction
  cardinality: 1
  on property: hasSite
subclass of: Restriction
  on property: hasWaveFormSetups
  min cardinality: 0
subclass of: SingleSiteActivity
subclass of: Restriction
  on property: hasDescriptions
  min cardinality: 0
subclass of: Restriction
  on property: testType
  max cardinality: 1

testType
type: DatatypeProperty
comment: Types of tests such as shake table, centrifuge, tsunami, reaction wall, various field tests, and etc.
domain: Event
type: FunctionalProperty
range: string

hasSite
type: ObjectProperty
range: Site
domain: SingleSiteActivity
comment: Defines the relationship of "contains" -- A domain such as SingleSiteActivity has one Site accociated with an Activity.
type: FunctionalProperty

hasDescriptions
type: ObjectProperty
domain: Class
  union of: SoftwareSetup
  union of: Specimen
  union of: Event
comment: Defines the relationship of "contains" -- A domain such as SoftwareSetup, Specimen or SpatialLocation has narrative descriptions and notes, which can be included in DescriptiveFiles.

TPMServer
type: Class
comment: Computer server that hosts some or all of the services that facilitate telepresence at a NEES facility.
subclass of: TelepresenceDevice

TelepresenceDevice
type: Class
subclass of: SecondaryEquipment
comment: Enables communication, collaboration visually and verbally.

Folder
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: description
comment: This class represents a named or designated location where an object (DataElements, including Files, InputData, and Publications) can be saved in memory, on disks, or in the repository, in any computer-readable format.
subclass of: Restriction
  max cardinality: 1
  on property: description
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: ComplexDataType
subclass of: Restriction
  on property: hasFiles
  min cardinality: 0

ComplexDataType
type: Class
comment: Complex data types. May need special I/O routines.

hasFiles
type: ObjectProperty
domain: Class
  union of: Folder
  union of: Material
range: DataElement
comment: Defines the relationship of "contains" -- A domain such as a Folder has at least one DataElement, which can be i.e. a File, InutData, Parameter or Publication.

RoboticSystem
type: Class
comment: A robotic system can be used before, during or after an Event to perform multiple tasks on a Specimen. For instance users can use robotic tools to for precision specimen construction, or manipulate other physical objects which obtain measurements during Events.
subclass of: SecondaryEquipment

Journal
type: Class
subclass of: Restriction
  on property: issue
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: page
subclass of: Publication
subclass of: Restriction
  on property: journalName
  cardinality: 1
subclass of: Restriction
  on property: volume
  cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: page
subclass of: Restriction
  on property: issue
  max cardinality: 1
comment: The title of a periodical dealing especially with matters of current interest.

issue
type: DatatypeProperty
domain: Journal
range: string
type: FunctionalProperty
comment: Something produced, published, or offered, such as a single issue of a periodical witin a set (i.e. edition), or a distinct set of copies of an edition of a book distinguished from others of that edition by variations in the printed matter.

page
type: FunctionalProperty
range: string
type: DatatypeProperty
comment: The specific number of a page in a document, or the number the pages of a document, such as a periodical, book or technical report.
domain: Journal

Publication
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: URI
comment: Subclasses within this class relate to any scientific document published in a conference or by a research institution.
subclass of: DataElement
subclass of: Restriction
  on property: title
  cardinality: 1
subclass of: Restriction
  on property: publicationYear
  cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: keyWords
subclass of: Restriction
  on property: name
  cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: authors
subclass of: Restriction
  min cardinality: 0
  on property: URI

journalName
type: DatatypeProperty
range: string
type: FunctionalProperty
comment: The title of a periodical presenting articles on a particular subject.
domain: Journal

volume
type: FunctionalProperty
domain: Class
  union of: Journal
  union of: Proceeding
comment: A series of printed sheets bound typically in book form, a series of issues of a periodical.
range: string
type: DatatypeProperty

Thesis
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: institutionLocation
subclass of: Restriction
  min cardinality: 0
  on property: institutionLocation
comment: A dissertation containing results of original research on a particular topic, and especially substantiating a specific view; such as one written by a candidate for an academic degree.
subclass of: Restriction
  on property: hasInstitution
  max cardinality: 1
subclass of: Publication
subclass of: Restriction
  cardinality: 1
  on property: type
subclass of: Restriction
  min cardinality: 0
  on property: hasInstitution

hasInstitution
type: FunctionalProperty
range: Organization
type: ObjectProperty
domain: Class
  union of: TechnicalReport
  union of: Thesis
comment: Defines the relationship of "contains" -- A domain such as TechnicalReport or Thesis has listed the institution at 1) which the work was accomplished, and or 2) at which published the document. The institution is described within the project as an Organization.

type
type: FunctionalProperty
domain: Thesis
range: string
type: DatatypeProperty
comment: Qualities common to ... that distinguish them as an identifiable class.

AudioInternetAppliance
type: Class
subclass of: TelepresenceDevice
comment: An on-line audio appliance that facilitates listeners to communicate with on-line audio content providers. Users may hear streamed audio of an experiment.

WaveGenerator
type: Class
subclass of: SecondaryEquipment
comment: Waveform signal generator that can produce precision sine, square, triangle or other waveforms within a specified frequency range for laboratory applications.

DAQCable
type: Class
subclass of: Restriction
  on property: connectorType
  max cardinality: 1
subclass of: Restriction
  on property: connectorType
  min cardinality: 0
comment: The cable that connects a Sensor to a DAQ (Data Acquisition System) Channel.
subclass of: DAQDevice

connectorType
type: DatatypeProperty
comment: Type LAN connector card, e.g. wireless.
domain: DAQCable
type: FunctionalProperty
range: string

HydraulicActuator
type: Class
comment: System that uses liquid pressures in cylinders to apply forces or control deformations. This system may interface with electric power infrastructure and a control system.
subclass of: SecondaryEquipment

ComputationalResource
type: Class
comment: Resource for performing computational/numerical simulations.
subclass of: Apparatus

Apparatus
type: Class
subclass of: Restriction
  on property: shortDescription
  min cardinality: 0
subclass of: Restriction
  on property: longDescription
  min cardinality: 0
comment: Apparatus is defined as any equipment, sensors, specimen, software or other tools that may be used in Activities.
subclass of: Restriction
  on property: longDescription
  max cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: name
subclass of: Restriction
  on property: hasInfoFolders
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: shortDescription

URI
type: DatatypeProperty
type: FunctionalProperty
comment: Indicates the location or identifier of a file object.
domain: Class
  union of: Publication
  union of: File
  union of: CoordinateReferenceSystem
  union of: SoftwareProgram
  union of: SoftwareProgramCapability
range: anyURI

DataElement
type: Class
comment: This is the abstration of all types of data that may be generated or processed during an experiment.

publicationYear
type: FunctionalProperty
domain: Publication
comment: When a document was published; year, or may include month and day.
type: DatatypeProperty
range: gYear

authors
type: ObjectProperty
range: Person
comment: One that originates or creates, such as the writer of a literary work.

SensorSetup
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: hasSensorLocations
comment: The arrangement (location, direction, etc.) of Sensors used in an EventGroup.
subclass of: PhysicalSetup
subclass of: Restriction
  min cardinality: 0
  on property: hasSensors

hasSensorLocations
type: ObjectProperty
comment: Indicates the sensor and its associated location. The location is represented in a coordinate system, which can be either global or local.
range: ApparatusLocation
domain: SensorSetup

PhysicalSetup
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: setupDescriptions
subclass of: ApparatusSetup
comment: The physical setup of the PrimaryEquipment, including related infrastructure, specimen(s), and sensor(s).
subclass of: Restriction
  min cardinality: 0
  on property: setupFigures

hasSensors
type: ObjectProperty
comment: Defines the relationship of "contains" -- A SensorSetup multiple Sensors.
range: Sensor
domain: SensorSetup

Material
type: Class
subclass of: Apparatus
subclass of: Restriction
  on property: hasDescriptions
  min cardinality: 0
subclass of: Restriction
  on property: description
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasFiles

CentrifugeEquipment
type: Class
subclass of: PrimaryEquipment
comment: Centrifige equipment includes the structure upon which test specimen(s) are mounted and the subcomponents such as actuators, power, and control systems. The test specimen(s) can include soil within a soil container, mounted robotic systems and shake tables, soil markers, swinging platform, bucket, centrifuge drive system, and non-research related instrumentation systems. A Centrifuge system can apply centrifugal forces to a test Specimen for the purpose of increasing pressures and stresses in the test specimen.

SoftwareProgram
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: currentVersion
subclass of: Restriction
  on property: developers
  min cardinality: 0
subclass of: Restriction
  on property: URI
  max cardinality: 1
subclass of: Restriction
  on property: URI
  min cardinality: 0
subclass of: Restriction
  on property: currentVersion
  min cardinality: 0
subclass of: Software
subclass of: Restriction
  cardinality: 1
  on property: contactPerson
comment: Piece of Computer Code that can be executed.

currentVersion
type: ObjectProperty
domain: SoftwareProgram
range: VersionedSoftware
comment: Latest release of software
type: FunctionalProperty

developers
type: ObjectProperty
domain: SoftwareProgram
comment: Human who develops computer program source code, including the two main types of software - system software and application software or application programs.
range: Class
  union of: Person
  union of: Organization

contactPerson
type: ObjectProperty
range: Person
domain: SoftwareProgram
comment: Person to be contacted for information

RolePerson
type: Class
comment: A ComplexDataType defined to represent a particular role that a person plays in an Activity. Possible roles include principle investigator, co-investigator, research associate, postdoctoral assistant, graduate assistant, undergraduate student, technician, and etc.
subclass of: Restriction
  max cardinality: 1
  on property: isActive
subclass of: Restriction
  on property: isActive
  min cardinality: 0
subclass of: ComplexDataType
subclass of: Restriction
  on property: hasPerson
  cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: hasRole

isActive
type: DatatypeProperty
domain: RolePerson
range: boolean
type: FunctionalProperty
comment: Indicator as to whether Persons are active or inactive, relative to a specified project {Boolean}.

hasPerson
type: FunctionalProperty
domain: RolePerson
comment: Defines the relationship of "contains" -- A domain such as RolePerson has Persons identified in particular project roles, such as principle investigator, co-investigator, research associate, postdoctoral assistant, graduate assistant, undergraduate student, technician, and etc.
range: Person
type: ObjectProperty

hasRole
type: DatatypeProperty
comment: Defines the relationship of "contains" -- RolePerson has a role within a project, such as principle investigator, co-investigator, research associate, postdoctoral assistant, graduate assistant, undergraduate student, technician, and etc.
type: FunctionalProperty
domain: RolePerson
range: string

hasInfoFolders
type: ObjectProperty
range: Folder
comment: Defines the relationship of "contains" -- A domain such as Apparatus has one or more Folders.
domain: Apparatus

MultiSiteEventGroup
type: Class
comment: MultiSiteEventGroup is defined as a collection of EventGroups which are related and may be carried out at different Sites. It contains one or more MultiSiteEvents.
subclass of: Restriction
  min cardinality: 0
  on property: hasMultiSiteEvents
subclass of: MultiSiteActivity
subclass of: Restriction
  on property: hasEventGroups
  min cardinality: 0

hasMultiSiteEvents
type: ObjectProperty
comment: Defines the relationship of "contains" -- A MultiSiteEventGroup has MultiSiteEvents.
domain: MultiSiteEventGroup
range: MultiSiteEvent

DAQChannel
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: excitationVoltage
subclass of: Restriction
  on property: hasSensor
  min cardinality: 0
subclass of: Restriction
  on property: channelFilter
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: excitationVoltage
subclass of: Restriction
  on property: channelOffset
  max cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: hasSensor
subclass of: Restriction
  max cardinality: 1
  on property: samplingRate
subclass of: Restriction
  max cardinality: 1
  on property: channelUnit
subclass of: Restriction
  max cardinality: 1
  on property: channelGain
subclass of: DAQDevice
subclass of: Restriction
  min cardinality: 0
  on property: hasDAQCable
subclass of: Restriction
  on property: channelLocation
  min cardinality: 0
subclass of: Restriction
  on property: hasDAQCable
  max cardinality: 1
subclass of: Restriction
  on property: channelOffset
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: channelFilter
subclass of: Restriction
  on property: samplingRate
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: channelGain
comment: DAQ (Data Acquisition System) Channel collects signals from a connected Sensor, processes and transforms the signals, and transfers the signals to a DAQSystem for recording.
subclass of: Restriction
  min cardinality: 0
  on property: channelUnit
subclass of: Restriction
  max cardinality: 1
  on property: channelLocation

excitationVoltage
type: ObjectProperty
comment: The voltage measurement of the excitation current.
type: FunctionalProperty
domain: DAQChannel
range: FloatMeasurement

hasSensor
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as DAQChannel is connected to a Sensor.
domain: DAQChannel
range: Sensor
type: FunctionalProperty

channelFilter
type: DatatypeProperty
comment: A DAQ (Data Acquisition System) channel is a digital computing means that accepts as its input a set of one or more digital signals from which it generates as its output a second set of digital signals. May include the following information: filter type (e.g. Butterworth), corner frequency, filter order, etc.
domain: DAQChannel
type: FunctionalProperty
range: string

channelOffset
type: ObjectProperty
domain: DAQChannel
comment: The offset value (measurement) of the DAQChannel.
type: FunctionalProperty
range: FloatMeasurement

channelUnit
type: ObjectProperty
range: Unit
comment: A unit of measure of the DAQ (Data Acquisition) channel.
domain: DAQChannel
type: FunctionalProperty

channelGain
type: FunctionalProperty
range: double
domain: DAQChannel
type: DatatypeProperty
comment: The DAQ (Data Acquisition System) channel gain refers to an increase in signal power, voltage, or current by an amplifier, expressed as the ratio of output to input. Also called amplification.

hasDAQCable
type: ObjectProperty
range: DAQCable
comment: Defines the relationship of "contains" -- A domain such as DAQChannel has at least one DAQCable, which is the cable that connects a Sensor to a DAQ (Data Acquisition System) Channel.
domain: DAQChannel
type: FunctionalProperty

channelLocation
type: ObjectProperty
range: DAQSystem
domain: DAQChannel
type: FunctionalProperty
comment: Indicates which DAQ (Data Acquisition System) System the DAQChannel connects to.

SoilContainer
type: Class
subclass of: SecondaryEquipment
comment: Devices designed to contain soil models and soil specimens during an experiment performed on the contained soil.

startDateTime
type: FunctionalProperty
range: dateTime
domain: Activity
comment: The beginning time, which can be used together with endDateTime to calculate the duration. Time is internally saved as a long integer. It can also be used to identify which event happens first, i.e. to sort out the sequence of several Activities
type: DatatypeProperty

endDateTime
type: DatatypeProperty
type: FunctionalProperty
range: dateTime
domain: Activity
comment: The ending time, which can be used together with startDateTime to calculate the duration. Time is internally saved as a long integer. It can also be used to identify which event happens first, i.e. to sort out the sequence of several Activities.

localTimezone
type: DatatypeProperty
domain: Activity
range: string
comment: This will store the local timezone in effect at the time the activity started.

ApparatusLocation
type: Class
subclass of: ComplexDataType
comment: The ApparatusLocation represents the particular location of an Apparatus. It is especially used for indicating the location of sensors.
subclass of: Restriction
  on property: theLocation
  cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: hasApparatus

theLocation
type: ObjectProperty
range: Location
domain: ApparatusLocation
comment: The physical location where the Apparatus resides.

hasApparatus
type: ObjectProperty
domain: ApparatusLocation
range: Apparatus
comment: The Apparatus (e.g. Sensor) that needs a location value.

SensorGroup
type: Class
subclass of: Restriction
  on property: includeSensors
  min cardinality: 0
subclass of: ComplexDataType
comment: A SensorGroup can be of two types, sensor package and sensor array. A sensor package is composed of multiple sensors that operate together to provide a collective observation or related group of observations. For example, a collection of sensors can be used in a combined fashion to create a sensor that measures wave velocity and direction. A sensor array is a set of sensors of the same type at different locations. These locations may be within a single sensor frame, a different location on a single mount, or on different platforms. A sensor array produces observations that are used to build a spatial coverage.

includeSensors
type: ObjectProperty
comment: ...hasSensors?
range: Sensor
domain: SensorGroup

VideoServer
type: Class
comment: Server dedicated to handling streaming and/or local capturing and storage of video.
subclass of: TelepresenceDevice

File
type: Class
subclass of: Restriction
  cardinality: 1
  on property: URI
subclass of: Restriction
  on property: description
  max cardinality: 1
comment: This class represents an object that can be saved in memory, on disks, or in the repository. A file can be saved in any computer-readable format.
subclass of: Restriction
  on property: description
  min cardinality: 0
subclass of: DataElement
subclass of: Restriction
  on property: name
  cardinality: 1

Proceeding
type: Class
subclass of: Restriction
  on property: conferenceLocation
  max cardinality: 1
subclass of: Publication
subclass of: Restriction
  on property: publisher
  min cardinality: 0
subclass of: Restriction
  on property: publisher
  max cardinality: 1
comment: Name of a published record of the meeting of a society, association, or other organization.
subclass of: Restriction
  on property: conferenceName
  cardinality: 1
subclass of: Restriction
  max cardinality: 1
  on property: volume
subclass of: Restriction
  on property: volume
  min cardinality: 0
subclass of: Restriction
  on property: conferenceLocation
  min cardinality: 0

publisher
type: DatatypeProperty
comment: An entity that is engaged in publishing printed material.
domain: Class
  union of: Proceeding
  union of: Book
type: FunctionalProperty
range: string

ControlSystem
type: Class
subclass of: Restriction
  min cardinality: 0
  on property: subcomponent
subclass of: Restriction
  on property: controlledAxes
  min cardinality: 0
comment: Electronic or digital system used to control experiments in a NEES facility or to control other components of a NEES facility.
subclass of: SecondaryEquipment
subclass of: Restriction
  max cardinality: 1
  on property: controllerType
subclass of: Restriction
  on property: controlledAxes
  max cardinality: 1
subclass of: Restriction
  on property: controllerType
  min cardinality: 0

subcomponent
type: DatatypeProperty
domain: ControlSystem
comment: hardware/software that make up the entire component of an apparatus (THIS DOES NOT MAKE SENSE, WHAT IS A SUBCOMPONENT OF A CONTROLSYSTEM ANYWAY…?
type: FunctionalProperty
range: string

controlledAxes
type: DatatypeProperty
comment: The axis which a specific controller controls.
domain: ControlSystem
range: string

controllerType
type: FunctionalProperty
range: DataRange
  one of: Analog
  one of: Digital
  one of: Other
domain: ControlSystem
comment: Type of controler; Analog, digital or other.
type: DatatypeProperty

Unit
type: Class
subclass of: Restriction
  max cardinality: 1
  on property: description
subclass of: Restriction
  on property: conversion
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: description
subclass of: Restriction
  max cardinality: 1
  on property: relativeTo
subclass of: ComplexDataType
subclass of: Restriction
  on property: conversion
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: relativeTo
subclass of: Restriction
  cardinality: 1
  on property: name
comment: A precisely specified quantity in terms of which the magnitudes of other quantities of the same kind can be stated. A good way to model unit is yet to be determined.

conversion
type: FunctionalProperty
range: double
comment: Something that is changed from one use, function, or purpose to another. For instance, the expression of a quantity in alternative units, as of length or weight.
domain: Unit
type: DatatypeProperty

relativeTo
type: FunctionalProperty
type: ObjectProperty
comment: A way to describe a value, as relative a particular Unit.
range: Unit
domain: Unit

month
type: FunctionalProperty
comment: A measure of time corresponding nearly to the period of the moon's revolution and amounting to approximately 4 weeks or 30 days or 1/12 of a year
domain: Date
type: DatatypeProperty
range: int

year
type: DatatypeProperty
domain: Date
range: int
type: FunctionalProperty
comment: A period of approximately the duration of a calendar year.

day
type: DatatypeProperty
domain: Date
type: FunctionalProperty
comment: The 24-hour period during which the earth completes one rotation on its axis.
range: int

Structure
type: Class
comment: A constructed test article such as a model of a building, building frame, or bridge, etc. arranged in a definite pattern of organization.
subclass of: Specimen

Location
type: Class
comment: A place where some objects, equipments or sensors are located or positioned.
subclass of: ComplexDataType

hasFigures
type: ObjectProperty
domain: Class
  union of: SecondaryEquipment
  union of: Specimen
  union of: PrimaryEquipment
  union of: DAQSetup
comment: Defines the relationship of "contains" – PrimaryEquipment has one or more Figures, such as Photos and Drawings.

operators
type: ObjectProperty
domain: PrimaryEquipment
range: Person
comment: One who operates a machine or device.

manufacturer
type: FunctionalProperty
comment: Entity that manufactured the apparatus, software, etc.
range: string
type: DatatypeProperty
domain: Class
  union of: SecondaryEquipment
  union of: PrimaryEquipment
  union of: ComputationalResource

SpatialLocation
type: Class
subclass of: Location
comment: Location given in terms of coordinates that refer to a specific actual part of the structure. The coordinate system can be either global or local, depending on if the relativeToLocation is spcified.

ParameterSet
type: Class
comment: a set of parameters
subclass of: ComplexDataType
subclass of: Restriction
  on property: hasParameters
  min cardinality: 0

hasParameters
type: ObjectProperty
range: Parameter
comment: Defines the relationship of "contains" -- A domain such as ParameterSet has Parameters.
domain: ParameterSet

Book
type: Class
subclass of: Publication
subclass of: Restriction
  on property: edition
  cardinality: 1
subclass of: Restriction
  on property: publisher
  cardinality: 1
subclass of: Restriction
  on property: editors
  min cardinality: 0
comment: Name of a published, printed, work bound together into a volume.

edition
type: FunctionalProperty
domain: Book
comment: The entire number of like or identical items issued or produced as a set. The entire number of copies of a publication issued at one time or from a single set of type.
range: string
type: DatatypeProperty

editors
type: DatatypeProperty
comment: The entire number of like or identical items issued or produced as a set. The entire number of copies of a publication issued at one time or from a single set of type.
domain: Book
range: string

Project
type: Class
subclass of: Restriction
  on property: contractID
  min cardinality: 0
subclass of: Restriction
  on property: objectives
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: keyWords
subclass of: Restriction
  on property: contractID
  max cardinality: 1
subclass of: Restriction
  cardinality: 1
  on property: NEESCode
subclass of: Restriction
  min cardinality: 0
  on property: acknowledgements
subclass of: Restriction
  min cardinality: 0
  on property: hasSites
subclass of: Restriction
  on property: hasPublications
  min cardinality: 0
subclass of: Restriction
  on property: hasRolePersons
  min cardinality: 0
subclass of: Restriction
  on property: hasSponsors
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasTasks
subclass of: Activity
comment: Project is an organized group of tasks to achieve common goals and objectives. This is the highest abstraction of activities. A Project may include several related Tasks sponsored by one or more funding sources.
subclass of: Restriction
  min cardinality: 0
  on property: executedBy
subclass of: Restriction
  min cardinality: 0
  on property: hasMultiSiteTasks

contractID
type: DatatypeProperty
comment: NSF or other identification number for a NEES project contract.
domain: Project
type: FunctionalProperty
range: string

objectives
type: DatatypeProperty
range: string
domain: Project
comment: The objectives and constraints of a project.

acknowledgements
type: DatatypeProperty
domain: Project
comment: Acknowledgements represent financial support, contributions of special instrumentations, or other types of sponsorship associated with a Activity. Several acknowledgements can be added for one Activity. Acknowledgement is modeled as String right now, can be changed to object if necessary.
range: string

hasSponsors
type: ObjectProperty
domain: Project
comment: Defines the relationship of "contains" -- A Project has sponsors identified as Organizations described within the project metadata.
range: Organization

hasTasks
type: ObjectProperty
comment: Defines the relationship of "contains" -- Domains such as Project and MultiSiteTask has Tasks associatied with Acitivites.
domain: Class
  union of: Project
  union of: MultiSiteTask
range: Task

executedBy
type: ObjectProperty
range: Organization
domain: Project
comment: A list of organization(s) that execute the Activity.

hasMultiSiteTasks
type: ObjectProperty
range: MultiSiteTask
domain: Project
comment: Defines the relationship of "contains" -- A Project has MultiSiteTasks.

Parameter
type: Class
subclass of: DataElement
comment: A parameter has a name and an associated value.
subclass of: Restriction
  cardinality: 1
  on property: parameterName
subclass of: Restriction
  on property: parameterValue
  cardinality: 1

parameterName
type: DatatypeProperty
comment: The name of the parameter.
domain: Parameter
range: string
type: FunctionalProperty

parameterValue
type: DatatypeProperty
domain: Parameter
range: string
comment: Value, range of values associated with a parameter.
type: FunctionalProperty

SoftwareSetup
type: Class
subclass of: Restriction
  on property: hasSoftwareProgram
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasDescriptions
subclass of: ApparatusSetup
comment: The setup of software, including installation, development and deployment, for a specified Activity.

hasSoftwareProgram
type: ObjectProperty
range: SoftwareProgram
domain: Class
  union of: SoftwareSetup
  union of: VersionedSoftware
comment: Defines the relationship of "contains" -- A domain such as SoftwareSetup or VersionedSoftware have an associated SoftwareProgram(s).

TechnicalReport
type: Class
subclass of: Restriction
  on property: institutionLocation
  max cardinality: 1
subclass of: Restriction
  on property: URI
  cardinality: 1
subclass of: Restriction
  on property: hasInstitution
  max cardinality: 1
comment: Usually a detailed, technical account of a NEESgrid Project, such as SiteInformation, Activities, Apparatus, DataElements, etc., or research related to NEESgrid Projects; or a formal record of the proceedings of a meeting.
subclass of: Restriction
  on property: institutionLocation
  min cardinality: 0
subclass of: Publication
subclass of: Restriction
  on property: hasInstitution
  min cardinality: 0

owner
type: ObjectProperty
domain: SecondaryEquipment
range: Organization
comment: The organization that the SecondaryEquipement belongs to.
type: FunctionalProperty

manufacturersPartNumber
type: FunctionalProperty
domain: SecondaryEquipment
range: string
type: DatatypeProperty
comment: Part number that identifies apparatus, software, etc.; this name is unique to the manufacturer

manufactuersModelNumber
type: FunctionalProperty
comment: Model number that identifies appratus, software, etc.; this name is unique to the manufacturer
range: string
domain: SecondaryEquipment
type: DatatypeProperty

serialNumber
type: DatatypeProperty
domain: SecondaryEquipment
comment: Part (serial) number of the Sensor, usually given by the manufacturer.
type: FunctionalProperty
range: string

CoordinateReferenceSystem
type: Class
comment: Detailed information on coordinate reference system(s) used in conducting test(s) at NEESgrid facility.
subclass of: SpatialLocation

H.323Device
type: Class
subclass of: TelepresenceDevice
comment: A device that is based on VoIP (Voice Over IP) protocol H.323, e.g. a VTC device.

setupDescriptions
type: ObjectProperty
comment: The test descriptions or notes that describe the setup.
domain: PhysicalSetup

setupFigures
type: ObjectProperty
domain: PhysicalSetup
comment: The figures and drawings that illustrate the setup. Locations to these image files need to be provided.

InputFileParameterSet
type: Class
subclass of: ComplexDataType
subclass of: Restriction
  on property: hasParameterSets
  min cardinality: 0
comment: A set of parameters that define the InputFile
subclass of: Restriction
  on property: hasInputFile
  cardinality: 1

hasParameterSets
type: ObjectProperty
domain: InputFileParameterSet
comment: Defines the relationship of "contains" -- A domain such as InputFileParemeterSet has ParameterSets, which contain Parameters.
range: ParameterSet

hasInputFile
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as an InputFileParameterSet has one or more InputFiles.
domain: InputFileParameterSet
type: FunctionalProperty

MultiSiteTask
type: Class
subclass of: Restriction
  on property: hasMultiSiteEventGroups
  min cardinality: 0
comment: MultiSiteTask is defined as a collection of Tasks which are related and may be carried out at different Sites. It contains one or more MultiSiteEventGroups.
subclass of: MultiSiteActivity
subclass of: Restriction
  on property: hasTasks
  min cardinality: 0

hasMultiSiteEventGroups
type: ObjectProperty
domain: MultiSiteTask
range: MultiSiteEventGroup
comment: Defines the relationship of "contains" -- A MultiSiteTask has MultiSiteEventGroups.

MultiSiteEvent
type: Class
comment: MultiSiteEvent is defined as a collection of Events which are related and may be carried out at different Sites. The Event can be an experiment or a simulation.
subclass of: Restriction
  on property: hasEvents
  min cardinality: 0
subclass of: MultiSiteActivity

Sensor
type: Class
comment: Sensor represents a device for the measurement of physical quantities. Key components of a sensor modeling include sensor identification, sensor location, constraints, platform attached by the sensor, coordinate reference system, sensor description, and measurement characteristics.
subclass of: Restriction
  max cardinality: 1
  on property: outputQuantity
subclass of: Restriction
  on property: sensorType
  min cardinality: 0
subclass of: Restriction
  on property: addtionalSpecifications
  min cardinality: 0
subclass of: Restriction
  on property: minRange
  max cardinality: 1
subclass of: Restriction
  on property: calibrationInfo
  max cardinality: 1
subclass of: Restriction
  min cardinality: 0
  on property: lastCalibrationDate
subclass of: Restriction
  on property: outputQuantity
  min cardinality: 0
subclass of: Restriction
  max cardinality: 1
  on property: sensorType
subclass of: Restriction
  max cardinality: 1
  on property: lastCalibrationDate
subclass of: SecondaryEquipment
subclass of: Restriction
  min cardinality: 0
  on property: maxRange
subclass of: Restriction
  on property: minRange
  min cardinality: 0
subclass of: Restriction
  on property: calibrationInfo
  min cardinality: 0
subclass of: Restriction
  on property: maxRange
  max cardinality: 1

outputQuantity
type: DatatypeProperty
domain: Sensor
range: string
comment: Quantity that sensor puts out in response to the input, it can be voltage, current, charge, or human read.
type: FunctionalProperty

sensorType
type: FunctionalProperty
comment: Information sensed by the Sensor, e.g. acceleration, pressure, displacement, strain, temperature, and etc.
range: string
domain: Sensor
type: DatatypeProperty

addtionalSpecifications
type: DatatypeProperty
comment: Any additional information about the Sensor, e.g. dimension, weight, etc.
range: string
domain: Sensor

minRange
type: FunctionalProperty
comment: The minimum measurable quantity.
type: ObjectProperty
range: FloatMeasurement
domain: Sensor

calibrationInfo
type: ObjectProperty
range: File
domain: Sensor
comment: A file that contains calibration information, expressed as formula, table, and etc.
type: FunctionalProperty

lastCalibrationDate
type: ObjectProperty
range: DateTime
type: FunctionalProperty
comment: The date of last calibration.
domain: Sensor

maxRange
type: FunctionalProperty
domain: Sensor
range: FloatMeasurement
type: ObjectProperty
comment: The maximum measurable quantity.

InfrastructureSetup
type: Class
subclass of: Restriction
  on property: hasPrimaryEquipments
  min cardinality: 0
comment: The assembly and arrangement of the PrimaryEquipment used for a specific Task. General laboratory infrastructure is described under TertiaryEquipment.
subclass of: PhysicalSetup
subclass of: Restriction
  on property: hasSecondaryEquipments
  min cardinality: 0

DAQSetup
type: Class
comment: The setup of one or more electronic devices whose primary purpose is to acquire data. It can be simple or complex, depending upon the needs. Typically a data acquisition system involves at least three main components. First, sensors respond to a physical stimulus and transmit signals or change electrical property such as resistance. Second, a datalogger measures the electrical signal, converts it to a number and stores either that value or some statistics on that value (average, maximum, minimum, standard deviation, etc.). Third, a PC uses some communications link (serial port, phone modem, radio modem, etc.) to retrieve the data from the datalogger.
subclass of: Restriction
  on property: hasDAQChannels
  min cardinality: 0
subclass of: Restriction
  on property: hasFigures
  min cardinality: 0
subclass of: Restriction
  on property: hasSetupFiles
  min cardinality: 0
subclass of: ApparatusSetup

hasDAQChannels
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as DAQSetup has at least one DAQChannel, collects signals from a connected Sensor, processes and transforms the signals, and transfers the signals to a DAQSystem for recording.
range: DAQChannel
domain: DAQSetup

hasSetupFiles
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as DAQSetup has one or more NumericalFiles.
domain: DAQSetup

DAQSystem
type: Class
subclass of: DAQDevice
comment: DAQ (Data Acquisition System) System reads the experiment event data from the detector, formats them, monitors them, and stores them for offline analysis.

Camera
type: Class
subclass of: TelepresenceDevice
comment: A video or still camera that captures visual information. This class also includes telerobotic cameras.

SpecimenSetup
type: Class
subclass of: Restriction
  on property: hasPrimaryEquipments
  min cardinality: 0
subclass of: Restriction
  min cardinality: 0
  on property: hasSpecimens
subclass of: PhysicalSetup
comment: The setup of specimen is modeled by this class. It is focused on how the specimen is set up with respect to PrimaryEquipment.

hasSpecimens
type: ObjectProperty
comment: Defines the relationship of "contains" -- A SpecimenSetup has one or more Specimens.
domain: SpecimenSetup
range: Specimen

hasDataTurbineChannels
type: ObjectProperty
range: DataTurbineChannel
comment: Defines the relationship of "contains" -- A domain such as ...

hasHydraulicPower
type: ObjectProperty
domain: HydraulicActuator
comment: Defines the relationship of "contains" -- A domain such as HydraulicActuator has Haydraulic Power.

accumulatorOilVolume
type: ObjectProperty
comment: Accumulator oil volume (liters), a standard specification for hydraulic power infrastructure.
range: FloatMeasurement
type: FunctionalProperty

nextVersion
type: ObjectProperty
range: VersionedSoftware
domain: VersionedSoftware
comment: The next version release of the software

specificGravity
type: ObjectProperty
type: FunctionalProperty
domain: SoilDeposit
comment: Ratio of density of soil grains to the density of water (see ASTM ####). The desnity of slids is defined as the ratio of the mass of solids to the volume of solids. The density of water is equal to 1 g/cm cubed and 62.4 pcf.
range: FloatMeasurement

resourceCost
type: ObjectProperty
range: FloatMeasurement
comment: Cost of performing work on resource $/hour
domain: ComputationalResource

torqueCapacity
type: ObjectProperty
range: FloatMeasurement
domain: HydraulicActuator
comment: A standard specification for a hydraulic actuator system.
type: FunctionalProperty

unitWeight
type: ObjectProperty
type: FunctionalProperty
comment: The soil weight per unit volume. Also termed density or mass density and reported total or wet density, dry density, and bouyant density.
range: FloatMeasurement
domain: SoilDeposit

coordZ
type: ObjectProperty
comment: The Z location given in terms of coordinates that refer to a specific actual part of the structure, such as a sensor.
domain: SpatialLocation
type: FunctionalProperty
range: FloatMeasurement

undrainedShearStrength
type: ObjectProperty
domain: SoilDeposit
type: FunctionalProperty
range: FloatMeasurement
comment: The unconsolidated undrained shear strength test is used to obtain the undrained shear strength of the soil; typical types of laboratory tests are the laboratory vane test and the unconfined compression test. Consolidated undrained shear strength test is used to obtain the failure envelope in terms of total stresses, i.e. total cohesion, and total friction angle; the triaxial apparatus is used to perform this test.

RAMSpace
type: ObjectProperty
comment: Size of available RAM in MBytes.
domain: ComputationalResource
type: FunctionalProperty
range: FloatMeasurement

diskSpace
type: ObjectProperty
domain: ComputationalResource
comment: Size of available disks for the temporary storage of data in MBytes.
range: FloatMeasurement

hasDisplayChannel
type: ObjectProperty
range: DisplayChannel
comment: Defines the relationship of "contains" -- A domain such as ...

azimuthUOM
type: ObjectProperty
type: FunctionalProperty
domain: CoordinateReferenceSystem
comment: The unit of measure of the horizontal direction expressed as the angular distance between the direction of a fixed point (as the observer's heading) and the direction of the object.
range: Unit

relativeToLocation
type: ObjectProperty
domain: SpatialLocation
comment: A text description of the location of an object in relation to a test apparatus, relative to some fixed or known point (or other object included in the Apparatus).
range: Location
type: FunctionalProperty

has
type: ObjectProperty
comment: Defines the relationship of "contains" - an object "contains" >1 of a specified property (hasProperties). "Containment" is used in lieu of multiple inheritance.

fluidType
type: ObjectProperty
domain: HydraulicActuator
type: FunctionalProperty
comment: Type of liquid used in a HydraulicActuator system. The system uses liquid pressures in cylinders to apply forces or control deformations.
range: FloatMeasurement

coordUom
type: ObjectProperty
range: Unit
comment: The unit of measurement for the defined coordinate system.
domain: SpatialLocation

coefficientOfUniformity
type: ObjectProperty
range: FloatMeasurement
domain: SoilDeposit
type: FunctionalProperty
comment: A coefficient used in the Unified Soil Classification System to determine whether a course-grained soil is well graded (many different particle sizes) or poorly graded ( many particles of about the same size).

creators
type: ObjectProperty
range: Person
comment: person who created the data file

hasComputationalResource
type: ObjectProperty
range: ComputationalResource
comment: Defines the relationship of "contains" -- A domain such as Activity-SingleSiteActivity-SimulationEvent utilizes Apparatus-Computational Resources.
type: FunctionalProperty
domain: ComputationalResource

latitude
type: ObjectProperty
range: FloatMeasurement
domain: SpatialLocation
comment: The latitude of the location reference point, given in the Geodetic Datum CRS.
type: FunctionalProperty

stroke
type: ObjectProperty
comment: Stroke (peak to peak travel), a standard specification for a hydraulic actuator system or peak-to-peak travel of a shake table platform.
type: FunctionalProperty
domain: HydraulicActuator
range: FloatMeasurement

requiredData
type: ObjectProperty
range: DataElement
comment: Data that is required to run the input file, e.g. ground motions, other sourced files.

maximumDryUnitWeight
type: ObjectProperty
range: FloatMeasurement
comment: Maximum value of the mass per unit volume dry material in a given sample.
domain: SoilDeposit
type: FunctionalProperty

maximumVelocity
type: ObjectProperty
domain: HydraulicActuator
type: FunctionalProperty
range: FloatMeasurement
comment: Maximum velocity that a Hydraulic actuator can safely.

compressionForceCapacity
type: ObjectProperty
domain: HydraulicActuator
comment: Compression force capacity, a standard specification for a hydraulic actuator system.
range: FloatMeasurement
type: FunctionalProperty

meanGrainSize
type: ObjectProperty
comment: The mean grain size of the material in the layer. This can be represented as a quantity of grain diameter (usually mm or phi), or as a text descriptor. If a text descriptor, a definition or reference to a classification system should be defined.
domain: SoilDeposit
range: FloatMeasurement
type: FunctionalProperty

LL
type: DatatypeProperty
type: FunctionalProperty
comment: The water contentof a soil at the arbitrary boundary between the semi-liquid and plastic states, generally expressed in percent. Can be given as a range of values.
range: string
domain: SoilDeposit

networkOperatingSystem
type: DatatypeProperty
comment: An operating system which includes software to communicate with other computers via a network. This allows resources such as files, application programs, and printers to be shared between computers.
range: string

eventType
type: DatatypeProperty
type: FunctionalProperty
domain: Event
comment: There are three types of Event (Experiment, Processed, and Simulation)
range: string

soilMaterialSource
type: DatatypeProperty
comment: The source of the soil, i.e. physical location it was taken from, name of geologic formation to which it belongs, and any other pertinent source identifier.
type: FunctionalProperty
domain: SoilDeposit
range: string

mapProjection
type: DatatypeProperty
domain: SpatialLocation
comment: The map projection used to give the X and Y locations of the location reference point.
type: FunctionalProperty
range: string

materialModels
type: DatatypeProperty
comment: Comma seperated list of material models and dimensionality, e.g. 3d-J2, 1d-concrete, 1d-elastic.
domain: SoftwareProgramCapability
range: string
type: FunctionalProperty

siteOrigin
type: DatatypeProperty
domain: CoordinateReferenceSystem
comment: A foreign key to the Project for which this CRS is a local, engineering CRS. This value indicates that the Project has defined a Location Reference Point, which is to be used as the origin for this CRS.
type: FunctionalProperty
range: string

degreeType
type: DatatypeProperty
comment: The hemisphere (N, E, S, W) is attached to the degrees as an attribute. Note: the values of '+' for N and E, and '-' for S and W are also permitted.
range: string

outletLocations
type: DatatypeProperty
type: FunctionalProperty
comment: Locations of receptacles, especially mounted in walls, that are connected to a power supply and equipped with a socket for a plug.
range: string

locationMethod
type: DatatypeProperty
type: FunctionalProperty
domain: SpatialLocation
comment: A description of the method by which the location reference point coordinates were obtained.
range: DataRange
  one of: LORAN
  one of: Added_to_CAD_Diagram_from_description
  one of: Unknown_from_owner/operator
  one of: Digitized_from_existing_CAD_Diagram
  one of: Estimated_from_photgraphs
  one of: DGPS
  one of: GPS
  one of: Unknown_from_3rd_party

markerType
type: DatatypeProperty
range: string
comment: Short text description of marker used in experiment.
type: FunctionalProperty

wiringMedia
type: DatatypeProperty
range: string
comment: The type of objects comprising a system of electric wires.

powerRequirments
type: DatatypeProperty
type: FunctionalProperty
range: string
comment: The energy or motive force required by a physical system or machine in order to operate.

piston
type: DatatypeProperty
comment: A solid cylinder or disk that fits snugly into a larger cylinder and moves under fluid pressure, as in a reciprocating engine, or displaces or compresses fluids, as in pumps and compressors.
range: string
domain: HydraulicActuator
type: FunctionalProperty

numProcessors
type: DatatypeProperty
comment: The number of processors available.
range: int
domain: ComputationalResource

cylinder
type: DatatypeProperty
range: string
type: FunctionalProperty
domain: HydraulicActuator
comment: The chamber in which a piston of a reciprocating engine moves; the chamber of a pump from which fluid is expelled by a piston.

geodeticDatum
type: DatatypeProperty
comment: The geographic coordinate reference system used to give the latitude and longitude of the location reference point.
range: string
domain: SpatialLocation
type: FunctionalProperty

hardware
type: DatatypeProperty
comment: A computer and the associated physical equipment directly involved in the performance of data-processing or communications functions.
range: string

CRStype
type: DatatypeProperty
range: DataRange
  one of: Geographic
  one of: Projected
  one of: Vertical
  one of: Engineering
comment: The type of CRS. Values are
domain: CoordinateReferenceSystem
comment: The type of CRS. Allowed values are
type: FunctionalProperty

shape
type: DatatypeProperty
type: FunctionalProperty
domain: SoilContainer
comment: The shape of a SoilContainer used in centrifuge testing; rectangular, circular in plan, etc.
range: string

hydraulicPump
type: DatatypeProperty
range: boolean
type: FunctionalProperty
comment: A water pump that uses the kinetic energy of flowing water to force a small fraction of that water to a reservoir at a higher level.

yAxisDescription
type: DatatypeProperty
domain: CoordinateReferenceSystem
range: string
type: FunctionalProperty
comment: A description of the Y-axis. If the Y Axis Azimuth is not given, then a textual description of the direction of the Y-axis should be given.

releaseDate
type: DatatypeProperty
comment: Date a specified versionof a specified software was released.
domain: VersionedSoftware
range: dateTime

interfaces
type: DatatypeProperty
domain: HydraulicActuator
range: string
comment: The layout of an application's graphic or textual controls in conjunction with the way the application responds to user activity.

powerType
type: DatatypeProperty
range: string
comment: Type of electircal power, such as AC versus battery.
type: FunctionalProperty

connector
type: DatatypeProperty
range: string
comment: LAN connector card specifications.

servoValve
type: DatatypeProperty
type: FunctionalProperty
comment: Valve that controls flow of fluid to the actuator; only applicable to servo-hydraulic actuators.
range: string
domain: HydraulicActuator

locationAccuracy
type: DatatypeProperty
domain: SpatialLocation
range: string
type: FunctionalProperty
comment: An estimate of the accuracy of the location reference point. As this may be subjective, the description may be quantitative or qualitative.

hasInputFileParameterSet
type: TransitiveProperty
type: ObjectProperty
range: InputFileParameterSet
comment: Defines the relationship of "contains" -- A domain such as SimulationEvent has one or more InputFIleParameterSets.

emax
type: FunctionalProperty
range: FloatMeasurement
type: ObjectProperty
domain: SoilDeposit
comment: void ratio corresponding to a standard loose condition (see ASTM ####)

lineElementTypes
type: FunctionalProperty
type: DatatypeProperty
domain: SoftwareProgramCapability
comment: Comma seperated list of line elements and dimesnionality, e.g 1d-truss, 2d-beam-column, etc.
range: string

geometricModeling
type: FunctionalProperty
domain: SoftwareProgramCapability
comment: Comma seperated list of geometric modelling capablities, e.g linear, p-dealta, large displacement small strain, large displacement large strain.
range: string
type: DatatypeProperty

versionNumber
type: FunctionalProperty
domain: VersionedSoftware
comment: A code which allows revisions of an object to be ordered by the times the revisions were made.
range: string
type: DatatypeProperty

hasData
type: FunctionalProperty
comment: Defines the relationship of "contains" -- A domain such as File-DataFile has at least one Data FIle which can be a NumericalFIle, each containing a link to the data and a link to a description of what the data is.
type: ObjectProperty

coordX
type: FunctionalProperty
range: FloatMeasurement
type: ObjectProperty
domain: SpatialLocation
comment: The X location given in terms of coordinates that refer to a specific actual part of the structure, such as a sensor.

minimumFrequency
type: FunctionalProperty
domain: ShakingSystem
range: long
type: DatatypeProperty
comment: Minimum frequency that can be simulated/generated by the shaking system (there is +/- error associated with this, need to revisit for the next version)

locationX
type: FunctionalProperty
range: FloatMeasurement
comment: The first coordinate for the location of the location reference point. In the US, this would be the Easting.
type: ObjectProperty
domain: SpatialLocation

minimumDryUnitWeight
type: FunctionalProperty
type: ObjectProperty
range: FloatMeasurement
domain: SoilDeposit
comment: Minimum value of the mass per unit volume dry material in a given sample.

relativeDensity
type: FunctionalProperty
domain: SoilDeposit
range: FloatMeasurement
comment: Term applied to a sand deposit to indicate it's relative density state, defined as the ratio of 1) the difference between the void ratio in the loosest state and the in situ void ratio to 2) the difference between the void ratios in the loosest and in the densest states.
type: ObjectProperty

localXYUom
type: FunctionalProperty
domain: SpatialLocation
range: string
comment: The Unit of Measure of the Local x,y coordiantes.
type: DatatypeProperty

calibrationDate
type: FunctionalProperty
range: dateTime
comment: Date that an instrument, equipment, etc. calibrated. (need to metion/add a calibration standard???)
type: DatatypeProperty

waterContent
type: FunctionalProperty
type: ObjectProperty
domain: SoilDeposit
comment: The water content of a soil in it's natural in situ moisture condition, generally expressed in percent. The water content is the ratio of the mass of water contained in the pore spaces of soil or rock material, to the solid mass of particles in that material, generally expressed in percent.
range: FloatMeasurement

peakToPeakDisplacement
type: FunctionalProperty
type: DatatypeProperty
range: long
domain: ShakingSystem
comment: Same as stroke.

measurement
type: FunctionalProperty
type: DatatypeProperty
range: string
comment: [Duplicated as an object under ComplexDataType...?] The dimensions, capacity, or amount of something ascertained by measuring; a measured quantity.
domain: SensorGroup

peakForceCapacity
type: FunctionalProperty
domain: ShakingSystem
range: long
type: DatatypeProperty
comment: Maximum absolute force that an appratus can exert on test article(s)

soilType
type: FunctionalProperty
comment: The name that identifies different mixture of soil particles, liquids and gasses
type: DatatypeProperty
domain: SoilDeposit
range: string

continumElementTypes
type: FunctionalProperty
comment: Comma seperated list of continuum element types and dimensionality, e.g. 2d-quad, 3d-brick.
type: DatatypeProperty
range: string
domain: SoftwareProgramCapability

pumpPressure
type: FunctionalProperty
comment: Pump Pressure (kN/m2), a standard specification for hydraulic power infrastructure.
range: FloatMeasurement
type: ObjectProperty

changeVibrationOrientation
type: FunctionalProperty
domain: ShakingSystem
comment: If system can shake in both horizontal and vertical directions, approximate time required to change vibration orientation choose one (less than 1 hr, less than one day, more than one day)
range: DataRange
  one of: lessThan1hr
  one of: lessThan1day
  one of: moreThan1Day
type: DatatypeProperty

hasVersionedSoftware
type: FunctionalProperty
type: ObjectProperty
range: VersionedSoftware
comment: Version of the software program

origin
type: FunctionalProperty
range: string
comment: A description of a point which serves as the origin of the CRS. This is an alternative to the Project Origin, which uses a Location Reference Point as the origin.
type: DatatypeProperty
domain: CoordinateReferenceSystem

voltage
type: FunctionalProperty
comment: Electric potential or potential difference expressed in volts.
type: DatatypeProperty
range: string

localX
type: FunctionalProperty
comment: The X location (first coordinate value) in the local CRS.
range: FloatMeasurement
type: ObjectProperty
domain: SpatialLocation

localY
type: FunctionalProperty
type: TransitiveProperty
range: FloatMeasurement
comment: The Y location (second coordinate value) in the local CRS.
type: ObjectProperty
domain: SpatialLocation

dimensionality
type: FunctionalProperty
range: string
domain: SoftwareProgramCapability
type: DatatypeProperty
comment: comma seperated list of dimensionality, e.g 2d, 3d

parallelCapability
type: FunctionalProperty
comment: yes or no...
range: string
domain: SoftwareProgramCapability
type: DatatypeProperty

xAxisAzimuth
type: FunctionalProperty
type: ObjectProperty
domain: CoordinateReferenceSystem
comment: The rotation from the north direction of the X-axis. The rotation is positive clockwise. If the x-axis is due east, the value would be 90 deg.
range: FloatMeasurement

hasControlSystem
type: FunctionalProperty
domain: HydraulicActuator
type: ObjectProperty
comment: Defines the relationship of "contains" -- A domain such as Apparatus-SecondaryEquipment has a ControlSystem, which is an electronic or digital system used to control experiments in a NEES facility or to control other components of a NEES facility.
range: ControlSystem

tensionForceCapacity
type: FunctionalProperty
range: FloatMeasurement
comment: Tension force capacity, a standard specification for a hydraulic actuator system.
type: ObjectProperty
domain: HydraulicActuator

northDirection
type: FunctionalProperty
comment: The direction that is assumed to be north in the engineering CRS.
type: DatatypeProperty
domain: CoordinateReferenceSystem
range: DataRange
  one of: TrueNorth
  one of: magneticNorth
  one of: Grid
  one of: Unknown
  one of: TrueCalculated

mountedOnShakerTruck
type: FunctionalProperty
range: boolean
type: DatatypeProperty
comment: {Boolean} Indicator of whether a FieldShaker associated with a specified Field test/Event is mounted on a truck.

locationReferencePoint
type: FunctionalProperty
type: DatatypeProperty
range: string
domain: SpatialLocation
comment: A description of a point at the Equipment Site which represents a local point of reference for all other locations determined at the Equipment Site. The location given in other attributes will be the location of this point. In general, a local CRS (coordinate reference system) for locating other objects at the Equipment Site will use this as the origin.

dataDescription
type: FunctionalProperty
comment: File that gives meaning to the data file
type: ObjectProperty

preconsolidationPressure
type: FunctionalProperty
comment: Equal to the highest previous vertical stress that a cohesive soil was subjected to and consolidated under (kPa or psf). Also referred to as maximum past pressure.
range: FloatMeasurement
domain: SoilDeposit
type: ObjectProperty

dimensions
type: FunctionalProperty
comment: A physical property, such as mass, length, time, or a combination thereof, regarded as a fundamental measure or as one of a set of fundamental measures of a physical quantity.
range: string
domain: HydraulicActuator
type: DatatypeProperty

accumualatorGaVolume
type: FunctionalProperty
range: FloatMeasurement
comment: Accumulator gas volume (liters), a standard specification for hydraulic power infrastructure.
type: ObjectProperty

CRScode
type: FunctionalProperty
comment: The standard code for a well-known CRS, defined and maintained, such as EPSG by the European Petroleum Survey Group.
range: string
domain: CoordinateReferenceSystem
type: DatatypeProperty

emin
type: FunctionalProperty
comment: void ratio corresponding to a standard dense condition (see ASTM ####)
domain: SoilDeposit
range: FloatMeasurement
type: ObjectProperty

pumpFlowCapacity
type: FunctionalProperty
comment: Pump Flow capacity (liters per minute), a standard specification for hydraulic power infrastructure.
range: FloatMeasurement
type: ObjectProperty

coordY
type: FunctionalProperty
comment: The Y location given in terms of coordinates that refer to a specific actual part of the structure, such as a sensor.
range: FloatMeasurement
type: ObjectProperty
domain: SpatialLocation

yAxisRotation
type: FunctionalProperty
domain: CoordinateReferenceSystem
type: DatatypeProperty
comment: The Y axis is assumed to be rotated 90 deg from the X axis. The rotation may either be {clockwise, counter clockwise}. The usual value is counter clockwise
range: DataRange
  one of: Clockwise
  one of: Counter-clockwise

longitude
type: FunctionalProperty
comment: The longitude of the location reference point, given in the Geodetic Datum CRS.
domain: SpatialLocation
range: FloatMeasurement
type: ObjectProperty

localCRS
type: FunctionalProperty
type: DatatypeProperty
domain: SpatialLocation
comment: Description of the local coordinate system which applies to local x,y coordinates. This is expected to be a foreign key to an instance, however there is no requirement that the instance exist.
range: string

PL
type: FunctionalProperty
comment: The water content of a soil at the arbitrary boundary between the plastic and semi-solid states, generally expressed in percent. Can be given as a range of values.
range: string
type: DatatypeProperty
domain: SoilDeposit

saturatedUnitWeight
type: FunctionalProperty
type: ObjectProperty
comment: Mass per unit volume material in a saturated sample.
range: FloatMeasurement
domain: SoilDeposit

maximumFrequency
type: FunctionalProperty
domain: ShakingSystem
type: DatatypeProperty
comment: Maximum frequency that can be simulated/generated by the shaking system (there is +/- error associated with this, need to revisit for the next version).
range: long

PLSS
type: FunctionalProperty
range: string
domain: SpatialLocation
type: DatatypeProperty
comment: The Public Land Survey System township, range, section, and quarter-quarter section where the site is located. This is most useful for Field Test Sites.

hasSoftwareCapabilities
type: FunctionalProperty
domain: VersionedSoftware
comment: Description of software capability.
range: SoftwareProgramCapability
type: ObjectProperty

permeability
type: FunctionalProperty
range: FloatMeasurement
domain: SoilDeposit
type: ObjectProperty
comment: A measure of the ability of soil, sediments, and rock to transport water horizontally and vertically. Permeability is dependent on the porosity of the medium the water is flowing through. Some rocks like granite have very poor permeability, while rocks like shale are actually quite pervious. As for soils, sand is the most pervious, while clay has the lowest permeability. Silt usually is somewhere in the middle.

solvers
type: FunctionalProperty
domain: SoftwareProgramCapability
range: string
comment: List of solver types, such as...?
type: DatatypeProperty

hasLocation
type: FunctionalProperty
comment: Defines the relationship of "contains" -- A domain such as Camera has a specified Location.
range: string
type: DatatypeProperty
domain: Camera

hasInputFiles
type: FunctionalProperty
comment: Defines the relationship of "contains" -- A domain such as SimulationEvent has InputFiles, which can be included in one of more Folders.
range: Folder
type: ObjectProperty

processorSpeed
type: FunctionalProperty
comment: Speed of available processors in MFlops.
range: FloatMeasurement
type: ObjectProperty
domain: ComputationalResource

saturationMethod
type: FunctionalProperty
domain: SoilDeposit
range: string
comment: Saturation is defined as the ratio of the volume of water in the void space to the total volume of voids. Usually espresses as a percentage. Method of saturation refers to how the sample became saturated, i.e. the sample was collected below the ground water table, or submergence in the laboratory.
type: DatatypeProperty

solutionMethods
type: FunctionalProperty
domain: SoftwareProgramCapability
range: string
type: DatatypeProperty
comment: List of solution types, e.g. static, dynamic, eigenvalue.

shakerType
type: FunctionalProperty
comment: Type of shaking system.
type: DatatypeProperty
range: string
domain: ShakingSystem

current
type: FunctionalProperty
comment: The amount of electric charge flowing past a specified circuit point per unit time.
type: DatatypeProperty
range: string

locationY
type: FunctionalProperty
range: FloatMeasurement
comment: The second coordinate for the location of the location reference point. In the US, this would be the Northing.
type: ObjectProperty
domain: SpatialLocation

signConvention
type: FunctionalProperty
type: DatatypeProperty
comment: Convention for describing sensor setup, and alighnment (directions).
range: string
domain: SensorGroup

watts
type: FunctionalProperty
range: string
comment: An International System unit of power equal to one joule per second.
type: DatatypeProperty

NEESMeta Instance 50009
type: TechnicalReport
authors: neesmeta UCSB2 merge Instance 23
title: Dynamic Characteristics of Woodframe Structures
publication year: 2002
authors: neesmeta UCSB2 merge Instance 25
authors: neesmeta UCSB2 merge Instance 24

neesmeta UCSB2 merge Instance 23
type: Person
first name: V.
last name: Camelo

neesmeta UCSB2 merge Instance 25
type: Person
last name: Hall
first name: J.

neesmeta UCSB2 merge Instance 24
type: Person
last name: Beck
first name: J.

UMN loadHistory record
type: File
URI: /UMN_Data/Chapter3/Chapt3E/LoadHistory.xls
name: UMN_loadHistory_record

NEESMeta Instance 50013
type: EventGroup
name: Test Phase 7A

miniMOST report1
type: TechnicalReport
authors: Narutoshi Nakata
authors: Bill Spencer
name: miniMOST_requirements.pdf
title: Sytem Requirements for Mini-MOST Experiment
authors: Guangqiang Yang
URI: /miniMOST/UIUC/narrative/miniMOST_requirements.pdf

Narutoshi Nakata
type: Person
last name: Nakata
first name: Narutoshi
title: Graduate Student

Bill Spencer
type: Person
first name: Bill
last name: Spencer

Guangqiang Yang
type: Person
last name: Yang
phone number type: voicePhone
first name: Guangqiang

test0228.txt
type: File
URI: /miniMOST/UIUC/test0228/test0228.txt
description: Testing results of miniMOST test 0228. Including the readings of LVDT, StrainGage, and LoadCell.
name: test0228.txt

NEESMeta Instance 2
type: File
name: Figure1.jpg
URI: figures/figure1.jpg
description: Shake Table of the UC-San Diego Uniaxial Earthquake Simulation System

ArturoSchultz
type: Person
person ID: 001231
first name: Arturo E.
last name: Schultz

neesmeta UCSB2 merge Instance 18
type: Person
last name: Kawinkler
first name: H.

Xiangdong Tong s
type: RolePerson
has person: XiangdongTong
is active: true
has role: Graduate Student

XiangdongTong
type: Person
last name: Tong
person ID: 0001234
first name: Xiangdong

miniMOST UIUC DAQ setup
type: DAQSetup
short description: The setup of Data Acquisition equipments.
has figures: pci6036board.jpg
has figures: SH6868EPCable.jpg
has figures: PC.jpg
has figures: Meter.jpg
has figures: Servo Motor Driver.jpg
has figures: BNCbox.jpg
has figures: pci7334.jpg
name: miniMOST_UIUC_DAQ_setup
has figures: SHC68Cable.jpg

pci6036board.jpg
type: File
URI: /miniMOST/UIUC/figures/pci6036board.jpg
name: pci6036board.jpg

SH6868EPCable.jpg
type: File
name: SH6868EPCable.jpg

PC.jpg
type: File
URI: /miniMOST/UIUC/figures/PC.jpg
name: PC.jpg

Meter.jpg
type: File
name: Meter.jpg
URI: /miniMOST/UIUC/figures/Meter.jpg

Servo Motor Driver.jpg
type: File
URI: /miniMOST/UIUC/figures/Servo_Motor_Driver.jpg
name: Servo_Motor_Driver.jpg

BNCbox.jpg
type: File
name: BNCbox.jpg
URI: /miniMOST/UIUC/figures/BNCbox.jpg

pci7334.jpg
type: File
name: pci7334.jpg
URI: /miniMOST/UIUC/figures/pci7334.jpg

SHC68Cable.jpg
type: File
name: SHC68Cable.jpg
URI: /miniMOST/UIUC/figures/SHC68Cable.jpg

L-shape anti spinner.jpg
type: File
URI: /miniMOST/UIUC/figures/L-shape_anti_spinner.jpg
name: L-shape_anti_spinner.jpg

NEESMeta Instance 50036
type: Sensor
sensor type: ForceTransducer
sensor type: Other
sensor type: LVDT
name: Group B 1
sensor type: DisplcamentTransducer
sensor type: AxialGauge
sensor type: Accelerometer
sensor type: PorePressureTransducer
sensor type: ShearGauge
sensor type: MomentGauge

miniMOST requirements.pdf
type: File
description: Describe the setup and requirements for miniMOST experiment.
name: miniMOST_requirements.pdf
URI: /miniMOST/UIUC/narrative/miniMOST_requirements.pdf

NEESMeta Instance 10010
type: File
description: Steel Base on Shake Table
name: Figure 2
URI: /figures/figure2.jpg

UMN Composite infill wall Beam-to-Column Connection
type: Structure
has descriptions: UMN Chapt3
has materials: UMN Composite infill wall Steel
short description: Beam-to-Column Connection Design
has figures: UMN Figure3.1.2
has figures: UMN Figure3.1.3
name: UMN_Composite_infill_wall_Beam-to-Column_Connection
has materials: UMN Composite infill wall Concrete

UMN Chapt3
type: File
URI: /UMN_Data/Chapter3/Chapt3.doc
name: UMN_Chapt3

UMN Composite infill wall Steel
type: Material
short description: The steel material properties
has files: UMN Table3.2.1
name: UMN_Composite_infill_wall_Steel
long description: The material properties of the steel components are reported in Table 3.2.1 and include: static yield stress Fys, dynamic yield stress Fyd, ultimate tensile stress Fu, modulus of elasticity Es, strain hardening modulus Esh, and strain at initiation of strain hardening esh. The material properties were obtained by performing tension tests on coupons taken from the steel members. Similar components were made from the same heat of steel for both specimens. Coupons WA-1 and WA-2 were removed from different legs of the web angle L2´2´5/16. Coupons TSA-1 and TSA-2 were removed from different legs of the top-and-seat angle L5´3´5/16. Coupons CW-1 and CW-2 were removed from the web of column member W5´19, and coupons CF-1 and CF-2 were removed from the flange of the W5´19. Coupons BW-1 and BW-2 were removed from the web of beam member W8´13, and coupons BF-1 and BF-2 were removed from the flange of the W8´13. The coupons were fabricated by cutting a 2 inch ´18 inch block from additional steel pieces provided from the heat, and then milled to the required dimensions as shown in Figure 3.2.1. Tension testing of coupons was performed in an MTS hydraulic testing machine in the Structural Engineering Laboratory at the University of Minnesota. It is noted that, although the columns were A572 Grade 50, the static yield strength was approximately 45 ksi.
has files: UMN Figure3.2.1

UMN Table3.2.1
type: File
description: Material Properties of Steel Members
name: UMN_Table3.2.1
URI: /UMN_Data/Chapter3/Chapt3A/Table3.2.1

UMN Figure3.2.1
type: File
description: Coupon Dimensions
URI: /UMN_Data/Chapter3/Chapt3B/coupon.vsd
name: UMN_Figure3.2.1

UMN Figure3.1.2
type: File
description: Partially-Restrained Connection Detailing
URI: /UMN_Data/Chapter3/Chapt3A/PRdetail.vsd
name: UMN_Figure3.1.2

UMN Figure3.1.3
type: File
URI: /UMN_Data/Chapter3/Chapt3A/PRdeform.vsd
description: Deformation of the PR Connection Subjected to Bending
name: UMN_Figure3.1.3

UMN Composite infill wall Concrete
type: Material
has files: UMN Table3.2.2
short description: The concrete material properties
long description: The infill walls were cast in place with two batches of concrete, with the first story being cast two days before the second story. Casting was initiated by pouring the concrete through three portal openings cut into the form on the east side of the wall, spaced uniformly across the mid-height of the panel. When the vibrated concrete reached the bottom of the portals, these portals were sealed with wood blocks, and the concrete pour continued through three chutes at the top of the infill panel, also spaced uniformly along the width of the panel. The concrete was allowed to harden 72 hours before removal of the forms. After removal of the forms, the concrete was covered with burlap and kept continuously moist for four days. The concrete that formed in the chutes was then chipped off and sanded smooth. Thirty-six 4 inch´8 inch cylinders were cast for each batch of concrete mix. Half of the cylinders were moist-cured (ASTM C192), and the others were cured under the same conditions as the infill panels. Content of the concrete mix included: cement, pea gravel, sand, fly ash, water, and retarder. The properties of each material include: Coarse aggregate: 3/8 inch maximum-size pea gravel (ASTM C33) with an oven-dry specific gravity of 2.63, absorption of 1.33%, and oven-dry rodded unit weight of 104 lb per cu ft. Fine aggregate: Natural sand (ASTM C33) with an ovendry specific gravity of 2.61 and an absorption of 1.07%. The fineness modulus was 2.70. Cement: Type III (ASTM C150) Fly ash: Class F (ASTM C618) Retarder: WR Grace Daratard-17 (ASTM C494) For the concrete mix, the water to cementitious material ratio was 0.71, the coarse aggregate to cementitious material ratio was 2.64, and the fine aggregate to cementitious material ratio was 3.38. The fly ash constituted 20% of the cementitious material by weight. The retarding admixture was 7 fl oz/100 lb cement in each batch of mix, which had approximately 0.35 cu yd of concrete. Table 3.2.2 shows the material properties o…
name: UMN_Composite_infill_wall_Concrete
has files: UMN Table3.2.3

UMN Table3.2.2
type: File
name: UMN_Table3.2.2
description: Concrete Material Properties for the First Story of the Specimen
URI: /UMN_Data/Chapter3/Chapt3A/Table3.2.2.doc

UMN Table3.2.3
type: File
description: Concrete Material Properties for the Second Story of the Specimen
name: UMN_Table3.2.3
URI: /UMN_Data/Chapter3/Chapt3A/Table3.2.3.doc

Civil Engineering UMN
type: Organization
home page: http://www.ce.umn.edu/
description: The department continues to work on many new initiatives. In August 2002, the St. Anthony Falls Laboratory received a $19.3 million science and technology center grant from the National Science Foundation to launch a major new research initiative. The National Center for Earth-Surface Dynamics brings together scientists across disciplines to study how erosion, sediment movement and other forces shape the planet's surface. This research will place the department on the forefront of the developing field of surface-process science. A second NSF-funded project, the Multi-Axial Subassemblage Testing system, is rising rapidly on the northeast corner of the Minneapolis campus. The $11.2 million MAST lab will allow researchers to test the effects of earthquakes, high winds, explosions, and other extreme forces on buildings and other structures.
NEES code: 00101
address: Department of Civil Engineering 500 Pillsbury Drive S.E. Minneapolis, MN 55455-0116
name: Department of Civil Engineering, University of Minnesota at Twin Cities

NEESMeta Instance 50021
type: Event
name: 3rd Seismic Test of Phase 5

Xiangdong Tong
type: Person
title: Ph.D. Student
first name: Xiangdong
last name: Tong
affiliation: Civil Engineering UMN

NEESMeta Instance 50039
type: SensorGroup
name: Group P 1-9

Xiangdong Tong thesis 2001
type: Thesis
name: Seismic Behavior of Composite Steel Frame-Reinforced Concrete Infill Wall Structural System
URI: /UMN_Data/Thesis/
title: Seismic Behavior of Composite Steel Frame-Reinforced Concrete Infill Wall Structural System
has institution: Civil Engineering UMN
type: Ph.D. Thesis
publication year: 2001
authors: Xiangdong Tong

UMN Figure3.4.8
type: File
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.8.vsd
description: Instrumentation Plan: Strain Gages in the Connection Region
name: UMN_Figure3.4.8

NEESMeta Instance 30001
type: Task
name: Task 1.3.3 - Dynamic Characteristics of Wood-Frame Buildings

NEESMeta Instance 20008
type: SensorGroup
measurement: Test Strucuture Absolute Acceleration, North-South Direction
sign convention: Absolute Acceleration to the North is Positive
name: Group D 1-23

UMN Composite infill wall BehaviorOfStud
type: Event
name: UMN_Composite_infill_wall_BehaviorOfStud
test type: Pseudo dynamic
has site: UMN Site
long description: The observations derived from the behavior of the interface headed stud connectors pertain to interface slip demands, stud axial strain demands, stud yielding, stud fracture, and interface concrete confinement. These are: 1) The headed studs connectors along the beam-infill wall interfaces had higher slip demands than the headed stud connectors along the column-infill wall interfaces. Furthermore, the slip demands were approximately equal in the two loading directions for the studs along the beam-infill interfaces, but had a large difference in the two loading directions for the studs along column-infill interfaces. 2) The headed studs along the bottom interface of each infill appeared to have the highest forces based upon strain data. These forces likely were sufficiently large to reduce the shear strength of the studs. However, failure of studs was likely controlled more directly by strain demands leading to low-cycle fatigue fracture. The majority of the studs that failed did so by low-cycle fatigue. The fractured studs were along the beam-infill interfaces. With respect to the low-cycle fatigue failure of the studs, it appeared that the slip demands far outweighed the axial deformation demands. 3) The headed studs along the top interface of each panel exhibited a more ductile failure pattern that the headed studs along the bottom interface, indicating that isolating the studs from the concrete at the base may be an effective approach for increasing their slip capacity. 4) The headed studs along the beam-infill wall interface were well confined by the reinforcing cages, but the corner concrete along the column-infill wall interfaces crushed substantially at limited interstory drift demands, indicating more confining steel is needed in these locations.s.
has output data: UMN Stud Results
has descriptions: UMN Chapter6
short description: This Event compares the “axial” and “bending” strain demands of the interface headed stud connectors, discusses the slip and separation demands along the interfaces, and determines the deformation capacity of the headed studs due to the low-cycle fatigue.

UMN Site
type: Site
name: UMN_Site

UMN Stud Results
type: Folder
has files: UMN Chapter6
name: UMN_Stud_Results

UMN Chapter6
type: File
description: Behavior of Interface Headed Stud Connectors
name: UMN_Chapter6
URI: /UMN_Data/Chapter6/Chapt6.doc

Narutoshi Nakata s
type: RolePerson
has role: Graduate Student
has person: Narutoshi Nakata

UMN Composite infill wall test
type: Task
has site: UMN Site
has role persons: Jerome Hajjar cpi
has event groups: UMN Composite infill wall EventGroup1
name: UMN_Composite_infill_wall_test
has role persons: Xiangdong Tong s
has publications: Xiangdong Tong thesis 2001
has infrastructure setups: Test Setup for Composite Infill Wall UMN
has role persons: Arturo Schultz pi

Jerome Hajjar cpi
type: RolePerson
has role: Co-PI
has person: JeromeHajjar

JeromeHajjar
type: Person
first name: Jerome
person ID: 001230
last name: Hajjar

UMN Composite infill wall EventGroup1
type: EventGroup
has events: UMN Composite infill wall GeneralBehavior
has sensor setups: UMN Composite infill wall SensorSetup global
short description: The first Event Group of the composite infill wall test.
has events: UMN Composite infill wall BehaviorOfStud
name: UMN_Composite_infill_wall_EventGroup1
has wave form setups: UMN Composite infill wall LoadHistory
has sensor setups: UMN Composite infill wall SensorSetup columns
has sensor setups: UMN Composite infill wall SensorSetup connection
has specimen setups: UMN Composite infill wall SpecimenSetup
has sensor setups: UMN Composite infill wall SensorSetup walls
has sensor setups: UMN Composite infill wall SensorSetup studs
has events: UMN Composite infill wall BehaviorOfWall
has site: UMN Site

UMN Composite infill wall GeneralBehavior
type: Event
has site: UMN Site
test type: Pseudo dynamic
long description: The main conclusions derived from the global response of the specimen pertain to strength, drift capacity, ductility, and distribution of forces between the frame and panel. These are: 1) The specimen provided sufficient system overstrength. The specimen was sized to resist approximately 70 kips prescribed design lateral load. The maximum load of the specimen was approximately 160 kips, 2.3 times the design lateral load. The yield strength of the specimen was defined as 85% of the maximum load, 1.9 times the design lateral load. 2) The second story interstory drift was able to surpass 3% without collapse of the structure. Approximately 50% of the lateral strength was lost when the total drift of the specimen was increased from 0.75% to 1.25%. The decrease in the lateral strength was primarily induced by the quick disruption of the corner concrete in the second story and failure of the headed stud connectors along the beam-panel interfaces. 3) The ductility index, m, is approximately equal to 4 for the second story and 3 for the entire structure. The first story was unable to exhibit the same level of the ductility, and consequently it did not dissipate the same amount of energy as the second story. The primary factor responsible for this behavior was the fixity of the first-story columns, which is an artifice of the test setup used. 4) The lateral shear force was resisted primarily by the compression strut and interface headed stud connectors. At the design lateral force level, the headed studs resisted 80-90% of the total lateral load, and the remaining 10-20% was resisted by the compression strut. The compression strut was required to resist increasing amounts of lateral shear force as the number of stud failure increased. 5) The overturning moment was shared by the steel frame and the RC infill wall. At the design lateral force level, the steel frame resisted approximately 80% of the overturning moment. The steel frame was required to resist increasing amounts of…
has output data: UMN GeneralBehavior Results
name: UMN_Composite_infill_wall_GeneralBehavior
has descriptions: UMN Chapter4
short description: This ProcessedEvent reports the strength and stiffness of the specimen; describes the observed behavior of each of the component, such as the cracking and crushing of the RC infill wall, yielding of the steel frame, and fracture of the interface headed stud connectors; and evaluates the ductility and energy dissipation capacity of the specimen.

UMN GeneralBehavior Results
type: Folder
has files: UMN Chapter4
name: UMN_GeneralBehavior_Results

UMN Chapter4
type: File
URI: /UMN_Data/Chapter4/Chapt4.doc
description: General Behavior of the Specimen
name: UMN_Chapter4

UMN Composite infill wall SensorSetup global
type: SensorSetup
setup figures: UMN Figure3.4.1
name: UMN_Composite_infill_wall_SensorSetup_global
setup figures: UMN Figure3.4.2
short description: The setup of instrumentation
long description: The specimen was heavily instrumented in order to obtain comprehensive information. Three types of instruments, including strain gages, linear variable differential transformers (LVDTs), and linear position transducers (LPTs) were employed to measure strains and displacements.
setup descriptions: UMN Chapt3

UMN Figure3.4.1
type: File
name: UMN_Figure3.4.1
description: Instrumentation of the Entire Specimen
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.1.jpg

UMN Figure3.4.2
type: File
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.2.vsd
description: Instrumetaion Plan: Global LVDTs
name: UMN_Figure3.4.2

UMN Composite infill wall LoadHistory
type: WaveFormSetup
has wave form: UMN LoadHistory
name: UMN_Composite_infill_wall_LoadHistory
short description: The cyclic loading history on the composite infill wall.
long description: The cyclic loading history is shown in Figure 3.5.1. A total of 25 loading cycles were divided into 9 loading groups. Each group had 3 loading cycles except for the last two groups, which had 2 loading cycles each. The cyclic loading history was modified from SAC protocol for testing of steel beam-column connections and other steel specimens (SAC, 1997). In order to capture the characteristics of crack formation and Fig. 3.5.1 Loading History progression in the RC infill wall, 3 loading group were applied before the total drift reached 0.5%, and these first 3 loading groups was controlled by the peak lateral load, with 40 kips for Group1, 80 kips for Group 2 and 120 kips for Group 3. The loading history of the remaining 6 loading groups was controlled by the total drift of the specimen, with 0.5% for Group 4, 0.75% for Group 5, 1.0% for Group 6, 1.25% for Group 7, 1.5% for Group 8 and 1.75% for Group 9. During these 6 loading groups, the increment of the total drift was set at 0.25% instead of the 0.5% or 1% in SAC protocol (SAC, 1997) because the specimen exhibited quick change in lateral stiffness and strength in such an increment of total drift. During each loading cycle, the specimen was first loaded in the south direction, then unloaded, and then loaded in the north direction, then unloaded. The reading of the applied lateral load and lateral displacement at each story level were set to be negative when the specimen was loaded in the south direction, and positive when the specimen was loaded in the north direction. In the following chapters, each loading group is sometimes referred to by using its the peak total lateral drift of the specimen during the first cycle of that loading group. Therefore, “0.05% cycles” represents loading group 1; “0.2% cycles” represents loading group 2; “0.3% cycles” represents loading group 3; “0.5% cycles” represents loading group 4; “0.75% cycle” represents loading group 5; “1.0% cycle” represents loading group 6; “1.25% cycle rep…
scale factor: 1.0

UMN LoadHistory
type: WaveForm
name: UMN_LoadHistory
description: Cyclic loading history
motion record: UMN loadHistory record

UMN Composite infill wall SensorSetup columns
type: SensorSetup
setup figures: UMN Figure3.4.3
short description: Instrumentation of the steel columns
setup descriptions: UMN Chapt3
name: UMN_Composite_infill_wall_SensorSetup_columns

UMN Figure3.4.3
type: File
name: UMN_Figure3.4.3
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.3.vsd
description: Instrumentation Plan: Strain Gages on the Columns

UMN Composite infill wall SensorSetup connection
type: SensorSetup
short description: Instrumentation of the partially-restrained connection regions
setup figures: UMN Figure3.4.7
name: UMN_Composite_infill_wall_SensorSetup_connection
setup figures: UMN Figure3.4.8
setup descriptions: UMN Chapt3

UMN Figure3.4.7
type: File
description: Instrumentation Plan: LVDTs in the Connection Region
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.7.vsd
name: UMN_Figure3.4.7

UMN Composite infill wall SpecimenSetup
type: SpecimenSetup
has specimens: UMN Composite infill wall HeadedStudConnectors
name: UMN_Composite_infill_wall_SpecimenSetup
long description: This object models several key issues of the specimen design: choice of dimensions, detailing of the PR connections, design of the interface headed studs, and design of wall reinforcement. The test setup is illustrated and material properties of the specimen are reported.
has specimens: UMN Composite infill wall Specimen
short description: The specimen setup for the composite infill wall experiment
has specimens: UMN Composite infill wall Beam-to-Column Connection
has specimens: UMN Composite infill wall Reinforcement
setup descriptions: UMN Chapt3

UMN Composite infill wall HeadedStudConnectors
type: Structure
has materials: UMN Composite infill wall HeadedStudsMaterial
has figures: UMN Figure3.1.6
has figures: UMN Figure3.1.5
has figures: UMN Figure3.1.4
has descriptions: UMN Chapt3
short description: Design of the Headed Stud Connectors along the Interfaces
name: UMN_Composite_infill_wall_HeadedStudConnectors

UMN Composite infill wall HeadedStudsMaterial
type: Material
short description: Material properties of headed studs
long description: The material properties of the headed studs, as provided by Stud Welding Associates, included the yield strength of the stud steel at 62.3 ksi, the tensile strength of the stud steel at 80.2 ksi and the maximum elongation at 21.0% for a two inch gage length.
name: UMN_Composite_infill_wall_HeadedStudsMaterial

UMN Figure3.1.6
type: File
URI: /UMN_Data/Chapter3/Chapt3A/Peribar.vsd
name: UMN_Figure3.1.6
description: Confinement of Headed Stud Connectors

UMN Figure3.1.5
type: File
URI: /UMN_Data/Chapter3/Chapt3A/StudMechnism.vsd
name: UMN_Figure3.1.5
description: Shear Force Transfer Mechanism of a Headed Stud Connector

UMN Figure3.1.4
type: File
URI: /UMN_Data/Chapter3/Chapt3A/StudMode.vsd
description: Failure Modes of a Headed Stud Connector Loaded in Shear
name: UMN_Figure3.1.4

UMN Composite infill wall Specimen
type: Structure
has figures: UMN Figure3.1.1
has materials: UMN Composite infill wall Steel
has descriptions: UMN Chapt3
has descriptions: UMN Table3.1.1
has materials: UMN Composite infill wall Concrete
name: UMN_Composite_infill_wall_Specimen
short description: The dimensions of the specimen

UMN Figure3.1.1
type: File
URI: /UMN_Data/Chapter3/Chapt3A/Testsetup.vsd
name: UMN_Figure3.1.1

UMN Table3.1.1
type: File
name: UMN_Table3.1.1
description: Geometry and Material Properties of the Prototype Structure and the Specimen
URI: /UMN_Data/Chapter3/Chapt3A/Table3.1.1.doc

UMN Composite infill wall Reinforcement
type: Structure
has figures: UMN Figure3.1.7
has descriptions: UMN Chapt3
has materials: UMN Composite infill wall ReinforcingMaterial
short description: Design of the wall reinforcement
name: UMN_Composite_infill_wall_Reinforcement

UMN Figure3.1.7
type: File
URI: /UMN_Data/Chapter3/Chapt3A/Wallbar.vsd
description: Detailing of Confining Cages and Wall Reinforcement
name: UMN_Figure3.1.7

UMN Composite infill wall ReinforcingMaterial
type: Material
name: UMN_Composite_infill_wall_ReinforcingMaterial
short description: Material properties of reinforcing bars
long description: The No. 2 model reinforcement was a hot-rolled deformed reinforcing bar with properties similar to Grade 60 reinforcement. The diameter was 0.25 inches and the effective area was 0.05 square inches. According to the tension testing results provided by CTL, the yield strength of this No. 2 reinforcement was 62.5 ksi, the ultimate strength was 88.8 ksi, the yield strain was approximately 2000 me, and the maximum elongation was 17.8%.

UMN Composite infill wall SensorSetup walls
type: SensorSetup
short description: Instrumentation of the reinforced concrete infill walls, and the interfaces between steel members and reinforced concrete infill walls
setup figures: UMN Figure3.4.2
setup figures: UMN Figure3.4.5
name: UMN_Composite_infill_wall_SensorSetup_walls
setup descriptions: UMN Chapt3
setup figures: UMN Figure3.4.4
setup figures: UMN Figure3.4.6

UMN Figure3.4.5
type: File
description: Instrumentation Plan: LVDTs along the Interfaces between the Steel Members and RC Walls
name: UMN_Figure3.4.5
URI: /UMN_Data/Chapter3/Chapt3D/SL&SE_LVDT.vsd

UMN Figure3.4.4
type: File
URI: /UMN_Data/Chapter3/Chapt3D/studgage.vsd
name: UMN_Figure3.4.4
description: Instrumentation Plan: Strain Gages on the Studs and Infill Walls

UMN Figure3.4.6
type: File
URI: /UMN_Data/Chapter3/Chapt3D/Fig3.4.6.jpg
name: UMN_Figure3.4.6
description: Installation of the Separation LVDTs

UMN Composite infill wall SensorSetup studs
type: SensorSetup
setup descriptions: UMN Table3.4.1
short description: Instrumentation of the headed studs
setup figures: UMN GageDistance
setup descriptions: UMN Chapt3
name: UMN_Composite_infill_wall_SensorSetup_studs

UMN Table3.4.1
type: File
name: UMN_Table3.4.1
description: Distance from the Strain Gage Center to the Stud Base
URI: /UMN_Data/Chapter3/Chapt3D/StudGagePos.xls

UMN GageDistance
type: File
description: Table 3.4.1 provides the measured distance from the center of each stud strain gage to the base of the stud.
name: UMN_GageDistance
URI: /UMN_Data/Chapter3/Chapt3D/GageDistance.vsd

UMN Composite infill wall BehaviorOfWall
type: Event
short description: This Event highlights the characteristics of the strain and internal forces at the critical sections of the steel columns, the strain profiles and internal forces at both ends of the middle beam, and the behavior of the PR connection. It also discusses the patterns and magnitude of deformations in the RC infill wall.
test type: Pseudo dynamic
has output data: UMN Wall Results
name: UMN_Composite_infill_wall_BehaviorOfWall
long description: The main observations derived from the local responses of the steel frame and the infill wall pertain to deformation demands of major components, internal force distribution in the steel columns, and strength capacity of the PR connections. These are: 1) The steel column flanges exhibited moderate yielding in and near the connection regions, but extensive shear yielding occurred to the steel column web due to the increasing compression strut force. As designed, the steel beam had minor shear yielding in the connection region so that the plastic deformation of the connection was contributed primarily by the connection angles. 2) The axial forces in the two columns comprised an important couple to resist overturning moment. The ratio of the tensile force in the windward column to the compressive force in the leeward column was greater than 1, and this ratio increased with increasing drift demands. It was more than 2 when the specimen reached its maximum strength. 3) The maximum shear force in the column occurred in the connection region, at the cross section just below or above the centerline of the bolts connecting the seat angle to the column flange. 4) As designed, the RC infill wall exhibited approximately uniform shear deformation until the headed studs failed and the corner concrete crushed. The percentage of the interstory drift induced by the gross shear deformation of the infill wall increased with increasing drift demands. In the first story, this percentage reached more than 50% when the specimen achieved its maximum strength. 5) The load-deformation response envelope of the PR connections exhibited bilinear (elastic-plastic) behavior. The plastic hinges in the PR connections started to form before the specimen reached its maximum lateral strength, and the plastic mechanism of the PR connections was fully achieved in the 0.75% cycles when the specimen reached its maximum lateral strength. 6) The plastic moment capacity of the PR connection was decreased by …
has site: UMN Site
has descriptions: UMN Chapter5

UMN Wall Results
type: Folder
has files: UMN Chapter5
name: UMN_Wall_Results

UMN Chapter5
type: File
name: UMN_Chapter5
description: Local Response of the Steel Frame and the Reinforced Concrete Infill Wall
URI: /UMN_Data/Chapter5/chapt5.doc

Test Setup for Composite Infill Wall UMN
type: InfrastructureSetup
long description: The specimen is oriented parallel to the strong wall, along the north - south direction, in order to utilize the strong wall as part of the out-of-plane bracing system.
short description: This shows the infrastructure setup for the experiment of a composite steel frame-reinforced concrete infill wall at University of Minnesota.
setup descriptions: UMN Chapt3
setup figures: UMN Fig 3.3.3
setup figures: UMN Fig 3.3.1
setup figures: UMN Fig 3.3.2
name: Test_Setup_for_Composite_Infill_Wall@UMN

UMN Fig 3.3.3
type: File
URI: /UMN_Data/Chapter3/Chapt3C/brace.vsd
name: UMN_Fig_3.3.3
description: Lateral Bracing Sytem

UMN Fig 3.3.1
type: File
URI: /UMN_Data/Chapter3/Chapt3C/base2.doc
description: View of the Foundation Plate and Column Base
name: UMN_Fig_3.3.1

UMN Fig 3.3.2
type: File
description: Effect of the Out-of-Plate Deforamation of Foundation Plates
name: UMN_Fig_3.3.2
URI: /UMN_Data/Chapter3/Chapt3C/PlateDeform.vsd

Arturo Schultz pi
type: RolePerson
has role: Principle Investigator
has person: ArturoSchultz
is active: true

neesmeta UCSB2 merge Instance 68
type: Sensor
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: LVDT
sensor type: MomentGauge
sensor type: Other
sensor type: Accelerometer
short description: Pore Pressure Transducer
sensor type: PorePressureTransducer
sensor type: AxialGauge
name: SJB_P4
sensor type: DisplcamentTransducer

NEESMeta Instance 10005
type: File
URI: /figures/figure34.jpg
description: Second Floor View of Instrumentation for Phase 5
name: Figure 34

neesmeta UCSB2 merge Instance 53
type: EventGroup
long description: Six-pile group (2x3) with a large embedded pile cap. Lateral spreading of a moderately overconsolidated nonliquefiable clay crust overlying a medium-thick deposit of liquefiable sand overlying dense sand. Crust at 4o slope. Three Santa Cruz motions and a Kobe motion. Centrifugal acceleration = 38.1g.
name: PDS03

NEESMeta Instance 20001
type: Unit
description: Acceleration
name: g

LVDT1.jpg
type: File
URI: /miniMOST/UIUC/figures/LVDT1.jpg
name: LVDT1.jpg

top view actuator beam.jpg
type: File
URI: /miniMOST/UIUC/figures/top_view_actuator_beam.jpg
name: top_view_actuator_beam.jpg

neesmeta UCSB2 merge Instance 48
type: Event
name: SJB01_04
has site: neesmeta UCSB2 merge Instance 54
long description: Consisted of scaled versions of the ground motion recorded during the 1989 Loma Prieta Earthquake at the UCSC/Lick Lab.
short description: Small Santa Cruz

neesmeta UCSB2 merge Instance 54
type: Site
long description: This is a NEES Equipment Site.
hosted by: neesmeta UCSB2 merge Instance 0
short description: This is a NEES Equipment Site.
name: UC Davis, CGM
has role persons: neesmeta UCSB2 merge Instance 96
has role persons: neesmeta UCSB2 merge Instance 97
has primary equipments: neesmeta UCSB2 merge Instance 76
has primary equipments: neesmeta UCSB2 merge Instance 77
has role persons: neesmeta UCSB2 merge Instance 95
has role persons: neesmeta UCSB2 merge Instance 94

neesmeta UCSB2 merge Instance 0
type: Organization
address: One Shields Avenue Davis, California 95616
home page: http://cgm.engr.ucdavis.edu
name: Center for Geotechnical Modeling at UC Davis

neesmeta UCSB2 merge Instance 96
type: RolePerson
has person: neesmeta UCSB2 merge Instance 91
has role: graduate researcher

neesmeta UCSB2 merge Instance 91
type: Person
first name: Dongdong
title: Ph.D. student
last name: Chang

neesmeta UCSB2 merge Instance 97
type: RolePerson
has person: neesmeta UCSB2 merge Instance 88
has role: principal investigator

neesmeta UCSB2 merge Instance 88
type: Person
first name: Bruce L.
last name: Kutter
title: Professor

neesmeta UCSB2 merge Instance 76
type: SoilContainer
long description: A flexible shear beam model container
short description: Soil Container
name: SJB01 Flexible Shear Beam2 (FSB2)

neesmeta UCSB2 merge Instance 77
type: CentrifugeEquipment
long description: The pile's outer diameter is 1.905 cm (0.75 in.) and wall thickness 0.089 cm (0.035 in.). The pile cap dimensions, including the sheet aluminum rectangle and plaster, were 26.5 x 17.0 x 6.5 cm (10.4 x 6.7 x 2.6 in). The piles were covered with shrink-wrap to prevent the gages from getting wet. The pile tips were made of plastic and the tip angle was 60o.
name: SJB01 Pile
short description: Pile composed of aluminum 6061-T6.

neesmeta UCSB2 merge Instance 95
type: RolePerson
has role: graduate researcher
has person: neesmeta UCSB2 merge Instance 92

neesmeta UCSB2 merge Instance 92
type: Person
last name: Brandenberg
title: M.S.
first name: Scott J.

neesmeta UCSB2 merge Instance 94
type: RolePerson
has person: neesmeta UCSB2 merge Instance 93
has role: principal investigator

neesmeta UCSB2 merge Instance 93
type: Person
first name: Ross W.
last name: Boulanger
title: Professor

neesmeta UCSB2 merge Instance 35
type: FloatMeasurement
value: 100.0
has unit: neesmeta UCSB2 merge Instance 36

neesmeta UCSB2 merge Instance 36
type: Unit
name: Hertz

NEESMeta Instance 20012
type: File
URI: /sensorReading/phase5/5.F.1.B.txt
name: Acceleration Record of the 1st Frequency Test of Phase 5

NEESMeta Instance 20009
type: Sensor
sensor type: LVDT
sensor type: DisplcamentTransducer
sensor type: MomentGauge
sensor type: Accelerometer
sensor type: AxialGauge
sensor type: ShearGauge
name: D1
sensor type: PorePressureTransducer
sensor type: ForceTransducer
sensor type: Other

NEESMeta Instance 27
type: WaveForm
sampling rate: neesmeta UCSB2 merge Instance 35
description: 1994 Northridge Canoga Park
record unit: NEESMeta Instance 20001
scale factor: 0.12
name: Level 1

concept minimost.ppt
type: File
URI: /miniMOST/UIUC/narrative/concept_minimost.ppt
name: concept_minimost.ppt
description: A Microsoft Powerpoint drawing of miniMOST components.

neesmeta UCSB2 merge Instance 10072
type: Unit
name: mm
description: milimeters

NEESMeta Instance 20005
type: File
description: Phase 5 Test Structure (View of North Wall)
name: Figure 9
URI: /figures/figure9.jpg

neesmeta UCSB2 merge Instance 10068
type: FloatMeasurement
value: 16.8
has unit: neesmeta UCSB2 merge Instance 10063

neesmeta UCSB2 merge Instance 10063
type: Unit
description: i.e. Unit weight UOM
name: kN/m3

NEESMeta Instance 50020
type: Event
name: 2nd Seismic Test of Phase 5

NEESMeta Instance 10015
type: SensorGroup
measurement: Shake table absolute displacement, North-South direction
sign convention: Absolute displacement to the North is Positive
name: Group A 1

NEESMeta Instance 30002
type: Sensor
sensor type: LVDT
sensor type: DisplcamentTransducer
sensor type: MomentGauge
name: D2
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: Accelerometer
sensor type: PorePressureTransducer
sensor type: Other
sensor type: AxialGauge

neesmeta UCSB2 merge Instance 57
type: EventGroup
long description: Larger six-pile group (2x3) with a large embedded pile cap. Lateral spreading of a highly overconsolidated nonliquefiable clay crust overlying liquefiable Nevada sand over dense Nevada sand. Crust at 3o slope. Three Santa Cruz motions and one Kobe motion. Centrifugal acceleration = 57.2g.
name: SJB03

miniMOST at UIUC
type: Task
has role persons: Guangqiang Yang r
start date time: 2004-08-01
local timezone: CST
has event groups: miniMOST UIUC EventGroup 2004
name: miniMOST_at_UIUC
has role persons: Bill Spencer pi
has site: UIUC Site
has infrastructure setups: miniMOST overall setup
has role persons: Narutoshi Nakata s
key words: miniMOST
end date time: 2004-08-03
short description: This is the miniMOST experiment at University of Illinois at Urbana-Champaign.
key words: University of Illinois at Urbana-Champaign

Guangqiang Yang r
type: RolePerson
has role: Researcher
has person: Guangqiang Yang

miniMOST UIUC EventGroup 2004
type: EventGroup
name: miniMOST_UIUC_EventGroup_2004
has sensor setups: miniMOST UIUC sensor setup
has specimen setups: miniMOST specimen setup
local timezone: CST
end date time: 2004-02-29
start date time: 2004-02-28
has site: UIUC Site
has events: miniMOST test 0228
has DAQ setups: miniMOST UIUC DAQ setup

miniMOST UIUC sensor setup
type: SensorSetup
setup figures: anchorage.jpg
setup figures: LVDT1.jpg
setup figures: motor.jpg
setup figures: StrainGauge.jpg
short description: The sensor setup for miniMOST experiment.
setup descriptions: miniMOST requirements.pdf
name: miniMOST_UIUC_setup
setup descriptions: Mini MOST Instrument Settings.pdf
setup figures: LoadCell.jpg

anchorage.jpg
type: File
name: anchorage.jpg
URI: /miniMOST/UIUC/figures/anchorage.jpg

motor.jpg
type: File
name: motor.jpg
URI: /miniMOST/UIUC/figures/motor.jpg

StrainGauge.jpg
type: File
URI: /miniMOST/UIUC/figures/StrainGauge.jpg
name: StrainGauge.jpg

Mini MOST Instrument Settings.pdf
type: File
name: Mini_MOST_Instrument_Settings.pdf
URI: /miniMOST/UIUC/narrative/Mini_MOST_Instrument_Settings.pdf
description: Instrument Wiring and Settings for Mini-MOST Experiment

LoadCell.jpg
type: File
name: LoadCell.jpg
URI: /miniMOST/UIUC/figures/LoadCell.jpg

miniMOST specimen setup
type: SpecimenSetup
name: miniMOST_specimen_setup
setup figures: test setup planeView.jpg
short description: Specimen setup for miniMOST experiment.
setup descriptions: MiniMostWiring.pdf
setup figures: side view actuator beam.jpg
has specimens: miniMOST specimen
setup descriptions: miniMOST requirements.pdf
setup figures: top view actuator beam.jpg

test setup planeView.jpg
type: File
URI: /miniMOST/UIUC/figures/test_setup_planeView.jpg
name: test_setup_planeView.jpg

MiniMostWiring.pdf
type: File
URI: /miniMOST/UIUC/narrative/MiniMostWiring.pdf
name: MiniMostWiring.pdf

side view actuator beam.jpg
type: File
URI: /miniMOST/UIUC/figures/side_view_actuator_beam.jpg
name: side_view_actuator_beam.jpg

miniMOST specimen
type: Structure
has figures: L-shape anti spinner.jpg
has descriptions: concept minimost.ppt
has figures: specimen.jpg
has figures: Base Plate.jpg
has figures: testbeam.jpg
name: miniMOST_specimen

specimen.jpg
type: File
URI: /miniMOST/UIUC/figures/specimen.jpg
name: specimen.jpg

Base Plate.jpg
type: File
URI: /miniMOST/UIUC/figures/Base_Plate.jpg
name: Base_Plate.jpg

testbeam.jpg
type: File
URI: /miniMOST/UIUC/figures/testbeam.jpg
name: testbeam.jpg

UIUC Site
type: Site
short description: The testing site at University of Illinois at Urbana-Champaign.
name: UIUC_Site

miniMOST test 0228
type: Event
test type: pseudo dynamic
has output data: miniMOST test 0228 results
has site: UIUC Site
name: miniMOST_test_0228
short description: An event with one-acurator miniMOST setup.
start date time: 2004-02-28T20:15:49.57800
end date time: 2004-02-29T02:11:14.78099
local timezone: CST

miniMOST test 0228 results
type: Folder
has files: test0228.txt
name: miniMOST_test_0228_results

Bill Spencer pi
type: RolePerson
has person: Bill Spencer
has role: Principle Investigator

miniMOST overall setup
type: InfrastructureSetup
name: miniMOST_overall_setup
setup figures: Mini MOST overall.jpg
setup descriptions: MiniMostWiring.pdf
setup descriptions: Mini MOST Instrument Settings.pdf
setup descriptions: Machining.xls
setup figures: Mini MOST.jpg

Mini MOST overall.jpg
type: File
name: Mini_MOST_overall.jpg
URI: /miniMOST/UIUC/figures/Mini_MOST_overall.jpg

Machining.xls
type: File
name: Machining.xls
URI: /miniMOST/UIUC/machine/Machining.xls

Mini MOST.jpg
type: File
name: Mini_MOST.jpg
URI: /miniMOST/UIUC/figures/Mini_MOST.jpg

NEESMeta Instance 50016
type: Event
name: 5th Frequency Test of Phase 5

neesmeta UCSB2 merge Instance 22
type: Person
last name: Medina
first name: R.

NEESMeta Instance 50043
type: SensorGroup
name: Group H 3-10

neesmeta UCSB2 merge Instance 10076
type: Unit
description: centimeters per second
name: cm/s

neesmeta UCSB2 merge Instance 43
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 36
value: 4000.0

NEESMeta Instance 50024
type: Event
name: 5th Damping Test of Phase 5

Shirley Dyke cpi
type: RolePerson
has person: Shirley Dyke
has role: co-Principle Investigator

Shirley Dyke
type: Person
first name: Shirley
last name: Dyke

neesmeta UCSB2 merge Instance 39
type: WaveForm
name: SCO60696_SJB01_02
record unit: NEESMeta Instance 20001
scale factor: 7.7
description: 1989 Loma Prieta Earthquake
sampling rate: neesmeta UCSB2 merge Instance 38

neesmeta UCSB2 merge Instance 38
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 36
value: 1900.0

neesmeta UCSB2 merge Instance 63
type: Sensor
sensor type: ShearGauge
sensor type: Accelerometer
sensor type: Other
sensor type: LVDT
short description: moment strain gauges
sensor type: AxialGauge
sensor type: PorePressureTransducer
sensor type: MomentGauge
name: SJB_NEM5
sensor type: DisplcamentTransducer
sensor type: ForceTransducer

NEESMeta Instance 55
type: Person
last name: Filiatrault
person ID: 001111
first name: Andre
affiliation: NEESMeta Instance 7
address: Department of Structural Engineering, JOSE School of Engineering, University of California, San Diego, CA 92093-0085
title: Professor
home page: http://www.structures.ucds.edu/Faculty/Filiatrault.shtml
phone number: (858) 822-2161

NEESMeta Instance 7
type: Organization
address: 9500 Gilman Dr. La Jolla, CA 92093
name: Department of Structural Engineering, UCSD
home page: http://www.structures.ucsd.edu

neesmeta UCSB2 merge Instance 33
type: File
name: SJB01 - Figure 7
URI: /sjb01_figures/Fig7.dwg
description: Pile Cap Details

NEES
type: Organization
home page: http://www.nees.org
name: Netowrk for Earthquake Engineering Simulation

neesmeta UCSB2 merge Instance 50
type: Event
long description: Consisted of scaled versions of the ground motion recorded at a depth of 83 m at Port Island in the 1995 Great Hanshin Awaji Earthquake
name: SJB01_06
short description: Large Kobe
has site: neesmeta UCSB2 merge Instance 54

miniMOST report2
type: TechnicalReport
URI: /miniMOST/UIUC/narrative/TR_2004_04.pdf
authors: David Gehrig
publication year: 2004
name: TR_2004_04.pdf
title: Guide to the NEESgrid Reference Implementation

David Gehrig
type: Person
first name: David
last name: Gehrig

neesmeta UCSB2 merge Instance 10079
type: Unit
description: kilometers
name: km

NEESMeta Instance 10004
type: File
description: South-West View of Instrumentation for Phase 5
name: Figure 33
URI: /figures/figure33.jpg

neesmeta UCSB2 merge Instance 10082
type: Folder
has files: neesmeta UCSB2 merge Instance 31
has files: neesmeta UCSB2 merge Instance 29
has files: neesmeta UCSB2 merge Instance 34
has files: neesmeta UCSB2 merge Instance 33
name: SJBO1 Centrifuge Output Data
has files: neesmeta UCSB2 merge Instance 30
has files: neesmeta UCSB2 merge Instance 16
has files: neesmeta UCSB2 merge Instance 27
has files: neesmeta UCSB2 merge Instance 32
description: SJBO1 Centrifuge output data and project information
has files: neesmeta UCSB2 merge Instance 28

neesmeta UCSB2 merge Instance 31
type: File
URI: /sensorReading/SJB01/sjb01_05.prn
name: Record_SJB01_05

neesmeta UCSB2 merge Instance 29
type: File
name: Record_SJB01_03
URI: /sensorReading/SJB01/sjb01_03.prn

neesmeta UCSB2 merge Instance 34
type: File
name: SJB01 model layout
URI: /File/Drawing/sjb01-layout.pdf

neesmeta UCSB2 merge Instance 30
type: File
name: Record_SJB01_04
URI: /sensorReading/SJB01/sjb01_04.prn

neesmeta UCSB2 merge Instance 16
type: TechnicalReport
publication year: 2001
authors: neesmeta UCSB2 merge Instance 93
authors: neesmeta UCSB2 merge Instance 88
key words: Geotechnical
title: SJB01 - Centrifuge Data Report
authors: neesmeta UCSB2 merge Instance 92
authors: neesmeta UCSB2 merge Instance 87
URI: /Publication/cgmdr0102.pdf
key words: Raw Data
has institution: neesmeta UCSB2 merge Instance 0
key words: Centrifuge

neesmeta UCSB2 merge Instance 87
type: Person
first name: Priyanshu
last name: Singh

neesmeta UCSB2 merge Instance 27
type: File
name: Record_SJB01_01
URI: /sensorReading/SJB01/sjb01_01.prn

neesmeta UCSB2 merge Instance 32
type: File
URI: /sensorReading/SJB01/sjb01_06.prn
name: Record_SJB01_06

neesmeta UCSB2 merge Instance 28
type: File
URI: /sensorReading/SJB01/sjb01_02.prn
name: Record_SJB01_02

NEESMeta Instance 30005
type: Sensor
sensor type: MomentGauge
sensor type: ShearGauge
sensor type: LVDT
sensor type: Accelerometer
name: E2
sensor type: DisplcamentTransducer
sensor type: ForceTransducer
sensor type: PorePressureTransducer
sensor type: AxialGauge
sensor type: Other

NEESMeta Instance 50033
type: File
name: S3 - Structural Plans & Framing Elevations

NEESMeta Instance 10008
type: Event
name: 2nd Frequency Test of Phase 5
has wave form setups: NEESMeta Instance 30009
test type: Frequency

NEESMeta Instance 30009
type: WaveForm
name: White Noise 2
description: 0 Hz for a total test duration of 165 seconds
record unit: NEESMeta Instance 20001
scale factor: 1.0
sampling rate: neesmeta UCSB2 merge Instance 35

NEESMeta Instance 30000
type: Task
name: Task 1.1.2 - Shake Table Test of Multi-Story Apartment Building with Tuck-under Parking

neesmeta UCSB2 merge Instance 10033
type: Unit
name: %
description: Percent

neesmeta UCSB2 merge Instance 45
type: Event
has output data: neesmeta UCSB2 merge Instance 10082
long description: a small step wave used primarily to ensure that the instruments and data acquisition system function properly.
name: SJB01_01
short description: Step Wave
has wave form setups: neesmeta UCSB2 merge Instance 10081
has site: neesmeta UCSB2 merge Instance 54

neesmeta UCSB2 merge Instance 10081
type: WaveFormSetup
has wave form: neesmeta UCSB2 merge Instance 37
has wave form: neesmeta UCSB2 merge Instance 41
has wave form: neesmeta UCSB2 merge Instance 42
has wave form: neesmeta UCSB2 merge Instance 40
name: SJB01 Input Wave Form Setup
has wave form: neesmeta UCSB2 merge Instance 39

neesmeta UCSB2 merge Instance 37
type: WaveForm
description: 1995 Great Hanshin Awaji Earthquake
record unit: NEESMeta Instance 20001
name: Kobe0807_SJB01
sampling rate: neesmeta UCSB2 merge Instance 38

neesmeta UCSB2 merge Instance 41
type: WaveForm
description: 1989 Loma Prieta Earthquake
scale factor: 30.8
name: SCO60696_SJB01_04
sampling rate: neesmeta UCSB2 merge Instance 38
record unit: NEESMeta Instance 20001

neesmeta UCSB2 merge Instance 42
type: WaveForm
description: 1989 Loma Prieta Earthquake
sampling rate: neesmeta UCSB2 merge Instance 43
scale factor: 2.0
name: Step
record unit: NEESMeta Instance 20001

neesmeta UCSB2 merge Instance 40
type: WaveForm
description: 1989 Loma Prieta Earthquake
sampling rate: neesmeta UCSB2 merge Instance 38
name: SCO60696_SJB01_03
scale factor: 15.4
record unit: NEESMeta Instance 20001

neesmeta UCSB2 merge Instance 67
type: Sensor
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: LVDT
sensor type: MomentGauge
sensor type: Other
sensor type: Accelerometer
short description: Pore Pressure Transducer
sensor type: PorePressureTransducer
name: SJB_P3
sensor type: AxialGauge
sensor type: DisplcamentTransducer

NEESMeta Instance 20007
type: WaveForm
record unit: NEESMeta Instance 20001
scale factor: 1.0
name: White Noise 1
sampling rate: neesmeta UCSB2 merge Instance 35
description: Flat random white noise with frequencies ranging from 1 Hz to 20 Hz for a total test duration of 165 seconds

NSF
type: Organization
name: National Science Foundation
NEES code: 00001
home page: http://www.nsf.gov

NEESMeta Instance 50004
type: Organization
NEES code: 001212
name: Federal Emergency Management Agency (FEMA)

NEESMeta Instance 50005
type: Person
first name: G. G.
last name: Schierle

NEESMeta Instance 20002
type: File
name: Drawing1.jpg
URI: /drawings/drawing1.jpg
description: Architectural Plans and Elevations: A CAD drawing created by GFDS Engineers

miniMOST-1
type: Project
acknowledgements: This work was supported by the George E. Brown, Jr. Network for Earthquake Engineering Simulation (NEES) Program of the National Science Foundation, Award CMS-0117853. Any opinions, findings, and conclusions or recommendations expressed in this material are, however, those of the authors and do not necessarily reflect the views of others and the National Science Foundation.
has role persons: Narutoshi Nakata s
has sites: UIUC Site
NEES code: 0000228
has role persons: Guangqiang Yang r
has publications: miniMOST report1
objectives: The main purpose of the Mini-MOST experiment is to show the capability of major NEESgrid service components using a small-scale physical experiment setup. Comparing with the Multi-site Online Simulation Test (MOST) conducted on July 30, 2003, the Mini-MOST experimental hardware, as implied by its name, is small in size and can be easily packed and shipped to other places. However, the software involved in this experiment is similar to what was used for the MOST experiment and provides the same level of funcationlaity and services. Therefore, Mini-MOST experiment provides a desirable platform for students and researchers to be familiar with the NEESgrid software and to gain first-hand experience before conducting full-scale experiment. Moreover, the Mini-MOST experiment can also be utilized for the purposes of educational demonstration and software installation debufgging.
has tasks: miniMOST at UIUC
has publications: miniMOST report2
name: miniMOST-1
key words: NEESgrid service
has role persons: Bill Spencer pi
key words: NEESpop server
has sites: Washington University Site
local timezone: CST
start date time: 2003-08-01
end date time: 2004-09-30
long description: This set of miniMOST data are used solely for the purpose of testing data model.
key words: Multi-Site Online Simulation Test
has sponsors: NSF
executed by: NEES
has role persons: Shirley Dyke cpi
has publications: miniMOST report3

Washington University Site
type: Site
name: U_Washington_Site
short description: The NEES experiment site at Washington University.

miniMOST report3
type: TechnicalReport
title: Setting Up a NEESgrid Node: An Overview (Release 2.2)
URI: /miniMOST/UIUC/narrative/TR_2004_06.pdf
name: TR_2004_06.pdf

neesmeta UCSB2 merge Instance 64
type: Sensor
sensor type: ShearGauge
sensor type: Accelerometer
sensor type: Other
sensor type: LVDT
short description: moment strain gauges
sensor type: AxialGauge
sensor type: PorePressureTransducer
sensor type: MomentGauge
sensor type: DisplcamentTransducer
name: SJB_NEM6
sensor type: ForceTransducer

NEESMeta Instance 10003
type: File
description: North-East View of Instrumentation for Phase 5
URI: /figures/figure32.jpg
name: Figure 32

neesmeta UCSB2 merge Instance 70
type: SensorSetup
short description: Absolute Acceleration to the North is Positive
has sensors: NEESMeta Instance 30002
long description: Test Strucuture Absolute Acceleration, North-South Direction
has sensors: NEESMeta Instance 10001
name: Group D
has sensors: NEESMeta Instance 20009

NEESMeta Instance 10001
type: Sensor
sensor type: Other
name: D23
sensor type: MomentGauge
sensor type: ShearGauge
sensor type: PorePressureTransducer
sensor type: AxialGauge
sensor type: ForceTransducer
sensor type: LVDT
sensor type: Accelerometer
sensor type: DisplcamentTransducer

neesmeta UCSB2 merge Instance 60
type: Sensor
short description: moment strain gauges
sensor type: AxialGauge
sensor type: Accelerometer
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: DisplcamentTransducer
name: SJB_NEM2
sensor type: Other
sensor type: LVDT
sensor type: PorePressureTransducer
sensor type: MomentGauge

NEESMeta Instance 50030
type: File
name: notes12

neesmeta UCSB2 merge Instance 21
type: Person
last name: Ibarra
first name: IL.

neesmeta UCSB2 merge Instance 49
type: Event
short description: Large Kobe
long description: Consisted of scaled versions of the ground motion recorded at a depth of 83 m at Port Island in the 1995 Great Hanshin Awaji Earthquake.
has site: neesmeta UCSB2 merge Instance 54
name: SJB01_05

neesmeta UCSB2 merge Instance 10067
type: SoilDeposit
maximum dry unit weight: neesmeta UCSB2 merge Instance 10068
coefficient of uniformity: neesmeta UCSB2 merge Instance 10074
minimum dry unit weight: neesmeta UCSB2 merge Instance 10069
name: SJB01 Centrifuge Specimen - Nevada Sand
has sensor setups: neesmeta UCSB2 merge Instance 72
specific gravity: neesmeta UCSB2 merge Instance 10080
mean grain size: neesmeta UCSB2 merge Instance 10073
permeability: neesmeta UCSB2 merge Instance 10075
short description: SJB01 Nevada Sand Soil Deposit
saturated unit weight: neesmeta UCSB2 merge Instance 10070
relative density: neesmeta UCSB2 merge Instance 10071

neesmeta UCSB2 merge Instance 10074
type: FloatMeasurement
value: 1.64

neesmeta UCSB2 merge Instance 10069
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 10063
value: 14.0

neesmeta UCSB2 merge Instance 72
type: SensorSetup
has sensors: neesmeta UCSB2 merge Instance 66
has sensors: neesmeta UCSB2 merge Instance 59
has sensors: neesmeta UCSB2 merge Instance 68
has sensors: neesmeta UCSB2 merge Instance 64
has sensors: neesmeta UCSB2 merge Instance 67
has sensors: neesmeta UCSB2 merge Instance 61
long description: Centrifuge experiment sensor setup.
has sensors: neesmeta UCSB2 merge Instance 63
has sensors: neesmeta UCSB2 merge Instance 65
name: SensorGroup SJB01
has sensors: neesmeta UCSB2 merge Instance 62
short description: Vertical array of sensors.
has sensors: neesmeta UCSB2 merge Instance 60

neesmeta UCSB2 merge Instance 66
type: Sensor
sensor type: Accelerometer
sensor type: AxialGauge
short description: Pore Pressure Transducer
sensor type: ForceTransducer
name: SJB_P2
sensor type: MomentGauge
sensor type: PorePressureTransducer
sensor type: ShearGauge
sensor type: LVDT
sensor type: DisplcamentTransducer
sensor type: Other

neesmeta UCSB2 merge Instance 59
type: Sensor
sensor type: PorePressureTransducer
short description: moment strain gauge
sensor type: Accelerometer
sensor type: AxialGauge
sensor type: Other
sensor type: ShearGauge
name: SJB_NEM1
sensor type: LVDT
sensor type: MomentGauge
sensor type: DisplcamentTransducer
sensor type: ForceTransducer

neesmeta UCSB2 merge Instance 61
type: Sensor
sensor type: LVDT
sensor type: PorePressureTransducer
sensor type: DisplcamentTransducer
sensor type: AxialGauge
name: SJB_NEM3
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: MomentGauge
sensor type: Other
short description: moment strain gauges
sensor type: Accelerometer

neesmeta UCSB2 merge Instance 65
type: Sensor
sensor type: Accelerometer
sensor type: AxialGauge
name: SJB_P1
short description: Pore Pressure Transducer
sensor type: ForceTransducer
sensor type: MomentGauge
sensor type: PorePressureTransducer
sensor type: ShearGauge
sensor type: LVDT
sensor type: DisplcamentTransducer
sensor type: Other

neesmeta UCSB2 merge Instance 62
type: Sensor
name: SJB_NEM4
sensor type: LVDT
sensor type: PorePressureTransducer
sensor type: DisplcamentTransducer
sensor type: AxialGauge
sensor type: ShearGauge
sensor type: ForceTransducer
sensor type: MomentGauge
sensor type: Other
short description: moment strain gauges
sensor type: Accelerometer

neesmeta UCSB2 merge Instance 10080
type: FloatMeasurement
value: 2.644

neesmeta UCSB2 merge Instance 10073
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 10072
value: 0.17

neesmeta UCSB2 merge Instance 10075
type: FloatMeasurement
value: 0.0032

neesmeta UCSB2 merge Instance 10070
type: FloatMeasurement
value: 20.0

neesmeta UCSB2 merge Instance 10071
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 10033
value: 80.0

NEESMeta Instance 28
type: WaveForm
name: Level 2
scale factor: 0.53
record unit: NEESMeta Instance 20001
description: 1994 Northridge Canoga Park
sampling rate: neesmeta UCSB2 merge Instance 35

neesmeta v05-2 Instance 1
type: SoilDeposit
name: SJB01 Centrifuge Specimen - Nevada Sand 2
short description: SJB01 Nevada Sand Soil Deposit 2
has sensor setups: neesmeta UCSB2 merge Instance 72

neesmeta UCSB2 merge Instance 74
type: SpecimenSetup
has specimens: neesmeta UCSB2 merge Instance 10067
has specimens: neesmeta v05-2 Instance 1
long description: The dense and loose sand layers were placed by dry pluviation. A barrel pluviator was used to achieve 20% relative density in the loose sand layer. A clay slurry consisting of reconstituted bay mud was prepared with a mixer, placed on the loose sand surface, and consolidated under a hydraulic consolidation press to a vertical pressure of 240 kPa. The clay layer was constructed in two lifts with a drainage layer consisting of filter paper and small sand seams between the lifts. After consolidation, the river channel was carved into the slope using a thin metal wire. The model was then flooded with CO2 gas and placed under a vacuum of 25 in. Hg to remove the air in the sand. Water was dripped slowly into the model until the water level reached the desired height, which required approximately 13 hours. A sheet-aluminum rectangle with dimensions 26.5 x 17.0 x 6.5 cm (10.4 x 6.7 x 2.6 in.) was pressed in to the clay in the location where the pile cap would be placed, and the clay inside of the rectangle was excavated. The piles were driven into the saturated model 5 cm at a time using a drop hammer and the pile cap was progressively slid down in 5 cm-increments after each of the piles had been advanced 5 cm. The process was repeated until the piles had been advanced to the desired depth. A plumb line and spirit level were used to ensure that piles were driven in vertically. The bucket was tilted at an angle of 0.75o during pile driving to ensure that piles were close to vertical during the shakes. The bucket was at an angle of 1.4o downward from horizontal while spinning, therefore the tops of the piles were tilted 0.65o toward the north before the shakes. The pile cap was lowered into the excavation such that it was horizontal and its top was flush with the clay surface on the south side. Plaster was placed between the pile cap and sheetaluminum rectangle. A clear lexan cover was fastened to the top of the model container to prevent dessication of the clay due to air mo…
name: SJB01 Centrifuge Specimen Setup
has specimens: neesmeta UCSB2 merge Instance 75

neesmeta UCSB2 merge Instance 75
type: SoilDeposit
PL: 35-40
short description: SJB01 Bay Mud Soil Deposit
undrained shear strength: neesmeta UCSB2 merge Instance 10062
has sensor setups: neesmeta UCSB2 merge Instance 72
specific gravity: neesmeta UCSB2 merge Instance 10059
name: SJB01 Centrifuge Specimen - Bay Mud
saturated unit weight: neesmeta UCSB2 merge Instance 10060
preconsolidation pressure: neesmeta UCSB2 merge Instance 10061

neesmeta UCSB2 merge Instance 10062
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 10065
value: 45.0

neesmeta UCSB2 merge Instance 10065
type: Unit
description: i.e. preconsolidation pressure uom
name: kPa

neesmeta UCSB2 merge Instance 10059
type: FloatMeasurement
value: 2.65

neesmeta UCSB2 merge Instance 10060
type: FloatMeasurement
value: 16.2

neesmeta UCSB2 merge Instance 10061
type: FloatMeasurement
has unit: neesmeta UCSB2 merge Instance 10065
value: 240.0

NEESMeta Instance 50012
type: EventGroup
name: Test Phase 6A

neesmeta UCSB2 merge Instance 17
type: TechnicalReport
URI: /publicatons/Test_Structure_Descripton.PDF
title: Task 1.1.1 Shake Table Tests of a Simplified Two-Story Single-Family House
publication year: 2000

NEESMeta Instance 50017
type: Event
name: 6th Frequency Test of Phase 5

NEESMeta Instance 50025
type: Event
name: 6th Damping Test of Phase 5

neesmeta UCSB2 merge Instance 58
type: Task
name: Centrifuge Experiment for Piles uder Earthquake Loading
has event groups: neesmeta UCSB2 merge Instance 52
has site: neesmeta UCSB2 merge Instance 54
has role persons: neesmeta UCSB2 merge Instance 97
has event groups: neesmeta UCSB2 merge Instance 51
has role persons: neesmeta UCSB2 merge Instance 95
has event groups: neesmeta UCSB2 merge Instance 56
has infrastructure setups: neesmeta UCSB2 merge Instance 73
key words: Centrifuge
has event groups: neesmeta UCSB2 merge Instance 53
has publications: neesmeta UCSB2 merge Instance 16
has role persons: neesmeta UCSB2 merge Instance 96
has event groups: neesmeta UCSB2 merge Instance 55
key words: Lateral Spread
has event groups: neesmeta UCSB2 merge Instance 57
has role persons: neesmeta UCSB2 merge Instance 94
key words: Pile

neesmeta UCSB2 merge Instance 52
type: EventGroup
name: PDS02
long description: Six-pile group (2x3) with a large embedded pile cap. Lateral spreading of a moderately overconsolidated nonliquefiable clay crust overlying a medium-thick deposit of liquefiable sand overlying dense sand. Crust at 4o slope. Two Kobe motions. Centrifugal acceleration = 36.2g.

neesmeta UCSB2 merge Instance 51
type: EventGroup
name: PDS01
long description: Three single piles with various diameters and a two-pile group. Lateral spreading of a moderately overconsolidated nonliquefiable clay crust overlying a medium-thick deposit of liquefiable sand overlying dense sand. Crust at 2o slope. Three Kobe motions. Centrifugal acceleration = 38.1g.

neesmeta UCSB2 merge Instance 56
type: EventGroup
name: SJB02
long description: Six-pile group (2x3) with a large embedded pile cap. Lateral spreading of a highly overconsolidated nonliquefiable clay crust overlying a thin deposit of liquefiable sand overlying dense sand. Crust at 4.4o slope. Three Santa Cruz motions and two Kobe motions. Centrifugal acceleration = 38.1g.

neesmeta UCSB2 merge Instance 73
type: InfrastructureSetup
long description: A pile group consisting of six 0.73-m-outer-diameter prototype steel pipe piles was modeled using aluminum tubing with an outer diameter of 1.905 cm (0.75 in.) and a wall thickness of 0.089 cm (0.035 in.). An embedded aluminum pile cap with dimensions 26.5 x 17.0 x 6.5 cm (10.4 x 6.7 x 2.6 in.) provided fixed-head conditions. The soil profile was prepared with an 11- cm-thick deposit of moderately over-consolidated clay overlying a 12-cm-thick loose sand layer (Dr = 20%), overlying dense sand (Dr = 80%). All of the layers were built to a slope of 3o, and the model container was tilted at an additional angle of 1.4o during spinning for an overall slope of 4.4o. A “river channel�? was cut at 25o through the clay layer in the east-west direction near the north end of the container. FSB2, a flexible shear beam model container, was used in this test. A total of six shaking events were applied to the model at a centrifugal acceleration of 38.1 g. The shaking was applied transverse to the river channel in the north-south direction.
has secondary equipments: neesmeta UCSB2 merge Instance 67
short description: The equipment and sensors included in SJB01.
has secondary equipments: neesmeta UCSB2 merge Instance 62
has secondary equipments: neesmeta UCSB2 merge Instance 63
has secondary equipments: neesmeta UCSB2 merge Instance 65
has secondary equipments: neesmeta UCSB2 merge Instance 59
has primary equipments: neesmeta UCSB2 merge Instance 76
has secondary equipments: neesmeta UCSB2 merge Instance 61
has secondary equipments: neesmeta UCSB2 merge Instance 68
has secondary equipments: neesmeta UCSB2 merge Instance 66
has secondary equipments: neesmeta UCSB2 merge Instance 64
name: SJB01 CentrifugeSetup
setup figures: neesmeta UCSB2 merge Instance 34
has primary equipments: neesmeta UCSB2 merge Instance 77
has secondary equipments: neesmeta UCSB2 merge Instance 60

neesmeta UCSB2 merge Instance 55
type: EventGroup
long description: Six-pile group (2x3) with a large embedded pile cap. Lateral spreading of a highly overconsolidated nonliquefiable clay crust overlying a medium-thick deposit of liquefiable sand overlying dense sand. Crust at 4.4o slope. Three Santa Cruz motions and two Kobe motions. Centrifugal acceleration = 38.1g.
has events: neesmeta UCSB2 merge Instance 50
has events: neesmeta UCSB2 merge Instance 49
has events: neesmeta UCSB2 merge Instance 45
has events: neesmeta UCSB2 merge Instance 47
name: SJB01
has site: neesmeta UCSB2 merge Instance 54
has events: neesmeta UCSB2 merge Instance 46
has specimen setups: neesmeta UCSB2 merge Instance 74
short description: This is the fourth test in a series to study the behavior of pipe piles in laterally spreading ground during earthquakes. This test focuses on the response of a pile-group during lateral spreading.
has sensor setups: neesmeta UCSB2 merge Instance 72
has events: neesmeta UCSB2 merge Instance 48

neesmeta UCSB2 merge Instance 47
type: Event
name: SJB01_03
has site: neesmeta UCSB2 merge Instance 54
long description: Consisted of scaled versions of the ground motion recorded during the 1989 Loma Prieta Earthquake at the UCSC/Lick Lab.
short description: Small Santa Cruz

neesmeta UCSB2 merge Instance 46
type: Event
name: SJB01_02
short description: Small Santa Cruz
long description: Consisted of scaled versions of the ground motion recorded during the 1989 Loma Prieta Earthquake at the UCSC/Lick Lab.
has site: neesmeta UCSB2 merge Instance 54

NEESMeta Instance 31
type: WaveForm
sampling rate: neesmeta UCSB2 merge Instance 35
name: Level 5
description: 1994 Northridge Rinaldi
record unit: NEESMeta Instance 20001
scale factor: 1.0

NEESMeta Instance 50042
type: SensorGroup
name: Group H 1-2

NEESMeta Instance 19
type: EventGroup
has events: NEESMeta Instance 50019
has events: NEESMeta Instance 50024
short description: Experiments made right after phases 1-4
has events: NEESMeta Instance 20003
name: Test Phase 5
has events: NEESMeta Instance 10006
has events: NEESMeta Instance 50015
has events: NEESMeta Instance 50025
has events: NEESMeta Instance 50027
has events: NEESMeta Instance 10008
has events: NEESMeta Instance 50022
has events: NEESMeta Instance 50018
has events: NEESMeta Instance 50016
has events: NEESMeta Instance 50023
has events: NEESMeta Instance 50020
has events: NEESMeta Instance 50026
has events: NEESMeta Instance 50017
long description: No structural repairs were made on the structure from Phase 1-4. The second story of the test structure was constructed for Phase 5 testing. The first and second stories of the east and west walls were fully sheathed with no openings. The north and south walls were framed with openings and sheathed. The roof of the test structure was sheathed and tiled with clay tile. A35 shear transfer clips were installed on the east and west walls as specified in the plans. HTT22 holdowns were only installed at the ends of the east and west shear walls. HTT22 holdowns were installed in the north and south walls as specified per plans. CS16 inter-story holdown straps were only installed at the ends of the east and west shear walls. CS16 inter-story holdown straps were installed on the north and south walls as specified in the plans. The interior walls of the first and second story were framed as specified in the plans. The second floor diaphragm was glued with PL400 Subfloor Adhesive, nailed with 100% of the specified nailing, and diaphragm blocking was removed.
has events: NEESMeta Instance 50021

NEESMeta Instance 50019
type: Event
name: 1st Damping Test of Phase 5

NEESMeta Instance 20003
type: Event
name: 1st Seismic Test of Phase 5
long description: Seismic Test was performed on the test structure during the dynamic testing.
test type: Seismic
has wave form setups: NEESMeta Instance 27

NEESMeta Instance 10006
type: Event
has wave form setups: NEESMeta Instance 20007
test type: Frequency
name: 1st Frequency Test of Phase 5
short description: This is the first frequency test of Phase 5. The data was not biased nor filtered

NEESMeta Instance 50015
type: Event
name: 3rd Frequecy Test of Phase 5

NEESMeta Instance 50027
type: Event
name: 5th Seismic Test of Phase 5

NEESMeta Instance 50022
type: Event
name: 3rd Damping Test of Phase 5

NEESMeta Instance 50018
type: Event
name: 2nd Damping Test of Phase 5

NEESMeta Instance 50023
type: Event
name: 4th Damping Test of Phase 5

NEESMeta Instance 50026
type: Event
name: 4th Seismic Test of Phase 5

NEESMeta Instance 10012
type: SpecimenSetup
name: Experimental Setup for CUREe/Caltech Woodframe Task 1.1.1
setup figures: NEESMeta Instance 10011
setup figures: NEESMeta Instance 10010
long description: The test structure was anchored to the shake table by a rigid steel base that was bolted on the top plate of the table. The base will incorporate outrigger arms in the east and west directions to accommodate the footprint of the test structure. Note that a structural reaction wall was available near the shake table to perform quasi-static cyclic testing by linking the second floor of the test structure to the wall and using the shake table as a horizontal loading device.

NEESMeta Instance 10011
type: File
URI: /figures/figure3.jpg
description: Test Structure and Stell Base on Shake Table
name: Figure 3

NEESMeta Instance 40003
type: EventGroup
name: Test Phase 7

neesmeta UCSB2 merge Instance 10078
type: Unit
name: m
description: meters

NEESMeta Instance 50003
type: Task
name: Task 1.3.1 - Loading Protocol and Rate of Loading Effects

neesmeta UCSB2 merge Instance 1
type: Organization
name: California Department of Transportation
description: Caltrans
home page: http://www.dot.ca.gov
address: Sacramento, CA

NEESMeta Instance 30004
type: Sensor
sensor type: Accelerometer
name: E1
sensor type: ForceTransducer
sensor type: PorePressureTransducer
sensor type: Other
sensor type: AxialGauge
sensor type: DisplcamentTransducer
sensor type: MomentGauge
sensor type: ShearGauge
sensor type: LVDT

NEESMeta Instance 50011
type: EventGroup
name: Test Phase 6

NEESMeta Instance 50006
type: Person
first name: L. Thomas
last name: Tobin

NEESMeta Instance 20006
type: File
URI: /figures/figure10.jpg
description: Phase 5 Test Structure (View of North & East Walls)
name: Figure 10

NEESMeta Instance 50034
type: File
name: S4 - Foundation Details

NEESMeta Instance 50038
type: SensorGroup
name: Group N 1-11

NEESMeta Instance 10002
type: InfrastructureSetup
setup figures: NEESMeta Instance 10005
short description: The sensors included in the phase 5
setup figures: NEESMeta Instance 10004
long description: The test structure was instrumented with load cells, displacement measureing devices, and accelerometers for the tests of Phase 5.
name: Phase 5 Instrumentation Setup
setup figures: NEESMeta Instance 10003

NEESMeta Instance 10017
type: Sensor
sensor type: PorePressureTransducer
sensor type: LVDT
sensor type: ForceTransducer
name: A1
sensor type: DisplcamentTransducer
sensor type: Other
sensor type: Accelerometer
sensor type: AxialGauge
sensor type: ShearGauge
sensor type: MomentGauge

neesmeta UCSB2 merge Instance 20
type: Person
last name: Hyoub
first name: A.

NEESMeta Instance 50031
type: File
name: north_wall_description_phase5

NEESMeta Instance 29
type: WaveForm
scale factor: 0.86
record unit: NEESMeta Instance 20001
name: Level 3
description: 1994 Northridge Canoga Park
sampling rate: neesmeta UCSB2 merge Instance 35

NEESMeta Instance 30
type: WaveForm
name: Level 4
record unit: NEESMeta Instance 20001
sampling rate: neesmeta UCSB2 merge Instance 35
description: 1994 Northridge Canoga Park
scale factor: 1.2

David Fischer
type: Person
first name: David
person ID: 001112
title: Ph.D. Student
affiliation: NEESMeta Instance 7
last name: Fischer
address: Department of Structural Engineering, JOSE School of Engineering, University of California, San Diego, CA 92093-0085

NEESMeta Instance 50008
type: TechnicalReport
authors: neesmeta UCSB2 merge Instance 18
authors: neesmeta UCSB2 merge Instance 19
authors: neesmeta UCSB2 merge Instance 20
publication year: 2001
authors: neesmeta UCSB2 merge Instance 21
title: Development of a Testing Protocol for Woodframe Structures
authors: neesmeta UCSB2 merge Instance 22

neesmeta UCSB2 merge Instance 19
type: Person
last name: Parisi
first name: F.

NEESMeta Instance 50041
type: SensorGroup
name: Group B 1

NEESMeta Instance 20000
type: Task
key words: California Residential Construction
has event groups: NEESMeta Instance 19
has role persons: David Fischer
long description: One clear issue that emerged from the Invitational Workshop on Seismic Testing, Analysis and Design of Woodframe Construction, organized by Element 1 of the CUREe-Caltech Woodframe project, was the lack of understanding of the seismic behavior of woodframe systems. Very few numerical models capable of analyzing the seismic behavior of three-dimensional woodframe structures currently exist. In addition, only limited experimental data has been generated at the system level. The research program of Element 1 emphasizes testing and analysis at both the component level and system level. The research strategy of Element 1 incorporates five main research tasks, with one of two shake table tests of large-scale woodframe systems to be conducted in the early stage of the project. The results of these shake table tests can be used to shape the testing and analysis to be performed in the subsequent tasks.
key words: CUREe-Caltech Woodframe Project
has event groups: NEESMeta Instance 50012
name: Task 1.1.1 - Shake Table tests of a Simplified Two-Story Single-Family House
short description: Shake table test descriptions, test phase descriptions, instrumentation, and construction drawings
has event groups: NEESMeta Instance 40003
has infrastructure setups: NEESMeta Instance 10012
key words: Uniaxial Seismic Simulation
key words: UC San Diego Facility
has event groups: NEESMeta Instance 50013
has event groups: NEESMeta Instance 50010
key words: Two-Story Single-Family House
has role persons: NEESMeta Instance 55
has event groups: NEESMeta Instance 50011

NEESMeta Instance 50010
type: EventGroup
name: Test Phases 1-4

neesmeta UCSB2 merge Instance 71
type: SensorSetup
has sensors: NEESMeta Instance 30005
has sensors: NEESMeta Instance 30004
long description: Test Structure Absolute Acceleration, East-West Direction
name: Group E
short description: Absolute Acceleration to the East is Positive

NEESMeta Instance 50002
type: Task
name: Task 1.2 - Organization of an International Benchmark

neesmeta 1.1 Individual 333
type: File
name: Stee

CUREe Woodframe Project
type: Project
name: CUREe-Caltech Woodframe Project
has tasks: NEESMeta Instance 30000
has role persons: NEESMeta Instance 50007
key words: Testing and Analysis
NEES code: 0000220
has sponsors: NEESMeta Instance 14
key words: Field Investigations
key words: Education and Outreach
has role persons: NEESMeta Instance 50005
objectives: The primary objective of this shake table testing was to measure and quantify the building’s overall dynamic characteristics and its component responses for various construction configurations, and to document how the distribution of forces within the structure changes between the various configurations. Another objective was to establish relationships between ground motion severity, deflections, damage, and to provide data for defining realistic performance objectives. The data collected from the tests can now be used in the development of analytic models for complete buildings and the prediction of damage states and failure modes. The shake table test results also provide a basis for calibration of the project’s other individual component, full-scale building test results and their integration into analytic models.
acknowledgements: The project is funded by the Federal Emergency Management Agency (FEMA) through a grant administered by the California Governors Office of Emergency Services.
has role persons: NEESMeta Instance 55
key words: Building Codes and Standards
has tasks: NEESMeta Instance 50003
has role persons: NEESMeta Instance 50006
key words: CUREe-Caltech Woodframe Project
key words: Economic Aspect
has tasks: NEESMeta Instance 30001
has publications: NEESMeta Instance 50009
has tasks: NEESMeta Instance 50002
has tasks: NEESMeta Instance 20000
has role persons: David Fischer
has sponsors: NEESMeta Instance 50004
has publications: NEESMeta Instance 50008

NEESMeta Instance 50007
type: Person
last name: Cobeen
first name: Kelly

NEESMeta Instance 14
type: Organization
home page: http://www.curee.org
NEES code: 100001
name: Consortium of Universtities for Research in Earthquake Engineering
description: As of January 2004, there are 28 University Members in 16 states - 354 professor members

neesmeta 1.1 Individual 337
type: File
URI: /UMN_Data/Chapter3/Chapt3A/Table3.2.1

neesmeta UCSB2 merge Instance 69
type: SensorSetup
has sensors: NEESMeta Instance 10017
long description: Shake table absolute displacement, North-South direction
name: Group A

NEESMeta Instance 50032
type: File
name: S2 - Typical Details

NEESMeta Instance 30007
type: File
name: Acceleration Record of the 1st Seismic Test of Phase 5
URI: /sensorReading/phase5/5.S.1.B.txt

Composite Steel Frame-RC Infill Wall
type: Project
objectives: 4) To provide data for the validation and calibration of computational models of this structural system, such as nonlinear, cyclic finite element analysis, which are being developed in separate research effort at the University of Minnesota.
short description: A series of prototype structures were designed to initiate investigation of the linear elastic response of the system, and to identify typical member sizes that have the potential to provide acceptable seismic performance. A preliminary design guideline was proposed for designing the prototype structures.
objectives: 1) To investigate the cyclic behavior of composite steel frame-RC infill wall structural systems by performing cyclic static loading tests on a one-third scale, two-story, one-bay specimen. Strength and stiffness deterioration, energy dissipation capability, deformation capacity of the structural components, and proportions of the forces resisted by different members are the major concerns in the investigation.
long description: The primary part of this research was conducting a cyclic loading test on one two-story, one-bay specimen, which represented the bottom two stories of a six-story prototype structure at approximately one-third scale. The steel frame comprised W5´19 wide flange columns and W8´13 wide flange beams. The columns and beams were joined through partially-restrained (PR) connections, which comprised top and seat angles and double web angles. The 3.5 inch thick infill wall was cast using regular concrete, with 0.5% reinforcement ratio in both the horizontal and vertical directions. Headed studs were used as the interface connectors, and were confined by steel cages to increase their strength and ductility.
has role persons: Arturo Schultz pi
name: Composite_Steel_Frame-RC_Infill_Wall
acknowledgements: I would like to acknowledge the financial support for this research, provided by the National Science Foundation (Grant No. CMS-9632506) under Dr. Shih-Chi Liu as part of the U.S.-Japan Cooperative Research Program, Phase 5 on Composite and Hybrid Structures, and by the University of Minnesota.
objectives: 3) To establish simple but rational design guidelines and suggestions for analysis modeling for this composite system based on the experimental results, as well as research results from other sources.
NEES code: 0000229
has role persons: Xiangdong Tong s
has sponsors: NSF
has tasks: UMN Composite infill wall test
has role persons: Jerome Hajjar cpi
has sites: UMN Site
objectives: 2) To determine the effect of the strength and ductility of the headed stud connectors on the seismic behavior of this composite system, and to explore a feasible construction method of using headed stud connectors in this composite system.
has publications: Xiangdong Tong thesis 2001
executed by: Civil Engineering UMN

NEESMeta Instance 30003
type: SensorGroup
name: Group E 1-12
sign convention: Absolute Acceleration to the East is Positive
measurement: Test Structure Absolute Acceleration, East-West Direction

NEESMeta Instance 50044
type: SensorGroup
name: Group Q 1-2

CEE UIUC
type: Organization
address: Newmark Civil Engineering Laboratory, 205 North Mathews Avenue, Urbana, IL 61801
name: Department of Civil and Environmental Engineering, University of Illinois at Urbana-Champaign
home page: http://cee.uiuc.edu/

NEESMeta Instance 50040
type: SensorGroup
name: Group S 1-5

neesmeta UCSB2 merge Instance 44
type: Project
has role persons: neesmeta UCSB2 merge Instance 96
has tasks: neesmeta UCSB2 merge Instance 58
start date time: 1999-02-23
key words: Lateral Spread
has sponsors: neesmeta UCSB2 merge Instance 1
has role persons: neesmeta UCSB2 merge Instance 94
NEES code: 0000230
end date time: 2000-03-16
has sites: neesmeta UCSB2 merge Instance 54
key words: Centrifuge
acknowledgements: This model test was funded by Caltrans under the direction of Abbas Abghari. The contents of this report do not necessarily represent a policy of that agency or an endorsement by the state government. The authors would like to acknowledge the suggestions and assistance of Abbas Abghari, Angel Perez, Dan Wilson, Tom Kohnke, Chad Justice, Tom Coker, Bill Sluis, Kiran Manda, Michael White, David Stevens and Hideo Nakajima.This model test was funded by Caltrans under the direction of Abbas Abghari. The contents of this report do not necessarily represent a policy of that agency or an endorsement by the state government. The authors would like to acknowledge the suggestions and assistance of Abbas Abghari, Angel Perez, Dan Wilson, Tom Kohnke, Chad Justice, Tom Coker, Bill Sluis, Kiran Manda, Michael White, David Stevens and Hideo Nakajima.
has role persons: neesmeta UCSB2 merge Instance 95
name: Behavior of Piles in Laterally Spreading Ground During Earthquakes
has role persons: neesmeta UCSB2 merge Instance 97
has publications: neesmeta UCSB2 merge Instance 16
key words: Pile

neesmeta UCSB2 merge Instance 10077
type: Unit
name: cm
description: centimeters