Skip to main content

Introducing Gov and the City

For more than twenty-eight years, I have lived in Washington, DC, the biggest government city of them all. I created this blog to share my thoughts on government, not only federal but also state and local government. Specifically, my areas of interest is information technology for government.

I came to DC back in 1980 to pursure a career in public affairs. I earned a Master of Science in Foreign Service at Georgetown University, with a concentration in international security affairs.

My first job outof graduate school was at the Center for Strategic and International Studies (CSIS), at that time associated with Georgetown University. I started as a research assistant, then worked through the ranks to research associate and ultimately fellow in international security affairs. I wrote books and papers and spoke to conferences.

What a heady time it was, back at the beginning of the 1980s, especially for a foreign policy wonk. The United States had been battered overseas, and morale was low both in the defense and intelligence communities. It was exciting to see academic theories put into practice, and the gratifying results on the world stage.

I ended up entering the information technology field while I was at the think tank. I helped write a proposal to create an international network in the field of Soviet studies. I traveled around the country helping connect scholars to the network and worked on building databases.

In 1987, I started a company, Information Strategies (Infostrat), focused on software for the public sector. My first contracts were building custom databases, largely relating to defense programs. Next, I won some work with Smithsonian Institution and Pepsi-Cola. We ultimately ended up specializing in Microsoft solutions. Today our business is divided among federal, state and local, and commercial customers.

I couldn't get the think tank out of my blood, so I applied what I learned at Georgetown and CSIS to my business. I stepped up my publishing efforts and wrote a half dozen computer books and numerous articles. Best of all, I surrounded myself with technology and subject matter experts much more capable than me.

We have written a number of books on software and technology topics. The most recent was on Microsoft's portal platform, particularly SharePoint. We are also publishing white papers, such as a comparison of SharePoint and Dynamics CRM, and Using Dynamics CRM as a Development Platform.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises