Embed Size (px)
DESCRIPTION
The PLM context - recap PLM stands for Product Lifecycle Management –The product lifecycle includes all the phases of the product life, from concept definition to product disposal and recycle –PLM imposes to manage the lifecycle from its beginning Why would anybody want to do PLM? –To optimize the cost of the lifecycle (cost of design, production, maintenance, usage...) –To shorten the time to market –To forecast problems that can arise later –To provide services for the product –To maintain the engineering knowledge of the company in an integrated way and reuse it PRODUCT DATA MODELING AND DEPLOYMENT
Citation preview
Progetto OPTIMUS
PLM and Interoperability in the defense sector
Vico Equense (NA) – April, 22 2015
Xenia Fiorentini
Agenda
• The PLM context– Interoperability in the PLM context
• The PLM context in the defense sector– Interoperability for the defense
• Cases
PRODUCT DATA MODELING AND DEPLOYMENT
The PLM context - recap• PLM stands for Product Lifecycle Management
– The product lifecycle includes all the phases of the product life, from concept definition to product disposal and recycle
– PLM imposes to manage the lifecycle from its beginning
• Why would anybody want to do PLM?– To optimize the cost of the lifecycle (cost of design, production, maintenance,
usage...)– To shorten the time to market– To forecast problems that can arise later– To provide services for the product– To maintain the engineering knowledge of the company in an integrated way and
reuse it
PRODUCT DATA MODELING AND DEPLOYMENT
The problem (1/2)• Several proprietary software applications manage the product data during its
whole lifecycle– Applications for requirements modeling, for engineering design, for manufacturing
cycles, for maintenance procedures, customer support, etc.
PRODUCT DATA MODELING AND DEPLOYMENT
The problem (2/2)• The business processes need these applications to communicate and share
product data with each other– Internal processes: requirements tracking for certification, integrated
logistic support for new types of contracts, reuse of manufacturing capabilities, design for sustainability, engineering changes due to customers complains, etc.
– Collaboration with partners, suppliers and customers– Long term archiving
• Why is the communication between applications a problem?– The applications are proprietary: few companies know how to “access”
them– The versions of the same application are often not compatible– The number of involved applications is high just right now. Plus, new
applications can be used in the future– Data are sometimes managed by legacy applicationsPRODUCT DATA MODELING AND
DEPLOYMENT
How the problem is commonly solved• Migrate legacy applications to a unique application• Implement some sort of application programming interface (API) for each application, and then,
in each application, implement "glue code" that exploits the APIs of other applications to link them together
• Design a single database to store the data of multiple applications, and implement each of the applications against this database (or repository)
THESE OPTIONS ARE EXPENSIVE
(see presentation “Interoperabilità: costi e benefici”)“This report, prepared for NIST by RTI International and the Logistic Management Institute,
estimates the cost of inadequate interoperability in the U.S. capital facilities industry to be $15.8 billion per year.”
[Cost Analysis of Inadequate Interoperability in the U.S. Capital Facilities Industry , NIST]
PRODUCT DATA MODELING AND DEPLOYMENT
Engisis focuses on Interoperability for PLMUse standards and specificationsPLCS (ISO 10303 AP 239) and DEXPDM Schema and ISO 10303 AP 233, AP 242, AP 235ISO 15926S3000LNIILS (Italian inter-forces specification for ILS)
Assess models against processesWe investigate existing product data models and their relationship with the processes.We apply data models to the business context.
Deploy common modelsWe apply standard data models for business cases and deploy the product data models to solve your interoperability issues.
Use skills and technologyModel-based engineeringModel and ontology for product dataModels transformationLanguages for data and process modelingSoftware architecture and programming
TrainWe provide educational services and trainings adapted to each organizational level, from business managers to software implementers.
Implement interoperabilityAssure interoperability between the software applications that manage product data during the whole product lifecycle.Test cases and data setsProducts
PRODUCT DATA MODELING AND DEPLOYMENT
The PLM context in the defense sector
• Doing PLM in the defense sector is challenging– Products are complex– Products have very long lifecycles– Nobody is responsible for the whole product– Acquisition and Deployment are managed as separate phases– Nobody has ever calculated the total cost of ownership of the
products– The actors in the lifecycle are numerous– The actors in the lifecycle are not necessarily known
PRODUCT DATA MODELING AND DEPLOYMENT
Interoperability in the defense sector: an example
FMECA AnalysisMaintenance TasksFunctionalAnalysis
Design
From the delivery of a product, to the delivery of capabilities
PRODUCT DATA MODELING AND DEPLOYMENT
Interoperability in the defense sector: an example
FMECA AnalysisMaintenance TasksFunctionalAnalysis
Design
From the delivery of a product, to the delivery of capabilities
DATA IN STANDARD FORMAT
PRODUCT DATA MODELING AND DEPLOYMENT
Interoperability in the defense sector: an example
FMECA AnalysisMaintenance TasksFunctionalAnalysis
Design
From the delivery of a product, to the delivery of capabilities
DATA IN STANDARD FORMAT
The failure effects of the FMECA are derived from the relationships between the product components and hte functional analysis
Maintenance tasks are linked to failure modes, which are detected through the failure effects, they are executed over the components and need equipments and tools
PRODUCT DATA MODELING AND DEPLOYMENT
Which standard?• ISO TC 184/SC 4 (Industrial data) created a serie of standards.
– ISO 10303-239 is the standard for Product Life Cycle Support (PLCS)
Define product requirements and configuration, including relationships between parts and assemblies in multiple product structures (as-designed, as-built, as-maintained).
Request, define, justify, approve, schedule and capture
feedback on work and related resources.
Describe and capture feedback on product properties, states, behavior and usage.
PLCS Capabilities
Product Description
Property, State & Behavior
Work Management
Support Solution & Environment
Define the support for a given set of products in a specified
environment and define support opportunity, facilities, personnel and organizations.
PRODUCT DATA MODELING AND DEPLOYMENT
Case 1: MoD/supplier interoperability for LSA• The MoD customizes a commercial tool (SAP) to manage the configuration of both the
design of the naval systems and their installation, together with their logistic engineering data
• The MoD needs to talk with the suppliers– To sync the configurations of the systems, and their logistics parameters– To sync the maintenance plans
• We build a PLCS adapter to this tool (by following, also, the S3000L specification)
PRODUCT DATA MODELING AND DEPLOYMENT
Case 2: PLM Interoperability strategy• A multinational company is deploying a PLM strategy. Interoperability is
seen as a means to– Give enough freedom and security to each country– Deploy a step-by-step PLM solution– Implement multinational collaboration– Exchange data with suppliers and partners
Single sign-onForum
Management of product structuresProject management capabilitiesSearch for product data in TAS
Man
age
orga
niza
tion,
pr
ojec
ts a
nd w
orkf
low
s Register system
sM
anage mappings
CheckAssign
QueryBrowse PrintADMIN SYS
SHARE
OPT
USER
Synchronize eBOMTransfer Technical baseline
Synchronize Change RequestsSynchronize CCNSynchronize RFD
Transfer the as-designed baselineSynchronize Change Proposals
We plan a standard-based share&exchange strategy
− We specify
› Collaboration processes
› Functionalities
› Data modeling
› Architecture
− We make a Business Case Analysis with real processes, data and systems
PRODUCT DATA MODELING AND DEPLOYMENT
Case 3: Coalition/Joint Logistics Interoperability
• The CLI/JLI project– each military service brings its own assets to repair its weapon systems– assets need to be purchased, stocked, managed and disposed by each military service– we can lower the cost of the repair processes by making the assets shared among the military
services in a joint/coalition interoperability logistic scenario• The scenario
– items are marked through UIDs (Unique Item Identifications)– one military service requires an item to be repaired– another military service repairs it
• We build interoperability between– The ERP of each military service– The UID registry
PRODUCT DATA MODELING AND DEPLOYMENT
16Interoperability in Public Transportation Systems
Thanks! Grazie!
• Xenia [email protected]+39 06 80368 947
• Engisis S.r.l.www.engisis.com
Project data
• Customer : power-plant design and operations• Project title: Models interoperability and systems architecture for PLM• Project duration: 2 years (ongoing)• Partners: an engineering school and an university
Approach
• 3 scenarios per year, each including state of the art, technical proposal and demonstration• Modeling of catalogues, CAD data and business rules for PLM • Usage of meta-modeling techniques, application of ISO 15926, definition of ontologies, selection of languages for rules expression
Achievements
• Analysis and application of standards to exchange product data• Modeling and mapping of proprietary data• Technical benchmarking of existing solutions• Software development and application in real cases
HOW: BUSINESS CASE A
PRODUCT DATA MODELING AND DEPLOYMENT
Project data
• Customer : international defense organization• Project title: Coalition logistics interoperability through PLCS• Project duration: 6 months• Partners: 3 consulting companies
Approach
• Development of use cases, architecture diagrams and test cases• Definition of the Business Object model and associated XML schemas• Software customization and validation
Achievements
• Definition of meta-data for the exchange• Use of everyPLM to exchange PLCS data for sharing maintenance capabilities between proprietary tools• Software demonstrations in environments with high security requirements
HOW: BUSINESS CASE B
PRODUCT DATA MODELING AND DEPLOYMENT
• Customer : defense prime contractor• Project title: S3000L Proof of concept• Project duration: 3 months• Partners: support from CALS Italy
Project data
• Analysis of data as currently managed by the customer• Application of the Logistic Support Analysis (LSA) business processes: as-is and
to-be• Usage of the PLCS SDK to implement the S3000L PLCS DEXes• Support for sharing achievements and obstacles in international industrial
communities
Approach
• Educational sessions: LSA processes and data• Development of reference data and mappings• Development of an S3000L generator and viewer• Feedback reporting to the S3000L community
Achievements
HOW: BUSINESS CASE C
PRODUCT DATA MODELING AND DEPLOYMENT
