Archive for the 'Innovation' Category
Judging from the comments on social media and the notes I have received from active and retired shipmates, the buzz surrounding CDR Guy Snodgrass’ “Keep a Weather Eye on the Horizon” is real and I’m encouraged to see it. It’s no surprise why this paper has become a topic of discussion in wardrooms and ready rooms around the fleet, and passed electronically across warfare communities.
Our Navy has a proud tradition of professional discourse, and this excellent paper lies squarely in that mold. Good arguments are typically dual-edged – one side passion, the other logic. Guy’s passion is evident and it appears many of you share it. More than that, he understands complete loyalty means complete honesty, and I know – personally – that he wrote this paper only to help make our institution better. It already has. Top naval leaders are aware of several of the issues he touches on. Many are being studied, budgeted for, or in the early stages of implementation. Others give us pause.
I share many of the concerns and have similar questions to those detailed in Guy’s paper. A quick example – many of you have heard me on the road talk about how BUPERS (being self-critical) historically “swings behind the pitch”, unable to nimbly react to economic and early stage retention issues. It’s not neglect, good people here trying to do the best they can with limited tools, but the fact is it has cost us in both good people and money. We have to do better, and I must say that this discourse helps.
We’ve all been JO’s and yes we can also fall victim to forgetting what it was like, but this is also the power of discourse. The idea that there is a perception that operational command is not valued and there is an erosion of trust in senior leadership bothers me…I want to hear more, learn more from you.
Fostering an environment where folks feel empowered to share their thoughts on important issues is a core responsibility of leadership. Ideas, good and bad, have no rank. Yet the discourse can’t just stop there. We need thoughtful debate on how to solve problems, not just an articulate accounting of what’s wrong and who’s at fault. We need leaders willing to offer new and innovative solutions to problems that at times appear impossible or hopeless. Those kind of leaders inspire all of us to continue serving men and women in our charge.
Guy has set an example for one way to ensure thoughtful debate has a voice. Please push your ideas forward — write about them, talk about them with your Sailors, up and down the chain of command. This is the only way we will overcome the challenges ahead of us – together.
The Defense Entrepreneurs Forum held their first locally organized event this past Saturday, called DEF[x] Annapolis (think TEDx vs TED). Organized by midshipmen at the Naval Academy, the goal was to bring together a group of people from around the region interested in furthering the discussion of innovation and disruption within the military.
This was the second DEF event, the inaugural conference having been held this past October in Chicago. Their format tries to emulate some of the lessons of TED, such as restricting speakers to a 20-30 minute window (including Q&A time) and bringing in people with a variety of experiences and perspectives. I was not at DEF in Chicago, so this was my first exposure to the DEF group.
There were a few major themes running throughout the speakers’ talks: how private industry can help the military innovate, that the military is resistant to change and innovation, and how military service can prepare you (or not) to be an entrepreneur. Most of the speakers were currently serving, or had at some point served, in the military and were in various stages of starting their own venture. They shared great lessons from their experiences both as military officers and as entrepreneurs. I’m not going to go into detail about what they said, because that’s not the focus of this post, and because (once the videos are online I’ll update this post with a link) you can hear them in their own words.
What struck me as largely absent from the conversation, and I’m not the only one who noticed this, was discussion about how to foster innovation from within the military – not just from the outside in via startups. Being a software developer and someone who appreciates the value of an outside disruptor to force change in an industry, I wasn’t terribly bothered by this absence. I noticed a lack of this type of discussion simply due to the nature of the event. BJ Armstrong rightfully raised the question though, both on Twitter and out loud during a session.
How about solving a problem inside the lifelines? Why do we all have to do "startups" on the outside? #DEF2014
— B Armstrong (@WWATMD) March 1, 2014
It’s a valid concern, and it got me thinking: why is there such a conspicuous lack of discussion, and (from where I’m sitting) a general lack of interest, about spurring innovation from the inside? Does it have to do with the type of person to whom this kind of thinking and iterating appeals? Is it a symptom of a culture of “shut up, do as you’re told, and don’t make waves” that persists inside the military? Perhaps it’s a combination of those factors?
I’m a lowly BM3, and a reservist at that, so my exposure to this type of thinking is far more limited than the members who are pushing this discussion further into the sunlight. My sense is that while the problem is probably a combination of the above factors, the scales tip further in the direction of a change-resistant culture. Perhaps more specifically, it’s the perception of the military at large being innovation-averse. The DEF[x] speakers are a perfect example: they saw something they felt was fundamentally wrong within the military, and they set out to correct it – by setting up their own company, not by working inside the system to push for change. Some of them may have been driven primarily by business opportunity, which is perfectly acceptable, but the sense I get is that most of them were genuinely interested in solving a problem for the betterment of the service.
My takeaway from DEF[x] was not that the answer to fixing the military’s problems lies in startups. What I took was that the biggest problem for innovation lies not with a lack of smart people with good ideas, but a lack of opportunity for those people to execute on those ideas. Innovation is alive and well in the minds of those who see a better way forward, but we need to encourage them to voice those thoughts and experiment. CRIC is a great idea, but it needs to go from one small group to a service-wide program that reaches down to the smallest unit level. Give the smart, creative thinkers the tools they need to improve the service they love, starting with a willingness to listen.
CAPT Rodgers, former CO of the USS PONCE Afloat Forward Staging Base, discusses how his ad-hoc crew of Sailors and civilian mariners plucked a 40 year old ship from decommissioning’s doorstep and turned it into the most in-demand platform in the Arabian Gulf.
Sea Control is available on Itunes and Stitcher Stream Radio. Remember to tell your friends! We think Sea Control is a fine product. Anyone who says otherwise is going to steal all your banking information and email passwords because information
All images from CAPT Rodgers’ unclassified post-deployment presentation on USS PONCE.
Innovation is about more than just coming up with new ideas. It is about personal interactions and developing relationships between people and organizations who have a desire to improve warfighter capabilities. Forward thinking organizations cannot exist in a vacuum but must learn from each other in both substance and style.
Last week, the CNO’s Rapid Innovation Cell (CRIC) traveled to San Diego, and met various some groups of disruptive thinkers and doers in the area. They visited a number of different innovative organizations and met men and women who had the courage to think and act differently from the status quo. These included a Grassroots science and technology (S&T) organization of young scientists and engineers at SPAWAR Systems Center, Pacific (SSC PAC) and an innovation forum organized by the sailors of the USS BENFOLD known as the Athena Project. In each of these organizations the CRIC saw individuals who had a vision and the courage to act on it, able to effect a positive and beneficial change to whatever field they were working in.
SSC PAC is the premier organization for developing naval command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) technologies. They have some of the best minds in the country advancing this field, but they are often not directly aware of warfighter needs. Along the same lines, warfighters are not technologists. They do not necessarily know what is within the realm of the possible from a scientific standpoint, and so might not fully understand what they can ask for. Under the leadership of Dr. Josh Kvavle, SSC PAC’s recently created Grassroots S&T group is working to bridge this technologist-to-warfighter gap and bring solutions to the Fleet faster.
The CRIC was also able to showcase a project led by LT Josh Steinman at the AFCEA West Conference. LT Steinman is working with Google to develop shipboard applications for Google Glass, and leverage its ease and portability to allow sailors easy access to information while performing tasks onboard ship. ADM Harris, Commander Pacific Fleet, utilized the Google Glass owned by the CRIC and SSCPAC as a prompter during his keynote address at AFCEA West. He demonstrated the ease of use and its wide range of applicability, and addressed the need for the Navy to develop and incorporate new technologies and ideas.
Another event the CRIC attended was the Athena Project. The Athena Project is an ongoing innovation forum started by the officers and sailors of the USS BENFOLD aimed at providing junior leaders on the ship the opportunity to present ideas and solutions to problems they are passionate about. The goal is to provide a venue where anyone, regardless of rank or position, can present their idea and be given serious consideration by an engaged audience. A set number of presenters are each given five minutes to present their idea to the audience, followed by a five minute question and answer period. At the end of each presentation, the audience votes on the idea, judging its quality, actionability, and presentation.
After presentations are finished, the votes are tallied, and the winner is awarded the Admiral Sim’s Award for Intellectual Courage. Recognition alone is not the reason behind the Athena Project. The real reward is the winner being given full permission and command backing to form a small functional team to put the idea into action during the following quarter. Since the Athena Project has started hosting innovation forums, they have grown from a mere 20 participants from a single ship’s company to an event with over 100 participants from multiple commands with onlookers from industry and academia.
The level of initiative and professionalism shown by the presenters was inspiring. Each one had taken time to research an idea they were passionate about and present it, understanding the possibility of failure., the winner of the Admiral Sim’s award at this event was an idea presented by LT Nobles and LTJG O’Donnell to pair sailors and scientists in order to foster direct communication between warfighters and the developers of their equipment. This was perfectly aligned with the goals of SSC PAC’s Grassroots S&T group. LT Nobles and LTJG O’Donnell will be developing their idea over the next quarter.
The Athena Project and other initiatives such as SPAWAR’s Grassroots S&T Group constitute the some of the best junior leaders currently in the Navy. These Sailors and civilians are forming themselves and making connections together now that will serve them as they become the future senior leadership in the Navy. These initiatives are not only important now, but are a key to ensuring the future of the Navy as an adaptable, mobile fighting force.
In the midst of political battles in Washington, D.C., dramatic cuts to military spending from the sequester and continuing resolutions, and the now infamous government shutdown of 2013, a group of military officers, enlisted, government civilians and men and women from industry gathered in Chicago last fall. The Defense Entrepreneurs Forum was held at the University of Chicago’s Booth School of Business to bring together innovators from the junior ranks of the military, senior officers with experience and advice, and experienced entrepreneurs who had come from the ranks to make a difference. Speakers ranged from Silicon Valley gurus, to military officers, and even one history geek. It was an inspiring event, and helped to stoke the embers of innovation that have been a central part of American military success time and again, through the ages.
This spring the opportunity is presenting itself again. This time, it’s closer to home for the decision makers in D.C. and the think tank crowd, as well as the U.S. Naval Institute. Not far from where the last Liberty Tree once stood, the gathering place for a previous generation of upstarts and thinkers, DEF[x] Annapolis will be held on 1 March, 2014 on the campus of St. John’s College. Bringing together the ideals of intellectual inquiry represented by St. John’s unique curriculum, the promise of military service from the U.S. Naval Academy, and a proximity to the movers and shakers in Washington, D.C., the speakers, breakouts, and social events show a lot of promise. Some of the events will be sponsored by organizations like Unleashed Technologies and USNI. The list of TED-style talks slated for this one day event are likely to be just as inspiring and informative as Chicago, including successful military innovators, operators, and again, at least one history geek.
If you’re looking to learn a little bit more about innovation in the U.S. military, about successful entrepreneurs, or about operators who have tried something new in the field, this will be the place to be on Saturday, 1 March. Even if you’re just looking for an excuse to escape the beltway and see historic Annapolis, it’s worth the short drive. Registration is limited and the seats are filling up quickly, so click through to sign up.
“Our objective must not be “safety first” in the sense of adherence to already tested practices and implements, but safety first in being the first to recognize, the first to experiment with, and the first to adopt improvements of distinct military value.” – Admiral William S. Sims, 1921.
In an era of defense draw down, technological acceleration, and globalized connections, doing the “same old, same old” is not an acceptable answer. Come join some folks who are interested in trying new things, and looking for creative solutions.
By Mark Tempest
Just click here to get to the live show (you may have to click again on a show page, but what are two clicks among friends?). Call in during the show with comments or thoughts or join us in the chat room if you think your voice is not yet ready for radio.
I think Cyber, Russia, Christine Fox’s comments, Coalition Warfare, budget constraints, the JSF, retention of our best talent, and the future of warfare will come up at some point. Plus more.
Join us live or listen later.
I made my way to the USNI/AFCEA West 2014 Conference because the theme is an important one. Shaping the Maritime Strategy. And because I was fairly certain it wouldn’t be snowing in San Diego. Sure enough, the speakers and panel sessions have not disappointed. And, there is not a snowbank in sight.
This morning’s keynote event was a roundtable on Information Dominance. Moderated by Mr. David Wennergren, VP for Enterprise Technologies and Services at CACI, the panel consisted of RADM Paul Becker USN, Director of Intelligence J2 from the Joint Chiefs of Staff, RADM Robert Day USCG, Assistant Commandant for C4I for Coast Guard Cyber Command, Mr. Terry Halvorsen, DoN CIO, and BGen Kevin Nally USMC, Marine Corps CIO.
Each spoke eloquently of the need for protecting trusted information networks in an increasingly interconnected military, as well as the complexities of the dependence on trusted networks for myriad systems, capabilities, and decision support of command and control functions. Not surprisingly, the emphasis of most of the discussion was on countering the threats to our use of the electronic spectrum, which is to say “cyber” security. Each of the roundtable speakers were insightful in describing the problem of data overload, and how that overload actually stymied efforts to retrieve information. And each commented in turn that “information dominance” was not synonymous with “cyber”, which merely represented one aspect of the concept.
The discussion amongst the roundtable members did fall disappointingly short in two critical areas. The first was the focus on technical solutions for managing data and information. Connectivity and data transfer capability dominated what should have been a cultural discussion about information management. It is not the lack of sensors, or data feeds, nor connectivity shortfalls which have hampered our attempts to wring the maximum value from our information systems. We have become so enamored of the colossal capability to access raw data that we have become less than disciplined about what we NEED to know, when we need to know it, from whom we should expect it, what form that data needs to be in, and how it is to be analyzed into information useful for decision support for C2. Little of that was directly addressed, which was unfortunate, as such lack of acumen about our information and intelligence requirements will render any system to deliver those products far less effective than they should be.
By far, however, the biggest shortcoming of the roundtable discussion was the inability of any of the panel members to actually define the term “Information Dominance” in any meaningful way. I had submitted precisely that question for the roundtable via the electronic submission system in use at West this year, but someone asked it ahead of me. The attempts to define “Information Dominance” would have made a junior high English teacher cringe. We heard what information dominance is similar to, and what the supposed goals of information dominance were, but neither was in any way a real definition. (This is not a surprise. Two years ago, the Navy had an “Information Dominance” booth on the “gizmo floor”, staffed alternately by a Captain and two Commanders. I asked each, separately, over a couple days, to give me their definition of “information dominance”. None of theirs were remotely similar, nor any more adequate than what we heard today.)
The problem, of course, is the term itself. Information cannot be “dominated”, despite assertions to the contrary. An enemy with a very specific information requirement that he can fulfill reliably and in a timely manner can be said to have information “dominance” over our massive sensor and communications networks that commanders and staffs pore over in attempts to see through the fog of war. The dust cloud from the dirt bike as the teenager rides from Baghdadi to Hit to tell the insurgents of the Coalition convoy headed their way trumps our networked, data-driven ISR platform links that cannot help prevent the ambush that awaits us.
We have much work ahead of us to make most effective use of our incredibly robust data collection systems and information networks. The solution to the problems of analytical capacity resident in C2 nodes with which to turn raw data into useful information and intelligence will be far more human than digital. Commanders have to insist on a philosophy of “Don’t tell me everything, tell me what I need to know”. And then go about ensuring that those who collect, compile, and analyze data have a very good idea of what they need to know.
And we can start by retiring the troublesome and ill-suited term “Information Dominance”. As General van Riper is fond of saying, “Words MEAN things!”. They’re supposed to, anyway.
Cross-posted at Bring the Heat, Bring the Stupid.
Cross-posted by permission from CIMSEC’s NextWar Blog
Within the U.S. Navy, routing up correspondence seems fairly straightforward, but in the execution there always seems to be issues that make it anything but. In some commands, dozens of pieces of correspondence are routed per day, and in even the best commands, an occasional piece of correspondence tends to either get lost or misplaced. Conversely, if leaders aren’t accountable, correspondence may be held onto for longer than standard policy, contributing to a negative climate. Either way, it seems like locating correspondence is always a hot topic. One thing I’ve noticed, when managing an administrative department at sea, is that most of the e-mails, questions, and drop-ins we received were related to the tracking of correspondence.
There is no standard issued software to administer the routing of correspondence at sea, so we decided to create one with support from other members of the administrative department and the CMC. The software, called eCART (Electronic Correspondence and Routing Tracker), is used to track all correspondence that goes up through the ship’s office to the XO and/or CO. Correspondence is still placed in a traditional folder with a routing slip, however, leaders now input the correspondence name into the eCART program for tracking. When it’s hand carried to the next person that it’s going up to, the user clicks a button in eCART to mark it as being “routed” to that next position in the chop chain. The program then automatically sends them an e-mail informing them they now have custody of that certain piece of correspondence. For ease of use, the e-mail contains a link that takes them to the eCART program, where they themselves can continue routing the correspondence up the chain.
When a user is routing up correspondence via eCART, they can add comments electronically. These comments, as well as the full chain of custody with dates and times, are seen both up and down the chop chain to increase transparency in the process.
When there are new comments to be read, there will be an asterisk preceding the subject that alerts the user. The interface is very straightforward and is broken into two tabs – “My box” and “My Correspondence”.
“My box” displays all the pieces of correspondence that the user’s position has custody of. “My Correspondence” displays all the originating correspondence from that user whose routing is still in progress or marked as completed/returned. For personnel that wear more than one hat, they could switch back and forth between their positions in the program by selecting their role in a drop-down box (ie: OPS may be the Safety Officer, and STRIKE may be the Legal-O). This allows any number of authorized users (even a whole office) to control one box and all receive e-mail notifications. It also allows another authorized user to fill into a position as “acting”. Thus, the routing process can still function when someone goes on leave or TAD. Since having several users control a box could create a problem with accountability, the program always logs the specific person that takes any action.
Included is a complete administrator interface, which allows designated managers to add, modify, and deactivate users and positions. There is also an option that allows the user to skip all e-mail routing notifications, which may be useful for VIP positions like the XO and CO that receive many pieces of correspondence. However, for the XO and CO, who may not want to be bothered to use the program themselves, it is more likely for designated authorized users, such as members of the ship’s office, to go in and record a change every time correspondence is transferred in or out of their boxes.
The program is built entirely on Microsoft Access. One Access file (acting as the database) is put onto a hidden directory on the ship’s shared drive or exchange server. A second Access file containing the user interface on top of 850 lines of VBA scripting acts as the client and is also put on the shared drive or exchange server as read-only and distributed to users. The client calls and communicates with the Access database on the network, which allows it to serve as a de facto software and database package, supporting up to 50 users accessing it simultaneously. The database file can easily be saved, backed up, and even transferred between LANs by simply compressing it into a zip file. The program calls and interacts with Outlook e-mail through an appropriate reference, and automatically detects the Windows’ user and alias information, so it automatically logs in the appropriate user when opening the program.
eCART is a finished product that can be deployed at any command, but is specifically intended for commands at-sea. Initially, it may be hard for all leaders in a command to adopt this new process, but with proper training, and even the implementation of policies such as one that rejects any correspondence not logged in eCART, it can easily become second nature.
James Bridger interviews adventurer extraordinaire, Rob Young Pelton, about his upcoming crowd-funded journey to find Jospeh Kony and further updates on the situation in Africa. Jim and Rob discuss civil wars, and piracy amongst others.
The episode finishes with an interview done on Federal News Radio, 1500AM, for their series “In Depth with Francis Rose.” Sean McCalley interviews our NEXTWAR Director, Matt Hipple, about his thoughts on what to watch in the coming year. They discuss Africa, China, drones, and informal military innovation/networks.
And remember… we are available on Itunes and Stitcher Stream Radio! Tell a friend, leave a comment, and rate 5 stars!
Cross-posted by permission from CIMSEC’s NextWar Blog
There’s been a big uproar lately about innovation in the Navy throughout message boards and the blogosphere – what is innovation, what it’s not, and what method Big Navy should be taking to jumpstart innovation among the fleet, if any at all. LT Jon Paris and LT Ben Kohlmann, both of whom are very involved in the conversation, had a great discussion about the topic on CIMSEC’s Sea Control Podcast, hosted by LT Matt Hipple. LT Paris followed up with an excellent blog post. While there are some contrasting views, it seems like one thing that’s agreed upon is that the deckplate innovation already occurring in the fleet sometimes doesn’t make it “up and out” or isn’t as publicized as it should be. In that capacity, LT Hipple, and some members from the CNO’s Rapid Innovation Cell, offered a challenge to start publishing examples of innovation in the fleet. I’ve decided to take this up head on in a series of “Innovation Files”.
Nearly every command has a “Plan of the Day” (POD) – a widely distributed one-page agenda with at least the current and following days’ schedule of events. Depending on the command, certain PODs are very long and many regularly contain dozens of events per day, some at overlapping times. Early on, I noticed a couple glaring inefficiencies particular to my command. First was the process – A yeoman would be specifically assigned to “do the POD” for the day, a duty rotated among the junior yeomen that nobody wanted. This task started by opening the previous day’s POD, changing the date, piling through various e-mails and files on the shared drive, and then writing the new daily schedule by hand. After an hour or two, it would get routed up to the ship secretary, personnel officer, admin officer, training officer, operations department, various department heads, command master chief (CMC), and some others before finally getting to the XO. Every position in the chop chain had their own changes and events to add, and it required the yeoman to literally go around the ship looking for each of these people, and then going back and correcting the changes for each correction or addition. It wasn’t uncommon to print in excess of 15 POD drafts before the final revision. As you can imagine, POD duties were an all-day event, and since the POD needed to be finalized and signed by the next day, it kept everybody around well into the evening.
After much thought, the XO, personnel officer, and I agreed on a plan to create a public calendar on Microsoft Outlook to streamline the POD process. However, PODs have a very specific format, and Outlook can print nothing close to the format. For example, asterisks had to be next to times if the event was to be announced on the 1MC, events had to be in bold lettering if the CO was attending, and everything had to fit on the page in two neat columns. It wasn’t as simple as hand-copying every single event into the old POD format though; the daily schedule constantly changed throughout the day, and there was no process in place to ensure if any late additions or modifications in Outlook were included in the POD. This, along with other human errors, severely complicated the process, and made it essentially as inefficient as the old method. If only there was a better way!
Introduce the automated POD (autoPOD). We decided to devise a macro app on top of Microsoft Publisher, a computer publishing tool, to automatically translate events on Outlook into the same easy POD format everyone was used to seeing. Macros are essentially programs, coded in easy-to-learn VBA (Visual Basic for Applications), that are built on top of application documents (in this case Publisher’s and Outlook’s) meant to automate tasks within these programs. Because of this attribute, it gets around IT policy requirements, which prohibit the introduction of specific executable programs not pre-approved by SPAWAR. Microsoft Publisher was chosen over Word because it’s specifically designed to manipulate documents with multiple dynamic text boxes. Through an appropriate script reference, the app asks the user permission to reach out to any designated public Outlook calendar. Then all the user has to do is click one button, and it automatically inserts the daily schedule into the POD publication – complete with dates, events, headers, etc. The layout is easily manipulated by different codes inputted into the appointment screen on Outlook. For example, for an event to appear “bold”, which indicates the CO is attending, an actual Outlook invitation for that appointment is sent to the CO, which is then designated on the user interface with a specific user name.
Along with events, the app supports all sorts of informational headers put in by different users through Outlook tags – for example, the operations officer puts in the appropriate command duty officers and duty sections, and the quartermasters put in sunrise and sunset times into Outlook. The app supports time structures displayed as “All Day” or “TBD”, and all types of recurring events. Different permissions (ie: read only, add, or modify/delete) can be granted to different users to modify the Outlook Calendar, and the program is set up for an administrator to view when and who is putting in the events, so it’s not possible to sneak a last minute evolution for the next day without the XO and CMC knowing.
AutoPOD was eventually customized for several other tasks. By request, we built an automated Plan of the Week (POW) 10-day printable outlook on top of Microsoft Excel for the Planning Board for Training (PB4T), which mimics the POD format each day, for planning purposes. Other ships had a weekly or monthly outlook summary with important events listed on the back of their POD, and autoPOD was customized for these commands as well, using the “priority” attribute to determine if the item should be displayed on a weekly summary. We have continuously refined AutoPOD to accommodate every ships’ POD format, meaning there will be little, if any, visible change to the Sailor. For example, there are options to modify the font, size, and width for the time and subject columns. Additionally, it’s designed to be plug-and-play – all contained in one publisher file – so it can be used immediately and without any complicated installation procedures. Detailed documentation is provided on how to install the program and manipulate the schedule via Outlook.
It is worth noting that the initial concept of autoPOD was not received well in its early stages. For example, the yeomen were used to a certain way of doing things, and didn’t want to move over from Word to Publisher. Despite comprehensive training, some department heads and department lead chief petty officers continued to send e-mails to admin with their events, instead of deconflicting and scheduling it themselves in Outlook. However, after much dedication and patience, everyone slowly acclimated. The new system is now second nature, and it’s hard to think of how life even functioned in the past.
To date, autoPOD has been distributed to over a dozen ships, across several waterfronts. It has undoubtedly made the POD process less frustrating, and has saved countless manhours and time, from the junior yeoman who can produce a POD in minutes, to the XO who no longer has to micromanage the process. Unfortunately, we recently hit a bump in the road when asked to set up the app on a ship that finished an extensive shipwide IT refresh known as a Consolidated Afloat Networks and Enterprise Services (CANES) installation. At the time, CANES strictly restricted ships from creating and using shared calendars, along with other security settings that prevented the app from working properly. A workaround is in progress, but it illustrates a point that has been brought up in the recent discussions – many Navy policies and procedures are around for valid reasons, but often come at the expense of productivity and innovation. It’s essential to collaborate between the fleet and appropriate project managers / designers / policymakers to figure out an optimal mix.
- Back to Basics: Restoring the United States Merchant Marine
- On Midrats 14 Sep 14: Episode 245: “The Carrier as Capital Ship” with RADM Thomas Moore, USN, PEO CVN
- Five Enduring Lessons from Arabian Gulf Patrol Craft Operations
- Solution to the Russian Mistral’s Conundrum: NATO Flagships
- Expanding the Naval Canon: Fernando de Oliveira and the 1st Treatise on Maritime Strategy