Statoil-NTNU contact meeting, 25 May 2009 STATOSS: OPEN SOURCE SOFTWARE AT STATOILHYDRO? NTNU-STATOILHYDRO contact meeting, 25 May 2009 Reidar Conradi et al., IDI, NTNU Software Technology Context: 1970: Systematic software reuse – less time & effort, better quality, ”best practises”, standardization – but non-technical obstacles like trust, ownership, ROI, updating, culture, policies … : Free Software and Open Software Software (OSS). Since 2005: software technology maturing through OSS: –Massive, global software reuse, i.e. standardization. –Cooperative and distributed work processes. –Ex. Roles: main developer (having ”gone open”), major co-developers, occational contributors, passive developers, and end-users. –Ex. Business models: double licensing, or shared OSS code run by foundations owned by IBM, Sun etc. and which may offer paid services.

Statoil-NTNU contact meeting, 25 May 2009 The OSS ”tsunami” and StatoilHydro Ongoing software revolution: –One million software components in Linux, Hibernate, libraries,.... –Public OFU contracts shall make delivered software open. –Half of 5000 Norwegian software companies use OSS in new code; that have gone open – like Ez Systems w/ 2 mill. downloads. What’s in it for StatoilHydro? –All software-intensive companies need to efficiently acquire, use and maintain high-quality ICT systems - costing StatoilHydro 3(?) bill. NOK per year. –Systematic reuse and OSS are vital to improve StatoilHydro’s software processes, perhaps in non-competitive communities with related companies (figure p. 4). Try base such efforts on SEVO project: –SW evolution of component-based systems (NFR, ); PhDs Gupta & Slyngstad, postdocs Mohagheghi & Li; StatoilHydro contacts: Rønneberg, Landre, Wesenberg. –4-year study of defect & change profiles of JEF reusable library and its 3 appl. –Recommendations for changed reuse policies and processes. –40 SEVO papers, 6 with StatoilHydro co-authors; all results public.

Statoil-NTNU contact meeting, 25 May 2009 Project STATOSS: StatoilHydro and OSS? For StatoilHydro, consider an internal OSS initiative: –Make a survey of the insight in and attitudes to OSS in StatoilHydro (human roadmap). –Find out how much and what kind of OSS is now in use in StatoilHydro (software roadmap). –Export: find ”code” that may be upgraded to new, own OSS components (go open). –Import: find ”code” that may be replaced by existing OSS components (more reuse). –Establish non-competitive communities with similar companies regarding domain-specific libraries (partner seek), cf. similar alliances in telecom between Nokia, Philips et al. –Couple this to ongoing ”Integrated Operations” project? –Adopt an incremental approach for all this. Identify risks and success factors. For NTNU, new R&D project to piggy-back on above StatoilHydro initiative: –Study related products and processes. Make research design w/ research goals. –Propose and validate revisions to the actual processes. Advancing state-of-the-art. –Similar for an ”open” business model to express StatoilHydro’s OSS policy and experience.. R&D resources at NTNU and StatoilHydro: –NEW: two PhD students: 5 MNOK over 3 years, some master students. –prof. Reidar Conradi, postdoc Daniela Cruzes, both IDI; f.aman. Alf Steinar Sætre, IØT; –a full-time coordinator and an action team of five persons from StatoilHydro.

Statoil-NTNU contact meeting, 25 May 2009 OSS Business Models - COSI ITEA2 project: New technology in upper-right corner (red), being eroded from lower-left (yellow). Maturing technology, from proprietary to open, towards lower-right corner (arrow on green diagonal).