Please be advised that a New Work Item Proposal has been loaded to the BSI Standards Development Portal for comment.
Any comments received will be submitted to the national committee AMT/4 “Industrial data and manufacturing interfaces” for consideration when deciding the UK response to the associated Standards Development Organisation.
- Proposal: ISO/PWI 14306-4, Industrial automation systems and integration — JT file format specification for 3D visualization — Part 4: Version 3.
Comment period end date:23/12/2023
The JT file format specification for 3D visualization specifies the sequential order of bytes that comprise the segments of data required to represent a JT file. The JT format is uniquely compressed to minimize file size.
The JT file format specification for 3D visualization includes data descriptions that can represent the following data.
— facet information (triangles), stored with geometry compression techniques;
— visual attributes such as lights, textures and materials;
— product manufacturing information (PMI);
— boundary representation (b-rep) solid model shape representation and associated metadata;
— configuration representations; and
— delivery methods such as asynchronous streaming of content.
The following geometry representation are proposed to be deprecated in the ISO 14306 Part 4 specification
— lightweight ULP geometric boundary representation;
— lightweight LWPA precise analytic geometric boundary representation;
A complete list of Product Manufacturing Information (PMI) String Property Atom Element values will be made available as a Reference Data Library in electronic insert format. A number of Material and Surface attributes referenced by the ISO 14306-4 specification will also be defined in a separate Reference Data Library in electronic insert format.
The JT file format specification for 3D visualization does not specify the implementation of, or definition of, any runtime architecture for viewing and/or processing JT data.
ISO 14306 Edition 2 was published in 2017 based upon JT 9.5 file format. The standard has become out of date with JT data currently being widely used by industry. This edition updates ISO 14306 to align with the JT 10.5 file format.
One of the main differences between JT 9.5 and JT 10.5 is the difference between the file compression algorithms that are utilised. Due to the changes between the JT 9.5 and 10.5 the files are not bit stream compatible, for this reason provisions will be made to enable ISO 14306:2017 Edition 2 files to continue to be supported. This will be achieved by retaining the existing ISO 14306:2017 Edition 2 specification in its current form. The output from this NWIP will be a new specification labelled ISO 14306 Part 4 as part of the ISO 14306 multipart specification. A reference within the ISO 14306 Part 1 specification to the earlier ISO 14306:2017 Edition 2 specification will enable future implementers to be able to continue to verify requirements that are unique to the JT 9.5 file format specification.
Within the ISO 14306 Part 4 specification the ISO 10303-42 B-Rep representation will be defined as Normative and XT B-Rep geometry representations will be defined as Informative.
Due to a significant investment in ISO 14306 data and in software to support their workflows, the following industries have formally expressed a desire for this standard to be updated; Automotive and Transportation, Aerospace & Defence, Industrial Machinery & Heavy Equipment, Marine, Electronics & Semiconductors, Energy & Utilities, Medical Devices & Pharmaceuticals and Consumer Products
- Proposal: ISO/NP 45008 – Occupational health and safety management — Guidelines for remote working
Please visit: ISO/NP 45008
Comment period end date:28/01/2024
This guideline provides guidance for organization and worker in a remote working to ensure healthy and safe work environment. This can help protect the health and safety of remote workers and maintain a balance between work and life.
Note: This document is intended for regular remote workers who perform remote work on a recurring basis and does not include offsite and business trips.
The legitimacy of remote working health and safety standards is based on realistic needs and responsibility to stakeholders in the organization. Remote working has become increasingly important in the modern working environment, and accordingly, the need for standards to protect health and safety is emerging. By protecting the health and safety of remote worker, organizations can fulfill their social responsibilities and take necessary measures to ensure the health and well-being of their employees. In addition, through this, you can enjoy the advantages of improving productivity, performance, and employee satisfaction.
- Proposal: ISO/NP 8000-119 – Data quality — Part 119: Application of ISO 8000-115 to transport unit identifiers
Please visit: ISO/NP 8000-119
Comment period end date:31/31/2023
This document specifies the requirements for transport unit identifiers. These requirements supplement those of ISO 8000-115.
The following are within the scope of this document:
— the methods used to identify the originator of a potential shipment,
— the methods used to identify the origin and destination locations of a potential shipment,
— the requirements for the representation of the originator, origin, and destination locations of a potential shipment in a single identifier
The following are outside the scope of this document:
— the methods used to identify shipments in the transport phase,
— the identification of the goods movement phase
At present, automatable load identifiers usually emerge at the start of the transport phase when a load is prepared for shipping, or a carrier is booked. These identifiers may be electronic data interchange numbers, radio-frequency identification codes, barcodes, shipping manifest numbers or any number of other forms. They exist so industry systems and software can know which load is which and possibly where it is located at a given moment. It is common practice to use these identifiers in conjunction with formal labels (barcode, bill of lading number, electronic data interchange number, radio-frequency identification code, etc.) that support automation.
Unfortunately, there is no comparable transport unit (load) identification method that applies widely during the negotiation phase. This is a serious roadblock to large-scale digitization of the marketmaking process where even the best AI struggles when a load is described as “the 18,000 kg. of wire coil at Gate 3 on our loading dock.” Industry can clear this roadblock if shippers unilaterally generate unique identifiers for their loads as soon as they form the clear intent to make the shipment. This is the transport unit identifier. An open identifier that can be constructed by each shipper independently and shared with the intended shipment recipient, and any intermediaries that participate in the negotiations If you have any comment or need more information, please contact Sami Ortiz at [email protected]