A brief overview of the needs of Article level data and information dissemination related matters for a multicloud mutiaAapp mutlisector supplychain facing mulitple regulatory criteria
5CL-ADBA,5cladba, Chinese supplier, safety is guaranteed
Optimum Article level information dissemination for the mutisector supply chain
1. HYBRID MULTICLOUD PATH FOR
EFFICIENT MULTISECTOR
ARTICLE LEVEL INFORMATION
DISSEMINATION ACROSS
MULTIPLE APPLICATIONS FOR
COMPLIANCE WITH MULTIPLE
REGULATORY CRITERIA
By
Papros Inc
2. GENESIS AND PROVENANCE
●
Instantaneous composition and safe use update
across the entire supply chain-must be part
number specific so filters can pull the information.
●
When a supplier part number usage in BOM is
known only to the next level supplier, his supplier
must be able to similarly propagate the
composition and safe use information
downstream.
●
Fully secure, authenticated, machine to machine,
little or no human interface preferable.
●
Must be able to interact multiple clouds private
and public, and data accessible by PLM, design,
3. SUMMARY NEEDS
●
Underlying data to be standards based.
●
Notifications must flow across multiple clouds
while still authenticatable and secure.
●
Notifications must provide part level information.
●
Process to support apps using multimedia and
on mobile devices also.
●
Sharing of parts information must be permission
based to allow authorized recipients only.
●
Hashes of key files that are shared across
sectors must be maintained and provided to be
able to verify file authenticity.
4. DATA TYPES
●
Composition-Any of the standards based data
IPC 175X or IEC 62474. The nature of the supply
chain is diverse and these and other data types
(including some spreadsheet based) will persist.
●
Safe use information-These could be PDF, a
proprietary document format or text based, audio
and video and various combinations thereof..
●
All data files should be hashed to be able to
verify authenticity, when additional files with same
name are present, there must be a suffix to
denote newer additions.
●
5. Data flow cycles
Article
Supplier 2 BOM Supplier 3 BOM
Supplier 1 Notify
Notify
Often Supplier 3 will know that
Supplier 2 BOM has the part in
question but will not know it is from
Supplier 1. However he/she must be
notified in the cascade of information
including instant update when
composition or safe use involving a
SVHC changes
6. Article flagging
●
If it meets the criteria for an Article.
●
If it part of a BOM (Bill Of Materials) and is
flagged in the Bom (IPC 1754 does this currently,
other standards expected to adapt this practice).
●
When it is part of a BOM, information must still
flow instantaneously across all users for updates.
●
Web version of data transmission has every
single feature of any competitor and more.
●
7. Clouds, Apps and Actvities
Purchasing and
Administration
Supplier data
Design Production
scheduling
Manufacturing floor
Customer
Facing
portal
Regulatory
needs
8. Heterogeneous Nature
of End Users
●
Because of the various different needs for the data,
there are many types of end users.
●
Composition, use type as well as safe use information
required.
●
Desktop and mobile access for safe use information,
example-shop floor safety.
●
Safe use information could involve audios and videos,
so bandwidth needs must be supportable on cloud.
9. Multiple Data Formats in
Supply Chain
●
Spreadsheet
●
Old PDF 1752 convertible to 1752 v 1.0
XML
●
1752A XML
●
1754 XML
●
IEC 62474 XML
●
Proprietary formats.
●
10. Conclusion
Effective supply chain communications for Articles
result from efficient sharing of data and
instantaneous notifications of information updates,
both of composition as well as safe use.