CCOM 4.1.0-RC1

CCOM 4.1.0-RC1 is a Release Candidate of a backward compatible release that makes several fixes and improvements over CCOM 4.0.0. This version of CCOM was used as part of the recent OIIE OGI Pilot phase 3.1

The main changes in this release include:

  • deprecation of the term ‘Attribute’ in preference for ‘Property’
  • Requests extended with RequestForInformation subtype and hierarchies of requests
  • addition of Model Variants, alongside Model Revisions, to improve device model property sheets

A full changelog will be included in the final release.

A number of enhancements were identified during the OIIE OGI Pilot phase 3.1. The changes will be incorporated into an updated release candidate in the near future.

Release Date: March 20, 2020
Version: 4.1.0-RC1
Release Status: Release Candidate

CCOM 4.0.0

CCOM 4.0.0 is a non-backward compatible release that makes substantial changes to simplify, rationalise and provide clarity to users of the standard compared to the 3.2.3 release. It is also the first time that it has been extracted from the OSA-EAI in order to provide greater flexibility for release management.

The fundamental new features of the 4.0.0 release include:

  • Data sheet definitions and data sheets (AttributeSetDefinition and AttributeSet) to support the ISDD Project
  • Temporal data structures to support effective dated records
  • Auditing of assessments
  • Support for parent/child solution packages
  • Multi-parameter attributes
  • TaxonomySets to group multiple taxonomies
  • Contextual data between Entities and Documents to support diagram X,Y positioning

Changelog

Release changes

  • Rename CCOM to Common Collaborative Object Model. It is no longer Conceptual.
  • Add CRIS documentation to UML and XSD
  • Add HTML documentation describing release. Some is derived from the OGI Pilot documentation.
  • Add Changelog

Model and Reference Data Changes

  • Rename Entity.GUID to UUID
  • UUID is mandatory – it was optional previously to support Query-By-Example, but now a different query schema will be used.
  • Change Entity.Tag to ShortName and Entity.Name to FullName. This allows multiple names for different languages/locales
  • Entity has EffectiveStatus, which has a EffectiveDate and link to a StatusType. This allows for temporal status (e.g. setting active date in the future)
    • Remove Start/End dates for ValidFor
    • Remove Valid prefix
  • Rename UnitType to UnitOfMeasure
    • Rename TextWithUnit to TextWithUOM
  • Rename ReferenceUnitType to UOMQuantity
  • Rename Enterprise to Organization and EnterpriseType to OrganizationType
  • Rename AssetOnSegmentEvent to AssetSegmentEvent
  • Change Request.FromSystem to FromAgent
  • Measure.Value should be a UNCEFACT NumericType
  • MonetaryAmount.Value should be a UNCEFACT NumericType
  • Separate UnitType and Enumeration
  • Merge SiteType into SegmentType
    • Subclass Site from Segment
    • Remove Equivalent Segment associations
    • Move MonitoredEntity.IsTemplate and Template to Segment
  • Rename UOMQuantities Length (L) and Time (T) to remove parenthesis
  • Rename UOMQuantities Latitude, Longitude, Slope curve of Signal Processing Filters to fix spelling mistakes and consistent capitalization
  • Rename UOMQuantitiy Flow Unit for Gallons etc. and Frequency / Hertz to remove Unit of Measure labels
  • Rename PossbleEquivalency to Equivalency
  • Only Sample and not measurement should be hierarchical
  • Rename and extend from XSD types
    • Rename URILink to URI from anyURI
    • Rename XMLAny to XML from anyType
    • Use alphabetical order for ValueClass and ValueContent
  • Remove embedded units of measure
    • MeasurementLocation.TransducerOrientationAngleDegrees to TransducerOrientationAngle
    • VectorMeasurement.DirectionDegrees to Direction
  • All schema restricted enumerations derive from xs:string
  • Move Data from Measurement to subclasses and make Measurement abstract.
    • Create SingleDataMeasurement
    • Rename GridMeasurement to MeasurementGrid and associate with SingleDataMeasurement. This is because multiple Grids can be drawn for a BLOB.
    • Create FFTMeasurement, CPBMeasurement, TimeWaveformMeasurement
  • Remove Reference time from OffsetArrayMeasurement – this is now the Start time from Measurement
  • Change Health Assessment association to TimestamppedEvent changed to “substantiated by”. This more aligns with original requirement in CRIS.
  • Allow all assessments to be audited.
  • Rename WorkAudit and WorkAuditType to WorkStatus and WorkStatusType
  • Rename Materiel to Material. Less military connotations.
  • EngineeringStudy and Algorithm inherit from Entity.
  • EngineeringStudy and Algorithm use the same template approach as Segment (i.e. IsTemplate, Template fields)
  • Attribute Reference Data ReadinessTypes to DLA Federal Condition Codes
  • Remove Entity.LastUpdatedInfoSource. There should only be a single system of record for an entity.
  • Remove DataSheet network
  • Remove MIMOSAClass
  • Remove equivalent relationship between Model->Segment and Asset->Segment
  • Remove equivalent relationship between InfoSource->Asset
  • Remove AssetConnection relationship from Site
  • Remove Conversion Scale and Offset for Currency and Currency Exchange Rate Units of Measure
  • Electrical Circuit and Measurement Location MeasurementLocationTypes
  • Remove Manufacturer. Model and Asset will point to Organization as the manufacturer
  • Remove Boolean in favor of xs:boolean
  • Remove WorkItemType – this is more likely a presentation concern
  • Remove MonetaryAmount – use Measure instead
  • Remove EquivalentAsset for InfoSource and Agent – attributes can be assigned directly
  • Remove Asset/SegmentTypeModelTemplate – these were for data sheets and are now supported using AttributeSetDefinition
  • Add multiple Descriptions for objects
  • Add parent/child to Solution Package to mirror Work Order
  • Attribute Set and Group
    • Remove Segment Group Reference Data
  • Attribute Set Definition, Attribute Group Definition, and Attribute Definition
    • MinOccurs should be xsd:nonNegativeInteger and MaxOccurs should be xsd:positiveInteger or *
  • Link AttributeDefinition from BaseType and CCOMClass
    • Remove ValidAttributeTypeForCCOMClass
  • Add InfoSource Type
  • Add URL to InfoSource
  • Add Document, DocumentType, and connections from Segment, Model, Asset to Document
    • Migrate BLOBContentType from CRIS and making this DocumentType rather than AttributeType
    • Have both URL and Content (BLOB) attributes
    • HypotheticalEvent points to Document instead of embedding content
  • UOMQuantity points to a ReferenceUnitOfMeasure
    • Add Box, Carton, Pallet UnitOfMeasure for UOMQuantity Materiel Issue Unit
  • UOMQuantities to MeasurementLocationTypes
  • LifecycleStatus for Segments and Assets
    • LifecycleStatusTypes in Reference Data
  • MultiParameter values for Attributes
  • Add bidirectional AssetType association with MaterialMasterItem. Missing from CRIS.
  • Add Asset Owner History as AssetOwnerEvent
  • Add TaxonomySet
    • Change Reference Data to use TaxonomySet
  • Add EngineeringStudyEntryFor… relationships. Missing from CRIS.
  • Add MeasurementLocationType and AgentRoleType associations from Port for Algorithm templates.
  • Allow SetAttributes directly on AttributeSet and similarly, AttributeDefinition directly on AttributeSetDefinition. This is to support applications where simple (not grouped) property lists are used.
  • Explode Document-Entity relationship to an association class to support contextual data, e.g. X,Y coordinates for diagrams.
  • Use ccom4 namespace as this will not be published as an OSA-EAI release.
  • Simplify Entity.RegistrationInfoSource to Entity.InfoSource.
  • Remove ControlledSite/ControllingOrganization association. CRIS had two enterprise associations due to UID rules, so with UUIDs, this is not needed.
  • Remove TextWithUOM. This is not needed now that enumerations have been split from UOM.
  • Attribute has a choice between associating with a Type or Definition. This is because an AttributeDefinition can reference an AttributeType (along with other data/constraints).
  • An AttributeGroup can reference a definition. This allows more granular conformance checking of group content.

Reference Data Changes

  • Add reference data in a human readable Excel format.
  • Corrections to force-related UOMs in reference data.
  • Remove symbol from Length UOM Quantity name.
Release Date: September 30, 2016
Version: 4.0.0

MIMOSA is a member of both the OpenO&M and the Standards Leadership Council.

© 1998 - 2024 MIMOSA. All rights reserved.

Up ↑