Market Survey - Draft Statement of Work.pdf

Market Survey - Draft Statement of Work CAEG-BIM Software& Professional Services

SCOPE:

This Market Survey – Draft Statement of Work (SOW) defines the requirements for the procurement of a complete solution for the creation, maintenance, analysis and management of Building and Facility

Engineering Drawings and Information models and associated services. The solution must include an architectural engineering software toolset that includes the ability to develop, modify and manage facility engineering drawings and building information models. The Software toolset (“Software”) must be Commercial Off-The-Shelf (COTS) and a Non-Developmental Item (NDI). This software will be integrated with other existing Federal Aviation Administration (FAA) software systems. Implementation of the new Software is expected to result in a seamless interface with facility & asset management, cost estimating and Geographic Information System (GIS) tools.

REQUIREMENTS

1.1 General Requirements

The contractor shall deliver architectural engineering development and management software, also known as the architectural engineering software toolset or software toolset, provide installation and implementation support, training, consulting and programming support in accordance with the CADD-

BIM and EDMS Specifications and operate in the environment as addressed in the provided Technical

Reference Model Information Technology (TRM IT) Standards and as defined herein. The terms software, software licenses and software applications are synonymous as used herein. The software delivered consisting of the Computer Aided Design – Building Information Modeling (CAD-BIM) and

Electronic Drawing Management Systems (EDMS) Software are also referred to as the system herein.

1.2 Technical Requirements

The contractor shall deliver an architectural engineering software toolset that meets the specification requirements as provided in CADD-BIM and EDMS Specifications and is compatible with the provided

TRM IT Standard. The software toolset delivered shall be provided in a license pool(s) rather than as static licenses assigned to individual desktops, to permit concurrent use of the software within the limits of the acquired number of licenses. The government shall have the ability to scale the number of software licenses in the license pool up or down to meet demand in accordance with government needs during the life cycle of this system. The software toolset delivered must be commercial-off-the-shelf and tailorable to government processes and provide an open architecture to allow for integration with the government’s cost accounting system software (Delphi), drafting services software (drafting tracker, a Coldfusion-based government developed software), Asset Management & Facility Management software (Archibus) and Geographic Information System (GIS) software (ESRI).

1.1.2. Architectural Engineering Software Toolset

The contractor shall deliver and architectural engineering software toolset that meets the requirement of the CADD-BIM and EDMS Specifications within 30 calendar days of contract award. The software must provide concurrent use.

1.1.3 Support Services.

The contractor shall provide installation and implementation support, training, software maintenance and hotline support, continuity of services during the implementation of the system, programming and consulting support for the successful installation and implementation of the system.

1.1.3.1 Installation & Implementation Support.

The contractor shall provide installation and implementation support as outlined in the contractor prepared plans and guides as described in the below paragraphs and upon delivery of the software toolset. The installation support shall require that the contractor work closely with the government’s IT staff to remotely deploy the software toolset and to correct any anomalies during the deployment of the same. The contractor shall also provide on-site migration services of all metadata and image files that are currently active on the FAA’s EDMS for each of the sites to operate within the software toolset provided by the contractor. The contractor must maintain continuity of services until such time that all sites are transitioned over. The implementation must be completed within 4 months.

1.1.3.1.1 Software Maintenance.

The contractor shall provide for software updates and upgrades for the software toolset delivered under the contract. All software upgrades, also known as major releases and full version releases and updates also known as point releases or point revisions, shall be made available to the government via either access and download from a secure website for the software toolset provided under the contract or via digital media or both.

1.1.3.1.2 Software Upgrades.

The contractor shall provide software upgrades that reflect improvements to the software toolset capabilities or supports new operating system releases and is available to the general public. The software upgrade shall be available to the FAA as it is made available to the general public.

1.1.3.1.3 Software Updates.

The contractor shall provide point releases and that address reported software anomalies to the government within 30 calendar days of the government’s identification of the problem or as released to the general public for all other reported software anomalies. The contractor shall provide software workarounds within 24 clock hours of a government reported issue.; software updates for the software toolset as they release them to the general public; the ability to pool, i.e. to permit concurrent usage of the software toolset rather than workstation specific use; hotline technical support; on-site technical support at the government’s request; and training for the provided software toolset. The requirement shall be extended to renamed or replaced products.

1.1.3.1.4 Software Replacements and Substitutions.

The contractor shall provide replacement software within 1 business week for all software that the contractor no longer supports. The software must offer equal or improved capabilities and must provide the same ease of use and backward compatibility with files created by the software it has replaced.

1.1.3.2. Security Certification and Accreditation Program (SCAP) Support

In accordance with FAA Order 1370.82A, Information System Security Program, the FAA must maintain, for each software, a System Certification and Authorization Package (SCAP) that documents the protocols for protecting the confidentiality, integrity, and availability of information that is collected, processed, transmitted, stored, or disseminated by the application. The Vendor must assist the FAA

Technical Team in completing the documentation required for the SCAP.

Preparation of the SCAP is the responsibility of the FAA; however, the Vendor shall be required to provide information specific to their software toolset offered under this statement of work in support of the SCAP within 1 business week of government request. The SCAP process ensures that software meets or exceeds the NIST’s minimum requirements for IT security. While the SCAP process is generally a pro forma exercise for COTS software, the Vendor understands that failure to meet NIST SCAP requirements will eliminate its product(s) from further consideration.

1.2. Documentation

The contractor shall provide access to online user and system administration reference material in support of the software toolset provided by the contractor, including replacement software upon delivery of the software.

1.3 Training

At the government’s request the contractor shall provide training for end users from contractor certified instructors for the end user provided software toolset during the normal core hours of operation as defined herein. The contractor shall also provide training for government and government support contractors and government program office designated programmers. The methods of training should include all of the following as exercised by the Government:

1.3.1 Formal Classroom

The contractor shall provide classroom training by certified instructors for the requisite software toolset at the government’s request. The contractor shall also provide training for the installed software toolset at deployment, refresher and new user as necessary. The training curriculum shall be reviewed and approved by the FAA prior to implementation. A minimum of 5 training curriculums shall be developed by the contractor and include System Administrator, FAA Certified Instructor, General User, Expert User and Computer Based Training Class developed for any training not directly provided by the contractor in a traditional classroom setting. The training shall cover all of the features and functionality provided by the software toolset and must be paced to provide sufficient time for the comprehension of software as denoted on user evaluation forms. At least, one formal class will be provided onsite or through a contractor- certified provider within 20 miles of the government address.

For onsite training, the government will provide access to the government-owned training facility and the contractor shall be responsible for setting up the requisite software toolset for the training with the government focal points’ assistance. The contractor must provide the requirements for the training set up to the locally designated government focal point at least 2 business weeks in advance of the planned on-site training. Appropriate exercises must be provided for all training offered to establish comprehension of the training material and the software toolset.

1.3.2 Optional Web-Based Self-Paced Training

The contractor shall provide the web-based, self-pased training softwarefor the software toolset offered by the contractor meeting the CAD-BIM and EDMS specification requirements to the government. The contractor shall also identify the requirements for hosting the web-based, self-paced training software and provide technical assistance in setting it up. The self-paced, i.e. recorded, training software must mimic the certified classroom instruction in content, but must also provide the ability to quickly access certain segments of the training for refresher level training. The self-paced training may be provided either on a CD/DVD or online.

1.3.3 Optional Web-Based Instructor Led Training

The contractor shall provide access to virtual `training that is offered live by the contractor for the contractor provided software toolset. The web-based instructor led training must be delivered in such a fashion that it will operate within the bandwidth limitations of the government facility and must not compromise the governments network of operations. The contractor shall identify the requirements for the conduct of the web-based instructor led training and will offer workarounds to issues with performance.

1.4 Training and User Documentation

The contractor shall provide training and user documentation as requested by the government for the software toolset provided by the contractor within 30 days of government request. Training shall be provided by contractor certified trainers for the software toolset in question. The contractor shall also provide training tailored to FAA requirements as directed by the government. Training tailored to FAA requirements may include the interaction of the contractor’s software with FAA software as adapted by the contractor. The FAA will provide the required tailoring requirements. All documentation furnished shall be in the English language.

At deployment, the contactor shall deliver three levels of documentation for each site: Users Manuals

(one for each trained user), administrators guide and programmers guide delineating the technical design and implementation of the software. Commercial Off-the-Shelf (COTS) manuals shall be provided to each site. All training manuals and reference guides shall be of professional publishing grade complete with text and illustrations directly related to the delivered and operational software toolset. All software upgrades shall come with updated documentation in accordance with stated requirements herein.

In addition, the contractor shall provide final updates to the implementation plan, the software installation guide, the software maintenance plan, the training plan and the transition plan at deployment updating the versions provided in response to the solicitation.

1.5 Implementation Documentation

The contractor shall furnish the following documentation in contractor format to assist with the installation and implementation of the provided software toolset. The documentation shall be updated after award and after surveying FAA sites to address the specific implementation details for the FAA.

1. 5.1 Implementation Plan (IP)

The contractor shall develop a draft implementation plan. The implementation plan shall fully describe all activities required to fully implement of the provided software toolset on the FAA servers. The implementation plan shall also fully describe all activities required to fully implement all of the client software under this contract using the FAA’s Marimba Deployment Tool. The plan shall also outline the development of workflow requirements within the software toolset and how to establish access privileges as per user role and responsibility and setting up the workspace within the software toolset.

These activities shall include 1) All site preparation requirements and step by step implementation procedures; 2) All resource requirements, including skill level recommendations to install, integrate, administer and maintain the software toolset and database; 3)Administrative and technical requirements for the installation and implementation of the software toolset. This shall include data formatting requirements and any recommendations for infrastructure improvements. The successful contractor will then be required to update the plans during the implementation of the software toolset.

The Draft IP shall contain but not be limited to the following requirements:

1. A pert chart outlining all of the activities leading up to the successful implementation of the all software toolset.

2. A description of all required activities to fully implement the software toolset in the format of a

Work Breakdown Structure (WBS).

3. A description of required formal Meetings and Interfaces between the contractor and the customer to transmit status and resolutions of issues.

4. Staffing to accomplish the implementation. All implementation activity must be coordinated with the IT release management.

5. The contractor shall generically describe the procedure or process to scope out the requirements for data conversion and/or re-hosting of the data and the procedure to be used to execute the data conversion or re-hosting of the data to the software toolset targeted

Relational Database Management System (RDBMS) using the contractor’s set(s) of tools.

Current table structures will be provided to the contractor.

6. Approach for designing a RDBMS structure to normalize the database and most efficiently manage the information the FAA has identified as being essential for the conduct of day-to-day business.

7. The software toolset system and non-system requirements for the Government to prepare in order to accommodate software toolset in all the sites. System requirements such as minimum and recommended requirements for hosting the software toolset within the FAA’s environment. Non-system requirements such as skill level requirements for the system administrator and prerequisite courses needed.

8. A transition procedure which delineates the vendor’s ability to implement the software toolset with a minimal loss of FAA productivity as detailed within the transition plan.

9. Information regarding how long the contractor’s proposed software toolset has been commercially available.

10. List of the contractor’s implementation management staff, key players, who have managed implementations of this magnitude and who will be available to implement the software toolset provided to the government.

1.5.2 Software Toolset Installation Guide

The contractor shall provide a software toolset installation guide which outlines the requirement for installing the software toolset to be provided under this contract.

The contractor shall provide an overview and explanation of the required staffing level, skill mix and experience that is necessary in installing the software.

The contractor shall also provide the following information:

1. For the contractor’s software toolset installation team:

A. The primary installation team staff outlined by skill mix.

B. Alternate team members also by skill mix.

C. Resumes for each of the installation team members, including alternates. The

Government reserves the right to validate information contained within each resume during the course of the evaluation process.

2. Technical and administrative support needed from the Government’s software toolset installation team. Examples may include:

A. Logical access to network and servers.

B. Hardware access to servers and desktop PC’s.

C. Database administrator(s) (DBA) access to Government existing Database (DB).

D. Preparations on data, administrative procedure and infrastructure required to convert or re-host the existing DB’s in order to populate the software toolset’s database.

3. Procedures for data formatting system requirements needed to run the all provided software:

A. Special protocols necessary for accommodating and executing the provided software toolset on the server and client side.

B. Hardware requirement such as RAM memory, and disk storage.

C. Special equipment requirements the FAA must provide for the installation of the provided software toolset.

4. Other project management requirements:

A. Organizational (functional) interface requirements to deal with issues.

B. Contingency plan detailing how the schedule can still be maintained in the event unforeseen circumstances arise which could include:

1) The shipment of defective software toolsets to the installation site(s).

2) The sudden unavailability of contractor installation personnel.

C. Conflict resolution path to ensure successful completion of the installation to the government’s satisfaction.

5. Complete step-by-step procedures for installing and adapting the server and client software

(for those solutions that require client software as part of its makeup) comprising the

Contractor’s solution.

1.5.3 Software Maintenance Plan

The contractor shall prepare a draft Software Maintenance Plan which shall contain, but not be limited to the following requirements:

1. Size and geographic presence of the maintenance work force.

2. Distribution of expertise over the geographic areas of the maintenance work force.

3. Types of expertise and their qualifications over the geographic areas of the maintenance work force.

4. Maintenance response time of trouble calls for “hot line” technical support.

5. Ability to provide real-time online troubleshooting.

6. Ability to provide web-based online informational services, i.e. FAQs.

7. Methodology used in the traceability of problems reported and solved.

8. The frequency of full upgrades.

9. The methodology the contractor shall employ to ensure and expedite the distribution of software updates and upgrades to the government.

10. Historical statistics of quantities of trouble calls/total number of seats and the total number of seats by software version of the contractor’s proposed software toolset.

11. History of the releases, timing of product releases in respect of interacting software releases, for the proposed software toolset in order to be made compatible with the software that it interfaces with.

12. Existing strategic partnerships with the various vendors of the interfacing software.

13. Corporate/government references to support all the above activities.

1.5.4 Training Plan

The contractor shall prepare a Draft Training Plan which shall contain, but not be limited to, the following requirements:

1. A general overview description of the contractor's approach to training.

2. A list of the contractor’s training courses proposed for this effort. The training courses shall address the software toolset provided in the contractor’s proposal to meet the requirements of the various users. It shall also include instructor-level training for government and government support personnel to allow them to provide for the training.

3. A complete description and syllabus for each proposed course offered.

4. List of training material and the standards by which the material has been developed.

5. Shall outline how training documentation will be furnished to the government in support of government and government support instructors.

6. The curriculum and prerequisites for each course.

7. Training goals and objectives for each and all proposed courses.

8. The training staff’s experience and qualifications. If a subcontractor provides training, the contractor shall disclose the agreement between the contractor and the subcontractor to the government. Provide resumes of all trainers (both contractor’s employee or subcontractor).

9. Schedules of all training courses to be made available to the Government expressed in terms of the timing, length and frequency of each course during the contractor’s operating year.

10. Geographic availability of training courses and whether offered on site or at Contractor’s/third party’s location for formal classroom training.

11. Agreement to customize training as required.

12. Course cancellation procedures and consequences and requirements.

13. References to support the quality level of the above training.

1.5.5 System Administration Guide

The contractor shall provide a draft system administrator’s guide containing but not limited to the following:

1. Procedures on how to backup all existing and new and application metadata

2. Procedures on recovering from a system crash

3. Procedures on how to tie the system software into a backup solution.

4. Procedures on account generation and management

5. Procedures on how to apply and manage security protocols

6. An outline in debugging system software issues.

7. Procedures on how to set up users groups

8. Procedures on how to monitor performance

9. Procedures on how to set up databases

10. Procedures on how to archive information

1.5.6 Transition Plan

The contractor shall develop a draft transition plan that shall outline the following:

1. An inventory of all of the software to be replaced.

2. An inventory of all of the software to be provided.

3. A cross reference table showing the relationship between the software to be replaced with the replacement software.

4. The actions the contractor will undertake to ensure that continuity of service is maintained during the transition to the software replacement system.

5. An elaboration of all of the critical activities that are necessary for a successful transition to the target system.

6. Detailed milestone schedule showing all activities and timing elements that are involved from transitioning from the current software to the target software. This will be referenced in the implementation plan.

1.5.7 User’s Guide

The contractor shall deliver user’s guides in contractor’s format providing a complete description for the operation of the software toolset delivered under the contract. The User’s Guides shall also include system software requirements for hosting the software toolset on servers and client workstations.

1.5.8 Training Manual

The contractor shall deliver training manuals in contractor format as part of the training provided for the software toolset offered under the contract at the time of request for training by the government.

Training manuals shall be provided in quantities required to fulfill classroom demand. Training manuals will be developed to support different competency levels for the trainees. All training manuals shall provide complete information for the operation of that software ordered by the government and shall provide exercises for each of the features supported by the software to ensure trainee comprehension.

1.5.9 Programmer’s Guide

The contractor shall deliver programmers guides, one each for each major site, in contractor format, to provide complete details for adapting software provided under the contract for the purposes of meeting unique FAA requirements. The guide shall include as a minimum every class, interface, method, constructor, parameter, and exception. The Application Program Interface (API) shall be easy to learn and use.

1.6 On-Site Support

The contractor, at the request of the government, shall provide technical onsite support to help mitigate issues with the implementation and operation of its software toolset. Operational issues will require on-site or through remote access only if they cannot be resolved by the hotline support.

Likewise, the contractor may be called upon to adapt the contractor provided software toolset or to provide for software integration support services to integrate the contractor-provided software toolset with Government-owned in-house software or to develop scripts for deployment of the software toolset remotely as part of the installation and implementation process. The services shall be furnished on a Time and Materials basis at an agreed to fixed rate for labor and not to exceed government rates for travel.

1.7 Technical Support.

The contractor shall provide help desk support to all installed government sites during the core business hours as 8:00 AM to 5:00 PM CT, Monday through Friday. The contractor shall establish a written service level agreement with the government addressing issues relative to support availability, response time as per the specification requirements, response procedures, critical elevations based on situation, on site response requirements, corrective and preventive maintenance requirements, software toolset and operating system upgrade synchronization requirements, maintenance log, maintenance and support organization and any other requirements the contractor deems necessary. The support plan shall be completed for government review and made available prior to contract award. Help Desk -

Technical support will be principally managed by FAA personnel. The Contractor must be able to provide second-level technical support across the country. Contractor to provide phone support for the following:

a) User application questions and bug reports.

b) Software application issues with respect to co-existing applications, PC environment, and server issues.

3. Delivery Sites.

The following sites are to receive the software and services as part of the contract:

• Anchorage, AK

• Kansas City, MO

• Jamaica, NY

• Des Plaines, IL

• Burlington, MA/Nashua, HN

• Renton, WA

• College Park, GA

• Fort Worth, TX

• Lawndale, CA

• Washington, DC

• Atlantic City, NJ

• Silver Spring, MD

• Oklahoma City, OK