Date: Fri, 21 Sep 2001 10:21:54 -0400 From: Kenneth Jezek Subject: Re: [Fwd: request for review of APRIME document] Here are some comments on A-Prime pretty much written as I read (so no deep thoughts!) "A-PRIME will not include the downlink of data at the ASF Receiving Ground Station, but will indicate the intended functionality within A-PRIME that supports the ingest of data from the RGS." This presumes that post acquisition handling is where the future ASF effort will be. That may well be true. It may also be true that distributed processing and archiving is the future in which case RGS may be a prime asset and the necessary focus for upgrades. "Data ingest will be highly asynchronous and require a great deal of design modularity. As ASF takes on additional missions and a more diverse customer base, the demands on this element will grow enormously." The goal is to take on more missions. Which missions are targeted over the next 5 years (I noticed ECHO later in the document)? First figure. I did not see a connection from the RGS back from the DMS. How will mission planning activities be handled? Where are the links for recieving acquisition scheduling information from the flight agencies? Is there a connection to MGS or is that abandoned. "Relative to present ASF order handling, A-PRIME will emphasize automation and consolidation of the order processes for the multiple product types hosted at ASF." Automation is a good idea. I note that we have been talking about automated systems since the beginnings of ASF. Without some sense of which presently manual processes will be automated, it is not possible to judge whether the goal is achievable. (Reading later, I did note the items on order handling and processing flow - these seem like good ideas but it would be useful to understand the specific contrasts with the current system) "Enhanced functionality from the present system, in the way of payment methods, will provide order capability to a broader customer community, increasing ASF's customer reach. " It is a brave new world but somehow I don't think that payment method options will much increase the customer community (visa or mastercard?) "ASF will operate nominally the same as it does now in terms of media support, but it will strive to accommodate service levels for electronic delivery exceeding those at present. " That sounds good but what are the numbers on the planned loads, the expected communications bandwidths etc and are these likely to be available to ASF. "What follows is a high-level outline of what "types" of data A-PRIME will manage and the context in which they will be used." At least as desribed here, the DMS looks alot like what ASF is supposed to be now. I know there have been some problems integrating the silo but people have made good progress on that. "The archive storage architecture will be centered around a StorageTek Powderhorn silo. " Isn't this in effect the situation today? What is native Level Zero format? Shouldn't the format be some approximation of a a CEOS standard? (Not that CEOS seems to be much of a standard!) "In a nutshell, EM essentially establishes the entire mechanism of planning, communicating, control, and continuous improvement with a focus on value creation in an organization." In my opinion, a mechanism can provide the information for planning communicating etc. "3.2.2 Planning Customer Acquisition Request" It is not clear how this procedure is different from the current procedure. I assume the implication is that there will be more automation - but specifics would be helpful and especially in contrast to the current arrangement. "ASF to extend its EDG support to the browse capability. " "Additionally, A-PRIME will enhance searches for Level Zero data with interferometric applications in mind. " Clearly valuable additions. "Upon acceptance of any data order, ASF will present the customer, depending on the service level, with a "no later than date" for data delivery. " Definitely important. "3.2.5 Management Insight Into Key Performance Indicators" There must be a performance indicator on the RGS. We know from experience that RGS problems can go undetected until the data are either scanned or processed to Level 0 and the results compared with expectations. "Customer Relations" Seem like reasonable ideas. "3.2.8 Performing Quality Assurance" I realize this is a draft but it is a bit jarring to see that the first item on Quality Assurance is Business Process Modeling. Is a widget the same thing as a GUI? Maybe I missed these things in a fast read but I did not see any personnel plan. By this I mean how will asf obtain and maintain critical technical expertise (it would also be useful to understand this plans staffing requirements and staffing capabilities). I also did not see a plan for processor technologies. Will this be all on subcontracts? Is there a connection to UAF? I know that one has been difficult to create but without one, you abandon a significant early driver for ASF in Fairbanks. I got more impressed with the document as I read it. It seems like a good business vision and I do think that after 20 years it is useful to rethink how ASF does business. In parallel there must be an assessment of user needs and expectations. (I did not see a market analysis for example). Originally we said that ASF should: extend the reach of SAR data over the arctic for polar oceanography studies; be established within an academic research environment. Is that still the driver, if not what is it and who will pay? Ken