SeaPort Enhanced (SeaPort-e)

Quality qualifications for Agile Communications, Inc. in support of the SeaPort-e Contract

At Agile Communications, Inc., quality is an established core value that guides everything we do.  Our success and continued success depends on achieving quality throughout the lifecycle of our efforts.  Our Quality process is tailored to the needs of each customer and program, and within each program to deliverables.

The quality of our deliverables is ensured by the constant reviews by multiple experts in applicable areas including management, technical, and cost.  The Program Manager on every program tracks the current technical status to the deliverables and performs the bi-weekly review.  A problem will be treated as a task and tracked and reviewed.  Quality is measured by the match (or miss-match) of the current status to the deliverable and the variance is identified and resolved.  Depending on the needs several individuals take on their quality role to ensure their goals are implemented.  Our Program Manager follows quality standards directly on the program.  The CFO will ensure that the resources match the quality needs as necessary.  The VP for Technology will be the most involved in identifying and resolving quality challenges.  Senior management, Agile’s President, will ensure that all actions are quick and responsive.

As a small company with an excellent reputation for quality delivery for over 14 years, we will not tolerate sub-par quality.  If sub-par quality is identified, it will be defined as a task to resolve with a schedule and senior management oversight.  That task will be analyzed for a cost effective solution.  Our open management process requires that we immediately bring our customer up to speed on our resolution and management of the quality.  We then incorporate any customer direction into our management of the task.

On a recent JUONS task, we were delivered sub-par software to incorporate into our delivery to theater.  We resolved the issue by first reviewing the program requirements and objectives and determining whether the software could be re-written or reused in a modular design.  With our modular design approach and plans for technology insertion, we were able to remove the sub-par software and efficiently integrate several legacy software components working in a distributed fashion.  With the legacy interfaces abstracted away and by using a common, open protocol (IRON Symphony) for communication, individual software components were architected as standalone, reusable modules consistent with modular open system requirements. This allowed for minimal dependencies and rapid integration with future systems and delivery ahead of schedule.