iBASEt Solumina and OAGIS

iBASEt
Solumina
and
OAGIS
May, 2009
Who is iBASEt ?
 The company has two Divisions
• Federal Services
• Commercial -- Solumina product
• www.solumina.com
 Solumina Industry niche – we used to call it MES
 MES has had broad range of meanings … from
automation and control, to paperless shop floor, to
illustrated work instructions, to …
 We call what we do OPM or MOM
• Operations Process Management
• Manufacturing Operations Management
2
Solumina in the Enterprise Systems Landscape
Design
Business
Shop Floor
3
What Is Solumina
 Operations Process Management software suite that manages work and
quality processes for the Manufacturing and MRO (Maintenance, Repair,
and Overhaul) of highly engineered products.
 Solumina targets Complex Discrete Manufacturing
• Complex processes
• Complex work instructions – images, multi-media, 3-D models
• Human “touch labor” involvement
• Electronic records
• Stringent data collection and inspection requirements
• Stringent tracking and as-built records requirements
• Regulatory Compliance or operational efficiency -- get rid of paper
• Broad, Integrated Footprint
• Reduce silo applications on shop floor, reduce paper, integrate with other key Enterprise
applications.
4
What industries does Solumina target ?
 Aircraft, Aerospace, Spacecraft
• Engines and components
 Nuclear energy
• DOE
• Naval vessels
• Commercial Reactors
 Defense Land Vehicles, Ships
and Submarines, Weapons
Systems
 Medical Devices
 Industrial Equipment and
Vehicles
5
Key Solumina Customers
6
Integrated Shopfloor Systems -> Lower TCO
Design
The How Space…
How to make it,
How well are you doing it,
How high is your quality?
Business
Evolving from CAD
and PDM
to PLM Product
Lifecycle
Management
ERP/MRP
Schedule
Costing
Procurement
Inventory
Financial
Performance
CAD
BOM
FMEA
DFSS
DFM
Simulation
NDE
Risk Assess
Where,
When
What
7
Solumina, PDM and ERP Integration
Traditional
P LM
PDM
ERP
Solumina
OPM
Integration based on OAGIS
XML Standards for Discrete
Manufacturing.
or Streamlined
PDM
Solumina
OPM
ERP
8
High Level Integration Areas
 Product Definition
• Parts, Geometry
• Product Structure, Components
• Tooling
 Process Definition
•
•
•
•
Departments, Work Centers, Employees and Qualifications
Process Routings
Tooling
Work Order Changes
•
•
•
•
Work Order Release, Work Order Status, Schedule, Labor
Material Issue, Scrap, Product Movement
Inspections and Data Collection
Work Order Quantity Split
 Process Execution
 Process Quality
• Discrepancies / Defects
9
What’s Different about Solumina?
 As-built no longer means just
final component genealogy…
Its everything that happened to or
around the item while in
production.
 Change Management to WIP
and beyond
 Complex Manufacturing
Sequences
 Seamless Integration of
Business Processes
• Who did what operation when?
• What components were installed and
removed, reworked?
• How many retries did it take to pass
an inspection?
How to phase an
engineering/product change into
production schedules, work in
process, inventory, field
• Cycles, loops, test and fit, parallel
and serial steps, alternate path
decisions
• New paradigms with PLM and ERP

10
OAGIS is the External API for Solumina
OAGIS
BODs in
JMS
Messages
11
Solumina Evolution with OAGIS
2000
OAGIS 7.2
adopted for
custom
projects
2000
XML
Connector
“minimiddleware”
framework
product
option.
2002
Partner
integration
with Kaba
Workforce
Solutions
Autotime
Based on
OAGIS 7.2
Catalog
product
options
2003
Prepackaged
add-on
library
based on
OAGIS 7.2
added as
product
option
2007
Migrated to
industry
standard
infrastructure
platforms
OAGIS 9.1
adopted for
product addon library
and custom
projects
2008
2009
Solumina
Business
Integration
Services
(BIS)
included in
core
product
Pre-built
Business
Packages for
other
Applications
SAP
Oracle EBS
Dassault
Delmia
PTC
More to come
12
Challenges
 Technical
• OAGIS Architecture
• OAGIS BOD Content models
• Infrastructure and tools
• Fit to customers infrastructure
and tools
 Cultural
 Try to lead to standards-based
Enterprise Architecture
• Business focus hard to maintain
• Point-point project focus limits
vision and scope
• Don’t make my problem even a little
harder this week to make someone
else’s problem easier next year.
• Service orientation is confusing
• XML is still mysterious and scary
• Need for infrastructure and tools is
an obstacle (cost and learning)
13
Addressing the Challenges - Technical
 Technical
• OAGIS Architecture
 OAGIS Training, Workgroup participation,
experience, OAGIS evolution
• OAGIS BOD Content
models
 Workgroup participation, OAGIS-Users
email group, OAGIS evolution two edged,
gap remains for examples, Profiles.
• Infrastructure and tools
 Industry evolution
• Fit to customers
infrastructure and tools
 Struggle with open standards, finding
correct modularity, still significant gap in
portability
14
Addressing the Challenges- Cultural
 Cultural
•
•
Business focus hard to maintain
Point-point project focus limits vision and scope
•
•
•
•
Don’t make my problem even a little harder this week to make
someone else’s problem easier next year.
Service orientation is confusing
XML is still mysterious and scary
Need for infrastructure and tools is an obstacle (cost and
learning)
• Best Solution
• Partner alignment
• Kaba Workforce Solutions Autotime
• Next Best
• Develop pre-built product-specific integration packages for other
applications
• Typically developed and deployed on favored infrastructure of
target
• SAP, Oracle EBS, Dassault Delmia, PTC, others to come
15
Integration for Partner Solutions
Multiple Partner solutions share common Solumina modules.
Reduces iBASEt development and life-cycle costs.
Partner solutions differentiation focuses on Partner-specific issues
Standards-based infrastructure supports alignment with Partner
solution infrastructure
16
AutoTime’s Integration Interfaces
ERP
Suite
17
Kaba
 Tier 1 global player in the security / WFM industry
 Internationally active and listed company (SWISS: KABN)
 Approximately 10,000 employees in more than 60 countries
 About 70 production and sales companies
 Technology leadership with more than 300 patents
 145 years of experience in security technology

is the Kaba division specializing in
Workforce Management Solutions based in Miramar Florida.
18
18
Kaba Workforce Solutions
 Kaba Workforce Solutions is a provider of Data
Collection Terminals, B-COMM Middleware and
AutoTime Workforce Management Software
 iBASEt’s Solumina integrates with Kaba’s
AutoTime software
 AutoTime is a Time and Attendance and Time and
Labor System.
 AutoTime offers a wide range of features designed
to streamline the collection of Workforce
Management data for a variety of businesses in a
wide range of industries.
 Current version is AutoTime 6 which uses OAGIS 7
documents
 Upcoming version is AutoTime 7 which will use
OAGIS 9 standards
19
19
Kaba Workforce Solution’s Customers
20
20
Developing Solumina Integration
21
Start with Business Scenarios/Use Cases
 We try to take a Business Orientation as opposed
to a data structure/ API Orientation.
 business objects, Business Events, Business
Workflow
 Identify key data
 THEN identify BOD and mappings
22
Solumina Integration Use Cases (selected examples)
Author
BOM
PLM
BOM
ERP
BOM
BOM
Operationalize
BOM
PPlg
Bill of Material
Master
Routing
ERP
Capacity
Planning and
Scheduling
Release
Work Order
Master
Routing
PPlg
Work
Order
Author
Process
Plan
Work Order
Instructions
Dispatch
Work Order
PExe
Process Planning and Execution
23
als to specific operations within a process plan, thus ‘operationalizes’ the
Product
M is passed
to the Definition
ERP system.
PDM
Author
BOM
BOM
Solumina
PPlg
Operationalize
BOM
BOM
ERP
BOM
Scenario 1-- PDM authors BOM and PPlg operationalizes BOM for ERP.
24
ences 3D models created using CAD software
tore Process
process sequences
authored using 3D process modeling softwa
Definition
process plans based on 3D models and process sequences obtained
PDM
3DModels
3D
Models
Author
Process
Sequence
3D
Models
Solumina
PPlg
Process
Routing Sync
Author
Process
Plan
Figure 5. PDM passes 3D models and sequences, PPlg user authors process plan.
25
receives master routings from PPlg system. Master routings are used in capac
workProcess
orders to theDefinition
PExe system.
Instructions are passed internally from PPlg to PExe system.
Solumina
PPlg
Author
Process
Plan
Process
Routing Sync
Work Instructions
Solumina
PExe
Dispatch
Work Order
Work
Order Issue
ERP
Master
Routing
Capacity
Planning and
Scheduling
Release
Work Order
26
Process Execution – Labor
Solumina
PExe
Supersede
Work Order
Release
Work Order
Work Order
Issue
La
ERP
bor
Work Order
Clock On/Off
Work Order
Revision
Account or
Project Clock
On/Off
Personnel
Clocking Sync
Personnel
Clocking Sync
Clock On/Off
Transactions
Work Orders
27
changes are sent from ERP to PExe.
er and
operation status
changes are–communicated
PExe to ERP
along with
Process
Execution
Changes,from
Status
Updates
Solumina
PPlg
Author
Process Plan
Changes
Process Plan
Revision
Solumina
PExe
Dispatch
Work Order
Supersede
Work Order
Update
Schedule
Change
Work Order/
Operation
Status
Work Order
Revision
WO Operation
Status
Work Order
Issue
ERP
Release
Work Order
WO Schedule
Sync
WO Routing
Change
Update
Work Order/
Operation
Status
Change
Schedule
ser executes work order and PExe receives updates from ERP and PPlg systems
28
Solumina OAGIS Profiles
 Solumina defines specific profiles of OAGIS BODs for catalog
touchpoints
– Manually developed and managed
• Includes
• Specific elements used, Solumina-specific interpretations
• Mapping to Solumina data elements
• Solumina-specific extensions
• Excludes elements not used, by omission
• Supports mapping for project’s external systems
 Solumina SMAP becomes the Profile repository for the project
• Solumina SMAP documents the element usage and data mapping
• SMAP is an enhanced XML document, based on the BOD format, with added
metadata
• SMAP tools extract into spreadsheet formats for easier use
29
Solumina OAGIS Extensions





New BODs – take to enhancement workgroup process
Content Gaps - take to enhancement workgroup process
Solumina-specific extensions
Project/Customer-specific extensions
Manage through namespaces, and our profiling methodology
 Mostly USERAREA Based -legacy from OAGIS 7.2
– Technical challenges with tools
30
Business Integration Services-Touchpoint Roadmap
Authorization
to
Ship
Non
Conformance
Notification
31
Summary Touchpoint List –Phase 1

Product Definition
•
•

Process Definition
•
•
•

Work Order Issue - Receive in Solumina
Work Order Operation Schedule Sync - Receive in Solumina
Work Order Issue - Send from Solumina
Process Execution
•
•
•
•

Process Model and Routing Sync - Receive in Solumina
Process Routing Sync - Send from Solumina
Work Order Revision - Send from Solumina
Process Scheduling
•
•
•

Part Number and Material Sync - Receive in Solumina
Bill Of Material Sync - Receive in Solumina
Work Order Operation Status - Send from Solumina
Personnel Clocking Sync – Send from Solumina
Work Order Status – Send from Solumina
Work Order Split - Send from Solumina
Organization Definition and Transactions
•
•
Personnel Sync – Receive in Solumina
Location, Department, Work Center Sync – Receive in Solumina
32
Core Solumina BIS Service Touchpoints
DESCRIPTION
DIRECTION
OAGIS BOD
Receive Work Order Operation Schedule Sync
INBOUND
SyncWorkOrder
Receive Part Number and Material Sync
INBOUND
SyncItemMaster
Receive Bill Of Material Sync
INBOUND
SynchBOM
Receive Process Model and Sequence Sync
INBOUND
SyncRouting
Receive Work Order Issue
INBOUND
SyncWorkOrder
Receive Personnel Sync
INBOUND
SyncPersonnel
Receive Location, Department, WorkCenter Sync
INBOUND
SyncLocation
Send Process Routing Sync
OUTBOUND
SyncRouting
Send Work Order Operation Status
OUTBOUND
UpdateConfirmWIP
Send Work Order Issue
OUTBOUND
SyncWorkOrder
Send Work Order Status
OUTBOUND
UpdateProductionOrder
Send Personnel Clocking Sync
OUTBOUND
ProcessEmployeeWorkTime
Send Work Order Split
OUTBOUND
SyncWorkOrder
Send Work Order Revision
OUTBOUND
SyncWorkOrder
33
Case Study for Standards-based Integration
System lifetime was expected to be 8-10 year horizon.
Within 3 years, an SAP implementation replaced MacPac
Neutral intermediate standards decoupled and isolated the systems
from changes.
Modifications made in MQ System Integrator middleware.
Minimal changes to Solumina interfaces.
Business Service focused changes
34
solumina.com
35