Swisslog Improves Quality Of Process Maturity With MKS - Mks.com

Case Study
Swisslog
Swisslog has adopted MKS form to capture
input from their field organization and
internal customers (QA, mechanical
engineering) allowing the development
team to identify bugs and change
requests from the field. This gives Scott’s
team a better understanding about the
volume and nature of bugs coming in.
This feedback loop increases effective
communication and allows for continuous
improvement in serving the customers’
needs. Field staff plan to use the web
interface to connect from customer sites.
There is no ‘after the fact’ write up
-- instead the field staff sit at a customers’
machine and send in the bug fix requirements.
With real-time entry, information
is more factual since it is done with
customer input on site.
2 | Swisslog Case Study
Swisslog additionally uses MKS to control
documentation on specifications – tech
writers can check in help builds and the
end user documents such as word files
and PDFs for the three different types of
customers – internal engineering, tech
field staff and the end-user, customer at
the hospital.
Swisslog is now introducing an issue type
called ‘requirement’ inside of MKS to allow
them to solicit customers and engineering
for their requirements up front as part of
a planned process. This requirements
management capability within MKS
Integrity enables Scott’s team to track the
requirements as an issue type, assign
issues to a developer and provides
complete downstream traceability and
connection to work being done, the
transition to QA.
If there’s a bug -- it tracks directly back to
the requirements. Project managers gain
complete visibility and can see how many
projects are complete, track against use
cases, and enter the use case if required.
As Scott’s team begins to interface with
other departments, they can showcase
their planning and estimates, and store
the requirements as needed when
projects come online or are put on hold.
Using MKS Integrity and project descriptions,
they are able to create various issue
types within the same projects so that
mechanical and software issues are both
able to be seen.