Comments:

Flat Nested Threaded Embedded

Oldest First Newest First

Author	Thread:
Todd Bergland	Contract pay items UML model document posted Posted: Monday, March 28, 2005 8:32 AM (EST) Below you will find comments from the Minnesota Department of Transportation as it pertains to the Contract Pay Item model.  The comments are isolated by the individual classes. Mn/DOT would like to see the following information added or clarified in the document.   DesignProject Class      - Provide an option for a Federal Work Type    - Provide an option for a Federal Project Number   DesignProjectPayItem        - What is the intention of this class? Does this class refer to tabulations of incidentals?   DesignProjectFunding and ReferenceFundingSource      -  Do we need more information regarding funding such as stationing or offsets of the element included within the funding?  Or is this covered within another schema or inheriting from another class?
Sum Lin	Contract pay items UML model document posted Posted: Monday, April 04, 2005 5:18 PM (EST) Todd, We are investigating how best to include Federal Work Type, it is something that needs to be coordinated with the Bid Package in the Construction/Materials business areas. DesignProjectPayItem is different from ReferencePayItem in that the ReferencePayItem is an item from a particular spec book and is not specific for a project.  The DesignProjectPayItem has attributes such as estimatedQuantity etc... that is project specific during the design phase.  Note that a given pay item may be sliced up into different “chunks”, different funding, different location etc...We intentionally prefixed the pay items with “design” to avoid confusion when it moves to another phase of the project life cycle.  For example, the estimatedQuantity in the DesignProjectPayItem class is a design estimate.  When it gets to construction, there may be other quantities such as authorized, installed, paid on, in place etc...that is not relevant in the design business area. In a design system, funding may be applied based on specific station ranges.  However, a design element subjected to different fundings (by station ranges for example) will be sliced up and rolled into different individual quantities.  The same is done today in aecXML, a pay item is sliced up into different chunks of quantities, each chunk for a different funding.  The station range is only needed in the design system in order to calculate the funding split, but once it is split, all is needed in the estimation system is how much of each pay item is subjected to different fundings. Regarding station offset locations, associated with each DesignProjectPayItemGroup is an optional location which has minimum, maximum, begin, end location in terms of latitude/longitude, station/offset, XY coordinates.  However, this is intended to convey location information for a project, or a portion of a project (eg. a bridge), but not broken down to the level of each individual graphic element.  We looked into that possibility, but since the primary purpose of this schema is to allow data to transfer between design and estimation, and most estimation system do not have a data model to capture design information to that level of granularity.
Bob DeHoff	Federal Work Type Classifications Posted: Monday, April 11, 2005 2:21 PM (EST) Todd Bergland recommended the addition of the Federal Work Type to the DesignProject class.  His comment was in reference to the ContractPayItem schema package, but it could also apply to the Proposal class in the BidPackage package and the Contract and ConstructionProject classes in the ProjectConstructionStatus and  ConstructionProgress packages. There is an FHWA work type classification standard.  A document listing examples of these work type codes is posted in the Construction/Materials Working Group Documents section here: http://www.transxml.net/Construction+Materials+Schema/Group+Documents/Downloads_GetFile.aspx?id=495 We are working with FHWA to locate the FHWA document that defines this standard. The Proposal, Contract, and ConstructionProject classes have a ConstructionType attribute that is associated with a ConstructionType code list stereotype. Question: Does the Federal Work Type meet the work type classification needs for projects and contracts at all stages of the lifecycle or is a separate agency-extensible work type classification scheme also needed? This question is being discussed in the Construction/Materials Working Group Forum.  We encourage your participation in this discussion.
Sum Lin	Contract pay items UML model document posted Posted: Wednesday, May 11, 2005 3:01 AM (EST) The second draft of the Design Project Pay Item UML model has been posted in the Survey/Design Schema Working Group Documents area: http://www.transxml.org/Survey/Group+Documents/Downloads_GetFile.aspx?id=529 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 additional project ID schemes to DesignProject. Added federalWorkType to DesignProject. Added referencePayItemID to ReferencePayItem. Certain attributes such as description are made optional.
Sum Lin	Contract pay items UML model document posted Posted: Wednesday, May 11, 2005 12:57 PM (EST) Todd, Draft 2 is posted.  We have added provisions for alternate project IDs, and you can specify more than one, as well as federal work type to the schema.  Please advise if this addresses MNDOT's requirements. Sum
Sum Lin	Contract pay items UML model document posted Posted: Tuesday, June 07, 2005 12:47 AM (EST) Additional annotations added to draft 2.   New document may be downloaded from: http://www.transxml.org/Survey/Group+Documents/Downloads_GetFile.aspx?id=535 Feedback appreciated. Sum
Sum Lin	Contract pay items UML model document posted Posted: Tuesday, September 27, 2005 1:54 PM (EST) One more updated draft of the CPI model to take care of some naming consistency issue. http://www.transxml.org/Survey/Group+Documents/Downloads_GetFile.aspx?id=556 Sum