Home > FPGA Design Services > Solutions > Architecture and Specification Plan ™

BLT’s Architecture, Specification and Plan ™

BLT’s exclusive Architecture, Specification and Plan ™ (ASP) results in a project plan identifying each major effort and critical path for your design. The ASP process reduces overall cost and shortens the schedule by identifying areas of potential risk and employing risk mitigation and avoidance strategies early in the project. The BLT ASP forms the foundation for projects and ensures predictable success.

We offer the Architecture, Specification and Plan ™ (ASP) as an independent solution, or as the first phase of your design, depending on how you choose to engage with BLT.

Contact us to discuss your ASP. 

About the ASP

Addressing the business needs ahead of any technical involvement is a fundamental aspect of the BLT process. The ASP Process is not intended to develop specific hardware or software engineering deliverables (device pinouts), design elements (circuit designs) or algorithms (software). Nor can an ASP guarantee device resource utilization or performance. The ASP is a highly probable estimate. These development tasks and determinations follow an ASP.


  • ASP tasks require our Client’s inputs more than any aspect of BLT’s involvement
  • The ASP steps completed are a function of the ASP budget, schedule, and scope of the project. Not all steps are completed for all projects.

Relationships matter.

As trusted partners and fellow engineers, your success is our success.

The ASP Process

Below is what you can expect BLT to accomplish during the “typical” ASP Phase.

Reverse Engineering

  • Review all specifications, block diagrams, and documents
  • Examine, dissect, and (where possible) identify components on sample units
  • Evaluate all possible ways to gain information relating to the existing design
  • Evaluate means to penetrate secure designs

Preliminary Design

Solidify specification enough to get started without wasted efforts.

  • Review specifications, block diagrams, and related development documents
  • Review compliance test procedures to verify specification coverage
  • Create initial top-level FPGA/SoC, Product, and/or System Architecture(s)
  • Identify and review specifications for key devices and system components
  • Identify critical mechanical dimensions, potential noise issues, data path, clock and pin-out requirements
  • We recognize the paramount importance of speed in today’s competitive landscape. Our streamlined processes and extensive FPGA design experience mean you can expedite your product’s time to market.


  • Identify critical design areas that could affect design performance or device density
  • Identify & investigate use of IP cores that may improve performance, reduce development time, and/or reduce cost


  • Determine simulation strategy and tools & define the verification environment
  • Flesh out verification plan including availability of required and desired simulation models
  • Utilize marketing compliance and final test procedures to cross-check the specifications.

ASP Non-Technical Tasks

  • Identify overall areas of risk and offer mitigation plans
  • Establish project priorities, interim deliverables, schedule, and component cost goals
  • Manpower planning and task delegation within BLT and within the Client’s company
  • Identify documentation requirements

Potential ASP Phase Deliverables

  • Project development plan including an outline of a project appropriate verification plan
  • Specification document, including:
    • Project specification including requisite peripheral specifications
    • Top-level architecture
  • Proposal for the completion of the project, including
    • Summary statement of work to implement and deliver the design
    • Resolution on outstanding specification issues (if any)
    • Detailed design, implementation, & verification efforts
    • Detailed list of deliverables and an overall schedule
    • ROM project cost & suggested payment milestones

The ASP Process as an Independent, First Effort

Segregating the ASP process can make sense for several reasons. Examples of projects where we would recommend the ASP as a first effort:

  • projects that span more than a few months
  • projects where specifications are non-existent, incomplete, non-standard, complex, or evolving
  • migration efforts from one device to another (example: when a part is discontinued)
  • where the project’s scope, schedule and budget need to be fully understood and agreed upon prior to the more lengthy and costly design, implementation, and simulation phases
  • to lowers everyone’s financial risk and facilitate a lower cost fixed price proposal

What Are You Waiting For?

Connect with BLT today to discuss your Architecture, Specification and Plan ™. See how we can save time and money on your design project with this initial effort.