MCA

From GICLWiki
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
[[Category:Engineering format]]
 
[[Category:Engineering format]]
−
'''Title(s):''' [[Title::I-DEA Web Access file (Crushed Ascii)]]  
+
'''Title(s):''' [[Title::I-DEAS Web Access file (Crushed Ascii)]]  
  
−
'''Version ID:''' [[Version ID::]] - Identification or version number of the engineering format.
+
'''Version ID:''' [[Version ID::No longer in use]]  
  
−
'''Date released:''' [[Version Date released::]] - Date that the version was released.
+
'''Date released:''' [[Version Date released::N/A]]  
  
−
'''Date:''' [[Format Date::]] - Date the format was created (YYYY-MM-DD)
+
'''Date:''' [[Format Date::1999-04-14]]  
  
−
'''Creator(s):''' [[Creator::Entity Template]] - The creator or original author of the engineering format.
+
'''Creator(s):''' [[Creator::Structural Dynamics Research Corporation (SDRC)]]  
  
−
'''Contributor(s):''' [[Contributor::]] - The current maintainers of the engineering format.
+
'''Contributor(s):''' [[Contributor::Siemens PLM Software]]  
  
−
'''Relationships:''' - Relationships that the engineering format has with organizations, other formats, etc.
+
'''Relationships:'''  
  
−
* '''Previous Version(s):''' [[Previous Version::]] - Any engineering format that is a previous version format of this one.
+
* '''Previous Version(s):''' [[Previous Version::N/A]]  
  
−
* '''Contains:''' [[Contains::]] - Any engineering format that is contained by this format.
+
* '''Contains:''' [[Contains::N/A]]  
  
−
* '''Syntax Format(s):''' [[Syntax Format::]] - Any syntax formats that the engineering format may use.
+
* '''Syntax Format(s):''' [[Syntax Format::N/A]]  
  
−
* '''Family Format(s):''' [[Family Format::]] - Any family formats to which the engineering format may belong.
+
* '''Family Format(s):''' [[Family Format::NX]]  
  
−
'''Description:''' [[Description::]] - Main description of the format, which can give extra information not categorized.
+
'''Description:''' MCA was used by I-DEAS Web Access, a program that was merged with Unigraphs to from Unigraphs NX, now known as NX.
  
−
'''History:''' [[History::]] - Historical description depicting major events surrounding development, creation, and maintenance of this format.
+
'''History:''' I-DEAS Web Access was announced in 1999 by SDRC with the foal of providing web-based collaboration and visualization for use with I-DEAS software. SDRC was bought by Electronic Data System (EDS) in 2001. EDS also acquired UGS Corp, the makers of Unigraphs. EDS merged both I-DEAS and Unigraphs into one product, NX. In 2007, UGS was bought by Siemens AG who renamed the company to Siemens PLM Software.
  
−
'''Example(s):''' [[Example::Example Template]] - Information and example models of the engineering format.
+
I-DEAS Web Access files are no longer used, as the program was merged into NX in 2001, but some programs are still able to read the files, for example [http://www.actify.com/products/importers/file-formats], [http://www.solidview.com/cadinterfaces.html], and [http://www.unifiedcad.com/Viewer_Specs.html].  
  
−
'''Identifier:''' [[Identifier::]] - A URL or other identifier that refers to the engineering format.
+
'''Example(s):''' [[Example::None]]  
  
−
'''Documentation:''' [[Documentation::Documentation Template]] - Information in general about the engineering format.
+
'''Identifier:''' [[Identifier::None]]  
  
−
'''File Extensions:''' [[File Extension::]] - Extensions of the engineering format, excluding the dot.
+
'''Documentation:''' [[Documentation::N/A]]  
  
−
'''Applications:''' - Applications that the engineering format uses.
+
'''File Extensions:''' [[File Extension::MCA]]
  
−
* '''Native application(s):''' [[Native Application::Engineering Format Application Template]] - Applications which are primarily designed to specifically run this engineering format.
+
'''Applications:'''  
  
−
* '''Interoperable applications:''' [[Interoperable Application::Engineering Format Application Template]] - Applications which can read or write files of this format, but are not native applications for the format.
+
* '''Native application(s):''' [[Native Application::None]]
  
−
'''Magic numbers:''' [[Magic Numbers::]] - Unique identifying characters at the beginning of files for this engineering format.
+
* '''Interoperable applications:''' [[Interoperable Application::Actify, SolidView, Unified CAD]]  
  
−
'''Format(s):''' [[Format::]] - The MIME file types.
+
'''Magic numbers:''' [[Magic Numbers::N/A]]  
  
−
'''Rights:''' [[Rights::]] - The name or type of the license for the engineering format. Examples: BSD-style license, Apache License, Proprietary license
+
'''Format(s):''' [[Format::N/A]]  
  
−
'''Sustainability Factors:''' - Facts about the sustainability of this particular engineering format.
+
'''Rights:''' [[Rights::N/A]]
  
−
* '''Standardization:''' [[Standardization::]] - Information regarding standardization attempts with this format.
+
'''Sustainability Factors:'''  
  
−
* '''Adoption:''' [[Adoption::]] - Information about how this format has been adopted by other organizations.
+
* '''Standardization:''' [[Standardization::N/A]]  
  
−
** '''Licensing and patent claims:''' [[Licensing and patent claims::]] - Any licenses or patent claims that the engineering format makes.
+
* '''Adoption:''' [[Adoption::N/A]]  
  
−
* '''Self-documentation:''' [[Self-documentation::]] - Any self-documentation capabilities of the format.
+
** '''Licensing and patent claims:''' [[Licensing and patent claims::N/A]]  
  
−
* '''External dependencies:''' [[External dependencies::]] - Anything that the format depends on outside of its control to function.
+
* '''Self-documentation:''' [[Self-documentation::N/A]]  
  
−
* '''Technical protection considerations:''' [[Technical protection considerations::]] - Any considerations that are necessary when it comes to technical protection.
+
* '''External dependencies:''' [[External dependencies::N/A]]  
  
−
'''Typical use:''' [[Typical use::]] - Keywords that describe the format's typical use. Examples: CAD and CAM
+
* '''Technical protection considerations:''' [[Technical protection considerations::N/A]]  
 +
 
 +
'''Typical use:''' [[Typical use::CAD]]
  
 
'''File classification:''' - Specific properties that pertain to this engineering format.
 
'''File classification:''' - Specific properties that pertain to this engineering format.

Revision as of 17:20, 13 May 2009

Title(s): I-DEAS Web Access file (Crushed Ascii)

Version ID: No longer in use

Date released: N/A

Date: 1999-04-14

Creator(s): Structural Dynamics Research Corporation (SDRC)

Contributor(s): Siemens PLM Software

Relationships:

  • Previous Version(s): N/A
  • Contains: N/A
  • Syntax Format(s): N/A
  • Family Format(s): NX

Description: MCA was used by I-DEAS Web Access, a program that was merged with Unigraphs to from Unigraphs NX, now known as NX.

History: I-DEAS Web Access was announced in 1999 by SDRC with the foal of providing web-based collaboration and visualization for use with I-DEAS software. SDRC was bought by Electronic Data System (EDS) in 2001. EDS also acquired UGS Corp, the makers of Unigraphs. EDS merged both I-DEAS and Unigraphs into one product, NX. In 2007, UGS was bought by Siemens AG who renamed the company to Siemens PLM Software.

I-DEAS Web Access files are no longer used, as the program was merged into NX in 2001, but some programs are still able to read the files, for example [1], [2], and [3].

Example(s): None

Identifier: None

Documentation: N/A

File Extensions: MCA

Applications:

  • Native application(s): None

Magic numbers: N/A

Format(s): N/A

Rights: N/A

Sustainability Factors:

  • Standardization: N/A
  • Adoption: N/A
    • Licensing and patent claims: N/A
  • Self-documentation: N/A
  • External dependencies: N/A
  • Technical protection considerations: N/A

Typical use: CAD

File classification: - Specific properties that pertain to this engineering format.

  • Type {Binary, Text}: - The type of file, choices are binary and text.
  • Raster data: - Section describes whether or not the engineering format supports raster data.
    • Raster data 2D: - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Raster data 3D: - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a 3D model supports 3D raster data.
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Geometric representation: - Section describes whether or not the engineering format supports geometric representations.
    • Implicit representation: - Section describes whether or not the engineering format supports implicit representations.
      • Implicit surfaces: - Can the format support implicit surfaces? Example: A format that can contain surfaces that are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 = 0, supports implicit surfaces.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Implicit curves: - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Point set: - Can the format support point sets? Example: A format that supports surfaces and lines that are generated by points that form triangles supports point sets.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Mesh: - Section describes whether or not the engineering format supports mesh.
      • Manifold surface meshes: - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Manifold volume meshes: - Can the format support manifold volume meshes? Example: A format that supports volumes that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Non-manifold meshes: - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Parametric representation: - Section describes whether or not the engineering format supports parametric representations.
      • Parametric surfaces: - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Parametric curves: - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Contour sets: - Can the format support contour sets?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • NURBS: - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Multi-resolution models: - Can the format support models with multiple resolutions? Examples: A format that supports a highly detailed and lowly detailed model simultaneously supports multi-resolution models.
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Dynamics: - Section describes whether or not the engineering format supports dynamics.
    • Kinematics: - Can the format support kinematics? Example: Does the format allow model parts to rotate?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Assembly: - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Force(s): - Can the format support forces? Example: Does the format support acceleration forces?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Boundary representation - Can the format support models with boundary representations?
    • Manifold surface boundary representations: - Can the format support manifold surface boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Manifold volume boundary representations: - Can the format support manifold volume boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Non-manifold boundary representations: - Can the format support non-manifold boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Material transparency: - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.

References: - A list of references regarding any aspects of this engineering format; any reading material supplemental to this page.

Retrieved from "http://gicl.cs.drexel.edu/wiki-data/index.php?title=MCA&oldid=31696"
Personal tools