Comments:

Flat Nested Threaded Embedded

Oldest First Newest First

Author	Thread:
Bob DeHoff	Comment from Mike Hruska Posted: Monday, April 11, 2005 9:26 AM (EST) Mike Hruska posted the following message to the general discussion forum.  I am copying it here so that the Working Group can discuss it...  Just a few questions regarding the ReferenceTestMethod Class- Would it be more beneficial to identify the SDO (Standards Development Organization) rather than just indicating the boolean condition of whether or not it was an AASHTO test? Beyond just the test method, is the version of the test method used important? Mike - These are both good points.  For ReferenceTestMethod, the AASHTOTest attribute will be replaced with a testSDO attribute and a testVersion attribute will be added. Thanks for your input, Bob
Todd Bergland	Materials Sampling and Testing UML model posted Posted: Wednesday, April 13, 2005 8:23 AM (EST) Bob, Below you will find coments from the Mn/DOT Office of Materials. I apologize for the delay in moving this forward. Mn/DOT looks forward to your review and feedback. I'm responding for the Office of Materials in regards to the TransXML Material Sampling and Testing Package. I am including comments from the IT staff who have been actively involved with the development of our current laboratory information management system (LIMS). 1. Integration of information from others. Mn/DOT would like to include information from the Independent Assurance Testers, contractors, 3rd party vendors, etc. 2. Tracking of failing test reports. No feedback loop from the field to the lab. 3. No identification of person performing the test. 4. Sample location. Location Class contains coordinates or references to curvilinear elements. The Location Class should be applied to the sample collection site, where appropriate. 5. Three dimensional coordinate system should be available. 6. Contract changes regarding failing material should include automatic deducts. No "backsheet" items (Mn/DOT term). 7. Electronic address needed. 8. Incomplete material category. Needs to include paints, seeds, curing compounds, epoxy, Portland and asphalt cements, other cementitious materials, other chemical tests. 9. Material Plant Type should include foundries, precast plants, plastic pipe producers, other vendor facilities. 10. Lab/field test result comparison.
Bob DeHoff	Sample location Posted: Sunday, April 17, 2005 2:15 PM (EST) Todd, thanks for your feedback.  Can you elaborate further on your 5th comment... “5. Three dimensional coordinate system should be available.“ Is this in reference to linear referencing?  Spatial coordinates?  Perhaps up or down from a curvilinear element by some additional height or depth? Thanks, Bob
Bob DeHoff	Materials Sampling and Testing UML model posted Posted: Thursday, April 21, 2005 8:47 AM (EST) Todd, Thank you for your input.  Following are responses to your input. It would be helpful if you could elaborate further in several areas. I have put those in bold. 1. Integration of information from others. Mn/DOT would like to include information from the Independent Assurance Testers, contractors, 3rd party vendors, etc. Can you elaborate more on the types of information and the aspects of the business that they relate to? Our objective under this project is to address the construction progress and materials sampling and testing information that is required to make a progress payment. Do you see this additional information from other sources as being required to meet that objective? 2. Tracking of failing test reports. No feedback loop from the field to the lab. Good point. We will add a testOutcome to the SampleTest class. Can you elaborate more on the field/lab feedback loop? Does that aspect of the workflow come into play in the reporting of the information required to make a progress payment? 3. No identification of person performing the test. The "test/tester" association between the SampleTest and AgencyStaffMember classes represents the person who performed the test. Is there additional information that is needed? 4. Sample location. Location Class contains coordinates or references to curvilinear elements. The Location Class should be applied to the sample collection site, where appropriate. Good point.  We will add an association between the MaterialSample and Location classes to represent the location where the sample was taken. 5. Three dimensional coordinate system should be available. As I mentioned in a separate posting, can you elaborate further on this? Is this in reference to linear referencing? Spatial coordinates? Perhaps up or down from a curvilinear element by some additional height or depth? 6. Contract changes regarding failing material should include automatic deducts. No "backsheet" items (Mn/DOT term). Can you elaborate further? Does this aspect of the workflow come into play in the reporting of the information required to make a progress payment? It sounds more like something related to the actual calculation of the payment once the progress information has been received. What is a "backsheet" item? 7. Electronic address needed. Please elaborate further. Is this in reference to email addresses of agency and/or contractor personnel? URL references to specification documents that are posted on line? Something else? 8. Incomplete material category. Needs to include paints, seeds, curing compounds, epoxy, Portland and asphalt cements, other cementitious materials, other chemical tests. 9. Material Plant Type should include foundries, precast plants, plastic pipe producers, other vendor facilities. The MaterialCategory and MaterialPlantType classes are code lists, and are therefore extensible. The list of values provided are for illustration purposes only. 10. Lab/field test result comparison. Please elaborate further. Is this in reference to recording of test results comparison in the model? Does this aspect of the workflow come into play in the reporting of the information required to make a progress payment? Thanks, Bob
Bob DeHoff	Materials Sampling and Testing UML model draft #2 posted Posted: Tuesday, May 03, 2005 9:29 PM (EST) The second draft of the Construction Progress UML model has been posted in the Construction/Materials Schema Working Group Documents area here: http://www.transxml.org/Construction+Materials+Schema/Group+Documents/Downloads_GetFile.aspx?id=522 Comments on this draft are requested by May 20th, 2005.  Please post your comments as responses to this thread.  If you need more time for this review, or you have any questions please send an email to transxml@camsys.com. Following is a summary of the changes made to the first draft: Added MaterialSampleControlType class. Changed MaterialSample.sampleID from type ID to String. Renamed MaterialSample.geographicalUnitType to geographicalUnit. Removed MaterialSample.statusType. Redundant with ConstructionProjectPayItem.itemStatus. Removed MaterialSample.town Removed MaterialSample.standardRemark Removed MaterialSample.locationDescription and added Location association to MaterialSample. Changed MaterialSample.sampleSize from type Integer to type Measure and removed MaterialSample.sampleUnit. Removed MaterialSample.effectiveDate. Added MixDesignType code list for MaterialSample.sampleMixDesignType. Added BuyUSARequirements code list for MaterialSample.buyUSARequirementsType. Changed SampleTest.labID type from ID to String. Replaced association between SampleTest and AgencyStaffMember with a new SampleTester union class associated with SampleTest. The union enables the SampleTester to be either an AgencyStaffMember or an OrganizationEmployee such as an employee of an external lab. Changed ReferenceMaterial.materialID from type ID to String. Added ReferenceMaterial.shortName, longName, and description. Changed ReferenceMaterial.sampleSize to type Measure and removed previously separate ReferenceMaterial.sizeCode. Changed ReferenceMaterial.defaultUnit to englishUnit and added metricUnit. Changed ReferenceTestMethod.testMethodID from type ID to String. Removed ReferenceTestMethod.testNumber. Replaced ReferenceTestMethod.AASHTOTest with ReferenceTestMethod.testSDO of type SDOType, which is a code list stereotype class. Added ReferenceTestMethod.testVersion Renamed ContractSampleAndTestRequirement.sampleLocation to sampleArea. Removed ContractSampleAndTestRequirement.satisfiedRepresentedMaterialQuantity. It can be derived from other elements. Removed ContractSampleAndTestRequirement.sampleCalculatedMaterialQuantity. It can be derived from other elements. Renamed MaterialPlant.ID to materialPlantID and changed type from ID to String. Added association between MaterialPlant and Location. Added MaterialPlant.lastInspectedDate. Added MaterialPlant.active. Added AgencyStaffMember.districtOffice.
Daryl Bushika	Materials Sampling and Testing UML model draft #2 posted Posted: Friday, August 12, 2005 8:51 AM (EST) New York is in the process of implementing SiteManager, and I am glad to see the similarity of your schema(s) to SiteManager.  I have noticed a few gaps, however, or maybe I'm just not looking in the right class.  In the SampleTest Class, there is no attribute to tell which test method is being performed, just dates, LabID, Test Number, and output  A Sample Status should be added to the MaterialSample Class, to allow for Sample tracking (sample received at lab, in testing, testing complete).  Also, a Test Status (testing, test complete-waiting for approval, retest, approved, etc) as a finer breakdown of Sample Status (since multiple tests can be running on the same sample at the same time) should be included in the Sample Test Class. Daryl Bushika, P.E.
Bob DeHoff	Materials Sampling and Testing UML model draft #2 posted Posted: Monday, August 22, 2005 3:17 PM (EST) Thanks for your feedback Daryl. The test method performed on a sample is specified through the association of the SampleTest class with the MaterialTest class.  The MaterialTest class identifies the specific test(s) (ReferenceTestMethod class) that are performed on a specific material (ReferenceMaterial class).  These tests on the material may be further constrained by sampling and testing requirements specific to the contract (ContractSampleAndTestRequirement class).  This is one of the more complex parts of the model.  The ReferenceMaterialAndTest Context Diagram on page 35 of the latest MaterialSamplingAndTesting Package document dated May 3, 2005 shows these associations. Regarding the Sample Status, you are absolutely right.  We need to add that to the MaterialSample class.  We will add a sampleTest attribute to MaterialSample.  We will also create an associated enumeration stereotype class called SampleTest that will have the following standard values for sampleTest: received, inTesting, and testingComplete. Regarding the Test Status on the SampleTest class, there is a TestOutcome attribute that we intended to represent the test status.  In retrospect, testStatus would be a more accurate name for that attribute.  We will rename testOutcome to testStatus.  We will also create an associated enumeration stereotype class classed TestStatus that will have the following standard values for testStatus: inProgress, retest, testCompleteWaitingForApproval, and approved. Note that the association between MaterialSample and SampleTest is 1 to 0..n, so the model enables tracking of multiple SampleTests per MaterialSample.  Given the changes discussed above, each separate sample will have an associated SampleStatus and each test on each sample will have an associated testStatus specific to that test on that sample.
Todd Bergland	Materials Sampling and Testing UML model posted Posted: Friday, October 07, 2005 1:34 PM (EST) This is in response to the Material Posted by Mn/DOT on Thursday, April 21, 2005 8:47 AM (EST) 1. Yes, certificate of compliance type of material acceptance. 2. This flow of information would be necessary to determine acceptability of material before payment. 3. Does this association allow comparison and identification of testers for split or companion samples? If a discrepancy occurs, it is beneficial to review both procedure (individual) and equipment. 5. I'm not sure how you want to proceed with this. Either x, y, z coordinates based on station, offset, and depth or GIS coordinates with depth. 6. The automatic calculation of reduction in unit price would result in accurate progress payment and satisfy the audit trail as action taken before payment. 7. The intent is electronic distribution or access of information. I was thinking primarily email but an electronic posting with a URL address may be acceptable. 10. The use of "field" tests by agency or contractor personnel are verified by companion/comparison testing by the laboratory. There are acceptable tolerance limits between two or more test results and these should be reviewed before payment. If these answers don't make sense, please let me know. I did have some questions regarding the depth of response necessary for the vendor. I don't want to confuse the issues with in-depth contractual or technical responses.
Bob DeHoff	Materials Sampling and Testing UML model posted Posted: Wednesday, November 02, 2005 2:48 PM (EST) Todd, Thank you for your clarifications.  Following is additional feedback on your responses. 1. The certificate of compliance type of material acceptance is represented in the model as the contractAcceptanceTestMethod specified by a ContractSampleAndTestRequirement and recorded for a specific MaterialSample. 2. The testStatus of a SampleTest would be used to track the status of tests. 3. Split or companion samples are represented in the model by the RelatedSample association that enables one MaterialSample to be associated with another MaterialSample. 5. The Location class enables locations to be specified in three dimensional coordinate systems. 6. The testStatus of a SampleTest can be used to identify test results that have not been accepted.  Payment adjustments can be made based on the test outcome. 7. The model includes email addresses of all agency and contractor personnel. 10. Due to the scope limitations of this TransXML project, tracking of the details of actual tests performed is beyond the scope of this initial TransXML initiative.  This model only tracks tests performed at a high level.  More detailed test information could be added to the TransXML model in future TransXML versions.