SPECIAL NOTICE
99 -- Request for Information - Interactive Electronic Technical Manual
- Notice Date
- 1/7/2002
- Notice Type
- Special Notice
- Contracting Office
- Department of the Navy, Naval Air Systems Command, Naval Air Warfare Center Aircraft Division Pax River, Building 2272 Suite 353 47123 Buse Road, Patuxent River, MD, 20670
- ZIP Code
- 20670
- Solicitation Number
- Reference-Number-251612IETMS
- Response Due
- 1/17/2002
- Archive Date
- 2/1/2002
- Point of Contact
- Jessica Nelson, Contract Specialist, Phone (301) 757-2527, Fax 301-757-2526, - Gregory Blew, Contracting Officer/Team Lead, Phone (301) 757-9058, Fax 301-757-9046,
- E-Mail Address
-
nelsonjl@navair.navy.mil, blewgt@navair.navy.mil
- Description
- 5600 331200N/rwf/ 07 Jan 2002 From: Contracts, AIR-2.5.1.6, Naval Air System Command Subj.: STANDARD NAVAL AVIATION TECHNICAL MANUAL PRESENTATION SYSTEM (SNPS), FUNCTIONAL REQUIREMENTS DOCUMENT (FRD); REQUEST FOR INDUSTRY AND DEPARTMENT OF DEFENSE (DOD) SERVICES REVIEW, COMMENT AND RECOMENDATIONS ON: Encl. (a) SNPS Functional Requirements Document dtd 21 Dec 2001- rev. 04 Jan 02 1. NAVAIRSYSCOM, AIR-3.0, Technical Data respectfully requests your participation in an informal review of Enclosure (a). 2. Scope. To provide an open forum, through which Industry and DOD Services may provide general comments and recommendation to the SNPS Draft FRD, which lists a set of functional attributes that should and/or may be present in an electronic technical manual standard presentation system. Your participation is very much appreciated and valued as this needed standard system and its specific requirements are formalized. 3. Background. Acquisition Reform has led weapon system managers to utilize different and often unique Interactive Electronic Technical Manual (IETM) and their accompanying unique IETM presentation system. While individual presentation systems may optimize the return to a specific program, these solutions are burdening the overall Fleet user environment with additional training and equipment requirements. A recent NAVAIR, 3.0 review of the differing IETM presentation systems has resulted in tasking to establish the requirements for a standard presentation system across Naval Aviation. 4. SNPS Goal. The overall interoperability goal is the ability to view all IETM data via a standard, web-enabled IETM presentation system. The DOD requires that all information systems comply with the Defense Information Infrastructure (DII), Common Operating Environment (COE). Additionally, the Navy is transitioning to the Navy/ Marine Corps Intranet (NMCI) and the Fleet web portal as defined in Task Force Web (TFW). The standard presentation system procured in this acquisition must successfully interface in this environment. 5. Cost analysis, pricing information, or proprietary technological information will NOT be accepted by the Government as part of this informal review. All comments received will be made available to the public and considered for possible incorporation in any resultant request for proposal (RFP). 6. Please submit one copy of your written response, on or before 17 January 2002 to Commanding Officer, NAVAIR, Code: AIR 251612, Attn: Ms. Jessica Nelson, Bldg. 515, 47227 Whalen Road, Patuxent River, MD 20670. E-mail: NelsonJL@navair.navy.mil. Electronic responses will be accepted. Enclosure 1 Functional Requirements Document (FRD) December 21, 2001 PROGRAM TITLE: Standard Naval Aviation Technical Manual Presentation System (SNPS) OBJECTIVE: To facilitate the early exchange of information between industry and NAVAIRSYSCOM in the development of a comprehensive suite of requirements, addressing both their functionality and definitions. 1. Definitions of Functionality Requirements: Table 1 provides an itemized set of definitions. Functional Requirements although listed separately, may be mutually exclusive. Respondents should address the functionality of each requirement separately. Rational in grouping requirements may be addressed, when felt appropriate. 2. General Elements: Respondents are requested to address the following additional general elements, which are not contained within Table 1: a. Ability to transport/offer fully portable data within known commercial web browsers b. Authoring system independent c. Ability to pass NMCI test events and operate in Navy/Marine Corps Intranet (NMCI) and Information Technology 21 (IT-21) environments d. Task Force Web compliance e. Ability to import data from multiple authored sources with interface documentation. f. Ability to complete applicable technical evaluation events by Subject Matter Experts (SME) to determine NAVAIR acceptability. g. Proposed ability to access data repositories to retrieve sharable objects for technical manuals and training courseware. Additionally the respondents may offer rational for offering alternatives or modifications to specific requirements. Each individual response, as either an omission or deviation, should address: (1). Best value analysis discussion points. (2). Expected utility of replacement/alternate functionality to the end user. (3). Proposed use of any Custom file extensions 3. Requirements Listing: See Table 1 on the following pages of this enclosure (i.e. pages 2-6). Table 1 Functional Requirements - NAVIGATION 1. Access by Model Series A feature that narrows the information presented appropriate to the end item maintenance. 2. History of Traversed Links A navigational feature that tracks and lists each node (link) a user sees along the navigational path through a document. In many cases the reader has the ability to bring the list up and use each node in the history list as a hyperlink back to a point in the path. This feature is useful when flipping back and forth between several data types or components of the unit under maintenance. 3. Key Word Search A navigational feature that allows the user to search a document for occurrences of a specific word associated with the document or data set. 4. Logical Next and Back A navigational function that takes the user through a part of the document in a sequential manner, both forward and backward. 5. System/Subsystem Navigation A navigational feature where a default navigational path follows the top-down breakdown structure of the end item. The path allows a user to begin at the system or end item level and follow a physical or functional breakdown to the next lower assembly and then to the next lower assembly from and single pane. 6. User creation of bookmarks A navigational feature that allows the user to flag certain nodes for later access. In essence it allows the user to build their own index of hyperlinks to specific nodes in the document. 7. Full Text Search A navigational feature that allows the user to search for words or phrases regardless of association to the document or subject. Searches are not limited to keywords, but are open to any textual element in the search domain using natural language across multiply files. 8. Access by Tail Number Self-Explanatory 9. Dialog-driven interaction A navigational feature that allows the user to directly feed information to the IETM environment. The IETM would cue the user to input specific data. The feature implies that at some point the IETM would then respond to the information entered. 10. Access by Modification This filter keys on the modification rather than the end item being modified. A user would enter specific modification tracking numbers and have the data unique to that modification presented. 11. User-Defined Boolean Searches A search feature that allows the reader to use logical association of terms to narrow the results of the search. Examples of commonly supported logic include instances of both x and y appear (Logical OR), instances where neither x nor y appear (Logical NOR), and instances where only x or only y appear (Logical EXCLUSIVE OR). 12. Viewer Navigation Pane Requirement A: as a minimum, the navigation pane shall include tabs to rapidly access the following data, Emergency Procedures, TOC, LOT, LOF. Requirement B: The navigation pane must have the ability to be hidden or minimized with a single mouse click or key stroke. 13. Search across Multiple Files Requirement A: Stand alone - Searches across resident files and databases and includes Boolean searches on the client device. Requirement B: Connected Mode - when connected to a server the ability to search multiple files and database on the client and the server device with a single search. Table 1 (Cont.) 14. Access by Configuration A feature that narrows down the information presented to the user to that associated with a specific configuration of the end item in questions. 15. Search across multiple databases/files A search feature that allows the user to look for Key Words or Full Text instances in several different documents 16. Voice-Activated Commands Self-Explanatory Functional Requirements - BASIC LINKING 17. Front Matter - All TOC Front matter is considered to be all the information previously displayed on the title page, (issue number, distribution data, date of issue etc.). A page (change information), verification status page (procedural data), export control notices, warning page, safety summary page and the normal table of contents information (paragraph, page number, etc.). 18. Link to Separate Parts Data Linkage from a maintenance task or narrative may be provided to a separate parts display (illustrated parts breakdown/catalog) in the current or separate window. 19. Figures Tables and Photos A feature to simplify a navigator 's access to the information contained within the data that is presented in a graphic (figure), table (spreadsheet) or captured photo format without regard to the associated textual references. 20. Warning, Cautions and Notes These elements must be readily identified and may require specific operator acknowledgment prior to proceeding with the data being presented. When multiple steps are involved, an icon should identify the condition being highlighted and the data should be readily available for review by activation of the icon. 21. Special Content Internal linking that may generate additional content such as acronyms to the definition, etc. 22. Internal Referencing Capability Internal cross-references via hotspots, ICONS, and, hyper links to related data that can be accessed from any one of the presentations by some manual intervention (normally a mouse click) by the operator. 23. Launching External Processes The ability to launch external processes by some manual intervention (normally a mouse click) by the operator. 24. External Referencing Capability External cross-references via hotspots, ICONS, and, hyper links to related data that can be accessed from any one of the presentations by some manual intervention (normally a mouse click) by the operator. Functional Requirements - UPDATES 25. Full Revision Viewer shall support ability to indicate updates and ability to link from list of changes to the changed data. 26. Block Cycle w/Rapid Action Changes Block cycle update means that changes from all sources are consolidated and issued at regularly scheduled intervals. Table 1 (Cont.) 27. Changes Changes may or may not be discrete and must be identified to the operator so that what's different is easily conveyed. Changes may be displayed as passive or active; passive is a summary of change data and active is displayed in context. Changes can be identified at the step, task, or chapter level. 28. On Demand/Near Real Time From a computer standpoint on demand/near real time means when I push the button the requested data appears. Functional Requirements - GRAPHICS 29. Pan, Zoom, Expand, Magnify Controls are provided to perform pan, zoom, expand and magnify on graphic elements. 30. Simultaneous Text/Graphics Display Self-Explanatory 31. Redlining The viewer shall provide the capability to make notes or annotations within the instance (free-hand type) and save this data to a separate file. Annotations will NOT be saved into the T.M. 32. Hotspotting Graphics that are enabled with hyperlinks. These can be at various levels and include both raster and vector based graphics. Hot spotting examples include links to detail breakouts, next higher assemblies, parts ordering information, parts breakdown data, and procedures from logic trees. 33. Pictorial Index Selection of the appropriate data through point and click graphical representations of the weapon system. 34. Logos Logos are used to indicate the presence of in-line graphics. When the cursor is paused over the logo, a thumbnail view of the graphic appears. Upon double clicking the logo, a full graphic view is launched. 35. Wire Tracing The capability to select wires in a diagram and have continuity highlighted through the circuit. Additional functionality can include circuit simulation (toggling switches, breakers, et al) for passive and active circuitry. 36. System Simulation Capabilities can include identifying continuity in wiring diagrams and circuit simulation for passive and active circuits including activating switches applying power, etc. These capabilities can also be used to model hydraulic, fuel, mission planning, pneumatic and other systems. 37. Assembly/Disassembly Graphical figures that can be used to allow virtual assembly, disassembly, removal, and installation of parts of the weapon system. These can be implemented through linked drawings or through manipulation of modeled vector graphics. 38. Walkthrough/Flythrough (3D Presentation) Solid object graphical figures that can be used to allow virtual assembly, disassembly, removal, and installation of parts of the weapon system. Levels of capability may include fly through type viewing. Functional Requirements DIAGNOSTICS 39. Independent Diagnostic System This requires integration with an external diagnostics engine. Table 1 (Cont.) 40. Interfaced with the System This capability assumes that the IETM extracts data from another media An example would include the use of computerized fault reporting within the IETM 41. Embedded In the IETM Self-Explanatory 42. Integrated with the System This requires integration with an external diagnostics engine. Functional Requirements PRINT 43. Print Screen When data is displayed on a portable or stationary device, the print screen capability will provide a print of only the screen currently being viewed by the maintainer. 44. Time/Date Stamp The printed IETM data would require a Time and date stamp and a Destruction Date displayed on the printer output 45. Task/Node Specific This capability to print more than a screen print is limited to a task or node. 46. Book Version/Fully Formatted This capability provides a document printout that conforms to a specifically called out Document Type Definition (DTD). ADDITIONAL FUNCTIONS 47. Audit Trail This functionality provides the capability to capture the navigation trail the maintainer used to perform a maintenance task. 48. Deficiency Reporting Provides a method for users to document errors and recommended changes to the IETMs. Different complexity considerations include improvement reporting tracking, local base collection and management of improvement reporting and user access to recommended improvements concurrent with viewing IETMs. 49. User Training User training complexity can range from on-line access during IETM run time to linking to a CBT database to run complete training lessons. Capability includes integrating or linking maintenance and/or operational training on the use of the weapon system with the IETM. Access of the data can be through a link to an external module or integrated with the IETM work package 50. Maintenance Data Collection This function provides the capabilities to identify the maintenance task, select the IETM task to perform, collect the parts data required to query and order the parts, collect parts data for configuration management, and update training jackets. 51. Operator Debriefing Includes interface with pilot and or maintenance debriefing system for selecting task assignments. 52. Supply Querying Query of the on-base supply system to check the availability of a replacement part needed to complete an action. 53. External Data/ Database Access This requires integration with an external search engine. 54. Parts Ordering This functionality is integrated with the parts catalogue. Linkage is to enable parts ordering from selection from parts catalog function. These links would not circumvent the supply system Table 1 (Cont.) 55. Context Sensitive Help Help information is available to the user based on the data being presented or the tasks being performed. Help data can be classified as IETM (how to use the IETM) or weapon system specific (what is happening during a specific testing procedure). 56. Audio Presentation standards must be addressed as well as content, duration and context of the audio. Consideration must be given to the anticipated environment to determine the usability of audio. 57. Motion Video Motion video can be used, primarily for demonstration of a unique procedure. Presentation standards must be addressed as well as content, duration and context of the video. 58. Animation Animation can be included to show a variety of system functions from theory of operation (hydraulic flow) to maintenance procedures (how to access a specific part). Presentation standards must be addressed as well as content, duration and context of the animation. 60. Local Data Supplement This functionality provides the maintainer (end user) with the capability to append locally developed data (i.e. local inspections). This locally developed data shall be limited in scope and required to be approved by the end user's Quality Assurance group and be made available to the IETM developer. 61. Training/Security Access This capability provides the IETM with the individual maintainer's training (skill level) and security level assignments. This requires the IETM database to either contain or have access to individual maintainer's training jacket and personnel information. ---------------------------------------------------------------- Note - for a more legible format of this RFI, please contact the Point of Contact (listed herein) to receive a facsimile copy of this request in formatted text.
- Place of Performance
- Address: TBD
- Record
- SN20020109/00012240-020108092535 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(will not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |