Will cloud CAD inherit data interoperability problem?

March 3, 2015

cloud-cad-pdm-interop

Cloud and CAD are probably getting to the point where it starts become a real thing. Autodesk Fusion360, Onshape, SolidWork Industrial design. It is likely to absorb some PDM functionality to make collaboration, branching, revisions and other data management tasks easier. Cloud CAD means no files, so engineers have nothing to mess with… Life is getting more Googley if you read John McEleney Onshape blog.

However, here is the thing… What if (for some crazy reason, which is easy to imagine when you deal with engineers :)), customer will decide to do a work with two cloud CAD systems? It is not unusual to see multiple desktop CAD systems in engineering organizations, so why cloud CAD will be any different.

In my yesterday blog – Cloud CAD infrastructure is getting more PDM-ish, I draw the picture of cloud CAD/PDM bundle helping us to collaborate and manage revisions. Now how two cloud CAD systems will work together? I’ve been trying to bring my cloud imagination and thought about Google Docs and Office 365 services co-existence. Actually, it is not very nice story- I can easy get my files distributed between my Dropbox, Google Drive and OneDrive accounts. So, what if my parts will be stored on Google Drive and Assembly on Dropbox? Not sure I will like it…

Similar problem in PLM world created many debates and issues. Do you remember Dassault CATIA V6 story, which required ENOVIA backend to run it? It made few customers unhappy when they discovered that they need to run two PDM/PLM systems. I can see some similarity with multiple CAD/PDM cloud bundles co-existence and interoperability.

What is my conclusion? How engineers will collaborate using multiple CAD cloud software? Cloud technology is great, but it looks like cannot magically resolve some old fundamental problems of multiple systems, collaboration and interoperability. I wish cloud CAD / PDM vendors will think about it upfront before customers will find themselves in the middle of messy CAD / import/export/migrate data scenarios. Just my thoughts…

Best, Oleg


Cloud CAD infrastructure is getting more PDM-ish

March 2, 2015

fusion360-cloud-pdm-cad-branches

PDM was long time a step child for many CAD systems. To deal with CAD files, their relationships and dependencies including multiple revisions of document was complex and painful. So, many customers just gave up and stored files on shared drives. It was okay until the our life was disrupted by a new way to get work done – online, connected, collaborative.

The initial intent of collaborative cloud systems was to solve the problem of collaboration and data sharing. The idea to provide a value on top of existing CAD desktop file systems was interested. So, specialized cloud CAD file sharing and collaboration systems got focus and attention.

At the same time, CAD vendors got to think about longer term solutions. CATIA was one of the first systems that announced the disconnect from a traditional file systems. I posted about that few years ago – The future of CAD without files.

These days, the race towards cloud CAD is accelerating development of data management and CAD collaboration technologies for the cloud. Few weeks ago, I shared some of my thoughts about importance of PDM technologies for cloud CAD. Cloud CAD vendors are clear about their intent to make PDM part of their core product technology.

My attention caught Autodesk Fusion360 article – Fusion System Architecture Changes Coming in the Next Release – Why and What. Read it, because it contains some very interesting pieces of information about how files are going to disappear into future cloud infrastructure. Here is the passage I captured:

With the coming release of Fusion, we will be introducing significant changes to Fusion Cloud Service architecture that lays a strong foundation on which we can build an environment that is rich in WIP DM. As part of this change, we are introducing the Autodesk Work In Progress Cloud Service which is designed to model and manage complex relationships that are associated with a design. The service is highly scalable, highly available and optimized for performance. Another important change in the February release is significant improvements to the Fusion Object Storage Service. Taken together, these changes will result in immediate benefits in the way of performance gains and high reliability in the Fusion upload and download data pipeline, and allow the Fusion team to deliver rich DM workflows in subsequent releases.

Another article from Fusion360 blog brings an excellent explanation what these date services mean for end user. These are functions that belonging to PDM system in a traditional file based CAD / PDM setup.

…it solves so many common design problems that we’ve heard from the community, both in Fusion 360 and other programs, and improves workflows for both teams and single designers. Branching and merging lets you easily:Work in parallel with other members of your team. Explore changes or alternatives to a project and keep changes that make sense while leaving behind changes that don’t. Understand how your project evolved over time and what decisions were made (and why). Restore or reuse any design(s) in your project from any point in your project. Use any point in your project as a starting point for a different project.

What is my conclusion? It is hard to bring a value of cloud design collaboration without re-thinking the way CAD-PDM bundle is operating. For new type of cloud CAD systems it means to embed core PDM collaborative function and make it part of CAD system. It sounds like a very exciting time- many collaboration and data management problems are going to be solved by that. However, here is a question. What will happen when two cloud CAD systems will have to collaborate together? Looks like a topic for another blog. Just my thoughts…

Best, Oleg


Cloud CAD will have to solve PDM problems at first place

February 10, 2015

ds-solidworks-cloud

The race towards CAD in the cloud is getting more interesting every day. I’ve been watching SOLIDWORKS World 2015 live streaming this morning. Overall SOLIDWORKS show was very impressive, as usual. I look forward to keep watching it following days.

However, what caught my special attention today is a presentation of a new cloud product – SOLIDWORKS Industrial Design. Couple of interesting facts about new product – works on top of Dassault 3DEXPERIENCE platform (in many aspects, think about it as ENOVIA V6); focus on free design with no traditional CAD constraints; leveraging cloud approach for social connection between users and collaboration. And… it is complimentary for SolidWorks users. Demo of product presented few scenarios in which design flow went between new cloud product and old SolidWorks connected by 3DEXPERIENCE platform. Sounds like a big deal.

The story about new SOLIDWORKS/3DEXPERIENCE product took me back to my comparison of Onshape and Autodesk Fusion360 visions few days ago – Carl Bass and Jon Hirschtick are in agreement about future of CAD. In my view, changes in design world towards distributed teams and ability to work effortlessly on any device without installation and manual upgrades are two main driving factors behind new cloud solutions. The story about Autodesk Fusion360, Onshape and SOLIDWORKS made me think about interesting priorities all creators of cloud CAD are thinking about. It was well articulated during SolidWorks World 2015 first day keynote – supporting any device, information is up to date all the time, users are connected (see picture above).

It makes a perfect sense to me, since it is a great reflection of modern cloud paradigm you can see well developed in products such as Google Apps, Office 365 and others. However, this is a place where complexity of CAD data requires from cloud products to be more sophisticated. Traditionally, CAD project is combined of multiple files – assemblies, parts, drawings, etc. As you start making changes you very quickly end up with a complexity of many-to-many relationships between different versions of parts, assemblies and drawings. Move it to the cloud – the complexity won’t disapear. Therefore, you can see both Autodesk Fusion360 and SolidWorks Industrial Design are trying to solve. I had no chance to see Onshape product yet, but my hunch Onshape will try to solve this problem too.

Autodesk Fusion360: revision control, branching and collaboration

autodesk-fusion360-rev-branches

carl-bass-fusion-360-au2014-2

SolidWorks Industrial design: 3DEXPERIENCE collaboration, branches, revision merging

solidworks-industrial-design-1

solidworks-industrial-design-2

What is my conclusion? In a traditional CAD world, the problem of file revisions, collaboration and data control was part of PDM solution. Historically, CAD vendors were reluctant to solve PDM problems unless it became absolutely necessarily. PDM was complex, required services, special pre-sale process, etc. However, cloud is creating a new demand and constraints for new CAD in the cloud paradigm. With the absence of file system exposed to end user, cloud CAD system will have to solve a PDM problem first. Just my thoughts…

Best, Oleg


How to prevent cloud PLM integration mistakes

February 2, 2015

connected-plm-erp

Cloud is huge enabler for collaboration between people. It makes your data and processes accessible everywhere from a browser. It can help you to collaborate between engineers and suppliers. It can help you to integrate systems and people across enterprise.

Let me speak about the last one. The integration topic is actually tricky. I’ve been sharing some of my thoughts about cloud integration challenges – Integration is holding back PLM cloud adoption few months ago. Last week, I had a chance to attend two webinars about PLM and integration.

Become a Connected Manufacturing Enterprise with Agile Integration by Jitterbit. The following picture gives you a perspective on a problem of “connected manufacturing” and architecture solutions like Autodesk PLM360 and Jitterbit are solving this problem.

plm360-jitterbit-1

Here is the view that shows you the reality of mixed (cloud and on-premise) integrations.

plm360-jitterbit-2

Another webinar by CIMdata – “PLM & ERP: What’s the Difference, and Why Should you Care?” is providing another perspective on integration challenges between engineering an manufacturing.

cimdata-plm-erp-1

cimdata-plm-erp-2

Companies are moving into mixed cloud and on premise environment. This is a reality and we cannot avoid it. So, for a foreseeable future, we will have to deal with integration of multiple systems – some of them will continue to run on premises and some of them will be elsewhere (public cloud). It made me think about potential mistakes you can run into while integrating systems.

1- Lost data semantics

Most of integration scenarios are about how to send data back and forth between systems. It is hard to keep semantics of data and not to loose it when exchanging information. So, define what data means and keep an overall integration data schema. Otherwise, the result can be messy.

2- Data transfer limitation

Although some of integration infrastructure can allow you to implement data exchange quickly, you can underestimate the bandwidth requirements. Sending large packets of data can cause significant latency and create runtime errors and problems. Check what monitoring tools are available to handle such situations.

3- Transaction management

Most of manufacturing systems are sensitive to transactions. To manage distributed transactions can be tricky and require some fine tuning. Pay attention on how you handle error processing when integrating transaction system managing ordering, lifecycle and bill of materials.

What is my conclusion? The complexity of integration is growing. Cloud systems are bringing many advantages, but will create additional challenges to IT and professional services. Most of integrations are not working out of the box. New tools running from the cloud can help you to integrate it faster, but it will require good coordination with IT and planning upfront to prevent potential mistakes. Data integration is hard and requires experience and familiarity with manufacturing systems. Just my thoughts…

Best, Oleg

photo credit: freefotouk via photopin cc


How PTC is delivering PLM in the cloud?

January 28, 2015

ptc-plm-cloud-1

Cloud is trending and it is hard to find a company who is not thinking how to leverage new cloud technologies and business models. However, just to say “cloud” these days means probably nothing. The right question is how to implement cloud. I guess many companies these days are coming to that question. It goes in parallel with the discussion about what is “cloud” and what is “not cloud”, which has some technical and some marketing aspects.

Long time ago, PTC introduced PLM “On Demand“. You should remember this marketing name that later was replaced by SaaS and cloud. According to the PTC website, the solution is available and hosted by IBM. I noticed some indication of PTC move to the cloud back in 2013 after acquisition of NetIDEAS. My writeup about that is here. According to PTC press release NetIDEAS allowed to PTC to develop a better foundation to offer multiple deployment options.

Earlier today, my attention was caught by PTC announcement – PTC Introduces PTC PLM Cloud New PTC Windchill SaaS offerings for small and midsized companies. The following passage is explaining the reason why PTC is coming with cloud product offering

Recognizing that many SMB organizations may lack a dedicated IT staff but still want to adopt a proven PLM environment, PTC designed PTC PLM Cloud specifically to enable team collaboration and data management in the cloud. This flexible offering eliminates the typical, but risky, SMB practice of shared folders and file naming conventions which hamper product development. With more effective and reliable data sharing in the cloud, customers are able to improve product development across teams in different locations, teams working with varying CAD applications, and with external teams such as partners and suppliers who are a growing part of the product development process.

I tried to dig inside of materials available online to see how PTC will provide cloud PLM and what options are available. Navigate here to learn more. It is available with 3 options – standard, premium and enterprise. While names mean nothing, the following definition caught my attention – “instant access” for standard vs. “dedicated database” for others. In addition to that, the differences between options down to “workflow customization” in premium “new business objects and UI customization” for enterprise. It looks like PTC recognized the importance of MCAD data management – all versions are coming with integrated viewing solution and support for Creo, AutoCAD, Inventor and SolidWorks.

ptc-cloud-28-jan-2015

The questions that remaining open me at this moment are price and cloud (hosting) architecture. It is essentially important for customers today as I mentioned earlier in my post – Why you should ask your cloud PLM vendor about Devops and Kubernetes.

What is my conclusion? Manufacturing companies are not implementing PLM because of high cost and availability of IT resources. To many customers and vendors today, cloud seems like a right path to remove IT cost and make implementations less painful. From that standpoint, PTC is taking right trajectory by delivering Windchill based PLM solution using cloud. However the devil is in details. I’m looking forward to learn more about “how” PTC on the cloud will be delivered and how it will be different from other PLM clouds from Autodesk, Aras, Dassault Systemes and Siemens PLM. Just my thoughts…

Best, Oleg


Cloud PDM: stop controlling data and check shadow IT practices

January 21, 2015

cloudpdm-shadow

An interest of customers in cloud PDM solution is growing. I guess there are multiple factors here – awareness about cloud efficiency and transparency, less concern about cloud security and improved speed and stability of internet connections. If you are not following my blog, you can catch up on my older blog articles about cloud PDM – Cloud PDM ban lifted. What next?; Cloud PDM hack with Google Drive and other tools; Cloud can make file check-in and check-out obsolete. The confluence of new technologies around cloud, web, mobile and global manufacturing is creating a demand for cloud (or web based) solution helping distributed design teams.

So, where is a challenge for cloud PDM? My hunch, the biggest one is how to sell cloud PDM to manufacturing companies. I can divide all customers into two groups – larger manufacturing companies that already implemented PDM solutions and smaller manufacturing firms that are still managing CAD design with folders, FTP and Dropbox accounts.

Analysts, researchers and PDM marketing pundits are trying to convince companies that cloud PDM can become a great enabler for collaboration and leaving CAD data “not managed” can bring even greater risk to organization. There is nothing wrong with that… PDM was build around the idea of how to take a control over data. However, the idea of “control” is not something engineers like. Ed Lopategui is speaking about engineers and control in his last blog – The day the strength of PDM failed. Here is a passage I liked:

The second reason, which is not so legitimate, is a loss of control. The reason so many engineers pine about the days of paper-based PDM in document control departments (or instead nothing at all) is that world could be circumvented in a pinch. It was flawed because it was run by humans, and consequently also replete with errors. Replaced with immutable and uncaring software, engineers working in groups nonetheless become irritated because they can’t just do whatever they want. You see this very conflict happening with regard to source control in software development circles. The order needed to manage a complex product necessarily makes manipulating pieces of that engineering more cumbersome. It’s one thing to be creating some widget in a freelance environment, it’s another matter entirely when that end product needs traceable configuration for a serialized certification basis. And that will happen regardless of how the software operates.

Here is the thing… Maybe cloud PDM should stop worry about controlling data and think more about how to bring a comfort to engineers and stop irritating users with complex lifecycle scenarios? It made me think about practice that known as “shadow IT”. For the last few years, shadow IT and cloud services have lot of things in common. Don’t think about shadow IT as a bad thing. Think about innovation shadow IT can bring to organizations.

Forbes article “Is shadow IT a runaway train or an innovation engine?” speaks about how shadow IT can inject some innovative thinking into organization. This is my favorite passage:

As we reported last month, one corporate employee survey found that 24% admit they have purchased and/or deployed a cloud application — such as Salesforce.com, Concur, Workday, DropBox, or DocuSign. One in five even use these services without the knowledge of their IT departments.

The rise of shadow IT may actually inject a healthy dose of innovative thinking into organizations, at a time they need it most. The ability to test new approaches to business problems, and to run with new ideas, is vital to employees at all levels. If they are encumbered by the need for permissions, or for budget approvals to get to the technology they need, things will get mired down. Plus, shadow IT applications are often far cheaper than attempting to build or purchase similar capabilities through IT.

What is my conclusion? Stop controlling data and bring a freedom of design work back to engineers. I understand, it is easy to say, but very hard to implement. To control data is a very fundamental PDM behavior. To re-imagining it require some innovative thinking. It is also related to the fact how to stop asking engineers to check-in, check-out and copy files between different locations. Maybe, this is an innovation folks at Onshape are coming with? I don’t know. In my view, cloud PDM tools have the opportunity to change the way engineers are working with CAD data. Many new services became successful by providing cloud applications and making existing working practices much easier than before. Just my thoughts…

Best, Oleg
photo credit: Dean Hochman via photopin cc


How many enterprise PLM systems will survive cloud migration

January 14, 2015

plm-stairs-to-the-cloud

Cloud adoption is growing. For most of existing PLM vendors it means to think about how to migrate existing platforms and applications to the cloud. I covered related activities of PLM vendors in my previous articles. Take a look here – PLM cloud options and 2014 SaaS survey. It can give you an entry point to few more articles. Some of vendors such as Dassault System are promising to deliver a full set of cloud options – private, public and hybrid. Aras is partnering with Microsoft Azure and Siemens PLM is focusing on a diverse set of IaaS options. At the same time to move existing platform to the cloud won’t be simple. To migrate customers’ environments to the cloud will be even more complicated.

My attention caught by InfoWorld article – Docker’s tremendous upside could upset some enterprises. If you are not familiar with what Docker is, navigate to my earlier blog – Why to ask cloud PLM vendor about Devops and Kebernetes. InfoWorld article speaks about Docker’s ability to support application portability and a potential clash between what Docker can provide and the cloud migration strategies developed by enterprises for the last few years. Here is an interesting passage.

With Google, Microsoft, and Amazon Web Services all supporting Docker, your management may feel compelled to take a hard look at it as the right enabling technology. If this means rebooting your existing application migration strategy, perhaps even redoing 50 applications, then so be it. After all, the technology is changing so quickly that enterprises should be allowed to change strategy when new developments arise.

How is that related to what PLM vendors are doing? In my view, it is an additional shakeout to PLM vendors as they go towards more learning about cloud applications, services, and ways to migrate from existing PLM platforms into future “clouds”. It is about “how” to make cloud real and it will require to go down from marketing messages about moving to the cloud into deep waters of DevOps and services. One of my PLM predictions for 2015 was about the fact software vendors will discover the complexity of cloud PLM migrations. You can listen to my 3 predictions for PLM in 2015 by navigating to the following podcast by SPK and Associates.

What is my conclusion? PLM vendors and enterprise customers soon to discover the complexity of migration to the cloud. It will come trough understanding of underlining architectures, complexity of operation, service level commitments and other business and technologies topics. Most of enterprises are heavy invested into customization of existing PLM platforms, which will add an level of complexity for migration. How many enterprise PLM apps will survive cloud migration? This is a good question to ask in coming year. Just my thoughts…

Best, Oleg

photo credit: M J M via photopin cc


Kenesto cloud PDM hybrid

December 18, 2014

cloud-pdm-hybrid

Few months ago, I posted about latest development of Kenesto cloud data management solutions – Kenesto revamp: does it change cloud PLM game? I saw it as a sharp turn for Kenesto from focusing on collaboration towards engineering and product data management business. From earlier comments made by Steve Bodnar of Kenesto here, I’ve learned Kenesto is developing technology to synchronize CAD data between desktops and cloud locations. Here is the comment made back in October:

…automatic synchronization maintains appropriate version control as well as permissions. This way, if you have “download only” permission, as an example, you can synchronize to one or more of your locations, and any updates will automatically be synchronized to those locations for you (in addition to notifications being sent).

CIMdata recent publication about Kenesto Collaboration Platform made me think again about what it does and how it might be different from other cloud PDM products available now or soon become available on the market. What caught my special attention in CIMdata publication is related to so called “innovative intersection of cloud-based file management and data sharing with traditional PDM vaulting”. A massive amount of CAD data is stored on corporate networks and just CAD desktops. It made me think Kenesto is trying to bring solution to customers that already have traditional PDM systems and extend it with a better collaborative option. The following passage from CIMdata commentary provides more explanations:

The Kenesto solution is a secure, hybrid, cloud-desktop collaboration platform where product development and delivery teams can collaborate using discussion threads, or by co-authoring documents and design files, with anytime, anywhere access. Kenesto puts a broad range of capabilities at the fingertips of product delivery teams to organize and manage their programs, products, and projects. Teams can create their workspaces with people, workflow, forms, data, and reports—including bills of materials, change requests, and purchasing forms—and be kept on the same page with Kenesto’s proprietary intelligent synchronization approach. Each user is provided with a dashboard that can be customized to personal preferences. An important feature in Kenesto is that users are always in full control of their documents and designs. A user can permit their teammates to view, mark-up, or edit their documents and designs and can collaborate with them in real time or asynchronously.

Many of features such as project, workspaces, workflow, forms, bill of materials, change requests etc. are not new in PDM industry. However, “cloud-desktop” hybrid sounds like a new buzzword. Does it mean Kenesto found something unique in terms how to bring desktop CAD users to the cloud? It hard to say based on a commentary, but it might go that way.

What is my conclusion? Market dynamics are bringing more engineering and manufacturing companies to the cloud. It gives more opportunities to cloud PDM/PLM vendors. At the same time, it raises more questions how existing environment and data assets will be managed and how people will collaborate in a hybrid environment. Kenesto might solve an interesting problem here and compete with other vendors in the same domain – Autodesk, SolidWorks, GrabCAD and others. Just my thoughts…

Best, Oleg

photo credit: ukCWCS via photopin cc

Photo is an illustration only and does not reflect Kenesto architecture.


Cloud is an opportunity to set open standards for PLM

December 11, 2014

standard-cloud

One of the topic that usually drives lot of attention in engineering software is standards. Or absence of standards. The story of standards goes back long way to CAD formats and multi-CAD universe. I’ve been touching topic of standards and PLM earlier. Catch up on my posts – CAD/PLM standards and toothbrush problem and PLM standards: from formats to frameworks.

With the raise of cloud technology development, the question I wanted to ask how it will impact future standards creation. Does cloud provides a better grounds to build standards in services, data exchange and communication?

InfoWorld article Open standards face an uphill climb in the cloud bring a perspective on cloud standards and enterprises. The interesting thing here – we can see again the challenge standards are facing to compete with established large vendors. The following passage summarizes the situation:

Despite initial enthusiasm for open technologies, enterprises are favoring proprietary big-name cloud providers.When it comes to cloud standards, enterprises voted with their dollars. Most have focused more on Amazon Web Services, Microsoft Azure, and Google offerings than on standards such as OpenStack and CloudStack. Of course, AWS, Microsoft, and Google are cloud services providers, whereas open standards are enabling technologies. But vendors that have built their public and private cloud offerings around a standard (usually OpenStack) have not been on the short list of cloud technology providers for most enterprises. In fact, most vendors that pledged allegiance to open standards years ago — including IBM, Hewlett-Packard, and Rackspace — have been largely overlooked by enterprises, which are mostly instead choosing AWS, Azure, and Google.

What is my conclusion? Cloud can revolutionize technological stack used in enterprise. This is an opportunity for companies to choose open standards, which will provide more openness and support establishment of new open PLM platforms. However, it is not happening yet. While large enterprise manufacturing voting with dollars and focusing on AWS, Azure and Google, small companies and individual makers can find cloud software using open standards as an interesting option. Just my thoughts…

Best, Oleg


Integration is holding back PLM cloud adoption

December 11, 2014

cloud-puzzle-integration

Cloud PLM adoption is growing. More PLM vendors these days are re-branding and re-building product and software architecture to keep up with fast moving cloud trend. This year I can see significant shift towards discussion about technical aspects of cloud implementation. The devils is in details and differentiate between variety of cloud implementation options is very important.

However, regardless on technological options, what do you think holding back all cloud implementations. In the past, the topic of security was one of the most debated among engineering software professionals and customers. Security is important. But what else

Forbes article Cloud Computing Adoption Continues Accelerating In The Enterprise speaks about different aspects of cloud business. I highly recommend you to read it -I’m sure you can find many interesting data points. My attention caught the following chart presenting top disconnects holding SaaS applications adoption:

The three biggest disconnects holding cloud-based infrastructure and applications back from greater adoption from an IT senior management perspective include concerns about the security (61%), integration challenges (46%) and information governance (35%). IT leaders perceive that line-of-business (LOB) leaders are most concerned about security (52%), difficulty measuring Return on Investment (ROI) and determining the accurate economic value of cloud solutions (37%) and a tie between information governance and cloud-based applications being able to meet enterprise and/or industry standards (32%).

cloud-software-disconnects-plm-forbes

Security is an obvious suspect. What was very interesting is to find Integration, standards and information governance as #2 and #3. As I posted few weeks ago, integration is one of the major challenges that influence broad PLM adoption and ROI. It looks like cloud applications adoption is even more dependent on the ability to integrate multiple SaaS and on premise applications.

What is my conclusion? Cloud adoption is growing. However, enterprise software landscape is complicated. Integration was always a challenge. However, cloud applications are bringing new type of challenges. PLM is data intensive with a lot of dependencies of data distributed between departments, databases and external companies-suppliers. New cloud technologies can make integration easier by leveraging modern web technologies. However, absence of standard and large amount of legacy software makes it really complex. Just my thoughts…

Best, Oleg

photo credit: Adam_T4 via photopin cc


Follow

Get every new post delivered to your Inbox.

Join 272 other followers