Just got a call from someone at Siemens, who wants to use MF04 to specify software. There are a couple of places for software in MF04, but I have not seen any software specifications that use MF04 and SectionFormat. Are there any out there?
Sheldon,
Can you elaborate?
He wants to specify software as a product, using CSI formats. It should be possible, but I don’t know if anyone has done it. Twenty years ago, I wrote specifications for a word processing system, including hardware, operating system, and application software. I’m sure those specs are gone, and I’m sure I would do it differently today, but I don’t see why software could not be specified in SectionFormat, in an MF04 section.
What is the software being used for?
Would their product fit into one of the following?:
25 15 00 - Building Automation Software
27 25 00 - Data Communications Software
In sections written for fire alarm integration, the functionality of the software is described in great detail. See MasterFormat Division 28 for examples. Hardware is included, too, but while software is not named (that I could see in the 2 sections I skimmed), the operations are resulting in a performance specification. It seems, though, that the software would have to be doing a specific task, not just being available for anything; although Division 27, 272500 Data Communications Software, has breakdowns for 272519 Email Software, 272523 Graphics/Multimedia Software, 272529 Operating System Software, 272533 Database Software - just to name a few.
Are you talking about writing specifications to address a team of software developers? That could take on a very different range of subjects than for constructing a building project, but there are some similarities.
PART 1 - GENERAL could address administrative requirements and goals for the system’s performance.
PART 2 - PRODUCTS could address the user interface and output of the program
PART 3 - EXECUTION could address issues regarding how the team will develop, test, debug, refine, and deliver the needed results.
Somewhere there must already be a standardized format that IT world “system architects” and analysts use to convey all this and a host of other kinds of information.
Finding an MF04 section number is not a problem, and I don’t see a big problem using SectionFormat. I just wondered if anyone had seen it done before, to use as a starting point. It’s easier to criticize than to create! 
In 1998, at the request of a C/M, I wrote a short few paragraphs for Division 01 requiring all software used in the project to be fixed for the Y2K problems that everyone expected. The only Y2K software bug I ever saw personally was at our January 2000 progress meeting at the jobsite, run by the same C/M, when he handed out logs showing us being 36,500 days late on all our submittal reviews.
Currently have a LEED project. Specified hardware (A wall mounted touch screen) and software to not only show location of room and their function but to track enviromental use of building by day, week and month.
Required coordinated with controls sections to make sure software being use by all parties was compatable and able to talk to each other.
Was give a spec by Software manufacturer in 3 part CSI format; needed some revising.
This is a significant topic if you think about software required for the BIM or even the software for typical project activities during design and construction:
- construction progress schedule
- management of submittals reviews
- management of RFIs and contract modifications
It’s not that there will be Sections written just for the required software, with Masterformat section numbers and titles assigned, but there will be articles in the applicable Sections that will specify the software.
As for data filing, well Masterformat is not supposed to be used for data filing. That’s another table under Omniclass.
we have a section that governs 3-D modeling software and translations – its a separate section in Division 1 that concerns itself with “Data Extraction, translation, transmission, exchanges” and how to make revisions and changes; we have another section that is called “Data Base Administration” that concerns itself with how the software is transmitted and stored.
even in my former office, the RFI software was regularly “negotiated” between the Architect and Contractor, because that submittal program tended to start running the administration of the project.