Software Support for Industrial Controls Contract Organization

1
Software Support for Industrial Controls
ContractOrganization

• IT-2711 C168/ST
• STTC Meeting 25/9/2000
• Eva Sanchez-Corral

2
Scope of the contract

• To OUTSOURCE the OPERARTION MAINTENANCE and the
  DEVELOPMENT of monitoring and control systems on
  a RESULT-oriented basis.

3
Target

• Start-up 15 October 2000
• Duration 3 years 2 renewals of 1 year
• Volume ? 1 to 1.5 MCHF/year

4
Scope of Services

• Projects
• small medium size
• according to ESA Software Engineering standards
  PSS-05 and CERN standards
• Operation and Maintenance
• corrective
• preventive
• system database administration
• user support documentation production

5
Contract Organization (1)

• Strategy
• OM and Projects activities follow-up
• Tools (MP5, EDMS, Project follow-up)
• Active participation of CERN staff
• Regular meetings (with Contractor, CERN C168
  users)
• Performance evaluation
• Project Milestone plans
• Training
• CERN staff and Contractor

6
Contract Execution (1)

• OM Service
• Transition period of 6 months, Learning period
• The Contractor should take over of the systems
  with CERNs collaboration.
• Maintenance Management System MP5
• Definition of
• systems to be maintained and
• maintenance tasks to be performed
• Interventions follow-up
• Unplanned OM tasks maximum intervention times
  required
• Volume of activities revised twice a year
• Maintenance Plan and Quality Assurance Plan
• To be provided by Contractor at the latest
  February 2000

7
Contract Execution (2)

• Projects
• 1) User Requirements Document Project
  Management Plan by Project Leader
• Review by C168 Review team
• Sent to Contractor
• 2) Contractors offer (financial and technical)
• According to Tender Reference projects
• CERN will approve/reject Contractors proposal
• 3) Follow-up
• Project life cycle and Milestones
• 4) After successful Provisional Acceptance
  Testing -gt 2 years guarantee
• OM repair all non-conformance with the
  specification done by Contractor
• 5) Final Acceptance

8
Contract Organization (2)

• CERN C168 Team responsibility chart

9
Contract Organization (3)

• OM activities (2) systems to be maintained

10
Conclusions

• The contract should
• improve the quality of OM and of the new systems
• partially compensate the decrease of staff
• Outsourcing a complex activity
• Give the responsibility to the contractor
• Control its monopoly situation
• Manage our loss of know-how (keep doing
  computing)
• Change our habits
• Methods, Standards
• Promote collaboration within ST

11
(No Transcript)