ENGINEERING SYSTEMS-OF-SYSTEMS
“DTC IS THE SECRET-EDGE WEAPON OF THE SAF”
DR NG ENG HEN MINISTER FOR DEFENCE The opinions and views expressed in this work are the authors’ and do not necessarily reflect II the official views of the Ministry of Defence ENGINEERING SYSTEM-OF-SYSTEMS III TABLE OF CONTENTS
Foreword
Message
Preface
1 CHAPTER 1 : Evolution and Development of Island Air Defence System-of-Systems
31 CHAPTER 2 : Concepts to Capabilities
39 CHAPTER 3 : Software Systems Design and Realisation
52 CHAPTER 4 : Operations and Support Engineering
69 CHAPTER 5 : Systems Engineering Methodologies and Tools
95 CHAPTER 6 : Organisation and People Development
107 CHAPTER 7 : Beyond Defence
122 CHAPTER 8 : Advancing the DTC's Systems Approach through the Generations
131 CHAPTER 9 : Beyond DTC50
136 APPENDIX TO CHAPTER 2
144 APPENDIX TO CHAPTER 3
153 APPENDIX TO CHAPTER 4
158 APPENDIX TO CHAPTER 5
185 ACKNOWLEDGEMENTS
191 GLOSSARY
197 INDEX FOREWORD
The journey of Singapore’s Defence engineers and scientists stands at the frontier The stories that are told in this book series Technology Community (DTC) parallels of technological progress. Indeed the DTC is should lift the spirits of Singaporeans, old that of the Singapore Armed Forces (SAF) the secret-edge weapon of the SAF. and young. They celebrate what pioneers – indeed both were co-dependent and and successive generations of committed iterative processes which fed off As the DTC celebrates its 50th anniversary, scientists and engineers have accomplished each other’s success. Pioneers in both we want to thank especially its pioneers over the years. But they also give hope to our communities recognised very early on the who were committed to achieve the future, as they will serve as reminders during stark limitations of a small island with no unthinkable and were not daunted by severe difficult times to overcome challenges and geographical depth and limited manpower. challenges along the way. Their efforts and continue to keep Singapore safe and secure But despite this realisation, they were beliefs have spawned world class agencies for many years to come. undaunted and shared a common resolve such as DSTA and DSO, and the family of to mitigate Singapore’s vulnerabilities Singapore Technologies (ST) companies. and constraints, and build a credible SAF through sheer will, commitment and the More hearteningly, the virtuous effects harnessing of the powers of technology. In extend into mainstream society too. Dr Goh Keng Swee’s words, “we have to Today the defence cluster of DSTA, DSO, Dr Ng Eng Hen supplement the SAF’s manpower with new MINDEF, the SAF and ST employs the Minister for Defence technology, as manpower constraints will largest proportion of scientists and engineers Singapore always be there. Our dependency should in Singapore – almost one in every 12! It be more on technology than manpower. is not an overstatement that these entities And we must develop indigenously that have been the main receptacles to maintain technological edge.” As worthy and the science and technology capabilities in important as these ideals were, it was an our nation, providing life-long careers in the arduous journey for the DTC. With poor process. standards of general education, let alone engineers or scientists, how could Singapore Beyond defence, the DTC has also positively develop such capabilities? impacted our society in a variety of ways: in producing mass thermal scanners to combat This book series chronicles the last 50 years the 2003 SARS outbreak, in designing and of that ascent that begun in 1966. The DTC building the iconic Marina Bay Floating has indeed come a long way from its humble Platform to host the National Day Parades and beginnings and with it, a transformation sports events, in breaking new ground and of the SAF’s capabilities. Today, both old mindsets when we built the underground the SAF and the DTC are respected storage for munitions, in forming the nucleus professional bodies and the requests from to start the MRO (maintenance, repair and advanced economies to collaborate reflect overhaul) industries to service airlines in the standards which we have achieved. Singapore and globally. Our closely-knit community of defence
ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS MESSAGE
The Defence Technology Community (DTC) • The integration of the RSN’s missile renowned R&D partners locally and around has steadily evolved over the last 50 years. We gunboats and missile corvettes which the world, I am confident that the DTC will started off as a small, three-man technical built up the DTC’s confidence to move remain steadfast in delivering the critical department in the Logistics Division in 1966 on to specify and acquire best of breed technologies and innovative solutions for supporting defence equipment procurement systems to integrate into new ships like the SAF and the nation. May the stories in and there was much work to be done. The the frigates. It also laid the foundations these books inspire our current and future Army then was largely equipped with for ST Engineering’s capabilities to design defence engineers and scientists to continue second-hand vehicles and surplus equipment and build ships for the RSN and some to push boundaries and think creatively to left by the British. The Republic of other navies. deliver capabilities that will safeguard our Singapore Navy (RSN) had two boats, one • The conversion of old US Navy’s A-4 sovereignty for the years to come. steel and the other wooden. Recognising the Skyhawk aircraft into the A-4SU Super need to overcome the immutable challenges Skyhawk for the Republic of Singapore of geography and resource constraints Air Force, building up ST Engineering’s facing Singapore, we extended our scope to capabilities to undertake further aircraft include conceptualisation, development and upgrades such as for the F-5E Tiger fighter upgrade of defence systems. These efforts aircraft, and to undertake servicing and Mr Ng Chee Khern leverage the force multiplying effects of repair of commercial aircraft. Permanent Secretary (Defence Development) technology to meet the unique challenges • The system-of-systems integration Ministry of Defence, Singapore and operational requirements of the Singapore efforts to evolve the island air defence Armed Forces (SAF), beyond what could be system, building on legacy systems left had buying off-the-shelf. by the British to seamlessly incorporate new weapons, sensors, and indigenously This four-book “Engineering Singapore’s developed command and control systems Defence – The Early Years” series covers the to extend the range and coverage of entire spectrum of the DTC’s work in the Singapore’s air defence umbrella, and land, air and sea domains to deliver cutting- the build-up of the DTC as a system-of- edge technological capabilities to the SAF. systems to deliver cutting-edge capabilities It chronicles our 50-year journey and and systems to the SAF, and to meet the documents the largely unheard stories of technology requirements of the nation. our people – their challenges, struggles and triumphs, their resolve and ingenuity, and While not exhaustive, these stories provide their persistence in overcoming the odds. us with a glimpse of the “dare-to-do” and These stories include: enterprising spirit that our DTC personnel and forerunners possess. • The upgrading of the French-made AMX-13 light tank to the AMX-13 SM1 There is no end to change and transformation. configuration by the DTC, the Army and Singapore and the SAF will continue to face ST Engineering, laying the foundation for many challenges in the years ahead. However, the design, engineering and production of with the capabilities and expertise developed the Bionix, Bronco and Terrex armoured over the years in its more than 5,000-strong fighting vehicles for the Army. personnel, and its established linkages with
ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS The engineering challenges of safeguarding depth via the use of stealth, speed and fast such as ground-based radars, surface-to-air Singapore’s security have involved overcoming decision cycles, with advanced platform missile systems, aircraft and command and the twin constraints of size (resources, technologies and C4ISR as critical enablers. control (C2) systems that work cooperatively PREFACE especially population) and strategic depth Yet another approach is to employ resilient to defend the skies of Singapore. In Chapter 1 (geographical space). Having a modest number networks and systems, with protective we will look at the history of how Singapore of high quality and high readiness defence technologies and system architectures as built up its IAD capability from the 1960s to systems that are capable of multiple roles critical enablers. the present, first by acquiring and developing provides a strong foundation for our defence, systems and subsequently evolving systems but how can we scale this to the level required Third, the achievement of sustainability over into a Defence SoS in the 2000s. for our needs? time requires efforts in multiple thrusts. One is to design adaptable and resilient systems By Enabling SoS, we refer to an integrated Our defence engineers have applied systems and architectures, including the ability collection of systems that enables the existence thinking and engineering approaches for legacy systems to be enhanced and of the Defence SoS, from designing it, to to overcome some of these challenges. integrated with new systems, enabled by implementing it, to sustaining it throughout A fundamental approach is to create a systems architecting. Another is to ensure its lifetime. An example is the Defence System-of-Systems (SoS) by integrating high reliability and readiness of systems, Technology Community (DTC), comprising individual systems together such that the enabled by a strong engineering and logistics an interdependent ecosystem of engineering SoS will have unique emergent properties capability. Yet another is to have highly organisations and methodologies that work in not available from the constituent systems trained, competent and motivated personnel, concert to deliver the Singapore Armed Forces' in themselves. Some of these properties include enabled by organisational development and technological systems (hardware, software). enhanced situational awareness, cooperative learning. Sound planning and execution Our defence systems have been engineered engagement, speed (both in decision with holistic and longer-term perspectives and supported by the DTC over the past 50 making and execution) as well as resilience. are also key, enabled by a defence capability years. This accumulated knowledge base and development and management system. the experience and expertise of our defence The desired emergent capabilities (or desired Finally, it is important to have a system that engineers form a formidable resource pool defence and security effects) of these SoS encourages innovation and learning, enabled that can be aptly termed an Enabling SoS. may be categorised into effecting force by a culture where its people “dare to dream multiplication, creating strategic depth, and to act upon these dreams”. The rest of the book will expound on the DTC enhancing sustainability and operating Enabling SoS. From Chapters 2 to 8, we will effectively in complex environments. These Fourth, the ability to operate effectively in examine more details of the DTC Enabling are elaborated as follows: complex environments is enabled by sense- SoS. Chapter 2 – Concepts to Capabilities making and C4ISR systems and users that will share more of how concepts and First, force multiplication is the ability to are accustomed to working in complex and requirements for Defence systems and SoS are deploy technology-enabled flexible force uncertain environments and who are tech- formulated before implementation; Chapter structures that can mass at decisive points savvy and well-schooled in complex systems 3 – Software Systems Design and Realisation to achieve superior combat power. The thinking. will elaborate on software systems (C2 and critical enablers for force multiplication are Enterprise Information Technology (IT) interoperability and Command, Control, For the purpose of this book, we will introduce systems) – a critical component that "glues" Communications, Computers, Intelligence, two notional categories of SoS – Defence SoS together different systems into a Defence Surveillance and Reconnaissance (C4ISR). and Enabling SoS. SoS; Chapter 4 – Operations and Support Engineering will illuminate a critical area that Second, strategic depth in both the space and By Defence SoS, we refer to an integrated is often away from the limelight, but one that time dimensions can be created via several collection of individual military systems enables defence systems and SoS to sustain complementary approaches. One is to provide required to defend Singapore by fulfilling their performance and viability. Chapter 5 foresight and early warning through the specific military operations such as air defence, – Systems Engineering Methodologies and exploitation and smart use of information, maritime security and land battle. An example Tools will provide more insights on the key with C4ISR and sense-making systems as is the networked Island Air Defence (IAD) SoS systems engineering methodologies and tools critical enablers. Another is to create virtual that comprises a suite of individual systems used in the DTC, in addition to those already
ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS Chapter One covered from Chapters 2 to 5; Chapter 6 offering food for thought in DTC's journey EVOLUTION AND Recollections of Prof Lui Pao Chuen, – Organisation and People Development ahead. Chapter 9 – Beyond DTC50, is a think DEVELOPMENT OF Er. BG (Ret) Wesley D'aranjo and Mr will trace how the organisations within piece with its focus on the decades ahead, William Lau Yue Khei on the journey DTC evolved over time, together with the examining the trends and constants that will ISLAND AIR DEFENCE in building up Singapore's IAD systems build-up of a critical mass of engineering shape the DTC and its contributions to the SYSTEM-OF-SYSTEMS from the 1960s to 1990s. and scientific expertise; Chapter 7 – Beyond long term survival, security and success of Defence will bring the reader beyond the Singapore as a nation. Five Power Defence Arrangements defence context in areas that DTC has and Integrated Air Defence System made significant impact with its engineering A Historical Narrative of Building and scientific expertise; and Chapter 8 – Singapore's Island Air Defence There was great fear that confidence in Advancing DTC's Systems Approach through Systems from the 1960s to 1990s Malaysia and Singapore would dip without the Generations will highlight key success the air umbrella provided by the Royal factors for the DTC thus far, summarising our RADM (Ret) Richard Lim A Journey Fuelled by a Need and Air Force (RAF). To allay this fear, the lineage of systems engineering leaders and Editor, Engineering Systems-of-Systems a Vision United Kingdom (UK) organised a Five Power Defence Conference with Australia, The evolution of Singapore's Island Air New Zealand, Malaysia and Singapore in Defence (IAD) system provides a useful Kuala Lumpur on 10th and 11th June 1968 narrative of the development of a Defence to address the issue of the needs for the System-of-Systems (SoS). At the same time it defence of Malaysia and Singapore. Volatile and Uncertain Environment illustrates the parallel development of some of the engineering capabilities and organisations The five countries agreed that in the that today form the Defence Technology event of an armed attack or such a threat, Community (DTC) – the Enabling SoS for the governments concerned would Force Multiplication, Strategic Depth, Sustainability, Effective Operations in Complex Environment Singapore's defence. immediately consult with one another Defence System-of-Systems (SoS) to decide on measures to be taken. The Mission Systems and Stakeholder Requirements In the early years, there was no established Five Power Defence Arrangements would SoS E.g. Island Air • Mission Performance • Secret Edge systems engineering body of knowledge be established with a Joint Consultative Defence SoS • Affordability • Self-Reliance • Reliability, Maintainability • Smart Buyer to take reference from. The Ministry of Council comprising the respective System System • Radar systems • Availability, Sustainability • Smart User A N • Missile systems • Robustness, Resilience • Etc Defence (MINDEF) Life Cycle Management Permanent Secretaries for defence of • C2 systems • Flexibility, Evolvability • Interoperability (LCM) Manual only came into being many Malaysia and Singapore, and the High System • Etc • Etc B years later. This was a journey of learning Commissioners of the UK, Australia and through trial and error by taking calculated New Zealand, and with an Air Defence risks and measured steps. Two factors made Council responsible for the functioning of this possible. First, the strong belief by the Integrated Air Defence System (IADS) Defence Technology Enabling System-of-Systems senior leadership within MINDEF that we and to provide direction for the Air Defence DTC Organisations and People needed to build a strong indigenous systems Commander. engineering capability and their trust and Systems Engineering Methodologies support given to our young engineers and IADS became operational on 1st September Long-Term Front-End Acquisition Transition Operations System Planning Planning Management to O&S & Support Retirement the fledgling engineering organisations that 1971 just before the complete withdrawal were established. Second, it was probably of UK troops. The headquarters of IADS fortuitous that we had very limited resources (HQ IADS) was located in Royal Malaysian Relationship between Defence SoS and Enabling SoS to engage foreign consultants and defence Air Force (RMAF) Butterworth Air Base contractors to meet our needs. Hence, there and the Commander IADS would be a was no easy way out but to do many things two-star Air Vice-Marshal of the Royal ourselves. Australian Air Force (RAAF). The staff of the IADS would come from the five nations.
ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 1 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
The RAAF with its fighter wing of French- The Bloodhound missile would be accelerated components that required regular servicing. made Mirage fighters would continue to by four boost rocket motors to a speed of Mach The missiles from the missile site at Lim operate from Butterworth, as they had 2.5 in three seconds. The spent rocket casings Chu Kang Hill would have to traverse half since 1955 with two fighter squadrons and would peel away and the Thor ramjet engines the island to get to the maintenance shops one bomber squadron. In 1970 the RAAF would continue propelling the missile to its of the squadron in Seletar. Each trip was a handed over Butterworth Air Base to the target. The prescribed safety distance was major logistics operation as a collision of the Malaysian Government and it became RMAF three miles around the launcher. This safety missile carrying vehicle could cause serious Butterworth Air Base. distance and height constraint around the damage. Because of all the care taken for each missile site resulted in the loss of development operation there were no road accidents with One RAAF Mirage squadron would be potential by the Housing and Development the Bloodhound missiles. deployed to Tengah Air Base from time to Board for Ang Mo Kio New Town. time for exercises to defend the southern From RAF Gombak Radar Unit to Air sector with the Bloodhound surface-to-air One Bloodhound missile was fired during its Defence Radar Unit missile (SAM) squadron. The late Mr Pang Tee Pow (left), then service with the Republic of Singapore Air Permanent Secretary (Defence), accepting Force (RSAF). The firing took place on 24th Bloodhound Surface-to-Air Missiles the handover of the Bloodhound SAM September 1980 at UK Ministry of Defence Squadron from a British Aircraft Corporation (MOD) Aberporth in Wales in the UK. MOD RAF No.65 Squadron with three sections representative in 1974 Aberporth has played a significant part in deployed at the north-eastern end of Seletar the development and testing of a variety of Air Base formed part of the RAF Far East Air military weapons and is still in use today. CPT Force. The Bloodhound Mk2 was the most Martin Baptist, a Bloodhound Engagement modern SAM with a range of 80km covering Controller from 170 Squadron, had the honour altitudes from 150ft to 65,000ft (around 46m of firing a missile selected randomly from the to 20km). The missile, powered by ramjet RSAF's inventory of Bloodhound missiles. engines would achieve a maximum velocity Soon after launch, the missile lost lock with of Mach 2.7 in its flight out to intercept its TIR but it was expertly re-acquired by CPT targets with speed of Mach 2 at a range Martin Baptist who continued to complete The Island Air Defence System in of more than 80km. The missile would be the engagement successfully. A “hit” with the early 1980s guided to its target by a target tracking and a miss distance of 69ft was recorded, well illumination radar (TIR), the Marconi Type within the lethality range of 180ft of the The radars and operations centre of the 97 Scorpion radar. warhead. The missile fired by the RSAF was RAF air defence system for Singapore and Bloodhound missile section deployed at the hundredth Bloodhound missile ever to southern Malaya were located on the top The Bloodhound squadron was however Seletar Air Base be launched. of Bukit Gombak, the second highest hill vulnerable as the launchers were fixed and in Singapore. The civilian air traffic control could be attacked with low-cost mortar The technical challenge in re-deploying the centre at Paya Lebar Airport hosted the bombs. Operational analysis studies showed two sections of Bloodhound missiles from Joint Air Traffic Control Centre (JATCC). A that the vulnerability would be greatly reduced Seletar was its re-integration with the search microwave communication system connected if two sections of Bloodhound missiles could radars and the GL-161 control centre of the the Gombak operations centre with JATCC, be deployed to other parts of the island. The Air Defence Radar Unit (ADRU) on the the operations centres of Tengah Air Base best site would be on the top of Lim Chu Kang top of Bukit Gombak. The air defence and Changi Air Base, and the Bloodhound Hill, just north of the Nanyang University controllers in ADRU would need to be squadron at Seletar. This was the most campus. The second best site would be at connected in real time to the Bloodhound comprehensive air defence system of the RAF Amoy Quee Camp. missile controllers at the three sites to outside the UK. Another view of Bloodhound missile share radar target data. deployment in 1974 The air defence system for northern Malaya The Bloodhound missile was effectively an consisted of radars and a control station unmanned aircraft with two ramjet engines located on Western Hill in Penang with two and electronic and electro-mechanical fighter squadrons based in the RAF airbase
2 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 3 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
at Butterworth. Western Hill is the highest provided “raw radar” video to the GL-161 for point in Penang at an elevation of 833m above processing and display. In those days, the Air sea level. A radar deployed at this site could Force operators preferred “raw radar” video detect targets from sea level to radar horizon. because, with experience, they could perceive It would be very difficult for enemy attack from the “raw radar” video information on aircraft to sneak into the defended airspace aircraft turning (that was not available from without being detected. synthetic extracted plots). Hence, they could predict what the targets would do by looking Given the limited height of our hills in at the dynamics of the “raw radar” video. As Singapore for deploying ground-based radars, sensors later became digital, “raw radar” video attacking aircraft flying low and hidden by was replaced by regenerated video (1986) and terrain features could not be detected till they later with symbols (1990s). There was a lot were 10km away. The defeat of attacking of debate in the Air Force then between the aircraft appearing at this range could only utility of “raw” versus “processed” video. It be achieved with low level SAM and anti- An Air Defence controller and his assistant A very large room of vacuum tube was expensive to handle “raw video” all the aircraft (AA) guns. at work in a pitch-dark operations room electronics re-designed and miniaturised way from the radar head. into two racks The two operations centres were connected CPT Wesley D'aranjo, an electrical and Mobile Operations Control Centre by a modern tropospheric scatter radio link electronic engineering graduate from Special Projects Organisation (also known as “troposcatter”). The RAF IADS the University of Manchester Institute of The acquisition from Plessey of a mobile was handed over to Malaysia and Singapore Science and Technology, was posted from In 1979, the Special Projects Organisation operations control centre (MOCC) was during the withdrawal of UK troops. the Singapore Army (the Army) to ADRU. (SPO) headed by then LTC Lui Pao Chuen one of the solutions selected to replace the He learnt the intricacies of radars, radios, as its Special Projects Director (SPD), was GL-161. MINDEF chose to purchase the All the radars deployed on the top of computers and display, and systems integration formed. This was part of MINDEF's efforts MOCC separately from the radar sensors. Bukit Gombak were exposed and could be by being hands-on. He took the initiative to to develop defence technological capabilities This meant that we took upon ourselves the harassed by air and artillery attacks. The replace all the vacuum tube electronics with and to undertake complex defence acquisition responsibility to integrate the MOCC with operations control centre was located inside transistors and integrated circuits. This was projects. SPO comprised five project divisions the radar sensors. The motivation for this a light building that had not been built to the first major upgrade of a complex radar (PD): PD1 to PD5. was the ability to keep knowledge of some of resist weapon effects. Space diversity would and control centre. its capabilities confidential and also to have therefore be required to reduce the chances of GL-161 Air Defence Command and the flexibility to “mix and match” systems to our air operations being disrupted by enemy Control System meet the operational requirements. action. Relocating the large stationary radars was one solution studied. The conclusion of Even at that time, SPD Lui understood that it The plan was to use the MOCC as a launch the operations research studies was that a was important for the then Defence Science pad for the build-up of the defence software mobile radar and mobile operations control Organisation (DSO) to build up capability to capability in DSO. A team comprising six fresh centre would be a more robust solution. The master the software of command and control graduates and experienced technicians from best mobile three-dimensional (3D) radar systems. He called this area “real-time” the Air Force was sent to Surrey, UK to master then was the AN/TPS-43 operated by the software and later DSO called it “defence the inner workings of the Plessey MOCC. US Air Force. The radar was manufactured software”. This real-time software processed by Westinghouse. The radar equipment and data from radar sensors and converted them There were two processing chains in the operational consoles were fitted inside cabins into useful information for the Air Force MOCC, each powered by a DEC PDP-11/34 that could be towed to alternate deployment The team that re-designed, upgraded operators in the control centres. processor. Each chain had a magnetic disk sites within a few hours. and manufactured new electronics for drive, which was not the most reliable for radars and signal processing at ADRU The British left behind the GL-161 which, a transportable cabin. The software was Integration with the GL-161 system in the at that time, was their latest real-time written in a now defunct high-level language operations centre at ADRU was a technical computerised air defence command and called RTL/2. Through RTL/2 the team challenge that kept the radar engineers very control system. The GL-161 was capable learned how to design software in modules busy but happy. of computing air intercepts. Radar sensors (called “bricks”). RTL/2 also had the “CODE”
4 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 5 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
statement which allowed the program to The team worked with Plessey to learn how models that specify the radar cross-section jump to assembler coding to achieve critical to integrate the ITT-RS320 radar but did of a given object. There were five types of real-time performance where needed. An the integration with the other two radars Swerling target models using a distribution in important aspect of a command and control independently. the location-scale family of the “chi-squared system that the team learned was how to distribution”. The ITT-RS320 did not meet achieve high availability through the switch- One challenge the team faced was that the the range detection performance the Air over between two processing chains. radar message formats were non-standard, Force wanted. What followed was a very unlike, for example, the Eurocontrol ASTERIX difficult and protracted negotiation with the Indigenous Systems Integration protocols of today. Each radar type had its own manufacturer on how the Swerling target unique interface specifications. This meant The ITT-RS320 radar models had been misinterpreted by us. The When the MOCC team returned to Singapore, that a common suite of utilities could not be performance of the radar was as it was, and it set about integrating the MOCC with three developed to interpret them. Each software Another challenge was that the interfaces were that we should have known better! In short, radars in parallel, almost simultaneously: interface had to be separately developed and of the synchronous type (this required tight the radar manufacturer's response was “you the team had to figure out where and how synchronisation between signal transmission tell me the answer you want and I will give • The existing mobile AN/TPS-43F – first to insert these pieces of software into the and signal reception mechanisms) which you a calculation for it”! Thereafter, this operational in 1975 as the AN/TPS-43DX MOCC. The radar manufacturers did not made them much more difficult to work with. bitter lesson taught us to use an unambiguous and then upgraded to improve radar provide any tools, not even a radar simulator. target – a “clean” F-5E aircraft flying head-on performance and allow integration with The team had no choice but to work with the So how did this team overcome all these into the radar, as the basis for contractual a control centre Interface Requirement Specifications (IRS) of challenges? First, it set about building an in- specification and performance verification. • The new ITT-RS320 each radar type and testing had to be done house tool to decode and process the different • The Hollandse Signaalapparaten LAR2 with live radar data. data formats. In 1985, the team made use Second, we discovered that the primary radar at the Long Range Radar and Display of an Apple IIe computer with an interface plots were out-of-sync with the secondary System I air traffic control centre at card that it fabricated to receive and decode surveillance radar plots. This was discovered Changi Airport – the LAR2 radar was the synchronous data coming from the radar through painstaking data analysis. This was commissioned in 1981 under live test. This must have been one most likely due to a design flaw that was of the first uses of the Apple IIe for serious not discovered during acceptance testing of All three radars were just being brought work! It also used a protocol analyser to the ITT-RS320. The secondary surveillance into service or newly commissioned! view the raw data. By doing this, the team radar plots were received much later and The MOCC came with the source codes was able to verify the correctness of the IRS therefore were not able to correlate with (except for the core operating system and eventually write the driver modules in tracks that were initiated from the primary called MTS-3G) compiler, linker and other the MOCC that were able to take in the radar plots. MINDEF reported the problem software tools. radar data correctly to be processed by the to the manufacturer but they could not fix MOCC tracker. it. The team eventually solved the problem The ITT-RS320 was developed for Sweden by modifying the MOCC tracking software and only 17 such radars were produced – 16 Other Radar Issues to delay the tracking sector which in turn for Sweden and one for Singapore. It was delayed the track-to-plot correlation process. the most advanced “pencil beam steering” Unlike the other two Air Force radars the This allowed more time for the secondary 3D radar available then and an improvement LAR2 was not a 3D radar. As the MOCC surveillance radar plots to come in for proper over the AN/TPS-32. The Swedes used their required plot height data, a fictitious height correlation. radars very cleverly. Each was installed on had to be set as a default value and this caused a 30m mast and protected in silos. Then, a the Air Force operators some consternation The integration of MOCC and ITT-RS320 was game of “musical chairs” would be played when such tracks were displayed, all with a big challenge. The non-release of software and surveillance achieved by elevating and the same height. by Plessey was a painful but very useful lowering the radars tactically. The radar learning exercise. The lessons learned were would be allowed to “blink” during the time We also had several issues with the ITT- applied to the purchase of the next generation it was exposed. The mast was an ordinary The AN/TPS-43F radar at a RS320 radar. First, we learned that one should of command and control system with the mast, the type used at construction sites. deployment site not specify and test radar range detection demand that the software be developed by a performance with theoretical Swerling target joint venture between Singapore Technologies
6 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 7 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
(ST) and Ericsson Microwave System called • Two squadrons of Hawker Hunter The pilot would need to aim at the target Twelve fire units, each comprising one unit “Software Engineering of Singapore”. fighter aircraft and to release the bombs. The time for this of fire control equipment and two guns, • Two squadrons of Next Generation depended on the skill of the pilot. Experienced were purchased (the guns are highly reliable The lessons learned from bravely taking fighter aircraft pilots would take less than two seconds and and with proper maintenance they remain on the systems integration tasks for the • Two airbases (Tengah and Changi) “rookies” up to six seconds. Thus the window operational to date). The analogue computer MOCC enabled the team to increase its • One squadron of Bloodhound SAM system of opportunity to shoot a fighter down would of the Superfledermaus was replaced in the confidence to take on more challenging • One air defence radar unit be between two to six seconds. early 1980s after about 10 years of service. projects in the future. • One mobile 3D air defence radar The tracking radar and optical sights had also
• One squadron of low level SAM system The Pk would therefore depend on the number seen many upgrades. The only original parts Link to HQ IADS Butterworth (Rapier was the prime candidate) of rounds the AA guns could fire in a two- of the Superfledermaus still in service are the • One squadron of Oerlikon 35mm second burst. The designer of the Oerlikon cabinets and mechanical components. Around 1987, MINDEF had offered to cross- AA guns 35mm AA guns had figured this out and had tell tracks from the MOCC to HQ IADS two barrels in each gun. With a combined rate- The maximum engagement range of 5km by at Butterworth in Malaysia to facilitate The acquisition of AA guns to protect vital of-fire of 1,100 rounds per minute from the the Oerlikon guns will require the target to exercises. The team developed and installed a assets began in early 1968 with the evaluation two barrels it was clearly superior compared be detected beyond this range. A search radar PDP11/34 serial interface card in the MOCC of the Bofors 40mm AA gun from Sweden to the single barrel Bofors gun which had a with a range exceeding 10km will enhance and another external interface box to re- and the Oerlikon twin 35mm AA guns from rate-of-fire of 330 rounds per minute. the effectiveness of the fire unit. format the track messages and send them via Switzerland. The fire control system of the a leased telephone line to Butterworth. At the Bofors 40mm AA gun, the L4/5, was made In 1969 a team comprising LTC M S Gill, Chief The radars at ADRU could not detect attackers Singapore end, the team also implemented a by Hollandse Signaalapparaten. The fire of Artillery, LTC Chew Bak Khoon, Chief approaching at low level. The Giraffe radar with large screen display projected from a Barco control equipment for the 35mm AA guns, Communications and Electronics Officer, a 12m high antenna mast, made by Ericsson projector connected to an International Superfledermaus, was made by Contraves of CPT Henry Cheong and CPT Lui Pao Chuen Microwave Systems for the Swedish Armed Business Machines Corporation (IBM) 286 Switzerland. visited Switzerland and Holland to verify Forces, was found to be the most effective radar AT PC that interpreted the tracks coming the performance of both systems during to cover the low level gap. It could provide from the interface box. The first study visit to Switzerland in March firing exercises and the logistics support direction to the Superfledermaus fire control 1968 was conducted by COL Kirpa Ram Vij, required. tracking radar to search and track targets. Singapore Air Defence System, Version 1 Director SAFTI and CPT Lui Pao Chuen, then Head Technical Department, Logistics The candidates for the low level SAM missile Following the decision to purchase the Division. system and their average fire unit cost (in Hunter fighter aircraft and Bloodhound Singapore dollars) were: SAM system, the Singapore Government The Bofors 40mm AA gun had the advantage decided expatriate officers would be of being the AA gun of the allied navies • Rapier (UK), $8m employed to build up the Air Force, during World War II. It was battle proven • Blindfire Rapier (UK), $14m known then as the Singapore Air Defence and remained the market leader after • Roland II (Germany), $21m Command (SADC). the war. • Crotale (France), $21m • Indigo (Italy), $20m In 1971 Brigadier General (BG) John Langer Operations research had shown that the was seconded by the RAF to be the first claims of both manufacturers (that the All the systems, except for Rapier, were radar
Director of Air Staff, MINDEF. The Head Probability of Kill (Pk) exceeded 0.8) were CPT Lui Pao Chuen (left) and CPT Henry guided and had an effective engagement range of Air Operations was Group Captain (GC) true only for the engagement of targets Cheong (second from left) in discussion with of 10km when there was a line-of-sight to the Marie Turnbull. The Head Air Logistics was flying straight and level, such as when firing personnel from Hollandse Signaalapparaten target beyond this range. Operations research GC Basil Fox. Head Air Engineering was Mr at banner targets towed by an aircraft. In in 1969 during the evaluation of the fire in the UK showed that in most scenarios Wong Yeok Yeok, a very experienced and an attack, fighters would be “jinking”, i.e. control radar for AA guns. detection of low flying aircraft could only be respected aircraft engineer seconded from executing evasive manoeuvres with sudden achieved by 10km and therefore a maximum Singapore Airlines. changes in direction, which made it very On completion of the evaluation the team engagement range of 6km for the missile difficult for the fire control system to predict recommended the Oerlikon 35mm AA guns would be sufficient. Rapier and Blindfire The SADC Order of Battle (ORBAT) would the future position of the aircraft for the AA and Superfledermaus fire control equipment Rapier had been designed to defeat attacking consist of: rounds to score a hit. for the Singapore Armed Forces (SAF). targets at 6km.
8 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 9 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
Rapier was selected for the SAF. Rapier had Stinger versus RBS-70 be defeated by fighter aircraft manoeuvre while searching and acquiring targets. The the cost advantage and being modular in and flares. critical need of target acquisition was met and design allowed a night engagement capability In 1974 the Army had determined an enhanced with the use of the Giraffe radar to to be added with the DN181 “Blindfire” operational need for the defence of Army The command line-of-sight guidance of detect targets and designate them to the fire radar. Slightly earlier, the US Air Force had units in the field. Though foliage and Blowpipe required the operator to guide the unit. The operator would then need to search conducted a competition for the acquisition camouflage would provide the best defence missile to target with a thumb joy stick on in the designated piece of sky and acquire of a low level air defence SAM system for from air attacks, the movement of armoured the aiming unit clipped to the launching tube. it as soon as it appeared in his sight. Target the protection of their airbases in Europe. units along roads and open ground would Target acquisition was very difficult and to identification would be determined initially However, Roland II was the winner of this expose them to attacks by fighter ground guide the missile required skills that would by air defence controllers in the Giraffe radar competition. attack aircraft and attack helicopters. be difficult for National Servicemen (NSmen). control cabin via their own aircraft situation This assessment was proven correct by the picture which was also connected to the Mr Norman Augustine, Under Secretary of Mobile air defence of armoured units is very operational use of Blowpipe by UK troops in regional air force operations control centre. the US Army, visited Singapore in the mid demanding. The very short range of combat the Falklands War. There were reports that The commander and gunner would make 1970s. A member of his delegation was BG required automatic detection and tracking of the 100 Blowpipe missiles launched only the final confirmation using IFF and optical John Dean, the project officer who had led of targets from the moving AA tank and nine scored hits against slow flying aircraft recognition. The chance of fratricide of RBS- the competition for the US Air Force low engagement within the dead zone of 1km and helicopters. 70 was greatly reduced as compared to Stinger. level air defence SAM system. He shared that of SAMs. Dr Buehler, then Chairman of The missile was immune to flares as it was Roland II won because it had an automatic Oerlikon, had identified this need and used The two finalists were Stinger and the Bofors guided to target riding on a laser beam that missile loader and a magazine that allowed company funds to develop a turret armed with RBS-70 used by the Swedish Army. the missile operator aimed at the target. 12 missiles to be launched before requiring twin Oerlikon 35mm AA guns and a radar reloading. Rapier had only four rounds on fire control mounted on a Leopard chassis. The advantage of Stinger was its “fire-and- RBS-70 was clearly a superior air defence fixed launcher rails. The RAF had found that The German Army evaluated and found forget” capability. However, target acquisition weapon system. However, one disadvantage in scenarios of less than 18 attacking aircraft, that this system best met their operational was a serious problem as the operator would assessed was that the operator would need a target defended by six Rapier fire units was requirements and purchased it. This AA tank need to find his target in his sight from verbal to track the target to keep the laser beam the most cost-effective system. In the most was named “Gepard”. directions provided by the commander and on it. This required the operator to be well demanding scenario of the US Air Force, with other crew members of his vehicle. Fratricide trained and calm when engaging a target. 54 attacking aircraft, Roland II was superior Unlike the German Army, the US Army was assessed to be a serious challenge as As operators could be expected to be excited as engagement opportunities were lost during did not have such a stringent operational the commander and gunner would have to and scared during combat, there was a need reloading of Rapier missiles. requirement. In their concept of operation decide if a target was “friend or foe” mainly to assess the loss of intercept performance a conflict would begin with air superiority by visual aircraft recognition. The simple under emotional stress. This information was helpful as it confirmed missions, which the US Air Force would Identification Friend or Foe (IFF) equipment the cost effectiveness of Rapier, determined undertake and complete before combat on mounted on the sight could help to identify To confirm the performance of our operators by our operations analysis studies. the ground began. A simple man-portable friendly aircraft if their IFF transponders locally, Bofors was requested to bring a training SAM, “Redeye”, was issued to their armoured were switched on. However, an aircraft system to Singapore for test and evaluation units for self-defence. Development of without IFF returns could be a friendly with from September to October 1977. The air Stinger to replace Redeye began in 1967 and its IFF turned off or not serviceable. The defence of army units was the responsibility adopted for service in 1972. commander with the help of his binoculars of the Army. Thus G5 Army led the test and would have to make the final decision to evaluation programme. The Chief of Artillery Our Army wanted Stinger as Gepard did launch the missile. The missile seeker was was the Senior Specialist Staff Officer for not meet their operational requirement. The assessed to be vulnerable to flares dropped by Army air defence and 160 Battalion, the AA candidates for this competition were: attacking aircraft. The weight of the launcher gun battalion, was an artillery unit then. The and missile at 15kg was heavy for our soldiers RSAF experts on SAM operation were from the • Redeye (US) to carry on their shoulders to search and 170 Squadron, the Bloodhound SAM unit. Air • Blowpipe (UK) acquire targets. Operations Department was a key participant • Stinger (US) as flying of aircraft for the tests would be its Illustration of multi-layered Island Air • RBS-70 (Sweden) For the RBS-70, the Swedes overcame the responsibility. Technical evaluation would be Defence System weight problem by using a stand to support done by Systems Integration Management Redeye was ruled out, as the missile could the launcher. The operator could then sit Team and Electronic Test Centre (now
10 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 11 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
known as DSO). This test and evaluation to Bofors to be trained on the operation and • Dedicated communications system The following were the requirements for programme was a landmark with the Army maintenance of RBS-70. In May 1980, on between commander and firer the new system. In effect, a completely new working closely with the RSAF in the completion of the training programme, a live- • IFF system with the antenna integrated system evolved: planning and execution of the programme. firing exercise was conducted at the Swedish with the transceiver Eight Non-Commissioned Officers from the missile range RFN located at Vidsel, close to • Target data receiver (TDR) • The fire unit had to be installed in 160 Battalion and 170 Squadron were trained the Arctic Circle. • Missiles the V-200 and operated in two modes by a team from Bofors on the operation of – inside the vehicle for transit and the RBS-70 missile system. A series of flight The RBS-70 project was the first project of The fire unit communicated with the Giraffe administrative moves, and elevated for trials was conducted in Changi and the final the Project Management Team (PMT) formed radar via the TDR only. target engagement. demonstration was conducted for VIPs in to take care of air defence projects. The PMT • The V-200 needed the following new October 1977. was the predecessor, and later formed one of mechanical parts: the divisions of the SPO. Today, we speak o redesigned top deck In the operational evaluation of RBS-70 in easily and confidently about missile systems, o new cupola standalone configuration and using fighter interfaces, integration, command line-of-sight o ready-use-missile container on the aircraft as targets, the average reaction time guidance, radars, data links and so on. At new top deck was found to be longer as compared to the that time, all of these were entirely new and o easy-to-use elevating platform to timing in the specifications. The latter could perhaps even “Greek” to novices who had to which the sight and stand were rarely be achieved even under ideal conditions. deliver such projects. “Daring” engineering installed and secured easily, and However, the test and evaluation was done work was undertaken by ourselves, despite the removed quickly if the fire unit needed without the critical Giraffe radar to enhance fact that we were completely inexperienced to redeploy outside the vehicle target acquisition. With the subsequent and had very few teachers to learn from. The o racks for missile storage in the V-200 integration of a Giraffe radar and the Air SAF constantly needed something “different”. o adjustable stand for the TDR Force air operations centres, reaction time Yet, the conventional wisdom was to leave • The fire unit communications system would be shorter and this would improve such requests for changes and modifications had to be interfaced to the combat radio the performance of RBS-70 and allow the to the overseas manufacturers. system of the V-200, and CVC helmets maximum range of the missile to be exploited. used instead of the RBS-70 headset. In order to keep up with armoured units, • The IFF antenna had to be split from its the RBS-70 system had to be installed in an transceiver and placed in front of the armoured vehicle. The V-200 was selected Firing of an RBS-70 missile from sight; the IFF transceiver was placed for this. This meant we decided to design, a V-200 vehicle low on the RBS-70 and lost line-of-sight develop, test locally as well as conduct live- when installed in the V-200 even in the firing in Sweden, and go into series production elevated mode. all on our own! • Ensure that operational and system technical performance – safety, shock The RBS-70 system was operated by a and vibration profiles, missile guidance, commander and firer. The complete fire unit DC power, ergonomics, coming-into- was designed for a “soft” ride and each major action and engagement workflow – was Local flight trials of RBS-70, component had its own protective transit case. not degraded by the new environment viewed by MINDEF officials, at Changi RBS-70 was designed for deployment on the in which the system was to be installed, Air Base in October 1977 ground; the Swedish Army had developed an transported and operated. optimal workflow for fire unit deployment • Conduct local trials to prove the viability RBS-70 was the obvious winner of the and target engagement. of the new system design (with very competition for an air defence weapon of limited test means and instrumentation the Army when the US disallowed the export The fire unit consisted of: available). of Stinger to Singapore. An initial purchase MINDEF and RSAF officials and • Prepare for live-firing trials at was made of one Giraffe radar and RBS-70 • Sight Singapore Air Defence Artillery operators Robotförsöksplats Norr (RFN) Vidsel, fire units and missiles for training in 1979. A • Stand with tripod legs onto which the at the live-firing exercise conducted at the Swedish missile test range inside team of 14 officers and 10 technicians went sight was attached RFN, Vidsel, circa 1980 the Arctic Circle.
12 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 13 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
• Take into consideration and prepare for both parties. The Bofors engineers were eventual production vis-à-vis the build-up pleasantly surprised by the amount of of Singapore Air Defence Artillery (SADA) information on operational concepts they battalions. had gained in the exchange. They were impressed by our solutions and concluded Work on the installation started towards the that the mounting would be safe and end of 1979. The team was well tutored by acceptable for firing the RBS-70 missile. SPD Lui. It consisted of CPT Wesley D'aranjo, one electronics technician “borrowed” from RBS-70 was designed for deployment on the ADRU and two mechanical technicians from ground. The Bofors engineers cautioned that Singapore Automotive Engineering, Mr Khoo the back blast of the missile could hit the top Wai Yeow and Mr Richard Kwok (now Dr deck of the V-200 for high elevation firings. Richard Kwok). SPD Lui was kind enough The back blast might rock the vehicle and to allow much time to complete the vehicle cause the laser guidance beam to be deflected V-200 and RBS-70 during for live-firing tests in Sweden. The second too much for the missile in flight resulting National Day Parade prototype had to be ready well before the in guidance loss and failure. To check if this firing date, which had already been set for would be a problem, we conducted two local early May 1980! simulated “high angle” firings with dummy Armburst missiles. Vehicle movements were The design for mounting the RBS-70 on measured and compared with the RBS-70 the V-200 – the “elevating platform” – was specifications for the allowable angular completed by March 1980. Two prototypes rotation rates of sight. were fabricated. The first prototype was used for various technical trials – vibration, During the May 1980 live firing exercise in shock, ergonomics and simulated firings – Sweden, and prior to each firing, the RBS- so as to verify the suitability of the design 70 sight was used intensely for numerous for operational use of the RBS-70. The first practice engagements. Ten missiles were fired prototype was subjected to a 5,000 mile successfully from the V-200. Our users, the endurance test over roads, tracks and cross- Swedish Army and Bofors were pleased with country at the Sungei Gedong armour driving the data collected based on a working model test track. Defects were analysed and the of the RBS-70 in the V-200. These firings design iterated to eliminate the causes of marked the end of the development period the defects. that lasted less than a year.
Some months later, we learned that Bofors By mid 1981, six prototype RBS-70/V-200 was planning to install RBS-70 in the vehicles were produced for further operational M113. Two engineers from Bofors came for evaluation and troop trials. These were a week to study our prototype. They wanted completed by September 1981 and all designs Air Defence Weapon Operators operating the RBS-70 Ground-Based Air Defence system to learn the methods we had adopted to “frozen”. Approval for series production was mounted on the V-200 Armoured Fighting Vehicle during Exercise Wallaby 2016 solve various problems, like the attenuation given and, in total, Singapore Automotive of vehicle vibrations, and elevating the sight Engineering delivered a considerable number RBS-70 versus Rapier out country. These units could enhance the from inside the vehicle to firing position. To of production vehicles by 1983. coverage but could not replace the need for encourage a more open exchange of views The selection of the Giraffe radar and RBS- national low level air defence units. and information, we took time to study their The RBS-70/V-200 vehicles have continued 70 precipitated a question as to whether air drawings and gave them our comments. to be used for air defence, air base defence defence units built for the Army could also be The second question was if the needs for In exchange, we received their drawings and island defence for many years. used for the low level air defence of Singapore. national low level air defence could be met by which contained some useful designs. This But, this would create a gap in the defence RBS-70. There would be economic benefits exchange of information was of benefit to of Singapore when the units were deployed to invest in RBS-70 instead of Rapier.
14 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 15 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
Rapier had a larger coverage against unserviceable assemblies and these would on fixed on-site infrastructure, it had the Army and MICOM were very resistant to manoeuvring targets equal to three times be replaced with spares. The assemblies flexibility to be deployed in other parts of the any configuration changes and dissuaded us that of RBS-70. Comparison of costs would be removed would then be sent to the battery island beyond the existing SAM sites. This from doing so. Their constant refrain was: “If based on one unit of Rapier versus three units maintenance unit for tests by an Automatic would enable the land at the Bloodhound anything goes wrong, it's your responsibility”. of RBS-70. As national air defence would need Test Equipment (ATE) and the sub-assemblies missile sites at Seletar and Amoy Quee to In addition to introducing the Super Giraffes, to be operational over long periods, the extent identified to be unserviceable would be sent to be returned to the State for re-development. we made several other configuration changes of manning time was a critical parameter. the manufacturer for repairs. The turnaround The lifting of height constraints to buildings that resulted in better performance and used time was long using this maintenance support in the immediate vicinity of Amoy Quee more modern equipment than those offered system. would also unlock development potential by the US Army. This resulted in considerable of the surrounding area. Overall, this would savings and significantly lower life cycle As distances to the deployment sites in result in huge benefits to the nation. costs. Two examples are described here. Singapore were short, a central supply and maintenance base using factory test The US Army deployed I-Hawk in a The power source for I-Hawk was the equipment and technicians would be standard “battalion” configuration. Studies MEP-115, a venerable 60kW, 400Hz diesel more efficient. Initially, the manufacturer of other users worldwide revealed that generator. It was antiquated and expensive. objected, as this had never done before, the deployment area for the “battalion” The MEP-115 was the US Army standard but was persuaded by our defence engineers configuration was large and Sweden diesel generator of which thousands had been and eventually agreed to the technical had found a way to reduce deployment produced. Hence, they were deliverable items The Rapier system being deployed soundness of the alternative solution. requirements and increase the mobility in our FMS case. More importantly, the MEP- of the fire unit. The Swedes had developed 115 was inadequate for the planned product Mr Quek Gim Pew became a defence engineer a new radar based on the Giraffe radar, the improvements (PIP-2) that our I-Hawk system in 1981 and expressed interest to do Research Super Giraffe, and had integrated it with would come with. It did not have the reserve and Development (R&D) at DSO. Due to the high power illuminator of the I-Hawk power capacity and was not responsive the urgency of building up our air defence and two sets of missile launchers. This enough for the PIP-2 upgrades. These upgrades capabilities, he was persuaded to manage was the ideal configuration for Singapore demanded more power from the diesel an acquisition project first. He managed as it would be very mobile, quick to deploy generator, as new equipment was added to the Rapier successfully and was then posted and camouflage, and required a very the fire unit, and the launchers were made to DSO. small footprint. to slew more rapidly for simultaneous and multiple target engagements. The increased Improved Hawk and Super Giraffe The US Army Missile Command (MICOM) surge power demand caused the generators did not support the integration of I-Hawk to “trip”, which in turn caused the computers Personnel preparing for the first The case for the replacement of Bloodhound with Super Giraffe. Their position was that in the control post to fail at the most critical Rapier live firing with Improved Hawk (I-Hawk) was made the MICOM would only sell complete fire phase of a target engagement. On the other on operational grounds and economics. The units. The smallest fire unit of the US Army hand, the US Army did not have any plans Rapier could be upgraded with DN181 Bloodhound missile would prevent an enemy was the Improved Assault Fire Unit (IAFU). to replace the MEP-115 in the near future. “Blindfire” radar for operation at night and from using medium and high altitudes to The solution to meet the demands of MICOM Thus, we decided to design and build new in time of poor visibility. This was considered perform its mission. It could not contribute to and our operational requirement was the diesel generators to our own specifications. to be another important capability. After the low level air defence of Singapore. Besides procurement of three IAFUs, the minimum all the operational studies and cost benefit medium and high altitude air defence, the order quantity, and five sets of equipment to From Raytheon we learned that a small analysis, MINDEF accepted the case for the I-Hawk missile could contribute to low level be integrated with Super Giraffe radars, which company had made a proposal to the US Air Force to acquire Rapier. air defence. MICOM termed the Modified Improved Army for replacement of the MEP-115, but Assault Fire Unit (MIAFU). approval for this would take years due to the The UK Army had developed Rapier to equip A squadron of I-Hawk was estimated to cost staffing process of the US Army. The company the units of the “British Army On the Rhine”. S$100m. The I-Hawk was also assessed to I-Hawk was the most costly system acquired was called Vallely Power and was owned by Maintenance would be done at three levels: have a lower operating cost compared to for SADA. The Foreign Military Sales James (“Jim”) Vallely – a very practical and the fire unit, the battery and the base level the Bloodhound, and an annual savings of (FMS) case for its purchase was signed in experienced specialist in customising power at the manufacturer of Rapier in the UK. S$5m could be achieved. As I-Hawk was February 1980. Eight Super Giraffe radars generators for demanding environments. He Trouble shooting at the fire unit would locate a mobile system that was not dependent complemented the I-Hawk system. The US briefed us on his proposal to the US Army.
16 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 17 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
His design utilised current state-of-the-art We did not need the AN/TPQ-29 to be project manager and Mr Kent Drefeldt was in The next day, I was called to attend an engines and alternators, and accurate and fast transportable as it would serve as a static charge of our Basic and Super Giraffe radars. unscheduled Defence Committee meeting at responding electronic “governors” compared simulator in the I-Hawk unit. Normal mains the Istana with Prime Minister Lee. Minister to the old mechanical governors of the MEP- power was thus used for the AN/TPQ-29. A US Army major gave the first briefing. In for Defence Goh Chok Tong and Second 115. The only shortcoming, in our opinion, Instead of using mil-spec 115VAC, 400Hz air- typical US Army style he stood erect and Minister for Defence Yeo Ning Hong were was that the power capacity of this new conditioning units, we over-cooled the AN/ stiff in front of us, hands clasped behind present. Dr Goh said, “Philip says we need design just matched the requirements of TPQ-29 with commercial and inexpensive his back and he delivered his presentation this [E-2C Hawkeye airborne early warning the PIP-2 upgrade. We suggested adding a Toshiba air-conditioners. The Commanding very formally and in staccato from his slides. aircraft].” Mr Lee asked what the next step more powerful diesel engine and a much Officer of the I-Hawk unit reported that the When he came to the MIAFU, he said “…. was. I replied that I would be going to the larger alternator. Jim Vallely agreed and we AN/TPQ-29 was heavily used and that its the Singaporeans have decided to adopt Pentagon. The meeting lasted less than two tested a prototype of the Singapore diesel serviceability and availability was always both the IAFU and MIAFU; IAFU stands minutes. No memo was needed. generator, which worked very well. We used high. The AN/TPQ-29 was delivered to for “Improved Assault Fire Unit” and the our own diesel generators for the first firing Singapore towards the end of 1982 and retired US has termed the MIAFU the “Mini- In Washington, I met up with John Lehman, of our I-Hawk system at the White Sands from service use in 2004. Improved Assault Fire Unit”. Secretary of the US Navy. The US Department missile test range in New Mexico. The firing of Defense Letter of Offer and Acceptance took place on 15th September 1982 and was Unlike Mr Bo Johannsen who was large to Singapore was US$601 million for four a success. The Singapore diesel generators and spoke loudly, Mr Kent Drefeldt was a Hawkeye E-2Cs and a basic integrated Logistics are still in service with the RSAF. Only two slightly built and generally soft-spoken man. System package. Our project staff completed have been replaced after more than 30 years He put up his hand and said: “Excuse me, but the overall programme for US$340 million …” of reliable service. in Sweden we call the MIAFU the “Much Improved Assault Fire Unit”. The silence in As E-2C was considered to be a strategic The AN/TPQ-29, the I-Hawk training the room was so thick you could have cut it system by the US, it took more than three simulator, was also a deliverable item in with a knife! years of staffing before the Letter of Offer and our FMS case. It was a transportable system Acceptance (LOA) would be sent to Singapore. that would be shipped together with an E-2C Airborne Early Warning (AEW) I-Hawk system that was deployed overseas. Aircraft – Changing the Rules of the The disruptive innovation the E-2C brought It used old vacuum tube technology and Game for Island Air Defence about was the breaking of the constraint of was powered by the 60kW, 400Hz MEP-115 “line-of-sight” to our air defence system. diesel generator. In turn, this necessitated the Introduction The disruptive change was created when we use of 400Hz “mobile” air-conditioning units. An I-HAWK MIAFU deployed in Sweden could position the E-2C and detect adversarial Very compact, maintenance intensive, mil- In the book “Up close with Lee Kuan Yew: fighters at a significantly further range that our spec 115VAC, 400Hz air-conditioning units The lesson learned from our experience with Insights from colleagues and friends”, Mr ground-based radars could and consequently were part of the system. In all, the AN/TPQ- the Bloodhound simulator is that electronics Philip Yeo recalls the following incidents also intercept them at extended ranges from 29 was an expensive and antiquated simulator equipment, especially analogue vacuum tube that took place when he was Second Singapore using our fighter aircraft. With with equally expensive and antiquated systems, should be cooled to as low a Permanent Secretary of MINDEF. The surface radars we could detect incoming power supplies and air-conditioning systems. temperature as practically possible. So while following is an extract from pages 94-95: fighters flying at 150 feet to approximately However, it was needed for training I-Hawk we over-cooled the AN/TPQ-29 – the vacuum 10km from their targets. Fighter interceptors SAM controllers locally. tubes were very happy, the reliability of the “… in February 1979, Dr Goh Keng Swee asked and medium level SAM would be useless simulator was very high – the trainees felt me to take charge of Air Defence build-up against such threats. Hence, our 1978 Air 170 Squadron operated and had much they were in Siberia! portfolio … Sometime later, he called me Defence Plan was based on Giraffe radars, experience with its Bloodhound Engagement to his office for our usual ten-minute catch- 35mm anti-aircraft artillery and the RBS-70, Controller Simulator, which was introduced A funny situation arose during a project up. He asked me how my SADA (Singapore Rapier and the I-Hawk SAM systems. With in 1971 and retired in 1990. It was, likewise, meeting: Mr Bo Johannsen and Mr Kent Air Defence Artillery) build-up was going. E-2C, the new air defence plan was changed to designed and produced from the era of Drefeldt of Ericsson Microwave Systems I replied that we needed Airborne Early be based on fighters complemented by SAMs. vacuum tube equipment. The main reason for joined us for a project meeting with the Warning capabilities to complete the air its high failure rate and general unreliability US Army, MICOM, Raytheon and others defence build-up. He knew what equipment In May 1982 during the Falklands War, Dr was the large amount of heat generated from at MICOM in Huntsville Alabama. Mr Bo was needed and asked how many I wanted. I Goh Keng Swee, then Minister for Education, the vacuum tubes. Johannsen was our Super Giraffe MIAFU replied, three. He countered, “Two is enough.” observed that the Royal Navy was lucky that
18 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 19 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
the bombs delivered by Argentinian A-4 The E-2C Project 1982-1987 programme was handed to MAJ Wesley few people developed a distaste for travel due Skyhawks that had struck their ships did D'aranjo who was appointed the Programme to the distances involved and the discomfort not explode. He observed that the lack of The vulnerability of Singapore to aerial Director. MAJ Wesley D'aranjo remembers of flying economy class in those days. AEW nearly caused the UK to lose the war assault was a big problem, due to the lack of clearly the briefing he received one Saturday and concluded that E-2C would be critical strategic depth to provide sufficient warning morning from his boss, SPD Lui: “I think you The first project meeting with USN Naval for the air defence of Singapore. Though time of threats to the entire country – “our know by now that we've decided to buy the Air Systems Command (NAVAIR), the the cost would be very high he stated that: front door is our back door!”. If we were E-2C and I want you to be in-charge”. (And, USN E-2C project management office, was “It is still cheaper than one oil refinery”. to allow enemy aircraft into our airspace, yes, we worked Saturdays then.) When MAJ held in Bethpage in December 1983. COL anywhere in Singapore would be bombed Wesley D'aranjo reminded SPD Lui that his Lui Pao Chuen, SPD, spoke on behalf of the An AEW radar was not part of the within seconds. An increase in our warning contract would end soon, as his scholarship Republic of Singapore and voiced his concerns consideration in the original design of time is crucial if we are not to be caught by bond expired in July 1983, SPD Lui said: “Please in the management of the programme. His Singapore's air defence system. We had surprise. Hence, the E-2C. tell that to DS (Air Force)”. Lim Ming Seong introductory speech (see page 28) is worth never even dreamed of it. Immediately, we was the DS (Air Force) then. He listened, said recounting. researched all that we could gather and learn The E-2C is the USN's airborne surveillance, “not acceptable”, and the rest is history. about the E-2C from our library – there was and command and control (C2) aircraft Managing the project involved a great amount no Internet or Wikipedia then. Once we knew designed and built to operate off an aircraft Intense negotiations between USN-Grumman of detailed work; this being the nature of large- and understood what operational capability carrier to support a naval task force. A fleet of and MINDEF preceded the signing of the scale systems integration work and logistics. and advantage the E-2C would bring to the four E-2Cs was estimated to cost more than LOA. As we now understood the E-2C better, Our aim was to build an infrastructure that air defence of Singapore, we thought we had S$1 billion in 1982. The other US alternative having just completed an extensive logistics would enable the squadron to maintain its “died and gone to Heaven”. then was the US Air Force Airborne Warning planning exercise on it, we wanted several intended operational readiness throughout and Control System E-3 Sentry which was software changes to better suit the RSAF's the life of the aircraft. Hence, not only Grumman Corporation, the designer and even more costly. There was also the Nimrod operational requirements; alternatives for did the hardware and logistics need to be manufacturer of the E-2C system, was quick proposed by the British. Fortunately, we did support and logistics implementation; as well purchased and installed on time, the equally to respond. In early 1982, it set up a regional not consider it as that project encountered as better terms and industrial offsets from important tasks of training adequate numbers office in Singapore and relocated the vice- many technical and insurmountable Grumman. The protracted delay caused the of operators, engineers, technical officers and president of their Tokyo office, Mr Herb difficulties and was eventually cancelled. Pentagon concern as approval for the release technicians on a continual basis had to be Moska, to Singapore. We would not have considered the Russian of E-2C to Singapore was given by President planned for and implemented. When the Bison. Ronald Reagan himself. Mr Jim White, an first aircraft arrived in Singapore in 1987, the In November 1982 a team of 11 senior staff Under Secretary at the Pentagon, travelled project team had prepared the logistics and from the RSAF, DSO and SPO was despatched For comparison, the most sophisticated to Singapore in mid September 1983 to meet operational infrastructure such that flying to the Grumman plant in Bethpage, New York aircraft operated by the RSAF then was the with SPD Lui and MAJ Wesley D'aranjo. could begin immediately, and it did! This is a to learn about the E-2C. The course lasted for F-5; and the Mass Rapid Transit (MRT) system After the pleasantries, he gingerly asked if testament to the sound groundwork laid more five weeks and ended just before Christmas. had just been approved at an estimated cost of the LOA would be signed as it would expire than 30 years before – and which continues S$5 billion. Compared to the MRT, a brand on 30th September 1983. Mr Jim White was to this day by the present generation of AEW A US Navy (USN) and Grumman team arrived new concept of transportation eagerly awaited left speechless when SPD Lui instructed MAJ operators and maintainers. While other in Singapore in January 1983 to work out the by the entire population of Singapore, the Wesley D'aranjo to draft and type, on the countries sometimes rely on foreign help even terms of reference for a logistics planning thought of spending S$1 billion for a mere spot, a letter confirming the purchase of the after many years, Singapore set a target to be conference (LPC) that was scheduled for four aircraft was quite daunting. As expected, E-2C with support, which SPD Lui signed self-reliant within two years. April 1983. US Congressional approval for the Singapore Government was engaged in and handed to him. The LOAs were signed the sale of E-2C to Singapore was obtained on a good amount of debate with opposition on 30th September 1983. As a legacy of the E-2C, the management of 17th May 1983 at a ceiling price of US$601m. members questioning the need for this large such large and complex projects was never The LOAs for four E-2Cs and support were expenditure. The press reported on the debate Two project teams under the direction of the same again from the project management presented by the USN at the end of July 1983. and Singaporeans got to know about the MAJ Wesley D'aranjo were established: one perspective. Our ability to integrate complex Detailed clarifications were held with USN E-2C. However, the E-2C was an essential at the Grumman plant in Bethpage, New systems, thereby producing a very effective officials in August and September 1983 to component in Singapore's defence strategy York headed by Mr Chinniah Manohara, SoS, was put to the test and we succeeded. review the scope and essential items with and had to be bought. and the other in Singapore headed by CPT respect to our requirements. The LOAs were John Wong. There was much travel between signed on 30th September 1983. The responsibility for managing this huge Singapore and New York. As a result, quite a
20 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 21 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
The E-2C Programme Spawned Several “Firsts” squadron. The senior squadron officers in the initial batch were the same officers managing It was the first SAF programme estimated at the local office of the project, thus ensuring a billion Singapore dollars. that they were the ones who had to live with the decisions they made. Upon returning It had the first full-time Government of from Grumman, most of the GOSPO staff Singapore Programme Office (GOSPO) were assigned to the squadron or took up established overseas: appointments in Air Logistics Department responsible for the E-2C. • Apart from the aircraft programme, GOSPO also took responsibility for The USN initiated each E-2C FMS project the spares management and housing / COL Lui Pao Chuen delivering his with a massive LPC. During the LPC, each accommodation for trainees, which at one speech during the handover ceremony and every main and subsystem – hardware point built up to about 140 such personnel A Project Management Review meeting and software – and sometimes up to the in the US. To the best knowledge of at Grumman – inspecting the fabrication individual component of the aircraft system the Programme Director, MAJ Wesley of a fuselage section was examined from the perspective of mission D'aranjo, this had not been done before needs. The operational, logistical and other on such a scale, nor has the range and local support needed to fulfil the mission was span of responsibilities been assigned derived and documented thoroughly in an to a single project office for subsequent implementation plan called the Technical and programmes or projects. Logistics Development Plan. This was very • Much of the work done at the GOSPO logical and commendable. However, a major was duplicated by Grumman for another mismatch in expectations arose soon after FMS programme that was running the start of the LPC. NAVAIR 231, the USN concurrently. Even our requirements for E-2C project management office, had limited aircrew flying suits, which we compiled COL Lui Pao Chuen (left) and BG George experience dealing with FMS customers and, based on the physical profile of our Yeo, then Chief of Staff (Air Staff) and understandably, assumed that what was good trainees, were accepted by the Egyptians. concurrently Director of Joint Operations for the USN was applicable for others as well. This was because the Egyptian pilots and Planning Directorate, taking a Many who came for the LPC were from found that the suits issued by Grumman commemorative photo with the E-2Cs USN fleet squadrons or bases and were only obviously did not fit, as the USN pilots Handover of Singapore's first E-2C in schooled in the USN way of doing things. were of much bigger build. January 1986 by Mr George Skurla, President What Was Learned? To make matters worse, the LPC for Japan of Grumman, to COL Lui Pao Chuen had been “successfully” completed recently The E-2C squadron was the first to In dealing with the USN, we had to learn a new and it was taken as an additional reference. incorporate maintenance of hardware set of vocabulary: FMSGEL, NAVAIR, ASO, For example, the Japanese required extensive and software within the squadron. Much NAVILCO, ILSMT, CINCPACFLT, FCDSSA, local manufacturing capability, which we confidence was gained from this project GOSPO, NAVSUP, TLDP, COMNAVAIRPAC, did not. They also wanted a complete radar in our own ability to maintain, repair and NAVFAC, SPAWARSYSCEN ………. The list test range for testing rotodomes (the rotating modify high technology equipment. of “NAVSpeak” is even longer. antenna of the E-2C radar); and the eight This mentality is still ingrained in the Japanese E-2Cs would be deployed at more SAF today. We learned a systematic way of managing than one operating base across Japan. To projects. This was the first time we managed the USN, it seemed obvious that Singapore's The USN is a professional and focused a project in such an integrated way; in what requirements had to be similar to those of organisation. Once they agree to do is today called “Ops-Tech” integration. The the Japanese. something, they do so without a fuss. skeleton crew of the squadron was formed Our first aircraft was handed over in March and both operators and logistics personnel The Singapore team assigned for the LPC 1986 during a six-monthly programme review were involved in the planning of the project, spent considerable time first learning how the at Grumman. including the physical requirements of the USN did things, then aligning expectations
22 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 23 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
and finally examining and outlining LMIS, and it continues to be implemented During the meeting with Mr Jim White, we standard IT hardware but very few had alternative cost-effective approaches to in SAP, albeit an updated version ECC6 took a chance and explained the dilemma and experience in implementing “interoperability” local and relevant industial support needs. Enhancement Pack 4. risk that Link ∑ posed to us. We asked if Link or working with classified US Government The support required for the E-2C – spares, 11 could be released to us. We were surprised datalinks. ground support equipment, a software Interoperability when Mr Jim White said he would staff our development facility and training – was request through USN and the Pentagon. It In mid 1984, we issued a request for proposal specified and decisions taken whether to buy The USN, and in general the US Armed Forces, was our turn to be speechless when we were to two companies, Grumman and Rockwell- them through the USN or directly from their interoperate via classified datalinks. The main granted release not only of Link 11 but also of Collins, for the development of a GES to manufacturers. This saved us an enormous datalinks used by the USN then were Link Link 4/4A, i.e. the USN's own configuration! interface the E-2C to our C2 system. Both amount of money. In all, teams from the 11 and Link 4/4A, the former for linking C2 This removed a big worry from our minds companies were asked to propose modern RSAF, DSO, Singapore Aerospace, other centres and the latter for the E-2C to “talk” to and saved at least US$26m. Often we are IT hardware and software solutions. local companies and SPO spent five weeks fighter aircraft. These datalinks encapsulate afraid to ask because we are afraid of negative Grumman's non-recurring development cooped up in a local hotel working with 40 decades of thought, war fighting experience and answers. The learning point here was to ask costs were very high and we continued with USN, Grumman and subcontractor personnel lessons learned by the USN. A “Book of sincerely, or innocently, in order to get the Rockwell-Collins. during the LPC. The USN estimated the LPC Standards” defines and disciplines every answer you wanted. However, what could to last 13 weeks. protocol aspect of each datalink – terminology, we do about the GES? The Rockwell-Collins group developing convention, metrics, data packages, interoperability solutions was based in The approach to logistics management learned transmission rates, track quality, error The GES proposed by the USN and Grumman Rodgau near Frankfurt and headed by Mr during the LPC evolved into a value-added correction schemes, “red / black” separation, was an actual “backend” of the E-2C – the three Dave Adams, a retired colonel from the robust process for MINDEF, which the encryption, change management and more. control workstations, a slightly antiquated US Marine Corps. Mr Dave Adams was a SAF described as the “LCM” of projects. All central computer and other associated graduate of the US Naval Postgraduate School subsequent projects adopted this methodology As Singapore is neither a member of the hardware. This was the standard solution in Monterey, and was well regarded in the and, in June 1990, it was formally accepted and North Atlantic Treaty Organization nor an proposed and implemented then. Imagine, a US military and industry for his expertise in documented as the MINDEF LCM Manual, ally of the US, the LOA included a provision full airborne mil-spec “backend” of the E-2C US and North Atlantic Treaty Organisation which clearly defined the Integrated Logistics for Grumman to develop a unique datalink sitting on the ground in an air-conditioned datalinks and C2 systems. Mr Dave Adams Support requirements for project systems. for Singapore called Link ∑. This would room and relaying data to and from our C2 had strong opinions on many things but he This was further codified into the Logistics cost at least US$26m but the operational system! This did not sit well with us. By delivered as promised. Management Information System (LMIS) and requirements had to be specified by the then, we had moved away from the use of implemented using the German software, RSAF. The requirement specifications were proprietary “mainframe” computers and had The E-2C GES was developed and delivered Systemanalyse und Programmentwicklung defined by the RSAF and DSO. An innovation already introduced commercially available by Mr Dave Adams and his team at a (SAP) R/3, which up till today is probably and specific requirement was a novel priority standard information technology (IT) fraction of the price of the Grumman GES. the best industrial Enterprise Resource scheme to ensure that the most important processors connected by local area networks Development of the E-2C GES took place Planning logistics software tool available messages get priority of bandwidth. However, and performing distributed processing. We from mid 1986 and it was commissioned commercially. The LCM methodology ensures a large amount of flight testing would be demurred and decided to study the matter in early 1989. Software staff from DSO, that all aspects of the system life cycle are required to qualify Link ∑ and there was in more detail. We discovered that several led by Mr William Lau, participated in the considered in arriving at relevant and cost- no guarantee it would work. In addition, companies could provide a “backend” using development of GES. effective solutions. It can be said with some for Link ∑ to be interoperable with our C2 degree of confidence that MINDEF and the system, the interface would have to be via SAF are now able to get the best value for a Ground Entry Station (GES), and the GES its money when acquiring weapon systems. would cost another US$26m. In 2012, the LCM Manual was replaced by the Defence Capability Management (DCM) This matter was of great concern as the SAF Manual to take into account the increased did not have the interoperability the USN sophistication of systems being acquired or assumed existed. We had not yet achieved developed, and the need for more Operations- interoperability within a service, let alone E-2C flying along the Fokker 50 Maritime Missile Corvette Logistics coordination and integration taking among the three services of the SAF. coastline of Long Island, USA Patrol Aircraft a capability perspective. Correspondingly, the Enterprise Systems for Logistics replaced the One may be surprised at what we did next. Systems enabled with C2 interoperability training
24 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 25 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
This was a valuable learning experience for provisioning of spares for the various systems A line item in the LOA was for a “staging “draw-down” plaque, and the presentation our work on various types of datalinks in and subsystems of the E-2C, which the USN area” in New York to receive, store and of mementoes. later years. wanted “Beltway Bandits” to do. Instead, dispatch to Singapore the multitude of we asked the Aviation Supply Office (ASO) spares and materials purchased for the E-2C The implementation of the E-2C GES enabled in Philadelphia to generate the listing of squadron. As we would have to manage the and spawned the following capabilities: spares with their reliability data based on logistics of the E-2C ourselves eventually, we USN usage data. We then worked out the informed the USN that we wanted to handle • Enhanced effectiveness to our weapon provisioning list based on our experience this task by ourselves. Singapore Aerospace systems via improved target acquisition and flying profiles. (SAMCO) was approached and asked if provided by E-2C they would take up the challenge of doing • Modernisation to Link 11 communications Deciding on the quantity of spares was an this. SAMCO established the “SAMCO system intimidating challenge because of the high Warehouse” close to Bethpage at less than • Advanced standalone and embedded costs involved. Relying on the spares list half the cost estimated by the USN. simulators for C2 interoperability training given by the USN would have cost many between the E-2C, MPA and RSN ships tens of millions of dollars more. Everything Onto Singapore seemed inflated, probably due to the relatively In 1991, Mr Dave Adams and three of his smaller number of E-2Cs compared to other After the “roll-out” of our first two E-2Cs senior system developers left Rockwell- aircraft types. So, without the benefit of at Grumman, they were used for pilot and Collins and formed their own company operational experience on the E-2C, and “wizzo” (weapon systems operator) training. called Interoperability Systems International relying on the reliability data provided by Upon completion of the flying training, the Hellas, which eventually moved to Athens, ASO, we had to decide which spares to buy, aircraft were flown to San Diego from the Greece and is still in existence today. item by item. We could have played it safe Grumman plant in Bethpage, preserved for and purchased what the USN recommended. sea transportation across the Pacific Ocean Financial Control Instead, we took a calculated risk by using and shipped to the USN naval base at Subic a yet untested (by us) software programme Bay. The sea journey took about three weeks. The GOSPO, though small, had oversight on spares provisioning called Optimisation After off-loading at Subic Bay the E-2Cs over all matters relating to our programme of Units as Spares (OPUS); we asked relevant were stripped of their preservation, made and they scrutinised all expenditures questions of various knowledgeable USN operational again and then flown to Brunei. and verified them to be necessary before personnel, and then made our own judgments. RSAF pilots flew our E-2Cs from Brunei to a agreeing. OPUS is a software provisioning tool to memorable welcome at Paya Lebar Air Base determine the spares holding necessary to in March 1987. Arrival of our first two E-2Cs Understandably, the first and main achieve a desired operational availability. at Paya Lebar Airbase in March 1987 preoccupation of NAVAIR 231 was the USN This became a standard tool for calculating “Draw-Down” and Renewal fleet. NAVAIR 231, who also handled our and provisioning our spares in future projects. The E-2C was replaced by the Gulfstream project under the FMS arrangement, was We sometimes wondered if anyone would The E-2Cs were decommissioned after 25 G550 AEW system. always short-handed and, as a practical thank us for saving tens of millions of dollars years of sterling service to Singapore and approach, could spend our funds to employ if a plane was grounded for want of a spare! the SAF. We are now into the fourth decade of AEW subcontractors to work on various aspects of operations in Singapore, and as we take stock our programme. These subcontractors were Being at Grumman enabled the team and the The “draw-down” ceremony was held on 15th of what the E-2C has gained for Singapore, called “Beltway Bandits” and they made RSAF to learn a lot about the evolution and October 2010 at the Air Force Museum in Paya MINDEF and the SAF, it can be argued that their living by performing work outsourced development of the E-2C, and the forthcoming Lebar Air Base with Chief of Air Force (CAF), we have reaped more than enough benefits to from the USN. The offices of many such modifications and upgrades planned. In MG Ng Chee Meng, as the guest-of-honour. justify its costs, if such benefits can be priced. companies lined the “beltway” (a ring road) fact, we received the latest multi-function The ceremony was dignified and comprised Singapore's AEW squadron must continue to that surrounds the Pentagon; hence the display consoles ahead of the USN as we a formation flypast with CAF on board the aim for and be “The best AEW squadron in name “Beltway Bandits”. Where we could, signed up for the modification in time for it E-2C. There was also a symbolic handover the world”. we would not agree to the use of “Beltway to be incorporated into our aircraft during of the E-2C yoke to Commander Air Force Bandits” and, where possible, we did most production. This saved a lot of money as a Training Command, a photo taking session, of the work ourselves. An example was the retrofit would have been more costly. a video tribute and unveiling of the E-2C
26 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 27 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS
means. We have had a surplus budget every year The Island Air Defence's weapons, electronic warfare systems, unmanned since we gained our independence in 1965. Transformation into a System-of- platform technologies, and a new type of soldier Systems in the 2000s who is trained to exploit these capabilities.” We, however, do not save on defence. Each year we spend 6% of our Gross National Product on defence. The Third Generation SAF in the 2000s Minister for Defence Teo Chee Hean, March 2004 It is the responsibility of our Ministry of Defence to Announcement in Parliament of the Third Generation ensure we get the maximum defence capability for We have seen three key categories of IAD SAF this investment. systems that were progressively acquired and modernised from the 1960s to 1990s: Island Air Defence as a System-of- G550 AEW flying alongside E-2C as part The E-2C is a very large investment when compared Systems in the 2000s of the E-2C decommissioning event to the Gross National Product of Singapore. Money • Sensor systems, e.g. ITT-RS320 radar, Super spent on the E-2C will have to be taken from the Giraffe, E-2C airborne radar, etc The Third Generation Networked IAD was budget of other weapon systems. To get the most • Weapon systems, e.g. Bloodhound, I-HAWK, unveiled publicly in 2007. The Networked “bang for the buck”, we must cut down expenditures Rapier, RBS-70, fighter jets, etc Air Defence system enhances the existing that do not result in tangible returns. In short, we • C2 systems, e.g. GL-161, MOCC, newer multi-layered air defence with the must trim project overhead costs. in-flight C2 systems, etc application of networked concepts to tightly integrate existing and new sensors, C2 and Being a small and relatively young country, we Through a journey of some 30 years, our weapon systems for enhanced awareness, are fortunate to have a small bureaucracy. We can DTC pioneers and predecessors grew in responsiveness and precision. There are three therefore be very fast in decision making and we proficiency and mastery of these systems notable qualities in enhancing our IAD from can complete our actions rather quickly, provided through “learning by doing”. By the 1990s, we a collection of systems to an SoS. we get the facts and figures. had a suite of capable sensor, C2 and weapon systems that were able to detect, sense-make First, it is more robust and survivable. The As we have built up a credible defence capability and deal with a range of air defence threats. networking of the various sensor, C2 and Then-CAF MG Ng Chee Meng (centre) in a relatively short time, we have to work in a weapon systems together prevents a single with founding members of the “pressure cooker” environment. We have become Moving into the 2000s, DTC embarked point of failure, thereby enhancing the E-2C project team intolerant of waste, especially of valuable time. on a journey to develop IAD into an SoS. robustness and survivability of the overall Please bear with us should you find us to be more Defence capabilities being developed were air defence system. With networking, the COL Lui's Introductory Speech at the “pushy” than other more established FMS countries. increasing in scale and complexity compared degradation of any single sensor, C2 and/or First E-2C Project Meeting with USN We pay cash, and on time. to the individual systems for sensors, weapon system will have minimal impact on NAVAIR in December 1983 weapons and C2 that DTC had managed the entire system as there are several other As we have spent considerable time during the so far. The continual advancement of sensors, C2 and/or weapon systems that will Then COL Lui Pao Chuen, SPD, spoke on Logistics Planning Conference, being briefed and communications, computing and information continue to function. behalf of the Republic of Singapore. His talking to each other, let us not cover subjects that technologies in the new millennium was speech, which voiced his concerns in the have been covered there and adequately documented. offering new opportunities for systems to Second, it is more responsive and effective management of this programme, was as We should get down to issues that will affect the be networked together and to interoperate. in defeating aerial threats. The IAD SoS has follows: project. We are ready to respond to any matters that Concepts of Network-Centric Warfare (NCW) enhanced awareness and responsiveness to any participant in this conference would like to raise were being explored or pursued by countries see farther, respond faster and engage targets Mr Chairman, Ladies and Gentlemen, and we will work as long as necessary to give a such as the US. It was at this time that the with greater precision. The Networked Air response before we end this conference. I hope that SAF embarked on a journey to transform itself Defence system effectively reduces the sensor- As most of you will now have discovered, Singapore the issues we raised with PMA-231 will be similarly into a Third Generation capability. to-shooter cycle between the time a target is a very small country. We have no natural resources. dealt with so that we can both feel satisfied that the is detected and the time it is engaged. In Even the water we drink has to be imported from conference is worth the effort of attending. “The transformation of the SAF to exploit addition to responsiveness, networking also Malaysia. rapidly emerging technologies and concepts is a provides greater strike effectiveness. In the Thank you. strategic imperative for the 3G SAF. These will past, a weapon system or shooter relied on To survive and prosper as a nation we have to work lead to changes in organisation, less demand for its own sensor to detect and track targets. very hard and be as efficient as we can. We have conventional platforms, more demand for less visible Today, however, the shooters and sensors are learned the habit of thrift and spending within our technologies like information systems, precision connected. Tracking data from a particular
28 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 29 Chapter 1 EVOLUTION AND DEVELOPMENT OF ISLAND AIR DEFENCE SYSTEM-OF-SYSTEMS Chapter Two
sensor, such as the FPS 117 or Giraffe Agile capabilities in the network. Underpinning CONCEPTS TO radars (one main S316L/S and one backup Multiple Beam Radar, can be relayed to these networked capabilities in our IAD is CAPABILITIES S319L), two Plessey HF 200 height finding the shooter most suitable to eliminate a an SoS architecture that has the flexibility radars and an advanced GL161 C2 system particular threat. The whole idea is to to allow subsequent insertions of the latest from the RAF located in Bukit Gombak under command these weapon systems centrally sensor systems and weapon systems to the command of the Bukit Gombak Radar on the network. It is now possible to select interoperate in a network-centric manner. Station. For weapons, we had the 35mm the best shooter, using the best tracking This is to ensure that our IAD capabilities A Historical View of Concept guns covering low-level air defence and the radars, to intercept any incoming targets more would maintain a cutting edge. As a result, Formulation for Island Air Defence Bloodhound SAM system covering the High efficiently and effectively. after 2007, new sensor and weapon systems, Altitude Air Defence. such as the G550 AEW Aircraft, Surface- We saw in Chapter 1 how careful analysis Third, it has the flexibility and ease for to-air PYthon and DERby (SPYDER) SAM of mission requirements and the use of Expanding a Multi-layered IAD in the growth. The IAD system integrates existing system and the Aster 30 SAM system, could Operations Research studies to support 1970 – 1980s and newly operationalised capabilities, while be successfully inserted into our networked urgent acquisition decisions for a single allowing for easy plug-and-play of future IAD. component system in IAD was carried out, A multi-layered IAD was beginning to take such as rationalising the rate of fire as a shape, and it became obvious that our IAD's critical parameter for our anti-aircraft guns initial inventory of systems would need to be and selecting the Oerlikon 35mm twin-barrel augmented. In the mid 1970s, the first mobile gun system over the Bofors 40mm single radar AN/TPS-43DX was acquired and put barrel gun. In this chapter, we will take a into operation, followed by the second mobile complementary perspective of how concepts radar ITT-RS320 and the Plessey Processing and capabilities for the overall IAD were and Display Cabin in the early 1980s. For shaped over time. We will also see some of the SAM systems, the Rapier and I-Hawk entered corresponding qualities within the DTC as service in the 1980s. For fighter aircraft, first an Enabling SoS that would allow it to to arrive was the pre-owned Hawker Hunter support the SAF in requirements definition in the early 1970s, followed by the pre-owned for complex systems, so as to evolve and A4 Skyhawk and soon after the supersonic realise large-scale complex defence systems, air defence fighter jet F-5E in 1979. such as the network-centric IAD SoS. Air Defence Master Plan 1978 Rapid Build-Up of Basic Systems for IAD in the 1960s – 1970s Even at a time when there was a critical need to meet very urgent operational needs Following Singapore's independence from in the early years, our defence technology Malaya in 1965, our defence build-up, pioneers demonstrated the ability to in particular air defence capability, was formulate requirements and acquire systems determined to a large extent by the abrupt with the resources available and yet keep announcement in 1968 that the British the big picture in mind. Amid operational Forces would be withdrawn by 1971. Over demands and acquisitions of additional air this early period of building up a credible air defence weapons, sensors and C2 systems, defence system, our pioneers from MINDEF MINDEF took a systems approach and Networked Island Air Defence unveiled in 2007 and the Defence Technology Group (DTG) embarked upon master-planning effort, rather worked against the odds and came up with than acquire new systems in a “piece-meal” an impressive record. manner and hope that they would somehow References: work as an integrated whole one day. By the early 1970s, we had set up a basic air Kuok, R., Yong, P. H., Othman, W., Puan, N. A., Nathan, S. R., Pillay, J. Y., … defence capability based on new purchases and In 1978, Dr Goh Keng Swee, then Minister Lim, T. K. (2015). Up close with Lee Kuan Yew: Insights from colleagues and friends. inherited systems from the RAF stationed in for Defence commissioned then LTC Lui Pao Singapore: Marshall Cavendish. Singapore. We had two Marconi Surveillance Chuen to develop the first air defence master
30 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 31 Chapter 2 CONCEPTS TO CAPABILITIES Chapter 2 CONCEPTS TO CAPABILITIES
plan. Prof Lui recalled “I felt that it had to be a of new systems. Into the 1980s and early from proficiency to mastery in operating the from fighter aircraft to stand-off munitions. joint effort [with the SAF] when Dr Goh Keng 1990s, the whole project management process systems in our inventory. We arrived at a Examples included long-range air-to-ground Swee tasked me to do the study”. As Prof Lui was continually rationalised and improved stage where we could exploit the systems' missiles that enabled adversarial aircraft to had already spent three years contemplating to ensure that only the most cost-effective capabilities to the fullest as well as overcome attack while staying out of harm's way. This this study, he had all the materials available. systems were acquired to meet Singapore's their limitations. Added emphasis was placed required an IAD that could respond faster, The team he put together had to put certain needs. Collectively, DTC and SAF users earned on optimising their performance as a larger since missiles would typically fly faster than scenarios to war-game, and the product was the reputation of being “smart buyers” and system, and their related areas of systems aircraft and would be harder for conventional the Air Defence 1978 Report. This was the “smart users” respectively in the eyes of many acquisition, integration, training, organisation radars to detect. The air defence's ability first time the SAF had a dedicated study for international defence systems contractors. and more. to defeat missile threats and robustness to the development of a major ORBAT in the Exemplary outcomes in this period included withstand some extent of missile hits would SAF based on inputs from our own people. the integration of the American I-Hawk An example was the Sensor Master Plan also be critical. A new suite of sensor and Before that, we always had to depend on SAM system with the Swedish Super Giraffe, that aimed to overcome shortcomings of the weapon systems synergistically integrated consultants. and likewise the RBS-70 and the 35mm existing sensors by introducing advanced with a responsive command, control and guns with the Basic Giraffe to improve their sensors, carefully integrated to form a communications (C3) system could optimally This was to set the stage for MINDEF and the capabilities. coherent whole, to provide overall system- handle stand-off munition threats. DTC's culture of master-planning. In the air level robustness. The suite of sensors provided defence domain, this discipline of conducting From SAM-centric to Fighter-centric Air overlap of coverage in various dimensions, Leveraging advancements in infocomm operational and engineering master-planning Defence in the 1980s such as space and frequency, as well as technologies and emerging network-centric continued in the late 1980s and early 1990s, radar functional modes. Each radar acquired concepts, the DTC and the RSAF developed led by planners from the RSAF and Systems A major paradigm shift in IAD occurred under the Sensor Master Plan was carefully a network-centric IAD, where the GBAD Engineers from the DTG. following the acquisition of the E-2C airborne defined, adapted or specially developed evolved from operating in firing units to early warning aircraft in the 1980s. Up to that to meet Singapore's unique requirements. operating networked “common pools” of “Ops-Tech” Integration point, in spite of our best efforts to tackle It was a product of comprehensive Ops- sensor and weapon systems that could be low-flying aircraft threats with capable radar Tech partnership with concerted efforts optimally paired by the C3 system against Other than rationalising the suite of systems and weapon systems such as the tactical Giraffe in engineering studies involving both specific threats. Moving away from the firing needed by our existing IAD, the 1978 Air low level air surveillance radar and the Rapier experienced RSAF air defence planners cum unit concept also meant better robustness. Defence Study led to the formation of and RBS-70 SAM systems, ultimately ground- operators and DSO Radar/Electronic Warfare This was because each firing unit typically the SADA formation in 1979 and the Air based air defence systems (GBAD) were still Systems Engineers. The outcome was a had a dedicated radar, and if the radar was Force Systems Command in 1983 – two subject to the “tyranny of line of sight (LOS)”. master plan that when realised would provide defeated by a missile, the firing unit could organisations that later merged to form Air With the E-2C now as an airborne radar, the a comprehensive recognised air situation be rendered ineffective. In a network-centric Defence Systems Division in 1995. This “tyranny of LOS” was broken and low-flying picture around Singapore to support various concept, another radar suitable for the mission represented a holistic approach to capability threat aircraft could be detected at much missions of the RSAF. The study also included could be selected from the “common pool” to development, where both new operational longer ranges. To complement the airborne the top-level systems integration approach bridge the gap. and technological concepts were formulated radar's extended reach, the natural choice of to be taken by MINDEF's engineering team. “hand-in-glove” so that the eventual new a complementary weapon system became the This Third Generation networked IAD was a capabilities were not just “new machines”, but air defence fighter. As a result, in terms of a Many more capability master plans were product of Ops-Tech partnership at the very new organisations which could exploit these multi-layered response to air intruders, the first developed as such a practice became the norm early stage of capability development. While new machines in a transformational manner. layer now became fighters, instead of SAM in MINDEF's capability planning process. The the RSAF was formulating the operational systems such as I-Hawk that was limited by master plan for Singapore's network-centric concept, the DTC complemented it with a This example of integrated “Ops-Tech” its 40km range and LOS. This “fighter-centric” IAD was conceptualised in the 2000s and it systems architecture approach (also known partnership early in the capability development air defence was further bolstered by the signified the new generation of networked as Systems Architecting or SA) to drive the life cycle sowed the seeds in developing a acquisition of the capable F-16 fighters in the air defence capability for the SAF. operating concept and architecture from rigorous and systematic approach to systems late 1980s. firing unit-based to network-centric. This was acquisition by MINDEF and the DTC. It From Fighter-Centric to Network-Centric crystallised in synergistic IAD master plans set the tone for future co-operation where Optimisation of the Larger System of IAD IAD in the 2000s from both the operational and engineering comprehensive project requirement studies perspectives to translate concepts into SoS and mutual consultation are embedded in the By the 1990s, with almost two decades In the 1990s and 2000s, the primary threat capabilities. evaluation, procurement and management of experience, the DTC and the SAF grew to air defences around the world shifted
32 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 33 Chapter 2 CONCEPTS TO CAPABILITIES Chapter 2 CONCEPTS TO CAPABILITIES
MINDEF's Long-Term Planning for the development of the SAF in response Formulation of Concepts and Master Plans innovation process between operational Process Today to advances in technology, the anticipated users and technical subject matter experts, threat landscape, constraints in resources and In the next stage, Operational Concept synergising future technology with future In realising the Third Generation SAF, MINDEF phasing out of old systems over a planning Formulation (OCF) looks at the medium-term operations, and enabled by a robust systems acquires and deploys cutting-edge weapon horizon of 10 years and beyond. This process planning horizon to develop concepts as the architecture design. systems and information technology so that involves agencies from both MINDEF and basis for the capability development master the SAF's operations are characterised by the DTC. plans, i.e. Operational Master Plan (OMP), and The DTC's SA journey began in late 2003 speed, precision, knowledge and integration. the Engineering Master Plan (EMP). OCF and with three senior staff as DSTA Systems The strength of the SAF is multiplied by Analysis during this strategic planning capability development master-planning is Architects with the charter to discover and our ability to network the various systems stage is at a highly aggregated level, looking iterative and collaborative. These master plans exploit new capabilities that could support and capabilities, so that the overall fighting at problems from the macro-system show the milestones for capability build-up, the SAF. As SA gained buy-in with MINDEF system is much more capable than the sum of perspective. These planning efforts aim the resource requirements (e.g. infrastructure, leadership and the demand for SA grew, the individual parts. Advanced C3 systems, to provide coherent strategic directions to equipment, manpower etc) and the training the DSTA Masterplanning and Systems enabled by information technology and guide the capability development of the SAF, requirements. Architecting (DMSA) Programme Centre networking, now allow rapid dissemination Research and Technology (R&T) thrusts, was subsequently set up in 2006. of information to give commanders and and development of defence industries. Systems Architecting their subordinate units better awareness, and Experiments may also be conducted to explore “Recognising that we need to view defence enable them to exercise better control and new operational and war-fighting concepts. With the Third Generation SAF being a task- capabilities as outputs of complex system-of- self-synchronisation in order to operate as a Ops-Tech Visioning can be done to derive organised networked force, it is vital to have systems, DSTA has established a masterplanning tightly integrated system. innovative system concepts to address the a systematic approach to design complex and systems architecting business area to ensure SAF's key operational challenges and to drive networked capabilities such as the Third coherence, fit, consistency and flexibility in In consideration of these, the first step is R&T requirements. Generation networked IAD. A systems developing new capabilities. The focus is to develop to formulate the “big picture” of defence architecture study enables the effective system architectures that will provide system level capabilities before new defence equipment The end product of the Strategic Planning formulation of the OCF, OMP and EMP coherence …” are acquired. Today, MINDEF and the DTC stage is a multi-year MINDEF/SAF Plan that for such complex networked capabilities. have a codified approach to long-term will define the key development milestones With Ops-Tech collaboration initiated Richard Lim, then Chief Executive of DSTA, planning to facilitate the formulation of for a pre-determined number of years ahead, upfront during the OCF stage via a systems announcing the formation of the DMSA Programme new concepts in defence into Defence SoS both in terms of force structure build-up architecture study, both the SAF and Defence Centre at the DSTA Suppliers Brief at Asian capabilities. This includes the stages of and “softer” areas such as human capital Science and Techonology Agency (DSTA) Aerospace 2006 on 22nd February Strategic Planning and Formulation of development, training and education. It counterparts would be in a good position Concepts and Master Plans. will be an integrated document synergising to jointly assess and mutually agree on the and articulating operational, technological need for an EMP. Once that need is firmed Strategic Planning and other defence and security related up, the work on the EMP can be expected to dimensions. proceed in parallel with the OMP. The Strategic Planning stage involves formulation of long-term strategic directions The systems architecture study analyses the capability from an SoS perspective, where different types of systems and technologies are considered in formulating innovative S P C P operational concepts for investigation. The Operational Master Plan SA methodology encompasses the art and Operational Concept science of designing effective operational (Multi-year plans Formulation at MINDEF level) capabilities – one where various types of The key roles of DMSA were to develop SoS Engineering Master Plan systems operate together in an integrated architectures for the SAF and to spearhead and coherent manner to deliver a quantum the build-up of SA as a strategic competency Systems architecting to support SoS capability development increase in warfighting capabilities, more than within DSTA. what the sum of the individual systems can MINDEF Long-Term Planning Process provide. It is a collaborative and often iterative Several years down the road, with a growing
34 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 35 Chapter 2 CONCEPTS TO CAPABILITIES Chapter 2 CONCEPTS TO CAPABILITIES
number of Defence SoS being developed and The OMP and EMP guide the implementation an expanding base of Systems Architects sensors. Hence, SCME is an integrated for IAD or Maritime Security. Insights of multiple projects in an integrated and being groomed, SA was codified in 2012 effort between the SAF and DTC where from these studies influence the choice of concurrent manner over multiple years. For in MINDEF's DCM systems manual as an technologists work alongside military systems for EMPs. Operations Analysis example, the IAD OMP and EMP formulated integral approach during MINDEF's Long- experimenters to transform Singapore's (OA), Modelling and Simulation (M&S) in the 2000s guided the requirements for new Term Planning Process. defence capabilities. tools are heavily used. systems such as radars and weapons, paving the way for projects to acquire systems such Enabling Tools SCME undertakes a multi-year strategy, as the SPYDER and Aster 30 SAM systems. which will systematically build up These new systems will be integrated via the The formulation of advanced operational a highly re-configurable C2 system. IAD architecture and enhance the IAD SoS. concepts and their complex systems during This also involves the integration of The Appendix provides more details on the the Long-Term Planning stage involves both an indigenously built modelling and DTC's SA and SoS approach. “art” and “science”. To facilitate such work simulation engine to create a rich with sufficient analytical rigour, MINDEF repository of re-usable models and In addition, each individual acquisition and the DTC had invested in laboratories exercise scenarios as new models are project is carefully scrutinised to ensure that equipped with the necessary hardware and created to meet specific experimentation the most cost-effective solution is acquired software tools, allowing both operational and requirements. A team of analysts from the to meet our operational needs. technical subject matter experts to develop DSTA Analytical Lab and evaluate alternative concepts. Two Systems Acquisition such labs are the SAF Centre for Military The DSTA Analytical Lab also enables Experimentation (SCME) and the DSTA a major paradigm shift in the approach Through the years, the DTC has adopted Analytical Lab. in designing systems, harnessing a pragmatic approach in our defence M&S to enable the DTC and the SAF acquisition, summarised as follows: to move beyond learning from legacy Experimentation of Future platforms (actual systems) to learning • Acquire off-the-shelf systems, wherever Operational Concepts from future platforms (simulated). This possible was epitomised in the example of the • Build – design and develop, only where The SCME is the one-stop centre RSN's Littoral Mission Vessel (LMV), necessary for all SAF experiments. Through where a mock-up of a first-of-its-kind • Collaborate with partners experimentation, the SAF can acquire Integrated Bridge-Combat Information new war-fighting knowledge, develop Centre-Machinery Control Room We only buy what we need, and what is innovative operational concepts and Battle Lab in SCME (IBCM) was simulated in the DSTA most suitable and cost-effective for us. doctrines to enhance mission planning. Analytical Lab. This allowed the RSN We buy very sophisticated and highly SCME was established in 2003 with to test the IBCM concept with its capable equipment, but only when it is three laboratories – the Command Post Analysis to Support the Engineering sailors on various simulated scenarios, needed. Often we do not need to buy of the Future Lab, Battlelab and the C4I of Complex Systems leading to a clear understanding of the latest piece of equipment, when upgrading Lab. These laboratories provide users the requirements for IBCM layout, or refurbishing can do the job. When we and engineers with an environment to To augment the DTC's foray into SA work flow and crew manning before replace older equipment with more modern explore, experiment and demonstrate to design coherent SoS for the Third implementing the IBCM. ones, we often do not need to replace them technology capabilities for the SAF’s Generation SAF, the DSTA Analytical on a one-for-one basis. future force. Lab was set up in 2008 to help engineers design, model and analyse the next Approaches to Systems Realisation For example, our A-4 Skyhawks first came The SAF and the DTC began planning generation defence systems. In terms of into operational service in refurbished for SCME in mid 2002 because it realised front-end studies, the DSTA Analytical After the Long-Term Planning Process, the condition in 1974. The Skyhawks that in future, physical boundaries of air, Lab has demonstrated its ability to help requirements definition and acquisition subsequently underwent an engine and land and sea would be made artificial identify suitable technical solutions of new defence equipment will take place. avionics upgrade in the late 1980s. When by the increasing reach of weapons and before implementing a Defence SoS, e.g. This will be realised through acquisition they retired from operational service, the projects. Skyhawks had served the RSAF for 30 years.
36 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 37 Chapter 2 CONCEPTS TO CAPABILITIES Chapter Three
We replaced them with smaller numbers of new operational concepts and processes SOFTWARE SYSTEMS Examples of military missions supported more modern fighters. readily, discovered in the course of the DESIGN AND by C2 systems include surveillance against SAF's operations, exercises and test-and- suspicious or hostile acts, wartime and The SM1 tanks which have been retired, evaluation, to evolve and enhance the C2 REALISATION peacetime communications, network-centric were bought as second-hand AMX-13 tanks capabilities continuously. warfare and disaster relief. from various countries in the late 1960s and refurbished. In the late 1980s, they were The preceding paragraphs on the development upgraded to the SM1 standard and were of the IAD through the decades are a case Overview phased out after over 40 years of service in in point that illustrates the need for tight the SAF. integration of the sensor, shooter and Software systems are vital in defence underlying C2 systems. The application of SoS. This chapter will cover two broad Beyond acquisitions and upgrades, we the networking concept synergises their categories of software systems that have been design and develop solutions only where individual capabilities through heightened designed and realised by the DTC through necessary, in order to meet our unique communication efficiency and awareness, and the years: operating requirements. In doing so, we reduces the sensor-to-shooter cycle between would carefully nurture the industry for the time a target is detected and the time • C2 systems that enable enhanced selected capabilities to be built up and it is engaged. There are many more such situational awareness and operational sustained. examples across the SAF's operating domains. effectiveness during military The numerous Defence Technology Prizes operations. We collaborate with partners, both locally awarded to project teams and individuals over • Enterprise IT systems that enable and internationally, where there are the years are testament to the significance enhanced operations across diverse convergence of interests and mutual and impact of this capability. domains such as the management of benefits. This can take place in multiple human resource (HR), supply chain, A typical C2 system forms. For instance, through strategic finance, procurement, learning, training outsourcing, we could tap industry's and knowledge. C2 Pillar Functions capacity and free up our internal resources. With research institutes, both locally Definition of C2 Systems There are four main functions – situational and abroad, we could rapidly harness awareness, planning, tasking and control, technologies from both military and dual- Today's military missions are simultaneously and collaboration – that form the basis of use domains for defence applications. more complex and more dynamic than in most C2 systems: Collaboration with foreign governments can the past. Achieving mission success demands also help to overcome our local constraints. the collective capabilities, resources and • Situational Awareness. For C2 to be carried collaborative efforts of many military out across entities executing a common Command and Control Systems entities. mission, it is important to have a common Development understanding of the environment, C2 can be defined as the exercise of authority status and deployment of friendly and Early in the DTC's journey, we recognised that and direction by a properly designated hostile forces. Thus, the entities need to it was important to build up an indigenous commander over assigned and attached share a common situation picture with capability to master the development of C2 forces in the accomplishment of the mission. additional information tailored to their systems, particularly in the software domain. C2 functions are performed through an specific needs. To construct the Common This is a strategic capability that will enable arrangement of personnel, equipment, Situation Picture (CSP), information the SAF's operational processes and doctrines communications, facilities and procedures of the battlefield has to be gathered to be optimally embedded into our C2 employed by a commander in planning, via reconnaissance capabilities. This systems. It involves very close collaboration directing, coordinating, and controlling forces information then needs to be processed, between operational users and defence and operations. C2 systems, by extension, evaluated, fused for dissemination and engineers in the design of C2 systems are systems that support the commander in finally displayed as the CSP. These steps that cannot be easily replicated. This these efforts. require the use of powerful, real-time will also provide flexibility to introduce computing capabilities.
38 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 39 Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION
• Planning. A key function of a C2 system is in-country technical expertise that would In the naval domain, a Coastal the 1990s. Several C2 development projects to help users make decisions and carry out enable us to maximise the potential gains of a Surveillance C2 System for the Coastal were initiated. planning to achieve the desired outcome. combined SoS to meet all specific operational Command Centre and a shipboard Action Various decision support tools are needed requirements. Relying on stovepiped solutions Information System for the MCVs were Upgrading the Mission C2 System of E-2C to help users analyse the situation and to address all perceived threats would have also taking shape in Sweden through the come up with different options based on been expensive in terms of equipping and same approach. The E-2C's original mission suite consisted the resources available. The C2 system can logistics, demanded expansive manning, of a mission computer, a 10-inch diameter then facilitate evaluation of these options and yet be ineffective in dealing with multi- Upon completion of these immersive stints, monochrome display and a 4-inch alpha- for faster and better decision making. A layered threats. the engineers brought home profound numeric display. As our AEW missions wide range of planning capabilities is systems knowledge and were hands-on matured in the 1990s, there was an increase needed to address different needs such as The first-generation C2 system was thus to provide system support, troubleshoot in workload for the E-2C operator. The system to optimise the use of resources. Examples conceived as part of the build-up of our air faults and implement upgrades of the was found to be increasingly inadequate of capabilities addressing this need include defence artillery unit in the late 1970s. application software and firmware of the in coping with operational demands for platform optimisation, route optimisation operationalised systems. missions. The system was limited in control and more. 1980s functions and man-machine interface • Tasking and Control. Once planning is The strong commitment of MINDEF to features, with many functions requiring done, the C2 system is needed to help We began to recruit computer science and pursue C2 competency in-country had also frequent operator actions. This resulted commanders allocate tasks to the various engineering graduates to be groomed in contributed to the formation of Singapore in an undue burden on the already heavy sub-entities and ensure that the tasks are systems design and development as part of the Engineering Software Pte Ltd (SES) in operator workload and distraction from received in a timely and clear manner. The strategy to nurture in-country competency in 1986, jointly owned by ST Electronics and actual mission execution. The display, C2 system must help users monitor and C2 systems development. In the early 1980s, Ericsson Radio System AB, to provide with its limited monochrome features, control the execution of tasks. Should a these new defence engineers were deployed further support in the transfer of C2 know- did not facilitate the operator in the quick change of plan be needed, the C2 system for on-the-job training stints in overseas how. SES has since evolved to become ST assimilation of information and the must also assist users to react to the change acquisition projects with established defence Electronics (Info-Software Systems) Pte Ltd, building of situational awareness. and carry out an alternate plan. contractors. One such example was the Air a key command, control, communications, • Collaboration. Throughout the various Defence Ground C2 System. computers and intelligence solutions Hence, there was an operational need to stages of operation, the different entities provider in Singapore today. upgrade the aircraft with modern computer involved need to work as a team. The The defence engineers were trained in Sweden's and display systems in the most cost- collaboration functions of the C2 system Ericsson Radio System AB to construct a new During the same period, another key defence effective manner in order to enhance the enable the coalition of entities to plan ground C2 system from design to deployment, system – the United States Navy's E-2C E-2C operator's efficiency and effectiveness and execute the operation coherently. and were part of the software development Hawkeye – was being procured via Foreign amid an increasing workload, as well as to Effective collaboration tools make it easier team tasked to implement core components Military Sales from Grumman Corp (which overcome system obsolescence issues. for the various entities to work towards of the real-time C2 system. They also took would later become Northrop Grumman a common goal. on the role of systems engineers in hardware Corporation). In late 1985, a team of 12 In the 1990s, MINDEF approved the E-2C designing and test management. software engineers was attached to Grumman Mission Control System Upgrade to enhance C2 Competency Build-Up Journey Corp in USA for 14 months to learn about the the operational efficiency and effectiveness of E-2C software. We needed this competency the E-2C controllers and their role in Airborne 1970s so that we could be self-reliant to carry out Early Warning and Control missions. Prof E-2C software changes upon their return. Lui Pao Chuen, then Chief Defence Scientist In the 1970s, most of our military capabilities Besides the full life cycle of the E-2C software in MINDEF, commented that the level of – sensors, weapons and platforms – were development, the engineers also learnt good confidence in our ability to implement the procured overseas and largely stovepiped practices like upkeeping personnel's expertise in-country upgrade was high “because of the in nature. While production was left to the and system capabilities through staging conscious investments made over the years in defence industries, operational requirements regular system refreshes. building up our in-house capability on E-2C were conceived in-country, grounded firmly systems and software”. in perceived threats unique to Singapore. 1990s The E-2C upgrade project was also a complex There were strong imperatives to develop Engineering an integrated C2 capability We began local development of C2 systems in and challenging programme. It not only
40 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 41 Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION
demanded extensive software development, Developing Air C2 Hub With COTS, system equipping and dissected the system requirements into but also hardware development and systems maintenance was significantly cheaper. More modular sub parts, and took to solving them integration. Beyond the complex real-time With the successful delivery of the Air Defence importantly, the adoption of COTS opened iteratively. Trials were conducted every six software, there was also the need to integrate and Air Traffic Control Systems, MINDEF's up avenues for quicker capability refreshes months to insert new functionalities and it with legacy aircraft systems like the radar, leadership rationalised and decided to embark and insertions. technologies, and to validate the robustness of IFF system and navigation systems, via non- on a new generation Air C2 Hub (AC2H) to the evolving systems architecture continually. standard protocols and in real-time with revolutionise the propriety Air Defence and The outcome of the programme was an With this continuous validation process to responses in milliseconds. There was also a Air Traffic C2 systems. This was to become indigenous and complex AC2H that was evolve the AC2H, stakeholders interacted challenge in developing hardware suitable for our first in-house, large-scale development extensively integrated, highly available and frequently and reinforced shared vision and an airborne environment, with various options programme. Another first was that we had adequately configurable to support stringent, passion. considered. The technology landscape in the capitalised on the advancement in COTS multi-role missions of the RSAF. 1990s was slowly gearing towards commercial products to modernise our C2 capabilities, For servers, we moved from proprietary off-the-shelf (COTS) computing and display which until then had been powered by In a separate track, the Coastal C2 system computers to UNIX computers; for network, technologies. Leveraging COTS hardware proprietary equipment. was also rejuvenated using COTS solutions we moved from Fiber Distributed Data allowed us to change our design with greater by another in-house development team. Interface to Gigabit Ethernet. We selected flexibility. Using field programmable gate COTS software components carefully as array in our interface cards allowed us to use A In-house Development – Confronting the building blocks for the middleware that was • First large indigenous software to define the hardware logic, which development Challenges to be the software foundation on which the could then be easily re-programmed when • Integrated with many AC2H was developed. hardware design needed changes. The concept sensors and systems To produce a C2 system in-country was of enclosing all the commercial cards into a C challenging – we had to deliver the required We assessed and tested several COTS rugged enclosure allowed us the flexibility A A C2 capabilities within the same timeline and products, eventually adopting one that was to redefine the system logic as the project budget as established foreign contractors had built for real-time and reliable distribution progressed. Additional computing power they been contracted for the project. of financial data for banks and brokerages was added, computers upgraded, interfaces world-wide. It had the required robustness A redesigned, as well as instrumentation and The team met daily to discuss software designs and fail-safe features already built in. We were data-logging implemented. All of these were and gathered weekly to review codes. The team the first to adopt it for a military application. achieved with minimal system modifications, also had to confront many technical challenges G A T which was an unprecedented feat for aircraft S S in meeting stringent, mission-critical and real- To effectively support the high-tempo and systems then. time requirements of the AC2H. precise operations of the AC2H, there was a need to have a coherent situation picture To mitigate development risks, the team and decision support systems to allow users (Civil ATC, Shipborne C2, fighters etc.) G UAV (Aircraft reporting) R A I S
AEW Tracks UAV
Track Identifi- Receiver Extractor Tracker Fusion cation
Recognised Air Picture C C
Raw video Plots (R,az) Tracks Correlated C C Tracks
Schematic views of AC2H Iterative Development Process
42 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 43 Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION
to concentrate on their missions and to between systems and the approach for system the operation of organisational functions such dependent on a conscript force, many of these make quick and accurate decisions. Together integration at the onset of the project. As as HR, logistics, procurement, finance as well leaders have gone on to contribute in other with expertise from the sensor community timeliness of information is crucial for air as softer organisational functions that include ways in service of the nation. in the Defence Materiel Organisation, target engagement, the status and latency innovation, engagement and knowledge we specified the requirement for a multi- for the inter-system communications are management. 1970s sensors tracker and acquired it through continually measured and monitored so that a competitive tender so that we could get any deviation can be alerted for corrective Extending out of the organisation, Enterprise Structure and Industry the best-of-breed product in a cost-effective actions to be taken. The C2N was also designed IT supports the delivery of services to the manner. In addition, we also worked with to ease the integration of combat systems into organisation's customers – NSmen, full-time In July 1970, in addition to the Data Processing defence scientists from the DSO to develop the SoS and is scalable for the addition of national servicemen (NSFs), as well as the Department, the Systems and Research the algorithm and decision support systems new and future systems. To facilitate this, general public for MINDEF and the SAF. Branch (SRB) was set up under the leadership for identification of radar detections and the team adopted international standards to Enterprise IT systems also support the conduct of Mr Philip Yeo1. With the British making conflict alert. perform systems integration and defined new of business with other organisations through the decision in 1968 to withdraw its military local standards when such standards were supply chain integration, electronic commerce presence from Singapore, there was a need In 2002, we successfully delivered a robust unavailable. In doing so, the team avoided portals and links to financial institutions. to review Singapore's ministerial structures, AC2H fit for the RSAF. suppliers lock-in and gained the freedom to procedures and methodologies. The set-up of choose the best sensors and weapons to meet Being integral to the organisation, IT operations the SRB was a first step towards the endeavour 2000s and Beyond the RSAF's operational requirements. have become critical to ensure business to institutionalise “systems thinking”. To continuity. From a strategic perspective, the build up the expertise in “systems thinking”, Building upon the success and experience of In 2014, the team delivered the first spiral use of IT has been instrumental in achieving personnel certified medically unfit for developing the AC2H, the team embarked of the Island Air Defence with the SPYDER significant productivity gains, better decision physically demanding roles and with good on the design and development of the C2 weapon system successfully integrated as outcomes, organisation agility and the ability tertiary qualifications were identified and system for the Third Generation Air Defence part of the C2N. to support the transformation of business posted to SRB to fulfil their National Service System. As mentioned in Chapter 1, the models and services. duties. In 1973, the Finance Systems Branch Third Generation Air Defence is based on a Enterprise IT Systems (FSB) was also created and SRB was reframed networked concept that integrates new and Enterprise IT Portfolio as the Logistics Systems Branch (LSB) to existing sensors as well as C2 and weapons While C2 systems focus on aspects of planning, further harness IT. systems into an SoS. To network these directing, coordinating and controlling military A portfolio approach is taken to manage systems, the team designed and developed the forces and operations, Enterprise IT systems Enterprise IT to provide a framework to In 1979, these entities – Data Processing C2 Network (C2N), which provides a conduit focus on orchestrating business processes and prioritise and manage IT investment. The Department, FSB and LSB – were amalgamated for tactical information to be exchanged in the automation of business functions that portfolio comprises the following key into a single system and computer entity to real time among all combat systems in the encompass complex business rules and policies segments: form the Systems and Computer Organisation network. The C2N manages the sensors and that form the fundamental operations of an (SCO) under the leadership of Dr Tan Chin weapons centrally and is able to assign the enterprise's business. Enterprise IT involves • Logistics Enterprise Nam2. The push for the build-up of a pool best sensor and weapon pair to achieve a high a diverse range of IT capabilities that support • Personnel Admin and Finance of IT professionals went beyond defence so kill probability for successful engagement the organisation's functions both internally • Defence Infrastructure and Information that Singapore's IT industry might benefit. of incoming air threats. The processing for and externally. This led to the set-up of the National the sensor and weapon assignment takes These segments work in tandem to shape the Computer Board. place continuously and is able to reassign the Within the organisation, an individual IT landscape for MINDEF and the SAF. sensors or weapons dynamically in the event employee's IT needs would start with 1 Mr Philip Yeo Liat Kok joined MINDEF in 1970 to set up the that some of the assets become unavailable, productivity tools such as Email, Document Enterprise IT Competency Build-Up SRB. In 2007, he was appointed Chairman for Spring Singapore ensuring continued engagement. Editing Tools and Calendar that would Journey and was the first Chairman of the National Computer Board typically be pre-installed within the personal (now known as the Infocomm Development Authority of Singapore). To realise the networked capabilities, it is computing device. At the team level, this would People are the valuable resource that make critical that all systems within the C2N work include collaboration tools such as shared up the whole organisation. Generations of 2 Dr Tan Chin Nam was the first Director for SCO. He retired well not only as an individual system, but folders, messaging and meeting applications leadership in MINDEF and the DTC have led from the Administrative Service as the Permanent Secretary of the Ministry of Information, Communications and the Arts in collectively as an SoS. Emphasis was hence that support team communications and work. effectively in the use of IT. Beyond harnessing 2007. He also served as Chairman of the Board for the National placed in the design of the communication At the organisation level, the solutions support IT to realise productivity gains to help an SAF Computer Board from 1987 to 1994.
44 ENGINEERING SYSTEMS-OF-SYSTEMS ENGINEERING SYSTEMS-OF-SYSTEMS 45 Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION Chapter 3 SOFTWARE SYSTEMS DESIGN AND REALISATION