Search results

The purpose of this paper is to argue in favor of the open hardware philosophy (open-source hardware – OSH) as a technological innovation and academic entrepreneurshipmodel in Brazil.

This argument is based on three pillars. The first one refers to a bibliographic review of theoretical frameworks related to academic entrepreneurship and technological innovation to emphasize the disruptive innovation capacity of academia. Second, a few elements related to the Brazilian political, economic and structural scenario, which entail a (more) favorable environment to technological innovation and academic entrepreneurship, is presented. Finally, concepts related to OSH and its business model are approached to demonstrate the facilitating effect toward the whole process.

As a result of the argument made herein, it is possible to perceive the viability of the OSH model in terms of entrepreneurship and technological innovation in the academic sphere, and to perceive its benefits before social and economic needs in areas such as health and education.

There are no empirical or quantifiable data in the literature that enable comparison between OSH and traditional technological innovation models.

The considerations on the philosophical value of OSH and its business models are scarcely explored in international literature. As far as we know, relating OSH to technological innovation entrepreneurship in the academic sphere, as well as its singularities in Brazil regarding the innovation national system and social and economic demands, is a unique approach in literature.

The purpose of this paper is to reduce the difficulty of model predictive control (MPC) deployment on FPGA so that researchers can make better use of FPGA technology for academic research.

In this paper, the MPC algorithm is written into FPGA by combining hardware with software. Experiments have verified this method.

This paper implements a ZYNQ-based design method, which could significantly reduce the difficulty of development. The comparison with the CPU solution results proves that FPGA has a significant acceleration effect on the solution of MPC through the method.

Due to the limitation of practical conditions, this paper cannot carry out a hardware-in-the-loop experiment for the time being, instead of an open-loop experiment.

This paper proposes a new design method to deploy the MPC algorithm to the FPGA, reducing the development difficulty of the algorithm implementation on FPGA. It greatly facilitates researchers in the field of autonomous driving to carry out FPGA algorithm hardware acceleration research.

Major public cloud providers, such as AWS, Azure or Google, offer seamless experiences for infrastructure as a service (IaaS), platform as a service (PaaS) and software as a service (SaaS). With the emergence of the public cloud's vast usage, administrators must be able to have a reliable method to provide the seamless experience that a public cloud offers on a smaller scale, such as a private cloud. When a smaller deployment or a private cloud is needed, OpenStack can meet the goals without increasing cost or sacrificing data control.

To demonstrate these enablement goals of resiliency and elasticity in IaaS and PaaS, the authors design a private distributed system cloud platform using OpenStack and its core services of Nova, Swift, Cinder, Neutron, Keystone, Horizon and Glance on a five-node deployment.

Through the demonstration of dynamically adding an IaaS node, pushing the deployment to its physical and logical limits, and eventually crashing the deployment, this paper shows how the PackStack utility facilitates the provisioning of an elastic and resilient OpenStack-based IaaS platform that can be used in production if the deployment is kept within designated boundaries.

The authors adopt the multinode-capable PackStack utility in favor of an all-in-one OpenStack build for a true demonstration of resiliency, elasticity and scalability in a small-scale IaaS. An all-in-one deployment is generally used for proof-of-concept deployments and is not easily scaled in production across multiple nodes. The authors demonstrate that combining PackStack with the multi-node design is suitable for smaller-scale production IaaS and PaaS deployments.

Smart industry initiatives focus on intelligent and interconnected cyber-physical systems. These initiatives develop complex technical architectures that integrate heterogenous technologies, causing significant organizational complexity. Tapping into the digital capabilities of distant partners while capturing profit from such innovation is demanding. Furthermore, firms often need to establish and orchestrate inter-organizational collaborations without prior relations or established trust. As a result, smart industry initiatives bring together disparate organizational forms and institutional environments, distinctive knowledge bases, and geographically dispersed organizations. We conceptualize this organizational capability as ‘distant capabilities integration’. This research explores the governance mechanisms that support such integration and their relation to value capture. We analyse 11 IoT case studies organized in three categories (process, product and technologies) of smart industry initiatives. Building on existing literature, we consider different ways to describe distance, including knowledge heterogeneity and organizational, geographical, institutional, cultural and cognitive distance. Finally, we describe the governance mode appropriate for upstream (developing foundational technologies) and downstream (leveraging existing distant technologies) smart industry initiatives.

This paper aims to describe an effort to provide for a robust and secure software development paradigm intended to support DevSecOps in a naval aviation enterprise (NAE) software support activity (SSA), with said paradigm supporting strong traceability and provability concerning the SSA’s output product, known as an operational flight program (OFP). Through a secure development environment (SDE), each critical software development function performed on said OFP during its development has a corresponding record represented on a blockchain.

An SDE is implemented as a virtual machine or container incorporating software development tools that are modified to support blockchain transactions. Each critical software development function, e.g. editing, compiling, linking, generates a blockchain transaction message with associated information embedded in the output of a said function that, together, can be used to prove integrity and support traceability. An attestation process is used to provide proof that the toolchain containing SDE is not subject to unauthorized modification at the time said critical function is performed.

Blockchain methods are shown to be a viable approach for supporting exhaustive traceability and strong provability of development system integrity for mission-critical software produced by an NAE SSA for NAE embedded systems software.

A blockchain-based authentication approach that could be implemented at the OFP point-of-load would provide for fine-grain authentication of all OFP software components, with each component or module having its own proof-of-integrity (including the integrity of the used development tools) over its entire development history.

Many SSAs have established control procedures for development such as check-out/check-in. This does not prove the SSA output software is secure. For one thing, a build system does not necessarily enforce procedures in a way that is determinable from the output. Furthermore, the SSA toolchain itself could be attacked. The approach described in this paper enforces security policy and embeds information into the output of every development function that can be cross-referenced to blockchain transaction records for provability and traceability that only trusted tools, free from unauthorized modifications, are used in software development. A key original concept of this approach is that it treats assigned developer time as a transferable digital currency.

Mumbai needs to be transformed into a world-class city as stated in the 2005–2025 development plan of Municipal Corporation. For this initiative, hospital management information system (HMIS) has to be implemented across 400+ health facilities in the city.

A case study methodology was adopted to study HMIS implementation. Wave 1 of Phase 1 implementation of HMIS is carried out as a pilot project at Film City’s Hospital, Mumbai, which “go-live” on 21st June 2018. The work for hardware and software implementation was awarded to HardSystems and Solutions Limited and SoftSolutions India Private Limited, respectively, through e-tender.

Provision of inadequate quantity of hardware, slowness of network or system, non-satisfactory training after observation confirmation and sign-off process, lack of data entry operators, mismatch in numbering systems in blood bank and many other challenges concerned with the specific departments had become a major impediment in the efforts to maximize number of patients registered into HMIS.

Even after providing many clinical and managerial benefits, being the first cloud-based centrally located HMIS in any of the hospitals in the city, it imposes a major challenge for the management in terms of resistance of employees toward technology and need for the adoption of theoretical models for implementing change for the overall organizational development.

To the best of the authors’ knowledge, no other teaching case study is conducted to study the HMIS implementation in large-scale public health-care services. This is a dummy case study for teaching exercises. The identity of the stakeholders, organizations and events has been masked to maintain confidentiality.