SOLICITATION NOTICE
70 -- Command Portal Calendar
- Notice Date
- 2/24/2009
- Notice Type
- Modification/Amendment
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Department of the Air Force, Air Force Space Command, 21CONS (Bldg 350), Specialized Flight-IT, O&M, Tech Serv, IT Resources, 135 E ENT Ave STE 1055, Peterson AFB, Colorado, 80914-1385
- ZIP Code
- 80914-1385
- Solicitation Number
- FA2517-09-T-6038
- Archive Date
- 3/12/2009
- Point of Contact
- Susan K Davis,, Phone: 719-556-7585
- E-Mail Address
-
susan.davis@peterson.af.mil
- Small Business Set-Aside
- N/A
- Description
- The purpose of this amendment/modification is to respond to contractors' questions. Calendar Functionality/User Interface 1. RFI Statement: CPC shall be a web part versus a standalone software application with web interface Question: The phrase "web part" might be a typo. We understand that you want a data base system behind a web site which will be accessed by COTS web browsers without the need to install software on client computers. Please correct our understanding if required. Answer: CPC shall be a SharePoint Web Part. 2. RFI Statement: CPC shall be compatible with Microsoft Office 2003 and 2007, Internet Explorer 2007, SharePoint Server 2003 and Microsoft Share Point Server 2007 Question: Please define how you want the CPC to be compatible with MS/Office and SharePoint Server. Answer: CPC shall be initially compatible with Microsoft SharePoint Portal Server 2003 and maintain compatibility after migration to Microsoft SharePoint Server 2007. 3. RFI Statement: Events shall be displayed and color-coded as shown in attachment 1 Question: Is the color coding to correspond to event types listed in your item 4? Answer: Yes 4. RFI Statement: CPC shall have a comment field with a maximum of 1000 characters Question: We expect that there are numerous other fields that will be needed. For example a title, date, start time, end time, item control information (such as creator ID, creation date, time, edit history). Later you reference a priority field that is needed. Later still you reference directorates implying that each event will or may have a directorate field. In 10 you reference the need for a hyperlink field. For each of these fields, we need to know your requirements more fully, for example, if there are more fields, how many of each field will be needed (for example, how many hyperlinks per record), if the fields are numeric or alpha, if you have preferences for color coding, or other limitations you need. Typically records should have a version number field so that system updates can respect old event record formats and handle them appropriately. Answer: Our intention is to find out what is available COTS with minimal customization. 5. RFI Statements: Users shall be able to access and modify the calendar simultaneously CPC shall allow only certain users to have read-only access CPC shall allow select users the ability to add, modify and delete data Question: We expect that this would be addressed with a user name and password access control system. Is this your intention? Answer: Our intention is to use SharePoint/Active Directory permissions. 6. RFI Statement: CPC shall be able to hyperlink documents to calendar entries Question: Is it correct that the documents the hyperlinks point to will be stored outside of the CPC (for example, external web sites or documents stored on your systems in other locations)? Should the CPC do any verification of the entered links? Answer: Yes, the documents will be stored in SharePoint Document Libraries or on Hard Drives. Link verification is not a requirement. 7. RFI Statement: CPC shall have a monthly and weekly calendar view Question: It would be to your benefit to provide sketches of the different views (or screens) that you need. While we're capable of creating these ourselves you'll likely find additional critical requirements by taking a few hours to produce sample screen formats. This should include the Briefing Displays you discuss later. Answer: Again, our intention is to see what is available COTS. 8. RFI Statement: CPC shall ensure all events are archived in a database for future retrieval Question: Do you have a particular archive database in mind, or are you saying that the entered calendar events will reside in the CPC's own data base? Do you want a management function to off-load records from the database in an archive format (for example a CSV file), and the comparable ability to load archived records back into the system for later use? Answer: We envision a SQL database that resides on a back end SQL Server. 9. RFI Statement: CPC shall allow users to search the events database and create custom reports Question: You should list the kinds of searches you'd like to be able to do. For example, do you want to search by one or multiple fields? Any particular fields or all defined fields? Do you want to construct Boolean searches (AND, OR, NOT type operators)? Answer: This will be spelled out more in the PWS. Again, once we know what is available COTS, we'll be able to determine any needed customizations. Briefing Displays 10. RFI Statement: CPC shall allow briefing calendars with font size large enough to be viewed from a distance of twelve feet Question: On what display device should this requirement be supported? For example, an LCD projector at 1024x768 resolution projected on an 8' x 10' screen will appear much bigger than displaying a record on a 15" LCD monitor for viewing at twelve feet. Answer: Briefings will be projected from a 1024x768 LCD Projector onto a 6' x 8' screen. 11. RFI Statement: CPC shall allow events to be displayed in priority order by color code Question: Does this requirement mean that the color codes relate to the priority field? Answer: Events shall be grouped and displayed by their color. For example, absences will be red in color and displayed before conferences which are blue in color. Custom Reports 12. RFI Statement: CPC shall have the ability to customize reports so that the x-axis be labeled with the days of the month and the Y axis be labeled with different directorates (minimum35) Question: You use the plural term "reports" here and in this section. Do you have a list of reports that you require? Answer: We require one custom report at delivery plus the ability to create additional ad hoc reports as needed. 13. RFI Statement: CPC shall have the ability to customize reports so that the x-axis be labeled with the days of the month and the Y axis be labeled with different directorates (minimum35) Question: Is this the only customization you require? Or are your customization requirements more general? Answer: This is the one custom report we require at delivery. Other customization will be based on what is or is not available COTS to meet our stated requirements. General 14. RFI Statement: N/A Question: Finally, is a particular commercial, off the shelf product that you are attempting to procure here or are you looking for the development of a custom system? Answer: At this time, we are investigating possible COTS solutions which meet our requirements or will meet the requirements with minimal customization.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=65c6e9f55c676bff14ae327adde5b2e3&tab=core&_cview=1)
- Place of Performance
- Address: Peterson AFB, Colorado, 80914, United States
- Zip Code: 80914
- Zip Code: 80914
- Record
- SN01756018-W 20090226/090224221208-65c6e9f55c676bff14ae327adde5b2e3 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |