70 Years Ago Today, Convoy HX 300 Crossed the Atlantic!

Convoy HX 300, the 300th of the numbered series of World War II HX convoys, consisting of 166 merchant ships sailing from New York, Halifax, Sydney, and St. John’s, arrived safely in the Western Approaches (and arrived in UK ports by August 3).

These ships were arranged in 19 parallel columns to produce a formation approximately 9 miles (14 km) wide and 4 miles (6.4 km) long. The convoy was protected by 6 warships when it left New York (2 submarine chasers, 1 minesweeper, and 3 corvettes), 5 warships when it left Halifax (1 minesweeper and 4 corvettes), and 7 warships (1 frigate and 6 corvettes) when Canadian Escort Force C5 assumed responsibility mid-ocean. Three warships (Isles class trawlers) escorted the Sydney ships to the main convey.

This was a very well coordinated logistics effort! And now that we have Post-Panamax cargo ships, not one we’re likely to see again. (Hopefully!)

Project Assurance: A Methodology for Keeping Your Supply Management Project on Track Part II

In Part I we introduced you to the concept of Project Assurance, the specialized discipline and practice involving independent and objective oversight, specialized experience, and audit skill to assess risk, finance, accounting, compliance, safety, and performance for any major capital expenditure (Source: Wikipedia), that is designed to minimize the risk of projet overruns and failure.

Project Assurance is a comprehensive, proactive, and preventative methodology that attempts to go beyond simply addressing tactical issues brought up in methodologies like Independent Verification and Validation (IV&V) to address strategic issues in a proactive manner so that potential issues are identified, and mitigated, before they become problems. In Project Assurance, the organization, under the guidance of the outside Project Assurance expert, a projet health assessment is conducted at a critical point of each project phase to make sure the project is on track, the project team is aligned, and the project is still likely to complete on time and on budget.

So when are these health assessments conducted and what is looked for?

  • Strategy Pre-Presentation

    before the business case is presented for funding and approval, a health assessment is conducted to insure that expectations and requirements are aligned with top management’s commitment; the key stakeholders are interviewed to determine their goals and reasons for approving the project, the cross-functional team is interviewed to gauge their take on the project, and the business case and project understanding is reviewed and compared to the stakeholder intent. Discrepancies are brought up so they can be addressed before they grow into full-blown issues.

  • Acquisition Pre-Vendor Selection

    before vendors are selected and negotiations begin, a review of software and services options is conducted to determine if there are any gaps between the proposed software and services and the business case and core requirements identified in the first phase. In addition to a review of proposals against project requirements is a review of proposed resolution procedures to make sure anything that is missed can be addressed and any issue identified can be resolved.

  • Planning Pre-Design

    after the initial drafts of the detailed project plan and change management plan have been developed to insure there is a strong methodology in place, that resources are adequate, and that time line and scope are realistic. All documents are cross-reviewed and research is conducted to identify potential issues that could arise in the project and to make sure that the plans address them or have mechanisms to address them should they arrive.

  • Design Pre-Acceptance

    after the initial drafts of the System Design documentation to ensure there are minimal gaps between the software and business requirements, the organization understands the impact of the coming change, and there are adequate resources allocated. All documents are reviewed and cross-validated and suppliers are interviewed in addition to the implementation team to make sure the core understanding of the software and service requirements is consistent and the design document addresses everyone’s concern.

  • Development Pre-Testing

    near the end of the phase to ensure project management methodology is (still) well in place, the impact of the coming change is being addressed, and the proposed education and training plans will meet user requirements and adequately cover the technology utilization requirements. The implementation is compared to the design, the training plans to the implementation, and the change management plan to the breadth of the impact. Project team members are interviewed for potential concerns and the current state is compared to the plan.

  • Testing & Training Pre-Acceptance

    near the end of the phase to ensure top management is committed to the cut-over, there are adequate resources in place for the go-live, and the education and training provided has sufficiently prepared the users for the new system. Problems explode into disruptions if a project goes-live before they are resolved.

So now that we know when project health assessments are conducted and what these assessments entail, how do they help you? Come back for Part III.

Project Assurance: A Methodology for Keeping Your Supply Management Project on Track Part I

Project Assurance, the specialized discipline and practice involving independent and objective oversight, specialized experience, and audit skill to assess risk, finance, accounting, compliance, safety, and performance for any major capital expenditure (Source: Wikipedia), is designed to improve performance, increase efficiency, avoid unnecessary cost, and, most importantly, minimize the risk of project overruns and failure.

Project Assurance goes beyond Independent Verification and Validation (IV&V) (Source: Wikipedia), which, while independent, is simply a set of procedures used for checking that a product, service, or system meets the requirements or specifications set forth for it. Project success depends on more than just getting the technical specifications right. Projects also depend on getting the talent right — as it is the people who will have to use the new system. And projects also depend on getting the transition right — if the changeover is not smooth, significant disruptions to daily operations can occur. And they depend on a 4th “T” — tracery. Organizational success depends on selecting a superior strategy and seeing it through until the desired results are achieved (or the organization changes the strategy). Tracery, from the late Middle English, can be defined as a “delicate, interlacing, work of lines as in an embroidery” or, more modernly, as a “network”. Implementing a strategy requires effectively implementing all of the intersecting “threads” that are required to execute the strategy to success. If any one aspect is overlooked, the project can fail.

And, as pointed out by Rob Prinzo in No Wishing Required, unlike IV&V, which mainly comes into play during the design and development stages, project assurance is part of the project from initial planning through initial roll-out. And at each stage it goes beyond traditional IV&V because, unlike IV&V, project assurance is not only comprehensive, but proactive and preventative. Whereas IV&V focusses simply on tactical issues relating to the system, project assurance considers the strategic intent as well as the tactical delivery. Whereas IV&V takes a reactive approach to issues discovered during the review, project assurance takes a proactive approach and tries to identify issues, and implement mitigations, before they arise. And while IV&V focuses on problems (and their solutions), project assurance focusses on prevention. The idea is to create collaborative resolution teams instead of crisis response teams when potential issues are identified. This way the issues are mitigated before crisis response is required.

So how does Project Assurance work? When using Project Assurance, organizations periodically stop and objectively assess project failure points as they arise, typically with the help of an outside third party who can be completely objective in his or her analysis on what the project team is and isn’t doing well and what could cause failure later if not adequately addressed now. In particular, the organization conducts a project health assessment at six critical points in every project — once in each of the six initial project phases defined by the classic waterfall project methodology.

Precisely when do these health assessments take place and how are they conducted? Come back for Part II.

HICX Solutions Wants To Buy You A Shiny New Pair of Shoes! Part III

In Part II of this series we not only noted that HICX, which stands for Harmonize, Integrate, Control, and eXchange, is a relatively new SIM offering on the market (even though it has been in development since 2004), addresses the classic SIM sweet-spots, but also hits a few new ones. Not only does it include on-boarding and an integrated supplier portal like classic SIM, and more than adequately address Performance and Compliance Management — mainstays of current SIM platforms, but also goes beyond to offer a complete Master Data Management (MDM) solution for your Supply Management operation.

But that isn’t the only trick it offers. As hinted at in Part I, it not only allows a user to define, and redefine, data models as necessary but define, and redefine, workflows as necessary to allow an organization to not only accommodate new product demands but adapt to new technologies and new business requirements as they arise. These new tricks are not to be underestimated. While a number of platforms allow you to extend and augment the data model, most do not allow the data model to be extended after the fact, and those that do require all existing elements to have the new property defined, or at least defaulted (to a default or a value that represents a not-yet-defined value).

In contrast, the HICX platform allows the data model for any element to be updated at any time by any user with authority, and since the HICX platform supports versioning with all data elements of the data model, no existing elements are impacted or need to be updated since the data (element) model is loaded with each data element and each data element is validated against the (element) model it was created with. (Once the data element is loaded, the user can add any additional elements required to update the associated data model, if desired.)

But that’s not the best trick that the HICX platform has to offer. The best trick is that the platform allows the workflow to be updated at any time by any user with the authority to do so, even if the workflow is being used in an initiative currently in progress — such as an on-boarding, compliance, or performance improvement initiative. This is because the platform not only versions data models, but workflows that drive the product and initiatives. If, during an event, the event administrator notices that that the workflow is causing problems for the suppliers and can be simplified, or notices that the information being collected is not what was expected, the administrator can simplify the workflow or add additional, mandatory, data requests. Suppliers who have already started the workflow will be able to finish the current workflow, and can then be sent a request for additional information by the administrator (who can limit the request to suppliers on the older version of the workflow) but suppliers who did not begin the initiative before the update will start on the new workflow.

But the real power of the workflow management capability is the ability to change registration, data collection, and performance measurement workflows (and associated data element models) when suppliers change, products change, and evaluation methods change. Traditional SIM platforms decline in usage because they can’t keep up with changing business requirements and user needs. But with the ability to update workflows to match the business needs at any time, using an integrated visual workflow designer, the HICX platform insures that SIM is always relevant and current. It’s the new trick that most SIM platforms have been missing.

Other tricks include:

  • Dynamic Dashboards

    like any good SIM product, the HICX platform supports user dashboards, but doesn’t stop at one dashboard per user — the user can create as many dashboards as he or she wants and customize them to specific purposes — compliance, performance improvement, on-boarding, insurance, etc.; the tool includes a sophisticated dashboard designer that allows a knowledgeable user to design a dashboard that is actually relevant to the initiative at hand (which can be focussed on non-compliance, non-performance etc. — since we all know that dashboards that report success are dangerous and dysfunctional)

  • Advanced Search

    that allows the user to search for any data element using any fields, and filter using any set of fixed values (lists) and related elements; these searches can be used to define supplier sets for initiatives, using as many dimensions as necessary to get it right

  • User Defined Escalations

    that allow the user to define multiple levels of automated escalation during initiatives, where each escalation can occur at a different interval and be targeted to a different group or individual

These aren’t all the tricks the platform has to offer, but they are most of the tricks of note that serve to distinguish the HICX platform from the other SIM products on the market. If you’re on the market for a SIM solution, you should definitely take a look. The name and website might be a bit non-descriptive, but the tool certainly isn’t.

HICX Solutions Wants To Buy You A Shiny New Pair of Shoes! Part II

In Part I we noted that, despite the fact that SIM (Supplier Information Management) was old news and a mature Supply Management solution offering (as the early leaders in this space were formed as early as 2000), it may still have a few tricks up its sleeves and the acquisition of the right technology platform might just get the acquirer a shiny new pair of shoes that are as coveted as Dorothy’s Ruby Slippers. (Of course, the acquisition of the wrong technology might get the acquirer a pink slip.)

We also noted in Part I that HICX, which stands for Harmonize, Integrate, Control, and eXchange, a relatively new SIM offering on the market (even though it has been in development since 2004), not only addresses the classic SIM sweet-spots, but also hits a few new ones that can bring significant value to your organization if properly implemented and utilized as it brings with it a new bag of tricks. How does it do this?

Let’s start with the five major areas of SIM covered in Part I:

  • Onboarding

    The HICX platform not only allows the entire process to be automated, but allows the workflow to be customized to each supplier according to the supplier type (sub-contractor, one-off vendor, product, service, importer, government agency, etc.), the region the supplier is in, the business unit(s) the supplier deals with, the products or services the supplier offers, the languages the supplier uses, and the data that is required for performance, compliance, or other initiatives that involve the supplier. The customized process insures that the supplier is only asked for data that is needed, and that the supplier can designate the appropriate personnel to provide that data. The portal can be configured to include a significant number of data checks to not only make sure that the data is of the right type (numeric, alpha-numeric, attachment, etc.) but that the data provided makes sense (is in range, is from a pre-defined set of answers, etc.) — which prevents a lot of typos (which can result in bad scorecards and unnecessary alerts in an exception management setup, which the platform also supports). In addition, known supplier data can be pre-populated for review, and can even come from supplier directories (including the D&B directory). It’s very easy for the user doing the onboarding to customize this process as that user can customize the process by simply selecting the supplier type, region, business unit, products, services, languages, etc. of relevance to each supplier and the system does the rest. The user then has the option to add or remove additional requirements for individual suppliers, and override any and all defaults (that they have the authority to override as per the fine-grained permissions and securities models).

  • Master Data Management

    Not only does the MDM solution provide you with numerous “out-of-the-box” data models, standards, and validations that you can customize as needed, but it recognizes that MDM systems have to integrate with downstream ERP/MRP systems, upstream sourcing and procurement systems, and even overarching BI, Spend Analysis, and Reporting systems that cross and connect the streams. (Supply Management streams are not dematerializers — sometimes it is beneficial if the streams cross.) As a result, it has out-of-the-box integrations with a number of upstream, downstream, and mid-stream systems and can push, pull, and sync data as required according to any number of user-defined rules. Plus, it allows certain aspects of master data, including bank master data, to be handled separately (and stored in separate, heavily encrypted, and highly secure data sources).

  • Performance Management

    The performance management component, as expected, allows the user to build scorecards around business goals and use whatever information is required, whether it is supplier provided, internal or third-party and whether it comes from the SIM solution, upstream solutions, downstream solutions, or cross-stream solutions. It also supports a very dynamic and flexible scoring mechanism that can support whatever formulae the user feels is necessary to construct an adequate scorecard.

  • Compliance Management

    The compliance module allows the user to create and manage compliance initiatives across one or more suppliers for one or more projects. This can be as simple as collecting raw material data to insure that the products your suppliers are manufacturing do not contain any restricted substances under RoHS or other directives, or as complex as collecting all data relating to sustainability initiatives to directly and indirectly support your organization-wide Corporate Social Responsibility (CSR) initiative.

  • Integrated Supplier Portal

    As per our coverage of the on-boarding solution, the portal is streamlined so that the supplier is only asked for data that is needed, all aspects of the portal provide the supplier with a consistent experience, and the supplier can designate the appropriate personnel to provide and maintain the data that is needed on a data type, product, or initiative basis.

But this is not all that the HICX solution has to offer. Come back for Part III.