Why does it matter?

Why go through the trouble of defining the end-of-line programming procedure as an MTSL Script?

• Single source of truth
  • By codifying the procedure, we can have multiple software clients drawing from the same, single source of truth rather than each software client hard-coding the procedure into their source code.
• Visibility
  • Not everyone around the company understands what happens at the programming station.
  • The codified procedure can be easily read in english or converted into a visual chart.
• Record keeping
  • Understanding during NPD is one thing, but MTSL allows the procedure to be easily referenced and shared years later.
  • This can help with understanding during PSE projects or with general troubleshooting.
• Testability
  • Ability to run and test scripts locally.
  • The JEDI team provides QuickLink Web as an MTSL interpreter to make it easy to test MTSL scripts locally.
• Change management
  • Changes to procedure can be live in minutes, not days since it no longer would require source code changes in most cases.