Profile of:
Barrie D. Gray B.Sc. M.B.C.S.
Achievements:
Over 45 years experience in Information Technology. Extensive
knowledge of system architecture, requirements, feasibility, costbenefit analysis, system engineering, Object-Oriented
Programming (OOP), Windows, SharePoint Server, web-based,
client-server and N-tier design, development and implementation.
Experienced in portfolio and project management, heading
multiple project teams in a Federal Government environment.
Responsibilities included:

Project planning, approval and management

Resource planning and scheduling

Team(s) motivation and morale

Budget management

Resource negotiations and acquisition

Technical architecture

Programming and documentation standards

Code re-usability

Database design and integration

Secure access control

Cross platform implementation

Mainframe connectivity

Intranet & Internet

Quality Assurance

Data conversion strategies & tools

Training plans, documentation, courses
Experience working with Microsoft Visual Studio .NET (VB.Net,
C#, ADO.Net, ASP.Net), SQL Server, Oracle, XML, XSD, XSLT,
XPATH. Numerous technical articles published on OOP,
development tools (Visual Basic, Access and C++) and Windows
NT/2000 in the national trade magazine, Computing Canada.
Top Secret (PWGSC) and Secret (PWGSC) Security Clearances
01
21
Midland Microcomputers Limited
Interaction Profiling - A New, Object-Oriented Design Paradigm for Simplified Business Process Management
Business Analyst / Creator / Designer / Prototype Creator and Developer
August 2012 -- Present
Interaction Profiling is a brand new, ground-breaking approach to simplify the implementation of Business Process
Management within almost all Enterprise Applications, including all Case Management / Case Tracking systems. The
concept focuses on the different types (profiles) of business interactions (transactions) in an enterprise business processing
application and associates the corresponding, table-driven validation rules and BPM tasks (and more) with each profile. This
metadata is managed by the Users directly with simple maintenance forms.
As an application development approach, Interaction Profiling does not involve hard-coding of any validation or business
processing logic. Once the first, comprehensive Interaction Profiling framework is constructed or acquired, it can be re-used
with minimal changes for all future applications. Based on the first prototype that embodies Interaction Profiling, it is
estimated that the new paradigm will halve development times and costs for all subsequent systems. Further details
can be reviewed in more depth on Mr. Gray's 12-post blog series. He also has an overview article on BPM.com. The URL
for that is http://bit.ly/1GJbQT8. Because of security issues on the BPM.com site, this link cannot be opened from MS Word
directly. Please cut and paste it into your browser. There is also a link to it on Midland Microcomputers' web site,
MidlandMicro.com.
Interaction Profiling was envisioned, created, designed and the world's first interaction-profiling-empowered prototype
application system designed and built entirely by Mr. Gray. The prototype system confirms the legitimacy of the claims for
development and maintenance effort and cost savings and can be demonstrated upon request from any interested parties.
Mr. Gray created this new BPM application implementation paradigm after reviewing his many years performing User
Requirements studies, Feasibility, Analysis, Design and often Development and Implementation as well, on the numerous
Case Management / Case Tracking systems and other custom-built application systems that incorporated Business Process
Management (BPM) logic to complete transaction processing. Several of these systems included home-grown BPM logic
and it is the refinement of these original ideas that led to the production of the Interaction Profiling paradigm. Interaction
Profiling is a bold, new concept. It is in its infancy, but once a general understanding of the benefits becomes more widely
accepted, Interaction Profiling techniques will be adopted by major BPM software vendors and it will become a tool in every
Business Analyst's tool box. Please check out Midland Microcomputers Limited web site for more information.
02
21
Public Works and Government Services Canada (PWGSC)
Operations Centres Information Portal (OCIP)
Technical Architect / Implementer
September 2011 -- July 2012
The OCIP system is a public web-facing, Microsoft SharePoint 2010 site collection for use by over 50 Federal Government
Departments' Emergency Operations Centres. It is a high availability implementation with a three-tier server architecture
replicated in a remote disaster recovery centre as well as the operational portal. Continual Microsoft SQL Server 2008 R2
log-shipping transfers occur between the operational centre and the disaster recovery site and six-monthly switchover
between the two centres was performed to ensure on-going viability of the disaster recovery facility. Initially, Mr. Gray was
the sole resource (in addition to the overall Project Manager) on the initial rollout to the two sites. The team was augmented,
after three months, with an additional three technical resources to provide on-going support and OCIP maintenance.
Technical Environment: Microsoft Windows Server 2008 R2 on all servers, .Net framework version 3.5, Visual Studio .Net
2008, C#.Net, SQL Server 2008 R2 Enterprise Edition, SharePoint Server 2010 Multi-language version with Forefront Anitivirus
security, Forefront Security for SharePoint 2010 and Forefront Management Console for Windows Server. Canada's Multi-
Barrie Gray
AMITA Corporation
2
Agency Situation Awareness System (MASAS) was embedded within OCIP for advanced GIS graphical displays of incident
locations. Final customization and implementation was performed remotely using an AMITA-based development environment,
SharePoint Designer 2010, C# .Net 2008, Powershell scipts, JavaScript, Collaboration Application Markup Language (CAML)
and CSS.
Roles/Responsibilities:
1.
Performed all initial software installations on all six servers (two locations), configured and implemented Microsoft
Windows Server 2008 R2, Active Directory Domain Services (ADDS), SQL Server 2008 R2 Enterprise Edition in
both sites and SharePoint 2010 and Forefront Security software.
2.
Rolled out the OCIP prototype portal in an operational configuration across the three-tier architecture.
3.
Installed and configured the MASAS OCIP module
4.
Designed and Implemented SQL Server log-shipping operations between the main centre and the disaster recovery
site.
03
21
5.
Created PowerShell scripts to manage and administer the portal environment and MASAS implementation
6.
Configured SharePoint portal Site Search and User Profile Synchronization.
7.
Triaged and fixed initial operational problems
Public Safety Canada (PS)
Security Screening System
System Technical Architect / Business Analyst / Developer
May 2004 – September 2011 (7 years)
The national security screening system has an on-line and batch component. The batch component is for Electronic Data Entry
(EDE) and was a legacy Cobol implementation. PS required the system to be re-developed in a Microsoft .Net environment.

Re-usable code library (dll);

Common XML Schema and transformations using XSLT and XPATH

Redesign and optimisation of the complex, phonetic search processing;

Program maintainability, and

Performance optimisation.
Technical Environment: Microsoft .Net framework version 1.1., 2.0, 3.0, 3.5, Visual Studio .Net 2003/5/8/10, Visual Basic.Net,
C#.Net, ADO.Net, SQL Server 2000/2005/2008. An application dynamic link library contains common class modules, applicationspecific and general utility routines. The new system is much more maintainable and robust because of the cleaner design,
structured program formats, structured exception handling, use of class libraries and functions and better code annotation. A
single XML schema is now common to all electronic data sources and extensive use of XSLT converts all different feeds to the
common model. A single point of entry has greatly simplified and dramatically improved validation, error handling and reduced
overall maintenance.
Roles/Responsibilities:
Barrie Gray
AMITA Corporation
3
1.
Provided and developed the initial technical architecture proposal and approval for the batch system re-write. Mr.
Gray architected the re-design of the batch component, has completed the Visual Basic .Net, ADO.Net, Microsoft
SQL Server programming and the revised system is fully operational. Was instrumental in proposing the use of the
.Net framework and designing the .Net implementation of the batch system. Built the framework for the project
(only developer) and completed the initial full re-write.
2.
Business analysis of existing processes and recommendations for process improvement using Sparx Systems
Enterprise Architect for modeling.
Also performed several system level process improvements, including the
introduction of a universal screening request schema merging the original 9 different schemas (client-specific), a
single validation point (replacing more than 9 and counting when Mr. Gray joined as team leader) and use of XSLT
transformations to replace multiple, individual XML feed upload programs unique to each Client.
3.
Development estimation, planning and scheduling;
4.
Program design, coding, testing; Converted COBOL specifications and reviewed COBOL code to determine what
the old system did.
Rebuilt the entire application (some very large code modules – 3000, 2000 modules) onto a
.NET SQL Server platform. Rebuilt the connections with ADO.NET, updated some documentation, and while
discovering bugs in the old system.
Packaged a release for the client and provided immediate fixes if any were
discovered. Used scripts to simulate loading of data during the unit testing, to ensure the product would behave
according to expectations, using tools previously developed for other projects. Served as System Architect /
Business Analyst and team leader on the maintenance and enhancements for the last five years. Conceived and
implemented the new XML / XSLT input feed handling and programmed all of the initial XSLT transformations
personally.
5.
Common library routine identification, design and programming and
6.
User liaison to discuss design issues and respond to testing issues.
7.
Worked on and prepared the Business Case for the replacement of the online national system.
8.
Conducted several feasibility studies on replacement COTS products including Miicrosoft XRM software prototyping
as part of the feasibility.
9.
Assisted with the User Requirements definition for the replacement system and performed initial conceptual
designs.
10. Designed major functional features of the proposed replacement system to empower effective, automated workflow,
table-driven validation and manual process optimization.
04
1
Public Safety and Emergency Preparedness Canada (PSEPC)
Commission for Public Complaints Against the RCMP (CPC)
Case Tracking System (CTS) and Complaints Management System (CMS)
Technical Architect / Developer
Jan 2000 – October 2007 (Part Time) – See also Section 07
Barrie Gray
AMITA Corporation
4
CPC’s CTS (See Section 07 Below) is their mission-critical tracking system that records and reports on all aspects of the
Complaint workload from initial enquiry through to Public Hearing if one is required. It is a Microsoft Access GUI client Data
Project (ADP) – using SQL Server as the back-end database. CTS has been in operation since 2000 and produces all of the
documents required for the full, 8-stage Complaints Processing process. It is operational in nature and the Surrey BC
Complaints Analysts are on-line all day every working day recording and updating data while they are actually on the phone.
The Complaints Management System (CMS) was designed and delivered over the three years 2004 – 2007 to support the
largest investigation ever undertaken by CPC – the Kingsclear Investigation. Several ex-police officers, including the exChief of Detectives for the Ottawa Police and a senior ex-Crown Counsel, aided by CPC staff conducted the investigation.
Mr. Gray designed, implemented and administered the three-server infrastructure acquired for the investigation and the
Police Officers claimed the facilities were “better than what we had as Cops”!
Technical Environment: CTS - Microsoft Access 2002/3/7 Data Project, Visual Basic for Applications, ADO, SQL Server
2000, Transact-SQL, MS Word 2003 (for automated documentation generation); CMS – Windows Server 2003 (3 servers), IIS,
SQL Server 2000, SharePoint Portal Server 2003 (SPS), Windows SharePoint Services (WSS), Coveo Enterprise Search,
AutoStore Image Processing software, Refero (I and II) bar code production and processing, C#.Net. CMASS - Microsoft
Access 2007 Data Project, Visual Basic for Applications, ADO, SQL Server 2000, Transact-SQL.
Roles/Responsibilities:
Mr. Gray was responsible for the technical architecture, feasibility studies, user requirements, design, development and
maintenance of both CTS (See section 07) and CMS and the complementary Complaints Management Analysis Support System
(CMASS). Specific tasks for CMS included:
1.
Mr. Gray was contracted to perform several feasibility studies on Scanning and image processing software, Search
technology and metadata requirements for the Investigation.
The automated document scanning and image
processing pipeline (resulting in OCR’d PDF documents residing in various SharePoint site libraries) selected and
implemented by Mr. Gray was a state-of-the-art facility that produced “better quality on-line images than the
scanned originals from the RCMP”;
2.
User Requirements analysis and production of the detailed user requirements specifications;
3.
Business Process modeling, analysis, redundancy elimination and optimization (Visio);
4.
Database design and implementation on SQL Server 2000 – both systems;
5.
Design and develop the CTS system using the Access Data Project approach, ADO and SQL Server 2000 stored
procedures, triggers, user-defined functions and views. Setup and tested connctions through ADO to ensure database
connectivity and worked with their DBA to access these systems, including performance testing over the 256 Kb line to
Surrey BC where a full 10 concurrent workstation users were supported with acceptable response;
6.
Implement the three-server development and production infrastructure hardware and software and configure and test
the IIS, SharePoint Portals (two) and the SQL Server databases;
05
1
7.
Complete development, system testing and user acceptance testing;
8.
Administer and maintain all components for the duration of the Investigation (3 years).
Public Safety and Emergency Preparedness Canada (PSEPC)
Office of the Correctional Investigator (OCI)
Barrie Gray
AMITA Corporation
5
Data And Tracking Information System (DATIS)
Technical Architect / Business Analyst / Developer
Jan 2005 – Current (2 Months)
OCI’s DATIS is a mission-critical tracking system that the investigators use to record and report on all aspects of their work
with the inmates and institutions they serve. It was originally a Microsoft Access, split client – data database implementation
and made good use of Access replication capabilities to empower laptop, mobile users to continue to use DATIS when on
the road, interviewing in institutions etc. The growing importance of the system to the OCI required that the technology be
upgraded to enterprise capability using SQL Server 2000 and the SQL Server – based Microsoft Data Engine (MSDE) on the
laptops. At the same time, the opportunity was seized to redesign some of the functionality and also the implementation
code. A number of different developers had worked on the old system and this was reflected in the rather cumbersome (in
places) and problematic maintainability of application.
Technical Environment: Microsoft Access 2002/3 Data Project, Visual Basic for Applications, ADO, SQL Server 2000,
Transact-SQL, Microsoft Data Engine, SQL Server 2000 distributed database technology, MS Word 2003 (for documentation).
Roles/Responsibilities:
Mr. Gray was responsible for the technical architecture, requirements, design and development of the enhanced DATIS and also
the implementation of the MSDE laptop replicas. Specific tasks included:
1.
Mr. Gray was contracted to perform the requirements definition, convert and enhance the database and develop the
new GUI using a Microsoft Access Data Project (ADP). The ADP technology is a very powerful, flexible, yet
relatively unknown tool for Rapid Application Development (RAD) using SQL Server 2000 as the database engine
for all data-related processing. The technology choice was made by the Systems support group for the OCI. In
accordance with Mr. Gray’s suggestion, a basic rewrite of the application is being performed, eliminating much
redundant code, streamlining processing and adding the new functionality that was agreed during the requirements
phase of the project.
2.
User Requirements analysis and production of the detailed user requirements specifications.
3.
Investigated and analyzed existing business processes using Microsoft Visio. Recommended optimzations that were
accepted by management;
4.
Complete the database re-design and implementation on SQL Server 2000. Design and develop the MSDE replica
database and the synchronization functionality and code;
5.
Design and develop the new system using the Access Data Project approach, ADO and SQL Server 2000 stored
procedures, triggers, user-defined functions and views. Setup and tested connctions through ADO to ensure database
connectivity and worked with their DBA to access these systems. Wrote stored procedures and built SQL statements
for various reports.
Used Visual Basic for this cleint server based application to develop numerous forms, with
customized toolbars, online help, and building interfaces to their reporting module. Maintained adherence to their VBX
and OCX standards.
6.
Liaise with the User group and provide prototyping JAD Sessions during development to refine and finalise detailed
requirements and functionality. Worked with users from various offices and helped them prioritize their requirements
and differing interests.
Barrie Gray
AMITA Corporation
6
7.
Implement the Publication / Subscription replication and synchronisation model on the Publisher server and in the
subscriber (laptop) environment and
8.
06
1
Complete development, system testing and user acceptance testing,
Canadian Food Inspection Agency (CFIA)
Interim Manual Data Entry System (IMDS)
Technical Architect / Business Analyst / Developer
Jan 2004 – July 2004 (6 Months)
CFIA is implementing a Corporate-wide Performance Management Framework (PMF) across the organisation. The performance
measures and indicators will be evaluated from a number of sources, some manual, some electronic (existing systems). For the
manual-based measures and indicators, CFIA required a cutom-built data entry application. The requirements mandated that the
system be browser-based and a decision was made to use Microsoft ASP.Net as the development platform – the first custombuilt, in-house, .Net application for CFIA. As a ground-breaker application in technological terms, significant emphasis was
placed, not only upon the application design and user interface, but also on the technical programming standards and
architecture.
Mr. Gray was selected as the designer and developer of IMDS because of his knowledge of Performance
Management systems and his expertise with the .Net framework.
Technical Environment: Microsoft .Net framework version 1.1. ASP.NET, ADO.NET, Visual Studio 2003, Visual Basic .Net,
Oracle 8i / 9i, PL/SQL, SQL*Plus, HTML, Total Oracle Administration and Development (TOAD), Erwin SQL (entity diagrams),
MS Word 2003 (for documentation).
Roles/Responsibilities: Mr. Gray was responsible for the technical architecture, requirements, process analysis, design and
development of IMDS. Specific tasks included:
1.
User Requirements analysis and production of the IMDS User Requirements Specification document. This
project-defining task included:
 Liaise and conduct meetings with the different parties involved in entering PMF data, defining the PM
Framework and operationally managing the PMF IMDS system;
 Document and clarify all requirements-related concepts and issues;
 Architect the database design, browser-based user interface and application functionality;
 Develop a “straw-man” proof-of-concept prototype using VB.Net, ASP.Net, ADO.Net and Oracle 8i (CFIA
upgraded to 9i during the project);
 Provide prototype demonstrations and Joint Application Development (JAD) sessions to the user group;
 Document the outcome from each JAD session and clarify any unresolved issues and
 Write the User Requirements Specification for IMDS, present, finalise and obtain acceptance for the
specifications.
2.
Complete the database design and implementation on Oracle 9i. Design and develop the PL/SQL packages for
all database interactions. Built stored procedures, used triggers, and analyzed query requirements for the
various SQL statements that had to be created. Used HTML to customize some web based screens for look
and feel.
Barrie Gray
AMITA Corporation
7
3.
Specified and implemented the technical architecture and coding standards for development, including
bilingualisation technology, state management (web application), user interface standards and application
navigation;
4.
Design and develop the ASP.Net pages:
 Design and develop custom controls for application navigation and data validation;
 Design an approach to dynamic construction at run time of IMDS data entry pages based upon
metadata defining the specifics of the data entry for each performance indicator (every one required unique
data entry content and formatting). A generic, flexible, metadata-driven approach was conceived, tested and
implemented successfully;
 Code and test the individual IMDS pages for data entry, performance indicator metadata maintenance and
user and security administration;
5.
Complete development, system testing and user acceptance testing and
6.
Produce comprehensive technical specifications for subsequent support and maintenance.
Transport Canada
07
1
Crisis Management System (CMS) Enhancements Project
Technical Architect / Developer
December 2003 – March 2004 (4 Months)

The emergency response Situation Centres within Transport Canada use CMS to communicate the latest details of
any emergency situations requiring their involvement. The system is a browser-based web application using Active
Server Pages (ASP), VBScript, JavaScript and an Oracle 8i database.
Technical Environment: Microsoft IIS, Windows 2000, Oracle 9i, PL/SQL, SQL*Plus, ASP, VBSript, JavaScript, HTML, Visual
Studio .Net 2003, VB.Net and ADO.Net.
Roles/Responsibilities:
1.
In the role of Technical Architect and developer, Mr. Gray was responsible for upgrading to Oracle 9i, a number
of functional enhancements were identified. In order to improve responsiveness a new Situation Update
module was required to provide much faster notification of situation changes to each of the Situation Centres
across Canada. The requirements included the need to notify relevant users of important events, even if they
were not using CMS at the time of the notification. Mr. Gray served as the technical architect for the
enhancement project and also developed the Windows Service component in VB.Net that was the most
appropriate response to the immediate notification requirement. He also designed and developed the detailed
changes to the individual ASP portions of the system.
2.
Liaison with users and the AMITA project manager to confirm User Requirements;
3.
Design the architectural changes in detail (primarily the new Windows Service) required;
4.
Liaison with users and the AMITA project manager to confirm and agree the Detailed Design Specifications;
5.
Design and implement the Oracle 9i database changes.
Also worked on optimizing the database which
entailed reviewing the index structures of other co-designers;
Barrie Gray
AMITA Corporation
8
6.
Design, develop and test the VB.Net Windows Service;
7.
Design, develop and test the ASP, VBScript and JavaScript additions and modifications to existing ASP pages.
Designed the connections to other systems and ensured client side code was efficient and properly
implemented. Also used HTML to tailor the appearance of he web based interface.
8.
Assist the AMITA project manager with system testing;
9.
Prepare a complete installation package and installation / upgrade instructions, and
10. Deliver the installation package, install on site and obtain user acceptance.
08
1
Public Safety and Emergency Preparedness Canada (PSEPC)
Ministry Secretariat
Ministerial Opportunities Tracking System (MOTS)
Technical Architect / Business Analyst / Developer
January 2003 – January 2004 (part-time) (12 Months)
The Ministery Secretariat supports the Solicitor General of Canada. One of the problems the Ministerial support staff face on a
regular basis is the issue of optimising the Minister’s time. It is difficult to keep track of the overwhelming information concerning
requests, events, activities that relate to the Departmental portfolio. In order to support the scheduling staff and provide continuity
and information access, MOTS was conceived (by Mr. Gray) as an appropriate solution to the problems described by the support
management and staff.
Technical Environment: Microsoft .Net framework version 1.1. ASP.NET, ADO.NET, Visual Studio 2003, Visual Basic .Net,
Microsoft Visio (entity diagrams), Active Reports .Net, XML, HTML, Javascript, SQL Server 2000, MS Word 2003 (for
documentation).
Roles/Responsibilities:
Mr. Gray was responsible for the technical architecture, user requirements, business analysis, design and development of MOTS.
Specific tasks included:
1.
Was contracted to complete the definition of requirements, investigate Use Cases, process modeling, analysis,
design and development of a browser-based solution and implement the system, including staff training and
appropriate documentation. Conducted detailed User Requirements analysis and production of the MOTS
User Requirements Specification document.
2.
Defined and analyzed use cases and existing business processes. Created a conceptual design addressing
requirements.
3.
Complete the database design and implementation on SQL Server 2000. Design and develop the stored
procedures for all database interactions;
4.
Agree, specify and implement the technical architecture and coding standards for development, including state
managemen, user interface standards and application navigation;
5.
Design and develop the ASP.Net pages:
 Design and develop custom controls for application navigation and data validation;
 Code and test the individual MOTS application pages;
Barrie Gray
AMITA Corporation
9
 Code and test the Active Reports .Net filtered reports;
 Implement full-text indexing and searching capabilities on the MOTS data;
6.
Complete development, system testing and user acceptance testing;
7.
Used HTML for customization of content. Also used dynamic DHTML for some parts.
8.
Developed numerous drop down and pick lists that could be updated from the database using VB.NET for the
front end.
9.
Produce the User Training Manual, course materials and labs;
10. Provide user training to all personnel and
11. Produce comprehensive technical specifications for subsequent support and maintenance.
09
32
Public Safety and Emergency Preparedness Canada (PSEPC)
Commission for Public Complaints Against the RCMP (CPC)
Case Tracking System (CTS)
Technical Architect / Business Analyst / Designer / Developer
September 2001 – March 2002 still Current (part-time and occasional since 2002- support)
(7 Months)
The CPC CTS is another mission-critical case tracking system whose current implementation has been designed and developed
solely by Mr. Gray. The Commission for Public Complaints against the RCMP processes several thousand cases per year and
the CTS is the vehicle for the automatic document generation, case tracking and reporting activities. One of the more
intriguing aspects of CTS is the requirement to handle low-bandwidth multiple concurrency requirements. Most of the Enquiry and
Complaint processing occurs in Surrey, BC, although the database itself, Case Review and Agency management reside in
Ottawa.
Technical Environment: Microsoft Access 2002/3 Data Project, Visual Basic for Applications, ADO, SQL Server 2000, Microsoft
Visio (entity diagrams). Batch Components: Microsoft .Net framework version 1.1. ADO.NET, Visual Studio 2003, Visual Basic
.Net, HTML, MS Word 2003 (for documentation).
Roles/Responsibilities:
Mr. Gray was responsible for the user requirements, business analysis, design and development of the enhanced CTS. Specific
tasks included:
1.
Initially, the communication line was through a 56Kbps connection (limited abilities) which handled all the Internet
access, email and backup processing in addition to the CTS users (10 to 12 concurrent connections from Surrey to
Ottawa). The technical design used a Microsoft Access Data Project, but with no bound forms and all data access
and updating was via ADO code and stored procedures on the SQL Server 2000 database in Ottawa. Restricting
Microsoft Access in this manner, resulted in one, cached client connection per user with minimal (20k) overhead on
the server and minimal network transmission. Despite the limited bandwidth, application performance was quite
acceptable during normal operation. Microsoft Access was restricted purely to the client workstation GUI and
reporting (also using stored procedures and OLE DB / ADO communications).
2.
Two batch components are also included in CTS for regular archiving and document location (Ottawa or BC)
optimisation. These batch components were designed and built by Mr. Gray using Visual Studio 2003 .Net
Barrie Gray
AMITA Corporation
10
(VB.Net). CTS is now highly electronic-document-intensive. In order to ensure optimal efficiency and minimal
network loading, the location of the CTS documents (shared between Ottawa and BC) is critical. An overnight
batch analysis and document relocation ensures optimal efficiency and minimal network impact.
3.
User Requirements analysis and production of the detailed user requirements specifications.
4.
Investigate, model, analyze and specify Use Cases, process models and optimization of processes for the
enhanced system to address requirements.
5.
Complete the database re-design and implementation on SQL Server 2000. There were numerous tables that
were normalized which was needed to be efficient. Built HTML code to provide a presentation layer onto data
being displayed on the web form;
6.
Design and develop the new system using the Access Data Project approach, ADO and SQL Server 2000 stored
procedures, triggers, user-defined functions and views. Setup all connections and checked for performance.
Optimized amount of data coming down the lines to limit bandwidth use while delivering data to the client;
7.
Liaise with the User group and provide prototyping JAD Sessions during development to refine and finalise detailed
functionality;
8.
Design and develop the new document-processing capabilities using a flexible, table-driven design allowing
operational flexibility in document location;
9.
Implement an innovative, document template approach for automatic insertion of case information using
bookmarks. The design allows for template additions on an ongoing basis;
10. Complete development, system testing and user acceptance testing of all modules including the batch sub-
systems for archival management and document location optimization;
11. Produce comprehensive training manual, training materials, user manual and technical specifications;
12. Design and present in-depth user training for data entry users and for supervisory staff;
13. Database conversion and production implementation;
14. Design of a change management system and process and
15. On-going system support and maintenance.
10
43
2
Human Resources Development Canada (HRDC)
Visual Basic 3 to Visual Basic 6 system conversions (3)
Technical Architect / Developer
January 2001 – June 2001 and September 2002 – January 2003 (11 Months)
HRDC operates a number of corporate support systems in their offices across Canada. The original implementation was
Visual Basic 3 and they required the systems to be upgraded to Visual Basic 6. This conversion mandates a transition from
16-bit to 32-bit technology and a considerable amount of rewriting to effect an efficient result. Mainframe connectivity was
also inherent in all systems, accessing the corporate mainframe on-line for existing client data. The Premier Arrive Premier
Servi (PAPS), Corporate Letterbook System (CLS) and CLS Batch Print applications were all converted by Mr. Gray to
Visual Basic 6. Existing 16-bit VBX controls (numerous) had to be converted to the OCX equivalent. Almost all required
complete rewrites to achieve this. All old DAO code was rewritten to use ADO and many queries redesigned to improve
efficiency.
Barrie Gray
AMITA Corporation
11
Technical Environment : Microsoft Visual Basic 3 and 6, Visual Studio 6, ADO, Sheridan, Videosoft VBX / OCX controls, HiEdit programmable word-processor OCX controls, Microsoft Access Jet database engine.
Roles/Responsibilities:
1.
Assisted in the development of the project plan and estimates for the conversion of a key module to their
correspondence systems. Created the technical design, which entailed an assessment of where the older
technology could be replaced with faster and more streamlined processes and technology (32 bit) which
represents nearly a re-write of the system. Had to conduct some preliminary research on the 16-bit to 32-bit
VBX to OCX conversions, to ensure the new OCX’s performed the same tasks in the same way as the older
VBX’s. For the ones that were not the same, had to investigate new OCX’x or rebuild the older custom controls
and VBX’s.
2.
Reviewed, assessed and converted 16-bit to 32-bit API call conversions. Also provided the DAO to ADO
code conversion. Had to have a detailed understanding of how the older VB application behaved and rewrote
under VB 6 a new interface that was well received by the user community. Worked closely with HRDC’s
mainframe experts to setup processes and connections to their Unisys Mainframe and also discovered bugs in
their old processes. Access was the database that was used as the backend and it was also migrated to a
newer version.
11
54
3
3.
System Testing
4.
Provided documentation - Technical Specifications
Department of National Defence (DND)
National Procurement Management System (NPMS)
Business Analyst / Technical Architect / Developer
July 2000 – October 2003 (part-time)
(12 Months)
The Directorate of Corporate Procurement Support (DCPS) in the ADM Materiel, ADM MAT, Branch of DND required a
procurement system to support the forecasting, tracking and reporting on all contracts and purchases over a certain
minimum amount. The ADM IM DIOM group also wanted to participate in this development as they provide the funding for
such system development activities. The National Procurement Management System interfaces to the DND FMAS SAP
financial control system to import all financial transactions from FMAS into NPMS on a weekly basis. The emphasis in NPMS
is on forecasting and activity-based forecasting in particular. The system automatically updates the actuals from the FMAS
import against the forecast allocations and provides detailed and flexible variance reports under a number of different
classification categories. Once operational, the system vastly improved the accuracy and efficiency at which DCPS could
produce regular forecasts for senior management. The ability to “balance” to the dollar with the FMAS actual commitment
and expenditure amounts was a great increase in the accuracy of the forecasting process and summaries provided to
management.
An initial prototype development in Microsoft Access was used as part of the User Requirements determination and as cost
was top priority, a Microsoft Access 2000 solution was selected as the most cost-effective approach for DCPS. Mr. Gray
Barrie Gray
AMITA Corporation
12
was tasked as the architect, business analyst, designer and developer of NPMS and supported the system until fall of 2003
when support was finally assumed by ADM IM internal staff.
Technical Environment: Microsoft Access 2000, Visual Basic for Applications, Data Access Objects (DAO), Erwin SQL,
Microsoft Word 2000 (for documentation).
Roles/Responsibilities:
1.
Project scoping and planning;
2.
User Requirements analysis;
3.
Production, presentation and approval of the User Requirements Specifications;
4.
Business process modeling and optimization;
5.
Liaison with the User Groups from two Branches;
6.
Produce and agree final system designs;
7.
Provide the Design, development and testing. Using Visual Basic, developed a more customized front end to
the application suited for an executive user. Using ERWIN, created the process and data models and
structure for the database. Setup the table structure, normalized the tables, and coded SQL Statements for
reports and built numerous financial and forecasting reports;
8.
Using Visual Basic developed a customized business knowledge management system that used picklists,
messages, workflow with Tabs that would step them through the process for easier navigation in a system that
would be deployed nationally.
9.
User, Training and Technical documentation;
10. Training users;
11. Conversion and Implementation and
12. Post-implementation support for three years
Ottawa Heart Institute
12
Automated Cardiovascular Entry System - Fast Track (ACES FT)
Technical Analyst / Programmer
November 2000 – April 2001 (7 Months)
The University of Ottawa Heart Institute is an academic health-care institution founded in May 1976 and serves as the centre
for cardiovascular care in the Ottawa region. It is an international centre of excellence in cardiac care focusing on prevention,
treatment and rehabilitation of patients with heart disease.
The Heart Institute is undertaking a proof of concept project to determine the feasibility of using pen based handheld devices
to capture Admittance data, CCU Discharge and WARD Discharge information. Once the data is captured, it will be used for
regular hospital duties as well as research. AMITA is currently developing the proof of concept prototype that will be piloted
in 6 hospitals in Canada.
Barrie Gray
AMITA Corporation
13
Technical Environment: Visual Basic 6, Oracle 8i Lite, Oracle 8i, Oracle data replication, Wireless LAN, Hand Held
computers.
Roles/Responsibilities:
1.
Technical program design of the Patient Status tracking and monitoring system;
2.
Design, development and implementation of the Oracle 8i Lite Patient Status database.
This is a large patient
record database that used wireless LAN technology. Used by Nurses, the system had to be designed as a
repository for nurses but also as a data mining source for drug research while protecting privacy;
3.
Provided Visual Basic 6 programming support to the development team in order to meet critical and demanding
development schedules. The system uses a dual-purpose ActiveX DLL and Visual Basic add-in designed and
developed by Mr. Gray, which distills the best practices for application bilingualisation, into one dll and a small VB
code module. The user interface is unique, it runs on a small had held NT based computer deigned for field work,
that captures day-today patient vitals and then uploaded after the nurse has done the rounds. Built a workflow
based set of VB forms linked to Oracle. Also Unit tested the application.
4.
Built statistical reports using stored procedures, wrote SQL statements, wrote reports in excess of 30 reports.
5.
Design and development of a re-usable billingualisation dynamic link library (dll).
6.
System testing.
Department of Heritage
13
54
Business Management System (BMS)
Technical Architect / Business Analyst / Developer
June 1999 – September 2000 (10 Months)
Mr. Gray was asked by the Deputy Minister at the time (Mr. Alex Himelfarb, who became the Clerk of the Privy Council) to
implement the Business Management System (initially designed for DND (see below) and subsequently enhanced and made
more generic by Mr. Gray), at the Department of Heritage, as they had little business planning support and had not started to
comply with the Treasury Board directive to implement a performance management framework within the Department. The
BMS was upsized from Microsoft Access to SQL Server 2000, customized for the Department of Heritage and implemented
by the informatics group as the first organizational unit. Some of the more significant reports were made available on the
Intranet using Cold Fusion and Crystal Reports.
Technical Environment: MS Access 2000, Visual Basic for Applications, SQL Server 2000, Cold Fusion, Crystal Reports
8.0, JavaScript, HTML, Microsoft Visio for Enterprise Architects, Word 2000 (for documentation).
Roles/Responsibilities:
1.
User requirements detailed analysis;
2.
Liaison with various user groups (Finance, Human Resources, Informatics);
3.
Definition of use cases, process modelling (Visio) and process optimization;
4.
Upsizing BMS to SQL Server 2000.
Created the database design, tables structures and links to other
databases;
5.
Used JavaScript to develop client side code, mouse over, flipping of messages with colour coding.
Used
HTML for customization of the interface.
Barrie Gray
AMITA Corporation
14
6.
Customization of the Performance Management module for Heritage requirements;
7.
Customization of the Human Resources Training module to HR needs;
8.
Design and development of Cold Fusion intranet pages using Crystal Reports;
9.
Production of User, Technical and Training Documentation and
10. Implementation of the Performance Management module for the Informatics group.
14
Department of National Defence (DND)
Vice Chief of the Defence Staff (VCDS), Deputy Chief of the Defence Staff (DCDS)
Business Management System (BMS)
76
Business Analyst / Technical Architect / Developer
October 1997 – January 2001 (part-time)
(36 Months)
The Performance Management Database System (PMDS), originally developed for DIOM 2 (see below) was selected by the
VCDS initially (and eventually the DCDS also) to satisfy their performance management needs without any changes. However,
the VCDS required much enhanced forecasting and financial planning functionality to meet their management planning and
control requirements.
Technical Environment: MS Access 2000, Visual Basic for Applications, Visual Basic 4 and 6, Erwin SQL, Microsoft
Access replication and synchronization programming, Microsoft Word 2000 (for documentation).
Roles/Responsibilities:
1.
Liaison with User Groups from VCDS and DCDS; JAD sessions and demonstrations to elicit enhancement
requirements. The PMDS from the DIOM 2 implementation was enhanced considerably, implemented in VCDS and
also enabled for replication as there were multiple offices within VCDS requiring access to BMS and they had
limited connectivity in terms of throughput between them.
2.
The BMS enhancements resulted in a system that incorporated allocation of budget monies down through the
organizational structure (paralleling what happens in the real world), each organization would then allocate
their personnel and funding resources by Activity, and various expenditure codes (fund, vote, line object etc.).
The activity-based plans could then be rolled up and reported on at any organizational granularity. A
comprehensive Training module was designed and constructed allowing for position and candidate skills, skill
searching and matching, training records and reporting. Together with the Performance Management module,
BMS allowed the detailed planning for next year to roll over into monitoring and reporting progress against
the plan for the current year. Developed an intuitive and user-friendly design provided a “drill-down” capability
for the Activity structure, the Organizational structure and the Performance Measures and Indicators structures.
As an achievement BMS was selected by DGISDS (a Corporate planning group) as the model for an initiative
to design and development a Department-wide performance management and planning application.
3.
Conducted the confirmation of detailed User Requirements and BMS enhancements. Developed with Visual
Basic the customized interface, that incorporated an easy to view thermometer style notification of goal
achievement status from the many key point indicator feedback sources.
4.
Barrie Gray
Provided the design, development and testing of the BMS enhancements;
AMITA Corporation
15
5.
Provided the development of replication and synchronization features;
6.
provided Year 2000 compliancy planning and implementation;
7.
Implementation in VCDS and DCDS;
8.
Establishment of operational replication and synchronization “farms”;
9.
On-going operational support for enhancements, occasional conflict resolution and new reporting requirements;
Department of National Defence (DND)
15
87
Directorate of Informatics Operations Management (DIOM)
Business Analyst / Technical Architect / Developer
December 1996 – October 1997 (9 Months)
DIOM 2 (the planning arm of DIOM) required a performance management database for the performance management
framework they were building in response to the Treasury Board directive for all Departments to implement performance
management into their operational activities. They knew they needed a database but had no concept of what it should look
like. Mr. Gray was selected for his skills in requirements analysis and conceptual design to architect a solution from the
users’ business-related requirements. The result was a Performance Management Database System (PMDS) that modeled
the performance management framework that DIOM was building.
Hierarchies of Performance Measures and Indicators were entered against the various organizational units within DIOM.
The system had the ability to facilitate periodic entry of actual metrics for performance against the framework, including
automatic generation of entry schedules, bring forward and reporting on overdue entries and so forth. Much use was made
of the graphical facilities in Microsoft Access for user-friendly graphing of actuals versus targets and standards for the
various measures and indicators concerned. The system automatically assessed performance in terms of red/yellow/green
(and blue for over-achievement) flag icons and enabled drill-down browsing through the hierarchical structures of
organizations, activities, measures and indicators.
Technical Environment: MS Access 2000, Visual Basic for Applications, Visual Basic 4, Erwin SQL, Microsoft Word 2000 (for
documentation).
Roles/Responsibilities:
16
10

User Requirements analysis and specification;

Existing Use Case and Process Modelling, with elimination of redundancies and processes optimized where possible;

Detailed design, development and testing of the performance management module;

Enhancement to include a basic financial planning module;

Development of system utilities in VB6;

Production of User Manual and Technical Specifications;

User Training and system implementation and

On-going support (part-time).
Department of Justice
Applications Portfolio Manager
Barrie Gray
AMITA Corporation
16
Manager / Business Analyst / System Architect
May 1993 – December 1996 (31 Months)
Mr. Gray was contracted by the Department of Justice to serve as one of the two Application Portfolio Managers, responsible
for all corporate applications within the Department. Mr. Gray headed an eight-person team of indeterminate employees and
consultants and was responsible for all Department-wide text-based applications, plus administrative and financial support
systems.
The other portfolio included legal support systems (that were not text-based), most prominently, Case
Management.
Mr. Gray’s achievements during the three and a half years he served as one of the senior managers in the Directorate
included:

The Legal Text Workbench project – first ever CD produced by the Department containing the Statutes and Regulations
of Canada (and other useful text materials) in full text searchable form (Folio Views). This project was proposed for a
GTech award. At the time of project completion (within budget and timeframe), CD burners cost over $7,000; 

Completion and implementation of the LOPORS – Legal Opinions On-line Reporting System;

Interfacing a number of financial support systems to the PWGSC FINCON mainframe financial control system;

Design, development and implementation of a Department-wide Travel Expenditures System (TES) that was emailenabled for authorizations and approvals (something much easier to accomplish nowadays);

Assistance with the Infrastructure upgrading from Novell networks to Windows for WorkGroups 3.11 and Windows
NT servers;

Design, development and implementation of client-server systems on SQL Server 4.21 through 7 for Client
Relations Management (CRM), Commitment Control, Financial Forecasting and Reporting, Question Period
Briefing Notes, Travel Expenditures management and HR Training records, and

Implementation of the first web / intranet-based reporting applications for the embryonic (at the time) intranet portal.
The Legal Text Workbench was a special achievement in that the senior management of the Department recognized the
value provided by the first-ever capability to search the laws of Canada with such speed, flexibility and accuracy that it
implied a huge quantum leap forward for the legal section of the user community (the majority of users in the case of the
Justice Department). Mr. Gray was awarded a commemorative plaque in recognition of his contribution to the project.
Mr. Gray was entirely responsible for assessing the existing state of the OARS (On-line Access to Regulations and Statutes)
as it was initially called when Mr. Gray joined the Department. OARS had been floundering along for 7 years and was mired
in a Unix-based, proprietary product that was completely incompatible with the infrastructure and planned infrastructure for
the Department. Mr. Gray cancelled the existing project, switched the technology choice to Folio Views (at that time the
premier full-text search and retrieval engine) and was able to conclude the project successfully within time and at a
much-reduced budget (from $3.5 million to less than $200,000) in a six-month timeframe.
Mr. Gray performed the requirements analysis, feasibility studies, process optimization (Visio) and even the C language and
Visual Basic 3 programming aspects of the project himself. An innovative menu system was designed and developed by Mr.
Gray in VB3, that sub-classed the Windows desktop itself. The Legal Text Workbench user was able to right-click on any
Barrie Gray
AMITA Corporation
17
portion of the visible Windows desktop and invoke a flexible, user-tailorable menu of Folio Views Infobases for their text
searching needs. This new paradigm was subsequently copied by Microsoft in Windows 95. As Project Manager and
Senior Developer designed, developed and implemented a range of systems. Designed and developed a range of
applications with SQL Server (Corporate database standard) and with Ms Access. Access was used for smaller system but
developed Visual Basic front end interfaces to these applications. Conducted numerous JAD sessions with users to develop
a data model for financial and legal services applications. Used HTML for developing some customized pages for their web
pilot projects along with Javascript for non-server type programming.
Also used Active Server Pages with embedded
script programs for processing on the web server side and then data was driven to the user. Used this as a
common gateway interface with customized page for the user. These pages get access to data on their SQL
Server which then builds or customizes the page dynamically and then sends it to the requestor.
Technical Environment: Microsoft Visual Basic 3 and 4, MS-Access 2 / 97, SQL Server 4.21, 6.0, 6.5 and 7, Folio Views
full-text search engine, Turbo-C++ for Windows, WordPerfect Macro language, Windows NT 3.51, 4
ASP, VBScript,
JavaScript, IIS
Roles/Responsibilities:
1.
Informatics directorate management planning, meetings etc.
2.
Project planning, approval and management
3.
Resource planning and scheduling
4.
Team(s) motivation and morale
5.
Budget management (in excess of $3 million per year)
6.
Resource negotiations and acquisition
7.
Technical architecture
8.
Programming and documentation standards
9.
Code re-usability
10. Lead analyst/programmer on all C and Visual Basic development
11. Team lead on all investigations, requirements analysis, business process modeling (Visio) and optimization;
12. Database design and integration
13. Secure access control
14. Cross platform implementation
15. Mainframe connectivity
16. Intranet & Internet
17. Quality Assurance
18. Data conversion strategies & tools
19. Training plans, documentation, courses
17
Computing Canada
14 Published Articles
Technical Journalist (part-time)
1990 - 2000
Barrie Gray
AMITA Corporation
18
Mr. Gray had 14 different technical articles published in Canada’s premier, national computer magazine, Computing
Canada at various times during the decade of the nineties. The subjects included Object Orientated Programming
(OOP), Windows NT/2000, C++ OOP development and Microsoft Access versions 97 and 2000.
18
Stentor Canada
Application Development and Support
Business Analyst / Technical Architect / Developer
Apr 1985 – Apr 1993
Stentor Canada (originally telecom Canada) was an alliance of all of the Canadian Telecom providers, Bell Canada, Manitoba
Telephone and Telegraph etc. The organisation, based in Ottawa, served to resolve inter-member issues and allocate longdistance revenues appropriately across the individual, constituent companies.
The Phone Power unit within Stentor was
mandated to provide long-distance telephone calling sales and marketing services and consisted of over 25 offices across
Canada. Stentor implemented a large and powerful Digital Equipment of Canada (DEC) VAX / VMS cluster of minicomputers for
their central application development and production operations in 1985. Mr. Gray was contracted (for 8 years) by the Phone
Power unit, as their main application architect and developer of their production applications. One year after Mr. Gray moved to
the Department of Justice, Phone Power ceased to exist as an independent organisation. (There was no causal relationship
between these two events, however.)
Mr. Gray designed and developed a large Sales Tracking And Reporting System (STARS) which included the entry and
recording of all Phone Power sales, the calculation (build up to gross) of sales advances, commission and bonuses for all of the
Phone Power representatives and numerous analysis and reporting facilities. The system was constructed using VAX Datatrieve,
RMS, FMS (forms management) software. A unique, table-driven menu approach was designed and built by Mr. Gray to provide
a re-usable, efficient menuing framework for all application functionality that overcame the lengthy login compilation overhead
normally associated with an interpretive development language such as Datatrieve. This design was so successful it was
adopted by Stentor for several other systems running on the Vax cluster. It was also entered into the DECUS (DEC user group)
tape library and subsequently utilised in several other locations around the world, until the demise of DEC and the VAX
technology in the mid-nineties.
Other applications designed and developed by Mr. Gray during his 8 years at Stentor included:

TAMIS, Telemarketing Application Management Information System for the Telemarketing unit within Phone Power – a
Datatrieve system like STARS;

PPIAS, Phone Power Inventory and Accounting System – a comprehensive finished good inventory and accounting
system with exponentially-smoothed demand forecasting, automatic re-ordering, out-of-stock warnings and notifications
and so forth;

CARS, Compensation and Results System – a Powerhouse and VAX C implementation of a revised compensation and
sales data warehousing application that was required when another consulting organisation developed TRACS
Barrie Gray
AMITA Corporation
19
(Telephone Revenue And Calculation System), the ultimate successor to STARS, that never attained the level of user
acceptance that STARS had received and was eventually discontinued shortly before Stentor ceased to exist.
In addition to the above, Mr, Gray assumed responsibility for the maintenance, enhancement and support of several other
applications developed by other units within Stentor. These systems were VAX COBOL applications using FMS forms
management and DEC’s RDBMS, relational database management product.
Technical Environment: VAX/VMS, VAX C, VAX Datatrieve, VAX COBOL, VAX RMS, VAX RDBMS, VAX FMS, DCL
(Digital Command Language), VAX Allin1 Office Automation.
Roles/Responsibilities:

Business Analyst / Technical Architect / Designer of the innovative menu-driver software coupled with DCL (Digital
Command Language) procedures and a sophisticated system startup program (written in C) that initialized
numerous virtual terminal application instances at boot-time. This approach reduced login compilation delays of
several minutes to just a couple of seconds. It also facilitated the continued use of VAX Datatrieve for all application
development and reporting. Datatrieve was a very powerful, flexible language that shortened development times
dramatically, particularly for reporting, but could also be used (as was the case at Stentor) for housing FMS forms
management software for data entry.
19
21

User requirements determination and specification;

Existing business processes investigation, modeling (Visio) and optimization where possible;

Liaison with various Stentor User Groups in the Phone Power organization;

Design, Development and implementation of the systems described above;

Development of all system, user and technical documentation and

On-going support for system enhancements and problem resolution.
Department of National Defence (DND)
Directorate of Aircraft Engineering Maintenance (DGAEM)
Configuration Status Accounting System (CSA)
Senior Analyst / Technical Architect
August 1983 – June 1985
DGAEM was responsible for the aircraft engineering maintenance and support systems across Canada. They required a
completely new Configuration Status Accounting system for the 150-string, relatively new fleet of CF18 jet fighters Canada had
acquired. The system had to provide recording, tracking and reporting capabilities for all of the hundreds of thousands of parts,
assemblies and sub-assemblies that were incorporated in each of the individual CF18 planes. The paperwork on just one aircraft
would fill a small room from floor to ceiling, so it was critical that the system be designed optimally to handle the large volume of
data and the high volume of transactions that result from the maintenance activities on a fleet of 150 high-tech, ultra-sophisticated
Barrie Gray
AMITA Corporation
20
aircraft on an on-going basis. Mr. Gray served as the Business Analyst and System Architect on the CSA project from its
inception until the completion of system testing in 1985.
The development effort commenced with the production (by Mr. Gray) of four key planning documents, as DND’s SDM 70
methodology had to be followed precisely as dictated by the contract. A large amount of analysis and design time was required
to refine and complete the conceptual designs as the volume of data was significant and the system requirements were complex.
The functional specifications and technical design documents were both several inches thick when produced, as was the system
testing documentation.
Technical Environment: Oracle Forms, SQL-Plus, RPT, VAX DCL.
Roles/Responsibilities:
20
21

Initial project planning and estimation;

Development and approval of the formal Project Management Plan.

Development and approval of the formal System Development Plan.

Development and approval of the formal System Testing Plan.

Development and approval of the formal Project Change Management Plan.

User Requirements analysis and specification;

Investigation and modeling of existing processes (Corel Draw);

Analysis and design of the Oracle CSA database;

Investigations, Analysis, design, production and approval of the formal Feasibility report;

Investigations, Analysis, design, production and approval of the formal Functional Design Specifications;

Analysis, design, production and approval of the formal Technical Design Specifications;

Support to the development team during system construction and program unit testing;

Production of the System Test Cases and Scripts;

System Testing, and

Production and approval of the User Reference Manual and System Technical Specifications documents.
Other Consulting projects between January 1981 and August 1983
Departments of Health and Welfare, Solicitor General and the National Research Council of Canada
Systems Architect / Analyst / Programmer
January 1981 – August 1983
Barrie Gray
AMITA Corporation
21
Mr. Gray carried out a number of consulting contracts for the Department of the Solicitor General, The Department of Health and
Welfare Canada and the National research Council of Canada during the above period after his immigration to Canada from the
United Kingdom. More details on these projects can be provided if required.
Technical Environment:VAX/VMS, VAX C, VAX Datatrieve, VAX COBOL, VAX RMS, VAX RDBMS, VAX FMS, DCL
(Digital Command Language), DEC PDP-11, RSTS/E, Basic, Basic+2, RMS-11, DBASE II, III and IV, Clipper
Projects/Roles/Responsibilities:

Initial Systems Master Plan (LRSP) for the National Research Council Canada (NRC) including conceptual design
of a Divisional MIS. 1984

Long Range System Plan for the Solicitor General Ministry Secretariat, evaluating over 40 systems, designing 13
integrated MIS systems in 1983

User Requirements study for Health Canada Medical Services Branch, conceptually designing an 11-system MIS.
1982

Specific Investigations into one Dental Office, process modeling (Corel Draw) and optimization. This exercise
resulted in Mr. Gray developing a small Basic+ program for the Saskatchewan Dental Office, which eliminated the
need for 5 temporary workers, all of whom spent all day, every day raising payment requests. This program was
adopted by the Branch and implemented (eventually) by the Central EDP group.

Design and implementation of a number of resource control systems for Health Canada and the Department of the
Solicitor General. Aug 1981 – Aug 1983.
21
21
Employment prior to January 1981 (in the United Kingdom)
Digital Equipment Corporation (DEC) United Kingdom
Senior Software Specialist
July 1976 – December 1980
Mr. Gray was recruited by DEC initially to provide technical support to the commercial sales unit. However, he soon moved to the
large computer support (educational product) group and was trained as an internals consultant on the DECSystem-10,
DECSystem-20 and then the VAX minicomputer ranges. He served for three years as DEC’s primary (and only) support
specialist on the 10 and 20 systems covering the Central and Southwest District (a third of the UK). He also served as one of the
first VAX support specialists in the District, assisting in the sale of VAXes to several universities and colleges. During this period,
he provided technical consulting services to universities and technical organisations, including the development of a card reader
device driver to handle non-standard ICL 1900 range, six-bit code punched cards for Trent Polytechnic, the design of a system for
the support of the thermal insulation assembly around the core of four advanced gas-cooled nuclear reactors (AGCRs) and
numerous conversions and benchmarks in the UK and in the USA DEC headquarters for potential DEC customers. In his final
year with Digital (2000), Mr. Gray served as the Sutton Office Sales person for Vax and DECSystem-20 computers in the
educational marketplace.
Barrie Gray
AMITA Corporation
22
Technical Environment: DECSystem-10, DECSystem-20, VAX, Macro-10 (Assembler), Macro-20, VAX Macro, various
languages including Fortran, Cobol, Pascal, Algol 68.
Roles/Responsibilities:

Benchmarks, presentations, demonstrations, installations, performance tuning and training courses on VAX and
DECsystem20 computers.
22
21

Internals level support to VMS, TOPS10 and TOPS20 users.

Consulting and design studies for existing customers.

Sales and account management to VAX and DECsystem10/20 customers in the educational marketplace.
Employment prior to January 1981 (in the United Kingdom)
RM Douglas Construction Limited
Development Manager / Deputy DPM
September 1971 - July 1976
Mr. Gray was employed by RM Douglas Contstruction as a Senior Systems Analyst, but was promoted after 6 months to the
position of Development Manager in charge of a team of 20 analysts, senior analysts and programmers. He served in this role for
over four years before taking his position with Digital Equipment.
Technical Environment: ICL System 4 (IBM 360 clone), COBOL, batch mainframe.
Roles/Responsibilities:

Systems and programming management;

Deputise for the DP Manager in his absence;

Liaison and meetings with Company senior management on directions, initiatives, priorities etc.;

Designed a new task scheduling an progress monitoring system for internal use that improved the efficiency and
productivity of the programming teams considerably;

Designed an operating system enhancement that improved throughput so significantly it was subsequently sold to
existing ICL System 4 customers around the world, achieving over 50% market penetration. Unfortunately, there
were only 70 or so System 4 machines ever sold by ICL.
23
01
Employment prior to September 1971
Barrie Gray
AMITA Corporation
23
Various
Details of Mr. Gray’s employment prior to 1971 can be provided if required. A synopsis of his career after leaving University and
before joining RM Douglas follows:

Senior Systems Analyst for Chrysler UK IBM 360 mainframes, COBOL – Order Processing/Back-Order Processing,
Parts Supply Analysis and Finished Goods Inventory Control, General File Interrogation System; December 1969 –
September 1971

Senior Systems Analyst for Ansells Brewery ICL 1900 Mainframe COBOL – Order Preocessing, Invoicing, Depot
Stock Control, Sales Ledger; August 1968 – December 1969

Systems Analyst for Herbert-BSA Machine Tools Limited – IBM 360 COBOL – Order Processing, Invoicing,
Accounts Payable, Sales Ledger, July 1967 – August 1968 and

Programmer – Programmer/Analyst for Southalls Limited – LEO III – Honeywell, COBOL – Invoicing, Sales
Analysis, Materials requirement Planning, Production Control / Shop Loading, Finished Goods Inventory Control.
June 1965 – July 1967
Barrie Gray
AMITA Corporation
24
24
01
IT SKILLS
Computer Hardware
Operating System
8086/8087/8088/80x86
DEC VAX 6200/6400/8700/8650/785
DEC VAX 11/785/780/750
DEC MicroVAX 3000 series and μVAX II
DECsystem20
IBM 360/370/3090
ALTOS & Intel
Windows 3.x, WFW 3.11, Win 95/98, XP, 7, 8
Windows NT 3.x, 4.0, Server 2000, 2005, 2008 R2
VAX/VMS (cluster v 5.0+)
VAX/VMS (1.7 through 5.4-1)
MicroVMS
TOPS20
OS MFTII / VM/MVS / DOS
UNIX / LINUX
Languages
Packaged Software
C#.Net, VB.NET, ASP.NET, Web Parts
Visual Basic 3.0, 4.0, 5.0 and 6.0
Oracle/IAF/IAG/PL-SQL/SQL+/RPT/SQL*FORMS
Microsoft Access 1.1, 2.0, 7.0, 8.0, 9.0, 97, 2002, 2003, 2007/10
Cold Fusion, Java script, Java, HTML, XML
C (Microsoft C/C++/C#.Net, Turbo C, VAX C)
Microsoft Transact-SQL, ORACLE PL/SQL, Gupta SQLBase
SQLWINDOWS (GUPTA)
COBOL (VAX and Mainframe – IBM, ICL)
Powerhouse (Cognos)
ALLIN1 Scripts/FMS named data
Datatrieve
Fortran
Pascal
DCL
Macro-32 Assembler
8086/80286/6502 Assembler
.NET Framework, VS.NET, ASP.NET, ADO.NET
SharePoint Server 2003, 2007, 2010, 2013, xRM
SQL Server 4.21a, 6.0, 6.5, 7.0, 2000/5/8, ORACLE 8i, 9i
Adobe Photoshop, ImageReady, Netscape Composer
Enterprise Architect, Cold Fusion Server, Homesite 4.x
Starbase (Interbase)
RDB/VMS
SQLBase
CICS/DB2
POWERHOUSE
ALLIN1
Datatrieve
DBMS-20
SPM (VAX performance monitor)
FMS
RMS-32
SAS
SPSS
PC software, all sorts - MS Office 4.3, 97, 2000/3/7/10,
Adobe Photoshop, ImageReady, Netscape
Composer, Homesite, Cold Fusion Studio,
Robohelp, Enterprise Architect (EA), Rational
Rose Business Process Modelling, ERWIN SQL
diagramming, Visual Modeller Component
Design, Excelerator, LBMS, VISIO, MS Project,
Artemis, Wordperfect, Lotus, xBASE languages,
Communications packages, utilities etc.
25
01
Education:
Bachelor of Science, Mathematics and Statistics, University of Birmingham, 1965
26
01
Public School:
King Edwards, Birmingham, 8 O-Levels, 3 Advanced Levels, 2 Scholarship
27
01
Professional Development
Levels – State Scholarship
Member of the British Computer Society (M.B.C.S.), 1968
Numerous self-paced courses on various Microsoft technologies including VS.Net, C#, VB.Net, XML, XPATH, XSLT, Visual Basic,
SQL Server database administration, ORACLE database design and development, PowerPlay and Impromptu user and
Barrie Gray
AMITA Corporation
25
administration, SQLWINDOWS application development (client-server, Windows 3.x 4GL), SQLBASE Database Administration,
Infotext relational database programming, VAX user/operator/system manager, VAX programming, VAX Nucleus, DECsystem20 new
hire, DECsystem20 internals, DEC sales training, NCC systems analysis, basic O&M, project management, programming
management, database concepts, computer communications, PERT, structured systems analysis, PROVAC project management,
Assembler programming, COBOL programming, program planning.
28
01
Security Clearance
Mr. Gray and the Midland Microcomputers Limited facility are both cleared to SECRET through Public Works and
Government Services Canada (PWGSC). Mr. Gray also was cleared to Top Secret through a Canadian security
agency (PS) until 2012 and is currently cleared to Top Secret with PWGSC.
Barrie Gray
AMITA Corporation
26